Distributed system, aircraft, method and program

JP2022113755A5Active Publication Date: 2024-11-01ベネデック アーロン サンジャヤ
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022091536
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-10-27
Filing Date
2022-06-06
Publication Date
2024-11-01
Estimated Expiration
2041-10-27

AI Technical Summary

Technical Problem

Flying objects such as drones and flying cars face challenges in safely changing direction or making emergency landings without colliding with other objects during flight, as existing technologies do not adequately manage spatial reservations and collisions.

Method used

A flight management device that selects and reserves specific spatial cells for flying objects based on reservation status, permitting or denying movement to ensure safe flight paths by communicating with aircraft to avoid collisions and adjust routes as needed.

Benefits of technology

Enhances the safety of flying objects by preventing collisions and ensuring safe flight paths through dynamic route adjustments and spatial cell management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

An object of the present disclosure is to provide a flight management device that can improve the safety of an aircraft. [Solution] As an example, the flight management device (10) of the present disclosure includes a determination unit (12) that, when receiving a request from an aircraft requesting permission to move to a specific spatial cell in space, determines whether the specific spatial cell has already been reserved based on the reservation status of the specific spatial cell, and a permission unit (13) that, when the determination unit determines that the specific spatial cell is not reserved, allows the aircraft to move to the specific spatial cell, and does not allow the aircraft to move to the specific spatial cell, when the determination unit determines that the specific spatial cell is already reserved.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] This disclosure relates to a flight management device, an aircraft, a flight management system, a distributed system, a flight management method, a flight control method, and a program. [Background technology]

[0002] Recently, technologies related to flying vehicles such as drones and flying cars have been advancing. For example, Patent Document 1 discloses a path control device that determines the route of a moving object represented by a block, which is a divided space. Specifically, when there is a common block in the movement paths of multiple moving objects, the path control device changes the movement path of one of the multiple moving objects so that it does not pass through that common block during the common time period. In this way, the path control device generates the movement paths of the moving objects.

[0003] Patent Document 2 discloses another related technology in which, when a management module receives a request from a mobile drive unit to reserve a destination segment, it reserves that segment for that mobile drive unit. This reservation process prevents collisions between mobile drive units.

[0004] Furthermore, Patent Document 3 discloses that a central station reserves a destination zone for a mobile drive unit and operates as a spatial allocator. [Prior art documents] [Patent Documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2019-066381 [Patent Document 2] U.S. Patent No. 7912574 [Patent Document 3] U.S. Patent No. 10591931 [Overview of the project] [Problems that the invention aims to solve]

[0006] Aircraft such as drones and flying cars may need to change direction or make emergency landings during flight. In such cases, management methods are desirable to guide the aircraft to maintain a safe distance from other aircraft and ensure safe flight.

[0007] This disclosure aims to provide a flight management device, an aircraft, a flight management system, a distributed system, a flight management method, a flight control method, and a program that can improve the safety of an aircraft. [Means for solving the problem]

[0008] In a first exemplary aspect, the flight management device includes a receiving unit that receives a request from one of a plurality of aircraft for permission to move to a specific spatial cell in the space along the flight route of the first aircraft determined by the first aircraft; a determination unit that, when the receiving unit receives the request, determines, based on the reservation status of the specific spatial cell, whether the specific spatial cell is already reserved by another of the plurality of aircraft; and a permission unit that, if the determination unit determines that the specific spatial cell is not reserved by another aircraft, permits the first aircraft to move to the specific spatial cell, and does not permit the first aircraft to move to the specific spatial cell if the determination unit determines that the specific spatial cell is already reserved by another aircraft.

[0009] In a second exemplary aspect, the aircraft includes a request generation unit that determines its own flight route and generates a request for permission to move to a specific spatial cell in the space along the flight route; a transmission unit that transmits the request generated by the request generation unit to a flight management device; and a flight control unit that moves the aircraft to the specific spatial cell when permission information is received from the flight management device that permits movement to the specific spatial cell, and does not move the aircraft to the specific spatial cell when permission information is received from the flight management device that does not permit movement to the specific spatial cell, wherein the request generation unit updates the flight route based on the permission information received from the flight management device.

[0010] In a third exemplary aspect, the flight management system comprises a plurality of aircraft and a flight management device for managing the plurality of aircraft, each of which has a request generation unit that determines its own flight route and generates a request for permission to move to a specific spatial cell in the space along the flight route, and a request transmission unit that transmits the request generated by the request generation unit to the flight management device, the flight management device having a receiving unit that receives the request from one of the plurality of aircraft, a determination unit that, when the receiving unit receives the request, determines, based on the reservation status of the specific spatial cell, whether the specific spatial cell is already reserved by another of the plurality of aircraft, and a permission unit that, if the determination unit determines that the specific spatial cell is not reserved by another aircraft, permits the one aircraft to move to the specific spatial cell, and if the determination unit determines that the specific spatial cell is already reserved by another aircraft, does not permit the one aircraft to move to the specific spatial cell.

[0011] In a fourth exemplary aspect, the distributed system comprises a plurality of aircraft, each of which has a communication unit that communicates with other aircraft using a peer-to-peer communication method to form a distributed system including itself and the other aircraft, and a ruling unit that causes the communication unit to transmit its vote for a specific spatial cell in space, which is weighted according to a predetermined order, to the other aircraft, and the ruling unit of the aircraft that transmits the heaviest weighted vote performs a ruling on which aircraft to assign the specific spatial cell to.

[0012] In a fifth exemplary aspect, the flight management method receives a request from one of a plurality of aircraft to grant permission for the first aircraft to move to a specific spatial cell in the space along the flight route of the first aircraft that has been determined. Based on the reservation status of the specific spatial cell, the method determines whether the specific spatial cell is already reserved by another of the plurality of aircraft. If it is determined that the specific spatial cell is not reserved by another aircraft, the method grants permission for the first aircraft to move to the specific spatial cell. If it is determined that the specific spatial cell is already reserved by another aircraft, the method does not grant permission for the first aircraft to move to the specific spatial cell.

[0013] In a sixth exemplary aspect, the flight control method determines its own flight route, generates a request for permission to move to a specific spatial cell in the space along the flight route, transmits the request to a flight management device, moves the aircraft to the specific spatial cell if the specific spatial cell is not reserved by another aircraft and permission information is received from the flight management device granting permission to move to the specific spatial cell, and controls the aircraft not to move to the specific spatial cell if the specific spatial cell is already reserved by another aircraft and disapproval information is received from the flight management device denying permission to move to the specific spatial cell, and updates the flight route based on the disapproval information received from the flight management device.

[0014] In the seventh exemplary aspect, the program receives a request from one of a plurality of aircraft to ask for permission to move to a specific spatial cell in space along the flight route of the first aircraft that has been determined. Based on the reservation status of the specific spatial cell, the program determines whether the specific spatial cell is already reserved by another of the plurality of aircraft. If it is determined that the specific spatial cell is not reserved by another aircraft, the program allows the first aircraft to move to the specific spatial cell. If it is determined that the specific spatial cell is already reserved by another aircraft, the program denies the first aircraft to move to the specific spatial cell.

[0015] In the eighth exemplary aspect, the program determines its own flight route, generates a request for permission to move to a specific spatial cell in the space along the flight route, transmits the request to a flight management device, moves the aircraft to the specific spatial cell if the specific spatial cell is not reserved by another aircraft and permission information is received from the flight management device granting permission to move to the specific spatial cell, controls the aircraft not to move to the specific spatial cell if the specific spatial cell is already reserved by another aircraft and disapproval information is received from the flight management device denying permission to move to the specific spatial cell, and causes the computer to update the flight route based on the disapproval information received from the flight management device. [Effects of the Invention]

[0016] This disclosure provides a flight management device, an aircraft, a flight management system, a distributed system, a flight management method, a flight control method, and a program that can improve the safety of an aircraft. [Brief explanation of the drawing]

[0017] [Figure 1] This is a block diagram of the flight management device 10 according to Embodiment 1. [Figure 2] This is a schematic diagram of multiple spatial cells according to Embodiment 1. [Figure 3] This is a flowchart showing the method executed by the flight management device 10 according to Embodiment 1. [Figure 4] This is a block diagram of the flight management system M1 according to Embodiment 1. [Figure 5] This is a block diagram of the flight management device 30 according to Embodiment 2. [Figure 6] This is a block diagram of the flying vehicle 40 according to Embodiment 2. [Figure 7] This is a block diagram of the flight management device 50 according to Embodiment 3. [Figure 8] This is a block diagram of the flying vehicle 60 according to Embodiment 3. [Figure 9] This is a sequence diagram showing the processes performed by the flight management system F3 according to Embodiment 3. [Figure 10A] This is an example of a schematic diagram showing the space cell C1 and its surrounding space cells while the flying object 60 according to Embodiment 3 is in flight. [Figure 10B] This is another example of a schematic diagram showing the space cell C1 and its surrounding space cells while the flying object 60 according to Embodiment 3 is in flight. [Figure 11] This is a schematic diagram showing the movement path of an aircraft 60 using the spatial cell reservation method according to Embodiment 3. [Figure 12] This is a block diagram of the flying object 60 according to Embodiment 4. [Figure 13] This is a block diagram of the flight management device 50 according to Embodiment 5. [Figure 14] This is a first schematic diagram illustrating the traffic management method according to Embodiment 5. [Figure 15] This is a schematic diagram showing the plane P1 and lanes D11 to D14 according to Embodiment 5. [Figure 16] This is a schematic diagram showing an example of a flight path in Embodiment 5 when an aircraft flies from a ground departure point D to a destination E. [Figure 17] This is a schematic diagram showing a set of planes in Embodiment 5. [Figure 18]This is a second schematic diagram illustrating the traffic management method according to Embodiment 5. [Figure 19] This is a third schematic diagram illustrating the traffic management method according to Embodiment 5. [Figure 20A] This is an example of a schematic diagram showing lane D102 according to Embodiment 5. [Figure 20B] This is another example of a schematic diagram showing lane D102 according to Embodiment 5. [Figure 21] This is a schematic diagram showing the traffic conditions in plane P9 after some time has passed since Figure 19, according to Embodiment 5. [Figure 22] This is a fourth schematic diagram illustrating the traffic management method according to Embodiment 5. [Figure 23] This is a fifth schematic diagram illustrating the traffic management method according to Embodiment 5. [Figure 24] This is a schematic diagram of the system configured by connecting multiple flight management devices in Embodiment 7. [Figure 25A] This is a first schematic diagram showing a method for dividing space in Embodiment 8. [Figure 25B] This is a second schematic diagram showing the method of dividing space in Embodiment 8. [Figure 26] This is a block diagram of the flight management device 70 according to Embodiment 9. [Figure 27] This is a block diagram of the flying vehicle 80 according to Embodiment 9. [Figure 28A] An example of the space in which the flying object 40 according to Embodiment 11 is located is shown. [Figure 28B] This is a top view of the determined route according to Embodiment 11. [Figure 28C] This is a side view of the determined route according to Embodiment 11. [Figure 28D] This figure shows the spatial cell to be reserved according to Embodiment 11. [Figure 29A] This is a schematic diagram of spacetime according to Embodiment 11. [Figure 29B]This is a first schematic diagram showing the flight path taken by the aircraft in Embodiment 11. [Figure 29C] This is a second schematic diagram showing the flight path taken by the aircraft in Embodiment 11. [Figure 29D] This is a schematic diagram showing the spatial cells assigned as flight routes along each sub-route in Embodiment 11. [Figure 30A] This is a schematic diagram showing the space-filling structure in Embodiment 12, where the space cell is a regular hexagonal prism. [Figure 30B] This is a schematic diagram illustrating the advantages of using a regular hexagonal prism as the spatial cell in Embodiment 12. [Figure 30C] This is a schematic diagram showing the space-filling structure in Embodiment 12 when the space cell is a regular triangular prism. [Figure 31] This is a block diagram of the flying object 40' according to Embodiment 13. [Figure 32A] This is a first schematic diagram showing the positions of multiple flying objects in space in Embodiment 13. [Figure 32B] This is a second schematic diagram showing the positions of multiple flying objects in space in Embodiment 13. [Figure 32C] This is a schematic diagram showing the ruling in space between two aircraft in Embodiment 13. [Figure 32D] This is a schematic diagram showing the ruling within space of four aircraft in Embodiment 13. [Figure 32E] This is a schematic diagram illustrating the ruling in the space surrounding the airport for two aircraft in Embodiment 13. [Figure 32F] This is a block diagram of the flight management system M2 according to Embodiment 13. [Figure 32G] This is a schematic diagram of a system that includes two spatial regions and another spatial region managed by multiple flight control devices. [Figure 33A] This is a block diagram of the flight management system M3 according to Embodiment 14. [Figure 33B]This is a block diagram of the flying object 60' according to Embodiment 14. [Figure 33C] This is a schematic diagram showing an example of the state of a spatial cell in an encrypted space and in real space according to Embodiment 14. [Figure 34] This is a block diagram showing an example of the hardware configuration of a flight management system, aircraft, or regional controller server. [Modes for carrying out the invention]

[0018] Embodiment 1 (1-1) Embodiment 1 of this disclosure will be described below with reference to the drawings.

[0019] Figure 1 is a block diagram of the flight management system 10. The flight management system 10 includes a memory 11, a determination unit 12, and a permission unit 13. The flight management system 10 can be composed of a general-purpose computer and can be applied as a controller device, an air traffic control device, etc. The details of each part of the flight management system 10 will be described below.

[0020] Memory 11 stores the reservation status of multiple space cells for multiple aircraft in a divided space. The multiple aircraft are managed by the flight management device 10 and fly within the multiple space cells. The aircraft are any flyable devices such as drones, flying cars, and airplanes.

[0021] Figure 2 is a schematic diagram of multiple spatial cells, which are divided spaces. Space S is divided into multiple cubic spatial cells C, each with a side length A, to manage the flight of multiple aircraft. Each spatial cell C is adjacent to another spatial cell in six directions in three-dimensional space. In addition, each spatial cell C is set up to be continuous with another spatial cell C so that the flight management device 10 can recognize the position of the aircraft. The aircraft 60 flies through space S by moving from one spatial cell C to an adjacent spatial cell C that faces the previous spatial cell C. In this case, one aircraft is permitted to reserve one spatial cell C. That is, only one aircraft is permitted to fly in one spatial cell C.

[0022] The reservation status of spatial cell C includes at least the location information of the spatial cell C being reserved. Furthermore, a reserved spatial cell C means, for example, that it is a spatial cell that an aircraft is currently or will be flying to in the future. However, spatial cell C may also be reserved for objects other than aircraft.

[0023] The flight management device 10 can identify each spatial cell C, for example, by spatial coordinates. Furthermore, if a building or other structure exists within space S and an area where flight is impossible occurs, the flight management device 10 may store that area as a no-fly zone in memory 11. A no-fly zone may be, for example, a spatial cell that is entirely or partially occupied by a building, or an area classified as a no-fly zone, and may also include nearby spatial cells (for example, adjacent spatial cells) to such a spatial cell.

[0024] In Figure 2, space S is divided into six equal parts in the x, y, and z directions by space cells C, but the method of dividing space S in each direction is not limited to this. The side length A of space cell C may be constant, or as described later, the flight control device 10 may change depending on the situation. Also, space cell C does not have to be a cube; it may be a rectangular prism, a sphere, or other three-dimensional shape, as long as it fills space S.

[0025] Returning to Figure 1, let's continue the explanation. When the determination unit 12 receives a request from one of the multiple aircraft to ask for permission to move to a specific spatial cell, it uses the reservation status stored in memory 11 to determine whether the specific spatial cell is already reserved. The specific spatial cell is considered already reserved if another aircraft is flying in the specific spatial cell or moving toward it.

[0026] The permission unit 13 permits the aircraft to move to a specific spatial cell if the determination unit 12 determines that the specific spatial cell is not reserved. This is because, if the specific spatial cell is not reserved, it is considered that the aircraft will not come into contact with other aircraft even if it moves to that specific spatial cell. However, if the determination unit 12 determines that the specific spatial cell is reserved, it does not permit the aircraft to move to that specific spatial cell. This is because, if the specific spatial cell is reserved, there is a possibility that the aircraft will come into contact with other aircraft if it moves to that specific spatial cell.

[0027] Figure 3 is a flowchart showing the flight management method performed by the flight management device 10. The method performed by the flight management device 10 will be explained below using Figure 3.

[0028] First, the flight management device 10 stores the reservation status of multiple spatial cells C in the memory 11 (step S11). For example, the flight management device 10 may decide that the spatial cells requested by the aircraft are reserved and the other spatial cells are unreserved, and store the reservation status. Alternatively, or in combination with the above method, the flight management device 10 may decide that the spatial cells that the aircraft cannot fly to are reserved and the other spatial cells are unreserved, and store the reservation status. "Spatial cells that the aircraft cannot fly to" are, but are not limited to, areas where flight is restricted due to the presence of buildings, areas where general aircraft flight is restricted because the passage of emergency aircraft is expected, etc.

[0029] Next, when the determination unit 12 receives a request from the aircraft for permission to move to a specific spatial cell, it uses the reservation status stored in the memory 11 to determine whether the specific spatial cell is already reserved (step S12). For example, the aircraft and the flight management device 10 may recognize the spatial cells in a common coordinate system. When the aircraft transmits the coordinates of the specific spatial cell to be reserved to the flight management device 10, the flight management device 10 recognizes the specific spatial cell to be determined based on the transmitted coordinates.

[0030] Then, if the determination unit 12 determines that a specific spatial cell is not reserved (No. in step S12), the permission unit 13 permits the aircraft to move to the specific spatial cell (step S13). In this case, the flight management device 10 can transmit permission information to the aircraft that sent the request, permitting its movement. The flight management device 10 can transmit permission information using, for example, a communication circuit (not shown).

[0031] On the other hand, if the determination unit 12 determines that a specific spatial cell is reserved (No. in step S12), the permission unit 13 does not permit the aircraft to move to that specific spatial cell and denies it (step S14).

[0032] In step S13, the flight management device 10 may transmit permission information to the aircraft that sent the request, granting it permission to move. Similarly, in step S14, the flight management device 10 may transmit denial information (denial information) to the aircraft that sent the request, denying it permission to move. The flight management device 10 may transmit permission or denial information using, for example, a communication circuit (not shown).

[0033] As described above, the flight management device 10 can, in response to a request from an aircraft, permit or deny the aircraft to move to the space cell where it is scheduled to fly. For example, even if an aircraft changes direction during flight or makes an emergency landing, the flight management device 10 can deny the aircraft's movement if the space cell to which the aircraft suddenly needs to move is already reserved. Therefore, the aircraft is prevented from coming into close proximity with other aircraft, allowing it to fly safely.

[0034] The determination unit 12 may determine whether a particular spatial cell is in a no-fly zone in parallel with or before / after the processing of step S12. If a particular spatial cell is in a no-fly zone, the permission unit 13 will not permit the aircraft to move to that particular spatial cell and will refuse. Therefore, the aircraft will be prevented from approaching the building, allowing for safe flight.

[0035] Furthermore, the reservation status may indicate whether a reservation exists for all space cells in space S, or it may indicate whether a reservation exists for a portion of the space, including the space cell requested by the aircraft. In addition, the reservation status may be input to the flight management device 10 from an external source, rather than being stored in the memory 11 of the flight management device 10.

[0036] (1-2) This section describes a flight management system according to Embodiment 1. Figure 4 is a block diagram of the flight management system M1. The flight management system M1 comprises a flight management device 10 and a plurality of aircraft 20. The configuration of the flight management device 10 is as described above, so its explanation is omitted.

[0037] Each aircraft 20 includes a request generation unit 21, a transmission unit 22, and a flight control unit 23. Multiple aircraft 20 can communicate with the flight management device 10 by being pre-registered with the flight management device 10 by an operator, for example. The aircraft 20 are appropriately equipped with an engine unit for flight or a buoyancy generating unit such as a propeller, but these will not be described in detail here. Communication between the flight management device 10 and the aircraft 20 can be carried out, for example, by a dedicated protocol.

[0038] The request generation unit 21 generates a request for permission to move to a specific spatial cell among multiple spatial cells. The "specific spatial cell" may be a spatial cell adjacent to the spatial cell in which the aircraft 20 is currently flying, or it may not be a spatial cell adjacent to the spatial cell in which the aircraft 20 is currently flying.

[0039] The transmitting unit 22 is capable of communicating with the flight management device 10 and transmits the request generated by the request generation unit 21. During normal flight, the aircraft 20 may determine the next destination space cell and transmit a request for permission to move to that space cell using the transmitting unit 22. Alternatively, if the aircraft 20 recognizes that an exceptional situation has occurred and decides to head to a different space cell instead of the space cell on the planned route, it may transmit a request for permission to move to that space cell using the transmitting unit 22.

[0040] Upon receiving a request from the aircraft 20, the flight management device 10 uses the reservation status stored in memory 11 to determine whether a particular spatial cell is already reserved. Based on the reservation status, it then permits or denies the aircraft's movement to that spatial cell. The details of this process are as described above.

[0041] In response to a request, if the aircraft 20 receives permission information from the flight management device 10 to move to a specific spatial cell, the flight control unit 23 moves the aircraft 20 to that specific spatial cell. However, if the aircraft 20 receives denial information that does not permit movement to the specific spatial cell, the flight control unit 23 does not move the aircraft to that specific spatial cell. The flight control unit 23 moves the aircraft by controlling the engine unit and buoyancy generation unit as described above.

[0042] By performing this flight control method, the aircraft 20 can fly safely. The spatial cell that the aircraft 20 requests may be one or multiple cells.

[0043] Embodiment 2 (2-1) Embodiment 2 of this disclosure will be described below with reference to the drawings. Embodiment 2 describes an embodiment in which a flight management device or an aircraft determines the flight route of the aircraft according to various circumstances. The flight route is navigational information indicating which spatial cell C the aircraft will fly through and when, and is represented by a combination of positional information and time information.

[0044] Figure 5 is a block diagram of the flight management device 30. The flight management device 30 includes a memory 31, a data acquisition unit 32, a route generation unit 33, and a transmission unit 34.

[0045] Memory 31 stores multiple spatial cells C that divide the space S managed by the flight management device 30 in a format that can be identified by coordinates, etc. Memory 31 may also store the flight routes of each aircraft generated by the route generation unit 33. Furthermore, if buildings or other structures exist within space S and an area becomes unflyable, the flight management device 30 may store that area as an unflyable area in memory 31.

[0046] Furthermore, memory 31 may also store the reservation status of space cells of multiple aircraft, similar to memory 11. The reservation status stored here may include not only the location information of the space cell C to be reserved, but also information about the time period in which space cell C is reserved.

[0047] The data acquisition unit 32 acquires data used to determine the flight route of the aircraft and is composed of, for example, a communication unit that performs communication with the aircraft or an external network. The data acquired includes at least one of the following: the departure and destination points of the flight route, the remaining amount of resources necessary for the aircraft's flight, the aircraft's priority, and weather information between the departure and destination points. The remaining amount of resources necessary for the aircraft's flight will be described below as battery level, but it may also be other things such as fuel level. In addition to the above, the data acquisition unit 32 can acquire identification information of the aircraft and position information of the aircraft from satellite positioning systems such as GPS (Global Positioning System), but the information that the data acquisition unit 32 can acquire is not limited to these. The data acquisition unit 32 can acquire telemetry data related to the aircraft's main body and internal equipment, such as battery level, from the aircraft via communication.

[0048] For example, the data acquisition unit 32 acquires information from the aircraft targeted for flight route generation, including the departure point (current location) and destination of the itinerary, as well as battery level and aircraft priority, before the aircraft takes off from the departure point. Furthermore, the data acquisition unit 32 may periodically or intermittently acquire real-time data from the aircraft during flight, including battery level and current speed. In addition, weather information between the departure point and destination can be obtained through communication with an external network.

[0049] The priority of an aircraft has the following meanings. For example, if an aircraft has a "high" priority and another aircraft has a "low" priority, and the flight route of one aircraft overlaps with the flight route of the other aircraft, then the aircraft can fly with priority over the other aircraft (for example, earlier in time) at least for the overlapping section. However, if an aircraft has a "low" priority, it cannot fly with priority over the other aircraft (for example, earlier in time). Priority is an aircraft property that can be used to determine the allocation status of a particular space cell, the number of space cells that can be allocated, etc., as described later. An aircraft with a "high" priority is, for example, an aircraft used for emergency or important purposes such as police, fire, and ambulance services, while an aircraft with a "low" priority is an aircraft used for general purposes. The flight management device 30 may also set the priority of an aircraft 40 with a battery level below a predetermined value to "high" and the priority of other aircraft 40 to "low".

[0050] The route generation unit 33 is a navigation unit that determines the flight route for each aircraft using information stored in the memory 31 and data acquired by the data acquisition unit 32. Ideally, the flight route for each aircraft should be configured such that the spatial cells, excluding areas where flight is prohibited, are connected by the shortest distance from the aircraft's departure point to its destination. However, for safety reasons, it is preferable that the flight route for each aircraft is set so as not to be too close to the flight routes of other aircraft. In other words, it is preferable to prevent near misses. Here, a near miss may mean that two aircraft are within a predetermined distance of each other, or it may mean that two aircraft are in a predetermined spatial cell at the same time. The route generation unit 33 may also generate flight routes so that the aircraft's flight route does not result in a near miss by using the already generated flight routes of other aircraft stored in the memory 31.

[0051] Furthermore, the route generation unit 33 may use the reservation status of the spatial cells C stored in memory 31 to generate the flight route of an aircraft so that it does not overlap with the reserved spatial cells of other aircraft. Note that "the flight route does not overlap with the reserved spatial cells" may mean, for example, that the flight route does not pass through any reserved spatial cells.

[0052] Furthermore, if the stored reservation status includes information about the time period in which spatial cell C is reserved, the route generation unit 33 may generate a flight route that avoids the time period in which the spatial cell is reserved if the flight route passes through a reserved spatial cell. To ensure the safety of the aircraft, it is preferable to set a margin time between the time period in which the flight route passes through a reserved spatial cell and the time period in which that spatial cell is reserved.

[0053] Furthermore, depending on factors such as the aircraft's battery level and weather conditions, it may be desirable to set a route other than the shortest distance. For example, if it is predicted that another flight route will consume less battery power than the shortest distance flight route, the route generation unit 33 can set the latter flight route. For example, if the aircraft's battery level is below a predetermined value, the route generation unit 33 may calculate the battery power consumption of each candidate flight route and select the flight route with the lowest battery power consumption. The route generation unit 33 may also predict battery power consumption using the flyable area of ​​space S (excluding the unflyable area) stored in memory 31, and weather information between the departure point and the destination (for example, whether or not there is rainfall, and wind speed and direction information).

[0054] Furthermore, depending on the weather, it is conceivable that the travel time from the departure point to the destination may be shorter on an alternative flight route compared to the shortest flight route. In such cases, the route generation unit 33 can also set the latter flight route.

[0055] Furthermore, if there are buildings or other structures between the departure point and the destination, and winds that may interfere with flight are generated, the route generation unit 33 may also take the influence of the buildings into consideration and derive a route that avoids the winds generated by the buildings, or a route in which the winds are avoided by the buildings.

[0056] Furthermore, the flight route generation method described above can be changed depending on whether the priority of the aircraft is high or low. When the priority of the aircraft for which flight route generation is to be performed is "high", the route generation unit 33 can derive one of the following flight routes: the shortest distance, the flight route with the lowest battery consumption, or the flight route with the shortest required time. In other words, the flight route of an aircraft with "high" priority can be set with priority over the flight route of an aircraft with "low" priority.

[0057] In this case, for aircraft with a "low" priority that would have a near miss with the flight route already set, the route generation unit 33 resets the flight route. Furthermore, for aircraft with a "low" priority, the reservation of the spatial cell where the near miss occurred is canceled. If a derived flight route would have a near miss with the flight route of an already set aircraft with a "high" priority, the route generation unit 33 modifies the derived flight route to avoid the near miss.

[0058] The route generation unit 33 can generate a flight route for each aircraft using one or more pieces of information from among the already generated aircraft flight routes, the reservation status of space cell C, the aircraft's battery level, weather information, and aircraft priority. The transmission unit 34 transmits the generated flight route information to the aircraft. The aircraft flies from the departure point to the destination using the transmitted flight route. The flight routes generated by the route generation unit 33 are stored in the memory 31.

[0059] The flight management device 30 may generate or update the current position and the flight route to the destination not only when the aircraft for which the flight route is to be generated is stationary on the ground, but also when it is in flight. For example, the aircraft may be equipped with sensors capable of measuring rainfall, or wind speed and wind direction information, and the flight management device 30 may acquire the information obtained from these sensors via the aircraft's communication unit. The aircraft may also transmit its battery level to the flight management device 30.

[0060] The route generation unit 33 of the flight management device 30 can generate or update the flight route for each aircraft using one or more pieces of information from among the already generated aircraft flight routes, the reservation status of space cell C, the aircraft's battery level, weather information, and aircraft priority. The flight route generated or updated here may, for example, be the one that minimizes battery consumption or travel time from the aircraft's current position to its destination. Furthermore, even if at least one of the flight routes of other aircraft stored in memory 31 or the reservation status of space cell C is updated, causing the target aircraft's flight route to become a near miss, the flight management device 30 can update the flight route.

[0061] (2-2) Here, we will describe an example in which the aircraft itself generates its own flight route, rather than a flight management system. Figure 6 is a block diagram of the aircraft 40. The aircraft 40 includes a memory 41, a data acquisition unit 42, a route generation unit 43, a transmission unit 44, and a flight control unit 45.

[0062] Memory 41 stores multiple spatial cells C that divide the space S in which the aircraft is flying, in a format that can be identified by coordinates, etc. Furthermore, if buildings or other structures exist within space S and an area becomes unflyable, the flight management device 30 may store that area as an unflyable area in memory 31. In addition, memory 41 may also store the remaining amount of resources necessary for the aircraft's flight and the priority of the aircraft 40.

[0063] The data acquisition unit 42 acquires data used to determine the flight route of the aircraft, and is composed of at least one of the following: a sensor, an input unit, or a communication unit that performs communication with an external network. For example, the data acquisition unit 42 can acquire weather information between the departure point and the destination by detection by a sensor or by communication with an external network. The data acquisition unit 42 can also acquire telemetry data related to the aircraft's body and internal equipment, such as battery level, from the aircraft's sensors. The data acquisition unit 42 may also acquire information such as the priority of the aircraft 40 from the memory 41. Furthermore, if the aircraft 40 is a vehicle that can carry a person, the aircraft 40 can acquire information by having the user input information about the departure point and destination of the flight route.

[0064] Furthermore, the data acquisition unit 42 may, through communication with the flight management device, acquire at least one of the flight routes of other aircraft or the reservation status of the spatial cells of other aircraft stored in the flight management device.

[0065] The route generation unit 43 is a navigation unit that determines the flight route of the aircraft 40 using the information stored in the memory 41 and the data acquired by the data acquisition unit 42. The details of the determination method are as described in (2-1), so the explanation is omitted here.

[0066] The transmitting unit 44 transmits the flight route information generated by the route generation unit 43 to the flight management device. The flight management device stores the flight route information in its memory unit. The flight control unit 45 controls the movement of the aircraft 40, similar to the flight control unit 23.

[0067] Furthermore, the aircraft 40 may generate or update a flight route to its destination not only when the aircraft whose flight route is to be generated is stationary on the ground, but also while it is in flight. For example, the aircraft 40 may be equipped with a sensor capable of measuring rainfall or wind speed and wind direction information, and the aircraft 40 may acquire weather information from that sensor while in flight. Also, if at least one of the flight routes of other aircraft stored in the memory unit of the flight management device, or the reservation status of space cell C, is updated and the flight route of the aircraft 40 becomes a near miss, the flight management device transmits information to the aircraft 40 indicating this. The aircraft 40 receives this information from the flight management device and can update its own flight route based on the received information.

[0068] As described above, the flight management device 30 or the aircraft 40 can set the flight route of the aircraft according to information such as weather and the reservation status of space cells. Therefore, the flight management device 30 or the aircraft 40 can set the optimal flight route in terms of safety, duration, battery consumption, etc.

[0069] Furthermore, the aircraft may send a request to the flight management device for permission to move to a spatial cell C on the set flight route, as shown in (1-2). The flight management device will then decide whether to grant or deny permission to move to the spatial cell in response to the request. The configuration and processing of the flight management device for performing this decision are as described in Embodiment 1.

[0070] Here, an aircraft may reserve all the spatial cells along its flight route in a single request, or it may reserve only some of the spatial cells along its flight route. For example, an aircraft can reserve the spatial cell at its current position and one or more spatial cells along the planned route for its flight. "One or more spatial cells along the planned route" may be only the adjacent spatial cells to the current spatial cell, or it may include spatial cells adjacent to those adjacent cells, and so on, up to N (N>1) spatial cells along the flight route.

[0071] However, if an aircraft has a "high" priority, the number of spatial cells along the flight route reserved in a single request may be increased compared to when the priority is "low". For example, if an aircraft has a "high" priority, when a flight route is set, a request may be sent to reserve all spatial cells along the flight route. This allows for the determination of flight routes for high-priority aircraft and enables such aircraft to fly without disruption.

[0072] Furthermore, in (2-1), if the priority of the aircraft setting the flight route is "high", the flight management device 30 may perform reservation processing for all spatial cells on the flight route at the time the route generation unit 33 generates the flight route. Similarly, in (2-2), if a flight route is transmitted from an aircraft 40 with a "high" priority, the flight management device may perform reservation processing for all spatial cells on the flight route.

[0073] The flight management device 30 may include information about the time period during which a space cell is reserved in the reservation status of the space cell. For example, the flight management device 30 may set the time period during which a space cell is reserved to be the time period before and after the time when an aircraft passes through that space cell, plus a margin of time. For example, if the time it takes for an aircraft to pass through one space cell is t, and the time when the aircraft arrives at that space cell is t0, the flight management device 30 may set the margin to t and configure the system so that the space cell is reserved from the time t0-t. This ensures the safety of the aircraft because when the aircraft reaches the space cell before the space cell it is heading to, there will be no other aircraft in the space cell that is the aircraft's next destination.

[0074] The flight management device 30 may increase the margin when the priority of the aircraft reserving the space cell is high compared to when it is low (for example, the margin may be 2t in the former case and t in the latter case). The flight management device 30 may also change the length of the margin based on weather information. For example, the flight management device 30 may increase the margin when the weather information acquired by the data acquisition unit 32 is rainy compared to when it is sunny. Also, the margin may be increased when the wind speed is above a predetermined value compared to when it is below a predetermined value. The margin may be set to increase continuously or stepwise in response to the increase in wind speed.

[0075] In the following embodiments, detailed specific examples of the processes performed in Embodiments 1 and 2 will be further described. It goes without saying that the technical features described in the following embodiments can be combined as appropriate.

[0076] Embodiment 3 Embodiment 3 of this disclosure will be described below with reference to the drawings. In this embodiment, a more specific process will be described with respect to (1-2). The flight management device 50 and the plurality of aircraft 60 shown below constitute the flight management system F3.

[0077] Figure 7 is a block diagram of the flight management device 50. The flight management device 50 includes a memory 51, a data acquisition unit 52, a route generation unit 53, a communication unit 54, a determination unit 55, and a permission unit 56.

[0078] Memory 51 stores information on multiple spatial cells C that can be identified by coordinates, the reservation status of the spatial cells of multiple aircraft, the flight routes of each aircraft generated by the route generation unit 53, and the reservation status of the spatial cells.

[0079] The data acquisition unit 52 acquires various data used to determine the flight route of an aircraft, similar to the data acquisition unit 32. The route generation unit 53, similar to the route generation unit 33, uses the information stored in the memory 51 and the data acquired by the data acquisition unit 52 to determine the flight route of each aircraft.

[0080] The communication unit 54 is an interface for communicating with the aircraft 60 (described later) or an external network, and includes the functions of the transmission unit 34.

[0081] When the flight management device 50 receives a request from one of several aircraft to ask for permission to move to a specific spatial cell, the determination unit 55 uses the reservation status stored in the memory 51 to determine whether that spatial cell is already reserved.

[0082] If the determination unit 55 determines that the specific spatial cell is not reserved, the permission unit 56 permits the aircraft to move to that specific spatial cell. However, if the determination unit 55 determines that the specific spatial cell is reserved, the permission unit 56 does not permit the aircraft to move to that specific spatial cell.

[0083] Figure 8 is a block diagram of the aircraft 60. The aircraft 60 comprises a memory 61, a communication unit 62, a request generation unit 63, and a flight control unit 64.

[0084] Memory 61 stores information on multiple spatial cells C that can be identified by coordinates, etc., the current position of the aircraft 60, the flight route of the aircraft 60, and information on the spatial cells C reserved by the aircraft 60 along that flight route.

[0085] The communication unit 62 is an interface for communicating with the flight management device 50 or an external network, and includes the functions of the transmission unit 22 described above. In particular, the communication unit 62 also functions as a request transmission unit that transmits requests generated by the request generation unit 63 to the flight management device 50.

[0086] The request generation unit 63 selects a spatial cell adjacent to the spatial cell where the aircraft 60 is currently located, which the aircraft 60 should reserve, based on the flight route of the aircraft 60 stored in memory 61 and the aircraft 60's current position. The request generation unit 63 then generates a request for the reservation of the selected spatial cell.

[0087] Furthermore, if the determination unit 55 rejects the request from the aircraft 60 and the communication unit 54 transmits rejection information, the request generation unit 63 selects a space cell adjacent to the currently located space cell, other than the rejected space cell. The request generation unit 63 then generates a new request for the reservation of the selected space cell.

[0088] The flight control unit 64 controls the movement of the aircraft 60. In particular, the flight control unit 64 controls the various parts of the aircraft 60 to move the aircraft 60 to a specific authorized spatial cell based on authorization information.

[0089] The specific processing of Embodiment 3 will be described below with reference to Figure 9. Figure 9 is a sequence diagram showing the processing performed by the flight management system F3.

[0090] During flight, the request generation unit 63 of the aircraft 60 refers to the flight route and current position stored in memory 61 and selects a spatial cell on the flight route that is adjacent to the spatial cell where the aircraft is currently located as a specific spatial cell (step S31). Note that the flight route reflects the current flight state of the aircraft 60 and therefore includes the spatial cell where the aircraft is currently located.

[0091] The request generation unit 63 generates a first request (the first request) that asks for permission to move to the selected spatial cell. The communication unit 62 transmits this request to the flight management device 50 (step S32). This first request may include information indicating the spatial cell C in which the aircraft 60 is currently located (e.g., position information). In that case, the flight management device 50 can store the current positions of multiple aircraft 60 in the memory 51.

[0092] The communication unit 54 of the flight management device 50 receives the first request. Based on this request, the determination unit 55 of the flight management device 50 uses the reservation status stored in the memory 51 to determine whether the specific spatial cell related to this request is already reserved. Here, the determination unit 55 determines that the specific spatial cell is reserved. Therefore, the authorization unit 56 does not authorize the aircraft 60 to move to the specific spatial cell and rejects the request (step S33). The authorization unit 56 uses the communication unit 54 to transmit rejection information rejecting the move (step S34).

[0093] The communication unit 62 receives rejection information. The request generation unit 63 selects a spatial cell adjacent to the currently located spatial cell, other than the specific spatial cell that was rejected, based on a predetermined algorithm (step S35). The request generation unit 63 generates a second request (second request) asking for permission to move to the selected spatial cell. The communication unit 62 transmits this request to the flight management device 50 (step S36).

[0094] The communication unit 54 of the flight management device 50 receives a second request. Based on this request, the determination unit 55 of the flight management device 50 uses the reservation status stored in memory 51 to determine whether the specific spatial cell related to this request is already reserved. Here, the determination unit 55 determines that the new specific spatial cell is not reserved. Therefore, the authorization unit 56 authorizes the aircraft 60 to move to the new specific spatial cell (step S37). The authorization unit 56 uses the communication unit 54 to transmit authorization information authorizing the move (step S38). Based on the authorization information, the flight control unit 64 moves the aircraft 60 to the new specific spatial cell.

[0095] Furthermore, the flight management device 50 updates the reservation status stored in the memory 51 for the specific spatial cell for which the reservation was authorized in step S37. In addition, the flight management device 50 generates a new flight route for the aircraft 60, with the specific spatial cell for which the reservation was authorized as the departure point and heading toward the destination. The method for generating this flight route is as described in Embodiment 2. The flight management device 50 stores the generated flight route in the memory 51 and transmits it to the aircraft 60. The aircraft 60 stores this flight route in the memory 61. Then, each time the aircraft 60 enters another spatial cell, it repeatedly performs the process shown in Figure 9 based on the flight route stored in the memory 61. The flight management device 50 also repeatedly performs the process shown in Figure 9 each time.

[0096] If, in step S37, the authorization unit 56 does not authorize the aircraft 60 to move to a specific spatial cell and rejects the request, the flight management device 50 transmits rejection information rejecting the move, similar to step S34. The flight management device 50 and the aircraft 60 then repeatedly execute the processes described in steps S31 to S36 until the flight management device 50 authorizes the request.

[0097] The processes in steps S31 to S37 will be further explained using Figure 10. Figures 10A and 10B are schematic diagrams showing space cell C1 and its surrounding space cells while the aircraft 60 is in flight. Figure 10A is a side view showing space cells C1 to C5. Figure 10B is a top view showing space cells C1, C3, C4, C6, and C7. Space cells C2 to C7 are all adjacent to space cell C1.

[0098] The request generation unit 63 of the aircraft 60 selects space cell C2, which is adjacent to space cell C1 where the aircraft 60 is currently flying and is located on the flight route stored in memory 61 (step S31). The request generation unit 63 then generates the first request for space cell C2, and the communication unit 62 transmits that request (step S32).

[0099] The determination unit 55 of the flight management device 50 determines that space cell C2 is reserved, and the permission unit 56 refuses the aircraft 60 to move to space cell C2 (step S33). The flight management device 50 transmits refusal information refusing the movement of space cell C2 (step S34).

[0100] The request generation unit 63 of the aircraft 60 selects one space cell from among space cells C3, C4, C5, C6, and C7, which are adjacent to the currently located space cell C1 and are not space cell C2, based on the rejection information (step S35). In this way, the request generation unit 63 updates the flight route based on the rejection information. The flight management device 50 may also send a notification prompting a change in the flight route when it sends rejection information to the aircraft 60, and the request generation unit 63 may update the flight route in response to receiving this notification. If the request generation unit 63 selects space cell C3 in step S35, the request generation unit 63 generates a second request for the reservation of space cell C3. The communication unit 62 sends this second request to the flight management device 50 (step S36). The determination unit 55 of the flight management device 50 determines that space cell C3 is not reserved, and the permission unit 56 permits the aircraft 60 to move through space cell C2 (step S37).

[0101] In step S36, the spatial cells C3 to C7 to be selected are those that are not stored in memory 61 as non-flyable areas. The request generation unit 63 may also select a single spatial cell using the positional relationship between the current position and the destination. For example, the request generation unit 63 can select a spatial cell that can form the shortest distance from the current position to the destination. Furthermore, the request generation unit 63 may not select the spatial cell in which the aircraft 60 was located immediately before the current spatial cell C, or it may give that cell the lowest priority as a selection target. This is because if the aircraft 60 were to move to the spatial cell immediately before the current spatial cell C, the aircraft 60 would have to retrace its flight route to the destination, which may not be an efficient movement.

[0102] Furthermore, the request generation unit 63 can select spatial cell C3 from spatial cells C3 to C7 based on real-time data. The real-time data may include, but is not limited to, at least one of the following: the remaining battery level of the aircraft 60, weather information (e.g., wind speed and wind direction information), and the current speed of the aircraft 60. This data is measured by the sensors of the aircraft 60 and stored in memory 61.

[0103] For example, in step S35, based on wind speed and direction information and the current speed of the aircraft 60, the request generation unit 63 can select a spatial cell from spatial cells C3 to C7 that minimizes battery consumption when moving from spatial cell C1. This process may be performed, for example, when the remaining battery level of the aircraft 60 is below a predetermined value. Alternatively, in step S35, the request generation unit 63 may select a spatial cell that allows for the shortest movement from spatial cell C1 based on similar real-time data.

[0104] The movement path of the aircraft 60 using the spatial cell reservation method described above will be explained using Figure 11. In Figure 11, the aircraft 60 is moving from departure point A to destination B via route T. Points C11 to C17 are for convenience indicated spatial cells C that the aircraft 60 passes through on route T.

[0105] First, the aircraft 60 moves (ascends) in the z-axis direction from the departure point A, passing through space cell C11 and reaching space cell C12. Next, the aircraft 60 moves in the y-axis direction and reaches space cell C13. This movement is the result of the aircraft 60 requesting space cells C11 to C13 as specific space cells based on its flight route, and the flight management device 50 approving that request.

[0106] Next, based on its flight route, the aircraft 60 requests space cell C14 as a specific space cell. However, the flight management device 50 refuses the aircraft 60's movement to space cell C14, based on the fact that space cell C14 is reserved. At this point, the aircraft 60 selects space cell C15, which is a space cell other than space cell C14 and can constitute the shortest distance from its current position, space cell C13, to destination B. The aircraft 60 sends a request regarding space cell C15 to the flight management device 50.

[0107] The flight management device 50 determines that space cell C15 is not reserved and grants permission to move to space cell C15. Based on this permission, the aircraft 60 moves in the x-axis direction and reaches space cell C15. At this point, the flight path of the aircraft 60 is updated because the target space cell has changed from space cell C14 to space cell C15. The aircraft 60 moves along the updated flight path, passing through space cells C16 to C17, and reaches destination B.

[0108] As described above, if the space cell C that the aircraft 60 initially requested is already reserved, it requests a reservation for another space cell C. This prevents the aircraft 60 from remaining in the same space cell C for an extended period and allows it to retreat to another space cell C. Therefore, other aircraft 60s will be able to move to the space cell C where the aircraft 60 is currently located in the future, enabling the smooth movement of multiple aircraft 60s.

[0109] In step S33 of Figure 9, if the permission unit 56 does not permit the aircraft 60 to move to a specific spatial cell and rejects the request, the determination unit 55 may present the spatial cell to which the aircraft 60 will move next. Specifically, the determination unit 55 identifies a spatial cell other than the rejected spatial cell C, that is adjacent to the spatial cell C where the aircraft 60 is currently located, does not fall under a no-fly zone, and is not reserved by another aircraft 60. This identification uses information indicating the spatial cell C where the aircraft 60 is currently located, which is included in the first request, as well as information on the spatial cell stored in memory 51 and its reservation status.

[0110] If the determination unit 55 identifies only one spatial cell C, the authorization unit 56 may reserve the spatial cell C identified by the determination unit 55 and notify the aircraft 60 of the authorization information relating to that spatial cell. The aircraft 60 moves to that spatial cell based on the received authorization information. This allows the flight management device 50 to reliably evacuate the aircraft 60.

[0111] If the determination unit 55 identifies multiple spatial cells C, the determination unit 55 may use the communication unit 54 to transmit information about the identified multiple spatial cells C to the aircraft 60. The aircraft 60 selects one of the received multiple spatial cells C. Here, the aircraft 60 may select a spatial cell that allows for the shortest distance from its current position to its destination. Alternatively, based on data such as the aircraft 60's battery level, weather information (e.g., wind speed and direction), and the aircraft 60's current speed, it may select a spatial cell that offers the most favorable battery consumption or travel time. Details of this method are as described above. The aircraft 60 sends a request to the flight management device 50 for permission to move to the newly selected spatial cell C. The flight management device 50 grants the request. This method is particularly effective when the aircraft 60 does not share its real-time data with the flight management device 50.

[0112] Furthermore, if the determination unit 55 identifies multiple spatial cells C, the determination unit 55 may select the optimal single spatial cell C from among them. The method by which the determination unit 55 selects a single spatial cell C is the same as the method by which the aircraft 60 selects a single spatial cell C.

[0113] Furthermore, the determination unit 55 may select a spatial cell C in a direction with low current or future density of other aircraft 60, based on at least one of the current positions of multiple aircraft 60 stored in memory 51, or the reservation status of spatial cells reserved by other aircraft 60. In other words, the determination unit 55 can select a spatial cell C in a less crowded direction. For example, in the example shown in Figure 10, consider a case where aircraft 60 is flying in spatial cell C1 and the determination unit 55 selects one of spatial cells C3 to C7. For spatial cell C3, the determination unit 55 calculates the number of aircraft 60 in a predetermined spatial cell C within a predetermined distance centered on spatial cell C3, the number of reserved cells, or both. The determination unit 55 performs similar calculations for each of spatial cells C4 to C7 and can select the spatial cell with the lowest calculated value among spatial cells C3 to C7. Furthermore, if a spatial cell adjacent to a surface with spatial cell C3 is defined as the 1st adjacent cell of spatial cell C3, and a spatial cell adjacent to that 1st adjacent cell with a surface is defined as the 2nd adjacent cell of spatial cell C3, the determination unit 55 may calculate the above values ​​for the region containing the 1st to Nth adjacent cells (where N is 1 or greater) of spatial cell C3. The determination unit 55 performs the same calculation for each of the spatial cells C4 to C7 and can select the spatial cell with the smallest calculated value among the spatial cells C3 to C7.

[0114] The flight management device 50 may reserve one selected space cell C and notify the aircraft 60 of the permission information relating to that space cell. The aircraft 60 then moves to that space cell based on the received permission information. Alternatively, the flight management device 50 may not reserve one selected space cell C but notify the aircraft 60 of the information relating to that space cell C. The aircraft 60 may then send a request to reserve the notified space cell C based on the notified information. In this case, the aircraft 60 may also send requests for space cells adjacent to the currently located space cell C, other than the space cell C that was initially requested and the space cell C that was received.

[0115] In the example described above, when the flight management device 50 authorized a reservation for a specific spatial cell in step S37, the route generation unit 53 of the flight management device 50 determined the flight route of the aircraft 60. However, other examples of flight route generation are also conceivable.

[0116] For example, the route generation unit 53 of the flight management device 50 does not need to directly determine the flight route for each aircraft when the flight management device 50 authorizes a reservation for a specific spatial cell in step S37. The route generation unit 53 functions as a route proposal unit that proposes candidate flight routes starting from the authorized spatial cell and inquires with the aircraft 60 via the communication unit 54 whether it agrees to or disagrees with the candidate flight routes. Here, the route generation unit 53 calculates candidate flight routes so that they do not overlap with the flight routes of other aircraft. The details of this calculation are the same as the method for setting flight routes described in (2-1). When the aircraft 60 receives the inquiry, the request generation unit 63 makes a determination of agreement or disagreement regarding the candidate flight route. The flight management device 50 may also be controlled to propose candidate flight routes and inquire in the same way when sending rejection information to the aircraft 60 in step S34. In particular, in this case, when the determination unit 55 identifies the next spatial cell to which the aircraft 60 will move, the flight management device 50 can propose candidate flight routes that start from that spatial cell.

[0117] At this time, the request generation unit 63 may determine whether a candidate flight route is flyable based on telemetry data. For example, based on information such as battery level and weather information, if it is calculated that the battery level will fall below a predetermined threshold while flying the flight route, the request generation unit 63 may determine that the candidate flight route is not flyable, and otherwise determine that the flight route is flyable. In addition, the request generation unit 63 may determine that a candidate flight route is not flyable if there is another aircraft in the vicinity of the aircraft based on detection results from detection units such as sensors, radar, and cameras mounted on the aircraft 60, and otherwise determine that the flight route is flyable. Furthermore, this agreement or disagreement may be decided on the computer of the occupant of the aircraft 60.

[0118] When the aircraft 60 transmits a signal indicating consent, the request generation unit 63 stores that flight route in the memory 61 as a new flight route, or updates a previously stored flight route to that route. When the route generation unit 53 receives a signal indicating consent from the aircraft 60, it stores that flight route in the memory 51 as a new flight route, or updates a previously stored flight route to that route.

[0119] Furthermore, if the request generation unit 53 receives a signal from the aircraft 60 indicating disagreement, it will propose a candidate route that is different from the proposed route and does not overlap with the flight routes of other aircraft, satisfying the above-mentioned conditions, and will inquire about that route from the aircraft 60. This inquiry will continue until the request generation unit 63 receives a signal from the aircraft 60 indicating agreement. The request generation unit 63 may agree to the entire route proposed by the route generation unit 53. In addition, if there is a sub-route that is not the entire route but is part of it (a part of the route that is close to the aircraft 60's current location) that the aircraft 60 can fly, the request generation unit 63 may send a signal indicating agreement regarding that sub-route. In this case, the aircraft 60 will be able to fly at least along that sub-route.

[0120] Furthermore, the aircraft 60 may set the target of a request in a single request to a sub-route consisting of multiple cells that is part of its own flight route. Based on conditions such as the aircraft 60's flight schedule, battery life, and set intermediate points on the route, the aircraft 60 determines the cells to request so that a sub-route that satisfies those conditions is set. When the flight management device 50 receives this request, if none of the spatial cells in a given sub-route are reserved, it permits the allocation of that sub-route and reserves the corresponding cells. On the other hand, if any of the spatial cells in that sub-route are reserved by another aircraft, it rejects that sub-route. At this time, the route generation unit 53 may generate another sub-route as a set of alternative spatial cells (a set of spatial cells that may be assigned to the aircraft) consisting of all or part of the rejected sub-route. The first spatial cell of this alternative sub-route is a cell adjacent to a spatial cell that exists before the rejected sub-route in the route assigned by the aircraft 60 (for example, the aircraft's current or future position at the time the sub-route was rejected). The flight management device 50 receives route information from the aircraft 60 in advance. The last space cell of the alternative subroute will be the same as the last space cell in the rejected subroute. The flight management device 50 sends the information of the generated alternative subroute, along with the rejection information, to the aircraft 60 for proposal. The aircraft 60 sends a signal indicating its agreement or disagreement with this proposal, following the process described above. If it disagrees, the flight management device 50 generates an alternative subroute different from the subroute it rejected and the subroute rejected by the aircraft 60, using the method described above, and proposes it to the aircraft 60. This process is repeated until the aircraft 60 sends an agreement signal.

[0121] If the aircraft 60 agrees, the flight management device 50 reserves cells covering all or part of the agreed-upon sub-route. The aircraft 60 updates its assigned route or sub-route to pass through its allocated spatial cells. In this way, the route generation unit 53 of the flight management device 50 can assist the aircraft 60 in determining its route. The entire route of the aircraft 60, rather than just a sub-route, may also be determined by the same process performed by the flight management device 50 and the aircraft 60. In this way, the aircraft 60 can fly by selecting a flight route or sub-route that is convenient for it from among those presented.

[0122] In the above example, the route generation unit 53 inquired for one candidate flight route in a single query, but it may also inquire for multiple candidate routes in a single query. The request generation unit 63 of the aircraft 60 determines whether or not there is a flyable route among them, and if no such route exists, it sends a signal indicating disagreement. If there is one flyable route, it sends a signal indicating agreement for that route. Furthermore, if there are multiple flyable routes, the request generation unit 63 may select one route that is, for example, the best in terms of battery usage, flight time, or distance during flight, and send a signal indicating agreement for that route.

[0123] Thus, when the aircraft 60 needs to initially set or change its flight route, the request generation unit 63 can also function as a route determination unit by agreeing to the flight route proposed by the route generation unit 53. The flight management device 50 has the computing power to visualize and analyze in real time the reservation status and flight routes of all aircraft in the space to be managed, using the information stored in the memory 51. Therefore, using this method, the aircraft can determine a safer flight route that takes into account the status of other aircraft, rather than determining its own flight route using only its own data. In this case, the aircraft is the entity that determines its own flight route, and the flight management device functions as an air traffic control device that assists the aircraft.

[0124] As another example, the flight management device 50 does not necessarily have to be equipped with a route generation unit 53. For example, the aircraft 60 may be equipped with a route generation unit 43 as described in (2-1), and when the flight management device 50 grants a reservation for a specific spatial cell in step S37, the aircraft 60 itself may generate a new flight route from the specific spatial cell for which the reservation has been granted as the departure point to the destination. Alternatively, neither the flight management device 50 nor the aircraft 60 may be equipped with a route generation unit and not formulate the aircraft's flight route. In either case, the flight management device 50 does not manage the aircraft 60's flight route. However, as described above, the flight management device 50 is aware of the reservation status of each spatial cell and the current position of each aircraft, and when it receives a request from the aircraft 60 regarding a spatial cell that the aircraft plans to fly to, it will perform the process of granting or denying permission to move to that cell.

[0125] Embodiment 4 In this embodiment, the reservation and release of the space cell C of the aircraft 60 will be further described.

[0126] Figure 12 is a block diagram of the aircraft 60 in Embodiment 4. This aircraft includes a memory 61, a communication unit 62, a request generation unit 63, a flight control unit 64, and a release unit 65. The components other than the release unit 65 are as described in Embodiment 3.

[0127] The aircraft 60 reserves at least the space cell C in which it is currently located, and adjacent space cell C adjacent to space cell C, which it will fly to in the future, through requests generated by the request generation unit 63. When the aircraft 60 passes through the space cell C in which it is currently located and enters an adjacent reserved space cell C, the release unit 65 generates a request (a third request) to release the reservation of the space cell C that has been passed through. The communication unit 62 transmits this request to the flight management device 50. The flight management device 50, having received the request via the communication unit 54, releases the reservation status of the space cell C that has been passed through in the reservation status stored in the memory 51.

[0128] As described above, space cell C, which has already been passed through by aircraft 60, becomes available for reservation by other aircraft. This allows multiple aircraft to fly simultaneously within the designated space, and ensures the safety of the flight paths of the listed aircraft from the cell currently occupied by the aircraft to the cell newly reserved by the aircraft.

[0129] Embodiment 5 Embodiment 5 of this disclosure will be described below with reference to the drawings.

[0130] When multiple aircraft are flying through space, it is generally safer for each aircraft to move along the same axis within a plane composed of spatial cells of the same height, rather than moving in different directions. Embodiment 5 describes a method for managing such a space.

[0131] Figure 13 is a block diagram of the flight management device 50 in Embodiment 5. This flight management device 50 includes a memory 51, a data acquisition unit 52, a route generation unit 53, a communication unit 54, a determination unit 55, a permission unit 56, and a traffic management unit 57 (movement management unit). The components other than the traffic management unit 57 are as described in Embodiment 3.

[0132] Traffic Management Unit 57 manages the flight (traffic) of aircraft within a plane as follows:

[0133] Figure 14 shows a first example of a traffic management method. In Figure 14, four planes P1 to P4 with different heights are set in space S1. Planes P1 to P4 are set with a spacing of at least one spatial cell in the height direction, and one-way lanes with the same vector direction as the direction of movement are set in each plane P1 to P4 by the traffic management unit 57. Each lane has a designated starting spatial cell C and an ending spatial cell C. Plane P1 has lanes D11 to D14 with the y-direction as the direction of movement, plane P2 has lanes D21 to D24 with the -y-direction as the direction of movement, plane P3 has lanes D31 to D34 with the -x-direction as the direction of movement, and plane P4 has lanes D41 to D44 with the x-direction as the direction of movement.

[0134] Figure 15 is a schematic diagram showing plane P1 and lanes D11-D14. The thickness of plane P1 in the z direction and the width of lanes D11-D14 in the x direction are equivalent to one spatial cell C. An aircraft can fly in the y direction by passing through any of the continuous lanes D11-D14 in the y direction. However, the thickness of plane P1 in the z direction and the width of lanes D11-D14 in the x direction may be equivalent to multiple spatial cells C. Also, the number of lanes in a single plane is not limited to four.

[0135] Lanes D11 to D14 may each have the same reference speed, or at least one lane may have a different reference speed from the others. The reference speed is the speed required for an aircraft flying in a lane, and the aircraft must fly in such a way that the absolute difference between its own speed and the reference speed falls within a predetermined range. For example, the reference speeds for lanes D11, D12, D13, and D14 may be set to 30 km / h, 60 km / h, 90 km / h, and 120 km / h, respectively. In this case, if the aircraft needs to move at a higher speed while moving in lane D12, it will move from lane D12 to lane D13 or D14 within plane P1. This allows the aircraft to move at a higher speed. The opposite movement occurs when the aircraft needs to move at a lower speed. Planes P2 to P4 and the lanes within each plane in Figure 14 have the same configuration as shown in Figure 15.

[0136] In this way, the traffic management unit 57 permits the aircraft to move in a predetermined direction within a given space, and does not permit movement in other directions. This enables the safe movement of the aircraft within the plane. Furthermore, by assigning different standard speeds to different lanes, traffic congestion can be alleviated. In addition, if the aircraft is a flying car carrying people, it can also alleviate passenger frustration caused by congestion.

[0137] The space between each plane is used for moving from one plane to another. Furthermore, if an aircraft moving within a plane cannot move because the next space cell C it intends to move to is already reserved, the aircraft may request the reservation of a space cell C above or below that plane. Alternatively, the flight management system may reserve a space cell C above or below that plane as an evacuation space cell and transmit information about the evacuation space cell to the aircraft. Details of these processes are described in Embodiment 3.

[0138] Furthermore, even if the flight path of the aircraft described in Embodiment 2 is changed while the aircraft is flying in a plane (i.e., if the movement within the plane assumed by the original flight path is eliminated), the aircraft can still move to a spatial cell C above or below the plane in which it is flying.

[0139] Figure 16 shows an example of a flight path when an aircraft flies from a ground departure point D to a destination E in the spatial configuration shown in Figure 14. First, the aircraft ascends from the departure point D and reaches spatial cell C21 in plane P1. Then, the aircraft moves to spatial cell C22 using lane D11. At this point, in order to move even faster in the y-axis direction, the aircraft moves to spatial cell C23 in plane P1 and reaches lane D12. Then, the aircraft moves to spatial cell C24 using lane D12.

[0140] The aircraft ascends from space cell C24 to move in the x-direction and reaches space cell C25 in plane P4. Then, using lane D41, it moves to space cell C26. The aircraft descends from space cell C26 for landing and arrives at destination E.

[0141] Thus, aircraft move in the same direction on the same plane, except when changing lanes due to changes in speed. Therefore, a large number of aircraft can move in an orderly manner on the same plane, allowing them to fly safely.

[0142] Note that there may be multiple planes P1 to P4. Figure 17 is a diagram showing that PA, which is a set of planes P1A to P4A, and PB, which is a set of planes P1B to P4B, are set up. Planes P1A to P4A and P1B to P4B are planes with the same direction of movement as planes P1 to P4 in Figure 14. In this way, by setting up multiple planes where the direction of movement of the aircraft is aligned, it becomes possible to move a larger number of aircraft.

[0143] Figure 18 shows a second example of a traffic management method. In Figure 18, four planes P5 to P8 with different heights are set in space S2. Planes P5 to P8 are set with a distance of at least one space cell in the height direction, and four lanes are set in each plane P5 to P8 by the flight management system. Plane P5 has lanes D51 to D54 with movement in the y-axis direction, i.e., the y direction or -y direction (lateral direction); Plane P6 has lanes D61 to D64 with movement in the x-axis direction, i.e., the x direction or -x direction (linear direction); Plane P7 has lanes D71 to D74 with movement in the y direction or -y direction; and Plane P8 has lanes D81 to D84 with movement in the x direction or -x direction.

[0144] Plane P5 is a plane for movement in the y-direction or -y-direction, with lanes D51 and D52 moving in the y-direction and lanes D53 and D54 moving in the -y-direction. The reference speeds for lanes D51 and D52 may be the same or different. If the reference speeds for lanes D51 and D52 are different, as described above, movement from one lane to the other is permitted to change speed. The same configuration applies to lanes D53 and D54.

[0145] Plane P6 is a plane for movement in the x-direction or -x-direction, with lanes D61 and D62 moving in the -x-direction and lanes D63 and D64 moving in the x-direction. Plane P7 is a plane for movement in the y-direction or -y-direction, with lanes D71 and D72 moving in the y-direction and lanes D73 and D74 moving in the -y-direction. Plane P8 is a plane for movement in the x-direction or -x-direction, with lanes D81 and D82 moving in the -x-direction and lanes D83 and D84 moving in the x-direction. Furthermore, the reference speeds of multiple lanes with the same direction of movement in each of the planes P6 to P8 may be the same or different. This is as explained for lanes D51 and D52. The space between each plane is used for moving from one plane to another. Note that either plane P5 or P7 may be provided or not. In addition to planes P5 and P7, further planes may be provided with the same direction of movement as planes P5 or P7. Similar variations are possible for planes P6 and P8.

[0146] In Embodiment 5, in the first and second examples described herein, when the aircraft is a flying car carrying people, the passengers do not see other aircraft approaching them from the front. Therefore, the passengers' feelings of anxiety or fear during flight can be suppressed. Furthermore, in these examples, the aircraft flies in a plane using a mechanism similar to that of a car driving on a two-dimensional road. Therefore, the driver has the advantage of being able to control the aircraft as if driving on a road.

[0147] In Figure 17, the reference speed of a designated lane in plane P1A may be set faster than the reference speed of a lane in plane P1B that corresponds to that designated lane. Alternatively, the average reference speed of the lanes in plane P1A may be set faster than the average reference speed of the lanes in plane P1B. This is to allow for a safer landing of the aircraft by further reducing its speed as it approaches the ground in the event that the aircraft leaves the plane and lands due to an emergency. A similar setting is possible in Figure 18.

[0148] Furthermore, when multiple lanes are set within a plane, and a no-fly zone (e.g., a building) exists near a given lane, the reference speed for the lane closer to the no-fly zone may be set lower, while the reference speed for the lane further away from the no-fly zone may be set higher. This is to prevent the aircraft from entering the no-fly zone if it deviates from its lane.

[0149] The above settings are stored in the memory of the flight management device 50, and the traffic management unit 57 manages traffic in the plane by using these settings. The definition of one-way traffic in each lane is achieved, for example, by setting a vector for the direction of movement in the spatial cell C belonging to the lane. The validity or invalidity of each vector can be arbitrarily configured to restrict the movement of aircraft within and / or outside the cell. Such configurations can be implemented algorithmically and / or manually by the operator of the flight management system based on various factors. In this case, it is preferable not to excessively invalidate vectors that cause congestion.

[0150] The traffic management unit 57 can generate a flight path for an aircraft moving in a plane, based on the vector set in this way, so that it follows the vector. Alternatively, the flight management device may, in response to a request from an aircraft for a specific spatial cell, determine whether the specific spatial cell lies in the direction of the vector set from the spatial cell where the aircraft is currently located. The flight management device can grant the request if the specific spatial cell lies in the direction of the vector, and deny it if the specific spatial cell lies in the direction of the vector. The one-way traffic in each lane described above corresponds to the current highway lane system, where a single direction of travel is set.

[0151] In the examples shown in Figures 14, 15, and 18, multiple lanes arranged on the same plane may be adjacent to each other, but for the safe flight of the aircraft, there may be a gap of one or more spatial cells between the lanes. This is also true for the examples shown in Figures 19 and 21-23, which will be described later.

[0152] Furthermore, the traffic management unit 57 can control the activation or deactivation of the direction vector for each lane, thereby giving the vector the function of a "stoplight" that instructs the aircraft to proceed or stop. By giving the vector this function, the flight management device can move multiple aircraft moving in different directions within a single space.

[0153] Figure 19 shows a third example of a traffic management method that allows multiple aircraft to move in different directions within a single plane. In Figure 19, within plane P9, lanes D91 and D92 are set up in the y-direction, lanes D93 and D94 are set up in the x-direction, lanes D95 and D96 are set up in the -y-direction, and lanes D97 and D98 are set up in the -x-direction. Plane P9 corresponds to a crossroads on a typical road.

[0154] The flight control system managing plane P9 performs the following control to ensure that aircraft moving along lanes D91 to D98 do not come dangerously close to each other. In Figure 19, by enabling a vector pointing in the y direction in each spatial cell C of lane D91 and lane D101 (which is an extension of lane D91), the aircraft in lane D91 is moved along lane D101 in the y direction. Similarly, by enabling a vector pointing in the -y direction in each spatial cell C of lane D95 and lane D103 (which is an extension of lane D95), the aircraft in lane D95 is moved along lane D103 in the -y direction.

[0155] Meanwhile, the flight management system sets a vector in space cell C of lane D102 within plane P9 such that an aircraft in space cell C at the y-direction end (endpoint) of lane D92 moves to a lane in the x-direction that is adjacent to lane D98 and is on the extension of lane D94, by turning within plane P9.

[0156] Figure 20A shows an example of lane D102. In lane D102, the vectors of space cells C are configured such that the aircraft turn at an "intersection" by moving alternately through one space cell in the x and y directions.

[0157] Figure 20B shows another example of lane D102. In Figure 20B, the aircraft travels along lane D102, passing through region E1 (two spatial cells in the example in Figure 20B) which extends in the x direction, then through region E2 (five spatial cells in the example in Figure 20B) which extends in the y direction, and finally through region E3 (three spatial cells in the example in Figure 20B) which extends in the x direction.

[0158] The configuration of lane D102 is not limited to the examples shown in Figures 20A and 20B. It is expected that the fewer the inflection points of lane D102 (i.e., the number of times the aircraft turns on lane D102), the less battery power the aircraft will consume when moving on lane D102. However, if lane D102 has only one inflection point, the aircraft will first move in a straight line in the y-axis direction on lane D102, and then in a straight line in the x-axis direction. Therefore, when the aircraft first moves in a straight line in the y-axis direction on lane D102, it is more likely to come into contact with an aircraft on lane D104, which will be described later. However, as shown in Figure 20B, if lane D102 has two inflection points, the aircraft first moves in the x-axis direction along region E1 on lane D102, thus reducing the area where lane D102 intersects with lane D104. Therefore, the aircraft on lane D102 can move more safely within the "intersection".

[0159] Furthermore, in Figure 20B, if there is a gap of one or more spatial cells between lane D95 and lane D96, it is preferable for the safe flight of an aircraft on lane D102 that the region E2 extending lane D102 in the y-axis direction be located between the extension of lane D95 and the extension of lane D96 in the x-axis direction.

[0160] Lane D102 intersects with lane D103 at some point. Therefore, the flight control system controls aircraft in lane D102 to prevent them from coming dangerously close to other aircraft moving through lane D103.

[0161] For example, the flight control system enables the vectors of all spatial cells in lane D103. On the other hand, to ensure that aircraft on lane D102 are not in the same spatial cells as aircraft on lane D103, the flight control system switches the vectors of spatial cells in lane D102 from enabled to disabled depending on the position of the aircraft on lane D103. When an aircraft on lane D103 is not in an intersecting spatial cell, the flight control system switches the vectors of spatial cells in lane D102, in the region where lane D102 intersects with lane D103 and its surroundings, from disabled to enabled.

[0162] Similarly, the flight management system sets a vector in space cell C of lane D104 in plane P9 such that an aircraft in space cell C at the -y end (endpoint) of lane D96 moves in a lane that is adjacent to lane D94 and on the extension of lane D98, and is directed in the -x direction, by turning within plane P9.

[0163] Furthermore, the flight control system disables the spatial cell vectors in lanes D93, D94, D97, and D98 to control aircraft moving in those lanes and prevent them from coming dangerously close to other aircraft moving along lanes D101-D104.

[0164] Figure 21 shows the traffic conditions within plane P9 after a time has elapsed since Figure 19. In Figure 21, the spatial cell vectors in lanes D91, D92, D95, and D96 are disabled, so aircraft in those lanes do not move. On the other hand, the spatial cell vectors in lanes D93, D97, D105, and D107 are enabled, allowing aircraft in those lanes to travel in a straight line. The flight control system enables and disables the spatial cell C vectors in lanes D94, D106 and lanes D98, D108 in the same way as the enabled and disabled spatial cell C vectors in lanes D92, D102 and lanes D96, D104 shown in Figure 19. This allows aircraft in lanes D94 and D98 to turn within the plane.

[0165] As described above, the flight control system can algorithmically stop traffic in one direction, thereby allowing traffic in another direction to pass.

[0166] Furthermore, the flight management system can enable or disable the vertical vector, thereby allowing or denying the takeoff, landing, and spatial movement of aircraft.

[0167] Figures 22 and 23 show a fourth example of a traffic management method in which the direction of lane movement changes according to time. In Figure 22, the city is in the y-direction and the suburbs are in the -y-direction of plane P10. Figure 22 shows the traffic flow on plane P10 during a specific time period in the morning (especially during rush hour), illustrating how people commute to the city using flying vehicles (flying cars). The spatial cell vectors in each lane are set so that lanes D111 to D113 are lanes moving in the y-direction, and lane D114 is a lane moving in the -y-direction.

[0168] In Figure 22, there are three lanes leading to the city and one lane leading to the suburbs. By setting up more lanes leading to the city than to the suburbs during rush hour, congestion within the P10 area can be alleviated.

[0169] Figure 23 shows the traffic flow on plane P10 during specific time periods in the evening and at night, illustrating people returning to their suburban homes using flying vehicles. Lane D111 is the lane leading to the city, and lanes D112-D114 are the lanes leading to the suburbs, with the spatial cell vectors set for each lane. Here, the flight management system alleviates congestion on plane P10 by setting more lanes leading to the suburbs than to the city.

[0170] In the above example, the spatial cell vectors in each lane may be set to always be active for aircraft with "high" priority. For example, in the example shown in Figure 19, if an aircraft with "high" priority is on lane D93, the flight management system will enable the spatial cell vectors in lane D93 instead of disabling them. This setting allows the aircraft to set its flight route and reserve the spatial cells along that route, enabling it to move in the x-direction. At this time, the spatial cell vectors in lanes D95, D96, D103, and D104 are temporarily disabled, allowing aircraft with "high" priority to move safely across lanes D103 and D104. The flight management system can obtain priority information from aircraft via communication protocols, etc.

[0171] Furthermore, the flight management system may change the validity or invalidity of the spatial cell vectors in the lanes based on weather information. For example, in Figure 22, the flight management system obtains from the network that the wind speed in plane P10 is above a predetermined value. At this time, the flight management system disables the spatial cell vectors in lane D112 out of lanes D111 to D113, thereby setting only lanes D111 and D113 to be operational. In this way, the spacing between lanes is increased, which improves flight safety.

[0172] The flight management system may set the spatial cell vectors in each lane by taking into account at least one of time information and / or date information. For example, during weekday morning rush hour, lanes D111 to D113 may be set as lanes heading towards the city and lane D114 as a lane heading towards the suburbs in plane P10, while on weekend mornings, lanes D111 and D112 may be set as lanes heading towards the city and lanes D113 and D114 as lanes heading towards the suburbs.

[0173] Embodiment 6 The flight management system may be configured to allow high-priority aircraft to enter a predetermined spatial cell or plane it manages, while denying entry to low-priority aircraft. Furthermore, the flight management system may be configured to deny departure of low-priority aircraft in directions from which high-priority aircraft can depart.

[0174] For example, in the example shown in Figure 14, the spatial cell vectors may be set so that, in spatial cells other than those at both ends of lane D11, low-priority aircraft are denied movement in the x-direction or movement in the z-direction (ascending or descending). This suppresses the movement of aircraft other than high-priority aircraft (emergency vehicles or vehicles with low battery levels) around lane D11, thereby ensuring the safety of flight around space P1. Similarly, in the example shown in Figure 14, the spatial cell vectors may be set so that, in spatial cells other than those at both ends of lane D31, low-priority aircraft are denied movement in the y-direction or movement in the z-direction (ascending or descending).

[0175] The flight management system may always perform the above settings for low-priority aircraft, or it may perform them at least during a specified time period or on a specified date.

[0176] Embodiment 7 By connecting multiple flight management systems and creating a continuous network of spaces managed by these systems, it is also possible to manage the movement of aircraft over a wide area.

[0177] Figure 24 is an illustrative diagram of a system formed by connecting multiple flight management devices. Flight management devices 50A to 50E have the same configuration as the flight management device 50 of Embodiment 3 described above, and each manages the spatial regions R1 to R5.

[0178] In Figure 24, spatial region R1 contains city 1, and spatial region R5 contains city 2. Spatial regions R2 to R4 are regions connecting city 1 and city 2, and the flying object 60 moves from one spatial region R1 or R5 to the other via spatial regions R2 to R4.

[0179] The following describes processes performed by the flight management device 50A, in addition to the processes performed by the flight management device 50 as described in Embodiment 3. While the aircraft 60 is flying through area R1 from city 1 to city 2, the aircraft 60 sends a request to the flight management device 50A regarding the spatial cell to which it will next move. As described above, the flight management device 50A approves or rejects this request.

[0180] When the aircraft 60 enters a spatial cell in area R1 that is at or near the boundary with area R2, the aircraft 60 sends a request to the flight management device 50B regarding the spatial cell in area R2 that is at the boundary with area R1. The flight management device 50A also recognizes that the aircraft 60 is at the edge of area R1 based on the request or GPS information obtained from the aircraft 60 by the data acquisition unit 52, and sends information to the flight management device 50B indicating that the aircraft 60 is approaching area R2. The transmitted information may include identification information of the approaching aircraft 60.

[0181] The flight management device 50B recognizes the aircraft 60 flying toward area R2 based on information obtained from the flight management device 50A. Then, the flight management device 50B permits or denies the request received from the aircraft 60.

[0182] If the flight control device 50B approves the request, the aircraft 60 can move from area R1 to R2. While flying in area R2, the aircraft 60 sends a request to the flight control device 50B regarding the next spatial cell to move to. By performing similar operations at or near the boundaries of each area, the aircraft 60 can reach area R5 and arrive at city 2.

[0183] If the flight management device 50B rejects the request, the aircraft 60 can move to (evacuate to) a different spatial cell than the one that made the request. The aircraft 60 sends a request regarding the spatial cell to be evacuated to the flight management device 50A, which manages the spatial cells in the region R1 to be evacuated. For example, if the aircraft 60 is in a spatial cell at the boundary between region R1 and region R2, the aircraft 60 may send a request to move to a spatial cell located above or below its current spatial cell. The details of this are as described in Embodiment 3 (particularly in Figure 9). Similar processing can be achieved with flight management devices other than the flight management devices 50A and 50B.

[0184] As described above, by connecting multiple flight management devices 50, the flight of the aircraft 60 over a wide area can be continuously managed. Since the overall system for managing a wide area can be configured by connecting multiple flight management devices, it is possible to manage the movement of aircraft at the level of local governments such as cities, prefectures, and states, or at the level of wide areas or nations that include multiple such entities. In other words, the overall system for managing a wide area can be distributed or divided into different regions, each managed by a separate flight management device. Therefore, the scalability and expandability of the system can be improved. The region managed by the flight management device is determined, for example, by geographical location or zoning set by the government.

[0185] In the example shown in Figure 24, the aircraft 60 can use the same communication protocol for communication with the flight management devices 50A to 50E.

[0186] Embodiment 8 Embodiment 8 of this disclosure will be described below with reference to the drawings. The flight management device can change the size of the spatial cells (in particular, the length of one side). Figures 25A and 25B show an example in which the size of the spatial cells dividing the same spatial region is changed. In Figure 25A, space S A However, one side W A 6 by the cube 3is divided into 216 spatial cells. On the other hand, in FIG. 25B, a space S A having the same volume as B space S is a cube with side W B and is divided into 3 3 = 27 spatial cells. The length of one side of W B is twice the length of that of W A .

[0187] When the spatial cells are small, although the number of flying objects that can exist within the same volume can be increased, the number of request transmissions that a flying object makes while flying through one space S increases. For example, from the time a flying object enters and then leaves the space S in FIG. 25A A , at least 6 request processes with the flight management device are required. Therefore, the processing load on the entire flight management system increases. Also, as described in Embodiment 3, when the spatial cell of the request destination is reserved by another flying object, the flying object needs to evacuate to another spatial cell. Thus, when the number of flying objects in the space increases, the evacuation actions of the flying objects when the request is rejected tend to increase. Therefore, the time required for a flying object to fly through one space S can become longer.

[0188] When the spatial cells are large, although the number of flying objects that can exist within the same volume decreases, the number of request transmissions that a flying object makes while flying through one space S decreases. For example, from the time a flying object enters and then leaves the space S in FIG. 25B B , the minimum necessary request process with the flight management device is 3 times. Thus, the fewer the number of flying objects in the space, the less likely the evacuation actions of the flying objects when the request is rejected, so the time required for a flying object to fly through one space S can become shorter.

[0189] Based on the above characteristics, the flight management system can change the size of the spatial cells in the space it manages depending on the time of day. For example, the flight management system that manages the space shown in Figures 22 and 23 sets the spatial cell size to be smaller during predetermined time periods in the morning and evening (especially during rush hour) to allow a large number of aircraft to move between cities and suburbs. On the other hand, during other times (especially late at night), it is assumed that there will be fewer aircraft moving between cities and suburbs, so the spatial cell size is set to be larger to allow aircraft to move faster.

[0190] Furthermore, the size of the spatial cells may be set according to the characteristics of the area managed by the flight management system. For example, the flight management system may reduce the size of the spatial cells when managing areas where a large number of aircraft are expected to be congested, and increase the size of the spatial cells when managing areas where a small number of aircraft are expected. The former would include urban areas and areas related to junctions where aircraft moving from multiple directions converge. The latter would include rural areas, mountainous areas, and sparsely populated areas connecting cities.

[0191] For example, in Figure 24, flight control devices 50A and 50E can set the spatial cell to be small, while flight control devices 50B to 50D can set the spatial cell to be large. This allows the speed at which the aircraft 60 flies through areas R2 to R4 to be increased, so that areas R2 to R4 can be set up like a highway connecting urban areas. In this way, the flight control devices can control the flow of traffic.

[0192] Furthermore, the following variations are also possible. When the spatial cell size is large, the aircraft has more time to reach the next spatial cell to fly to compared with the case of a small spatial cell. Therefore, when the spatial cell size is large, the time it takes for the aircraft to send a request for the next spatial cell to the flight management system after entering the spatial cell may be longer compared with the case of a small spatial cell. For example, spatial S in Figure 25A AIn this case, immediately after the aircraft enters a spatial cell, it sends a request for the next spatial cell on its flight path. Meanwhile, in spatial S in Figure 25B B In this scenario, after an aircraft enters a space cell, it may send a request for the next space cell on its flight path after traveling a distance approximately half the length of one side of the space cell.

[0193] In another example, if the spatial cell is small, the aircraft sends a first request, and if that request is rejected, it sends a second request for the spatial cell to be evacuated. On the other hand, if the spatial cell is large, the aircraft may send multiple requests for the same spatial cell. Specifically, if the aircraft sends a first request and that request is rejected, it sends a second request for the same spatial cell as the first request at a predetermined interval. If that second request is also rejected, the aircraft may send a third request for a different spatial cell to be evacuated, or it may send a third or subsequent request for the same spatial cell at predetermined intervals.

[0194] Even when the spatial cell size is small, the aircraft may send multiple requests to the same spatial cell. However, when the spatial cell size is large, the number of requests the aircraft can send to the same spatial cell may be increased compared to when it is small. This allows the aircraft to fly as close to its original flight path as possible when the spatial cell is large, thereby shortening the aircraft's flight time.

[0195] Embodiment 9 This embodiment describes the hazard avoidance processes performed by the aircraft and the flight management system in an emergency. An emergency means, but is not limited to, situations where two or more aircraft are in the same cell, or where an aircraft experiences trouble and further flight is impossible, making an emergency landing necessary for safety.

[0196] (9-1) Figure 26 is a block diagram showing the configuration of the flight management device 70. The flight management device 70 comprises a memory 71, a data acquisition unit 72, an emergency management unit 73, and a communication unit 74. The memory 71 stores multiple spatial cells and their reservation status. The memory 71 may also store at least one of the following information: information on areas where flight is not permitted, the flight route of each aircraft, and vector setting information in the spatial cells. The data acquisition unit 72 acquires various data used to determine the flight route of an aircraft, similar to the data acquisition unit 32.

[0197] As described later, the emergency management unit 73 executes the appropriate processing when it receives an urgent request from the aircraft 80. The communication unit 74 is the interface through which the flight management device 70 communicates with the aircraft 80.

[0198] Figure 27 is a block diagram showing the configuration of the aircraft 80. The aircraft 80 comprises a memory 81, a data acquisition unit 82, an emergency detection unit 83, a selection unit 84, a communication unit 85, and a flight control unit 86. Similar to memory 61, memory 81 stores information about spatial cell C, the current position of aircraft 60, the flight route of aircraft 60, and information about spatial cell C reserved by aircraft 60 along that flight route. The data acquisition unit 82 consists of detection units such as sensors, radar, and cameras mounted on aircraft 80, and detects when other aircraft are within a predetermined distance (for example, less than 100m). Similar to the request generation unit 63, the selection unit 84 selects a spatial cell adjacent to the currently located spatial cell that aircraft 60 should reserve, and also selects a spatial cell adjacent to the currently located spatial cell other than the rejected spatial cell when rejection information regarding the request is transmitted from the flight management device 70. Furthermore, as described later, the selection unit 84 selects a destination spatial cell in an emergency situation where it is necessary to evacuate from the current spatial cell immediately. The communication unit 85 is an interface through which the aircraft 80 communicates with the flight management device 70. The flight control unit 86 controls the movement of the aircraft 80.

[0199] The following describes a specific example of the process. After the aircraft 80 reserves a predetermined space cell, the data acquisition unit 82 detects that another aircraft is flying in the same space cell while the aircraft is flying in that space cell. Based on the results detected by the data acquisition unit 82, the emergency detection unit 83 determines that it is an emergency situation in which another aircraft is approaching. Based on the determination of the emergency detection unit 83, the aircraft 80 decides that it is necessary to evacuate its current space cell and reserve another space cell, and the selection unit 84 selects one or more evacuation space cells (evacuation cells).

[0200] For example, if the aircraft 80 is flying in a predetermined plane, the selection unit 84 may select a spatial cell located above or below the plane, or both. Also, if the data acquisition unit 82 can detect the direction and speed of another aircraft in the same spatial cell, the selection unit 84 may select one or more evacuating cells such that the vector of the direction of travel of the aircraft 80 does not overlap with the vector of the direction of travel of the other aircraft. For example, if another aircraft is located in front of the aircraft 80 and moving upward, the selection unit 84 may select a spatial cell located below the current spatial cell.

[0201] The aircraft 80 uses the communication unit 85 to transmit an urgent request regarding the movement of the spatial cell selected by the selection unit 84. At this time, the communication unit 85 may also transmit to the flight management device 70 information about the spatial cell in which the aircraft 80 is currently located, as well as detailed information about another aircraft detected by the data acquisition unit 82 (for example, information on its direction of travel and speed).

[0202] The communication unit 74 of the flight management device 70 receives an urgent request from the aircraft 80. In response to the request, the emergency management unit 73 determines whether there are any space cells among the one or more space cells related to the request that are not pre-booked and are not located in a no-fly zone. If there are space cells that meet these conditions, the emergency management unit 73 executes the reservation process for the space cell that meets the conditions and transmits information about the space cell for which the reservation process has been executed using the communication unit 74.

[0203] If there are no spatial cells that meet the conditions in the spatial cell related to the request, the emergency management unit 73 may further identify spatial cells adjacent to the spatial cell where the aircraft 80 is currently located, that are not in a no-fly zone, and that are not reserved, based on their reservation status. Here, the emergency management unit 73 may identify a single spatial cell based on real-time data, similar to the request generation unit 63 described above. The emergency management unit 73 executes the reservation process for the identified spatial cell and transmits information about the spatial cell for which the reservation process has been performed using the communication unit 74.

[0204] Based on the received information, aircraft 80 moves to a reserved space cell as quickly as possible. This allows aircraft 80 to avoid collisions with other aircraft and fly safely.

[0205] Furthermore, the flight management device 70 may also include the route generation unit 33 shown in Embodiment 2. After the emergency management unit 73 identifies the spatial cells to which the aircraft 80 should take refuge, the route generation unit 33 generates a new flight route for the aircraft 80 based on the original flight route of the aircraft 80 stored in the memory 71, the reservation status of the spatial cells, the location information of the identified spatial cells, and the data of the no-fly zone. For example, the route generation unit 33 may generate a new flight route that allows the aircraft 80 to return to its original flight route after flying through a predetermined number of refuge spatial cells (for example, after flying through spatial cells located vertically away from the plane in which multiple aircraft are flying). At that time, the flight management device 70 may perform reservation processing for all or some of the spatial cells in the newly generated flight route. The flight management device 70 transmits the information of the newly generated flight route or the information of the newly reserved spatial cells to the aircraft 80. The aircraft 80 stores this information in the memory 81.

[0206] Alternatively, the aircraft 80 may further include the route generation unit 43 shown in Embodiment 2. After receiving information on the spatial cells for which reservation processing has been performed from the flight management device 70, the route generation unit 43 determines a new flight route for the aircraft 80 using the original flight route information stored in the memory 41, the data acquired by the data acquisition unit 82, and the data on the non-flyable area. The method for determining the flight route is as described above. The aircraft 80 then uses the communication unit 85 to transmit a request for the movement of all or part of the spatial cells related to the newly determined flight route. The flight management device 70 performs the spatial cell reservation processing by executing the process described in Embodiment 3 (particularly Figure 9).

[0207] As described above, the flight management device 70 or the aircraft 80 can generate a new flight route after evacuation and provide guidance to the aircraft 80.

[0208] (9-2) Next, we will describe an example of making an emergency landing when the aircraft's battery level falls below a predetermined threshold. The configuration of the flight management device 70 and the aircraft 80 is as shown in Figures 26 and 27.

[0209] First, the data acquisition unit 82 detects that a problem has occurred with the aircraft 80. The problem may be that the battery level is below a predetermined threshold, that there is an engine malfunction in the aircraft 80, or that there is a sudden change in weather. A sudden change in weather means that at least one of the following occurs: precipitation per hour exceeding a predetermined value, strong winds exceeding a predetermined wind speed, or a drop in atmospheric pressure exceeding a predetermined value, resulting in weather conditions unsuitable for flight. This information can be acquired by sensors attached to the battery and engine, and by sensors that detect weather information.

[0210] The emergency detection unit 83 determines, based on the detection results of the data acquisition unit 82, that an emergency landing is necessary. The selection unit 84 then selects one or more evacuation space cells (evacuation cells). The selection unit 84 may select a space cell located below the space cell where the aircraft 80 is currently located for a rapid emergency landing. However, instead of, or in conjunction with, the selection unit 84 may, based on the real-time data described above, select a space cell in front of or to the side of the space cell where the aircraft 80 is currently located that consumes less battery power during movement.

[0211] The aircraft 80 uses the communication unit 85 to transmit an urgent request regarding the movement of the spatial cell selected by the selection unit 84. At this time, the communication unit 85 may also transmit information about the spatial cell in which the aircraft 80 is currently located to the flight management device 70.

[0212] The communication unit 74 of the flight management device 70 receives an urgent request from the aircraft 80 regarding an emergency landing. The emergency management unit 73, in response to the request, performs the same determination and reservation process as in (9-1) and transmits information about the reserved space cell to the aircraft 80. Based on the received information, the aircraft 80 moves to the reserved space cell.

[0213] The flight management device 70 may also include the route generation unit 33 shown in Embodiment 2. After the emergency management unit 73 identifies a space cell to which the aircraft 80 should take refuge, the route generation unit 33 generates a new flight route for the aircraft 80 for emergency landing based on the location data of the space cell related to the emergency landing location stored in the memory 71, the reservation status of the space cell, the location information of the identified space cell, and the data of the unflyable area. The route generation unit 33 may also generate a flight route that minimizes the time to the emergency landing location or the battery consumption. The flight management device 70 may also perform reservation processing for all or some of the space cells in the newly generated flight route. The flight management device 70 transmits the information of the newly generated flight route or the information of the newly reserved space cells to the aircraft 80. The aircraft 80 stores this information in the memory 81.

[0214] Alternatively, the vehicle 80 may further include the route generation unit 43 described in the second embodiment. After receiving information on the space cells for which reservation processing has been executed from the flight management device 70, the route generation unit 43 uses the position data of the space cells related to the potentially emergency landing sites stored in the memory 81, the data acquired by the data acquisition unit 82, and the data on no-fly areas to generate a new flight route for the emergency landing of the vehicle 80. Then, the vehicle 80 uses the communication unit 85 to transmit requests for all or some of the space cells in the newly determined flight route. The flight management device 70 performs reservation processing for the space cells by executing the processing described in the third embodiment (particularly FIG. 9).

[0215] In (9-1) and (9-2), when the flight management device 70 or the vehicle 80 detects or receives information that two or more vehicles are flying in the same cell, or that the remaining battery level of a vehicle is less than a predetermined value and an emergency landing is necessary, it may notify the local authority in charge of the area of the danger.

[0216] Also, in (9-1) and (9-2), when an emergency detection unit 83 of the vehicle 80 detects an emergency, the vehicle 80 does not necessarily have to transmit a request regarding a specific space cell to the flight management device 70. The vehicle 80 notifies the flight management device 70 of emergency information including information on the emergency situation detected by the emergency detection unit 83 (such as a situation where another vehicle is approaching the vehicle 80, a situation where the remaining battery level is less than a predetermined value, etc.) and the position information of the space cell in which the vehicle 80 is flying. The emergency management unit 73 of the flight management device 70 selects a space cell for the evacuation of the vehicle 80 based on the emergency information. <00009​​​​​ Furthermore, if the remaining battery level of the aircraft 80 is below a predetermined value, the emergency management unit 73 may select a space cell that is not in a no-fly zone and is not reserved, and which is (i) a space cell located below the space cell in which the aircraft 80 is currently located, or (ii) a space cell that requires the minimum battery consumption to move from the current space cell. In addition, the flight management device 70 may generate a flight route for the aircraft 80 to make an emergency landing and reserve all or part of the space cells along that flight route.

[0219] Furthermore, in (9-2), the flight management device 70 may set the priority of the aircraft 80 that sent the emergency landing request to "high". The emergency management unit 73 of the flight management device 70 then identifies the shortest route or the route with the minimum battery consumption from the space cell where the aircraft 80 is currently located or the requested space cell to the space cell where an emergency landing is possible, regardless of the reservation status of the space cells. The emergency management unit 73 then reserves all or some of the space cells along the identified route.

[0220] The emergency management unit 73 cancels the reservation in memory 71 for other aircraft that have reserved the spatial cell related to the identified route (i.e., other aircraft currently flying along the route or planning to fly along it in the future), and also notifies the other aircraft that the reservation has been canceled. The aircraft that receive the notification promptly move out of their current spatial cell or process a request for the next spatial cell to move to.

[0221] Furthermore, the emergency management unit 73 may cancel the reservations in memory 71 for other aircraft that have reserved a space cell relating to a location where an emergency landing is possible and / or a space cell adjacent thereto, and may also notify those aircraft that the reservation has been canceled. "Adjacent space cell" means, for example, a space cell that includes an area within a predetermined distance from the space cell relating to a location where an emergency landing is possible. In response to the received notification, the aircraft may decide again which space cell to fly and send a request for permission to fly the space cell.

[0222] As described above, the flight management device 70 can improve the safety of the aircraft experiencing the emergency and other aircraft.

[0223] Embodiment 10 In this embodiment, the flight control device further explains how it restricts or prohibits the aircraft from moving to a specific spatial cell.

[0224] (10-1) As in Embodiment 1, if a building or other structure exists within space S and an area where flight is impossible occurs, the flight management device 10 may store that area as a no-fly zone in memory 11. However, the flight management device may also set space cells that satisfy other conditions as no-fly zones. Other conditions include, for example, space cells that are entirely or partially occupied by densely populated areas, airports, military facilities, government facilities, etc., and space cells in the vicinity (e.g., adjacent) of such cells. The setting of no-fly zones as described above may be permanent or temporary, and the setting of no-fly zones for all or some space cells may be switched on or off automatically or manually (operation of the flight management device by the operator). Space cells where the no-fly zone setting is enabled become areas where aircraft cannot fly, and space cells where the no-fly zone setting is disabled become areas where aircraft can fly.

[0225] Furthermore, the flight management system may acquire weather information from weather sensors or external networks indicating that unsuitable weather conditions for flight are occurring in a designated area within the space it manages. Unsuitable weather conditions for flight include, for example, heavy rain, strong winds, lightning, tornadoes, etc. The flight management system may also determine that unsuitable weather conditions for flight are occurring by determining from the weather information that precipitation per hour exceeds a predetermined value, strong winds exceed a predetermined wind speed, or a pressure drop exceeds a predetermined value are occurring.

[0226] When unsuitable weather conditions occur in a designated area, the flight management system sets the spatial cells constituting that area as unflyable zones. This setting may be applied during the period in which such weather conditions occur and deactivated (disabled) after the period ends. The setting can be deactivated automatically or manually. For example, the flight management system may obtain weather information from an external network and determine the period in which unsuitable weather conditions will occur based on that information.

[0227] Furthermore, the flight management system may set a predetermined spatial cell, a plane in which an aircraft is flying, or a space managed by the flight management system as a no-fly zone based on the number of aircraft flying. For example, the flight management system may set a predetermined spatial cell as a no-fly zone if the density of aircraft in the surrounding spatial cells (for example, spatial cells within a predetermined distance from the predetermined spatial cell) is above a threshold. Also, the flight management system may set a predetermined plane or space as a no-fly zone if the density of aircraft in that plane or space managed by the system is above a threshold. This setting may be disabled if the detected density falls below the threshold. The density threshold can be set arbitrarily and may optionally include hysteresis.

[0228] Furthermore, in Embodiment 8, when the density of aircraft in the plane or space managed by the flight management device exceeds a threshold, the flight management device may change the size of the spatial cells that divide the plane or space from large to small. For example, suppose the flight management device sets the size of the spatial cells as shown in Figure 25B, and the density of aircraft in the entire space exceeds 20 per 100 spatial cells. In this case, the flight management device sets the size of the spatial cells to small, as shown in Figure 25A. This allows the flight management device to manage the flight of a large number of aircraft.

[0229] (10-2) Furthermore, the flight control system may, if an aircraft attempting to take off meets certain conditions, restrict its movement to a space cell located above its current position, thereby preventing the aircraft from taking off.

[0230] For example, the data acquisition unit 32 of the flight management device 30 in Embodiment 2 may acquire real-time data of the aircraft using a communication protocol before it takes off from the departure point. The real-time data is information about the aircraft's status, including at least one of the following: battery level, engine status, and aircraft maintenance status (e.g., whether or not a vehicle inspection has been performed within a predetermined period). If the aircraft is a flying car, the status of the driver's license (e.g., whether or not the license is suspended) may also be included in the real-time data. The driver's license information, like other real-time data, is stored in the aircraft's memory. The data acquisition unit 32 also acquires data on the aircraft's current location. The current location data is, for example, data of the spatial cell in which the aircraft is currently located, GPS data of the current location, etc.

[0231] The flight management device 30 is configured to reject the reservation process for a space cell located above the aircraft's current position if the real-time data acquired from the data acquisition unit 32 meets predetermined conditions. These predetermined conditions include, for example, at least one of the following: the battery level is below a predetermined value, the engine is malfunctioning, the aircraft has not undergone a predetermined inspection within a predetermined period, or the driver's license is suspended or expired. The flight management device 30 can also release the restriction on movement when the aircraft no longer meets the predetermined conditions. In this way, the flight management device can restrict the flight of aircraft that are considered unsafe by switching whether or not they can move to a space cell according to predetermined conditions.

[0232] The spatial cell setting changes shown in Embodiment 10 are transmitted from the flight management device to the aircraft and stored in the aircraft's memory, thereby being shared with the aircraft. Furthermore, the flight restrictions to the spatial cells, etc., described above may also be implemented using the vector-based setting method described in Embodiment 5.

[0233] Embodiment 11 In this embodiment, a flight method that is comfortable for the passengers on board the aircraft will be explained in detail. In previous embodiments, when the aircraft changed direction during flight, it sometimes flew at right angles or nearly right angles in an attempt to move along the arrangement of spatial cells. However, this flight method was sometimes uncomfortable for the passengers.

[0234] In this embodiment, the following processing is performed to suppress such situations. That is, the flight route generation unit of the aircraft determines the flight route from its current location to the destination independently of the physical properties (size and shape) of the spatial cell. This flight route can be determined by the following factors as related information. For example, the flight route may be determined after considering at least one of the following: the flyable area of ​​space S other than the unflyable area, or weather information between the departure point and the destination (e.g., whether or not there is rainfall, wind speed and wind direction information). The route generation unit may also consider distance, battery consumption, and required time (travel time) as related information when setting the flight route. For example, the route generation unit can calculate one of the following: the flight route with the shortest distance, the flight route with the lowest battery consumption, or the flight route with the shortest required time.

[0235] Furthermore, the aircraft may obtain from the flight management device the current and future reservation status of other aircraft in the flight route and the surrounding space cells (for example, space cells within a predetermined distance from the space cells on the flight route). Then, based on the relevant information, the route generation unit of the aircraft may select, as the target of the flight route, space cells in the surrounding space cells (for example, space cells within a predetermined distance from a predetermined space cell) where the density of aircraft is less than the threshold value during the time period when the flight is scheduled. That is, the aircraft can fly in an uncongested area. Note that an example where the aircraft generates its own flight route without depending on the flight management device is as described in (2-2) and the like.

[0236] After that, the aircraft requests the flight management device to reserve one or more space cells including the determined flight route therein. After the request is approved by the flight management device, the aircraft controls its flight to fly along the reserved space cells along the determined flight route. That is, the aircraft determines the flight route and the space cells separately.

[0237] Hereinafter, in (11-1), a specific and simple example of this method will be described, and in (11-2), an extended general case will be described. Note that the configuration of the aircraft shown below is the same as the configuration of the aircraft 40 shown in (2-2), so the description will be omitted.

[0238] (11-1) FIG. 28A shows an example of the space where the aircraft is located. Each cube in this figure represents each space cell. The cell where the current location (departure location) of the aircraft 40 is located is C10, and the destination cell is D10. D10 is located at a place that has moved 3 in the x direction, -2 in the y direction, and -1 in the z direction from C10. Here, a plane composed of space cells at the same z-direction position (same height) as C10 is called UF, and a plane composed of space cells at the same z-direction position as D10 is called LF. Also, for simplicity, it is assumed that all the space cells shown in FIG. 28A are in a state where the aircraft 40 can pass through.

[0239] In this state, the route generation unit 43 of the aircraft 40 generates a flight route from C10 to D10. At this time, the route generation unit 43 defines a straight line passing through C10 to D10 as the shortest route from C10 to D10.

[0240] Figure 28B shows the determined route as viewed from the top view in Figure 28A, and Figure 28C shows the route as viewed from the side view in Figure 28A. The hatched spatial cells in Figures 28B and 28C are spatial cells that contain the determined route and are reserved for the flight of the aircraft 40. The spatial cell of the current location also needs to be reserved and is therefore hatched in these figures.

[0241] Figure 28D shows the reserved spatial cells indicated by hatching in Figure 28A. As shown in Figure 28D, when the aircraft 40 determines its route, it requests the flight management system via the transmitter 44 to reserve a total of 3 spatial cells in planar UF and a total of 4 spatial cells in planar DF. Details of this request are as shown in (2-2). After the request is approved by the flight management system, the flight control unit 45 controls the flight so that the reserved spatial cells fly along the route shown in Figures 28B and 28C.

[0242] Through the above process, the aircraft 40 becomes capable of traveling along a straight flight path, providing a more comfortable flight for its passengers.

[0243] If, when the aircraft 40 makes a request, at least one of the spatial cells to be requested has already been reserved by another aircraft, the flight management device may reject the request and send rejection information to the aircraft 40, as described in other embodiments. In that case, the route generation unit 43 of the aircraft 40 calculates and sets a new flight route that does not include the rejected spatial cell. For example, the route generation unit 43 may determine a route that does not include the rejected spatial cell, taking into account at least one of the following: the flyable area of ​​space S other than the no-fly zone, weather information between the departure point and the destination, or information on uncongested areas. The route generation unit 43 may also set the flight route to be one of the following among the routes that do not include the rejected spatial cell: the shortest distance, the flight route with the lowest battery consumption, or the flight route with the shortest required time. Details of this calculation method are as described above. The aircraft 40 then requests the flight management device again to reserve a spatial cell that includes its flight route. In this way, the aircraft generates a flight route and requests the reservation of spatial cells related to that flight route until it is approved by the flight management system.

[0244] Furthermore, when requesting a reservation, the aircraft 40 may request the reservation of a space cell close to C10, such as a space cell adjacent to C10, which constitutes part of the flight route rather than all of it. In this case, after the request is approved by the flight management system, the aircraft 40 moves to a reserved space cell that is on the flight route and closest to D10, generates a flight route from that cell to D10, and requests the flight management system to reserve all or part of the space cells that constitute that route. This process makes it easier for the aircraft 40 to have its request approved and to move compared to when it tries to reserve all the necessary space cells in a single request. The number of space cells that can be reserved in a single request may be changed according to the aircraft's priority, etc., as described in (2-2).

[0245] (11-2) Next, we will explain a generalized example. Hereinafter, we define a three-dimensional region R10 as a space delimited by the maximum dimensions of length (l) in the x-axis direction, width (w) in the y-axis direction, and height (h) in the z-axis direction. The x, y, and z directions are as shown in Figure 28A. Furthermore, we assume that C is the set of all spatial cells in a single dimension along a single axis. This set starts from the origin of that axis and ends at the maximum dimension of that axis. The spatial cells included in C each have a predetermined size, structure, etc., and for convenience, they are shown here as cubes, but as will be described later, they may have other structures.In this case, C is expressed as follows. C={C0, C1, ... C n | C n is C n-1 A space cell adjacent to it, where n is an index (natural number) greater than or equal to 1. (1) Also, the following C 3 Let be the set of all three-dimensional cells contained within the region R. C 3 ={C 0,0,0 , C 1,0,0 , ··· C i,j,k | C i,j,k is C i-1,j,k、 C i,j-1,k and C i,j,k-1 It is a space cell adjacent to it, where i, j, and k are indices (natural numbers) greater than or equal to 1. (2)

[0246] Then, spacetime ST is defined as all cells C within region R at any given time. 3 The state is as follows. In this case, ST is defined as follows. ST={R0, R1,···R n | n is the index of a predetermined time interval (a natural number greater than or equal to 1)}...(3)

[0247] Figure 29A is a schematic diagram of spacetime ST as defined in (3). The regions R0, R1, ... are arranged in a continuous sequence along the time axis. Furthermore, each spatial cell (hereinafter also referred to as a spacetime cell) in four-dimensional spacetime, taking into account the time element t, is C i,j,k,tIt should be written as follows.

[0248] Next, region R, as follows: i Defines the set F of all flying objects at a specific time within that period. F={F1, F2, ...F n | n is the number of flying objects in Ri}...(4) (4) F i is region R t A specific spatial cell C was introduced. i,j,k It is a single flying object occupying F. i The aircraft moves by drawing an appropriate flight route from a predetermined starting point to a predetermined ending point. The aircraft can perform this movement arbitrarily or by programmatically considering relevant information. Relevant information refers to factors such as weather information, congestion, and travel time, as described in (11-1).

[0249] F i In this flight route, all spacetime cells C along that route i,j,k,t Space cells must be allocated in such a way that the flight path is valid (flyable). However, if there are multiple routes that satisfy this condition, any one of them may be assigned as the flight path.

[0250] Figures 29B and 29C are schematic diagrams showing the flight path that F1 takes in spacetime ST. The horizontal axis in Figures 29B and 29C represents the time axis, and each spacetime cell C i,j,k,tFor simplicity, the space is represented as a two-dimensional square, and space cells that cannot be assigned due to other aircraft passing through them are shown with diagonal hatching. Figure 29B shows that F1 reaches its destination D11 by passing through routes (subroutes) V1, V2, and V3 from its departure point C11. Figure 29C also shows that F1 reaches its destination D11 by passing through subroutes V1' and V2' from its departure point C11. Both subroutes are configured to avoid space cells that cannot be assigned. Figure 29D shows cells assigned as flight routes along subroutes V1-V3 in Figure 29B with vertical dashed hatching.

[0251] The flight route FR of each aircraft can be expressed as follows, using sub-route V: FR={V1, V2, ...V n | V n This is a four-dimensional vector on ST representing a subroot. (5) In particular, in (5), V1 is a four-dimensional vector representing the first sub-route from the starting point, and V n This is a four-dimensional vector representing the final sub-route that terminates at the destination.

[0252] Also, spacetime cell C i,j,k,t Flying object F consisting of i Here, A is the set of cells assigned along the path. i Defined as follows: Set A i It is defined as follows: A i ={C i,j,k,t , identical or adjacent (C i,j,k,t+1 ),···C n | n is a four-dimensional index consisting of the indices i, j, k, and t in the sequence at the destination cell. (6) set A i It consists of one or more spacetime cells, depending on factors such as the priority of the aircraft. Aircraft F i This is sub-route V nBefore passing through, it is necessary to allocate the spatial cells that make up the subroute, for example, by performing the reservation process described above with the flight management system. If the allocation of cells required for the subroute cannot be obtained, then aircraft F i It can generate new subroutes. Also, flying object F i When leaving a space cell during flight, it is necessary to release the allocation of that space cell by performing a release process on the flight management device, for example, as shown in Embodiment 4.

[0253] Similarly, spacetime cell C l,m,p,t Flying object F consisting of j Here, B is the set of cells assigned along the path. i This is how it is defined. B i ={C l,m,p,t , identical or adjacent (C l,m,n,p+1 ),···C n | n is a four-dimensional index consisting of the indices l, m, p, and t in the sequence at the destination cell. (7) And then, flying object F i and F j For safe flight, Group A i is set B i They are mutually exclusive (A i ∩B i It must be constructed such that = 0. This condition applies to set B i This condition must be satisfied not only for this particular aircraft, but also for the set of spacetime cells assigned to all other aircraft.

[0254] For example, the memory 41 of the aircraft 40 stores multiple spacetime cells that divide the space and time in which the aircraft flies, in a format that can be identified by an index or the like. The route generation unit 43 also obtains information on spacetime cells that have been assigned (reserved) to other aircraft from the flight management device or other aircraft. Based on the above method, the route generation unit 43 sets a flight route consisting of spacetime cells that are exclusive to the set of spacetime cells assigned to all other aircraft, and assigns spacetime cells that constitute its sub-route. This makes it possible for the aircraft 40 to fly along that flight route. The aircraft 40 can also determine a flight route that satisfies conditions such as weather information and distance as shown in (11-1). The flight control unit 45 controls the flight of the aircraft 40 so that it moves to the assigned spacetime cells along the determined flight route.

[0255] As shown above, by extending the domain for determining the flight path from three dimensions to four dimensions including time, it becomes possible to have multiple reservations for a single 3D cell. Therefore, even if uncertainties arise due to the actual operation of the aircraft, such as changes in the aircraft's speed, the aircraft can easily adjust its path in response. Furthermore, the above method can be handled by simply including the time dimension in the components of matrix / vector operations in standard space, thus simplifying the computation process.

[0256] It should be noted that the determination of the flight route of the aircraft as described above may be performed not by the aircraft itself, but by the flight management device according to each embodiment. The flight management device can assign (reserve) flight routes to multiple aircraft under its management using the method of Embodiment 11, or it can use the method of Embodiment 11 to derive candidate flight routes to propose to the aircraft in Embodiment 3. In the latter case, the request generation unit 63 of the aircraft 60 determines the flight route by agreeing to the proposed flight route. The flight control unit 64 then controls the flight of the aircraft 60 to move along the determined flight route to a spatial cell for which movement is permitted according to permission information received from the flight management device 50.

[0257] Embodiment 12 In this embodiment, variations of the spatial cell are described. Each spatial cell, which is set by the flight control device or aircraft to divide space, can take any structure as long as it is a structure that can be adjacent to other spatial cells on all sides (i.e., a structure that can fill three-dimensional space without gaps).

[0258] Figure 30A shows a space-filling structure (honeycomb structure) where the space cells are regular hexagonal prisms. In Figure 30A, the base of each space cell lies on the xy-plane, and the generatrix of the cells (regular hexagonal prisms) is aligned with the z-axis (height direction). However, the base of each space cell may also lie on the xz-plane or the yz-plane.

[0259] Figure 30B is a schematic diagram illustrating the advantages of using a regular hexagonal prism as the spatial cell, as shown in Figure 30A. Figure 30B shows the state in which the flying object passes through multiple spatial cells along sub-route V, with (1) showing the case where the spatial cell is a regular hexagonal prism and (2) showing the case where the spatial cell is a cube. Although the direction and distance of flight are the same in (1) and (2), the number of cells that the flying object passes through is 2 in the case of (1) compared to 3 in the case of (2). Therefore, the spatial cell reservation process described in the above embodiment can be further simplified, leading to a reduction in computing resources.

[0260] Figure 30C shows a space-filling structure when the space cells are regular triangular prisms. In Figure 30C, the base of each space cell lies on the xy-plane and the generatrix of the cell is aligned with the z-axis, but the base of each space cell may also lie on the xz-plane or the yz-plane.

[0261] In addition to the examples shown above, a prism with a base shape that can fill a plane can also be used as a spatial cell. However, by using a regular hexagonal prism as the spatial cell, one spatial cell can occupy more adjacent spatial cells, and as mentioned above, the number of cells that an aircraft passes through can be reduced even for the same distance and direction of flight.

[0262] Embodiment 13 In this embodiment, we describe a technology that, in the spatial cell allocation (reservation) of each flight route for multiple aircraft, does not require processing by a flight management device, but instead performs spatial cell allocation as a result of communication between aircraft. Hereinafter, this technology will also be referred to as distributed spatial cell technology.

[0263] Figure 31 shows the configuration of the aircraft 40' according to Embodiment 13. Compared to the configuration of the aircraft 40 shown in (2-2), the aircraft 40' is equipped with a communication unit 46 instead of a transmission unit 44. The communication unit 46 enables wireless communication with other aircraft, flight management devices, servers described later, etc. The aircraft 40' also further includes a ruling unit 47 that performs ruling processing, which will be described in detail below. A simple example of this method will be described in (13-1), and further variations will be described in (13-2) and beyond.

[0264] (13-1) Figure 32A is a schematic diagram showing the spatial positions of aircraft F1-F5. For simplification, each spatial cell is represented by a two-dimensional square. In this example, we focus on aircraft F2. Aircraft F2 forms a distributed system with nearby aircraft to assign each spatial cell. In Figure 32A, aircraft F1-F4 form a distributed system within Region 1 (indicated by hatching), which is within three cells of aircraft F2's position. Aircraft F1-F4 require an adjudication in which all of them participate to decide which spatial cell each will move to next within Region 1. However, in Figure 32A, aircraft F4 can also move outside of Region 1.

[0265] Figure 32B is a schematic diagram focusing on aircraft F4 in the positional state of the aircraft shown in Figure 32A. In Figure 32B, aircraft F1-F4 form a distributed system within Region 2 (indicated by hatching), which is within 3 cells of the position of aircraft F4. Each of aircraft F1-F4 requires a ruling involving all of them to decide which spatial cell to move to next within Region 2. Hereafter, participating aircraft will also be referred to as "participants." However, in Figure 32B, aircraft F1-F3 can also move outside of Region 2. Note that this distributed system within Region 2 is a separate system from the distributed system within Region 1 described above.

[0266] The arbitration made in each decentralized system may be done by voting in which each aircraft has equal rights, or, as described below, by voting with different weights depending on predetermined conditions. This process does not require a flight management device (external server; especially a central server) that calculates the next destination for all aircraft; the allocation process is completed and implemented within the system. For this purpose, the aircraft in the surrounding environment that form the decentralized system play the role of a flight management system (especially a flight management device), that is, the role of arbitrating the allocation of spatial cells. The arbitration in each decentralized system is performed using blockchain or a variation thereof. Here, the decentralized assets of the decentralized system represent the allocation status of spatial cells within the region. The result of the arbitration process represents the response of permission or denial to the spatial cell allocation request. This response is similar to the response in the flight management device described above.

[0267] Each aircraft constituting the distributed system can obtain each other's location information by broadcasting its own position via wireless communication from the communication unit 46. The area encompassing the distributed system is the range within which each aircraft can establish and maintain peer-to-peer (P2P) communication with each other in order to perform arbitration. Furthermore, since the aircraft are moving, the participants constituting each distributed system change over time. This P2P communication can be performed using the broadcast (multicast) network protocol of UDP (User Datagram Protocol), which is widely used.

[0268] Each aircraft has priority and status information stored in memory, which are used to weight the vote in the ruling. Status information includes real-time data such as battery level (operating time) and whether or not there is an emergency. An emergency is the detection of a problem as described in (9-2). Note that a state where the battery level falls below a predetermined threshold may be reflected by increasing the aircraft's priority, or it may be reflected as the occurrence of an emergency. In the ruling, at least one of priority and status information is taken into consideration. Therefore, for example, if multiple aircraft request the same allocation cell, the ruling will be made in such a way that the request of the aircraft with the higher priority is more likely to be granted.

[0269] To give a concrete example, an aircraft located near a spatial cell that is an "airport" where aircraft take off and land (for example, an aircraft located within three cells of that spatial cell) is likely to be in the middle of a takeoff or landing operation. Therefore, in order to give priority to the flight of that aircraft, that aircraft, or other aircraft that make up the same distributed system as that aircraft, may be given a higher priority than other aircraft. Also, for aircraft located near an "airport," that aircraft, or other aircraft that make up the same distributed system as that aircraft, may be given a higher priority to aircraft at lower altitudes than to aircraft at higher altitudes. By setting priorities as described above, aircraft that are performing takeoff or landing are more likely to be able to continue their operation, thus making it easier to achieve safe flight.

[0270] The arbitration panel 47 may use one of the following elements, or any combination of any multiple elements, to determine the weighting in the vote. However, the elements listed below are examples only and are not limited to them. (a) Each aircraft's flight route: If a target cell (a spatial cell located near each aircraft that is subject to allocation by voting) is not on a particular aircraft's flight route, the weight of that aircraft's vote for that target cell may be reduced compared to another aircraft whose target cell is on its flight route. (b) Direction of movement: If an aircraft is moving away from a target cell, it can have a lower weight on its vote for that target cell compared to another aircraft moving towards the target cell. (c) Distance from the aircraft to the target cell: The closer the aircraft is to the target cell, the greater the weight of the aircraft's vote for that target cell. (d) Status information of the aircraft: For example, the shorter the battery life of an aircraft, the greater the weight of its vote for the target cell can be for safety reasons. (e) Priority (f) Cell occupancy status: Aircraft that already occupy an existing cell within the requested timeframe are preferably given a large weight (e.g., the largest weight in a distributed system) in the ruling of that existing cell. (g) Cell allocation status: It is preferable that aircraft that already have an allocation status for a requested cell, determined before receiving a new allocation request, also have a large weight (e.g., the largest weight in a distributed system) in the ruling for that requested cell.

[0271] Furthermore, distributed spatial cell technology is more preferably applied to regions where the number of participants in a distributed system is relatively small (e.g., around 10-20), that is, regions where the density of flying objects in space is generally considered to be low (e.g., rural areas). This is because it is thought that the time required for the arbitration process can be shortened compared to regions with a larger number of participants in a distributed system (e.g., 50 or more).

[0272] Furthermore, it is preferable that the voting process for target cells considers only votes received by participants within a specified period (a requested timeframe, e.g., in seconds) to be valid.

[0273] Furthermore, one of the participating aircraft calculates its ruling for each target cell and broadcasts the result to all participants. This enables rulings based on the consensus of all participants. By using blockchain technology in this process, the ruling unit 47 can enhance the resistance to data tampering and reduce the possibility of the ruling process being interrupted due to failures or other issues.

[0274] Figure 32C is a schematic diagram showing the ruling in space between two aircraft F1 and F2. The specific details of the ruling process described above will be explained below with reference to this figure. In Figure 32C, space is represented in two dimensions for simplification, and the space is divided into 8 x 10 spatial cells. At the same time, aircraft F1 is at C 3,2 Located in the spatial cell, the aircraft F2 is C 3,6 It is located in the spatial cell. The arrows in Figure 32C indicate the flight routes of each aircraft. Regions A1 and A2 are the neighboring regions of aircraft F1 and F2, respectively, and are designated by each aircraft as arbitration regions. As described above, aircraft F1 and F2 are able to participate in the arbitration process by knowing each other's positions and establishing communication with each other via P2P.

[0275] In this example, regions A1 and A2 are C 2,4 , C 2,5 , C 3,4 , C 3,5 , C 4,4 , C 4,5 , C 5,4 , C 5,5 There is an overlap between these two areas. Aircraft F1 and F2 understand the overlap relationship in each of these areas through broadcast communication. Therefore, aircraft F2 can participate in the arbitration process regarding aircraft F1 for these spatial cells. For example, aircraft F1 is C 4,4When it assigns a space cell as its desired move cell, it broadcasts that request to aircraft F2. At this time, it is assumed that aircraft F2 assigns that space cell to a time frame that overlaps with aircraft F1. As in this example, it is F2's intention to also request the assignment of the same space cell, and aircraft F2 can respond with a weighted vote "No". F2 also C 4,4 Each aircraft can individually initiate its own allocation request, which is broadcast to F1, and F1 can then sequentially respond with weighted votes of "No". F1 and F2 calculate the result of the initiated voting process based on an algorithm involving the weights of the requesting aircraft's votes, which include elements (a) to (g), and the weights of the responding aircraft's vote results, which also include elements (a) to (g), and publish the result. Here, since the final results of the requests, responses, and voting processes of both aircraft are published, the aircraft to be allocated will be the object with the highest weight in the result of the initiated voting process. Subsequently, all participants (F1, F2) in this ruling are rebroadcast that the allocation of this spatial cell was successful. Participants can also abstain from the voting process if they are not interested in the voting results.

[0276] Furthermore, as aircraft F1 and F2 continue to move along their respective flight paths, their regions A1 and A2 will overlap even more than the state shown in Figure 32C. Consequently, the number of spatial cells that each aircraft is involved in during the ruling process increases. This state continues until their respective flight paths begin to diverge from each other.

[0277] Furthermore, regions A1 and A2 may be resized based on, for example, at least one of the elements shown in (a) to (g) above. In addition, the positions of aircraft F1 and F2 within regions A1 and A2 may be offset based on at least one of these elements (for example, the flight path). In other words, aircraft F1 and F2 do not need to be positioned at the center of each region.

[0278] In the example shown above, for the sake of simplicity, the case where the number of participants is 2 was considered. Next, an example where the number of participants increases and the adjudication becomes complicated will be shown.

[0279] FIG. 32D is a schematic diagram showing the adjudication within the space of four flying objects F3 - F6. Hereinafter, further specific examples will be described while referring to this figure. <000!125> In FIG. 32D, the coordinate settings of the space and the space cells are the same as those in FIG. 32C. At the same time, the flying object F3 is located in the space cell of C 3,2 the flying object F4 is located in the space cell of C 3,6 the flying object F5 is located in the space cell of C 3,3 the flying object F6 is located in the space cell of C 5,4 The arrows extending from each flying object in FIG. 32D indicate the flight routes of each flying object. The regions A3 - A6 are the vicinity regions of the flying objects F3 - F6 respectively, and are set as adjudication regions by each flying object. Also, the flying objects F3 - F6 can participate in the adjudication process by grasping each other's positions and establishing communication with each other via P2P. Hereinafter, the adjudication process regarding the allocation of the space cell C 4,3 by F3 and F6 and C 3,5 by F4 will be described.

[0281] In this example, since the regions A3, A5 and A6 overlap in the cell C 4,3 F3, F5 and F6 participate in the adjudication regarding the allocation of the cell C 4,3 Note that since the region A4 does not cover the cell C 4,3 at the time of this vote, F4 is not a participant in this adjudication process. At this time, F3 starts the allocation request for C 4,3 by publicly announcing its request to F5 and F6. Similarly, F6 also starts the allocation request for C 4,3 <00!131> C 4,3Since it does not exist in the F5 route, the voting weight of F5 may accordingly decrease. However, F5 may still abstain or choose to vote for F3 or F6 or both according to its preference tendency. In one scenario, based on elements (a) - (g) presented by each claimant, since the F6 route branches more from the F5 route than the F3 route, F5 may choose F6, and if possible, due to other factors, considering safety, it responds with "No" to F3 and "Yes" to F6. F6 is presumed to respond with a weighted "No" vote to F3's request, and F3 is presumed to respond with a weighted "No" vote to F6's request. F3 and F6 calculate the result of each request for the allocation including the weighted vote of each participant and the weight of each request for C 4,3 and broadcast the result of the adjudication process of each request for C 4,3 . In this case, by prioritizing F6 over F3 for F5, F6 may disclose the heaviest weighted result and obtain the allocation. Each participant may update their respective memories regarding the adjudicated allocation status of C 4,3 for F6. Using blockchain technology here, participants can reach an agreement regarding potential fluctuations in the space cell allocation status represented in the memories of individual participants at any time. Also, each participant may calculate the adjudication of all votes of all participants on behalf of each claimant and disclose their own results leading to a "consensus" process such as blockchain.

[0283] Also, since regions A4 and A5 overlap at cell C 3,5 , F4 and F5 participate in the adjudication regarding the allocation of cell C 3,5 . Also, since regions A3 and A6 do not cover this cell during this voting, F3 and F6 are not participants in this adjudication process. At this time, cell C 3,5Since it is not on F5's flight path, F5's vote will have less weight and is unlikely to have much impact on the ruling. In contrast, F4's vote will have more weight, making it more likely that F4 will make a ruling on this cell and broadcast its cell assignment evaluation.

[0284] Through the above process, we were able to demonstrate that spatial cell ruling can be performed even when a large number of aircraft are located close together. By voting based on the elements (a) to (g) described above, aircraft can rule on spatial cells where they do not want other aircraft to come.

[0285] Furthermore, participants can choose to completely opt out of a ruling if they are not interested in the ruling for a particular spatial cell. For example, in the example shown in Figure 32D, both F3 and F6 are cell C 4,3 Because it is located in the very vicinity of cell C, F3 and F6 are attempting to assign this cell to themselves almost simultaneously. F3 and F6 broadcast requests to assign this cell, and F5 receives that information. Based on that information, F5 recognizes that F3 and F6 want the cell, and instead determines that F3 is preferable to be assigned, based on the priority of F3 and F6 that it has obtained (and possibly other factors). Therefore, by prioritizing F3 over F6 with respect to that cell ("siding with F3"), F5 itself becomes cell C 4,3 Without making it its own target cell, it can effectively influence the outcome of the arbitration. Since F5's region A5 covers this cell, F5 can thus participate in the arbitration.

[0286] Also, in the example in Figure 32D, F3 is cell C 4,3 Assuming that it has obtained the assignment, F4 is in cell C 4,3 and another adjacent spatial cell, for example, C 5,3、 C 6,3又は C 6,4 Either change your route to arbitrate the allocation to cell C4,3 Within the time frame (additional time) that does not overlap with the allocation of F3 in cell C 4,3 You can choose to either re-arrange the allocation or...

[0287] Furthermore, the voting format in the ruling may resemble a so-called "cumulative vote." In this case, each participant can choose to vote on each spatial cell's ruling request or abstain and not vote. The latter means that the participant is not interested in the outcome of the ruling.

[0288] The arbitration process in each aircraft as described above is realized when the arbitration unit 47 of aircraft 40' performs the selection of whether or not to vote, the determination of the voting content, and the allocation process for each spatial cell, based on the information stored in the memory 41 and the information obtained from the communication unit 46. In this case, the flight management device according to the other embodiment exists not as a physical server, but as a blockchain-type system, virtualized among aircraft. Therefore, the allocation structure of various components (spatial cells, routes and subroutes, allocation status, etc.) has the same characteristics as those disclosed in the other embodiment.

[0289] (13-2) In the process shown in (13-1), multiple aircraft performed arbitration processing via P2P communication. However, since the P2P communication format is open to anyone, a third party may attack that communication (denial-of-service attack, snooping, etc.). Therefore, in this example, the concept of a supernode in networking is introduced to improve the robustness of the network that constitutes the distributed system.

[0290] For example, in the example shown in (13-1), an additional supernode server SN may be provided, which is used to verify the certificate of an aircraft and to associate aircraft with valid certificates with other aircraft located nearby in an arbitration process. Here, the server SN needs to know the location of each aircraft for this purpose. The server SN may also be a server dedicated to this purpose.

[0291] The term "neighborhood of an aircraft" here is uniquely generated by the server SN for each aircraft, and within that neighborhood, there may be other aircraft that are likely to fly in that neighborhood in the future (i.e., have an "interest" in the spatial cells located in the neighborhood) for reasons related to any of the aircraft's elements (a) to (g) (for example, their flight route or direction of travel is close to that aircraft).

[0292] Furthermore, the radius of the neighboring area can be arbitrarily set by the server SN, or it may be changed based on the perspective of any of the elements (a) to (g) of the aircraft (e.g., priority), the location of the target spatial cell, or other factors. For example, if the location of the target spatial cell is a sparsely populated area (e.g., a rural area), the server SN may set this radius wider than if it were located in a densely populated area (e.g., a large city). For example, in Figure 32D, the server SN can assign areas A3-A6 to each aircraft based on the factors described above.

[0293] (13-3) Figure 32E shows an example of further ruling. The spatial and spatial cell coordinate settings in Figure 32E are the same as in Figure 32C. However, Figure 32E shows the space of the airport and its surrounding area. At the same time, aircraft F7 is at C 2,1 Located in the spatial cell, the aircraft F8 is C 6,9 It is located in the spatial cell. In Figure 32E, the arrows extending from each aircraft indicate the flight path of each aircraft, and regions A7 and A8 are the neighboring regions of aircraft F7 and F8, respectively.

[0294] Furthermore, Figure 32E shows that a regional controller server 90 is provided to manage the airspace around the airport. Region A9 is the vicinity of the regional controller server 90. Here, server SN assigns regions A7-A9, which are the ruling areas, to aircraft F7, F8, and the regional controller server 90, respectively.

[0295] Figure 32F is a block diagram of the flight management system M2 in this example. The flight management system M2 comprises aircraft F7, F8 and a regional controller server 90. The configurations of aircraft F7 and F8 are as described above, so their explanation is omitted. The regional controller server 90 comprises a memory 91, a communication unit 92, a data acquisition unit 93, and a ruling unit 94.

[0296] Memory 91 stores information on multiple spatial cells C that can be identified by coordinates, etc., and the reservation status of spatial cells for multiple aircraft. Memory 91 may also store information related to spatial cells C, such as the aforementioned information on no-fly zones. Furthermore, a super-priority (i.e., a higher priority compared to all other aircraft in area A9) is set and stored in memory 91.

[0297] The communication unit 92 is an interface through which the regional controller server 90 performs P2P communication with aircraft F7 and F8. The data acquisition unit 93 consists of detection units such as sensors, radar, and cameras, and acquires information on general aircraft and other air traffic within area A9 (information on aircraft other than aircraft F7 and F8).

[0298] The ruling unit 94 performs rulings regarding each spatial cell C shown in Figure 32E based on information obtained from the memory 91 and the communication unit 92. Here, since superpriority is set as the priority for the regional controller server 90, the regional controller server 90 can effectively control the ruling results for spatial cells for all aircraft within its region A9.

[0299] Aircraft F7 and F8 are able to participate in the arbitration process by determining each other's positions and establishing communication via P2P. Similarly, the regional controller server 90 is also able to participate in the arbitration process by establishing communication with aircraft F7 and F8 via P2P.

[0300] The following provides an illustrative explanation of the ruling process of the ruling unit 94. For example, aircraft F7 is a safe aircraft selected by the airport air traffic controller to allow entry into the airport area. The ruling unit 94 can perform the aforementioned ruling control to ensure that the position of aircraft F7 does not overlap with other aircraft. Also, aircraft F8 is in space cell C 6,8 Assuming that the request for the allocation is from a privately owned aircraft, the ruling unit 94 may deny the allocation and transmit denial information as a response to the ruling allocation. This ruling is based on the reservation status of the space cell and information regarding air traffic.

[0301] In either of these cases, the ruling unit 94 can effectively determine the ruling result based on the super-priority priority. Therefore, aircraft F7 can land at the airport by moving to the space cell assigned to it, in accordance with the ruling of the regional controller server 90. Also, aircraft F8 recalculates its flight route based on the disallowance information received from the regional controller server 90, and C 6,8 It may request a different cell allocation. This different cell is outside the area of ​​the regional controller server (e.g., C 7,9 Therefore, the regional controller server will not be a participant in the ruling for this cell. As a result, the regional controller server 90 will not place aircraft F8 in spatial cell C 6,8 It is possible to prevent it from being moved.

[0302] It is assumed that a large number of aircraft will be present around the airport for takeoffs and landings. In such cases, by giving special priority to the regional controller server 90 that manages the airport and having it participate in a distributed system, the arbitration process for the space around the airport can be efficiently controlled. Furthermore, the regional controller server 90 only manages the local area A9, and the allocation of space cells in other areas with low aircraft density (e.g., outside A9) is handled by a distributed system among the aircraft, as shown in (13-1) and (13-2). Therefore, the computational load is distributed among the participants involved in any arbitration, eliminating the need to introduce a large-scale computer system as a management server. Such a system is considered particularly useful for regional airports where there is a large difference in the density of aircraft per unit volume between the area around the airport and other areas.

[0303] Figure 32G is an illustrative diagram of a system illustrating an example of such a situation. Flight management devices 50F and 50G have the same configuration as the flight management device 50 of Embodiment 3 and manage spatial regions R6 and R7, respectively. In Figure 32G, spatial region R6 includes airport 1, and spatial region R7 includes airport 2. Spatial region R8 is the region connecting airport 1 (spatial region R6) and airport 2 (spatial region R7), and the aircraft 40" moves from one spatial region R6 or R7 to the other via spatial region R8.

[0304] Here, the aircraft 40" further comprises the configuration of the aircraft 60 according to Embodiment 7, in addition to the configuration of the aircraft 40' described above. Therefore, in spatial regions R6 and R7, the aircraft 40" flies in those spatial regions by obtaining permission for the reservation of spatial cells from the flight management devices 50F and 50G. The details of this are as described in Embodiment 3. In contrast, in spatial region R8, the aircraft 40" flies without such management, forming a distributed system as described in Embodiment 13 with other aircraft in the vicinity, and making rulings regarding the surrounding spatial cells.

[0305] Thus, the spatial regions managed by the flight management devices 50F and 50G do not need to be adjacent; they can be separate regions. In this case, the flight management devices 50F and 50G may or may not be connected. This is because, since the spatial regions R6 and R7 are not adjacent, it is not necessarily required for the flight management devices 50 to share information about the aircraft 40. Furthermore, variations similar to those described in Embodiment 7 can be applied to this example.

[0306] In Embodiment 13, the following variations can also be adopted. For example, the data acquisition unit 42 may further include detection units such as sensors, radar, and cameras mounted on the aircraft 40', and may detect when another aircraft is within a predetermined distance (e.g., less than 100m). In this way, if another aircraft is approaching the aircraft abnormally close, the aircraft 40' broadcasts this information to the distributed system (P2P network) and supernodes that it forms with the other aircraft, and performs evasive action as necessary. This action may be the same as that disclosed in (9-1).

[0307] Aircraft 40' may broadcast a pulse signal containing its own identification information to other aircraft. For example, in Figure 32D, aircraft F3 broadcasts its pulse signal, and other aircraft F4-F6 and server SN detect it with their communication units, thereby detecting the presence of aircraft F3. If aircraft F3 becomes unable to communicate with other aircraft due to a malfunction in its communication unit, etc., other aircraft F4-F6 and server SN detect that the pulse signal has unexpectedly disappeared, and recognize that aircraft F3, which should normally be detectable, is no longer detectable (a so-called AWOL: absent without leave state). Based on this recognition, aircraft F4-F6 and server SN issue a warning by further broadcasting this information to other aircraft with which they can communicate. If the location where aircraft F4-F6 and server SN last detected aircraft F3's pulse can be identified from data from their communication units or data acquisition units, they may also include information about that location in the warning.

[0308] In addition to its unit configuration shown in Figure 32F, the regional controller server 90 may also include an airport air traffic control unit to more effectively control air traffic around the airport. The airport air traffic control unit can analyze the air traffic information acquired by the data acquisition unit 93 based on airport-specific guidelines and rules stored in memory 91, and update the no-fly zone information stored in memory 91. For example, the airport air traffic control unit can set space cells used by general aircraft as no-fly zones. The airport air traffic control unit may also acquire weather information from data acquisition units such as cameras and sensors installed on the network or locally, and update the no-fly zone information based on the weather information. For example, if strong winds with a wind speed above a predetermined value are blowing in area A9, the airport air traffic control unit can set space cells in the area where approaching the airport is deemed dangerous due to the strong winds as no-fly zones. As a result, the ruling unit 94 can make rulings (assign space cells to aircraft) based on the updated no-fly zone information, enabling safe and efficient takeoffs and landings of aircraft. Furthermore, this method is simple and low-cost, while also being able to reduce the large-scale calculations required for flight control.

[0309] Embodiment 14 In the above-described embodiment, the flight management device determined the position of the aircraft, received requests from the aircraft regarding spatial cells, decided whether to permit or deny them, and notified the aircraft of the result. In this embodiment, the objective is to achieve an encrypted spatial representation by using a public-key cryptography scheme for communication between the aircraft and the flight management device in order to conceal the aircraft's location while it is in flight.

[0310] Figure 33A is a block diagram of the flight management system M3. The flight management system M3 comprises aircraft F9 and F10 and a flight management device 50. When aircraft F9 and F10 send a request to the flight management device 50 for permission to move to a selected spatial cell, they send encrypted location information of the spatial cell C in which they are currently located and the spatial cell to which they wish to move during the request. The flight management device 50 receives the encrypted location information, determines whether the specific spatial cell to which the request is made is already reserved, and sends permission or denial information to aircraft F9 and F10.

[0311] Figure 33B shows the configuration of the aircraft 60' that make up aircraft F9 and F10. Compared to the configuration of aircraft 60 shown in Embodiment 3, aircraft 60' further includes an encryption processing unit 66. The encryption processing unit 66 encrypts the current location information of aircraft 60' and the location information of the movement request target with a public key acquired in advance, and the communication unit 62 transmits the encrypted location information to the flight management device 50. Furthermore, when the encryption processing unit 66 receives location information from the flight management device 50, it decrypts this information using a private key acquired in advance. The information of the public key and private key is stored in the memory 61.

[0312] The configuration of the flight management device 50 is generally as described in Embodiment 3. However, the flight management device 50 stores encrypted information of the spatial cell C, the reservation status of the spatial cell, and the flight route of each aircraft in memory 51, rather than the actual position coordinates of the cell. The flight management device 50 uses this information to perform the processing described in Embodiment 3. In other words, the flight management device 50 performs processing using encrypted spatial information, not real space.

[0313] The following describes the processes performed by the flight management system M3. Note that detailed descriptions of the following information are omitted as they are the same as those described in Embodiment 3. First, the same public and private keys are distributed to all aircraft to be managed in advance. These public and private keys are generated by a key generation server and stored in a secure location.

[0314] Each aircraft 60' encrypts its current position information and the position information it wishes to move to using a public key by the cryptographic processing unit 66, and sends the encrypted information to the flight management device 50 in the first cell reservation request. The flight management device 50 receives the request and uses the encrypted information included in the request as is to refer to the reservation status stored in the memory 51 and determine whether the specific spatial cell related to this request has already been reserved.

[0315] Figure 33C is a schematic diagram illustrating an example of the state of space cells in encrypted space and real space. Figure (A) shows the state of space cells in encrypted space, and (B) shows the state of space cells in real space. Each square in (A) and (B) represents one space cell, and the space cells labeled F9-F11 indicate the cell in which each aircraft is currently located. Space cells labeled E indicate cells that are not reserved.

[0316] (1) First, the aircraft F9 transmits encrypted information about its current spatial cell and the spatial cell to which it wishes to move, in order to move downward in real space from its current spatial cell. The flight management device 50 determines the reservation status of the spatial cell related to the request based on the encrypted information.

[0317] As can be seen from Figure 33C, the flight management device 50 cannot determine where the requested spatial cell is located in real space. However, the flight management device 50 can determine whether the requested cell is already reserved using the information stored in memory 51. As shown in the figure, the determination unit 55 determines that the requested cell is already reserved and occupied by F10. Therefore, the authorization unit 56 does not permit the aircraft F9 to move to that spatial cell and uses the communication unit 54 to send a denial message to F9 refusing the move.

[0318] When aircraft F9 receives denial information via the communication unit 62, the request generation unit 63 generates a second request (second request) based on a predetermined algorithm, selecting another spatial cell and requesting permission to move to that spatial cell. The communication unit 62 transmits this request to the flight management device 50.

[0319] (2) The communication unit 54 of the flight management device 50 receives the second request. Based on this request, the determination unit 55 of the flight management device 50 uses the reservation status stored in the memory 51 to determine whether the requested space cell is already reserved. In this case, since the requested space cell is "E", the authorization unit 56 authorizes the aircraft 60 to move to a new specific space cell. The authorization unit 56 uses the communication unit 54 to transmit authorization information to the aircraft F9, and the aircraft F9 moves toward that space cell based on that authorization information.

[0320] When sending refusal information to F9 to reject movement, the flight management device 50 may or may not have the determination unit 55 identify a candidate spatial cell (for example, cell "E") to which the aircraft F9 will move next, and send it to the aircraft F9. The flight management device 50 may not know which spatial cell is adjacent to the spatial cell in the allocation request, depending on how the encrypted space is provided, and the flight management device 50 may not have any knowledge of candidate spatial cells that may replace the requested one. Therefore, the flight management device 50 does not necessarily need to identify a candidate spatial cell to which the aircraft will move next. The coordinate information of the spatial cell transmitted at this time is encrypted, and the aircraft F9, upon receiving this information, decrypts the information using the encryption processing unit 66 to understand the position of the spatial cell in real space presented by the flight management device 50. The aircraft F9 then performs the same processing as described in Embodiment 3. Furthermore, when flight route position information is transmitted and received between the flight management device 50 and the aircraft 60, similar to the case of position information in a spatial cell, a public-key cryptography scheme can be used to configure the aircraft 60 to understand the flight route in real space and the flight management device 50 to understand the flight route in encrypted space.

[0321] In Embodiment 14, since location information is encrypted and decrypted in this manner, even if the flight management device 50 is hacked, it becomes difficult for an attacker to grasp the location information of the aircraft managed by the flight management device 50. Therefore, a more desirable effect is obtained from the standpoint of protecting personal information and cybersecurity. In addition, a server (not shown), which is a trusted entity that possesses the secret key, may be provided for the administrator, and the actual location of each aircraft may be decrypted using the secret key.

[0322] This disclosure is not limited to the embodiments described above, and can be modified as appropriate without departing from the spirit of the invention. For example, the priority of aircraft is not limited to two levels, but may be set to three or more levels. As an example, if there are three levels of priority, an emergency vehicle or a general aircraft with a battery level less than the first threshold th1 may be set as the aircraft with the highest priority, a general aircraft with a battery level less than the second threshold th2 (>th1) may be set as the aircraft with the second highest priority, and a general aircraft with a battery level of th2 or higher may be set as the aircraft with the lowest priority.

[0323] In the above embodiment, the data that an aircraft can acquire or store includes GPS information, radar information, identification information, engine status, battery level, weather information (rainfall, wind speed and direction information, atmospheric pressure, etc.), maintenance status, driver's license information, and speed information. However, the aircraft may acquire other information such as acceleration data using sensors. The aircraft may also store flight rules. Furthermore, in the above embodiment, the aircraft may detect proximity to each other by communicating via V2V (Vehicle-to-Vehicle) communication.

[0324] In the above embodiment, the data stored in the memory of the flight management system included spatial cell information, reservation status information (traffic information), and information on areas where flight is prohibited. However, in addition to these, the current time, date, weather information, and flight management rules may also be stored. Furthermore, the memory may be provided externally as a database, and the flight management system may acquire data by communicating with the database. The variations of the flight management system described above are also applicable to regional controller servers.

[0325] Figure 34 is a block diagram showing an example of the hardware configuration of a flight management system, aircraft, or regional controller server in an arbitrary embodiment. Referring to Figure 34, the information processing device 900, which collectively refers to the flight management system, aircraft, or regional controller server described above, includes a network interface 901, a processor 902, and memory 903. The network interface 901 can send and receive data to and from other devices via wireless communication. Alternatively, in the case of a flight management system, regional controller server, or external server (for example, weather, traffic, etc.), the network interface 901 can send and receive data via wired communication.

[0326] The processor 902 reads and executes software (computer programs) from the memory 903 to perform the processing of the flight management device, aircraft, or regional controller server described in the above embodiment. The processor 902 may be, for example, a microprocessor, an MPU (Micro-Processing Unit), or a CPU (Central Processing Unit). The processor 902 may include multiple processors.

[0327] Memory 903 is composed of a combination of volatile and non-volatile memory. Memory 903 may also include storage located away from the processor 902. In this case, the processor 902 may access memory 903 via an I / O (Input / Output) interface, which is not shown.

[0328] In the example shown in Figure 34, memory 903 is used to store a group of software modules. The processor 902 can read these software modules from memory 903 and execute them to perform the processing described in the above embodiment.

[0329] As explained with reference to Figure 34, each of the processors in the flight management device, aircraft, or regional controller server in the above-described embodiment executes one or more programs that include a set of instructions for causing the computer to perform the algorithm described above. This process enables the processing described in the above-described embodiment.

[0330] In the above example, the program can be stored and supplied to the computer using various types of non-transitory computer-readable medium. Non-transitory computer-readable medium includes various types of tangible storage medium. Examples of non-transitory computer-readable medium include magnetic storage media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical storage media (e.g., magneto-optical disks), CD-ROMs (Compact Disk Read Only Memory), CD-Rs (Compact Disk Recordable), CD-R / Ws (Compact Disk Rewritable), and semiconductor memory (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, RAMs (Random Access Memory)). Alternatively, the program may be supplied to the computer by various types of transient computer-readable medium. Examples of transient computer-readable medium include electrical signals, optical signals, and electromagnetic waves. A temporary computer-readable medium can supply programs to a computer via a wired communication channel (e.g., an electric wire, an optical fiber) or a wireless communication channel.

[0331] While the present disclosure has been described above with reference to embodiments, the present disclosure is not limited thereto. Various modifications to the structure and details of the present disclosure may be made that can be understood by those skilled in the art within the scope of the disclosure.

[0332] This application claims priority based on international patent application PCT / JP2020 / 040323, filed on 27 October 2020, and incorporates all of its disclosures herein. [Explanation of Symbols]

[0333] 10 Flight management device 11 Memory 12 Determination unit 13 Permission unit 20 flying objects 21 Request generation unit 22 Transmission unit 23 Flight control unit 30 Flight management device 31 Memory 32 Data acquisition unit 33 Route generation unit 34 Transmitter 40 flying object 40' flying object 41 Memory 42 Data acquisition unit 43 Route generation unit 44 Transmitter Unit 45 Flight Control Unit 46 Communications Unit 47 Tribunal 50 Flight management device 51 Memory 52 Data acquisition unit 53 Route generation unit 54 Communication Department 55 Judgment Department 56 Permission Department 57 Traffic Management Department 60 flying object 60' flying object 61 Memory 62 Communication Unit 63 Request Generation Unit 64 Flight control unit 65 Decryption unit 66 Cryptography processing unit 70 Flight management device 71 Memory 72 Data acquisition unit 73 Emergency Management Department 74 Communications Department 80 flying objects 81 Memory 82 Data acquisition unit 83 Emergency detection unit 84 Selection Unit 85 Communication Unit 86 Flight Control Unit 90 Regional Controller Servers 91 Memory 92 Communication Unit 93 Data Acquisition Unit 94 Tribunal 900 Information Processing Equipment 901 Network Interface 902 Processor 903 Memory

Claims

1. A system comprising a plurality of flying objects, Each of the plurality of flying objects is A first communication unit that forms a distributed system including the aircraft itself and one or more other aircraft by communicating with one or more other aircraft using a peer-to-peer communication method; a first arbitration unit that causes the first communication unit to transmit a vote of the other aircraft indicating permission or denial of a request for allocation to a specific spatial cell in space, the vote being weighted with respect to the specific spatial cell, to one or more of the other air vehicles, and to receive votes from the one or more of the other air vehicles indicating permission or denial of a request for allocation to the specific spatial cell, the votes being weighted with respect to the specific spatial cell, respectively; A flight control unit that moves the aircraft body; A memory for storing information on a plurality of space cells into which the space is divided, the first arbitration unit performs arbitration to determine which one of the plurality of air vehicles is to be assigned the particular spatial cell based on the vote of the own aircraft with a predetermined weighting and votes from one or more of the other air vehicles, each of which is also assigned a predetermined weighting; When the result of the determination indicates that the specific spatial cell has not been assigned to the aircraft, the flight control unit changes the flight path of the aircraft so that another spatial cell adjacent to the specific spatial cell is assigned to the aircraft, and the specific spatial cell and the other spatial cell are included in the multiple spatial cells. Distributed systems.

2. A system comprising a plurality of flying objects, Each of the plurality of flying objects is A first communication unit that forms a distributed system including the aircraft itself and one or more other aircraft by communicating with one or more other aircraft using a peer-to-peer communication method; a first arbitration unit that causes the first communication unit to transmit a vote of the other aircraft indicating permission or denial of a request for allocation to a specific spatial cell in space, the vote being weighted with respect to the specific spatial cell, to one or more of the other air vehicles, and to receive votes from the one or more of the other air vehicles indicating permission or denial of a request for allocation to the specific spatial cell, the votes being weighted with respect to the specific spatial cell, The first arbitration unit causes the first communication unit to transmit a vote of the aircraft to assign the specific space cell to another aircraft; the first arbitration unit performs arbitration to determine which one of the plurality of air vehicles is to be assigned the particular space cell based on the vote of the own aircraft with a predetermined weighting and votes from one or more of the other air vehicles, each of which is also assigned a predetermined weighting; Distributed systems.

3. The first arbitration unit of each flying object selects, from among one or more of the other flying objects that transmit votes for the specific spatial cell, the other flying object to which the specific spatial cell is assigned, based on at least one of the priority or flight route of the flying object. The distributed system of claim 2.

4. when the result of the arbitration indicates that the specific spatial cell has not been assigned to the aircraft, the first arbitration unit of each aircraft causes the first communication unit to transmit the aircraft's vote with the predetermined weighting for the specific spatial cell within a time frame that does not overlap with the assignment of other aircraft to the specific spatial cell; A distributed system according to claim 2 or 3.

5. The first communication unit of each air vehicle broadcasts the result of the arbitration to one or more of the other air vehicles. A distributed system according to any one of claims 1 to 4.

6. The first arbitration unit of each flying object determines the predetermined weight using at least one of the flight route of the flying object, a direction of travel, a distance to the specific spatial cell, status information, a priority, an occupancy state of the specific spatial cell, or an allocation state of the specific spatial cell. A distributed system according to any one of claims 1 to 5.

7. The first arbitration unit of each flying object performs the arbitration by calculating the result of each flying object's request for allocation, including a predetermined weight of each flying object itself and a weight of each flying object's request for the particular spatial cell. A distributed system according to any one of claims 1 to 6.

8. The first arbitration unit of each flying object determines which flying object will be assigned the specific spatial cell by voting based on at least one of the flight route, direction of travel, distance to the specific spatial cell, status information, priority, occupancy status of the specific spatial cell, or allocation status of the specific spatial cell of one or more of the other flying objects. A distributed system according to any one of claims 1 to 7.

9. If the air vehicle receives the vote within a specified time period, the vote is valid for the award. A distributed system according to any one of claims 1 to 8.

10. Each flying object sets an area of ​​arbitration, The first communication unit of each air vehicle transmits the area of ​​the arbitration of the air vehicle to one or more of the other air vehicles; when the specific spatial cell is an overlapping area between the arbitration area of ​​the air vehicle and one or more arbitration areas of the other air vehicles, the first arbitration unit of each air vehicle causes the first communication unit to transmit its own vote with the predetermined weighting for the specific spatial cell, and causes the first communication unit to receive the votes with the predetermined weighting for the specific spatial cell from one or more of the other air vehicles; The first arbitration unit of each flying object executes the arbitration to determine which one of the flying objects is assigned to the particular spatial cell. A distributed system according to any one of claims 1 to 9.

11. The first arbitration unit of each flying object determines a size of the arbitration area of ​​the flying object using at least one of the flight route of the flying object, the direction of travel, the distance to the specific spatial cell, status information, priority, the occupancy status of the specific spatial cell, or the allocation status of the specific spatial cell. The distributed system of claim 10.

12. when the first communication unit of the air vehicle transmits the most heavily weighted vote among the weighted votes of the plurality of air vehicles, the first arbitration unit of the air vehicle performs arbitration to determine which one air vehicle is assigned to the particular spatial cell. A distributed system according to any preceding claim.

13. The distributed system further comprising a control server, Each of the plurality of flying objects is a request generating unit that determines a flight route of the aircraft and generates a first request for permission to move to a spatial cell in the space on the flight route; a transmission unit that transmits the first request generated by the request generation unit to the control server; A flight control unit that moves the aircraft to the spatial cell when the spatial cell is not reserved by another flying object and permission information permitting movement to the spatial cell is received from the control server, and does not move the aircraft to the spatial cell when the spatial cell is already reserved by another flying object and permission information prohibiting movement to the spatial cell is received from the control server, The control server includes: a receiver for receiving the first request from one of the plurality of air vehicles for permission to move into the spatial cell; a determination unit that, when the receiving unit receives the first request, determines whether the spatial cell has already been reserved by another flying object among the plurality of flying objects based on a reservation state of the spatial cell; a permission unit that permits the movement of the one aircraft to the spatial cell when the determination unit determines that the spatial cell is not reserved for another aircraft, and does not permit the movement of the one aircraft to the spatial cell when the determination unit determines that the spatial cell is already reserved for another aircraft, Each of the plurality of flying objects is configured such that, when the spatial cell is within a predetermined area, the request generation unit, the transmission unit, and the flight control unit execute their respective processes, and, when the spatial cell is outside the predetermined area, the first communication unit and the first arbitration unit execute their respective processes; the control server is configured such that, when the spatial cell is within the predetermined area, the receiving unit, the determining unit, and the permitting unit execute their respective processes, and, when the spatial cell is outside the predetermined area, the receiving unit, the determining unit, and the permitting unit do not execute their respective processes. A distributed system according to any preceding claim.

14. The control server further includes a memory for storing reservation states of a plurality of space cells into which the space is divided. The distributed system of claim 13.

15. The control server, A second communication unit that communicates with the plurality of aircraft using a peer-to-peer communication method; a second arbitration unit that causes the second communication unit to transmit its own vote, with a predetermined weighting, indicating permission or denial of a request for allocation to the specific spatial cell to the multiple air vehicles, and to receive votes, with a predetermined weighting each, indicating permission or denial of a request for allocation to the specific spatial cell from the multiple air vehicles, with respect to the specific spatial cell, the second arbitration unit of the control server performs arbitration to determine which one of the plurality of air vehicles is assigned to the particular spatial cell; When either the first communication unit of the air vehicle or the second communication unit of the control server transmits the most heavily weighted vote, either the first arbitration unit of the air vehicle or the second arbitration unit of the control server performs arbitration to determine which one of the plurality of air vehicles is assigned to the particular spatial cell. A distributed system according to claim 13 or 14.

16. A communication unit that forms a distributed system of multiple aircraft including the aircraft itself and one or more other aircraft by communicating with one or more other aircraft using a peer-to-peer communication method; an arbitration unit that causes the communication unit to transmit a vote of the other aircraft indicating whether a request for allocation to a specific spatial cell in space is allowed or denied, with a predetermined weighting, to one or more of the other air vehicles, and to receive votes from the one or more of the other air vehicles indicating whether a request for allocation to the specific spatial cell is allowed or denied, with a predetermined weighting, to the specific spatial cell; A flight control unit that moves the aircraft body; A memory for storing information on a plurality of space cells into which the space is divided, the arbitration unit performs arbitration to determine which one of the plurality of air vehicles is to be assigned the particular spatial cell based on the vote of the own aircraft with the predetermined weighting and votes from one or more of the other air vehicles, each of which is also assigned a predetermined weighting; When the result of the determination indicates that the specific spatial cell has not been assigned to the aircraft, the flight control unit changes the flight path of the aircraft so that another spatial cell adjacent to the specific spatial cell is assigned to the aircraft, and the specific spatial cell and the other spatial cell are included in the multiple spatial cells. Flying vehicle.

17. A communication unit that forms a distributed system of multiple aircraft including the aircraft itself and one or more other aircraft by communicating with one or more other aircraft using a peer-to-peer communication method; an arbitration unit that causes the communication unit to transmit a vote of the other aircraft indicating whether a request for allocation to a specific spatial cell in space is permitted or denied, with a predetermined weighting, to one or more of the other air vehicles, and receives votes from the one or more other air vehicles indicating whether a request for allocation to the specific spatial cell is permitted or denied, with a predetermined weighting, The arbitration unit causes the communication unit to transmit a vote of the aircraft to assign the specific space cell to another aircraft; the arbitration unit performs arbitration to determine which one of the plurality of aircraft will be assigned to the particular space cell based on the vote of the aircraft itself with the predetermined weighting and votes from one or more of the other aircraft, each of which is also assigned a predetermined weighting; Flying vehicle.

18. A method for storing information on a plurality of space cells into which a space is divided, forming a distributed system of a plurality of aircraft including the aircraft itself and the one or more other aircraft by communicating with the one or more other aircraft using a peer-to-peer communication method; transmitting a weighted vote of the vehicle to one or more of the other air vehicles, the weighted vote indicating whether or not the request for allocation to the particular space cell is approved, for a particular space cell in space; receiving votes from one or more of the other air vehicles with respect to the particular spatial cell, each vote having a predetermined weighting, indicating a grant or denial of a request for allocation to the particular spatial cell; performing arbitration to determine which one of the plurality of air vehicles will be assigned to the particular spatial cell based on the weighted vote of the own aircraft and the weighted votes of one or more of the other air vehicles; When the result of the determination indicates that the specific spatial cell has not been assigned to the air vehicle, modifying the flight path of the air vehicle so that another spatial cell adjacent to the specific spatial cell is assigned to the air vehicle, the specific spatial cell and the other spatial cell being included in the plurality of spatial cells. The manner in which the flying object performs.

19. A method for forming a distributed system of multiple flying objects including the flying object itself and one or more of the other flying objects by communicating with the one or more other flying objects using a peer-to-peer communication method; transmitting a weighted vote of the user's aircraft indicating whether or not to grant a request for allocation to a particular spatial cell in space to one or more of the other air vehicles, the vote of the user's aircraft being for allocating the particular spatial cell to the other air vehicles; receiving votes from one or more of the other air vehicles with respect to the particular spatial cell, each vote having a predetermined weighting, indicating a grant or denial of a request for allocation to the particular spatial cell; performing arbitration to determine which one of the plurality of air vehicles will be assigned to the particular spatial cell based on the weighted vote of the own aircraft and the weighted votes of one or more of the other air vehicles; The manner in which the flying object performs.

20. A method for storing information on a plurality of space cells into which a space is divided, forming a distributed system of a plurality of aircraft including the aircraft itself and the one or more other aircraft by communicating with the one or more other aircraft using a peer-to-peer communication method; transmitting a weighted vote of the vehicle to one or more of the other air vehicles, the weighted vote indicating whether or not the request for allocation to the particular space cell is approved, for a particular space cell in space; receiving votes from one or more of the other air vehicles with respect to the particular spatial cell, each vote having a predetermined weighting, indicating a grant or denial of a request for allocation to the particular spatial cell; performing arbitration to determine which one of the plurality of air vehicles will be assigned to the particular spatial cell based on the weighted vote of the own aircraft and the weighted votes of one or more of the other air vehicles; When the result of the determination indicates that the specific spatial cell has not been assigned to the air vehicle, modifying the flight path of the air vehicle so that another spatial cell adjacent to the specific spatial cell is assigned to the air vehicle, the specific spatial cell and the other spatial cell being included in the plurality of spatial cells. A program that causes a computer to carry out the method.

21. A method for forming a distributed system of multiple flying objects including the flying object itself and one or more of the other flying objects by communicating with the one or more other flying objects using a peer-to-peer communication method; transmitting a weighted vote of the user's aircraft indicating whether or not to grant a request for allocation to a particular spatial cell in space to one or more of the other air vehicles, the vote of the user's aircraft being for allocating the particular spatial cell to the other air vehicles; receiving votes from one or more of the other air vehicles with respect to the particular spatial cell, each vote having a predetermined weighting, indicating a grant or denial of a request for allocation to the particular spatial cell; performing arbitration to determine which one of the plurality of air vehicles will be assigned to the particular spatial cell based on the weighted vote of the own aircraft and the weighted votes of one or more of the other air vehicles; A program that causes a computer to carry out the method.