Drone air traffic control and flight plan management

Patent metadata

Field	Value
Publication number	US-9852642-B2
Application number	US-201615064536-A
Country	US
Kind code	B2
Filing date	Mar 8, 2016
Priority date	Mar 8, 2016
Publication date	Dec 26, 2017
Grant date	Dec 26, 2017

Abstract

One embodiment provides a method comprising receiving a flight plan request for a drone. The flight plan request comprises a drone identity, departure information, and arrival information. The method further comprises constructing a modified flight plan for the drone based on the flight plan request, wherein the modified flight plan represents an approved, congestion reducing, and executable flight plan for the drone, and the modified flight plan comprises a sequence of four-dimensional (4D) cells representing a planned flight path for the drone. For each 4D cell of the modified flight plan, the method further comprises attempting to place an exclusive lock on behalf of the drone on the 4D cell, and in response to a failure to place the exclusive lock on behalf of the drone on the 4D cell, rerouting the modified flight plan around the 4D cell to a random neighboring 4D cell.

First claim

What is claimed is:

1. A method, comprising:
receiving a flight plan request for a drone, wherein the flight plan request comprises an identity of the drone, departure information for the drone, and arrival information for the drone, and the arrival information comprises one or more locations that the drone is programmed to perform one or more tasks at;
constructing a flight plan for the drone based on the flight plan request, wherein the flight plan represents an executable flight plan for the drone that reduces air traffic congestion, and the flight plan comprises a sequence of four-dimensional (4D) cells representing a planned flight path for the drone; and
for each 4D cell of the flight plan:
determining whether an exclusive lock on behalf of the drone on the 4D cell is available;
in response to determining an exclusive lock on behalf of the drone on the 4D cell is available, placing the exclusive lock on behalf of the drone on the 4D cell, thereby restricting use of air space within the 4D cell to the drone only; and
in response to determining an exclusive lock on behalf of the drone on the 4D cell is not available, rerouting the flight plan around the 4D cell to a neighboring 4D cell, wherein the rerouting includes delaying take off of the drone;

wherein flight of the drone to the one or more locations is controlled in accordance with the flight plan; and
wherein, in response to receiving a report identifying a current location of the drone and determining the current location of the drone is inconsistent with the flight plan, rerouting the flight plan from the current location.

2. The method of claim 1 , wherein:
for each 4D cell of the flight plan:
a neighboring 4D cell is to the left of, right of, above, below, or later in time than the 4D cell, from the point of view of the flight plan towards the 4D cell.

3. The method of claim 1 , wherein each 4D cell represents 4D locations represented by two horizontal intervals, one vertical interval and one time interval.

4. The method of claim 1 , wherein each 4D cell in the flight plan is within a distance of a point on the planned flight path.

5. The method of claim 1 , further comprising:
partitioning available air-space below an altitude into multiple 4D cells; and
organizing the multiple 4D cells into rectilinear two-dimensional (2D) zones.

6. The method of claim 5 , further comprising:
maintaining a pre-determined rate of lock conflict for each zone by repartitioning the zone into more or fewer 4D cells independent of other zones and subject to minimum dimensions for 4D cells.

7. The method of claim 1 , further comprising:
receiving a 4D position report identifying the current location of the drone;
determining whether the current location of the drone is consistent with the flight plan; and
in response to determining the current location of the drone is inconsistent with the flight plan, rerouting the flight plan from a current 4D cell that the drone is in.

8. The method of claim 1 , further comprising:
receiving an input indicating a detected failure of the drone;
overriding an exclusive lock on a 4D cell where the detected failure is located; and
for at least one other flight plan for at least one other drone affected by the override, rerouting the at least one other flight plan from a current 4D cell that the at least one other drone is in.

9. A system comprising a computer processor, a computer-readable hardware storage medium, and program code embodied with the computer-readable hardware storage medium for execution by the computer processor to implement a method comprising:
receiving a flight plan request for a drone, wherein the flight plan request comprises an identity of the drone, departure information for the drone, and arrival information for the drone, and the arrival information comprises one or more locations that the drone is programmed to perform one or more tasks at;
constructing a flight plan for the drone based on the flight plan request, wherein the flight plan represents an executable flight plan for the drone that reduces air traffic congestion, and the flight plan comprises a sequence of four-dimensional (4D) cells representing a planned flight path for the drone; and
for each 4D cell of the flight plan:
determining whether an exclusive lock on behalf of the drone on the 4D cell is available;
in response to determining an exclusive lock on behalf of the drone on the 4D cell is available, placing the exclusive lock on behalf of the drone on the 4D cell, thereby restricting use of air space within the 4D cell to the drone only; and
in response to determining an exclusive lock on behalf of the drone on the 4D cell is not available, rerouting the flight plan around the 4D cell to a neighboring 4D cell, wherein the rerouting includes delaying take off of the drone;

wherein flight of the drone to the one or more locations is controlled in accordance with the flight plan; and
wherein, in response to receiving a report identifying a current location of the drone and determining the current location of the drone is inconsistent with the flight plan, rerouting the flight plan from the current location.

10. The system of claim 9 , wherein:
for each 4D cell of the flight plan:
a neighboring 4D cell is to the left of, right of, above, below, or later in time than the 4D cell, from the point of view of the flight plan towards the 4D cell.

11. The system of claim 9 , wherein each 4D cell represents 4D locations represented by two horizontal intervals, one vertical interval and one time interval.

12. The system of claim 9 , wherein each 4D cell in the flight plan is within a distance of a point on the planned flight path.

13. The system of claim 9 , further comprising:
partitioning available air-space below an altitude into multiple 4D cells; and
organizing the multiple 4D cells into rectilinear two-dimensional (2D) zones.

14. The system of claim 13 , further comprising:
maintaining a pre-determined rate of lock conflict for each zone by repartitioning the zone into more or fewer 4D cells independent of other zones and subject to minimum dimensions for 4D cells.

15. The system of claim 9 , further comprising:
receiving a 4D position report identifying the current location of the drone;
determining whether the current location of the drone is consistent with the flight plan; and
in response to determining the current location of the drone is inconsistent with the flight plan, rerouting the flight plan from a current 4D cell that the drone is in.

16. The system of claim 9 , further comprising:
receiving an input indicating a detected failure of the drone;
overriding an exclusive lock on a 4D cell where the detected failure is located; and
for at least one other flight plan for at least one other drone affected by the override, rerouting the at least one other flight plan from a current 4D cell that the at least one other drone is in.

17. A computer program product comprising a computer-readable hardware storage device having program code embodied therewith, the program code being executable by a computer to implement a method comprising:
receiving a flight plan request for a drone, wherein the flight plan request comprises an identity of the drone, departure information for the drone, and arrival information for the drone, and the arrival information comprises one or more locations that the drone is programmed to perform one or more tasks at;
constructing a flight plan for the drone based on the flight plan request, wherein the flight plan represents

Assignees

• IBM

Inventors

• Butler Eric K
• Chandra Anca A
• Chowdhary Pawan R
• Glissmann-Hochstein Susanne M
• Griffin Thomas D
• Jadav Divyesh
• Lee Sunhwan
• Strong Jr Hovey R

Classifications

• G08G5/0039 Primary

  Physics · mapped topic

• G08G5/0069

  Physics · mapped topic

• G08G5/727

  from a ground station · CPC title

• G08G5/76

  for monitoring atmospheric conditions · CPC title

• G08G5/57

  for unmanned aircraft · CPC title