Aeronautical Information Service Data Standardization System and Method

Abstract

This relates to receiving aviation data from different countries and standardizing the data into a common format for use in flight planning and / or controlling aircraft in flight. [Solution] The aeronautical navigation data standardization system (100) comprises an import module (106) configured to receive aeronautical navigation datasets (102) from ANSPs located in each country, a detection module (108) that identifies the type of data and / or the country in which the ANSP is located, a storage module (112) that selects a data standardization case to modify the data based on previous detections of the type of data for one or more previous changes to the data, and an execution module (110) that modifies the data according to the selected one or more data standardization cases. The execution module (110) modifies the format and / or syntax of the aeronautical navigation data in the dataset (102).

Description

Technical Field

[0001]

[0001] Embodiments of the present disclosure relate to receiving aviation data from different countries and standardizing the data into a common format for use in flight planning and / or control of an aircraft during flight.

Background Art

[0002]

[0002] Digital aviation navigation data is information used by pilots and air traffic control before and during flight to ensure flight safety. This information can be used for flight planning, navigation (e.g., avoiding obstacles or other aircraft), and executing in-flight emergency procedures. This information can include airport electronic maps, weather information, aircraft procedures at the airport, primary hazards, air traffic control information, etc.

[0003]

[0003] Digital aviation navigation data, such as aviation information service (AIS) data, is provided by aviation navigation service providers (ANSPs) from various countries in the form of digital data sets. Although these data sets have a globally recognized data model and data exchange standard in the form of the aviation information exchange model (AIXM), each country still provides its respective AIS data set in a country-specific version or "flavor" of AIXM, or in a completely different format such as csv, xml, JSON, shape, etc.

[0004]

[0004] Currently, most known digital data sources are available but not used in Boeing's production systems because the data is still provided or published in paper format (i.e., as a section of the Aeronautical Information Publication (AIP) that is searchable in unstructured formats such as PDF and HTML). An exception is the obstacle dataset known as eTOD (Electronic Topography and Obstacle Data), which is available in digital format in many countries but is no longer included in the AIP. In such cases, country-specific data transformations can be applied in the Jeppesen manufacturing process, the data can be mapped and converted to USF format, and then loaded into the Jeppesen Obstacle Database (JODA). For all other digital sources, such as the AIP dataset containing navigation data, there are currently no solutions that can leverage the advantages of processing digital data sources, such as improved data quality or reduced manual handling of the data, as user data validation is not required in such cases. [Overview of the project]

[0005]

[0005] In one embodiment, an aeronautical data standardization system is provided, comprising a module formed of hardware circuits and one or more processors. The module includes a data import module configured to receive a dataset of aeronautical data from ANSPs located in each country; a detection module configured to examine the dataset and identify one or both of the types of aeronautical data in the dataset or the countries in which the ANSPs are located; a storage module configured to select one or more data standardization cases for one or more datasets in order to modify the aeronautical data in one or more datasets based on one or more previous detections of the types of aeronautical data or countries for one or more previous changes to one or more previous datasets; and an execution module configured to modify the aeronautical data according to the selected one or more data standardization cases, wherein the execution module is configured to modify one or both of the format or syntax of the aeronautical data in one or more datasets.

[0006]

[0006] In another embodiment, the aeronautical navigation data standardization method includes receiving a dataset of aeronautical navigation data from ANSPs located in each country, identifying one or both of the types of aeronautical navigation data in the dataset or the countries in which the ANSPs are located, selecting one or more data standardization cases for one or more datasets to modify the aeronautical navigation data in one or more datasets based on one or more previous detections of the types of aeronautical navigation data or countries for one or more previous changes to one or more previous datasets, and modifying the aeronautical navigation data according to the selected one or more data standardization cases, wherein one or both of the format or syntax of the aeronautical navigation data changes in one or more datasets.

[0007]

[0007] Another aeronautical navigation data standardization system includes a data import module configured to receive a dataset of aeronautical navigation data from ANSP; a detection module configured to inspect the dataset and identify the types of aeronautical navigation data in the dataset; a storage module configured to select one or more data standardization cases for one or more datasets to modify the aeronautical navigation data in one or more datasets based on one or more previous detections of the types of aeronautical navigation data for one or more previous changes to one or more previous datasets; and an execution module configured to modify the aeronautical navigation data according to the selected one or more data standardization cases, the execution module configured to modify one or both of the format or syntax of the aeronautical navigation data in one or more datasets. [Brief explanation of the drawing]

[0008] [Figure 1]

[0008] An embodiment of the aeronautical navigation data standardization system is shown. [Figure 2]

[0009] A flowchart illustrating one example of a method for standardizing aeronautical navigation data is shown. [Figure 3]

[0010] This document presents one example of machine learning / artificial intelligence. [Modes for carrying out the invention]

[0009]

[0011] The above summary, as well as the following detailed descriptions of specific embodiments, will be better understood when read in conjunction with the accompanying drawings. It should be understood that, as used herein, a singular element or step following “a” or “an” does not necessarily exclude multiple such elements or steps. Furthermore, when referring to “one embodiment,” it is not intended to be interpreted as excluding the existence of additional embodiments incorporating the features described herein. Moreover, embodiments “comprising” or “having” one or more elements having certain conditions may include additional elements that do not have such conditions (unless expressly stated otherwise).

[0010]

[0012] One or more embodiments of the subject matter of the invention described herein provide an AIS data standardization system and method capable of inspecting AIS digital datasets from various countries, recognizing non-standardized elements within this source data, and aligning these non-standardized elements to a predefined common AIXM standard format. This standardized data can then be provided to data consumers according to their data requirements, while avoiding country-specific data processing solutions that are maintained on a standalone and manually. For example, the AIS data standardization system and method can operate in a fully automated manner, thereby enabling more frequent updates, larger datasets, etc., than some currently known systems and methods can handle.

[0011]

[0013] Figure 1 shows one embodiment of an aeronautical navigation data standardization system 100. The standardization system 100 receives various datasets 102 (e.g., datasets 102A, 102B, 102n) from various sources 104 (e.g., 104A, 104B, 104n). In the illustrated embodiment, sources 104 represent various ANSPs. For example, one source 104A may represent an ANSP in one country (e.g., Germany), another source 104B may represent another ANSP in another country (e.g., the United States), and another source 104n may represent another ANSP in another country (e.g., France), and so on. Although three sources 104 are illustrated, alternatively, fewer or more sources 104 may provide datasets 102 to the standardization system 100.

[0012]

[0014] Dataset 102 may include data features such as navigation aids, routes, restrictions, airport-helipad locations, important geographical points (i.e., waypoints and terminal points), runway locations, flight patterns, airspace, airway locations, and layouts.

[0013]

[0015] The standardized system 100 includes several modules. Each module may include one or more processors (e.g., integrated circuits, field-programmable gate arrays, microprocessors, application-specific integrated circuits, etc.) that perform the operations described in relation to the various modules, and / or represent hardware circuits connected thereto. Modules may share one or more (or all) of the processors, or two or more modules may employ separate processors to perform the operations described in relation to the modules.

[0014]

[0016] One of these modules is a data import module 106 that receives dataset 102 from ANSP 104. The data import module 106 may include one or more modems, transceivers, etc. They receive dataset 102 from ANSP 104 via one or more computerized wired and / or wireless communication networks. Dataset 102 may be received periodically, such as once every two to three hours, several times a day, or several times a week. Optionally, dataset 102 that modifies or changes previously submitted dataset 102 may be received.

[0015]

[0017] The detection module 108 may receive a dataset 102 from the import module 106. The detection module 108 identifies the standardization cases that apply to the received dataset 102. For example, the detection module 108 may examine the dataset 102 received via the data import module 106 and identify the data source (e.g., ANSP 104) that provided each of the datasets 102. The dataset 102 may include specific information that identifies the country where the ANSP 104 that sent the dataset 102 is located, and specific information that identifies the ANSP 104 that sent the dataset 102.

[0016]

[0018] The execution module 110 can perform data transformations on the provided dataset 102. The execution module 110 may be a module that actually modifies the source data in dataset 102 by applying the prescribed procedures of the detected or selected AIXM standardization cases. For example, the execution module 110 can modify the data in dataset 102 by changing (adding or deleting) spaces in text, numbers, and / or alphanumeric strings, can change the coding used to identify various waypoints, can change the semantics of the data in dataset 102, and can change the geometry of one or more routes, airports, etc., represented in dataset 102.

[0017]

[0019] The execution module 110 can change the data in the dataset 102 to a standard format. The execution module 110 may select a standardization case to apply to each dataset 102 (or may be directed by the storage module 112 as described herein). Various standardization cases may include normalization, standardization, or extension. A normalization case may be selected by the execution module 110 and / or the storage module 112 to change the structure or content of the format of the data (e.g., AIXM data), but without changing the semantics of the data. The data format may define the structure and organization of the data, such as the arrangement and representation within the data. Various data formats may define the syntax of the data, such as rules and conventions for describing and / or encoding the data in various formats. Several examples of various data formats may include CSV, JSON, XML, PDF, etc. The semantics of the data may define the meaning or interpretation of the data, such as the significance of the various elements within the data. The semantics of the data may also provide a framework for understanding the relationships between the various elements within the data. For example, a dataset in CSV format may contain semantic information about the meaning of various parts of the data (e.g., columns, groups, etc.). Conversely, standardization cases may be selected by the execution module 110 and / or storage module 112 to modify the semantics of the data in dataset 102. Extension cases may be selected by the execution module 110 and / or storage module 112 to store data in dataset 102 that is not covered by the AIXM standard and to optionally add further AIXM-specific features, characteristics, and relationships.

[0018]

[0020] Standardization cases can be defined at various levels. At one level, a general standardization may apply to all datasets 102, regardless of the source ANSP 104 or the country of ANSP 104. At another level, country-specific standardization may be applied to datasets 102 based on the country from which the dataset 102 originates (e.g., where the ANSP 104 providing the dataset 102 is located). Various standardization changes may apply to datasets 102 from different countries. For example, a dataset 102 from a first country may be modified in a first way, while a dataset 102 from a different second country may be modified in a different second way. If a country includes multiple ANSPs providing various datasets 102, the same country-specific standardization may apply to all datasets 102 from those ANSP 104s. At yet another level, dataset type-specific standardization may apply. This type of standardization may apply to specific types of datasets 102. For example, a dataset 102 containing information about obstacles (e.g., an obstacle dataset) may have a first type of modification applied to dataset 102, while a dataset 102 containing information about waypoints (e.g., a waypoint dataset) may have a different second type of modification applied to dataset 102. Standardization specific to the same type of dataset may be applied to datasets 102 containing the same type of information, regardless of the country where the source ANSP 104 of dataset 102 is located.

[0019]

[0021] Different standardization cases may be identified by unique identifiers known to the storage module 112 and the execution module 110. Each different standardization case may include metadata associated with the standardization changes applied to the dataset 102 modified by the respective case, as well as a problem statement, justification for the changes to be made, details of the data transformation process, and one or more examples of the changes made to the data.

[0020]

[0022] Regarding the normalization group of standardization cases, namespace standardization can be applied to dataset 102 regardless of the country where ANSP104, which provides dataset 102, is located (e.g., standardization is not country-specific) and regardless of the type of dataset being standardized (e.g., standardization is not dataset-specific). Namespace standardization can change the set of codes (e.g., names) used to identify and refer to various types of objects within dataset 102. Namespaces can help ensure that objects or elements within dataset 102 have unique names, thereby allowing objects or elements to be easily identified and distinguished from one another. Namespace standardization can modify data by assigning a version of the AIXM standard to the data. For example, ANSP104, which provided dataset 102, may be using or reporting (to the executable module 110) that dataset 102 was created using AIXM version 5.1.1. Optionally, the execution module 110 may identify a version of AIXM that uses the execution module 110 and / or one or more consumer systems 114 (e.g., consumer systems 114A, 114B, 114n). Consumer systems 114 may represent navigation databases or systems, flight planning systems, airport mapping databases, chart generation systems, flight data processing systems, obstacle databases, procedure design systems, airspace planning systems, NOTAM systems, AIS systems, etc., which use the database 102 (after standardization) to plan or schedule flights, airport resources, air traffic control, etc.

[0021]

[0023] For example, dataset 102 may contain the item "xmlns:aixm="http: / / www.aixm.aero / schema / 5.1.1"". This data item (or element, object) can be standardized by the execution module 110 by changing the data item to "xmlns:aixm-5.1.1="http: / / www.aixm.aero / schema / 5.1.1". This change involves adding the AIXM version number after the string "aixm".

[0022]

[0024] The feature of referring to the normalization of the normalization group of the standardized case is not country-specific or dataset-specific and can be applied to dataset 102. This normalization can find local references between features within dataset 102, such as xlink:href references to the gml:id attribute, and resolve these local references by using abstract references to the universally unique identifier (UUID) of AIXM. For example, dataset 102 includes the entry "aixm:bobstacle xlink:href="#uuid.01dec353-a1b0-4156...", but this can be changed to "aixm-5.1.1:bobstacle xlink:href="urn:uuid:dd8dff39..." to reference the UUID instead of the local reference or identifier within dataset 102.

[0023]

[0025] The data value initialization normalization of the general normalization group of the case is not country-specific or dataset-specific and can be applied to dataset 102. This normalization can map the values of the code lists of the AIXM schema for which values are missing from dataset 102. For example, if dataset 102 has a specific data item (e.g., "OTHER") that is not standard in the AIXM schema, this standardized case can remove all "OTHER" values from dataset 102.

[0024]

[0026] The integration normalization of the general normalization group of the case can be applied to dataset 102 and not be country-specific, but can also be applied to a specific dataset (e.g., the normalization is dataset-specific). This normalization can be applied to dataset 102 that stores information about obstacles to an aircraft. This normalization can add information to dataset 102 that has limited information, such as the type of obstacle (e.g., characteristic type), when that information is missing from dataset 102.

[0025]

[0027] The alignment standardization of the general standardization group of cases can be applied to dataset 102 and is not country-specific or dataset-specific. This standardization can correct the coding of data features in the incorrect dataset 102 according to the AIXM coding guidelines. For example, the data item of the takeoff flight path area is encoded as OTHER:TAKEOFFFLIGHTPATHAREA. TAKEOFFFLIGHTPATHAREA is inaccurate or does not follow the AIXM coding guidelines. The execution module 110 can change this data item to OTHER:TAKE_OFF_FLIGHT_PATH_AREA.

[0026]

[0028] The part designator creation standardization of the general standardization group of cases can be applied to dataset 102 from a specific country (e.g., Austria or Norway) and dataset 102 containing information about obstacles. Depending on the ANSP 104, it may not provide designator values for the vertical structures identified within dataset 102. This standardization is used by the execution module 110 to add values to the data items related to multi-part obstacles, indicating that multiple obstacles are different parts of the same multi-part obstacle. Otherwise, the designators of the obstacles in dataset 102 may be duplicated or unable to be imported into the system of the consumer 114.

[0027]

[0029] Base elevation standardization can be applied to dataset 102 from a specific country (e.g., Austria) and to dataset 102 containing information about obstacles. Dataset 102 may include elevations of various obstacles to indicate how high these obstacles extend, in order to assist flight planning in order to avoid collisions with obstacles. ANSP 104 may provide these elevations as base elevations of obstacles, rather than elevations of the top or highest point of the obstacles. This standardization can be used by the execution module 110 to add information (e.g., text) to the obstacle elevations to indicate that the provided elevations are base elevations and not top elevations of the obstacles. This additional information may help consumers 114 understand what the obstacle elevations in dataset 102 mean.

[0028]

[0030] The memory module 112 can store which AIXM standardizations have already been performed on the dataset 102. For example, the memory module 112 can check which standardization cases have been applied to dataset 102 containing data of a particular type (e.g., obstacles, airports, runways, etc.) and / or dataset 102 from ANSP 104 in a particular country. The memory module 112 can learn from previous standardization cases and automatically continue to apply the same standardization cases when future datasets 102 are received from the same ANSP 104 and / or contain the same type of data as before. For example, if a first dataset 102 contains airport information from ANSP 104 in a first country and a first set of standardization cases has been applied to the first dataset 102 by the execution module 110, the memory module 112 can instruct the execution module 110 to apply the same first set of standardization cases to a second dataset 102 containing airport information and / or received from the same country. However, the memory module 112 can instruct the execution module 110 to apply a different second set of standardization cases to a third dataset 102 received from ANSP 104 in a different second country, which may contain different information (e.g., waypoint information).

[0029]

[0031] The management module 116 can be used to control which standardization cases are applied to (or not applied to) various datasets 102. For example, some standardization cases can be deactivated or turned off so that they are no longer applied to dataset 102, and activated or turned on so that they are applied to dataset 102. Standardization cases can be deactivated or activated based on user input or based on the detection of one or more errors. For example, the consumer system 114 may provide feedback to the management module 116 indicating errors in dataset 102. The standardization cases that resulted in these errors can be automatically deactivated or manually deactivated.

[0030]

[0032] Similarly, the selection module 118 can be used to control which standardization cases are applied to (or not applied to) various datasets 102. For example, a set or group of standardization cases may be selected to apply to datasets 102 of a particular type (e.g., obstacles) and / or from a particular country. The selection module 118 can instruct which standardization cases are applied to various datasets 102. The selection module 118 may select standardization cases based on user feedback and / or feedback from the consumer system 114. For example, the consumer system 114 may send an instruction to the selection module 118 (e.g., via the reporting module 122 and / or execution module 118 described herein) instructing which standardization cases are applied to a particular dataset 102 (e.g., a dataset 102 containing a particular type of information, a dataset 102 from a particular ANSP 104, a dataset 102 from ANSP 104 in a particular country, etc.).

[0031]

[0033] The execution module 110 may output one or more transformed datasets 102' after applying one or more standardization cases to one or more datasets 102 received by the execution module 110. These transformed datasets 102' may contain modified data compared to dataset 102, as described above. The transformed datasets 102' are output by the execution module 110 and may be recorded or stored in the database 120. The database described herein may represent one or more tangible, non-transient, computer-readable storage media, such as a computer hard drive, a removable drive, a cloud drive, or a server. The transformed datasets 102' may be stored for review and verification of the changes made by the application of the standardization cases. Optionally, one or more consumer systems 114 may obtain the transformed datasets 102' from the database 120.

[0032]

[0034] The reporting module 122 may generate and store a report 124 listing the standardization cases applied to dataset 102 (to generate the transformed dataset 102'). These reports 124 may be stored in a separate database 126 for review and verification and / or accessed by the consumer system 114. Optionally, the reporting module 122 may send the report 124 and / or the transformed dataset 102' to the consumer system 114. The reporting module 122 may assist the consumer system 114 in verifying and confirming the transformation of the data in dataset 102 to dataset 102'.

[0033]

[0035] Figure 2 shows a flowchart of one embodiment of method 200 for standardizing a dataset. Method 200 may represent steps performed by the standardization system 100. In step 202, the dataset is received from various sources. These datasets may include aeronautical navigation data, as described above, and may be received from ANSPs in various countries. In step 204, one or more source countries and the types of data contained within the dataset are detected. For example, it may be known that the ANSP that sent the dataset is located in a particular country, and / or the dataset may be examined to identify the types of data contained within it.

[0034]

[0036] In section 206, standardization cases applicable to the data within the dataset are identified. These standardization cases may be identified based on prior applications of the data standardization cases. For example, based on prior analysis of the dataset and prior applications of the standardization cases, the same standardization case may be applied to datasets from ANSP in the same country and / or datasets containing the same type of data. In section 208, activated and / or selected standardization cases are identified. Some data standardization cases may be deactivated and therefore not applicable to the dataset. Other data standardization cases may be activated and applicable to the dataset (if the case is identified based on country and / or data type). Furthermore, some standardization cases may be selected for application to the dataset (e.g., by a consumer system or user of the standardization system).

[0035]

[0037] In 210, data standardization cases identified based on country and / or data type are applied to the dataset. These data standardization cases are activated (or deactivated) and / or selected for application and applied to the dataset. This may modify or transform the data, such as by changing the format and / or syntax of the data within the dataset. In 212, the dataset modified by the application of a standardization case may be stored in the database and / or communicated to the consumer system. Furthermore, a report indicating the data standardization cases applied to the dataset may be generated, sent to the consumer system and / or stored in the database. This allows for verification of the data modifications made.

[0036]

[0038] The standardization systems and methods described herein provide technical solutions to a technical problem: the ability to quickly, consistently, and accurately correct aeronautical navigation data into a standardized format, even when the given data volume is large and the data is frequently updated. Without the data standardization systems and methods described herein, the volume and frequency of updates of data in aeronautical navigation datasets are too much for humans to consistently correct without introducing human error into the dataset. Given that accurate data is crucial for the safe operation of many aircraft flying simultaneously near the same obstacles or airports, the standardization systems and methods provide technical solutions that help ensure the safe operation of aircraft even when datasets are large and frequently updated.

[0037]

[0039] Figure 3 shows one embodiment of a machine learning (ML) / artificial intelligence (AI) system 300. The ML / AI system 300 may represent one or more modules of the standardized system 100 shown in Figure 1, such as the memory module 112. The ML / AI system 300 can be embodied as one or more application-specific integrated circuits (ASICs) for an artificial neural network (ANN). The ML / AI system 300 (or one or more ASICs) may include a series 302 of multiple layers 304A-D. Each layer includes one or more artificial neurons 306 arranged as one or more neuron arrays or sequences. Four neurons 306 are shown in each layer 304A-D, and four layers 304A-D are shown, but alternatively, different numbers of neurons 306 may also be in one or more of the layers 304A-D, and / or different numbers of layers 304A-D may exist.

[0038]

[0040] The ML / AI system 300 may include neurons 306 located in the input layer 304A, the output layer 304D, and two or more fully connected hidden or intermediate layers 304B, 304C between the input layer 304A and the output layer 304D. Each neuron 306 may include or represent a register 308, a microprocessor 310, and at least one input 312. A neuron 306 may produce an output based on one or more activation functions. A neuron 306 may receive input from another neuron 306 (for example, the output from one neuron 306 may be an input to another neuron 306). This input may also include a set of weights. Neurons 306 may be connected to each other via synaptic circuits 314, 314'. The synaptic circuits 314, 314' may include or represent memory for storing synaptic weights.

[0039]

[0041] One or more neurons 306 in the input layer 304A of the ML / AI system 300 may receive an input 316 into the ML / AI system 300. The input 316 may include, for example, one or more of the following: a dataset 102, the identification of the ANSP 104 that sent or otherwise provided the dataset 102 (one or more), the country in which the dataset 102 was sent or otherwise located, and / or the type of information contained in the dataset 102 (one or more). Neuron 306 may receive input data 316 via one or more inputs 312 of the neuron 306 in the input layer 304A. Neuron 306 receives the input data 316 and applies one or more formulas or relations (including weights) stored in register 308 to generate an output. The processor 310 of neuron 306 applies the formula / relation and may pass the output to another neuron 306 in the same layer 304A or in different layers 304B, 304C. The output from one neuron 306 is passed along the synaptic circuit 314 to another neuron 306 and used as input to this other neuron 306. This process continues until one or more neurons 306 in the output layer 304D produce an output 318 from the ML / AI system 300.

[0040]

[0042] The synaptic circuits 314, 314', the weights stored within the synaptic circuits 314, 314', and / or the mathematical relationships between neurons 306 can define a model used to determine which standardization case should be applied to the dataset 102 (one or more). For example, the AI / ML system 300 may examine the input data 316 and, based on the training of the AI / ML system 300 defining the synaptic circuits 314, 314', the weights stored within the synaptic circuits 314, 314', and / or the mathematical relationships between neurons 306, select the modifications to be made to the dataset 102 (one or more).

[0041]

[0043] During training of the AI / ML system 300, labeled data may be provided as input data 316 to the AI / ML system 300. The labeled data may include standardization cases previously selected to modify datasets 102 sent from various datasets 102 and / or ANSP 104 in various countries. For example, the labeled data may identify which data standardization cases have been applied to dataset 102 in the past. Neuron 306 processes the input data 316 to generate a training output for the AI / ML system 300. This training output may identify which standardization cases should be applied to dataset 102 (one or more). This output may then be compared to data standardization cases selected for dataset 102 (one or more) (e.g., when previously modified and / or selected by a human analyst).

[0042]

[0044] Feedback may be provided to the AI / ML system 300 in the form of a display of the calculated error or other difference between the standardization case selected by the AI / ML system 300 and the standardization case previously applied by the (one or more) dataset 102. Based on this error, the neuron 306 may modify one or more of the synaptic circuits 314 that connect neuron 306, the weights applied by one or more of the neurons 306, and / or the mathematical relationships between the neurons 306. For example, some synaptic circuits 314 may be changed to modified synaptic circuits 314'. This may result in the same input 316 causing different neurons 306 to receive the input, pass the output to other neurons, and produce different outputs 318' from the AI / ML system 300. Consequently, modifying one or more of these weights or relationships (e.g., synaptic circuits 314, 314') may also change which standardization case is selected to be applied to the (one or more) dataset 102. In other words, the AI / ML system 300 learns, based on previous errors, which standardization case should be applied to the (one or more) dataset 102.

[0043]

[0045] As described herein, after training the AI / ML system 300, it may use (one or more) trained models to select standardization cases to modify the dataset 102. During post-training iterations of the operation of the AI / ML system 300, further feedback may be provided to the AI / ML system 300 based on errors in the selection of standardization cases. For example, after training, an analyst may verify which standardization cases were selected for various datasets 102 and provide feedback to the AI / ML system 300. The AI / ML system 300 may repeatedly receive such feedback and modify one or more weights and / or one or more synaptic circuits, etc. Thereafter, the AI / ML system 300 repeatedly changes to improve and reduce errors in selecting standardization cases to be applied to the dataset 102.

[0044]

[0046] In contrast to several known solutions, the standardization systems and methods described herein enable country-specific and / or data-specific data transformations without the need for separate standalone workbenches or tools for data transformation. This eliminates the need to manually set up and configure each data transformation workbench individually (for each country, for each dataset). Whenever there are changes to the schema or structure of datasets provided by ANSP, the standardization systems and methods will not require manual analysis and modification to accept those changes. The modified datasets generated by the standardization systems and methods provide a consistent data standard usable by all consumer systems, while avoiding manual inspection and modification of datasets when they are provided and / or updated. One or more operations can be performed using the modified datasets. For example, a modified dataset can be used to plan a flight and / or control an aircraft in flight.

[0045]

[0047] Furthermore, this disclosure includes several embodiments as defined below.

[0046]

[0048] Article 1. An aeronautical navigation data standardization system comprising a module formed of hardware circuits and one or more processors, the module including a data import module configured to receive datasets of aeronautical navigation data from ANSPs located in each country; a detection module configured to examine the datasets and identify either or both of the types of aeronautical navigation data in the datasets or the countries in which the ANSPs are located; a storage module configured to select one or more data standardization cases for one or more datasets in order to modify the aeronautical navigation data in one or more datasets based on one or more previous detections of the types of aeronautical navigation data or the countries in which one or more previous datasets; and an execution module configured to modify the aeronautical navigation data according to the selected one or more data standardization cases, the execution module configured to modify either or both of the format or syntax of the aeronautical navigation data in one or more datasets.

[0047]

[0049] Article 2. The aeronautical navigation data standardization system as described in Clause 1 also includes a reporting module configured to transmit the modified one or more datasets to one or more aeronautical consumer systems for use, for example, in flight planning or aircraft control. Optionally, the datasets may be used for generating or creating aeronautical charts, updating onboard navigation databases used to control aircraft flight, updating or running training or flight simulators, updating or controlling synthetic vision systems, generating alerts from ground proximity warning systems and minimum safe altitude warning (MSAW) systems, determining contingency response procedures to be used for events such as misapproach or emergency situations during takeoff, analyzing aircraft operational limitations, designing aircraft instrument procedures (including turning procedures), identifying in-route "drift-down" procedures and in-route emergency landing sites, ground guidance and navigation (e.g., A-SMGCS), traffic awareness including monitoring and runway approach detection and alerting, resource and aerofield facility management, and facilitating aerofield, terminal and route-related aeronautical information, including NOTAMs.

[0048]

[0050] Article 3. The aeronautical data standardization system according to Clause 1 or 2, further comprising a reporting module configured to produce and store reports of one or more data standardization cases selected and applied to changes in the format or syntax of the aeronautical data in one or more of the datasets.

[0049]

[0051] Article 4. The aeronautical data standardization system according to any one of Clauses 1 to 3, further comprising a selection module configured to select the data standardization case to be applied to the one or more datasets, regardless of the type of aeronautical data or the country of the ANSP that provided the one or more datasets.

[0050]

[0052] Article 5. The aeronautical navigation data standardization system according to any one of Clauses 1 to 4, further comprising a management module configured to selectively deactivate one or more of the data standardization cases, and to prevent the one or more of the deactivated data standardization cases from being used to modify the format or syntax of the aeronautical navigation data in one or more of the datasets.

[0051]

[0053] Article 6. The aeronautical navigation data standardization system described in any one of Clauses 1 to 5 includes one or more of the following in the dataset: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground contamination, endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, meteorological conditions, etc.

[0052]

[0054] Article 7. An air navigation data standardization system according to any one of Clauses 1 to 6, wherein the execution module is configured to apply the one or more data standardization cases to the air navigation data in order to rename objects in the air navigation data, add a universally unique identifier to one or more objects in the air navigation data, remove values ​​from the air navigation data, add an identifier to an object in the air navigation data, or change the encoding of the air navigation data.

[0053]

[0055] Article 8. The aeronautical navigation data standardization system according to any one of Clauses 1 to 7, wherein the hardware circuit of the module and the one or more processors include an ASIC for an ANN, the ASIC comprising neurons organized in an array, each of the neurons including a register, a processing element, and at least one input, and synaptic circuits, each of the synaptic circuits including a memory for storing synaptic weights, each of the neurons being connected to at least one other of the neurons via at least one of the synaptic circuits, and the processing element of the neuron being configured to select the one or more data standardization cases to apply to the one or more of the datasets based on a previous selection of the one or more data standardization cases.

[0054]

[0056] Article 9. A method for standardizing air navigation data, comprising: receiving a dataset of air navigation data from ANSPs located in each country; identifying one or both of the types of air navigation data in the dataset or the countries in which the ANSPs are located; selecting one or more data standardization cases for one or more datasets to modify the air navigation data in one or more datasets based on one or more previous detections of the types of air navigation data or the countries for one or more previous changes to one or more previous datasets; and modifying the air navigation data according to the selected one or more data standardization cases, wherein one or both of the format or syntax of the air navigation data changes in one or more datasets.

[0055]

[0057] Article 10. The aeronautical navigation data standardization method described in Clause 9, further comprising transmitting the modified one or more datasets to one or more aeronautical consumer systems used for flight planning or aircraft control, aeronautical chart generation, registration in onboard navigation databases, use in training / flight simulators, use in synthetic vision systems, use in ground proximity warning systems and minimum safe altitude warning (MSAW) systems, identification of contingency response procedures used for misapproach or emergency events during takeoff, analysis of aircraft operational limitations, design of aircraft instrument procedures (including turning procedures), identification of in-route "drift-down" procedures and in-route emergency landing sites, ground guidance and navigation (e.g., A-SMGCS), traffic awareness including monitoring and runway approach detection and warning, resource and aerofield facility management, and facilitation of aerofield, terminal and route-related aeronautical information, including NOTAMs.

[0056]

[0058] Article 11. The aeronautical data standardization method according to Clause 9 or 19, further comprising creating and storing a report of one or more data standardization cases that are selected and applied to changes in the format or syntax of the aeronautical data in one or more of the datasets.

[0057]

[0059] Article 12. A method for standardizing air navigation data according to any one of paragraphs 9 to 11, further comprising selecting the data standardization case to be applied to the one or more datasets, regardless of the type of air navigation data or the country of the ANSP that provided the one or more datasets.

[0058]

[0060] Article 13. The aeronautical navigation data standardization method according to any one of Clauses 9 to 12, further comprising selectively deactivating one or more of the deactivated data standardization cases to prevent them from being used to modify the format or syntax of the aeronautical navigation data in one or more of the datasets.

[0059]

[0061] Article 14. The aeronautical navigation data standardization method described in any one of Clauses 9 to 13, wherein the aeronautical navigation data in the dataset includes one or more of the following: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground contamination, flight endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, meteorological conditions, etc.

[0060]

[0062] Article 15. A method for standardizing air navigation data according to any one of Clauses 9 to 14, wherein one or more of the data standardization cases are applied to the air navigation data in order to rename objects in the air navigation data, add a universally unique identifier to one or more objects in the air navigation data, remove values ​​from the air navigation data, add an identifier to an object in the air navigation data, or change the encoding of the air navigation data.

[0061]

[0063] Article 16. An aeronautical navigation data standardization system comprising: a data import module configured to receive a dataset of aeronautical navigation data from ANSP; a detection module configured to inspect the dataset and identify the type of aeronautical navigation data within the dataset; a storage module configured to select one or more data standardization cases for one or more datasets in order to modify the aeronautical navigation data in one or more datasets based on one or more previous detections of the type of aeronautical navigation data for one or more previous changes to one or more previous datasets; and an execution module configured to modify the aeronautical navigation data according to the selected one or more data standardization cases, wherein the execution module is configured to modify one or both of the format and syntax of the aeronautical navigation data in one or more datasets.

[0062]

[0064] Article 17. The detection module is also configured to identify the country where the ANSP that provided the one or more of the dataset is located, and the storage module is configured to select the one or more of the data standardization cases based on the identified country, in the aeronautical navigation data standardization system according to Clause 16.

[0063]

[0065] Article 18. An air navigation data standardization system as described in Clause 16 or 17, further comprising a reporting module configured to transmit modified data sets to one or more air consumer systems used for flight planning or aircraft control, generating aeronautical charts, registering in onboard navigation databases, use in training / flight simulators, use in synthetic vision systems, use in ground proximity warning systems and minimum safe altitude warning (MSAW) systems, identification of contingency response procedures used for misapproach or emergency events during takeoff, analysis of aircraft operational limitations, design of aircraft instrument procedures (including turning procedures), identification of in-route "drift-down" procedures and in-route emergency landing sites, ground guidance and navigation (e.g., A-SMGCS), traffic awareness including monitoring and runway approach detection and warning, resource and aerofield facility management, and facilitating aerofield, terminal and route-related aeronautical information, including NOTAMs.

[0064]

[0066] Article 19. The aeronautical navigation data standardization system described in any one of Clauses 16 to 18 includes one or more of the following in the dataset: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground contamination, endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, meteorological conditions, etc.

[0065]

[0067] Article 20. An air navigation data standardization system according to any one of Clauses 16 to 19, wherein the execution module is configured to apply the one or more data standardization cases to the air navigation data in order to rename objects in the air navigation data, add a universally unique identifier to one or more objects in the air navigation data, remove values ​​from the air navigation data, add an identifier to an object in the air navigation data, or change the encoding of the air navigation data.

[0066]

[0068] For the purpose of describing the embodiments of this disclosure, various spatial and directional terms such as top, bottom, bottom, center, lateral, horizontal, vertical, and forward may be used, but it should be understood that such terms are used only in relation to the orientation shown in the drawings. These orientations may be reversed, rotated, or otherwise changed, resulting in top becoming bottom, bottom becoming top, or horizontal becoming vertical.

[0067]

[0069] When used herein, any structure, limitation, or element “configured to perform a work or action” is structurally formed, configured, or adapted in particular to correspond to the work or action. For clarity and to avoid misunderstanding, any object that can be modified to perform a work or action is not “configured / set up to perform a work or action” as used herein.

[0068]

[0070] The above description should be understood as illustrative, not limiting. For example, the examples (and / or embodiments thereof) described above can be used in combination with each other. In addition, many modifications can be made to adapt the teachings of the various embodiments of this disclosure to specific situations or materials without departing from the scope of this disclosure. The dimensions and types of materials described herein are intended to define the embodiments of the various embodiments of this disclosure, but the embodiments are illustrative, not limiting. Many other embodiments will become apparent to those skilled in the art by examining the above description. The scope of the various embodiments of this disclosure should be determined in relation to the appended claims and the entire scope of equivalents to which such claims are recognized. In the appended claims and embodiments for carrying out the invention herein, the words “including” and “in which” are used as plain English synonyms for “comprising” and “wherein,” respectively. Furthermore, terms such as “first,” “second,” and “third” are used merely as labels and are not intended to impose numerical requirements on those objects. Moreover, the following limitations on the claims are not written in means-plus-function form and are not intended to be interpreted under Section 112(f) of the U.S. Patent Act unless or not explicitly used with the phrase “means for” followed by a description of a function lacking further structure.

[0069]

[0071] The use of examples in the description herein is intended to disclose various embodiments of the disclosure, including the best mode, and to enable a person skilled in the art to carry out various embodiments of the disclosure, including creating and using any device or system and implementing any incorporated method. The patentability of the various embodiments of the disclosure is defined by the claims and may include other embodiments that a person skilled in the art can imagine. Such other embodiments are intended to be within the scope of the claims if the embodiment has structural elements that are not different from the language of the claims, or if the embodiment includes equivalent structural elements that differ only slightly from the language of the claims.

Claims

1. An aeronautical navigation data standardization system (100), comprising a module formed from a hardware circuit and one or more processors (310), wherein the module is A data import module (106) configured to receive a dataset (102) of aeronautical navigation data from aeronautical navigation source providers (ANSPs) located in various countries. A detection module (108) configured to examine the dataset (102) and identify either or both of the types of aeronautical navigation data in the dataset (102) or the country in which the ANSP is located. A storage module (112) configured to select one or more data standardization cases for one or more of the datasets (102) in order to modify the aeronautical navigation data in one or more of the datasets (102) based on one or more previous detections of the type or country of the aeronautical navigation data for one or more previous changes to one or more previous datasets (102), and An aeronautical navigation data standardization system (100) comprising an executable module (110) configured to modify the aeronautical navigation data according to one or more selected data standardization cases, the executable module (110) configured to modify one or both of the format or syntax of the aeronautical navigation data in one or more of the dataset (102).

2. The aeronautical navigation data standardization system (100) according to claim 1, further comprising a reporting module configured to transmit the modified one or more datasets (102) to one or more aeronautical consumer systems for use in flight planning or aircraft control.

3. The aeronautical data standardization system (100) according to claim 1, further comprising a reporting module configured to produce and store reports of one or more data standardization cases that are selected and applied to changes in the format or syntax of the aeronautical data in one or more of the dataset (102).

4. The aeronautical data standardization system (100) according to claim 1, further comprising a selection module configured to select the data standardization case to be applied to the one or more datasets (102), regardless of the type of aeronautical data or the country of the ANSP that provided the one or more datasets (102).

5. The aeronautical navigation data standardization system (100) according to claim 1, further comprising a management module configured to selectively deactivate one or more of the data standardization cases, and to prevent the one or more of the deactivated data standardization cases from being used to change the format or syntax of the aeronautical navigation data in one or more of the dataset (102).

6. The aeronautical navigation data standardization system (100) according to claim 1, wherein the aeronautical navigation data in the dataset (102) includes one or more of the following: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground pollution, flight endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, or meteorological conditions.

7. The aeronautical navigation data standardization system (100) according to claim 1, wherein the execution module (110) is configured to apply the one or more data standardization cases to the aeronautical navigation data in order to change the names of objects in the aeronautical navigation data, add a universally unique identifier to one or more objects in the aeronautical navigation data, remove values ​​from the aeronautical navigation data, add an identifier for an object to the aeronautical navigation data, or change the encoding of the aeronautical navigation data.

8. The hardware circuit of the module and the one or more processors (310) include an application-specific integrated circuit (ASIC) for an artificial neural network (ANN), and the ASIC is Neurons (306) organized within an array, each of the neurons (306) includes a register, a processing element, and at least one input, and The aeronautical navigation data standardization system according to claim 1, comprising a synaptic circuit, each of which includes a memory for storing synaptic weights, each of which is connected to at least one other of the neurons (306) via at least one of the synaptic circuits, and the processing element of the neurons (306) is configured to select the one or more data standardization cases to apply to the one or more of the dataset (102) based on a previous selection of the one or more data standardization cases.

9. A method for standardizing aeronautical navigation data (200), Receiving a dataset (102) of aeronautical navigation data from aeronautical navigation source providers (ANSPs) located in each country, Identifying either or both of the types of aeronautical navigation data in the dataset (102) or the country in which the ANSP is located. Based on one or more previous detections of the type or country of the aeronautical navigation data for one or more previous changes to one or more previous datasets, to modify the aeronautical navigation data in one or more of the datasets (102), by selecting one or more data standardization cases for one or more of the datasets (102), and A method for standardizing aeronautical navigation data (200), which includes modifying the aeronautical navigation data in accordance with one or more selected data standardization cases, wherein the format or syntax of the aeronautical navigation data, or both, changes in one or more of the dataset (102).

10. A method for standardizing air navigation data (200) according to claim 9, further comprising transmitting the modified one or more data sets (102) to one or more air consumer systems used for flight planning or aircraft control.

11. A method for standardizing aeronautical data (200) according to claim 9, further comprising creating and storing a report of one or more data standardization cases that are selected and applied to changes in the format or syntax of the aeronautical data in one or more of the dataset (102).

12. A method for standardizing air navigation data (200) according to claim 9, further comprising selecting a data standardization case to be applied to the one or more datasets (102), regardless of the type of air navigation data or the country of the ANSP that provided the one or more datasets (102).

13. The aeronautical navigation data standardization method (200) according to claim 9, further comprising selectively deactivating one or more of the data standardization cases so as to prevent the deactivated one or more of the data standardization cases from being used to modify the format or syntax of the aeronautical navigation data in one or more of the dataset (102).

14. The aeronautical navigation data standardization method (200) according to claim 9, wherein the aeronautical navigation data in the dataset (102) includes one or more of the following: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground pollution, flight endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, or meteorological conditions.

15. A method for standardizing aeronautical navigation data (200) according to claim 9, wherein one or more data standardization cases are applied to the aeronautical navigation data in order to change the names of objects in the aeronautical navigation data, add a universally unique identifier to one or more objects in the aeronautical navigation data, remove values ​​from the aeronautical navigation data, add an identifier for an object to the aeronautical navigation data, or change the encoding of the aeronautical navigation data.

16. A standardization system for aeronautical navigation data (100), A data import module (106) configured to receive a dataset (102) of aeronautical navigation data from an Aeronautical Navigation Source Provider (ANSP), A detection module (108) configured to examine the dataset (102) and identify the type of aeronautical navigation data within the dataset (102), A storage module (112) configured to select one or more data standardization cases for one or more of the datasets (102) in order to modify the aeronautical navigation data in one or more of the datasets (102) based on one or more previous detections of the type of the aeronautical navigation data for one or more previous changes to one or more previous datasets (102), and An aeronautical navigation data standardization system (100) comprising an executable module (110) configured to modify the aeronautical navigation data according to one or more selected data standardization cases, wherein the executable module (110) is configured to modify one or both of the format or syntax of the aeronautical navigation data in one or more of the dataset (102).

17. The aeronautical navigation data standardization system (100) according to claim 16, wherein the detection module (108) is also configured to identify the country where the ANSP that provided the one or more of the dataset (102) is located, and the storage module (112) is configured to select the one or more of the data standardization cases based on the identified country as well.

18. The aeronautical data standardization system (100) according to claim 16, further comprising a reporting module configured to transmit the modified one or more datasets (102) to one or more aeronautical consumer systems used for flight planning or aircraft control.

19. The aeronautical navigation data standardization system (100) according to claim 16, wherein the aeronautical navigation data in the dataset (102) includes one or more of the following: navigation aids, landing systems, satellite navigation systems, radar systems, aeronautical ground lights, routes, cruise schedules, flight restrictions, airports, heliports, seaports, aprons, taxiways, lighting, markings, signs, gates, waypoints, landing areas, ground pollution, flight endurance patterns, terminal procedures, minimum and emergency safe altitudes, airspace, grid MORA, obstacles, ground assessment areas, aviation authorities, airport ground services, traffic separation and positioning services, information services, communication facilities, aerial refueling, aircraft and flight characteristics, rules and procedures, or meteorological conditions.

20. The aeronautical navigation data standardization system (100) according to claim 16, wherein the execution module (110) is configured to apply the one or more data standardization cases to the aeronautical navigation data in order to change the names of objects in the aeronautical navigation data, add a universally unique identifier to one or more objects in the aeronautical navigation data, remove values ​​from the aeronautical navigation data, add an identifier for an object to the aeronautical navigation data, or change the encoding of the aeronautical navigation data.

Images