Abstract

The generation and use of GNSS analysis products that allow—particularly for the needs of single-receiver applications—precise point positioning with ambiguity resolution (PPP-AR) are becoming more and more popular. A general uncertainty concerns the question on how the necessary phase bias information should be provided to the PPP-AR user. Until now, each AR-enabling clock/bias representation method had its own practice to provide the necessary bias information. We have generalized the observable-specific signal bias (OSB) representation, as introduced in Villiger (J Geod 93:1487–1500, 2019) originally exclusively for pseudorange measurements, to carrier phase measurements. The existing common clock (CC) approach has been extended in a way that OSBs allowing for flexible signal and frequency handling between multiple GNSS become possible. Advantages of the proposed OSB-based PPP-AR approach are: GNSS biases can be provided in a consistent way for phase and code measurements and it is capable of multi-GNSS and suitable for standardization. This new, extended PPP-AR approach has been implemented by the Center for Orbit Determination in Europe (CODE). CODE clock products that adhere to the integer-cycle property have been submitted to the International GNSS Service (IGS) since mid of 2018 for three analysis lines: Rapid, Final, and MGEX (Multi-GNSS Extension). Ambiguity fixing is performed not only for GPS but also for Galileo. The integer-cycle property of between-satellite clock differences is of fundamental importance when comparing satellite clock estimates among various analysis lines, or at day boundaries. Both kinds of comparisons could be exploited at a very high level of consistency. Any retrieved comparison essentially indicated a standard deviation for between-satellite clocks from CODE of the order of 5 ps (1.5 mm in range). Finally, the integer-cycle property that may be recovered between the CODE Final clock and the accompanying bias product of consecutive daily sessions (using clock estimates additionally provided for the second midnight epoch) allows us to deduce GPS satellite clock and phase bias information that is consistent and continuous with respect to carrier phase observation data over two, three, or, in principle, yet more days. Phase-based clock densification from initially estimated integer-cycle-conform clock corrections at intervals of 300 s to 30 s (5 s in case of our Final clock product) is a matter of particular interest. Based on direct product comparisons and GRACE K-band ranging (KBR) data analysis, the quality of accordingly densified clock corrections could be confirmed to be on a level similar to that of “anchor” (300 s) clock corrections.

Highlights

  • Precise point positioning (PPP) is a well-established tool to enable single-receiver users to compute their receiver positions with an accuracy conforming to geodetic network standards (Zumberge et al 1997; Kouba and Héroux 2001)

  • The CPU time of our precise point positioning with ambiguity resolution (PPP-ambiguity resolution (AR)) procedure typically takes a couple of minutes only

  • The results of experiment 1 we summarized in Sect. 3.4.1 showed us that we can accomplish the generation of ambiguity-fixed GNSS clock corrections and associated phase biases by complying with the following sequence of processing steps: 1. GNSS satellite clock estimation, called “zero floated” iteration: using phase and pseudorange code tracking data, with floating phase ambiguities; 2. phase bias determination and single-receiver integer fixing, using the global tracking data sample from step 1; 3

Read more

Summary

Introduction

Precise point positioning (PPP) is a well-established tool to enable single-receiver users to compute their receiver positions with an accuracy conforming to geodetic network standards (Zumberge et al 1997; Kouba and Héroux 2001). This paper shall help to make another step toward standardization in the PPP-AR domain by consistently relying on standards for OSB-based PPP-AR (as they should apply to Bias-SINEX) Such a standardization has to be considered beneficial especially for all PPP-AR users, which thereby should get a common interface for standardized, applicable GNSS bias data that, may be expected to be consistent to existing IGS clock analysis products. 5 demonstrates that we are able to straightforwardly generate continuous integer clock information over three consecutive daily sessions and it addresses the question whether densification of clock corrections (by analyzing time differences of carrier phase observation data) is harmful for an ambiguity-fixed clock product.

Melbourne–Wübbena linear combination
Relevance of single-differenced receiver phase and code biases to widelane AR
Ionosphere-free linear combination
Integer clocks
81 Page 6 of 25
Basic principles
81 Page 8 of 25
Algorithm for retrieval of fractional phase biases
Some specific experiments
Experiment 2
Experiment 3
GNSS clock generation scheme approved for use
Advantages of the CC-OSB method
Overview of CODE clock analysis products
Results
81 Page 12 of 25
GPS and Galileo widelane phase bias results
CODE internal validation
Integer-property clock results
Comparison of integer clocks among various CODE analysis lines
Regular comparisons and combinations made by IGS analysis center coordinator
81 Page 16 of 25
Comparison of integer clocks at day boundaries
81 Page 18 of 25
Validation by comparing high-rate clocks of two analysis lines
Densification of clocks
81 Page 20 of 25
Validation by comparing clocks at day boundaries
Validation using GRACE K-band ranging data
Summary and conclusions
Implementation at CODE
81 Page 22 of 25
Outlook and further developments
PPP-AR user side
81 Page 24 of 25
PPP-AR product provider side
Special case of integer-recovery clock products
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.