The satellites disappear in the tunnel. The position can't.
GNSS is superb outdoors and useless in a tunnel — and the position still has to be right. Holding an accurate location through urban canyons, underpasses and indoor stretches means fusing satellite fixes with inertial and motion sensors so that when the sky disappears, the estimate coasts instead of jumping.
DomainWireless, positioning
PlatformsFaststream Radio
ScopeMulti-sensor fusion to continuous position
Binding constraintHold position when the satellites are gone
DisclosureRepresentative programme; customer not named
CONTEXT
Where this started.
Satellite positioning is excellent with a clear sky and degrades sharply without one. In a city the signal reflects off buildings and the fix jumps; in a tunnel or a car park it vanishes entirely. For navigation, tolling, tracking or an autonomous function, a position that disappears or leaps is not acceptable.
The answer is not a better antenna but sensor fusion. An inertial measurement unit, wheel or motion data and a model of how the platform moves let the system dead-reckon through the gap, while the satellite fix, when trustworthy, corrects the drift. The art is trusting each source exactly as much as it deserves, moment to moment.
So the system is built as a fusion problem: honest sensor models, a filter that weights satellite and inertial data by their real reliability, and detection of the reflected, untrustworthy fixes that would otherwise poison the estimate.
CHALLENGES
4 problems, named.
Stated before any of them had an answer.
01
GNSS fails exactly where it's needed
Tunnels, canyons and indoors are where the fix vanishes or reflects; the system has to be best precisely where the satellites are worst.
02
Reflected fixes lie confidently
In a city, multipath produces a satellite fix that looks valid and is metres wrong; trusting it naively is worse than ignoring it.
03
Inertial drifts
Dead reckoning coasts through gaps but drifts over time; it holds position for a while, not forever, and the fusion has to know that.
04
Trust has to be dynamic
The right weighting between satellite and inertial changes second to second with conditions; a fixed blend fails in the hard moments.
ARCHITECTURE
How it was built.
A clear-sky fix is easy. The engineering is the tunnel, the canyon and the car park — coasting on inertial and rejecting the reflections until the satellites come back.
CONTRIBUTION
What Faststream did.
The scope of the work, rather than a capability list.
Sensor models — honest characterisation of the inertial and motion sensors so the fusion knows what each is worth.
Fusion filter — weighting satellite and inertial data by their real, moment-to-moment reliability rather than a fixed blend.
Multipath rejection — detecting and discarding the reflected satellite fixes that look valid and are wrong.
Dead-reckoning — coasting the position through GNSS gaps with bounded, understood drift.
Reacquisition handling — correcting cleanly when the satellites return instead of jumping.
Honest confidence — reporting uncertainty so a consumer of the position knows how much to trust it.
WHAT WAS HARD
The parts that consumed the schedule.
Rarely the subsystem that sounds difficult.
01
Weighting trust in real time
The core difficulty is deciding, second by second, how much to believe the satellite versus the inertial data as conditions change; a fixed answer fails.
02
Catching the plausible-but-wrong fix
A multipath fix in a city looks entirely valid; recognising and rejecting it before it corrupts the estimate is subtle and essential.
03
Bounding the drift
Dead reckoning is only as good as how long it holds; understanding and limiting the drift is what makes coasting through a tunnel trustworthy.
04
Reacquiring gracefully
When the sky returns the estimate has to snap back to truth without a visible jump, which the fusion has to manage deliberately.
OUTCOME
What resulted.
Position that never drops
A continuous location through tunnels, canyons and indoors, coasting where the satellites fail.
No confident lies
Reflected, untrustworthy fixes rejected instead of poisoning the estimate.
Bounded drift
Dead reckoning that holds accurately for the length of a real gap.
Clean reacquisition
A position that corrects smoothly when GNSS returns rather than jumping.
Confidentiality
Customer projects are presented at property, capability, outcome and integration level. Customer names, internal architecture, confidential deliverables and commercial terms are not disclosed. Where a detail would identify a customer it is omitted rather than approximated. More is available under a non-disclosure agreement, within the limits the customer has agreed.
Because the problem is not sensitivity but physics. In a tunnel there is no satellite signal to receive, however good the antenna, and in an urban canyon the signal reflects off buildings so the fix is present but wrong. No receiver improvement fixes a signal that is absent or corrupted, which is why the answer is fusing GNSS with inertial and motion sensors that keep working when the sky does not.
02
What is dead reckoning and what are its limits?
Dead reckoning estimates position from motion — how fast and in what direction the platform has moved since the last known fix — using inertial and vehicle sensors. It lets the system coast through a GNSS gap, but it drifts: small sensor errors accumulate over time, so it holds an accurate position for the length of a tunnel or an underpass, not indefinitely. The fusion has to understand and bound that drift and correct it the moment a trustworthy satellite fix returns.
03
How does it avoid trusting a wrong GNSS fix?
By weighting each source by its real reliability and actively detecting multipath. In a city, a reflected signal can produce a fix that looks valid but is metres off, and blindly trusting it is worse than ignoring it. The fusion filter recognises the signatures of an untrustworthy fix and down-weights or discards it, leaning on the inertial estimate until a genuinely reliable fix is available.