GNSS fundamentals: from satellite signals to a position fix¶
A satellite navigation receiver measures signals and uses them to estimate where it is and what time it is. Understanding that chain is useful before opening a spectrum viewer or trying to receive navigation signals with an SDR.
What GNSS means¶
Global Navigation Satellite System (GNSS) is the umbrella term for satellite systems that provide positioning, navigation and timing. GPS, Galileo, GLONASS and BeiDou are examples. GPS is one GNSS, rather than a synonym for the entire field.
A GNSS has three main parts: satellites broadcasting signals, a ground control infrastructure maintaining the system, and user receivers processing those signals. The receiver needs information about both signal timing and satellite orbits. ESA describes this architecture in its GNSS data processing reference.
Measuring travel time¶
The basic idea is to compare a received ranging code with a local replica. Their alignment provides timing information. Multiplying a signal travel time by the speed of light converts time into distance.
The result is called a pseudorange because receiver clock error and other effects are included. A simplified code measurement model for satellite \(i\) is:
Here \(P_i\) is measured in metres, \(\mathbf{x}\) is receiver position, \(\mathbf{s}_i\) is satellite position at transmission time, and \(c\) is the speed of light. The clock offsets are in seconds; \(I_i\) and \(T_i\) represent ionospheric and tropospheric code delays in metres. The remaining term collects effects such as noise, multipath and unmodelled biases. A practical implementation also needs consistent coordinate frames and corrections beyond this introductory model. See ESA's GNSS basic observables.
Why four satellites are usually needed¶
For a basic single-system, unconstrained three-dimensional solution, the receiver estimates four unknowns: three position coordinates and its clock offset. At least four independent satellite measurements with suitable geometry are needed. Extra measurements provide redundancy; the number alone does not guarantee accuracy. Multi-system processing can introduce additional clock-bias unknowns. ESA develops the basic solution in code-based positioning.
Inside a receiver¶
flowchart LR
A[Antenna and RF front end] --> B[Complex IQ samples]
B --> C[Acquisition]
C --> D[Code and carrier tracking]
D --> E[Navigation data and observables]
E --> F[Position, velocity and time]
Acquisition searches for a known code over candidate code delays and frequency offsets. Tracking refines those estimates over time. Navigation processing then combines timing measurements, satellite orbit and clock information, and appropriate corrections. The stages have different success criteria: finding an acquisition peak does not establish a position fix. ESA provides a receiver introduction.
What this means for an SDR experiment¶
Keep the evidence for each stage separate:
| Stage | Useful evidence | What remains to be shown |
|---|---|---|
| Sample capture | File format, duration, sample rate, continuity | Whether a GNSS signal is present |
| Acquisition | A repeatable code-delay and frequency peak | Stable tracking |
| Tracking | Loop histories and lock metrics | Valid navigation data and observables |
| Position solution | Timestamped fixes and quality indicators | Accuracy against an independent reference |
A spectrum is useful for inspecting the receive chain, but it does not identify a particular ranging code. Repeatable processing of a saved IQ file helps separate changes in receiver software from changes in the RF environment.
Where to go next¶
Read PRN codes and correlation to understand the acquisition step. The SDR section provides a starting point for documenting a hardware experiment.