Access Official Technical PDF

Share Summary:LinkedInEmail

GNSS resilience is an important engineering consideration wherever positioning, navigation and timing (PNT) support operational decisions or automated systems. The ION GNSS+ 2018 program brought together topics that clarify what resilience involves: understanding signal limitations, combining complementary sensors, monitoring solution integrity and preparing for interference. These themes offer a useful framework for industrial automation teams assessing how location and time information fits into system design.

The program covered satellite navigation fundamentals, multi-constellation signals, receiver processing, inertial integration, autonomous systems and interference response. Taken together, those subjects point to a practical principle: dependable navigation is not just a question of receiving GNSS signals. It also depends on how a system measures, checks and supplements those signals in its operating environment.

GNSS resilience starts with understanding the measurement

A GNSS receiver estimates position using measurements derived from signals transmitted by navigation satellites. One key measurement is the pseudorange, which represents an apparent distance between a satellite and receiver. It is affected by several sources of error, including the ionosphere, troposphere and multipath—the reception of signals that have reflected off nearby surfaces.

Those effects matter because receiver output is only as useful as the measurements behind it. In urban or otherwise obstructed settings, buildings and other structures can block direct signals or create reflections. The program’s sessions on urban navigation addressed approaches such as detecting non-line-of-sight signals, examining measurement history and using three-dimensional city models. These topics illustrate why a positioning system should be evaluated in the environments where it will actually operate, rather than only under ideal signal conditions.

For automation engineers and system integrators, the same reasoning applies when specifying GNSS-dependent equipment: assess likely obstructions and reflections, understand the receiver’s available measurements, and consider how the system identifies degraded or inconsistent data. The appropriate design depends on the application and its requirements; the program does not prescribe a single solution for every site.

Design for interference, not just normal operation

GNSS signals can be affected by interference. The program distinguished between understanding possible threats and selecting measures to detect, identify or reduce their effects. It also highlighted the value of situational awareness: interpreting receiver behavior in the context of the signal environment helps teams understand whether a change in navigation output may be related to interference or another cause.

Potential mitigation approaches discussed included adaptive antenna arrays and inertial measurement unit (IMU) aiding. The program also covered civil jamming incidents, spoofing detection and signal authentication. These are different aspects of the problem: interference may disrupt reception, while spoofing concerns the presentation of misleading signals. Monitoring and response strategies therefore need to reflect the threat being addressed.

In industrial applications, the practical takeaway is to make interference response part of system planning. Engineers can identify which functions rely on GNSS, determine what behavior is expected when measurements become unreliable, and establish how operators or other system components will recognize a problem. The source program identifies relevant technical approaches but does not establish that any one approach is suitable for all installations.

Combine sensors to support navigation in difficult environments

GNSS and inertial navigation can complement one another. An IMU measures motion-related quantities, which can support dead reckoning when satellite measurements are interrupted or degraded. Sensor integration uses information from more than one source to estimate navigation states; a Kalman filter is one method used in integrated navigation to combine measurements over time.

Effective integration requires more than connecting two devices. The tutorial topics included selecting state variables, understanding observability, accounting for sensor error sources and bandwidth, setting update rates, synchronizing time and considering the physical lever arm between sensors. These details affect how measurements relate to one another and how an estimator interprets them.

The broader sensor-integration program also considered wireless networks, imaging sensors and other navigation sources for GNSS-challenged settings. For autonomous vehicles, the agenda included both traditional multisensor fusion and machine-learning approaches. The implication for system designers is to match sensing and estimation methods to the operating conditions, available data and required behavior—not to assume that adding sensors automatically ensures a robust solution.

Make integrity part of the application design

Accuracy describes how close an estimate is to a reference; integrity concerns whether users can trust that estimate and be alerted when it should not be relied upon. The program connected integrity with autonomous vehicles and other safety-related applications, including work on augmentation systems, multipath modeling and autonomous integrity monitoring.

That distinction is relevant to industrial decision-makers. A position value alone may not communicate whether the underlying solution is suitable for a given action. System requirements should therefore consider how navigation quality is assessed and what happens when confidence is insufficient. The required response will vary by application, but the design question is broadly applicable: how does the system detect that its navigation input may no longer be dependable?

Apply the themes to PNT-dependent systems

The ION GNSS+ program also addressed timing, satellite-system status and the wider infrastructure that depends on PNT. This broader perspective matters because GNSS can provide both location and time, and system designers need to understand which functions depend on each. A failure or degradation in a shared PNT input may have implications beyond a single navigation display.

For engineering teams, a useful review can include:

  • Map dependencies: identify equipment and processes that rely on GNSS position or time.
  • Characterize conditions: consider signal blockage, multipath and potential interference in the intended environment.
  • Review complementary sensors: assess whether inertial or other available measurements can support the application during GNSS degradation.
  • Define integrity behavior: determine how the system recognizes questionable navigation data and communicates that condition.
  • Test the complete design: examine measurement quality, sensor timing and system behavior together.

Conclusion

GNSS resilience is a system-design challenge that spans signal quality, interference awareness, sensor integration and integrity monitoring. The technical themes presented at ION GNSS+ 2018 show why dependable PNT should be treated as more than a receiver specification. Industrial automation teams can use these considerations to clarify dependencies, evaluate operating conditions and define how systems should respond when navigation data is degraded. The result is a more deliberate basis for integrating GNSS into applications where position and time matter.

Access Official Technical PDF

About The Author