
Technical Article • November/December 2016
Satellite Selectionfor Aviation Users of MultiConstellation SBASThe incorporation of multiple constellations into satellitebased augmentation systems may lead to cases where more satellites are in view than an aviation receiver has tracking channels. This article examines methods for selecting the optimal set of satellites and further describes a method to specify performance instead of a minimum hardware channel capacity. This form of specification allows for greater flexibility in receiver design. Manufacturers would be allowed to choose between more channels combined with a simpler algorithm versus fewer channels and a more sophisticated algorithm.
Share via: Slashdot Technorati Twitter Facebook The advent of multiple constellations provides the opportunity to eliminate geometry weakness as a source of satellitebased augmentation system (SBAS) unavailability. GPS users occasionally encounter areas where an insufficient density of satellites exists to support all desired operations. This most often occurs when a primary slot satellite is out of service. However, adding one or more constellations easily compensates for this geometric shortcoming. In fact, we may now experience the opposite problem of having more satellites that can be tracked by a receiver. There are many possible methods for selecting a set of satellites to use for the GPS position solution. Very often, elevation angle is used to rank satellites. A receiver may sort the satellites by their elevation angle and keep k (number of receiver hardware channels) highest ones. While this choice is good from a tracking robustness point of view, it does not lead to the best availability. Ideally, when choosing from n total satellites in view, the user will be able to find k that produce protection level values that are below the required integrity alert limits. In general, for aviation SBAS users it is desirable to find an algorithm that minimizes the vertical protection level (VPL) and the horizontal protection level (HPL). A brute force search, through all combinations, yields the optimal set for a given k, but may be costly and impractical when there are many possible satellite subsets. In this article, we examine and compare several methods that are more practical than the “optimal” brute force search. One such method is a “greedy” algorithm that iteratively removes the single least important satellite one at a time until only k satellites remain. An important consideration is that the optimal set of satellites depends on the specific protection level being minimized. The best sets will be different for SBAS VPL and SBAS HPL. Therefore, we need to define a balance when choosing between deselecting a satellite that least affects the VPL versus deselecting a satellite that least affects the HPL. Another factor is that the receiver is also capable of reverting to advanced receiver autonomous integrity monitoring (ARAIM) when leaving the SBAS service area – or in the event of an SBAS outage. The optimal satellite sets for ARAIM VPL and HPL differ even further from the SBAS sets; so, we may want to pursue another desirable goal: finding a satellite set that simultaneously allows the SBAS and ARAIM VPLs and HPLs to remain below their respective alert limits. We then use these algorithms to evaluate the decrease in performance relative to the allinview protection levels. We perform this analysis for dualconstellation conditions in order to examine sensitivity to satellite redundancy and geometric strength. Later, different constellation scenarios should be evaluated to determine the robustness of the techniques to initial geometric strength, and total numbers of satellites. This article will address several important questions:
Prior Satellite Selection Algorithms Probably the most common satelliteselection method is to use the elevation angle as a discriminator. The receiver may determine elevation angle, given a rough position estimate and the satellite almanac files that describe the approximate satellite orbital locations. The user does not need to track the satellites to estimate their elevation angle for the assumed location. The receiver will determine the elevation angle for every satellite for which it has almanac data. It can then eliminate from consideration signals from all of those satellites whose elevation angle falls below some elevation mask angle (e.g., five degrees as in today’s GPS aviation receivers). If the receiver has enough channels to track all of the remaining satellites then no further selection is required. However, if more satellites remain than the number of receiver tracking channels, the receiver must choose a set of satellites to track (or equivalently, the complementary set of satellites to exclude). The “elevation” method sorts the satellites by elevation angle and keeps the k satellites with the largest values. If more satellites are present above the mask angle than the receiver has tracking channels, the lowest elevation satellites are excluded. The lowest elevation satellites typically have the lowest received power and are the most vulnerable to loss due to aircraft banking. However, they are often quite important for good vertical geometry. Removing the lowest satellites can significantly increase the vertical dilution of precision (VDOP) and, in turn, VPL for SBAS and ARAIM. We should note, however, that the elevation method does not take into account satellite health or weighting factors. Higher elevation satellites may be unmonitored by SBAS or have large variances associated with their corrections. Simply looking at elevation angles discards this additional information. A better method would also make use of the health and weighting information that is broadcast from the SBAS satellites. This information should be used together with the satellite locations. Only satellites designated as healthy by the SBAS should be included in the n satellites to be considered for tracking. An “optimal” brute force method would look at all possible combinations of k out of n satellites to determine the best performance. This method is optimal in terms of returning the best possible outcome, but is distinctly nonoptimal in terms of computational cost. If there were n healthy satellites above the mask, a receiver with k channels would have to evaluate N_{opt} geometries where N_{opt} is given by
Equation (1) (see inset photo, above right, for all equations) If n = 30 and k = 24, then N_{opt} = 593,775 geometries to evaluate. As n becomes larger or k becomes smaller, the number of geometries to evaluate becomes even larger. As we will show later, we can efficiently code subset evaluations without having to compute full matrix inversions for each. However, even with efficient implementations, this approach has significant computational cost. We have used it for a few isolated geometries to compare the optimal result to the results from other methodologies. The “greedy” method is similar to the optimal in that it evaluates the performance of the subsets. The key difference is that the greedy method removes one satellite at a time and then uses the resulting geometry with the corresponding satellite removed to evaluate the next iteration. For a case with 30 initial satellites, all 30 subsets containing 29 satellites are evaluated. Then the one with the best metric is used for the next step where 29 subsets each containing 28 satellites are evaluated. This continues until only the desired number of satellites remains. The number of subsets to be evaluated by this method, N_{greedy}, is given by: Equation (2) For n = 30 and k = 24, then N_{greedy} = 165 geometries to evaluate. This is certainly more work that the elevation angle method, but far less than the optimal. Ideally, we would like to find a method that has an even smaller computational cost. A large number of selection algorithms have been developed over time. (See the Additional Resources near the end of this article for some examples.) Many of these seek to minimize the geometrical dilution of precision (GDOP) and do so by maximizing the volume of a polyhedron defined by the satellite locations. However, such methods do not account for the SBAS weights and are therefore not as well suited for our application.
Performance Optimization If the receiver knows the vertical alert limit VAL and the horizontal alert limit (HAL), it could use a cost function designed to try to keep the VPL and the HPL below these thresholds. Such cost functions would be small while the protection levels are below their respective alert limits but would dramatically increase as the protection level approaches or exceeds these thresholds. However, some classes of SBAS receiver merely output position estimates and protection levels. They do not know which service levels or alert limits are being targeted. Such receivers do not know how much margin they have against the alert limit thresholds. In the more demanding SBAS services, the VAL is smaller than the HAL. Also, the user almost always has a larger VPL than HPL. Therefore, it is typically much more important to minimize the VPL than it is to keep the HPL small. However, one should take both into account and try to prevent either one from exceeding their respective alert limits. We have therefore chosen to use the following cost function for ranking geometries: Equation (3) where Equation (4) and Equation (5) is the position estimate covariance matrix in the EastNorthUp (ENU) frame, G is the geometry matrix (also in the ENU frame), and W is the weighting matrix. This cost function represents a tradeoff between the vertical horizontal protection levels. The factor of ¼ multiplying the square of the HPL shifts priority to minimizing the VPL over minimizing the HPL. This factor is arbitrary and could easily be adjusted to shift the balance in one direction or the other. Indeed, the cost function itself was subjectively chosen. It was chosen in large part due to its simplicity. We had initially optimized only the VPL but found that sometimes satellite sets were chosen that had large HPL values. We found that by including the horizontal terms as in (3) we prevented large growth in the HPL. There are likely other cost functions that would lead to superior availability, however we believe that (3) is reasonable first choice.
Measurement Downdate Method Equation (6) where C_{(i)} is the position covariance matrix with the i_{th} satellite removed, S_{i} is the i_{th} column of the S matrix Equation (7) and Equation (8) Thus, starting from a single matrix inversion to obtain the allinview position estimate covariance matrix C, we can then find all the subset position estimate covariance matrices using much less computationally costly matrix multiplications rather than inversions. While this downdate method points to a more efficient means to implement the greedy algorithm, we can see that it also points the way to an even more efficient algorithm. From (6) we can see that Equation (9) The last term in (9) represents the increase in the covariance matrix, along the j_{th} user position axis, when removing the i_{th} satellite. The smaller this term is, the less impact it has in increasing the corresponding covariance term. Therefore, if we calculate Equation (10) and find the minimum value over all satellites, i, we will approach the cost function of (3). Most often we will have identified the satellite that the greedy algorithm would choose to exclude at the first step. However, rather than following the greedy algorithm and calculating the covariance matrices for subsubsets, we can simply sort the values in (10) from the allinview calculation and retain the satellites corresponding to the k largest values. We will call this the “downdate” method. We can see that it is much more efficient than the greedy method. As with the elevation angle method, we determine a set of values once for the allinview solution and then use the satellites with the k largest values. In the elevation method, the retained satellite elevation angles are maximized. In the downdate method, the retained satellite values given by (10) are maximized. Although it requires more effort to determine the downdate values than it does to determine the elevation angles, the downdate method is still very efficient compared to other alternatives. A similar method was recently proposed for GBAS by Gerbeth et alia (Additional Resources), that uses s_{3,i} to sort satellites. Although s_{3,i} correlates well with VPL, the authors had to add further logic to ensure the minimum VPL was found. For SBAS, s^{2}_{3}_{,i}/p_{i,i} is proportional to ΔVPL^{2}, so excluding the satellite with the minimum value directly corresponds to finding the oneout subset with the smallest VPL. In the next sections we will compare the ability of the various selection routines to optimize performance.
Simulation Setup We evaluated performance for users spaced on a twodegree by twodegree grid and used 300 evenly spaced time steps over one sidereal day. User positions were constrained to be in a lat/lon box between 15 degrees North and 75 degrees North, and between 175 degrees West and 50 degrees West. This set up was expected to create many different user scenarios, including ones where many satellites were in view, but with very different weights. The weights in particular are subject to variability. It is uncertain what values will be obtained for the weighting terms by the various SBAS providers, especially in a future DF environment. Thus, the absolute values of the protection levels are subject to change, however, we believe that the relative percentage change due to removing satellites should be representative. The SF simulation created 158,788 valid position estimates with 23,768 of them having more than 24 usable satellites in view. The DF simulation created 188,200 valid position estimates, with 26,709 having more than 24 usable satellites. Figure 1 shows histograms for the relative numbers in view for each case. The maximum number in view for this constellation configuration was 31 satellites. The different simulations created a wide variety of user scenarios featuring different weighting and geometry conditions. We then applied the elevation, greedy, and downdate methods to simulate receivers that had differing values for the maximum number of satellites that could be tracked.
Example Geometry The SBAS GEOs, as is typical, have much higher sigmas, and therefore, much lower weighting. Figure 3 shows which satellites are excluded by the elevation, greedy, or downdate method assuming a maximum of 24 satellites can be tracked. Satellites excluded by the elevation method are indicated by the blue pie wedges at the top of the numbered circles identifying the PRNs and location of the spacecraft. Satellites excluded by the greedy method are indicated by the cyan pie wedges at the bottom left of the numbered circles, and those excluded by the downdate method are indicated by the yellow pie wedges at the bottom right of the circles. Note that the greedy and downdate methods show much better agreement between themselves than with the elevation method. Both greedy and downdate methods agree that PRNs 12 and 92 are the least important satellites. They also both exclude 11, 93, 94, and 104, but not in the same order. Greedy also excludes 103 while downdate also removes 22. Both see relatively small increases in the VPL (three centimeters for greedy and two centimeters for downdate) and somewhat larger increases in HPL (70 centimeters for greedy and 98 centimeters for downdate). Both increases are much smaller than the increases seen by the elevation angle method (3.48 m in VPL and 1.23 m in HPL). Table 1 shows the HPLs and VPLs for four methods and for the maximum number of channels ranging from 31 down to 20. We also evaluated the optimal brute force method for this table. The downdate, greedy, and optimal methods are all comparable, even when removing 11 out of 31 satellites. This is particularly impressive because the downdate method only calculates the S and P matrices one time, for the full allinview solution. These matrices are not reevaluated after each satellite removal, as is the case for the greedy and optimal methods. Although these methods may not completely agree on the order in which to remove satellites, we find little difference in performance. They are choosing between roughly equally important satellites; so, the exact ranking is not critical. Contrast this to the elevation method, which is clearly removing satellites that otherwise keep the VPL small. Which method truly performs better is debatable as it is not obvious how much more important minimizing VPL over HPL is in this case. The last three methods all achieve VPLs below 10 meters and HPLs below 6 meters. Table 2 shows the order in which satellites are removed when excluding satellites by each method. When the number of channels is reduced by one, a single satellite is excluded from the prior set for the elevation, downdate, and greedy methods. This satellite will not be used for any cases with an even smaller number of channels. The optimal method, however, completely reevaluates each possible set of satellites. Thus, sometimes satellites that were excluded for a particular number of channels are not excluded for a smaller number of channels. For example, the difference between the satellite set for the optimal method when going from 26 to 25 channels is to reintroduce PRN 11 and remove PRNs 22 and 103. In the following section we look at statistical performance for the full set of users and time steps.
Simulation Results We could significantly increase the HPL without crossing its threshold; however, the VPL has substantially less margin. This is what motivated the factor of four dividing the horizontal terms in our cost functions. Note that in the example geometry, the elevation angle method does not support CATI autoland with fewer than 27 channels, while the other methods support this mode down to at least 20 channels. Remember that the broadcast sigma values are subject to change, as they depend on future dualfrequency algorithms. If the sigmas were made three times larger, the VPLs and HPLs would also all become three times larger. In that case, the allinview solution would still support LPV200 (but not CATI autoland). In such a scenario, the elevation angle method would not support LPV200 with fewer than 25 channels. The other methods would support it down to at least 20 channels. Figure 4 shows the maximum observed percentage increase in the protection levels observed for the singlefrequency simulation. These values decrease as the number of channels increases. The elevation method has significantly larger values for the VPL, ranging from a ~5 percent increase at 30 channels, to more than a 100 percent increase for 20 channels. At 24 channels, there was nearly a 50 percent increase. The downdate and greedy methods show dramatically smaller increases in VPL. They range from less than a 0.2 percent increase at 30 channels to less than 9 percent for 20 channels. These methods saw a ~2 percent maximum increase at 24 channels. The HPL increases for the three methods are much more similar, but the greedy method has the best performance. For 24 channels, the elevation and downdate methods see up to ~30 percent increase, while the greedy method sees up to ~20 percent. A similar set of curves was obtained for the dual frequency simulation. Availability is typically specified as an average, which over time requires more than 99 percent of all geometries at a single location to be instantaneously available. We can calculate the effect that having a limited number of channels has on observed availability, but it is harder to generalize the results. They will depend greatly on the assumed constellations and weights. They also will be very dependent on alert limits for the desired operation. Figure 4 shows the largest observed protection level increases. If such large increases are only rarely observed, they may have little effect on average availability. However, if we evaluate constellations with an even greater number of satellites, the large increases in protection levels will be more common and will have a larger impact on average availability. Table 3 shows the percent decrease in CATI autoland coverage area for the dualfrequency simulation. The coverage region is the area in which a specified availability is met. We determined the coverage region for the allinview case corresponding to availabilities, ranging from 95 percent to 100 percent, and then compared them to the corresponding regions for different numbers of channels. No changes were seen by any of the methods that employed 26 or more channels. The elevation method saw some significant decreases when falling below 24 channels. The downdate and greedy methods saw small decreases below 23 channels. The elevation method results indicate that the maximum increases indeed only affected relatively few geometries for our simulated scenarios. However, these results depend largely on the assumption in the simulation scenario. A scenario with even more satellites or worse weights would see larger impacts at a higher number of channels.
Performance Specification Instead, we would like to encourage the use of downdate or greedy selection methods. These methods are very robust to differing numbers of satellites in view and perform better as more satellites become available. However, we do not wish to mandate a particular algorithm because receiver manufacturers may have even better options available to them. Instead of a mandate, we propose to specify a reference set of geometries and weights. Each geometry would include the elevation and azimuth angles, the identity of the GNSS constellation to which the satellite belongs, and the variances used to create the weighting matrix. We would also specify a maximum allowed VPL and HPL for each geometry. This information would be included as part of a Matlab tool that would allow a manufacturer to encode their selection algorithm and evaluate its performance against each geometry. The specified algorithm would be considered acceptable if the tool confirms that the algorithm always returns protection levels below the thresholds. The thresholds would be set such that the downdate algorithm would pass the test, perhaps with some added margin. We still need to determine an appropriate number as well as which geometries to include. We envision that the tool could easily run hundreds, if not thousands, of simulated cases. We would include geometries that are representative of potential future satellite configurations and that do not perform well with the elevation selection method. These scenarios need to be agreed upon by the wider SBAS community.
Compatibility with ARAIM A cost function that combines the protection levels for both services would simultaneously limit the growth of each term, yet may fail to provide desired service through either. In contrast, a scheme that optimizes either SBAS or ARAIM may provide service through one, at the expense of the other. ARAIM optimization is a little more difficult than optimizing SBAS because the user will not necessarily know what confidence to place on a specific satellite until after a receiver is already tracking it. In contrast, the SBAS geostationary satellite broadcasts all of the confidence parameters for all of the GNSS satellites, regardless of whether the user is tracking them or not. The SBAS user has full knowledge of the W and G matrices. In offline ARAIM, the user range accuracy/signalinspace accuracy (URA/SISA) value is only included in the ephemeris data broadcast from each satellite. The ARAIM user can only guess at the contribution to the W matrix before devoting a channel to track and gather the required data. Currently, GPS constellation broadcasts a URA value of 2.4 meters more than 90 percent of the time; so, this confidence value is not necessarily difficult to predict. However, it remains to be seen how predictable these values will be in the future with new constellations and new messages on GPS that can broadcast a wider range of URA values. Nevertheless, we will assume that the URA/SISA values usually are near to a known constant value.
Example Geometry Revisited The greedy selection method can be very effectively applied to ARAIM as well as SBAS. Two ARAIM specific metrics were evaluated: the ARAIM VPL and the ARAIM vertical accuracy estimate, σ_{v}. The ARAIM VPL involves evaluation of numerous subsets, its specific formulation can be found in Annex A of the Milestone 3 Report under the EUU.S. Cooperation on Satellite Navigation referenced in Additional Resources. The vertical accuracy estimate is often very similar to the square root of the SBAS vertical covariance term c3,3 (especially when the ratio of the ARAIM accuracy values is similar to the ratio of the SBAS confidence terms). Therefore, minimizing this term is usually comparable to minimizing the SBAS VPL. Table 4 shows the results for four different selection algorithms: using the highest elevation angle satellites, the greedy algorithm selecting the best ARAIM VPL at each step, the greedy algorithm selecting the best vertical accuracy estimate at each step, and an optimal method that selects the smallest VPL over all possible combinations. Unlike for SBAS, ARAIM HPLs and VPLs can improve when removing satellites. This is because the least squares weights used for ARAIM do not necessarily minimize the ARAIM VPL, which also includes bias terms. In the Table 4 results, the last three methods obviously all perform much better at limiting VPL growth than selecting the highest elevation angle satellites. In this example, all subset geometries have VPLs that are slightly below the allinview case. This situation is not uncommon when many satellites are available and the protection levels are small. The SBAS protection levels in Table 1 are all smaller than the corresponding values in Table 4. This is to be expected inside SBAS coverage, where nearly all satellites have access to a good SBAS correction. However, on the edge of coverage, only some satellites will be corrected by SBAS, but all satellites will likely be usable by ARAIM. A possible algorithm would be to compare the allinview SBAS with the ARAIM protection levels and then optimize for whichever one performs better. In regions of good SBAS coverage, SBAS would be preferred. At the edges, and outside of SBAS coverage, ARAIM would be preferred.
Operational Considerations One may also want to be cautious about selecting too many lowelevation satellites. These satellites typically provide lower received power to user equipment and are more susceptible to unexpected loss of signal lock. Some lowelevation satellites will also be in the process of setting, in which case it may be preferable to select a replacement before the satellite goes below the elevation mask. Having a large number of channels and a large number of satellites in view will hopefully provide sufficient margin such that the loss of any one satellite will not result in a loss of service. Finally, we should note the time evolution of satellite selection involves many aspects. However, these are beyond the scope of this article.
Conclusions We have quantified this potential impact for an assumed set of different geometries. Nearly 50 percent increases in VPL and HPL are possible when assuming 24 channels, as compared to the allinview solution that contained as many as 31 satellites. We also presented an algorithm that does a much better job of selecting the satellites to track. This downdate algorithm limited the VPL growth to below two percent when considering 24 tracking channels under the same set of geometries. Furthermore, this algorithm is very efficient and does not require repeated evaluation of subset geometries. It acts on the allinview geometry to create a ranked list of which satellites are most important to track. Finally, we propose a new specification method to evaluate performance, rather than simply state a minimum number of tracking channels. The better the selection algorithm, the fewer required tracking channels. Manufactures would also have the option to use a simpler algorithm, but at the cost of having a larger number of tracking channels.
Acknowledgments
Additional Resources
Author Profiles
Todd Walter, Juan Blanch
Victoria Kropp Copyright © 2018 Gibbons Media & Research LLC, all rights reserved. 
