This disclosure relates generally to urban air taxi and related air mobility vehicle position control and management, whether crewed or uncrewed, and more particularly to a method and system for monitoring and managing separation for multiple air taxis in a shared airspace.
Urban air mobility (UAM) generally refers to the operations of manned and unmanned vertical takeoff and landing (VTOL and eVTOL for electric) vehicles intended to operate in Class E and Class G airspace (as specified by Federal Aviation Administration airspace visual flight rules (VFR) regulations), respectively between 0 and 700 feet and 700to 1,200 feet above ground level (AGL) in metropolitan areas with or without designated airfields. Herein, such vehicles will be referred to as “air taxis” to distinguish them from conventional aircraft flying at higher altitudes and subject to established air traffic management controls and separation standards. Such an air taxi can include a relatively small unmanned delivery drone, as well as a relatively large piloted or unpiloted craft that transports large items and/or passengers.
Current safe spacing requirements for air taxis operating in Class E and G airspace are limited to visibility and cloud clearance standards. Increasingly unpredictable and crowded ground transportation options will lead to increased air taxi demand, correspondingly tighter spacing, and the need for new approaches to controlling air taxi separation. Industry planning documents such as NASA's UAM Vision Concept of Operations (ConOps) UAM Maturity Level (UML)4, acknowledge that UAM air traffic management (ATM) must enable safe, sustained, resilient, close-proximity, multi-vehicle operations in constrained urban environments, including off-nominal situations. Further, to deliver the same scalability and resilience expected from traditional air traffic management, UAM airspace operations will similarly need to have multiple layers of system redundancy, procedural specificity, and technical capability in the areas of communication, navigation, surveillance, and information that inform traditional ATM. However, with formal air traffic management presently only available at higher altitudes and based at local airports, it is expected that UAM air traffic management will need to be provided by third-party services. In other words, there is a need for a more specific and capable urban air taxi traffic system which may be operated by third parties.
At scale, UAM traffic management will depend on layering redundant systems and promoting contingency-based procedures to provide needed safety and efficiency. These will include designated landing and takeoff areas, dedicated routing, geofencing around secured locations (e.g., power stations), safe separation distances, detection and avoidance technology, and control intelligence and warning systems supporting manual intervention to manage traffic flow and avoid imminent collisions. However, these capabilities cannot ensure safety in metropolitan environments with limited visibility, poor weather conditions, inconsistent communication connectivity, nighttime operations, or high traffic density. Accordingly, more recent NASA industry guidance indicates that “ . . . much can undoubtedly be achieved through on-board technical improvements. There is an evolving consensus that for on-demand mobility to grow there must be a shift from prescriptive to performance-based guidelines.” (Understanding Risk in Urban Air Mobility: Moving Towards Safe Operating Standards, NASA/TM-20205000604, NASA Ames Research Center, Mary Connors, February 2020).
This disclosure provides a reliable and safe separation strategy for urban air taxis based on automatic and autonomous systems that can be implemented on board all air taxis, and which detects incursions, manages unsafe proximity, and establishes sympathetic (synchronized in time and coordinated in direction) routing. They system enables two or more air taxis to adjust their trajectories in a complementary fashion to avoid unsafe separation, while at the same time minimizing the risk of imposing too closely on other air taxis that may be nearby. This is distinct from conventional detection and avoidance (DAA) techniques which focus on relatively close proximity collision avoidance. Safe separation under existing visual flight rules for UAM vehicles occurs at thousands of feet apart, requiring greater situational awareness and the ability to adjust trajectories to maintain separation.
Disclosed is a system and method for autonomously determining, displaying (e.g., on a display device), and directing the target trajectories each air taxi should fly to regain or maintain safe separation from one or more air taxis in a shared airspace. In an embodiment, the system guides one or more air taxis to independently adjust trajectories to maintain or restore safe air taxi separation, and can do so without central guidance from air traffic control, or any form of communication among pilots to coordinate their respective maneuvers.
Also disclosed is a system and method for determining, displaying, and implementing how two or more air taxis in too close proximity can safely and autonomously maneuver to regain safe separation without the intervention of air traffic controllers, without any communication between the pilots of the air taxis, and without direct coordination or linkage between the systems onboard each air taxi. The disclosed system installed on multiple air taxis independently directs each to restore safe separation through complementary recovery actions completely autonomously. Resulting benefits include safer trips, reduced burden on pilots, and a clearer roadmap to air taxi separation at scale.
A system installed on all air taxis and promising to deliver autonomous safe separation of air taxis thousands of feet apart may satisfy three conditions to be effective: First, it must be able to detect air taxis in its relevant airspace and determine their position, trajectory and speed. Second, it must be able to independently direct each air taxi in such a way that they move mutually toward restoring separation. Finally, the movement toward separation needs to be contained so that the movement itself does not risk penetrating other air taxi airspace.
In an embodiment, two features enable the achievement of safe and autonomous separation: First, a system-generated initial reference formation airspace establishes a sphere or “bubble” of virtual surrounding air taxis based on a formation of a set of virtual air taxis positioned at the safe or regulatory minimum longitudinal, minimum lateral, and minimum vertical separation positions around the current position of a reference air taxi. For example, the spheres of 6 virtual air taxis arrayed evenly around the reference air taxi may be sufficient to represent possible surrounding traffic. The positioning of these virtual air taxis forms a set of spheres around the center reference air taxi. This is the baseline for defining safe separation and therefore for identifying penetration of this reference formation airspace.
The second feature is the application of centroid vectoring to establish a target separation vector to restore safe separation between air taxis. The centroid is the geometric balance point computed within any space, and may be an ideal target for establishing a vector toward separation. According to an embodiment, two air taxis, which have either penetrated their respective airspaces or are on a path that would result in airspace penetration, may be given target separation vectors to redirect them to the centroids of their respective penetrated airspaces. Thus directed, each of the air taxis will independently move in a way that restores safe separation for both air taxis, while also maintaining separation from the virtual air taxis on station around the original perimeter of each air taxis which act as proxies for any other air taxis that might be close or approaching to minimum separation distance.
The air taxi at the center of the reference formation airspace is referred to as the “reference air taxi,” and it occupies the centroid of its respective reference formation airspace. In physics and geometry, a centroid is the mean position within a particular space, and represents the geometric center of the space. As such, the properties of the centroid make it ideal as a guiding position: it is always at the geometric center of the reference formation airspace, however uniform or uneven; it is always inside the reference formation airspace; and the centroid can be calculated through a mathematical computation within the capability of onboard avionics equipment. In an embodiment for air taxis, the reference formation airspace forms a sphere, and the centroid is at the intersection of at least two diameters of the sphere, positioning it at the three-dimensional center of the sphere.
When incursion of an airspace occurs among two or more air taxis, the reference formation airspace of at least one air taxi is penetrated and thus deformed, causing each air taxi to no longer occupy the centroid position relative to its original formation airspace (because the formation airspace itself has been distorted by the penetration). In an embodiment, each air taxi equipped with the disclosed system is autonomously provided a target separation vector determined based on the new “penetration airspace” defined by the positions of the original surrounding virtual air taxis, plus the position of the penetrating air taxi. All of these positions are known: the virtual air taxis are known with precision based on their position relative to and moving in tandem with the reference air taxi, enabling the presence, distance, direction, and position of each virtual air taxi to be calculated precisely. The reference air taxi's sensors can also track a penetrating air taxi with precision using position data received by the air taxi's GPS system and/or other onboard DAA sensors, such as phased array radar and electro-optical systems. Each air taxi's autonomous separation unit (ASU) generates the dimensions of the penetrated airspace based on both virtual and penetrating air taxi positions. Based on these inputs, a new centroid is determined for each air taxi relative to its own now-penetrated airspace. With the new centroid located, each air taxi's ASU system generates a target separation vector to that position. Each air taxi's heading toward the centroid of its penetrated airspace represents an optimal separation solution with three essential features: (a) each air taxi's penetrated airspace is distinct; (b) each heading will always be away from the other penetrating air taxi, because their centroids are positions in different formations; and (c) the separation vector each air taxi follows will always be inward to its respective penetrated airspace, thus maintaining separation from any actual air taxis close to the air taxi's perimeter, as well as those represented by virtual air taxi positions.
Several features of this autonomous resolution of safe separation make it an appealing solution to the problem of maintaining safe separation among air taxis without requiring either pilot or human controller intervention:
Embodiments of the disclosed system have benefits for air taxi pilots and for air traffic controllers:
In an embodiment, disclosed is a method for managing air taxi flight separation of a plurality of air taxis in an urban flight region for safe separation or for compliance with a predetermined separation standard based on predetermined separation parameters or dimensions, the method comprising the steps of (1) receiving current position data for each of the air taxis within a target range from a reference air taxi, (2) constructing, for each of the identified air taxis in the air traffic information region, a reference formation airspace in the form of a sphere with dimensions based on the separation parameters, and with the centroid of the formation airspace as the current position of the air taxi, (3) comparing, for a first air taxi in the target range, the reference formation airspace of the first air taxi to the current position of a second air taxi in the target range, to determine if the second air taxi has penetrated the reference formation airspace of the first air taxi, and if the second air taxi has penetrated the reference formation airspace of the first air taxi: (a) constructing a penetration airspace of the first air taxi representing a modification of the reference formation airspace of the first air taxi deformed by the position data of the second air taxi, (b) determining a centroid of the penetration airspace of the first air taxi, and (c) generating a target separation vector defined by the direction from the current position of the first air taxi to the centroid of the penetration airspace of the first air taxi.
In an embodiment, the target separation vector is transmitted to the first air taxi and/or to an air traffic management operator control system associated with safe separation within the urban taxi operating environment.
In an embodiment, the steps of the method are continuously performed in real time for each of the air taxis in the region with respect to all the other air taxis in the flight information region.
In an embodiment, the reference formation airspace may be constructed by defining positions of 6 virtual air taxis spaced about the reference air taxi. Four of the virtual air taxis are located evenly around the reference air taxi on a horizontal plane, and the remaining two virtual air taxis are located above and below the reference air taxi. In alternative embodiments, the airspace may be defined by more or fewer virtual air taxis arranged about the periphery of the reference formation sphere. Further, the penetration airspace may be constructed based upon the set of virtual air taxis with the position of one of the air taxis closest to the penetrating air taxi modified to the position of the penetrating air taxi. In an alternative arrangement, the position of the penetrating air taxi may form an additional point for defining the penetration airspace.
In an embodiment, the method may include configuring a proximity risk trigger defined by a proximity distance, generating a proximity risk warning when another air taxi is within a predetermined proximity distance to the reference formation airspace of an air taxi, and sending the proximity risk warning to least one of the air taxis, the other penetrating air taxi or an urban air traffic management system associated with the flight region.
In an embodiment, disclosed is a method for managing air taxi flight separation of a reference air taxi during flight for compliance with a predetermined safe separation distance or standard, the method including the steps of receiving current position data of the reference air taxi, constructing a reference formation airspace in the form of a sphere with dimensions based upon minimum longitudinal, minimum lateral and minimum vertical separation parameters and the centroid of the formation airspace as the current position of the reference air taxi, defining positions of 6 virtual air taxis spaced about the reference air taxi. Four of the virtual air taxis are located evenly around the reference air taxi on a horizontal plane, and the remaining two virtual air taxis are located above and below the reference air taxi: (1) constructing a penetration airspace defined by the positions of the 6 virtual air taxis wherein the position of one of the virtual air taxis closest to the penetrating air taxi is modified to the position of the penetrating air taxi, (2) determining a centroid of the penetration airspace, (3) generating a target separation vector extending from the current position of the reference air taxi to the centroid of the penetration airspace, and (4) sending the target separation vector to the reference air taxi.
The steps of the method may be performed continuously in real time.
In an embodiment, if an approaching or penetrating air taxi is determined to be within a collision risk distance (for example, as a result of technical failure or pilot error), the method may hand off control to an onboard detection and avoidance system programmed to take emergency action.
In an embodiment, the target separation vector may be sent to an onboard autopilot system, or, if an autopilot system is not present or not engaged, the target separation vector may be displayed on a pilot display.
In an embodiment, the penetration airspace may be defined by the positions of multiple penetrating air taxis and the positions of the multiple virtual air taxis.
In an embodiment, disclosed is a method for managing air taxi flight separation of a reference air taxi during flight for compliance with a predetermined safe separation distance or standard, the method including the steps of receiving position data of the reference air taxi, constructing a reference formation airspace in the form of a sphere with dimensions based upon the minimum longitudinal, lateral and vertical separation parameters and the position of the reference air taxi as the centroid of the reference formation airspace, receiving position data of at least one other air taxi that is nearest to the reference formation airspace, and if the at least one other air taxi penetrates into the reference formation airspace: (1) constructing a penetration airspace representing a modification of the reference formation airspace deformed by at least the position data of the at least one other air taxi, (2) determining a centroid of the penetration airspace, and (3) sending to the reference air taxi a vector representing a direction to the centroid of the penetration airspace.
In an embodiment, the method may define a plurality of virtual positions spaced about the reference formation airspace, and wherein the penetration airspace is represented by the plurality of virtual positions and a penetrating air taxi position.
The disclosed embodiments may be understood from the following detailed description taken in conjunction with the accompanying drawings of which:
In
In
Turning to
By contrast, the present disclosure describes a technology enabling individual air taxis and similar UAM vehicles to create their own (autonomous) safe separation. As noted earlier, autonomous safe separation requires three conditions be met: (a) detecting when an air taxi has penetrated the airspace of a reference or center air taxi; (b) independently generating mutually compatible or “sympathetic” routings to restore safe separation; and (c) automatically containing the direction and range of separation restoral so that the potential for moving into the path of another air taxi is forestalled. With these conditions met, autonomous safe separation is a vehicle-borne air traffic management capability fully compatible with the airspace-based air traffic management.
Turning to
The ASU system in air taxi 704B calculates a new centroid based on its penetration airspace 703B, generating the new centroid position 704CENT among all points of the now-changed airspace. Similarly, air taxi 702B recalculates its own new centroid 702CENT based on the deformations imposed by air taxi 704B. The centroid 704CENT is located deeper into its penetrated airspace and further from its current position because the rest of the original perimeter of the airspace remains intact and serves to contain the continued movement away from the incursion. This functional action contains further separation by imposing virtual boundaries. This third and final capability establishes autonomous separation: penetration detection, sympathetic routing, and now, contained separation.
In an embodiment, a target separation vector may be “combined” with a current flight vector of an air taxi, to guide the air taxi towards the centroid as it continues its flight.
Any number of penetrations can be addressed, resulting only in the potential tightening of the airspace in which the centroid location is computed. Further, while the virtual air taxis are used to frame the reference formation airspace and typically at least a portion of a penetration airspace, these virtual air taxis are not real, and thus offer no risk of real danger even as the centroid draws closer. In fact, the framing virtual air taxis establish the closest location of potentially penetrating real air taxis and circumscribe the range of movement of air taxis as the restoration of safe separation is underway.
In step 901, operation of the ASU is initiated by ensuring the air taxi ID is entered, the transponder is set, GPS and/or sensor signals can be received, and that in an embodiment both broadcast and reception to and from ATC and other air taxis are enabled. In modern air taxis a flight management system is activated in step 902, and can be set to manual 903 or autopilot 904 operation of the air taxis. In step 905, the system is configured to establish the reference formation airspace that creates a sphere around the air taxi at the safe distance longitudinally, laterally, and vertically. In addition, in an embodiment, risk triggers 907 can be set to govern how far away a potentially-penetrating air taxis should be before being tracked by the system and considered a threat, and when the proximity of an air taxis is such that the separation system is suspended and the Detection and Avoidance (DAA) system 911, takes over.
Once airborne, in step 906 the ASU system monitors broadcast or sensor data from GPS and other air taxi data, and in step 907 assesses the degree to which any air taxi may pose a trigger-level risk. If the threat from an approaching air taxi is deemed a sufficient risk, in step 908 the system will generate a penetration airspace. In an embodiment, a set of virtual air taxis spaced about the perimeter of the penetration airspace may be defined, and virtual air taxis may be replaced or substituted with the data from the nearest-risk, real approaching air taxi(s). In step 909, the approaching air taxi is evaluated to determine if it has penetrated the reference formation airspace of the air taxis. If the approaching air taxi does not breach the separation distances, the system returns to monitoring for vicinity air taxis in step 906. On the other hand, in step 909, if separation is violated and the approaching air taxi has penetrated the reference formation airspace, then in step 910 the incoming distance is checked to see if it is so close and closing so quickly that the system automatically hands off to DAA in step 911. However, if in step 910 DAA is not triggered, the penetration data—for current and additional air taxis if any—is incorporated in step 912, and the updated penetration airspace is constructed in step 913. In step 914, the centroid of the penetration airspace is computed, and in step 915 the target separation vector is generated. In step 916, if in an embodiment the autopilot is engaged, then in step 918 the target separation vector is displayed and supplied to the autopilot system for the air taxi to navigate to the centroid along the target separation vector which will reestablish safe separation. If the autopilot is not engaged, then in step 917 the target separation vector information is displayed, possibly with an audible or visual indicator alerting the pilot to the penetration and the recommended target safe separation vector. Further, after the target separation vector is generated in step 915, the process returns to step 908 to continuously update the penetrated airspace until, in step 909, it determines that a separation violation no longer exists.
According to an embodiment, the Autonomous Separation Unit 1006 may be installed and interfaced with direct access to the flight management system 1001, in order to facilitate the display of information such as the separation trajectory as shown in
In an embodiment, the ASU system is integrated with the Area Control Center 1101 and is interfaced with the available directional and communications systems. In an embodiment, as indicated in step 1102, the ASU is deployed en-route in an urban air traffic information region (ATIR) role, referring to a non-airport-based control center that is primarily engaged in managing air taxis en-route to their destinations and thus not within the control of origin or destination launch and landing points. In an alternative embodiment, the ASU may be deployed at an airport. The ASU can be operated in standby mode 1103 supplying data and information to controllers who would then review, amend if needed, and transmit the recommended separation actions to multiple air taxis. Alternatively, operating in an automated mode 1104, the Area Control Center-based ASU transmits instructions to multiple air taxis simultaneously after tracking and computing individual reference formation airspaces and, when needed, penetration airspaces for multiple air taxis, and determining their target separation vectors as needed.
In addition to separation management for minimum-space adherence purposes, the ASU can also compute and transmit trajectories designed to optimize fuel efficiency and limit emissions. The specific operation of the ASU in an Urban Air Traffic Information Region tracking multiple air taxis and with full access to GPS and all related sensor, positioning, navigation, and air taxi transponder and communications performs the following representative steps:
The phrases “at least one,” “one or more,” “or,” and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C,” “at least one of A, B, or C,” “one or more of A, B, and C,” “one or more of A, B, or C,” “A, B, and/or C,” and “A, B, or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more,” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising,” “including,” and “having” can be used interchangeably.
Any of the steps, functions, and operations discussed herein can be performed continuously and automatically.
The exemplary systems and methods of this disclosure have been described in relation to computing devices. However, to avoid unnecessarily obscuring the present disclosure, the preceding description omits several known structures and devices. This omission is not to be construed as a limitation. Specific details are set forth to provide an understanding of the present disclosure. It should, however, be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein.
Furthermore, while the exemplary aspects illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined into one or more devices, such as a server, communication device, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switched network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system.
Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. These wired or wireless links can also be secure links and may be capable of communicating encrypted information. Transmission media used as links, for example, can be any suitable carrier for electrical signals, including coaxial cables, copper wire, and fiber optics, and may take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
While the flowcharts have been discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosed configurations and aspects.
Several variations and modifications of the disclosure can be used. It would be possible to provide for some features of the disclosure without providing others.
In yet another configurations, the systems and methods of this disclosure can be implemented in conjunction with a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device or gate array such as PLD, PLA, FPGA, PAL, special purpose computer, any comparable means, or the like. In general, any device(s) or means capable of implementing the methodology illustrated herein can be used to implement the various aspects of this disclosure. Exemplary hardware that can be used for the present disclosure includes computers, handheld devices, telephones (e.g., cellular, Internet enabled, digital, analog, hybrids, and others), and other hardware known in the art. Some of these devices include processors (e.g., a single or multiple microprocessors), memory, nonvolatile storage, input devices, and output devices. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
In yet another configuration, the disclosed methods may be readily implemented in conjunction with software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this disclosure is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized.
In yet another configuration, the disclosed methods may be partially implemented in software that can be stored on a storage medium, executed on programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this disclosure can be implemented as a program embedded on a personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated measurement system, system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system.
The disclosure is not limited to standards and protocols if described. Other similar standards and protocols not mentioned herein are in existence and are included in the present disclosure. Moreover, the standards and protocols mentioned herein, and other similar standards and protocols not mentioned herein are periodically superseded by faster or more effective equivalents having essentially the same functions. Such replacement standards and protocols having the same functions are considered equivalents included in the present disclosure.
This patent application is a continuation of U.S. patent application Ser. No. 17/871,175, filed Jul. 22, 2022, which is a continuation-in-part of U.S. patent application Ser. No. 17/700,382, filed Mar. 21, 2022, which is a continuation of U.S. patent application Ser. No. 17/492,904, filed Oct. 4, 2021, all of which are incorporated by reference in their entirety herein.
Number | Date | Country | |
---|---|---|---|
Parent | 17871175 | Jul 2022 | US |
Child | 18057325 | US | |
Parent | 17492904 | Oct 2021 | US |
Child | 17700382 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17700382 | Mar 2022 | US |
Child | 17871175 | US |