If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor

Receiver Operations: Difference between revisions

From Navipedia
Jump to navigation Jump to search
No edit summary
No edit summary
Line 8: Line 8:
}}
}}


In the first years of GNSS, when only GPS was available for public use, a receiver was not expected to perform as the navigation devices we see today. In fact, a first-generation GPS receiver could be designed to only process 4 or 5 signals at any given time, and it was deemed suitable for positioning applications. Today, with the increased availability and potencial of different GNSS signals and constellations, any receiver is expected to track at least 10 or 12 signals in parallel channels, and up to hundreds, resulting in a more accurate solution. However, at their core, and despite the many differences in target applications or implementation philosophy, most receivers still share many common control flow properties, such as:
In the first years of GNSS, when only GPS was available for public use, a receiver was not expected to perform as the navigation devices we see today. In fact, a first-generation GPS receiver could be designed to only process 4 or 5 signals at any given time, and it was deemed suitable for positioning applications. Today, with the increased availability and potencial of different GNSS signals and constellations, any receiver is expected to track at least 10 or 12 signals in parallel channels, and up to hundreds, resulting in a more accurate solution. However, at their core, and despite the many differences in target applications or implementation philosophy, most receivers still share many common control flow properties<ref>Although common, these (and other) tasks are not necessary parallel, nor always in place.</ref>, such as:


*<b>Channel management</b>: each channel is managed depending on the opeartion mode and current status, and resources are allocated as needed. For every step of the computations, each channel is seamlessly controlled in the receiver.
*<b>Channel management</b>: each channel is managed depending on the opeartion mode and current status, and resources are allocated as needed. For every step of the computations, each channel is seamlessly controlled in the receiver.


*<b>Signal processing</b>: from signal capture at the antenna up to successfull tracking and data demodulation, different processing tasks are performed for each receiver channel for [[Baseban Processing|baseband processing]]. Examples are the [[Correlators|correlation operations]] or the [[Tracking Loops|tracking loops]].
*<b>Signal processing</b>: from signal capture at the antenna up to successfull tracking and data demodulation, different processing tasks are performed for each receiver channel for [[Baseband Processing|baseband processing]]. Examples are the [[Correlators|correlation operations]] or the [[Tracking Loops|tracking loops]].


*<b>Navigation solution computation</b>: with the observables from [[Digital Signal Processing|signal processing]] stages, together with [[GNSS_signal|almanac and ephemeris]] from the data messages, the receiver periodically computes the different outputs, such as the PVT solution.
*<b>Navigation solution computation</b>: with the observables from [[Digital Signal Processing|signal processing]] stages, together with [[GNSS_signal|almanac and ephemeris]] from the data messages, the receiver periodically computes the different outputs, such as the PVT solution.


Although common, these (and other) tasks are not necessary parallel, nor always in place. The following sections detail several receiver operation modes controlled and managed within a receiver, that fall under the above categories.   
The following sections detail several receiver operation modes controlled and managed within a receiver, that fall under the above categories.   


==Operation modes==
==Operation modes==
Line 31: Line 31:
*<b>Lock detection</b>: a receiver constantly performes decisions to assess the quality of the observables in terms of noise or uncertainty, and these decisions determine the probability of a given tracked signal being "lost". This decision can yield a loss of lock, and the receiver channel is free to process other signals (e.g. start acquisition for other satellites).
*<b>Lock detection</b>: a receiver constantly performes decisions to assess the quality of the observables in terms of noise or uncertainty, and these decisions determine the probability of a given tracked signal being "lost". This decision can yield a loss of lock, and the receiver channel is free to process other signals (e.g. start acquisition for other satellites).


*<b>Solution output</b>: when tracking is successfull for a large enough period of time, and for enough satellites, the navigation message can be decoded from each signal, and the extracted information is used to compute the best solution needed - in most cases, the user's [[GNSS Receivers General Introduction|PVT solution]].
*<b>Solution computation</b>: when tracking is successfull for a large enough period of time, and for enough satellites, the navigation message can be decoded from each signal, and the extracted information is used to compute the best solution needed - in most cases, the user's [[GNSS Receivers General Introduction|PVT solution]].


==RF stage==
===RF stage===
GNSS receivers operate in three
GNSS receivers operate in three


==Start-up==
===Start-up===
GNSS receivers operate in three
GNSS receivers operate in three


==Acquisition==
===Acquisition===
GNSS receivers operate in three
GNSS receivers operate in three


==Tracking==
===Tracking===
GNSS receivers operate in three
GNSS receivers operate in three


==Lock detection==
===Lock detection===
GNSS receivers operate in three
GNSS receivers operate in three


==Solution computation==
===Solution computation===
GNSS receivers operate in three
GNSS receivers operate in three
where que se encarga de encontrar los 4 satélites con geometría óptima para la navegación, a partir de una lista de satélites visibles
where que se encarga de encontrar los 4 satélites con geometría óptima para la navegación, a partir de una lista de satélites visibles

Revision as of 18:17, 30 March 2011


ReceiversReceivers
Title Receiver Operations
Author(s) GMV
Level Medium
Year of Publication 2011
Logo GMV.png


In the first years of GNSS, when only GPS was available for public use, a receiver was not expected to perform as the navigation devices we see today. In fact, a first-generation GPS receiver could be designed to only process 4 or 5 signals at any given time, and it was deemed suitable for positioning applications. Today, with the increased availability and potencial of different GNSS signals and constellations, any receiver is expected to track at least 10 or 12 signals in parallel channels, and up to hundreds, resulting in a more accurate solution. However, at their core, and despite the many differences in target applications or implementation philosophy, most receivers still share many common control flow properties[1], such as:

  • Channel management: each channel is managed depending on the opeartion mode and current status, and resources are allocated as needed. For every step of the computations, each channel is seamlessly controlled in the receiver.
  • Navigation solution computation: with the observables from signal processing stages, together with almanac and ephemeris from the data messages, the receiver periodically computes the different outputs, such as the PVT solution.

The following sections detail several receiver operation modes controlled and managed within a receiver, that fall under the above categories.

Operation modes

One thing most GNSS receivers have in common is how they operate in terms of processing chain, from reception of signals to solution outputs. Alhough their types, architectures, and applications may vary, the operations of receivers apply transversly:

  • RF stage: the first stage of a receiver comprises the antenna and front end, responsible for the RF processing chain.
  • Start-up: a receiver starts processing the samples from the RF stage in different ways, depending on the available a priori information.
  • Acquisition: the first step, in many cases, is the search for visible satellites that can be tracked and used in the computed solution.
  • Tracking: after the initial determination of the satellites to track, several signal processing algorithms are use to continuously track the satellite's motion relative to the user.
  • Lock detection: a receiver constantly performes decisions to assess the quality of the observables in terms of noise or uncertainty, and these decisions determine the probability of a given tracked signal being "lost". This decision can yield a loss of lock, and the receiver channel is free to process other signals (e.g. start acquisition for other satellites).
  • Solution computation: when tracking is successfull for a large enough period of time, and for enough satellites, the navigation message can be decoded from each signal, and the extracted information is used to compute the best solution needed - in most cases, the user's PVT solution.

RF stage

GNSS receivers operate in three

Start-up

GNSS receivers operate in three

Acquisition

GNSS receivers operate in three

Tracking

GNSS receivers operate in three

Lock detection

GNSS receivers operate in three

Solution computation

GNSS receivers operate in three where que se encarga de encontrar los 4 satélites con geometría óptima para la navegación, a partir de una lista de satélites visibles output modes and data, protocols...


Related articles

For further details on GNSS receivers, please visit the following links:

References

  1. ^ Although common, these (and other) tasks are not necessary parallel, nor always in place.