A new single-epoch method for resolving GNSS ambiguity with segmented search in short baseline

Abstract

Correct ambiguity resolution (AR) is the key for high-precision positioning. In order to reliably resolve ambiguity, an improved single-epoch segmented ambiguity algorithm is proposed in this paper. First, the double-difference wide-lane ambiguities resolved by the Melbourne-Wubbena (MW) method are divided into two categories based on signal-to-noise ratio (SNR). One is the primary ambiguity group that can be resolved easily, and the other is the secondary ambiguity group that is difficult to resolve. Second, the primary ambiguity group is divided into different levels in a (4,1,1…1) pattern based on SNR, and the different levels’ ambiguities are resolved successively, and the method being that the integer ambiguity is selected from two candidate values built by rounding up and down. Third, the resolved primary ambiguity group is used as a constraint to solve the secondary ambiguity group. Finally, the wide-lane observation equation and the basic observation equation are combined to solve the ambiguity of the L1 carrier phase, and the resolved ambiguity can be obtained by directly rounding. The candidate values of the primary ambiguity group is limited to two cycles through this step, and the (4,1,1…1) pattern can reduce ambiguity search times. Since an appropriate selection enables the correct resolution of primary wide-lane ambiguities, the selection of the threshold for SNR is the key to group wide-lane ambiguity, and we use the data from Novatel receiver as an example to discuss how to confirm the SNR threshold in this paper. Static short baseline data and kinematic short baseline that were less than 20 km were collected to validate the proposed algorithm. These results were compared with the commercial software IE8.60. These experiments show that the successful rate reaches 100%, 99.78% and 99.42%, respectively, for the new single-epoch segmented ambiguity method in the three data sets, and the accuracy is similar to that of IE8.60 for the combined double difference.