Tutorial Series · Part 21 of 27
Loose Coupling vs Tight Coupling
Compare fusing a receiver PVT solution against raw GNSS measurements in GNSS/INS integration.
Navigation from First Principles
This article is part of an ordered course. Use the previous and next links to stay in sequence.
GNSS/INS integration can happen at different levels. A loosely coupled system fuses the GNSS receiver’s position/velocity/time solution. A tightly coupled system fuses raw or preprocessed satellite measurements such as pseudorange and Doppler. Groves’ book is a useful broad reference for integrated navigation architectures.1
The problem
If a GNSS receiver cannot produce a full position fix, a loosely coupled filter may receive nothing useful. A tightly coupled filter can sometimes still use partial satellite measurements, because it does not require the receiver to output a complete PVT solution first.
Loose coupling
The GNSS receiver solves:
The navigation filter then uses this as a measurement:
This is simpler and modular.
Tight coupling
The navigation filter directly predicts measurements such as pseudorange:
The filter update uses each satellite measurement individually. Navipedia’s GNSS observables and measurement-modelling pages are good supporting references for these raw measurement terms.23
Interactive demo: coupling architecture simulator
The demo below keeps the maths lightweight and focuses on the architectural distinction: loose coupling updates only when the receiver can produce PVT, while tight coupling can still use partial raw measurements in the three-satellite teaching case.
Loose vs Tight Coupling
Read the three views together: the route shows the estimate, the sky plot shows how many satellites survive, and the block diagram shows whether the filter receives a full receiver fix or only partial raw measurements.
What to watch
- With four or more good satellites, both modes pull the estimate back toward truth.
- When the receiver falls below its PVT threshold, loose coupling stops correcting and just coasts on INS.
- Tight coupling can still extract some value from partial measurements when the receiver itself cannot declare a full fix.
- The extra robustness comes with more measurement-modelling complexity.
Try this
Drive into the outage zone until the receiver no longer has enough satellites for PVT. In loose mode, the fused path simply follows inertial drift. Switch to tight mode and keep three satellites visible to see the partial correction survive.
Where this breaks
Tightly coupled integration is not automatically better in every implementation. It requires careful measurement modelling, satellite ephemerides, clocks, quality control and filter design. The right framing is trade-off, not slogan.
Footnotes
-
Paul D. Groves, Principles of GNSS, Inertial, and Multisensor Integrated Navigation Systems, Second Edition, Artech House, 2013. https://uk.artechhouse.com/Principles-of-GNSS-Inertial-and-Multisensor-Integrated-Navigation-Systems-Second-Edition-P1557.aspx - Core textbook reference for navigation systems, GNSS, INS, multisensor integration, coordinate frames, dead reckoning, feature matching and environmental aiding. Accessed 2026-06-11. ↩