The analysis of various data is a challenging issue in the field of air traffic flow management (ATFM). Managing a large volume of data and their correct interpretation plays a key role in the prevention of air accidents, human errors, and flight interactions. In general, pilots and flight navigators deal with massive information, including flight safety messages, meteorological messages, aviation NOTAMs, aviation company information messages, and airplane system alerts. Air collisions are possible due to the high volume and variety of such information considering the human errors in their interpretation and application. Therefore, attempts should be made to develop systematic information and establish logical communication between large data volumes in order to increase the reliability factor in flights. Recently, the semantic web has been recognized as a novel foundation of knowledge management that relies on ontology (concept modeling language) and effective techniques for the modeling of integrated information systems and eliminating barriers to the interpretation and exchange of data. The present study aimed to propose an efficient infrastructure for ATMs by defining the concepts, rules, and relationships between the concepts related to the scope of flight information. To this end, we designed and implemented the ontology of flight safety messages, which included an important part of flight operation information. In this research, the IPS-based aviation networks and methontology methodology were exploited for the engineering of the ontology of flight messages. In addition, the implementation process was carried out using the Protégé software. The analysis of the system was performed using the actual data of Mashhad Airport, Iran. The obtained data were based on the inbound and outbound flights of the airport, which were collected using the radar system and FDS and normalized. Finally, the implementation of the ontology of flight messages was demonstrated after a case study of several flight examples. The developed ontology could be incorporated into the foundation of an ATN aviation network as an application.
Research
Ontology Generation for Flight Safety Messages in Air Traffic Management(ATM)
https://doi.org/10.21203/rs.3.rs-139993/v1
This work is licensed under a CC BY 4.0 License
You are reading this latest preprint version
Ontology
Semantic Web
Air Traffic Flow
IPS-based Aviation Networks
Ontology
Protégé
Today, the growth of human communities and the increasing need for travel have led to more transfer of products. Among various travel methods, air travel is of particular interest in terms of quality, speed, security, and comfort. Increased flights and air travel require an efficient air traffic flow management (ATFM) system. The diversity of information and its analysis are important challenges in ATFM. In general, most pilots and air traffic controllers deal massive information, including flight safety messages (e.g., flight plan, airplane departure, arrival messages, flight delays, changes in the flight plan, flight cancelation, and airplane return), meteorological messages, aviation NOTAMs, snow, volcanic phenomenon NOTAMs, ATM messages, airline information messages, and aircraft systems warnings. An important issue regarding ATFM is the arrangement of the flight traffic sequence for preventing the interference and delay of flights. The analysis of this information is extremely difficult and mostly associated with human error. Any mistakes in the interpretation and analysis of aviation data and information (especially aviation messages) may lead to air accidents and cause irreparable financial and human damages.
The semantic web has presented the solution of giving meaning to data by means of knowledge graphs (ontology), with the aim of taking a step from a data-based system toward an information-based system on web data, which affects all the infrastructures of knowledge-based systems. In this context, the ontological approach to the words and concepts in a field of knowledge and their correlations is the infrastructure for the formation of the knowledge graphs (ontology) in that field. In fact, the main goal of ontology for flight safety messages in aviation is that the compatibility between systems and intelligent agents conveys the meaning of information, so that the ability to access information is optimal and enables the processing of the information by the machine correctively.
Ontology defines a joint word for the pilots, flight staff, flight dispatchers, and air traffic controllers who need to share information in a specific field and domain. This glossary includes the definitions of basic concepts (understandable by machine), formation of flight safety messages, as well as their interpretation and communication. This ontology is defined in the official and processable language of the machine for the purpose of semantic commonalities in automated systems, and the implementation of the process is carried out by a special graphic language.
The present study aimed to design the ontology for flight safety messages, which encompassed an important part of flight operation information. The ontology could be directly used by pilots, flight staff, flight dispatchers, air traffic controllers, aviation information networks, and systems based on web and TCP-IP (e.g., ATN). The implementation of the process was carried out using the Protégé software and methodology. The use of the ontology through IPS-based aviation networks enables the interpretation of aviation messages by the systems and machines that are classified as flight operations to improve the concepts of safety and reliability in air traffic control.
In (1), the researchers divided ontology into four categories of upper ontology, domain ontology, interface ontology, and process ontology. Domain ontology refers to the modeling of a specific domain of knowledge through a specific semantic representation and display of concepts based on their application. Upper ontology is a model of common objects, which are generally applied in a domain of the related fields. Interface ontology describes the concepts of two fields, whereas process ontology explains the inputs, outputs, constraints, and sequences of the information involved in businesses or engineering processes (1). Some researchers believe that domain ontology is the most important category that has been defined in a specific domain as it provides the words in the field of domain concepts and the desired field, as well as their communication, activities occurring in the field, and the primary theories of the domain (2).
Ontologies are used with various objectives, including the place where people, computers or both require the conceptualization of a domain. According to Noy et al. (3), one of the goals of domains is the implementation of a phrase by sharing the joint concept in the information structure between individuals or smart agents. In addition, Reese et al. (4) used ontologies to build simulation and training scenarios.
The open travel alliance (OTA) messaging system is among popular and widely used ontologies. In (5), the researchers aimed to use OTA messages and generate a new ontology for air travels as well. In (6), the researchers attempted to manage air traffic by information sharing, which was carried out by various ontologies. For instance, information of ontology was used for indexing and searching, while a different ontology was applied to prevent accidents and traffic alerts, and another case was exploited to run a system. As a result, satisfaction with airlines increased, which in turn led to the higher NAS efficiency. The following ontologies are common for space and aeronautical applications.
-
Critical ontology has been developed for the indexing and searching of meteorological documents. One of the uses of the critical ontology relates to the concepts of specific weather conditions and the relevant scenarios for air traffic alert and collision avoidance systems (7).
-
AIAA is a semantic database used to generate concepts and vocabulary communication in the field of aviation (8).
-
XCALIBR is the ontology that is used for designing spacecraft and supporting spacecraft designers in determining the dependence of components on other elements (9).
-
MillInfo ontology describes military aviation information as the basis for the semantic architectural models of air force systems (10).
-
TSONT ontology is applied to simulate air force in war. The main goal of general research is re-construction for use in the development of various air route simulations and clash of fighter aircrafts (11).
The evaluation of previous studies and ontologies in the aviation area (12) showed that most of the studies in this regard have been focused on the construction of aircrafts or spacecraft, as well as military aviation activities. On the other hand, the studies in the non-military aviation domain have often been focused on ATM, the implementation of aviation NOTAMs, and aviation meteorology based on the format of the International Civil Aviation Organization (ICAO). In the present study, we chose the domain of flight safety messages, which is frequently used during flight operations, and no specific ontology has been carried out in this regard; this may be considered the novelty of our research. In addition, this domain is a joint field between the ICAO as the executor of aviation governance and the International Air Transport Association (IATA) as the representative of aviation companies (13–15).
Ontology is a clear and formal description of the concepts within a domain. The features of each concept and special attribute and various properties of the concept are known as properties. Furthermore, classes are taken into account by the majority of ontologies to define the domain concepts. A class could encompass several subclasses, which describe the more specific concepts of the parent class. The following issues should be considered for the initial definition of ontology:
A) It should be made clear which questions are to be addressed by the ontology. For instance, this article is supposed to address questions such as:
-
What kind of aviation messages are exchanged in the ontology?
-
In which airports and systems could they be implemented?
-
Is it possible to enter information into the radar and aircraft autopilot system through the ontology?
-
Could it be developed and integrated with other systems?
B) The users of the ontology should be determined; the ontology could be used by the flight crew, air traffic controllers, airlines, and travel and pilgrimage agencies.
C) The project scope should also be determined in the design and implementation of the ontology. In the present study, the domain considered for the ontology partly included safety messages, such as the flight design, airplane departure, arrival messages, flight delay, changes in the flight plan, flight cancelation, and flight return. These messages were in the range of the required information and data for air traffic control, pilots, flight crew and flight dispatcher. In addition, the aviation messages for the flight operations included meteorological messages, aviation NOTAMs, aviation maps, air information services, ATM messages, aviation company information messages, and aircraft systems alerts (Fig. 1).
D) The general goals of ontology design should be clarified. In the present study, we had primary and secondary categories of objectives. The primary goals were evaluating the possibility of implementing a flight safety messaging system based on the ontology and automation of the ATMs. The secondary goals were adding the ability of self-navigation to the flight navigation systems, simplifying the tasks of the flight crew (captain) and ATM, and the possibility of integrating aviation information into other data, such as meteorological and maintenance information.
E) The uses of ontology should be determined. In the present study, the applications of the ontology were as follows:
1) Given the significantly large volume of the required data for flight operations, a method should be established to present data to aviation machines and systems in a plausible manner.
2) The public understanding of the structure of the aviation information should be shared among humans or machine factors.
3) The aviation domain knowledge and flight safety messages should be reusable.
4) The domain knowledge should be separated from the operational knowledge.
4) The domain knowledge should be analyzed.
For instance, an FPL includes detailed information about a flight. If the FPL is expressed based on the ontology, it will be able to form a target on the radar automatically. Similarly, the radar inside the airplane exchanges information between the radar target and its own systems with the same ontology. Notably, this version should be debugged and evaluated after defining the primary ontology version, which is possible through specialized discussions with the experts in the field for which the ontology has been prepared. Nonetheless, the revision process should be carried out in the primary ontology in any way possible, and the iterative process continues through all the stages of the ontology lifecycle.
A specialized methodology could be exploited to generate and evaluate ontology. There are standard ontology generation methodologies, and various methodologies could be used depending on the application of the ontology. Some of the most important ontology generation methodologies include:
-
Methontology methodology
-
Ontology development
-
On-To-Knowledge methodology (OTKM)
-
NeOn methodology
Methontology methodology was developed in the Artificial Intelligence Lab of the Technical University of Madrid (UPM). The methontology framework enables the construction of ontologies at the knowledge level and encompasses the identification of the ontology development process, as well as a lifecycle based on evolving prototypes and specific techniques for the description of the processes.
Ontology development was developed based on software management principles in order to achieve high-quality ontology at low maintenance costs. In this methodology, the instructions are presented for the conceptualization and design stages in algorithm forms.
OTKM was designed based on the European project of EU-IST (No. 10132), which created an ontology-based tool environment to accelerate knowledge management. This methodology was generated with a large number of heterogeneous, distributed, and semi-structured documents, which mostly exist in large corporate intranets and the global internet platform. The results of this project are:
-
A set of tools for processing semantic information and user access;
-
OIL, which is a web-based core inference layer;
-
Formation of a conventional methodology;
-
Validation through industrial case studies
NeOn methodology is used to create the ontology networks that are adapted from the scenario-based method and supports the aspects of development collaboration and ontology reuse, as well as the dynamic evolution of the ontology networks in distribution environments. The methodology encompasses a set of nine scenarios for the generation of ontologies and ontology networks, which emphasizes the reuse of ontology and non-ontology resources, re-engineering and integration, cooperation, and dynamism in the ontology construction process. The NeOn glossary comprises of processes and activities, the identification and definition of which occur when the ontology networks are formed jointly by the construction team. The methodology instructions for various processes and activities of the ontology network development procedure include the reuse of the ontology and non-core resources, deploying the characteristics of the ontological requirements, ontology localization, and process planning. In the current research, the processes and activities were carried out through the three stages of filling out a card, workflow, and sampling.
In the current research, we applied the methontology methodology considering the numerous advantages for the preparation of ontologies in specialized application domains. Furthermore, the methodology exploits a thesaurus of an organized source of knowledge provided by the experts in the field. The semantic relations (general/specific) in the thesaurus allowed us to create the hierarchical structure required for the ontology. Notably, we applied the methontology methodology with 11 stages as depicted in Fig. 2.
A few basic laws also helped with the decision-making stages of the ontology generation process, as follows:
-
There is no one-size-fits-all way to model a domain, but rather various executive options, and the optimal solution in modeling a domain depends on two parameters, which are the application that the designer has in mind and the developments that are envisaged for the model.
-
Ontology development is necessarily an iterative process.
-
The concepts of ontology are limited to the names of objects (physical/logical) and their relations within the domain. These concepts are very similar to the names (objects) and verbs (relations between objects) that may be found in the sentences describing the scope of the problem.
-
Regarding the selection of various solutions, we should consider a more efficient solution that is more logical, has a higher capacity for development, and is maintained easier. In addition, ontology is a model of world realities, and ontological concepts should reflect these realities.
Based on the scope of the definition in Section 3, the methontology methodology was selected for the implementation and evaluation of the ontology of flight safety messages. In addition, the IPS-based aviation network standard and the methontology methodology were applied for the engineering of the ontology of flight messages. The Protégé software was also used to implement the ontology. The system was tested based on the actual data of Mashhad Airport, which were obtained from the outbound and inbound flights of the airport, collected through the radar system and FDS, and finally normalized. By conducting a case study on several flight data samples, we demonstrated the implementation of the flight message ontology, the development of which as an application based on the ATN aviation network could lead to its exploitation. In the present study, the ontology engineering was based on a top-down approach to ontology construction (methodology), the main stages of which included:
- Building a glossary of terms;
- Unification of the concepts;
- Building a concept classification;
- Diagram of the binary relations between the concepts
In practice, ontology development encompasses the following steps:
- Defining the classes in the ontology
- Arrangement of the classes in a hierarchy of 'parent-child classes'
- Defining the features and describing the values that are allowed to be possessed by the features;
- Determining the values of the features for the class samples
5.1. Flight Information Messages
According to the ICAO documents, the flight information messages included:
- Messages containing aviation traffic information;
- Messages containing meteorological data;
- Messages containing the performance status of the aviation equipment;
- Messages containing information on the flight safety messages;
- Messages containing the airline messages
5.2 Types of Flight Safety Messages
Safety messages include the flight plan, departure and arrival messages, flight delays, changes in the flight plan, cancelations, and flight return.
Table 1. Various Types of Flight Safety Messages
|
Message type designator |
Message type |
Message category |
|
ALR RCF |
Alerting Radio communication failure |
Emergency |
|
FPL CHG CNL DLA DEP ARR |
Filed flight plan Modification Cancellation Delay Departure Arrival |
Filed flight plan and associated update |
|
CPL EST CDN ACP LAM |
Current flight plan Estimate Coordination Acceptance Logical acknowledgement |
Coordination |
|
RQP RQS SPL |
Request flight plan Request supplementary flight plan Supplementary flight plan |
Supplementary |
5.2.1 Flight Plan Message
A flight plan includes the details of flight operations. The plan should be presented to the flight plan acceptance unit within a minimum of one hour and maximum of 24 hours before the flight. The flight should occur up to one hour after the time announced in the flight plan. Otherwise, the flight plan would be canceled and should be presented again. Figure 4 depicts a flight plan filled as a hypothetical flight.
5.2.2 Departure Message
A departure message announces the departure time of the flight from the airport of origin to the destination airport.
5.2.3 Arrival Message
An arrival message announces the arrival time of the airplane at the airport.
5.2.4 Delay Message
The pilot or their representative is allowed to announce a delay of up to 15 minutes after the flight time is specified in the flight plan.
5.2.5 Change Message
The pilot or their representative is allowed to announce a change in the type of the airplane up to 15 minutes after the time has been specified in the flight plan. The goal of this message is to inform the relevant units about the change that is to be expected in the primary flight plan.
5.2.6 Cancelation Message
The purpose of a cancelation message is to inform the relevant units about the cancellation of the flight.
5.2 Glossary of Terms
The glossary of terms was formed based on the terms existing in the thesaurus. In the current research, these terms were extracted and selected by the subject matter experts from various sources in each field.
Table 2. Example of Glossary of Terms and Concepts
|
type |
Description |
Acronyms |
synonyms |
name |
|
concept |
A telecommunication service between specified fixed points provided primarily for the safety of air navigation and for the regular, efficient and economical operation of air services (ICAO Doc 4444). |
AFS |
- |
Aeronautical Fixed Service |
|
concept |
A gateway via the internet into the Aeronautical Fixed Telecommunications Network (AFTN) and allows pilots or small airfields access to file their own flight plans and other flight related messages (UK AIP). |
AFPEx |
- |
Assisted Flight Plan Exchange Service |
|
concept |
A publication issued by or with the authority of a State and containing aeronautical information of a lasting character essential to air navigation (ICAO Doc 4444). |
AIP |
- |
The Aeronautical Information Publication |
|
concept |
An aircraft system based on secondary surveillance radar (SSR) transponder signals which operates independently of ground-based equipment to provide advice to the pilot on potential conflicting aircraft that are equipped with SSR transponders (ICAO Doc 4444). |
ACAS |
- |
Airborne Collision Avoidance System |
|
concept |
A service established with the objective of contributing to a safe, orderly and expeditious flow of air traffic by ensuring that ATC capacity is utilized to the maximum extent possible, and that the traffic volume is compatible with the capacities declared by the appropriate ATS authority(UK AIP). |
ATFM |
- |
Air Traffic Flow Management |
|
concept |
The flight plan, including changes, if any, brought about by subsequent clearances (ICAO Annex 2 / ICAO Doc 4444). |
CPL |
- |
Current flight plan |
|
concept |
The estimated time required to proceed from one significant point to another (ICAO Doc 4444). |
EET |
- |
Estimated Elapsed Time |
|
concept |
A world-wide system of aeronautical fixed circuits provided, as part of the aeronautical fixed service, for the exchange of messages and/or digital data between aeronautical fixed stations having the same or compatible communications characteristics. |
AFTN |
- |
AERONAUTICAL FIXED TELECOMMUNICATION NETWORK |
|
Instance Attribute |
A time record when an aircraft take off from and airport |
- |
- |
Departure Time |
|
concept |
Maximum of passenger that load in an aircraft |
- |
- |
Aircraft passenger capacity |
|
Instance Attribute |
Name of airline in IATA book |
- |
- |
Company Name |
|
Instance Attribute |
Time for DLA register after file in fpl |
- |
- |
Delay Time |
|
concept |
The flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes |
FPL |
Flight plan |
|
|
concept |
The DLAY message as filed with an ATS unit by the pilot or a designated representative, for delay time of flight |
DLA |
DLAY |
|
|
concept |
A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft. |
AP |
AIRPORT |
|
|
Instance Attribute |
Aircraft category that fill in flight plan |
Type of Flights |
||
|
Relation |
Flight arrival in airport that is fill in flight plan as arrival airport |
Is Arrival airport of |
||
|
Relation |
Flight departure from airport that is fill in flight plan as departure airport |
Is Departure airport of |
||
|
Relation |
A flight plan is filled for a flight |
Fill flight plan |
||
|
Relation |
A flight plan is cancel of a flight |
Cancel flight plan |
5.4 Classification of Concepts with a Taxonomic Structure
The classification of the concepts was based on the conceptual system in thesauruses. In the present study, each reference term was intended as a concept or class, and the relationships (general/specific) were converted into relationships (subclass/class) using taxonomy or the graph theory in the four sections of subclass, disjoint, exhaustive, and partition.
5.5 Diagrams of Single-function Binary Connection Diagrams
Taxonomic diagrams were formed in the previous step to classify the concepts. Afterwards, the established diagrams were evaluated and determined as a goal in the stages of the conceptualization of forming the single-function binary connection diagrams.
5.6 Table of Dictionary of Concepts, Examples, Relationships, and Features
Table 3 shows the concepts used in the scope of the ontology, along with the relationships, examples, and characteristics of the examples
Table 3. Dictionary of Concepts, Examples, Relationships, and Features
|
Concept Name |
Class Attribute |
Instance Attribute |
Relation |
|
Iran Air 461 |
- |
- |
Same Flight as |
|
Iran Air Flight |
Company Name |
- |
- |
|
Zagross Airlines Flight |
Company Name |
- |
- |
|
Airport |
- |
Name |
Is Arrival airport of Is Departure airport of |
|
Flight Plan |
- |
Arrival Airport Company Name Departure Airport Type of Flights Time of Flights Alternative Airport |
Arrival airport Departure airport |
|
Delay |
- |
Arrival Airport Company Name Departure Airport Delay Time |
Arrival airport Departure airport |
|
Change |
- |
Arrival Airport Company Name Departure Airport Type of Flights Time of Flights |
Arrival airport Departure airport |
|
Iranian Airports |
- |
- |
- |
5.7 Table of Single-responsibility Binary Relations
Table 4 shows the single-responsibility binary relations defined in the dictionary of the concepts. The generation of the table required the explanation of each single-responsibility binary relation in detail, such as the degree of influence, inverse relations, and the mathematical properties.
Table 4. Single-responsibility Binary Relations
|
Source Concept |
Relation Name |
Source card(max) |
Target Concept |
Mathematical Property |
Inverse Relation |
|
Flight |
Arrival airport |
1 |
Airport |
- |
Is Arrival airport of |
|
Flight |
Departure airport |
1 |
Airport |
- |
Is Departure airport of |
|
Flight |
Same Flight as |
N |
Flight |
Symmetrical Transitive |
- |
5.8 Table of Class Features
Contrary to the sample properties, which described the concept samples and received their values in the samples, Table 5 describes the properties of the concept classes and defines the corresponding values in the classes. Class features are inherited by subclasses. For each class feature, the ontology developer should fill the related fields with information on the name of the concept in which the feature is defined, type of the value, value, unit of measurement, value accuracy (in case of numerical values), ability, and sample features, the values of which could be evaluated based on the value of the class feature.
Table 5. Table of Class Features
|
Attribute Name |
Defined at Concept |
Value Type |
Measurement Unit |
precision |
Cardinality |
Value |
|
company Name |
Iran Air |
String |
- |
- |
(1,1) |
IRA |
|
company Name |
Zagross Airline |
String |
- |
- |
(1,1) |
TBZ |
|
company Name |
Mahan Airlines |
String |
- |
- |
(1,1) |
IRM |
|
Degree of seat |
First Class |
Integer |
percent |
1 |
(1,1) |
100 |
|
Degree of seat |
Economy Class |
Integer |
Percent |
1 |
(1,1) |
60 |
|
Degree of seat |
Queen Class |
Integer |
Percent |
1 |
(1,1) |
75 |
5.9 Formal Rules Table (Inferred)
For this stage, the ontology developer should identify and accurately describe the formal rules required for the desired ontology; there are inferred formal rules for each definition. The methontology process should assist the information on name as an explanation for NL, which includes a logical term that officially describes the term using primary instructions, logic, concepts, features, the single-responsibility relationships that refer to its meaning, and the used variables.
Table 6. Formal Rules (inferred)
|
Axiom Name |
Domestic Flight |
|
Description |
Every Domestic Flight that Departed From a Iranian Location must Arrival at another Iranian Location |
|
Expression |
For all (?x,?y,?z) ([Domestic Flight] (?x) and [Departure Place] (?x , ?y) and [arrival Place] (?x,?z) and [Iranian Location ] (?y) -> [Iranian Location ] (?z)) |
|
Concept |
Domestic Flights Iranian Location |
|
Refer Attribute |
|
|
Ad hoc binary relation |
Departure Airport Arrival Airport |
|
Variables |
?x ?y ?z |
5.10 Table of the Definition of Rules
Similar to the previous section, the ontology developer had to determine and describe the required rules for the ontology based on the table of rules. For each rule definition, the methontology considers the items such as the name, NL explanation, formal description of the rule, concepts, traits, and relations for the table, which are referred to, as well as the variables used in the ruling term. The following specific format is used by methontology to draw the rules:
If <conditions> then <consequent>
In the model above, the left side of the phrases includes the rules and conditions, and the right side of the rule includes the adopted arrangements
Table 7. Applied Rules
|
Rule Name |
Separation for Arrival Aircraft |
|
Description |
All Medium aircrafts behind Heavy aircraft shall be Apply 2 minutes minima separation to behind aircraft |
|
Expression |
If [ Medium aircrafts ] (?x) behind [Heavy aircraft] (?y) then [minima separation ] is 2 minutes |
|
Concept |
Medium aircraft Heavy aircraft |
|
Refer Attribute |
Aircraft Type |
|
Ad hoc binary relation |
Sequence |
|
Variables |
?x ?y |
5.11 Description of the Samples
The ontology developer may define the related samples that emerge in the concept dictionary in a sample table in order to define the samples when a special ontology model is generated. For each sample, the ontology developer should define the name, which is a conceptual title belonging to the feature values of the name. Table 8 shows an example of flight TBZ5699 on Mashhad-Tehran route, which was expressed for its FPL message and CNL message.
FPL Message:
FF OIFMZTZX OIIIZAZA OIIIZAZX OIIIZTZX OIIXZQZX OIIXZRZX OIMMZAZA
OIMMZPZX OIMMZTZX OISSZTZX
301838OIMMZPZX
(FPL-TBZ5699-IS
-MD83/M-SDFGHIRWXY/S
-OIMM1200
-N0442F320 ORDOB1C ORDOB A647 SBZ/N0442F320 A647 MUXOR MUXOR1V
-OIII0120 OIFM OISS
-PBN/B2B3B4 DOF/180131 REG/URCQC PER/C )
Supplementary:
-E/0249 P/TBN R/EV S/M J/F
A/W AND R STRIP WITH COMPANY LOGO ON THE TAIL C/AMID)
Cancel Message:
311105OIMMZPZX
(CNL-TBZ5699-OIMM1200-OIII-DOF/180131)
Table 8. FPL and CNL Example for TBZ5699 flight
Pilots and air traffic controllers deal with massive information, including flight safety messages, meteorological messages, aviation NOTAMs, aviation maps, AIS, ATM messages, aviation company information messages, and aircraft system alerts. The analysis and evaluation of such volume of data are extremely difficult. In fact, the main goal of ontology generation for the management of flight safety messages in aviation is to initially establish the same language between the mechanized systems and smart factors involved in the ATM, followed by providing the possibility of the accurate processing of the information by a machine.
Ontology defines a joint glossary for the pilots, flight crew, flight dispatchers, and air traffic controllers who need to share information in a specific field and domain. The glossary contains the definitions of basic concepts for creating flight safety messages, interpretation, and communication to be comprehended by a machine. In the present study, the ontology was generated for the flight safety messages that contained an important part of the flight operation information. The ontology could be directly used by pilots, flight crew, flight dispatchers, air traffic controllers, systems, and web and TCP/IP-based air communication networks (e.g., ATN). The implementation of the ontology was carried out using the methontology methodology and the Protégé software. The use of the ontology based on the IPS-based aviation networks leads to the processing of aviation messages by flight operations systems and machines, thereby ensuring safety and reliability in air traffic affairs. Therefore, it is recommended that an information retrieval structure be developed in the ontology based on the SPARSQL in further studies and be used in a flight operation system.
Declarations
Not applicable.
Automatic dependent surveillance broadcast (ADS–B)
is a surveillance technology in which an aircraft determines its position via satellite navigation and periodically broadcasts it, enabling it to be tracked.
Aircraft Sequencing Problem(ASP)
is a well-known operations research problem. It is concerned with defining optimal strategies for the sequencing of arriving flights at an airport to optimize as part of the management of traffic flow during the final flight phase.
Air traffic management (ATM)
is an aviation term encompassing all systems that assist aircraft to depart from an aerodrome, transit airspace, and land at a destination aerodrome, including Air Traffic Service(ATS), Airspace Management (ASM),and Air Traffic Flow and Capacity Management (ATFCM).
Methontology methodology was developed in the Artificial Intelligence Lab of the
Technical University of Madrid (UPM). The methontology framework enables the
construction of ontologies at the knowledge level and encompasses the identification
of the ontology development process, as well as a lifecycle based on evolving
prototypes and specific techniques for the description of the processes.
Ontology: encompasses a representation, formal naming and definition of the categories, properties and relations between the concepts, data and entities that substantiate one, many, or all domains of discourse.
Terminal Control Area(TCA or TMA): A terminal control area (TMA, or TCA in the U.S. and Canada), also known as a terminal manoeuvring area (TMA) in Europe, is an aviation term to describe a designated area of controlled airspace surrounding a major airport where there is a high volume of traffic.
7-Refrences
[1] Vesselin Petrov (2011). "Chapter VI: Process ontology in the context of applied philosophy". In Vesselin Petrov, ed. Ontological Landscapes: Recent Thought on Conceptual Interfaces Between Science and Philosophy. Ontos Verlag. pp. 137 ff. ISBN 3-86838-107-4.
[2] Mizoguchi .R, Vanwelkenhuysen .J and M. Ikeda. 1997. Task ontology for reuse of problem solving knowledge. In N. J. I. Mars, editor. Towards Very Large Knowledge Bases: Knowledge Building & Knowledge Sharing.
[3] Noy, N. F., & McGuinness, D. L. (2001). Ontology Development 101: A Guide to Creating Your First Ontology (Technical Report No. SMI-2001-0880).
[4] Reiss, M., Moal, M., Barnard, Y., Ramu, J.-P., & Froger, A. (2006). Using Ontologies to Conceptualize the Aeronautical Domain. Paper presented at the International Conference on Human-Computer Interaction in Aeronautics.
[5] Vukmirovic, M., M. Paprzycki, and M. Szymczak. Designing ontology for the open travel alliance airline messaging specification. in Proceedings of the 2006 Information Society Multiconference. 2006. Citeseer.
[6]Putten, B.-J.v., S. Wolfe, and M. Dignum, An ontology for traffic flow management 2008.
[7] Marshall, J. R., & Morris, A. T. (2007). Organization’s Orderly Interest Exploration: Inception, Development and Insights of AIAA’s Topics Database. Paper presented at the AIAA [email protected]
[8] Neff, J. M., Some, R., & Lyke, J. (2007). Lessons Learned in Building a Spacecraft XML Taxonomy and Ontology. Paper presented at the AIAA [email protected]
[9] Valente, A., Holmes, D., & Alvidrez, F. C. (2005). Using a Military Information Ontology to Build Semantic Architecture Models for Airspace Systems. Paper presented at the IEEE Aerospace Conference.
[10] Durak, U., Oguztuzun, H., & Ider, S. K. (2006). An ontology for trajectory simulation. Paper presented at the 38th Winter Simulation Conference.
[11] Dignum, V., Dignum, F., & Meyer, J. J. (2004). An Agent-Mediated Approach to the Support of Knowledge Sharing in Organizations. Knowledge Engineering Review, 19(2), 147–174.
[12] Sierhuis, M., Clancey, W. J., & Van Hoof, R. (2007). Brahms: A multiagent modeling environment for simulating work processes and practices. International Journal of Simulation and Process Modelling, Inderscience Publishers, 3(3), 134–152.
[13] Idris, H., et al. (2006) Field Observations of Interactions Between Traffic Flow Management and Airline Operations. In AIAA 6th Aviation, Technology, Integration, and Operations Conference (ATIO’06). Wichita, Kansas.
[14] Idris, H., et al. (2005) Operational Concept for Collaborative Traffic Flow Management based on Field Observations. In AIAA 5th Aviation, Technology, Integration, and Operations Conference (ATIO’05). Arlington, Virginia.
[15] Wolfe, S. R. (2007). Supporting Air Traffic Flow Management with Agents. Paper presented at the AAAI Spring Symposium: Interaction Challenges for Intelligent Assistants, Stanford, CA.
ACP
Acceptance
ADS-B
Automatic Dependent Surveillance Broadcast
ALR
Alerting
ASP
Aircraft Sequencing Problem
ATC
Air Traffic Control
ARR
flight Arrival message
ATFM
AIR Traffic Follow Management
ATM
Air Traffic Management
ATN
Aeronautical telecommunication network
CDN
Coordination
CHG
flight modification message
CNL
flight cancelation message
CPL
current flight plan
DEP
Flight Departure message
DLA
Flight delay message
EST
estimate
ETA
Estimated Time of Arrival
ETD
Estimated Time of Departure
FDS
Flight data system
FPL
Filed flight plan
IATA
Air Transport Association
ICAO
International Civil Aviation Organization
IPS
Internet protocol suite
LAM
Logical acknowledgement
NAS
national aviation system
Notam
notice for airman
OTA
open travel alliance
OTKM
On-To-Knowledge methodology
RCF
Radio communication Failure
RQP
Request flight plan
RQS
Request supplementary flight plan
SPL
Supplementary flight plan
SSR
Secondary survillance radar
TCA
Traffic Control Area
TCP/IP
Transmission Control Protocol/Internet Protocol
TMA
Terminal Manoeuvring Area
Not applicable.
Availability of data and materials
Datasets that have been used for experiments in this paper are available at: kaggle.com
Competing interests
The authors have no conflict of interest.
Author details
Mahdi Yousefzadeh Aghdam
Department of Computer Engineering ,Neyshobur Branch, Islamic Azad University, Neyshabur IRAN
Seyed Reza Kamel Tabbakh
Department of Computer Engineering, Mashhad Branch, Islamic Azad University, Mashhad, IRAN
Seyed Javad Mahdavi Chabok,
Department of Computer Engineering, Mashhad Branch, Islamic Azad University, Mashhad, IRAN
Maryam kheyrabadi1
Department of Computer Engineering ,Neyshobur Branch, Islamic Azad University, Neyshabur IRAN
Funding
Not applicable
Authors' contributions
Not applicable
Consent for publication:
Acknowledgements
Acknowledgements The authors are thankful to anonymous reviewers for their valuable comments and suggestions that helped improving the quality of the paper.
[1] Vesselin Petrov (2011). "Chapter VI: Process ontology in the context of applied philosophy". In Vesselin Petrov, ed. Ontological Landscapes: Recent Thought on Conceptual Interfaces Between Science and Philosophy. Ontos Verlag. pp. 137 ff. ISBN 3-86838-107-4.
[2] Mizoguchi .R, Vanwelkenhuysen .J and M. Ikeda. 1997. Task ontology for reuse of problem solving knowledge. In N. J. I. Mars, editor. Towards Very Large Knowledge Bases: Knowledge Building & Knowledge Sharing.
[3] Noy, N. F., & McGuinness, D. L. (2001). Ontology Development 101: A Guide to Creating Your First Ontology (Technical Report No. SMI-2001-0880).
[4] Reiss, M., Moal, M., Barnard, Y., Ramu, J.-P., & Froger, A. (2006). Using Ontologies to Conceptualize the Aeronautical Domain. Paper presented at the International Conference on Human-Computer Interaction in Aeronautics.
[5] Vukmirovic, M., M. Paprzycki, and M. Szymczak. Designing ontology for the open travel alliance airline messaging specification. in Proceedings of the 2006 Information Society Multiconference. 2006. Citeseer.
[6]Putten, B.-J.v., S. Wolfe, and M. Dignum, An ontology for traffic flow management 2008.
[7] Marshall, J. R., & Morris, A. T. (2007). Organization’s Orderly Interest Exploration: Inception, Development and Insights of AIAA’s Topics Database. Paper presented at the AIAA [email protected]
[8] Neff, J. M., Some, R., & Lyke, J. (2007). Lessons Learned in Building a Spacecraft XML Taxonomy and Ontology. Paper presented at the AIAA [email protected]
[9] Valente, A., Holmes, D., & Alvidrez, F. C. (2005). Using a Military Information Ontology to Build Semantic Architecture Models for Airspace Systems. Paper presented at the IEEE Aerospace Conference.
[10] Durak, U., Oguztuzun, H., & Ider, S. K. (2006). An ontology for trajectory simulation. Paper presented at the 38th Winter Simulation Conference.
[11] Dignum, V., Dignum, F., & Meyer, J. J. (2004). An Agent-Mediated Approach to the Support of Knowledge Sharing in Organizations. Knowledge Engineering Review, 19(2), 147-174.
[12] Sierhuis, M., Clancey, W. J., & Van Hoof, R. (2007). Brahms: A multiagent modeling environment for simulating work processes and practices. International Journal of Simulation and Process Modelling, Inderscience Publishers, 3(3), 134-152.
[13] Idris, H., et al. (2006) Field Observations of Interactions Between Traffic Flow Management and Airline Operations. In AIAA 6th Aviation, Technology, Integration, and Operations Conference (ATIO’06). Wichita, Kansas.
[14] Idris, H., et al. (2005) Operational Concept for Collaborative Traffic Flow Management based on Field Observations. In AIAA 5th Aviation, Technology, Integration, and Operations Conference (ATIO’05). Arlington, Virginia.
[15] Wolfe, S. R. (2007). Supporting Air Traffic Flow Management with Agents. Paper presented at the AAAI Spring Symposium: Interaction Challenges for Intelligent Assistants, Stanford, CA.