Software-Defined Radio · GNSS · Assured PNT

Navigation that keeps working
where GPS goes silent

We build SDR-based receivers in which signal processing lives in the software domain. Four bands at once, six GNSS constellations plus an additional LEO-PNT layer, spoofing detection at the level of correlation samples and complete independence from GPS L1 — the platform stays controllable under electronic warfare, spoofing and jamming.

4
frequency bands simultaneously
6
constellations — Galileo and GLONASS CDMA at the core
0
altitude and velocity limits
<2 s
response to detected spoofing

Four decisions that change how a receiver behaves under pressure

Four-band receiver

Four independent RF chains tracking simultaneously across L1/E1/B1I/B1C, L2/G2, L5/E5a/B2a/NavIC L5 and E6/B3I. Each band is handled by its own software channel, so losing or jamming one of them does not stop the navigation solution.

  • Independent ADC and front-end per band
  • Fourth chain configurable for E6/B3I or the NavIC S band
  • Cross-frequency consistency checking of measurements
  • Ionospheric correction without external services

Spoofing resistance

Spoofing detection runs before a position is ever computed: the receiver analyses correlation-function distortion, power level and distribution, Doppler consistency and signal angle of arrival.

  • Multi-peak and Early-Late correlation analysis
  • Cross-validation between constellations and bands
  • Automatic fallback to trusted-signals-only mode

No dependence on L1 or GPS

The receiver needs GPS L1 neither for a cold start nor to sustain a solution. Navigation is formed from whatever combination of signals is available — Galileo E5/E6, GLONASS L3OC/L2OC (CDMA), BDS B2a/B2b/B3I, NavIC L5 and S.

  • Direct signal acquisition without L1 C/A assistance
  • Operation with L1 completely suppressed
  • A solution on Galileo + GLONASS CDMA alone, with no GPS measurement
  • LEO-PNT as a separate layer when MEO signals are fully denied
  • Ready for Galileo OSNMA and authenticated signals

No altitude limits

Our solutions carry no CoCom thresholds (18 km / 515 m/s). The dynamic model is built for high altitude, supersonic speeds and high acceleration without loss of lock.

  • Operation at suborbital altitudes
  • Extended Doppler search range
  • Tracking through high-jerk manoeuvres

Six GNSS constellations and a LEO layer above them

Every constellation is a separate, interchangeable measurement resource. The receiver computes a solution on whatever subset remains available and treats disagreement between sources as independent evidence of spoofing. Galileo and the GLONASS CDMA signals give the most here: a modern signal structure with a pilot component is exactly what an SDR receiver turns into sensitivity margin. Above GNSS sits a separate tier — LEO-PNT, low-orbit signals that are an order of magnitude more expensive to jam.

BeiDou / BDS

global · BDS-3
  • B1I
  • B1C
  • B2a
  • B2b
  • B3I

The densest coverage over Asia and the Middle East. The PPP-B2b service delivers corrections straight from the satellite — decimetre accuracy with no ground link and no internet.

NavIC / IRNSS

regional
  • L5
  • S band

The only system with an operational S band (2492.028 MHz) — 1.3 GHz above every other GNSS. Typical L-band jammers do not cover it, which is why NavIC often remains the last trusted source.

GPS

global
  • L1 C/A
  • L1C
  • L2C
  • L5

An equal source rather than the basis of the solution: on detected anomalies it is excluded entirely, with no degradation of navigation.

QZSS

regional
  • L1
  • L2C
  • L5
  • L6

Highly elliptical orbits give large elevation angles — useful in urban canyons and mountainous terrain across the Asia-Pacific region.

LEO-PNT

low orbit · 500–1200 km
  • Iridium STL
  • Xona PULSAR
  • ESA LEO-PNT
  • SoOP

A satellite 700 km away instead of 20,000: the signal arrives 25–30 dB stronger, so the same jammer denies it at an order of magnitude shorter range. Fast motion produces large geometry change within tens of seconds — the solution converges faster, and faking the consistent Doppler dynamics of an entire LEO constellation is practically impossible.

SBAS corrections are received as well: EGNOS, WAAS, MSAS and GAGAN. The set of active constellations and signals is set by configuration and changes with a firmware update — no hardware replacement involved.

SDR instead of hard-wired logic

In a conventional receiver, correlation and tracking are baked into an ASIC — changing behaviour in response to a new threat is impossible. We move the entire chain after the ADC into the programmable domain: FPGA for streaming correlation, CPU for decisions. A new spoofing signature or a new constellation signal is a firmware update, not a new hardware batch.

  1. 01

    Wideband front-end

    Four channels, low-noise amplifiers, tunable filters and high-resolution ADCs to preserve headroom under strong interference. The dynamic range is designed for both weak MEO signals and far stronger LEO ones.

  2. 02

    FPGA correlation core

    Hundreds of parallel correlation channels with access to raw I/Q samples and the full correlation-function profile. Pilot and quasi-pilot are tracked as a pair — coherent accumulation continues where data-channel tracking is no longer possible.

  3. 03

    Trust assessment layer

    Peak-distortion, power, Doppler and geometry metrics build a trust rating for each satellite individually.

  4. 04

    Navigation filter

    Tightly coupled processing with IMU and odometry: untrusted measurements are excluded, the solution keeps running.

DNS-4B platform

Technical specifications of the DNS-4B platform
Frequency bandsL1/E1/B1I/B1C · L2/G2 · L5/E5a/E5b/B2a/NavIC L5 · E6/B3I
Fourth chain (option)E6/B3I or NavIC S band — 2492.028 MHz
ConstellationsGalileo, GLONASS, GPS, BeiDou (BDS-3), NavIC (IRNSS), QZSS; SBAS: EGNOS, WAAS, MSAS, GAGAN
Galileo signalsE1-B/C, E5a-I/Q, E5b-I/Q, E6-B/C; OSNMA, E6 HAS
GLONASS signalsCDMA: L1OC, L2OC, L3OC (pilot + data); legacy FDMA: L1OF, L2OF
Component processingpilot, quasi-pilot with data prediction (data wipe-off); coherent integration up to 1 s
BDS signalsB1I, B1C, B2a, B2b, B3I; PPP-B2b corrections straight from the satellite
NavIC signalsL5 and S; support for the modern NVS-series satellites
LEO-PNTdedicated low-orbit signals (Iridium STL, Xona PULSAR, ESA LEO-PNT) and a signals-of-opportunity mode
Doppler search rangeup to ±45 kHz — covers LEO dynamics and high-speed platforms
Channel countup to 480 software tracking channels
Accuracy (RTK / PPP)1 cm + 1 ppm / decimetre level
Standalone accuracy< 1.2 m CEP (multi-frequency)
Update rateup to 100 Hz
Altitude / velocity limitsnone (no CoCom thresholds)
Spoofing detectioncorrelation, power, Doppler, cross-constellation (GPS↔Galileo↔BDS↔NavIC)
Inertial supporttightly coupled IMU integration, GNSS-denied coasting mode
InterfacesUART, USB, Ethernet, CAN, PPS; NMEA-0183, RTCM 3.3, proprietary binary protocol
Power5–36 V, 3.8 W typical
Operating temperature−40…+85 °C
Updatesin-field FPGA and algorithm firmware, signed images

Typical parameters of the base configuration are shown. Exact values for your form factor and integration are provided on request in the technical package.

Where this already makes sense

Unmanned platforms

Holding route and return point inside an active EW zone, when L1 is unavailable entirely.

High-altitude vehicles

Balloons, sondes and suborbital carriers — no altitude or velocity thresholds in the firmware.

Ground vehicles

Convoys and single vehicles: position-spoofing control, operation through intermittent reception.

Maritime platforms

Robust positioning under coastal jamming and a record of every spoofing event.

Time synchronisation

Trusted time for networks and power grids with independent verification of the signal source.

Spectrum monitoring

Fixed sites recording and classifying jamming and spoofing events with geolocation.

Technical documentation

Public product materials are available as direct PDF downloads. Pick a document — the download starts right away.

  • Loading the document list…

Let's talk about your task

Tell us about the platform, the operating conditions and the accuracy you expect — we will put together a configuration and an integration plan.