Satellite-Based Augmentation System (SBAS) Terminology

Purpose

This note defines recurring SBAS terms used across the knowledge base. It is now a controlled terminology page, not the main beginner explanation. New readers should start with What is SBAS and then continue to SBAS Architecture.

Definitions here are concise and intentionally conservative. Exact operational thresholds, message definitions, approval criteria, and service-performance commitments must be traced to the relevant source notes and official documents before being used as authoritative requirements.

Core terms

TermWorking definitionRelated notes
SBASWide-area GNSS augmentation service that broadcasts correction and integrity information to usersWhat is SBAS, SBAS Architecture
GNSSSatellite navigation constellations and signals used as the base positioning sourceSBAS Architecture
Reference stationSurveyed ground receiver used to monitor GNSS signal behavior for augmentation processingSBAS Architecture
Master or processing stationFacility/function that estimates corrections, integrity parameters, and broadcast messagesSBAS Architecture
Uplink stationGround element that sends SBAS messages to the broadcast satellite or payloadSBAS Architecture Flow
SBAS broadcastSignal carrying augmentation messages to user receiversSBAS Architecture Flow
SBAS-capable receiverUser equipment able to receive, decode, and apply SBAS information according to its approval basisSBAS Ground Segment and Airborne Receiver Responsibilities
SBAS message flowFunctional path from monitored observations through augmentation messages to receiver processingSBAS Signal and Message Flow
CorrectionInformation used to reduce modeled navigation errors where applicableSBAS Corrections and Integrity Separation
IntegrityAbility to support timely warning when navigation information should not be relied upon for the intended operationSBAS Integrity
Protection levelReceiver-computed or service-supported bound used to judge whether navigation error remains acceptable for an operationProtection Levels
Alert limitOperation-specific bound that protection levels must satisfy for the operation to continueAlert Limits
AvailabilityProbability or proportion of time that service requirements are met in the relevant contextSBAS-Systems-by-Region-MOC
ContinuityProbability that service remains available for the duration of a defined operationSBAS in Civil Aviation MOC
LPVLocalizer Performance with Vertical guidance; an SBAS-enabled approach concept where approvedLPV-Approach-Procedure
APVApproach with vertical guidance; operational family relevant to GNSS/SBAS implementationSBAS in Civil Aviation MOC
GBASGround-Based Augmentation System; local-area augmentation, usually airport-centeredGBAS-Approach-Procedure, SBAS-vs-Other-Augmentation-Methods
ABASAircraft-Based Augmentation System; receiver/aircraft-side monitoring rather than a regional broadcast serviceSBAS-vs-Other-Augmentation-Methods, ASEAN ABAS Concept

Terms requiring careful source handling

The following terms are frequently misused or over-generalized:

  • Accuracy: must be tied to a metric, confidence level, service mode, and source.
  • Integrity: should not be reduced to “high accuracy”; it is about bounding and alerting.
  • Availability: may refer to signal availability, service availability, procedure availability, or operational availability; these are not interchangeable.
  • Operational: can mean a live technical service, a certified aviation service, a published procedure, or an approved aircraft operation. State which meaning is intended.
  • Coverage: a coverage footprint does not automatically imply approved procedures or service-level compliance at every airport.
  • Readiness: in regional implementation analysis, readiness includes institutional, regulatory, AIS/AIM, procedure-design, aircraft-equipage, and safety-oversight dimensions.

Source posture

Terminology in this page is aligned with the site’s current synthesis and source scaffolds. High-priority source anchors include:

See also