Keeping time in contested environments: Assured synchronization beyond GNSS

In defense and aerospace operations, precision timing is a foundational requirement. Secure communications, coordinated avionics and multi-domain operations all depend on trusted, assured and synchronized time.

But that foundation is increasingly under pressure. Reliance on GNSS alone has become a growing operational risk, as jamming, spoofing and other forms of interference are now routine in contested environments. When satellite signals are degraded or denied, maintaining trusted time across platforms becomes a critical challenge.

Meeting that challenge requires timing architectures that can bridge legacy military interfaces and modern, network-based synchronization, while continuing to operate reliably beyond GNSS. This is where the integration of STANAG and Have Quick time codes into the edgeSync+™ Series OSA 5422 PTP grandmaster becomes particularly relevant, as part of a broader shift towards more resilient and interoperable timing architectures.

Why this matters

For decades, NATO platforms have relied on STANAG-based time of day (ToD) and Have Quick timing to ensure radios hop together, mission systems stay aligned and coalition forces remain interoperable.

Delivering these time codes, however, has typically required multiple components:

• GNSS receiver
• ToD converter
• Have Quick generator
• Serial interface module

Each adds SWaP (size, weight and power), complexity and potential points of failure.

The OSA 5422 consolidates these functions into a single platform, with native support for both STANAG and Have Quick, alongside NTP, PTP and White Rabbit.

What’s new in the OSA 5422?

The platform now directly generates key NATO timing formats:

• STANAG 4430 / XHQ
• STANAG 4246 HQ I / HQ II
• STANAG 4372 HQ IIA
• Have Quick ICD ToD

All supported time code formats for the OSA 5422 are detailed in our data sheet here.

These formats provide essential benefits:

• Standardized time (year, day, hour, minute, second)
• Deterministic, low-jitter timing
• Support for:
  
  • Time of day (ToD) – absolute time reference
  • Word of day (WoD) – encoded timing/control data used for synchronization
  • Hopping sequence – the actual frequency pattern radios follow

This allows aircraft, radios and mission systems to interface directly without external converters or adaptation layers.

Why this matters now

Timing is under pressure. GNSS disruption is an operational reality, and when signals are lost, timing must be maintained locally.

The OSA 5422 supports this through:

• High-performance holdover
• Network-based synchronization (NTP/PTP/White Rabbit)
• Optical cesium clock integration

Platforms span generations

Legacy systems remain in service alongside modern networks.

STANAG serial interfaces	✓
Packet-based timing	✓
Both operating simultaneously	✓

SWaP constraints continue to tighten

Reducing multiple devices to a single platform directly improves efficiency, maintainability and deployment flexibility.

Interoperability is essential

Coalition operations require consistent timing across platforms, domains and generations.

Where it applies

Air forces

• Have Quick radios
• Synchronized avionics systems
• Legacy fleet upgrades

Naval forces

• Mixed radio environments
• STANAG for navigation + PTP for combat systems
• Ship-wide synchronization

Ground forces

• Tactical radio networks
• Mobile command posts
• Hybrid analog/IP environments

A more unified approach to resilient timing 

The integration of STANAG and Have Quick time codes into the OSA 5422 is less about adding features and more about simplifying and strengthening timing architectures.

By combining legacy interoperability with modern synchronization and resilient holdover, it enables a more unified approach to timing – one that is better hardened for contested, multi-domain operations.

Originally published April 1, 2026. Updated April 2, 2026.