2006 space based augmentation systems

8/3/2019 2006 Space Based Augmentation Systems

http://slidepdf.com/reader/full/2006-space-based-augmentation-systems 1/65

1Copyright 2006 EUROCONTROL

Global Navigation Satellite SystemsGlobal Navigation Satellite SystemsGlobal Navigation Satellite SystemsGlobal Navigation Satellite Systems

Space Based Augmentation SystemsSpace Based Augmentation Systems




AgendaAgenda

Space Based Augmentation Systems -Principles

Implementations: EGNOS

Implementations: US A's WAAS

Implementations: Japan's MS AS




NAV32516.3602

Master Control Site

(MCS)

(x,y,z)

Atmospheric

Effects

(x,y,z)

(x,y,z)

Single Frequency Avionics

Reference Stations (RSs)

Dual or Single Frequency

Satellite Broadcast of:1. Vector Correction

2. µUse/Don¶t Use¶

3. Ranging SignalIndicated Location

True Location

SBAS: The PrincipleSBAS: The Principle




Lateral

Accuracy95%

Vertical

Accuracy95%(1)(3)

Integrity(2)

Time to

Alert (3)

Continuity(4)

Availability(5)

En-Route 2 NM (6) N/A 1-10-7/h 5 min 1-10

-4/h to

1-10-8

/h

0.99 to

0.99999

ER, Terminal 0.4 NM N/A 1-10-7

/h 15 s 1-10-4

/h to

1-10-8

/h

0.99 to

0.99999

Initial andIntermediate Approach,NPA, SID

220 m N/A 1-10-7

/h 10 s 1-10-4

/h to

1-10-8

/h

0.99 to

0.99999

APV-I 16.0 m 20 m 1-2x10-7

/hper

approach

10 s 1-8x10-6

in

any 15 s

0.99 to

0.99999

APV-II 16.0 m 8.0 m 6 s 1-8x10-6

inany 15 s

0.99 to0.99999

PA- CATI (8) 16.0 m 6.0 m to4.0 m (7)

6 s 1-8x10-6

inany 15 s

0.99 to0.99999

1-2x10-7

/hper

approach

1-2x10-7

/hper

ap

proach

Typical SBAS RequirementsTypical SBAS Requirements




Overview of SBAS ObjectivesOverview of SBAS Objectives

Augment GPS & Possibly GLONASS

Achieve Aviation Requirements With Added

± Integrity - monitoring and ³use/don¶t use´ message

± Accuracy - with differential corrections

± Availability & Continuity - with ranging signals

Serve En-route Down to Category I Precision

Approach Time Scales: Introduction beginning 2006+




Geostationary satellite

Uplink Corrections

Repeat,

Broadcast

Corrections

The Role of the Geostationary SatelliteThe Role of the Geostationary Satellite




GEOS Satellites in Service: ExamplesGEOS Satellites in Service: Examples

INMARS AT-III

± POR

± IOR

± AOR-W

± AOR-E

ARTEMIS

± Launch Failed

± Eventually reached correct orbit end of Jan 03




AOR-EAOR-E IORIOR

POR

AOR-WAOR-W

POR

ARTEMIS

INMARSAT III AND ARTEMIS Broadcast AreasINMARSAT III AND ARTEMIS Broadcast Areas




Three Interwoven Services (1)Three Interwoven Services (1)

Ranging ± the geostationary satellite(s) broadcasts a spread-

spectrum ranging signal

± avionics adds this ³GPS-like´ signal to the existing set of

GPS measurements

± improves availability and continuity

Integrity

± supporting ground network monitors the health of all SVs ± ³use/don¶t use´ warnings broadcast via geostationary

satellite(s)

± improves flight safety




Three Interwoven Services (2)Three Interwoven Services (2)

Accuracy ± ground network also develops differential corrections

for all SVs

± broadcast via geostationary satellites (along with

integrity data)

± separate corrections for SV clock, SV ephemeris &

ionosphere

± such a vector correction is valid over continental areas

± improves accuracy from 100 meters to better than 8

meters




Vertical Ionospheric Delay Estimated at Stanford University

(West Coast Region of United States)

-140-135

-130-125

-120-115

-110-105

2025

3035

4045

50550

1

2

3

4

5

Longitude (deg)Latitude (deg)

V e r t i c a l I o n o s

p h e r i c D e l a y ( m )

Local Time: 13:17:60

Elko

ArcataSan Diego

Stanford

Ionospheric Measurements: MCS OutputsIonospheric Measurements: MCS Outputs




GEO Navigation Signal CharacteristicsGEO Navigation Signal Characteristics

Frequency: 1575.42 MHz

Modulation: BPSK

PRN code: 1023 bit Gold codes with good

orthogonality to GPS codes

Data rate: 250 bit per second (encoded with

forward error correction to 500 bps

throughput) Polarisation: Right handed circular




GEO information useless (SBAS test mode)PRN MaskFast correctionsIntegrity informationFast corrections degradation factor

GEO ranging functions parametersDegradation parametersSBAS Network Time/UTC offset parametersGEO satellite almanacsIonospheric grid point masksMixed fast corrections/long term satellite error corrections

Long term satellite error correctionsIonospheric delay correctionsSBAS service messageNull MessageReserved

01

2-567

91012171824

25262763

Others

Type Contents

SBAS Messages TypesSBAS Messages Types




Availability of expected Positioning Accuracy for CONUS Region

A v a i l a b i l i t y

sv (metres)

0 50 100 150 200 250 3000%

90%

99%

99.9%

99.99%

99.999%

Stand-Alone GPSs = 32 m

Stand-Alone GPS

FullWAAS

and INMARS ATLimited-S A GPS

INMARS AT and

Predicted Performance Over CONUSPredicted Performance Over CONUS




Global Navigation Satellite SystemsGlobal Navigation Satellite SystemsGlobal Navigation Satellite SystemsGlobal Navigation Satellite Systems

Space Based Augmentation SystemsSpace Based Augmentation Systems




Problems at High LatitudesProblems at High Latitudes

Concern about the visibility of geostationary satellites atthe edge of the coverage footprints

Reception may be particularly difficult during aircraft

maneuvers

Reception is particularly critical during approach &landing

Eurocontrol organized flight trials:

± to investigate reception at high latitudes

± real flight data rather than simulation

± designed flight trials with UK CAA and DRA Bedford

± October 1994: trials conducted with DRA¶s BAC-1-11




Thule

SondrestromKeflavik

Svalbard

Tromso

TrondheimStockholm

Bergen

BoscombeDown

High Altitudes: Flight Trial RouteHigh Altitudes: Flight Trial Route




AgendaAgenda








What is EGNOS?What is EGNOS?

European implementation of SBAS

Operating using INMARS AT GEOs and ES A ARTEMIS

Aimed to provide:

± Integrity

± Continuity

± Accuracy

± Availability Use with GPS and GLONASS

Planned to be compatible WAAS, MS AS andGAGAN




EGNOS MilestonesEGNOS Milestones

AOC IMPLEMENTATION:

System Development

Deployment & Verification

Initial Operations

TEST BED:

Development & Integration

Verification

Operation

AOC INITIAL PHASE:

Baseline System Design

Early Trials

Preliminary System Design

96 97 98 99 00 01 02 03 04 05 06

ORR

PDR CDR FQR

PDR

MRRBSDR




EGNOS Timescale: Initial OperationsEGNOS Timescale: Initial Operations

ORR ODR

Operations

performance

Time (in months)

OQR

+3 +6 +12+9 +15

Ramp-up

Stabilization

Qualification

ESA Reqt

ESA Reqt

¨ ESA Reqt

2006 2007




Corrections for Accuracy

Ranging for Availability

Continuity and Integrity for Flight Safety

EGNOS: Service AreaEGNOS: Service Area

Geostationary

Broadcast Area




EGNOS AOC PhaseEGNOS AOC Phase

Advanced Operational Capability (AOC) ± Ranging function

± Ground Integrity function

± Wide Area Differential function ± Operations down to APV II

± 2006 onwards

System consists of:

± Space Segment

± Ground Segment




EGNOS FOCEGNOS FOC

Final Operational Capability (FOC)

± No longer considered

± Did not provide additional functionality

± Additional system components to increase

availability and continuity performance

± Sole means (Volpe Report) of operation, down

to CAT-I precision approach ± Originally planned 2 years after AOC




Mission requirements for civil aviation,

operational test and validation for aviation,

support for safety regulation.

Development - Deployment - Technical Validation.

Institutional and policy matters, the coordination of the implementation of a Transeuropean navigation

and positioning network, identification of user

requirements. Funding the navigation transponders.

European Tripartite AgreementEuropean Tripartite Agreement




Participating StatesParticipating States




NAV32516.3627

EC

EOIG

ES A

Financing EGNOS to Operational UseFinancing EGNOS to Operational Use

Total cost to Operational Readiness Review (Apr 04):

± ¼ 310 Million

Annual running costs:

± ¼ 33 Million (15% of GALILEO¶s costs)

Approval Procedure costs and additional expenses:

± ¼ 14.4 Million




Advantages of EGNOSAdvantages of EGNOS

NAV32516.3628

General:

± Technical

Enabled Europe to develop capability and know how

Enhance GPS and GLONASS services

Will be provided free (at outset!)

Will provide some guarantees

± Political

Completes first phase of European GNSS

Offers opportunities in developing countries withpoor infrastructure

A product of US, Russian and EU cooperation

Sectors

± Civil aviation has the most demanding requirements




EGNOS Expected PerformanceEGNOS Expected Performance

GEOs provide 3 additional ranging sources

3 satellites to fix position in 2 dimensions

± +/- 3 metres expected

4 satellites to fix position in 3 dimensions

± +/- 5 metres expected

Significant improvement in integrity expected

± Probability of SBAS not detecting a failure is 10-7

± RAIM will used to protect against local effects




GPS GLONASS

NLES

Transmits navigationand integrity data

Master Control Centre

Generates NAV signalProcesses integrityinformationProvides WADGNSS

corrections

Wide Area Ground Segment

Provides monitoring networkChecks integrityCollects GPS/GLONASS/GEOdata

NavigationReferenceSignal

(C-band)

NavigationSignals(L-band)

Geostationary

Satellites

EGNOS: System DesignEGNOS: System Design




EWAN

MCC 1 MCC 2 MCC 3 MCC 4

NLES

(x 6)

PACF ASQF DVP

RIMS

(x 34)

EGNOS: Ground Segment (1)EGNOS: Ground Segment (1)




RIMSRIMS NLESNLESMCCMCC

EGNOS: Ground Segment (2)EGNOS: Ground Segment (2)




EGNOS Representative RIMS LocationsEGNOS Representative RIMS Locations




EGNOS: Master Control Centres (MCC)EGNOS: Master Control Centres (MCC)

MCC: Master Control Centres

± Spain, UK, Germany and Italy

± Pre-planned rotation of MCC

Comprised of 2 parts:

± CPF ± CCF

Functions

± Determine the integrity ± Determine Pseudo Range differential corrections

for each monitored satellite

± Determine ionospheric delay

± Generate GEO satellite ephemeris




EGNOS: Ranging and Integrity Monitor EGNOS: Ranging and Integrity Monitor

Stations (RIMS)Stations (RIMS) 33 RIMS:

± Type A - Raw measurements of GPS,GLONASS,GEO

for CPF processing

± Type B - Raw measurements of GPS,GLONASS,GEO

for CPF checking ± Type C (15 only) - Evil waveforms - GPS only

Paris RIM (Type A)

± Measure difference between UTC and EGNOS

Network Time

Functions

± Data collection

± Transmit data to all MCCs every second




NLES: Navigation Land Earth Station

Functions

± Select the message provider CPF

± Modulate the message generated by the CPF ± Synchronise the up-link signal to GPS time

± Up-link dataAORAOR--EE

IORIOR--WWArtemisArtemis

EGNOS: Navigation Land Earth stationsEGNOS: Navigation Land Earth stations

(NLES)(NLES)




RIMS

Sub-

Network

Back-Bone

2 Mbps

MCC-

1

MCC-

4

MCC-

3MCC-

2

NLES-1

NLES-1 NLES-6

EGNOS Wide Area Network (EWAN)EGNOS Wide Area Network (EWAN)




EGNOS Support Facilities: ESTBEGNOS Support Facilities: ESTB

Scilly Isles (GB)

Hönefoss (N)

Tromsö (N)

Cadiz (E)

Rotterdam (NL)

Höfn (Iceland)

Toulouse (F)

Ankara (T)

EURIDIS RS

Seatex RS

MTB RS

Processing Facility

NLES

Hartebeeshoek

(South Africa)

Kourou

(French Guyana)

Lario (I)

Fucino (I)

Matera (I)




ESTB to EGNOSESTB to EGNOS

Minimum elevation angle contours for E=5 degrees

150 W 100 W 50 W 0 50 E 100 E 150 E

80 S

60 S

40 S

20 S

0

20 N

40 N

60 N

80 N

IOR W

ARTEMIS

ECAC

AOR-E




NAV32516.3566

Metres

EGNOS Performances: Horizontal AccuracyEGNOS Performances: Horizontal Accuracy




EGNOS Performances: Vertical AccuracyEGNOS Performances: Vertical Accuracy

EGNOS Level 3 A average VNSE (2) map

Meters




EGNOS Stability TestsEGNOS Stability Tests -- September 2004September 2004




Horizontal AccuracyHorizontal Accuracy -- November 2005November 2005




GALILEO/EGNOS IntegrationGALILEO/EGNOS Integration

NAV32516.3629

3 Options:

± Cut Public Expenditure

Signals end of programme

Loss of technical know how

Loss of ¼310 Million

± Complete Independence

EU¶s single European policy on satellite navigation?

Duplication of effort and expenditure

± Full Integration

Technically

Institutionally




EGNOS Operational Test and Validation:EGNOS Operational Test and Validation:

ChallengesChallenges

International acceptability

Distributed infrastructure

Institutional concerns System complexity

Time/space performance dependence

WAAS/MS AS interoperability

Lessons learned for GBAS & Galileo




AgendaAgenda








WAAS: Initial ScheduleWAAS: Initial Schedule

1983: RTCA SC 159 chartered to study GPS for

aviation

± 1988: DO-202 GPS MASPS

± 1994: WAAS signal specification

± 1996: DO-229 WAAS MOPS for en-route,terminal & non-precision approach

± 1996+: WAAS MOPS for precision approach

1992: FAA establishes National Satellite Testbed

(NSTB) to develop WAAS 1994: FAA issues WAAS Request for Proposals

1996: First contract for WAAS terminated & new

award made




Date Status1997 Flight Verification System (FVS)

2MCSs, 5WRSs, 2GES, 1GEO

1997-8 Initial WAAS Service Volume

y 2MCSs, 24WRSs, 6GES, 2GEO

yPrimary Means NPA, terminal & en-route

y Supplemental Means CAT-I

1999-2001

End State WAASyAdditional WRSs and GEO

yPrimary Means for CAT-I

WAAS: Initial ScheduleWAAS: Initial Schedule




00 01 05040302 06

GPS

Level - I I

Inmarsat (2 GEOs)

Supportability Upgrades

Level - I I I

Acquisition

1109 1007 20

WAAS

SATs

08

24 Satellites Additional GPS ??

L5

NAVAIDs Full

GEO # 1

GEO # 2

GEO # 3

GEO # 4 (If Required)

?

WAAS: Original ScheduleWAAS: Original Schedule




GI 51989_1000

WAAS: Independent Review BoardWAAS: Independent Review Board

10 April 2001

± FAA should commit to WAAS

± Enormous benefits for all GPS Users

± LNAV and VNAV by 2003

± GEO Redundancy is biggest risk




FAA must decide whether to stop WAAS development in

2003 or continue to refine the technology to meet more

demanding precision approach capability known as a

Category precision approach.

NAV GI 51989_1006

The current implementation does not lead to cost savings

13 Feb 2002: Inspector General of DOT13 Feb 2002: Inspector General of DOT




WAAS Schedule UpdateWAAS Schedule Update

00 01 05040302 06

GPS

Level - I I

Inmarsat (POR and AOR-W)

Supportability Upgrades

IOC

Acquisition

1109 1007 20

WAAS

GEOs

08

Average of 27 Satellites Available

IOC

NAVAIDs Full

GEO # 3

GEO # 4

GEO # 3

?

Acquisition

? If Required

FOC

L5 FOC

GPS III




WAASWAAS

Wide Area

Master Station

Wide AreaReference Stations

Ground

Earth

Station

WAAS

EGNOSGEO + GPS satellites




WAAS Service AreaWAAS Service Area




WAAS Future GEO CoverageWAAS Future GEO Coverage

ANIK F1RANIK F1R

PORPOR AOR-WAOR-W

GALAXY XVGALAXY XVGALAXY XVGALAXY XV




GI 51987_1001

Late on 28 July 2001, PRN22 sufferred a

clock failure and the satellite broadcast

erroneous data for over an hour.«.

«It appears that as soon as the receiver

started tracking PRN22, the position solution

became in error by about a couple of hundred

kilometres.

Richard B. Langley

Geodetic Research Laboratory Dept. of

Geodesy and Geomatics Engineering

On Canadian Space Geodesy Forum (24

Aug 2001)

PRN 22 Failure on 28 July 2001PRN 22 Failure on 28 July 2001




NAV GI 51989_1004

First Step: Immediately

Broadcast Clock

Corrections

Second Step

Declare satellite

unusable

6 Minutes

WAAS and the PRN 22 Failure on 28 July 2001WAAS and the PRN 22 Failure on 28 July 2001




WAAS Vertical PerformanceWAAS Vertical Performance




AgendaAgenda



Implementations: US A's WAAS Implementations: Japan's MS AS




Implementations: Japan's MSASImplementations: Japan's MSAS

MS AS (MTS AT Satellite Based Augmentation System)

based on ICAO FANS concept & provides:

± GNSS for navigation

± Aeronautical Mobile Satellite Service (AMSS) for two way

voice/data including ADS

Hosted on Multi-functional Transport Satellite (MTS AT),which has aeronautical & meteorological mission.

First launch in 1999,

Subsequent launches every 5 years

1994: Initiate design of MS AS

1996-2000: First phase of development

1999: Launch Failed!




15 November 199915 November 1999




Replacement: MTS AT-1R, Launch 2003 2004 2005

MTSATMTSAT--1 Launch Failure1 Launch Failure

The National Space Development Agency of Japan

(NASD A) launched the H-II Launch Vehicle No.8 carrying

the Multi-functional Transport Satellite (MTS AT) from

Tanegashima Space Center at 16:29, Nov. 15, 1999

(JST). However, the vehicle went out of the planned flight

path due to the abnormal stoppage of the combustion of the 1st stage engine, and the command for destruction

was sent to the H-II Launch Vehicle No.8.

In this reason, it became impossible to inject MTS AT into

the orbit as planned.




GMS

Naha

ACC

GMS

Fukuoka

ACC

GMS

Tokyo

ACC

GMS

Sapporo

ACC

L1 / L2

MRS

Hawaii

MRS

Australia

International

Network

NES-1

CPF

NES-2

NCS

NES-1

CPF

NES-2

NCS

MCS Master Control Station

NES Navigation Ground Earth Station

CPF Central Processing Facility

NCS Network Communication System

MRS Monitoring and Ranging Station

GMS Ground Monitor Station

Kobe MCS Ibaraki MCS

L1 /L2

Overlay

Primary

Ka /Ku

GPSGPS

MTSAT-1R MTSAT-2

MSASMSAS




AOR-E POR AOR-WMTSATIOR

MSAS Service AreaMSAS Service Area



End of this ModuleEnd of this Module

DATE/TIME 09:00 12:30 13:30 16:30

Monday 20/03/06

Introduction Terrestrial Navigation The History of Satellite Navigation

Tuesday 21/03/06

Satellite Navigation: Theory and Application GLONASS Current System

StatusNavigating with GPS

Wednesday 22/03/06

From GPS to GNSS Airborne Based Augmentation Systems Space Based Augmentation Systems

Thursday 23/03/06

Ground Based Augmentation Systems Data Integrity Modernisation Programmes

Friday 24/03/06

Towards the Future Debrief

2006 space based augmentation systems

Documents