Protected constellation, frequency and desired GNSS signal condition.
Performance evidence
GNSS Anti-Jam & Anti-Spoof Test Planning
A credible GNSS resilience test links the quoted configuration to a defined signal or threat scenario, an explicit system boundary, recorded receiver or host outputs and measurable pass/fail criteria.
A credible GNSS anti-jam or anti-spoof acceptance test links the quoted hardware and software configuration to a defined RF scenario, explicit system boundary, synchronized measurements, pass/fail limits and recovery criteria. A demonstration video alone does not establish performance.
Supplied demonstration
NOVA-S65 platform video.
This demonstration is provided as integration evidence. It is not a substitute for a configuration-specific acceptance report with stated RF conditions and pass/fail criteria.
Choose the test method for the evidence required
| Test method | Useful evidence | Important limitation |
|---|---|---|
| Bench and interface check | Power, communications, RF path, receiver outputs and configuration control | Does not reproduce spatial or platform effects |
| Simulator or conducted RF test | Repeatable signal, interference and receiver-response comparison | System boundary and channel architecture must be stated |
| Record and replay | Repeatable regression against a captured RF environment | Evidence is limited to the recorded scenario and playback setup |
| Radiated or chamber evaluation | Antenna, spatial processing and integrated RF-chain behavior | Facility geometry, calibration and installation representation matter |
| Representative-platform check | Mounting, cabling, self-interference and host-system response | Must remain authorized and cannot replace controlled repeatability |
The European Space Agency Navigation Laboratory lists GNSS signal simulators, signal recording and playback, anomaly simulation and an anti-spoofing test bed among its receiver-evaluation capabilities. See the ESA Navigation Laboratory overview. A supplier report should state which method was used and what part of the complete system it evaluates.
Build a buyer-ready acceptance record
| Record stage | What to capture | Why buyers need it |
|---|---|---|
| Configuration control | Hardware identifier, software version, interfaces, setup drawing and calibration state | Links the result to the quoted system |
| Baseline | Desired GNSS condition, tracked signals, receiver status and host output before disruption | Creates a reference for comparison |
| Applied scenario | Waveform or threat definition, bandwidth, power, geometry, timing and protected bands | Makes the exposure repeatable and comparable |
| System response | Synchronized RF, receiver, alert and host-system outputs | Shows what happened across the stated system boundary |
| Recovery | Clear condition, reacquisition, return to trusted output and repeated-run result | Verifies behavior after the disruption ends |
Acceptance should use one agreed matrix for the supplier and buyer. Any published suppression, detection or recovery result should be read together with its test conditions and measurement point.
Information to capture
Waveform, bandwidth, input power, direction count and geometry.
Antenna array, processing electronics, receiver and host-platform interfaces.
RF, C/N₀, position, timing, availability or another agreed observable.
Mounting, cabling, radome, nearby emitters, voltage and environment.
Pass/fail thresholds, repetitions, records and responsible parties.
Suggested validation stages
- Document reviewConfirm the configuration, interfaces and acceptance matrix.
- Bench verificationCheck power, communication and protected-signal behavior.
- Controlled RF evaluationApply the agreed scenario in an authorized test environment.
- Representative-platform checkVerify installation effects and host-system behavior.
Questions procurement teams ask
What should a GNSS anti-jam test report include?
Record the quoted hardware and software configuration, protected constellations and bands, desired-signal condition, interference waveform, bandwidth, power, direction and geometry, system boundary, measurement point, receiver or host outputs, pass/fail limits, repetitions and recovery behavior.
Is a headline suppression value enough for acceptance?
No. A suppression figure is only comparable when the waveform, input level, geometry, protected bands, system boundary and measurement method are stated. Platform installation and receiver behavior should be checked separately under agreed conditions.
Which outputs should be logged during a GNSS resilience test?
Use synchronized timestamps to record the applied RF condition and relevant outputs such as C/N₀, tracked satellites, receiver solution status, position or timing error, alerts, host-system mode, loss or rejection behavior, reacquisition and recovery. The required list depends on the stated system boundary.
Is a demonstration video sufficient acceptance evidence?
No. A video can show installation or visible host behavior, but it does not establish the RF waveform, input level, geometry, protected bands, measurement point, configuration or pass/fail result unless those items are documented separately.
How should GNSS anti-spoofing behavior be evaluated?
Use an authorized simulator, record-and-replay setup or other controlled facility with a defined threat model. Record detection, alert latency, mitigation or rejection, position or timing behavior, host-system response, false alarms and recovery to trusted navigation.
RF interference and spoofing tests must be conducted in properly authorized, controlled or shielded facilities and in accordance with applicable spectrum rules.
Next step
Build a configuration-specific acceptance brief
Share platform, protected bands, interfaces and project timing. Zhiyunlai will confirm a suitable starting configuration and the information needed for validation.