We consider the typical actions of users and the interfaces they need at various stages of organizing UAV flight.
2.1.2. User actions and their interfaces before flight
Prior to the flight of EP, it is necessary to complete preliminary training, consisting of the following tasks:
-
study the area of planned work: analyze information about the terrain, check the presence of power lines, view up-to-date information on restrictions and prohibited areas of flight;
-
choose a platform for take-off and landing, taking into account the possibility of access to them;
-
get acquainted with the preliminary weather forecast for the day of flights;
-
perform calculation of aeronautical flight elements (safe flight altitude, calculation of distance, flight time, etc.);
-
make a flight plan;
-
coordinate the use of airspace with the zonal center;
-
prepare cartographic material for the flight.
Thus, EP requires the following interfaces to perform preconditioning:
1. Interface with display of:
-
terrain;
-
power lines in the flight area;
-
up-to-date information on flight restrictions and restricted areas and other AI;
-
maps of the area for the selection of take-off and landing sites, taking into ac-count the possibility of access to them.
2. Interface for getting acquainted with the actual and forecast information about the weather on the day of flights;
3. Interface for performing calculations of air navigation elements of the flight;
4. Interface for drawing up a flight plan;
5. Interface for interaction with the main center of the unified ATFM to coordinate the possibility of using the airspace.
Prior to the flight, the provider must:
-
prepare a daily plan of air traffic;
-
inform the airports of departure/arrival about changes in routes;
-
during the day, control the arrival of the airborne personnel to the flight area to perform pre-flight preparation, inform about the conditions for the flight;
-
perform other procedures in accordance with the rules of air navigation services for airspace users.
Thus, the provider needs the following interfaces to prepare the dispatcher for duty:
1. Interface for preparing daily air traffic plan;
2. Interface for interaction with other dispatchers;
3. Interface for interaction with EP:
-
to control the arrival of EP in the area of the flight;
-
to inform about flight conditions.
2.1.3. User actions and their interfaces during flight
During the flight of EP, we must:
1. Conduct pre-flight preparation:
-
check the compliance of the weather in the flight area with the operational characteristics of UAV;
-
compose a flight task and upload it to the ground control station;
-
deploy a ground control station and prepare the take-off site;
-
check the technical condition of UAV;
-
obtain permission to use the airspace in the zonal center of air traffic management two hours before departure;
2. Keep in touch with the dispatcher of the zonal center.
3. Monitor the air situation during the flight.
4. Inspect the area according to the images of UAV FPV camera.
5. Monitor UAV and flight parameters.
Thus, EP needs the following interfaces:
1. Interface described above with the display of the terrain, power lines, air navigation flight zones and terrain maps.
2. Interface described above to see the actual weather information.
3. Interface described above for compiling a flight plan:
- for loading into the ground control station.
4. Interface described above for interaction with the main center of the unified air traffic management system for:
- obtaining permission to use the airspace;
- exchange of information about the air situation during the flight.
5. Interface for monitoring UAV and flight parameters.
During the flight, the provider must:
1. Ensure the release and reception of UAV.
2. When UAV is taking off, assess the air situation, paying special attention to the location of departing, flying and landing aircraft and meteorological situation and make sure that there are no obstacles on the runway.
3. During the flight, assess the air situation, report the accumulation and flights of birds, as well as dangerous weather events.
4. Control the flight of UAV, in case of deviations from the flight route, inform EP.
5. When landing UAV, ensure that there are no other air and mobile technical means in the landing area.
6. Other procedures in accordance with the rules of air navigation services for airspace users.
Thus, the provider needs the following interfaces to serve the airspace:
1. Interface to ensure the release and reception of UAV for:
- clarification of the technical condition of the aerodrome of departure and destination;
- assessment of the air situation for the presence of restrictions or a ban on the flight of UAV, for the presence of other air assets, as well as mobile technical equipment, for the presence of obstacles on the airstrip;
- assessment of meteorological and ornithological conditions.
2. Interface for assessing the air situation during the flight:
- for the presence of accumulation and flights of birds;
- for the presence of dangerous weather phenomena;
3. Interface for controlling the flight of UAV (for example, in case of deviations from the flight route, inform EP).
2.1.4. User actions and their interfaces after the flight
After the flight of EP, we must:
- inform the dispatcher about a successful landing;
- conduct a post-flight inspection of UAV.
In accordance with this EP, after the flight, the above-described interface for interacting with an air traffic controller in order to inform the controller of a successful landing.
After the flight, the provider must:
- receive a report on the completion of the flight;
- record the landing time and UAV callsign in the log.
The provider needs the following interfaces:
- the above-described interface for communicating with EP to receive a message about the end of the flight.
2. Interface for keeping a log of UAV flights.
External users of RUTM system can analyze flight data and upload analytical reports on specific UAV flights. External users can be, for example, insurance companies in the investigation of aviation accidents. They require a separate interface to access flight data with the ability to upload analytical reports on flight accidents.
2.2. AI database functionality and dimension requirements
As follows from the above description of the main services of RUTM system users, their organization requires the full amount of AI necessary to build and control UAV route. To accumulate, store, process and provide all users with up-to-date information, AI database is required, which should provide:
- generation and display of two-dimensional and three-dimensional images based AI;
- managing the display parameters of the territory model on the graphical client;
- display control using devices for user interaction with the system;
- receiving, processing and displaying incoming data from external systems.
An important aspect of AI database is its size, by which we mean the area of the territory described by its contents with a given accuracy. The minimum size of AI database should cover RUTM service area plus 25-40 km as a buffer zone.
The maximum size of the database should provide for modeling a large state or region. For the case when the simulated territory is expressed by the surface of the entire planet, the amount of information of all types, even in average quality, will be very significant. Large amounts of information necessitate the use of:
- effective data projections, which are discussed in sections 3.2 and 4.2;
- organization of non-trivial structures of information storage;
- effective methods of data compression and special file formats, for example, ARINC, WXXM, GeoTIFF, etc. [15,16].