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

Galileo Receivers: Difference between revisions

From Navipedia
Jump to navigation Jump to search
No edit summary
 
(21 intermediate revisions by 4 users not shown)
Line 4: Line 4:
|Level=Intermediate
|Level=Intermediate
|YearOfPublication=2011
|YearOfPublication=2011
|Logo=GMV
|Title={{PAGENAME}}
|Title={{PAGENAME}}
}}
}}
The [[GALILEO General Introduction|Galileo]] System will be an independent, global, European-controlled, satellite-based navigation system and will provide a number of guaranteed services to users equipped with Galileo-compatible receivers.  
The [[GALILEO General Introduction|Galileo]] System is an independent, global, European-controlled, satellite-based navigation system and provides a number of services to users equipped with Galileo-compatible receivers.  


Basic elements of a generic [[GNSS Receivers General Introduction|GNSS Receiver]] are an antenna with pre-amplification, an L-band radio frequency section, a microprocessor, an intermediate-precision oscillator, a feeding source, some memory for data storage, and an interface with the user. The calculated position is referred to the antenna phase centre.
Basic elements of a generic [[GNSS Receivers General Introduction|GNSS Receiver]] are an antenna with pre-amplification, an L-band radio frequency section, a microprocessor, an intermediate-precision oscillator, a feeding source, some memory for data storage, and an interface with the user. The calculated position is referred to the antenna phase centre.
Line 12: Line 13:
==Galileo receivers==
==Galileo receivers==
[[File:ArchitectureGalileoReceiver.PNG|450px|A Galileo Acquisition Receiver Architecture|right|thumb]]
[[File:ArchitectureGalileoReceiver.PNG|450px|A Galileo Acquisition Receiver Architecture|right|thumb]]
The Galileo global navigation satellite system will employ many new methods and technologies to offer superior performance and reliability. Development of the advanced receivers required to make use of the system is continuing.<ref name="EsaGalileoweb">[http://www.esa.int/esaNA/SEMY800DU8E_galileo_0.html ESA Galileo web page]</ref>
The Galileo global navigation satellite system employs many new methods and technologies to offer superior performance and reliability. Development of the advanced receivers required to make use of the system is continuing.<ref name="EsaGalileoweb">[http://www.esa.int/esaNA/SEMY800DU8E_galileo_0.html ESA Galileo web page]</ref>


A GALILEO Receiver is a device capable of determining a navigation solution by processing the signal broadcasted by Galileo satellites. Once the signal is acquired and tracked, the receiver application decodes the navigation message. The navigation data contain all the parameters that enable the user to perform positioning service. The four types of data needed to perform positioning are:<ref name="SIS_ICD">[http://ec.europa.eu/enterprise/policies/satnav/galileo/files/galileo-os-sis-icd-issue1-revision1_en.pdf Galileo OS SIS ICD Issue 1 Revision 1 September 2010e]</ref>
A GALILEO Receiver is a device capable of determining a navigation solution by processing the signal broadcasted by Galileo satellites. Once the signal is acquired and tracked, the receiver application decodes the navigation message. The navigation data contain all the parameters that enable the user to perform positioning service. Data needed to perform positioning:<ref name="OS-SDD">[https://www.gsc-europa.eu/system/files/galileo_documents/Galileo-OS-SDD.pdf Galileo Open Service - Service Definition Document]</ref>
# Ephemeris which are needed to indicate the position of the satellite to the user receiver.
# Ephemeris which are needed to compute the position of the satellite to the user receiver.  
# Time and clock correction parameters which are needed to compute pseudo-range.
# Time and clock correction parameters which are needed to compute satellite clock offsets and time conversions.  
# Service parameters which are needed to identify the set of navigation data, satellites, and indicators of the signal health.
# Service parameters with satellite health.
# Almanac which are used to compute the position of all the satellites in the constellation with a reduced accuracy, so that the receivers improve the time needed for the initial satellite acquisition process.
# The ionospheric parameters model, needed for single-frequency users.
# Almanac which allow less precise computation of the position of all the satellites in the constellation to facilitate the initial acquisition of the signals by the receiver.  


For single frequency receivers, the Broadcast Group Delays and Ionospheric parameters are also needed.
For single frequency receivers, the Broadcast Group Delays are also needed.
Three receiver development activities have been initiated within the Galileo programme, addressing the different needs of the system development process and covering the range of signals and services that will be offered.
 
Activities in receiver development are in the following areas:<ref name="EsaGalileoweb"></ref>
:
* test user segment;
* receivers for the signals transmitted by the first, experimental satellites;
* receivers for the Galileo receiver chain.


Up-to-date ephemeris are needed to indicate the position of the satellite to the user receiver. Time and clock correction parameters for all the satellites are needed to compute pseudo-range. Receivers must retrieve the values of navigation parameters relevant to the type of navigation solution to be computed from the most recent navigation data set broadcast on a Healthy SIS by the Galileo system after the start of the current receiver operation. The navigation performance can be increased by implementing fault detection and isolation algorithms, as those based on the consistency of redundant pseudorange data sets (such as Receiver Autonomous Integrity Monitoring algorithms)<ref name="OS-SDD"/>.


==Particularities==
==Particularities==
Line 35: Line 30:
In an analogous way, each system has its own [[Time References in GNSS| time reference]] defined by the respective control segments; the time reference for Galileo is called “Galileo System Time” (GST).
In an analogous way, each system has its own [[Time References in GNSS| time reference]] defined by the respective control segments; the time reference for Galileo is called “Galileo System Time” (GST).


Each GNSS System transmits its own navigation message, defined in the respective Signal In Space Interface Control Documents, SIS ICD. As an example, the satellites transmit information that allows the receiver to compute their positions. For the case of Galileo (in-line with GPS but unlike GLONASS), the satellites transmit the orbit parameters as updated by the Ground Segment and refreshed every 3 hours. The Galileo receiver then [[GPS and Galileo Satellite Coordinates Computation| computes the satellite position]] based on these transmitted ephemeris parameters.
Each GNSS System transmits its own navigation message, defined in the respective Signal In Space Interface Control Documents, SIS ICD<ref name="SIS_ICD">[https://www.gsc-europa.eu/sites/default/files/sites/all/files/Galileo_OS_SIS_ICD_v2.0.pdf Applicable Galileo Open Service – SIS ICD]</ref>. As an example, the satellites transmit information that allows the receiver to compute their positions. For the case of Galileo (in-line with GPS but unlike GLONASS), the satellites transmit the orbit parameters as updated by the Ground Segment and refreshed every 3 hours (in nominal operations). The Galileo receiver then [[GPS and Galileo Satellite Coordinates Computation| computes the satellite position]] based on these transmitted ephemeris parameters.


Another distinction regarding the transmitted navigation message with impact on the receiver is the ionospheric parameters transmitted to support the single frequency receiver in computing the ionospheric error; Galileo uses the [[NeQuick Ionospheric Model]].
Another distinction regarding the transmitted navigation message with impact on the receiver is the ionospheric parameters transmitted to support the single frequency receiver in computing the ionospheric error; Galileo uses the [[NeQuick Ionospheric Model]].


GNSS signals modulation, structure, navigation message contents and formats are often different among signals from the same system and from different systems. Most of these characteristics are easily implemented at the receiver (e.g. requiring only “software modifications”, such as the use of different PRN codes or the ability to cope with different message structures). The main difference among GNSS receivers falls into the specific characteristics that have impact at RF level, such as the [[CDMA FDMA Techniques| Multiple Access Techniques]] employed. Galileo (as GPS and COMPASS) uses CDMA techniques allowing a simpler RF module (than for example GLONASS), since all signals in the same frequency band have a common carrier.
GNSS signals modulation, structure, navigation message contents and formats are often different among signals from the same system and from different systems. Most of these characteristics are easily implemented at the receiver (e.g. requiring only “software modifications”, such as the use of different PRN codes or the ability to cope with different message structures). The main difference among GNSS receivers falls into the specific characteristics that have impact at RF level, such as the [[CDMA FDMA Techniques| Multiple Access Techniques]] employed. Galileo (as GPS and BeiDou) uses CDMA techniques allowing a simpler RF module (than for example GLONASS), since all signals in the same frequency band have a common carrier.
 
It should be noted that the current trend consists on facilitating the access of each system to the receivers, i.e. fomenting multi-constellation receivers. Hence, most discussions and agreements among the systems’ responsibles are conducted in the sense of taking this effort out of the user segment, focusing on [[Principles of Compatibility among GNSS| compatibility]] and [[Principles of Interoperability among GNSS| interoperability]] aspects in the system design.


It should be noted that the current trend consists on facilitating the access of each system to the receivers, i.e. fomenting multi-constellation receivers. Hence, most discussions and agreements among the systems’ responsible are conducted in the sense of taking this effort out of the user segment, focusing on [[Principles of Compatibility among GNSS| compatibility]] and [[Principles of Interoperability among GNSS| interoperability]] aspects in the system design.


==Test user segment==
The test user segment is being used for system validation and signal experimentation. Two parallel developments have been performed, with the aim of securing equipment availability and achieving the highest confidence in the results. The test user segment consists of:<ref name="EsaGalileoweb"/>
* a test user receiver for the [[Galileo Open Service (OS)|Open Service]], [[Galileo Commercial Service (CS)|Commercial Service]] and [[Galileo Safety of Life (SoL)|Safety-Of-Life Service]];
* a test user receiver for the [[Galileo Public Regulated Service (PRS)|Public Regulated Service (PRS)]];
* [[Galileo Search and Rescue Service |Search and Rescue (SAR)]] test beacon equipment;
* test support tools, such as a simulator for the satellite constellation.
The receivers are based on a highly flexible software-defined concept implementing 14 different receiver configurations. They are able to emulate different receiver types and provide a variety of internal measurements when combined with an analysis sub-system running on an attached laptop computer.
==Experimental satellite receivers==
These receivers are being used to receive the signals that are transmitted by the first, experimental satellites GIOVE. They serve both as reference receivers for Galileo sensor stations and as experimental receivers for field tests.


==Galileo receiver chain==  
==Galileo receiver chain==  
Galileo sensor stations will be equipped with high-performance, ultra-reliable receivers. The stations provide measurement data to the Galileo system central processing facilities for establishing system integrity and performing satellite orbit determination and time synchronisation.  
Galileo sensor stations are equipped with high-performance, ultra-reliable receivers. The stations provide measurement data to the Galileo system central processing facilities for establishing system integrity and performing satellite orbit determination and time synchronisation.  
    
    
==Receivers==  
==Receivers==  


GNSS Receivers manufacturers have already made multi-constellation receivers designed for a variety of [[GNSS Applications|applications]]. These receivers support a wide range of satellite signals, including Galileo signals in E1 and E5 bands.  
GNSS Receivers manufacturers have already made multi-constellation receivers designed for a variety of [[GNSS Applications|applications]]. These receivers support a wide range of satellite signals, including Galileo signals in E1 and E5 bands. Examples for devices that implement Galileo and user receiver technology trends can be found on the GSA website and in relevant GSA publications such as Market<ref name="GSA-Market">[https://www.gsa.europa.eu/market/gnss-market GSA Market website]</ref> and User Technology reports<ref name="GSA-User-Tech">[https://www.gsa.europa.eu/european-gnss/gnss-market/gnss-user-technology-report GSA User Technology Report]</ref> respectively.
 
===Commercial Receivers===
 
Among the companies developing multi-constellation commercial receivers, both in OEM Receiver Boards and/or Enclosures Receivers already on-sale, we can find (non exhaustive list):
 
*[http://www.septentrio.com/products/receivers/ Septentrio]
*[http://www.novatel.com/products/gnss-receivers/ Novatel]
*[http://www.trimble.com/srv_new_era.shtml Trimble]
*[http://www.leica-geosystems.com/en/Leica-GRX1200-Series_5547.htm Leica]
*[http://www.maxim-ic.com/datasheet/index.mvp/id/5241 Maxim]
*[http://www.javad.com/jgnss/products/receivers/delta.html Javad]
*[http://www.topcon.co.jp/en/positioning/products/product/gnss/ TopCon]
 
The corresponding datasheet for each receiver (available in the company website) claims Galileo receivers compliant to Galileo Open Service SIS ICD<ref name="SIS_ICD"/>.
 
===Scientific/ Space Receivers===
 
A few examples of scientific and space receivers:
*[http://payloadsystems.esa.int/static/TEC-ETN/receivers.html GPS/Galileo miniaturised space Rx ]
 
The is more information on [[Space Applications]] in NAVIPEDIA.
 
==First achievements==
The objectives of the initial part of the design phase for the test user segment have been fully achieved. A prototype receiver has been constructed, which is capable of receiving all Galileo signal components on all carriers defined in the current specification. The feasibility of acquiring and tracking the new Galileo signals has been proven.<ref name="EsaGalileoweb"/>


Prototype receivers have also been used for verification of the payloads on the experimental satellites, GIOVE-A and GIOVE-B. They are also being used for validation of the satellite constellation simulator, which emulates the signals as generated by the satellites and modified by environmental effects (such as atmospheric effects, multi-path reception and interference), resulting in a signal that a user receiver would see on the ground.
   
   
The Open Service Interface Control Document (ICD) for Galileo is available on the European Commission website <ref>[http://ec.europa.eu/enterprise/policies/satnav/galileo/open-service/index_en.htm European Commission Galileo website]</ref>, so receiver manufacturers can already work to prepare the acquisition of real Galileo data.
The Open Service Interface Control Document (ICD) for Galileo is available<ref name="SIS_ICD"></ref>, so receiver manufacturers can already work to prepare the acquisition of real Galileo data.
Furthermore, the European GNSS Agency (GSA) has been supporting a number of activities within the user segment <ref> http://www.gsa.europa.eu/</ref>.
Furthermore, the European GNSS Agency (GSA) has been supporting a number of activities within the user segment<ref>[https://www.gsa.europa.eu/ European GNSS Agency (GSA)]</ref>.


==References==
==References==
<references/>
<references/>


[[Category:GALILEO|Receivers]]
[[Category:GALILEO]]
[[Category:GALILEO Receivers]]
[[Category:GALILEO Receivers]]

Latest revision as of 09:14, 17 May 2021


GALILEOGALILEO
Title Galileo Receivers
Edited by GMV
Level Intermediate
Year of Publication 2011
Logo GMV.png

The Galileo System is an independent, global, European-controlled, satellite-based navigation system and provides a number of services to users equipped with Galileo-compatible receivers.

Basic elements of a generic GNSS Receiver are an antenna with pre-amplification, an L-band radio frequency section, a microprocessor, an intermediate-precision oscillator, a feeding source, some memory for data storage, and an interface with the user. The calculated position is referred to the antenna phase centre.

Galileo receivers

A Galileo Acquisition Receiver Architecture

The Galileo global navigation satellite system employs many new methods and technologies to offer superior performance and reliability. Development of the advanced receivers required to make use of the system is continuing.[1]

A GALILEO Receiver is a device capable of determining a navigation solution by processing the signal broadcasted by Galileo satellites. Once the signal is acquired and tracked, the receiver application decodes the navigation message. The navigation data contain all the parameters that enable the user to perform positioning service. Data needed to perform positioning:[2]

  1. Ephemeris which are needed to compute the position of the satellite to the user receiver.
  2. Time and clock correction parameters which are needed to compute satellite clock offsets and time conversions.
  3. Service parameters with satellite health.
  4. The ionospheric parameters model, needed for single-frequency users.
  5. Almanac which allow less precise computation of the position of all the satellites in the constellation to facilitate the initial acquisition of the signals by the receiver.

For single frequency receivers, the Broadcast Group Delays are also needed.

Up-to-date ephemeris are needed to indicate the position of the satellite to the user receiver. Time and clock correction parameters for all the satellites are needed to compute pseudo-range. Receivers must retrieve the values of navigation parameters relevant to the type of navigation solution to be computed from the most recent navigation data set broadcast on a Healthy SIS by the Galileo system after the start of the current receiver operation. The navigation performance can be increased by implementing fault detection and isolation algorithms, as those based on the consistency of redundant pseudorange data sets (such as Receiver Autonomous Integrity Monitoring algorithms)[2].

Particularities

Each GNSS system uses a specific Reference Frame; although a multi-constellation receiver is able to convert all information to the same common frame, a Galileo-only receiver uses the Galileo GTRF reference frame. In an analogous way, each system has its own time reference defined by the respective control segments; the time reference for Galileo is called “Galileo System Time” (GST).

Each GNSS System transmits its own navigation message, defined in the respective Signal In Space Interface Control Documents, SIS ICD[3]. As an example, the satellites transmit information that allows the receiver to compute their positions. For the case of Galileo (in-line with GPS but unlike GLONASS), the satellites transmit the orbit parameters as updated by the Ground Segment and refreshed every 3 hours (in nominal operations). The Galileo receiver then computes the satellite position based on these transmitted ephemeris parameters.

Another distinction regarding the transmitted navigation message with impact on the receiver is the ionospheric parameters transmitted to support the single frequency receiver in computing the ionospheric error; Galileo uses the NeQuick Ionospheric Model.

GNSS signals modulation, structure, navigation message contents and formats are often different among signals from the same system and from different systems. Most of these characteristics are easily implemented at the receiver (e.g. requiring only “software modifications”, such as the use of different PRN codes or the ability to cope with different message structures). The main difference among GNSS receivers falls into the specific characteristics that have impact at RF level, such as the Multiple Access Techniques employed. Galileo (as GPS and BeiDou) uses CDMA techniques allowing a simpler RF module (than for example GLONASS), since all signals in the same frequency band have a common carrier.

It should be noted that the current trend consists on facilitating the access of each system to the receivers, i.e. fomenting multi-constellation receivers. Hence, most discussions and agreements among the systems’ responsible are conducted in the sense of taking this effort out of the user segment, focusing on compatibility and interoperability aspects in the system design.


Galileo receiver chain

Galileo sensor stations are equipped with high-performance, ultra-reliable receivers. The stations provide measurement data to the Galileo system central processing facilities for establishing system integrity and performing satellite orbit determination and time synchronisation.

Receivers

GNSS Receivers manufacturers have already made multi-constellation receivers designed for a variety of applications. These receivers support a wide range of satellite signals, including Galileo signals in E1 and E5 bands. Examples for devices that implement Galileo and user receiver technology trends can be found on the GSA website and in relevant GSA publications such as Market[4] and User Technology reports[5] respectively.


The Open Service Interface Control Document (ICD) for Galileo is available[3], so receiver manufacturers can already work to prepare the acquisition of real Galileo data. Furthermore, the European GNSS Agency (GSA) has been supporting a number of activities within the user segment[6].

References