GNSS Signals & Receiver Compatibility
GNSS Frequency Bands and Signals Explained: Codes and Modulation
GNSS signals occupy several radio-frequency bands. GPS L1, L2 and L5 are centered at 1575.42, 1227.60 and 1176.45 MHz. Other constellations share some of these frequencies, but use their own signals, ranging codes and navigation-data formats. A matching frequency alone does not establish compatibility.
This guide maps common frequencies to named signals, explains their structure, and shows what to specify for receiver and simulator testing. It is part of the GNSS Simulation 101 hub.
GNSS Frequency Bands: GPS, Galileo and BeiDou
A carrier frequency identifies the nominal RF center. A band also has width: the signal’s spectrum extends around that center. The table below groups representative civil signals by nominal frequency so shared frequencies are easy to recognize.
| Nominal frequency | System and signal examples | Important distinction |
|---|---|---|
| 1575.420 MHz | GPS L1 C/A and L1C; Galileo E1-B/E1-C; BeiDou B1C. | Shared center frequency, different codes and signal structures. |
| 1561.098 MHz | BeiDou B1I. | B1I is not B1C and has a different center frequency. |
| 1278.750 MHz | Galileo E6-B/E6-C. | E6 support and service features must be specified separately from E1/E5. |
| 1268.520 MHz | BeiDou B3I. | Do not infer support from a generic “BeiDou” label. |
| 1227.600 MHz | GPS L2C. | A civil L2 signal distinct from GPS L1 and L5. |
| 1207.140 MHz | Galileo E5b; BeiDou B2I and B2b. | B2I and B2b are distinct signals despite the shared center. |
| 1176.450 MHz | GPS L5; Galileo E5a; BeiDou B2a. | The same nominal center does not make the waveforms interchangeable. |
Representative examples, not a complete signal catalog or a product support specification. GPS frequencies are defined in IS-GPS-200/705/800; Galileo and BeiDou values are supported by their official technical documents.[1] [2] [3] [4] [5]
Three naming traps to avoid
- “L1 supported” is incomplete. Confirm GPS L1 C/A, GPS L1C or another specifically named signal.
- “E5” is broader than E5a. Galileo’s full E5 signal is centered at 1191.795 MHz and includes E5a and E5b. Specify sub-band reception or full-band processing.
- “B1” and “B2” need a suffix. Write B1I/B1C and B2I/B2a/B2b explicitly.
Signal definitions do not establish which satellites or services are usable at a particular test epoch. Check the applicable signal/service status and the receiver’s implementation when building a scenario.
GLONASS: Frequency Channels Need Separate Treatment
Legacy GLONASS L1 and L2 signals use frequency division multiple access (FDMA). Their nominal carrier frequencies depend on a channel index k:
L2: fk = 1246 + 0.4375k MHz
Here, k is a frequency-channel index, not a satellite PRN number. For example, k = −7 gives 1598.0625 MHz on L1 and 1242.9375 MHz on L2. These are calculated channel examples, not a statement about current satellite assignments.
GLONASS also has CDMA signal designs. Do not generalize the legacy FDMA equations to every GLONASS signal; specify the exact signal and interface document.[6]
For system-level differences and constellation selection, read our GPS, Galileo, GLONASS and BeiDou comparison.
Band, Signal, Code and Carrier: Different Layers
| Term | Meaning | Example |
|---|---|---|
| Constellation | The satellite navigation system. | GPS, Galileo, GLONASS or BeiDou. |
| Band / carrier frequency | The RF region and nominal center occupied by a transmission. | GPS L1 at 1575.42 MHz. |
| Named signal / component | A defined waveform or part of it with specified codes and structure. | GPS L1 C/A, GPS L1C pilot, Galileo E1-B. |
| Ranging code | A known sequence correlated with a local replica to estimate delay. | A GPS C/A PRN sequence. |
| Navigation message | Encoded information used in navigation processing. | Satellite orbit, clock, time and health information. |
| Modulation / multiplexing | How codes, data and components are carried and combined. | BPSK, BOC or time-multiplexed components. |
“Carrier + code + navigation data” is a useful introduction to a data-bearing GNSS signal. It is not a universal description of every component: a pure pilot has a ranging structure without navigation-message data.[8] [2]
In code division multiple access (CDMA), multiple satellites can share a nominal carrier frequency while using distinguishable codes. This differs from the frequency-channel separation used by legacy GLONASS FDMA signals.
What Is a GNSS Ranging Code?
A ranging code is a deterministic sequence with useful correlation properties. The receiver searches for the expected code and its delay in the incoming signal. “Pseudo-random” does not mean the sequence is unknown to a compatible receiver, and a PRN code is not inherently encryption.
For CDMA signals, the code assignment helps separate transmissions. Interpret an identifier with its constellation and signal/component; the same number in two protocols need not identify the same signal.
Chip rate is different from navigation-data rate
A chip is an element of the spreading code. A data bit belongs to the navigation message. Their rates can differ by many orders of magnitude.
| Property | Value | Interpretation |
|---|---|---|
| Carrier frequency | 1575.42 MHz | The nominal RF center. |
| C/A code length | 1023 chips | Length of one repeating ranging-code sequence. |
| Code chip rate | 1.023 Mcps | 1,023,000 chips per second. |
| Code period | 1 ms | 1023 ÷ 1,023,000 seconds. |
| Legacy navigation data | 50 bit/s | One data bit lasts 20 ms, spanning 20 C/A code periods. |
These are GPS L1 C/A design values, not generic parameters for every GNSS signal.[1]
The light-travel distance for one C/A chip is approximately 293 m. This is not a 293 m accuracy limit: receivers estimate fractional-chip delay, and measurement quality also depends on bandwidth, noise, multipath and processing. The repeating code phase alone does not provide an unambiguous full satellite-to-receiver travel time.
GNSS Modulation, Data Components and Pilots
Modulation determines how a signal’s code and data affect its waveform. It influences the spectrum and correlation function, so RF bandwidth and receiver processing must match the actual signal structure.
| Signal | Structure example | What to distinguish |
|---|---|---|
| GPS L1 C/A | BPSK spreading with C/A code and legacy navigation data. | Code chips and navigation bits have different rates. |
| GPS L1C | BOC(1,1) data component and TMBOC pilot. | L1C is a different signal from L1 C/A.[3] |
| GPS L2C | Time-multiplexed CM and CL codes; CM carries navigation data. | CM and CL are components, not separate RF bands.[1] |
| GPS L5 | Quadrature I5 data and Q5 pilot components with BPSK spreading. | Both components have defined codes and timing.[2] |
| Galileo E1-B/E1-C | CBOC components: E1-B carries data; E1-C is a pilot. | Component names matter even at the same carrier.[4] |
| Galileo full-band E5 | AltBOC composite containing E5a and E5b. | Full-band processing differs from receiving a sub-band.[4] |
BPSK means binary phase-shift keying. BOC means binary offset carrier and adds a subcarrier structure. CBOC, TMBOC and AltBOC describe particular composite or multiplexed designs; the names are not interchangeable compatibility labels.
A pilot is not an unmodulated carrier
A pure pilot omits navigation-message bits but still contains its defined spreading code and may contain a secondary or overlay code. It can support tracking and integration strategies that avoid unknown navigation-bit transitions. Actual benefit depends on the receiver and conditions. Check the named component and ICD version rather than assuming every channel labelled Q has identical behavior.
What does the navigation message provide?
Depending on the signal, navigation data includes satellite ephemeris, clock parameters, time, health and other system information. Ephemeris supports detailed satellite-state computation over its validity period; almanac is coarser constellation information useful for tasks such as acquisition planning.
The satellite does not broadcast the user’s coordinates. The receiver combines observations and satellite data to estimate position, velocity and time. Continue with how GNSS navigation works. For retained-data effects on startup, use the TTFF and receiver metrics guide.
Code Measurements, Carrier Phase and Doppler
Code pseudorange comes from signal timing. It contains geometric distance plus clock, propagation, hardware and measurement effects. Carrier phase provides a more precise observable but includes an unknown whole-cycle ambiguity; loss of lock and cycle slips require careful handling. Doppler reflects range-rate and clock-frequency effects.[7]
What is code minus carrier?
Code-minus-carrier (CMC) compares code pseudorange P with carrier phase converted into metres:
Use compatible observations from the same satellite, signal/frequency and epoch; φ is in cycles and λ is metres per cycle. Shared geometric, clock and tropospheric terms cancel in a simplified model, but ionosphere, ambiguity, differing biases, multipath and noise remain. A cycle slip changes the ambiguity offset. CMC is therefore a diagnostic combination, not a direct position-error or pure multipath measurement.
Carrier-phase precision alone does not guarantee centimeter-level positioning. Corrections, ambiguity handling, reference quality and operating conditions also matter. See GPS/GNSS accuracy and error measurement for result-level assessment.
Multi-Frequency Is Different from Multi-Constellation
Multi-constellation means using more than one satellite system. Multi-frequency means using observations at more than one carrier frequency. GPS L1, Galileo E1 and BeiDou B1C share 1575.42 MHz: combining them adds constellations, not three distinct carrier frequencies.
Observations on suitably separated frequencies can support estimation or reduction of first-order ionospheric effects. Additional constellations can increase available observations and improve geometry. Neither feature removes all multipath, outages or receiver errors.
Support must exist throughout the receive chain:
- Antenna and RF path: frequency coverage, polarization, gain/noise behavior, filtering and losses.
- Receiver hardware: front-end bandwidth, sampling and processing resources.
- Firmware and configuration: named signals, components, navigation messages and simultaneous combinations.
- Application output: required observables, status fields, solution mode and logging rate.
An antenna advertised for a band does not establish that the receiver decodes every signal in it. Likewise, a simulator’s constellation label does not establish its licensed signals or simultaneous RF configuration.
Specify Signals for Receiver and Simulator Testing
Replace a broad requirement such as “multi-band GNSS support” with named signals, simultaneous combinations and observable outcomes. The following checklist can be used in a test brief or configuration request.
| Requirement | What to specify | What to verify |
|---|---|---|
| Exact signals | Constellation, signal/component, frequency and relevant ICD/service version. | Acquisition, tracking and navigation-data support for each. |
| Simultaneous combination | Signals needed together, satellite/channel load and test duration. | Concurrent operation, not only individual capability listings. |
| DUT configuration | Receiver model, hardware/firmware, enabled features and startup state. | The tested setup matches the required product configuration. |
| RF delivery | Ports, combined or separate bands, antenna/cable path, reference plane and losses. | Required waveform bandwidth and levels at the DUT input. |
| Test conditions | Epoch, motion, signal-level changes, outages and required multipath or obstruction conditions. | Each requested control/model is available in the selected system. |
| Evidence and outputs | Per-signal status, code/carrier/Doppler observations where available, PVT and timing. | Expected signals are used and application criteria are met. |
Illustrative requirement: “Evaluate GPS L1 C/A and L5 I5/Q5 concurrently with Galileo E1-B/E1-C. Confirm component support, RF delivery, relative timing and the DUT’s enabled firmware configuration. Record per-signal tracking, available observables and fresh PVT during a declared signal-level change.”
This is an example test brief, not a claim that a particular simulator configuration supports every item.
For each combination, establish a nominal baseline before applying a declared change. Keep navigation data, geometry, RF path and DUT settings consistent where practical, and record other variables that change. Compare signal tracking with actual solution behavior.
Record RF power with its reference plane and measurement bandwidth. C/N₀ and SNR are different quantities; use the metrics guide to interpret their units and limits.
Continue with GNSS scenario design, the receiver validation test plan or how to choose a GNSS simulator. For the underlying test method, read what GNSS simulation does.
Review Your GNSS Signal Requirements
Send your receiver model, exact signal list, simultaneous combinations, RF input arrangement and test objectives. Our team can review the required configuration, identify options and clarify any uncovered requirements.
Explore GNSS signal simulation systems, including the NSG8000, or review GNSS simulation solutions for your application. Confirm signal support, licenses, interfaces and simultaneous operation for the proposed configuration.
Frequently Asked Questions
What are the GPS L1, L2 and L5 frequencies?
The nominal carrier centers are L1 at 1575.42 MHz, L2 at 1227.60 MHz and L5 at 1176.45 MHz. A frequency label still needs a named signal, such as L1 C/A, L1C or L2C, to define compatibility.
Are GPS L1, Galileo E1 and BeiDou B1C the same signal?
They share a nominal center of 1575.42 MHz but use distinct signal structures and codes. A receiver must support the particular waveform and navigation-data processing, not only the RF frequency.
What is the difference between BeiDou B1I and B1C?
They are different signals: B1I is centered at 1561.098 MHz, while B1C is at 1575.42 MHz. Do not use a generic “B1” entry as proof that hardware or firmware supports both.
Is a GNSS pilot signal just a carrier?
No. A pure pilot omits navigation-message data but retains a defined spreading structure and may include a secondary code. It is not an unmodulated tone.
Does a faster ranging code guarantee better positioning?
No. Code rate and waveform bandwidth affect ranging behavior, but actual position error also depends on signal quality, multipath, geometry, hardware, corrections and processing.
Does multi-constellation support imply dual-frequency support?
No. A receiver can track several constellations near the same carrier frequency. Check the exact signals and distinct frequencies that can be used simultaneously.
Technical References
- GPS — IS-GPS-200N: L1/L2 interfaces, C/A code, L2C and navigation data.
- GPS — IS-GPS-705J: L5 carrier, components and interface requirements.
- GPS — IS-GPS-800J: L1C signal structure.
- European GNSS Service Centre — Galileo OS SIS ICD: Galileo frequency plan and signal/component definitions.
- China Satellite Navigation Office — BD 410002A-2022: GNSS signal identifiers and frequency entries. See also the ESA BeiDou Signal Plan.
- ESA Navipedia — GLONASS Signal Plan: legacy FDMA channel equations and distinct CDMA designs.
- ESA Navipedia — GNSS Basic Observables: pseudorange, carrier phase and Doppler models.
- ESA Navipedia — GNSS Signal: carrier, ranging-code and navigation-data fundamentals.
Use the applicable specification revisions and change notices for implementation work. Public signal definitions describe the interfaces; device and simulator support must be verified separately.