If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor
Generic Receiver Description
| Receivers | |
|---|---|
| Title | Generic Receiver Description |
| Author(s) | GMV |
| Level | Basic |
| Year of Publication | 2011 |
GNSS receivers are responsible for processing the L-band Signals In Space (SIS) coming from the GNSS satellites. This way, a GNSS receiver can be seen as a radionaviagation user device that aims at tracking the GNSS signals in view, in order to correctly demodulate and extract the measurements and navigation information - one example is to decode the transmitted navigation message and calculate the user's position.
Receiver overview
Although each receiver architecture is tailored to the different GNSS systems applicable and to the target applications, the basic building blocks of a generic GNSS receiver are as shown in Figure 1:
- Antenna - L-band antenna, responsible for capturing the GNSS signals transmitted (as well as noise and possible interference).
- Front End - The hardware front-end typicaly downconverts, filters, amplifies, and digitizes the incoming signals.
- Baseband signal processing - Several signal processing routines are used to acquire and track the different signals.
- Receiver application - Depending on the envisaged task, the receiver performs different tasks with the resulting GNSS information, and provide meaningful results to the user.
In a typical receiver implementation, the Signals In Space (SIS) arriving at the antenna are down-converted, filtered, and digitized in the front end section.
This process ultimately generates a baseband representation of the desired GNSS spectrum, yelding the samples as real and complex components, namelly I (In-Phase) and Q (Quadrature) components, in baseband.
The baseband processing blocks are built around the principle of signal correlation.
The receiver tracks each signal using dedicated channels running in parallel, where typically each channel tracks one signal (i.e. for single frequency users, each channel tracks one satellite), providing pseudo-range and phase measurements, as well as navigation data and additional signal information (such as C/N0).
See the receiver types and system design details sections for a detailed description of different GNSS receiver architectures and implementations.
In the application processing block, the receiver may use the incoming information for different purposes, from computing its own position and velocity, to performing time transfer, or simply collecting data to be post-processed in the ground stations. For a wider discussion on application specifics see GNSS Applications.
In addition to processing the SIS, GNSS receivers may also use aiding information to enhance their solution performance. There are various architectural solutions to cope with aiding information: in fact, this information can be used potentially at any block of the receiver. As an example, when using Inertial Navigation Systems (INS), the sensor information is usually used in the application processing block (although it could also be used as feedback to the baseband processing block for improved performance).
This section tackles the basic functions of the standalone GNSS Receiver. See System Design Details.
Trade-offs and limitations
GNSS Receiver manufacturers rely on each system’s SIS ICD (Signal In Space Interface Control Documents) to develop their solutions. The SIS ICDs define signal properties, transmitted codes and navigation messages contents that allow the receivers to process the SIS signals. For further information please refer to XXX. Pushed by the emergence of new services aimed at professional and safety of life users, standardization activities have been launched at European level (CEN, CENELEC and ETSI), at global level (e.g. ICAO standard and recommended practices) and at industry level (e.g. industry standards, RTCA and EUROCAE MOPS/ MASPS).
The design and selection of a receiver is tightly linked to the target user application: for example, a multi-constellation GNSS receiver will certainly improve solution availability (critical for example in urban environments), whereas if the user application is focused on improved accuracies, then the selected receiver will probably turn to carrier-based technologies or differential and augmented solutions. The type of assisting/aiding information to be used also focuses on the user application. On one hand, different technologies such as WiFi, UWB and INS can be used to improve solution availability and continuity, in environments where GNSS cannot guarantee the desired availability (e.g. mixed open/ indoor environments). On the other hand, this information can be used to improve indicators such as Time To First Fix (TTFF): as an example, downloading the navigation data through the internet will greatly improve this factor, since the receiver will not have to wait to demodulate the whole message to compute position.
Related articles
For further details of GNSS receivers and operations, please visit the following links: