Patent Description:
Various types of communication systems can be used by autonomous, semi-autonomous, and human-controlled aerial vehicles, and/or by ground-based or other non-aerial systems that communicate with aerial vehicles. In some cases, a UAS may have to communicate with manned aerial vehicles, related legacy support system entities (e.g., a manned air-traffic controller station), other UASs, and/or wholly or partially computer-automated air traffic control systems.

<CIT> discloses a system and method for the adaptive control of VHF communications in aircraft. An adaptive communications system for an aircraft has a communications processor that accesses a communications switching model to select a preferred ground communications station. A method of communication between an aircraft and a ground station includes receiving a communications switching model and determining a flight parameter for the aircraft as the aircraft navigates along a flight route and selecting a ground station based upon the determined flight parameter. The aircraft then communicates with the selected ground station. A method for compiling a communications switching model includes receiving signals from a ground station and measuring a signal strength. A preferred ground station is selected based upon the measured signal strength value.

<CIT> discloses an aviation facility nominating device for an aircraft which includes a position receiving component that receives position data indicating a position of the aircraft, an aviation data receiving component that receives aviation data associated with a plurality of aviation facilities, a facility selecting component for selecting aviation data for a selected plurality of the aviation facilities based on a position of the aircraft and a nominating component that nominates at least one but not all of the selected plurality of aviation facilities as a nominated aviation facility likely to be of interest to a pilot based on the position of the aircraft. In another embodiment, an aviation signal nominating device includes a position receiving component that receives position data indicating a position of the aircraft, an aviation signal receiving component that receives a plurality of aviation signals associated with an aviation facility, each aviation signal having a prescribed frequency, and a nominating component that nominates at least one but not all of the plurality of aviation signals as a nominated aviation signal likely to be of interest to a pilot based on the position of the aircraft.

Techniques and apparatus are provided for aviation communications. When an aircraft travels from point to point, the aircraft can be in communication with a number of different entities, including air traffic control entities that guide the aircraft while taking off, landing, and in flight, and ground control entities that guide the aircraft on land, such as while taxing to or from a runway. The aircraft can determine these communications based on an airspace related to the aircraft. The airspace can be divided into different classifications, such as classifications associated with airports, classifications associated with uncontrolled flight, and other classifications. The aircraft can determine an airspace classification based on position data. Then, the aircraft can use the airspace classification to select a communication repository that store data for generating communications based on the airspace classification and then generate communications with another entity, such as an air traffic control entity, another aircraft, or a ground control entity, using the selected communication repository.

The matter for protection is defined in appended independent claims <NUM>, <NUM> and <NUM>, with optional features defined in the dependent claims appended thereto. In the description, a method is provided. A computing device receives position data indicating a position of an aerial vehicle, where the position includes an altitude. A first airspace classification at the position of the aerial vehicle is determined from a plurality of possible airspace classifications. Each airspace classification specifies one or more communication parameters for communication within an associated airspace. The computing device selects a first communication repository that is associated with the first airspace classification from a plurality of communication repositories. Each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification. The computing device generates a communication related to the aerial vehicle using the first communication repository. The generated communication is sent to at least one recipient.

In the description, a computing device is provided. The computing device includes one or more processors; and data storage including at least computer-executable instructions stored thereon that, when executed by the one or more processors, cause the computing device to perform functions. The functions include: receiving position data indicating a position of an aerial vehicle, where the position includes an altitude; determining, from a plurality of possible airspace classifications, a first airspace classification at the position of the aerial vehicle, where each airspace classification specifies one or more communication parameters for communication within an associated airspace; selecting, from a plurality of communication repositories, a first communication repository that is associated with the first airspace classification, where each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification; generating a communication related to the aerial vehicle using the first communication repository; and sending the generated communication to at least one recipient.

In the description, a non-transitory computer readable medium is provided. The non-transitory computer readable medium has stored thereon instructions, that when executed by one or more processors of a computing device, cause the computing device to perform functions. The functions include: receiving position data indicating a position of an aerial vehicle, where the position includes an altitude; determining, from a plurality of possible airspace classifications, a first airspace classification at the position of the aerial vehicle, where each airspace classification specifies one or more communication parameters for communication within an associated airspace; selecting, from a plurality of communication repositories, a first communication repository that is associated with the first airspace classification, where each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification; generating a communication related to the aerial vehicle using the first communication repository; and sending the generated communication to at least one recipient.

In the description, a computing device is provided. The computing device includes: means for receiving position data indicating a position of an aerial vehicle, where the position includes an altitude; means for determining, from a plurality of possible airspace classifications, a first airspace classification at the position of the aerial vehicle, where each airspace classification specifies one or more communication parameters for communication within an associated airspace; means for selecting, from a plurality of communication repositories, a first communication repository that is associated with the first airspace classification, where each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification; means for generating a communication related to the aerial vehicle using the first communication repository; and means for sending the generated communication to at least one recipient.

In the description, a system is provided: The system includes an aerial vehicle and a computing device. The aerial vehicle computing device is configured to perform aerial-vehicle functions. The aerial-vehicle functions include: sending position data indicating a position of the aerial vehicle, where the position includes an altitude. The computing device includes one or more processors and data storage including at least computer-executable instructions stored thereon that, when executed by the one or more processors, cause the computing device to perform computing-device functions. The computing-device functions include: receiving the position data indicating the position of the aerial vehicle, where the position includes the altitude; determining, from a plurality of possible airspace classifications, a first airspace classification at the position of the aerial vehicle, where each airspace classification specifies one or more communication parameters for communication within an associated airspace; selecting, from a plurality of communication repositories, a first communication repository that is associated with the first airspace classification, where each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification; generating a
communication related to the aerial vehicle using the first communication repository; and sending the generated communication to at least one recipient.

In addition to the illustrative examples and features described above, further examples and features will become apparent by reference to the figures and the following detailed description and the accompanying drawings.

Disclosed herein are apparatus and techniques related to providing autonomous communications between aerial vehicles and air traffic control systems.

In many areas, including the United States, many three-dimensional airspaces are defined. Flight and/or communication parameters for these airspaces can be based on a number of pre-defined airspace classes, which can specify how an airspace can be used by commercial, governmental, and/or private aircraft, among other possibilities. For example, the United States identifies different types of airspace using six airspace classifications - classes A, B, C, D, E, and G. Each position in the airspace above the United States can be classified as being in one of these airspace classifications.

As a more specific example, classes B, C, and D are associated with airspaces surrounding controlled airports, and so these classes include communications related to various air traffic control entities, such as control towers, ground control for taxiing, departure control related to post-takeoff flight, and approach control related to pre-landing flight, that are not utilized in other airspaces. In contrast, airports in class G airspaces generally do not have control towers, and communications related to takeoffs and landings are broadcast to all nearby aerial vehicles rather than being directed to a control tower or other air traffic control (ATC) entity. As another example, class A airspace includes much of the airspace between <NUM>,<NUM> and <NUM>,<NUM> feet above the United States, which can be traversed using "jet routes" or pre-determined paths through class A airspace that act as highways in the sky - these jet routes are typically not used in other airspace classifications.

In example embodiments, a UAS and/or an automated air traffic control system can send and receive communications, including but not limited to voice communications, with other aerial vehicles, air traffic control entities, and perhaps other recipients. A computing device associated with the UAS or automated air traffic control system can recognize and generate these communications using speech generation and/or recognition software executing on the computing device.

In example embodiments, different communication repositories may be defined for different airspace classifications. As such, automated systems for communications with aerial vehicles can determine the particular airspace classification at an aerial vehicle's current position (e.g., current GPS coordinates and altitude), and use the communication repository for the particular airspace classification to generate communications and/or determine flight parameters for the aircraft.

For example, a class A communication repository can store language segments such as words, phrases, and/or templates related to flight communications related to a class A airspace. Similarly, class B, C, D, E, and G communication repositories can store words, phrases, and/or templates related to flight communications related to respective class B, class C, class D, class E, and class G airspaces. In some examples, a common repository can be used to store words, phrases, and/or templates, related to terminology used in multiple or all airspaces; e.g., store information about words, phrases, and/or templates, related to numbers, directions, military alphabet terminology, aircraft identifiers, etc. that can be communicated while in multiple or all airspaces.

It should be understood that "communication parameters," indicated by airspace classifications, specify how a communication in an associated airspace should be conducted. For example, communication parameters can define the types of entities to which an aircraft should send messages (e.g., to air traffic controllers or directly to other aerial vehicles), the communication protocols for encoding communications, etc. Communication parameters differ from "communication components," which are specified by a communication repository. Communication components are the building blocks that are used to form the substance of communications. In other words, communication parameters are provided by an airspace classification and specify how a message should be communicated in the airspace, while the communication components in an associated repository provide the content that makes up the substance of communications in an associated airspace.

In example embodiments, to determine which communication repository to use, an aerial vehicle or other device can determine a position associated with the aerial vehicle. The position can be determined in a three-dimensional (3D) coordinate system, such as a position specified in terms of latitude, longitude, and altitude, or in a two-dimensional (2D) coordinate system, such as a position specified in terms of latitude, longitude. Locations can be specified in terms of other 2D and/or 3D coordinate systems as well. The position associated with the aerial vehicle can be specified in position data that can include 2D and/or 3D coordinate data, including, but not limited to, data about latitude, longitude, and/or altitude.

Then, an airspace classification can be determined based on the position of the aerial vehicle, and one or more communication repositories can be selected based on the airspace classification. For example, if the aerial vehicle is flying <NUM>,<NUM> feet above O'Hare Intemational Airport in Chicago, IL, the aerial vehicle is flying in class B airspace. To generate and/or recognize communications for the aerial vehicle, the position of the aerial vehicle - <NUM>,<NUM> feet above O'Hare - can determine an airspace classification - class B - for the aerial vehicle, and one or more communication repositories can be selected based on the airspace classification; e.g., a communication repository storing communication components related to communications with an aerial vehicles in class B airspaces, and perhaps a common communication repository storing communication components related to communications associated with multiple airspaces. Then, the selected one or more communication repositories can be used to generate and/or recognize communications while the aerial vehicle is in the class B airspace.

Storing communications based on airspace classifications can simplify speech generation and/or recognition. For example, once communication repositories of communications data are selected based on airspace classification, then the universe of possible communications data to generate and/or recognize has been limited from a universal set of communications data covering multiple topics of communication to a set of flight-related communications data tailored to an airspace environment of an aerial vehicle, as represented by the selected communication repositories of communications data. As the set of communications data represented by the selected communication repositories of communications data is smaller than the universal set of communications data, simplify speech generation and/or recognition using the selected communication repositories is simplified. This simplified speech generation and/or recognition can be faster and more accurate than speech generation and/or recognition relying on the universal set of communications data. And, faster and more accurate speech generation and/or recognition can enhance aerial vehicle safety and efficiency.

<FIG> includes diagram <NUM> illustrating airspace classifications in an environment, according to an example embodiment. In many countries, including the United States, navigable airspace is divided based on airspace classifications. Diagram <NUM> shows an example division of a navigable airspace into airspace classifications that include class A airspace, class B airspace, class C airspace, class D airspace, class E airspace, and class G airspace.

An upper portion of diagram <NUM> indicates that class A airspace is a portion of the navigable airspace between <NUM>,<NUM> feet above mean sea level (MSL) and Flight Level Six Hundred, or <NUM>,<NUM> feet as indicated by an altimeter set to a standard barometric pressure; e.g., <NUM> inches of mercury. Diagram <NUM> illustrates class B airspace surrounds and includes controlled airport <NUM>, where class B airspace has an upside-down ziggurat shape centered on controlled airport <NUM> that extends up to <NUM>,<NUM> above mean sea level. In other examples, class B airspace can be associated with one or more large, busy, and/or important controlled airports; e.g., Chicago-O'Hare International Airport in Chicago, IL.

Diagram <NUM> illustrates class C airspace surrounding and including controlled airport <NUM>, where class C airspace has a T-shape centered on controlled airport <NUM> that extends up to <NUM>,<NUM> above mean sea level. In other examples, class C airspace can be associated with one or more controlled airports that are smaller, less busy, and/or less important than airports associated with class B airspace; e.g., Chicago Midway International Airport in Chicago, IL. Diagram <NUM> illustrates class D airspace surrounding and including controlled airport <NUM>, where class D airspace has a rectangular shape centered on controlled airport <NUM> that extends up to <NUM>,<NUM> above mean sea level. In other examples, class D airspace can be associated with one or more controlled airports that are smaller, less busy, and/or less important than airports associated with class C airspace; e.g., Chicago/Aurora Municipal Airport in Sugar Grove, IL.

Diagram <NUM> illustrates class G airspace ranging from ground level (GL), indicated by the bottom of diagram <NUM> to altitudes ranging between <NUM> feet above ground level (AGL), <NUM> feet AGL, and <NUM>,<NUM> feet above mean sea level. A size of an airspace, such as class G airspace, can vary based on different conditions, such as weather, visibility, proximity to airports, etc. Diagram <NUM> illustrates that class E airspace includes any portion of navigable airspace not otherwise classified; e.g., class E is the default airspace classification. In some examples, class E airspace can extend above class A airspace; i.e., airspace above Flight Level Six Hundred. Other divisions of navigable airspaces into airspace classifications are possible as well.

Note that airspace classification can depend on both location and altitude (i.e., on position). For example, a line through point <NUM> from Flight Level Six Hundred to ground level is shown as a dotted line in <FIG> This dotted line goes through, from top to bottom: class A airspace, class E airspace, class B airspace, class E airspace, and class G airspace. Thus, a location corresponding to point <NUM>, such as a location specified by latitude and longitude, can be classified as class A, class B, class E, or class G airspace depending on altitude.

In some examples, an airspace classification can be associated with one or more legally-defined airspace volumes. A legally-defined airspace volume can be a three-dimensional space specified by one or more local, regional, national, and/or international governments and/or governmental agencies. In some cases, non-governmental entities, such as industry associations and/or non-governmental organizations, can specify one or more legally-defined airspace volumes in accordance with existing law; e.g., a specification of airspace into one or more legally-defined airspace volumes can be proposed by a non-governmental entity and the specification can be ratified by an appropriate governmental entity. In some other cases, a legally-defined airspace volume can be specified in terms of a two dimensional area; e.g., a volume of airspace can be as being above a specified airport, county, country, state, city, an area defined by international law, or even an area defined by some more temporary measure (e.g., a "disaster area" or "no-fly zone" as defined by one or more governments), or other area. The legally-defined airspace volume can have one or more legally-defined airspace boundaries; e.g., boundaries specifying one or more two dimensional areas and altitude-based boundaries of airspaces such as illustrated by diagram <NUM>.

<FIG> is a block diagram of aircraft <NUM>, according to an example embodiment. Aircraft <NUM> includes navigation sensors <NUM>, communication interface <NUM>, computing device <NUM>, and flight components <NUM>. Navigation sensors <NUM> can include avionics sensors, Global Positioning System (GPS) sensors including Wide Area Augmentation System (WAAS) GPS sensors, GLONASS devices, Very-High Frequency (VHF) Omnidirectional Range (VOR) radio navigation devices, compasses, and other devices suitable for aiding aircraft navigation. Communication interface <NUM> can include one or more: tunable radios suitable for aircraft communications, aviation radios, VHF radios, navigation (NAV) radios, communications (COM) radios, VOR radios, instrument landing system (ILS), and glide slope (GS) radios, transponders (e.g., a device that, upon reception of a radar or other input, produces a response, such as a response that includes a "squawk code" identifying aircraft <NUM>, altitude information, and perhaps other data associated with aircraft <NUM>), wireless communication interfaces, and wired communication interfaces. Flight components <NUM> include one or more components that enable aircraft <NUM> to enable and control its flight, including but not limited to, one or more aircraft engines, wings, winglets, ailerons, rudders, flaps, wheels, fuselages, jets, propellers, stabilizers, spoilers, elevators, and cockpits.

Computing device <NUM> includes one or more processors <NUM> and data storage <NUM>. Processor(s) <NUM> can be one or more computer processors such as computer processors <NUM> discussed herein in the context of <FIG>. Data storage <NUM> can include one or more computer-readable storage media, such as data storage <NUM> discussed herein in the context of <FIG>. As shown in <FIG>, data storage <NUM> can store one or more communication repositories 230a, 230b, 230c, and speech generation and/or recognition software <NUM>. In some examples, one or more of communication repositories 230a, 230b, 230c can be formatted as communication repository <NUM>, communication repository <NUM>, communication repository <NUM>, communication repository <NUM>, and/or communication repository <NUM> discussed herein in the context of <FIG>.

Speech generation and/or recognition software <NUM> can, when executed by processor(s) <NUM>, perform a set of functions. The set of functions can include: receiving position data from navigation sensors <NUM> or perhaps other sources, where the position data can indicate a location and altitude of aircraft <NUM> within an airspace that is classified according to a plurality of airspace classifications, where each airspace classification can be associated with one or more communication components for flight within the airspace; determining an airspace classification associated at least with an altitude of aircraft <NUM> indicated by the position data for the aerial vehicle; selecting a communication repository, such as communication repository 230a, of communication data from among communication repositories 230a, 230b, 230c based at least on the airspace classification, where at least communication repository 230a can provide pre-defined communication components for at least the first airspace classification; generating a communication related to aircraft <NUM> using the selected communication repository (e.g., communication repository 230a), and sending the communication related to aircraft <NUM> to at least one recipient via communications interface <NUM>.

The recipients of the communication can include an airspace-related entity. An airspace-related entity can be an entity associated with travel that is related to one or more airspaces; e.g., an entity involved with flight, flight control, and/or ground control in one or more airspaces. Some example airspace-related entities include, but not are not limited to, one or more: air traffic control entities associated with an airport classified as being in class B, C, D, or G airspace, one or more ground control entities associated with the airport, other air traffic control and/or ground entities associated with one or more airspace classifications, aircraft flying in or otherwise associated with one or more airspace classifications, other air traffic control entities, and other ground control entities. Then, the selected repository can be selected based on an airspace classification and the airspace-related entity; and, in some examples, the generated communication can include a communication to the airspace-related entity. A similar set of functions can include recognizing a received communication using the selected communication repository, which can include a received communication from an airspace-related entity such as discussed immediately above. Then, the generated communication can include a response to the received communication. The generated communication and/or the response can include a voice communication, a data communication, or a combination of voice and data communications.

<FIG> shows another block diagram of aircraft <NUM>, according to an example embodiment. <FIG> shows that aircraft <NUM> can include navigation sensors <NUM>, communication interface <NUM>, computing device <NUM>, and flight components <NUM>. Navigation sensors <NUM>, communication interface <NUM>, and flight components <NUM> can be as discussed herein in the context of <FIG>.

Computing device <NUM> includes one or more processors <NUM> and data storage <NUM>. Processor(s) <NUM> can be one or more computer processors such as computer processors <NUM> discussed herein in the context of <FIG>. Data storage <NUM> can include one or more computer-readable storage media, such as data storage <NUM> discussed herein in the context of <FIG>. As shown in <FIG>, data storage <NUM> can store a plurality of communication repositories <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and speech generation and/or recognition software <NUM>. In some examples, one or more of communication repositories <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can be formatted as communication repository <NUM>, communication repository <NUM>, communication repository <NUM>, communication repository <NUM>, and/or communication repository <NUM> discussed herein in the context of <FIG>. Speech generation and/or recognition software <NUM> can, when executed by processor(s) <NUM> can perform at least the set of functions discussed herein in the context of <FIG>.

Communication repositories <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can store one or more terms related to aviation communications in or otherwise related to a particular airspace classification; such as respective class A airspace, class B airspace, class C airspace, class D airspace, class D airspace, class E airspace, and class G airspace classifications. Communication repository <NUM> store one or more terms related to multiple / all airspace classifications; i.e., terms in communication repository <NUM> can be common to multiple / all airspaces. For example, communication repository <NUM> can include at least one of: a word associated with a geographic position, a word associated with a route, a word associated with a direction, a word associated with a unit of measure, a word associated with a number, and a word associated with a meteorological condition. In some examples, communication repositories 230a, 230b, 230c can store one or more terms related to aviation communications that are based on particular airspace classification(s) such as discussed herein in the context of communication repositories <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>.

In some embodiments, aircraft <NUM> can be configured with software and/or hardware that enables aircraft <NUM> to be operated as an unmanned aerial system; e.g., software and/or for automated and/or remotely-operated flight control. In still other embodiments, computing device <NUM> can be utilized outside of aircraft <NUM>; e. g speech generation and/or recognition software <NUM> can, when executed by processor(s) <NUM> can perform at least the set of functions, discussed herein in the context of <FIG> to generate and/or recognize aviation communications related to an air traffic control entity, a ground control entity, and/or one or more entities other than aircraft <NUM> that may participate in aviation communications. For example, speech generation and/or recognition software <NUM> can embody one or more communication parameters that specify how communications in one or more associated airspaces are to be conducted. In particular, speech generation and/or recognition software <NUM> can embody one or more communication parameters and/or rules to select one or more communication repositories based on a particular airspace classification; e.g., while generating and/or recognizing one or more communications in an airspace associated with the particular airspace classification.

<FIG> depicts data network <NUM> with aircraft communications server <NUM> configured to communicate, via network <NUM>, with aircraft <NUM>, <NUM>, air traffic control <NUM>, and ground control <NUM> in accordance with an example embodiment. Network <NUM> may correspond to a LAN, a wide area network (WAN), a corporate intranet, the public Internet, or any other type of network configured to provide a communications path between networked computing devices. Network <NUM> may also correspond to a combination of one or more LANs, WANs, corporate intranets, and/or the public Internet.

Although <FIG> only shows two aircraft, one air traffic control, one ground control and one aircraft communications server, data networks may serve tens, hundreds, or thousands of computing devices. Moreover, aircraft <NUM>, <NUM> (or any additional aircraft) can include one or more computing devices, such as computing device <NUM> described herein.

Aircraft communications server <NUM> can be configured to generate and/or recognize aircraft communications using at least some of the techniques described herein. In particular, aircraft communications server <NUM> can include one or more term depositories, such as discussed herein at least in the context of FIGS. 3A and 3B, to generate and/or recognize voice and perhaps data communications involving one or more aircraft such as aircraft <NUM>, <NUM>, air traffic control entities such as air traffic control <NUM>, ground control entity such as ground control <NUM>, and/or other entities involved in mechanized flight. In some embodiments, voice and perhaps data communications involving one or more aircraft can include compressed and/or uncompressed content and/or can include encrypted and/or unencrypted content. Other types of content are possible as well. Many other examples of server devices are possible as well.

<FIG> is a functional block diagram of computing device <NUM>, in accordance with an example embodiment. In particular, computing device <NUM> shown in <FIG> can be configured to perform at least one function related to one or more of: aircraft <NUM>, <NUM>, <NUM>, <NUM> navigation sensors <NUM>, communication interface <NUM>, computing device <NUM>, flight components <NUM>, processor(s) <NUM>, data storage <NUM>, communication repositories 230a, 230b, 230c, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, speech generation and/or recognition software <NUM>, networks <NUM>, <NUM>, aircraft communications server <NUM>, air traffic control <NUM>, ground control <NUM>, method <NUM>, scenarios <NUM>, <NUM>, and communication flows <NUM>, <NUM>.

Computing device <NUM> may include a user interface module <NUM>, a network-communication interface module <NUM>, one or more processors <NUM>, data storage <NUM>, and one or more sensors <NUM>, all of which may be linked together via a system bus, network, or other connection mechanism <NUM>.

User interface module <NUM> can be operable to send data to and/or receive data from external user input/output devices. For example, user interface module <NUM> can be configured to send and/or receive data to and/or from user input devices such as a keyboard, a keypad, a touch screen, a computer mouse, a track ball, a joystick, a camera, a voice recognition module, and/or other similar devices. User interface module <NUM> can also be configured to provide output to user display devices, such as one or more cathode ray tubes (CRT), liquid crystal displays, light emitting diodes (LEDs), displays using digital light processing (DLP) technology, printers, light bulbs, and/or other similar devices, either now known or later developed. User interface module <NUM> can also be configured to generate audible output(s), such as a speaker, speaker jack, audio output port, audio output device, earphones, and/or other similar devices.

Network-communications interface module <NUM> can include one or more wireless interfaces <NUM> and/or one or more wireline interfaces <NUM> that are configurable to communicate via a network. Wireless interfaces <NUM> can include one or more wireless transmitters, receivers, and/or transceivers, such as a Bluetooth transceiver, a Zigbee transceiver, a Wi-Fi transceiver, a WiMAX transceiver, and/or other similar type of wireless transceiver configurable to communicate via a wireless network. Wireline interfaces <NUM> can include one or more wireline transmitters, receivers, and/or transceivers, such as an Ethernet transceiver, a Universal Serial Bus (USB) transceiver, or similar transceiver configurable to communicate via a twisted pair wire, a coaxial cable, a fiber-optic link, or a similar physical connection to a wireline network. In some embodiments, network- communications interface module <NUM> can perform at least some of the functionality of communication interface <NUM> of aircraft <NUM> discussed herein in the context of at least <FIG>. For example, network-communications interface module <NUM> can include a tunable aviation radio configured for use in voice communications and/or a radar transponder for automatically reporting data, such as one or more altitude data and squawk codes related to an aircraft.

In some embodiments, network communications interface module <NUM> can be configured to provide reliable, secured, and/or authenticated communications. For each communication, information for ensuring reliable communications (i.e., guaranteed message delivery) can be provided, perhaps as part of a message header and/or footer (e.g., packet/message sequencing information, encapsulation header(s) and/or footer(s), size/time information, and transmission verification information such as CRC and/or parity check values). Communications can be made secure (e.g., be encoded or encrypted) and/or decrypted/decoded using one or more cryptographic protocols and/or algorithms, such as, but not limited to, DES, AES, RSA, Diffie-Hellman, and/or DSA. Other cryptographic protocols and/or algorithms can be used as well or in addition to those listed herein to secure (and then decrypt/decode) communications.

One or more processors <NUM> can be one or more computer processors, which can include one or more general purpose processors, and/or one or more special purpose processors (e.g., digital signal processors, graphics processing units, application specific integrated circuits, etc.). One or more processors <NUM> can be configured to execute computer-readable program instructions <NUM> that are contained in data storage <NUM> and/or other instructions as described herein.

Data storage <NUM> can include one or more computer-readable storage media that can be read and/or accessed by at least one of one or more processors <NUM>. The one or more computer-readable storage media can include volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with at least one of one or more processors <NUM>. In some embodiments, data storage <NUM> can be implemented using a single physical device (e.g., one optical, magnetic, organic or other memory or disc storage unit), while in other embodiments, data storage <NUM> can be implemented using two or more physical devices.

Data storage <NUM> can include computer-readable program instructions <NUM> and perhaps additional data. In some embodiments, data storage <NUM> can additionally include storage required to perform at least part of the herein-described methods, scenarios, and techniques and/or at least part of the functionality of the herein-described devices and networks. In some embodiments, data storage <NUM> can store one or more communication repositories and/or speech generation and/or recognition software such as discussed herein in the context of data storage <NUM> of <FIG>.

In some embodiments, computing device <NUM> can include one or more sensors <NUM>. Sensor(s) <NUM> can be configured to measure conditions in an environment of computing device <NUM> and provide data about that environment. For example, sensor(s) <NUM> can include one or more of: (i) an identification sensor to identify other objects and/or devices, such as, but not limited to, an RFID reader, proximity sensor, one-dimensional barcode reader, two-dimensional barcode (e.g., Quick Response (QR) code) reader, and a laser tracker, where the identification sensor(s) can be configured to read identifiers, such as RFID tags, barcodes, QR codes, and/or other devices and/or object configured to be read and provide at least identifying information; (ii) a location sensor to measure locations and/or movements of computing device <NUM>, such as, but not limited to, a gyroscope, an accelerometer, a Doppler sensor, a Global Positioning System (GPS) device, a sonar sensor, a radar device, a laser-displacement sensor, and a compass; (iii) an environmental sensor to obtain data indicative of an environment of computing device <NUM>, such as, but not limited to, an altimeter, an infrared sensor, an optical sensor, a light sensor, a camera, a biosensor, a capacitive sensor, a touch sensor, a temperature sensor, a wireless sensor, a radio sensor, a movement sensor, a microphone, a sound sensor, an ultrasound sensor, and/or a smoke sensor; and (iv) a force sensor to measure one or more forces (e.g., inertial forces and/or G-forces) acting about computing device <NUM>, such as, but not limited to one or more sensors that measure: forces in one or more dimensions, torque, ground force, friction, and/or a zero moment point (ZMP) sensor that identifies ZMPs and/or locations of the ZMPs. Many other examples of sensor(s) <NUM> are possible as well. In some embodiments, sensors <NUM> can include some or all of navigation sensors <NUM> discussed herein in the context of <FIG>.

<FIG> depicts a network <NUM> of computing clusters 409a, 409b, 409c arranged as a cloud-based server system in accordance with an example embodiment. Computing clusters 409a, 409b, 409c can be cloud-based devices that store program logic and/or data of cloud-based applications and/or services; e.g., perform at least one function related to one or more of: aircraft <NUM>, <NUM>, <NUM>, <NUM> navigation sensors <NUM>, communication interface <NUM>, computing device <NUM>, flight components <NUM>, processor(s) <NUM>, data storage <NUM>, communication repositories 230a, 230b, 230c, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, speech generation and/or recognition software <NUM>, networks <NUM>, <NUM>, aircraft communications server <NUM>, air traffic control <NUM>, ground control <NUM>, method <NUM>, scenarios <NUM>, <NUM>, and communication flows <NUM>, <NUM>.

In some embodiments, computing clusters 409a, 409b, 409c can be a single computing device residing in a single computing center. In other embodiments, computing clusters 409a, 409b, 409c can include multiple computing devices in a single computing center, or even multiple computing devices located in multiple computing centers located in diverse geographic locations. For example, <FIG> depicts each of computing clusters 409a, 409b, and 409c residing in different physical locations.

In some embodiments, data and services at computing clusters 409a, 409b, 409c can be encoded as computer readable information stored in non-transitory, tangible computer readable media (or computer readable storage media) and accessible by other computing devices. In some embodiments, computing clusters 409a, 409b, 409c can be stored on a single disk drive or other tangible storage media, or can be implemented on multiple disk drives or other tangible storage media located at one or more diverse geographic locations.

<FIG> depicts a cloud-based server system in accordance with an example embodiment. In <FIG>, functionality of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device can be distributed among computing clusters 409a, 409b, 409c. Computing cluster 409a can include one or more computing devices 400a, cluster storage arrays 410a, and cluster routers 411a connected by a local cluster network 412a. Similarly, computing cluster 409b can include one or more computing devices 400b, cluster storage arrays 410b, and cluster routers 411b connected by a local cluster network 412b. Likewise, computing cluster 409c can include one or more computing devices 400c, cluster storage arrays 410c, and cluster routers 411c connected by a local cluster network 412c.

In some embodiments, each of computing clusters 409a, 409b, and 409c can have an equal number of computing devices, an equal number of cluster storage arrays, and an equal number of cluster routers. In other embodiments, however, each computing cluster can have different numbers of computing devices, different numbers of cluster storage arrays, and different numbers of cluster routers. The number of computing devices, cluster storage arrays, and cluster routers in each computing cluster can depend on the computing task or tasks assigned to each computing cluster.

In computing cluster 409a, for example, computing devices 400a can be configured to perform various computing tasks of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device. In one embodiment, the various functionalities of a an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device can be distributed among one or more of computing devices 400a, 400b, 400c. Computing devices 400b and 400c in respective computing clusters 409b and 409c can be configured similarly to computing devices 400a in computing cluster 409a. On the other hand, in some embodiments, computing devices 400a, 400b, and 400c can be configured to perform different functions.

In some embodiments, computing tasks and stored data associated with an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device be distributed across computing devices 400a, 400b, and 400c based at least in part on the processing requirements of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device, the processing capabilities of computing devices 400a, 400b, 400c, the latency of the network links between the computing devices in each computing cluster and between the computing clusters themselves, and/or other factors that can contribute to the cost, speed, fault-tolerance, resiliency, efficiency, and/or other design goals of the overall system architecture.

Cluster storage arrays 410a, 410b, 410c of computing clusters 409a, 409b, 409c can be data storage arrays that include disk array controllers configured to manage read and write access to groups of hard disk drives. The disk array controllers, alone or in conjunction with their respective computing devices, can also be configured to manage backup or redundant copies of the data stored in the cluster storage arrays to protect against disk drive or other cluster storage array failures and/or network failures that prevent one or more computing devices from accessing one or more cluster storage arrays.

Similar to the manner in which the functions of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device can be distributed across computing devices 400a, 400b, 400c of computing clusters 409a, 409b, 409c, various active portions and/or backup portions of these components can be distributed across cluster storage arrays 410a, 410b, 410c. For example, some cluster storage arrays can be configured to store one portion of the data of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device, while other cluster storage arrays can store other portion(s) of data of an aircraft, a network, an aircraft communications server, an air traffic control, a ground control, and/or a computing device. Additionally, some cluster storage arrays can be configured to store backup versions of data stored in other cluster storage arrays.

Cluster routers 411a, 411b, 411c in computing clusters 409a, 409b, 409c can include networking equipment configured to provide internal and external communications for the computing clusters. For example, cluster routers 411a in computing cluster 409a can include one or more internet switching and routing devices configured to provide (i) local area network communications between computing devices 400a and cluster storage arrays 410a via local cluster network 412a, and (ii) wide area network communications between computing cluster 409a and computing clusters 409b and 409c via wide area network connection 413a to network <NUM>. Cluster routers 411b and 411c can include network equipment similar to cluster routers 411a, and cluster routers 411b and 411c can perform similar networking functions for computing clusters 409b and 409b that cluster routers 411a perform for computing cluster 409a.

In some embodiments, the configuration of cluster routers 411a, 411b, 411c can be based at least in part on the data communication requirements of the computing devices and cluster storage arrays, the data communications capabilities of the network equipment in cluster routers 411a, 411b, 411c, the latency and throughput of local networks 412a, 412b, 412c, the latency, throughput, and cost of wide area network links 413a, 413b, 413c, and/or other factors that can contribute to the cost, speed, fault-tolerance, resiliency, efficiency and/or other design criteria of the moderation system architecture.

<FIG> is a flowchart of method <NUM>, in accordance with an example embodiment. Method <NUM> can be executed by a computing device, such as computing device <NUM>.

Method <NUM> begins at block <NUM>, where the computing device can receive position data indicating a position of an aerial vehicle, where the position includes, e.g., location and altitude, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>. In some embodiments, the aerial vehicle can be configured as an autonomous aerial vehicle.

At block <NUM>, a first airspace classification at the position of the aerial vehicle of a plurality of airspace classifications can be determined, where each airspace classification can specify one or more communication parameters for communication within an associated airspace, such as discussed herein at least in the context of <FIG> and <FIG>. In some embodiments, the first airspace classification can be associated with one or more legally-defined airspace volumes, such as discussed herein at least in the context of <FIG>.

At block <NUM>, the computing device can select, from a plurality of communication repositories, a first communication repository that is associated with the first airspace classification, where each communication repository can specify a set of pre-defined communication components for at least one associated airspace classification, such as discussed herein at least in the context of <FIG>, <FIG>, and <FIG>. In some embodiments, the set of pre-defined communication components specified by the first communication repository can include one or more language segments, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>.

In other embodiments, the first airspace classification can be further associated with an airspace-related entity. Then, selecting the first communication repository can include selecting a communication repository from among the plurality of communication repositories based on the particular airspace classification and the airspace-related entity, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>.

In still other embodiments, the plurality of communication repositories can further include a common communication repository that stores one or more words associated with each of the plurality of airspace classifications, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>. In particular of these embodiments, the common communication repository can store at least one of: a word associated with a geographic position, a word associated with a route, a word associated with a direction, a word associated with a unit of measure, a word associated with a number, and a word associated with a meteorological condition, such as discussed herein at least in the context of <FIG>.

At block <NUM>, the computing device can generate a communication related to the aerial vehicle using the first communication repository, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>. In some embodiments, the first airspace classification can be further associated with an airspace-related entity. Then, generating the communication related to the aerial vehicle can include generating a communication related to the aerial vehicle that is also associated with the airspace-related entity, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>. In particular of these embodiments, generating the communication related to the aerial vehicle that is also associated with the airspace-related entity can include: receiving a received communication from the airspace-related entity at the computing device; and generating a response communication to the received communication using the first communication repository, such as discussed herein at least in the context of <FIG>. In other embodiments, generating the communication related to the aerial vehicle using the first communication repository can include generating a voice communication, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>.

At block <NUM>, the generated communication can be sent to at least one recipient, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>. For example, the computing device can send the communication related to the aerial vehicle to at least one recipient. In some embodiments, the first airspace classification can be further associated with an airspace-related entity. Then, the at least one recipient can include the airspace-related entity, such as discussed herein at least in the context of <FIG>, <FIG> and <FIG>.

In some embodiments, method <NUM> can further include: after sending the communication related to the aerial vehicle, receiving a voice response communication at the computing device; and recognizing the voice response communication based on the first communication repository, such as discussed herein at least in the context of <FIG>. In particular of these embodiments, receiving the voice response communication can include receiving the voice response communication from the at least one recipient, such as discussed herein at least in the context of <FIG>.

In a variation on method <NUM>, the computing system may initially receive position data indicating a future position of an aerial vehicle (e.g., a position where the aerial vehicle is expected to be at some time in the future). The computing system may then determine the airspace classification of the airspace in which the future position is located, and carry out the blocks <NUM> to <NUM> according to the future position of the aerial vehicle (instead of the current position).

<FIG> shows flight diagram <NUM> and flight plan <NUM> related to scenario <NUM>, in accordance with an example embodiment. During scenario <NUM>, aircraft <NUM> takes off / departs from controlled airport <NUM>, which is named "City A Airport", flies along flight path <NUM>, and lands / arrives at uncontrolled airport <NUM> named "Town Airport" as shown in diagram <NUM>. Flight plan <NUM> summarizes the flight between airports <NUM> and <NUM> that occurs during scenario <NUM> by aircraft <NUM> and indicates the flight will follow visual flight rules (VFR).

Diagram <NUM> shows that airport <NUM> has a tower and ground control to control air and ground travel, respectively, associated with the airport, and is surrounded by class D airspace. Each of the tower and the ground control at airport <NUM> has separate radio frequencies for communications. Uncontrolled airport <NUM> is associated with a universal communications (UNICOM) radio frequency that is monitored at all times, but air and ground traffic are not controlled at airport <NUM>. Rather, aircraft flying in and around airport <NUM> follow procedures for airports without a control tower, such as expressed in Advisory Circulars <NUM>-42F and <NUM>-66A issued by the Federal Aviation Administration (FAA). Flight path <NUM>, which is between airports <NUM> and <NUM>, starts in the class D airspace surrounding airport <NUM> upon takeoff, proceeds into class E airspace, and travels into class G airspace while approaching and landing at airport <NUM>.

<FIG> is a flow diagram illustrating communication flow <NUM> corresponding to scenario <NUM>, in accordance with an example embodiment. During scenario <NUM> and in communication flow <NUM>, all communications are voice communications carried out by radio; in other scenarios and/or communication flows, some or all communications can be wireless data communications and/or wired communications.

Scenario <NUM> and communication flow <NUM> begin with aircraft <NUM> preparing for departure from airport <NUM>. A radio of communications interface <NUM> of aircraft <NUM> is initially tuned to a radio frequency associated with airport <NUM> ground control (GC). In scenario <NUM> and communication flow <NUM>, airport <NUM> ground control is a traffic control entity controlling ground transportation at airport <NUM>. In scenarios <NUM> and <NUM> and in communication flows <NUM> and <NUM>, many communications originated by an originating entity and intended for a terminating entity start with the name of the terminating entity, followed by the name of the originating entity, and then followed by any information to be conveyed in the communication. For example, a communication from aircraft <NUM> to airport <NUM>'s tower, which can be called "City A Tower" below, to request permission to take off can be presented herein as follows:
AIRCRAFT <NUM>: City A Tower, Aircraft <NUM>, Request permission to take off.

In scenario <NUM> and communication flow <NUM>, airport <NUM>'s tower is an air traffic control entity controlling the airspace that includes runways of airport <NUM>. Communication flow <NUM> continues with communications (Comms) <NUM> between aircraft <NUM> and airport <NUM> ground control, which can be called "City A Ground" below, for obtaining clearance to taxi to runway <NUM> of airport <NUM>, in preparation for taking off / departing from airport <NUM>. In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM> ground control:.

After communications <NUM> grant aircraft <NUM> permission to taxi via taxiway A to runway <NUM>, aircraft <NUM> can carry out the procedures of block <NUM> to tune the radio frequency for a radio of aircraft <NUM> to a radio frequency associated with airport <NUM>'s tower.

Communication flow <NUM> continues with communications <NUM> between aircraft <NUM> and airport <NUM>'s tower related to aircraft <NUM>'s take off / departure from airport <NUM> via runway <NUM>. In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM>'s tower:.

After communications <NUM> grant aircraft <NUM> permission to take off via runway <NUM>, aircraft <NUM> can carry out the procedures of block <NUM> to take off from airport <NUM> using runway <NUM> and begin flying toward airport <NUM>.

Communication flow <NUM> continues with communications <NUM> between aircraft <NUM> and airport <NUM>'s tower related to aircraft <NUM>'s flight toward airport <NUM>:.

After carrying out communications <NUM>, aircraft <NUM> can carry out the procedures of block <NUM> to fly to the edge of class D airspace controlled by airport <NUM>'s tower and carry out communications <NUM> regarding changing from class D controlled flight to visual flight rules (VFR) flight procedures in classes E and G airspaces. A "squawk" is a setting for a transponder to generate a squawk code that identifies aircraft <NUM> when radar service is available; e.g., airspaces in classes A, B, C, D, and perhaps E.

In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM>'s tower:.

Scenario <NUM> and communication flow <NUM> continue with aircraft <NUM> following the procedures of block <NUM> to continue on course and overfly landmark <NUM>. At that point, aircraft <NUM> begins to descend toward airport <NUM>, which can be called "Town Airport" below. In scenario <NUM> and communication flow <NUM>, airport <NUM> is an uncontrolled airport that monitors a UNICOM frequency. Also, aircraft <NUM> tunes the radio frequency for its radio to the UNICOM frequency associated with uncontrolled airport <NUM>.

When aircraft <NUM> is within radio contact with airport <NUM>, communication flow <NUM> continues with communications <NUM> between aircraft <NUM> and airport <NUM> related to aircraft <NUM>'s upcoming landing at airport <NUM>. First, aircraft <NUM> requests information about an active runway at airport <NUM> using the following portion of communications <NUM>:.

Then, aircraft <NUM> reports its progress toward landing using runway <NUM> at airport <NUM> to all traffic near airport <NUM> using the airport <NUM> UNICOM radio frequency as the following portion of communications <NUM>:
AIRCRAFT <NUM>: Town Airport Traffic, Aircraft two zero zero, Seven miles east, will overfly the field at one thousand two hundred feet for a left downwind entry to runway three two.

In scenario <NUM>, aircraft <NUM> proceeds to within one mile west of airport <NUM>, and in and communication flow <NUM>, communications <NUM> continue as follows:
AIRCRAFT <NUM>: Town Airport Traffic, Aircraft two zero zero, One mile west, to enter the left downwind entry to runway three two.

Scenario <NUM> continues with aircraft <NUM> coming within range of airport <NUM>'s radio. In communication flow <NUM>, aircraft <NUM> communicates its status to all traffic near airport <NUM> using the airport <NUM> UNICOM radio frequency as communications <NUM> as follows:
AIRCRAFT <NUM>: Town Airport Traffic, Aircraft four one four, Seven miles east, continuing at four thousand feet.

Scenario <NUM> continues with aircraft <NUM> landing at active runway <NUM> of airport <NUM> and communication flow <NUM> continues with communications <NUM> continuing between aircraft <NUM> and all traffic near airport <NUM> as follows:.

In communication flow <NUM>, aircraft <NUM> can generate and/or recognize communications <NUM>, <NUM>, and <NUM> using communications data using class D communication repository <NUM> and common communication repository <NUM>, as communications <NUM>, <NUM>, and <NUM> take place in the class D airspace surrounding airport <NUM>. Also, aircraft <NUM> can generate and/or recognize communications <NUM> and <NUM> using communications data using class E communication repository <NUM> and common communication repository <NUM>, as communications <NUM>, <NUM>, and <NUM> take place in class E airspaces. Further, aircraft <NUM> can generate and/or recognize communications <NUM> using communications data using class G communication repository <NUM> and common communication repository <NUM>, as communications <NUM> take place in a class G airspace surrounding airport <NUM>.

In some embodiments, aircraft <NUM> can recognize communications <NUM> using class G communication repository <NUM> and common communication repository <NUM>, as aircraft <NUM> in in a class G airspace when receiving communications <NUM> from aircraft <NUM>, even though communications <NUM> are originated by aircraft <NUM> that is in a class E airspace. In still other embodiments, aircraft <NUM> can recognize communications <NUM> using class E communication repository <NUM>, class G communication repository <NUM>, and common communication repository <NUM>, as communications <NUM> are originated by aircraft <NUM> in class E airspace and received by aircraft <NUM> while aircraft <NUM> is in class G airspace.

For example, at the beginning of scenario <NUM> and communication flow <NUM>, aircraft <NUM> can receive position data from navigational sensors <NUM> and perhaps other devices and determine an airspace classification associated with a current location of aircraft <NUM>; e.g., a location at airport <NUM> that is associated with a class D airspace. Then, speech generation and/or recognition software <NUM> of aircraft <NUM> can select class D communication repository <NUM> and common communication repository <NUM> based on the determination that aircraft <NUM> is at a position associated with class D airspace. Speech generation and/or recognition software <NUM> of aircraft <NUM> can then use communication data stored in class D communication repository <NUM> and common communication repository <NUM> to generate and/or recognize some or all of communications <NUM> with airport <NUM> ground control. Similar techniques used to generate communications <NUM> can be used to generate and/or recognize some or all of communications <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of scenario <NUM> and communication flow <NUM>.

In other scenarios and/or communication flows, speech generation and/or recognition software <NUM> and/or communication repositories 230a-230c, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can be executed and stored on one or more computing devices not located in aircraft <NUM>. Then, aircraft <NUM> can provide position data and perhaps other information to the one or more computing devices executing speech generation and/or recognition software <NUM>, speech generation and/or recognition software <NUM> of aircraft <NUM> can generate and/or recognize at least some of communications of scenario <NUM> and communication flow <NUM>, and then communicate information about the generated and/or recognized communications to aircraft <NUM>.

After completing communications <NUM>, aircraft <NUM> can taxi from active runway <NUM> to a hangar at airport <NUM> and shut down. After aircraft <NUM> shuts down, scenario <NUM> and communication flow <NUM> can be completed.

<FIG> shows flight diagram <NUM> and flight plan <NUM> related to scenario <NUM>, in accordance with an example embodiment. During scenario <NUM>, aircraft <NUM> takes off / departs from controlled airport <NUM> for Big City <NUM> in class B airspace, flies along flight path <NUM> in class B, E, A, and C airspaces, and lands / arrives at controlled airport <NUM> for Medium City <NUM> as shown in diagram <NUM>. Flight plan <NUM> summarizes the flight between airports <NUM> and <NUM> that occurs during scenario <NUM> by aircraft <NUM> and indicates the flight will follow instrument flight rules (IFR).

In scenario <NUM>, Big City <NUM> and the surrounding airspace is in one airspace region controlled by a regional air traffic control entity termed "Big City Center", and Medium City <NUM> and the surrounding airspace is in a different airspace region controlled by a regional air traffic control entity termed "Medium City Center". Diagram <NUM> include a dashed vertical line indicating a dividing line between the airspace region controlled by Big City Center and the airspace region controlled by Medium City Center.

<FIG> and <FIG> are a flow diagram illustrating communication flow <NUM> related to scenario <NUM>, in accordance with an example embodiment. During scenario <NUM> and in communication flow <NUM>, all communications are voice communications carried out by radio; in other scenarios and/or communication flows, some or all communications can be wireless data and/or wired communications.

Scenario <NUM> and communication flow <NUM> begin with aircraft <NUM> preparing for departure from airport <NUM>. A radio of communications interface <NUM> of aircraft <NUM> is initially tuned to a radio frequency associated with airport <NUM>'s control tower, which can be called "Big City Tower" below. In scenario <NUM> and communication flow <NUM>, airport <NUM> tower is an air traffic control entity controlling the airspace that includes runways of airport <NUM>. Also, many communications of scenario <NUM> and communication flow <NUM> originated by an originating entity and intended for a terminating entity start with the name of the terminating entity, followed by the name of the originating entity, and then followed by any information to be conveyed in the communication, such as discussed above in the context of <FIG>.

Communication flow <NUM> continues with communications <NUM> between aircraft <NUM> and airport <NUM> tower for obtaining clearance to depart from airport <NUM>. In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM> tower:.

Scenario <NUM> and communication flow <NUM> continues with aircraft <NUM> getting automated weather information from Automated Terminal Information Service (ATIS) associated with Airport <NUM> as follows:
ATIS: Big City Airport automated airport information foxtrot, 2125Z, Winds <NUM> at <NUM>. Visibility <NUM> miles. Temperature <NUM>, dew point <NUM>. Altimeter <NUM>. Landing and departing runway <NUM>. All taxiways open. All aircraft read back short instruction. Caution: balloon festival <NUM> miles west of airport. Advise on initial contact you have information foxtrot.

Communications <NUM> between aircraft <NUM> and airport <NUM> tower continue as follows:.

Aircraft <NUM> can carry out the procedures of block <NUM> to tune the radio frequency for a radio of aircraft <NUM> to a radio frequency associated with ground control at airport <NUM>. Scenario <NUM> and communication flow <NUM> continue with communications <NUM> between aircraft <NUM> and airport <NUM> ground control for obtaining clearance to taxi to runway <NUM> of airport <NUM> in preparation for taking off / departing from airport <NUM>, where airport <NUM> ground control is a traffic control entity controlling ground transportation at airport <NUM> that can be called "Big City Ground" below.

In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM> ground control:.

After communications <NUM> grant aircraft <NUM> permission to taxi via taxiway B (Bravo) to runway <NUM>, aircraft <NUM> can carry out the procedures of block <NUM> to taxi to runway <NUM> via taxiway B and then tune the radio frequency for the radio of aircraft <NUM> to the radio frequency associated with airport <NUM>'s tower.

Communication flow <NUM> continues with communications <NUM> between aircraft <NUM> and airport <NUM>'s tower related to granting aircraft <NUM> clearance to and airplane <NUM>'s subsequent takeoff / departure from airport <NUM> via runway <NUM>. In communication flow <NUM>, communications <NUM> include the following communications between aircraft <NUM> and airport <NUM>'s tower:.

Communication flow <NUM> continues with aircraft <NUM> carrying out the procedures of block <NUM> to take off from airport <NUM> via runway <NUM>. Next, airport <NUM> tower and aircraft <NUM> carry out communications <NUM> related to switching air traffic control from airport <NUM> tower to Big City Departure. In scenario <NUM>, Big City Departure is an air traffic control entity controlling the airspace just outside of the runways of airport <NUM>.

Communications <NUM> can proceed as follows:.

Aircraft <NUM> can then carry out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to a radio frequency associated with Big City Departure.

Turning to <FIG>, after carrying out the procedures of block <NUM>, aircraft <NUM> can proceed along flight path <NUM> to class A airspace at flight level <NUM> (<NUM>,<NUM> feet at standard pressure), while carrying out following communications <NUM> with Big City Departure.

In scenario <NUM>, aircraft <NUM> reaches <NUM> feet and maintains that altitude until leaving class B airspace. In communication flow <NUM>, communications <NUM> continue as follows:.

In scenario <NUM>, aircraft <NUM> begins to climb to flight level <NUM>. Then, upon reaching an altitude of <NUM> feet, aircraft <NUM> reaches class A airspace and sets its altimeter to <NUM> inches of mercury, which is standard pressure for class A airspace. In communication flow <NUM>, communications <NUM> continue as follows:.

Aircraft <NUM> can carry out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to <NUM>, which is a radio frequency associated with Big City Center. After carrying out the procedures of block <NUM>, Aircraft <NUM> and Big City Center can carry out the following communications <NUM> while aircraft <NUM> proceeds along flight path <NUM>:.

When aircraft <NUM> nears the boundary of the airspace region controlled by Big City Center, communications <NUM> continue as follows:.

Aircraft <NUM> can then carry out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to <NUM>, which is a radio frequency associated with Medium City Center. After carrying out the procedures of block <NUM>, aircraft <NUM> can proceed along flight path <NUM> toward airport <NUM> and can carry out the following communications <NUM> with Medium City Center:.

Scenario <NUM> continues with aircraft <NUM> proceeding along flight path <NUM> toward airport <NUM>. Communication flow <NUM> continues with communications <NUM> as follows:.

Aircraft <NUM> can carry out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to <NUM>, which is a radio frequency associated with Medium City Approach. In scenario <NUM> and communication flow <NUM>, Medium City Approach is an air traffic control entity controlling the airspace just outside of the runways of airport <NUM>.

After carrying out the procedures of block <NUM>, aircraft <NUM> and Medium City Approach can carry out the following communications <NUM> while aircraft <NUM> proceeds along flight path <NUM> in preparation for landing at airport <NUM>, which can be called "Medium City Airport" below:.

In scenario <NUM>, aircraft <NUM> turns left to <NUM> degrees and descends to <NUM>,<NUM> feet while approaching airport <NUM> along flight path <NUM>. In communication flow <NUM>, communications <NUM> continue as follows:.

In scenario <NUM>, aircraft <NUM> turns left to <NUM> degrees and descends to <NUM>,<NUM> feet slowing to <NUM> knots (nautical miles per hour) while approaching airport <NUM> along flight path <NUM>. In communication flow <NUM>, communications <NUM> continue as follows:.

Aircraft <NUM> can then carry out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to <NUM>, which is a radio frequency associated with airport <NUM> tower, which can be called "Medium City Tower". In scenario <NUM> and communication flow <NUM>, airport <NUM> tower is an air traffic control entity controlling the airspace that includes runways of airport <NUM>.

After carrying out the procedures of block <NUM>, aircraft <NUM> and airport <NUM> tower can carry out the following communications <NUM> as aircraft <NUM> proceeds to land on runway <NUM> of airport <NUM>:.

Scenario <NUM> continues with aircraft <NUM> landing at airport <NUM> on runway <NUM> and then carrying out the procedures of block <NUM> to tune the radio frequency for the radio of aircraft <NUM> to a radio frequency associated with airport <NUM> ground control. In scenario <NUM> and communication flow <NUM>, airport <NUM> ground control is a traffic control entity controlling ground transportation at airport <NUM> that can be called "Medium City Ground". After the procedures of block <NUM> are completed, aircraft <NUM> and airport <NUM> ground control can carry out the following communications <NUM> while aircraft <NUM> proceeds to Hangar <NUM> at airport <NUM>:.

In communication flow <NUM>, aircraft <NUM> can generate and/or recognize communications <NUM>, <NUM>, <NUM>, and <NUM> using communications data using class B communication repository <NUM> and common communication repository <NUM>, as communications <NUM>, <NUM>, <NUM>, and <NUM> take place in a class B airspace surrounding airport <NUM>. Also, aircraft <NUM> can generate and/or recognize communications <NUM>, <NUM>, and <NUM> using communications data using class A communication repository <NUM> and/or class E communication repository <NUM> as well as common communication repository <NUM>, as communications <NUM>, <NUM>, and <NUM> take place in class A and class E airspaces. Further, aircraft <NUM> can generate and/or recognize communications <NUM>, <NUM>, and <NUM> using communications data using class C communication repository <NUM> and common communication repository <NUM>, as communications <NUM>, <NUM>, and <NUM> take place in a class C airspace surrounding airport <NUM>.

For example, at the beginning of scenario <NUM> and communication flow <NUM>, aircraft <NUM> can receive position data from navigational sensors <NUM> and perhaps other devices and determine an airspace classification associated with a current location of aircraft <NUM>; e.g., a location at airport <NUM> that is associated with a class B airspace. Then, speech generation and/or recognition software <NUM> of aircraft <NUM> can select class B communication repository <NUM> and common communication repository <NUM> based on the determination that aircraft <NUM> is at a position associated with class B airspace. Speech generation and/or recognition software <NUM> of aircraft <NUM> can then use communication data stored in class B communication repository <NUM> and common communication repository <NUM> to generate and/or recognize some or all of communications <NUM> with airport <NUM> tower. Similar techniques used to generate and/or recognize communications <NUM> can be used to generate and/or recognize some or all of communications <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of scenario <NUM> and communication flow <NUM>.

After completing communications <NUM>, aircraft <NUM> can taxi to Hangar <NUM> at airport <NUM> and shut down. After aircraft <NUM> shuts down, scenario <NUM> and communication flow <NUM> can be completed.

<FIG> illustrate communication repositories, according to example embodiments. A communication repository can be a data structure that enables storage, review, insertion, deletion, and/or modification of a collection of one or more pre-defined communication components and perhaps other data. In some embodiments, one or more databases can store one or more communication repositories. In particular, a communication repository can store pre-defined communication components for aviation-related communications.

Example communication components can include one or more terms. Some communication components can specify scope and relationships between terms. For example, communication components can specify how a term is to be used; e.g., for communication generation and/or for communication recognition, one or more airspace classifications associated with the term, related communication components and/or terms. As another example, a communication component can identify a particular term. Other communication components are possible as well.

A term can be a word, phrase, or template that is used in sending and/or receiving information; i.e., the term can be used in communications. A phrase can include two or more words. A template can include one or more pre-determined terms and/or later-determined terms, where the later-determined terms can be represented by one or more tags. That is, a tag can include a placeholder or other representation for the one or more later-determined terms. An example of a template follows:
"Turning <LorR> to heading <NumericHeading>",
where "<LorR>" is a tag representing a selection between the words "left" and "right", and where "<NumericHeading>" is a tag representing a selected number specifying a heading in degrees; e.g., a value between zero and <NUM>. In some examples, tags can be associated with one or more rules indicating which terms can be used to evaluate the tag; e.g., a rule such as "<LorR> = 'left' OR 'right'" that indicates a tag "<LorR>" can be evaluated to either a term "left" or "right". In particular of these embodiments, tags can refer to other tags - for example, a rule such as "<NumericHeading> = <0To99> OR <100to359> AND degrees " indicates that the "<NumericHeading>" tag can involve evaluation of either a "<0To99>" tag, or a "<100to359>" tag and the word "degrees", where the "<0To99>" tag can evaluate to one "spelled-out" number between <NUM> and <NUM> using "niner" for the number <NUM>; e.g., the "<0To99>" tag can evaluate to one of "zero" for <NUM>, " one" for <NUM>,. "niner" for <NUM>, "one zero" for <NUM>, "one one" for <NUM>,. "niner eight" for <NUM>, and "niner niner" for <NUM>. Also, the "<100to359>" tag can evaluate to one spelled-out word for a number between <NUM> and <NUM> - the maximum numerical flight heading - as "one hundred" for <NUM>, "one zero one" for <NUM>,. "one niner niner" for <NUM>, "two hundred" for <NUM>, "two zero one" for <NUM>,. "three five eight" for <NUM>, and "three five niner" for <NUM>. Then, in the specific example of a heading value of <NUM>, the "<NumericHeading>" tag can be evaluated for the heading value of <NUM> to generate an output of "two five zero degrees". Other terms, tags and rules are possible as well.

To generate a communications output or to recognize a communications input based on this template, the tags can be evaluated to have specific values and those values used to generate the output. Continuing this example, if the tag <LorR> evaluated to "left", and the tag <NumericHeading> evaluated to "<NUM>", then the resulting communication can be "turning left to heading two one three degrees", where the bold words "left" and "two one three degrees" are generated based on the evaluated tag values. Many other terms, including many other words, phrases, and templates are possible as well.

<FIG> shows communication repository <NUM> formatted to include term field <NUM>. That is, each row of communication repository <NUM> can represent one communication component, which in this example includes a term in term field <NUM>. A term in term field <NUM> can be a word such as "Word <NUM>" shown in <FIG>, a tag such as "Tag <NUM>" shown in <FIG>, a phrase such as "Phrase <NUM>" shown in <FIG>, or a template such as "Template <NUM>" shown in <FIG>.

In some examples, communication repository <NUM> can relate to aviation-related and perhaps other communications, such as communications involving human-piloted aircraft and/or UASs. For example, each of the words "one", "two", "three", "four", "five", "six", "seven", "eight", "niner", and "zero", can be a "spelled-out" number, which can be one or more words corresponding to a respective number <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. In this example, "niner" can be a word used in aviation communications corresponding to the number <NUM>. Example phrases related to aviation communications include "requesting clearance to take off", "cleared to take off", "requesting clearance to land", and "cleared to land", which are phrases related to departure / take off of an aircraft from an airport and related to landing / arrival of an airplane at an airport. In other examples, terms in communication repositories <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> can relate to other topics than aviation communications.

In some embodiments, a communication repository can include information about how terms in the communication repository can be used for automated communications. For example, in the case of automated voice/speech communications, the communication repository can store information about a term that indicates whether the term can be used for voice/speech recognition, whether the term can be used for voice/speech generation, and/or whether the term can be used for both voice/speech recognition and generation. Further, the communication repository can store other information about how terms in the communication repository can be used in communications as well.

<FIG> shows communication repository <NUM> formatted to include term field <NUM> and recognize / generate field (R/G) <NUM>. That is, each row of communication repository <NUM> can represent one communication component. In this example, the communication component includes a term in term field <NUM> and one communication component in recognize / generate field <NUM>. Term field <NUM> can specify a term related to aviation communications, such as term <NUM> discussed herein in the context of <FIG>. Recognize / generate field <NUM> can indicate whether a term can be used for recognition of aviation communications, generation of aviation communications, or both recognition and generation of aviation communications. For example, <FIG> shows that "Word <NUM>" can be used for "Recognition" of aviation communications, "Tag <NUM>" is not used for either recognition or generation of aviation communications, "Phrase <NUM>" can be used for "Generation" of aviation communications, and "Template <NUM>" can be used for "All" - that is, for both recognition and generation of aviation communications.

To recognize (or generate) communications, communication repository <NUM> can be queried for all terms that can be used for either "All" recognition and generation or for "Recognition" ("Generation") of aviation communications - selecting terms based on Recognize / generate field <NUM> can reduce a number of terms used in, and so simplify and speed recognition (generation) of aviation communications.

In some embodiments, a communication repository can include information about how terms relate with each other. For example, a term FL related to a flight level, which is a specification of vertical altitude expressed in hundreds of feet, can be associated with one or more terms NUMS related to numbers. In this example, the communication repository can store information about the relationship between the term FL related to a flight level and the terms NUMS related to numbers. Further, the communication repository can store other information about how terms relate with each other.

<FIG> shows communication repository <NUM> formatted to include term field <NUM> and related term field <NUM>. That is, each row of communication repository <NUM> can represent one communication component. In this example, the communication component includes a term in term field <NUM> and one communication component in related term field <NUM>. Term field <NUM> can specify a term related to aviation communications, such as term <NUM> discussed herein in the context of <FIG>.

Related term field <NUM> can be used to specify one or more terms that can be associated with the term specified in corresponding term field <NUM>. For example, suppose that "Word <NUM>" is a number; e.g., "four". Then, as the number "four" is not necessarily related to any other terms, a related term field <NUM> for "Word <NUM>" could be "None" as shown in <FIG>. As an example related to "Tag <NUM>", suppose that "Tag <NUM>" is the <LorR> tag mentioned above; then "Word <NUM>" shown as a related term to "Tag <NUM>" in <FIG>, can be the word "left" (or the word "right"). In some embodiments, related term field <NUM> can refer to multiple related terms; e.g., in this example of the <LorR> tag, suppose that "Word <NUM>" is "left" and "Word <NUM>" is "right"; then, a related term field for "Tag <NUM>" could include references to both "Word <NUM>" and "Word <NUM>".

As another example, suppose "Phrase <NUM>" is the group of words "requesting permission" and "Phrase <NUM>" is the group of words "to take off". Then, by relating Phrase <NUM> and Phrase <NUM>, a communication can be generated and/or recognized that includes the two groups of words "requesting permission to take off'. Also, suppose that "Template <NUM>" is "Climbing to <NumericAltitudeFt>", where a <NumericAltitudeFt> represents a numerical value for an altitude expressed in feet; e.g., "two thousand" for an altitude of two thousand feet, and "Tag <NUM>" shown in related term field <NUM> can refer to the <NumericAltitudeFt> tag. Many other examples of related terms are possible as well.

In some embodiments, a communication repository can include information about relationships between terms and airspace classifications. For example, a term FL related to a flight level can be a term often used in class A airspaces. In this example, the communication repository can store information indicating that term FL can be used when an aircraft is in class A airspace and/or otherwise be related to class A airspace. Further, the communication repository can store other information about relationships between terms and airspace classifications.

<FIG> shows communication repository <NUM> formatted to include term field <NUM> and classes field <NUM>. That is, each row of communication repository <NUM> can represent one communication component. In this example, the communication component includes a term in term field <NUM> and one communication component in classes field <NUM>. Term field <NUM> can specify a term related to aviation communications, such as term <NUM> discussed herein in the context of <FIG>. Classes field <NUM> can specify one or more airspace classifications related to a term. For example, <FIG> shows an example that a word "Word <NUM>" is associated a "Common" airspace classification; that is, Word <NUM> is associated with all airspace classifications. For example, Word <NUM> can be a word related to: a number, the military alphabet (e.g., Alpha, Bravo, Charlie. Zulu), weather / meteorological conditions, routes, times, courses, headings, other types of airspaces (e.g., restricted, controlled), vectors, navigational and/or other flight-related equipment, distances, and units of measure. Many other words, tags, phrases, and templates are possible related to all airspace classifications are possible as well. <FIG> shows an example tag "Tag <NUM>" that is associated with class "B", "C", and "D" airspaces in communication repository <NUM>; for example, the tag "<ControlEntities>" associated with a rule of "Tower OR Control Tower OR Center OR Ground OR Ground Control OR ATC OR Approach OR Departure", which are names of air traffic and ground control entities controlling air and ground transportation in B, C, and D airspaces.

<FIG> shows a phrase "Phrase <NUM>" that is associated with class "A" airspace in communication repository <NUM>; e.g., "Phrase <NUM>" can be "standard pressure" which refers to the standard barometric pressure setting for an altimeter of <NUM> inches that is use for all altimeters in class A airspace. <FIG> also shows an example that a template "Template <NUM>" is associated with class "G" airspace. For instance, Template <NUM> can be a template such as "<AirportName> UNICOM", where <AirportName> is a tag representing a name of an airport, and where UNICOM represents a universal communication channel at an uncontrolled airport in class G airspace.

One communication repository can store multiple types of information about terms, including, but not limited to, information about how terms in the communication repository can be used for automated communications, information about how terms relate with each other, and information about relationships between terms and airspace classifications. In some embodiments, each term in the communication repository can have a unique identifier - then a term can be expressly identified by and referred to using the unique identifier.

<FIG> shows communication repository <NUM> formatted to include identifier (ID) field <NUM>, term field <NUM>, recognize / generate field (R/G) <NUM>, classes field <NUM>, and related term identifier field <NUM>. That is, each row of communication repository <NUM> can represent one communication component. In this example, the communication component includes a term in term field <NUM> and four communication components in term field <NUM>, recognize / generate field (R/G) <NUM>, classes field <NUM>, and related term identifier field <NUM>.

Identifier (ID) field <NUM> can be a numerical, alphanumerical, or other value specifying a communication component in communication repository <NUM>. For example, ID "<NUM>" can be used to uniquely identify a communication component for "Phrase <NUM>". Term field <NUM> can specify a term related to aviation communications, such as term <NUM> discussed herein in the context of <FIG>.

Recognition / generation field <NUM> can specify whether a term can be used for generation of aviation communications, recognition of aviation communications, both recognition and generation of aviation communications, or neither recognition nor generation of aviation communications, such as discussed herein in the context of <FIG>. Classes field <NUM> can specify one or more airspace classifications / classes associated with a term, such as discussed herein in the context of <FIG>. Related term identifier field <NUM> can specify one or more identifiers related to a term; for example, <FIG> shows that term identified with identifier "<NUM>", which is the "Tag <NUM>" term, is associated with a term whose identifier is "<NUM>". Relationships between terms are also discussed herein in the context of <FIG>. Other specifications for communication repositories than those illustrated by <FIG> are possible as well.

The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims.

The above detailed description describes various features and functions of the disclosed systems, devices, and methods with reference to the accompanying figures. In the figures, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, figures, and claims are not meant to be limiting. Other embodiments can be utilized, and other changes can be made, without departing from the spirit or scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.

With respect to any or all of the ladder diagrams, scenarios, and flow charts in the figures and as discussed herein, each block and/or communication may represent a processing of information and/or a transmission of information in accordance with example embodiments. Alternative embodiments are included within the scope of these example embodiments. In these alternative embodiments, for example, functions described as blocks, transmissions, communications, requests, responses, and/or messages may be executed out of order from that shown or discussed, including substantially concurrent or in reverse order, depending on the functionality involved. Further, more or fewer blocks and/or functions may be used with any of the ladder diagrams, scenarios, and flow charts discussed herein, and these ladder diagrams, scenarios, and flow charts may be combined with one another, in part or in whole.

A block that represents a processing of information may correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique. Alternatively or additionally, a block that represents a processing of information may correspond to a module, a segment, or a portion of program code (including related data). The program code may include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique. The program code and/or related data may be stored on any type of computer readable medium such as a storage device including a disk or hard drive or other storage medium.

The computer readable medium may also include non-transitory computer readable media such as non-transitory computer-readable media that stores data for short periods of time like register memory, processor cache, and random access memory (RAM). The computer readable media may also include non-transitory computer readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. A computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device.

Moreover, a block that represents one or more information transmissions may correspond to information transmissions between software and/or hardware modules in the same physical device. However, other information transmissions may be between software modules and/or hardware modules in different physical devices.

Claim 1:
A method, comprising:
receiving (<NUM>), by a computing device, position data indicating a position of an aerial vehicle (<NUM>), wherein the position comprises an altitude;
determining (<NUM>), from a plurality of possible airspace classifications, a first airspace classification at the position of the aerial vehicle, wherein each airspace classification specifies one or more communication parameters for communication within an associated airspace;
selecting (<NUM>), by the computing device, from a plurality of communication repositories (230a, 230b, 230c, <NUM>, ... , <NUM>, <NUM>, ...), a first communication repository that is associated with the first airspace classification, wherein each communication repository specifies a set of pre-defined communication components for at least one associated airspace classification;
generating (<NUM>), by the computing device, an automated voice communication (<NUM>, <NUM>, <NUM>) related to the aerial vehicle using one or more of the pre-defined communication components specified by the first communication repository; and
sending (<NUM>), based on the one or more communication parameters specified by the first airspace classification, the generated automated voice communication to at least one recipient.