If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor


From Navipedia
Jump to navigation Jump to search

Title Correlators
Edited by GMV
Level Advanced
Year of Publication 2011
Logo GMV.png

Correlations are the key operation for GNSS receivers to synchronize with the incoming signal, generate GNSS observables, and retrieve the navigation message that will be used to provide a navigation solution later on. The reason is that GNSS signals transmit a ranging code modulated into the carrier, also called Pseudo-Random Noise (PRN) code, which not only spreads the spectrum but also allows retrieving ranging information.

Pseudo-Random Noise Codes

Pseudo-Random Noise (PRN) Codes - also called ranging codes - are a sequence of pulses that are used by GNSS to spread the spectrum of the transmitted signal. For this purpose, several types of codes are used, and some examples are given here (for further information on the codes used by each system, refer to the respective SIS ICDs):

  • GPS L1 C/A uses Gold codes[1] that are actually a combination of two maximum length codes[2].
  • GLONASS uses only one maximum length code. Since it uses an FDMA approach, low cross-correlation characteristics are not so critical for this system.
  • Galileo uses tiered codes, a combination of medium length primary code with a smaller length secondary code. Some of these secondary codes are memory codes, which are not generated through linear feedback shift registers (LFSR)[3] like the others: instead, they are stored in the local memory. The advantage of these codes is that they are harder to decode by unauthorized users.
Figure 1:Example of auto-correlation and cross-correlation between GPS PRN1 and GPS PRN17, without noise.

The choice of these codes for each specific signal is a trade-off between:

  • Code length: the longer the code, the smaller the code cross-correlation properties, and the higher number of codes can be generated. Nevertheless, the receiver takes more time to acquire the signal. The code length is also limited by the navigation symbol boundaries, hence related to bit rate.
  • Code chipping rate: the higher the chipping rate, the wider the signal bandwidth will be (imposing wider front ends at the receiver), but better ranging accuracies can be potentially achieved.
  • Code characteristics: although not so critical in FDMA GNSS (e.g. GLONASS), which guarantee satellite separation using different frequencies, ranging codes are selected to have high auto-correlation values and low cross-correlation values. This characteristic guarantees the separation between satellites that use concurrent spectrum (e.g. GPS and Galileo).

As an example, Figure 1 depicts the auto-correlation of GPS PRN1 and the cross-correlation between GPS PRN1 and GPS PRN17. It can be seen that regardless of the delay considered, the cross-correlation always provides low values, while the auto-correlation (correlation between PRN1 and itself) presents a peak only when both replicas are aligned.

The peak can be seen at delay = 1023, since the length of the code is 1023 chips. In addition, when both replicas are aligned, the peak value is the sum of all absolute values of the chips, yielding the code length of 1023. This is observed since no noise was considered.

Correlation: Mathematical Model

The continuous correlation between two signals, x and y, in the time domain, can be defined as:

[math]\displaystyle{ R_{xy}(\tau) = \int_{-\infty}^\infty x(t)y^{*}(t-\tau) dt\, }[/math]

where "*" denotes the complex conjugate. When x=y, this is also called the Auto-Correlation Function (ACF).

Considering a low-pass signal with constant power, as the ones processed by GNSS receivers, the correlation function can be written as:

[math]\displaystyle{ R_{xy}(\tau) = \lim_{T \to \infty} \frac{1}{2T} \int_{-\infty}^\infty x(t)y^{*}(t-\tau) dt\, }[/math]

The power spectral density of a signal is defined by the Fourier transform of the auto-correlation function, and can be written as:

[math]\displaystyle{ G(f) = \int_{-\infty}^\infty R_{xx}(\tau) exp[-j2\pi f \tau] dt\, }[/math]

Finally, since GNSS receivers deal with digitized signals, the discrete auto-correlation function is given by:

[math]\displaystyle{ R_{xx}(k) = \sum_{n=-\infty}^\infty x[n]x^{*}[n-k]\, }[/math]

Block Diagram

The block diagram, zoomed-in from the Digital Signal Processing block is depicted in Figure 2, where the Doppler removal block is omitted for clarity reasons. Furthermore, only the generation of the Prompt (P) replica is considered, i.e. the replica that is generated at the receiver so as to align with the incoming code.

Figure 2:Correlators Block Diagram.

The local code is generated according to an input code delay, which indicates the quantity by which the code should be shifted before correlating it with the incoming signal. From the previous definitions, it is clear that when the local replica is aligned with the incoming signal, the correlation output will be maximum.

Since real life signals are subject to noise and other disturbances, the assessment of the correlation output is rarely performed on a single shot. In fact, the receiver uses Integration & Dump (I&D) blocks to integrate the correlation outputs over time. The main objective is to combine the correlations from consecutive signal data with the PRN codes replica, in order to increase the power of any potential peak and to reduce the inherent noise. GNSS receivers often use a combination between coherent and non-coherent integrations, as discussed here.

Effect of the Modulation on Auto-Correlation Function

The shape of the Auto-Correlation Function (ACF) is affected not only by the PRN code's characteristics, but also by the signal modulation itself. As an example, Figure 3 presents the normalized Auto-Correlation Functions for BPSK(1) (used in GPS L1 C/A), BOC(1,1) (used in Galileo E1-B), and CBOC(6,1,1/11) (used in GPS L1-M and Galileo E1-B).

Figure 3:Auto-Correlation Functions (left) and Power Spectral Densities (right) for modulations in L1 band: example for Open-Service GPS and Galileo.

Bearing in mind that GNSS receivers aim at tracking the peak of the auto-correlation function using the prompt correlator, and adjusting its delay to keep high auto-correlation values, it is rather intuitive to infer that narrower autocorrelation peaks potentially yield better accuracies[footnotes 1]. In fact, an ill-formed prompt local replica will lead to a lower correlation output for small variations around the center. As a consequence, it can be inferred that BOC modulations can reach better accuracies, being CBOC the best one, when looking at the GPS and Galileo Open-Service signals in the L1 band. When looking at the Power Spectral Density (PSD), this can be explained by the wider bandwidths of the BOC signals: the drawback is that the receiver needs wider front ends in order to process the full signal.

The main drivers for including the BOC modulations in GNSS are[4]:

  • To guarantee compatibility while supporting interoperability among GNSS.
  • To provide signals that are more robust in harsh environments such as noise, multipath and interference.
  • To reduce self-interference.

BOC modulations present additional side peaks (in Figure 3 for offsets of 0.5 chips). At receiver level, additional processing may be required in order to guarantee that the tracking loops are actually tracking the main peak, and not one of the side peaks.

Finally, when the lag between the local replica and the incoming signal is higher than 1 chip, the auto-correlation is minimum, and only noise will be observed.


  1. ^ Actually, GNSS receivers also use additional correlators to track the auto-correlation peak, as described here.

Related articles


  1. ^ Gold code in Wikipedia
  2. ^ Maximum length code in Wikipedia
  3. ^ LFSR in Wikipedia
  4. ^ “Status of Galileo Frequency and Signal Design”, Guenter W. Hein, Jeremie Godet, Jean-Luc Issler, Jean-Christophe Martin, Philippe Erhard, Rafael Lucas-Rodriguez and Tony Pratt, Proceedings of the 15th International Technical Meeting of the Satellite Division of The Institute of Navigation (ION GPS 2002), September 24 - 27, 2002, Oregon Convention Center, Portland, OR.