US 8,700,306 B2Grant
Autonomous collision avoidance system for unmanned aerial vehicles
Issue Date:2014-04-15
•9 Claims
•7 Drawing Sheets
Abstract
Autonomous collision avoidance systems for unmanned aerial vehicles are disclosed. Systems illustratively include a detect and track module, an inertial navigation system, and an auto avoidance module. The detect and track module senses a potential object of collision and generates a moving object track for the potential object of collision. The inertial navigation system provides information indicative of a position and a velocity of the unmanned aerial vehicle. The auto avoidance module receives the moving object track for the potential object of collision and the information indicative of the position and the velocity of the unmanned aerial vehicle. The auto avoidance module utilizes the information to generate a guidance maneuver that facilitates the unmanned aerial vehicle avoiding the potential object of collision.
Metadata
Assignee
- L-3 Unmanned Systems Inc.
Inventors
- Davis S. Duggan
- David A. Felio
- Craig S. Askew
Application Information
Application Number:US 13/734,341
Filing Date:2013-01-04
Priority Date:2004-06-18
Art Unit:3663
Classifications
IPC:
G08G5/04
Patent Drawings (7 sheets)
Description
Reference to Related Applications
[0001] The present application is a continuation of and claims the priority of application Ser. No. 12/880,292, filed on Sep. 13, 2010, which is a continuation of and claims the priority of application Ser. No. 10/872,144, filed on Jun. 18, 2004, the contents of which are hereby incorporated by reference in their entirety.
Background
[0002] Many vehicles, such as aircraft vehicles, have systems which use radar for detecting potential objects of collision, such as terrain and other vehicles. Radar can detect potential objects of collision located within a certain proximity to the aircraft vehicle. Upon radar detecting the presence of a potential object of collision, a warning signal is provided to a pilot of the aircraft. The pilot must then analyze the object and determine if action needs to be taken in order to avoid the object. If action needs to be taken, the pilot obeys general aviation and etiquette rules promulgated by the FAA (Federal Aviation Administration) to regulate aircraft vehicle traffic in national air space (NAS).
[0003] These types of conventional avoidance systems are very expensive. Therefore, integrating such a system on smaller vehicles is not entirely feasible. In addition, these conventional avoidance systems detect potential objects of collision and provide warning signals only. Thus, conventional avoidance systems rely on the presence of a pilot to recognize the signal and take appropriate action by altering the course of the vehicle.
[0004] The potential for collisions is even greater in the context of unmanned vehicle systems. In one application of such a technology, a remotely located operator manages and controls an unmanned aerial vehicle (UAV), typically from a ground control station. Although the ground control station enables some degree of controlled flight, generally, UAVs lack the ability to scout out their surrounding airspace and watch for incoming obstacles. Even if a UAV is equipped with some sort of forward-looking camera or video capability, the remotely located operator is primarily focused on payload and mission operations and has a limited ability to accurately interpret and analyze video information. In addition, under the circumstances, a remotely located operator may have a difficult time complying with the FAA rules for flying in civilian airspace.
[0005] Currently, UAVs are not allowed to fly in NAS. In particular, UAVs are not allowed to fly in any air space unless the UAV has received FAA approval. One of the most significant technology barriers for integrating UAVs into NAS is an effective and reliable collision avoidance system. Overcoming this technology barrier will open beneficial services to the national civilian marketplace such as forest management, mineral surveys, border patrol, agriculture and pipeline and power line inspections. Beyond these and other specific potential UAV markets, an effective and reliable collision avoidance system can provide pilots an additional mechanism to safely fly manned aircraft.
Summary
[0006] Embodiments of the present disclosure include autonomous collision avoidance systems for unmanned aerial vehicles. Systems illustratively include a detect and track module, an inertial navigation system, and an auto avoidance module. The detect and track module senses a potential object of collision and generates a moving object track for the potential object of collision. The inertial navigation system provides information indicative of a position and a velocity of the unmanned aerial vehicle. The auto avoidance module receives the moving object track for the potential object of collision and the information indicative of the position and the velocity of the unmanned aerial vehicle. The auto avoidance module utilizes the information to generate a guidance maneuver that facilitates the unmanned aerial vehicle avoiding the potential object of collision.
Brief Description of the Drawings
[0007] FIG. 1 illustrates a simplified block diagram of a collision avoidance system in accordance with an embodiment of the present invention.
[0008] FIG. 2 illustrates a simplified block diagram of an auto avoidance module in accordance with an embodiment of the present invention.
[0009] FIG. 3 illustrates an earth centered, earth fixed (ECEF) reference frame.
[0010] FIG. 4-1 illustrates a geodetic reference frame and local vertical coordinate frame.
[0011] FIG. 4-2 illustrates a local vertical reference frame with respect to a geodetic reference frame.
[0012] FIG. 5 illustrates a local vertical reference frame and line of sight reference frame.
[0013] FIG. 6 illustrates a guidance logic routine in accordance with an embodiment of the present invention.
Detailed Description
[0014] Much of the description of the present invention will be devoted to describing embodiments in the context of unmanned aerial vehicles (UAV). However, it is to be understood that the embodiments of the present invention pertain to a collision avoidance system and are designed for broad application. The embodiments can be adapted by one skilled in the art to be applied in the context of any of a variety of unmanned and manned vehicles including, but not limited to, airplanes, helicopters, missiles, submarines, balloons or dirigibles, wheeled road vehicles, tracked ground vehicles (i.e., tanks), and the like.
[0015] FIG. 1 illustrates a simplified block diagram of autonomously controlled collision avoidance system 100 as implemented in a UAV 102 in accordance with an embodiment of the present invention. Collision avoidance system 100 includes a detect and track module 104 coupled to an auto avoidance module 106 which is in communication with a ground control station 108, an inertial navigation system 105 and flight controls 114.
[0016] Detect and track module 104 includes sensors 110 and moving target detection and tracking module 112. In one embodiment, sensors 110 include video or optical cameras that use visible-light wavelength detector arrays and can optically sense various objects within a particular range depending at least on camera quality and resolution capability. Sensors 110 are configured to take real-time video, typically digital video, of the environment in which UAV 102 is flying. For example, the video is provided to moving target detection and tracking module 112. In another embodiment, sensors 110 could be non-visual sensors, such as radio frequency (RF), laser, infrared (IR) or sonar. Module 112, using sensed information, is configured to provide moving object tracks to auto avoidance module 106. Inertial navigation system 105 provides auto avoidance 106 with information related to velocity, position and angular position of UAV 102.
[0017] Based on the moving object tracks provided by detect and track 104 and information provided by inertial navigation system 105, auto avoidance module 106 is able to generate the best estimate of position and velocity for the object of collision. Auto avoidance module 106 also calculates various relative or navigational states of the object of collision with respect to UAV 102 and generates guidance maneuver commands for flight controls 114 to avoid the potential object of collision. In addition, module 106 communicates with ground control station 108. Module 106 can relay status information, such as information related to position and velocity of UAV 102 and information related to the potential object of collision, to ground control station 108 through an operator interface 116. In accordance with one embodiment, the navigational status information alerts an operator that UAV 102 is on a course to collide with an object. Relaying status information gives the operator a chance to take over flight controls 114 to manually avoid the object and/or notify the operator that UAV 102 will enter an auto avoidance guidance mode. The status information also relays information related to potential objects of collision to a situation awareness display 118 via operator interface 116.
[0018] Situational awareness display 118 illustratively displays synthetic imagery of operator situational awareness. For example, situational awareness display 118 incorporates commercial off-the-shelf technology developed by SDS International of Arlington, Va. The synthetic imagery illustratively provides synthetic real-time displays of two-dimensional and/or three-dimensional views of UAV 102 and its surroundings as it flies within a particular airspace. For example, if current weather conditions are hazy or cloudy, the synthetic imagery displays UAV 102 in a clear synthetic corresponding environment. Auto avoidance module 106 provides information about a potential object of collision to situation awareness display 118 such that ground control station 108 can instruct situation awareness display 118 to generate visuals of objects based on the real-time position of the objects.
[0019] FIG. 2 illustrates a simplified block diagram of auto avoidance module 106 and inertial navigation system 105 in accordance with an embodiment of the present invention. Auto avoidance module 106 includes a track state estimator 120. Track state estimator 120, in the current embodiment, is configured to receive moving object tracks in the form of elevation εel and azimuth εaz direction finding (DF) angle information relative to the visual sensor bore sight. It should be noted that those skilled in the art could incorporate other track state information from detect and track module 112 in track state estimator 120. For example, range, closing velocity (VC) and DF rates can be incorporated from detect and track module 112. Track state estimator 120 is also configured to receive estimations of position and velocity for UAV 102 provided by inertial navigation system 105. Inertial navigation system 105 includes a global positioning system (GPS) 132 and an inertial measurement unit 134. These sensors are coupled with strapdown equations and a sensor error estimator such that the best estimate of position, velocity and angular position are determined for UAV 102. In addition, information determined by inertial navigation system 105 is also configured to be received by auto avoid guidance 128 to aid in guiding UAV 102 away from an object of collision. Track state estimator 120 uses the DF angle information and the best estimate of position and velocity of UAV 102 to estimate the relative range vector R , the relative range rate vector {dot over ( R , a line-of-sight angle vector λ LOS and a line-of-sight rate vector {dot over ( λ LOS between UAV 102 and the potential object of collision.
[0020] In accordance with one embodiment of the present invention, track state estimator 120 is an Extended Kalman Filter. Extended Kalman Filters are well known in the art. A detailed discussion of Extended Kalman Filters is described in the article by Taek L. Song et al. titled “Suboptimal Filter Design with Pseudomeasurements for Target Tracking”. 1988. IEEE Transactions on Aerospace and Electronic Systems. Vol. 24. However, those skilled in the art should recognize that track state estimator 120 can utilize other types of mathematical systems that provide estimations of past, present and future states of an object based on DF angles obtained by various types of sensors.
[0021] The information determined and provided by track state estimator 120 is received by auto avoid monitor 122 to determine various parameters that forecast future collisions and received by auto avoid guidance 128 to develop guidance commands that divert the path of UAV 102 to avoid such a collision. Auto avoid monitor 122 includes an avoid state calculator 124 and an avoid alert calculator 126. Avoid state calculator 124 takes the information estimated by track state estimator 120 and calculates various navigational states. For example, avoid state calculator 124 determines a time-to-go (tgo) to the closest point of approach based on current velocity and range profiles, the relative closing velocity (VC) along the line of sight between the object and UAV 102 and the zero effort miss distance (ZEM) or closest point of approach based on non-accelerated current velocity and range profiles. Currently, FAA guidelines require that a vehicle must miss another vehicle by 500 feet. Thus, the avoidance maneuver of the present invention illustratively guarantees at least a 500-foot miss (of course, any other range is within the scope of the present invention). In addition, the minimum miss distance or ZEM is used as an indicator to terminate the avoidance maneuver and return UAV 102 to its prior path.
[0022] Avoid alert calculator 126 calculates an alert avoid flag and a head-on flag based on ZEM. The head-on flag indicates that UAV 102 is on course to collide with the potential object of collision head-on. The alert avoid flag indicates that UAV 102 is on course to enter in to some other type of collision. Both head-on flag and alert avoid flag should activate auto avoid guidance 128 to avoid an object. Auto avoid guidance 128 receives the calculated parameters from avoid state calculator 124, the alert avoid flag as well as the head-on indicator to override the existing guidance mode of UAV 102. Auto avoid guidance 128 maneuvers UAV 102 by generating avoidance maneuver commands for flight controls 114 to avoid a collision and miss an approaching object by at least the predetermined miss distance. Auto avoid guidance 128 can also use an active transponder system, used in commercial aviation, to inject commands into auto avoid guidance module 128.
[0023] In accordance with one embodiment, auto avoid guidance 128 is programmed to make an avoidance maneuver according to the FAA's “rules of the road” for civilian aircraft operating in National Air Space (NAS). In particular, the avoidance maneuver complies with Part 91 of the FAA regulations and meets the FAA's Collision Avoidance Systems Final Rule FAA-2001-10910-487 and FAA 2001-10910-489. After auto avoid guidance 128 completes a maneuver, auto avoid recovery 130 generates recovery commands for flight controls 114 such that UAV 102 gracefully resumes the previous guidance mode.
[0024] FIG. 3 illustrates an earth centered, earth fixed (ECEF) reference frame 300. ECEF reference frame 300 is oriented with its origin at the earth center, wherein the x-axis and the y-axis lie in the equatorial plane 302 with the x-axis passing through the Greenwich Meridian 304. The z-axis is normal to the x-y plane and passes through the North Pole 306.
[0025] FIG. 4-1 illustrates a geodetic reference frame 400 that defines the lines of latitude λ and longitude l along the earth's surface. Geodetic latitude λ is the angle between the equatorial plane 402 and the normal to the surface of an ellipsoid. Geodetic longitude l is the angular rotation relative to the ECEF x-axis in the equatorial plane 402. Geodetic altitude h (not shown) is the elevation above the ellipsoid surface.
[0026] FIG. 4-2 illustrates a local vertical coordinate frame 404 with respect to the geodetic reference frame 400. The local vertical reference frame 404 is illustrated as a north, east, down (NED) reference frame. The NED reference frame is a right handed, orthogonal coordinate system oriented at the surface of the Earth's ellipsoid. The z-axis is tangent to the normal of the Earth surface ellipsoid and has its positive direction pointing into earth. The positive x-axis points towards true north and the positive y-axis points towards the East.
[0027] Certain embodiments of the present invention involve coordinate frame transformations. For example, a function can be applied to transform local vertical (NED) coordinates to body frame coordinates. In this example transformation, the following 3×3 transformation matrix (TBL Matrix):
[0028]
[0029] where θ is the pitch angle, ψ is the yaw angle and Φ is the roll angle of UAV 102.
[0030] FIG. 5 illustrates a local vertical coordinate frame showing the north, east and down (NED) components relative to UAV 102 and an object of collision 103. In addition, FIG. 5 illustrates a line of sight (LOS) coordinate frame, wherein the three components are labeled A, H and V in relation to the local vertical reference frame. Local vertical can be transformed into the LOS coordinate frame or vice versa based on the range components of the NED coordinate frame.
[0031] Upon detect and track module 104 (FIG. 1 ) detecting an object, track state estimator 120 of FIG. 2 is configured to receive the corresponding elevation angle εel and azimuth angle εaz of the potential object of collision and is configured to receive positional and velocity information from inertial navigation system 105. Based on this information, track state estimator 120 determines the position vector P OBJ,LV and the velocity vector V OBJ,LV of the potential object of collision in local vertical coordinates.
[0032] Track state estimator 120 uses these position and velocity values of the potential object of collision and position and velocity values of UAV 102 to calculate the relative range vector R of the potential impediment with respect to UAV 102, the relative range rate vector {dot over ( R , the line of sight rate vector {dot over ( λ , the line of sight angle vector λ , the range magnitude R and the range rate {dot over (R)}. The values of relative range vector, relative range rate vector, line of sight angle vector and line of sight rate vector are all computed into local vertical coordinates. For example local vertical coordinates can be based on a North, East, Down (NED) reference frame 404 as illustrated in FIG. 4-2 .
[0033] The relative range vector R (illustrated in FIG. 5 ) and range rate vector {dot over ( R are the differences between the position and velocity of the potential object of collision and the position and velocity of UAV 102 as illustrated in the following equation:
R = P OBJ,LV− P UAV,LV Equation 2
{dot over (R = V OBJ,LV− V UAV,LV Equation 3
{dot over (
[0034] The line of sight angle vector λ is calculated by:
λD=arctan(RE, RN) Equation 4
λE=arctan(−RD, √{square root over (RN2+RE2)}) Equation 5
λD=arctan(RE, RN) Equation 4
λE=arctan(−RD, √{square root over (RN2+RE2)}) Equation 5
[0035] where λD is the down component of the line of sight angle, λE is the east component of the line of sight angle, RN is the north component of the range vector (shown in FIG. 5 ), RE is the east component of the range vector (shown in FIG. 5 ) and RD is the down component of the range vector (shown in FIG. 5 ). The line of sight rate vector {dot over ( λ is the angular rate of change of the line of sight vector and is calculated by:
[0036]
[0037] where R is the relative range vector of the potential object of collision with respect to UAV 102, {dot over ( R the relative range rate vector of the potential object of collision with respect to UAV 102 and R is the magnitude of the relative range and is calculated by:
R=√{square root over (RN2+RE2+RD2)} Equation 7
R=√{square root over (RN2+RE2+RD2)} Equation 7
[0038] where RN is the north component of the relative range, RE is the east component of the relative range and RD is the down component of the relative range.
[0039] In accordance with an embodiment of the present invention, avoid state calculator 124 receives the relative range magnitude R, the relative range rate {dot over (R)} and the line of sight rate vector {dot over ( λ as determined and calculated by track state estimator 120. Avoid state calculator 124 calculates a closing velocity VC and a time-to-go tgo based on the relative range R and relative range rate {dot over (R)}. The closing velocity is the relative velocity along the line of sight between UAV 102 and the potential object of collision. Closing velocity is equal to the relative range rate provided by track state estimator 120 and is calculated by:
[0040]
[0041] where R is the relative range vector, {dot over ( R is the relative range rate vector and R is the relative range magnitude.
[0042] Time-to-go tgo is the amount of time until UAV 102 is at its closest point of approach to the potential object of collision assuming both the potential object of collision and UAV 102 continue at constant non-accelerating velocities. Time-to-go is calculated by:
[0043]
[0044] where R is the magnitude of the relative range vector and VC is the closing velocity as calculated in Equation 8. The calculation of closing velocity and the calculating of time-to-go are used for guiding UAV 102 away from an object as well as in the calculation of ZEM.
[0045] Avoid state calculator 124 also calculates ZEM of UAV 102. ZEM is the estimated zero miss distance or closest point of approach vector that UAV 102 will be with respect to the potential object of collision based on current velocity and range profiles. ZEM is calculated by:
ZEM={dot over (λ VCtgo2 Equation 10
ZEM={dot over (
[0046] where {dot over ( λ the relative range rate vector of UAV 102, VC is the closing velocity as calculated by Equation 8 and tgo is time-to-go as calculated in Equation 9.
[0047] Referring back to FIG. 2 , auto avoid monitor 122 includes an avoid alert calculator 126 configured to determine when a head-on flag and an avoid alert flag should be activated. To activate an avoid alert flag, avoid alert calculator 126 compares the magnitude of ZEM to the predetermined miss distance limit, such as 500 feet, or a predetermined allowable miss distance from the potential object of collision. If the ZEM is greater than the predetermined allowable miss distance, then the avoid alert flag is not activated. If, however, the ZEM is less than the predetermined allowable miss distance, then the avoid alert flag is activated. The alert flag remains activated until the ZEM becomes greater than the predetermined deactivation distance, which is greater than the allowable miss distance. This creates a hysterisis effect that prevents the alert flag from entering a cycle in which it is activated and deactivated repeatedly.
[0048] Upon auto avoid guidance 128 receiving an avoid alert flag from avoid alert calculator 126 and/or a head-on flag, auto avoid guidance 128 begins a guidance logic routine that continues as long as auto avoid monitor 122 predicts that UAV 102 will approach an object within the predetermined miss distance. FIG. 6 illustrates such a routine 600 as implemented by auto avoid guidance 128 in accordance with an embodiment of the present invention.
[0049] Routine 600 begins at block 602 and determines whether an avoid alert flag has been activated by auto avoid calculator 126. If an avoid alert flag is activated, then control passes to block 614 to determine if a head-on flag has been activated. Routine 600 continues to determine if an avoid alert flag has been activated until auto avoid calculator activates an avoid alert flag.
[0050] If a head-on flag is activated, then routine 600 proceeds to block 604 initializes head-on avoidance. At block 604, a head-on collision maneuver under auto avoid guidance is activated and a waypoint leg is calculated. A waypoint leg is calculated which consists of at least two waypoints parallel to the current vehicle heading that are offset by a predetermined amount to ensure that the miss distance is achieved. After calculation of the waypoint leg, auto avoid guidance 128 begins guidance of UAV 102 at block 606. At block 608, the routine determines whether the avoid alert flag is still activated. If the avoid alert flag is still activated, then the routine passes to block 610 to determine if the final waypoint of the waypoint leg has been reached. If the avoid alert flag is not activated, then control passes to block 612 and auto avoid guidance returns UAV 102 back to the stored or previous guidance mode as set in initialization. If the final waypoint leg has been reached, then control also passes to block 612. If the final waypoint has not been reached, then control passes back to block 606 to continue auto avoid guidance. The routine passes through blocks 608 and 610 until either the avoid alert flag is not activated or the final waypoint has been reached.
[0051] Referring back to block 614, if, however, a head-on flag is not activated, then the routine passes to block 616 to initialize avoidance. At block 618, an inverse homing command is calculated and designed to guide UAV 102 off of the collision trajectory it is on. Under the inverse homing commands, auto avoid guidance 128 alters UAV 102 away from the object of collision and recalculates the ZEM to determine if UAV 102 is still on course to collide with the object of collision. If the recalculation still indicates that UAV 102 is on course to collide, then auto avoid guidance repeats altering UAV 102 away from the object of collision until UAV 102 Is no longer on course to collide with an object of collision.
[0052] The calculated acceleration commands are generated normal to the current line of sight vector to the object of collision as shown below:
[0053]
[0054] where nc is the acceleration command in local vertical coordinates, N is the guidance gain for avoidance, ZEM is the current Zero Effort Miss as calculated in Equation 10 by auto avoid monitor 122, ZEMDesired is the desired zero effort miss, and tgo is the time to go as calculated in Equation 9 by the auto avoid monitor 122. ZEMDesired is most appropriately defined in the LOS frame (illustrated in FIG. 5 ) and then transformed into the local vertical frame to support the previous calculation.
[0055] At block 620, the routine determines if the alert avoid flag is still activated. If the avoid alert flag is still activated, then control passes back to block 618 to continue guiding UAV 102 away from the object of collision. If, however, the alert avoid flag is not activated, then control passes to block 612 to return UAV 102 back to the stored or previous guidance mode.
[0056] Although the present invention has been described in detail with respect to a control system for an unmanned aerial vehicle, the present invention is applicable to any vehicle control system or autopilot. In addition, although not specifically described, in one embodiment of the present invention, auto avoid guidance 128 (FIG. 2 ) supplies flight controls 114 (FIG. 2 ) with acceleration vectors in order to guide UAV 102 away from an object of collision. This acceleration vector can be used to accommodate any vehicle control system. If a particular vehicle control system does not accept an acceleration vector for its autopilot, the acceleration vector can be translated into a suitable parameter in order to guide a vehicle away from an object of collision.
[0057] Although the present invention has been described with reference to preferred embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.
Claims
What is claimed is:
1. A method for autonomously controlling a vehicle so as to avoid potential collisions, the method comprising:
detecting and tracking potential objects of collision by identifying directional finding angle information;
determining that at least one of the potential objects of collision will enter a path of the vehicle;
guiding the vehicle out of the path, wherein guiding the vehicle out of the path comprises putting the vehicle on a different path that allows the vehicle to miss the objects of collision by at least a predetermined miss distance, and wherein guiding the vehicle further comprises determining a zero effort miss distance, the zero effort miss distance being a function of the line of sight rate, a closing velocity and an amount of time until the vehicle has reached a closest point of approach to the potential objects of collision; and
wherein said determining and guiding are based on the directional finding angle information and a navigational state of the vehicle.
2. The method of claim 1, wherein determining comprises calculating a relative range, a relative range rate, a line of sight angle and a line of sight rate between the potential objects of collision and the vehicle based on the directional finding angle information and navigational states of the vehicle.
3. The method of claim 2, wherein the line of sight angle is based on a trigonometric function of the relative range.
4. The method of claim 2, wherein the line of sight rate is a function of the relative range and the relative range rate.
5. The method of claim 1, and further comprising:
activating an alert flag based at least in part upon a determination that the vehicle is on course to enter within the predetermined distance relative to the potential object of collision; and
altering the course of the vehicle based at least in part on the activation of the alert flag.
6. The method of claim 5, wherein the alert flag provides an indication of whether the vehicle is on course to collide head-on with the potential object of collision or whether the vehicle is on course to enter into another type of collision with the potential object of collision.
7. The method of claim 5, wherein altering the course comprises calculating a waypoint leg to alter the course of the vehicle.
8. The method of claim 1, and further comprising returning the vehicle to a previous guidance mode by restoring a previous course of the vehicle after the vehicle has avoided the potential object of collision.
9. A method for autonomously controlling a vehicle so as to avoid potential collisions, the method comprising:
detecting and tracking potential objects of collision by identifying directional finding angle information;
determining that at least one of the potential objects of collision will enter a path of the vehicle;
guiding the vehicle out of the path;
wherein said determining and guiding are based on the directional finding angle information and a navigational state of the vehicle;
activating an alert flag based at least in part upon a determination that the vehicle is on course to enter within the predetermined distance relative to the potential object of collision;
altering the course of the vehicle based at least in part on the activation of the alert flag; and
wherein the alert flag provides an indication of whether the vehicle is on course to collide head-on with the potential object of collision or whether the vehicle is on course to enter into another type of collision with the potential object of collision.
Patent Citations (132)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3025514(A) | 1962-03-01 | Alexander et al. | Applicant |
| US4155525(A) | 1979-05-01 | Peter-Contesse | Applicant |
| US4611771(A) | 1986-09-01 | Gibbons et al. | Applicant |
| US4642774(A) | 1987-02-01 | Centala et al. | Applicant |
| US4725956(A) | 1988-02-01 | Jenkins | Applicant |
| US4868755(A) | 1989-09-01 | McNulty et al. | Applicant |
| US5042743(A) | 1991-08-01 | Carney | Applicant |
| US5048771(A) | 1991-09-01 | Siering | Applicant |
| US5123610(A) | 1992-06-01 | Oaks | Applicant |
| US5157615(A) | 1992-10-01 | Brodegard et al. | Examiner |
| US5179377(A) | 1993-01-01 | Hancock | Examiner |
| US5181673(A) | 1993-01-01 | Hubricht et al. | Applicant |
| US5214584(A) | 1993-05-01 | Dingee et al. | Applicant |
| US5240207(A) | 1993-08-01 | Eiband et al. | Applicant |
| US5313201(A) | 1994-05-01 | Ryan | Examiner |
| US5321489(A) | 1994-06-01 | Defour et al. | Examiner |
| US5422998(A) | 1995-06-01 | Margolin | Applicant |
| US5448233(A) | 1995-09-01 | Saban et al. | Examiner |
| US5522567(A) | 1996-06-01 | Kinstler | Applicant |
| US5552983(A) | 1996-09-01 | Thornberg et al. | Applicant |
| US5553229(A) | 1996-09-01 | Margolin | Applicant |
| US5566073(A) | 1996-10-01 | Margolin | Applicant |
| US5566074(A) | 1996-10-01 | Hammer | Examiner |
| US5581250(A) | 1996-12-01 | Khvilivitzky | Examiner |
| US5605307(A) | 1997-02-01 | Batchman et al. | Applicant |
| US5666531(A) | 1997-09-01 | Martin | Applicant |
| US5691531(A) | 1997-11-01 | Harris et al. | Applicant |
| US5782429(A) | 1998-07-01 | Mead | Applicant |
| US5822515(A) | 1998-10-01 | Baylocq | Applicant |
| US5839080(A) | 1998-11-01 | Muller et al. | Applicant |
| US5872526(A) | 1999-02-01 | Tognazzini | Examiner |
| US5904724(A) | 1999-05-01 | Margolin | Applicant |
| US5933099(A) | 1999-08-01 | Mahon | Examiner |
| US5933156(A) | 1999-08-01 | Margolin | Applicant |
| US5938148(A) | 1999-08-01 | Orenstein | Applicant |
| US5944762(A) | 1999-08-01 | Bessacini et al. | Applicant |
| US5951607(A) | 1999-09-01 | Senn et al. | Applicant |
| US5951609(A) | 1999-09-01 | Hanson et al. | Applicant |
| US5969665(A) | 1999-10-01 | Yufa | Examiner |
| US5974423(A) | 1999-10-01 | Margolin | Applicant |
| US5978488(A) | 1999-11-01 | Margolin | Applicant |
| US5993156(A) | 1999-11-01 | Bailly et al. | Applicant |
| US6021374(A) | 2000-02-01 | Wood | Examiner |
| US6023278(A) | 2000-02-01 | Margolin | Applicant |
| US6025790(A) | 2000-02-01 | Saneyoshi | Applicant |
| US6054937(A) | 2000-04-01 | Von Viebahn et al. | Examiner |
| US6057786(A) | 2000-05-01 | Briffe et al. | Examiner |
| US6062513(A) | 2000-05-01 | Lambregts | Applicant |
| US6064939(A) | 2000-05-01 | Nishida et al. | Applicant |
| US6076042(A) | 2000-06-01 | Tognazzini | Examiner |
| US6092009(A) | 2000-07-01 | Glover | Applicant |
| US6122570(A) | 2000-09-01 | Muller et al. | Applicant |
| US6122572(A) | 2000-09-01 | Yavnai | Examiner |
| US6138060(A) | 2000-10-01 | Conner et al. | Applicant |
| US6177943(B1) | 2001-01-01 | Margolin | Applicant |
| US6219592(B1) | 2001-04-01 | Muller et al. | Applicant |
| US6222480(B1) | 2001-04-01 | Kuntman et al. | Examiner |
| US6262679(B1) | 2001-07-01 | Tran | Applicant |
| US6271768(B1) | 2001-08-01 | Frazier et al. | Examiner |
| US6304819(B1) | 2001-10-01 | Agnew et al. | Applicant |
| US6314366(B1) | 2001-11-01 | Farmakis et al. | Applicant |
| US6377436(B1) | 2002-04-01 | Margolin | Applicant |
| US6393362(B1) | 2002-05-01 | Burns | Examiner |
| US6433729(B1) | 2002-08-01 | Staggs | Examiner |
| US6498984(B2) | 2002-12-01 | Agnew et al. | Applicant |
| US6584382(B2) | 2003-06-01 | Karem | Applicant |
| US6584383(B2) | 2003-06-01 | Pippenger | Applicant |
| US6748325(B1) | 2004-06-01 | Fujisaki | Examiner |
| US6778906(B1) | 2004-08-01 | Hennings et al. | Examiner |
| US6789016(B2) | 2004-09-01 | Bayh et al. | Examiner |
| US6798423(B2) | 2004-09-01 | Wilkins et al. | Examiner |
| US6804607(B1) | 2004-10-01 | Wood | Examiner |
| US6826458(B2) | 2004-11-01 | Horvath et al. | Examiner |
| US6847865(B2) | 2005-01-01 | Carroll | Applicant |
| US6862501(B2) | 2005-03-01 | He | Applicant |
| US6885874(B2) | 2005-04-01 | Grube et al. | Applicant |
| US6889123(B2) | 2005-05-01 | Wittenberg | Examiner |
| US6909381(B2) | 2005-06-01 | Kahn | Applicant |
| US6917863(B2) | 2005-07-01 | Matos | Examiner |
| US6975246(B1) | 2005-12-01 | Trudeau | Examiner |
| US7010398(B2) | 2006-03-01 | Wilkins et al. | Examiner |
| US7057549(B2) | 2006-06-01 | Block | Examiner |
| US7116266(B1) | 2006-10-01 | Vesel et al. | Examiner |
| US7124000(B2) | 2006-10-01 | Horvath et al. | Examiner |
| US7132982(B2) | 2006-11-01 | Smith et al. | Examiner |
| US7158073(B2) | 2007-01-01 | Ybarra | Examiner |
| US7190303(B2) | 2007-03-01 | Rowlan | Applicant |
| US7212918(B2) | 2007-05-01 | Werback | Examiner |
| US7343232(B2) | 2008-03-01 | Duggan et al. | Applicant |
| US7349774(B2) | 2008-03-01 | Werback | Examiner |
| US7408552(B2) | 2008-08-01 | Kellman et al. | Examiner |
| US7693624(B2) | 2010-04-01 | Duggan et al. | Applicant |
| US7769502(B2) | 2010-08-01 | Herman | Examiner |
| US7818127(B1) | 2010-10-01 | Duggan et al. | Applicant |
| US8395533(B2) | 2013-03-01 | Ganille et al. | Examiner |
| US8570211(B1) | 2013-10-01 | Piesinger | Examiner |
| US2001/0013836(A1) | 2001-08-01 | Cowie | Examiner |
| US2002/0055909(A1) | 2002-05-01 | Fung et al. | Applicant |
| US2002/0069019(A1) | 2002-06-01 | Lin | Examiner |
| US2002/0080059(A1) | 2002-06-01 | Tran | Examiner |
| US2002/0133294(A1) | 2002-09-01 | Farmakis et al. | Examiner |
| US2002/0152029(A1) | 2002-10-01 | Sainthuile et al. | Applicant |
| US2003/0014165(A1) | 2003-01-01 | Baker et al. | Examiner |
| US2003/0046025(A1) | 2003-03-01 | Jamieson et al. | Examiner |
| US2003/0122701(A1) | 2003-07-01 | Tran | Examiner |
| US2003/0132860(A1) | 2003-07-01 | Feyereisen et al. | Examiner |
| US2003/0137444(A1) | 2003-07-01 | Stone et al. | Examiner |
| US2003/0182060(A1) | 2003-09-01 | Young | Examiner |
| US2003/0233192(A1) | 2003-12-01 | Bayh et al. | Examiner |
| US2004/0000991(A1) | 2004-01-01 | Schiffmann et al. | Examiner |
| US2004/0174295(A1) | 2004-09-01 | Stayton et al. | Examiner |
| US2004/0193334(A1) | 2004-09-01 | Carlsson et al. | Applicant |
| US2004/0217883(A1) | 2004-11-01 | Judge et al. | Examiner |
| US2004/0239529(A1) | 2004-12-01 | Tran | Examiner |
| US2005/0004723(A1) | 2005-01-01 | Duggan et al. | Applicant |
| US2005/0024256(A1) | 2005-02-01 | Ridderheim et al. | Examiner |
| US2005/0055143(A1) | 2005-03-01 | Doane | Examiner |
| US2005/0057372(A1) | 2005-03-01 | Taylor | Applicant |
| US2005/0077424(A1) | 2005-04-01 | Schneider | Examiner |
| US2005/0156777(A1) | 2005-07-01 | King et al. | Examiner |
| US2005/0219113(A1) | 2005-10-01 | Rowlan | Examiner |
| US2005/0256938(A1) | 2005-11-01 | Margolin | Applicant |
| US2006/0097895(A1) | 2006-05-01 | Reynolds et al. | Examiner |
| US2006/0142903(A1) | 2006-06-01 | Padan | Examiner |
| US2007/0093945(A1) | 2007-04-01 | Grzywna et al. | Applicant |
| US2007/0210953(A1) | 2007-09-01 | Abraham et al. | Examiner |
| US2009/0048723(A1) | 2009-02-01 | Nugent et al. | Examiner |
| US2009/0125163(A1) | 2009-05-01 | Duggan et al. | Applicant |
| US2010/0121575(A1) | 2010-05-01 | Aldridge et al. | Examiner |
| US2010/0256909(A1) | 2010-10-01 | Duggan et al. | Applicant |
| US2010/0292873(A1) | 2010-11-01 | Duggan et al. | Applicant |
| US2010/0292874(A1) | 2010-11-01 | Duggan et al. | Applicant |
Non-Patent Literature (24)
- RIS Press Release, “Landform Situation Aware”, pp. 1-4, http://www.landform.com/pages/PressReleases.htm (last viewed on Nov. 17, 2005).Applicant
- Beringer, Dennis; “Applying Performance-Controlled Systems, Fuzzy Logic, and Fly-By-Wire Controls to Generate Aviation Office of Aerospace Medicine,” May 2002, pp. 1-14.Applicant
- Parrish, R. et al.; “Spatial Awareness Comparisons Between Large-Screen, Integrated Pictorial Displays and Conventional EFIS Displays During Simulated Landing Approaches,” NASA Technical Paper 3467, CECOM Technical Report 94-E-1, Oct. 1994, 29 pages.Applicant
- Airspace Integration for Unmanned Aviation, Office of the Secretary of Defense, Nov. 2004, 69 pages.Applicant
- Abernathy, Michael, “Virtual Cockpit Window” for a Windowless Aerospacecraft, Jan. 2003, pp. 1-2, http://www.nasatech.com/Briefs/Jan03/MSC23096.html (last viewed Nov. 17, 2005).Applicant
- Guckenberger, Dr. Donald et al., “UCAV Distributed Mission Training Testbed: Lessons Learned and Future Challenges,” Conference Theme: Partnerships for Learning in the New Millennium, 2000, pp. 1 and 7.Applicant
- Swihart, Donald et al., “Results of a Joint US/Swedish Auto Ground Collision Avoidance System Program,” Sep. 13-18, 1998, pp. 1-8, 17 and 18, International Council of the Aeronautical Sciences (ICAS) and American Institute of Aeronautics and Astronautics, Inc. (AIAA), Melbourne, Australia.Applicant
- Leavitt, Charles A., “Real-Time In-Flight Planning,” Aerospace and Electronics Conference, May 1996, pp. 1-7.Applicant
- Margolin, Jed, “Response to a Non-Final Office mailed on Sep. 1, 2010,” U.S. Appl. No. 11/736,356, pp. 1-76.Applicant
- Margolin, Jed, Declaration of Jed Margolin, “Response to a Non-Final Office Action mailed on Sep. 1, 2010,” U.S. Appl. No. 11/736,356, pp. 77-79.Applicant
- Margolin, Jed, Exhibit 1, “AWST Article NASA Plans UAS Push,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 80-81.Applicant
- Margolin, Jed, Exhibit 2, “Duggan Filewrapper Documents,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 82-89.Applicant
- Margolin, Jed, Exhibit 3, “Geneva License Agreement,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 90-107.Applicant
- Margolin, Jed, Exhibit 4, “Public Records from Palm Beach County, Florida,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 108-178.Applicant
- Margolin, Jed, Exhibit 5, “UCAV Distributed Missing Training Testbed: Lessons Learned and Future Challenges,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 179-183.Applicant
- Margolin, Jed, Exhibit 6, “Documents from Geneva Aerospace Trademark Applications, Serial No. 78355947 for ‘Variable Autonomy Control System’ from USPTO Trademark Document Retrieval Website,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 184-188.Applicant
- Margolin, Jed, Exhibit 7, “Documents from Geneva Aerospace Trademark Applications, Serial No. 78355939 for ‘VACS’ from USPTO Trademark Document Retrieval Website,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 189-193.Applicant
- Margolin, Jed, Exhibit 8, “Decelopment and Testing of a Variable Autonomy Control System (VACS) for UAVs, by Dave Duggan of Geneva Aerospace and Luis A. Pineiro of AFRL contained in the Proceedings AUVSI Symposium, 2002,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 194-209.Applicant
- Margolin, Jed, Exhibit 9, “From Geneva Aerospace U.S. Appl. No. 60/480,192 Small Business Innovation Research (SBIR) Program Projects Summary, Topic No. AF98-179,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 210-233.Applicant
- Margolin, Jed, Exhibit 10, “Geneva Phase I Contract Information for AF98-179 from Air Force SBIR Website,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 234-235.Applicant
- Margolin, Jed, Exhibit 11, “IDS from Duggan U.S. Appl. No. 60/480,192,” Response to a Non-Final Office Action mailed on Sep. 1, 2010, U.S. Appl. No. 11/736,356, pp. 236-241.Applicant
- Prosecution documents from U.S. Appl. No. 12/956,735, filed Nov. 30, 2010, 16 pages.Applicant
- Prosecution documents from U.S. Appl. No. 10/872,144, filed Jun. 18, 2004, 182 pages.Applicant
- Prosecution documents from U.S. Appl. No. 12/880,292, filed Sep. 13, 2010, 68 pages.Applicant