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

EGNOS Architecture: Difference between revisions

From Navipedia
Jump to navigation Jump to search
No edit summary
No edit summary
 
(46 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Article Infobox2
{{Article Infobox2
|Category=EGNOS
|Category=EGNOS
|Title={{PAGENAME}}
|Editors=GMV
|Authors=GMV.
|Level=Basic
|Level=Basic
|YearOfPublication=2011
|YearOfPublication=2011
|Logo=GMV
|Logo=GMV
|Title={{PAGENAME}}
}}
}}
The goal of [[EGNOS General Introduction|EGNOS]]  (European Geostationary Navigation Overlay Service) is to augment GNSS in order to improve the navigation performances in terms of accuracy and integrity (with the required levels of availability and continuity of service) over the European Civil Aviation Conference (ECAC) Region and to be expandable over neighbouring regions. Current EGNOS only augments GPS satellites on L1 signal.


The goal of [[EGNOS General Introduction|EGNOS]]  (European Geostationary Navigation Overlay Service) is to augment the [GPS Introduction|GPS]] in order to improve the navigation performances in terms of accuracy and integrity (with the required levels of availability and continuity of service) over the European Civil Aviation Conference (ECAC) Region and to be expandable over neighbouring regions.  
These augmentations are obtained by providing orbit and clock corrections for GNSS satellites and also correcting the ionospheric delays affecting the signal paths to the users. The complex message broadcast by EGNOS GEOs also include Integrity data which allow to bound the remaining errors with a high level of confidence.


These augmentations are obtained by providing a GPS-like Geostationary Ranging service (R-GEO), by broadcasting precise Wide Area Differential corrections to correct for GPS, GLONASS and GEO orbit and clock errors and also to correct the ionospheric delays affecting the signal paths to the users. The complex message broadcast by EGNOS GEOs also include Integrity data which allow to bound the remaining errors with a high level of confidence. EGNOS has deployed its Advanced Operational Capability (AOC) using two existing INMARSAT-III navigation transponders (AOR-E and IOR-W) plus a navigation transponder on board of Artemis satellite.<ref name=" THE EGNOS SYSTEM ARCHITECTURE EXPLAINED">THE EGNOS SYSTEM ARCHITECTURE EXPLAINED; Didier Flament, Jean Poumailloux, Jean-Louis Damidaux, Stéphane Lannelongue Alcatel Alenia Space, France ; Javier Ventura-Traveset, P. Michel and C. Montefusco ; European Space Agency, EGNOS Project Office; </ref>
The EGNOS architecture is very complex and highly redundant. It is currently composed by more than 40 elements deployed in more than 20 countries. EGNOS has been designed to meet the international SBAS standards and performs the following tasks:
 
The EGNOS architecture is very complex and highly redundant. It is composed by 47 elements deployed onto 41 sites in 22 Countries. EGNOS has been designed to meet the international SBAS standards and performs the following tasks:
* Collect GPS/GLONASS/GEO signals and data.
* Collect GPS/GLONASS/GEO signals and data.
* Estimate the integrity data and WAD corrections for the service area.
* Estimate the integrity data and WAD (Wide Area Differential) corrections for the service area.
* Transmit to the users, via the GEO satellites, a GPS-like signal, augmented with integrity and correction messages.
* Transmit to the users, via the GEO satellites, a GPS-like signal, augmented with integrity and correction messages.
* Verify the correctness of these integrity and correction messages.
* Verify the correctness of these integrity and correction messages.
For the next generation of the EGNOS augmentation system (EGNOS V3), the GSA requested the complete overhaul of the EGNOS ground segment, which was becoming obsolete. This modernization programme will see the deployment of EGNOS V3 in ground stations at more than 50 sites in Europe, and surrounding countries.
The GSA also requested the development of new EGNOS capabilities to support the augmentation of a second GPS signal (L5) and of the Galileo signals E1-E5. Another requirement is that the system is made more robust, to deal with the growing number of users numbers and to reflect their increasing dependence on EGNOS and its ground applications - in some countries (e.g. France) instrument landing systems (ILS) are being decommissioned on several airports because the civil aviation authorities have decided instead to rely on EGNOS.
The current EGNOS augments the accuracy of GPS signals across Europe and informs users of their current reliability level within six seconds. EGNOS belongs to a family of systems called Satellite Based Augmentation Systems (SBAS).
EGNOS V3 is planned to provide the aviation community with advanced Safety of Life (SoL) services as well as new services to maritime and land users. EGNOS V3 will provide augmented operational SoL services over Europe that improve the accuracy and availability of user positioning services from existing Global Navigation Satellite Systems (Galileo and GPS) and provides crucial integrity messages to EGNOS users with alerts within a few seconds in case of system degradation, consolidating EGNOS’ position as one of the leading edge GNSS Systems in the future.
EGNOS V3 will thus offer improved SoL services performances (where people’s lives are potentially at stake) over Europe to Civil Aviation community and new applications for maritime or land users, and will improve robustness against increasing security risks, in particular cyber-security risks.
EGNOS V3 will ensure a full continuity of service for the next decade and will be within the first operational SBAS systems implementing the dual frequency and multi constellation world standard, with both GPS and Galileo, replacing EGNOS V2 which has been in operation since 2011.<ref name=" AIRBUS-EGNOS V3 RIMS+NLES Performance Enginee ">Analysis Of Safety Of Life Service Provision For The European GNSS Elements, EGPC-10-04-23-04, 16 April 2010, European GNSS Programmes Committee, European Commission </ref>


==Architecture Overview==
==Architecture Overview==
The EGNOS system is directly decomposed in its four segments, a Ground Segment, a Space Segment, a User segment and a Support Segment:<ref name=" EGNOS SoL SDD">[http://www.essp-sas.eu/service_definition_documents  EGNOS Safety of Life (SoL) Service Definition Document (SDD) ]</ref>


[[File:EGNOS_architecture.JPG| EGNOS functional architecture  |390px|thumb|right]]
[[File:EGNOS_architecture.JPG| EGNOS functional architecture  |300px|thumb|right]]
The EGNOS system is directly decomposed in its four segments, a Ground Segment, a Space Segment, a User Segment and a Support Segment:<ref name=" The EGNOS System Architecture explained">The EGNOS System Architecture explained; Didier Flament, Jean Poumailloux, Jean-Louis Damidaux, Stéphane Lannelongue Alcatel Alenia Space, France ; Javier Ventura-Traveset, P. Michel and C. Montefusco ; European Space Agency, EGNOS Project Office; </ref><ref name=" EGNOS SoL SDD">[http://www.essp-sas.eu/service_definition_documents  EGNOS Service Definition Documents (SDD) ]</ref>


* The [[EGNOS Ground Segment |Ground Segment]] is the real-time part of EGNOS. It computes precise differential corrections as well as the GEO ranging and makes all these information available to users through a broadcast by the Space Segment.
* The [[EGNOS Ground Segment |Ground Segment]] computes precise differential corrections and integrity bounds and makes all these information available to users through a broadcast by the Space Segment.
* The [[EGNOS Space Segment |Space segment]], using three GEO satellites, provides redundant data transmission channel to broadcast toward EGNOS users messages containing differential corrections with the associated integrity information. The GEO satellites additionally provide GPS-like ranging signal that is permanently steered and synchronised by the ground segment.
* The [[EGNOS Space Segment |Space segment]], using GEO satellites, provides redundant data transmission channel to broadcast toward EGNOS user messages containing differential corrections with the associated integrity information.  
* The [[EGNOS User Segment |User Segment]] is made of EGNOS receivers that enable EGNOS users to accurately compute their position.
* The [[EGNOS User Segment |User Segment]] is made of EGNOS receivers which enable EGNOS users to accurately compute their position.
* The Support segment contains off-line facilities listed hereafter:
* The Support Segment contains off-line facilities supporting activities such as performance analysis, troubleshooting, maintenance and qualification.
** PACF: Performance Assessment and Check-out Facility, provides support to EGNOS management in such area as performances analysis, troubleshooting, operational procedures as well as upgrade specification and validation, support to maintenance.
** ASQF: Application specific qualification facility provides civil aviation and aeronautical certification authorities with the tools to qualify validate and certify the different EGNOS applications.
** DVP: Development & Verification platform is used to validate and verify EGNOS requirements during the design phase. It contains simulation facilities, a real-time testbed and an assembly, integration and verification platform. The DVP is incorporated in PACF.


==EGNOS Space Segment==
==EGNOS Space Segment==


The EGNOS Space Segment comprises 3 GEO satellites broadcasting corrections and integrity information for GPS satellites in the L1 frequency band (1575,42 MHz). At the
The [[EGNOS Space Segment | EGNOS Space Segment]] comprises 3 GEO satellites broadcasting corrections and integrity information for GPS satellites in the L1 frequency band (1575,42 MHz).  
date of publication the 3 GEOs used by EGNOS are:<ref name=" THE EGNOS SYSTEM ARCHITECTURE EXPLAINED"/>
This configuration provides a high level of redundancy over the whole service area in case of a geostationary satellite link failure. The EGNOS operations are handled in such a way that, at any point in time, typically two of the three GEOs broadcast an operational signal, the others broadcasting test signal. Since it is only necessary to track a single GEO satellite link to benefit from the EGNOS SoL, this secures a switching capability in case of interruption and ensures a high level of continuity of service. The configuration of the GEOs in operation does not change frequently but possible updates are nevertheless reported to users by the EGNOS Service Provider.
 
{| style="#008542;background-color:#FDC82F;" cellpadding="7" cellspacing="0" border="1"
|-
! align="center"  |GEO Name || align="center" |  PRN Number  || align="center" |ID(NMEA) || align="center" |Orbital Slot
|-
| style="background-color:#FFFFFF;" ; align="center"  |'''ARTEMIS''' || style="background-color:#FFFFFF;" ; align="center"  |  124  || style="background-color:#FFFFFF;" ; align="center"  |37 || style="background-color:#FFFFFF;" ; align="center"  |21.5E
|-
|style="background-color:#FFFFFF;" ; align="center"  |'''INMARSAT AOR-E''' || style="background-color:#FFFFFF;" ; align="center"  |  120  || style="background-color:#FFFFFF;" ; align="center"  |33 || style="background-color:#FFFFFF;" ; align="center"  |15.5W
|-
|style="background-color:#FFFFFF;" ; align="center"  |'''INMARSAT IOR-W''' || style="background-color:#FFFFFF;" ; align="center"  |  126  || style="background-color:#FFFFFF;" ; align="center"  |39 || style="background-color:#FFFFFF;" ; align="center"  |25E
|}
This space segment confi guration provides a high level of redundancy over the whole service area in case of a geostationary satellite link failure. The EGNOS operations
are handled in such a way that, at any point in time, typically two of the three GEOs broadcast an operational signal. Since it is only necessary to track a single GEO
satellite link to benefi t from the EGNOS SoL, this secures a switching capability in case of interruption and ensures a high level of continuity of service.


It is intended that the EGNOS space segment will be replenished over time in order to maintain a similar level of redundancy. The exact orbital location of future satellites may
It is intended that the EGNOS space segment will be replenished over time in order to maintain a similar level of redundancy. The exact orbital location of future satellites may
vary, though this will not impact the service offered to users. Similarly, different PRN code numbers may be assigned to future GEOs. However, all SBAS user receivers
vary, though this will not impact the service offered to users. Similarly, different PRN code numbers may be assigned to future GEOs. However, all SBAS user receivers
are designed to automatically detect and use any code in a pre-allocated set reserved for SBAS. Such evolutions will therefore be transparent for end users and will not
are designed to automatically detect and use any code in a pre-allocated set reserved for SBAS. Such [[EGNOS_Future_and_Evolutions|evolutions]] will therefore be transparent for end users and will not
necessitate any human intervention or change of receiving equipment.
necessitate any human intervention or change of receiving equipment.
The GSA’s request for EGNOS V3 development is part of its overall EGNOS modernization program that also includes renewal of the space segment. As part of this program, the GSA contracted Eutelsat for the preparation and service provision phases of the EGNOS GEO-3 payload, to be hosted on the EUTELSAT 5.<ref name=" INSIDE-GNSS: EGNOS V3">[http://insidegnss.com/esa-airbus-sign-contract-for-egnos-v3-upgrades/ INSIDE-GNSS: EGNOS V3]</ref>


==EGNOS Ground Segment==
==EGNOS Ground Segment==
 
The [[EGNOS Ground Segment |EGNOS Ground Segment]] comprises a network of Ranging Integrity Monitoring Stations (RIMS), two Mission Control Centres (MCC), six Navigation Land Earth Stations (NLES), and the EGNOS Wide Area Network (EWAN) which provides the communication network for all the components of the Ground Segment. Two additional facilities are also deployed as part of the ground segment to support system operations and service provision, namely the Performance Assessment and Checkout Facility (PACF) and the Application Specific Qualification Facility (ASQF), which are operated by the EGNOS Service Provider.<ref name=" ESSP HomePage">[https://www.gsa.europa.eu/european-gnss/egnos/egnos-system  EGNOS System in EGNOS Service Provider website ]</ref>
The [[EGNOS Ground Segment |EGNOS Ground Segment]] comprises a network of Ranging Integrity Monitoring Stations (RIMS), four Mission Control Centres (MCC), six Navigation Land Earth Stations (NLES), and the EGNOS Wide Area Network (EWAN) which provides the communication network for all the components of the ground segment. Two additional
facilities are also deployed as part of the ground segment to support system operations and service provision, namely the Performance Assessment and Checkout Facility (PACF) and the Application Specific Qualification Facility (ASQF), which are operated by the EGNOS Service Provider (ESSP SAS).


The EGNOS system is a widely distributed and redundant system. Data flows from one subsystem to another subsystem have different level of criticality.
The EGNOS system is a widely distributed and redundant system. Data flows from one subsystem to another subsystem have different level of criticality.
Line 64: Line 59:
[[File:EGNOS_data_Flow.JPG| EGNOS Data flow  |350px|thumb|right]]
[[File:EGNOS_data_Flow.JPG| EGNOS Data flow  |350px|thumb|right]]


The main EGNOS functions are carried out by the Ground Segment through the following critical subsystems: the RIMS stations, the CPF units and the NLES stations. The Ground Segment is a periodic synchronous and pipelined system. The synchronisation of subsystems located in widely separated geographic places is referred to
The main EGNOS functions are carried out by the Ground Segment through the following critical subsystems: the RIMS stations, the CPF units and the NLES stations. The Ground Segment is a periodic synchronous and pipelined system. The synchronization of subsystems located in widely separated geographic places is referred to
the GPS time by means of GPS receivers providing a 1 PPS (one Pulse Per Second) synchronisation pulse to the associated subsystem.
the GPS time by means of GPS receivers providing a 1 PPS (one Pulse Per Second) synchronization pulse to the associated subsystem.


Another feature of the EGNOS Ground Segment is that all Monitoring and Control (M&C) functions performed by humans (non automatic functions) are centralised and implemented
Another feature of the EGNOS Ground Segment is that all Monitoring and Control (M&C) functions performed by humans (non-automatic functions) are centralized and implemented
in the CCF subsystems, which is outside of the critical data flow . Operators on duty in another CCF (hot backup) are ready to take over the system monitoring and control if the master CCF fails. Remaining two CCF (cold backup) can be reactivated if the master one fails.
in the CCF subsystems, which is outside of the critical data flow. Operators on duty in another CCF (hot backup) are ready to take over the system monitoring and control if the master CCF fails. Remaining two CCF (cold backup) can be reactivated if the master one fails.


In the EGNOS data flow representation, the real time critical data flow is indicated in red whereas the non-critical data flow is indicated in green.
In the EGNOS data flow representation, the real time critical data flow is indicated in red whereas the non-critical data flow is indicated in green.


The sub-systems involved in the processing of the critical data are responsible for the achievement of the main EGNOS system performance (accuracy, integrity, continuity, time to alarm, and service coverage) while the sub-systems involved in the management of non-critical data perform the Monitoring and Control (M&C) and archive functions.
The sub-systems involved in the processing of the critical data are responsible for the achievement of the main EGNOS system performance (accuracy, integrity, continuity, time to alarm, and service coverage) while the sub-systems involved in the management of non-critical data perform the Monitoring and Control (M&C) and archive functions.
The EGNOS Ground Segment includes the following support facilities (EGNOS Support Segment):
* PACF: Performance Assessment and Check-out Facility, provides support to EGNOS management in such area as performances analysis, troubleshooting, operational procedures as well as upgrade of specification and validation, and support to maintenance.
* ASQF: Application Specific Qualification Facility provides civil aviation and aeronautical certification authorities with the tools to qualify validate and certify the different EGNOS applications.
Due to the implementation of EGNOS V3, the RIMS and NLES performance engineering have to be updated in order to be responsible for:
*Monitoring the proper implementation of the RIMS and NLES specifications imposed by EGNOS V3 system.
*Characterizing the RIMS and NLES performances as achieved by the implemented RIMS and NLES (incl. characterization of RIMS and NLES environment) used as input for EGNOS V3 system performance analysis.
*Maintaining and updating RIMS and NLES specifications as needed to support EGNOS V3 system performance analysis (this includes survey of specifications provided as CFI by the customer (e.g. scintillation specifications, RIMS and NLES RFI environment specifications, User Rx standards (e.g. new L5 DFMC SBAS MOPS), survey of NLES specification provided by the Customer).


==EGNOS User Segment==
==EGNOS User Segment==
The [[EGNOS User Segment | EGNOS User Segment]] consists of the GNSS receivers that enable their users to accurately compute their positions using EGNOS corrections. It is important to bear in mind that a GNSS receiver only monitors signals sent by the satellites and does not establish any contact with them. Therefore, a GNSS receiver cannot be used by a third party to find out a user’s position without his knowledge.<ref name=" USER GUIDE FOR EGNOS APPLICATION DEVELOPERS">[http://www.cnes-csg.fr/automne_modules_files/standard/public/p7853_cb8d73df13dfd104092d3f8c5cc2062bguide_egnos_2011_GB_112_P.pdf  USER GUIDE FOR EGNOS APPLICATION DEVELOPERS ]</ref>


The [[EGNOS User Segment | EGNOS User Segment]] segment consists of the GPS receivers. It is important to bear in mind that a GPS receiver only monitors signals sent by the satellites and does not establish any contact with them. Therefore, a GPS receiver cannot be used by a third party to find out a user’s position without his knowledge.<ref name=" USER GUIDE FOR EGNOS APPLICATION DEVELOPERS">[http://ec.europa.eu/enterprise/policies/satnav/egnos/files/brochures-leaflets/egnos-user-guide_en.pdf   USER GUIDE FOR EGNOS APPLICATION DEVELOPERS ]</ref>
To receive EGNOS signals an EGNOS compatible receiver is required. There are many receivers available on the market from a variety of manufacturers.
An EGNOS receiver is like a GNSS receiver but with special software inside that allows the receiver to lock onto the code used by the EGNOS satellites and compute the EGNOS corrections to the GNSS signals. Apart from this, an EGNOS receiver is just like a GNSS receiver. This means that it can pick up GPS signals as well. An EGNOS receiver is the same size as a GPS receiver and uses the same type of antenna.<ref name=" ESA Navigation Site on EGNOS User Segment">[http://www.esa.int/esaNA/ESAQZ20VMOC_index_0.html   ESA Navigation Site on EGNOS User Segment ]</ref>


To receive EGNOS signals an EGNOS compatible receiver is required There are many receivers now already on the market from a variety of manufacturers.
To test the EGNOS receiver, special prototypes have been developed with extensive capabilities to log and analyze data.
An EGNOS receiver is like a GPS receiver but with special software inside that allows the receiver to lock onto the code used by the EGNOS satellites and compute the EGNOS corrections to the GPS signals. Apart from this, an EGNOS receiver is just like a GPS receiver. This means that it can pick up GPS signals as well. An EGNOS receiver is the same size as a GPS receiver and uses the same type of antenna.<ref name=" ESA Navigation Site on EGNOS User Segment">[http://www.esa.int/esaNA/ESAQZ20VMOC_index_0.html  ESA Navigation Site on EGNOS User Segment ]</ref>


To test the EGNOS receiver, special prototypes have been developed with extensive capabilities to log and analyze data.
EGNOS V3 will provide enhanced performances and robustness in the whole GEO broadcast area for those users equipped with standard space based augmentation system (SBAS) receivers capable of both Galileo and GPS. Moreover the baseline V3 system architecture will be modular and upgradeable in time in order to progressively accommodate and support a very wide span of brand new GNSS services for various user communities.<ref name=" DLR-Institute of Communications and Navigation">[https://www.dlr.de/kn/en/desktopdefault.aspx/tabid-4309/3222_read-32227/  DLR-Institute of Communications and Navigation]</ref>


==Notes==
==Notes==
Line 89: Line 95:


[[Category:EGNOS]]
[[Category:EGNOS]]
[[Category:EGNOS Architecture]]

Latest revision as of 14:08, 12 March 2020


EGNOSEGNOS
Title EGNOS Architecture
Edited by GMV
Level Basic
Year of Publication 2011
Logo GMV.png

The goal of EGNOS (European Geostationary Navigation Overlay Service) is to augment GNSS in order to improve the navigation performances in terms of accuracy and integrity (with the required levels of availability and continuity of service) over the European Civil Aviation Conference (ECAC) Region and to be expandable over neighbouring regions. Current EGNOS only augments GPS satellites on L1 signal.

These augmentations are obtained by providing orbit and clock corrections for GNSS satellites and also correcting the ionospheric delays affecting the signal paths to the users. The complex message broadcast by EGNOS GEOs also include Integrity data which allow to bound the remaining errors with a high level of confidence.

The EGNOS architecture is very complex and highly redundant. It is currently composed by more than 40 elements deployed in more than 20 countries. EGNOS has been designed to meet the international SBAS standards and performs the following tasks:

  • Collect GPS/GLONASS/GEO signals and data.
  • Estimate the integrity data and WAD (Wide Area Differential) corrections for the service area.
  • Transmit to the users, via the GEO satellites, a GPS-like signal, augmented with integrity and correction messages.
  • Verify the correctness of these integrity and correction messages.

For the next generation of the EGNOS augmentation system (EGNOS V3), the GSA requested the complete overhaul of the EGNOS ground segment, which was becoming obsolete. This modernization programme will see the deployment of EGNOS V3 in ground stations at more than 50 sites in Europe, and surrounding countries.

The GSA also requested the development of new EGNOS capabilities to support the augmentation of a second GPS signal (L5) and of the Galileo signals E1-E5. Another requirement is that the system is made more robust, to deal with the growing number of users numbers and to reflect their increasing dependence on EGNOS and its ground applications - in some countries (e.g. France) instrument landing systems (ILS) are being decommissioned on several airports because the civil aviation authorities have decided instead to rely on EGNOS.

The current EGNOS augments the accuracy of GPS signals across Europe and informs users of their current reliability level within six seconds. EGNOS belongs to a family of systems called Satellite Based Augmentation Systems (SBAS).

EGNOS V3 is planned to provide the aviation community with advanced Safety of Life (SoL) services as well as new services to maritime and land users. EGNOS V3 will provide augmented operational SoL services over Europe that improve the accuracy and availability of user positioning services from existing Global Navigation Satellite Systems (Galileo and GPS) and provides crucial integrity messages to EGNOS users with alerts within a few seconds in case of system degradation, consolidating EGNOS’ position as one of the leading edge GNSS Systems in the future.

EGNOS V3 will thus offer improved SoL services performances (where people’s lives are potentially at stake) over Europe to Civil Aviation community and new applications for maritime or land users, and will improve robustness against increasing security risks, in particular cyber-security risks.

EGNOS V3 will ensure a full continuity of service for the next decade and will be within the first operational SBAS systems implementing the dual frequency and multi constellation world standard, with both GPS and Galileo, replacing EGNOS V2 which has been in operation since 2011.[1]


Architecture Overview

EGNOS functional architecture

The EGNOS system is directly decomposed in its four segments, a Ground Segment, a Space Segment, a User Segment and a Support Segment:[2][3]

  • The Ground Segment computes precise differential corrections and integrity bounds and makes all these information available to users through a broadcast by the Space Segment.
  • The Space segment, using GEO satellites, provides redundant data transmission channel to broadcast toward EGNOS user messages containing differential corrections with the associated integrity information.
  • The User Segment is made of EGNOS receivers which enable EGNOS users to accurately compute their position.
  • The Support Segment contains off-line facilities supporting activities such as performance analysis, troubleshooting, maintenance and qualification.

EGNOS Space Segment

The EGNOS Space Segment comprises 3 GEO satellites broadcasting corrections and integrity information for GPS satellites in the L1 frequency band (1575,42 MHz). This configuration provides a high level of redundancy over the whole service area in case of a geostationary satellite link failure. The EGNOS operations are handled in such a way that, at any point in time, typically two of the three GEOs broadcast an operational signal, the others broadcasting test signal. Since it is only necessary to track a single GEO satellite link to benefit from the EGNOS SoL, this secures a switching capability in case of interruption and ensures a high level of continuity of service. The configuration of the GEOs in operation does not change frequently but possible updates are nevertheless reported to users by the EGNOS Service Provider.

It is intended that the EGNOS space segment will be replenished over time in order to maintain a similar level of redundancy. The exact orbital location of future satellites may vary, though this will not impact the service offered to users. Similarly, different PRN code numbers may be assigned to future GEOs. However, all SBAS user receivers are designed to automatically detect and use any code in a pre-allocated set reserved for SBAS. Such evolutions will therefore be transparent for end users and will not necessitate any human intervention or change of receiving equipment.

The GSA’s request for EGNOS V3 development is part of its overall EGNOS modernization program that also includes renewal of the space segment. As part of this program, the GSA contracted Eutelsat for the preparation and service provision phases of the EGNOS GEO-3 payload, to be hosted on the EUTELSAT 5.[4]

EGNOS Ground Segment

The EGNOS Ground Segment comprises a network of Ranging Integrity Monitoring Stations (RIMS), two Mission Control Centres (MCC), six Navigation Land Earth Stations (NLES), and the EGNOS Wide Area Network (EWAN) which provides the communication network for all the components of the Ground Segment. Two additional facilities are also deployed as part of the ground segment to support system operations and service provision, namely the Performance Assessment and Checkout Facility (PACF) and the Application Specific Qualification Facility (ASQF), which are operated by the EGNOS Service Provider.[5]

The EGNOS system is a widely distributed and redundant system. Data flows from one subsystem to another subsystem have different level of criticality.

EGNOS Data flow

The main EGNOS functions are carried out by the Ground Segment through the following critical subsystems: the RIMS stations, the CPF units and the NLES stations. The Ground Segment is a periodic synchronous and pipelined system. The synchronization of subsystems located in widely separated geographic places is referred to the GPS time by means of GPS receivers providing a 1 PPS (one Pulse Per Second) synchronization pulse to the associated subsystem.

Another feature of the EGNOS Ground Segment is that all Monitoring and Control (M&C) functions performed by humans (non-automatic functions) are centralized and implemented in the CCF subsystems, which is outside of the critical data flow. Operators on duty in another CCF (hot backup) are ready to take over the system monitoring and control if the master CCF fails. Remaining two CCF (cold backup) can be reactivated if the master one fails.

In the EGNOS data flow representation, the real time critical data flow is indicated in red whereas the non-critical data flow is indicated in green.

The sub-systems involved in the processing of the critical data are responsible for the achievement of the main EGNOS system performance (accuracy, integrity, continuity, time to alarm, and service coverage) while the sub-systems involved in the management of non-critical data perform the Monitoring and Control (M&C) and archive functions.

The EGNOS Ground Segment includes the following support facilities (EGNOS Support Segment):

  • PACF: Performance Assessment and Check-out Facility, provides support to EGNOS management in such area as performances analysis, troubleshooting, operational procedures as well as upgrade of specification and validation, and support to maintenance.
  • ASQF: Application Specific Qualification Facility provides civil aviation and aeronautical certification authorities with the tools to qualify validate and certify the different EGNOS applications.

Due to the implementation of EGNOS V3, the RIMS and NLES performance engineering have to be updated in order to be responsible for:

  • Monitoring the proper implementation of the RIMS and NLES specifications imposed by EGNOS V3 system.
  • Characterizing the RIMS and NLES performances as achieved by the implemented RIMS and NLES (incl. characterization of RIMS and NLES environment) used as input for EGNOS V3 system performance analysis.
  • Maintaining and updating RIMS and NLES specifications as needed to support EGNOS V3 system performance analysis (this includes survey of specifications provided as CFI by the customer (e.g. scintillation specifications, RIMS and NLES RFI environment specifications, User Rx standards (e.g. new L5 DFMC SBAS MOPS), survey of NLES specification provided by the Customer).

EGNOS User Segment

The EGNOS User Segment consists of the GNSS receivers that enable their users to accurately compute their positions using EGNOS corrections. It is important to bear in mind that a GNSS receiver only monitors signals sent by the satellites and does not establish any contact with them. Therefore, a GNSS receiver cannot be used by a third party to find out a user’s position without his knowledge.[6]

To receive EGNOS signals an EGNOS compatible receiver is required. There are many receivers available on the market from a variety of manufacturers. An EGNOS receiver is like a GNSS receiver but with special software inside that allows the receiver to lock onto the code used by the EGNOS satellites and compute the EGNOS corrections to the GNSS signals. Apart from this, an EGNOS receiver is just like a GNSS receiver. This means that it can pick up GPS signals as well. An EGNOS receiver is the same size as a GPS receiver and uses the same type of antenna.[7]

To test the EGNOS receiver, special prototypes have been developed with extensive capabilities to log and analyze data.

EGNOS V3 will provide enhanced performances and robustness in the whole GEO broadcast area for those users equipped with standard space based augmentation system (SBAS) receivers capable of both Galileo and GPS. Moreover the baseline V3 system architecture will be modular and upgradeable in time in order to progressively accommodate and support a very wide span of brand new GNSS services for various user communities.[8]

Notes

References

  1. ^ Analysis Of Safety Of Life Service Provision For The European GNSS Elements, EGPC-10-04-23-04, 16 April 2010, European GNSS Programmes Committee, European Commission
  2. ^ The EGNOS System Architecture explained; Didier Flament, Jean Poumailloux, Jean-Louis Damidaux, Stéphane Lannelongue Alcatel Alenia Space, France ; Javier Ventura-Traveset, P. Michel and C. Montefusco ; European Space Agency, EGNOS Project Office;
  3. ^ EGNOS Service Definition Documents (SDD)
  4. ^ INSIDE-GNSS: EGNOS V3
  5. ^ EGNOS System in EGNOS Service Provider website
  6. ^ USER GUIDE FOR EGNOS APPLICATION DEVELOPERS
  7. ^ ESA Navigation Site on EGNOS User Segment
  8. ^ DLR-Institute of Communications and Navigation