Carrier Phase Positioning
Understanding Carrier Phase Positioning
Code-Phase versus Carrier-Phase Tracking
Standard GPS and GNSS receivers determine position by measuring the time-of-arrival of the pseudo-random noise (PRN) codes modulated onto the carrier wave. Because these code chips have a duration of about 1 microsecond (corresponding to a physical length of approximately 300 meters), code-phase positioning is typically limited to an accuracy of 1 to 5 meters. Carrier phase positioning, on the other hand, measures the phase of the high-frequency carrier wave itself (e.g., L1 carrier at 1575.42 MHz, which has a wavelength of 19 centimeters). Measuring the phase with a precision of 1% of the wavelength allows the receiver to resolve distance changes to the millimeter level.
The primary challenge in carrier phase positioning is the integer ambiguity problem. While a receiver can measure the fractional phase of the arriving wave, it does not know the total integer number of full wave cycles between the satellite and the antenna. Resolving this integer ambiguity requires differential techniques, such as Real-Time Kinematic (RTK) positioning, which compares measurements from a rover antenna with a stationary base station at a known location.
Cycle Slips and Phase Noise Vulnerabilities
High-precision carrier tracking is sensitive to signal blockages and phase noise. If the line-of-sight to a satellite is temporarily blocked by trees or buildings, the receiver loses track of the wave cycles. This event is called a cycle slip. When a cycle slip occurs, the receiver must restart the integer ambiguity resolution process. Additionally, phase noise in the local oscillator of the receiver can corrupt the phase measurements, degrade the tracking loop stability, and increase the time-to-first-fix.
Key Mathematical Relations
Technical Specifications Comparison
| Positioning Method | Measurement Target | Signal Wavelength Reference | Typical Accuracy | Acquisition Time (Time to Fix) |
|---|---|---|---|---|
| Code-Phase (Standard GNSS) | Modulated PRN Code Chips | ~ 300 meters | 1.5 to 5 meters | Instantaneous (< 1 second) |
| Carrier-Phase DGNSS | Carrier Wave Phase + Code | ~ 19 cm (L1 Band) | 10 to 50 centimeters | 10 to 30 seconds |
| Real-Time Kinematic (RTK) | Double-Differenced Carrier Phase | ~ 19 cm (L1 Band) | 1 to 2 centimeters | 1 to 5 minutes (for initialization) |
| Precise Point Positioning (PPP) | Dual-Frequency Carrier Phase | Multi-wavelength (L1/L2/L5) | 2 to 5 centimeters | 15 to 30 minutes (worldwide convergence) |
Frequently Asked Questions
What is the integer ambiguity problem in carrier-phase tracking?
The receiver can measure the fractional phase of the incoming carrier wave (the point within a 360-degree cycle), but it cannot directly count how many full wave cycles lie between the satellite and the antenna. Resolving this unknown integer count is called integer ambiguity resolution, and it is required to achieve centimeter accuracy.
What causes cycle slips and how do they affect positioning accuracy?
Cycle slips are caused by temporary signal blockages, low signal-to-noise ratio, or high acceleration of the receiver. When the tracking loop momentarily loses lock, it loses the count of the integer wave cycles. This causes the positioning accuracy to instantly degrade back to standard code-phase limits until the ambiguity is re-resolved.
Why is a base station or reference network required for RTK carrier phase positioning?
Measuring the carrier phase at a single receiver contains errors from atmospheric delays (ionosphere and troposphere) and satellite clock drift. By double-differencing the measurements between a local rover and a stationary base station close by, these common-mode errors cancel out, leaving only the relative position vector.