In addition to providing a navigation solution, navigation systems should also be able to provide users with timely warnings indicating when it is not safe/acceptable to use the navigation solution. A navigation system with this capability is, by definition, a navigation system with integrity.
With GPS for example, satellite failures can occur which result in unpredictable deterministic range errors on the failing satellite. Satellite failures are rare (i.e., on the order of 1 every year), but safety-critical navigation systems must account for these errors. Typically, navigation systems (e.g., GPS Receivers) provide integrity on their position solution (i.e., horizontal position and altitude), but do not provide integrity on other navigation parameters, such as ground speed and vertical velocity.
In an embodiment of the invention, a navigation system for a vehicle having a receiver operable to receive a plurality of signals from a plurality of transmitters includes a processor and a memory device. The memory device has stored thereon machine-readable instructions that, when executed by the processor, enable the processor to determine a set of error estimates corresponding to delta pseudo-range measurements derived from the plurality of signals, determine an error covariance matrix for a main navigation solution, and, using a solution separation technique, determine at least one protection level value based on the error covariance matrix.
Preferred and alternative embodiments of the present invention are described in detail below with reference to the following drawings.
An embodiment builds on many of the concepts applied to position integrity in order to provide integrity on the following navigation states: North Velocity, East Velocity, Ground Speed, Vertical Speed, Flight Path Angle, and Track Angle.
One or more embodiments may include a bank of filters/solutions (whether Kalman Filter or Least Squares) that may be composed of a main solution that processes all satellite measurements along with a set of sub-solutions; where each sub-solution processes one satellite fewer than the main solution
Navigation systems primarily employ one of the following implementations in order to calculate a navigation solution: a Kalman Filter or a Least Squares Solution. In general, GPS receivers which have GPS satellite measurements (and possibly altitude aiding) use a Least Squares solution while Hybrid Inertial/GPS systems use a Kalman Filter. Both methods use a recursive algorithm which provides a solution via a weighted combination of predictions and measurements. However, a Least Squares Solution possesses minimal prediction capability and is therefore heavily influenced by measurements (in fact the weighting factor on predictions in a Least Squares Solution approaches zero with each iteration). A Kalman Filter on the other hand is able to take advantage of additional information about the problem; such as additional measurement data (e.g., inertial data) or additional information about system noise and/or measurement noise. This allows the Kalman Filter to continuously vary its weighting on its own predictions versus measurement inputs (this may be done via the Kalman Gain). A Kalman Filter with very low confidence in its own predictions (i.e., a very large Kalman Gain) will behave much like a Least Squares Solution.
The Error Covariance Matrix, often denoted by the symbol “P.” within a navigation system represents the standard deviation of the error state estimates within a navigation solution. For example, given a 3×3 matrix representing the error covariance for the x, y, and z velocity states within a Kalman filter:
We would expect (with a properly modeled Kalman Filter) that, under the condition that a satellite fault is not a factor, the absolute value of the difference between the true ground speed and the Kalman Filter's ground speed would exceed 2√{square root over ((σx2+σy2))} ˜5%, or less, of the time. The same would be true for vertical velocity using 24732 instead. Note the off diagonal terms here represent cross-correlation between the velocities (how a change in x-velocity impacts a change in y-velocity or z-velocity for example).
The Error Covariance Matrix may be a critical component of any fault detection and integrity limit algorithm. For a Kalman Filter, P may be a fundamental part of the recursive Kalman Filter process. A Kalman Filter navigation solution may not be produced without the P matrix. With a Least-Squares solution, calculation of the actual navigation solution may not require use of an error covariance matrix. Therefore, a Least Squares Solution may only produce a P matrix if it is desired to provide integrity with the navigation solution. Calculation of a P matrix for a Least Squares solution is based on the satellite geometry (line of sight from user to all satellites in view) and an estimate of the errors on the satellite measurements.
Once a navigation system has an error covariance matrix along with its actual navigation solution, fault detection and calculation of integrity can be performed via Solution Separation or Parity Space Based techniques.
User set 12, mounted to an aircraft (not shown), includes receiver 14, processor 16, and processor memory 18. Receiver 14, preferably NAVSTAR GPS compatible, receives the signals, extracts the position and time data, and provides pseudorange measurements to processor 16. From the pseudorange measurements, processor 16 can derive a position solution for the user set. Although the satellites can transmit their positions in World Geodetic System of 1984 (WGS-84) coordinates, a Cartesian earth-centered earth-fixed system, an embodiment determines the position solution in a local reference frame L, which is level with the north-east coordinate plane and tangential to the Earth. This frame choice, however, is not critical, since it is well-understood how to transform coordinates from one frame to another.
Processor 16 can also use the pseudorange measurements to detect satellite transmitter failures and to determine a worst-case error, or protection limit, both of which it outputs with the position solution to flight management system 20. Flight management system 20 compares the protection limit to an alarm limit corresponding to a particular aircraft flight phase. For example, during a pre-landing flight phase, such as nonprecision approach, the alarm limit (or allowable radial error) may be 0.3 nautical miles, but during a less-demanding oceanic flight phase, the alarm limit may be 2-10 nautical miles. (For more details on these limits, see RTCA publication DO-208, which is incorporated herein by reference.) If the protection limit exceeds the alarm limit, the flight management system, or its equivalent, announces or signals an integrity failure to a navigational display (not shown) in the cockpit of the aircraft. The processor also signals whether it has detected any satellite transmitter failures.
As shown in
Inertial reference unit 22, mounted to the aircraft (not shown), preferably includes three accelerometers 24a-24c for measuring acceleration in three dimensions and three gyroscopes 26a-26c for measuring angular orientation, or attitude, relative a reference plane. Inertial reference unit 22 also includes inertial processor 25 which determines an inertial position solution ri, preferably a three-element vector in an earth-fixed reference frame. Inertial processor 26 also preferably converts the acceleration data into raw acceleration vector araw and attitude data into raw angular velocity vector ωraw. The preferred angular velocity vector defines the rotation of the body frame (fixed to the aircraft) in three dimensions, and the preferred inertial acceleration defines the three components of acceleration in body frame coordinates. Inertial processor 26 also determines a transformation matrix C for transforming body frame coordinates to local vertical frame L, a three-element rotation vector ωIE which describes rotation of the earth-based frame E versus inertial frame I transformed to L frame, and rotation vector co/, which describes rotation of the L frame versus the earth-fixed frame E transformed to L frame. The details of this inertial processing are well known in the art.
An embodiment of the invention involves the processor 16 receiving pseudo-range and delta pseudo-range measurements from the receiver 14. The delta pseudo-range measurement from a GPS satellite represents the change in carrier phase over a specific time interval. The delta pseudo-range corresponds to the change (over that time interval) in user-satellite range plus receiver clock bias and can be used to determine the velocity of a user (along with the clock frequency of the user's clock). An embodiment of the invention determines the integrity values on horizontal and vertical velocities calculated from a least-squares solution and then applies those integrity values in order to obtain integrity for: North Velocity, East Velocity, Groundspeed, Vertical Velocity, track angle, and flight path angle for a hybrid navigation solution.
Referring to
At a step 330, the processor 16 determines the measurement matrix. The true vector of delta pseudo-range residuals {dot over (ρ)} is related to the incremental velocity and clock frequency bias solution vector y (distance from the velocity linearization point) as follows:
H represents the measurement matrix and can be thought of as the mechanism for relating errors in the satellite delta pseudo-ranges into the solution vector. At a step 340, the processor 16 computes the Error Covariance Matrix. The vector of measured delta pseudo-range residuals {dot over ({tilde over (ρ)} is the true delta pseudo-range residual vector {dot over (ρ)} described above) plus the vector of residual errors δ{dot over (ρ)} and is thus
{dot over ({tilde over (ρ)}=Hy+δ{dot over (p)} (3)
The processor 16 designates the least-squares post-update estimate of y as ŷ. Then, the processor 16 can define the vector of post-update measurement residuals as
ξ={dot over ({tilde over (ρ)}−Hŷ (4)
Each post-update measurement residual is the difference between the measured delta pseudo-range residual and the predicted delta pseudo-range residual based on the post-update estimate ŷ. The processor 16 can compute a vector of normalized post-update measurement residuals by dividing each residual ξi by the expected one-standard deviation value of the corresponding delta pseudo-range error σdr(i). In vector form, this would be
If we assume that errors in each delta pseudo-range measurement are uncorrelated with the errors in the others, then W represents the inverse of the delta pseudo-range error covariance matrix.
At a step 350, the processor 16 computes a weighted least-squares solution. A “weighted least-squares solution” can be determined by finding the value of ŷ which minimizes the sum of squared normalized residuals. Thus we wish to minimize
T
This minimizing value is determined by taking the derivative of (7), setting it equal to zero, and solving for ŷ. Doing this, the processor 16 obtains
where we have defined the weighted least-squares solution matrix S as
S=(HTWH)−1HTW (9)
The error in the post-updated solution is
Substituting (3) into (10), the processor 16 gets
Thus, the solution matrix S maps the delta pseudo-range errors into the post-updated solution error vector. The solution error covariance matrix P is defined as
Instead of utilizing the matrix W explicitly, the processor 16 could incorporate the weightings into the measurement matrix and the residual vector directly by making the following substitutions
{dot over (
δ{dot over (
Equations (8), (9), (11), and (12) then become
At a step 360, the processor 16 computes weighted least-squares velocity integrity values. The processor 16 can employ a snapshot solution separation algorithm that utilizes equations 16-19 which incorporate W.
In snapshot solution separation, one is interested in the separation between the main solution and sub-solution (one which excludes a satellite from its solution). The jth sub-solution can be computed by zeroing out the jth row of the measurement matrix H. If the processor 16 designates the measurement matrix of the sub-solution as Hj, then the resulting least-squares sub-solution is:
where the least-squares sub-solution matrix is defined as:
j=(
and similarly the covariance matrix Pj is defined as:
P
j=(
The error covariance matrix P represents the uncertainty in horizontal and vertical velocity error estimates. Element (3,3) of this matrix represents the uncertainty of the vertical velocity error while the upper 2×2 portion of P describes the uncertainty for the x and y horizontal velocity errors. A 2×2 matrix is required for x and y velocity in order to account for cross-correlation between x and y.
Note that the jth column of
where Δ
dP
j
=E[dŷ
j
·dŷ
j
T
]=Δ
j
Δ
j
T
or
dP
j
=E[dŷ
j
·dŷ
j
T
]=P
0
−P
j (24)
The horizontal velocity separation is an elliptical distribution in the x-y plane. Since the separation is caused by the sub-least-squares solution processing one less satellite than the main solution, it is predominantly along one direction (the semi-major axis of the ellipse). Thus, the processor 16 assumes that the error is entirely along the semi-major axis of this ellipse. The separation along any one axis is normally distributed. The variance in this worst case direction is given by the maximum eigenvalue λdP
The detection threshold is computed using the allowed false alarm probability and a Normal distribution assumption as follows
where
Pfa=probability of false alert per independent sample
Nsol=Number of sub-least-squares solutions
Kfa=False alarm sigma multiplier
and Q−1 is the inverse of
The function F(z) is the well known standard normal distribution function.
Note that the allowed probability must be divided by 2, since the distribution is 2-sided, and divided by Nsol, since each active sub-filter has a chance for a false alert.
Based on (23) above the horizontal velocity discriminator (the horizontal velocity difference between the main solution and a sub-solution) can be calculated as follows:
d
j
horz=√{square root over ([dyj(1)]2+[dyj(2)]2)}{square root over ([dyj(1)]2+[dyj(2)]2)} (28)
where 1 and 2 indicate the x and y components of the velocity states.
A fault (or failure) is detected/declared anytime the discriminator exceeds the detection threshold for any main solution/sub-solution combination.
By definition, the horizontal velocity protection level (HVPL) is the error bound which contains the horizontal velocity error for the main least-squares solution to a probability of 1−pmd (where pmd is the allowable probability of missed detection of a GPS satellite failure) when the discriminator is at the threshold (i.e., when the largest undetectable error is present).
At the time an error is detected, the main least-squares horizontal velocity solution is separated from the sub-least-squares horizontal velocity solution by D0nhorz (defined in (26) above). The main least-squares velocity with respect to the true velocity is thus Djhorz plus the sub-least-squares velocity error (assuming, in the worst case, that the sub-solution velocity error is in the opposite direction as its difference from the main solution). The sub-solution velocity error bound ajhorz can be determined from the 2×2 matrix formed from the horizontal velocity error elements of the sub-solution “Fault Detection” error covariance, Pj. As a worst case, the processor 16 assumes that this direction coincides with the worst-case direction (semi-major axis) of the error ellipse. Thus, the variance is given by the maximum eigenvalue of the 2×2 matrix formed from the horizontal position error elements of the sub-filter “Fault Detection” error covariance matrix as shown below:
And the sub-solution velocity error bound can be defined as:
a
0n
horz=σhorz
where Q−1 is as defined in (27)
Note that the processor 16 only considers one side of the distribution, since the failure biases the distribution to one side. The allowed probability of missed detection is 1.0e−3/hr. When combined with the satellite failure probability of 1.0e−4/hr, an integrity failure rate of 1.0e−7/hr is achieved. Evaluating the Kmd, the processor 16 gets
Kmd=3.1 (31)
The HVPL for each active sub-solution j, is then computed as
HVPLj=Djhorz+ajhorz (32)
The final horizontal velocity protection level selected for the main least-squares solution is the maximum HVPL value from all main/sub-solution combinations.
Calculation of the Vertical Velocity Protection Level is done in the same manner as the horizontal method described above with one difference: Since the error distribution is only along one axis:
Equation (25) becomes:
σd
Equation (26) becomes:
Equation (28) becomes:
d
j
vert=√{square root over ([dyj(3)]2)} (35)
where 3 indicates the z-component of the velocity state.
Equation (29) becomes:
σvert
Equation (30) becomes:
a
0n
vert=σvert
At a step 370, the processor 16 computes Hybrid Integrity Values. Once the HVPL and VVPL values are known for the main least-squares solution they can be applied to the hybrid solution via the following equations:
North Velocity:
HVPLHybridNorth=HVPLLeast-Squares+|VHybridNorth−VLeast-SquareNorth| (38)
where:
HVPLHybridNorth=Horizontal Velocity Protection Level on Hybrid North Velocity
HVPLLeast-Square=Horizontal Velocity Protection Level from Solution Separation
VHybridNorth=Hybrid North Velocity
VLeast-SquareNorth=Least-Squares North Velocity
Similarly for East Velocity, Ground Speed, and vertical velocity:
HVPLHybridEast=HVPLLeast-Squares+|VHybridEast−VLeast-SquareEast| (39)
HVPLHybridGroundSpeed=HVPLLeast-Squares+|VHybridGroundSpeed−VLeast-SquareGroundSpeed| (40)
VVPLHybrid=VVPLLeast-Squares+|VHybridVertical−VLeast-SquareVertical| (41)
Note that the conservative assumption may be made here by the processor 16 that all least-squares horizontal protection levels are the same for north velocity, east velocity, and ground speed.
The track angle is defined as follows:
Taking the partial differentials, we find the error in the track angle
where vg is ground speed. The mean square value is
If we assume that the north and east errors have equal standard deviations and are uncorrelated, then for a large ground speed the ground speed error standard deviation may be the same as the north and east standard deviations. Thus,
Therefore, the standard deviation of the track angle error is
Based on this standard deviation track angle error, computation of hybrid track angle protection level TAPLhybrid (in degrees) may be defined as:
In a similar manner it can be shown that, if the vertical velocity is zero, then the standard deviation of the flight path angle error is
Therefore, computation of hybrid flight path angle protection level FPAPLhybrid (in degrees) is defined as:
Note that these approximations for track angle and flight path angle may not be valid for very slow ground speeds below 120 knots.
Satellite pseudo-range errors are composed of the following components:
Receiver Noise and Multipath Errors
Clock and Ephemeris Errors
Tropospheric and Ionospheric Errors
Note that the ionosphere is the dominating error impacting GPS accuracy.
Receiver noise and multipath along with clock and ephemeris standard deviations can all be treated as constants.
Calculation of a tropospheric standard deviation may be based on a standard model which accounts for the variation in range delay through the troposphere based on the elevation of the satellite (in reference to the user).
Similarly, ionospheric range errors may be modeled using a thin shell model which accounts for the elevation of the satellite along with geomagnetic latitude of the satellite's thin shell pierce point (ionospheric errors are largest near the equator and decrease as geomagnetic latitude increases).
Delta pseudo-range standard deviations can be calculated by determining the one standard deviation change of a pseudo-range error over a short time period (e.g., 1 second). For a 1st order Gauss-Markov model x(t), the one standard deviation change over time Δt is:
σΔx=σx√{square root over (2(1−e−Δt/τ))} (50)
σx=Standard deviation of Gauss-Markov Model
While a preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. Instead, the invention should be determined entirely by reference to the claims that follow.