If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor
Generic Receiver Description: Difference between revisions
Rui.Sarnadas (talk | contribs) No edit summary |
No edit summary |
||
(61 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{Article Infobox2 | {{Article Infobox2 | ||
|Category=Receivers | |Category=Receivers | ||
| | |Editors=GMV | ||
|Level=Basic | |Level=Basic | ||
|YearOfPublication=2011 | |YearOfPublication=2011 | ||
|Logo=GMV | |Logo=GMV | ||
|Title={{PAGENAME}} | |||
}} | }} | ||
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 | GNSS receivers are responsible for processing the L-band Signals In Space (SIS) coming from the GNSS satellites. Each satellite transmits a continuous signal in the GHz range, modulated by a periodic digital code (called a pseudo-random noise code, or [[GNSS signal|PRN code]]), and further modulated with a data message. User receivers search for the presence of these radio signals that travel through space, and try to synchronize with them. This way, a GNSS receiver can be seen as a radionavigation user device that aims at tracking the GNSS signals, 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. | ||
The following sections present an overview of a typical GNSS receiver structure and processing chain. | |||
==Receiver overview== | |||
Although receiver architectures are tailored to the different [[GNSS signal|GNSS systems]] available and to different [[GNSS Applications|target applications]], the basic building blocks of a generic GNSS receiver are as shown in Figure 1: | |||
*<b>[[Antennas|Antenna]]</b> - L-band antenna, capturing GNSS signals, noise and possible interference. | |||
*[[Antennas|Antenna]] - L-band antenna, | |||
*<b>[[Front End|Front End]]</b> - The front-end typically down-converts, filters, amplifies and digitizes the incoming signals. | |||
[[ | *<b>[[Baseband Processing|Baseband signal processing]]</b> - Several [[Digital Signal Processing|signal processing]] routines are used to acquire and track the different signals. | ||
*<b>[[System Design Details#Applications Processing|Applications Processing]]</b> - Depending on the envisaged application, the receiver performs different tasks with the resulting GNSS information, and provides meaningful results to the user. | |||
[[File:Generic_Receiver_Architecture.PNG|center|thumb|628px|'''''Figure 1:''''' Generic Receiver Architecture. See this [[Receiver Block Diagram|block diagram]] for a detailed view.]] | |||
This section | In a typical receiver implementation<ref>See the [[Receiver Types|receiver types]] and [[System Design Details|system design details]] sections for a detailed description of different GNSS receiver architectures and implementations.</ref>, 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 signal|GNSS spectrum]], yielding the samples as real and complex components, namely I (In-Phase) and Q (Quadrature) components, in baseband. | ||
<b>Baseband signal processing</b> gathers all the algorithms to find and follow a visible GNSS signal, by means of synchronization to the known PRN code, and removing errors as best as possible. This process is built around the principle of [[Correlators|signal correlation]]: the incoming signal is repeatedly correlated with a replica of the expected PRN code, which is known <i>a priori</i>. To extract valid significance from the correlation, the local replica is generated in the receiver taking into account the signal carrier frequency, code delay, Doppler frequency, and [[GNSS signal|PRN code]] (which is unique to each satellite/signal). | |||
[[File:Acq_example.png|right|thumb|320px|'''''Figure 2:''''' Example of an acquisition process, showing the Doppler / code delay search space and correlation peak that indicates presence of a signal with code delay of 650 chips and Doppler frequency of -1750 Hz.]] | |||
The correlation principle is first used to search for the satellites in view. After a receiver starts operating, it first needs to know which satellites are in view and can be tracked for extracting measurements. This process is known as <b>acquisition</b>, and it is based on several correlations between the incoming signal and multiple replicas of the possible "expected" signals, generated for different code delays and Doppler frequencies. In fact, because the signal is originated by moving satellites, there is a Doppler<ref>[[Wikipedia:Doppler_effect|Doppler Effect in Wikipedia]]</ref> and code delay effect observed in the received signals. Therefore, the first two unknowns in detecting GNSS signals is the amount of delay and relative motion between the transmitted signal and the receiver. To search for the signals, different local replicas (corresponding to different code delay / Doppler frequency pairs) are generated and correlated with the input signals. When the local replica and the incoming signal are aligned, their correlation generates a peak (see Figure 2), and the code delay / Doppler frequency pair corresponding to this peak is assumed to be a good estimate to initialize the <b>tracking</b> process. | |||
In the [[Tracking Loops|tracking loops]], correlations are also used to refine the local replica generation, so as to match as best as possible the incoming signal. The correlation results are then applied to support different tracking loops in providing a measurement of tracking quality. Typically, the receiver tracks each signal using dedicated channels running in parallel, where each channel tracks one signal (i.e. for single frequency users, each channel tracks one satellite), providing pseudorange and phase measurements, as well as navigation data and additional signal information, such as carrier-to-noise ratio (C/N0). For details on the signal processing blocks, see the [[Digital Signal Processing|signal processing]] section. | |||
After correctly tracking the signals, and returning the measurements and data to the <b>application processing</b> block, the receiver uses the information from the tracking loops 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. | |||
==Trade-offs and limitations== | |||
The design and selection of a [[Receiver Types|receiver type]] is tightly linked to the target user application: for example, a multi-constellation GNSS receiver will certainly improve solution availability (critical, for instance, 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. This choice is usually a result of trade-off analysis that take into account several (and often related) factors, such as target application, performance, accuracy, power consumption, or cost. | |||
Deriving from the characteristics of radionavigation systems, electromagnetic wave propagation, and receiver architectures, different receivers yield different performances. As of today, there is still ongoing debate on the qualification and quantification of error measurements, receiver accuracy, and how they relate<ref>http://www.gpsworld.com</ref>. | |||
==Related articles== | ==Related articles== | ||
*[[GNSS Receivers General Introduction]] | |||
*[[Receiver Types]] | *[[Receiver Types]] | ||
*[[Receiver Operations]] | *[[Receiver Operations]] | ||
*[[System Design Details#Applications Processing|Applications Processing]] | |||
*[[Interfaces and Protocols|Interfaces and Protocols]] | |||
==References== | |||
<references/> | |||
[[Category:Receivers]] | [[Category:Receivers]] |
Latest revision as of 19:40, 2 September 2018
Receivers | |
---|---|
Title | Generic Receiver Description |
Edited by | 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. Each satellite transmits a continuous signal in the GHz range, modulated by a periodic digital code (called a pseudo-random noise code, or PRN code), and further modulated with a data message. User receivers search for the presence of these radio signals that travel through space, and try to synchronize with them. This way, a GNSS receiver can be seen as a radionavigation user device that aims at tracking the GNSS signals, 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.
The following sections present an overview of a typical GNSS receiver structure and processing chain.
Receiver overview
Although receiver architectures are tailored to the different GNSS systems available and to different target applications, the basic building blocks of a generic GNSS receiver are as shown in Figure 1:
- Antenna - L-band antenna, capturing GNSS signals, noise and possible interference.
- Front End - The front-end typically down-converts, filters, amplifies and digitizes the incoming signals.
- Baseband signal processing - Several signal processing routines are used to acquire and track the different signals.
- Applications Processing - Depending on the envisaged application, the receiver performs different tasks with the resulting GNSS information, and provides meaningful results to the user.
In a typical receiver implementation[1], 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, yielding the samples as real and complex components, namely I (In-Phase) and Q (Quadrature) components, in baseband.
Baseband signal processing gathers all the algorithms to find and follow a visible GNSS signal, by means of synchronization to the known PRN code, and removing errors as best as possible. This process is built around the principle of signal correlation: the incoming signal is repeatedly correlated with a replica of the expected PRN code, which is known a priori. To extract valid significance from the correlation, the local replica is generated in the receiver taking into account the signal carrier frequency, code delay, Doppler frequency, and PRN code (which is unique to each satellite/signal).
The correlation principle is first used to search for the satellites in view. After a receiver starts operating, it first needs to know which satellites are in view and can be tracked for extracting measurements. This process is known as acquisition, and it is based on several correlations between the incoming signal and multiple replicas of the possible "expected" signals, generated for different code delays and Doppler frequencies. In fact, because the signal is originated by moving satellites, there is a Doppler[2] and code delay effect observed in the received signals. Therefore, the first two unknowns in detecting GNSS signals is the amount of delay and relative motion between the transmitted signal and the receiver. To search for the signals, different local replicas (corresponding to different code delay / Doppler frequency pairs) are generated and correlated with the input signals. When the local replica and the incoming signal are aligned, their correlation generates a peak (see Figure 2), and the code delay / Doppler frequency pair corresponding to this peak is assumed to be a good estimate to initialize the tracking process.
In the tracking loops, correlations are also used to refine the local replica generation, so as to match as best as possible the incoming signal. The correlation results are then applied to support different tracking loops in providing a measurement of tracking quality. Typically, the receiver tracks each signal using dedicated channels running in parallel, where each channel tracks one signal (i.e. for single frequency users, each channel tracks one satellite), providing pseudorange and phase measurements, as well as navigation data and additional signal information, such as carrier-to-noise ratio (C/N0). For details on the signal processing blocks, see the signal processing section.
After correctly tracking the signals, and returning the measurements and data to the application processing block, the receiver uses the information from the tracking loops 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.
Trade-offs and limitations
The design and selection of a receiver type is tightly linked to the target user application: for example, a multi-constellation GNSS receiver will certainly improve solution availability (critical, for instance, 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. This choice is usually a result of trade-off analysis that take into account several (and often related) factors, such as target application, performance, accuracy, power consumption, or cost.
Deriving from the characteristics of radionavigation systems, electromagnetic wave propagation, and receiver architectures, different receivers yield different performances. As of today, there is still ongoing debate on the qualification and quantification of error measurements, receiver accuracy, and how they relate[3].
Related articles
- GNSS Receivers General Introduction
- Receiver Types
- Receiver Operations
- Applications Processing
- Interfaces and Protocols
References
- ^ See the receiver types and system design details sections for a detailed description of different GNSS receiver architectures and implementations.
- ^ Doppler Effect in Wikipedia
- ^ http://www.gpsworld.com