global navigation satellite system
Enable an AI agent to identify a global navigation satellite system, assess the availability and trustworthiness of its positioning, navigation and timing services, and determine appropriate uses and authorized interventions.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Researched by: Codex + Grok
Purpose and description
Enable an AI agent to identify a global navigation satellite system, assess the availability and trustworthiness of its positioning, navigation and timing services, and determine appropriate uses and authorized interventions.
A global navigation satellite system is a radionavigation-satellite service made of a space segment (Earth-orbiting satellites), a control segment, and a user segment that broadcasts time-stamped ranging signals from which a receiver on or near Earth computes position, velocity and time by trilateration, typically needing at least four satellites in view.
It can be Identify the system and distinguish its services from those of other constellations or augmentation providers.; Match documented signals, reference conventions and access conditions to receiver and application requirements.; Assess service suitability for a specified location, time and required positioning or timing performance.; Trace a service degradation to affected signals, constellation assets or ground-segment dependencies.; Recommend continued use, a documented fallback or suspension of reliance when evidence supports that decision.; Prepare an operational change for an authorized operator using the applicable control procedure and service-impact evidence..
Distinguishing features
Has an explicit global positioning, navigation or timing service objective; current incomplete deployment or outages are recorded separately from that objective.
Uses a coordinated constellation to broadcast navigation signals and associated data, rather than merely relaying communications or observing Earth.
Owns a primary navigation service whose identity can be distinguished from an augmentation service that corrects or monitors another system.
Has a coherent operator, control arrangement and service specification, distinguishing it from a receiver that combines several independently operated systems.
Scope
+ System identity, responsible operator and intended global service coverage
+ Constellation configuration and dependencies on ground control and monitoring
+ Broadcast navigation signals, navigation data and positioning, navigation and timing services
+ Reference frames, time references and published service performance commitments
+ Service health, degradation, integrity information and operational changes
+ Service access conditions and authority to operate or modify the system
- Individual satellite construction, component inventories and maintenance histories
- Standalone receiver hardware, firmware and antenna designs
- Independent augmentation systems and correction networks
- Regional navigation satellite systems as separate registered systems
- User navigation applications, vehicle guidance and route planning
- Local propagation environments, interference emitters and downstream time-distribution networks
Characteristics
- System identity and operator
- Official system designation, aliases, operator and authoritative identifiers Prevents confusing a constellation, a service, a programme phase or a multi-system receiver with the registered system.
- Lifecycle and declared service status
- Operator-declared status, effective date and supporting notice Separates intended capability from capability declared available at the assessment time.
- Constellation configuration
- Links to satellites, orbital assignments and navigation-service roles, each time-qualified Connects service availability to the assets currently contributing to it.
- Coverage and availability
- Geographic extent and availability percentage by service, interval and stated reception assumptions Tests whether a service is usable where and when an application needs it.
- Signal and service profile
- Published signal identifiers, carrier frequencies in Hz, service classes and interface versions Establishes which receiver capabilities and access conditions are necessary.
- Spatial and temporal references
- Reference-frame realization, system time scale and documented transformations or offsets Allows positions and times to be interpreted and combined without silently mixing references.
- Position and time performance
- Position error in m and time error in ns, with service, confidence level, interval and test conditions Supports comparison with application requirements without treating unlike performance statements as equivalent.
- Health and integrity provision
- Published health semantics, integrity provision or absence, affected signals and validity interval Distinguishes declared usability from evidence that an error will be detected and reported.
- Control and monitoring dependencies
- Links to controlling, monitoring, upload and reference-maintenance functions Identifies dependencies whose disruption could affect navigation data or service continuity.
- Access and intervention authority
- Per-service reception conditions and documented permissions for configuration, control and publication of status Separates permission to receive a service from authority to alter its operation.
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 18 findings · 29 questions.
System identity and boundary Establishes which global navigation system is being modelled and where its responsibility ends.
A named navigation programme, a constituent constellation and an independent augmentation service must not silently become the same thing.
Authoritative system identity
Records the system designation, accountable operator and declared service objective.
Identity and global service intent
Record evidence tying the registered thing to an operator-defined system with a global navigation service objective.
- Which authoritative designation, aliases and operator identify this system? provenance
- How does the operator define its global positioning, navigation or timing service objective? definition
Primary service boundary
Separates the system's own service from receivers, external corrections and cooperating constellations.
Owned and external capabilities
Record which capabilities belong to this system and which require separately governed systems.
- Which signals, service commitments and control functions fall under this system's responsibility? boundary
- Which advertised capabilities depend on external augmentation, corrections or other constellations? boundary
Constellation and ground control Connects navigation service delivery to the space assets and ground functions that sustain it.
A constellation count alone cannot establish whether satellites broadcast usable navigation data or remain adequately controlled.
Space segment contribution
Records the time-dependent configuration and service contribution of constellation members.
Service-contributing satellites
Distinguish deployed satellites from those assigned and declared usable for particular navigation services.
- Which satellites and orbital assignments contribute to each service at the assessment time? measurement
- What evidence distinguishes operational contributors from testing, spare or unavailable satellites? provenance
Navigation data control chain
Records the ground functions that monitor satellites and maintain broadcast navigation information.
Monitoring, estimation and upload
Identify dependencies responsible for satellite monitoring, orbit and clock information, and navigation-message updates.
- Which functions produce, validate and upload the orbit, clock and status data used by receivers? provenance
- What service limitations are documented when monitoring or uploads are interrupted? boundary
Signals and reference conventions Defines how a compatible user obtains and interprets the system's navigation service.
Signal reception is insufficient unless service access, navigation-message interpretation and spatial and temporal references agree.
Signal and service interfaces
Maps broadcast interfaces to service classes and receiver requirements.
Documented reception contract
Record the published interfaces and conditions that determine access to each service.
- Which interface documents and versions define each signal, navigation message and associated service? provenance
- What receiver capabilities, credentials or other conditions are required to use each service? action
Position and time interpretation
Makes the references underlying reported coordinates and time explicit.
Reference realizations and transformations
Record the spatial and temporal conventions needed to interpret outputs or combine them with other systems.
- Which reference-frame realization and time scale apply to each service and effective period? definition
- Which documented transformations, time offsets and uncertainties are needed for the intended external reference? measurement
Service performance and trust Relates service commitments and current evidence to the conditions of a proposed use.
Global intent and healthy broadcasts do not by themselves establish adequate accuracy, continuity or integrity for a particular application.
Coverage and performance evidence
Separates declared commitments from measured outcomes and their reception assumptions.
Conditional service suitability
Record coverage, accuracy and availability evidence with enough context to judge the intended use.
- What coverage, accuracy and availability commitments apply to the selected service, and under which conditions? definition
- What dated measurements support suitability at the intended location and time, with what confidence and receiver assumptions? measurement
Health, integrity and anomalies
Records how unusable or misleading service is indicated and what remains undetected.
Trust evidence and alert limits
Distinguish signal health, integrity alerts, authentication evidence and observed anomalies without treating them as interchangeable.
- What do this service's health indicators and any integrity or authentication mechanisms establish, and what do they leave unverified? boundary
- Which current notices or observations indicate degradation, and how are system faults distinguished from local interference or receiver faults? provenance
- Which documented conditions require rejecting a signal, using a fallback or suspending reliance on the service? action
Operational change and authority Records how deployment, maintenance and control decisions change the usable navigation service.
Service capabilities evolve, while receiving navigation broadcasts and commanding the system require different authority.
Service transition management
Tracks dated service declarations and changes that affect compatibility or reliance.
Effective service configuration
Record which service configuration is currently effective and which announced transitions remain pending.
- Which authoritative declarations establish current deployment, testing, operational or retirement status? provenance
- What receiver or application changes are required by announced signal, message or service transitions, and by when? action
Authorized system intervention
Identifies who may change constellation operation, navigation data and official service status.
Control rights and change conditions
Record the authority and operational conditions required before an agent can participate in a service-affecting change.
- Which roles may command satellites, modify navigation-data production or issue official service-status declarations? provenance
- What approved procedure, impact assessment and recovery conditions govern the proposed service-affecting intervention? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Kinds and varieties
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- GPS / NAVSTAR GPS (United States)
- GLONASS (Russian Federation)
- Galileo (European Union)
- BeiDou Navigation Satellite System / BDS (China)
- Regional navigation satellite systems (NavIC/IRNSS; QZSS; planned KPS)
- Satellite-based augmentation systems (WAAS, EGNOS, MSAS, GAGAN, SDCM, BDSBAS, KASS)
- Differential and precise techniques (DGNSS, GBAS, RTK, PPP / Galileo HAS)
- Open civil service versus authorized, encrypted or public-regulated service
- Which of these kinds and varieties hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Identifiers and schemes
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Wikidata - Q188728 - Global Positioning System, the type specimen; generic satellite-navigation/GNSS items are adjacent in Wikidata and should be checked before reuse.
- ITU Radio Regulations service name - RNSS (Radionavigation-Satellite Service) - The radio-service class that covers GNSS, regional systems and SBAS downlinks, not a product code for one constellation.
- NMEA 0183 / NMEA 2000 talker ID - GP (GPS), GL (GLONASS), GA (Galileo), GB or BD (BeiDou), GQ (QZSS), GI (NavIC), GN (multi-GNSS) - Sentence talker prefix identifying which constellation produced a reported fix.
- GPS/SBAS PRN (ranging-code identifier) - GPS PRN 1-32 (expanded in later blocks); SBAS PRN typically 120-158 - Satellite identity in the GPS family and in SBAS overlays; other constellations use analogous SVID/slot numbers.
- ITU-R M.1787 annex - Annex 1 GLONASS; Annex 2 GPS; Annex 3 Galileo; Annex 4 QZSS; Annex 10 IRNSS/GAGAN; further annexes for named SBAS networks - The Recommendation is the ITU catalogue of RNSS transmitting space stations.
- Which of these identifiers and schemes hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Standards and regulation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- ICAO Annex 10 to the Chicago Convention, Volume I (Radio Navigation Aids), GNSS SARPs in Chapter 3.7 and Attachment D - International Civil Aviation Organization; GPS and GLONASS are the core constellations written into the SARPs.
- ICAO Doc 9849, GNSS Manual - International Civil Aviation Organization (implementation guidance, not SARPs).
- ITU Radio Regulations frequency allocations for the radionavigation-satellite service, and Recommendation ITU-R M.1787 (system descriptions) - International Telecommunication Union.
- International Committee on Global Navigation Satellite Systems (ICG) - UNOOSA-hosted voluntary body on compatibility and interoperability of civil GNSS.
- Operator interface control documents: IS-GPS-200 (United States Space Force); Galileo OS SIS ICD (European Union); GLONASS ICD (Russian Federation); BeiDou SIS ICD (China).
- RTCA DO-229 (MOPS for GPS/SBAS airborne equipment) - RTCA; corresponding EUROCAE documents for European airborne GNSS.
- IEC 61108 series, Maritime navigation and radiocommunication equipment and systems - Global navigation satellite systems (GNSS) - International Electrotechnical Commission.
- IMO SOLAS Chapter V and the IMO World-Wide Radionavigation System policy (Resolution A.1046(27)) - International Maritime Organization.
- Which of these standards and regulation hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Real-world use
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Consumer and vehicle navigation: phones, watches and in-car units compute a multi-GNSS fix and display it on a map; new vehicles commonly track GPS+GLONASS+Galileo, with BeiDou depending on chipset and market.
- Civil aviation: en-route and terminal RNAV/RNP, and vertically guided approaches (LPV/APV) where an ICAO-compliant SBAS or GBAS is available; States remain responsible for declaring GNSS performance in their airspace.
- Maritime: SOLAS shipborne receivers, ECDIS, AIS position, and harbour approaches; distress beacons use GNSS position and, on some satellites, a 406 MHz MEOSAR relay.
- Surveying and construction: RTK or PPP from a CORS network or commercial correction service to centimetre-level coordinates.
- Precision agriculture and machine control: multi-GNSS plus RTK/PPP on tractors and excavators.
- Timing: GNSS-disciplined oscillators hold UTC-traceable time for mobile-network base stations, power-grid synchrophasors and financial timestamping.
- Scientific geodesy: IGS tracking networks produce precise orbits and clocks used to measure Earth rotation, reference frames and sea level.
- Military and sovereign PNT: encrypted or public-regulated signals independent of a foreign civil service.
- Which of these real-world use hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Typical measurements
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Standalone civil horizontal position accuracy (open sky) - about 1 to 10 (few metres per ITU; dual-frequency GPS near 1; GLONASS often near 2) - m
- Augmented / precise horizontal accuracy (RTK, PPP, Galileo HAS, QZSS CLAS) - 0.01 to 0.2 (centimetre RTK; decimetre HAS/PPP; centimetre CLAS in Japan) - m
- ICAO GNSS horizontal accuracy requirement, CAT I / LPV-200 (95%) - 16 (vertical 4 to 6) - m
- Time offset to UTC (civil timing receivers) - tens of nanoseconds (order 10 to 100) - ns
- Space-segment orbital altitude (MEO core constellations; GEO/IGSO used by BeiDou, QZSS, NavIC, SBAS) - 19000 to 37000 (GPS about 20180; GLONASS about 19130; Galileo about 23222) - km
- Nominal constellation size per global system - 24 to 35 slots (GPS 24/6 planes; extras on orbit; BeiDou also uses GEO/IGSO) - satellites
- Civil L-band carrier frequencies (examples) - 1176.45 (GPS L5 / Galileo E5a) to 1602 (GLONASS L1 FDMA); GPS/Galileo L1/E1 at 1575.42 - MHz
- Satellites used for a 3-D fix - minimum 4; multi-GNSS open-sky often 8 to 20+ - count
- Which of these typical measurements hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Failure modes and hazards
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Radio-frequency interference and jamming: GNSS downlink power at Earth is extremely low, so cheap jammers or strong adjacent-band transmitters can deny a fix over kilometres (ITU interference FAQ; aviation and maritime incident reports).
- Spoofing: counterfeit ranging signals can capture a receiver and report a false position or time, affecting navigation, AIS, and timing-dependent infrastructure.
- Ionospheric delay and scintillation: uncorrected ionosphere is a metre-class error; equatorial and polar scintillation can drop lock. Dual-frequency (L1+L5) is the designed mitigation.
- Multipath and blockage: urban canyons, foliage, terrain and indoor spaces hide or reflect signals; consumer GNSS is not a reliable indoor position source without assistance or other sensors.
- Constellation or control-segment failure: satellite clock/ephemeris faults and rare system-wide outages (e.g. the 2019 Galileo timing outage) produce hazardously misleading or unavailable PNT until flagged.
- Insufficient integrity without augmentation: standalone GNSS meets ICAO en-route and non-precision-approach accuracy but not precision-approach integrity, continuity or vertical guidance; landing requires SBAS/GBAS or an independent aid.
- Geopolitical denial: civil services are offered by states and can be regionally jammed, degraded or (in principle) withheld; that is why operators field national GNSS/RNSS and encrypted signals.
- Error-budget terms that remain even in clear sky: broadcast ephemeris and clock (order 1 m for GPS broadcast), troposphere, receiver noise and antenna phase-centre variation.
- Which of these failure modes and hazards hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Regional variation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- English-language public usage often says "GPS" for any satellite fix; specialists and non-US operators use GNSS as the generic, and treat GPS as one constellation.
- Coordinate and time frames differ by system: GPS uses WGS 84 and GPS Time; GLONASS uses PZ-90 and UTC(SU); Galileo uses GTRF and GST; BeiDou uses CGCS 2000 and BDT - receivers must apply published offsets.
- China treats BeiDou as the primary national system and has required BDS capability in some domestic transport and consumer equipment; Russia similarly privileges GLONASS in national procurement.
- Europe uses Galileo plus EGNOS for aviation; Japan uses QZSS (Michibiki) both as a GPS complement (high elevation in urban canyons) and as a free centimetre/decimetre correction broadcast (SLAS/CLAS).
- India operates NavIC (formerly IRNSS) over the subcontinent plus about 1 500 km, and GAGAN as its SBAS; Korea operates KASS and is developing KPS.
- ICAO SARPs still centre on GPS and GLONASS as core constellations; Galileo and BeiDou airborne use depends on later SARPs work and on national/EASA equipment approval, so aviation certification lags consumer multi-GNSS.
- US policy language sometimes treats "GNSS" as a system-of-systems under GPS leadership; Chinese and European usage treats the four global systems as plural GNSS and calls regional-only systems RNSS - a naming split also noted in Japanese technical literature.
- SBAS service is regional by construction: WAAS (North America), EGNOS (Europe/Africa expansion), MSAS (Japan), GAGAN (India), SDCM (Russia), BDSBAS (China), KASS (Korea), SouthPAN (Australia/NZ).
- Which of these regional variation hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- GPS (NAVSTAR) - GPS is one global constellation. GNSS is the generic class that also includes GLONASS, Galileo and BeiDou. A receiver labelled only "GPS" may still be a GNSS receiver; the test is which constellations and talker IDs it actually tracks.
- Regional navigation satellite system (RNSS in the regional sense) - NavIC and QZSS are designed for a service area, not worldwide 24-satellite MEO coverage. ITU also uses RNSS for the radio service that includes GNSS. Test: advertised coverage (global vs regional) and constellation geometry (MEO global vs GEO/IGSO/QZSS HEO).
- Positioning, navigation and timing (PNT) - PNT is the capability. GNSS is one PNT source among inertial sensors, terrestrial radio, clocks and (emerging) LEO-PNT. Test: whether the system still functions when all satellite ranging signals are removed.
- Satellite-based augmentation system (SBAS) - SBAS (WAAS, EGNOS, etc.) broadcasts corrections and integrity on GNSS-like signals from GEO; it does not replace a core constellation. Test: whether a standalone 3-D fix exists without GPS/GLONASS/Galileo/BeiDou ranging.
- Ground-based augmentation / DGNSS / RTK - Local terrestrial reference stations send corrections; coverage is tens of kilometres (RTK/GBAS) not global. Test: need for a nearby base or CORS versus a satellite-only solution.
- Inertial navigation system (INS) - INS integrates accelerometers and gyros and needs no external radio. It drifts with time; GNSS is absolute but fragile. Test: behaviour in a Faraday cage or under jamming.
- Terrestrial radionavigation (VOR, DME, ILS, eLoran) - Ground transmitters, regional coverage, different frequencies and failure modes. Test: whether position is derived from MEO/GEO satellite ranging in the RNSS bands around 1.1-1.6 GHz.
- Assisted GNSS (A-GNSS) - Cellular or internet assistance (ephemeris, time, coarse position) shortens time-to-first-fix; the ranging still comes from GNSS satellites. Test: whether a fix remains possible with the assistance channel cut but satellites in view.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of global navigation satellite system this model covers, and on what evidence? provenance
Sources
- FAQ on Global Navigation Satellite Systems (GNSS) Interference - International Telecommunication Union (ITU), 13 May 2024 - ITU definition of GNSS as Earth-orbiting constellations providing worldwide PNT; the four global systems plus two regional RNSS; uses of GNSS; interference as the principal radio hazard.
- Global Navigation Satellite Systems (GNSS) - United Nations Office for Outer Space Affairs (UNOOSA) - Three-segment architecture (satellites, ground control, receivers); transport, timing and critical-infrastructure uses; SBAS examples; role of the International Committee on GNSS (ICG).
- What are Global Navigation Satellite Systems (GNSS)? - NovAtel (Hexagon) - Space, control and user segments; MEO altitudes about 20 000-37 000 km; four global constellations plus QZSS and IRNSS; trilateration from at least four satellites.
- Global Navigation Satellite System (GNSS) Manual, Doc 9849 - International Civil Aviation Organization (ICAO) - ICAO sense of GNSS as core constellations plus augmentations; Annex 10 Volume I SARPs (Amendment 76, 2001); GPS and GLONASS as core constellations; accuracy sufficient for en-route through non-precision approach only without augmentation.
- Recommendation ITU-R M.1787-6 (02/2026), Description of systems and networks in the radionavigation-satellite service - ITU Radiocommunication Sector - Official ITU-R technical descriptions of GPS, GLONASS, Galileo, QZSS, IRNSS/GAGAN and SBAS space stations as RNSS systems.
- Modernization of GNSS, RNSS, and SBAS - Technologies (MDPI), 2025 - Practice of treating GPS, GLONASS, Galileo and BDS as GNSS, QZSS/NavIC/KPS as RNSS, and SBAS as a separate ICAO-regulated overlay class.
- What's the Difference Between GNSS and PNT? - Spirent - GNSS as one (classic) PNT source, not a synonym for all positioning, navigation and timing; GPS as a single constellation under the GNSS umbrella.
- GPS/GNSS Glossary (Timing) - Furuno Electric Co. - Industry glossary distinguishing GNSS (global constellations) from RNSS (NavIC, QZSS) and naming GPS, Galileo, GLONASS and BeiDou as the four GNSS.
What the second pass must settle
- Does the registry intend this entry to cover systems with a global service objective during deployment, or only systems with declared global operational capability?
- Where should integrated augmentation or correction services be bounded when they share the primary system's operator or broadcast infrastructure?
- Which authoritative sources provide sufficiently current constellation membership, service status and interface versions for individual system instances?
- Which performance and integrity measures can be compared across systems without obscuring different confidence levels, reception assumptions or service commitments?
- How should an agent represent conflicting operator notices and independent observations, especially when system faults cannot yet be separated from local interference or receiver errors?