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

Receiver Characteristics: Difference between revisions

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


Receiver characteristics and design (link to system design) are strongly related to the application at hand. In fact, the target application requirements are actually the main driver to a given receiver architecture and design decisions and therefore the selection of an adequate receiver usually underlies a large set of trade-offs.
Receiver characteristics and [[System Design Details|design]] are strongly related to the application at hand. In fact, the target application requirements are actually the main driver to a given receiver architecture and design decisions and therefore the selection of an adequate receiver usually underlies a large set of trade-offs.


==Design considerations==
==Environmental Constraints==
From a system design perspective, there isn't a real set of "rules of thumb" to chose a given approach for a GNSS receiver design. In fact, the requirements are strongly influenced by the application itself, whether in terms of architecture or performance. Below are a few examples<ref>For another example on receiver design considerations, see <i>Kaplan, E.D. et al, "Understanding GPS: Principles and Applications", second edition, chapter 3, section 3.4</i>.</ref> of the requirements, analysis and tradeoffs involved:


*<b>Environmental Constraints</b>: Factors such as temperature, humidity, water resistance, shock and vibration ranges depend on the application. Furthermore, the surrounding environment can also impact the design in terms of performance, e.g. urban environments can originate several multipath signals, where the reflection of GNSS signals on surrounding surfaces generates a non-line-of-sight ray. In the latter case, multipath mitigation signal-processing techniques may be required.
The surrounding environment influences the receiver behaviour in terms of performance, some examples are:
*<b>Multipath</b>: GNSS signals can be affected by multipath, whenever the reflection of the SIS signal on surrounding surfaces distorts the received signal or even generates a non-line-of-sight ray. Multipath mitigation techniques may be implemented in the receiver, at the cost of increasing the processing load. Conversely, it may be beneficial to process NLOS reflected signals for improving availability while sacrificing accuracy. The trade-off “availability vs accuracy” will rely mainly on the receiver application. For non-critical road applications in urban environments, for example, availability may be more important than accuracy, since the receiver often makes use of map matching techniques to extrapolate its position and therefore tracking of NLOS may come as a design decision, despite the large errors introduced in the final solution.


*<b>Precision and Accuracy</b>: Higher precision is required, for instance, in survey or military operations, whereas automotive or mobile applications may not require centimeter-level precision. As another example, the solution accuracy, precision, and rate are surely different for aircraft precision approach, than for marine or automotive navigation.
*<b>Interference</b>: in some applications it may be possible to predict that a certain type of interference will be present in some locations. An example is the case of aeronautical applications, where it is foreseen that TACAN/ DME beacons will cause pulse interference in the L5/ E5a band. In this case, the receiver may consider including techniques of pulse interference mitigation in the front end (link to front end). Another example to be considered are the case of some military applications that use antenna arrays and beam-forming to insert nulls in the radiation diagram of the antenna in the direction of an interferer whose position is known a-priori or detected dynamically.


*<b>Single/Multi Frequency/Constellation</b>: An increasing range of GNSS frequencies, bands, modulations and constellations enable a multitude of possibilities in receiver design, from single frequency / single constellation (e.g. the common GPS L1 C/A devices on current PND's or smartphones) to multi-frequency / multi-constellation (e.g. L-band GPS/Galileo/GLONASS capable high-end survey receivers).
*<b>Atmospheric</b>: Atmospheric delays that affect the signal during its propagation have a significant impact on the accuracy of the receiver measurements; therefore solution accuracy is directly linked to the receiver’s ability to correct for these delays. The most significant atmospheric delays are caused by the [[Ionospheric Delay|ionosphere]] and the [[Tropospheric Delay|troposphere]].


*<b>Assisting Sources</b>: Several external or assistance information sources can be taken into account at system design, since there is a straightforward impact on resources and solution computation. If the use of augmentation (SBAS) or differential (DGPS) data is envisaged, the receiver must be prepared to interface and use the information provided from such systems. Other external interfaces and aiding sensors can be coupled to a receiver, such as inertial sensors<ref>[[wikipedia:Inertial measurement unit]]</ref> (IMU and INS), or even the means to get external aiding information (e.g. accessing the internet through WiFi or GPRS/UMTS).
*<b>Operation Conditions</b>: Factors such as temperature, humidity, water resistance, shock and vibration ranges depend on the application. This has an influence not only on the choice of the platform (see below), but also on the casing (e.g. ruggedization, radome) and applicable standards (e.g. if subject to certification). As an example, space receivers will have to cope with huge levels of vibration (e.g. during launch) and they will be submitted to highly inauspicious environments (e.g. radiations in space).


*<b>Hardware Platform</b>: On a physical platform point of view, several design considerations are made in terms of the hardware host platform, user interface design, storage capability, power/battery consumption, electromagnetic compatibility, or portability. The underlying platform for a GNSS receiver can be an ASIC, FPGA, DSP, CPU, hardware/software defined, or a combination of these and other technologies. Table 1<ref>Hein, G., Pany, T., Wallner, S., Won, J., <i>"Platforms for a future GNSS receiver - A discussion of ASIC, FPGA, and DSP technologies"</i>, Working Papers, InsideGNSS, March 2006.</ref> below shows an assessment of the advantages and disadvantages of each approach.
==Application Constraints==
*<b>Receiver Dynamics</b>: receiver dynamics may affect the received signal (e.g. increasing the range of Doppler frequencies of the incoming signals). In such applications, the design of the receiver needs to cope with such requirements. As an example, a stationary receiver is expected to handle Doppler frequencies within the range of ±4 kHz, but this value is largely exceeded in GPS-guided ballistic applications. These considerations will also have an impact on the [[Tracking Loops|tracking loops]] since the integration times must take these factors into consideration.


*<b>Military applications</b>: legacy military applications use the [[GPS signal description|GPS Precise Position Service (PPS)]] which implies encryption capabilities and dual frequency receivers. Furthermore, (un)intentional interference is a major concern for military applications, since the receiver will likely have to operate in an environment where jammers and spoofers are present. Interference mitigation techniques are therefore usually welcomed for these applications.
*<b>Aeronautical applications</b>: the main challenge in the aeronautical domain is concentrated in the landing and taking-off phases, not only due to the required accuracy but mostly because of the need for integrity, due to its being a safety critical application. Furthermore, interference in the aeronautical band is expected in most airport vicinities, e.g. DME/ TACAN pulses in the L5 band.
*<b>Professional applications</b>: professional applications usually have sub-metric accuracy requirements. In addition, end-users use accurate GNSS receiver solutions for a final purpose (e.g. [[Precision Agriculture|precision agriculture]] and [[Space-time Metrology|space-time metrology]]). Therefore these applications often require a great deal of dedicated software customisation, mostly in the [[Applications Processing|application block]] to ensure the interface between the receiver and the final user.
==Hardware Platform==
From a physical point of view, several design considerations are made in terms of the hardware host platform, user interface design, storage capability, power/battery consumption, electromagnetic compatibility, or portability. Common underlying platforms for a GNSS receiver are ASIC, FPGA, DSP, CPU, hardware/software defined, or a combination of these (and other) technologies. Table 1<ref>Hein, G., Pany, T., Wallner, S., Won, J., <i>"Platforms for a future GNSS receiver - A discussion of ASIC, FPGA, and DSP technologies"</i>, Working Papers, InsideGNSS, March 2006.</ref> below shows the comparative analysis of the platform technologies.


{| border="1" align="center" cellpadding="5" style="text-align: center; font-size: 11px;"
{| border="1" align="center" cellpadding="5" style="text-align: center; font-size: 11px;"

Revision as of 16:49, 12 April 2011


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


Receiver characteristics and design are strongly related to the application at hand. In fact, the target application requirements are actually the main driver to a given receiver architecture and design decisions and therefore the selection of an adequate receiver usually underlies a large set of trade-offs.

Environmental Constraints

The surrounding environment influences the receiver behaviour in terms of performance, some examples are:

  • Multipath: GNSS signals can be affected by multipath, whenever the reflection of the SIS signal on surrounding surfaces distorts the received signal or even generates a non-line-of-sight ray. Multipath mitigation techniques may be implemented in the receiver, at the cost of increasing the processing load. Conversely, it may be beneficial to process NLOS reflected signals for improving availability while sacrificing accuracy. The trade-off “availability vs accuracy” will rely mainly on the receiver application. For non-critical road applications in urban environments, for example, availability may be more important than accuracy, since the receiver often makes use of map matching techniques to extrapolate its position and therefore tracking of NLOS may come as a design decision, despite the large errors introduced in the final solution.
  • Interference: in some applications it may be possible to predict that a certain type of interference will be present in some locations. An example is the case of aeronautical applications, where it is foreseen that TACAN/ DME beacons will cause pulse interference in the L5/ E5a band. In this case, the receiver may consider including techniques of pulse interference mitigation in the front end (link to front end). Another example to be considered are the case of some military applications that use antenna arrays and beam-forming to insert nulls in the radiation diagram of the antenna in the direction of an interferer whose position is known a-priori or detected dynamically.
  • Atmospheric: Atmospheric delays that affect the signal during its propagation have a significant impact on the accuracy of the receiver measurements; therefore solution accuracy is directly linked to the receiver’s ability to correct for these delays. The most significant atmospheric delays are caused by the ionosphere and the troposphere.
  • Operation Conditions: Factors such as temperature, humidity, water resistance, shock and vibration ranges depend on the application. This has an influence not only on the choice of the platform (see below), but also on the casing (e.g. ruggedization, radome) and applicable standards (e.g. if subject to certification). As an example, space receivers will have to cope with huge levels of vibration (e.g. during launch) and they will be submitted to highly inauspicious environments (e.g. radiations in space).

Application Constraints

  • Receiver Dynamics: receiver dynamics may affect the received signal (e.g. increasing the range of Doppler frequencies of the incoming signals). In such applications, the design of the receiver needs to cope with such requirements. As an example, a stationary receiver is expected to handle Doppler frequencies within the range of ±4 kHz, but this value is largely exceeded in GPS-guided ballistic applications. These considerations will also have an impact on the tracking loops since the integration times must take these factors into consideration.
  • Military applications: legacy military applications use the GPS Precise Position Service (PPS) which implies encryption capabilities and dual frequency receivers. Furthermore, (un)intentional interference is a major concern for military applications, since the receiver will likely have to operate in an environment where jammers and spoofers are present. Interference mitigation techniques are therefore usually welcomed for these applications.
  • Aeronautical applications: the main challenge in the aeronautical domain is concentrated in the landing and taking-off phases, not only due to the required accuracy but mostly because of the need for integrity, due to its being a safety critical application. Furthermore, interference in the aeronautical band is expected in most airport vicinities, e.g. DME/ TACAN pulses in the L5 band.
  • Professional applications: professional applications usually have sub-metric accuracy requirements. In addition, end-users use accurate GNSS receiver solutions for a final purpose (e.g. precision agriculture and space-time metrology). Therefore these applications often require a great deal of dedicated software customisation, mostly in the application block to ensure the interface between the receiver and the final user.

Hardware Platform

From a physical point of view, several design considerations are made in terms of the hardware host platform, user interface design, storage capability, power/battery consumption, electromagnetic compatibility, or portability. Common underlying platforms for a GNSS receiver are ASIC, FPGA, DSP, CPU, hardware/software defined, or a combination of these (and other) technologies. Table 1[1] below shows the comparative analysis of the platform technologies.

Table 1: GNSS technology comparison, from (++) major advantage to (--) major disadvantage.
Technology Development Costs Performance Power Consumption Single Unit Costs Flexibility
ASIC -- ++ ++ ++ --
FPGA - ++ + - +
DSP / CPU ++ + / ++ + / -- + / - ++
Hybrid FPGA / CPU + ++ + - +


Table 1[2] presents an order of magnitude of the 3-D position/time errors achieved with different types of receivers, both for Standard Positioning Service (SPS) and Precise Positioning Service (PPS) using legacy GPS. Note that this table is valid for GPS only and it is provided here for illustrative purposes[3].


Table 1: Comparative 95% three-dimensional position/time errors across various receivers.
  SPS PPS
  Best Location Median Location Worst Location Best Location Median Location Worst Location
Handhelp (best 4-SV solution) 16m 32m 72m 10m 30m 71m
Handhelp (AIV solution) 11m 25m 54m 8m 23m 53m
Mobile (land/marine vehicle) 7m 23m 53m N/A N/A N/A
Aviation receiver (AIV, RAIM, tightly coupled with INS) 7m 24m 55m 4m 5m 6m
Survey receiver (dual-frequency, real-time performance) 3m 4m 5m 3m 4m 5m
Aviation receiver dynamic time transfer performance 14ns 45ns 105ns 12ns 13ns 14ns
Time transfer receiver static time transfer performance 10ns 19ns 35ns 10ns 10ns 11ns

Related articles

References

  1. ^ Hein, G., Pany, T., Wallner, S., Won, J., "Platforms for a future GNSS receiver - A discussion of ASIC, FPGA, and DSP technologies", Working Papers, InsideGNSS, March 2006.
  2. ^ Kaplan, E.D. et al, "Understanding GPS: Principles and Applications", second edition, chapter 7, section 7.7.
  3. ^ For further information on the accuracy of each of the GNSS, please refer to the applicable sections.