Four Constellations, Two Frequencies: What Modern GNSS Integration Requires from Embedded Hardware
GPS became the default positioning solution for embedded products not because it was the only option but because for a long time it was the only practical one. Every other constellation was either unavailable, incomplete, or undocumented. That situation changed progressively through the 2010s as GLONASS recovered to full operational status, Galileo reached serviceable coverage, and BeiDou-3 expanded to global operation. As of March 2026, approximately 130 active GNSS satellites operate across the four global constellations — more than four times what GPS provides alone.
The practical consequence for embedded product design is not just better accuracy. A receiver with access to 30–40 satellites simultaneously from multiple constellations has fundamentally different failure modes than one depending on 8–12 GPS satellites. It has better geometry under partial sky blockage, faster time-to-first-fix from a cold start, more graceful degradation under interference, and built-in cross-constellation integrity monitoring. For embedded products that moved from GPS-only to GPS+GLONASS in 2012 and stayed there, the additional benefit of adding Galileo and BeiDou-3 is less obvious — this article makes the technical case for it and explains what dual-frequency reception adds on top of multi-constellation.
The Four Global Constellations — What Each Actually Provides
Understanding why GPS alone is no longer sufficient requires a concrete comparison of what each constellation contributes, not just a count of satellites.
GPS (United States):
- 31 active satellites across 6 orbital planes, 20,180 km altitude
- L1 (1575.42 MHz) and L5 (1176.45 MHz) civil signals; L2C on modernized satellites
- Approximately 1 m horizontal accuracy with dual-frequency receivers
- CDMA signal structure; well-understood receiver implementation
- Most widely supported in existing infrastructure (corrections services, map databases, testing equipment)
GLONASS (Russia):
- 24+ active satellites, 64.8° inclination (highest of the four — strongest benefit at high latitudes above 55°)
- Legacy G1/G2 signals use FDMA — each satellite transmits on a slightly different frequency, which complicates receiver design relative to CDMA systems
- GLONASS-K2 modernized satellites introduce CDMA signals (L1OC, L3OC, L5OC), simplifying future receiver implementations
- Approximately 2 m typical horizontal accuracy — slightly less precise than GPS or Galileo
- Geographic benefit: provides the most additional satellites above 60° latitude where GPS geometry is weakest
Galileo (European Union):
- 28 active satellites; High Accuracy Service (HAS) operational since 2024 delivering approximately 20 cm horizontal accuracy for free over E6 band
- E1 (1575.42 MHz, same frequency as GPS L1 — interoperability by design) and E5a/E5b signals
- Higher transmitted power on E5 than GPS L5, improving link margin in challenging environments
- The most accurate civilian GNSS signal currently available, with HAS corrections broadcast via satellite (no internet required)
- Open service documentation, authentication service (OSNMA) for anti-spoofing
BeiDou-3 (China):
- 35 satellites including MEO, IGSO, and GEO components — the only constellation mixing orbit types
- B1C (1575.42 MHz, interoperable with GPS L1 and Galileo E1), B2a (1176.45 MHz, interoperable with GPS L5 and Galileo E5a)
- The GEO and IGSO components provide enhanced regional coverage over Asia-Pacific; MEO provides global coverage
- Unique Short Message Communication (SMC) service via GEO satellites — bidirectional messaging at up to 14,000 characters per message, accessible to embedded devices with appropriate hardware
- Approximately 100 satellites from combined regional network across full BeiDou-3 deployment zones
Regional systems that embedded products increasingly support:
- QZSS (Japan): 4 satellites in highly elliptical orbits over Japan/APAC, transmitting GPS-compatible signals; improves availability in Japan's mountainous urban environments
- NavIC/IRNSS (India): regional constellation for South Asia, now supported by chipsets including u-blox F10/F11; L5 signal at 1176.45 MHz
What Multi-Constellation Actually Improves
The benefit of adding constellations is most visible in three specific metrics: satellite count under obstruction, dilution of precision (DOP), and time-to-first-fix.
Satellite count and DOP under obstruction:
In an open field with clear sky, a GPS-only receiver at mid-latitudes sees 8–12 satellites with good geometry. Adding three more constellations brings that to 30–40 visible satellites. Under partial sky blockage — a vehicle in an urban canyon, a device mounted under eaves, a tracker strapped to an asset near a building — the visible fraction of a GPS-only sky may drop to 4–5 satellites, degrading DOP to the point where the position solution is unreliable or impossible. With 30+ total satellites available, the same partial obstruction typically leaves 10–15 visible, and DOP remains acceptable.
Quantified accuracy improvements in constrained environments from research on four-constellation positioning show:
| Configuration | Urban position error (CEP95) | Availability |
| GPS L1 only | ~15–30 m | ~70–80% of time |
| GPS + GLONASS L1 | ~8–15 m | ~85–90% of time |
| GPS + GLONASS + Galileo + BeiDou L1 | ~4–8 m | ~95–98% of time |
| GPS + Galileo + BeiDou L1/L5 dual-band | ~1–2 m | ~97–99% of time |
Time-to-first-fix:
A cold-start TTFF requires the receiver to acquire at least four satellites, decode their navigation messages (approximately 12.5 minutes for GPS if the almanac is cold), and compute a position. With 30+ satellites available, acquisition typically succeeds faster because more satellites are visible and some will have favorable signal strength and geometry. With an assisted GNSS (A-GNSS) service like u-blox AssistNow providing ephemeris and almanac data over the network at power-on, TTFF drops to under 2 seconds regardless of constellation count — but A-GNSS availability is not guaranteed in all embedded deployments, making the native cold-start time relevant for offline or intermittently connected products.
Integrity and availability:
A GPS-only receiver with fewer than 4 visible satellites cannot compute a position at all. A four-constellation receiver under the same obstruction almost always has enough satellites from the combined view to maintain a position. This availability property is not just a product quality improvement — for applications where position loss triggers a safety event (loss of asset tracking, geofence violation, dead reckoning gap in an ADAS system), it is a functional requirement that GPS alone cannot meet in all deployment environments.
Dual Frequency — The L1/L5 Decision
Multi-constellation improves satellite count and geometry. Dual-frequency reception (L1 + L5) addresses a different class of problem: multipath and ionospheric error.
The ionospheric error problem:
GPS and GNSS signals travel through the ionosphere, where charged particles delay the signal by an amount that varies with solar activity, time of day, latitude, and weather. A single-frequency receiver can only estimate this delay using a broadcast ionospheric model (Klobuchar for GPS, NeQuick for Galileo), which corrects approximately 50–60% of the actual delay. The residual error — which can reach 5–10 m under disturbed ionospheric conditions — is irreducible with a single frequency. A dual-frequency receiver measures the differential delay between L1 and L5 directly (the two signals have different frequencies and therefore different ionospheric delays), computing an iono-free combination that eliminates this error entirely.
The multipath problem in urban environments:
Multipath occurs when a satellite signal bounces off a building or other reflective surface before reaching the receiver, arriving slightly later than the direct-path signal. The receiver's correlator sees the combination of direct and reflected paths, producing a range measurement error. Multipath error can reach 30 m in severe urban canyon environments for a single-frequency receiver.
L5 signals have characteristics that make them substantially more resistant to multipath than L1:
- L5 uses BPSK(10) modulation — 10× the chipping rate of L1 C/A — giving it a much narrower correlation peak and better ability to separate direct from reflected paths
- L5 is transmitted at higher power than L2C (−154 dBW versus −158 dBW), improving signal strength under attenuation
- L5's wider bandwidth provides more frequency diversity against multipath correlation artifacts
The practical result, measured in u-blox's urban driving tests: L1-only receivers achieve approximately 4 m CEP50; L1/L5 dual-band receivers achieve under 2 m CEP50 in the same urban environment. In severe urban canyons, the difference is larger — L1-only can reach 30 m error while L1/L5 stays under 5 m.
The u-blox F10 platform (2024) and its successor F11 (2025) implement an intelligent algorithm that switches between L1-only and L1/L5 dual-band based on detected signal conditions. In open sky with sufficient L1 signal quality, the receiver conserves power by using L1 alone. When multipath or degraded signals are detected, it engages L5 processing. The F11 describes this as "Selective L5 mode" — delivering dual-band accuracy at near single-band power consumption, which is the key constraint for battery-powered applications.
Module Selection Framework for Embedded Designers
Choosing a GNSS module requires matching the accuracy tier, power budget, and form factor to the application's actual requirements. The market divides clearly into three tiers.
Standard precision tier (L1 single-band, multi-constellation):
Representative modules: u-blox M10, MAX-M10S, SAM-M10Q, Quectel L89, Telit SE868
Typical specifications:
- 1.5–3 m CEP accuracy in open sky
- 10–30 m in dense urban environments
- TTFF cold start: 30–60 s (typical), 2 s hot start
- Power: 10–20 mW typical tracking power
- Cost: $2–$8 module cost at volume
Suitable for: asset tracking in open environments, pet trackers, fleet management in low-density urban areas, logistics, simple navigation. Not suitable for: urban micromobility, dense-urban telematics, or any application where lane-level accuracy matters.
Dual-band precision tier (L1/L5, multi-constellation):
Representative modules: u-blox NEO-F10N, MAX-F10S, DAN-F10N (20×20×8 mm with integrated antenna), Quectel LC79H, ST Teseo-LIV4F
Typical specifications:
- 1.5–2 m CEP in dense urban environments (versus 4–30 m for L1-only)
- L5 multipath mitigation engaged automatically in urban conditions
- TTFF: similar to M10 with assisted GNSS
- Power: 20–30 mW dual-band tracking; F11 achieves near single-band consumption via selective L5
- Cost: $8–$20 module cost at volume
Suitable for: urban telematics and micromobility (e-scooters, e-bikes needing lane-level geofencing), delivery robot navigation, UAV waypoint accuracy, aftermarket vehicle OBD tracking. Key differentiator from standard precision: distinguishes which side of a road a vehicle is on — standard precision cannot reliably do this.
High precision tier (RTK/PPK, L1/L2 or L1/L5, multi-constellation):
Representative modules: u-blox ZED-F9P, ZED-F9R, ST Teseo-APG
Typical specifications:
- 1–2 cm CEP with RTK corrections
- Full carrier-phase tracking on L1 and L2 (or L5)
- Requires correction data stream (NTRIP, RTCM, or proprietary service)
- Power: 40–100 mW
- Cost: $50–$200 module cost
Suitable for: agricultural machinery guidance, survey and mapping, precision landing systems, autonomous robotics with lane-level or sub-lane positioning requirements. Requires RTK correction infrastructure within approximately 10–30 km.
Spoofing, Jamming, and Signal Authentication
GPS jamming and spoofing have moved from edge cases to expected failure modes in many deployment environments. Low-cost GPS jammers (nominally marketed as "privacy devices") are widely available and create interference zones of several hundred meters. Sophisticated spoofing — broadcasting false GPS signals to mislead a receiver's position calculation — has been documented in conflict zones and is increasingly observed in commercial shipping lanes.
The embedded security implications differ by threat type:
Jamming (RF interference that drowns out legitimate signals):
- Broadband or narrowband RF transmitter desensitizes the receiver's front end
- Primary defense: multi-constellation reception — a jammer covering GPS L1 frequency does not simultaneously cover GLONASS G1, Galileo E1, and BeiDou B1 if they are on different frequencies, though the close proximity of L1/E1/B1C at 1575.42 MHz means a single-frequency jammer can affect all three
- L5 band (1176.45 MHz) is far enough from L1 that a jammer targeting L1 does not affect L5 — dual-frequency reception provides meaningful jam resistance
- Dedicated jamming detection: modern modules including ST Teseo series and u-blox M10/F10 include hardware and firmware jamming detection with configurable thresholds and interrupt outputs
Spoofing (false signals designed to mislead the receiver):
- A spoofer must generate plausible false signals for every constellation the receiver tracks — spoofing GPS alone is relatively simple; spoofing GPS + Galileo + BeiDou simultaneously requires substantially more sophisticated equipment
- Galileo's Open Service Navigation Message Authentication (OSNMA) transmits cryptographic authentication data within the Galileo E1B navigation message, allowing receivers to verify that received signals originated from genuine Galileo satellites
- OSNMA support was declared operational in 2023 and is supported by ST Teseo receivers
- Cross-constellation consistency checking — a receiver computing position from GPS and from Galileo independently and comparing the results — detects spoofing attacks that only target one constellation
- Receivers with on-chip Hardware Security Modules (HSM): ST's secure Teseo variants include on-chip HSM and comply with ISO/SAE 21434 automotive cybersecurity specifications
Firmware-level response to detected attacks:
- A product integrating a GNSS module needs to handle the interrupt or flag that the module raises when jamming or spoofing is detected
- Responses depend on the application: switching to dead reckoning, raising an alert, refusing to act on the compromised position, logging the event
- This firmware design is application-specific but should be explicitly specified during product design rather than discovered at integration
The practical design implication: products deployed in infrastructure-critical applications (utility asset monitoring, precision timing for communications networks, autonomous vehicle navigation) should specify modules with hardware jamming detection and OSNMA support as minimum requirements, not optional features.
Quick Overview
GPS alone provides 8–12 visible satellites at mid-latitudes under open sky and degrades significantly in urban environments. Four-constellation reception (GPS + GLONASS + Galileo + BeiDou) provides 30–40 visible satellites, maintaining acceptable geometry under partial sky obstruction and improving urban positioning accuracy from 15–30 m (GPS L1 only) to 4–8 m (four-constellation L1). L1/L5 dual-frequency reception addresses multipath and ionospheric error separately from constellation count, reducing urban CEP50 from approximately 4 m to under 2 m. The u-blox F10/F11 platform implements adaptive L1/L5 power management to deliver dual-band accuracy at near single-band power consumption for battery-powered applications. Galileo OSNMA provides cryptographic spoofing resistance; multi-constellation cross-consistency checking detects spoofing attacks targeting a single constellation.
Key Applications
Urban micromobility (e-scooters, e-bikes) requiring lane-level geofencing and side-of-road discrimination, vehicle aftermarket telematics needing accurate position in covered parking and dense urban areas, precision agriculture with RTK-grade positioning for autonomous guidance, industrial IoT asset tracking requiring high position availability under partial sky blockage, embedded timing references in telecommunications and smart grid infrastructure requiring multi-constellation for redundancy, and any product exported globally where market-specific geopolitical restrictions on individual constellations would reduce availability.
Benefits from multi-constellation and dual-frequency:
- Satellite availability: 30–40 versus 8–12 for GPS alone — maintained even under 50% sky obstruction
- Urban accuracy: 1–2 m CEP with L1/L5 versus 15–30 m for GPS L1 only
- TTFF improvement: more satellites available accelerates cold-start acquisition
- Interference resilience: jamming one frequency or constellation does not disable the receiver
- Spoofing resistance: cross-constellation consistency and Galileo OSNMA authentication
- Regional optimization: BeiDou-3 and QZSS add satellites in Asia-Pacific; GLONASS adds high-latitude coverage
Challenges
Dual-frequency reception increases power consumption by 35–50% compared to single-band, which is significant for coin-cell or harvested-energy IoT designs (mitigated by adaptive selective L5 in F11-class receivers). GLONASS FDMA architecture adds receiver complexity — each satellite transmits on a slightly different frequency, requiring separate tracking channels per satellite rather than shared code tracking. BeiDou B1I and B1C are distinct signals at different frequencies from the same satellites; receiver firmware must correctly differentiate them for optimal accuracy. RTK L1/L5 correction networks are less established than L1/L2 RTCM networks, though this is improving rapidly as u-blox and Swift Navigation build L5-capable correction services.
Outlook
The GPS L5 constellation is not fully operationally capable as of May 2025 — not all GPS satellites transmit L5. This is the primary remaining limitation of L1/L5 dual-band receivers, which compensate by tracking L5 from Galileo E5a, BeiDou B2a, and QZSS L5 where GPS L5 is unavailable. Full GPS L5 operational capability is expected by 2027–2028. Galileo's HAS 20 cm free accuracy service, operational since 2024, represents the first free centimeter-accurate global positioning service — competitive with RTK for applications where 20 cm is sufficient and the E6 band receiver hardware is available. The convergence of high-precision and standard-precision GNSS through free broadcast correction services is the trajectory that will make sub-meter accuracy the default for embedded products by 2028.
Related Terms
GNSS, GPS, Galileo, GLONASS, BeiDou-3, QZSS, NavIC, multi-constellation, dual-frequency, L1, L2, L5, E1, E5a, E5b, E6, B1C, B1I, B2a, G1, G2, CDMA, FDMA, multipath, urban canyon, DOP, dilution of precision, TTFF, time-to-first-fix, A-GNSS, AssistNow, RTK, PPK, RTK corrections, NTRIP, RTCM, carrier phase, ionospheric error, iono-free combination, BPSK(10), multipath mitigation, OSNMA, spoofing detection, jamming detection, dead reckoning, u-blox M10, u-blox F10, u-blox F11, u-blox ZED-F9P, NEO-F10N, DAN-F10N, ST Teseo, Quectel LC79H, HAS, High Accuracy Service, CEP, CEP50, CEP95, SAW filter, LNA, TCXO, patch antenna, selective L5, SBAS, WAAS, EGNOS, MSAS, ISM-RNS, geofencing, lane-level accuracy
Our Case Studies
FAQ
Why does adding Galileo and BeiDou improve positioning when GPS and GLONASS already provide global coverage?
GPS and GLONASS together provide global coverage, meaning a receiver can always compute a position under open sky. The improvement from Galileo and BeiDou comes from satellite count under partial obstruction and geometric diversity. In an urban canyon where buildings block half the sky, a GPS+GLONASS receiver may see 6–8 satellites — marginal geometry. Adding Galileo and BeiDou typically brings this to 12–18, which maintains good DOP and position accuracy. Additionally, Galileo's E5 signals and BeiDou-3's B2a have favorable characteristics for multipath resistance, and cross-constellation consistency checking enables integrity monitoring that two-constellation receivers cannot perform.
What is the difference between L1/L2 and L1/L5 dual-frequency reception?
L1/L2 combines the primary L1 signal with the GPS L2C (civil) signal at 1227.6 MHz. Both allow ionospheric error correction through the dual-frequency differential measurement, and L2 supports full RTK carrier-phase positioning when combined with RTK corrections. L1/L5 combines L1 with the L5 signal at 1176.45 MHz. L5 is transmitted at higher power than L2C, uses BPSK(10) modulation with 10× the chipping rate of L1 C/A, and is substantially more resistant to multipath than L2. For high-precision RTK applications (surveying, precision agriculture), L1/L2 remains common because L2 is well-established in correction networks. For meter-level urban accuracy without RTK (telematics, micromobility), L1/L5 is the preferred choice because of its superior multipath resistance and wider availability across Galileo and BeiDou-3.
How does Galileo's OSNMA service provide spoofing protection?
OSNMA (Open Service Navigation Message Authentication) transmits cryptographic authentication data within Galileo's E1B navigation message using a public key infrastructure maintained by the European Space Agency. A receiver with OSNMA support can verify that the navigation message data it received was signed by the genuine Galileo space segment, making it computationally infeasible for a spoofer to generate plausible fake Galileo signals without breaking the cryptographic scheme. The service has been operational since 2023 and provides genuine protection against the most common category of spoofing attacks. Spoofing GPS only (without also spoofing authenticated Galileo) produces a detectable inconsistency between the GPS-derived position and the Galileo-derived position.
What should embedded firmware do when a GNSS module reports jamming or spoofing detection?
The response depends on the application, but the firmware design should explicitly specify it rather than treating jamming/spoofing detection as an exceptional error. Common responses include: switching to dead reckoning using inertial sensors (IMU/odometer) if available and accepting position uncertainty growth; freezing the last known good position and flagging it as potentially invalid; logging the detection event with timestamp and duration for post-event analysis; raising an alert through the product's communication channel; and refusing to use the GNSS position for safety-critical decisions while maintaining the last dead-reckoned estimate. The specific GNSS module's interrupt line and status registers communicate the detection state, and the firmware must poll or interrupt-service these in the navigation loop.




