GP-Probe TGE2 sends a large set of raw GNSS data to GP-Cloud from three embedded GNSS receivers and RF signal analyzer, enabling interference classification into spoofing and jamming.
With the GP-Probe TGE2, it is possible to determine which attack scenario was used and what constellations were affected by spoofing, and which were jammed.
Below in the picture is an example of a complicated spoofing attack detected by GP-Probe TGE2 in conjunction with GP-Cloud. The attack began with 10 minutes of jamming of all constellations then GPS + Galileo spoofing combined with GLONASS jamming:
Supported Classification
Spoofing
The spoofing status is determined by the detection of false GNSS signals. Calculated for each constellation separately.
Only supported by GP-Cloud algorithms. The Onboard Signal Processing option of GP-Probe can solely detect anomalies caused by spoofing.Jamming
Interference resulting in reduced SNR and number of visible satellites.
Only supported by GP-Cloud algorithms. The Onboard Signal Processing option of GP-Probe can solely detect anomalies caused by jamming.Interference
Interference detected by the built-in RF spectrum analyzer but not resulting in degradation of GNSS signals reception quality.
Anomaly
The system is capable of detecting any unusual behavior of GNSS signals that deviate from their usual patterns. Anomalies can be caused by spoofing with insufficient signal power.
Low Position Accuracy
When the accuracy of coordinates produced by an embedded receiver on the first channel of GP-Probe TGE2 goes beyond the set limits, this status is shown.
