GNSS Fundamentals · Dual-Frequency & Precision Positioning
Galileo vs BeiDou: Frequencies, Accuracy and Precision Positioning
Galileo and BeiDou both offer modern navigation signals that can be combined in a compatible receiver. Their shared frequency bands simplify part of the RF design, while their signal definitions, satellite geometry and precision services create different integration and testing requirements.
What is the difference between Galileo and BeiDou? Galileo is the European Union's global navigation satellite system. BeiDou is China's, with global navigation provided by BDS-3. Galileo uses a medium Earth orbit constellation; BeiDou combines MEO, IGSO and GEO layers. Both support code-separated civil navigation signals.
Which is more accurate? Define the receiver mode before comparing results. Galileo E1/E5a and BeiDou B1C/B2a are relevant dual-frequency configurations. A standalone comparison measures their navigation implementations; a precision comparison must also identify the correction service, eligible measurements and PPP processing.
Galileo vs BeiDou at a Glance
| Feature | Galileo | BeiDou / BDS |
|---|---|---|
| System origin | European Union | China |
| Navigation coverage | Global | Global through BDS-3 |
| Orbital architecture | Medium Earth orbit (MEO) | MEO, inclined geosynchronous (IGSO) and geostationary (GEO) layers |
| Signals to specify | E1, E5a, E5b and E6, with the required components | B1I, B1C, B2a, B2b and B3I; distinguish legacy signal requirements |
| Example dual-frequency pair | E1/E5a | B1C/B2a |
| Precision-service example | High Accuracy Service (HAS) | PPP-B2b |
| Engineering priority | Verify exact signals, simultaneous operation, measurement quality and the complete correction-processing workflow. | |
The table identifies architectures and representative configurations. Available signals depend on the satellite payload, health state and selected epoch. References: [1]–[4].
For a wider system overview, see our comparison of global and regional GNSS constellations .
Galileo and BeiDou Frequencies: Where They Align
The two systems share several nominal carrier frequencies. This can support a common RF design, provided its bandwidth and performance suit the selected signals. Each signal still requires its own acquisition, tracking and navigation-message processing.
| Carrier frequency | Galileo | BeiDou | Receiver implication |
|---|---|---|---|
| 1575.420 MHz | E1 B/C | B1C | Shared carrier; distinct signal definitions |
| 1176.450 MHz | E5a I/Q | B2a | Useful second carrier for supported dual-frequency configurations |
| 1207.140 MHz | E5b I/Q | B2I / B2b | Identify the exact signal and service component |
| 1278.750 MHz | E6 B/C | No directly corresponding BeiDou carrier | Confirm E6-B reception if HAS is received over satellite |
| 1561.098 MHz | No directly corresponding Galileo carrier | B1I | B1I support does not establish E1 or B1C support |
| 1268.520 MHz | No directly corresponding Galileo carrier | B3I | Explicit B3I RF and signal support is required |
Carrier frequency, signal bandwidth and receiver filter bandwidth are separate specifications. Frequency references: Galileo OS SIS ICD and manufacturer RF documentation. [3] [4]
E1 and B1C are compatible frequency choices, not identical signals
A receiver tracking Galileo E1 does not automatically decode BeiDou B1C. The same applies to E5a and B2a. Confirm the required data and pilot components, the navigation messages and the simultaneous tracking modes in the delivered receiver configuration.
B1I and B1C need separate attention
B1I occupies a different carrier from B1C. A product described as “BeiDou capable” may therefore have a different RF and processing scope from one designed around B1C/B2a. Request the actual signal list rather than treating a constellation logo as a complete specification.
Which Is More Accurate: Galileo or BeiDou?
Accuracy belongs to a defined positioning workflow. A standalone code-based fix, an RTK-fixed solution and a converged precise point positioning (PPP) solution use different observations, correction inputs and processing states.
Compare equivalent operating modes
For a modern dual-frequency comparison, start with Galileo E1/E5a, BeiDou B1C/B2a and the combined configuration. Hold the receiver hardware, firmware, start procedure, output rate and environmental model steady. Keep each constellation's own geometry and document the signals actually used.
Two-frequency measurements allow processing that addresses frequency-dependent ionospheric delay. They do not remove all antenna, multipath or receiver errors. Report accuracy alongside fresh-output availability and outage duration.
Evaluate geography and satellite visibility explicitly
Both Galileo and BDS-3 provide global navigation. Their orbital architectures create different visible satellite distributions. In BeiDou, GEO and IGSO visibility and the signals available from those payloads deserve particular attention when comparing regions. [1] [2]
A B1C/B2a test is a comparison of that selected signal configuration. It does not include every possible BeiDou measurement. Likewise, “Galileo dual-frequency” should name E1/E5a, E1/E5b or another explicit pair.
Combining constellations and adding a frequency answer different questions. Galileo E1 + BeiDou B1C adds a second constellation at one shared carrier. Galileo E1/E5a and BeiDou B1C/B2a add two-frequency observations within their respective systems.
See our GNSS accuracy and measurement guide for error definitions and reporting conventions.
Galileo HAS vs BeiDou PPP-B2b
HAS and PPP-B2b supply precision correction information to compatible processing engines. They are additional workflows beyond ordinary signal tracking, with different delivery channels, message definitions and applicability conditions.
| Comparison | Galileo HAS | BeiDou PPP-B2b |
|---|---|---|
| Satellite delivery | Galileo E6-B at 1278.75 MHz | B2b correction broadcast from BeiDou GEO satellites at 1207.14 MHz |
| Additional distribution | Official Internet Data Distribution interface | Define the actual correction-input path used by the selected implementation |
| Documented correction systems | Galileo and GPS in the documented service configuration | BDS-3 and GPS in the published PPP-B2b configuration |
| Geographic consideration | Apply the published HAS service-area and service-level conditions | The published service standard defines a regional service for China and surrounding areas; include GEO visibility |
| Processing requirement | HAS message handling and a compatible PPP engine | PPP-B2b message handling and a compatible PPP engine |
| Evidence to retain | Correction reception, applicability, age, solution state, convergence, position error and recovery after interruption | |
Use the applicable service definitions, interface revisions and satellite/signal masks for the test date. References: official HAS documentation, the PPP-B2b interface and service definitions, and primary decoding research. [5]–[8]
The correction broadcaster and corrected constellation can differ
Receiving a Galileo correction broadcast does not mean that the resulting solution uses only Galileo measurements. HAS includes corrections for supported GPS signals. Similarly, published PPP-B2b work describes corrections for BDS and GPS. Identify the measurements actually eligible for each correction set. [5] [8]
Corrections and authentication serve different purposes
Galileo OSNMA authenticates navigation data carried through E1-B I/NAV. It is separate from HAS precision corrections. Log authentication state independently if it is a product requirement; a converged PPP solution is not evidence that navigation data authentication has succeeded. [9]
Why Receiving Corrections Is Only Part of Precision Positioning
A PPP engine combines navigation observations with applicable corrections and its own estimation models. The correction decoder and the position solver may be separate functional blocks. Logging both sides makes it possible to distinguish delivery failures from positioning failures.
Check that a decoded correction matches the relevant satellite, signal, reference navigation data and validity interval before evaluating its effect. Retain the correction age used by the engine and the treatment of stale or missing data. Successful RF tracking or message decoding alone cannot establish that valid corrections reached the position estimate.
How to Compare Galileo and BeiDou in the Lab
The following illustrative program separates standalone navigation from precision-service behavior. Use a controlled scenario and the same DUT where its capabilities permit the required modes.
1. Establish standalone dual-frequency baselines
Run Galileo E1/E5a only, BeiDou B1C/B2a only and both enabled. Disable external precision corrections for this group. Specify the epoch, position, height/reference frame, motion, sky mask, signal components and power at the DUT input.
Use consistent initialization, firmware and output settings. Preserve each constellation's own geometry and payload-supported signals. Compare accuracy, accepted-fix availability and satellites used across several representative epochs or regions. A matched location and epoch do not make the satellite geometries identical.
2. Define what the precision-service comparison is intended to measure
- Complete product workflows: compare the actual HAS-enabled and PPP-B2b-enabled configurations, recording differences in measurements, delivery and processing. The result characterizes those complete configurations.
- Correction or algorithm effects: where both services support a common eligible measurement subset, use that subset and a consistent estimator. Verify masks, reference data and bias conventions before treating a change as a correction-service effect.
Use a location within the applicable service area for each run. Keep corrections consistent with scenario time and navigation data; unrelated live corrections cannot simply be attached to an arbitrary simulated trajectory. Include the required correction-data generation, replay or injection method in the bench design.
3. Interrupt correction delivery while ranging continues
- Establish a baseline: wait until the selected solution meets predeclared validity and error limits for a stated duration. Record its correction and processing states.
- At event T0: stop correction delivery at a defined interface while keeping the navigation RF scenario and observation inputs unchanged. Verify and timestamp the event.
- After an illustrative 60-second gap: restore a fresh, consistent correction stream at event T1. Record input receipt and acceptance by the engine separately.
- Observe recovery: measure the time from T1 to the start of a sustained interval meeting the same acceptance criteria. Extend the observation window if recovery is incomplete.
This isolates a correction-data outage. RF interruption, multipath and navigation-message authentication require their own cases. Repeat the correction-outage procedure for the supported delivery paths, retaining each service's declared handling of expired data.
4. Record the metrics needed to explain the result
| Metric | Definition or evidence |
|---|---|
| Position error | Horizontal and vertical error against truth at matched measurement epochs; declared median and percentile statistics. |
| Accepted-solution availability | Expected epochs with fresh output meeting validity, mode and error criteria, divided by all expected epochs; missing output counts as unavailable. |
| Correction availability and age | Valid, applicable correction coverage for the observations used, including age limits and periods of stale or rejected data. |
| Convergence | Elapsed time from a defined initialization event to the start of an interval meeting the selected precision criteria for a required duration. |
| Post-outage recovery | Time from verified correction restoration to a sustained accepted solution; distinguish incomplete recovery within the test window. |
| Processing diagnostics | Signal and satellite use, correction acceptance, reference-data identifiers, residuals and exposed PPP/RTK state. |
Map the receiver measurement epoch to scenario truth using declared time and coordinate conventions. Host message-arrival time is a separate timestamp. Keep out-of-limit outputs visible in the report, and include an independently aligned truth source in field evaluations.
5. Use the observations to choose the next test
If correction reception remains healthy while position error grows, inspect applicability and estimator behavior. If correction age rises before the solution degrades, examine delivery and expiry handling. If combined navigation helps only at certain epochs, expand the geometry sample. Preserve the scenario, software versions and acceptance criteria for regression testing.
Our GNSS signal simulation workflow covers RF delivery, reference records and receiver logging for a complete bench.
Plan a Galileo and BeiDou Receiver Test
Send your DUT model, required signals, deployment region and test objectives. Specify whether the program covers standalone navigation, HAS, PPP-B2b or another correction workflow, together with the available logging and correction-input interfaces.
Review the NSG8000 GNSS simulator for a configured multi-constellation ranging bench. Confirm the ordered Galileo/BeiDou signals, simultaneous resources and scenario controls. E6-B or PPP-B2b delivery, correction content and receiver processing require an explicit service-test configuration review.
Frequently Asked Questions
Are Galileo E1 and BeiDou B1C the same signal?
No. They share a 1575.42 MHz carrier frequency, but have distinct signal definitions. A receiver needs the appropriate tracking and navigation-message processing for each.
Can Galileo and BeiDou work together?
Yes. A compatible receiver can combine supported measurements from both systems. Confirm the enabled signal pairs, simultaneous tracking configuration and observations actually used in navigation.
Is Galileo plus BeiDou automatically dual-frequency?
No. Galileo E1 plus BeiDou B1C uses one shared carrier. Dual-frequency configurations require two-frequency observations, such as Galileo E1/E5a and BeiDou B1C/B2a.
What is the main difference between HAS and PPP-B2b?
They use different correction messages and delivery arrangements. HAS provides corrections through Galileo E6-B and an official Internet interface. PPP-B2b uses a BeiDou GEO correction broadcast with its own regional service definition. Both require compatible correction handling and PPP processing.
Does receiving B2b prove that PPP-B2b positioning is working?
No. Confirm that the required corrections are decoded, applicable to the observations and accepted by a compatible positioning engine. Verify solution state, convergence and error against truth separately.
Technical References
- European GNSS Service Centre: Galileo programme and orbital architecture .
- China Satellite Navigation Office: BeiDou application service architecture .
- European GNSS Service Centre: Galileo Open Service reference documents , including the OS SIS ICD.
- Hexagon / NovAtel: PwrPak7 installation and operation manual , RF input frequency specifications.
- European GNSS Service Centre: Galileo High Accuracy Service and HAS Service Definition Document .
- China Satellite Navigation Office: PPP-B2b signal-in-space interface specification .
- China Satellite Navigation Office: BeiDou PPP service performance standard , regional service definition.
- Lu and colleagues: Decoding PPP Corrections from BDS B2b Signals Using a Software-defined Receiver: an Initial Performance Evaluation , 2020.
- European GNSS Service Centre: Galileo OSNMA service description .