Dynamic activation and de-activation of airspace for improved flight planning operations
In some aspects, the techniques described herein relate to a method including: receiving, at a processor, a blocked airspace request from a utilizing organization (UO), the blocked airspace request identifying airspace; filtering, by the processor, the blocked airspace request using a cross-domain guard; transmitting, by the processor, the filtered blocked airspace request to a data sharing platform for authorization; storing, by the processor, the blocked airspace request in a database; receiving, by the processor, a network message from a flight planning system, the network message including at least one flight path; and providing, by the processor, a status of the blocked airspace in response to the network message.
1. A method comprising:
receiving, at a processor, a blocked airspace request from a utilizing organization (UO), the blocked airspace request identifying airspace;
applying, by the processor, a cross-domain guard comprising one or more filters to the blocked airspace request to remove classified information from the blocked airspace request;
transmitting, by the processor, the filtered blocked airspace request to a data sharing platform for authorization;
storing, by the processor, the blocked airspace request in a database;
receiving, by the processor, a network message from a flight planning system, the network message including at least one flight path;
querying, by the processor, the database using an identifier of the blocked airspace to determine a status of the blocked airspace in response to the network message;
transmitting, by the processor, the determined status to the flight planning system; and
adjusting the flight path based on the determined status.
2. The method of claim 1 , wherein storing the blocked airspace request in a database comprises hashing a response received from the data sharing platform and storing the hash.
3. The method of claim 1 , wherein before querying the database, the method further comprises:
determining that the blocked airspace is located in the at least one flight path.
4. The method of claim 1 , further comprising:
determining, after querying the database, that the blocked airspace request has been deactivated; and
transmitting a notification to the flight planning system indicating the blocked airspace is available.
5. The method of claim 1 , further comprising:
determining, after querying the database, that the blocked airspace included in the blocked airspace request is not available;
transmitting a message to the UO, the message identifying the blocked airspace request;
receiving a response from the UO to the message, the response including an updated status of the blocked airspace request; and
updating the blocked airspace request stored in the database based on the response.
6. The method of claim 5 , wherein the updated status comprises one of a deactivation or release of the blocked airspace.
7. The method of claim 1 , wherein the blocked airspace comprises a special use airspace (SUA).
8. A non-transitory computer-readable storage medium for tangibly storing computer program instructions capable of being executed by a computer processor, the computer program instructions defining steps of:
receiving a blocked airspace request from a utilizing organization (UO), the blocked airspace request identifying airspace;
applying, by the processor, a cross-domain guard comprising one or more filters to the blocked airspace request to remove classified information from the blocked airspace request;
transmitting the filtered blocked airspace request to a data sharing platform for authorization;
storing the blocked airspace request in a database;
receiving a network message from a flight planning system, the network message including at least one flight path;
querying, by the processor, the database using an identifier of the blocked airspace to determine a status of the blocked airspace in response to the network message;
transmitting, by the processor, the determined status to the flight planning system; and
adjusting the flight path based on the determined status.
9. The non-transitory computer-readable storage medium of claim 8 , wherein storing the blocked airspace request in a database comprises hashing a response received from the data sharing platform and storing the hash.
10. The non-transitory computer-readable storage medium of claim 8 , wherein before querying the database, the steps further comprise:
determining that the blocked airspace is located in the at least one flight path.
11. The non-transitory computer-readable storage medium of claim 8 , the steps further comprising:
determining, after querying the database, that the blocked airspace request has been deactivated; and
transmitting a notification to the flight planning system indicating the blocked airspace is available.
12. The non-transitory computer-readable storage medium of claim 8 , the steps further comprising:
determining, after querying the database, that the blocked airspace included in the blocked airspace request is not available;
transmitting a message to the UO, the message identifying the blocked airspace request;
receiving a response from the UO to the message, the response including an updated status of the blocked airspace request; and
updating the blocked airspace request stored in the database based on the response.
13. The non-transitory computer-readable storage medium of claim 12 , wherein the updated status comprises one of a deactivation or release of the blocked airspace.
14. The non-transitory computer-readable storage medium of claim 8 , wherein the blocked airspace comprises a special use airspace (SUA).
15. A device comprising:
a processor configured to:
receive a blocked airspace request from a utilizing organization (UO), the blocked airspace request identifying airspace;
apply a cross-domain guard comprising one or more filters to the blocked airspace request to remove classified information from the blocked airspace request;
transmit the filtered blocked airspace request to a data sharing platform for authorization;
store the blocked airspace request in a database;
receive a network message from a flight planning system, the network message including at least one flight path;
query the database using an identifier of the blocked airspace to determine a status of the blocked airspace in response to the network message;
transmit the determined status to the flight planning system; and
adjust the flight path based on the determined status.
16. The device of claim 15 , wherein storing the blocked airspace request in a database comprises hashing a response received from the data sharing platform and storing the hash.
17. The device of claim 15 , wherein before querying the database, the device is further configured to:
determine that the blocked airspace is located in the at least one flight path.
18. The device of claim 15 , the processor further configured to:
determine, after querying the database, that the blocked airspace request has been deactivated; and
transmit a notification to the flight planning system indicating the blocked airspace is available.
19. The device of claim 15 , the processor further configured to:
determine, after querying the database, that the blocked airspace included in the blocked airspace request is not available;
transmit a message to the UO, the message identifying the blocked airspace request;
receive a response from the UO to the message, the response including an updated status of the blocked airspace request; and
update the blocked airspace request stored in the database based on the response.
20. The device of claim 15 , wherein the blocked airspace comprises a special use airspace (SUA).