HaveQuick is a frequency-hopping, anti-jam (AJ) and low probability of intercept (LPI) communication system developed by the United States Department of Defense for secure tactical voice and data links. In the context of precision timing, frequency control, and synchronization, HaveQuick is fundamentally a time-division multiple access (TDMA) system whose core operational integrity is entirely dependent on high-accuracy, network-wide time-of-day (TOD) synchronization. It uses a derived, encrypted timing signal to synchronize the hopping patterns and time-slot allocations of all participating transceivers, making precise time a critical enabling component of its anti-jam and channel access capabilities.
---
**Technical Background and Principles**
Developed in the 1980s, HaveQuick was designed to provide jam-resistant UHF (225-400 MHz) communications for tactical aircraft. Its underlying principle is that transmitting on a single, predictable frequency makes a signal vulnerable to jamming. By rapidly hopping across many frequencies within the UHF band according to a pseudo-random sequence, the signal is dispersed, requiring a jammer to cover a much wider bandwidth to be effective.
The synchronization of this hopping sequence is where precision timing becomes paramount. HaveQuick employs a Time-of-Day (TOD) based synchronization scheme. The TOD is a precise reference time, typically derived from a master clock (which itself may be synchronized to GPS). This TOD is then encrypted using a classified algorithm and key material to generate a network-specific seed. This encrypted TOD seed is distributed to all participants, often via a brief, secure transmission at the start of a mission.
All transceivers in the network then use this common encrypted seed to compute identical hopping patterns and time-slot schedules. Because the encryption ensures unpredictability, an adversary cannot easily deduce the hopping sequence. However, for this to work, every radio must be able to compute the sequence at the exact same instant—hence the requirement for precise TOD synchronization. A small timing error between two radios means they are not on the same frequency at the same time, resulting in a lost link.
---
**Relation to Timing and Frequency Applications**
HaveQuick transforms the problem of frequency synchronization into a problem of time synchronization. The relationship is governed by its TDMA structure:
**Time Base:** The fundamental time unit in HaveQuick is the 32.768 kHz clock, which is divided down to create precise time slots. The entire network is framed into a superstructure of cycles (12.8 minutes), frames (12 seconds), and time slots (7.8125 ms or 15.625 ms). **Network synchronization means aligning all radios to this master TDMA frame structure.**
**Synchronization Sources:** The master TOD can be sourced from:
**GPS:** The most common and precise source, providing UTC time with nanosecond-level accuracy.
**An External Time Standard:** Such as an IRIG-B signal from a ground-based time server.
**An Onboard Precision Oscillator:** A high-stability oscillator (e.g., a Rubidium atomic clock or a Chip Scale Atomic Clock - CSAC) can maintain a holdover TOD for periods when GPS is denied, though its accuracy degrades over time.
**Frequency Control:** The hopping synthesizer within each HaveQuick radio must be exceptionally agile and accurate. It must change frequency within the guard time between time slots (typically <100 microseconds) and settle to the correct frequency within the allocated slot's frequency tolerance (usually within a few hundred Hz). This requires a highly stable local oscillator, often disciplined by the same TOD source, to ensure low phase noise and fast switching.
**Key Specification - Synchronization Accuracy:** For reliable communication, the time-of-day error between any two radios in the network must be significantly less than the duration of a time slot. For a 7.8125 ms slot, an alignment error on the order of **1-2 milliseconds or less** is typically required. More advanced systems and newer iterations like HAVE QUICK II require tighter tolerances to support higher data throughput and denser networks.
---
**Key Parameters and Specifications**
**Frequency Range:** 225.000 to 399.975 MHz (UHF band).
**Channel Spacing:** 25 kHz.
**Modulation:** Typically FSK (Frequency Shift Keying) or PSK (Phase Shift Keying) for digital data.
**Hopping Rate:** The dwell time per frequency can vary but is tied to the time slot duration. It can be on the order of several hundred hops per second.
**Number of Hopping Frequencies:** The system can hop across a preset list of up to 100 or more frequencies within the UHF band.
**Synchronization Accuracy:** Requires TOD alignment to within ~1-2 ms for standard operation. Precision is often maintained via 1 PPS (Pulse Per Second) signals from GPS receivers.
**Time Slot Duration:** Standard slots are 7.8125 ms (for 32 slots per 250 ms sub-frame). Newer modes may use 15.625 ms slots for longer messages.
**Network Entry:** A new user must acquire the current TOD and network crypto variables to synchronize its local counter and begin computing the correct hopping pattern and slot schedule.
**Encryption:** Uses the U.S. National Security Agency (NSA)-sanctioned cryptographic algorithms (historically KGV-13, KGV-8, or newer equivalents like the COMMSEC Module) to encrypt both the TOD seed for synchronization and the voice/data payload.
---
**Typical Use Cases**
**Tactical Air Networks (TACNET):** The primary application. Enables secure, jam-resistant voice and data communication between fighter aircraft, bombers, tankers, and ground controllers in contested environments.
**Ship-to-Air and Ship-to-Ship Links:** Used by naval vessels to communicate with aircraft and other ships, forming part of the broader naval communications architecture.
**Ground-Based Air Defense:** Integrates air defense assets (e.g., radar stations, missile launchers) into the tactical air picture via HaveQuick links.
**Multi-Domain Operations:** Provides a resilient backup or complementary link to other systems like Link 16, often serving as a voice fallback when the primary data link is degraded or for initial network entry.
**Training and Readiness:** Allows military forces to practice operating in GPS-denied or heavily jammed environments by using HaveQuick's inherent AJ characteristics, with timing often maintained by local, high-precision oscillators.
---
**Related Terms and Cross-References**
**Link 16 / JTIDS / MIDS:** A related but more advanced tactical data link that also uses TDMA and frequency hopping in the L-band (960-1215 MHz). HaveQuick is often considered the predecessor or a complementary system for voice. Both rely on precise TOD synchronization. See entries for **Link 16** and **TDMA**.
**Time-of-Day (TOD):** The absolute time reference (e.g., UTC) used to seed the synchronization and hopping algorithm. The accuracy of TOD dissemination is critical.
**GPS-Denied Synchronization:** A major challenge where HaveQuick networks must rely on holdover from precision oscillators like **Chip Scale Atomic Clocks (CSAC)** or **Rubidium Standards** after initial GPS lock.
**Anti-Jam (AJ) / Low Probability of Intercept (LPI):** The core operational capabilities provided by HaveQuick's frequency-hopping spread spectrum (FHSS) technique.
**Frequency-Hopping Spread Spectrum (FHSS):** The fundamental radio technique used by HaveQuick. See **FHSS** entry.
**IRIG-B:** A common time-code standard used to distribute precise time (often derived from GPS) to HaveQuick ground stations or aircraft for synchronization.
**1 PPS (Pulse Per Second):** A standard timing signal from GPS receivers used to discipline oscillators and align the start of each second, a fundamental element for TOD generation in HaveQuick systems.
**KGV / COMMSEC Module:** The cryptographic hardware that encrypts the TOD and message traffic, central to the system's security.
**TDMA (Time-Division Multiple Access):** The channel access method that divides the radio spectrum into repeating time slots for different users. See **TDMA** entry.