Understanding Link 16

Understanding
Link-16
A Guidebook for New Users
September 2001
Limited Rights
Contract No.: N00244-02-C-0008
Contractor Name: Commanding Officer Navy Center for Tactical Systems Interoperability (NCTSI)
Contractor Address : 53690 Tomahawk Drive, Suite A125, San Diego, CA 92147-5082
The Government’s rights to use, modify, reproduce, release, perform, display, or disclose these technical
data are restricted by paragraph (b)(3) of the Rights in Technical Data—Noncommercial Items clause
contained in the above identified contract. Any reproduction of technical data or portions thereof marked
with this legend must also reproduce the markings. Any person, other than the Government, who has been
provided access to such data must promptly notify the above named Contractor.
Distributed by: NCTSI

Understanding
Link-16
A Guidebook for New Users
Prepared: April 1994
Contract No. N00024-87-C-5195
AEGIS Program Manager
Washington, D.C. 20362-510
First Revision: September 1996

Second Revision: December 1998
Third Revision: September 2001
Prepared by:
Northrop Grumman Corporation

Information Technology
Communication & Information Systems Division
4010 Sorrento Valley Boulevard
San Diego, CA 92121-1498, USA
Limited Rights
Contract No.: N00244-02-C-0008
Contractor Name: Commanding Officer Navy Center for Tactical Systems Interoperability (NCTSI)
Contractor Address : 53690 Tomahawk Drive, Suite A125, San Diego, CA 92147-5082
The Government’s rights to use, modify, reproduce, release, perform, display, or disclose these technical
data are restricted by paragraph (b)(3) of the Rights in Technical Data—Noncommercial Items clause
contained in the above identified contract. Any reproduction of technical data or portions thereof marked
with this legend must also reproduce the markings. Any person, other than the Government, who has been
provided access to such data must promptly notify the above named Contractor.
1_LK16_title-NCTSI 1 8/8/2, 2:06 PM

Introduction
The guidebooks in the Understanding Tactical Data Links Series are designed
to be used both for reference and for review. Detailed information is presented
in the text, with important points summarized in the margins and in the figure
captions. The format of this guidebook incorporates the following features:
■ Bold Type Important terms are printed in bold typeface the first time
they appear, and a definition is given.
■ Margin Notes Key points are summarized in the margin notes, which
are printed in blue. Wide margins are provided, and you are encouraged
to add your own notes as well.
■ Illustrations Figures and diagrams are intended to complement the

text. Their captions, also printed in blue, summarize important points.
■ Tables Facts are collected and summarized in tables to allow for quick
lookups and comparisons.
Recommended procedures are highlighted

throughout the text as "rules of thumb."
In this guidebook, we present extensive information on the Navy

implementation of Link-16, including the equipment, signal structure,
communication protocol, and operational considerations. Note that the Class
1 terminal and the IJMS message standard are not supported by the Navy
implementation and have, therefore, not been included in this guidebook.
You can use this guidebook in either of two ways: for review or for reference.
You can review the most important concepts simply by reading the blue margin
notes and figure captions. To enhance its use as a reference, a list of acronyms,
a glossary, and an index may be found at the back of the guidebook.
2_INTRO_TOC 1 9/19/1, 12:23 PM

Chapter 1
Section A
Introduction to Link-16
Background
Table of 1
Section B
Section C
Comparison to Link-11 and Link-4A
Features of the JTIDS Architecture
Contents
Section D Summary of New Capabilities
Section E Planned Implementation
Chapter 2 The Shipboard Link-16 Equipment

Section A Overview 2
Section B The Tactical Data System
Section C The Command and Control Processor
Section D The JTIDS Class-2 Terminal
Section E Link-16 Antennas
Section F The Link-16 Data Flow
Chapter 3 The Airborne Link-16 Equipment

Section A Overview of Navy Link-16 Airborne Platforms 3
Section B The E-2C Hawkeye
Section C The F-14D Tomcat
Chapter 4 Messages and Interfaces

Section A Overview
Section B The N-Series Messages
Section C The J-Series Messages
Section D Terminal Input Messages
4
Section E Terminal Output Messages
Section F The Multiplex Cycle
Section G Data Transfer Blocks
Section H Housekeeping Words
Section I Voice Transmission / Reception
Section J The TACAN Port Interface
Chapter 5 Building the JTIDS RF Signal

5
Section A TDMA and the JTIDS Network
Section B Link-16 Messages
Section C Inside the Time Slot
2_INTRO_TOC 2 9/19/1, 12:23 PM

Chapter 6 Structuring the Link-16 Network
Section A Participation Groups Table of 6
Section B
Section C
Time Slot Assignments
Network Roles Contents
Section D Net Entry
Section E Location and Identification: PPLIs
Section F Receipt/Compliance
Section G Relays
Section H Communications Security
Section I
Section J
Multinetting
Range Extension
7
Chapter 7 Link-16 Operations

Section A Design Goals
Section B Platform Identification, Position, and Status
Section C Surveillance
Section D Force Training
Section E Air Control
Section F Special Functions
Section G Network Management
Appendixes
Appendix A Multilink Operations
Appendix B Link-16 Platforms
Appendix C Acronyms and Abbreviations
Appendix D Glossary
Appendix E Index
2_INTRO_TOC 3 9/19/1, 12:23 PM

1
C
H
A
P
T
E
R
Introduction to
Link-16
Introduction
Link-16 is the designation of a new tactical data link which is being introduced into
operations of the United States Navy, the Joint Services, and forces of the North Atlantic
Treaty Organization (NATO). It became operational in U.S. Navy ships and aircraft
during 1994. Link-16 does not significantly change the basic concepts of tactical data
link information exchange supported for many years by Link-11 and Link-4A. Rather,
Link-16 provides certain technical and operational improvements to existing tactical
data link capabilities.
This chapter summarizes the improvements to data link capabilities resulting from the
introduction of this new link to the Battle Group. You will learn what is provided by the
expanded message structure and what is provided by the improved waveform. And,
you will see how Link-16 compares with the existing links. A working knowledge of
current Link-11 and Link-4A operations is assumed.
1-1
LK16 CH1 1 9/20/1, 5:55 PM

LGN 135-02-002
Section A
Background
The general purpose of Link-16 is the same as that of
Link-11 and Link-4A: the exchange of real-time tactical
data among units of the force. While Link-16 is identical in
purpose to these links, it also provides some data exchange
elements which they lack, and it provides significant
improvements as well, such as nodelessness, jam resistance,
flexibility of communication operations, separate transmission
and data security, increased numbers of participants,
increased data capacity, network navigation features, and
secure voice.
All Those Names: Link-16, TADIL J,

JTIDS, IJMS, MIDS ■
The U.S Navy uses the NATO designation Link-16 when
referring to Tactical Digital Information Link (TADIL) J.
“Link-16” is thus synonymous with TADIL J. The latter
term is employed only by U. S. Joint Services other than the
U. S. Navy. Similarly, Link-11 is synonymous with TADIL
A, Link-11B with TADIL B, and Link-4A with TADIL C.
1-2 Section A Background
LK16 CH1 2 9/20/1, 5:55 PM

Chapter 1 Introduction to Link-16
Link-16 uses the Joint Tactical Information Distribution

System (JTIDS). The acronym JTIDS refers to the JTIDS refers
communications component of Link-16. It encompasses the to the
Class 2 terminal software, hardware, RF equipments, and the communications
high-capacity, secure, antijam waveform that they generate. component of
Among NATO subscribers, the equivalent term for JTIDS is Link-16.
the Multifunctional Information Distribution System
(MIDS). All information about Link-16 in this guidebook
applies equally to USN, Joint Service, and NATO operations.
It is planned for all USN platforms to be fully interoperable
with the Joint and Allied platforms that implement Link-16.
Net 3
Net 2
Net 1
Net 0
Host Class 2 Class 2 Host

Computers Terminal Terminal Computers
JTIDS
Link-16
LK16/1-08M-004
(TADIL J)
Figure 1-1. Tactical data is shared among friendly units equipped with
Tactical Data Systems over Link-16 using the Class 2 JTIDS data terminal.
Section A Background 1-3
LK16 CH1 3 9/20/1, 5:55 PM

LGN 135-02-002
IJMS refers to The acronym IJMS refers to the Interim JTIDS Message
an interim Specification. Messages formatted according to this early, interim
specification specification were implemented in early TADIL J terminals
implemented in designated as the Class 1 terminals. These Class 1 terminals are
the early terminals. used primarily by U.S. Air Force and NATO E-3 aircraft. They
It is not fully support a limited JTIDS capability that is not fully compatible with
compatible Link-16.
with Link-16.
The U.S. Air Force Class 2 terminal implements the Class 1 IJMS
protocol as well as JTIDS. Because it can translate between
IJMS messages and J-series messages, it is said to be bilingual.
The U.S. Navy Class 2 terminal is not bilingual and cannot process
IJMS messages.
Throughout this guidebook, the term “Link-16” refers to the tactical

data link that is specified in MIL-STD-6016, formerly known as
the JTIDS Technical Interface Design Plan (Test Edition),
the JTIDS TIDP-TE, as interpreted and amplified for the USN by
the Link-16 Operational Specification (OS-516.2). All information
about Link-16 contained herein applies equally to USN, Joint
Service, and NATO operations.
Link-16, using the JTIDS data terminal, represents major

improvements in data link communications over the current Link-11
and current Link-4A. Link-16 will not replace these links entirely,
but it will become the preferable alternative when feasible. Because
JTIDS uses only the UHF spectrum, Link-16 communications are
limited to line of sight unless suitable relay platforms are available.
Furthermore, many current Link-11 platforms will not be equipped
with JTIDS. It is therefore anticipated that Battle Group operations
will employ both Link-11 and Link-16 simultaneously for at least
20 years after Link-16 has been introduced. Appendix A explains
how interoperability is maintained among all units in a force
employing multiple links.
1-4 Section A Background
LK16 CH1 4 9/20/1, 5:55 PM

Features of Link-16 ■
Link-16 includes many features which improve on Link-11.
These include:
■ Jam resistance
■ Improved security
■ Increased data rate (throughput)
■ Increased amounts/granularity of information
exchange
■ Reduced data terminal size, allowing installation in
fighter and attack aircraft
■ Digitized, jam-resistant, secure voice capability
■ Relative navigation
■ Precise participant location and identification.
Link-11 + Link-4A
+ Secure Voice
+ Jam Resistance + Security equals Link-16
+ Throughput + Granularity + Capacity
LK16/1-08M-001
Figure 1-2. While Link-16 is functionally similar to the combined capabilities

of Link-11 and Link-4A, it provides technology and capabilities not available
in these links.
Section A Background 1-5
LK16 CH1 5 9/20/1, 5:55 PM

LGN 135-02-002
Section B
Comparison to Link-11
and Link-4A
Because Link-16 is functionally equivalent to an improved Link-11
with voice and Link-4A’s air control, comparing the architecture,
capacity, and data rates of these three links is worthwhile.
Architecture ■
■ Link-11
Link-11 uses a polling protocol and a netted architecture. A net is an
ordered conference whose participants have common information
needs or similar functions to perform. A net operates under the
supervision of a controller, who permits access and maintains circuit
discipline.
64
• •• 56 64 64 04 •• •
LK16/1-08M-080
NCS 04
27
56 10
Figure 1-3. Link-11 uses a netted architecture and a polling protocol in

which one unit designated the NCS calls each PU in turn to report its data.
1-6 Section B Comparison to Link-11 and Link-4A
LK16 CH1 6 9/20/1, 5:55 PM

The Link-11 net is normally operated according to a protocol called

Roll Call. Participating Units (PUs) transmit all data eligible for
reporting when they are polled by the Net Control Station (NCS).
After transmission, they revert to the receive mode while, one by
one, the other PUs transmit their data. This cycle continues until all
PUs have transmitted at least once, and then it is repeated. The time
required to poll all PUs and to transmit all their eligible data at least
once is known as net cycle time. At any given time, a PU is either
transmitting or receiving data on a single Link-11 net.
■ Link-4A
Link-4A uses a command-and-response protocol and the principle of

Time Division Multiplexing (TDM) to derive apparently simulta-
neous channels from a given frequency spectrum. It connects two
points by assigning a sequence of discrete time intervals to each of
the individual channels. Thus, one controller can control multiple
aircraft independently on the same frequency. At any given time,
a TADIL C unit is either transmitting, receiving, or idle on a single
point-to-point circuit.
CTL A/C CTL A/C CTL A/C CTL

LK16/1-08M-081
Figure 1-4. Link-4A uses time division multiplexing and a command-and-

response protocol to connect a controller with multiple controlled aircraft.
Section B Comparison to Link-11 and Link-4A 1-7
LK16 CH1 7 9/20/1, 5:55 PM

LGN 135-02-002
■ Link-16
Link-16 uses the principle of Time Division Multiple Access

(TDMA), an automatic function of the JTIDS terminal. The
TDMA architecture uses time interlacing to provide multiple
and apparently simultaneous communications nets. All JTIDS
Units, or JUs, are preassigned sets of time slots in which to
transmit their data and in which to receive data from other
units. Each time slot is 1/128 second, or 7.8125 milliseconds
(msec), in duration.
Multiple nets can be “stacked” by allowing time slots to be

used redundantly, with the data transmitted in each net on
different frequencies. There are 51 frequencies available for
JTIDS transmissions. The frequency is not held constant
during the time slot but is changed rapidly (every 13 micro-
seconds) according to a predetermined pseudo-random
pattern. This technique is called frequency hopping. Each
net is assigned a number which designates a particular
hopping pattern. There are 128 possible numbers, with the
number 127 reserved to indicate a stacked net configuration.
During any given time slot, a unit is either transmitting or
receiving on one of a possible 127 nets.
LK16 CH1 8 9/20/1, 5:55 PM

Net 3
Net 2
Net 1
Net 0
Figure 1-5. JTIDS units automatically transmit and receive data at preassigned times on
preassigned nets based on instructions given to their terminals when they are initialized. These
preassignments are determined in advance of operations to support the expected information
exchange requirements of the force.
Data Exchange ■
The Link-11 data is divided into 24-bit frames, with two frames constituting
a Link-11 message. The messages used to exchange information over Link-11 are
known as the M-series messages. At the fast data rate, 24 bits of data are transmitted
every 13.33 milliseconds (msec). This is 75 frames, or 1800 bits, per second.
The more commonly quoted rate of 2250 bits per second includes 6 bits with each
frame for error detection and correction (EDAC).
LK16 CH1 9 9/20/1, 5:55 PM

LGN 135-02-002
The Link-4A message exchange is divided between control

messages and aircraft replies. The control messages are
known as the V-series messages. The aircraft reply messages
are known as the R-series messages. A 56-bit control message
is transmitted every 32 msec, for an effective one-way tactical
data rate of 1750 bits per second. The effective two-way
tactical data rate is slightly better than 3000 bits per second.
In Link-16, either 3, 6, or 12 Link-16 words can be transmitted

in a 7.8125-msec time slot, depending on whether the Standard,
Packed-2, or Packed-4 data packing structure is used. A
Link-16 word is analogous to a Link-11 frame. Each Link-16
word comprises 70 bits of data. A Link-16 message is
composed of a variable number of words — normally 1, 2, or 3
— although messages longer than 40 words are possible.
Three types of messages are possible: fixed format, free text,
and variable format. The fixed-format messages exchanged
over Link-16 are known as the J-series messages.
The effective tactical data rates of Link-16 are 26,880, or

The Link-16 data 53,760, or 107,520 bits per second, depending on the data
rate is much packing structure used. The Packed-4 data structure is not
higher than the normally used by the U.S. Navy. The more commonly quoted
Link-4A or data rates are 28,800, or 57,600, or 115,200 bits per second and
Link-11 data include 5 bits of parity with each word. If the additional bits
rates. for Reed-Solomon EDAC encoding are considered, the
calculated rate increases to 59,520, to 119,040, or to 238,080
bits per second.
All of these rates are technically correct. The appropriate rate

to use in comparing data throughput on the different links is the
rate at which tactical information is exchanged. For Link-16,
this depends on whether or not the data is encoded and which
packing structure is employed. Each time slot of unencoded
information holds 450 bits at Standard packing, 900 bits at
LK16 CH1 10 9/20/1, 5:55 PM

Message Data Rates (kbps)

Link Architecture Protocol
Standard Tactical with Parity with EDAC
Link-4A TDM Command/Response V-Series 3.06 – –

R-Series
Link-11 Netted Polling by Net Control M-Series Fast 1.80 – 2.250

Slow 1.09 – 1.364
Link-16 TDMA Assigned Time Slots J-Series Standard 26.88 28.8 59.520
Packed-2 53.76 57.6 119.040
Packed-4 107.52 115.2 238.080
LK16/1-08M-002
Figure 1-6. Link-16 supports the functions of both Link-11 and Link-4A, as well as additional
functions such as voice, relative navigation, and an expanded electronic warfare capability.
Packed-2, and 1800 bits at Packed-4. The same time slot with Reed-Solomon
encoding holds 210 bits of tactical information at Standard packing, 420 bits of
tactical information at Packed-2, and 840 bits of tactical information at Packed-4.
To calculate the average data rate, multiply the number of tactical information bits
per slot by the number of slots per second.
Because of the increased data rate of JTIDS, far more data can be transmitted on
Link-16 than on Link-11 during the same period of time. Recognizing this,
the developers of the Link-16 J-series message standard have added J-series data
elements that cannot currently be exchanged over Link-11. The Link-16 J-series
messages allow the reporting of two to three times as much tactical information as
Link-11. However, the amount of Link-16 data operationally required and
implemented by USN platforms is estimated to be only about 50 percent more than
currently implemented Link-11 data.
The nearly 54 kilobits per second (kbps) tactical data rate for the Packed-2 structure
is actually the instantaneous rate, determined by assuming 420 data bits (6 70-bit
words) are transmitted in 1/128 second. The capacity of the JTIDS network can be
increased further by using multinetting techniques. Statistical analysis has shown
LK16 CH1 11 9/20/1, 5:56 PM

LGN 135-02-002
that approximately 20 different nets can be collocated without

mutual interference. Another option is to allow simultqneous
transmissions. The first transmission received, that of the
nearest unit, will be the only one processed.
The actual increase in the rate at which tactical data is

exchanged is not as great as a straight comparison of the
effective data rates of Link-11 and Link-16 might indicate.
There are several reasons for this. A portion of the time slots
in every network is allocated to functions that are not included
in Link-11, such as Air Control and Voice. The number of
time slots allocated to tactical data must be doubled to satisfy
relay requirements. All time slots that are assigned are not
always used. Finally, the terminal automatically adjusts the
density of message packing to support the amount of data it
has to transmit. You will not be overwhelmed! The effective
tactical data rate, assuming a single-hop relay throughout a
Link-16 network and the packing structure normally used by
the USN (Packed-2), is approximately four times that of
Link-11.
It is sometimes useful to estimate the system capacity of

Link-16 in bits per second. For a rough estimate, multiply
the number of time slots actually in use each second
(maximum of 128) by the number of bits transmitted in each
time slot (225 or 450), and multiply the result by the number
of nets in operation. To be realistic, however, the values used
in this calculation should consider the reductions in capacity
that can occur because data is relayed, the packing structure
changes, time slots go unused, and some time slots belong
only to single nets.
Techniques for increasing capacity, such as data compression

and/or operating at Packed-4, are under investigation. But
regardless of how great the system capacity is estimated to be,
the throughput of any one terminal is limited to a single set of
128 time slots every second.
LK16 CH1 12 9/20/1, 5:56 PM

Architecture
■ TDMA
■ Nodeless
■ Message and Transmission Encryption
■ Frequency Hopping
■ UHF, L x Band
■ Line of Sight
Message Types
■ Fixed Format (J-Series)
■ Free Text (voice)
■ Variable Format
Operational Use
■ Surveillance
■ Electronic Warfare
■ Mission Management
■ Weapons Coordination
■ Air Control
■ Fighter-to-Fighter
■ Secure Voice
■ Navigation
■ Positive Identification
Figure 1-7. Link-16 is a high-capacity, multifunctional, secure,

jam-resistant tactical data link.
LK16 CH1 13 9/20/1, 5:56 PM

LGN 135-02-002
Section C
Features of the JTIDS
Architecture
Several features of Link-16 resulting in improved communi-
cation are derived from the unique JTIDS architecture.
Nodelessness ■
An established
JTIDS network A node is a unit required to maintain communications. In
operates Link-11, for example, the NCS is a node. If the NCS goes
independently down, the link goes down. In Link-16 there are no nodes.
of any particular Time slots are preassigned to each participant, and the link
unit. will function regardless of the participation of any particular
unit. The closest thing in Link-16 to a node is the Net Time
Reference (NTR). An NTR is needed to start up a network
and for a new unit to synchronize with and enter a network.
After a network has been established, however, it will
continue to operate for hours without an NTR.
1-14 Section C Features of the JTIDS Architecture
LK16 CH1 14 9/20/1, 5:56 PM

Security ■
Both the message and the transmission are encrypted. The
message is encrypted by the KGV-8 encryption device in
accordance with a cryptovariable specified for message
security, or MSEC. Transmission security, or TSEC, is
provided by another cryptovariable that controls the specifics
of the JTIDS waveform. One important feature of this
waveform is its use of frequency hopping. The hopping
pattern is determined by both the net number and the TSEC
cryptovariable. This instantaneous relocation of the carrier
frequency spreads the signal across the spectrum, making it
both difficult to detect and difficult to jam. The TSEC
cryptovariable also determines the amount of jitter in the
signal, and a predetermined, pseudorandom pattern of noise
that is mixed with the signal prior to transmission.
Cryptovariable Type of Security
MSEC Encryption of message data
TSEC Encryption of JTIDS waveform

– Jitter
– Pseudorandom Noise
– Frequency-Hopping Pattern
Figure 1-8. In Link-16, the message and the transmission are

encrypted.
Section C Features of the JTIDS Architecture 1-15
LK16 CH1 15 9/20/1, 5:56 PM

LGN 135-02-002
Network Participation Groups ■

The JTIDS time slots of a net can be parceled out to one or
more Network Participation Groups (NPGs). An NPG is
defined by its function, and thus also by the types of
messages which will be transmitted on it. Among the NPGs
that will be used by the Navy are:
Network capacity ■ Surveillance

is allocated into
segments, or groups,
dedicated to specific ■ Network Management
functional purposes.
■ Weapons Coordination
■ Air Control
■ Fighter-to-Fighter
■ Secure Voice
■ Precise Participant Location and Identification

(PPLI) and Status.
This division of the net into functional groups allows JUs to

participate on only the NPGs used for functions which they
perform. It is anticipated, however, that in the great majority
of operations, all USN Command and Control (C2) JUs —
that is, ships and E-2Cs — will operate on all defined NPGs
except the Fighter-to-Fighter NPG.
1-16 Section C Features of the JTIDS Architecture
LK16 CH1 16 9/20/1, 5:56 PM

Stacked Nets ■
The same set of time slots may be used for more than one net Time slots may be
simply by assigning a different frequency-hopping pattern to "stacked" into
each. The hopping pattern is determined by the TSEC multiple nets by
cryptovariable and the net number. Nets which have the same assigning a
TSEC and same MSEC cryptovariables, but different net different
numbers, are referred to as stacked nets. frequency-hopping
pattern to each.
For each time slot, a JU is either transmitting or receiving on
one net. In order to use the stacked net structure, the partici-
pants on each net must be mutually exclusive. Stacked nets
are particularly useful for air control purposes with mutually
exclusive sets of controlling units and controlled aircraft.
They are also used for voice communications, providing a
potential for 127 different voice circuits for each of the two
voice NPGs.
AA
AA
AAAA
AA
AA
AAAA
AA
AAAA AA
A
AAAA
NET 3
AA
AAAA
AAAA
Stacked Net
Air Control
AAAA
AAA
NET 3
NET 2
AAA
AAAA
AAA
A
NET 1
NET 0
A AA
AAA
AA AA
AAAAA
AA
NET 1
LK16/1-08M-082
AA
AAAA
Figure 1-9. Stacked nets are useful for air control purposes, with
mutually exclusive sets of controlling units and controlled aircraft.
Section C Features of the JTIDS Architecture 1-17
LK16 CH1 17 9/20/1, 5:56 PM

LGN 135-02-002
Section D
Summary of New
Capabilities
The Link-16 J-series messages allow the reporting of two to
three times as much exchangeable tactical information as
the Link-11 M-series messages. Some of the field sizes have
been increased to allow an improved degree of precision in
the reporting of data. Some new functions are defined.
Areas in which major improvements or changes have been
made include:
■ Addresses
■ Track Numbers
■ Track Quality
■ Track Identification
■ Friendly Status
■ Increased Granularity of Measurement
■ Lines and Areas
■ Geodetic Positioning
■ Relative Navigation
■ Land Points and Tracks.
1-18 Section D Summary of New Capabilities
LK16 CH1 18 9/20/1, 5:56 PM

Addresses ■
Each participant, or JTIDS Unit, is assigned a unique
address. In Link-16, the JU addresses are five-digit octal
numbers in the range 00001 to 77777, whereas the Link-11
PU Address field accommodates only the three-digit octal
addresses up to 177. However, to accommodate multilink
communication, C2 JUs must always be assigned addresses
below 00177. The Link-16 addresses 00001 to 00177 are
equivalent to the Link-11 addresses 001 to 177. An address
in this range can be assigned only to one unit, whether it is
a PU or a C2 JU. NonC2 JUs — for example, fighters — use
only the addresses 00200 through 77776. The address 77777
uniquely identifies the TADIL J Manager.
The address 00034 used on Link-16 is the same

as address 034 used on Link-11. When a unit
operates on both links at the same time, it
uses the same address on both links.
Section D Summary of New Capabilities 1-19
LK16 CH1 19 9/20/1, 5:56 PM

LGN 135-02-002
Track Numbers ■
Link-16 employs a five-character alphanumeric Track
Number (TN) within the range 00001-77777 or within the
range 0A000-ZZ777, allowing up to 524,284 TNs. Link-11
uses a four-digit TN in the range 0001 to 7777, allowing
only 4,092 TNs on Link-11. Link-16 cannot be operated in a
TN pool mode, as can Link-11, in which a common pool of
track numbers can be shared by several PUs. The TDMA
architecture does not permit proper TN accountability in a
pool. Therefore a much larger number of Link-16 TNs is
necessary in order to permanently or semi-permanently
allocate adequate blocks of TNs to each of the many units
which will eventually be equipped for Link-16.
It is important to understand that, for TN allocation and

assignment purposes, the Link-11 TNs 0200-7777 are
considered to be the same TNs as the Link-16 TN/Addresses
00200-07777. For example, TNs 0200 and 00200 are the
same TN and cannot both be assigned to two different tracks,
nor can they be assigned both to a Link-11 track and a
Link-16 JU.
The track or JU reported as TN 00200 on

Link-16 is the same track as that reported
as TN 0200 on Link-11.
LK16 CH1 20 9/20/1, 5:56 PM

Track Quality ■
Link-16 uses Track Quality (TQ) values that range from 0
through 15. Each TQ value is defined by a specific positional
accuracy range. The highest Link-16 TQ value requires better
than 50-foot accuracy. By comparison, the highest Link-11
TQ value is 7. A Link-11 air track can have a TQ of 7 with
a positional accuracy worse than 3 nautical miles (nm).
Track Identification ■
The Track Identification (ID) reporting capabilities of
Link-16 have been greatly expanded. Tracks are reported on
Link-16 with a detailed ID that includes Platform, Activity,
Specific Type, and Nationality. In addition, a provision has
been made for an identity of “Neutral,” and Unknown
Assumed Enemy has been changed to “Suspect.” In Link-11,
track identification is limited to three fields: Identification,
Primary Amplification, and ID Amplification.
Friendly Status ■
The Link-16 messages allow much more detailed reporting
of the status of friendly aircraft, including the following
which are not reported on Link-11: equipment status, exact
ordnance inventory, radar and missile channels, fuel available
for transfer, gun capability, and ETA and ETD to/from
station. On Link-16 a unit can also report its inventory of
specific surface missiles such as SM-2(ER), Tomahawk
TLAM C, and others.
LK16 CH1 21 9/20/1, 5:56 PM

LGN 135-02-002
Increased Granularity of
Measurement ■
Granularity is a measure of how precisely a data item can
be reported in the data link messages. The major Link-16
granularity improvements are in track positions, air track
speeds, altitudes, and lines of bearing.
Lines and Areas ■

Link-16 messages allow the reporting of multisegmented
lines, as well as areas of all sizes and descriptions. Link-11,
by contrast, does not allow lines, and it allows only areas of
limited size that are circles, ellipses, squares, or rectangles.
AA
AA
AA
AA
AA A
AA
AA
AA A
AA A LK16/1-08M-083
Figure 1-10. Link-16 allows corridors and areas of all shapes and
sizes to be reported.
LK16 CH1 22 9/20/1, 5:56 PM

Geodetic Positioning ■
The Link-16 messages implement a three-dimensional
geodetic coordinate system using latitude, longitude, and
altitude. This allows positions to be reported anywhere in the
world, subject only to display and data base limitations. By
contrast, Link-11 uses the Cartesian coordinate system, and
allows track reporting only within a limited range of the
reporting unit.
Latitude: 20° N
Longitude: 7° E
Altitude: 10,000 feet
LK16/1-08M-084
Figure 1-11. With three-dimensional geodetic positioning, a location anywhere in the world
can be reported.
LK16 CH1 23 9/20/1, 5:56 PM

LGN 135-02-002
Relative Navigation ■
Relative Navigation (RELNAV), an automatic function of
the JTIDS terminal, is used to determine the distance
between platforms by measuring the arrival times of
transmissions and correlating them with reported positions.
This information is required for the terminals in a network to
remain synchronized. Automatic RELNAV is in constant
operation in all JTIDS terminals, providing information that
allows terminals in the network to remain synchronized. This
RELNAV data can be used to improve a unit’s positional
accuracy. And, if two or more units have accurate, indepen-
dent knowledge of their geodetic positions, RELNAV can
provide all units of the network with accurate geodetic
positions. As a result, the precise geodetic position of every
unit can be maintained constantly by every other unit.
Link-11 positions, on the other hand, are not geodetic. Each

unit reports its position relative to a prespecified origin, the
Data Link Reference Point (DLRP). Maintaining positions
on Link-11 is dependent upon the correct reception of the
reporting unit’s position relative to the DLRP.
Electronic Warfare ■
Link-16 allows greater exchange of Electronic Warfare
(EW) parametric information and a wider range of EW
control. EW units exchange parametric data and orders on
their own NPG and EW product information on the
Surveillance NPG.
LK16 CH1 24 9/20/1, 5:56 PM

Land Points and Tracks ■

The Link-16 messages add Land as a track category, a category not
currently available on Link-11. On Link-16, some of the Special
Points currently reported on Link-11 are reported as Land Points,
while others are reported as Reference Points. Land Points describe
physical objects, such as a tank or building, whereas Reference
Points are used for theoretical constructs, such as waypoints or
stations. A Land Track is simply a mobile Land Point. The U.S.
Navy’s implementation of Link-16 Land Points and Tracks will be
very limited.
70°
50°
Waypoint (50° N 27° E)
30°
Waypoint (30° N 24° 15' E)
LK16/1-08M-085
10°
22° 23° 24° 25° 26° 27° 28° 29° 30° 31°
Land Points Reference Points
Figure 1-12. The Link-16 messages add land as a track category. Land points describe
physical objects. Reference points describe theoretical constructs.
LK16 CH1 25 9/20/1, 5:56 PM

LGN 135-02-002
Comparison of Information Exchange

Link-11 Link-16
Addresses 001-176 00001-77777
Track Numbers 0200-7777 00200-ZZ777
Track Quality 0–7 0 – 15
Track Identification Identity Identity

Pri Amp Platform
ID Amp Specific Type
Activity
Nationality
Status Information Limited Detailed
Position Granularity 500 yds 32 feet
Air Speed Granularity 28 dmh 2 dmh
Lines and Areas No Yes
"Playing Field" 512 x 512 nm Worldwide
Relative Navigation Limited Detailed
EW Limited Detailed
LK16/1-08M-003
Figure 1-13. Link-16 adds to the capabilities of Link-11 by offering

improved identification, new functions, and increased granularity
of measurement.
LK16 CH1 26 9/20/1, 5:56 PM

Section E
Planned Implementation
Many more platforms will be equipped for Link-16 than were
equipped for Link-11 and Link-4A. It is anticipated that the
number of MIDS/JTIDS-equipped U.S. platforms will
approach 5000 by the year 2015.
Several classes of JTIDS terminals have been produced, with

different host interfaces and protocols. After 1999, new
installations of Link 16 will employ the MIDS terminal.
These terminals are reduced in size and cost from the original
Class 2 terminals, and are interoperable with the secure JTIDS
waveform.
As with JTIDS terminals, there are several versions or classes

of the MIDS terminal that differ in their host programming.
The MIDS/Low Volume Terminal (LVT) for NATO platforms,
most notably the EF-2000 (Eurofighter 2000) and the F/A-18
is programmed according to a new Interface Control
Document. The MIDS/Fighter Data Link (FDL) is a version
that has no TACAN or voice capability and has been
programmed to be host software compatible with the F-15
Class 2 terminal. The US Navy shipboard MIDS terminal has
a special I/O front end that will be host compatible with the
Class 2 U.S. Navy shipboard terminal.
Section E Planned Implementation 1-27
LK16 CH1 27 9/20/1, 5:56 PM

LGN 135-02-002
U.S. Navy ■
U.S. Navy ships which will have JTIDS and Link-16 include
aircraft carriers (CVs and CVNs), cruisers (CGs and CGNs),
destroyers (DDGs), amphibious assault ships (LHDs and
LHAs), and submarines (SSNs). Implementation of Link-16
aboard U.S. Navy ships is planned in two phases, which are
designated Model 4 and Model 5. These differ greatly in the
capabilities they provide. Current configuration information,
and much more, is available at the Navy website —
http://link16.spawar.navy.mil.
U.S. Navy aircraft to be equipped with Link-16 include the

E-2C Hawkeye and the F-14D Tomcat. The implementation
of Link-16 in airborne platforms requires a software upgrade
to the mission computers, as well as the addition of the JTIDS
Class-2 terminal. Because this software upgrade fully
supports the capabilities provided by the J-series message
standard, it is referred to as Model 5 for all aircraft.
A Link-16 capability in the F/A-18 Hornet will be provided by

the MIDS terminal. Other platforms, such as the EA-6B and
EP-3B aircraft, are also under consideration for Link-16, but
without definite plans. This guidebook is confined to those
listed above, which use the JTIDS Class-2 terminal and for
which implementation plans are definite.
1-28 Section E Planned Implementation
LK16 CH1 28 9/20/1, 5:56 PM

U.S. Marine Corps ■

The U.S. Marine Corps employs the AN/URC-107(V)9
Class 2 terminal with the High Power Amplifier Group
(HPAG) in support of the Tactical Air Command Center
(TACC), Tactical Air Operations Center (TAOC), and Air
Defense Communications Platform (ADCP). The interface
between the host systems and the terminal is a MIL-STD-1553
interface. The JTIDS interface for the TACC and TAOC is
through the AN/TYQ-82 shelter which contains the Class 2
terminal.
The U.S. Marine Corps aircraft to be equipped with TADIL J

is the F/A-18 C/D. Aircraft will employ the MIDS terminal.
U.S. Army ■
The U.S. Army employs the JTIDS Class-2M (modified)
terminal. This terminal, weighing less than 88 lbs, is
manufactured by GEC-Marconi. It is designed specifically for
Army ground-based operations, with a user rate below 8 Kbps
and a connectivity requirement of 85 percent in a non-
jamming environment and 70 percent in a jamming
environment.
The operational program executes on a single, Motorola

29-MHz 68030 CPU with a single Common Signal Processor
and a Receiver/Synthesizer module for the Receiver/
Transmitter Subassembly, which is manufactured by
Rockwell-Collins. The U.S. Army JTIDS Class-2M terminal’s
interface to the host system is not the MIL-STD-1553 bus.
Instead, a variant of the CCITT X.25 interface, called
the PLRS JTIDS Hybrid Interface, is employed.
Section E Planned Implementation 1-29
LK16 CH1 29 9/20/1, 5:56 PM

LGN 135-02-002
U.S. Air Force ■

The U.S. Air Force employs the Class-2 terminal with the
High Power Amplifier Group (HPAG) in both the MCE and
the E-3A. The terminal installed in the F-15 does not use the
HPAG. The interface between the host system and the
terminal in the E-3A aircraft is a proprietary Boeing serial data
bus rather than the MIL-STD-1553 interface.
1-30 Section E Planned Implementation
LK16 CH1 30 9/20/1, 5:56 PM

2
C
H
A
P
T
E
R
The Shipboard
Link-16 Equipment
Introduction
To understand the operation of the shipboard Link-16 system, it is important to be able

to identify the hardware components which comprise it and the functions they perform.
In this chapter, you will learn about the components of the U.S. Navy’s shipboard
Link-16 system, including the Tactical Data System (TDS), the Command and Control
Processor (C2P), the Joint Tactical Information Distribution System (JTIDS) Terminal,
the JTIDS Antennas, and the interfaces between them. Navy airborne Link-16 systems
are described in Chapter 3.
2-1
lk16_ch2 1 9/24/1, 11:19 AM

LGN 135-02-002
Section A
Overview
Link-16 improves on existing tactical data link communications in
two ways—through more complete and more accurate tactical
information and through superior communications technology. The
major components of the Navy shipboard Link-16 system include:
■ Tactical Data System (TDS)

■ Command and Control Processor (C2P)
■ JTIDS Terminal
■ JTIDS Antennas
The TDS and C2P provide the tactical data to be exchanged. The
JTIDS terminal and antennas provide the secure, antijam,
increased-capacity waveform. There are two configurations of
Link-16, known as Model 4 and Model 5.
Receive Transmit /
Antenna Receive
Antenna
Tactical Command Joint Tactical Information

Data and Distribution System
System Control (JTIDS)
(TDS) Processor Terminal
(C2P)
LK16/2/08M-016
Figure 2-1. A typical shipboard Link-16 system consists of a Tactical

Data System (TDS), a Command and Control Processor (C2P), the Joint
Tactical Information Distribution System (JTIDS) Terminal, and the
Link-16 Antennas.
2-2 Section A Overview
lk16_ch2 2 9/24/1, 11:19 AM

Model-4 Link-16 ■
The Model-4 implementation of Link-16, also referred to as
Block 0 on ACDS platforms, was designed as a “transparent”
equipment upgrade to existing ships’ tactical systems.
Currently, both the AEGIS and the ACDS TDS software are
programmed to comply with operations specifications
OS-411 and OS-404. For both AEGIS and ACDS platforms,
the Model-4 Link-16 upgrade consists of the addition of new
hardware: the Command and Control Processor, and the
JTIDS terminal and antennas. The tactical systems, including
the Combat Direction Systems (CDS), Shipboard Gridlock
System (SGS), Command and Decision (C&D), and Weapons
Control Systems (WCS), are virtually unchanged.
The interface between C&D and the Model-4 C2P is the

parallel interface described by MIL-STD-1397 Type A. The
interface between WCS and the Model-4 C2P is the low-level
serial interface described by MIL-STD-1397 Type E. The
Model-4 C2P, also referred to as Version 0, is located
between these systems and the Link-11, Link-4, and JTIDS
data terminals.
Section A Overview 2-3
lk16_ch2 3 9/24/1, 11:19 AM

LGN 135-02-002
Model 4 provides For the transmit function, the Model-4 C2P receives the
the JTIDS M-series messages normally output for Link-11 from the
waveform for the CDS and the V-series messages normally output for Link-4A
existing Link-11 from the WCS. It reformats the data contained in these
and Link-4A messages in accordance with Link-16’s J-series message
data-exchange standard and passes them to the JTIDS terminal for
capabilities. transmission over the link.
For the receive function, the Model-4 C2P receives the

J-series messages from the Link-16 network via the JTIDS
terminal. These are reformatted as M-series or R-series
messages and passed to the CDS or WCS.
Link-4A
Link-4A Messages Link-4 UHF

DTS Radio
Model 4 Link-4A Messages Link-11

WCS
Link-11 Messages Link-11 HF/UHF
Crypto Radio
Model 4 DTS
C2P
(Version 0)
Link-11 Messages Link-16
Model 4 SGS
C&D
Joint Tactical Information
Link-16 Messages
Distribution System
MIL-STD-1553B Bus (JTIDS) Terminal
LK16/2-08M-017b
Navigation
Figure 2-2. Modification of the AEGIS Model-4 equipment configuration

to add a Link-16 capability requires the addition of a C2P, JTIDS
terminal, and antennas. The C2P interfaces between the Model-4 TDS
computers and the link data terminals.
lk16_ch2 4 9/24/1, 11:19 AM

Because Model-4 C2P directly translates the existing Link-11

and Link-4A messages, Model-4 Link-16 does not implement
any of the expanded data-exchange capabilities provided by
the J-series messages. Instead, it supports the existing
capabilities with its jam-resistant, increased-capacity JTIDS
waveform. Note that the C2P can be placed in bypass mode
to run Link-11 and Link-4A directly.
Model 4 is currently undergoing both developmental and

operational testing with the Initial Operational Capability
(IOC) scheduled to occur during 1994. Only a few ships
are planned to have the Model-4 implementation, and most
of these will be upgraded after 1996 to Model 5.
Link-4A

DTS Radio
Link-11
Link-4A Messages Link-11 Messages Link-11 HF/UHF

Crypto
Model 4 DTS Radio
Model 4 C2P
CDS (Version 0)
Link-11 Messages Link-16
(BlockØ)
SGS
Link-16 Messages
Distribution System
LK16/2-08M-017d
Navigation
Figure 2-3. Modification of the CDS Model-4 equipment configuration to

add a Link-16 capability requires the addition of a C2P, JTIDS terminal
and antennas. All data for all links passes through the C2P.
lk16_ch2 5 9/25/1, 1:14 PM

LGN 135-02-002
Model-5 Link-16 ■
Model 5 is the full The Model 5 implementation of Link-16, also referred to as
implementation of Block 1 on ACDS platforms, is the full and complete
Link-16: JTIDS implementation of Link-16 in accordance with OS-516.1. It
waveform and provides many improvements in data link communications as
expanded described in Chapter 1. Its implementation requires major
data-exchange modifications to the TDS computer program and data base.
capabilities. The displays and the operator interface to support the new
Link-16 capabilities are implemented in a new console, the
OJ–663. The installation of the Model-5 system is both an
equipment upgrade and a computer program upgrade.
Link-4A
Model 5
WCS Link-4A Messages Link-4 UHF
DTS Radio
Link-11

Crypto
Model 5 DTS Radio
C2P
(Version 1)
Link-16
Model 5 Normalized Data
C&D N-Series Messages
Link-16 Messages Joint Tactical Information

Distribution System
MIL-STD-1553B Bus
LK16/2-08M-017a
(JTIDS) Terminal
SGS Navigation
Figure 2-4. The AEGIS Model-5 Link-16 equipment configuration consists

of a C2P, JTIDS terminal, antennas, and an updated TDS. The TDS
exchanges normalized data with the C2P. The C2P translates between this
normalized data and the appropriate message series required by each link.
lk16_ch2 6 9/24/1, 11:19 AM

The C2P for Model 5, also referred to as Version 1, receives

data from the updated tactical system over the low-level serial
interface described by MIL-STD-1397 Type E. This data has
been normalized to be independent of any particular link. The
messages exchanged between the TDS and the C2P, which
contain this normalized data, are referred to as the
N-series messages. The C2P reformats this normalized data
as J-series messages for transmission over Link-16, and/or as
M-series messages for transmission over Link-11, and/or as
V-series for transmission over Link-4A. The installation of
Model 5 is scheduled to begin during 1994 and continue
through the early 2000s. New AEGIS ship construction
beginning with DDG 68 will incorporate Model-5 Link-16.
Existing ships will be outfitted with Model-5 Link-16 as they
become available for the upgrade during their overhaul and
repair cycles.
Link-4A

DTS Radio
Link-11

Crypto
Model 5 DTS Radio
C2P
(Version 1)
Model 5 Link-16
ACDS Normalized Data
AA
(Block 1) N-Series Messages
SGS Link-16 Messages

Distribution System
LK16/2-08M-
Navigation
Figure 2-5. The ACDS Model-5 tactical system incorporates the SGS
function. Like the AEGIS Model 5, it exchanges normalized data with the
C2P. The C2P translates between this normalized data and the
appropriate message series required by each link.
lk16_ch2 7 9/24/1, 11:19 AM

LGN 135-02-002
Section B
The Tactical Data System
The shipboard Link-16 TDS consists of one or more AN/UYK-43
computers. The Model-5 operator interface is implemented on the
OJ-663 console, which supports color graphics and overlaid
windows-based displays.
8
01
M-
/08
16/2
LK
AN/USQ-69 (V) AN/UYK-43A (V) OJ-663

Terminal Set Computer Set Operator Console
Figure 2-6. The Link-16 capability is implemented in platforms equipped

with the AN/UYK-43-based tactical systems. In Model 5, the TDS also
includes OJ-663 color graphics consoles.
2-8 Section B The Tactical Data System
lk16_ch2 8 9/24/1, 11:19 AM

The major functions of the TDS are:

■ providing tactical digital information to data link
participants
■ receiving and processing incoming tactical digital
information from data link participants
■ maintaining the tactical data base.
The program residing in the TDS computer performs many other

functions in addition to these. It supports system management,
Link-11 and Link-16 management, identification, and weapons
selection. It permits operators to perform control and integration
functions for the combat system, and it also manages the data
displays.
Link-4A

DTS Radio
Link-11
Link-11 Messages
Tactical Normalized Data Crypto
Link-11 HF/UHF
A A
DTS Radio
Data N-Series Messages
C2P
System
Link-16

Link-16 Messages
Distribution System
■ Provide tactical data to

other units
■ Receive tactical data
from other units
■ Maintain the tactical
LK16/2-08M-067
data base
Figure 2-7. The exchange of data among TDS computers allows all
JTIDS units to share the same integrated tactical picture.
Section B The Tactical Data System 2-9
lk16_ch2 9 9/24/1, 11:19 AM

LGN 135-02-002
To ensure interoperability among Navy platforms, all TDS

programs are required to pass rigorous testing, called
certification testing, before operational deployment. Navy
certification testing is conducted by the Navy Center for
Tactical Systems Interoperability (NCTSI) headquartered in
San Diego, California. The TDS platforms currently
scheduled for Link-16 installations are those with tactical
systems based on the AN/UYK-43 computers.
2-10 Section B The Tactical Data System
lk16_ch2 10 9/24/1, 11:19 AM

Section C
The Command and Control
Processor
The AN/UYQ-62(V) Command and Control Processor
subsystem, or C2P, is a message distribution system that
provides the interfaces between the TDS computer and the
JTIDS terminal, the Link-11 DTS and the Link-4A DTS.
It consists of an AN/UYK-43 computer, which runs the C2P
computer program, controlled by an AN/USQ-69 data
terminal set (DTS). The AN/USQ-69 DTS serves as the
Man-Machine Interface (MMI), also known as the
Human-Computer Interface (HCI), to the C2P hardware and
software. Two versions of the C2P software are implemented:
Version 0 for Model 4, and Version 1 for Model 5.
The rehost of the C2P software onto more affordable COTS

equipments has been completed. The Model 4 system has been
installed in LHD platforms and training sites; Model 5 AEGIS
installations commence in FY 1999. This new configuration
is designated the C2P Rehost, or C2P(R). The UYK-43
computer is replaced by an UYQ-70(V) configured with two
20-slot VME card racks containing the computer and interface
cards and the USQ-69 DTS is replaced by an Aydin worksta-
tion for the HCI. The basic functions and operator inputs
remain the same although the HCI has been improved in the
new workstation.
Section C The Command and Control Processor 2-11
lk16_ch2 11 9/24/1, 11:19 AM

LGN 135-02-002
C2P Functions ■
The C2P is at the heart of the Link-16 system and performs a
multitude of critical functions. It receives outgoing information
from the TDS computer, translates it, and formats it for
subsequent transmission on Link-16, on Link-11, or on Link-4A.
Conversely, the C2P receives incoming information from these
tactical data links, translates it, and provides it to the TDS
computer. The C2P also automates many link-protocol, message-
formatting, and message-receipt/compliance functions. Finally, it
performs data forwarding whereby information received on one
data link is translated and retransmitted on another data link.
Link-4A

DTS Radio
Link-11
Link-11 Messages
Link-11 HF/UHF
DTS Radio
A
A AA
C2P
System
AA
Link-16
Link-16 Messages
Distribution System
MIL-STD-1553B Bus
(JTIDS) Terminal
■ Interface between the tactical

computers and the link data
terminals
■ Translate messages
■ Distribute messages
■ Perform receipt / compliance
LK16/2-08M-068
■ Forward data between links
Figure 2-8. The C2P is at the heart of the shipboard tactical data link
systems. As a message translation and distribution system, it provides the
interfaces between the TDS computer and the JTIDS terminal, the
Link-11 DTS, and the Link-4A DTS. The C2P is housed in a separate
AN/UYK-43 computer.
2-12 Section C The Command and Control Processor
lk16_ch2 12 9/24/1, 11:19 AM

Operator Selections and Inputs ■

The AN/USQ-69 DTS provides the HCI between the
operator and the C2P. It is an alphanumeric device used to
control the UYK-43 computer and the C2P program. The
AN/USQ-69 DTS is configured with a cathode-ray tube
(CRT) display for output and a keyboard for input. It
provides the means to prepare, display, edit, and transmit
text messages to the UYK-43 C2P computer and to display
the computer’s output. The operator of the C2P on AEGIS
ships is the Tactical Information Coordinator (TIC) and on
ACDS ships is the Track Supervisor (“Track Sup”).
To control the data links, the operator may select any of over
30 displays from the HCI’s “Table of Contents” screen.
Operator entries, such as Participating Unit or JTIDS Unit
(PU/JU), Data Link Reference Point (DLRP), track block
assignments for both Link-16 and Link-11, and operational
mode, must be entered at the HCI before a link can be
initiated. Improperly entering any of these values may cause
the link to degrade or to break down completely.
It should be noted that AEGIS Model-5 ships will incorporate

or embed the C2P HCI control functions into the AEGIS
TDS Model-5 system. In other words, the interface between
the C2P and the JTIDS terminal will be controlled at the
OJ-663 operator console, rather than at the AN/USQ-69. The
AN/USQ-69 DTS will still be connected, however, and will
be available as a backup in the computer room.
Section C The Command and Control Processor 2-13
lk16_ch2 13 9/24/1, 11:19 AM

LGN 135-02-002
Section D
The JTIDS Class-2 Terminal
The AN/URC-107(V)7 shipboard JTIDS terminal is an
advanced radio system that provides for the rapid exchange
of tactical information among a large number of users. It
employs secure, jam-resistant, digital data and voice
communications at a combined rate of 28.8, 57.6, or 115.2
kbps to provide a communications link with a low probability
of intercept (LPI). JTIDS operates in the 960-MHz to
1215-MHz frequency band and employs the Time Division
Multiple Access (TDMA) architecture described in Chapter 4.
JTIDS, which provides line-of-sight (LOS) communications,
is designed for interoperability with other Services and the
Allies.
Terminal Functions ■
To better understand all the functions of the JTIDS terminal,
let’s compare it with a Link-11 system. A shipboard Link-11
system includes a KG-40 for encryption, a Link-11 DTS for
analog-to-digital conversions, and a radio for transmission
and reception.
2-14 Section D The JTIDS Class-2 Terminal
lk16_ch2 14 9/24/1, 11:19 AM

The shipboard JTIDS terminal incorporates the functions of The JTIDS

all three of these components (the KG, DTS, and radio) into terminal
one cabinet and includes many other capabilities in addition combines the
to exchanging tactical information. These include: functions of the
KG, DTS, and
■ Precise Participant Location and Identification radio into one
■ Relative Navigation cabinet.
■ Synchronization
■ Secure Voice
■ Relay
■ Built-in Test
Link-4A

DTS Radio
Link-11
Link-11 Messages
Link-11 HF/UHF
A
A A
DTS Radio
C2P
A
System
Link-16
Link-16 Messages Joint Tactical Information

Distribution System
MIL-STD-1553B Bus
(JTIDS) Terminal
■ Secure, jam-resistant, high

capacity, LPI digital data
communications
■ Secure voice circuits
■ Precise location and
identification
■ Relative navigation
■ Relay
9
06
M-
08
/2-
16
LK
Figure 2-9. The JTIDS terminal provides the RF connection to other

JTIDS units.
Section D The JTIDS Class-2 Terminal 2-15
lk16_ch2 15 9/24/1, 11:19 AM

LGN 135-02-002
■ Precise Participant Location and

Identification
Every JTIDS Transmission of Precise Participant Location and Identifi-

terminal cation (PPLI) messages is an automatic function of the
periodically JTIDS terminal that allows JTIDS units to report their
transmits position current status. Each PPLI message contains an abundance of
and status information about a unit, including its detailed position and
information identification information, its time quality, its IFF codes, and
automatically. much more.
■ Relative Navigation
Locations reported Relative Navigation (RELNAV) is also an automatic function

on the link are of the JTIDS terminal that uses both position estimates
combined with received from other units (for example, PPLI messages) as
time-of-arrival well as its own unit navigational inputs to calculate own
measurements by unit’s position. RELNAV is based on the ability to
the JTIDS terminal accurately determine interplatform ranges using RF pulses.
to improve the The mutual exchange of PPLI messages allows the posi-
unit’s positional tional accuracy of all platforms to approach that of the best
accuracy. unit in the network. Position is reported in both geodetic and
relative grid coordinate systems.
lk16_ch2 16 9/24/1, 11:19 AM

■ Synchronization
Synchronization is another automatic function of the JTIDS All terminals

terminal that is required for net entry and participation. A new adjust their clocks
unit wanting to enter the network “listens” for an Initial Entry to match the time
(IE) Message transmitted by the Network Time Reference of the NTR.
(NTR). Once the IE is successfully received, the new unit is
said to be in coarse synchronization with the network. It can
then transmit a Round Trip Timing (RTT) message, to which
the NTR replies. This exchange of RTT messages allows the
new JTIDS terminal to adjust its clock to match, within
nanoseconds, that of the NTR in a process called fine
synchronization. Every JTIDS terminal must maintain fine
synchronization in order to communicate with other units in
the network.
■ Secure Voice
The JTIDS terminal supports two simultaneous secure voice The JTIDS
channels, often referred to as J1 and J2, for JTIDS voice terminal provides
channel 1 and voice channel 2, respectively. Each shipboard for two
terminal contains two 16-kbps voice digitizers, or vocoders, independent
that translate voice audio to a stream of bits and divide them secure voice
into the designated time slots. On reception, the bits are channels, each
recombined and translated back into the audio signal. capable of
operating on 127
Multiple JTIDS voice circuits can be operated simultaneously, different circuits.
since each circuit of each channel is defined by a different net
number (0-127). In other words, if voice users A, B, C, and D
are all on separate platforms, voice users A and B can talk on
J1 on net 50 while voice users C and D are also talking on J1,
but on net 25. A and B will not interfere with C and D.
Although digital voice data is not error-coded — all transmitted
bits correspond to actual data bits — it is encrypted.
lk16_ch2 17 9/24/1, 11:19 AM

LGN 135-02-002
■ Relay
Any JTIDS unit The JTIDS terminal employs radio relay techniques to
can be initialized extend communications beyond line of sight (LOS). The
to function as a relay function is performed by retransmitting messages
relay. received during one time slot in another designated time slot
at a later time. The delay between the original transmission
and the relay retransmission varies between 6 and 31 time
slots. Any JTIDS terminal can function as a relay, but relays
must be designed into a JTIDS network in advance because a
JTIDS terminal must be assigned pairs of time slots in its
initialization load. After a terminal has been initialized as a
relay, it will automatically perform the function unless
directed otherwise. Note that the use of relays doubles the
number of time slots required to exchange data. More
detailed information concerning relays can be found in
Chapter 6.
■ Built-in Test
Terminal The Built-in Test (BIT) function of the JTIDS terminal

performance performs both on-line performance monitoring and manually
is continuously initiated monitoring for fault isolation. While the terminal is
monitored operating in the Link-16 net, the on-line performance
during monitoring function runs automatically and continuously in
operations. the background. If a fault is detected, a light will be
illuminated on the status panel. The manually initiated BIT
is more thorough than on-line monitoring, but it can only be
run when the terminal is not in the Link-16 net. Manual BIT
will isolate problems down to the Shop-Replaceable
Assembly (SRA) level — for example, to a faulty card. BIT
is intended to eliminate the need for support equipment to
isolate a JTIDS terminal fault.
lk16_ch2 18 9/24/1, 11:19 AM

Shipboard Terminal
Components ■
The AN/URC-107(V)7 Navy shipboard JTIDS terminal is
74 inches high, 24 inches wide, and 44 inches deep. It
weighs approximately 1600 pounds and consists of several
components, including:
■ Electronic Cabinet Assembly (ECA)

■ Digital Data Processor Group (DDPG)
■ Secure Data Unit (SDU)
■ Receiver/Transmitter (R/T)
■ High-Power Amplifier Group (HPAG)
■ Notch Filter Assembly (NFA)
■ Power Interface Units (PIUs)
■ Battery Assembly
Some of these items are composed of one or more Weapons

Replaceable Assemblies (WRAs). Each WRA, in turn, is
composed of Shop-Replaceable Assemblies (SRAs) —
individual cards, for example.
lk16_ch2 19 9/24/1, 11:19 AM

LGN 135-02-002
AAAAAAAAAAAAAAAAAAAAAAAA
Antenna A Antenna B
Link-16 Link-16
Receive Transmit /
Receive
RF Limiter
Antenna Notch
Interface Filter
Unit Assembly
To MIL-STD-1553B Bus
C2P
External High-
Timer Digital Data Receiver/
Power
Processor Transmitter Amplifier
Voice
Users
Blanker
Interface
Mute Unit
Secure
Data Unit
Indicator
Control Panel
Keyer
Control
JTIDS Terminal
Digital Data Processor Group Receiver/Transmitter High-Power Amplifier Group
LK16/2-08M-073
Figure 2-10. The JTIDS terminal consists of the Digital Data Processor Group, the Receiver/
Transmitter, and the High-Power Amplifier Group. Two control panels are provided. The
Secure Data Unit is a separate assembly that mounts directly on the terminal.
lk16_ch2 20 9/24/1, 11:19 AM

■ Electronic Cabinet Assembly
All of the components of the shipboard JTIDS terminal are housed

in an Electronic Cabinet Assembly (ECA) containing five drawers.
The ECA provides compartments to mount each item, interconnecting
cabling, blowers and ducting for cooling, host interface ports, and
protection against electromagnetic interference and environmental
hazards.
JTIDS Shipboard Terminal
Receiver/Transmitter
Drawer
Indicator Control Panel
WRA Status Panel
High-Power Amplifier
Group Drawer
Digital Data Processor

Group Drawer
Keyer Control Panel
On / Off / Standby
Battery
Secure Data Unit Fill Port
Power Interface Unit

Drawers
0
02
M-
-08
1 6/2
LK
Figure 2-11. The components of the shipboard JTIDS terminal are housed
in a single cabinet containing, from top to bottom, the Receiver/Transmitter,
High-Power Amplifier Group, Digital Data Processor Group, Secure Data
Unit, and Power Interface Units. Batteries are included.
lk16_ch2 21 9/24/1, 11:19 AM

LGN 135-02-002
■ Digital Data Processor Group
The Digital Data Processor Group (DDPG) resides in the

third drawer of the ECA and consists of two major
components:
■ the interface unit (IU)
■ the digital data processor (DDP).
The IU provides a tailored interface between the JTIDS

terminal and the host platform. In the shipboard
configuration, the C2P acts as the host computer for the
terminal. Data is transferred from the C2P to the IU over a
multiplexed (MUX) bus. This MUX bus has two parts,
which are designated the A bus and the B bus. Data may
pass over either one. The characteristics of this redundant,
multiplexed bus are defined in MIL-STD-1553B.
The Subscriber Interface Computer Program (SICP), a

software program that executes in the IU, is responsible for
The SICP,
all communications with the host platform and provides the
executing within
data processing necessary to integrate the terminal functions
the IU, is
with the host systems. Together, the IU and SICP provide for
responsible for
the exchange of digital data with the C2P, the conversion of
communications
voice signals from analog-to-digital and digital-to-analog, a
with the host
feedthrough interface to the DDP for the SDU and primary
platform.
power, a DC power interface with the battery, and the
interfaces for supplying and receiving blanking pulses from
the SLA-10B Blanking System. The blanking system blanks
the TACAN receivers while the JTIDS transmitter is active,
and blanks the JTIDS receiver while the TACAN transmitter
is active.
lk16_ch2 22 9/24/1, 11:19 AM

The DDP provides control of the R/T and HPAG, and

performs the processing necessary for transmitting and
receiving the JTIDS TDMA signal. RF signals between the
DDP and the R/T are exchanged on an intermediate
frequency of 75 MHz. Processors within the DDP perform
encryption and decryption, Reed-Solomon encoding and
decoding, and interleaving (refer to Chapter 4 for discussions
of these concepts). Other functions performed by the DDP
include the generation of jitter, the frequency-hopping
pattern, selection of the carrier frequency, the measurement
of Time of Arrival (TOA) data for position and
synchronization calculations, the execution of Built-in Tests
(BIT) for fault isolation, and the generation of alerts.
The Network Interface Computer Program (NICP), a The NICP,

software program that executes in the DDP has overall executing within
responsibility for communications with the JTIDS RF the DDP, is
network. In general, it controls TDMA message transmission responsible for
and reception processing, coarse and fine synchronization, communications
relative navigation (RELNAV) processing, and terminal and with the JTIDS RF
network monitoring. network.
lk16_ch2 23 9/24/1, 11:19 AM

LGN 135-02-002
Processors within The processors within the JTIDS terminal are connected by
the JTIDS the Plain Text Bus to each other and to shared Global
terminal Memory residing in the DDP. All transactions on this bus
communicate either are reads and writes to Global Memory or are port-to-
through shared port transfers. Port-to-port transfers are used, for example,
Global Memory. when communicating with the host external timer. Thus, the
SICP executing within the IU, and the NICP executing
within the DDP, communicate with each other through the
use of shared Global Memory located in the DDP.
J-Series
Messages
500-kHz TACAN Control

NFA JTIDS C2P TDS
Class-2
Terminal
Host Avionics TACAN Port
(Airborne Only)
AIU
Audio Voice
Port 1
HPA
Voice PTP
Audio
Port 2
C2P SICP NICP R/T

Global
Memory
LK16/2-08M-070
IU DDP
JTIDS Class-2
Terminal
Figure 2-12. The Digital Data Processor Group contains several processors which communicate
through shared Global Memory.
lk16_ch2 24 9/24/1, 11:20 AM

■ Secure Data Unit
The Secure Data Unit (SDU) is a removable assembly The SDU holds
mounted on the IU. It stores the cryptovariables loaded cryptovariables
during initialization and provides both message security which provide
(MSEC) and transmission security (TSEC). An Electronic both message
Transfer Device (ETD) is used to load the cryptovariables. security and
transmission
The cryptovariables (CVs), which are binary keys security.
represented by strings of ones and zeroes, are normally used
in pairs called today/tomorrow pairs. Each pair consists of
one CV for today’s operation and another CV for tomorrow’s
operation. This pairing of cryptovariables allows all
participating terminals to automatically shift to the
designated CV at “crypto rollover,” thereby providing
continuous JTIDS operations across the rollover period. The
SDU is provided as Communications Security (COMSEC)
material.
■ Receiver/Transmitter
The Receiver/Transmitter (R/T) resides in the top drawer of

the ECA. This component provides the radio frequency (RF) The R/T provides
and intermediate frequency (IF) signal processing required the RF and IF
for the JTIDS TDMA transmit and receive functions. It signal processing
contains eight JTIDS frequency synthesizer and receiver required for the
channels. When the R/T receives an RF signal from one of JTIDS transmit
the JTIDS antennas, it down-converts the signal to an IF of and receive
75 MHz and sends it to the DDPG for processing. When functions.
transmitting, the R/T receives a Continuous Phase-Shift
Modulation (CPSM) IF signal from the DDPG, up-converts it
to RF, and outputs a low-level, 200-watt signal to the high
power amplifier for transmission.
lk16_ch2 25 9/24/1, 11:20 AM

LGN 135-02-002
The R/T is controlled by the DDPG for all TDMA signal

processing. When receiving or transmitting a signal, the
DDPG tells the R/T which antenna to select and which
receiver to use, as well as providing frequency, timing, and
other necessary information.
■ High-Power Amplifier Group
The High-Power Amplifier Group (HPAG) resides in the

second drawer of the ECA. It consists of a high-power
amplifier (HPA) and an antenna interface unit (AIU). The
HPA amplifies a low-level, continuous phase-shift modu-
lated (CPSM) RF signal received from the R/T from about
200 watts to 1000 watts. The HPA can also operate at low
power when necessary, during which the HPA output is
about the same as the R/T output (200 W). The AIU pro-
vides the RF interface between the HPA and the shipboard
antenna system. Like the R/T, the components of the HPAG
are controlled by the DDPG.
■ Notch Filter Assembly
The Notch Filter Assembly (NFA) is an RF filter consisting

of a dual-notch band-pass filter and a circulator. An RF
filter, by definition, is a device used to reject signals of
certain frequencies while allowing others to pass. The band-
pass filter prevents transmissions of the JTIDS waveform in
both the Identification Friend or Foe (IFF) transponder
frequency bands centered on 1030 MHz and 1090 MHz and
on the shared JTIDS and TACAN frequencies. The circula-
tor routes outgoing transmissions to the antenna and routes
incoming signals received from the antenna to the R/T. An
RF Limiter prevents the receiver from being overdriven by
nearby transmitters.
lk16_ch2 26 9/24/1, 11:20 AM

Bandpass Filter
Circulator
Notch Filter Assembly
960 1030 1090 1215
IFF IFF
TACAN / DME
Channels
every 1 MHz
51 Frequencies
969 1008 1053 1065 1113 1206
JTIDS
Frequencies
every 3 MHz LK16/2-08M-021
Figure 2-13. The Notch Filter Assembly (NFA) prevents transmission of

the JTIDS waveform on any of the frequencies used for IFF and TACAN.
lk16_ch2 27 9/24/1, 11:20 AM

LGN 135-02-002
The PIUs condition ■ Power Interface Units

ship’s power and
control the The JTIDS shipboard terminal is equipped with two Power
application of Interface Units (PIUs). The HPAG’s PIU resides in the
power to the fourth drawer of the ECA. The PIU for the R/T and DDPG is
components of the in the fifth, or bottom, drawer. The two PIUs condition the
JTIDS terminal. shipboard power and control the application of power to the
terminal’s components. The 3-phase, 115-VAC, 60-Hz ship
power is converted to two outputs: 3-phase, 115-VAC at
400 Hz and 1-phase, 115-VAC at 400 Hz. The two PIUs are
identical and interchangeable. To minimize hazard to the
operator and to facilitate in-drawer maintenance, each PIU
contains a power interrupter that automatically removes
power from an ECA drawer whenever the drawer is opened.
■ Battery Assembly
The battery assembly is located on the face of the DDPG

Batteries are
drawer. It contains one nickel cadmium (NiCad) battery and
included for
two lithium sulphur dioxide cells. During brief primary
emergency
power interruptions, the NiCad battery provides emergency
backup power.
backup power to hold cryptovariables and maintain
synchronization and initialization data in Global Memory.
If the NiCad battery fails, the entire battery assembly must
be replaced. The lithium sulphur dioxide cells maintain
power to the chronometer. A removable cover provides
access to these replaceable cells.
lk16_ch2 28 9/24/1, 11:20 AM

Terminal Controls and Indicators ■

During operations, the JTIDS terminal is normally controlled
through the AN/USQ-69 DTS or the OJ-663 console. For
maintenance loading of cryptovariables, and backup purposes,
there are two control panels on the front of the equipment:
■ Indicator Control Panel

■ Keyer Control Panel
JTIDS Shipboard Terminal

Indicator
Control
Panel
Keyer
Control
Panel
0a
02
M-
08
/2-
16
LK
Figure 2-14. Two control panels on the equipment itself are

provided for loading cryptovariables, displaying terminal status,
and executing maintenance tests.
lk16_ch2 29 9/24/1, 11:20 AM

LGN 135-02-002
■ Indicator Control Panel
The Indicator Control Panel (ICP), which is located on the face of

the R/T drawer, consists of a display, alphanumeric keypad
function keys, and indicators. It provides the interface between the
technician and the JTIDS terminal. The ICP can be used to monitor
the terminal status and to display currently stored values of
terminal initialization and control data. The ICP permits initiation
of the terminal’s Built-in Test (BIT), and displays the results. The
ICP can also be used to manually initialize and control the JTIDS
terminal.
TIME SURFACE
OVERLOAD OVERRIDE CONTROL CPU/ALARM COL DRIVE
ICP FAIL
SCL PGI RST
U CE PANEL
DEF BM
DISPLAY
RST RST
PAGE STEP
1 2 3
A B C D E F G H I J 4 5 6
K L M N O P Q R S T 7 8 9
U V W X Y Z SP + – / • 0 ENT
LK16/2-08M-025
Figure 2-15. The Indicator Control Panel can be used to monitor

terminal status and to display currently stored initialization and control
data. Built-in Test functions are executed from this panel.
lk16_ch2 30 9/24/1, 11:20 AM

■ Keyer Control Panel
The Keyer Control Panel (KCP) is located on the face of the DDPG
drawer and is used during shipboard terminal initialization to
control the transfer of cryptovariables from the Electronic Transfer
Device (ETD) into memory in the Secure Data Unit (SDU).
VAR SELECT
4 5 SECURE ALARM
3 6
2 7
1 8
LAMP TEST
CONTROL COMMAND LOAD

OFF ENABLE FLAG
ZERO TEST
LK16/2-08M-024
Figure 2-16. Cryptovariables are loaded into the Secure Data Unit
through the Keyer Control Panel.
Terminal Initialization ■
The C2P initializes the shipboard JTIDS terminal from a tape
containing a library of predesigned networks. This tape is called
the JTIDS Network Library, or JNL. During initialization, the
operator specifies a network number, design option, and option
sequence number which enables the C2P to extract the required
time slot assignments from the JNL tape. Other parameters such as
the JU number and track block assignments are also entered.
Information required for initialization is disseminated to the Battle
Group in a military message called the Operational Tasking Data
Links or OPTASK LINK.
lk16_ch2 31 9/24/1, 11:20 AM

LGN 135-02-002
Section E
Link 16 Antennas
An antenna performs two functions: radiating electromagnetic
energy from a transmitting device to the atmosphere, and
converting the atmospheric electromagnetic radiation to RF
electric current for the receiver.
JTIDS operates in the UHF frequency spectrum, which is

limited to line of sight (LOS). UHF antennas, therefore, are
mounted as high as possible to maximize distance of LOS
communication. UHF signals are also subject to phenomena
Because of UHF such as shadowing and quadrant blockage, which limit the
LOS limitations, potentially omnidirectional coverage of UHF antennas. Null
JTIDS antennas points, or dead areas, in the antenna radiation pattern may
prevent a user from establishing full-period omnidirectional
are mounted as
coverage. Null points result when the antenna becomes
high as possible.
obstructed by metal objects, such as masts or other antenna
platforms. RF energy strikes these metal objects and is
reflected around them. An analogy is the shadow (or “null
point”) created when you stand in front of the beam
(UHF antenna radiation) of your car headlights.
The JTIDS The earlier version of the JTIDS shipboard antenna system
employs the AS-4127/URC-107(V) Transmit/Receive (T/R)
terminal receives
antenna and the AS-177B Receive-Only (RO) antenna. The
information from
AS-4127 antenna is 28 inches high, 47 inches in diameter, and
both antennas
weighs 133 pounds. It is physically mounted at the top of the
and selects mast supporting the TACAN antenna. The AS-177B antenna,
the messages from which is 20 inches high, 6.5 inches in diameter, and weighs
the antenna with 7 pounds, is mounted in a different location on each ship.
the more favorable The JTIDS terminal receives information from both antennas
signal-to-noise and selects the message from the antenna with the more
ratio. favorable signal-to-noise ratio.
2-32 Section E Link-16 Antennas
lk16_ch2 32 9/24/1, 11:20 AM

TACAN
Antenna
JTIDS
Antenna 1
AS-4127
Antenna 2
AS-177B
Feed-through Tube
MAST
Figure 2-17. The JTIDS antenna system employs two antennas. The larger, main antenna
interfaces to the NFA and transmits as well as receives. The smaller antenna interfaces
directly to the R/T and performs only the receive function. The earlier version of the JTIDS
antenna system employs the AS-4127 and the AS-177B antennas.
The new Link-16 antenna system consists of the AS-4127A T/R antenna and the
AS-4400 RO antenna. These units are issued as a set for shipboard installation, and
AEGIS ships were the first to receive them. The AS-4127A is a two-half,
wrap-around antenna that is 19.5 inches high, 41 inches in diameter, and weighs
100 pounds. It can be mounted in one of three configurations: on a vertical
cylindrical mast, on a canted rectangular mast, or with a mast extension unit that
supports the TACAN antenna. This last configuration is the highest on the mast and
provides the best LOS communication. The AS-4400 antenna, which is 17.7 inches
high, 6.0 inches wide at the base, and weighs 5 pounds, offers several improvements
over the AS-177B. It has a higher gain and an excellent voltage standing-wave ratio
(VSWR) throughout the JTIDS band. And, the AS-4400 can be used as a transmit
antenna if a failure occurs in the main T/R antenna — with some degradation in
pattern, however, due to blockage.
Section E Link-16 Antennas 2-33
lk16_ch2 33 9/24/1, 11:20 AM

LGN 135-02-002
Both antennas are broadband, vertically polarized UHF antennas that provide
omnidirectional coverage over the 960-to-1215-MHz JTIDS frequency band. Both
have a “peak-of-beam” at the horizon, which maximizes LOS, and both can operate
at 1.2 kW peak power and 140W average power. They are mounted so that the
antenna elevations have a 1:3 ratio. This height diversity between the AS-4127A and
the AS-4400 helps resolve multipath problems.
The AS-4400 antennas have also been installed for JTIDS applications at some
land-based facilities. At certain sites, two of the AS-4400 antennas have been
installed, with one configured to perform the T/R function and the other configured
for the RO function.
JTIDS
Antenna 1
AS-4127A
H/3
JTIDS
Antenna 2
AS-4400
Deep Water Line
Baseline
Figure 2-18. The newer configurations employ the AS-4127A T/R antenna with the AS-4400
RO antenna, mounted with a height diversity ratio of 1:3. Together these provide improved
performance, and the AS-4400 can be used as a transmit antenna if the main T/R antenna
fails.
2-34 Section E Link-16 Antennas
lk16_ch2 34 9/24/1, 12:32 PM

Section F
The Link-16 Data Flow
The successful exchange of Link-16 tactical information
requires that the data pathway extend completely from the
transmitting TDS computer to the receiving TDS computer.
The flow of digital data during transmission is illustrated in
Figure 2-19.
Section F The Link-16 Data Flow 2-35
lk16_ch2 35 9/24/1, 12:32 PM

LGN 135-02-002
Data to be transmitted is transferred from the TDS computer over

the MIL-STD-1397 interface to the C2P. From the C2P data is
passed to the JTIDS terminal over the MIL-STD-1553B bus. It is
received by the SICP software program executing in the IU. The
SICP passes it through Global Memory to the NICP software
program executing in the DDP. The NICP, acting together with
the Plain Text Processor and Cipher Text Processor, handles the
necessary encryption, encoding, interleaving, and conversion to a
series of CPSM pulses. This pulse train is modulated onto the
75-MHz IF and transferred to the R/T, where it is modulated onto
one of 51 UHF carriers in a predetermined hopping pattern. The
modulated carrier is boosted to 1000 watts by the HPA and output
to the antenna through the AIU and NFA. The NFA filters the
transmitted signal to ensure there is no interference with IFF or
TACAN. The signal is transmitted on a particular time slot of a
particular net. Certain signal characteristics are determined by the
TSEC cryptovariable.
Tactical
Data JTIDS Terminal
C2P
System
(70 bits) (70 bits) Transmit on
10110101 10110101
SICP NICP assigned time
slot of assigned
. . . . 01 . . . . 01 ■ Net ■ Encrypt net of assigned
■ NPG ■ Parity NPG
■ Time Slot ■ Encode R/T NFA

■ Interleave
■ Symbol Generation
■ CPSM pulses
Modulation
LK16/2-08M-071
Figure 2-19. The 70-bit data words for transmission are encrypted, encoded, interleaved, and
converted to transmission symbol pulses for transmission during an assigned time slot on an
assigned net of an assigned Network Participation Group (NPG).
2-36 Section F The Link-16 Data Flow
lk16_ch2 36 9/24/1, 12:32 PM

Any unit assigned to receive that particular time slot of that

particular net with that identical TSEC cryptovariable can receive
the transmitted signal. The flow of data during reception is
illustrated in Figure 2-20. Signals received at the antennas are
passed to the R/T, where the pulse train is demodulated from the
hopping carriers. The CPSM pulse train is passed on the intermediate
frequency to the DDP. Software within the DDP controls which
antenna is used. In order to correctly deinterleave, decode, and
decrypt the message data, the receiving unit must also have the
correct MSEC cryptovariable. The deinterleaved, decoded,
decrypted data is passed through Global Memory to the SICP. The
SICP forwards it over the 1553B bus to the C2P which, in turn,
forwards it over the MIL-STD-1397 interface to the TDS computer.
Not all transmitted messages originate at the TDS computer. Some

messages originate at the terminal, including the synchronization
messages exchanged between terminals, the periodic transmission of
messages providing identification, position, and status of each unit,
and the machine acknowledgment of the receipt of particular
messages.
Tactical
Data
JTIDS Terminal C2P System
(70 bits) (70 bits)
Receive on NICP SICP 10110101 10110101
assigned time . . . . 01 . . . . 01
slot of assigned ■ Convert to symbols
net of assigned
NPG ■ Deinterleave
R/T
■ Decode
■ Parity check
■ Decrypt
Demodulation
LK16/2-08M-072
Figure 2-20. Frequency-hopped pulses are demodulated from the carrier and passed to the
JTIDS terminal for deinterleaving, decoding and decrypting of the 70-bit message data
words. Reed-Solomon error correction and parity checking ensures that the original message
is received uncorrupted by bit errors.
Section F The Link-16 Data Flow 2-37
lk16_ch2 37 9/24/1, 12:32 PM

LGN 135-02-002
Figure 2-21. Ships scheduled to receive Link-16 include crusiers, destroyers, amphibious
assault ships, and all aircraft carriers.
2-38 Section F The Link-16 Data Flow
lk16_2_38 38 9/21/1, 5:55 PM

3
C
H
A
P
T
E
R
The Airborne Link-16

Equipment
Introduction
To understand the operation of the airborne Link-16 system, it is important to be able to
identify the hardware components which comprise it and the functions they perform. In
this chapter, you will learn about the U.S. Navy’s airborne platforms, their missions, and
the components of their airborne Link-16 systems, including their mission computers,
their Joint Tactical Information Distribution System (JTIDS) terminals, and their JTIDS
antennas.
The E-2C Hawkeye and the F-14D Tomcat are the only two Navy airborne platforms on
which JTIDS are currently being installed. Nearer the end of this century, the Navy’s
F/A-18 Hornets will become equipped with a different Link-16-compatible terminal, the
Multifunctional Information Distribution System (MIDS). This chapter concentrates on
the E-2C and the F-14D and the airborne variants of the JTIDS terminal.
3-1
*ch3_1-18 1 9/24/1, 4:39 PM

LGN 135-02-002
Section A
Overview of Navy Link-16
Airborne Platforms
The Link-16 systems aboard aircraft differ somewhat from
their shipboard counterparts. Constraints on space and the
load envelope aboard aircraft, for example, dictate that the
components of airborne JTIDS terminals be located
separately, rather than within a single large, heavy cabinet.
Further, the human-computer interface must sometimes
accommodate existing controls and displays. The systems on
both types of platform however, perform the same function:
transmitting and receiving Link-16’s J-series messages. All
airborne platforms implement Model-5 Link-16.
The Navy The Navy airborne Link-16 platforms are of two general
airborne types. One, the E-2C Hawkeye, is a carrier-based Airborne
Link-16 Early Warning (AEW) system, equipped as an airborne
platforms command and control (C2) platform. The other, the F-14D
are the Tomcat, is an interceptor (“fighter”) aircraft, equipped for
E-2C and carrying out airborne intercept missions under the direction
the F-14D. of a C2 platform and capable of communicating with
similarly equipped fighters using J-series messages in the
Link-16 Fighter-to-Fighter Network Participation
Group (NPG).
Airborne platforms extend and augment the tactical

information available to ships and to land-based facilities,
thereby expanding their radar picture. The radar range of an
E-2C at 30,000 feet is greater than 200 miles, for example,
whereas the radar horizon at the earth’s surface is only about
40 miles.
3-2 Section A Overview of Navy Link-16 Airborne Platforms
*ch3_1-18 2 9/24/1, 4:39 PM

Operational testing and evaluation of the airborne Model-5 Airborne

Link-16 system occurred during the early 1990s. Squadrons platforms extend
of E-2Cs and F-14Ds on the West Coast supported this the tactical
testing. Initial Operational Capability (IOC) for the Link-16 picture to provide
systems, both airborne and shipboard, was planned for 1994. early warning
information.
E-2C
Manufacturer Grumman
Wing Span (ft) 81 (29 folded)
Length (ft) 58
Height (ft) 18
Service U.S. Navy
Mission Early Warning, Tactical Command & Control
Based Carrier, Shore
Crew Size 5
F-14 Tomcat
Manufacturer Grumman Service U.S. Navy

Wing Span (ft) 64 Mission Tactical Fighter
LK-16/3-08M-90
Length (ft) 62 Based Carrier

Height (ft) 16 Crew Size 2
Figure 3-1. Airborne Link-16 platforms greatly extend the tactical

picture available to ships and land-based facilities by providing
early warning information. They also act as JTIDS relays. The
E-2C is a command and control (C2) platform. The F-14D, a
nonC2 JU, possesses the fighter-to-fighter capability.
Section A Overview of Navy Link-16 Airborne Platforms 3-3
*ch3_1-18 3 9/24/1, 4:39 PM

LGN 135-02-002
Tactical Data Link Support ■

The addition of the Link-16 system will enhance the present
capabilities of these airborne platforms by adding precise
participant location, identification (PPLI) and status, relative
navigation, two channels of jam-resistant secure voice, and
voice and data relay. The F-14D will also gain secure data
networks for air control and fighter-to-fighter communica-
tions, while the E-2C will gain an antijam antenna system,
as well as secure data networks for air control, surveillance,
electronic warfare, and weapons coordination and mission
management. These aircraft perform a vital role in the JTIDS
network by acting as relays of the other units’ transmissions.
Both the E-2C and the F-14D will retain the ability to
communicate on other tactical data links. The E-2C Hawkeye,
The airborne for example, retains its current Link-11 and Link-4A
platforms will capabilities and will now be able to conduct simultaneous
retain their Link-4A and Link-16 air control while performing Link-16
ability to support surveillance. A special broadcast mode in the E-2C, used
other links. when all other units have been placed in emission control
(EMCON), will allow this aircraft to transmit all tracks
simultaneously on Link-11 and Link-16. Because the E-2C
is not equipped with a C2P, however, it cannot function as a
data forwarder between the two links.
The F-14D Tomcat is equipped for Link-4A air control and

Link-4C fighter-to-fighter communications. It retains its
ability to be controlled over Link-4A and can now be
controlled over Link-16 which, unlike Link-4A, is
jam-resistant and secure. While the F-14D is operating on
Link-4A, its Link-16 system nevertheless will continue to
transmit PPLI messages and JTIDS voice communications.
*ch3_1-18 4 9/24/1, 4:39 PM

Airborne Link-16 System

Components ■
The major components that comprise the Navy airborne
Link-16 system are:
■ the mission computer

■ the JTIDS terminal
■ the JTIDS antennas.
The mission computer provides the tactical data to be

exchanged; the JTIDS terminal and antennas provide the Airborne
secure, antijam, increased-capacity waveform. Unlike the platforms, having
Link-16 configurations of surface platforms, however, the no C2P, cannot
airborne platform configurations do not include the forward data
Command and Control Processor (C2P). Their mission between links.
computers act as the host computer, interfacing with the
JTIDS terminal directly.
In contrast to the ship’s two-phased computer program

upgrade (the Model-4 and Model-5 phases), the Navy’s All airborne
airborne Link-16 system has been planned as a single-phase Link-16 platforms
implementation, which is designated Model 5. The computer are Model-5
program upgrades to the mission computers of the E-2C and platforms.
the F-14D support the expanded capabilities provided by the
J-series messages.
*ch3_1-18 5 9/24/1, 4:39 PM

LGN 135-02-002
JTIDS Terminal Variants ■

The Navy currently employs three variants of the JTIDS AN/
URC-107 terminal. These are the E-2C’s airborne terminal,
designated the AN/URC-107(V)5, and the F-14D’s airborne
terminal, designated the AN/URC-107(V)6 and, of course,
the Class-2H shipboard terminal, the AN/URC-107(V)7,
discussed in Chapter 2.
The principal components common to each of the three

versions are:
■ the digital data processor group (DDPG)

■ the secure data unit (SDU)
■ the receiver/transmitter (R/T)
■ the battery assembly.
One component of the DDPG, the digital data processor

(DDP), is basically identical for both shipboard and airborne
terminals. A single version of the Network Interface Control
Program (NICP) executes in all versions of the DDP.
Different versions of the Subscriber Interface Control
Program (SICP), however, execute in the Interface Units
(IUs) of the airborne terminals.
Airborne The R/T is nearly identical for shipboard and airborne

terminals terminals, except that the airborne R/T implements the
include a terminal's built-in TACAN functions allowing it to replace
TACAN the ARN-118 TACAN system. The F-14D’s JTIDS terminal
function. components do not include the high-power amplifier
group (HPAG).
*ch3_1-18 6 9/24/1, 4:39 PM

Operational Considerations ■
JTIDS operates in the UHF frequency spectrum, which limits Maximum
communications to line of sight (LOS). With aircraft at 30,000 practical LOS
feet, however, LOS communications can occur at distances range for
greater than 300 nautical miles (nm). Setting up an aircraft as a air-to-air
relay can extend LOS communications to nearly 600 nm. With communications
ship-to-ship LOS communications limited to about 25 nm, it is is about
easy to see the importance of a Link-16 aircraft. 300 nm.
Acting as relays, the Link-16 aircraft perform a vital role in

extending the JTIDS radio horizon. The range of LOS
communications is limited by the curvature of the earth. The By operating
distance to the geometric horizon increases with altitude. UHF as relays, the
radio transmissions actually travel further than the geometric Link-16 aircraft
horizon because of refraction, or bending, of the signal by the extend the
atmosphere. The path of this refracted signal may be represented by radio horizon
straight-line propagation if the radius of the earth is modified so that of the JTIDS
the relative curvature between the signal and the earth remains network.
unchanged. The new radius of the earth, known as the effective
earth radius, defines the radio horizon.
The ratio between the effective earth radius and the true earth
radius, denoted by the symbol K, can vary between 1/2 and 5.
The average value of K in temperate climates, however, is
approximately 4/3. Using this value for the effective-radius
factor, and assuming that the altitude of a transmitter is much
smaller than the radius of the earth, a good approximation of the
distance to the radio horizon (in miles) is √2h where h is the
altitude measured in feet. The nomogram in Figure 3-3 gives the
maximum radio path length between a transmitting antenna at
one altitude and a receiving antenna at another. The distance to
the radio horizon can be found by using a value of zero for one
of the antennas.
*ch3_1-18 7 9/25/1, 1:29 PM

LGN 135-02-002
Radio coverage
D at altitude h
h
"TRUE" EARTH
"RADIO" EARTH
D= 2h LK-16/3-08M-91 R1
h = altitude in feet
D = distance in miles
K = 4/3; not to scale
Figure 3-2. The range of LOS communications is limited by the curvature of the earth. UHF
radio transmissions actually extend beyond the geometric horizon because of refraction, or
bending, of the signal by the atmosphere. This increase in range can be approximated by an
enlarged earth. Using an effective-earth-radius factor suitable for temperate climates, the
distance D in miles to the radio horizon for a transmitter at height h in feet can be
approximated by D = √2h.
*ch3_1-18 8 9/25/1, 1:30 PM

Receiving Antenna Maximum Radio Path Transmitting Antenna

Height In Feet Distance in Miles Height In Feet
Figure 3-3. The maximum radio path length in miles between antennas at
different heights is given in this nomogram. In this example, the height of the
receiving antenna is 200 feet and the height of the transmitting antenna is
15,000 feet, giving a maximum radio-path length of 190 miles. To obtain the
distance to the radio horizon, use a height of 0 feet for one of the antennas.
*ch3_1-18 9 9/24/1, 4:41 PM

LGN 135-02-002
Section B
The E-2C Hawkeye
The E-2 Hawkeye, manufactured by Grumman, was one of
the first airborne early warning, tactical command and
control aircraft. Sixty-two of these aircraft were initially
delivered as E-2As to carrier-based squadrons during the
1960s. In the early 1970s, the E-2As were modified to meet
the E-2B standard, which differed mainly in having an
improved computer. Deliveries of the E-2Cs also began in
the early 1970s. The E-2C is the current configuration, and
over eighty of these models are in operation.
Mission ■
The E-2C's primary mission is to augment and extend the
Battle Group's air picture. At an altitude of 30,000 feet, the
E-2Cs extend the radar detection range of the E-2 exceeds 300 miles. The
Battle Group's air E-2C can maintain a 3-million-cubic-mile surveillance
picture. envelope while simultaneously monitoring maritime traffic.
It can track over 600 targets and control over 40 airborne
intercepts. A squadron of E-2Cs is usually assigned to a
carrier. Currently, sixteen squadrons are deployed.
E-2Cs are additionally employed to patrol the skies during

space shuttle launches, as well as to direct drug smuggling
interceptions by the U.S. Coast Guard and the U.S. Customs
Service.
3-10 Section B The E-2C Hawkeye
*ch3_1-18 10 9/24/1, 4:41 PM

Figure 3-4. The E-2C Hawkeye is a Link-16 airborne platform deployed for
surveillance and air intercept control. With its enhanced radar range, it
provides surface combatants with early warning information.
Section B The E-2C Hawkeye 3-11
*ch3_1-18 11 9/24/1, 4:41 PM

LGN 135-02-002
Description ■
Because the E-2Cs are carrier-based, they have the unusual

feature of foldable wings. A rotodome, atop the aircraft,
houses the search radars and IFF antennas. It is 24 feet in
diameter and rotates at 10 rpm during flight.
The aircraft is manned by a crew of 5, consisting of the pilot,

copilot, CIC Officer (CICO), Air Control Officer (ACO),
and Flight Technician (FT) or Radar Operator. While it can
remain aloft for up to 6 hours, the time on station is usually
3 or 4 hours.
Equipment Configuration ■
The E-2C’s Link-16 system consists of the L-304 mission
computer, the JTIDS terminal and specially adapted controls,
and four JTIDS antennas. As part of the mission computer
upgrade, the JTIDS terminal was installed along with the
Global Positioning System (GPS), an Enhanced High-Speed
Processor (EHSP), an improved APS-145 radar, and new
displays. The L-304 mission computer program has been
upgraded as well, to implement the protocols for Link-16
data exchange. The equipment configuration of the E-2C is
illustrated in Figure 3-5. Refer to Figure 3-6 for their
locations aboard the aircraft.
*ch3_1-18 12 9/24/1, 4:41 PM

Link-16 Receive
TACAN Link-16
Transmit / Receive Transmit
Antenna
Interface
Unit
MIL-STD-1553B BUS
Mission
Computer External Digital High
Timer Receiver/
Data Power
Transmitter
Processor Amplifier
Voice
Blanker
Mute Interface
Unit
SAHRS
Course
Indicators
IFF
BDHIs
TACAN
Control Secure
JTIDS Data Unit
Control Panel
Load Control
Unit
Battery LK-16/3-08M-095
Figure 3-5. The E-2C JTIDS system consists of the JTIDS Class-2 terminal, which interfaces
with the mission computer and several other host systems to provide Link-16, TACAN, and
navigation functions. In addition, the E-2C JTIDS system includes a High Power Amplifier
Group and the JTIDS antennas.
*ch3_1-18 13 9/24/1, 4:41 PM

LGN 135-02-002
1 2 3 8
6 7 9
A A
4
10
5
LK-16/3-08M-094
11 11
1 ACO Display 7 JTIDS HPAG

2 CICO Display 8 TACAN Control Panel
3 FT Display 9 Cockpit Display
4 Computer 10 JTIDS Audio Select Panel
5 JTIDS DPG and Battery 11 JTIDS Antennas
6 JTIDS R/T
Figure 3-6. The E-2C’s Link-16 configuration consists of an upgrade to its mission computer,
an improved radar system, JTIDS terminal components, and new displays. The E-2C’s JTIDS
components are located in its forward section, and the controls and displays are located in the
aft section. The wing-mounted antennas are not shown.
■ E-2C Mission Computer

Installation of the Link-16 system in the E-2C was an
integral part of the Group II upgrade. The upgraded mission
The E-2C’s computer program formats tactical digital information into
upgraded mission J-series messages and provides them directly to the JTIDS
computer supports a terminal through the MIL-STD-1553B multiplex (MUX)
complete Model-5 bus. The L-304 mission computer supports a complete
Link-16 database. Model-5 TADIL-J database, enabling it to take full advantage
of Link-16, including enhanced Link-16 air control, improved
identification and status reporting, improved navigation, and a
greater degree of accuracy in surveillance track processing.
*ch3_1-18 14 9/24/1, 4:41 PM

■ Display and Control Consoles

The E-2C controls and displays include Multifunction Control and
Display Units (MFCDUs), JTIDS audio select panels, Enhanced
Main Display Units (EMDUs), and the main JTIDS functional
control panel. The MFCDU controls JTIDS terminal operating
modes, functions, and data exchange. One MFCDU is located in
the cockpit, and three more are located aft at the Combat
Information Center (CIC).
1
4
LK-16/3-08M-097
1 JTIDS Audio Select Panel
2 MFCDU
3 TACAN Control Panel
(Above Windshield)
4 JTIDS Audio Select Panel
5 MFCDU Control
Figure 3-7. The JTIDS controls in the E-2C's cockpit include two audio
select panels, the MFCDU, and the TACAN control panel.
*ch3_1-18 15 9/24/1, 4:41 PM

LGN 135-02-002
A
AAAAAA
AAAAAAA
AA
AA
1 MFCDU Control Panel
2 JTIDS Audio Channel Select

Panel
3 JTIDS Functional Control

Panel
AAAAA
4 MFCDU
AAAAA
3
EMDU
1 2 4
ADU
LK-16/3-08M-098
Figure 3-8. The E-2C's CIC also contains JTIDS controls and displays. Here, the location
of the ACO station in the CIC is shown. The ACO station contains a Multifunction Control
and Display Unit (MFCDU), an Enhanced Main Display Unit (EMCU), and a JTIDS
functional control panel.
*ch3_1-18 16 9/24/1, 4:41 PM

The JTIDS audio select panels, in the cockpit and at the Air
Control Officer (ACO) station in the CIC, indicate voice
channel activity and allow the selection of TRANSMIT,
TRANSMIT/RECEIVE, or RECEIVE ONLY on each of the
two JTIDS secure voice channels. The EMDU, located at
each of the aft CIC stations, is integrated with the E-2C’s
weapons control functions, including communications
functions associated with Link-16, Link-11, and Link-4A.
The single main JTIDS functional control panel, located at
the ACO station in the aft CIC section, performs the ON/
STANDBY/OFF function necessary when resetting the
terminal. It also contains a separate switch to zeroize the
encryption device, another switch for enabling long-term
transmit inhibit (LTTI) during EMCON operations, and
audio volume controls for the two JTIDS voice channels.
The E-2C’s JTIDS terminal also includes the TACAN

functions, replacing the AN/ARN-118 TACAN system. The
operation of the TACAN control panel in the cockpit has not
changed.
*ch3_1-18 17 9/24/1, 4:41 PM

LGN 135-02-002
■ JTIDS Antennas
The E-2C’s antenna system used for JTIDS consists of four

antennas. The main receive-only antenna is mounted on the
underside of the E-2C, in the middle of the aircraft. The
main JTIDS transmit antenna is also mounted on the
underside, but farther aft toward the tail. Both antennas are
broadband, vertically-polarized UHF antennas that provide
omnidirectional coverage over the 960-to-1215-MHz JTIDS
frequency band. The E-2C's antennas also support other
communications systems besides JTIDS.
One antijam (AJ) receive antenna is mounted on each wing.

When the signal-to-noise ratio is low on the main receive
antenna, the E-2C’s mission computer will automatically
select one of the two wing-mounted AJ receive antennas.
The wing-mounted antennas are particularly useful when the
E-2C is operating in a jammer environment. The body of the
aircraft will shield one of the AJ antennas from the jammer,
thereby allowing reception to continue without being
jammed.
The E-2C The E-2C's JTIDS terminal is loaded from a Raymond
JTIDS terminal cassette created by the Tactical Aircraft Mission Planning
is loaded from System (TAMPS). Three initialization files can be stored on
a Raymond each cassette. Processing a JNL tape to create terminal
cassette. initialization files is just one of the functions performed by
TAMPS. Information required for building initialization
files is provided in the OPTASK LINK message.
*ch3_1-18 18 9/24/1, 4:41 PM

Section C
The F-14D Tomcat
The Navy’s F-14 Tomcat fighter aircraft, built by Grumman,
has been deployed aboard aircraft carriers since the early
1970s. Over 500 F-14As were delivered until production of
this version ceased in the late 1980s. In addition, 80 F-14As
were sold to the Iranian Air Force between 1976 and 1978.
The F-14D, built since the mid-1980s, is the current version,
containing upgrades to its radar, weapons management, and
navigation systems.
Navy F-14 Tomcat squadrons are stationed aboard twelve

aircraft carriers, as well as at the Naval Air Stations at
Miramar, California; at Oceana, Virginia; and at
Dallas, Texas.
Mission ■
The multimission-capable F-14D Tomcat is designed for air The F-14D can be
superiority and fleet air defense. Its primary mission is controlled over
performing air intercepts. It can be controlled either over either Link-16 or
Link-16 or Link-4A. Link-4A.
Section C The F-14D Tomcat 3-19
*CH3_19-28 19 9/24/1, 7:33 PM

LGN 135-02-002
Description ■
The Tomcat is a supersonic, twin-seat, twin-engine fighter aircraft.
It can vary its wing geometry from forward to swept-back position.
Its wings are programmed to move forward or backward
automatically for optimal flight, although the aircrew may override
this programming. The twin vertical fins of its tail is readily
observed in forward profile. Although it typically cruises at speeds
between 400 and 550 knots, at high altitude the Tomcat is capable
of exceeding twice the speed of sound.
The aircrew consists of two persons: the pilot occupies the front
seat, and the Radar Intercept Officer (RIO) occupies the rear seat.
Figure 3-9. The F-14D Tomcat is a two-person interceptor (“fighter”) aircraft

equipped for airborne intercept and surface strike missions. It can be controlled
over both Link-16 and Link-4A and can exchange tactical data with other
F-14Ds on either Link-16 or Link-4C. The F-14D’s wings can sweep farther aft
at high speeds to optimize its aerodynamic profile.
3-20 Section C The F-14D Tomcat
*CH3_19-28 20 9/24/1, 7:34 PM

Equipment Configuration ■
To provide Link-16 communications, the F-14 Tomcat employs the
AYK-14 mission computer in conjunction with the JTIDS terminal.
In addition, it retains its capability to perform Link-4A and can
now conduct air control operations on either Link-4A or Link-16.
The F-14D will also be able to exchange target information and
report engagement status with other F-14Ds through the fighter-to-
fighter NPG. The F-14D’s equipment configuration is illustrated in
Figure 3-10. Refer to Figure 3-11 for their locations aboard
the aircraft. Antenna A Antenna B
Link-16/TACAN Link-16/TACAN
Transmit/Receive Transmit/Receive
MIL-STD-1553B BUS
Mission
Computer External Digital
Timer Receiver/
Data
Transmitter
Processor
Voice
Blanker
Mute Interface
Unit
SAHRS
Course
Indicators
IFF
BDHIs
TACAN
Control Secure
JTIDS Data Unit
Control Panel
Load Control
Unit
Battery
LK16/3-08M-096
Figure 3-10. The JTIDS terminal interfaces with the mission computer
and several other host systems to provide Link-16, TACAN, and
navigation functions for the F-14D.
*CH3_19-28 21 9/24/1, 7:34 PM

LGN 135-02-002
7 8 9
LK-16/3-08M-099
6 5 4 3 2 1
1 JTIDS Battery 6 JTIDS Receiver/Transmitter (or TACAN)

2 JTIDS Data Processor 7 JTIDS Control Box
3 Mission Computer #2 (AYK-14) 8 Mission Computer #4 (AYK-14)
4 JTIDS Bottom Antenna 9 JTIDS Top Antenna
5 LCU Control Panel
Figure 3-11. The F-14D’s Link-16 configuration consists of the AYK-14 mission computer,
the JTIDS terminal, and the JTIDS antennas. With the Model-5 upgrade in place, JTIDS’
TACAN function will replace the F-14D’s AN/ARN-118 TACAN system.
*CH3_19-28 22 9/24/1, 7:34 PM

■ Mission Computer
Link-16 system integration on the F-14D is part of the

complete avionics overhaul of an earlier version, the
F-14A-Plus. The JTIDS terminal is integrated into the
aircraft through the AYK-14 mission computer. The mission
computer program of the AYK-14 has been upgraded to
implement the Link-16 protocols for data exchange. This
program formats tactical digital information into J-series
messages and provides them directly to the JTIDS terminal
via the MIL-STD-1553B MUX bus.
The AYK-14 mission computer supports a Model-5 Link-16

database. Because the F-14D JTIDS terminal includes the
TACAN system functions, the complete overhaul also
includes replacing the existing AN/ARN-118 TACAN set.
*CH3_19-28 23 9/24/1, 7:34 PM

LGN 135-02-002
■ Controls and Displays
The F-14D’s Link-16 controls and displays include the

Digital Display and Tactical Information Display (DD/TID),
three Multifunction Digital Readout Indicators (MDRI), a
Data Entry Unit (DEU), a cryptoload control unit (LCU),
and several switch panels and indicators. The DD/TID,
located at the back seat or Radar Intercept Officer (RIO)
position, provides control and display of Link-16
information and display of Link-16 and local sensor targets
and orders. The three MDRIs have three Link-16-related
operating modes:
■ Tactical Situation Display, similar to DD/TID

■ Navigation aid control and display
■ Link-16 data readout.
Two of the MDRIs are located in the front at the pilot

position, while the third is located in the back at the RIO
position. The DEU, a 20-pushtile keypad with a two-line
display, is used to change operating modes, aircraft
navigation modes, and other crew-selectable data. Status
information requested at the DEU can be displayed to the
RIO and the Pilot by the MDRI.
*CH3_19-28 24 9/24/1, 7:34 PM

1 1
LK-16/3-08M-100
1 MDRI
2 Radio Frequency/Channel
Indicator
3 Audio Controls
Figure 3-12. Some of the F-14D’s JTIDS controls and displays,

including two Multifunction Digital Readout Indicators (MDRIs)
and an RF channel indicator, are available to the pilot.
*CH3_19-28 25 9/24/1, 7:34 PM

LGN 135-02-002
6
4
9
3
7
8
2
LK-16/3-08M-101
1 Antenna Select Panel 6 MDRI

2 JTIDS Control Panel 7 Data Entry Unit (DEU)
3 Radio Frequency/Channel Indicator 8 Data Link Control Panel
4 Tactical Information Display (TID) 9 Data Storage Set (DSS)
5 Digital Display (DD)
Figure 3-13. Most of the F-14D’s JTIDS controls and displays are available to the
RIO. These include a digital display, a tactical information display, an RF channel
indicator, a JTIDS control panel, an antenna selection panel, one MDRI, a data
entry unit (DEU), and a data link control panel.
*CH3_19-28 26 9/24/1, 7:34 PM

The switch panels and indicators installed at the RIO position

as part of the Link-16 system include
■ the JTIDS control panel, which selects JTIDS

terminal operating modes, zeroizes crypto keys, and
provides alarm resets
■ the antenna select panel, which allows automatic or

manual selection of the upper and lower JTIDS
antennas
■ the radio frequency channel indicator, which controls

the JTIDS voice channel audio volume and selects
transmit and receive combinations on each of the two
JTIDS voice channels.
The JTIDS terminal also contains an integrated TACAN,

eliminating the ARN-118 TACAN unit. Controls and
indicators for the TACAN function, however, remain
unchanged.
*CH3_19-28 27 9/24/1, 7:34 PM

LGN 135-02-002
■ JTIDS Antennas
The F-14D antenna system used for JTIDS consists of two

new ARC-182(V) UHF transmit/receive (T/R) antennas,
which are located on the top and bottom of the aircraft. The
top antenna is mounted just behind the canopy, and the
bottom antenna is mounted on the underside, near the front
of the aircraft. Both are broadband, vertically-polarized UHF
antennas that provide omnidirectional coverage over the
960-to-1215-MHz JTIDS frequency band. The transmit and
receive selection can be made either manually or
automatically. The JTIDS terminal will automatically select
the antenna with the more favorable signal-to-noise ratio.
The F-14D’s T/R antennas also support other communications
equipment besides JTIDS in the VHF and UHF ranges.
The F-14D JTIDS The F-14D's JTIDS terminal is loaded from a Data Storage
terminal is loaded Unit (DSU). The DSU contains nonvolatile memory and can
from a DSU. hold one initialization load file. Like the terminal load file
for the E-2C, this file is created by TAMPS from the JNL
tape and parameters supplied in the OPTASK LINK mes-
sage.
*CH3_19-28 28 9/24/1, 7:34 PM

4
C
H
A
P
T
E
R
Messages and
Interfaces
Introduction
Several processors are involved in the successful exchange of information between
Link-16 tactical systems. This chapter explains the flow of data between these processors,
and summarizes the standards that govern its transfer. It’s okay to skip this chapter if
you’re not interested in the nitty-gritty details of how the tactical data gets from the
tactical system computers to the processor that actually transmits it on the network ... as
long as you realize that it takes several steps and requires several intermediary
computers.
4-1
ch4 LK16_2001 1 10/1/1, 9:12 AM

LGN 135-02-002
Section A
Overview
Between tactical systems, the exchange of information
over Link-16 is defined by the J-series message formats.
The interface between the TDS and the C2P, which is unique
to the shipboard configuration, is defined by the N-series
message formats. The interface between the host, either a
C2P or an airborne mission computer, and the JTIDS
terminal over the 1553B MUX bus to the JTIDS terminal is
defined by Terminal Input Messages (TIMs) and
Terminal Output Messages (TOMs). This data is received
by the Subscriber Interface Control Program (SICP)
executing within the Interface Unit (IU) component of
the terminal.
Within the terminal are several other processors, including

the Digital Data Processor (DDP) and the Plain Text
Processor (PTP). The transfer of information among these
processors within the terminal is accomplished through
shared Global Memory. Data exchanged between the SICP
executing in the IU and the Network Interface Control
Program (NICP) executing in the Digital Data Processor
(DDP) is defined by DataTransfer Blocks (DTBs).
Information is exchanged between the NICP and Plain Text
Processor by means of housekeeping words written in
Global Memory.
ch4 LK16_2001 2 10/1/1, 9:12 AM

J-series
messages
500-kHz TACAN Control JTIDS

NFA Class-2 C2P TDS
Tactical
Terminal
System
Host TACAN Port List of
Avionics (Airborne House- AIU
Only) keeping
UYK-43 Words HPA
Audio Voice
Port 1
N-series
messages Voice
Audio PTP
Port 2
1553B A Bus
1553B B Bus
MDTC Interrupt
C2P DTBs
(Shipboard SICP NICP R/T
Only)
DT Interrupt
Global
Memory
LK16/4-08M-005
UYK-43
TIMs DDP
IU
TOMs JTIDS Class-2

Terminal
Figure 4-1. The exchange of information between the components of the JTIDS system is
strictly defined for each interface.
ch4 LK16_2001 3 10/1/1, 9:12 AM

LGN 135-02-002
Section B
The N-Series Messages
The Model-4 C2P relies on input from the tactical systems
in the form of messages from Link-11 and messages from
Link-4A. The Model-4 C2P reformats the data in these
messages to create the Link-16 J-series messages. The
Model-4 capabilities and data resolution (accuracy)
are limited to the same capabilities and resolution supported
by existing Link-11 and Link-4A message formats.
The N-series The N-series messages exchanged between the Model-5

messages are TDS and the Model-5 C2P, on the other hand, contain
implemented in tactical data that has been normalized to be independent of
Model-5 Link-16. the particular link on which the data will ultimately be
transmitted, or on which it was received. Thus, the Model-5
configuration is the full and complete implementation
of Link-16.
4-4 Section B The N-Series Messages
ch4 LK16_2001 4 10/1/1, 9:12 AM

This complete implementation of Link-16 with the normal-

ized messages increases the granularity in track positions, air
track speeds, altitudes, and bearings. It achieves such
improvements as:
■ geographic reporting of positions anywhere in the

world
N-series
■ expanded electronic warfare (EW) parametric data messages allow
and a wider range of control more detailed
reporting on
■ reporting lines and areas of all sizes and descriptions Link-16.
■ more detailed reporting of friendly aircraft status,

including equipment status, exact ordnance inventory,
fuel available for transfer, radar and missile channels,
and ETA/ETD to/from station.
rol
er
ont
itt
Ai r Co n
ke C
Em
tro ce
l rfa
EW
Stri
Su
En
ga
ge Ref
ck
Tra
m
Air
en rence
EW F ge
g / Ra n
tS
re q tat ear in
u us B
e
ti c
en
y
us
c
Ac o
Po
t in
N-series
LK16/4-08M-006
messages
Figure 4-2. The N-series messages are exchanged between the

shipboard tactical system and the C2P. The tactical data contained
in these messages does not depend on the link over which the data
will be transmitted or over which it was received.
Section B The N-Series Messages 4-5
ch4 LK16_2001 5 10/1/1, 9:12 AM

LGN 135-02-002
Section C
The J-Series Messages
Like other tactical data links, Link-16 conveys its informa-
tion in specially formatted messages. These message for-
mats are composed of sets of fields, each of which is com-
posed, in turn, of prescribed numbers of bits that may be
encoded into predetermined patterns to convey specific
information. The messages exchanged over Link-16 between
participating TADIL J units are the J-series messages.
Each J-series message format is identified both by a label

and a sublabel. Its five-bit label defines 32 specific formats,
while its three-bit sublabel permits up to eight subcategories
Up to 256 different for each defined format. Together, these labels and sublabels
J-series messages comprise 256 possible message definitions. Within this
are possible. series there are messages similar to the M-series messages
for friendly status, surveillance, electronic warfare, and
weapons employment. There are also messages similar to
the V-series and R-series messages for air control.
4-6 Section C The J-Series Messages
ch4 LK16_2001 6 10/1/1, 9:12 AM

TADIL-J Message Catalog

Network Management J9.2 ECCM Coordination
J0.0 Initial Entry J10.2 Engagement Status
J0.1 Test J10.3 Handover
J0.2 Network Time Update J10.5 Controlling Unit Report
J0.3 Time Slot Assignment J10.6 Pairing
J0.4 Radio Relay Control Control
J0.5 Repromulgation Relay J12.0 Mission Assignment
J0.6 Communication Control J12.1 Vector
J0.7 Time Slot Reallocation J12.2 Precision Aircraft Direction
J1.0 Connectivity Interrogation J12.3 Flight Path
J1.1 Connectivity Status J12.4 Controlling Unit Change
J1.2 Route Establishment J12.5 Target/Track Correlation
J1.3 Acknowledgement J12.6 Target Sorting
J1.4 Communicant Status J12.7 Target Bearing
J1.5 Net Control Initialization Platform and System Status
J1.6 Needline Participation Group Assignment J13.0 Airfield Status Message
Precise Participant Location and Identification J13.2 Air Platform and System Status
J2.0 Indirect Interface Unit PPLI J13.3 Surface Platform and System Status
J2.1 Indirect Supporting Unit PPLI J13.4 Subsurface Platform and System Status
J2.2 Air PPLI J13.5 Land Platform and System Status
J2.3 Surface PPLI Electronic Warfare
J2.4 Subsurface PPLI J14.0 Parametric Information
J2.5 Land Point PPLI J14.2 Electronic Warfare Control/Coordination
J2.6 Land Track PPLI
Threat Warning
Surveillance J15.0 Threat Warning
J3.0 Reference Point J16.0 Imagery
J3.1 Emergency Point J17.0 Target Weather
J3.2 Air Track
J3.3 Surface Track
National Use
J28.0 U.S. National 1 (Army)
J3.4 Subsurface Track
J28.1 U.S. National 2 (Navy)
J3.5 Land Point or Track
J28.1.2 TBMD Training
J3.6 Space Track
J28.2 U.S. National 3 (Air Force)
J3.7 Electronic Warfare Product Information
J28.3 U.S. National 4 (Marine Corps)
Undersea Warfare J28.4 French National 1
J5.4 Acoustic Bearing and Range J28.5 French National 2
Intelligence J28.6 U.S. National 5 (NSA)
J6.0 Intelligence Information J28.7 U.K. National 1
Information Management J29.1 U.K. National 2
J7.0 Track Management J30.0 German National 1
J7.1 Data Update Request J30.1 German National 2
J7.2 Correlation J30.2 Italian National 1
J7.3 Pointer J30.3 Italian National 2
J7.4 Track Identifier J30.4 Italian National 3
J7.5 IFF/SIF Management J30.5 French National 3
J7.6 Filter Management J30.6 French National 4
J7.7 Association J30.7 French National 5
J8.0 Unit Designator Miscellaneous
J8.1 Mission Correlator Change J31.0 Over-the-air Rekeying Management
Weapons Coordination and Management J31.1 Over-the-air Rekeying
J9.0 Command J31.7 No Statement
J9.1 TMD Engagement Coordination
Figure 4-3. Using the J-series message formats, the U.S. Services exchange digital
information between tactical systems over Link-16 .
Section C The J-Series Messages 4-7
ch4 LK16_2001 7 10/1/1, 9:12 AM

LGN 135-02-002
In the shipboard systems, the C2P creates the J-series

messages from normalized data received from the tactical
system in N-series messages. In the airborne systems, there
is no C2P. The J-series messages are processed directly by
the mission computer. The C2P can also perform a second
function: the forwarding of data between Link-11 and
Link-16.
ol
ontr
r
itte
Ai r Co n
eC
Em
tro ce
l rfa
Strik
EW
k
Su Refe
rac
En
r
ga
dT
en
ge Ref
tus
Lan
ck
ce
Tra
C2P ta
me eren
Fli ent S
Air ng e
ol
gem
Poin
EW F a
nt
ring / R gh
ntr
re q ta tP
Cor ga
ea
S
tus r
Co
e
u cB ath
En
t
Air
ti
EW
l at
en
Tra
y
s
Convert N-series
u
ion
ce
c
Ac o
ck
Po
in
to J-series
t
N-series and J-series

messages vice versa messages
Forward data
between
Link-11 and
LK16/4-08M-007
Link-16 M-series
Figure 4-4. The C2P is a critical component of the shipboard Link-16 system. Not only does
it create the J-series messages from normalized data, it forwards data between Link-11 and
Link-16.
4-8 Section C The J-Series Messages
ch4 LK16_2001 8 10/1/1, 9:12 AM

Section D
Terminal Input Messages
Terminal Input Messages (TIMs) are sent from the host TIMs transfer
computer to the terminal’s Interface Unit (IU) over the data from the
MIL-STD-1553B multiplex (MUX) data bus. On airborne host (C2P or
platforms, the mission computer is the host. On shipboard mission
platforms, the C2P is the host. The host, acting as bus computer) to the
controller, issues command words to control the transfer of terminal.
data.
Thirty TIMs have been defined for transferring data from the
host to the SICP that executes in the IU. Besides data words,
which are issued by a tactical or mission computer, TIMs also
contain command words and status words. The command
words are issued by the bus controller, and the status words
are issued by the IU in response to command words.
The host can send TIMs to the IU at any time. The host
restricts its transfer of TIMs, however, so that no given TIM
type is updated more frequently than every 20 milliseconds.
Additionally, the host restricts its transfer of common
carrier messages, which are sent in TIMs 2 through 11, to
the rate of 10 per 50 milliseconds.
Section D Terminal Input Messages 4-9
ch4 LK16_2001 9 10/1/1, 9:12 AM

LGN 135-02-002
AAAAAAA
AAAAAAA
JTIDS Class-2 Terminal
AAAAAAA
AAAAAAA
1553B A Bus
1553B B Bus
AAAAAAA
MDTC Interrupt
AAAAAAA
HOST SICP
TIMs AAAAAAA
AAAAAAA
IU
AAAAAAA LK16/4-08M-008a
■ Initialization Data
■ Common Carrier Messages (J-series)
■ Target Sorting (J-series)
■ Air Platform and System Status (J-series)
■ Host Navigation Data
■ Requests for Data
■ External Time Reference
■ Clock Synchronization
Figure 4-5. The host sends information to the JTIDS terminal

Interface Unit (IU) using Terminal Input Messages (TIMs).
On airborne platforms the host is the mission computer.
On ships, it is the C2P.
4-10 Section D Terminal Input Messages
ch4 LK16_2001 10 10/1/1, 9:12 AM

TIM 1 conveys a block of initialization data to the SICP. Blocks

are numbered from 1 to 63; each block contains 32 16-bit words.
The first word is a checksum. The second word identifies the
block being transferred and its length. The remaining words of
the block (words 3 through 32) contain the terminal initialization
information.
TIMs 2 through 11 are the common carrier messages. Each TIMs 2 through
message generates a block of data that consists of 10 words 11 convey most
of header followed by 5 to 120 words of message body. of the J-series
The message body, containing the appropriate initial, message data
extension, and continuation words defined for the J-series to the SICP.
messages, spans as many of the ten 32-word TIMs as
necessary. By setting a Loopback ID number in the header, the
host may request that the terminal periodically report on the
status of a given message. This message status information
might indicate whether or not the message has been transmitted,
what state the receipt/compliance processing is in, and so on.
TIM 12 is not used by the U.S. Navy.
t
Hos
m:
Fro (C2P) ries
J-se
To: JTIDS Terminal
Attn: SICP
TIM
LK16/4-08M-009a
Figure 4-6. J-series messages for transmission are transferred from

the host to the terminal in Terminal Input Messages 2 through 11.
ch4 LK16_2001 11 10/1/1, 9:12 AM

LGN 135-02-002
TIMs 13 and 14 TIMs 13 and 14 offer an alternative method for conveying

offer an to the SICP for transmission sensor target data and an intent
alternative to engage a surveillance track. Each contains a loopback ID,
method for an indication of the age of the message, the host-defined
conveying sensor track ID, the message length (two to four TADIL-J words)
target data to the and Group (A or B), and a fully composed J-series message
SICP. without the TADIL-J header and parity bits. These TIMs are
an alternative to the common carrier messages, and one or
the other, but not both, should be used.
TIM 15 conveys the air platform and system status to the

SICP for transmission. It contains a loopback ID, priority
indication, and a fully composed J-series message without
the TADIL-J header and parity bits.
The host can TIM 16 can be used to request information from the SICP,
request including the current contents of any memory location. It is
information from also used to set time of day, to provide the host’s response to
the SICP, provide a message that requires operator acknowledgement, to
operator request advanced notification of specific time slots, and to
acknowledgements, specify a particular net number and network participation
and specify net group.
numbers and
NPGs.
TIM 17 transfers navigation data and geodetic position fixes
from the navigation systems of the host platform to the
SICP. Dead-reckoning data is provided at least once every
250 milliseconds. Geodetic fixes are provided as available.
4-12 Section D Terminal Input Messages
ch4 LK16_2001 12 10/1/1, 9:12 AM

TIM 18 transfers External Time Reference measurements

from the host to the SICP. This TIM is sent within one
second of the time mark whose time it defines.
TIMs 19 through 28 are not used.
TIM 29 controls the process of accessing the MUX port by

signaling that the host has completed its requests for output
messages for the current MUX cycle. The transfer of a
TIM 29 causes a MUX Data Transfer Complete Interrupt
(MDTCI) to be generated to the SICP.
TIM 30 transfers clock synchronization data from the host to

the SICP. It is used only when the time tags in the navigation
data are invalid.
ch4 LK16_2001 13 10/1/1, 9:12 AM

LGN 135-02-002
Section E
Terminal Output Messages
TOMs transfer Terminal Output Messages (TOMs) are used to transfer data
data from the from the terminal SICP to the host computer over the
terminal to the MIL-STD-1553B bus. Thirty TOMs have been defined.
host.
In addition to the J-series messages received from the JTIDS
network, TOMs contain terminal status information,
performance statistics, and confirmation of control setting
changes made by the operator. Data destined for an optional
tape recorder used during testing is transferred to the host in
TOMs 21 through 27. Also available are the transmission
and receipt/compliance status of up to 10 messages identified
by the host with a loopback number.
The SICP has 10 milliseconds to write its TOMs to the

buffer. The host can then take as much time as necessary to
read these TOMs from the buffer, signaling the SICP when it
is finished by writing a TIM 29.
4-14 Section E Terminal Output Messages
ch4 LK16_2001 14 10/1/1, 9:12 AM

AAAAAAAA
AAAAAAAA
JTIDS Class-2 Terminal
1553B A Bus AAAAAAAA

AAAAAAAA
AAAAAAAA
1553B B Bus
AAAAAAAA
MDTC Interrupt
HOST SICP
AAAAAAAA
AAAAAAAA
AAAAAAAA
IU
TOMs
AAAAAAAA
LK16/4-08M-008b
■ Status
■ Received Messages (J-series)
■ TACAN Data
■ Terminal Navigation Data
■ Loopback Data
■ Tape Recording Data
■ Host-Requested Data
Figure 4-7. The SICP, executing in the JTIDS terminal Interface

Unit (IU), transfers information to the host using Terminal Output
Messages (TOMs).
Section E Terminal Output Messages 4-15
ch4 LK16_2001 15 10/1/1, 9:12 AM

LGN 135-02-002
TOM 1 conveys the system status each MUX cycle. This

message includes the time at which the message was written,
a count in 16-bit words of the received messages assembled
during the last cycle, a count of the 16-bit words assembled
for tape recording (if applicable), initialization and
operational status, and confirmation of any control settings
changed by a TIM 16. In addition, TOM 1 contains the
loopback status on the transmission and the receipt/
compliance acknowledgements for the first three JTIDS
messages sent to the SICP for transmission with a loopback
ID assigned. The status on the fourth through tenth requests
is contained in TOM 29. Finally, TOM 1 reports the status of
the three NPG message-metering buffers, the status of the
two Target-Sorting buffers, the status of advanced slot
notification requests, the composite blanking status, the relay
inhibit status, the host NPG filter status, and the value of the
current time quality.
TOMs 2 through TOMs 2 through 20, along with TOM 1, are used to
20 convey transfer messages received from the network to the host.
network J-series Message filtering is performed by the terminal in accordance
messages to the with instructions supplied by TIM 1 at initialization.
host. Messages which satisfy the filter requirements will be
assembled into blocks that consist of five words of header
followed by five to 120 words of message data. The message
body, containing the appropriate initial, extension, and
continuation words defined for the J-series messages, spans
as many of the 32-word TOMs as necessary. The SICP will
duplicate the header as necessary to order the data in the
sequence: header/message, header/message, header/message,
and so on.
ch4 LK16_2001 16 10/1/1, 9:12 AM

The message data consists of the initial, extension, and

continuation words of the J-series messages. A count of the
total number of 16-bit words is supplied in TOM 1.
S
JTIDl
ries
m: a
Fro ermin
T
J-se
To: Host
(C2P or
Mission Computer)
TOM
LK16/4-08M-009b
Figure 4-8. J-series messages received from the network are

transferred from the terminal to the host in Terminal Output
Messages 2 through 20.
TOMs 21 through 27 support the tape recording function.

The SICP contains a 700-word buffer that can hold
recorded data. The content and format of this data is
specified by the host during initialization.
TOM 28 provides the information requested by the host

in TIM 16. This may include the contents of specific
memory locations, blocks of status information, or blocks
of initialization data.
Section E Terminal Output Messages 4-17
ch4 LK16_2001 17 10/1/1, 9:12 AM

LGN 135-02-002
TOM 29 provides the status of a net selection request

including the NPG on which the net change was requested
and the requested net number. It also provides the loopback
status (transmission and receipt/compliance) on the fourth
through tenth messages assigned a loopback ID (the status of
the first three messages requiring a loopback report is
contained in TOM 1). Finally, for airborne configurations,
TOM 29 provides Tactical Air Navigation (TACAN) data.
TACAN data includes range, bearing, TACAN mode and
channel, function status, range rate, bearing rate, and
built-in test results. Shipboard configurations do not
implement the terminal’s embedded TACAN function.
TOM 30 provides the terminal’s navigation data to the host

for use by the host’s navigation systems. It contains latitude,
longitude, altitude, and velocity in both geodetic and relative
coordinates. It also reports position quality, altitude and
azimuth qualities, and velocity quality.
ch4 LK16_2001 18 10/1/1, 9:12 AM

Section F
The Multiplex Cycle
The exchange of TIMs and TOMs takes place cyclically
during what is called the MUX (multiplex) cycle. TIMs may The MUX cycle
be sent to the SICP in the IU at any time during this cycle. prevents the C2P
But access to the TOM buffers is controlled to avoid and the JTIDS
collisions by the host and SICP. Which system has access is terminal from
governed by an interrupt, called the MUX Data Transfer writing to the
Complete Interrupt (MDTCI). For the 10 msec immedi- same place at the
ately following this interrupt, the SICP has authorization to same time.
update the TOM buffers. The TOM 1 buffer is updated every
time. All other TOM buffers are updated only when required.
Following this 10-msec interval, the host may read the data
for as long as necessary. When the host has finished reading
the buffers, it signals its completion by writing a TIM 29.
This causes another MDTCI interrupt to be generated, and
the next MUX cycle begins. The length of each cycle varies,
but must be at least 20 milliseconds.
Host writes TIMs at any time
(MDTCI) (MDTCI)
Host
SICP updates Host reads
writes
TOM buffer buffers
TIM 29 Elapsed
Time
0 msec 10 msec (Variable,
20 msec)
LK16/4-08M-011
Figure 4-9. Host-generated interrupts define the timing of the MUX cycle and control the
exchange of data and status information between the host and SICP.
Section F The Multiplex Cycle 4-19
ch4 LK16_2001 19 10/1/1, 9:12 AM

LGN 135-02-002
Section G
Data Transfer Blocks
J-series J-series messages contained in the TIMs passed from the
messages are host to the SICP must next be passed to the NICP program
transferred back executing in the Digital Data Processor (DDP). Global
and forth Memory within the DDP is used for this purpose and is
between the IU accessed by the SICP and the NICP using the Plain Text Bus
and the DDP in (PTB). Information is exchanged between these two
DTBs. programs in Data Transfer Blocks (DTBs).
DTBs sent from the SICP to the NICP may contain messages
for transmission, initialization data, status information or
navigational data. Those sent in the other direction, from the
NICP to the SICP, may contain received messages,
looped-back messages, navigational data, network
configuration information, or message status. In addition,
every 12 seconds the NICP generates a complete status
report, which includes the quality measurements as well as
tabulations of successful and unsuccessful transmissions,
receptions, loopbacks, and test messages.
4-20 Section G Data Transfer Blocks
ch4 LK16_2001 20 10/1/1, 9:12 AM

DTBs
SICP DTBs
NICP
Global
IU Memory DDP
P
s
ge
C
via st
SI
sa ion
Ho
a
at
s
n
ice
s
ta
e is
lD
io
Da
:
sM m
at
Vo
om
na
rm
ie ans
n
io
ed
tio
Fr
r
fo
at
tiz
se Tr
iza
In
vig
J- for
gi
al
us
Na
Di
iti
at
In
St
m ce
s
tu
ts
re n
en
ta
su ma
sS
ea or
ge
M erf
sa
P
es
M
NI ork
Ship to: NICP

CP
n
via etw
s
io
ed
e
ice
at
ed g
itt
iv ssa
ur
N
k C ta
Vo
es sm
fig
Da
e e
:
sa ran
ed
c
om
on
Re es M
l
tiz
na
es T
Fr
gi
SICP to NICP
M k
io
ri
or
c
Di
at
a
e
tw
-b
-s
vig
d
Ne
ed
ive
J
Na
op
ce
Lo
Re
10
-0
08M
4-
Ship to: SICP 16
/
LK
NICP to SICP
Figure 4-10. Data Transfer Blocks (DTBs) written to global memory are
used to exchange information between the SICP and the NICP. The J-series
messages are only a portion of the information that is exchanged.
Section G Data Transfer Blocks 4-21
ch4 LK16_2001 21 10/1/1, 9:13 AM

LGN 135-02-002
DTBs are passed from the NICP to the SICP using two sets of
pointers and buffers. The SICP and the NICP each have a set
of five pointers and five buffers. If the buffer is empty, the
pointer to that buffer is set to 0. If there is data, the pointer is
set to the beginning of the buffer. The NICP reads and writes
The NICP and its data immediately following the End-of-Slot interrupt, which
SICP take turns occurs at the end of each time slot: every 7.8125 milliseconds.
exchanging data After the NICP has filled the buffer(s) with DTBs for the SICP
during every time and has set the pointer(s), it generates a Data Transfer Interrupt
slot. (DTI) to the SICP. This interrupt is generated even when the
NICP has no data for the SICP. The SICP receives this
interrupt and reads the buffers. It then writes buffers contain-
ing DTBs for the NICP, using a second set of five pointers
and five buffers.
The End-of-Slot interrupt and the DTI each occur once during
every time slot. Together they control the orderly exchange of
information in both directions between the NICP and SICP.
By counting the DTIs, the SICP is able to maintain a slot
count.
End-of-Slot DTI End-of-Slot

Interrupt Interrupt
NICP reads NICP writes SICP reads SICP writes

buffers buffers buffers buffers
Elapsed
Time
0 msec 5.6 msec 7.8125 msec
LK16/4-08M-012
Figure 4-11. End-of-Slot Interrupts and Data Transfer Interrupts (DTIs) control the exchange
of data between the NICP and SICP.
ch4 LK16_2001 22 10/1/1, 9:13 AM

The Message-to-Transmit DTB ■

The SICP Message-to-Transmit DTB contains one or more
70-bit words of TADIL-J message data along with descriptive The Message-to-
information. This descriptive information specifies the type Transmit DTB
message structure (fixed format, variable format, or free conveys J-series
text) and indicates whether or not the message should be message data to
encoded. It also tells when the message should be the NICP for
transmitted, what its priority is, when it should be deleted transmission on
due to staleness, and whether any special action, such as the the network.
acknowledgement of receipt/compliance processing, is
required. Every message that is transmitted is also looped
back to the SICP with error statistics about its transmission.
The Received-Message DTB ■

The NICP Received-Message DTB contains the message The Received-
body, the block error and erasure counts determined by the Message DTB
error correction function, and descriptive information. This conveys J-series
descriptive information includes the time of arrival (TOA), message data
the antenna on which the message was received, the type of received from
message structure, whether or not the message was encoded, the network to
whether or not the message was relayed, and the track the SICP.
number of the unit sending the message.
ch4 LK16_2001 23 10/1/1, 9:13 AM

LGN 135-02-002
Status DTBs ■
Every 12 seconds, the NICP provides the SICP with a status
report that details the number of messages transmitted during
the last interval, the number of Round Trip Timing (RTT)
interrogations transmitted, the number of replies received,
the number of transmissions received in error, the number
of messages not acknowledged, counts on loopback failures,
the Interference Protection Feature (IPF) status, the crypto
status, the relay status, and built-in test (BIT) status for the
Receiver/Transmitter (R/T), Plain Text Processor (PTP), and
Crypto Text Processor (CTP).
The SICP provides a status report as well. The SICP status

DTB contains status on the host interface, telling whether it
is active or inactive, and provides a summary of the status of
each of the voice channels. Voice channel status includes the
net number, MSEC, coding, channel rate, packing, assigned
voice port, and channel activity.
ch4 LK16_2001 24 10/1/1, 9:13 AM

Navigation Data DTBs ■

The navigation function supports inertial, noninertial, and
TOA-only systems. Dead-reckoning navigation data is Dead-reckoning
provided by the SICP to the NICP. This includes latitude, data is conveyed
longitude, altitude, velocity in the local earth-referenced to the NICP.
coordinates (north, west, up), the direction of the north axis
with respect to true north, and changes in the components
of velocity since the previous data. Also provided are the
components of the lever arm from the Navigational System
to antenna A and antenna B.
One of the major functions performed by the JTIDS terminal

is navigation, and the NICP provides the SICP with extensive
navigational data. Several DTBs support this function. The JTIDS-corrected
NICP provides position and speed with respect to both the data is conveyed
relative grid and the earth’s surface. It also provides to the SICP.
information on heading corrections, tilt corrections, wander
angle, wind and water movement, the status of the relative
navigation Kalman filter, the position quality, the time
quality, and much, much more.
ch4 LK16_2001 25 10/1/1, 9:13 AM

LGN 135-02-002
Section H
Housekeeping Words
Housekeeping The Plain Text Processor (PTP) has access to Global
words provide Memory by means of the Plain Text Bus. During every
information time slot, the NICP provides the PTP with 35 housekeeping
necessary for words. These words contain decryption information for
encryption and slot n and encryption information for slot n+1, as well as
decryption of transmission control information, such as the message
messages. header, source track number (STN), which location of the
Secure Data Unit (SDU) encryption device to use for
message security (MSEC), which to use for transmission
security (TSEC), time adjustments for antenna cable delays,
and so on.
During every time slot, the PTP provides the NICP with 18
words reflecting input status, external time references, a
relay tag, the SDU serial number, a unique variable update
number, the R/T BIT status, the PTP BIT status, and so on.
Input status includes a message-received indicator, antenna
identification, and SDU status.
4-26 Section H Housekeeping Words
ch4 LK16_2001 26 10/1/1, 9:13 AM

Housekeeping List
Housekeeping List PTP to NICP
NICP to PTP
■ Variable for Slot n + 1 ■ Status
■ Variable for Slot n ■ External Time Reference
■ Time of Day for Slot n ■ Relay Tag
■ Time of Day for Slot n + 1 ■ SDU Serial Number
■ Message Header ■ Unique Variable Update Number
■ STN ■ Receiver / Transmitter Built-in Test
■ Message Transmit Control – Word 1
■ Slot Type n + 1 – Word 2
■ TOA Adjustment Antenna A – Word 3
■ TOA Adjustment Antenna B – Word 4
■ TOA Adjustment Sum ■ PTP Built-in Test
■ Receiver Thresholds – Word 1
■ Time Quality – Word 2
■ Track Number Addressee for RTT
■ Receiver / Transmitter Initialization
■ Receiver / Transmitter Control
■ Transmit Time
LK16/4-08M-015
■ Location of Receive Buffer
■ Location of Transmit Buffer
■ Time Correction
■ SDU Zeroing
Figure 4-12. Information is exchanged between the NICP and the PTP
through a list of housekeeping words in Global Memory.
Section H Housekeeping Words 4-27
ch4 LK16_2001 27 10/1/1, 9:13 AM

LGN 135-02-002
The exchange of information between the NICP and PTP, which is

strictly controlled, is based on an end-of-slot interrupt signal from
the DDP. The NICP reads the 18 words from the PTP and writes
the 35 housekeeping words for the PTP during every slot, within
5.6 msec of the interrupt. Between 5.6 and 7.8 msec after the
interrupt, the PTP reads the 35 words from the NICP and writes
the 18 words for the NICP. The location in Global Memory of the
data received in time slot n will be written to the buffer by the PTP
in time slot n+1, and retrieved by the NICP in time slot n+2.
DTI
End-of-Slot End-of-Slot
Interrupt Interrupt
SICP reads NICP writes PTP reads

NICP reads NICP writes
buffers buffers and writes
buffers buffers
buffers Elapsed
Time
0 msec 5.6 msec 7.8125 msec
LK16/4-08M-013
Figure 4-13. The PTP reads and writes data for the NICP in the period between 5.6 msec and
7.8 msec after the end-of-slot interrupt. The NICP retrieves this information when it reads
buffers during the next time slot.
4-28 Section H Housekeeping Words
ch4 LK16_2001 28 10/1/1, 9:13 AM

Section I
Voice Transmission/
Reception
Link-16 includes two secure voice channels, or ports. Both
port 1 and port 2 operate at 16 kilobits per second (kbps). In
addition, port 1 is capable of interfacing to an external voice
encoder (vocoder) that can operate at either 2.4 kbps or 4.8 Both Link-16
kbps. Thus the system is capable of supporting Reed- secure voice
Solomon-encoded voice. However, only non-error-corrected channels are
voice at 16 kbps is implemented aboard the Navy shipboard push-to-talk
platforms. The voice audio is digitized within the IU of the (PTT).
terminal. Control of each voice channel is provided by a
Push-to-Talk (PTT) protocol. Note that even though the
digitized voice is not encoded for error correction, it is still
encrypted, and is therefore secure.
"Black Lion 201 . . RTB . . your steer
for Home Plate is two, seven, " Fire Horse, this is Wee Willie . . .
zero . . fifty". your unrep time with Twinkle Toes
is fifteen thirty today. . . "
1 2 3 FO
4 5 6F
78 9I
ROCP
ASDS-
11M-018
4a
-01
8M
/4-0
II LK
16
Figure 4-14. The Link-16 network may include two secure voice ports operating without
error encoding at 16 kbps. Voice continues to operate when the terminal is set to Data
Silent.
Section I Voice Transmission / Reception 4-29
ch4 LK16_2001 29 10/1/1, 9:13 AM

LGN 135-02-002
When the Digitized voice data is transferred between the SICP and the
operator presses two digital voice ports through several buffers located in
the PTT button, Global Memory. The SICP supplies two transmit buffers and
two voice buffers two receive buffers for each voice port. The voice buffers
are alternately hold a maximum of 450 bits, as required for non-error-
filled with corrected digitized data. Upon a PTT command, the voice
digitized voice port obtains the transmit buffer address from Global
data. Memory and starts loading the buffer with digitized voice.
When the buffer is full, it sets a flag to notify the SICP and,
if the PTT signal is still present, begins loading the second
transmit buffer. The SICP unloads the data and transfers it in
a DTB to the NICP for transmission. After the second buffer
is full, the voice port signals the SICP and switches back to
the first.
Alternately switching back and forth between the two buffers
continues until the PTT is removed. Computer programmers
call this double-buffering. When the PTT is removed, the
voice port switches to reception processing.
During voice-
receive, digitized When the SICP receives a voice message from the NICP, it
data is converted stores the received digital data in the first voice receive
back to audio. buffer and sets a flag for the voice port. The voice port
retrieves the digitized data as it becomes available. The SICP
alternates between the first and second buffers either until
there is no more data, or until the PTT is issued locally.
Unencoded JTIDS
secure voice Practical experience indicates that JTIDS voice remains
degrades more understandable with up to 10 percent of the transmission in
quickly than error, compared to 50 percent in error for encoded data.
encoded JTIDS JTIDS voice will degrade into unusability, therefore, before
data. JTIDS data does.
4-30 Section I Voice Transmission / Reception
ch4 LK16_2001 30 10/1/1, 9:13 AM

Voice 1 Audio Input

Voice 1 Audio Output Voice
Push-to-Talk Port 1
Audio
Control Voice 2 Audio Input
Voice 2 Audio Output Voice
A
Push-to-Talk Port 2
AA AA
AAAA AA
AAA
SICP
DTBs To / From
NICP
Free Text JTIDS
Messages
Global Network
Memory
Port 1 Port 2
Optional 2.4 kbps 16 kbps
LK16/4-08M-074
External only
Vocoder 4.8 kbps
16 kbps
Not used in shipboard

configuration
Figure 4-15. Voice audio is digitized and is passed through Global Memory to the SICP for
output to the network as free text messages. Voice messages received on the network by the
NICP are passed to the SICP. The SICP transfers the digitized voice through Global Memory
to the voice port, where it is converted back to audio.
Section I Voice Transmission / Reception 4-31
ch4 LK16_2001 31 10/1/1, 9:13 AM

LGN 135-02-002
Section J
The TACAN Port Interface
The JTIDS
TACAN function Tactical Air Navigation (TACAN), which is used by the
replaces existing airborne platforms, is one of the functions supported by
airborne TACAN the JTIDS terminal. In the airborne platforms, the JTIDS
equipment. terminal replaces the ARN-118 TACAN. The TACAN port
of the terminal provides the interface between the host
avionics and the terminal R/T and DDP.
On airborne platforms, the TACAN function of the R/T

normally employs a 500-kHz serial channel clock.
Synchronized to this clock are serial input and output
channels. R/T mode and channel tuning information, as well
as zero-distance calibration information, are provided on the
input channel. Bearing, range, and range rate are provided
on the output channel. There is also an audio Morse Code
output signal providing the TACAN station identification.
If the normal channel clock is not connected, or if the
TACAN channel is set to 0, the TACAN port can use control
inputs from the Stand-Alone Control Panel (SACP).
The inputs from this control panel are written by the SICP
to the TACAN buffer in Global Memory.
4-32 Section J The TACAN Port Interface
ch4 LK16_2001 32 10/1/1, 9:13 AM

■ Channel
Input JTIDS Terminal R/T
■ Mode
TACAN Modes
■ Receive
■ Transmit / Receive
■ Distance Output
LK16/4-08M-075
■ Air-to-Air Receive
■ Bearing
■ Air-to-Air Interrogator / Transponder
■ Audio Identification
Figure 4-16. The R/T component of the JTIDS terminal provides

an independent Tactical Air Navigation (TACAN) function.
Information received from the R/T by the TACAN port is

written into Global Memory for the host avionics systems.
This information can include range, bearing mode and
channel, status, an odometer (distance) reading, range rate,
bearing rate, and a BIT summary. Control of the TACAN
function from the SICP, which is accomplished by operator
entries at the SACP, consists of the TACAN mode and
channel and Distance Measuring Equipment (DME)
calibration data. The DME calibration data includes delays
for antennas A and B, and identification of the information
the operator desires. TACAN continues to operate when the
terminal is set to Data Silent.
Section J The TACAN Port Interface 4-33
ch4 LK16_2001 33 10/1/1, 9:13 AM

5
C
H
A
P
T
E
R
Building the JTIDS

RF Signal
Introduction
This chapter describes the JTIDS communications architecture known as TDMA (time
slots, sets, and RRNs), the general data structures supported by the network architecture
(fixed format, free text, headers, Reed-Solomon encoding, and RTTs) and the
modulation techniques for encoding this data onto a carrier for transmission during the
time slots (CCSK, CPSM, pulses, and frequency hopping).
Section A TDMA and the JTIDS Network 5-1
**CH5A_1-21 1 10/1/1, 5:37 PM

LGN 135-02-002
Section A
TDMA and the JTIDS
Network
The JTIDS network employs a communications architecture
known as Time Division Multiple Access (TDMA). This
architecture uses time interlacing to provide multiple and
apparently simultaneous communications circuits. Each
circuit, and each participant on the circuit, are assigned
specific time periods during which to transmit and in which
to receive. This TDMA architecture forms the framework
of Link-16 communications.
5-2 Section A TDMA and the JTIDS Network
**CH5A_1-21 2 10/1/1, 5:37 PM

Epochs, Slots, and Sets ■
Every 24-hour day is divided by the JTIDS terminal into The time slot is
112.5 epochs. An epoch is 12.8 minutes in duration. An the basic unit of
epoch is further divided into 98,304 time slots, each of access to the
which is 7.8125 milliseconds (msec) in duration. JTIDS network.
The time slot is the basic unit of access to the JTIDS A JU is either
network. These units, the time slots, are assigned to each transmitting or
participating JTIDS Unit (JU) for particular functions. A receiving in each
JU is assigned either to transmit or to receive during each time slot.
time slot.
The time slots of an epoch, in turn, are grouped into three

sets, named set A, set B, and set C. Each contains 32,768
time slots numbered from zero to 32,767. This number is
called the slot index. (Three times 32,768 equals 98,304,
the total number of time slots in an epoch.) The time slots
belonging to set A, for example, are identified as A-0
through A-32767. By convention the time slots of an epoch
are named in an alternating pattern. The time slots of each
set are interlaced, or interleaved, with those of the other sets
in the following repetitive sequence:
A-0, B-0, C-0,

A-1, B-1, C-1,
A-2, B-2, C-2,
•
•
•
A-32767, B-32767, C-32767
This sequence, ending with slot C-32767, is repeated for

each epoch.
**CH5A_1-21 3 10/1/1, 5:37 PM

LGN 135-02-002
12
11 1
10 2
Each 24-hour day is divided into

9 3
12-minute 48-second intervals
called epochs.
8 4
7 5
6
Each day is divided into 112.5 epochs.
.........................
0 98,303
Each epoch is divided into
98,304 time slots. A-32766
B-32766
C-32766
A-32767
B-32767
C-32767
...........
B-0
C-0
A-1
B-1
C-1
A-2
B-2
C-2
A-3
B-3
C-3
A-4
B-4
C-4
A-0
Time slots are organized into

interleaved sets called A, B and C.
SECONDS
Each time slot is 7.8125
msec in duration.
WF16-08M-003
Figure 5-1. The JTIDS TDMA architecture divides a 24-hour day

into epochs, sets, and time slots.
**CH5A_1-21 4 10/1/1, 5:37 PM

Powers and Logarithms ■

Notice that the number of slots in each set of an epoch is a
power of 2. This is not a coincidence, but a consequence of
the binary nature of the computers that are used to generate
and process messages for Link-16.
n 2n
0 1
1 2
2 4
3 8
4 16
5 32
6 64
7 128
8 256
9 512
10 1024
11 2048
12 4096
13 8192
14 16384
15 32768
Figure 5-2. Powers of 2 are represented by 2 n. Powers of 2

relevant to JTIDS are those where n takes on values between
0 and 15.
**CH5A_1-21 5 10/1/1, 5:37 PM

LGN 135-02-002
The nth power of 2 is calculated by multiplying 2 by itself for

n times. By convention, 2 to the 0th power is defined to be 1.
The number 2 is called the base and number n is called the
exponent. The reverse operation, which converts the power
number back to an exponent, is called the logarithm to the
base 2. Thus, the logarithm (to the base 2) of 16384 is 14.
Recurrence Rate ■
The logarithm of the number of slots in the time slot block is
called the recurrence rate number (RRN). The recurrence
rate indicates how many time slots are in the block and, since
The RRN is used they are evenly distributed, how often they occur. The entire
to assign how set of time slots in set A is 32,768 or 215. It is distributed
often a JU every 3rd slot and is identified by the notation A-0-15. Half of
accesses the the slots in set A would be 16,384 time slots. They would
JTIDS network. occur every 6th slot and would be designated by an RRN of
14. Half of these would occur every 12th slot and would be
designated by an RRN of 13.
The relationship between RRN and the interval between slots

both in number of slots and in time is provided in Figure 5-3.
Note that as a consequence of the 3-set interleaved structure, 3
is the minimum spacing between slots in the same set. The
time between slots can be calculated by multiplying the
number of slots in the interval by 7.8125 msec.
**CH5A_1-21 6 10/1/1, 5:37 PM

RRN No. Slots Slot Interval

per Epoch (slots) (time)
15 32768 3 23.4375
14 16384 6 46.8750
13 8192 12 93.7500
msec
12 4096 24 187.5000
11 2048 48 375.0000
10 1024 96 750.0000
9 512 192 1.50
8 256 384 3.00
7 128 768 6.00 seconds
6 64 1536 12.00
5 32 3072 24.00
4 16 6144 48.00
3 8 12288 1.6
2 4 24576 3.3
minutes
1 2 49152 6.4
0 1 98304 12.8
Figure 5-3. The recurrence rate is the logarithm to the base 2 of

the number of slots in the block. Since the time slots are evenly
distributed, both the number of slots and the interval between them
can be determined from the recurrence rate number (RRN).
**CH5A_1-21 7 10/1/1, 5:37 PM

LGN 135-02-002
Frames ■
The 12.8-minute epoch is too unwieldy a time interval for
describing the rapid communications required by Link-16, so
a smaller, more manageable, time interval is defined. This is
Each epoch is divided the basic recurring unit of time in the JTIDS network and is
into 64 frames. called a frame. There are 64 frames per epoch. Each frame
is 12 seconds in duration and is composed of 1536 time
At 12 seconds each, slots: 512 belonging to set A, 512 belonging to set B, and
a frame is a more 512 belonging to set C. The time slots of a frame are
manageable unit of numbered from 0 to 511 and are interleaved in a repetitive
time than the epoch. cycle such that A-0, B-0, C-0 are followed by A-1, B-1,
C-1 — and are preceded by A-511, B-511, C-511. Frames
occur repeatedly, with one following another, for as long as
the link is operational. For this reason, a frame is often
illustrated by a ring in which slot A-0 follows slot C-511.
12 seconds
A-510 B-51 B-1 C-1 -004

0 C-510 A-511 A-1 -08M
B-511 C-511 A-0 B-0 C-0 6/5A
WF1
Figure 5-4. A frame consists of 1536 time slots grouped into

interleaved sets A, B, and C, with each set containing 512 time
slots numbered from 0 to 511.
**CH5A_1-21 8 10/1/1, 5:37 PM

RRN No. Slots Slot Interval

per Frame (within (within (time)
set) interleaved sets)
15 512 1 3 23.4375
14 256 2 6 46.8750
msec
13 128 4 12 93.7500
12 64 8 24 187.5000
11 32 16 48 375.0000
10 16 32 96 750.0000
9 8 64 192 1.50
seconds
8 4 128 384 3.00

7 2 256 768 6.00
6 1 512 1536 12.00
Figure 5-5. Since 64 frames comprise an epoch, the number of

slots per frame is found by dividing the number of slots per epoch
by 64. An RRN of 15 represents every slot in a set: 32,768 in the
epoch, 512 in the frame. Because the three sets are interleaved,
the interval between slots in any one set is actually 3, not 1.
**CH5A_1-21 9 10/1/1, 5:37 PM

LGN 135-02-002
Time Slot Blocks ■

Time slots are assigned to each terminal in the network as
A terminal's time blocks of slots. This block of slots, known as the time slot
slot usage is block (TSB), is defined by three variables: a set (A, B, or C),
specified by a starting number or index (0 to 32,767) and the recurrence
up to 64 TSB rate. Up to 64 TSBs may be assigned. RRNs of 6, 7 and 8,
assignments. which correspond to reporting intervals of 12 seconds,
6 seconds, and 3 seconds, are used most often in TSB
assignments.
A-20485
...
A-16389
... ...
A-24581
A-12293
WF16/5A-108M-006
...
AA AA
...
AA
AAAA AAAA
A A
A-28677
A-8197
AA
AAAA
AAAAA AAAA
AAAAA
... 1.6 min ...
A-4101
A-5
AAAA
AAAAAAAAAAAAAAA
...
A-5-3
set index RRN
Figure 5-6. Time slots are assigned in blocks by specifying a set,

index, and RRN.
For example, the TSB A-2-11 represents the block of time

slots belonging to set A that occur every 16th slot within the
set beginning with slot 2. (We obtain the value 16 for an
RRN of 11 from Figure 5-5.) These are the slots A-2, A-18,
A-34, A-50, A-66, ... A-498. In general, they are represented
by the expression (2+16n), where n = 0, 1, 2...31 for the
12-second frame. Similarly, TSB B-2-11 contains the slots
B-2, B-18, B-34, B-50, B-66, ..., B-498. Observe that
**CH5A_1-21 10 10/1/1, 5:37 PM

although TSB A-2-11 and TSB B-2-11 have identical

starting slot indices and RRNs, they nevertheless have no
slots in common. They are therefore said to be mutually
exclusive.
TSBs specifying different sets are mutually

exclusive.
The TSB A-7-11 represents the block of time slots belonging

to set A that occur every 16th slot beginning with slot 7.
These are the slots (7+16n), n = 0 through 31: A-7, A-23,
A-39, A-55, A-71, ..., A-503. Observe that TSB A-2-11 and
A-7-11 have no slots in common. These TSBs are also
mutually exclusive.
TSBs having the same RRN but different

indices are mutually exclusive.
Notice also that if the index of a time slot block is even, all
the time slot numbers in that block are also even. If the
index of a time slot block is odd, all the time slot numbers in
that block are also odd.
If one index is even and one index is odd, the TSBs

are mutually exclusive, regardless of their RRNs.
**CH5A_1-21 11 10/1/1, 5:37 PM

LGN 135-02-002
Now consider TSBs C-7-11 and C-7-10. From the RRNs it

is clear that C-7-10 contains half as many slots as C-7-11.
Since the slots are distributed evenly, C-7-10 consists of
every other slot of C-7-11. This is clearly shown by listing
the slots in each:
C-7-11 contains C-7, C-23, C-39, C-55, C-71, ...

C-7-10 contains C-7, C-39, C-71, C-103, C-135, ...
TSBs having the same set and index but

different RRNs are not mutually exclusive.
The one with the smaller RRN is a subset
of the one with the larger RRN.
Time slot blocks interrelate in a tree-like structure. For

example, TSB A-0-15 contains every time slot in set A:
A-0, A-1, A-2, A-3, and so on. If this block is divided in half
(RRN=14), the two subsets thus formed are denoted by
A-0-14 and A-1-14. TSB A-0-14 contains the time slots:
A-0, A-2, A-4, A-6, and so on. TSB A-1-14 contains A-1,
A-3, A-5, A-7 and so on. If these blocks are each divided in
half again, the RRN is 13. TSB A-0-14 contains blocks
A-0-13 and A-2-13. TSB A-1-14 contains blocks A-1-13
and A-3-13. Continue this process and you will see that the
TSB A-5-12 contains time slots that are also contained in the
TSBs A-1-13, A-1-14, and A-0-15.
**CH5A_1-21 12 10/1/1, 5:37 PM

12 second interval
RRN Slots/
Frame
Set C TSBs
15 512 C - 0 - 15
14 256 C - 0 - 14 C - 1 - 14
13 128 C - 0 - 13 C - 2 - 13 C - 1 - 13 C - 3 - 13
12 64 C - 0 - 12 C - 4 - 12 C - 2 - 12 C - 6 - 12 C - 1 - 12 C - 5 - 12 C - 3 - 12 C - 7 - 12
C-0-11 C-8-11 C-4-11 C-12-11 C-2-11 C-10-11 C-6-11 C-14-11 C-1-11 C-9-11 C-5-11 C-13-11 C-3-11 C-11-11 C-7-11 C-15-11
11 32
RRN Slots/
Frame
10 16 Set B TSBs
15 512 9 8 B - 0 - 15
14 256 8 4 B - 0 - 14 B - 1 - 14
13 128 7 B2
- 0 - 13 B - 2 - 13 B - 1 - 13 B - 3 - 13
12 64 6 B - 0 - 121 B - 4 - 12 B - 2 - 12 B - 6 - 12 B - 1 - 12 B - 5 - 12 B - 3 - 12 B - 7 - 12
B-0-11 B-8-11 B-4-11 B-12-11 B-2-11 B-10-11 B-6-11 B-14-11 B-1-11 B-9-11 B-5-11 B-13-11 B-3-11 B-11-11 B-7-11 B-15-11
11 32
RRN Slots/
10
Frame 16 Set A TSBs
15 5129 8 A - 0 - 15
14 2568 4 A - 0 - 14 A - 1 - 14
13 1287 2A - 0 - 13 A - 2 - 13 A - 1 - 13 A - 3 - 13
12 646 A - 0 -112 A - 4 - 12 A - 2 - 12 A - 6 - 12 A - 1 - 12 A - 5 - 12 A - 3 - 12 A - 7 - 12
A-0-11 A-8-11 A-4-11 A-12-11 A-2-11 A-10-11 A-6-11 A-14-11 A-1-11 A-9-11 A-5-11 A-13-11 A-3-11 A-11-11 A-7-11 A-15-11
11 32
10 16
9 8
8 4
WF16/5A-08M-005
7 2
6 1
Figure 5-7. Time slot blocks are interrelated in a tree-like structure. Simultaneous
transmissions can occur when TSB assignments intersect.
**CH5A_1-21 13 10/1/1, 5:38 PM

LGN 135-02-002
The interrelationship of TSBs is important to remember when

making assignments of time slots to participants. Suppose
TSB B-196-7 is assigned to one participant for his transmis-
sions and B-4-9 is assigned to another. If the TSBs are not
mutually exclusive, both participants would transmit simulta-
neously.
One way to determine whether the TSBs are mutually exclu-

sive is to list all the slots in each. The slots represented by an
RRN of 7 occur within a set at intervals of 256. Thus TSB B-
196-7 contains the slots numbered (196+256n):
B-196 and B-452. The slots represented by an RRN of 9
occur within a set at intervals of 64. Thus TSB B-4-9 contains
the slots numbered (4+64n): B-4, B-68, B-132, B-196, B-260,
B-324, B-388, and B-452. These TSBs are not mutually
exclusive; B-196-7 is a subset of B-4-9.
Another way to look at this is to consider the family of TSBs

to which a given slot belongs. For example, slot A-52 belongs
to the TSB A-52-6, which consists of the single slot. It also
belongs to A-52-7, A-52-8, A-52-9, A-20-10, A-4-11, A-4-12,
A-0-13, and so on. How do we know the index for each
successive RRN? The new index is the original index (52)
modulus 2(15-r), where r is the RRN. Thus, A-52 is a member
of the TSB with THE RRN 10, having THE index
( 52 mod(25) ) = 52 mod 32 = 20.
The network structure described thus far represents a single

net. This is the architecture of the network when the JTIDS
terminal is set to either communications Mode 1 with the
Normal IPF setting, or to Mode 2. In Mode 2, only the
frequency 969 MHz is used and all messages are assigned to
time slots in the single net.
**CH5A_1-21 14 10/1/1, 5:38 PM

Problem: To determine whether two TSBs within the same set defined by
starting slot indices of S0 and S1 with respective RRNs of r0 and r1
are mutually exclusive.
Solution: Step 1. Label the TSBs such that S0 is assigned to the larger index.
Step 2. Calculate S 0 – S1
215 – r 1
Conclusion: If the result is an integer, there's an intersection and the TSBs are
not mutually exclusive.
Example A: Are TSBs A-7-12 and A-3-13 mutually exclusive?

Step 1. Let S0 = 7 and S1 = 3. Then r0 = 12 and r1 = 13.
Step 2. Calculate 7–3 4 4

= = =1
2 15 – 13 22 4
Conclusion: An integer! They intersect, therefore they are not mutually
exclusive.
Example B: Are TSBs C-7-10 and C-2-13 mutually exclusive?

Yes. One index is odd, one is even. Tricked you!
Example C: Are TSBs B-5-9 and B-7-11 mutually exclusive?

Step 1. Let S0 = 7 and S1 = 5. Then r0 = 11 and r1 = 9.
Step 2. Calculate 7–5 2 2 1

= = =
2 15 – 9 26 64 32
Conclusion: Not an integer. These TSBs do not intersect. They are mutually
exclusive.
Figure 5-8. One method for determining whether two TSBs are mutually exclusive is to list
all the slots belonging to each. An alternative method is described above.
**CH5A_1-21 15 10/1/1, 5:38 PM

LGN 135-02-002
A group of participants exchanging messages among themselves is

a net. The time slot structure discussed thus far represents a single
JTIDS net.
Single Net
.
.
A- 32766
B- 32766
.
.
C- 32766
A- 32767
B- 32767
C- 32767
.
.
C- 1
.
.
B- 1
A- 1
.
C- 0
.
B- 0
A- 0
Time Slot
Figure 5-9. The JTIDS single net architecture divides each 12.8-minute
epoch into 98,304 time slots.
Multiple Nets ■
Link-16 Multiple nets can be constructed by “stacking” several single nets,
supports as illustrated in Figure 5-10. The time slots of these nets are
multiple, synchronized so that a time slot of one net coincides exactly with
simultaneous the corresponding time slot of every other net. Thus the multinet
nets. architecture contains 98,304 time “slices” per epoch.
This multinet architecture allows several groups of participants to

exchange messages independent of the other groups, during the
same time slot. The 7-bit net number allows a network of up to 128
nets to be constructed. One of these numbers, net number 127, is
Each net has a reserved to indicate a stacked net configuration. The remaining nets
unique pattern are numbered from 0 to 126. In a stacked net configuration, the
of frequency operator selects which net to use during operations. Each net is
hops. assigned a unique frequency-hopping pattern for its transmissions.
Although it is theoretically possible to define a network containing
127 nets, statistical studies have shown that operating about 20 nets
simultaneously in the same geographical area can cause some
degradation in communications.
**CH5A_1-21 16 10/1/1, 5:38 PM

Multiple Nets
Time Slice Time Slot
Net
Number
126
125
124
123
50
49
48
47
2
WF16/5A-08M-
0
.
.
A- 32766
B- 32766
.
.
C- 32766
A- 32767
B- 32767
C- 32767
.
.
C- 1
.
.
B- 1
A- 1
C- 0
.
.
B- 0
A- 0
Time Slot
Figure 5-10. The JTIDS multinet architecture stacks 127 of these single net
structures with their time slot boundaries aligned. This multi-net architecture
can be conceptualized by imagining a cylinder of 98,304 time slices.
**CH5A_1-21 17 10/1/1, 5:38 PM

LGN 135-02-002
Synchronization ■
In order to establish a synchronized network, a single
terminal must be designated to provide the time reference.
The JTIDS This terminal is called the Net Time Reference (NTR). The
terminal time maintained by this designated terminal defines the
automatically system time of the JTIDS network. As the reference, this
synchronizes to time defines the beginning and end of time slots and ensures
the system time the alignment of time slices in the multiple nets. Periodically
of the NTR. the NTR transmits a net entry message to assist other
terminals in synchronizing with the network and thereby
acquiring system time.
Synchronization, an automatic function of the JTIDS

terminal, is achieved in two steps. Coarse synchronization,
the first step, is achieved when a net entry message is
successfully received. Fine synchronization, the second
step, occurs when the terminal successfully exchanges
Round Trip Timing messages with the NTR. Thereafter,
each terminal maintains a measure of how accurately it
knows system time, called its Time Quality (Qt). It
continuously refines its knowledge of system time by
periodically transmitting Round Trip Timing messages and
by measuring the time of arrival (TOA) of all received
messages.
**CH5A_1-21 18 10/1/1, 5:38 PM

Components of the Time Slot ■

Recall that the basic unit of access to the Link-16 network is
the time slot. Each time slot is 7.8125 msec in duration.
Within every 12-second frame, 512 time slots are distributed
uniformly among sets A, B, and C. A platform is assigned
either to transmit or receive in each time slot. Each time slot
is, therefore, a transmission opportunity. Several components
comprise a time slot. From beginning to end, these
components are:
■ jitter
■ synchronization
■ time refinement
■ message header and data
■ propagation
Data is transmitted within the time slot as a series of

information-carrying pulse symbol packets. A pulse symbol
packet is a 13-microsecond (µsec) period during which the
carrier is modulated for 6.4 µsec. This is followed by
6.6 µsec of dead time.
The slot starts with a delay or dead time, called jitter, in Jitter contributes
which no pulses are transmitted. The amount of jitter varies to transmission
from time slot to time slot in a pseudorandom way that is security by
determined by the TSEC cryptovariable. Jitter contributes to causing the start
time of a
the antijam nature of the signal by making it difficult for a
transmission
jammer to know when to turn on the jamming signal. to vary.
**CH5A_1-21 19 10/1/1, 5:38 PM

LGN 135-02-002
Jitter is followed by two sets of predetermined pulse symbol

packets called synchronization and time refinement. These
patterns are used by the receiver to recognize and synchronize with
the signal. The message portion of the transmission is next. These
pulses carry header and data information.
Transmission of Pulse Symbol Packets
Propagation
Time Refine
Jitter
Sync
Message
(Header & Data)
7.8125 msec Time

Slot
126
Nets
WF16/5A-08M-008
Figure 5-11. The time slot contains the following components: jitter,
synchronization, time refinement, message header and data, and
propagation. During the synchronization, time refinement and message
header and data portions of the time slot, a sequence of symbols encoded
into information-carrying pulses is transmitted. The jitter and
propagation portions are dead times in which no pulses are transmitted.
**CH5A_1-21 20 10/1/1, 5:38 PM

Finally, the end of the slot is marked by a guard period which A guard period at
allows for the propagation of the signal. The propagation the end of the time
guard time allows for a normal range of 300 nautical miles slot provides time
or an extended range of up to 500 nautical miles, depending for the signal to
on the network's range setting. propagate.
In summary, the JTIDS TDMA architecture divides network

time into epochs, frames, and time slots. The time slot is the
basic unit of access to the network. With a duration of
7.8125 msec each, there are 128 time slots in every second.
A JU is assigned either to transmit or to receive in each time
slot. Pulses encoded with information are transmitted during
the time slot. Transmissions from multiple units during the
same time slot are permitted.
1 Day = 24 hours
= 112.5 Epochs
1 Epoch = 12.8 minutes
= 64 Frames
= 98,304 Time Slots
= 32,767 Time Slots/Set
1 Frame = 12 seconds
= 1,536 Time Slots
= 512 Time Slots/Set
128 Time Slots = 1 second
1 Time Slot = 7.8125 milliseconds
Figure 5-12. The JTIDS network employs a communications

architecture known as Time Division Multiple Access. Network time
is divided into epochs, frames, and time slots.
**CH5A_1-21 21 10/1/1, 5:38 PM

LGN 135-02-002
Section B
Link-16 Messages
Link-16 messages are exchanged during the TDMA time
slots of the JTIDS network. Each message consists of a
message header and message data. The message header is
not considered part of the message structure and is the same
for IJMS and JTIDS. The message header specifies the type
of data and identifies the source track number of the transmit-
ting terminal.
Four types of messages are defined:
■ fixed format
■ variable format
■ free text
■ round-trip timing
Fixed-format messages are used to exchange the J-Series

messages. Variable-format messages provide a general way
to exchange any type of user-defined messages. They are not
used by the U.S. Navy. Free-text messages are used for
digitized voice. Round-trip timing messages are used for
synchronization.
The data contained in these messages is always transmitted

as fixed-length, 3-word blocks of 225 bits each. These
3-word blocks may be packed into a time slot at different
densities: Standard (one 3-word block), Packed-2 (two
3-word blocks), and Packed-4 (four 3-word blocks).
5-22 Section B Link-16 Messages
*CH5B_22-37 22 10/1/1, 11:53 AM

Fixed-Format Messages ■
The fixed-format messages consist of one or more words, up
to a maximum of eight. Each word consists of 75 bits, of
which 70 are data, 4 are used for parity checks, and 1 is
reserved as a spare. Three types of words are defined: the
initial word, the extension word, and the continuation
word. Fixed-format messages consist of an initial word, one
or more extension words, and one or more continuation
words. If there are an insufficient number of 75-bit words to
fill a transmit block, the terminal pads the block with No
Statement (NS) words. Message metering in the host com-
puter helps to minimize the number of NS words inserted by
the terminal.
The fixed-format messages are used to exchange tactical and

command information over Link-16. These are the messages
commonly referred to as the J-series messages. The U.S.
Navy implementation of the J-series message standards is
defined in the Link-16 Operational Specification, OS 516.1.
Section B Link-16 Messages 5-23
*CH5B_22-37 23 10/1/1, 11:53 AM

LGN 135-02-002
Fixed Format Message Words
Initial Word
Word
Message
Parity Information Fields Sub-Label Label Format
Length
00
74 70 13 10 7 2 0
Extension Word
Word
Parity Information Fields Format
10
74 70 2 0
Continuation Word
Word
Parity Information Fields Continuation Format
Label
01
74 70 7 2 0
WF16/5B--08M-001
Figure 5-13. The JTIDS fixed-format messages may contain an initial

word, one or more extension words, and one or more continuation
words. Up to 8 words may be used to create a single J-Series message.
*CH5B_22-37 24 10/1/1, 11:54 AM

■ Parity Checking
Fixed format messages are always encoded for parity
checking. Bits 4 through 18 of the message header, which
contain the source track number, are used in conjunction
with the 210 data bits of the 3 data words to calculate a 12-
bit parity value. These parity bits are distributed at bit
positions 71-74 of each 75-bit word. Bit 70 of each word is
reserved as a spare.
■ Error Detection and Correction

Fixed format messages are also always encoded for error
detection and correction. The encoding scheme is an
algorithm known as Reed-Solomon (R-S) encoding.
Sixteen error detection and correction bits are added for
every 15 bits of data, so that 15 bits of actual data become 31
bits in the message. R-S encoding can detect and correct up
to 8 bits in error. The notation (31,15) is sometimes used to
describe this encoding algorithm. R-S encoding transforms
the 75-bit sequence, therefore, into a 155-bit sequence.
These bits are then taken in groups of five to create 31
symbols. Thus, R-S encoding transforms each 75-bit Link-
16 word into a
31-symbol R-S codeword.
*CH5B_22-37 25 10/1/1, 11:54 AM

■ Parity Checking
Fixed format messages are always encoded for parity
checking. Bits 4 through 18 of the message header, which
contain the source track number, are used in conjunction
with the 210 data bits of the 3 data words to calculate a 12-
bit parity value. These parity bits are distributed at bit
positions 71-74 of each 75-bit word. Bit 70 of each word is
reserved as a spare.
■ Error Detection and Correction

Fixed format messages are also always encoded for error
detection and correction. The encoding scheme is an
algorithm known as Reed-Solomon (R-S) encoding.
Sixteen error detection and correction bits are added for
every 15 bits of data, so that 15 bits of actual data become 31
bits in the message. R-S encoding can detect and correct up
to 8 bits in error. The notation (31,15) is sometimes used to
describe this encoding algorithm. R-S encoding transforms
the 75-bit sequence, therefore, into a 155-bit sequence.
These bits are then taken in groups of five to create 31
symbols. Thus, R-S encoding transforms each 75-bit Link-
16 word into a 31-symbol R-S codeword.
*CH5B_22-37 25 10/2/1, 3:59 PM

LGN 135-02-002
Variable-Format Messages ■
Like fixed-format messages, variable-format messages consist of
75-bit words. Variable format messages, however, may vary both
in content and length, and fields within the message can cross word
boundaries. Information within the message itself identifies the
fields and their length. The U.S. Army uses this format to exchange
ATDL messages between units — over the JTIDS network!
Variable Format TADI L J Word

Word
Parity Information Fields Format
00
74 70 2 0
WF16-/5B-08M-002a
Figure 5-14. Variable-format messages vary in content and length. These

messages are used to support the Army TADIL-B communication
requirements. They are not used by the U.S. Navy.
*CH5B_22-37 26 10/1/1, 11:54 AM

Free-Text Messages ■
Free-text messages are independent of any message standard.
They are unformatted and utilize all 75 bits in the data word —
all 225 data bits in the 3-word block.
Free Text Word
Digital Data
74 0
WF16-/5B-08M-002b
Figure 5-15. Free-text messages are independent of any message

standard. All bits in the word are used for data.
No parity processing is associated with free text messages. They

may or may not be Reed-Solomon encoded for error correction.
When R-S encoding is used, the 225 bits of data are mapped onto
465 bits for transmission. When R-S encoding is not used, all 465
bits are available for data. However, only 450 of these are used.
This allows a single assignment of slots to be compatible with
standard line rates (2400 bits per second (bps), 4800 bps, etc). The
free-text message format is used for Link-16 voice.
RRN Slots/Frame Slots/Sec Bits/Slot Bits/Sec
13 128 10-2/3 225 (R-S encoded) 2400

450 (unencoded) 4800
Figure 5-16. A single assignment of slots containing free text messages

can support standard serial line baud rates.
*CH5B_22-37 27 10/1/1, 11:54 AM

LGN 135-02-002
Message Packing ■
Message words may be taken in groups of 3 words, 6 words, or
12 words to form transmissions. If there are an insufficient number
of words to complete a group, the terminal fills in with a “no
statement” word. The processing of a group of 3 words is called
Standard (STD) format. The processing of a group of 6 words is
called Packed-2 (P2) format. The processing of 12 words is called
Packed-4 (P4) format.
Message Header ■
The message header specifies whether the message to follow is
fixed format, variable format, or free text. It identifies whether the
message is encoded or unencoded, and which packing structure has
been used. It also identifies the serial number of the Secure Data
Unit and the track number of the source terminal.
Header
P
SDU Serial Numb er Source Track Numb er Typ e
R
34 19 4 3 0
WF16/5B-08M-010b
Figure 5-17. The message header specifies the type of data and identifies
the source track number of the transmitting terminal. The bits of the
header are also used in the calculation of parity for each 3-word group.
P/R, the Type Modifier bit, provides packing or relay information.
The message header contains 35 bits. These are R-S encoded with
a (16, 7) algorithm such that the 35 bits become 80 bits. These are
taken five at a time to form an R-S header codeword containing
16 symbols.
*CH5B_22-37 28 10/1/1, 11:54 AM

Word 1 Word 2 Word 3 HDR 4 – 18

(70) (70) (70) (15)
Parity
■ 70 Bits → 75 Bits
Word 1 Word 2 Word 3 HDR 0 – 34

Word 1 (70) Word 1 (70) Word 1 (70) Word 1 (70)
(75) (75) (75) (35)
R-S Encoding
■ 15 Bits → 31 Bits
Encoded Encoded HDR

Word 1 Word
(70) Encoded Word
Word 1 (70) Encoded
Word 1 Word
(70) Word 1 (70)
(155) (155) (155) (80)
Conversion to
5-bit symbols
■ 5 Bits → 1 Symbol
WF16/5B-08M-015
R-S codeword R-S codeword R-S codeword R-S codeword

(31 symbols) (31 symbols) (31 symbols) (16 symbols)
Figure 5-18. Data undergoes several ordered operations in its

transformation from Link-16 words to JTIDS symbol packets: parity
checking, Reed-Solomon encoding, and conversion to 5-bit symbols.
Here the process is illustrated for the standard packing structure.
*CH5B_22-37 29 10/1/1, 11:54 AM

LGN 135-02-002
Symbol Interleaving ■
The packing structure is specified in the header, along with
the track number—which is required for parity checking.
Ah Ha! A jammer could interfere with the exchange of data
by jamming the header — if he could find it.
Interleaving the symbols of all codewords of the message

contributes to message security and to the antijam (AJ)
margin of the JTIDS signal. The number of symbols to be
interleaved depends on the number of codewords in the
packing structure. The three packing structures contain the
following numbers of symbols:
■ Standard (STD) format’s 3 codewords contain

93 symbols
■ Packed-2 (P2) format’s 6 codewords contain

186 symbols
■ Packed-4 (P4) format’s 12 codewords contain

372 symbols
For each packing format, the 16 symbols of the header

are interleaved with its data symbols in a predetermined
sequence.
*CH5B_22-37 30 10/1/1, 11:54 AM

R-S Codeword R-S Codeword R-S Codeword R-S Codeword

(31 symbols) (31 symbols) (31 symbols) (16 symbols)
Symbol
108 77 46 15 0
Number
Symbol
Interleaving
34
76
57
31
10
3
24
29
62
83 10
4 6 2
7 92 10 30 70 23
WF16/5B-08M-022
Figure 5-19. Symbols of message data and header data are interleaved.
*CH5B_22-37 31 10/1/1, 11:54 AM

LGN 135-02-002
Round-Trip Timing Messages ■

Recall that the network consists of time slices whose
alignment is established by one JTIDS unit, the NTR. In
order to receive and transmit on a JTIDS network, a terminal
must be synchronized with the net.
RTT messages Acquisition and maintenance of system time is called

are exchanged synchronization. A special set of messages are defined to
within a single support this function. These are the Round-Trip Timing
time slot. (RTT) Messages. They represent the only exception to the
rule that a terminal can transmit or receive, but not both, in a
given time slot. With the RTT messages, a terminal can
transmit an interrogation and receive a reply within a single
time slot.
The initial exchanges of RTT messages enable the terminal

to synchronize with the network. Subsequent exchanges
allow the terminal to refine its measurement of system time,
i.e., its Time Quality (Qt ). Each terminal reports its Qt over
the network. It also maintains an internal table of the
terminals that are within LOS which have the highest values
of this parameter. Entries in this internal table help the
terminal choose who to interrogate for the next RTT message.
*CH5B_22-37 32 10/1/1, 11:54 AM

RTT Interrogations (RTT-I) ■

The RTT interrogation may be either addressed (RTT-A) or RTT-As are
broadcast (RTT-B). The RTT-A consists of a header message transmitted on
addressed to the unit who reports the highest time quality. It is NPG 2.
transmitted in a dedicated time slot and only the terminal that
has been addressed will reply.
The RTT-B, on the other hand, contains the interrogator’s Qt . RTT-Bs are
It is not addressed to a specific recipient, and any terminal transmitted on
with a higher value can reply. It is typically used with a NPG 3.
stacked net structure. Terminals receive interrogations and
transmit replies on the net number equal to their own Qt .
They transmit interrogations on the net number equal to the
Qt of the desired recipient, as determined from their internal
table.
The RTT interrogation is very similar to the message header.

It contains 35 bits and is R-S encoded. But, it is not followed
by data and its symbols are not interleaved: they are transmit-
ted in consecutive order. Moreover, the transmission begins
at the beginning of the time slot. No delay or dead time
(jitter) is associated with the RTT messages.
*CH5B_22-37 33 10/1/1, 11:54 AM

LGN 135-02-002
RTT Interrogation
Type A (Addressed)
Type
SDU Serial Number Source Track Number 0 010
34 19 4 3 0
Type B (Broadcast)
Time Type
SDU Serial Number Spare 1 010
Quality
34 19 14 4 3 0
RTT Reply
Interrogator's SDU Serial Number Time of Arrival (12.5 nanosec)
34 19 0
WF16/5B-08M-010a
Figure 5-20. The Round-Trip Timing interrogation and reply messages

are part of a procedure to establish and maintain synchronization with
the net.
RTT Reply (RTT-R) ■

The reply to an RTT interrogation is transmitted 4.275 msec after
the beginning of the time slot, as measured by the receiving
terminal. The reply contains the time that the last symbol of the
interrogation was received. This time of arrival (TOA) is measured
at the antenna and is reported in units of 12.5 nanoseconds.
*CH5B_22-37 34 10/1/1, 11:54 AM

Propagation time can be determined from the

Time of Arrival of the Interrogation (TOA i )
RTT-I RTT-R
Replier: Received Transmit-
ted
start 4.275 end

msec
RTT-I RTT-R
Interrogator: Transmit- Received
ted
Propagation time can be determined from the

Time of Arrival of the Reply (TOA r )
WF16/5B-08M-012
Figure 5-21. The Round-Trip Timing reply message is transmitted during

the same time slot as the interrogation. No jitter is associated with either
message, and the reply is transmitted precisely 4.275 msec after the start
of the time slot.
*CH5B_22-37 35 10/1/1, 11:54 AM

LGN 135-02-002
The interrogating terminal uses the reported TOA along with

its own measurement of the TOA of the reply to calculate a
correction to its system clock. Suppose, for example, that
the error in the interrogating terminal’s system time is such
that its time slot boundary is late by an amount E. The size
of this clock error E can be calculated from three pieces of
information:
■ the TOA of the interrogation (TOAi ), as reported in the

reply
■ the TOA of the reply (TOAr ), as measured directly by

the interrogating terminal
■ the knowledge that the reply was transmitted exactly

4.275 msec into the time slot.
By exchanging RTT messages with a unit that has a more

accurate system time — that is, a higher Qt value — units
can improve the accuracy of their own system time.
*CH5B_22-37 36 10/1/1, 11:54 AM

TOA
TOAi Propagation time (t p) = TOAi – E
E tp
Replier: RTT-I RTT-R

(more accurate Received Transmit-
time) ted
start 4.275 end

msec
Interrogator: Clock RTT-I RTT-R

(with clock Error Transmit- Received
error) ted
tp
E TOA r
Propagation time (t p) + 4.275 = TOAr + E

In other words, (t p) = TOAr + E – 4.275
Assuming tp is the same for both the interrogation and reply,

the clock error E can be calculated:
Reply t p = Interrogation t p
TOAr + E – 4.275 = TOAi – E

WF16/5B-08M-011
E = TOAi – TOAr + 4.275

2
Figure 5-22. The exchange of RTT messages allows the interrogating unit to improve its
estimate of system time by calculating the error in its clock.
*CH5B_22-37 37 10/1/1, 11:54 AM

LGN 135-02-002
Section C
Inside the Time Slot
In order to communicate digital information over a radio, the
RF carrier must be modulated with the digital data. The
method used to encode digital data onto the JTIDS carrier
has two parts: Cyclic Code Shift Keying (CCSK) and
Continuous Phase Shift Modulation (CPSM).
CCSK and Chipping Sequences ■

Cyclic Code Shift Keying is applied to the 5-bit interleaved
symbols of the R-S codewords. Each 5-bit symbol is
represented by a 32-bit sequence. The bits of this sequence
are called chips to avoid confusion. The 32-chip sequences
are derived by shifting a starting sequence number left one
place each time. The starting chip sequence, designated S0,
is 01111100111010010000101011101100. Since the 5-bit
symbol can vary in value from 0 to 31, there are 32 unique
chipping sequences. These chipping sequences, also called
symbol packets, represent phases of a 32-bit direct-sequence
spreading code used to create the JTIDS spread spectrum
signal. They are numbered S0 through S31.
5-38 Section C Inside the Time Slot
*CH5C_38-51 38 10/1/1, 2:56 PM

DIRECTION OF SHIFT
5-Bit
32-Chip Sequence (CCSK Code Word)
Symbol
00000 S0 = 01111100111010010000101011101100
00001 S1 = 11111001110100100001010111011000
00010 S2 = 11110011101001000010101110110001
00011 S3 = 11100111010010000101011101100011
00100 S4 = 11001110100100001010111011000111
•
•
•
11111 S31 = 00111110011101001000010101110110
Figure 5-23. The CCSK chipping sequences are derived by shifting

S0 left by an amount equal to the 5-bit symbol it represents. A bit
shifted off the left end is inserted on the right end.
Detection consists of computing the cross-correlation be-

tween the received sequence and each of the valid sequences
in turn until a threshold is exceeded. The original 5-bit
symbol can be retrieved perfectly in the presence of several
chip errors in the 32-chip sequence.
Section C Inside the Time Slot 5-39
*CH5C_38-51 39 10/1/1, 2:56 PM

LGN 135-02-002
Pseudorandom Noise ■
To increase the transmission security of the JTIDS signal, the
32-chip sequence is exclusively or’d (XOR) with a 32-chip sequence
of pseudorandom noise (PN). The resulting chipping sequence is
often called a transmission symbol. This PN code is determined by
the TSEC cryptovariable and is continuously changing. As a result,
when the data is finally transmitted, it looks like incoherent noise.
Interleaved Reed-Solomon Encoded Data (465 bits) and Header (80 bits)
5-bit
Symbol • • •
Cyclic Code Shift Keying

(CCSK)
32-chip CCSK Symbol 32-chip Pseudorandom Noise
XOR
32-chip Transmission Symbol
WF16/5C-08M-018
Figure 5-24. The CCSK 32-chip code is masked by pseudorandom noise.
*CH5C_38-51 40 10/1/1, 2:56 PM

Carrier Modulation ■
The waveform is generated by Continuous Phase Shift
Modulation (CPSM) of the carrier frequency at a 5-megabit-
per-second rate using the 32-chip sequence of the trans-
mission symbol as the modulating signal. With a 5-MHz
chipping rate, the duration of each chip is 200 nanoseconds;
0.000000200 seconds.
Two frequencies are used in the modulation process. The

periods of these frequencies differ by half a wavelength
every 200 nanoseconds. Thus the transition from one
frequency to the other at the end of a 200-nanosecond period
is phase continuous.
These two frequencies are used to represent a change in chip

value rather than an absolute chip value. The nth chip is
transmitted at the lower frequency when it is the same as the
(n-1)th chip and at the higher frequency when it is different.
The frequency transmitted for the first chip is arbitrary since
noncoherent detection methods are used in the receiver. This
CPSM technique can also be described as phase-coherent
binary Frequency Shift Keying (FSK) modulation.
At the lower frequency there are an exact number of

complete cycles in the 200-nanosec period. At the higher A transmission
frequency, there is exactly an additional half cycle in the consists of multiple
200-nanosecond period. The time required to modulate the pulses, with one
chipping sequence
carrier with the entire 32-chip sequence is
per pulse.
200 x 32 = 6400 nanoseconds, or 6.4 microseconds (µsec).
*CH5C_38-51 41 10/1/1, 2:56 PM

LGN 135-02-002
32-chip Transmission Symbol
10........1.......110 0111......0......10
1 1 0 0 1 1
(same chip) (different chip) (same chip) (different chip)
Lower Frequency Upper Frequency Lower Frequency Upper Frequency

200 nanosec 200 nanosec 200 nanosec 200 nanosec
3
-01
8M
C-0
16/5
WF
Single Pulse
Figure 5-25. The carrier is encoded with the chipping sequence by shifting the
modulating signal between two frequencies The frequencies are chosen so that the
modulating signal is phase-continuous. If the chip is the same, the lower frequency is
used. If the chip is different, the upper frequency is used.
*CH5C_38-51 42 10/1/1, 2:56 PM

Pulses: Single and Double ■

The single pulse symbol packet consists of one 6.4-µsec pulse
of modulated carrier followed by a 6.6-µsec dead time for a
total pulse symbol packet duration of 13 µsec.
The double pulse symbol packet consists of two single pulses Each pulse of
both modulated with the same transmission symbol. The the double pulse
double pulse has a duration of 26 microseconds. Although the symbol packet
two pulses contain identical information, the carrier frequencies conveys the
for each are chosen independently. same information.
Single Pulse
6.4 6.6
13 µsec
Double Pulse
WF16/5C-08M-014
6.4 6.6 6.4 6.6
26 µsec
Figure 5-26. Either the single or the double pulse structure is

used to transmit JTIDS data. The double pulse structure provides
redundancy and increases the antijam capability of the link.
*CH5C_38-51 43 10/1/1, 2:56 PM

LGN 135-02-002
JTIDS uses 51 different carrier frequencies, hopping from one

to another for every 6.4-µsec pulse. This frequency-hopping
technique makes the JTIDS signal extremely difficult to
locate, giving it a low probability of intercept (LPI). It
also contributes to the reliability of the link. Data that is
transmitted as double pulses is not only output twice, but on
two different frequencies! This makes the signal doubly
difficult to jam, and far less likely to be subject to multipath
interference.
The synchronization ■ Synchronization Pulses

and time refinement
components of the The synchronization component of the time slot follows the
time slot are always jitter dead time and contains a fixed pattern of 16 double-pulse
transmitted symbols. The total time taken to transmit the synchronization
redundantly — in symbols is 416 µsec. These 32 pulses are transmitted on
the double-pulse 8 different carrier frequencies.
format.
■ Time Refinement Pulses

The time refinement component of the time slot contains four
double-pulse S0 symbols. The total time taken to transmit
the time refinement pulses is 104 µsec.
*CH5C_38-51 44 10/1/1, 2:56 PM

■ Header and Data Pulses

The header and data component of the time slot may be
packed in one of three ways: Standard (3 words), Packed-2 The data may be
(6 words), and Packed-4 (12 words). The Standard format is transmitted as single
always transmitted with the double pulse structure. The or double pulses,
Packed-2 format may be transmitted either with the single depending on the
pulse or the double pulse structure. The Packed-4 format is packing structure.
always transmitted with the single pulse structure. Thus,
there are four packing options for JTIDS data:
■ Standard Double Pulse (STD-DP)

■ Packed-2 Single Pulse (P2SP)
■ Packed-2 Double Pulse (P2DP)
■ Packed-4 Single Pulse (P4SP)
The header always uses the double pulse format, but the The header
packing structure of the data can vary for each time slot. component is
Part of the information specified in the header is the packing always transmitted
structure of the data. redundantly — as
double pulses.
*CH5C_38-51 45 10/1/1, 2:56 PM

LGN 135-02-002
Unencoded R-S Encoded

Wds: data + parity = total Total Type Wds: data + parity = total Total Type
bits data, Output (Modifier) bits data, Output (Modifier)
SP
RTT 2(0)
DP 0 0 0 0 0 2(1)
SP
STD
Fixed Format
DP 3: 210 + 15 = 225, 465 4(r)
SP 6: 420 + 30 = 450, 930 3(r)
P2
DP 6: 420 + 30 = 450, 930 5(r)
SP 12: 840 + 60 = 900, 1860 7(r)
P4
DP
SP
STD
DP N/A: 450 + 0 = 450, 450 0(0) 3: 210 + 15 = 225, 465 6(0)
*
Free Text
SP N/A: 900 + 0 = 900, 900* 0(1) 6: 420 + 30 = 450, 930 6(1)

P2
DP N/A: 900 + 0 = 900, 900 * 1(0) 6: 420 + 30 = 450, 930 2(0)
SP N/A: 1800 + 0 = 1800, 1800 * 1(1) 12: 840 + 60 = 900, 1860 2(1)
WF16/5C-08M-017
P4
DP
Only 450 of each available 465 bits are used so that a single assignment of (r) = relay indicator
*time slots is compatible with standard line rates of 2400 bps, 4800 bps, . . .
N/A = not applicable
Figure 5-27. Using the Type and Type Modifier fields, the header defines the
packing structure of the data that follows. This table summarizes the number
of words and data bits for fixed format and free text, unencoded and encoded
messages for each type of packing structure.
*CH5C_38-51 46 10/1/1, 2:56 PM

The following illustrations of the time slot structures are not to time
scale. The header and data are shown separately to illustrate clearly
the increased data capacity associated with each packing structure.
In actuality, of course, the header and data symbols are interleaved.
■ Standard Double Pulse
The STD-DP header and data portion of the time slot consists of 109 The redundancy
interleaved symbols. This represents 225 bits of coded information, of the STD-DP
or 465 bits of uncoded data. Recall that the header and data portion packing
of a Standard message consists of three 75-bit data words and one structure
makes it
35-bit header. These are Reed-Solomon encoded to 465 bits and
the most
80 bits, respectively. These bits are then taken five at a time to
reliable
generate 93 32-chip transmission symbols for the data and 16 32- type of
chip transmission symbols for the header. The data and header transmission.
symbols are interleaved. The total time taken to transmit 109
double pulse symbols is 2.834 msec.
Standard Double Pulse
Jitter S TR H D1 Propagation
16x2 4x2 16x2 93x2
S = Sync TR = Time Refinement H = Header D = Data WF16/5C-08M-016a
Figure 5-28. The STD-DP time slot structure contains a variable amount
of jitter, 3.354 msec of symbol packets representing synchronization, time
refinement, header, 225 bits of encoded Link-16 message data, and a
variable amount of propagation time. The header and data are actually
interleaved.
*CH5C_38-51 47 10/1/1, 2:56 PM

LGN 135-02-002
■ Packed-2 Single Pulse

The P2SP header and data portion of the time slot consists of
16 double-pulse header symbols and 186 single-pulse data
By sacrificing symbols. The header and data symbols, which are inter-
redundancy, the leaved, represent 35 bits of header data and 450 bits of
P2SP packing encoded Link-16 message data (or 930 bits of unencoded
structure can
free text data). The total time required to transmit the header
contain twice as
much data as the
and data portion of the timeslot in the P2SP structure is
STD-DP structure. 2.834 msec, the same as the time required for the STD
structure. Note that the P2SP is not as jam-resistant:
although the header information is still transmitted
redundantly, the doubling of the data capacity is achieved by
transmitting the data only once.
Packed-2 Single Pulse
Jitter S TR H D1 D2 Propagation
16x2 4x2 16x2 93x1 93x1
S = Sync TR = Time Refinement H = Header D = Data WF16/5C-08M-016b
Figure 5-29. The P2SP time slot structure contains a variable amount of
jitter, 3.354 msec of symbol packets representing synchronization, time
refinement, header and 450 bits of encoded Link-16 message data, and a
variable amount of propagation time. The header is transmitted
redundantly (double pulses), the data is transmitted only once
(single pulses).
*CH5C_38-51 48 10/1/1, 2:56 PM

■ Packed-2 Double Pulse

The P2DP header and data portion of the time slot consists
of 202 interleaved double-pulse symbols: 16 for the header
information and 186 for the 450 bits of the six encoded In the P2DP
packing structure
Link-16 words (or 930 bits of unencoded free text data).
data redundancy is
The total time required to transmit the header and data
restored, but jitter
portion of the time slot in the P2DP structure is 5.252 msec. is sacrificed.
The additional time required to transmit the data redun-
dantly is obtained by eliminating the jitter period at the
beginning of the time slot. A transmission in the P2DP
format begins immediately at the start of the time slot.
Packed-2 Double Pulse
S TR H D1 D2 Propagation
16x2 4x2 16x2 93x2 93x2
S = Sync TR = Time Refinement H = Header D = Data WF16/5C-08M-016c
Figure 5-30. The P2DP time slot structure contains no jitter. The 5.772
msec of symbol packets represent synchronization, time refinement,
header and 450 bits of encoded Link-16 message data. The remaining
time is reserved for propagation.
*CH5C_38-51 49 10/1/1, 2:56 PM

LGN 135-02-002
■ Packed-4 Single Pulse

The P4SP header and data portion of the time slot consists of
Both jitter and data 16 double-pulse header symbols and 372 single-pulse data
redundancy are symbols. The header and data symbols which are inter-
sacrificed so that the leaved, represent 35 bits of header data and 900 bits of
P4SP packing encoded Link-16 message data (or 1860 bits of uncoded free
structure can text data). The total time required to transmit the header and
contain four times as
data portion of the timeslot in the P4SP structure is 5.252
much data as the
STD-DP structure.
msec, the same as the time required for the P2DP structure.
Note that the P4SP structure is the least jam-resistant of all.
There is no jitter and the data is transmitted only once.
Packed-4 Single Pulse
S TR H D1 D2 D3 D4 Propagation
16x2 4x2 16x2 93x1 93x1 93x1 93x1
S = Sync TR = Time Refinement H = Header D = Data WF16/5C-08M-016d
Figure 5-31. The P4SP time slot structure contains no jitter. The 5.772
msec of symbol packets represent synchronization, time refinement,
header and 900 bits of encoded Link-16 message data.
Message Packing Limitations ■

The throughput, range, and antijam (AJ) ruggedness of Link-16
transmissions depends on the packing structure. Throughput is
determined by the density of message packing: 3, 6 or 12 data
words can be packed into a single time slot.
*CH5C_38-51 50 10/1/1, 2:56 PM

Range can be normal or extended. The normal range of 300

nm can be accommodated by all the packing structures, but the
extended range of 500 nm can only be used with STD-DP and Extended range
P2SP. In extended range mode, the jitter dead-time is short- cannot be used with
ened to allow a longer period for propagation of the signal. the P2DP and P4SP
Because the structure of the time slot depends on the range, all packing structures.
units participating in the network must have range set identi-
cally. Some AJ capability is lost with extended range.
The AJ ruggedness of the Link-16 transmissions depends on,

among other things, the variation in time slot start times (jitter)
and redundancy (double pulses). The amount of AJ margin Throughput
decreases as throughput increases, with P4SP providing the increases at the
greatest throughput with the least amount of AJ margin. The expense of AJ
terminal is designed to use the highest AJ margin, which is margin.
provided by the STD packing structure, wherever possible. As
the message load increases, however, it will automatically give
up AJ margin in favor of throughput.
The packing structure to be used is selected by the terminal in

the following order of preference: STD, P2SP, P2DP, and
P4SP. One of the terminal initialization parameters, the Upper
Packing Limit, places an upper limit on how far down this list
the terminal can go. In other words, the Upper Packing Limit
specifies how much AJ margin can be given up during any
particular time slot. The host can override this limit for specific
time slots, however, with a Terminal Input Message.
The U.S. Navy normally initializes its terminals with an Upper

Packing Limit of P2DP, thereby ensuring that some AJ margin
is always retained. The terminal automatically shifts back and
forth between Standard and Packed-2 as the data load increases
and decreases.
*CH5C_38-51 51 10/1/1, 2:56 PM

LGN 135-02-002
Section D
The JTIDS RF Signal
The JTIDS signal is transmitted in a radio frequency (RF)
band in the UHF portion of the spectrum. UHF communica-
tions are always line of sight. Line of sight is normally 150 nm
for ship-to-air and 300 nm for air-to-air. But it is only 25 nm
for ship-to-ship. To achieve Battle Group connectivity,
therefore, Link-16 requires the use of relays.
JTIDS Communication Modes ■

Three settings control the communication mode used by the
JTIDS terminal:
Mode 1, the ■ Mode 1 This is the normal JTIDS mode of

normal operation. It includes frequency-hopping
operational with full message security (MSEC) and
mode, allows full transmission security (TSEC) processing.
MSEC and TSEC
processing as ■ Mode 2 No frequency-hopping. All pulses are
well as transmitted on a single frequency.
multinetting. Peacetime constraints on slot usage are
eliminated.
■ Mode 4 No frequency-hopping. Some

communications security processing is
eliminated to allow the terminal to
function as a fairly conventional data link.
5-52 Section D The JTIDS RF Signal
CH5d_52-70 52 10/1/1, 4:27 PM

Mode 1 is the normal operational mode. Modes 2 and 4

represent a reduction in capacity and capability. Mode 3 is an
invalid mode. It is not implemented in the Class-2 terminal
and is not recognized by the NATO Standardization
Agreement (STANAG) on JTIDS. In fact, the Mode 4
described above is called “Mode 3” in the NATO STANAG.
The Lx Band ■
The portion of the frequency spectrum between 950 MHz
and 1150 MHz is called the L x Band. JTIDS operates within
this band. Also operating within this band are civilian and
military air navigation systems, including civil Distance
Measuring Equipment (DME) and military Tactical Air
Navigation (TACAN) equipment. DME and TACAN
channels occur every 1 MHz within this band.
Frequenc
AA AAAAAAAAAAAAAA A
300 KHz 3 MHz 30 MHz y 300 MHz 3 GHz 30 GHz
A
AA
A
MF A
A A
A A
A A
A A
A A
A A
A
HFA
A A
A A
A A
A A
A A
A A
A
VHF UHF SHF AA
WF16-/5D-08M-020
AA A A A A A A A A A A A A A A AA
L Band
AA AAAAAAAAAAAAAA
Lx
Military HF Military UHF JTIDS Search

2-30 MHz 225-400 MHz Frequency Band Radars
960-1215 MHz
Figure 5-32. The portion of the spectrum used for JTIDS communications is in the UHF band.
UHF communications are line of sight.
Section D The JTIDS RF Signal 5-53
CH5d_52-70 53 10/1/1, 4:27 PM

LGN 135-02-002
JTIDS Frequencies ■
JTIDS operates in JTIDS operates in the Lx band between 960 MHz and
the 960 to 1215 1215 MHz. The 51 frequencies assigned to JTIDS for
MHz band, with TDMA transmissions are those between 969 MHz and
JTIDS frequencies 1206 MHz, 3 MHz apart. Two sub-bands centered on
occurring every 1030 MHz and 1090 MHz are excluded because they are used
3 MHz between by IFF. In Mode 1, each pulse is transmitted on a different
969 MHz to frequency in a pseudorandom pattern that depends on the net
1206 MHz. number and the TSEC cryptovariable. In Mode 2, all pulses
are transmitted at 969 MHz.
CH5d_52-70 54 10/1/1, 4:27 PM

Frequency Frequency Frequency Frequency Frequency Frequency

Number (MHz) Number (MHz) Number (MHz)
0 969 17 1062 34 1158

1 972 18 1065 35 1161
2 975 19 1113 36 1164
3 978 20 1116 37 1167
4 981 21 1119 38 1170
5 984 22 1122 39 1173
6 987 23 1125 40 1176
7 990 24 1128 41 1179
8 993 25 1131 42 1182
9 996 26 1134 43 1185
10 999 27 1137 44 1188
11 1002 28 1140 45 1191
12 1005 29 1143 46 1194
13 1008 30 1146 47 1197
14 1053 31 1149 48 1200
15 1056 32 1152 49 1203
16 1059 33 1155 50 1206
Figure 5-33. For every pulse, the JTIDS carrier is changed to one
of 51 possible frequencies. The nominal frequency-hopping rate is
greater than 33,000 hops per second.
CH5d_52-70 55 10/1/1, 4:27 PM

LGN 135-02-002
DME ■
DME DME is a civilian navigation system consisting of an airborne
frequencies interrogator and ground transponder. The interrogator
occur every transmits about 30 pulse-pairs per second on one of
1 MHz between 126 channels between 1025 and 1150 MHz. The transponder
962 MHz and replies on one of 126 channels at 962 to 1024 and 1151 to
1213 MHz. 1213 MHz. An indicator in the aircraft’s cockpit displays the
transmit-to-receive time on a meter calibrated in nautical
miles. The DME ground transponder is often co-located with
a VHF Omnidirectional Range (VOR) transmitter to
provide an aircraft with both distance and direction. The
VOR operates on frequencies outside the JTIDS band,
between 108 and 118 MHz.
TACAN ■
TACAN is a military navigation system which combines the
distance and direction function into a single system. The
TACAN ground unit transmits a DME beacon (for distance)
Thousands of to which is added a rotating cardioid antenna pattern plus a
VORTAC 9-lobed pattern (for direction). The pattern rotates 15 times a
stations second generating a 15-Hz coarse-bearing signal. The
throughout the 9 lobes rotating 15 times a second generate a 135-Hertz
U.S. provide fine-bearing signal. Military aircraft translate the received
civilian and signal into a visual presentation of both azimuth and distance.
military aircraft
with distance In the U.S. and some other countries, the distance-and-
and directional direction navigation system is often implemented by
information co-locating VOR and TACAN stations to create a VORTAC
necessary for station. The VORTAC is a unified (civilian and military)
navigation. navigational aid. Both components operate simultaneously at
all times to provide three services at one site: VOR azimuth,
TACAN azimuth, and TACAN distance (equivalent to DME).
CH5d_52-70 56 10/1/1, 4:28 PM

115.3
MILES MIN KNOTS
96:00
DME 60
0 90
180
FROM
270
n
tio Hz nse MHz z
ga M ) spo
t e rro 1150 nels Re 1024 3 MH ) 33
In 5 – han – 121 els 0
2 c 96251 – hann
10 (126 11 126 c 30
(
3
27
6
SANTA BARBARA
24
114.9 CH 96 SBA
9
VOR TACAN / DME
Frequency Channel
21
12
18
15
JTIDS TDMA TACAN/DME
Frequency (MHz) 969 – 1206 962 – 1213
Channel Spacing (MHz) 3 1
Power Output 200 watts 500 watts

LK16/5D-08M-021
Figure 5-34. Link-16 shares the L x Band with civilian and military navigation systems.
CH5d_52-70 57 10/1/1, 4:28 PM

LGN 135-02-002
The airborne JTIDS terminals have an integrated TACAN

function, which provides TACAN interrogation and reply
processing. Aboard airborne platforms, this TACAN function
replaces the AN/ARN-18 TACAN equipment, and operates on the
lowest search and track rates. Blanking pulses prevent
simultaneous JTIDS TDMA and TACAN transmissions.
IFF ■
The Air Traffic Control Radar Beacon System (ATCRBS)/
Identification Friend or Foe (IFF) uses sub-bands centered on
1030 MHz and 1090 MHz. A ground-based interrogator at 1030
MHz transmits about 400 pulse-pairs per second. Replies from the
aircraft transponder are received at 1090 MHz, pulse-coded with
identity, altitude, and other information essential in identifying
the aircraft.
Mode S IFF ■
Mode Select Beacon System (Mode S) IFF is a combined beacon
radar and ground-air-ground data link system that replaces the
ATCRBS. It is backwards compatible with ATCRBS, using the
same frequencies for interrogation and reply.
Mode S also interrogates for surveillance and altitude, but in

addition, has a data link capability. Mode S has over 16 million
possible address codes, permitting a unique address for each
aircraft. It is being installed at nearly 150 airports across the
United States, and is intended to provide a reliable
communications capability as well as accurate surveillance in
dense traffic conditions. It is capable of selective interrogation,
single-scan interrogation, all-call interrogation, error detection and
correction, and mono-pulse beam splitting.
CH5d_52-70 58 10/1/1, 4:28 PM

A
Transponder
Code 2001
Hz
M
Hz
30
M
10
0
09
ns
)1
tio
..
ga
e.
ro
ter
ud
ltit
In
,A
(ID
es
pli
Re
Interrogator
Code 2001
LK16/5-08M-025
Figure 5-35. Notch filters on the JTIDS terminal transmitter prevent the JTIDS signal from
encroaching on the ATCRBS/IFF bands.
CH5d_52-70 59 10/1/1, 4:28 PM

LGN 135-02-002
IFF IFF
960
1030 1090 1215
960 970 980
WF16/5D-08M-019
TACAN/DME Channels JTIDS Frequency

(every 1 MHz) (every 3 MHz)
Figure 5-36. JTIDS, IFF, TACAN and DME transmissions use the same frequency band.
Within this band, TACAN and DME channels occur every 1 MHz. JTIDS center frequencies
occur every 3 MHz, with notches at 1030 MHz and 1090 MHz for IFF.
CH5d_52-70 60 10/1/1, 4:28 PM

Interference ■
The JTIDS terminal must continue to operate on Link-16 in The frequency
the presence of interfering signals from the IFF interrogator, band in which
the AIMS transponder, TACAN interrogators, and its own JTIDS must
built-in TACAN function, as well as interfering signals from operate is flooded
TACAN interrogators aboard adjacent platforms. An with low-level RF
airborne TACAN interference environment might consist of signals.
as many as 60 interrogators in search mode and 540
interrogators in track mode. These interfering signals are JTIDS
distributed uniformly in frequency over the entire TACAN transmissions
band and located such that the peak signal level from each is must not interfere
– 42 dBm. A ground beacon environment typically has a with the operation
beacon on every ground-to-air channel, each transmitting of the systems
3600 pulse-pairs per second. The power level associated relying on these
with 50 beacons is – 60 dBm. low-level signals.
CH5d_52-70 61 10/1/1, 4:28 PM

LGN 135-02-002
JTIDS Emissions Requirements ■

The terminal's To prevent the terminal’s RF transmissions from interfering
RF signal with normal operations of other systems, the pulse power
characteristics spectrum and the out-of-band emission characteristics are
are strictly strictly specified. The pulse power spectrum is unrestricted
specified. within 3 MHz of the center frequency, but it must be 10 dB
down at ± 3 MHz, 25 dB down at ± 6 MHz, and 60 dB down
beyond 15 MHz. The out-of-band emission characteristics,
including broadband noise, side band splatter, harmonics,
and other spurious emissions, must be kept below – 65 dBm
per KHz.
CH5d_52-70 62 10/1/1, 4:28 PM

Interference Protection Feature ■

Because JTIDS transmissions could potentially interfere To preclude
with national air navigation and flight safety, JTIDS termi- potential
nals are equipped with an Interference Protection Feature interference,
(IPF) to monitor all terminal transmissions. IPF monitors its each terminal
transmitter output for out-of-band transmissions, transmis- monitors its own
sions in the IFF notches, improper frequency-hopping transmissions.
distribution, incorrect pulse lengths, high R/T thermal level,
HPA operation, and time-slot duty factor. If authorized
levels are exceeded, the IPF function will automatically
disable the terminal’s transmissions.
The terminal implements two sets of protection features. The

first feature imposes peacetime constraints on the terminal’s
operation in Mode 1. (These limitations are automatically
overridden in the less capable modes, Modes 2 and 4.) The
second feature automatically monitors the terminal transmis-
sions to ensure that it does not interfere with navigation
systems.
The operator controls the IPF setting through three IPF

settings:
■ Normal
■ Exercise Override
■ Combat Override
CH5d_52-70 63 10/2/1, 4:01 PM

LGN 135-02-002
■ Normal
Setting IPF to normal in Mode 1 is generally required

within 12 nm of land, and enforces the peacetime constraints
on the terminal’s transmissions. TDMA is authorized, but
the capability and capacity of the network is reduced to
prevent interference with civilian and military navigation
systems, which are particularly susceptible to total pulse
density and frequency power levels. Peacetime constraints
address these susceptibilities.
When the normal IPF setting is in effect, the transmission

packing structure is limited to Standard or Packed-2 Single
Pulse. High power output is forbidden. Multinetting is not
allowed. Contention access, in which simultaneous trans-
missions may occur, also is not allowed. Time-slot usage is
minimized to a system level of 40% capacity and a terminal
level of 20% capacity. These limitations apply to all time
slots: free text (voice) messages, fixed format messages, and
relays. The permitted time slot blocks are A-0-14, B-1-14,
C-0-12, and C-4-11. This restriction on time slot usage,
which limits the number of pulses per unit time, is referred
to as a time slot duty factor (TSDF) of 40/20.
The terminal monitors its performance for compliance with

these restrictions. It also measures pulse width, monitors the
distribution of the pulses to ensure a uniform distribution
across the spectrum, and watches for transmissions at
unauthorized carrier frequencies. Any infraction of these
constraints will cause the terminal to disable all transmissions.
CH5d_52-70 64 10/1/1, 4:28 PM

IPF Description Comments

All monitoring functions Used in port and during
Normal in operation (peacetime coastal transit
constraints)
Overrides peacetime Allows higher time-slot

Exercise constraints duty factor and high
Override power output
Overrides all Battle short. Use only

Combat interference protections after a known IPF
Override failure when continued
operation is required
LK16/5-08M-025b
Figure 5-37. When IPF is set to NORMAL in Mode 1, peacetime

constraints are imposed on a terminal’s JTIDS transmissions.
CH5d_52-70 65 10/1/1, 4:28 PM

LGN 135-02-002
■ Exercise Override
The exercise override setting provides partial interference

protection. The peacetime constraints are overridden to allow
contention access, multinetting, a time slot duty factor of
100/50, and high power output. Shipboard and E-2C
terminals have a High Power Amplifier (HPA) that can boost
outgoing transmissions to 1000 watts. Since normal 300 nm
connectivity is provided with low power (200 watts), the
HPA high power is provided for “burn-through” against
jamming. In this setting, the terminal continues to monitor
the signal characteristics of the terminal transmissions
including pulse spread, invalid frequencies, and nonuniform
frequency distribution.
The authorization required for Exercise Override is provided

by the Battle Group Commander, often as part of a military
message called the Operational Tasking Data Links, or
OPTASK LINK. This message provides detailed instructions
for establishing and operating tactical data links.
■ Combat Override
With IPF set to Combat Override, all protection features are

overridden. This override must be authorized by the Battle
Group Commander. It should be used only when continued
operation is imperative — in spite of a known IPF failure,
and realizing that navigation systems will probably be
jammed.
CH5d_52-70 66 10/1/1, 4:28 PM

Peacetime Constraints for Mode 1
■ Type 2A RTT only

■ STD or P2SP packing structures
■ Transmitter power of 200 watts
■ Dedicated time slot access (no contention)
■ Limit usage to TSDF of 40/20
■ Single net (net 0), no multinetting
■ Uniform frequency-hopping distribution
LK16/5-08M-025a
Figure 5-38. Because the JTIDS waveform can potentially

interfere with national air navigation and flight safety, employing
the Exercise and Combat IPF overrides requires the Battle Group
Commander’s authorization.
CH5d_52-70 67 10/1/1, 4:28 PM

LGN 135-02-002
TSDF ■
Time slot duty factor (TSDF) is a measure of JTIDS pulse
density. A TSDF of 100% is defined as 396,288 pulses per
12-second frame. This density is realized when a transmission
A TSDF of 100% with Standard or Packed-2 Single Pulse packing (containing
is 396,288 pulses 258 pulses) occurs in every one of the 1,536 time slots of the
per 12-second frame (258 x 1536 = 396,288). It would also be closely
frame. approximated by 892 time slots at Packed-2 Double Pulse or
Packed-4, each of which contains 444 pulses (444 x 892 =
396,048).
TSDF is normally expressed as two or three numbers separated

by slashes. The first number is the percentage assigned to all
participants by the network design. The middle number, if
present, is the percentage that may be used by the relay. The
last number is the percentage that may be used by any one
platform. Thus, a network TSDF authorization may be
expressed as 40/20 or 100/50/20.
If only Standard and Packed-2 Single Pulse packing structures

are employed, these percentages are also equal to the
percentage of 1,536 time slots used. Thus, a network with a
TSDF of 40/20 allocates not more than 40% of the pulses to all
JUs, and not more than 20% of the pulses to any individual JU.
A network with a TSDF of 100/50/20 allocates 396,288 pulses
in the frame to participants, but the relay will transmit not
more than 50% of them, and any individual unit will transmit
not more than 20% of them.
Note that TSDFs greater than 100% are possible. A network

that has all time slots assigned with an upper packing limit of
Packed-2 Single Pulse except for 224 time slots assigned to
voice, which is relayed, will have a total TSDF of 121%
(1088 slots @ 258 pulses + 448 slots @ 444 pulses).
CH5d_52-70 68 10/2/1, 4:48 PM

FAA Restrictions ■
JTIDS operates within the frequency band allocated for
aeronautical radio navigation and controlled by the FAA.
Thus, coordination with and approval by the FAA is required
for JTIDS operations within 200 nm of the U.S., its
territories and possessions. NAVEMSCEN coordinates
frequency assignments and is the DOD point of contact for
JTIDS spectrum management issues. Geographic
deconfliction within a given area is further coordinated
through the Geographic Area Assignment Controller
(GAAC). A JTIDS/MIDS Deconfliction Server is
maintained to support this coordination among the services.
The following restrictions are typical:
■ TSDF: 100/50/20 within a 200 nm circle around

each terminal; coordination and deconfliction
through the GAAC; E-2C relay operates above
18,000 ft and is at least 3 nm from other aircraft
■ Contention Access: Limited to RTT, Initial Entry,
HUR PPLI, and Fighter-to-Fighter
■ Power Output: Low
■ TACAN/DME beacons: No operations within
.5 nm; TSDF limited to 50% within 7 nm
■ ATCRBS IFF sites: No surface operations within
900 ft
■ Mode S Sensors: No operations by E-2Cs and
ship/shore units employing notch filters within
5 nm; fighter aircraft which have no notch filter
assemblies are restricted within 30 nm
■ Operational DME/P beacons: No operations
within radio LOS (however, none are currently
in operation)
CH5d_52-70 69 10/1/1, 4:28 PM

LGN 135-02-002
Waivers are approved by the FAA on a case-by-case basis.

These restrictions may be relaxed as more information about
the potential for JTIDS interference with navigation aids
becomes available. Current restrictions may be found at the
Navy web site http://link16.spawar.navy.mil.
Coordinate with the GAAC before

transmitting on JTIDS.
CH5d_52-70 70 10/1/1, 4:28 PM

6
C
H
A
P
T
E
R
Structuring the
Link-16 Network
Introduction
The previous chapter focuses on the physical structure of the JTIDS network. The focus
of this chapter is on its logical structure. The logical structure is mission-oriented and
based on fleet requirements. Many different logical structures are possible. They are
currently designed by the Naval Research and Development Division (NRaD) of the
Naval Command Control and Ocean Surveillance Center (NCCOSC) located in
Warminster, Pennsylvania, and are collected into a library stored on magnetic tapes.
Networks are operationally oriented, and are designed to meet fleet requirements. Even
though the operator has almost no control over defining the network structure, an
understanding of how it is designed and how it works is helpful in recognizing problems
and diagnosing their probable cause. Knowledge of the logical structure of the network
also enables an operator to distinguish between the limitations that are inherent in the
JTIDS waveform and those that are part of the design of a particular network.
6-1
*CH_6_2001 1 10/2/1, 5:30 PM

LGN 135-02-002
Section A
Participation Groups
Superimposed on the physical structure of the JTIDS network
is a logical structure that allows it to be adapted to specific
operational environments or needs. This adaptation is
accomplished by apportioning the network capacity among
multiple “virtual circuits” whose transmissions are dedicated
to a single function. Participants are then assigned to these
circuits, or functional groups, as required by their mission
and their capabilities.
In addition to friendly force identification and position

reporting, functional groups can include:
■ battle group surveillance,

■ fighter-to-fighter target sorting,
■ air control,
■ electronic warfare reporting and coordination,
■ battle group mission management and weapons
control, and
■ two secure voice channels.
Participation There are also functional groups which support the operation
Groups are the of the network, including Initial Entry and RTT. All of these
functional functional groups are known as Network Participation
building blocks of Groups, or NPGs. The transmissions on each NPG consist
a network. of messages which support its particular function.
6-2 Section A Participation Groups
*CH_6_2001 2 10/2/1, 5:30 PM

This functional structuring allows JTIDS Units (JUs) to participate on only

the NPGs necessary for the functions they perform. In the U.S. Navy, it is
likely that all Command and Control (C2) JUs (ships and the E-2C) will
operate on all applicable NPGs at all times. A maximum of 512
participation groups is possible. Of these, 30 have been allocated for
subject-oriented functions, 22 are currently defined, and 16 are applicable
to the U.S. Navy C2 JUs. NPGs 30 and 31 are specifically dedicated to
IJMS messages.
The NPGs 32 through 511 are assigned for the Needline participation
groups. Needline participation groups are address-oriented and require
that a destination address be specified. They are used strictly for intra-
Army communications. The data exchanged in the needline groups
consists of ATDL-1 messages embedded in the variable-format message
structure supported by JTIDS. Because the USN does not employ these
groups, they are not discussed further in this guidebook. All further
references to NPG will refer to the subject-oriented Network Participation
Groups.
Participation
Group Contents Used By
0 – 29 J-series messages USN, USAF, USMC, US Army,

NATO
30 – 31 IJMS Messages USAF, NATO E-3
32 – 511 ATDL-1 messages embedded US Army

in JTIDS variable format
messages
LK16/6-08M-026
Figure 6-1. The JTIDS Class-2 terminal can be initialized to participate in up to

32 network participation groups, or NPGs, drawn from 512 possible selections.
Section A Participation Groups 6-3
*CH_6_2001 3 10/2/1, 5:30 PM

LGN 135-02-002
The Class-2 terminal permits the assignment of 64 time slot

blocks to as many as 32 participation groups drawn from 512
possible selections. The chosen NPGs have an “external”
number, which is the number (between 1 and 511) assigned,
and an “internal” number, sequenced from 1 to 32. Each
NPG is associated with a particular set of J-series messages.
For example, the J3 set of messages is transmitted on NPG 7.
NPGs ■
Network capacity NPGs support operational communications needs. They allow
is assigned first to the network designer to separate the functions implemented in
NPGs, and then the J-series messages. Network capacity is first allocated to
to users NPGs, and then to the users that participate in that NPG. The
participating in following paragraphs briefly describe each NPG that is
that NPG. currently defined. NPGs can be divided into two basic
categories: those used for the exchange of tactical data,
including voice, and those required for network maintenance
and overhead.
In general, networks are designed to support particular

operational goals. The NPGs described here may or may not
be included in a given network, depending on the objectives
and functional requirements that the network was designed
to meet.
*CH_6_2001 4 10/2/1, 5:30 PM

■ NPG 1: Initial Entry
This NPG supports coarse synchronization and entry onto

the network. The JU assigned as Net Time Reference
periodically transmits net entry messages in this NPG to be
used by other terminals in acquiring system time. Net entry Initial Entry
messages are also transmitted by any JU defined to be an messages are
Initial Entry JU (IEJU), also called a Net Entry Control transmitted by the
Terminal (NECT), and by all active relays. The Class-2 NTR, IEJUs and
terminal transmits the TADIL-J Initial Entry message as the all active relays.
net entry message in the A-0-6 slots on Net 0, unless an
alternate net entry slot is designated. This is the first time
slot of every frame, and preempts any other assignment that
might have been made during initialization. Because this
NPG supports coarse synchronization and entry onto the
network, it is required for all networks. Every JU participates
in this NPG.
■ NPG 2: RTT A (Dedicated)
RTT messages are automatically exchanged between JTIDS Round-trip timing

terminals on this NPG to support fine synchronization. This messages allow
NPG also supports network entry and facilitates relative new units to
navigation computations. The time slots in this group are synchronize
dedicated for use by specifically identified JUs and the RTTs quickly with the
they exchange are addressed RTTs. When this NPG is not network.
included in the network, the RTT messages preempt
occasional time slots in NPG 5 or 6. During synchronization,
Class-2 terminals transmit up to three RTT messages within
12 seconds. After fine synchronization is achieved, Class-2
terminals exchange RTT messages about once per minute.
*CH_6_2001 5 10/2/1, 5:30 PM

LGN 135-02-002
■ NPG 3: RTT B (Contention)
This NPG performs the same function as NPG 2, but the time
slots are shared by a group of JUs using an access method in
which all units can transmit. It is usually configured as a stacked
net, with the net numbers corresponding to values of the Time
Quality parameter — 0 through 15.
■ NPG 4: Network Management
This NPG permits the redistribution of network capacity

through commands issued over the network. Navy units
exercise a limited amount, if any, of net management.
However, all JTIDS terminals are capable of receiving and
processing network management messages. A C2 unit could
change the time slot assignments for an Air Force F-15’s
replies with an over-the-air net management message, for
example, to allow it to interoperate on the Navy air control
net.
■ NPG 5: PPLI and Status, Pool A
Position, This NPG is used by nonC2 units in conjunction with NPG 6.

identification, and By using time slots assigned to both NPGs 5 and 6,
status reports are fast-moving fighters are able to transmit their location with a
generated High Update Rate (HUR). Ships do not need to update their
automatically by position as often as aircraft. Terminal status messages
the terminal. containing information such as fuel and weapons status are
also broadcast automatically by each terminal in these
PPLI NPGs.
*CH_6_2001 6 10/2/1, 5:30 PM

■ NPG 6: PPLI and Status, Pool B
This NPG is used by all JUs, C2 and nonC2 alike, for

identification, synchronization, and relative navigation. In
addition to identification and detailed positional information,
the PPLIs include the voice and air control net numbers that
each platform is using. All JUs can display any JU’s PPLI.
By default, when an RTT NPG has not been separately
defined, the JTIDS terminals will exchange RTTs on this
NPG as well. Data from this NPG can be forwarded to
Link-11.
■ NPG 7: Surveillance
Surveillance consists of searching for, detecting, identifying,

and tracking objects. Air, surface, and subsurface tracks,
land-point SAM sites, reference points, ASW points, acoustic All ships and
bearings, and EW bearings and fixes are all exchanged on this the E-2C
NPG. All ships, as well as the E-2C, participate on this NPG. participate
F-14Ds do not currently monitor nor process messages from in the
this NPG — the air picture is uplinked to them by their surveillance
controller — but they can relay it when initialized to do so. function.
In the future, F-14Ds will be upgraded to monitor and update
their track file from this NPG. Data from this NPG can be
forwarded to Link-11.
*CH_6_2001 7 10/2/1, 5:30 PM

LGN 135-02-002
■ NPG 8: Weapons Coordination
NPG 8 provides a means for a command-designated unit to

coordinate Battle Group weapons and order weapons
engagements, and for all C2 JUs to report engagement status,
controlling unit status, and tactical pairings. Data from NPG
8 can be forwarded to Link-11.
■ NPG 9: Air Control
This NPG provides the means for C2 JUs to control nonC2

Air Control is JUs. It is divided into two components each of which is
configured as a configured as a stacked net: the uplink and the backlink.
stacked net with Each net is assigned to a specific controller, either a ship or
two parts: E-2C, and the fighter aircraft being controlled. The control-
the uplink and ling unit provides mission assignments, vectors, and target
the backlink. reports to fighter aircraft on the time slots assigned to the
uplink. The F-14Ds receive a processed and correlated
tactical picture from their controlling unit on the uplink.
*CH_6_2001 8 10/2/1, 5:30 PM

Air Control Backlink

■ Radar Targets
■ Pilot Responses
■ Engagement Status
Air Control Uplink
■ Mission Assignments
■ Vectors
■ Target Reports
■ Correlated Tracks
LK-16/6-08M-032a
Figure 6-2. The F-14D depends on the Air Control uplink from its
controlling unit for situation awareness. Radar targets, pilot responses,
and status reports are transmitted to the controlling unit on the Air
Control backlink.
On the NPG 9 backlink, or downlink, fighters transmit radar targets,

pilot responses to commands, and status to their controlling units.
The backlink time slots are distributed such that each controlled
fighter has dedicated access to its assigned time slots. A maximum
of 16 fighters can participate, with options available to permit either
4 or 8 fighters instead. Because of equipment limitations, the
F-14Ds do not receive and process each other’s backlinked radar
data. Instead, radar data is exchanged between F-14Ds on NPG 19,
the fighter-to-fighter NPG.
*CH_6_2001 9 10/2/1, 5:30 PM

LGN 135-02-002
Net 6
Air Control
t6
Ne
Net 3
Air Control
Ne
t3
47
Net 6
LK/6-08M-032b
Net 5
Net 4
Net 3
Net 2
Net 1
Net 1 Net 0
Air Control
t1
Ne
Net Backlink
6 16 Fighters
5
UPLINK
4
3 4 Fighters
2
1 8 Fighters
0
Capacity Allocation
Figure 6-3. The Air Control NPG’s uplink and backlink typically contain commands to the
fighters, responses from the fighters, fighter engagement status, and target reports. Air
Control is configured as a stacked net, with each C2 unit and its fighters assigned to a
different net. The backlink time slots can be allocated to 4, 8, or 16 fighters.
*CH_6_2001 10 10/2/1, 5:30 PM

■ NPG 10: Electronic Warfare
This NPG supports the dissemination of electronic warfare EW parametric

orders and parametric data among EW-capable ships and data can be
E-2Cs. It is often multinetted with the NPG for fighter shared over the
PPLIs, since the fighters do not participate in this C2-to-C2 network.
exchange of EW data. Data from this NPG can be forwarded
to Link-11.
■ NPG 12: Voice Group A
This NPG provides a secure, digitized voice channel for use

by all JUs. It is usually configured as a stacked net with 127 Voice NPGs may
possible subcircuits. A net initialized with the 128th number, be assigned
net number 127, is understood by the terminal to mean interchangeably
currently undefined. During operations, the terminal uses a to either port.
number supplied by the operator. The operator can change
this number at will. Thus, voice nets initialized with net
number 127 feature a “dial-a-net” capability.
Voice Group A may be assigned to either Port 1 or Port 2 of

the JTIDS terminal. Port 2 is always 16 kbps non-error- Voice remains
correction coded. Port 1 has been implemented in the U.S. active in data
Navy as a 16 kbps non-error-correction-coded voice circuit silence.
as well. Note that voice circuits remain active when the
terminal is set to Data Silent.
*CH_6_2001 11 10/2/1, 5:30 PM

LGN 135-02-002
■ NPG 13: Voice Group B
This NPG provides a second voice channel with the same

characteristics as NPG 12.
■ NPG 14: Indirect PPLI
This NPG supports multilink operations by providing time

slots in which a Forwarding JU (FJU) will transmit PPLIs
containing position and identification information for
Link-11 PUs and Link-11B RUs that are not participating
directly on the JTIDS network, but whose data is being
forwarded to Link-16 by the FJU. It is used solely by the
U.S. Navy and has been implemented in the Model 4 and
Model 5 C2P.
■ NPG 19: Fighter-to-Fighter (Dedicated)
NonC2 units, such as fighters, exchange radar sensor target

information and status on this NPG. It is usually configured
F-14Ds
as a stacked net, with each fighter group assigned dedicated
exchange radar
time slots on one of the nets. A controller can access all the
targets and
nets in the stack with the dial-a-net capability. The
status data on
maximum fighter flight size is 8 fighters, but options are
the Fighter-to-
provided to allow either 2, 4, or 8 fighters per net. Dedicated
Fighter NPG.
access is preferred by the U.S. Navy, and participants on this
NPG are typically F-14Ds.
A small portion of The U.S. Navy’s implementation of this NPG does not allow
the Fighter-to- F-14Ds to be simultaneously active on both the air control
Fighter NPG is backlink and the fighter-to-fighter NPGs. To retain
assigned to the communication between the USN controller and a group of
controlling C2 JU. fighters that have detached from control and are engaged in
*CH_6_2001 12 10/2/1, 5:30 PM

a semi-autonomous fighter mission, several time slots within

this NPG are also dedicated to the controlling C2 JUs. This
small subblock is called the fighter advisory.
■ NPG 20: Fighter-to-Fighter (Contention)
This NPG serves the same purpose as NPG 19, but the time
slots are allocated for contention access. Contention access is
preferred by the U.S. Air Force, and participants on this NPG
are typically F-15s.
■ NPG 21: Engagement Coordination
This NPG is used solely by the U.S. Army for inter-Army

coordination of engagements by PATRIOT and THAAD units.
■ NPG 27: Joint PPLI
Identification and location information can be exchanged

during Joint operations on this NPG.
■ NPG 28: Distributed Network Management
This NPG is not used at the present time.
*CH_6_2001 13 10/2/1, 5:30 PM

LGN 135-02-002
■ NPG 29: Residual Message
This is a special NPG provided to ensure a transmission

opportunity for messages that are not assigned to one of the
other NPGs. Such a left-over, or residual, message could
occur when the particular NPG with which the message is
usually associated was not included in the network in use, or
if the message is not normally assigned to a particular NPG.
The J28 series of proprietary messages which permit the
exchange of free-text, character-oriented messages, for
example, would be transmitted in this NPG.
■ NPG 30: IJMS Position & Status
The IJMS Position & Status messages, or P-messages, are

transmitted in this NPG. The U.S. Air Force Class-2
NPGs designated terminals can interoperate with both JTIDS-equipped and
for IJMS IJMS-equipped units, and forward between them. Although
messages are not the U.S. Navy cannot interoperate with IJMS-equipped
used by the USN. platforms, they do share the same network structure and can
be colocated without mutual interference given the proper
network design.
■ NPG 31: IJMS Messages
All IJMS messages except for position messages and voice

are transmitted on this NPG. These are the IJMS
T-messages. Although the U.S. Navy cannot interoperate
with IJMS-equipped platforms, they share the same network
structure and can be colocated without mutual interference
given the proper network design.
*CH_6_2001 14 10/2/1, 5:30 PM

NPG Function
1 Initial Entry
2 RTT A
3 RTT B
4 Network Management
5 PPLI and Status A
6 PPLI and Status B
7 Surveillance
8 Weapons Coordination
9 Air Control
10 Electronic Warfare
12 Voice Group A
13 Voice Group B
14 Indirect PPLI (Navy Only)
19 Fighter-to-Fighter Targeting (Dedicated)
20 Fighter-to-Fighter Targeting (Contention)
21 Engagement Coordination (Army Only)
27 PPLI (Joint Net Broadcast)
28 Distributed Network Management
29 Residual Message
30 IJMS Position & Status
LK16/6-08M-027
31 IJMS Message
Figure 6-4. Particular J-series messages are associated with each

Network Participation Group and are transmitted automatically by
the JTIDS terminal in the time slots assigned to that NPG.
*CH_6_2001 15 10/2/1, 5:30 PM

LGN 135-02-002
NPG Buffering ■
Messages for up to three NPGs can be buffered in the JTIDS
terminal by the Subscriber Interface Control Program
(SICP). Buffering decreases the chances that a message will
be lost or dropped when message traffic is heavy. An
operator selects which NPGs to buffer. Valid choices are
Surveillance, Mission Management, Weapons Coordination,
Electronic Warfare, and Air Control.
*CH_6_2001 16 10/2/1, 5:30 PM

Section B
Time Slot Assignments
The amount of network capacity assigned to a given NPG
depends on communications priorities, including:
■ The number and types of participants

■ How often the participant needs access to
the NPG
■ The expected volume of data
■ The update rate of the information
■ Relay requirements
The number of time slots that must be allocated within the

NPG to each participant depends on the type of unit and the
method of accessing the time slot.
Section B Time Slot Assignments 6-17
*CH_6_2001 17 10/2/1, 5:30 PM

LGN 135-02-002
Unit Types ■
JTIDS Units are of two basic types: the Command and Control
(C2) JUs and the non-Command and Control (nonC2) JUs. C2 JUs
are those platforms that have the requisite equipment, mission, and
personnel to exercise command and control authority. They direct
the activities of other platforms. In the U.S. Navy, the C2 JUs
include CVs and CVNs, CGs and CGNs, DDGs, LHDs, SSNs, and
E-2Cs. The nonC2 JUs are those whose activities are controlled or
monitored by the C2 JU. In the U. S. Navy, the only nonC2 JUs are
the F-14Ds and F/A-18s.
These two types of units have different missions and different

requirements in terms of which NPGs they participate on and how
often their data must be updated. The primary C2 functions are
surveillance, electronic warfare, weapons coordination, air control,
and net management. The primary nonC2 functions are target
sorting and engagement.
C2 NonC 2
USN CV, CG, DDG, LHD, SSN, E-2C F-14, F/A-18
USAF MCE, E3-A, E-8, ABCCC, MAOC F-15 LK16/6-08M-028
USMC TAOM, ATACC F/A-18

U.S. Army FAAD, TSQ-73, Patriot C2 Center Air Defense Units
Figure 6-5. The primary functions of a C2 JU are surveillance, EW, weapons

coordination, air control, and management of the network. The primary
functions of a nonC2 JU are target sorting and engagement.
6-18 Section B Time Slot Assignments
*CH_6_2001 18 10/2/1, 5:30 PM

Time Slot Access Modes ■

Within each NPG, the time slots assigned to each unit are evenly
distributed over time and generally occur every three seconds,
every six seconds, and so on. These slots are assigned using time
slot blocks which specify a set, index, and recurrence rate, as
previously described, and a net number. Time slot block
assignments are numbered from 1 to 64. The terminal is limited,
therefore, to a maximum of 64 assignments.
While several different access modes for each time slot block have
been proposed at one time or another, two are currently
in use and a third is in development:
■ Dedicated Access
■ Contention Access
■ Time Slot Reallocation Access
■ Dedicated Access
The assignment of time slots to a uniquely identified unit for

transmission purposes is known as dedicated access. Only the
assigned JU can transmit during that time slot. If there is no data to Only one
transmit, the slot goes unused. The advantage of dedicated access JU transmits
is that it provides each JU on an NPG with a predetermined portion in dedicated
of the network’s capacity and a guarantee that there will be no access.
transmission conflicts, at least not in a single-net environment.
One of the disadvantages of dedicated access is that assets are not

interchangeable. One aircraft, for example, cannot simply replace
another aircraft. If this were necessary during an operation, its
terminal would first have to be reinitialized to transmit and receive
during time slots matching those of the unit it would be replacing.
*CH_6_2001 19 10/2/1, 5:30 PM

LGN 135-02-002
Dedicated access can pose a problem for conducting handovers, as

well. Recall the stacked nets used for air control. Fighters are
assigned specific time slots during which to transmit back to their
controller. The same time slots are used for the different fighter
groups, but on separate nets. Net 1 can have eight fighters
(1 through 8) and Net 2 can have eight fighters (1 through 8).
Suppose Control Unit 1 on Net 1 wants to hand Fighter 5 over to
Control Unit 2 on Net 2. The new Fighter 5 will use the same time
slots as the existing Fighter 5, causing simultaneous transmissions
on what is supposed to be a dedicated time slot. A fighter cannot
change groups unless there is a vacancy with the same number, or
unless its terminal is reinitialized over the air.
Dedicated Access
1
NPG 6 on net number _____
Access to _______
00034
is dedicated to JU ____________
32
in the amount of _______ time slots per frame
for transmission of its information.
Guarantee
There will be no interfering transmissions from any
other JU on this net. We guarantee it.
Figure 6-6. Dedicated access uniquely allocates

network capacity to each JU on each NPG,
thereby ensuring that simultaneous transmissions
will not occur.
*CH_6_2001 20 10/2/1, 5:30 PM

■ Contention Access
The assignment of time slots to a group of units as a pool for Several JUs
transmission purposes is known as contention access. In contention may transmit
access, each unit randomly selects a time slot from the pool during simultaneously
which to transmit. The frequency of a terminal’s transmission in contention
depends on the access rate assigned to that terminal. access.
The advantage of contention access is that each terminal is given the

same initialization parameters for this time slot block. This simplifies
the network design and reduces the network management burden.
Since specific assignments for each JU are unnecessary, JUs are
interchangeable. This facilitates the inclusion of new participants
and allows units to be easily replaced. This is particularly important
for aircraft, and the U.S. Air Force uses contention access routinely.
The disadvantage of contention access is that there is no guarantee
that a transmission will be received.
Contention Access
00042 is hereby
JU ________
authorized to take time slots from a pool of
128
________ slots assigned for the
transmission of its information on NPG
64 slots
19 at a rate that shall not exceed ______
______
12 seconds.
every ______
Caution: There is no guarantee that the information you transmit will be
received. The probability of reception can be calculated and depends on the
number of intervening units contending for the same time slots, their access
rates, and their message traffic load.
Figure 6-7. In the contention mode of access,

data is transmitted in time slots chosen at
random from a pool of slots. The number of
slots chosen is determined by the access rate.
*CH_6_2001 21 10/2/1, 5:30 PM

LGN 135-02-002
Because the time slot is not dedicated to one user,

simultaneous transmissions are possible with contention
access. The likelihood of simultaneous transmissions
depends on the number of time slots in the pool, the number
of units in the group, and the frequency with which they
must transmit. If two units do transmit simultaneously during
the same time slot on the same net, whether in dedicated
access or contention access, it is called time slot reuse.
Whenever this occurs, receivers will always hear the unit
closest to them. In some situations, time slot reuse can
provide additional throughput and connectivity.
The probability of reception from a particular unit within

LOS depends on how many intervening units are operating
A probability of in contention, their access rates, and the volume of their
reception can be message traffic. Due to the reduced probability of reception,
calculated for the U.S. Navy does not use contention access extensively,
units exchanging and, in fact, discourages the relaying of contention access
data in contention NPGs. The primary use of contention access by the U.S.
access. Navy is for voice, where the Push-to-Talk protocol serves to
prevent multiple units from transmitting simultaneously. It is
also used for RTTs in a stacked net configuration.
*CH_6_2001 22 10/2/1, 5:30 PM

AAA
AAA
AAA AAAAA
AAA AAAA
A
AAA AAA
AAAAAA
AAAA
A
AAAAA
AAA A
AAA
AAAAA
AAAAAAAA
AA
A AA A
AAA
AAAAA
AAA
AAAA
AAAAA
AAAAA AAA AAA AAAA
AAAA AAAA
AAAAA
AAA
AA
AA
A
AAAA AAAA
AAA
AAA
A
AAAA
AAA
A
AAAA
AA AAAAA
AAAA
A AAA
AAAAA
A
AAAAAAAAA
AA
AAA
AA
AA
AA AAAAA
AAAAA AAA AAAA
AAAA
AAA
AAA AA AAAAAAAAA
AAA
AA AA
AAA
AA
AA
Simultaneous
Silmultaneous
Transmissions
Transmissions
AAA AAAA AAAAAA AAAA AAA

AAAAAAAAA
AAA
AAA
AAAAAAAAAAA AAAA AAAAAAA
LK16/6-08M-032
Period Period
Number Access Rate (Average, Number Access Rate (Average,
in Seconds) in Seconds)
1 2 slots per 48 sec 24.0 9 6 slots per 12 sec 1.50

2 3 slots per 48 sec 16.0 10 8 slots per 12 sec 1.00
3 2 slots per 24 sec 12.0 11 12 slots per 12 sec .75
4 3 slots per 24 sec 8.0 12 20 slots per 12 sec .60
5 2 slots per 12 sec 6.0 13 26 slots per 12 sec ~ .46
6 3 slots per 12 sec 4.0 14 32 slots per 12 sec ~ .38 LK16/6-08M-031
7 4 slots per 12 sec 3.0 15 64 slots per 12 sec ~ .19

8 5 slots per 12 sec 2.0
Figure 6-8. Contention access allocates NPG capacity as a pool of time slots to a group of JUs.
Simultaneous transmissions are possible. These are avoided in the voice NPGs by the
incorporation of a Push-to-Talk protocol. If time slot reuse should occur, that is, if two units
transmit simultaneously in the same time slot on the same net, the transmission from the closest
unit will be the one that is received.
*CH_6_2001 23 10/2/1, 5:30 PM

LGN 135-02-002
■ Time Slot Reallocation

Time Slot Reallocation (TSR) is an access mode which allows
the network capacity of an NPG to be assigned dynamically,
based on the projected needs of its participants. It is intended to
support a fluctuating demand from a varying group of users.
TSR allows network capacity to be distributed where it is
needed, as it is needed, by periodically allocating time slots
from a pool to each participant. Each platform reports its
transmission needs over the network, and algorithms within the
terminal redistribute the pool of time slots to meet these needs.
If the need exceeds the available capacity, the time slots are
redistributed to participating units in proportion to their
reported needs so that there is a graceful degradation of the
link. Once fully implemented, TSR will eliminate the need for
the design option files currently used to reallocate NPG
capacity at initialization time.
Time Slot Reallocation

NPG 7 on net number _____
Access to ________ 0
will be allocated to each JU
according to his need.
128 time slots.
The available pool size is _____
48 seconds.
Reallocation will occur every _____
Warranty
Any network degradation will be shared by all.
Figure 6-9. TSR allows time slots to be periodically

reassigned among the participants of an NPG based
on their reporting needs.
*CH_6_2001 24 10/2/1, 5:30 PM

Assignment of Network Capacity ■

The first step in defining a JTIDS network is the assignment of
network capacity to NPGs. The next step is the assignment of NPG
capacity to JUs. NPG capacity is assigned by specifying time slot
blocks and access modes for each participating JU.
Several additional parameters must be specified in order to use

these time slots. These include the MSEC and TSEC
cryptovariables and an indication of whether to receive, relay A selection of
receive, transmit, or relay transmit during the time slot. They are predesigned
specified at the time the network is designed. Network designs are networks are
stored on tape or cartridges in the JTIDS Network Library (JNL) available from
and made available to all JTIDS users. JNL tapes are employed the JNL.
primarily by the U.S. Navy.
For Link-16 operations, one of these network designs — the one

that best meets operational requirements — is designated and any
design options are specified. This information is conveyed to the
Battle Group as part of the OPTASK LINK. The OPTASK LINK
also specifies the net numbers for stacked nets, associates JU
addresses and track block numbers with each platform, and assigns
key network roles.
The Advanced Tactical Data Links System Program Office has

fielded an Electronic JNL distribution capability known as ELEX
JNL. This capability enables Link-16 BG/ARG/MEF ships to
electronically receive and load JNL files while deployed by
accessing the Link Project Office web page via NIPRNET or by
receiving a JNL file as an e-mail attachment. JNL files are
normally loaded by the C2P from an RD-358 tape drive. JNL files
received electronically can be loaded from a shipboard PC
equipped with the proper interface card and a program called
TAPESIM which simulates the RD-358 tape drive. They can also
be loaded into TAMPS for use in preparing platform loads for the
E-2C and F-14D aircraft.
*CH_6_2001 25 10/2/1, 5:30 PM

LGN 135-02-002
Dynamic Network Management ■

The JTIDS The JTIDS terminal has been designed to accept initialization
terminal accepts commands over the network and a limited capability for
reinitialization over-the-air terminal reinitialization has been implemented.
commands over The E-2C, for example, can assign time slots in the Air
the air. Control NPG to a fighter requesting control over the air. The
C2P can do the same thing. Expansion of these over-the-air
reinitialization commands, currently in the planning stages,
could allow time slots currently allocated to a JU that is
leaving, has left, or was never part of the network, to be
reassigned to other JUs who have requested more capacity,
or to new JUs that wish to join the network. Dynamic
network management has not yet been implemented.
*CH_6_2001 26 10/2/1, 5:30 PM

Section C
Network Roles
Network roles are functions assigned to a JU, either by
initialization or by operator entry. A network role can
support one or more of the following functions:
synchronization, navigation, and multilink operations. Roles
are assigned to C2 units and are made on the basis of platform
capabilities and expected platform position. With the
exception of Network Manager, all roles are terminal
functions. They may be changed during operations and
include:
■ Network Time Reference

■ Position Reference
■ Initial Entry JU (Net Entry Control Terminal)
■ Navigation Controller
■ Secondary Navigation Controller
■ Secondary User
■ Primary User
■ Forwarding JU
■ Network Manager
Roles are assigned in the OPTASK LINK. A JU should hand

off its assigned role(s) to another unit before it inhibits
transmissions or goes data silent.
Section C Network Roles 6-27
*CH_6_2001 27 10/2/1, 5:30 PM

LGN 135-02-002
Network Time Reference ■

The most essential role in establishing the JTIDS network is
that of Network Time Reference (NTR). A single JU is
assigned to be NTR for a given network. The time established
by this unit is, by definition, the network system time. This
system time is propagated to all other units by means of the
initial net entry messages that are transmitted by the NTR.
All other units use these messages to synchronize with the
network. By definition, the NTR is the only unit to have the
maximum time quality, 15. All units periodically adjust their
internal clocks to maintain synchronization with the NTR.
Once established, networks can continue to operate for hours
without an NTR.
By definition, the
initial entry Only one NTR per network is allowed, but an alternate NTR
messages may be designated. The alternate NTR is next in line to
transmitted by the assume the NTR role whenever directed to do so. If a strike
NTR establish the force leaves its Battle Group and establishes a fighter-only
timing of the network, it will coordinate the designation of a separate NTR
JTIDS network. after separating from the other members of the Battle Group.
Assign NTR to a C 2 unit that will be present

throughout the operation and that will have
LOS connectivity with as many other units
as possible.
6-28 Section C Network Roles
*CH_6_2001 28 10/2/1, 5:31 PM

Position Reference ■
The Position Reference (PR) must have a geodetic positional
accuracy within 50 feet, and should be assigned only to well-
surveyed, stationary sites. By definition, PRs are assigned a
position quality of 15. They provide a stable geodetic
reference for other units to use in determining their own
geodetic position via the RELNAV function. PRs also assist
the NC in refining the accuracy of the relative grid.
Networks can, however, operate without a PR.
Never assign the role of PR to a Navy unit!
Initial Entry JU ■
An Initial Entry JU (IEJU) assists in the propagation of The IEJU
system time to units that are beyond line of sight of the NTR. provides system
After the IEJU has become synchronized with the NTR, it time to units
also transmits initial net entry messages. A unit not within beyond LOS of
LOS of the NTR can then synchronize with the network by the NTR.
synchronizing with the IEJU. Any active terminal can
perform this function, and any number of IEJUs may be
active at one time. The IEJU function can be performed by
both surface and air units and can be selected by the opera-
tor. The IEJU is also referred to as a Net Entry Control
Terminal (NECT).
Assign the role of IEJU to all active units.
*CH_6_2001 29 10/2/1, 5:31 PM

LGN 135-02-002
Navigation Controller ■
The Navigation Controller (NC) is not a required role. An
NC is designated only when a relative grid is desired. The
The relative grid relative grid is a three-dimensional coordinate system used
is established by by JUs to report their position from the grid origin. The
the NC. relative grid origin is the origin calculated by the NC,
which includes any geodetic navigation errors made by the
NC. The NC acts as the reference unit for the grid and is
assigned a relative position quality of 15. The relative grid
becomes operational as soon as it is established by the NC.
The NC should be mobile, present for the

duration of the operation, and have
good LOS connectivity to as many units
as possible.
*CH_6_2001 30 10/2/1, 5:31 PM

When a relative grid is established, the Relative Navigation

function of the terminal will provide accurate relative
positions between JUs, even when some JUs hold inaccurate
geodetic data for their own positions. The unit assigned the
role of NC must be a C2 unit that is both mobile and in active
synchronization. For the U.S. Navy and U.S. Air Force, there
can be only one NC. The U.S. Army, however, may use
multiple stationary NCs. An E-2C operating near the center
of the Battle Group should be NC (with no SNC) when
possible.
If the NC becomes stationary, hand off

the role!
Secondary Navigation Controller ■

The Secondary Navigation Controller (SNC) provides
stability to the Relative Grid. There is only one SNC unit,
and it must be in active synchronization within LOS of the
NC. Either a mobile or a stationary unit can serve as the
SNC. There should, however, be relative motion between the
NC and SNC. One possibility is to assign two ships within
LOS as NC and SNC. Another good combination is to
assign NC to an E-2C operating greater than 50 nm away
from the Battle Group and SNC to a ship within LOS of the
E-2C. They must remain separated by more than 50 nm to
meet the low angular motion criteria.
*CH_6_2001 31 10/2/1, 5:32 PM

LGN 135-02-002
Primary User ■
A PRU transmits All JUs, except the NTR, are said to be Primary Users (PRU)
RTTs to actively if they routinely transmit RTT messages to achieve and
maintain maintain fine synchronization with the network. Networks
synchronization designed for use by the U. S. Navy typically support up to
with the network. 200 primary users. If the number of users exceeds 200,
however, some will have to be designated as secondary
users.
Secondary User ■
A JU operating passively is said to be a Secondary User
An SU does not (SU). Units can enter the network passively, or an operator
transmit RTTs can select passive operations after entering the network
or PPLIs. actively. Two passive modes can be selected by an operator:
Synchronization
with the network ■ Long Term Transmit Inhibit
is maintained
passively. ■ Data Silent
Long Term Transmit Inhibit, or LTTI, is radio silence —

all transmissions are inhibited. In Data Silent, voice remains
active, and TACAN (in an air platform) operates normally.
Relays are inhibited. SUs can receive messages but do not
transmit PPLIs or RTTs. If a JU inhibits transmissions or
goes data silent, the terminal transmits one last PPLI with its
user identification set to SU. It can return to operation as a
PRU by resuming active synchronization.
*CH_6_2001 32 10/2/1, 5:32 PM

Forwarding JU ■
A JU designated to forward data between links is called a
Forwarding JU (FJU). The FJU which translates and The FJU
forwards data between Link-11 and Link-16 is a Forwarding translates and
JU-TADIL A (FJUA). All U.S. Navy surface C2 JUs can forwards data
function as FJUAs. A unit communicating on both Link-16 between tactical
and TADIL B and which translates and forwards data links.
between them is an FJUB. U.S. Navy units do not function
as FJUBs and throughout this document the acronym FJU
should be understood to be synonymous with FJUA.
Data transmitted in the PPLI, Mission Management,

Weapons Coordination, EW, and Surveillance NPGs of
Link-16 may be translated and forwarded to Link-11 by the All ships can
FJU. Similarly, Link-11 data may be forwarded to Link-16, perform the FJU
with PPLIs provided for the Link-11 units automatically by role.
the FJU and transmitted on NPG 14. The C2P is the only
Navy system capable of performing the FJU function.
Ideally, only one FJU is assigned for the entire force, but an
alternate may be designated. The alternate FJU participates
in the Link-16 network and monitors the Link-11 net through
the C2P. Whenever it detects that the active FJU has stopped
transmitting on either link, it automatically alerts an operator
who must decide whether or not to assume the FJU function.
*CH_6_2001 33 10/2/1, 5:32 PM

LGN 135-02-002
Interface Control Officer ■

One unit is assigned the responsibility for administering the
minute-by-minute operation of the Link-16 network. This
unit is the Interface Control Officer (ICO). The role of
Interface Control Officer is a responsibility rather than a
terminal function. The ICO monitors force composition,
geometry, network configuration, relay requirements, and
multilink requirements. Actions by the ICO relative to
network control and coordination include the assignment of
functional network roles, changes in IPF modes, relay
activation and deactivation, and changes in the data silent
condition of a JU.
*CH_6_2001 34 10/2/1, 5:32 PM

Section D
Net Entry
Protocol for entering the JTIDS network is handled by the Net entry is
terminal. One unit is designated to be the system time performed by the
reference. This unit is called the Net Time Reference. It JTIDS terminal.
transmits a net entry message on NPG 1 of Net 0 using the
default TSEC and MSEC cryptovariables, usually in the first
time slot of every frame. This is time slot block A-0-6.
The net entry message for JTIDS is the Initial Entry message.
The time at which this message is transmitted defines the
system time. The body of the net entry message includes the
time quality, RTT radio silence status, and the current default
net number. It may contain voice, PPLI, and RTT time slot
assignments on the default net for the next epoch. Depending
on the transmitting terminal’s AJ Communications Mode
setting, the terminal may automatically append extension or
continuation words to the message.
The process of acquiring system time is called synchroniza-

tion. It can be performed actively or passively. Each method
requires several steps. Since the process starts with an
estimate of the current time, net entry can be simplified for
everyone if the NTR uses coordinated Universal Time (UT)
from the Global Positioning System (GPS)!
Simplify net entry by having the NTR use

GPS for UT.
Section D Net Entry 6-35
*CH_6_2001 35 10/2/1, 5:32 PM

LGN 135-02-002
Coarse Synchronization ■
The first step to entering a network is to acquire synchroni-
zation. Using an estimate of the current time and an estimate
of its own clock error (time uncertainty), a terminal entering
The only the net chooses a time slot from the A-0-6 time slot block
transmission which it is certain has not yet occurred. It begins listening
made by a for a net entry message. It starts listening one time-uncer-
terminal in coarse tainty period before the expected time slot, and continues to
sync is the RTT listen for one time-uncertainty period afterwards. If the
interrogation. uncertainty estimate is correct, it should receive the message.
If the message is not received, the terminal tries again. If the
message is received, the time of receipt is used to correct the
terminal’s system time. This adjusted system time may still
include an error due to propagation time.
Once the net entry message has been received the terminal is
declared to be in coarse synchronization. After a terminal
has achieved coarse synchronization, it knows the system
time to within one slot-time and it can begin to transmit RTT
interrogations.
Fine Synchronization ■
The terminal must Once in coarse synchronization, the terminal transmits an
be in fine sync to RTT-I interrogation to the NTR. The NTR responds during
transmit messages the same time slot with a reply. This reply contains the time
on the network. of arrival of the interrogation at the NTR. Using both the
measured time of arrival of the reply, and the reported time
of arrival of the interrogation, the terminal can further adjust
its system time to remove the error due to propagation time.
The terminal is then declared to be in fine synchronization.
The terminal must be in fine synchronization to fully
participate in the network.
6-36 Section D Net Entry
*CH_6_2001 36 10/2/1, 5:32 PM

The error in the clock maintaining system time is estimated

continuously by the terminal. Even the temperature of the
terminal components, as estimated by the length of time the
terminal has been powered up, is considered. If the current
clock frequency will keep the terminal’s clock error to within
36 µsec during the next 15 minutes, fine sync can be confirmed.
If the clock error exceeds a threshold setting by as little as 54
µsec, the terminal’s status is downgraded from fine sync
confirmed to fine sync in process. Terminals in fine sync can
maintain time with sufficient accuracy to continue operating
for up to 3 hours.
Active vs. Passive Synchronization ■

The process of transmitting RTTs to refine the terminal’s
estimate of system time is known as active synchronization.
If a terminal is within LOS of the NTR, it takes only seconds
to become active on the network.
It is also possible to acquire system time passively—that is,

without transmitting on the network. Passive synchronization Passive sync
must be used when the Long Term Transmit Inhibit (LTTI) is must be
enabled and the terminal is in radio silence. Instead of performed when
transmitting RTTs after coarse synchronization has been the terminal is in
established, the terminal listens for position messages on the radio silence.
PPLI NPGs. Using the position of the unit reported in the
PPLI message and the knowledge of its own position from its
navigation system, the terminal can estimate the propagation
time required for the message. By comparing the expected
time of arrival with the actual time of arrival, the terminal can
adjust its estimate of system time to remove the propagation
error. Time-of-arrival measurements are made to the nearest
12.5 nanoseconds.
Section D Net Entry 6-37
*CH_6_2001 37 10/2/1, 5:32 PM

LGN 135-02-002
Section E
Location and
Identification: PPLIs
JTIDS terminals employ relative navigation techniques to
constantly fix their platform’s position. This information is
transmitted periodically, along with other identification and
status information, in the Precise Participant Location and
Identification (PPLI) message. The PPLI is the “friendly unit
reporting message.” It can be used to determine link partici-
pants and data forwarding requirements, as well as to initiate
air control. It also supports passive synchronization. PPLIs
are transmitted periodically by all JUs active on the network
on NPG 5 and/or NPG 6. PPLIs generated for Link-11 units
by the FJU are transmitted on NPG 14.
6-38 Section E Location and Identification: PPLIs
*CH_6_2001 38 10/2/1, 5:32 PM

Precise Location ■
Location is reported as a three-coordinate geodetic point
having latitude, longitude, and altitude. Present course and
speed are also provided. This information is used by the
receiving terminal’s RELNAV function, along with other
information such as the quality reports, RTTs, and local
navigation inputs, to refine its calculations of its own position.
Positive Identification ■
Each participant in Link-16 is assigned a unique JTIDS Unit
(JU) number between 00001 and 77777. In addition, the In addition to
JTIDS terminals themselves require a Source Track Number identification and
(STN) of 5 octal numbers. This must be the same as the JU position, the PPLI
number in order that the terminals may perform receipt/ message reports
compliance processing. air control and
voice net
In addition to the JU number, the PPLI message contains numbers, time
information such as IFF codes, platform type, mission, quality, and
location and movement information, and link activity position qualities.
information. Not all of this information is available to Model
4 platforms, which are limited by their Link-11 and Link-4
database structure.
Section E Location and Identification: PPLIs 6-39
*CH_6_2001 39 10/2/1, 5:32 PM

LGN 135-02-002
Status ■
Host platforms provide detailed equipment and ordnance

status and inventory data to the JTIDS terminal for periodic
Detailed fuel, inclusion with the PPLI data. The specific numeric inventory
weapons, and of shipboard force defense missiles and aircraft weapons, as
equipment status well as operational, degraded, or non-operational status of all
is reported in relevant shipboard and aircraft systems, is reported. This will
status messages allow automatic compilation and display of complete force
on the PPLI NPG. status to appropriate operational commanders, as well as a
summary of the status of selected units, such as the JTIDS
aircraft under control.
Status information reported in the PPLI also includes the air

control and JTIDS voice net numbers, or other UHF voice
frequencies, each platform is currently using. This
information is helpful in establishing voice comms or
initiating air control operations. There is also an indicator in
track messages that allows a unit to assume reporting
responsibility for an inactive JU and informs participants
that the ID is based on previous receipts of PPLI messages
from the JU with that track number.
*CH_6_2001 40 10/2/1, 5:32 PM

Time Quality ■
Each terminal estimates how well it knows system time. This
estimate is based on its clock drift, the accuracy with which
the terminals replying to its RTT interrogations know system
time, and the time since it last completed an RTT exchange. Only the NTR
This estimate is used to set its time quality (Qt ). Values of has a time quality
time quality range from 0 to 15. Only the NTR has a time of 15.
quality of 15. Each terminal provides its time quality to the
network in every PPLI message that it transmits, as well as
in the RTT message and any Initial Entry message that it
transmits.
Time Standard Time Time Standard Time

Quality Deviation Quality Deviation
Qt (Nanoseconds) Qt (Nanoseconds)
15 ≤ 50 7 ≤ 800
14 ≤ 71 6 ≤ 1130
13 ≤ 100 5 ≤ 1600
12 ≤ 141 4 ≤ 2260
11 ≤ 200 3 ≤ 4520
10 ≤ 282 2 ≤ 9040
9 ≤ 400 1 ≤ 18080
8 ≤ 565 0 > 18080
Figure 6-10. Time quality is a value between 0 and 15 indicating

the accuracy with which a unit knows system time.
*CH_6_2001 41 10/2/1, 5:32 PM

LGN 135-02-002
Position Quality ■
Position quality is a value between 0 and 15 indicating the
Geodetic position is accuracy with which a unit knows its geodetic position
measured in latitude, (Qpg ) and its relative position (Qpr ). Geodetic position is
longitude, and altitude. measured in latitude, longitude, and altitude. Position is
provided by navigation sources, and the value entered by the
system manager should be consistent with the platform’s
navigation equipment. A geodetic position quality of 15 is
assigned to stationary Position References and indicates
accuracy of position within 50 feet.
Relative position is Sometimes the network uses a relative grid instead of a

measured with respect geodetic one. In this case, one unit is designated as the
to the unit designated Navigation Controller (NC) and all positions are measured
as the Navigation relative to this reference unit. A relative position quality of
Controller (NC). 15 is assigned to the NC in this case.
Positional accuracy is important not only for track correlation

and the prevention of dual designations, but also for systems
using remote data for over-the-horizon targeting, and for
remote intercept control.
Passive Synchronization ■
The PPLI message is essential to the process of passive
synchronization. Using the position of a unit reported in the
PPLI and knowledge of its own position, a unit operating
passively can estimate the range and therefore the propagation
time required for the message. Combining this information
with the actual arrival time, and taking into consideration the
time quality and position quality reported in the PPLI, the
terminal can make adjustments to its estimate of system time.
*CH_6_2001 42 10/2/1, 5:32 PM

Position Position Error Bound

Quality Uncertainty (3 std devs)
(ft) (ft)
15 < 50 < 150

14 71 213
13 100 300
12 141 423
11 200 600
10 282 846
9 400 1200
8 565 1695
7 800 2400
6 1130 3390
5 1600 4800
4 2260 6780
3 4520 13560
2 9040 27120
1 18080 54240
0 >18080 >54240
LK16/6-08M-035
Figure 6-11. Position quality is a value between 0 and 15 indicating

the accuracy with which a unit knows its position.
*CH_6_2001 43 10/2/1, 5:33 PM

LGN 135-02-002
Section F
Receipt/Compliance
Certain messages require acknowledgment to indicate that
the message was received. Two levels of acknowledgement,
called receipt/compliance (R/C) processing, are performed.
Machine receipts The first level of acknowledgement, called machine receipt
are issued by the (MR), is performed automatically by the system. The second
JTIDS terminal level of acknowledgment is a response from the operator and
as required. indicates an intention to comply (HAVCO) or not to comply
(CANTCO). In Link-11, the machine receipt portion of the
R/C processing is performed by the TDS computers. In
Link-16, it is an automatic function performed by the JTIDS
terminals. Other responses, such as can’t process
(CANTPRO), are possible as well.
Both in Link-11 and in Link-16, the message is automatically

retransmitted if the MR is not received . This process can
occur several times. The appropriate operators are informed if
the message is not MRed after several retransmissions have
been made.
6-44 Section F Receipt/Compliance
*CH_6_2001 44 10/2/1, 5:33 PM

The Donated Slot ■

Special time slots do not need to be assigned for receipt/ Whenever a
compliance processing. Whenever a terminal transmits a terminal
message that requires an acknowledgement, the terminal transmits a
donates one of its assigned transmit slots for the response. message that
By donating a slot, the transmitting terminal knows where to requires an
look for the MR and ensures that the response is timely. The acknowledgement,
location of the donated slot is specified in the transmitted the terminal
message’s R/C recurrence rate field. The donated slot must donates one of its
be within 16 to 1536 slots of the slot in which the message assigned transmit
was received. JTIDS terminals other than the one addressed slots for the
note the position of the donated slot as well, and lock out response.
transmissions in that slot.
Section F Receipt/Compliance 6-45
*CH_6_2001 45 10/2/1, 5:33 PM

LGN 135-02-002
Section G
Relays
JTIDS is strictly a UHF line-of-sight communications
system. For air-to-air, or ship-to-air, this is approximately
Relays are 300 nautical miles. For ship-to-ship, this is closer to
required to 25 nautical miles. Because of this, relays are almost always
extend JTIDS required for the Battle Group. Relays are established during
connectivity network design, and time slots are allocated specifically for
beyond this purpose. As many JUs as possible are preassigned as
line of sight. either conditional, unconditional, or suspended relays. Time
slots are allocated for relay as part of the network design and
can be changed only by time slot reassignment.
General Requirements ■
The network is The JU designated to be a relay must be provided with the
designed with capacity to transmit the relayed message. Messages received
specific time slots in one time slot are relayed at a later time in a specified,
designated as preallocated slot. The original message and the retransmitted
relay pairs and message are referred to as a relay pair. Paired time slot
specific JUs blocks are assigned as part of each NPG that requires relay
designated to support. The number of time slots required depends on the
perform the relay number of relay hops required to reach the destination. The
function. U.S. Navy is currently using only single-hop relays.
In addition, the relaying unit must be in fine sync and in the

normal range mode. Reed-Solomon error correction is
performed by the relaying terminal on messages prior to
retransmission. Messages with uncorrectable errors are not
retransmitted.
6-46 Section G Relays
*CH_6_2001 46 10/2/1, 5:33 PM

The most basic type of relay technique is called the paired

slot relay. The originating terminal transmits a message. The
relaying terminal receives it, stores it, and retransmits it. The
transmit slot is paired with the receive slot by a fixed offset
called the relay delay. The relay delay must be greater than
6 and less than 31 time slots. The net number on which the
relay transmits does not have to be the same as that on which
it received. The JTIDS terminal of the relaying unit can be
initialized, for example, to relay-receive on Net 0 and The use of relays
relay-transmit 6 time slots later on Net 1. The assignment of reduces the
a relay pair counts as one time slot block assignment. By potential capacity
doubling the time slot requirements, relays reduce the of an NPG by
potential capacity of an NPG by 50%. 50%.
Paired Slots
AA AA
•• •
AA
AA AA
AA
• •
•
Relay Delay
Original Relayed
Transmission Transmission
LK-16/6-08M-032c
Figure 6-12. In the paired slot relay, the slot of the original
message is paired with a slot for the relay retransmission of the
message by specifying the original slot and a relay delay.
Section G Relays 6-47
*CH_6_2001 47 10/2/1, 5:33 PM

LGN 135-02-002
Problem: To determine the relay delay between the Relay Receive

TSB n0 – s0 – r and the Relay Transmit TSB n1 – s1 – r.
Note that the RRNs must be the same for relay TSBs.
Solution: Step 1. Let the set be represented by a number,
such that A = l, B = 2, and C = 3. Thus,
TSB B – 4 –12 would be represented by
n = 2, s = 4, and r = 12.
Step 2. Calculate the relay delay as
D = (3 x sl+n1) – (3 x S0 + n0)
Step 3. If the delay is negative, add the following
correction factor: (3 x 215 – r)
Example A: Relay receive has a TSB of A-0-12. Relay transmit has a TSB of
A-4-12. Calculate the relay delay.
Step 1. Set n0 = 1, s0 = 0 and n1 = l, s1 = 4.
Step 2. Calculate D
D = (3 x 4 + 1) – (3 x 0 + 1)
= (13) – (1)
= 12
Conclusion: Delay is 12 time slots.
Example B: Relay receive is assigned a TSB of B – 31 – 10. Relay transmit is

assigned a TSB of B – 23 – 10. Calculate the relay delay.
Step 1. Set n0 = 2, s0 = 31 and n1 = 2, s1 = 23.
Step 2. Calculate D
D = (3 x 23 + 2) – (3 x 31 + 2)
= (71) – (95)
= – 24
Step 2. Apply the correction factor to the negative delay.
= – 24 + (3 x 215 – 10) = - 24 + (3 x 25)
= – 24 + (3 x 32) = -24 + (96)
= 72
Conclusion: Delay is 72 time slots. This exceeds the maximum allowable
delay and the assigned TSBs should be reallocated by the network
designer.
Figure 6-13. If the time slot block assignments are known, the relay delay can be
calculated. The delay must be between 6 and 31 time slots.
*CH_6_2001 48 10/2/1, 5:33 PM

Relay Types ■
The type of paired-slot relay is specified in the message itself
and provides additional information to the terminal about the
information to be relayed. The following types are defined:
■ Main Conditional/Unconditional
■ Voice Conditional/Unconditional
■ Control Conditional/Unconditional
■ Zoom
■ Directed
■ Message Directed
■ Participation Group
The main net is the net on which housekeeping and overhead

functions are performed. These include the exchange of RTT
and PPLI messages and the main net is usually on Net 0. All time slots
Voice and air control nets are usually defined as stacked assigned to a
nets. The zoom relay allows selected portions of the main particular NPG
net to be relayed on another net. The zoom net number must can be specified
be specified with this relay type. The message-directed relay for relay.
allows a particular message to be directed to a particular
NPG. And, finally, messages from an entire NPG can be
specified for relay.
If the relay is defined to be an unconditional relay, the

terminal relays messages in accordance with the receive and
relay transmit time slot assignments provided at initialization
time. The relay will occur unless the terminal is not in fine
sync or has been set to data or radio silence.
*CH_6_2001 49 10/2/1, 5:33 PM

LGN 135-02-002
The conditional relay, on the other hand, requires the terminal

to selectively activate or deactivate the relay function based on
which JU can provide the most efficient coverage. The
conditional relay becomes active if its geographic coverage is
greater than that of the current relay. Geographic coverage is
The conditional determined from the height and range data provided in the
relay depends on relay unit’s PPLI. In general, the unit with the greater altitude
geographic is assumed to be in a better relay position. For stacked nets
coverage. such as the voice and control nets, the net numbers of the
originator and the relay must match. For example, an F-14 on
voice net 11 can only relay voice net 11, not all voice nets.
Several units can be assigned to relay the same NPG in the
conditional mode. A unit can be assigned to relay-receive on
one net and relay-transmit on a different net.
A relay can be suspended by placing the terminal in the

suspend mode.
■ Flood Relay
Paired-slot flood relay is a strategy designed to improve

connectivity to units out of line of sight with each other. It is
the principle relay mode for the USN and is used whenever
practicable. In the flood relay, any NPG designated to be
In the flood relay, relayed in the network design is relayed by everyone! Here’s
all units act as how it works. The originating terminal transmits the message
unconditional, in the original time slot — and in all paired relay slots as
multiple relays. well. All units receiving the original message will transmit it
in all remaining paired relay slots. For multiple hop relays,
units receiving the relayed transmission on the first hop will
transmit it in any remaining relay slots (checking to ensure
there is no relay beyond the designated number of hops).
Flood relay is slot reuse to the max!! Flood relay is not
allowed under the 40/20 IPF rules. It is allowed under the
100/50 IPF rules.
*CH_6_2001 50 10/2/1, 5:33 PM

JU 3
JU 5
1st Relay
2nd Relay
3rd Relay
Original
JU 4
JU 6
AA AA AA A
1 2 JU
JU JU
7
•••
AA AA A
Original Relay Relay Relay
•••
AAAAAAAAAAAAAA
A A A A A A A AA AA A A A
1st Hop 2nd Hop 3rd Hop
AAAAAAAAAAAAAA
AAAAAAAAAAAAAA
JU 1 XMT XMT XMT XMT
AAAAAAAAAAAAAA
JU 2 RCV XMT XMT XMT
JU 3 RCV XMT XMT XMT
AAAAAAAAAAAAAA
JU 4 – RCV XMT XMT
LK-16/6-08M-032d
JU 5 – – RCV XMT
AAAAAAAAAAAAAA
A AAAAAAAAAAAAA
JU 6 – – – RCV
JU 7 – – – RCV
Figure 6-14. In the flood relay, all units receiving the original message as well as
the message originator retransmit it in all remaining relay slots.
*CH_6_2001 51 10/2/1, 5:33 PM

LGN 135-02-002
■ Repromulgated Relay
An enhanced repromulgation relay is available in the Class

2M terminals used by the U.S. Army. The repromulgation
(reprom) relay is useful for moving ground units in
situations where line-of-sight to other units changes. Once a
source transmits, any initialized receiver will relay the
message in the next time slot. The message header contains
information required for a reprom relay including a reprom
indicator, the original hop count and the current hop count.
If the receiving terminal has not already relayed the message,
it decrements the current hop count and retransmits the
message in the next time slot. The source can specify how
many times the message should be retransmitted by specify-
ing the desired hop count. Thus messages are relayed out
from the originator by whatever connectivity paths exist,
hopping from unit to unit.
■ Blind Relay
A relay assignment in which the relaying unit is unable to

decrypt the message contents is known as a blind relay. The
relaying unit has the correct TSEC cryptovariable so it is
able to receive and transmit the message, but it does not have
the MSEC cryptovariable necessary to determine the
message contents.
*CH_6_2001 52 10/2/1, 5:33 PM

The Source transmits message:
Source Relay Relay Destination
The first relay retransmits the message in the first

time slot after the original message:
The second relay transmits the message in the second

time slot after the original message. At the same
time the source transmits a new message.
Figure 6-15. The reprom relay accommodates up to 9 hops. Like

Paired Slot relays, the reprom relay doubles the slot requirements
for a message. After the first relay hop is completed, however, the
originator can transmit another message. The first message keeps
being relayed outwards in the meantime. The U.S. Navy does not
use reprom relays.
*CH_6_2001 53 10/3/1, 1:08 PM

LGN 135-02-002
Section H
Communications Security
Communications security (COMSEC) is provided by the
KGV-8 Secure Data Unit (SDU) and entails several layers of
encryption.
The KGV-8 ■
The Secure Data Unit encryption device, the KGV-8,
attaches directly to the terminal and has memory locations
available for 8 cryptovariables. A cryptovariable (CV) is a
binary key used to encrypt and decrypt data. CVs are not
referred to directly but are given a label. This
cryptovariable logical label (CVLL) is a number between
0 and 127 . The Network Designer assigns a CVLL to each
time slot. CVLLs are used during network design to segment
or isolate portions of the network into cryptonets.
Cryptovariables are provided via cannisters of paper tape.

Each cannister is associated with one CVLL and contains all
the CVs to be used for that CVLL for each day of an entire
month.
6-54 Section H Communications Security
*CH_6_2001 54 10/2/1, 5:33 PM

SDU
CPD CCPD = 0 CVLL CV
Memory Location
1st Pair 0 0 today 6 01001 . . . 11 CCPD for
July 7, 1994
1 1 tomorrow 6 01011 . . . 10 is 0.
2nd Pair 2 0 today 1 00101 . . . 01
3 1 tomorrow 1 00111 . . . 01 July 5
CV 5 CPD = 0
3rd Pair 4 0 today 23 10101 . . . 10 July 6
CV 6 CPD = 1
5 1 tomorrow 23 10001 . . . 11
July 7
4th Pair 6 0 today 2 01011 . . . 01 CV 7 CPD = 0
7 1 tomorrow 2 00010 . . . 01 CV 8 July 8

CPD = 1
CVLL = 2
July '94
Figure 6-16. The SDU memory locations contain pairs of cryptovariables used to
encrypt and decrypt the message data. These CVs are assigned a label, or CVLL, used
by the Net Designer to assign the CV to each time slot. The current Crypto Period
Designator (CCPD) identifies which of the pairs to use.
Within the SDU are eight memory locations organized as four today/
tomorrow pairs. Each location is associated with a CVLL. It is also
associated with a crypto period designator (CPD). The even-numbered
locations are assigned a CPD of 0 and the odd-numbered locations are
assigned a CPD of 1. Crypto personnel load the appropriate CVs into the
appropriate SDU locations. The designation of which CVLL is loaded into
which member of the pair is not happenstance. Every day is assigned a CPD,
beginning with 0 on January 1, 1985 and alternating between 0 and 1 for
each day thereafter. The Current CPD (CCPD) is established by the date
on which the terminal is initialized. It is either a 0 or 1 and designates to
the terminal which one of the pair to use for today. The other one is
automatically used for tomorrow. An additional parameter, the sequence
number, varies between 0 and 7 and indicates how long the CVs will
be used.
Section H Communications Security 6-55
*CH_6_2001 55 10/2/1, 5:33 PM

LGN 135-02-002
CPD Prediction Table

2000, 2008, 2016 2004, 2012
Day is Day is
Month Month
Odd Even Odd Even
Jan 0 1 Jan 1 0
Feb 1 0 Feb 0 1
Mar 0 1 Mar 1 0
Apr 1 0 Apr 0 1
Leap Years
May 1 0 May 0 1
Jun 0 1 Jun 1 0
Jul 0 1 Jul 1 0
Aug 1 0 Aug 0 1
Sep 0 1 Sep 1 0
Oct 0 1 Oct 1 0
Nov 1 0 Nov 0 1
Dec 1 0 Dec 0 1
1999, 2002, 2005, 2007, 1998, 2001, 2003, 2006,

2010, 2013, 2015, 2018 2009, 2011, 2014, 2017
Day is Day is
Month Month
Odd Even Odd Even
Jan 1 0 Jan 0 1
Feb 0 1 Feb 1 0
Non-Leap Years
Mar 0 1 Mar 1 0
Apr 1 0 Apr 0 1
May 1 0 May 0 1
Jun 0 1 Jun 1 0
Jul 0 1 Jul 1 0
Aug 1 1 Aug 0 1
Sep 0 1 Sep 1 0
LK-16/6-08M-032f
Oct 0 1 Oct 1 0
Nov 1 0 Nov 0 1
Dec 1 0 Dec 0 1
Figure 6-17. Each time slot is assigned a cryptovariable using a CVLL.

These CVs are loaded into the KGV-8 memory in today/tomorrow pairs.
Associated with each calendar day is a CPD of 0 or 1, which designates
which one of the pair to use. For example, the CPD for 4 July 1994 is 1.
The CVs for this day are located in the odd memory locations.
6-56 Section H Communications Security
*CH_6_2001 56 10/3/1, 1:24 PM

MSEC and TSEC ■

There are two layers of communications security provided:
message security, or MSEC, and transmission security, or
TSEC. The MSEC CV (pointed to by the MSEC CVLL) is
used to encrypt the message data prior to the Reed-Solomon
encoding, interleaving, pulse generation, etc. The TSEC CV
(pointed to by the TSEC CVLL) determines the amount of
jitter in the time slot and the 32-chip pseudorandom noise
variable. The TSEC CV, together with the net number and
time slot number, also determines the frequency hopping
pattern of the carrier.
Two encryption modes are distinguished. When the MSEC

and TSEC CVLLs are the same, the common variable
mode (CVM) is in effect. When MSEC and TSEC have
different CVLLs, the partitioned variable mode (PVM) is
in effect.
Each NPG is assigned two CVLLs, one to be used for MSEC

and one to be used for TSEC. In addition, a default net
number, a default MSEC, and a default TSEC are also
assigned. When the terminal has nothing to transmit, it
defaults to receive using these default parameters. Navy
networks, thus far, have used CVLL 1 in the common
encryption mode for the default, or global, MSEC and TSEC
encryption parameters.
Section H Communications Security 6-57
*CH_6_2001 57 10/2/1, 5:33 PM

LGN 135-02-002
Section I
Multinetting
The JTIDS waveform allows for the definition of 127 different
nets. The net number, along with the TSEC cryptovariable and
time slot number, determines the carrier frequency hopping
pattern. These different hopping patterns are what keep the nets
separate and distinct and allow multiple nets to operate
concurrently. Multiple nets can be established simply by
specifying different net numbers for a particular NPG, without
changing the TSEC and MSEC cryptovariables. If the MSEC
and TSEC cryptovariables are changed, several variations of
multinetting are possible, including blind relays. The most
common forms of multinetting are stacked nets, and crypto nets.
MSEC TSEC Net Number Type of Multinetting
Same Same Same Not multinetting!

Same Same Different Stacked net
Same Different Same Crypto net
Same Different Different Crypto net

Different Same Same Crypto net (Blind relay)
Different Same Different Crypto net (Multiple nets)
Different Different Same Multiple Networks

Different Different Different Multiple Networks
Figure 6-18. The blind relay, a type of multinetting, occurs when two
JUs are assigned the same TSEC cryptovariable and the same net
number, but a different MSEC cryptovariable.
6-58 Section I Multinetting
*CH_6_2001 58 10/2/1, 5:33 PM

Multiple Nets ■
Multiple nets can be established simply by specifying
different net numbers. The SDU of the Class-2 terminal
holds up to 8 cryptovariables stored as today/tomorrow pairs
which could be used at any one time. Using one of these CVs
in conjunction with 127 possible net numbers allows a
potential of 508 different hopping patterns, or independent
nets for any given time slot block. Although hundreds of nets
are possible, any given terminal can transmit or receive on
only one of them for each time slot.
•
•
• Note: The time slots
Net 4 of each TSB are
Net 3 actually interleaved,
Net 2 not contiguous.
Net 1 NPG 10
Net 0 NPG 4
NPG 8
Time Slot Block NPG Net # MSEC TSEC
A – 8 – 10 8 0 1 1
LK-16/6-08M-032g
A – 40 – 9 4 1 1 1
A – 0 – 12 10 2 2 1
Figure 6-19. Multiple nets can be established simply by specifying

different net numbers.
Section I Multinetting 6-59
*CH_6_2001 59 10/2/1, 5:33 PM

LGN 135-02-002
Stacked Nets ■
A stacked net is created by assigning the same group of time slots
to the same NPG with the same TSEC parameter but with different
net numbers. The time slots must have the same set, initial slot
number, and recurrence rate. They may have different net numbers
and the same crypto keys, or different net numbers and different
crypto keys. The Voice Nets and the Control Nets are examples of
stacked nets.
•
•
• Note: The 16 time slots
Net 4 of TSB A – 8 – 10 are
Net 3 actually interleaved,
Net 2 not contiguous.
Net 1
Net 0
NPG 19
Time Slot Block NPG Net # MSEC TSEC Participants

A – 8 – 10 19 0 1 1 CV + 8 F-14Ds
A – 8 – 10 19 2 1 1 E-2C + 8 F-14Ds
LK-16/6-08M-032h
A – 8 – 10 19 3 1 1 E-2C + 4 F-14Ds
A – 8 – 10 19 4 2 1 E-3A + 8 F-15s
Figure 6-20. A stacked net is created by assigning the same time slots to the same
NPG with the same TSEC parameter, but with different net numbers.
*CH_6_2001 60 10/2/1, 5:33 PM

Stacked nets are often defined to the terminal with a net

number of 127. This indicates “no statement” or no
definition and allows the operator to specify a net number
during operations. If the cryptovariables of the stacked nets
are the same, an operator can “dial-a-net” by entering the
desired net number.
Stay on your assigned net.
Section I Multinetting 6-61
*CH_6_2001 61 10/2/1, 5:33 PM

LGN 135-02-002
Crypto Nets ■
Isolation between networks or between network users is
created by configuring the terminal’s cryptovariables with
different CVLLs. Only authorized users, those with the
correct TSEC and MSEC CV will be able to exchange
A group of JUs information. Crypto nets are created by assigning a different
can be isolated TSEC CVand/or MSEC CV to a group of users.
from other JUs by
assigning them a If the TSEC CV is the same and only the MSEC CV is
different MSEC different, unauthorized users can receive the signal, error
and /or TSEC CV. correct it, and retransmit it. But, they cannot decrypt it, and
this configuration of CVs is used to establish blind relays. The
net consisting of the participants with the correct MSEC is
sometimes referred to as cryptonet with CVLL = n, where n is
between 1 and 127. If the TSEC CV is different, unauthorized
users cannot even receive the signal. If both the TSEC and
MSEC are different, complete isolation is established.
Multiple Networks ■
Each network has Multiple networks have a different TSEC and a different
its own NTR. MSEC. Each network is independent of the other and has its
own NTR assigned. This complete isolation of networks
allows independent networks for each service to coexist
within the same OpArea.
*CH_6_2001 62 10/2/1, 5:33 PM

Section J
Range Extension
The most common method of extending JTIDS range beyond
line of sight (BLOS) is the employment of airborne relays.
This is not always feasible, however, due to the lack of
airborne assets or conflicting mission requirements. Several
means of employing satellite communications to extend the
range of TADIL J are under development as part of the Joint
Range Extension (JRE) program. None of them have yet been
certified for interoperability nor undergone operational
evaluation. Various connectivity devices have been developed
as well to support testing and training over landlines.
Satellite Range Extension ■

Satellite resources include Military Strategic and Tactical
Relay Satellite (MILSTAR), the UHF Follow-On (UFO), the
Defense Satellite Communications System (DSCS), and Fleet
Satellite (FLTSAT). These satellites provide communications
in three frequency bands: Ultra High Frequency (UHF), Super
High Frequency (SHF) and Extremely High Frequency (EHF).
UHF communications employ the WSC-3(V) radio, using the

Demand Assigned Multiple Access (DAMA) protocol on
5-KHz and 25-KHz channels, to exchange data at 2400 or LDR provides data
4800 bps. SHF communications employ the WSC-6(V) on rates of 75 bps
dedicated channels capable of operating at aggregate data rates to 2400 bps.
in excess of 64 Kbps. EHF communications employ the
AN/USC-38(V) Navy EHF SATCOM Program (NESP)
terminal. EHF satellite payloads support communications at MDR provides data
a low data rate (LDR) of 75 bps to 2400 bps, and a medium rates of 4800 bps
data rate (MDR) of 4800 bps to 1.544 Mbps. to 1.544 Mbps.
Section J Range Extension 6-63
CH6_63-70 3 10/2/1, 3:56 PM

LGN 135-02-002
■ STDL
The Satellite Tactical Data Link (STDL) was the first
implementation of satellite Link-16, and provides the means
for the Royal Navy of the United Kingdom to exchange
Link-16 tactical data using SHF satellite communications.
Three modes of operation are to be used: a network mode,
group mode, and broadcast mode. A TDMA architecture
permits participation by up to 16 transmitting Satellite Units
(SatUs) in the network mode, forwarding from an STDL
network to a Link-11 or JTIDS/Link-16 network by
Forwarding Satellite Units (FSatUs) in the group mode, and
transmission by one unit to other SatUs in the broadcast mode.
In the network mode, propagation and processing delays are
taken into consideration in order to synchronize satellite
transmissions with the SHF TDMA slot. Data rates up to an
aggregate of 19.2 Kbps are provided.
6-64 Section J Range Extension
CH6_63-70 4 10/2/1, 3:56 PM

■ S-TADIL-J
Satellite TADIL J (S-TADIL-J) is a Navy design for extending
the range of Link-16 using satellites. This capability has been
demonstrated in the Model 4 C2P, and will be implemented in
both the Model 4 and Model 5 C2P. It requires no
modifications to the tactical system. The C2P operates on
both the JTIDS network and the satellite concurrently.
Transmissions on the satellite are generally delayed with
respect to the JTIDS network, and data received from the
JTIDS network is given precedence by the C2P over data
received from the satellite. When a JU drops out, as evidenced
by no PPLI reception for 60 seconds, the C2P automatically
and “seamlessly” takes data for that JU from the satellite.
S-TADIL-J implements most of the J-series messages

although those required for network management, air control,
and national use are not implemented. It uses a token-passing,
round-robin network protocol, and employs the KG-84A
encryption device. KG-84A and compatible cryptos are used
for most standard serial data protocols. The net cycle time
associated with S-TADIL-J depends on the number of satellite
JUs (SJUs) and the number of tracks. Clearly, data rates over
satellite links at 2400 baud or 4800 baud are much lower than
conventional JTIDS rates, and data latency is a potential
problem. For example, a four-unit net exchanging information
on 180 tracks at 2400 baud is estimated to require 20 seconds.
There’s a token-passing switching delay estimated to be
2 seconds per unit. Higher data rates will become available,
however, as the EHF MDR satellite communications provided
by MILSTAR become operational.
CH6_63-70 5 10/2/1, 3:56 PM

LGN 135-02-002
■ JRE
JTIDS Range Extension (JRE) is the Army/Air Force
approach to extending Link-16 coverage across “zones” to
include multiple networks that cover an entire theater. Units
within LOS or connected by airborne relay or satellite and
employing the same network design, such as that described for
S-TADIL-J, define a zone.
JRE “gateways” will be associated with each zone, and

equipped with JTIDS terminals, EHF SATCOM terminals, and
application software to perform J-to-J forwarding. Protocols
to permit the connection of multiple zones by means of
satellites and these JRE forwarding “gateways” are under
development. Issues such as track block assignments within
and across zones, the impact on relative navigation of
forwarded PPLIs containing position and time quality
measurements that conflict with TOA measurements from the
transmitting unit, and how to perform receipt/compliance are
being identified and addressed.
CH6_63-70 6 10/2/1, 3:56 PM

S-TADIL-J
Model 4: 3Q ’98
Model 5: 1999
Joint Range
S-TADIL-J
Extension
Zone 1 Zone 2 . . . . . . Zone 8
Figure 6-21. S-TADIL-J and JRE, under development as part of the Joint Range Extension
(JRE) program, use satellite communications to extend the range of TADIL J beyond
line-of-site.
CH6_63-70 7 10/2/1, 3:56 PM

LGN 135-02-002
Connectivity Devices ■
Other methods of extending the JTIDS range currently in use
vary from wireline to unmanned aerial vehicles (UAVs) to
radios that employ tropospheric scattering! Several devices
have been specifically designed to provide serial connections
to “glue together” tactical systems at remote locations. These
systems employ serial interfaces and secure telephone lines.
They include:
■ Link-16 AEGIS Broadcast Network (ABN-16)

■ Multi-TADIL Distribution System (MTDS)
■ Gateway (GW)
■ Link-16 Data Terminal Set Simulator (DTSS-16)
■ Link-16 Data Distribution System (LDDS-16)
Each system implements a different protocol on its serial

interface. An effort to standardize this protocol has been
proposed and is known as the Standard Interface for Multiple
Platform Link Evaluation (SIMPLE).
■ ABN-16
ABN-16 is employed by the U.S. Navy to connect Link-16-

capable systems using dial-up telephone lines and Local Area
Networks (LANs). It is being enhanced to accommodate any
IP-based communications medium, such as ATM. It also has
an S-TADIL-J capability in which it emulates satellite
equipment between satellite JUs. Components of the ABN-16
function as a Local Terminal Interface Unit (LTIU), Local
Host Interface Unit (LHIU), Network Control Interface Unit
(NCIU), Remote Terminal Interface Unit (RTIU), or Remote
Host Interface Unit (RHIU) to provide connectivity among
geographically dispersed platforms. ABN-16 components are
CH6_63-70 8 10/2/1, 3:56 PM

located at ACC Dahlgren, ATRC Dahlgren, NSWC Dahlgren,

ACSC Wallops, CSEDS Moorestown, JHU/APL, NAWCAD
Patuxent River, NSWC-PHD Dam Neck, NCTSI San Diego,
Bath Ironworks, and the Litton Shipyard at Pascagoula, as
well as at sites in France and Japan that support naval systems
development and testing. Any site with the ABN-16 LCIU
equipment can act as the network hub.
■ MTDS
The MTDS acts as a networking device and forwarder. It
permits multiple units to share a single JTIDS terminal. The
connection is serial and implements a landline protocol known
as Serial J. The MTDS also can operate as a TADIL B
forwarder. The display shows the tactical situation and
provides throughput information on the active connections.
■ Gateway
The Link-16 Gateway is a connectivity device developed by
NRAD to provide Link-16 communications between
geographically separated facilities, enabling a greatly
expanded range of JTIDS/MIDS interoperability testing and
training. The Gateway system can be configured as a
Gateway Terminal Emulator (GTE), Gateway Host (GH)
emulator, or Gateway Monitor (GM). Gateway supports the
MIL-STD-1553b, X.25, and E-3 Boeing Serial data bus and
can be equipped with nine RS-232 interfaces. These RS-232
serial interfaces implement a proprietary protocol as well as an
open standard known as SIMPLE.
A TADIL J Host Simulator (TJHS) is also available which

provides a scripting capability for injecting simulated objects
into a tactical exercise features as well as capabilities to
configure, initialize, monitor and control various types of
MIDS and JTIDS terminals.
CH6_63-70 9 10/2/1, 3:56 PM

LGN 135-02-002
■ DTSS-16
The DTSS-16 is a connectivity device for extending Link-16

communications. It can act as a host, as a terminal, as a
monitor, or as a record/replay device. It implements all of the
terminal ICDs — Navy, F-15, Army Class 2M, and MCE —
as well as the MTDS Serial J. It is employed by the Services
as a data collection tool, to provide remote connectivity
between hosts and/or terminals in operational Link-16
networks, to support remote certification, and to verify fleet
readiness. It is also employed by developers to support host
and terminal software development.
■ LDDS-16
The LDDS-16 is a DTSS-16 with conferencing capabilities

added. Its eight serial interfaces permit multiple units to be
interfaced in up to four independent, simultaneous digital
Link-16 networks in a variety of configurations. It supports
two landline protocols with on-the-fly conversions. Multiple
LDDS-16s can be cascaded for large networks, with their
placement determined by phone line costs.
CH6_63-70 10 10/2/1, 3:56 PM

7
C
H
A
P
T
E
R
Link-16
Operations
Introduction
This chapter reviews the design goals of Link-16 and summarizes concepts relevant to
its operation. It illustrates some of the basic Link-16 operational concepts, primarily by
comparison with current Link-11 and Link-4A, and by describing the differences
between these other two tactical data links. For detailed Link-16 Standard Operating
Procedures, refer to the OPNAVINST C3120.43 series.
7-1
**CH7_2001 1 10/1/1, 6:24 PM

LGN 135-02-002
Section A
Design Goals
Link-16 was designed, and has been implemented in the
U. S. Navy, to satisfy particular goals. These include:
■ Autonomous operation
■ Maximum automation
■ Standardization
■ Backward implementation
Autonomous Link-16 Operation ■

The Link-16 message standard is designed to support the full
range of tactical information exchange requirements
necessary in the great majority of operational scenarios.
Ideally, a force should be able to operate quite sufficiently
using Link-16 as the sole means of external real-time tactical
communications, without reliance on voice or other forms of
external communications. This is the reason for the greatly
expanded volume of information that can be exchanged over
Link-16, as compared with the volume that can be
exchanged over Link-11.
7-2 Section A Design Goals
**CH7_2001 2 10/1/1, 6:24 PM

Maximum Automation ■
The Link-16 message standard, particularly the protocols for
data exchange, are designed to support maximum automa-
tion of tactical functions, such as engagement tactics and
combat decisions. This concept enables a system to be
designed such that operator burden can actually be reduced
over that required for operating on current Link-11. The
digital hand-over process is a good example of the concept
of maximum automation.
Standardization ■
A general policy of maximum standardization is reflected in
the Link-16 message standard in two important ways. First,
data element definition and employment is standardized to
the maximum feasible extent across the various warfare
areas (AAW, ASW, etc.). Second, Naval implementation of
all data items is standardized to the maximum appropriate
extent among all platforms. Such standardized implementa-
tion is intended to:
■ Promote interoperability between platforms and

services
■ Improve operator (including staff) cross-training
among participating ship types and classes
■ Greatly reduce the need for operators to learn
and accommodate differences between ships
operating together
■ Promote efficiency in the overall Naval system
design process — to facilitate, for example, the
introduction of the C2P.
Section A Design Goals 7-3
**CH7_2001 3 10/1/1, 6:24 PM

LGN 135-02-002
Backward Implementation ■
Systems which implement a Link-16 capability that is
equivalent to a Link-11 capability not currently implemented
will implement the Link-11 and Link-16 capabilities
simultaneously. Furthermore, some of the Link-16
capabilities that were not previously available in the Link-11
message standard are now, where feasible, being added to
Link-11. This concept clearly promotes multilink
interoperability, as well as cost-efficient system design.
AUTONOMOUS OPERATION
Ideally, no voice
MAXIMUM AUTOMATION
Ideally, hands-off operation
STANDARDIZATION
All ships and E-2C virtually identical
BACKWARD IMPLEMENTATION
Update Link-11 as Link-16 is implemented
Figure 7-1. Several concepts underlie the design of Link-16 and its
implementation in the U. S. Navy.
7-4 Section A Design Goals
**CH7_2001 4 10/1/1, 6:24 PM

Section B
Platform Identification,
Position, and Status
The installation of JTIDS/Link-16 in a wide variety of U. S.
and Allied platforms, many of which have no current tactical
data link capability, provides a greatly improved friendly
force location, identification, and status reporting capability.
The JTIDS terminals employ RELNAV techniques to
constantly fix their host platform’s position. The terminals
automatically transmit detailed positional and identification
data on Link-16 in PPLI messages at frequent intervals.
JTIDS-equipped platforms also provide detailed equipment

and ordnance status and inventory data to the JTIDS
terminal for periodic inclusion with the PPLI data. This
information allows the automatic compilation and display of
complete force status to operational commanders, as well as
selected unit status to appropriate operators — for example,
the Air Intercept Controller (AIC) of a JTIDS-equipped
aircraft.
Section B Platform Identification, Position, and Status 7-5
**CH7_2001 5 10/1/1, 6:25 PM

LGN 135-02-002
Section C
Surveillance
Surveillance consists of searching for, detecting,
identifying, and tracking objects which have tactical
significance to the Battle Group. These objects, which are
assigned a unique track number, include land points,
bearings, and fixes, as well as air, surface, and subsurface
contacts acquired from radar, IFF, sonar, and other sensors.
Automatic procedures exist to limit the reporting of a contact
to a single unit. This unit is said to have reporting
responsibility (R2) for the track. This minimizes the volume
of tracks reported, while allowing each unit to track all
contacts.
Track Reporting ■
The concept of track reporting on Link-16 is identical to that
of Link-11, with the new addition of land tracks. JUs
originate tracks and assume reporting responsibility (R2) for
Air, Surface, Subsurface, and Land Tracks using exactly the
same rules as current Link-11. Furthermore, in a multilink
force with both JUs and PUs, which communicate with each
other through a Forwarding JTIDS Unit (FJU), track
reporting is homogeneous within the entire force. Only one
Interface Unit (IU), either a PU or a JU, will have R2 for a
track at any given time.
7-6 Section C Surveillance
**CH7_2001 6 10/1/1, 6:25 PM

Link-16 is designed to support the concepts of cooperative
electronic warfare (EW) and data fusion. EW data is of two types:
parametric and product. Parametric data is the raw, unevaluated
EW intercepts and parameters received from systems such as the
SLQ-32 or LAMPS. These include data on fixes, areas of
probability (AOPs), and lines of bearing (LOBs). Product data is
evaluated data and normally means that an EW coordinator or
other qualified operator has evaluated the intercepts from one or
more participants and has developed a product which is deemed to
be of general tactical significance. Two different Network
Participation Groups (NPGs) support the exchange of EW data:
the EW NPG and the Surveillance NPG.
EW NPG
Parametrics
■ Fix, AOP, or LOB
Surveillance NPG
■ Frequency Product
■ Pulse Width ■ Track Number
■ Pulse Repetition Frequency Evaluation ■ Line of Bearing
■ Antenna Scan Period ■ Emitter Number
■ more ■ more
LK16/7-08M-065
Orders
Figure 7-2. Two NPGs support the distribution of EW parametric and

product data.
Section C Surveillance 7-7
**CH7_2001 7 10/1/1, 6:25 PM

LGN 135-02-002
To achieve cooperative EW, the EW NPG is intended for use

by all JUs that have a significant passive EW capability to
exchange detailed parametric data about EW detections,
including Electronic Support (ES) and Radio Direction
Finding (RDF) intercepts and Electronic Attack (EA)
jamstrobes. The intent is that all participants transmit
essentially raw (unevaluated) data direct from their passive
sensors onto the EW NPG. To achieve data fusion, certain
systems capable of processing large amounts of EW data
from various sources receive, correlate, and evaluate the
reported data and develop the EW “products” — that is, the
evaluated Lines of Bearing, the Areas of Probability, and
Fixes.
These evaluated products are then reported on the wide-area

Surveillance NPG to all participating JUs. Individual JUs
which have developed evaluations of their own EW sensor
data are not prevented from reporting evaluated product data
on the Surveillance NPG, if an operator selects an EW
product for such transmission.
The EW NPG also allows an EW Coordinator (EWC) to

coordinate and control the reporting of EW data by
selectively directing actions by participating JUs. Link-16
enables approximately 30 different EW Orders, only 15 of
which can be transmitted on Link-11.
**CH7_2001 8 10/1/1, 6:25 PM

Intelligence Information Reporting ■

Employed for years among most U. S. Armed Services,
although not by the Navy, the Link-16 intelligence reporting
capability is essentially identical to that of Link-11. For this
reason, Link-16 intelligence reporting, while not a new
capability, represents a new concept for the Navy.
The basic concept of data link intelligence reporting is to

amplify link-reported tracks, either realtime or non-realtime,
with tactical information gained by intelligence sources
through other than the traditional means of radar, sonar, and
ES. The information may be reported by any such source,
regardless of track reporting responsibility. Reportable types
of intelligence information are the detailed identification and
activity of the track, which can include hostile actions either
imminent, planned, or in progress. In many U. S. Navy ships,
this information is gained within the Ship’s Signals
Exploitation Space (SSES). It can also, however, be gained
and transmitted by a variety of other Navy, Joint, and Allied
sources. Acceptance of the intelligence information for
inclusion in track reports is at the discretion of tactical
operators, such as the Track Data Coordinator (TDC) or
ship’s ID Supervisor.
Section C Surveiilance 7-9
**CH7_2001 9 10/1/1, 6:25 PM

LGN 135-02-002
Lines and Areas ■

Link-16 provides a new capability to exchange lines and areas of
any geometric description. The lines and areas either may be
defined by a series of connected reference points, which are
referred to as multisided lines and areas, or they may be described
as regular circles, ellipses, squares, or rectangles centered on a
single point.
Regular AC001
(Defined by One-Point)
AC002
Multi-sided
02134 (Multiple Points)
Corridor (2 Lines)
Rectangle OP Area
(or Square)
12437
AE123
LK16/8-08M-066
Figure 7-3. The implementation of lines and areas allow JUs to share a
complete picture of the tactical theater of operations, including
geographic boundaries, operating areas, transit lanes, and other
geometric descriptions.
**CH7_2001 10 10/1/1, 6:25 PM

The purpose of this capability is to allow JUs to share a complete

picture of the tactical theater of operations, including geographic
boundaries, operating areas, restricted areas, air, surface, and
subsurface transit lanes (for example, air traffic control corridors),
ASW screen boundaries, and the like. Certain units will be
designated to enter the lines and areas of mutual tactical interest on
their displays and in their databases, and then to transmit them to
all JUs on the Surveillance NPG.
Data Filters ■
Data Filters may be employed to inhibit selected tracks from
transmission, to exclude them from track stores upon reception,
and to inhibit them from being forwarded. Filters may be required
to prevent the disclosure of protected data, or to prevent the
overload of an individual unit’s database, of the data link itself, or
even of the operator. Normally, filters are assigned either by
OPORDER, or in the OPTASK LINK before the link is initialized.
In view of both the high track density anticipated for modern and
future warfare and of the great numbers of JUs expected to
participate, a versatile filtering capability is a prerequisite for
participating in Link-16 operations.
This data filtering capability allows R2 to be partitioned according

to various combinations of geographic areas, track environment or
category, and track identity. Furthermore, the ordering and
reporting of filter insertion may be reported over the link, although
this capability will not be implemented for the U. S. Navy’s
Link-16 IOC. Preplanned filters will be assigned in the OPTASK
LINK, while others will be designed, ordered, and reported during
the course of operations, as situations dictate. Filters will normally
be ordered by, and reported to, the C2 JU designated to control
filters, normally the Track Data Coordinator (TDC). Filters ordered
and reported on Link-16 may also apply to Link-11 and to data
forwarding.
Section C Surveillance 7-11
**CH7_2001 11 10/1/1, 6:25 PM

LGN 135-02-002
Section D
Force Training
Link-16 fully supports the concept of “train the way you
fight.” Unlike Link-11, it has been specifically designed to
facilitate data link training and the use of data links in
exercises. Associated with all Link-16 track and EW product
messages are two special indicators: the Exercise Indicator
and the Simulation Indicator.
Exercise Tracks ■
The Exercise indicator signifies that a track is actually a
Friend acting as the link-reported Identity for the purpose of
the exercise. Friendly aircraft, ships, submarines, or emitters
providing opposition in exercises can be identified thereby
as Exercise Hostile (Faker), Exercise Suspect (Joker),
Exercise Assumed Friend, Exercise Unknown, or Exercise
Neutral. All other data normally reported for tracks, such as
Platform, Activity, and Specific Type, can also be reported
artificially for exercise tracks. Thus, an actually friendly
track can be fully identified, just as though it were a genuine
enemy track.
7-12 Section D Force Training
**CH7_2001 12 10/1/1, 6:25 PM

Simulated Tracks ■
Both Link-16 and Link-11 enable full training scenarios to
be conducted. Simulated tracks, based on simulated video,
are initiated with or without the presence of actual live
tracks. Both links allow the simulated video to be distributed
to all ships in a Battle Group. The Simulation Indicator
specifically identifies link tracks as simulated, not live. This
capability should also prove quite valuable during link
testing.
Section D Force Training 7-13
**CH7_2001 13 10/1/1, 6:25 PM

LGN 135-02-002
Section E
Air Control
Because only Link-4A will be implemented on many aircraft
and ships for several years after Link-16 IOC, Link-4A will
be retained after Link-16 becomes operational. However,
Link-16 will be used to control any JTIDS-equipped aircraft,
whether or not it is also equipped for Link-4A. A single
controlling unit can simultaneously control some aircraft on
Link-16 while controlling other aircraft on Link-4A.
Current Design ■
As currently planned, the Link-16 concept of air control
merely combines and expands the existing Link-4A air
control and the Link-11 air weapons coordination
capabilities. The J12 series of messages provides the same
mission assignment, vector discrete, uplink and downlink
target reporting, and control transfer capabilities as Link-4A,
although in each case the Link-4A capabilities are expanded
somewhat in Link-16. The Link-16 C2 to C2 capabilities for
digital handover requests, controlling unit (CU) reports,
engagement status reports, and pairing reports are virtually
identical to those of Link-11.
7-14 Section E Air Control
**CH7_2001 14 10/1/1, 6:25 PM

Link-16 provides more complete automation of air control

functions than Link-4A and Link-11. A prime example of
this is Link-16’s digital handover process. For handing over
a nonC2 JU aircraft between two C2 JUs, the entire handover
process is automated from the time the air controller in the
current controlling unit takes console actions to request the
new unit to assume control. The only unautomated
procedures are the manual WILCOs still required from the
new controlling unit and the aircraft. The newly automated
Link-16 handovers will normally require only a few seconds
to execute.
Air Control Enhancements ■

Under the original U.S. Navy Link-16 air control concept,
naval aircraft compiled their remote track picture in exactly
the same manner as on Link-4A. Controlling units uplinked
controller-selected targets of interest to the aircraft.
However, a major change to this Link-16 air control concept
was developed in the mid-1990s. It requires controlled
Link-16 aircraft to compile their own tactical picture by
monitoring the Link-16 Surveillance NPG, processing and
displaying reported remote tracks which meet criteria
selected and programmed in the aircraft, such as range,
heading, CPA, and identity. This change is necessary for
U.S. Navy units to be fully interoperable with aircraft and
controlling units of the United States Air Force and British
Royal Air Force which do not have Link-4A.
Section E Air Control 7-15
**CH7_2001 15 10/1/1, 6:25 PM

LGN 135-02-002
Third Party Direction of Handovers ■

Link-16 provides new capabilities for a third party, such as the
Area Air Defense Commander (AADC), to direct aircraft
handovers between two controlling units, and for a controlling
unit to request control of an aircraft from the current
controlling unit. These capabilities are conceived for use in
situations where a unit has no appropriate aircraft under its
control but is better situated than any other current controlling
units, due to positioning, radar capabilities, areas of
responsibilities, or the like, to control an engagement.
7-16 Section E Air Control
**CH7_2001 16 10/1/1, 6:25 PM

Section F
Special Functions
Special functions, such as the transfer of video imagery, may be implemented in
the future. The quality of an image depends on four factors: the size of the image,
whether it is color or gray-scale, the compression ratio, and the parameters of
the time slot assignment. These time slot parameters will specify whether parity is
employed, whether the data is unencoded or encoded, what the packing structure is,
and how many slots are assigned to the transmitting unit.
The standard commonly employed for images is known as JPEG — Joint Photo-
graphic Experts Group. This standard, which typically achieves a compression ratio
of 25:1, works with either color or gray-scale. Full color requires 16 bits per
pixel; gray-scale requires 8. As an example of the calculation methodology, consider
a single gray-scale image that is 640 x 480 pixels. How many time slots would be
required to send this image? Calculate the amount of binary data (640 x 480 x 8 =
2,457,600 bits) and divide by the compression ratio (2,457,600 ÷ 25 = 98,304 bits).
If the data is sent encoded, without parity, with a P2DP packing structure, 450 bits
per time slot are available. This requires just over 218 time slots. There are 128 time
slots per second. If 96 of them were assigned to a single unit as an imagery backlink,
for example, it would take about 2 1/4 seconds to transfer the entire image.
The international standard employed for video is known as MPEG — Motion Picture
Equipment Group. MPEG uses an interframe method, which compresses the differ-
ences between frames. This method has a typical compression ratio of 150:1. To
estimate how many frames per second (fps) JTIDS could support, assume that the
data is sent R-S encoded, without parity, with a P4 packing structure. This allows
900 bits per time slot. Allocation of 768 time slots per JTIDS 12-second frame
would support a data rate of 57.6 kbps. With a 150:1 compression ratio, this is 3.5
fps for a 640 x 480 gray-scale image and 16.5 fps for a 256 x 256 gray-scale image.
Section F Network Management 7-17
**CH7_2001 17 10/1/1, 6:25 PM

LGN 135-02-002
Section G
Network Management
The Area Air Defense Commander (AADC) is responsible for
monitoring force composition and geometry and for maintain-
ing proper network configuration. Ship COs and aircraft
Mission Commanders, under the AADC’s direction, may
modify operating parameters appropriate to mission changes.
The AADC designates an Interface Control Officer (ICO) to
maintain successful, continuous data exchange on the operat-
ing Link-16 network. The ICO function may be assigned to
any surface C2 JU. The ICO may designate a TADIL J
Manager to manage Link-16 for him in complex multilink
networks. The ICO is referred to as the Joint ICO (JICO) in a
U. S. Joint interface not including Allied units.
Management of the operating Link-16 network, as performed

The ICO plans by the ICO, consists of those actions needed to dynamically
and manages the establish, maintain, and terminate Link-16 communications
multi-TADIL among net participants. He must also be ready to take action
interface. to accommodate a changing operational environment. In
conducting the functions of network control and coordination,
the ICO must monitor force composition, geometry, proper
network configuration, and multilink requirements, as well as
perform general link administration. His actions can include
assigning network roles to specific units, activating and
deactivating relays, changing Interference Protection Feature
(IPF) settings, and changing the active-or-data-silent status of
a JU. He must, for example, ensure that a sufficient number of
JUs transmit initial entry messages to support net entry.
7-18 Section G Network Management
**CH7_2001 18 10/1/1, 6:25 PM

One of the tools employed by the ICO to manage the multi-

TADIL network is the Link-16 Management System (LMS-16).
LMS-16 ■
The LMS-16 acquires Link-16 data via the MIL-STD-1553
data bus from an instrumented JTIDS receiver. It provides
both signal and tactical information about the performance of
the multi-TADIL network.
Signal measurements provide the ICO with information about

packing structure, noise and interference, and range based on
actual RF propagation time. Both direct and relayed transmis-
sions are processed, permitting assessment of relay perfor-
mance. The performance of TADIL A and B units is reflected
by the JTIDS messages transmitted by their forwarder.
Network utilization measurements verify that units have the

correct network load, have entered the proper option and
sequence numbers, and have sufficient capacity for their trans-
mission requirements. The JNL network design may be graphi-
cally displayed and compared with actual usage. Time slot
usage is updated in realtime and may be referenced back to the
actual JNL platform loads to determine who actually transmit-
ted, who is assigned to transmit, who is assigned to receive, and
who is assigned to relay.
The ability of the LMS-16 to synchronize on transmissions

other than the first one in the time slot permits the ICO to
detect unintentional contention access due to incorrect platform
initialization and to verify IEJU transmissions of the J0.0 net
entry message. The Time Slot Duty Factor is calculated for
each JU and for the network as a whole, taking into account the
contention transmissions of multiple, authorized relayers.
Section G Network Management 7-19
**CH7_2001 19 10/1/1, 6:25 PM

LGN 135-02-002
Tactical data displayed by the LMS-16 provides situational

awareness and historical trends. Tracks may be color coded
by age, by ID, or by reporting unit with or without their
history. Color coding by reporting unit makes R2 battles and
dual designations immediately and clearly visible. The ICO
may scroll received messages, filtering them by NPG, by JU,
by Track Number, and/or by message label. Messages are
automatically logged for postmission data analysis. Four
track data readout windows are provided for hooking and
comparing track information. Expert system software auto-
matically detects anomalies and logs alerts for the ICO.
An overview display maintains information on the distribu-

tion of the current track load by ID and by category. It
identifies which units are transmitting PPLIs and how many,
which are being forwarded from TADIL A/B and by whom,
which units have active sensors and the number of tracks they
are reporting, and which units are actively relaying data and
how much.
The LMS-16 With this information, the ICO can proactively manage the
provides multi-TADIL network to ensure reliable and complete connec-
information the tivity among all participants. Supported by the hardcopy and
ICO needs to replay capabilities of the LMS-16, the ICO can make presenta-
manage the tions on network performance at hot washes and debriefings.
Link-16 network.
A special version of the LMS-16 software is available that
permits the LMS-16 to connect to a Navy Class 2 JTIDS
terminal as either a host or as a bus monitor.
7-20 Section G Network Management
**CH7_2001 20 10/1/1, 6:25 PM

Appendixes
Appendix A
Multilink Operations
This appendix describes the simultaneous operation of Link-11 with Link-16. It focuses
on the methods by which units operating on Link-11 and units operating on Link-16 will
interoperate across both links while maintaining a common, cohesive tactical picture.
Such a multilink community is truly an integrated, single, united data link community,
sharing a common tactical picture. In fact, in any operational unit which has both
Link-11 and Link-16, the link or links on which the unit is operating should be transparent
to most operators.
A-1
**app_A_2001 1 9/21/1, 1:36 PM

LGN 135-02-002
Section A
Data Forwarding
Data forwarding is the process of receiving data on one
digital data link and outputting the data onto another digital
data link in the proper format. In the process, messages
received on one link are translated to appropriate messages
on the other. Applicable data fields within the messages are
translated to the appropriate data fields in the corresponding
messages. There is not always a one-to-one correspondence
between messages; for example, multiple messages on one
link sometimes translate into a single message on another
link. All Link-11 data can be translated and forwarded to
Link-16; however, approximately half of the data originated
on Link-16 either cannot be forwarded to Link-11 or will be
degraded (lose specificity) in translation.
The term multilink operations is used to describe operations

in which both Link-11 and Link-16 operate and data is being
forwarded between them. A force employing both Link-11
and Link-16 for tactical data exchange, therefore, is referred
to here as a multilink force. Data forwarding allows as
much tactical information as possible to be shared by all
members of a multilink force.
A-2 Section A Data Forwarding
**app_A_2001 2 9/21/1, 1:36 PM

Appendixes
The Forwarding JU ■
A unit which performs the data forwarding function for a multilink
force is referred to as a Forwarding JTIDS Unit (FJU). Any ship
with a Command and Control Processor (C2P) can
perform the data forwarding function. In fact, the C2P is the only
U. S. Navy system capable of performing the FJU function. The
C2P will be installed in all shipboard platforms.
JU JU
FJU
PU
ork
e tw
1N
k-1 Link-16 Network
Lin
Net 3
PU Net 2
PU Net 1
Net 0
JU
LK16/A-08M-
067
Figure A-1. The U. S. Navy FJU forwards data between the Link-11 PUs
and the Link-16 JUs, in both directions. It is a participant on both links.
Section A Data Forwarding A-3
**app_A_2001 3 9/21/1, 1:36 PM

LGN 135-02-002
Units that forward data between Link-16 and Link-11

(TADIL A) are sometimes referred to as FJUAs. Those that
forward TADIL B data are known as FJUBs. Navy FJUs are
always FJUAs, and the acronym FJU is used throughout this
appendix to mean FJUA. Navy units may receive data
forwarded from TADIL-B reporting units through an FJUB.
It is also possible to receive TADIL-B (Link-11B) from a
Link-11 Forwarding PU (FPU), which forwards data directly,
without translation, between Link-11 and Link-11B, since
these two links use the same messages.
The Alternate FJU ■

The major drawback to using an FJU is that continuous
multilink interoperability between JUs and PUs is highly
dependent on the assigned FJU’s ability to remain
continuously operational on both links. The FJU, therefore,
becomes a node in our previously nodeless architecture. The
potential loss or degradation of multilink interoperability can
be minimized, however, and perhaps avoided completely, by
assigning another unit as an Alternate FJU. This unit can
assume the FJU duties rapidly upon losing the primary FJU.
Toward this end, all C2Ps are programmed with an Alternate

FJU mode. When assigned as Alternate FJU, the unit will
monitor both links to determine when the FJU becomes
inactive on either link. During this time, it will actually
participate on only one of the links. When the program
detects that the FJU has become inactive, an operator at the
Alternate FJU will immediately be alerted to allow
expeditious transfer of the FJU function.
**app_A_2001 4 9/21/1, 1:36 PM

Appendixes
Multiple FJUs ■
Generally, only one unit should be assigned the role of FJU
between any two links to prevent the possibility of data
being transmitted over redundant paths. Having mentioned
this, however, we now discuss two situations in which more
than one FJU is needed. Multiple FJUs are needed when
■ No single FJU-capable unit is located within range

of all Link-11 units and all Link-16 units, or
■ Link-16, Link-11, and TADIL B are all interfaced,

sometimes requiring at least one FJUA and one
FJUB.
Careful planning is needed whenever more than one FJU is

assigned.
**app_A_2001 5 9/21/1, 1:36 PM

LGN 135-02-002
■ Forwarding for Distance

It may be necessary to assign more than one FJU for an
NPG, or for all NPGs, solely as a result of distance
considerations. It may simply be the case that no single
FJU’s transmissions can reach all Link-11 and Link-16
participants. In this case, multiple FJUs must be assigned
forwarding responsibility for messages from, or addressed
to, mutually exclusive subsets of PUs and JUs. A possible
scenario requiring more than one FJU might be one in which
two or more naval Battle Groups are operating within HF
range of each other, but outside the JTIDS range without an
airborne relay. The individual units of the Battle Groups
could be intraconnected by Link-16, and by Link-11 if
necessary, but could also be interconnected, one Battle
Group to another, through multiple FJUs.
**app_A_2001 6 9/21/1, 1:36 PM

Appendixes
PU 02
PU 04
PU 01 PU 03
JU 01
FJU 1
JTIDS Network 1
JU 10
HF Link-11 No. 1
JU 03 JU 02
PU 05
JU 13 JU 11
JU 05
FJU 2
PU 33
HF Link-11 No. 3
JTIDS Network 2
PU 20
JU 25
JU 20
FJU 5 PU 12
JU 12
FJU 3
JTIDS Network 3
HF Link-11 No. 2
PU 17
JU 17
FJU 4 LK16/A-08M-068
Figure A-2. When an airborne relay is not available, multiple FJUs operating on HF Link-11
can connect two or more Battle Groups that are out of UHF range.
**app_A_2001 7 9/21/1, 1:36 PM

LGN 135-02-002
■ Forwarding for TADIL B
U.S. Navy FJUs Since the U. S. Navy’s FJUs cannot forward to or from
cannot forward TADIL-B units, it will normally be necessary to assign some
for TADIL B. combination of other services’ FJUBs and FPUs to forward
messages between their TADIL B Reporting Units (RUs),
Link-16, and Link-11. When these links are operating
together, the necessity of assigning multiple forwarding units
can be avoided only when a non-naval unit is available that
can forward messages for all three links. Such a unit is
known as a FJUAB.
RU
AAAA AAA
AAAAAAAAA
RU
AA
AA
AAA
AAAAAAA
JU
AAAA
AAAA AA
AA AAA
AAA
JU
AAAAA
AA JU
AAAA AAAA AAAA AAAA

RU
FJUB
AA
AA AA
AAAA AA RU
AA
JU
AA
JU
AA AAA
AA
AA
AAAA AAA AA
AAA
AA AAAAAA AAAA
AAA AA
AAAA
AAAA
AAAAAAAAA
AAAAA
AAAAAAAAA AAA
AAA AAAAAA
AAA AA AAA
AAAA AAA
AAA
AA
AAAA
FJUAB
AAA
AA
AAAA
AA AAA AAAA
AAAAAA
AAA
AAA AAAA
JU JU
FJUA PU
AAAAAAA
AAAA
AAA A AAAAA AA AA
PU
AA
AA AAA AA
AA AA
AA
AA
AA
AA AA AA AA
AAA
AAA AA
AAA
AA AAAA
AAAAA AAAAA
AAA
AAAAAA AAA
AAA AAAAA AAAA
AAA PU
LK16/A-08M-
PU
AAAAAAAAAAAA AAAAAAA
AAAA
PU
069
PU
Figure A-3. Multiple FJUs may be necessary to forward data between Link-16, Link-11, and
TADIL B...unless an FJUAB from another service is available.
**app_A_2001 8 9/21/1, 1:36 PM

Appendixes
Data Forwarding Filters ■

Recall that Link-16 has a higher data rate and allows the
reporting of much more tactical information than Link-11.
There would appear to be a high risk of saturating Link-11,
or of greatly increasing its net cycle time, if all translatable
Link-16 messages are forwarded. In most scenarios, this will
not necessarily be the case. Link-16 tracks are normally
updated at approximately the same time interval as Link-11
tracks. Also, some of the extra data on Link-16 is not
translatable, and therefore will not affect Link-11.
Nevertheless, a potential for saturating Link-11 with
forwarded data remains. Therefore, all FJUs have extensive
capabilities for inhibiting certain translatable messages from
being forwarded.
The FJU’s filtering of forwarded data is under operator

control. Filtered data will be forwarded only when link
loading conditions and the tactical situation dictate that this is
necessary and feasible. Navy FJUs can filter forwarded data
just as they can filter their ownship data from transmission on
each link. Data can be filtered on the basis of Environment/
Category (including EW and Reference Points), Identity, and
Geographic Area, as well as on the basis of Exercise,
Simulation, and Special Processing Indicators.
Some forwarded data, however, cannot be filtered. Data on

PUs, RUs, and C2 JUs, Emergency and Force Tell alerts,
commands, engagement status, handovers, controlling unit
reports, pairings, and track management messages are
examples of data which cannot be filtered.
**app_A_2001 9 9/21/1, 1:36 PM

LGN 135-02-002
Section B
Concurrent Operations
If perfect connectivity could be maintained at all times
between all units of a multilink force, and if the FJUs could
always remain fully operational, there would be no need for units
to operate on more than one link at a time. In this ideal world,
Link-16 and multilink-capable units would operate only on
Link-16, and units having only Link-11 would maintain
interoperability through an FJU. Only the FJU would need to
operate on both Link-11 and Link-16.
Normal OPS
JU
Link-16 Network
Net 3
Net 2
Net 1 FJU PU
Net 0
JU
LK16/A-08M-071a
Figure A-4. If perfect connectivity could be maintained at all times, only

the FJU would need to operate on both Link-11 and Link-16.
A-10 Section B Concurrent Operations
**app_A_2001 10 9/21/1, 1:36 PM

Appendixes
The world is not perfect, however, and perfect connectivity A Concurrent

with continuous operations by FJUs is improbable. The USN Interface Unit
has planned for this reality and developed the concept of (CIU) operates on
concurrent operations (CONCOPS), in which units may both Link-11 and
be active on both Link-11 and Link-16 concurrently even Link-16, but does
when they are not a data forwarder. CONCOPS is undergo- not forward data.
ing testing by USN and is not to be used in operational inter-
faces until testing has proved its validity and effectiveness
and it is authorized for use. A unit which operates on both
Link-11 and Link-16, but is not an FJU, is called a Concur-
rent Interface Unit (CIU).
CONCOPS can be conducted with or without the presence of

an FJU. When the FJU is directly interfaced to the host CONCOPS is
Combat Direction System (CDS) in its platform, the host a future mode
CDS must operate as both a PU and a JU, and is thus a form of operation.
of CIU. The Navy C2P is capable of CONCOPS.
CIU
CIU
Link-11 FJU Link-16
CIU
LK16/A-08M-070
Figure A-5. FJUs and CIUs operate on both links simultaneously. The
existence of one or more CIUs can greatly expedite the transfer of the
FJU function.
Section B Concurrent Operations A-11
**app_A_2001 11 9/21/1, 1:36 PM

LGN 135-02-002
Rules for CONCOPS ■

To prevent data looping — the forwarding of forwarded data in an
endless circle — several rules are established for CIUs and FJUs.
CIUs transmit and receive all data directly, not through a data for-
warder. Thus, the direct path merely replaces the indirect path
which exists when a unit transmits and receives on only one link
and its data are forwarded to the other link.
The following rules ensure that only the direct path is followed:
■ FJUs do not forward any data received from a CIU, nor

any data specifically addressed to a CIU. If the FJU cannot
comply with this rule, CONCOPS must not be conducted.
■ CIUs discard forwarded data.
■ CIUs receive tactical data from other CIUs on Link-16

only.
■ CIUs receive tactical data directly from PUs on Link-11

and from JUs on Link-16.
■ CIUs receive tactical data from TADIL-B Reporting Units

(RUs) on Link-16 only.
■ When a CIU originates a track or assumes Reporting

Responsibility (R2) for a track, it always has R2 on both
links. The only exception would be whenever a link trans-
mit filter exists on one link, but not on the other. Also, if
the CIU originates the track, it always assigns the same
TN on both links, with a leading zero preceding the sig-
nificant digits of the Link-16 track number (TN).
A-12 Section B Concurrent Operations
**app_A_2001 12 9/21/1, 1:36 PM

Appendixes
Concurrent OPS
CIU
Link-11 Network
Net 3
Net 2 FJU PU
Net 1
Net 0
(Does not forward CIU data)
JU
LK16/A-08M-071
Figure A-6. CIUs transmit and receive all data directly, rather than through
a data forwarder.
Concurrent Operations
Advantages Disadvantages
■ Expedites FJU shifts ■ Slightly increases Link-11
overhead
■ Increases unit availability
■ Brief data loss when CIU
■ Enhances data specificity loses one link
■ Avoids some multilink problems

LK16/A-08M-073
Figure A-7. Concurrent Operations (CONCOPS) offers several advantages,

but not without slight disadvantages.
Section B Concurrent Operations A-13
**app_A_2001 13 9/21/1, 1:36 PM

LGN 135-02-002
Section C
Multilink Functions
The message standards of both Link-11 and Link-16 include
numerous protocols for conducting various tactical functions
over a data link. The primary functions which are performed
over a tactical data link include:
■ Assigning track numbers and reporting

responsibilities
■ Allocating track block numbers
■ Resolving information differences
■ Requesting data updates
■ Coordinating the use of weapons
■ Controlling aircraft
■ Reporting platform status
■ Reporting EW data
The functions and protocols contained in the message

standards apply equally throughout any data link community.
It matters not whether all participants are on Link-11, whether
all are on Link-16, or whether a multilink community is
composed of participants on both links. This section explains
briefly how these functions are achieved in a multilink
community. The list is by no means complete, and is intended
only to illustrate the means by which a cohesive tactical
picture will be maintained in a multilink force.
A-14 Section C Multilink Functions
**app_A_2001 14 9/21/1, 1:36 PM

Appendixes
Track Number Block Allocation ■

The octal Link-11 Track Numbers (TNs) range from 1 to
7777. The Link-16 TNs include octal numeric values between
1 and 77777 as well as alphanumeric values between 0A000
and ZZ777. To provide multilink interoperability, a JU may
be allocated up to three different noncontiguous blocks of
TNs: The Low TN Block, the High TN Block, and the Data
Forwarding TN Block.
■ Low TN Block
The Low TN block is limited to TNs less than 07777, which
by definition includes all Link-11 TNs. Low TNs are used
for originating tracks on Link-11, with the leading zero
removed, as well as on Link-16.
■ High TN Block
The High TN block includes all TNs greater than 07777. It
consists of the numeric TNs 10000 - 77777 and the alphanu-
meric TNs 0A000 - ZZ777. These TNs are used only to
originate tracks on Link-16. They will normally be allocated Only the FJU will
only for “overflow” purposes; that is, they will be used only see both low and
when all allocated Low TNs are in use. Furthermore, during high TNs.
the early years of Link-16 operations, it is anticipated that
every effort will be made to avoid allocating these High TNs
at all, to simplify interoperability between PUs and JUs.
Section C Multilink Functions A-15
**app_A_2001 15 9/21/1, 1:36 PM

LGN 135-02-002
■ Data Forwarding TN Block

The block of Low TNs allocated specifically for data
forwarding is referred to as the Data Forwarding (DF) TN
block. These TNs are used by the FJU only when the
received Link-16 TN is a High TN. If the received Link-16
TN is a Low TN, it is used with the leading zero removed in
the forwarded track report. However, if it is a High TN, the
FJU will associate a Low DF TN in order to forward the
track to Link-11. The Alternate FJUs must know the DF TN
block allocated to the FJU.
Low TN High TN DF TN
Value 07777 or less 10000-77777 07777 or less
0A000-ZZ777
Purpose Track origination Track origination Data forwarding

on Link-16 or on Link-16 of high TNs to
Link-11 Link-11
(with leading zero
omitted)
LK16/A-08M-074
Figure A-8. Because of differences between link capabilities, a JU

operating in a multilink force may be allocated track numbers
(TNs) in three different, noncontiguous blocks.
**app_A_2001 16 9/21/1, 1:36 PM

Appendixes
R2 and Common Track Number ■

The unit reporting a particular track is said to have Reporting
Responsibility (R2). It is the objective of the R2 rules to
have only one unit of the force report a particular track,
while all others withhold their reports. Because the length of
the Track Number field used in Link-11 is shorter than that
used in Link-16, special provisions are necessary to achieve
this objective in a multilink force.
All Link-11 TNs can be used on Link-16 by the addition of a

leading zero, but not all Link-16 TNs can be used on Link-11.
When the Link-16 TN is less than 07777, that TN is used on
both links and is known as the Common TN (CTN).
Limit Link-16 TN block allocations to Low

TNs if possible.
**app_A_2001 17 9/21/1, 1:36 PM

LGN 135-02-002
3
Air Track TN = AB02
Air Track TN = 7001
PU FJU AB023 = 7001 JU
LK16/A-08M-072
Figure A-9. The FJU uses its DF TN block to forward tracks with Link-16 High TNs to
Link-11. The FJU reports this associated “CTN” to Link-16 for use in voice coordination.
When a given When the Link-16 TN is greater than 07777, however, the
track is assigned FJU associates a new TN with it for use on Link-11. This
different TNs on process is called TN association. The FJU must insert the
Link-11 and Link-16 TN into all subsequent messages concerning this
Link-16, the track when they are forwarded from Link-11, and insert the
Link-11 TN will Link-11 TN into all messages when they are forwarded from
be used as the Link-16. The TN for Link-11 is taken from the block of DF
CTN in all voice TNs assigned to the FJU specifically for TN association. At
communications. the same time, the FJU generates a message informing all
Link-16 JUs of the associated Link-11 TN. This Link-11 TN
will be used as the CTN in all voice communications. In the
future, all PUs may be able to receive and display the High
TNs, and then the Link-16 TN will become the CTN.
To preclude the need for TN association, it is preferable, if

possible, to limit TN allocations throughout a multilink force
to TNs less than 07777. In this manner, each track will be
assigned only a single TN, and the potential for confusion
can be avoided.
**app_A_2001 18 9/21/1, 1:37 PM

Appendixes
Resolving Information
Differences ■
Resolving information differences ensures that all units of
a multilink force hold the same Environment/Category and
Identity for any given track. To achieve this objective, the
protocols of the two links for resolving information
differences are virtually identical.
Data Update Requests ■

Any unit requiring an update on data of various types
currently being reported throughout the multilink force can
issue a Data Update Request (DUR). This request will be
forwarded to the other link by the FJU. Units currently
reporting data of the requested type, regardless of the link
upon which they are operating, will respond with updated
reports. Link-16 allows isolating DURs to specific subsets
of data, whereas Link-11 DURs essentially request all data
which is not transmitted on a periodic basis.
**app_A_2001 19 9/21/1, 1:37 PM

LGN 135-02-002
Weapons Coordination ■
All engagement status reports will be forwarded by the FJU.
Thus, all units of a multilink force will have a common pool
of knowledge upon which to base engagement decisions and
resource allocation. All Command orders will also be for-
warded, even if the addressee is on the same link as the origi-
nator of the Command. This redundancy ensures that the
Composite Warfare Commander (CWC) and all warfare area
commanders are aware of all orders that have been issued.
Aircraft Control ■
All reports which identify the controlling unit of controlled
aircraft will be forwarded by the FJU. Requests for handover
of aircraft control will be forwarded whenever the addressee
is on a link other than the one on which the originator of the
request is operating.
Platform Status Reporting ■

All JUs continually report their position and status on
Link-16, offering a greatly improved picture of friendly
status over that provided by Link-11. All Link-16 fighter and
attack aircraft position and status reports will be forwarded
onto Link-11 as friendly air tracks and friendly status
reports, respectively, regardless of whether the aircraft are
under control of a data link unit. Although a considerable
volume of the status data will not be translatable to Link-11,
the multilink force shares a much more complete and
cohesive picture of the status of friendly forces than is the
case with a force that employs Link-11 only.
**app_A_2001 20 9/21/1, 1:37 PM

Appendixes
All Link-11 electronic warfare (EW) data is always forwarded
to Link-16, but not all Link-16 EW data is forwarded to
Link-11. The problem of possibly saturating Link-11 with
detailed parametric EW data has been recognized for a long
time. Because of its comparatively slow data rate, Link-11 is
not used for EW data exchange to any great extent. The
J-series message standard allows reporting considerably
more EW data on Link-16 than can be reported on Link-11.
Because of the potential for overloading Link-11 by
forwarding to it all Link-16 EW data, all FJUs are capable of
operating in either of two EW data forwarding modes:
■ Product Mode
■ All Mode.
In the Product Mode, only the Link-16 EW product

messages are forwarded. In the All Mode, all Link-16 EW
data is forwarded. In the Product Mode, therefore, the
multilink force is not truly an integrated multilink force.
EW-capable PUs will not receive the raw EW data from
Link-16 until it has been evaluated. For this reason, when it
is necessary to operate in the EW Product Mode, the EW
Coordinator must always be aboard a unit that is operating
on Link-16.
Ensure that the EW Coordinator is aboard a

Link-16-capable platform when using the
Product Mode of EW data forwarding.
**app_A_2001 21 9/21/1, 1:37 PM

Appendix B
Link-16 Platforms
This appendix contains a list of all Joint and Allied Link-16 Platforms. Names and hull
numbers are provided for United States Navy units expected to become Link-16 capable.
In this appendix, units designated with an asterisk (*) are NonC2 JUs. Others are C2 JUs.
Appendix B Link-16 Platforms B-1
LK16 app B_2001 1 9/24/1, 8:40 AM

LGN 135-02-002
Platforms of Allied Nations ■

France
Air Force
E-3 Sentry AWACS Aircraft
STRIDA Air Defense Ground Environment
*“Rafale” Fighter/Attack Aircraft
Army
NC3 and NC2 Operations C2 Centers
NC1 SAM and SHORAD Control Stations
Various other command posts and control stations
Navy
Aircraft Carrier (CVN) Charles De Gaulle
Cassard-Class AAW Frigates
New Generation (or “Project Horizon”) AAW Frigates
E-2C AEW Aircraft
Germany
Air Force
*EF-2000 European Fighter Aircraft (EFA)
B-2 Appendix B Link-16 Platforms
LK16 app B_2001 2 9/24/1, 8:40 AM

Appendixes
Italy
Air Force
Air Command and Control System (ACCS) Sites
MRCS 403 Mobile Control and Reporting Center
*Tornado Air Defense Aircraft
*Tornado Fighter Bomber Aircraft
*AMX Multipurpose Aircraft
*EF-2000 European Fighter Aircraft
Army
*Air Defense Artillery Sites
Navy
Cruiser Garibaldi
Maestrale-Class Frigates
*EF-101 and NFH-90 Helicopters
NATO
E-3 AEW Aircraft
Spain
Air Force
Air Command and Control System (ACCS) Sites
*F/A-18 Hornet Fighter Aircraft
LK16 app B_2001 3 9/24/1, 8:40 AM

United Kingdom
Air Force
UK Air Defense Ground Environment (UKADGE) System
E-3 Sentry AWACS Aircraft
*Tornado Air Defense Version Fighter Aircraft
Navy
CVSG Aircraft Carriers
Type 42 AAW Destroyers
*Sea Harrier (SHAR) Aircraft
United States
Air Force
Modular Control Element (MCE)
E-3 Sentry Airborne Warning and Control System (AWACS)
Aircraft
E-8 Joint Surveillance Target Attack Radar System (JSTARS)
Aircraft
Airborne Command, Control, and Communications (ABCCC)
Aircraft
Mobile Air Operations Center (MAOC)
*F-15 Eagle Fighter Aircraft
LK16 app B_2001 4 9/24/1, 8:40 AM

Appendixes
Army
Forward Area Air Defense (FAAD) System
Patriot, Theater High Altitude Area Defense (THAAD)
Joint Tactical Ground Systems (JTAGS)
Corps Surface-to-Air Missile (Corps SAM)
Army Theater Missile Defense Tactical Operations Center
(AMTD TOC)
Marine Corps
Tactical Air Operations Module (TAOM)
Advanced Tactical Air Control Center (ATACC)
*F/A-18 Hornet Fighter Aircraft
Navy
Aircraft Carriers
California-Class Cruisers
Ticonderoga-Class Cruisers (beginning with CG-52)
Kidd-Class Destroyers
Arleigh Burke-Class Destroyers
Wasp-Class Amphibious Assault Ships
E-2C AAW Aircraft
*F-14 Tomcat Fighter Aircraft
*F/A-18 Hornet Fighter Aircraft (MIDS)
USN Shipboard Platforms ■

The U.S. Naval vessels slated to receive Link-16 are presented
in two tables. The first table is organized alphabetically by
name. The second table is organized by hull number for each
platform type.
LK16 app B_2001 5 9/24/1, 8:40 AM

LGN 135-02-002
Hull Hull
USS USS
Number Number
ABRAHAM LINCOLN CVN 72 JOHN S. McCAIN DDG 56

ANTIETAM CG 54 KEARSARGE LHD 3
ANZIO CG 68 KIDD DDG 993
ARKANSAS CGN 41 KITTY HAWK CV 63
ARLEIGH BURKE DDG 51 LASSEN DDG 82
BARRY DDG 52 LABOON DDG 58
BATAAN LHD 5 LAKE CHAMPLAIN CG 57
BENFOLD DDG 65 LAKE ERIE CG 70
BONHOMME RICHARD LHD 6 LEYTE GULF CG 55
BOXER LHD 4 MAHAN DDG 72
BULKELEY DDG 84 McFAUL DDG 74
BUNKER HILL CG 52 MILIUS DDG 69
CALIFORNIA CGN 36 MISSISSIPPI CGN 40
CALLAGHAN DDG 994 MITSCHER DDG 57
CAPE ST GEORGE CG 71 MOBILE BAY CG 53
CARL VINSON CVN 70 MONTEREY CG 61
CARNEY DDG 64 NIMITZ CVN 68
CHANCELLORSVILLE CG 62 NORMANDY CG 60
CHANDLER DDG 996 O’KANE DDG 77
CHOSIN CG 65 OSCAR AUSTIN DDG 79
COLE DDG 67 PAUL HAMILTON DDG 60
CONSTELLATION CV 64 PHILIPPINE SEA CG 58
COWPENS CG 63 PORT ROYAL CG 73
CURTIS WILBUR DDG 54 PORTER DDG 78
DECATUR DDG 73 PRINCETON CG 59
DONALD COOK DDG 75 RAMAGE DDG 61
DWIGHT D. EISENHOWER CVN 69 RONALD REAGAN CVN 76
ENTERPRISE CVN 65 ROOSEVELT DDG 80
ESSEX LHD 2 ROSS DDG 71
FITZGERALD DDG 62 RUSSELL DDG 59
GEORGE WASHINGTON CVN 73 SAN JACINTO CG 56
GETTYSBURG CG 64 SCOTT DDG 995
GONZALES DDG 66 SHILOH CG 67
HARRY S. TRUMAN CVN 75 SOUTH CAROLINA CGN 37
HIGGINS DDG 76 STETHAM DDG 63
HOPPER DDG 70 STOUT DDG 55
HOWARD DDG 83 THE SULLIVANS DDG 68
HUE CITY CG 66 THEODORE ROOSEVELT CVN 71
INDEPENDENCE CV 62 VELLA GULF CG 72
IWO JIMA LHD 7 VICKSBURG CG 69
JOHN C. STENNIS CVN 74 WASP LHD 1
JOHN F. KENNEDY CV 67 WINSTON CHURCHILL DDG 81
JOHN PAUL JONES DDG 53
B-6 Appendix B Link-16 Platforms
LK16 app B_2001 6 9/24/1, 8:40 AM

Appendixes
Hull USS Hull USS

Number Number
CG 52 BUNKER HILL DDG 53 JOHN PAUL JONES
CG 53 MOBILE BAY DDG 54 CURTIS WILBUR
CG 54 ANTIETAM DDG 55 STOUT
CG 55 LEYTE GULF DDG 56 JOHN S. McCAIN
CG 56 SAN JACINTO DDG 57 MITSCHER
CG 57 LAKE CHAMPLAIN DDG 58 LABOON
CG 58 PHILIPPINE SEA DDG 59 RUSSELL
CG 59 PRINCETON DDG 60 PAUL HAMILTON
CG 60 NORMANDY DDG 61 RAMAGE
CG 61 MONTEREY DDG 62 FITZGERALD
CG 62 CHANCELLORSVILLE DDG 63 STETHAM
CG 63 COWPENS DDG 64 CARNEY
CG 64 GETTYSBURG DDG 65 BENFOLD
CG 65 CHOSIN DDG 66 GONZALES
CG 66 HUE CITY DDG 67 COLE
CG 67 SHILOH DDG 68 THE SULLIVANS
CG 68 ANZIO DDG 69 MILIUS
CG 69 VICKSBURG DDG 70 HOPPER
CG 70 LAKE ERIE DDG 71 ROSS
CG 71 CAPE ST GEORGE DDG 72 MAHAN
CG 72 VELLA GULF DDG 73 DECATUR
CG 73 PORT ROYAL DDG 74 McFAUL
CGN 36 CALIFORNIA DDG 75 DONALD COOK
CGN 37 SOUTH CAROLINA DDG 76 HIGGINS
CGN 40 MISSISSIPPI DDG 77 O’KANE
CGN 41 ARKANSAS DDG 78 PORTER
DDG 79 OSCAR AUSTIN
CV 62 INDEPENDENCE
DDG 80 ROOSEVELT
CV 63 KITTY HAWK
DDG 81 WINSTON CHURCHILL
CV 64 CONSTELLATION
DDG 82 LASSEN
CV 65 ENTERPRISE
DDG 83 HOWARD
CV 67 JOHN F. KENNEDY
DDG 84 BULKELEY
CVN 68 NIMITZ DDG 993 KIDD
CVN 69 DWIGHT D. EISENHOWER DDG 994 CALLAGHAN
CVN 70 CARL VINSON DDG 995 SCOTT
CVN 71 THEODORE ROOSEVELT DDG 996 CHANDLER
CVN 72 ABRAHAM LINCOLN LHD 1 WASP
CVN 73 GEORGE WASHINGTON LHD 2 ESSEX
CVN 74 JOHN C. STENNIS LHD 3 KEARSARGE
CVN 75 HARRY S. TRUMAN LHD 4 BOXER
CVN 76 RONALD REAGAN LHD 5 BATAAN
DDG 51 ARLEIGH BURKE LHD 6 BONHOMME RICHARD
DDG 52 BARRY LHD 7 IWO JIMA
LK16 app B_2001 7 9/24/1, 8:40 AM

Appendixes
Appendix C
Acronyms and Abbreviations
Appendix C Acronyms and Abbreviations C-1
APP_C_2001 1 9/24/1, 8:50 AM

LGN 135-02-002
AADC Area Air Defense Commander

AAW Anti-Air Warfare
ABCCC Airborne Command, Control, and Communications
ABN-16 AEGIS Broadcast Network
ACDS Advanced Combat Direction System
ACO Air Control Officer
ADCP Air Defense Communications Platform
ADGE Air Defense Ground Environment
ADSI Air Defense Systems Integrator
AEGIS Not an acronym. Lit., Greek for 'goatskin'. A shield,
emblematic of majesty, that was associated with
Zeus. The U. S. Navy's AEGIS Program derives its
name from the shield-shaped octagonal outer panel
of its SPY-1 phased-array radar, visible on the
superstructures of AEGIS ships.
AEW Airborne Early Warning
AIC Air Intercept Controller
AIU Antenna Interface Unit
AJ Antijam
ASW Anti-Submarine Warfare
ATACC Advanced Tactical Air Control Center
ATCRBS Air Traffic Control Radar Beacon System
ATDL Army Tactical Data Link
AWACS Airborne Warning and Control System
BDHIs Bearing, Distance, Horizontal Indicators

BIT Built-in Test
BLOS Beyond Line-of-Sight
BPS Bits per second
C-2 Appendix C Acronyms and Abbreviations
APP_C_2001 2 9/24/1, 8:50 AM

Appendixes
C2 Command and Control

C2P Command and Control Processor
CANTCO Cannot Comply
CANTPRO Cannot Process
CCPD Current Crypto Period Designator
CCSK Cyclic Code Shift Keying
CDS Combat Direction System
CG Guided Missile Cruiser
CGN Guided Missile Cruiser, Nuclear
CIC Combat Information Center
CICO Combat Information Center Officer
CIU Concurrent Interface Unit
CMDR Commander
CO Commanding Officer
COMSEC Communications Security
CONCOPS Concurrent Operations
COTS Commercial Off-the-Shelf
CPD Crypto Period Designator
CPSM Continuous Phase-Shift Modulation
CRT Cathode Ray Tube
CTN Common Track Number
CTP Crypto Text Processor
CU Controlling Unit
CV CryptoVariable
CV Aircraft Carrier
CVLL CryptoVariable Logical Label
CVM Common Variable Mode
CVN Aircraft Carrier, Nuclear
APP_C_2001 3 9/24/1, 8:50 AM

LGN 135-02-002
DAMA Demand Assigned Multiple Access

DC Direct Current
DDG Guided Missile Destroyer
DDP Digital Data Processor
DDPG Digital Data Processor Group
DD/TID Digital Display and Tactical Information Display
DEU Data Entry Unit
DFTN Data Forwarding Track Number
DLRP Data Link Reference Point
DME Distance Measuring Equipment
DMH Data Miles per Hour
DP Double Pulse
DPG Data Processor Group
DSCS Defense Satellite Communications System
DSS Data Storage Set
DSU Data Storage Unit
DTB Data Transfer Block
DTI Data Transfer Interrupt
DTS Data Terminal Set
DTSS-16 Link-16 Data Terminal Set Simulator
DUR Data Update Request
EA Electronic Attack
ECA Electronic Cabinet Assembly
EDAC Error Detection and Correction
EHF Extremely High Frequency
EHSP Enhanced High-Speed Processor
EMCON Emissions Control
EMDU Enhanced Main Display Unit
ES Electronic Surveillance
ETA Estimated Time of Arrival
APP_C_2001 4 9/24/1, 8:50 AM

Appendixes
ETD Estimated Time of Departure

ETD Electronic Transfer Device
EW Electronic Warfare
EWC Electronic Warfare Coordinator
FAAD Forward Area Air Defense

FDL Fighter Data Link
FJU Forwarding JTIDS Unit
FJUA Forwarding JTIDS Unit, TADIL A
FJUAB Forwarding JTIDS Unit, TADIL A and TADIL B
FJUB Forwarding JTIDS Unit, TADIL B
FLTSAT Fleet Satellite
FPU Forwarding PU
FSK Frequency Shift Keying
FT Flight Technician
GAAC Geographic Area Assignment Controller

GH Gateway Host
GM Gateway Monitor
GPS Global Positioning System
GRU Gridlock Reference Unit
GTE Gateway Terminal Emulator
HAVCO Have Complied

HCI Human-Computer Interface
HF High Frequency
HPA High-Power Amplifier
HPAG High-Power Amplifier Group
HUR High Update Rate
Hz Hertz
APP_C_2001 5 9/24/1, 8:50 AM

LGN 135-02-002
ICO Interface Control Officer

ICP Indicator Control Panel; Interface Change Proposal
ID Identification
ID AMP Identification Amplification
IDS Interface Design Specification
IE Initial Entry
IEEE Institute of Electrical and Electronics Engineers
IEJU Initial Entry JTIDS Unit
IF Intermediate Frequency
IFF Identification Friend or Foe
IFF/SIF Identification Friend or Foe/Selective Identification Feature
IJMS Interim JTIDS Message Specification
IOC Initial Operational Capability
IPF Interference Protection Feature
IU Interface Unit
JICO Joint Interface Control Officer

JNL JTIDS Network Library
JRE Joint Range Extension, JTIDS Range Extension
JSTARS Joint Surveillance Target Attack Radar System
JTIDS Joint Tactical Information Distribution System
JU JTIDS Unit
Kbps Kilobits per second

KCP Keyer Control Panel
KHz KiloHertz
LAMPS Light Airborne Multiple Purpose System

LCU (Crypto-)load Control Unit
LDR Low Data Rate
LDDS-16 Link-16 Data Distribution System
APP_C_2001 6 9/24/1, 8:50 AM

Appendixes
LHIU Local Host Interface Unit

LPI Low Probability of Intercept
LOB Lines of Bearing
LOS Line-of-Sight
LPI Low Probability of Intercept
LTIU Local Terminal Interface Unit
LTTI Long-Term Transmit Inhibit
MAOC Mobile Air Operations Center

MCE Modular Control Element
MDR Medium Data Rate
MDRI Multifunction Digital Readout Indicator
MDTCI MUX Data Transfer Complete Interrupt
MF Medium Frequency
MFCDU Multifunction Control and Display Units
MHz MegaHertz
MIDS Multifunctional Information Distribution System
MILSTAR Military Strategic and Tactical Relay
MMI Man-Machine Interface
MM/WC Mission Management/Weapons Coordination
MR Machine Receipt
msec Millisecond
MSEC Message Security
MTDS Multi-TADIL Distribution System
MUX Multiplex
µsec Microsecond
NATO North Atlantic Treaty Organization

NC Navigation Controller
NCCOSC Naval Command Control and Ocean Surveillance Center
NCIU Network Control Interface Unit
APP_C_2001 7 9/24/1, 8:50 AM

LGN 135-02-002
NCS Net Control Station

NCTSI Navy Center for Tactical Systems Interoperability
NECT Net Entry Control Terminal
NFA Notch Filter Assembly
NiCad Nickel Cadmium
NICP Network Interface Control Program
nm Nautical Miles
NPG Network Participation Group
NRaD NCCOSC Research, Development, Test, and Evaluation Division
NS No Statement
NTR Net Time Reference
OPORDER Operation Order

OPSPEC Operational Specification
OPTASK Operational Task
OS Operational Specification
OTAR Over-the-air Rekeying
OTC Officer in Tactical Command
P2 Packed 2
P2DP Packed-2, Double Pulse
P2SP Packed-2, Single Pulse
P4 Packed 4
P4SP Packed-4, Single Pulse
PIU Power Interface Unit
PN Pseudorandom Noise
PPLI Precise Participant Location and Identification
PR Position Reference
PRI AMP Primary Amplification
PRU Primary User
PTB Plain Text Bus
APP_C_2001 8 9/24/1, 8:50 AM

Appendixes
PTP Plain Text Processor

PTT Push-to-Talk
PU Participating Unit
PVM Partitioned Variable Mode
Qpg Geodetic Position Quality

Qpr Relative Position Quality
Qt Time Quality
R2 Reporting Responsibility
RAF Royal Air Force (British)
R/C Receipt/Compliance
RDF Radio Direction Finding
RELNAV Relative Navigation
RF Radio Frequency
RHIU Remote Host Interface Unit
RIO Radar Intercept Officer
RN Royal Navy (British)
RR Recurrence Rate
RRN Recurrence Rate Number
R-S Reed-Solomon
R/T Receiver/Transmitter
RTT Round Trip Timing
RTT-A Round Trip Timing – Addressed
RTT-B Round Trip Timing – Broadcast
RTT-I Round Trip Timing – Interrogation
RTT-R Round Trip Timing – Reply
RTIU Remote Terminal Interface Unit
RU Reporting Unit
SACP Stand-Alone Control Panel
APP_C_2001 9 9/24/1, 8:50 AM

LGN 135-02-002
SAHRS Standard Attitude Heading Reference System

SAM Surface-to-Air Missile
SDU Secure Data Unit
SGS Shipboard Gridlock System
SHAR Sea Harrier
SHF Super High Frequency
SICP Subscriber Interface Control Program
SIMPLE Standard Interface for Multiple Platform Link Evaluation
SNC Secondary Navigation Controller
SP Single Pulse
SRA Shop-Replaceable Assembly
SSES Ship's Signals Exploitation Space
SSI Similar Source Integration
STANAG Standardization Agreement
STD Standard
STDL Satellite Tactical Data Link
STN Source Track Number
SU Secondary User
TACAN Tactical Air Navigation

TADIL Tactical Digital Information Link
TAMPS Tactical Aircraft Mission Planning System
TDC Track Data Coordinator
TDM Time Division Multiplex
TDMA Time Division Multiple Access
TDS Tactical Data System
TIC Tactical Information Coordinator
TIDP-TE Technical Interface Design Plan (Test Edition)
TIM Terminal Input Message
TJHS TADIL J Host Simulator
TN Track Number
APP_C_2001 10 9/24/1, 8:50 AM

Appendixes
TOA Time of Arrival

TOM Terminal Output Message
TQ Track Quality
T/R Transmit/Receive
TSB Time Slot Block
TSDF Time Slot Duty Factor
TSEC Transmission Security
TSR Time Slot Reallocation
UAV Unmanned Aerial Vehicles

UHF Ultrahigh Frequency
UFO UHF Follow-On
UPL Upper Packing Limit
USAF United States Air Force
USMC United States Marine Corps
USN United States Navy
UT Universal Time
VAC Volts Alternating Current

VHF Very High Frequency
VOR VHF Omnidirectional Range
VORTAC VOR and TACAN (colocated stations)
W watts
WCM Weapons Coordination and Management
WCS Weapons Control System
WILCO Will Comply
WRA Weapons Replaceable Assembly
XOR Exclusive Or
APP_C_2001 11 9/24/1, 8:50 AM

Appendixes
Appendix D
Glossary
The following terms have been used or defined in this guidebook. Terms in italics are
cross-references.
Appendix D Glossary D-1
APP_D_2001 1 9/21/1, 3:12 PM

LGN 135-02-002
Access rate The assigned rate that determines the frequency of a JTIDS
terminal’s contention access to an assigned time-slot block.
Active The JTIDS terminal’s procedure for transmitting round-trip

synchronization timing messages to refine and maintain its estimate of
system time.
Address A number applied to an interface unit to associate information

and directives with other interface units for digital and voice
communication on Link-16 and on Link-11.
Advanced Combat A tactical data system, modified to process messages

Direction System received over Link-16, that employs enhanced data capacity
and granularity to cross-associate threats and more fully
automate battle decisions.
Air Control The Network Participation Group (NPG 9) that provides the
means for command and control (C2) JTIDS units (JUs) to
control nonC2 JUs.
Antijam margin The degree of protection against jamming provided by

several characteristics inherent in a communications
architecture. Factors contributing to the antijam margin of
the JTIDS signal include error-correction encoding,
pseudorandom noise, transmission redundancy, jitter, and
frequency hopping.
Backlink An adjective describing the time slots that are dedicated to

the transmitted responses of controlled aircraft. It also
applies to aircraft equipped with JTIDS terminals that are
capable of transmitting them.
D-2 Appendix D Glossary
APP_D_2001 2 9/21/1, 3:12 PM

Appendixes
Bilingual The ability of a JTIDS terminal to process both IJMS and

JTIDS messages.
Bit A binary digit. A bit has only two possible values: zero
and one.
Blind relay A relay in which a JTIDS relaying unit is initialized with the
correct transmission security (TSEC) cryptovariable for
receiving and retransmitting messages, but is initialized with
a different message security (MSEC) cryptovariable, which
prevents it from being able to decrypt the messages it relays.
Buffer An area in computer memory that is reserved for the

temporary storage of data. Tactical data systems reserve
buffers for input and output.
Carrier An electromagnetic wave or alternating current whose

modulations are used as signals in radio transmissions.
Chipping A transformation, by cyclic code-shift keying, of the

sequence interleaved symbols of message codewords for transmission.
This transformation produces for each symbol a sequence of
32 bits, or chips.
Coarse The initial procedure of Link-16 net entry, during which a

synchronization JTIDS unit attempts to receive an initial entry message
without adjusting its internal clock for the propagation time
of the message. During this synchronization state, the JTIDS
terminal can receive and process messages and achieve fine
synchronization.
Codeword A sequence consisting of 31 5-bit symbols that correspond to

a sequence of 155 Reed-Solomon-encoded bits, which in
turn correspond to a 75-bit data word to which 80 bits have
been added for error detection and correction.
APP_D_2001 3 9/21/1, 3:12 PM

LGN 135-02-002
Command and A tactical computer introduced into various Combat

Control Processor Direction Systems (CDSs). It has two distinct purposes: data
(C2P) link communications and data forwarding. Data link commu-
nications includes the formatting, transmitting, receiving and
processing of data link messages to allow the CDS to
participate on Link-11 and/or Link-16. Data forwarding is
performed when the C2P is assigned as FJU. It requires that
messages received over one tactical data link be translated
into messages for transmission on another data link.
Command and A platform equipped to direct the activities of other JTIDS

Control (C2) Unit units over Link-16.
Common Track The track number held by all interface units for a contact and
Number (CTN) used in voice and other communications to identify it.
Common A Link-16 communications security (COMSEC) mode in

variable mode which identical cryptovariable logical labels are assigned to
message security (MSEC) and transmission security (TSEC).
Communication A setting on the Class-2 JTIDS terminal that controls the

mode degree of message security (MSEC) and transmission security
(TSEC) employed. This can include slot usage and whether
frequency hopping is employed. Three communication
modes are recognized by NATO and the United States
Armed Services.
Concurrent A unit participating concurrently, but not as a forwarding

Interface Unit (CIU) unit, in both Link-11 and Link-16.
Concurrent Operations Operations by a single unit on both Link-16 and Link-11 at

(CONCOPS) the same time.
APP_D_2001 4 9/21/1, 3:12 PM

Appendixes
Conditional relay A relay mode in which JTIDS units (JUs) selectively activate
or deactivate their relay function based on which JU can
provide most efficient coverage.
Contention access The assignment of time slots to a group of units unit for
transmission purposes, such that any or all of the units may
be transmitting simultaneously during the assigned time
slots.
Continuation word The final portion of a fixed-format message. It contains

70 data bits, 4 parity bits, and one spare bit.
Continuous The process of modulating the frequency of a carrier in such

phase-shift a way that the phase remains continuous.
modulation
Controlled (nonC2) A platform equipped to accept the direction of its activities

unit over Link-16 by a C2 JU.
Crypto net A communications net whose participants are isolated from

other participants by the use of a separate encryption key.
Crypto period A number, either 0 or 1, which designates to a JTIDS

designator (CPD) terminal which cryptovariable of a today/tomorrow pair to
use when encrypting and decrypting Link-16 transmissions.
Cryptovariable (CV) A binary key used by the JTIDS terminal to encrypt and
decrypt data or transmissions. Cryptovariables are assigned
during network design and are loaded into the Secure Data
Unit during terminal initialization.
Cryptovariable A label which applies to a cryptovariable in a Link-16

logical label (CVLL) network. The CVLL is a number between 0 and 127.
APP_D_2001 5 9/21/1, 3:12 PM

LGN 135-02-002
Cyclic code shift A method of encoding and decoding data using a class of
keying codes that are particularly effective in detecting and
correcting multiple errors. In JTIDS, cyclic code shift
keying is applied to a five-bit symbol to produce a 32-bit
chipping sequence by shifting leftward the bits of a 32-bit
starting sequence number by a number of places that
corresponds to the numerical value of the symbol.
Data filter A technique for including or excluding data of certain types

for transmission.
Data forwarding An operational function by which data from units on one

link is forwarded by an intermediary unit to other units on a
different link. In Link-16, the C2P performs the function of
forwarding data between Link-11 and Link-16.
Data Link A fixed geographic reference point, specified by appropriate

Reference Point authority, from which Link-11 participating units calculate
(DLRP) the relative positions of ownship and local tracks, and from
which all tracks are reported over this link. The DLRP is the
origin of the force X/Y-grid.
Data silence A setting on the JTIDS terminal which inhibits the

transmission of data. Voice and TACAN transmissions,
however, are still enabled. A JTIDS unit functioning in data
silence becomes a Secondary User on the JTIDS network.
Data Transfer A message structure defined for the exchange of information

Blocks between the terminal’s Subscriber Interface Control
Processor (SICP) and its Network Interface Control
Processor (NICP).
Dedicated access The assignment of time slots to a uniquely identified unit for
transmission purposes, such that only that unit transmits
during the assigned time slots.
APP_D_2001 6 9/21/1, 3:12 PM

Appendixes
Distance Measuring A civilian system of navigation, used for measuring distance,

Equipment that consists of an airborne interrogator and a ground
transponder.
Donated time slot A time slot, assigned to a particular JTIDS unit, that the unit
temporarily donates to the receiver of a message that
requires an automatic acknowledgement, and during which
the receiving JTIDS unit transmits its required response.
Double pulse A Link-16 transmission format for redundantly conveying

message data, employing two pulse symbol packets that are
transmitted on two different carrier frequencies.
Effective Earth Radius A modification to the radius of the earth that allows the
propagation path of radio waves uniformly bent by the
atmosphere to be treated as though it were straight-line
propagation. The ratio of the effective earth radius to the
true earth radius is denoted by K and can range between 0.6
and 5.0. Its average value in temperate climates is
approximately 1.33.
Electronic Warfare (1) Generally, the use of radiated electromagnetic energy to

(EW) passively establish the location, course and speed of another
platform. (2) The Link-16 Network Participation Group
(NPG 10) that supports such functions by conveying orders
and parametric data.
Epoch The period of longest duration in the TDMA structure of the

JTIDS architecture. A single day consists of 112.5 epochs.
One epoch occupies 12.8 minutes. Epochs are subdivided
into 64 frames and three sets of time slots. An epoch
contains 98,304 time slots, which are its smallest division
of time.
APP_D_2001 7 9/21/1, 3:12 PM

LGN 135-02-002
Extension word The second portion of a fixed-format message. It contains 70

data bits, 4 parity bits, and one spare bit.
Fighter-to-Fighter A Network Participation Group (NPG 19) used by nonC2

Target Sorting units, such as fighter aircraft, to exchange radar, sensor, and
target data.
Fine Part of a procedure for entering a Link-16 net during which a

synchronization JTIDS unit adjusts its internal clock to correct for propagation
time. Fine synchronization must be achieved in order to
participate on the network. A JTIDS terminal may employ
either active synchronization or passive synchronization to
achieve this state.
Fixed format A Link-16 message format consisting of multiple words,

each containing 70 data bits, 4 parity bits, and one spare bit.
Fixed-format messages consist of an initial word, one or
more extension words, and one or more continuation words.
Flood relay A network design strategy in which every JTIDS unit,

including the originator, acts as a relay by retransmitting
messages that it receives.
Forwarding JTIDS A network role assigned to a JTIDS unit that will forward
Unit (FJU) data between tactical data links during a multilink operation.
An FJU that translates and forwards data between Link-16
and Link-11 (TADIL A) is referred to as an FJUA, and one
that translates and forwards data between Link-16 and
TADIL B is referred to as an FJUB.
F-series messages Messages transmitted between fighter aircraft over Link-4C.
Frame A period of time in the JTIDS TDMA architecture equal to

one sixty-fourth of one epoch. A frame is 12 seconds in
duration and contains 1,536 time slots.
APP_D_2001 8 9/21/1, 3:12 PM

Appendixes
Free text A type of Link-16 message structure that uses all bits for
data. Free text messages are used for Link-16 voice
communications.
Frequency The number of cycles a wave completes during one second.
Frequency hopping A transmission technique in which the carrier frequency is

changed for each pulse of a pulsed signal. For Link-16, 51
different frequencies are used and the duration of each pulse
is 6.4-microseconds. The pseudorandom assignment of
frequency establishes a hopping pattern and is part of the
transmission encryption process.
Frequency The transmission technique that modulates or shifts the

modulation (FM) carrier frequency of the signal to convey information.
Frequency A method of encoding data by shifting a carrier frequency

shift keying between two predetermined values.
Geodetic grid An earth-based coordinate system used by JTIDS units to

report positions by specifying latitude, longitude, and
altitude. The geodetic grid is always active.
Gigahertz (GHz) A measure of frequency equal to a billion Hertz.
Global Memory An area in the JTIDS terminal’s memory that is reserved for
the sharing and exchange of information among the multiple
processors within the terminal.
Handover A procedure for passing the control of an aircraft from one

controller to another.
Hertz A unit used to measure frequency. One Hertz equals one

vibration, or cycle, per second.
APP_D_2001 9 9/21/1, 3:12 PM

LGN 135-02-002
High TN Block A block of assignable Link-16 track numbers, including the

octal track numbers 10000 through 77777 and the alphanu-
meric track numbers 0A000 through ZZ777. No track
numbers in this block correspond to Link-11 track numbers.
Housekeeping Blocks of information that are exchanged, in either direction,

Words between the JTIDS terminal’s Subscriber Interface Control
Program (SICP) and its Network Interface Control Program
(NICP). Their primary purpose is to convey information
required for the encryption and decryption of the signal.
Identification An interrogator, which can be either ground-based (with the

Friend or Foe Air Traffic Control Radar Beacon System) or airborne, that
(IFF) transmits pulses and receives replies containing the
responding aircraft’s identity, altitude, and other essential
information.
Indirect Precise The Network Participation Group (NPG 14) on which

Participant Forwarding JTIDS units transmit to other JTIDS units the
Location and Precise Participant Location Information of units not
Identification participating on the JTIDS network.
Initial Entry The Network Participation Group (NPG 1) which supports

coarse synchronization between a JTIDS unit and the
Link-16 network.
Initial Entry JTIDS A JTIDS unit (JU) that transmits Initial Entry messages for
Unit (IEJU) the purpose of assisting other units in achieving
synchronization with, and entry into, a Link-16 network.
Initial Entry A Link-16 message transmitted by a JTIDS unit (JU) to

message facilitate the entry of other units into the JTIDS network.
Initial word The first portion of a fixed-format message. It contains

70 data bits, 4 parity bits, and one spare bit.
APP_D_2001 10 9/21/1, 3:12 PM

Appendixes
Interference An automatic function of the Class-2 JTIDS terminal that

Protection monitors its own transmissions and disables the terminal
Feature (IPF) whenever it detects that they are in any way improper. Three
settings of IPF are available on the terminal: normal,
exercise, and combat.
Interim JTIDS An early implementation of messages exchanged between

Message the Class-1 JTIDS terminals. The Air Force Class 2
Specification (IJMS) terminals retain both an IJMS and JTIDS message capability,
Messages and can translate between them. NPG 31 is provided for the
exchange of IJMS messages.
Interleave To arrange in an alternating sequence or order. Time slots of

the three sets A, B, and C are interleaved, as are the
transmission symbols of the message and data code words.
Jamming The process of obstructing, or rendering unintelligible, a

transmitted message by sending out interfering signals or
messages.
Jitter The first portion of the time slot, during which the
transmitter is silent. Jitter may be either applied or not
applied within a time slot and when applied, it may be of
varying duration. Its purpose is to render the actual start time
of the data transmission impossible to predict.
Joint Precise A Network Participation Group (NPG 27) in which

Participant Location identification and location information is exchanged during
and Identification Joint operations.
Joint Tactical (1) The method, hardware, and software by which tactical
Information information is disseminated over Link-16. (2) Commonly,
Distribution System the JTIDS terminal, which modulates, transmits, receives,
(JTIDS) and demodulates messages for a participant in a Link-16
network.
APP_D_2001 11 9/21/1, 3:12 PM

LGN 135-02-002
JTIDS Network A collection of network designs on tape or cartridge

Library available to all JTIDS units.
JTIDS unit (JU) A platform equipped to participate in Link-16 communica-

tions. A JU is either a Command and Control (C2) unit or a
controlled (nonC2) unit.
J-series message The fixed format messages, containing tactical data and
commands, that are used to exchange information over
Link-16. These messages adhere to the standards defined
in OS 516.1.
Kilohertz (KHz) A measure of frequency equal to 1,000 Hertz.
L Band L Band A portion of the RF UHF band stretching from

390 MHz to 1.550 GHz. JTIDS operates within this band on
frequencies between 960 and 1216 MHz.
Line of Sight The direct line in which radio waves travel, without bending
over mountains or the curve of the earth.
Link-4A The tactical digital data link protocol, specified by OS-404.1,

for controller-to-controlled aircraft communications. Its
communications are characterized by strict message timing
of control data, which is conveyed in V-series messages, and
of its controlled aircraft replies, which are conveyed in
R-series messages. Link-4A messages conform to the
TADIL-C message standard.
Link-4C The tactical digital data link protocol, specified by OS-404.1,

for fighter-to-fighter aircraft communications between F-14
aircraft. Its data is conveyed in F-series messages that adhere
to a TADIL-C message standard that is separate and distinct
from that of Link-4A.
APP_D_2001 12 9/21/1, 3:12 PM

Appendixes
Link-11 The tactical digital data link protocols, specified by OS-411,

for communications among a multiple number of units. Its
netted communications are characterized by a round robin,
designated roll call, in which every participant reports in turn
when requested to do so by one unit, designated the Net
Control Station. The messages exchanged over Link-11,
known as M-series messages, adhere to the TADIL-A
message standard.
Link-16 The secure, jam-resistant, high-capacity, nodeless tactical

digital data link, also known as TADIL J, which utilizes the
JTIDS terminal and its TDMA architecture for multinetted
communications. The information exchanged on this link
are conveyed in the J-series messages and conform to the
operational specifications contained in OS-516.1.
Long-Term Transmit A setting on the JTIDS terminal which inhibits all radio
Inhibit (LTTI) transmissions including voice and TACAN as well as data.
Low TN Block The block of assignable Link-16 track numbers that range
from 0 to 07776. The track numbers in this block correspond
to all Link-11 assignable track numbers.
M-series messages Messages transmitted over Link-11 between participating

units.
Machine Receipt A Link-16 message, automatically transmitted by a JTIDS

(MR) terminal, that acknowledges the receipt of certain types of
other messages.
Megahertz A measure of frequency equal to 1 million Hertz.
Message formats For a given tactical data link, the set of sequences of fields,
composed of prescribed numbers of bits, that may be encoded
into prescribed patterns to convey specific information. The
message formats of Link-4A/C are classified.
APP_D_2001 13 9/24/1, 9:14 AM

LGN 135-02-002
Message header That portion of a Link-16 message, consisting of a single

codeword, that specifies the format of the message data,
whether the data is encoded, which packing structure has
been used for its transmission, the secure data unit serial
number, and the track number of the JTIDS terminal that
originated the message.
Message security A cryptovariable which is used by a JTIDS unit to encrypt

(MSEC) message data for transmission on Link-16.
Microsecond One one-millionth of a second.
Millisecond One one-thousandth of a second.
Mission The Network Participation Group (NPG 8) that provides a

Management means for coordinating weapons and engagements for the
Battle Group.
Nautical Mile A unit of distance used in air and sea navigation based on the
length of a minute of arc of a great circle of the earth. The
unit used by the U.S. is equal to 6076.115 feet, or approxi-
mately 1.15 statute miles.
Navigation A network role, assigned when a relative grid is to be used

Controller (NC) by units of a Link-16 network, to a mobile unit that acts as
the reference unit for the grid and whose position quality is
by definition the maximum value, 15.
Needline A functional grouping of Link-16 message formats that

Participation supports a particular type of messages used by the United
Group States Army. Needline participation groups constitute a
subclass of network participation groups.
Net Entry Control A network role that propagates the system time to units
Terminal (NECT) beyond line of sight of the Network Time Reference.
APP_D_2001 14 9/21/1, 3:12 PM

Appendixes
Network Interface A software program, residing within the JTIDS terminal, that
Control Program has overall responsibility for communications with the
(NICP) JTIDS RF network.
Network The Network Participation Group (NPG 4) during which

Management commands are transmitted for managing the operation of a
particular Link-16 network.
Network A functional grouping of Link-16 messages that supports a

Participation particular type of mission.
Group (NPG)
Network role A function assigned, on the basis of platform capabilities and

expected platform position, to a command and control JTIDS
unit (JU), either by initialization or by operator entry.
Network roles support network synchronization, navigation,
and interlink operations.
Network Time A network role assigned uniquely to a single command and

Reference (NTR) control unit. The NTR’s clock establishes the timing for the
network and is the reference with which all other units must
achieve and maintain fine synchronization to remain in the
network. By definition, the NTR’s Time Quality is 15, the
maximum value.
No statement word A word supplied by the JTIDS terminal when there is an

insufficient number of words that are required to complete a
message packing format for transmission.
N-series messages The “normalized” messages exchanged between the

Command and Control Processor and the tactical computer
aboard either an ACDS Block 1 ship or an AEGIS Model 5
ship. The data contained in these messages is independent
of the link on which the data was received or is to be
transmitted.
APP_D_2001 15 9/21/1, 3:12 PM

LGN 135-02-002
OPTASK LINK That portion of the Operation Tasking Order that applies to
tactical data link communications involving ships.
Passive A secondary method of net entry, employed by JTIDS units

synchronization in radio silence, during which fine synchronization is
achieved and maintained by passively monitoring the
messages on the Precise Participant Location and
Identification Network Participation Groups.
Packing structure The grouping of Link-16 message words, of any format, into a
Link-16 transmission. These groups can contain 3 words,
6 words, or 12 words.
Packed-2 format A message consisting of six words which may be transmitted

redundantly within a single time slot. Nonredundant
transmission is referred to as Packed-2 Single-Pulse (P2SP)
format, and redundant transmission is referred to as
Packed-2 Double-Pulse (P2DP) format.
Packed-4 format A message consisting of 12 words which are transmitted

within a single time slot. Its nonredundant transmission is
also referred to as Packed-4 Single-Pulse (P4SP) format.
Paired slot relay A type of relay in which the time slot of the original
transmission is paired with a second time slot after a
specified delay for the retransmission of the message by the
relaying unit.
Parallel interface A computer interface in which multiple bits are transferred

in parallel, at the same time, along separate lines.
APP_D_2001 16 9/21/1, 3:12 PM

Appendixes
Parametric data For electronic warfare (EW), the unprocessed data that is
collected by sensors and includes lines of bearing, pulse
width, pulse repetition frequency, antenna scan period, etc.
A Network Participation Group (NPG 10) is reserved for the
transmission of this parametric data before it is evaluated by
a tactical data system.
Partitioned A Link-16 communications security (COMSEC) mode in

variable mode which different cryptovariable logical labels are assigned to
message security (MSEC) and transmission security (TSEC).
Passive The process by which a JTIDS terminal in radio silence ad-

synchronization justs its estimate of system time by interpolation from the
received positions of other units, the time of arrival of their
messages, and the knowledge of its own position, maintained
internally by its navigation system.
Phase-coherent The application of two frequencies whose periods differ by

binary precisely one-half wavelength during a specified interval to a
frequency-shift carrier, such that the higher frequency represents one value
or condition and the lower frequency represents its opposite.
keying
For Link-16, the difference in frequencies represents a
change in the value of contiguous constituents of chipping
sequences, rather than the absolute value of any constituent.
The higher frequency is applied whenever a constituent
differs from the previous constituent, and the lower value is
applied whenever they are identical. For Link-16, the period
over which the requisite frequencies are maintained is
precisely 200 nanoseconds.
P-messages A designation for Interim JTIDS Message Specification

(IJMS) Position and Status messages transmitted on the
Network Participation Group (NPG 30) reserved for this
purpose.
APP_D_2001 17 9/21/1, 3:12 PM

LGN 135-02-002
Position Quality A value between 0 and 15 that indicates the accuracy with
which a JTIDS units fixes its own position. Two position
qualities are maintained: the geodetic position quality and
the relative position quality. When the geodetic grid is
operational, the maximum value is assigned to JTIDS units
acting as Position References. When the relative grid is
operational, the maximum value is assigned to the JTIDS
unit acting as Navigation Controller. The maximum value,
15, indicates a positional accuracy of within 50 feet.
Position A network role that is always assigned to a well-surveyed,

Reference stationary site whose position quality is the maximum value,
15. This role is not required and may not be assigned in
every network.
Positive The means of identifying a JTIDS unit, during Network

Identification Participation Groups dedicated to Precise Position Location
Information, that consists of a unique JTIDS unit number,
Identification Friend or Foe (IFF) codes, platform type, and
information on the platform’s movement and link activity.
Precise Two Network Participation Groups (NPG 5 and 6) during

Participant which JTIDS units transmit their precise location,
Location and identification, fuel and weapons status, and communications
Identification(PPLI) data. Controlling units and controlled units use NPG 6, PPLI
and Status and Status, Pool B; controlled units such as fighter aircraft
also use NPG 5, PPLI and Status, Pool A, to transmit more
rapid position updates.
Primary User A network role assigned to every JTIDS unit that is actively
(PRU) maintaining synchronization with its Link-16 network. The
Network Time Reference, as the unit which establishes the
timing of the network, does not need to maintain synchroni-
zation and is therefore not considered a primary user.
APP_D_2001 18 9/21/1, 3:12 PM

Appendixes
Propagation The fifth and final portion of the time slot, during which no
pulses are transmitted and the signal is allowed to propagate.
Pseudorandom noise A 32-bit sequence that, when exclusively OR’d bitwise with
a 32-bit chipping sequence, produces another 32-chip
sequence, the transmission symbol. The 32-chip pseudoran-
dom noise sequence, which is determined by the transmission
security (TSEC) cryptovariable, changes continuously.
Pulse symbol A 13-microsecond transmission period within the time slot.

packet A single pulse symbol packed consists of a 6.4-microsecond
pulse of modulated carrier frequency followed by 6.6
microseconds of dead time. A double pulse symbol packet
consists of two single pulse symbol packets, and is
26 microseconds in duration.
Radio horizon The distance to the horizon as defined by the slightly curved
path followed by a radio wave. This distance can be
determined from the effective earth radius.
Receipt/Compliance The protocol by which certain messages are acknowledged

(R/C) and responded to by the machine and, in some cases, by the
operator. For Link-16, the machine receipt function is
performed automatically by the JTIDS terminal.
Reed-Solomon The scheme employed for encoding Link-16 message data

encoding that consists of the addition of error detection and correction
bits to 75-bit words to form 155-bit sequences, which are
then taken, in groups of five, to create 31 symbols.
Relative grid A three-coordinate flat-plane system used by JTIDS units to

report their position from the relative grid origin. The
relative grid is active when there is a grid origin provided by
the NC and SNC.
APP_D_2001 19 9/21/1, 3:12 PM

LGN 135-02-002
Relative grid origin The origin, calculated by the network’s Navigation

Controller (NC), that inherently includes the NC’s own
geodetic navigation errors.
Relative Navigation An automatic and constant function of the JTIDS terminal,

(RELNAV) used for synchronizing all platforms in the network and for
determining the distance between platforms.
Relay A network role assigned to a JTIDS unit. Messages received

within designated time slots are retransmitted after a
specified delay. The retransmission of messages by
airborne relay platforms allows information to be propagated
to other units that are not within line of sight of the original
transmitters.
Relay delay A fixed offset, of from 7 to 30 time slots, between the time
slot during which a message is originally transmitted and the
time slot during which it is retransmitted by a relaying
JTIDS unit.
Relay pair The first and relay-repeated transmissions of a single

message.
Reporting Automatic procedures exist to limit the number of units

Responsibility (R2) reporting a particular radar contact, or track, to a single unit.
This determination is based on track qualities and the unit
designated as having responsibility for reporting the track is
said to have R2.
Repromulgated A relay technique, used by the U. S. Army, in which any

relay suitably initialized receiver will relay a transmitted message
during the next time slot.
R-series messages Messages originating at a controlled platform that are

transmitted over Link-4A in response to control messages.
APP_D_2001 20 9/21/1, 3:12 PM

Appendixes
Residual Message A Network Participation Group (NPG 29) in which

NPG messages not specifically assigned to other NPGs may be
exchanged.
Rotodome The disk radar antenna on an E-2C that rotates in flight to

provide radar coverage.
Round-Trip One of a set of messages that support fine synchronization

Timing (RTT) between the units of a Link-16 network. They are both sent
message and received during a single time slot by an individual
JTIDS unit: the interrogation is sent, and the reply is
received.
RTT-A (NPG 2) By definition, the Network Participation Group during

which specifically addressed Round-Trip Timing messages
are transmitted during time slots that are dedicated to
particular JTIDS units.
RTT-B (NPG 3) By definition, the Network Participation Group during

which Round-Trip Timing messages are transmitted during
time slots that are shared among units and which are
accessed by contention.
Secondary A network role, assigned when a relative grid is to be used

Navigation Controller by units of a Link-16 network, to a single unit that can be
(SNC) either stationary or mobile, but which must be in relative
motion with respect to the navigation controller, and must
be in synchronization and line of sight of it.
Secondary User A network role taken by any JTIDS unit that enters a
(SU) Link-16 network under restricted conditions during which
they remain either radio silent or data silent.
APP_D_2001 21 9/21/1, 3:12 PM

Serial interface A computer interface in which single bits are transferred
serially, one after the other, along one line.
Set In JTIDS TDMA architecture, one-third the total number of

time slots in one epoch. The three sets of time slots are
designated set A, set B, and set C. The epoch consists of the
interleaved time slots of these three sets.
Single pulse A Link-16 transmission format employing one pulse symbol

packet to convey messages.
Spread Spectrum A modulation/demodulation technique in which the

transmission bandwidth is much greater than the minimum
bandwidth that would be required to transmit the digital
information, and which results in a performance improve-
ment. In JTIDS, 5 bits of digital information are transmitted
with each pulse by associating each 5-bit message with a dif-
ferent phase of the 32-bit direct-sequence spreading code.
Stacked nets The principle of JTIDS TDMA architecture by which the

time slots of a single NPG may be simultaneously allocated
to 128 different nets, transmitting on different frequency-
hopping patterns. The Voice and the Air Control NPGs are
the most common examples of stacked nets.
Standard format A message consisting of three words which is transmitted

redundantly within a single time slot. Because messages of
this format are always transmitted with the double-pulse
structure, it is sometimes referred to as Standard
Double-Pulse (STD-DP) format.
Subscriber Interface A computer program, residing within the JTIDS terminal,

Control Program that has overall responsibility for communicating with the
(SICP) host platform.
APP_D_2001 22 9/21/1, 3:12 PM

Surveillance The process of searching for, detecting, locating, identifying,
and tracking objects. Surveillance information is exchanged
on Network Participation Group (NPG 7).
Symbol A single element of a codeword which corresponds to five

Reed-Solomon encoded bits of a 155-bit sequence. This
sequence represents a 75-bit data word, to which 80 bits
have been added for error detection and correction.
Symbol The intermixing of the symbols that constitute the header and
interleaving data of the message. Its purpose is to render the positions of
elements of the message header unpredictable, thus greatly
decreasing the possibility that the message transmission can
be intercepted, exploited, or jammed.
Synchronization (1) The acquisition and maintenance of system time by any

member of a Link-16 network. (2) The second portion of the
time slot, during which a specific sequence of symbols are
transmitted.
Tactical Air A military navigation system that combines distance and

Navigation direction measurement to military aircraft, which are
(TACAN) specially equipped to reference them.
Terminal Input Messages that transfer data from a host computer, which
Messages (TIMs) aboard ships is a Command and Control Processor (C2P) and
aboard aircraft is a mission computer, to the JTIDS terminal
over the MIL-STD-1553B multiplex data bus.
Terminal Output Messages that transfer data over the MIL-STD-1553B

Messages (TOMs) multiplex data bus from the JTIDS terminal to a host
computer, which aboard ships is a Command and Control
Processor (C2P) and aboard aircraft is a mission computer.
Time Division The architectural principle by which JTIDS networks are

Multiple Access structured and periods of transmission are assigned to every
(TDMA) unit.
APP_D_2001 23 9/24/1, 8:43 AM

LGN 135-02-002
Time Quality The measure, kept by every JTIDS unit, of its accuracy with
respect to a designated Net Time Reference. Time Quality
(Qt ) is expressed as an integer from 0 to 15 that represents
the number of nanoseconds’ deviation about the standard
reference. The maximum Qt value is 15, which represents a
deviation less than or equal to 50 nanoseconds.
Time refinement The third portion of the time slot, during which four
double-pulse starting sequence number (S0) symbols are
transmitted over 104 microseconds.
Time slice For the JTIDS TDMA architecture, the designation for a
single time slot that occurs during the identical period of
time for all 128 stacked nets.
Time slot The allocated period of time during which a netted unit
contributes its information over a tactical data link. Also, the
period of shortest duration of which the JTIDS TDMA
architecture is structured. The time slot is the basic window
of access to the network and is the period during which a
JTIDS unit is either transmitting or receiving.
Time slot duty A restriction that limits the usage of time slots to a number
factor (TSDF) of pulses per unit of time.
Time slot An access method which establishes a pool of time slots

reallocation which are periodically reassigned among the participants of
an NPG based on their transmission needs.
Time slot reuse The practice of assigning two or more JTIDS units to
transmit on the same net during the same time slot.
T-messages A designation for Interim JTIDS Message Specification

(IJMS) messages, except for IJMS Position and Status
messages, that are transmitted on the Network Participation
Group (NPG 31) reserved for this purpose.
APP_D_2001 24 9/21/1, 3:12 PM

Appendixes
Today/tomorrow A schedule for the use of cryptovariable pairs loaded into the
pair Secure Data Unit that allows the network to rollover
cryptovariables from one day to the next without disruption
to the link.
Track number A number, applied to a located object, used to associate

(TN) information and directives for digital communication over
Link-16.
Track number The process of assigning, and consistently using, a low track
association number for tracks which were originated on Link-16 with a
high track number and are forwarded to Link-11.
Transmission A cryptovariable which is used by a JTIDS unit to determine

security (TSEC) the duration of jitter within the time slot, as well as the
pseudorandom noise with which the received transmission
was masked by the transmitter.
Transmission A 32-bit sequence that results from the bitwise exclusive-or

symbol operation of a 32-bit sequence of pseudorandom noise and a
32-bit chipping sequence of data.
Unconditional A relay mode in which a JTIDS unit in fine synchronization

relay with the network and not in Long-Term Transmit Inhibit
(radio silence) always relays messages in accordance with its
time slot assignments.
Upper Packing
Limit An initialization parameter of the Class-2 JTIDS terminal
which constrains its transmissions to a subset of the full
range of possible packing structures. Its purpose is to
establish the minimum amount of antijam margin always
retained.
APP_D_2001 25 9/21/1, 3:12 PM

LGN 135-02-002
Variable format A Link-16 message format that supports the U. S. Army’s

Link-16 communications requirements, and that consists of a
variable number of 75-bit words.
V message The control message in a Link-4A net.
VHF A transmitter that is used by aircraft for measuring range. It

Omnidirectional can be colocated with Distance Measuring Equipment for
Range (VOR) providing aircraft with both range and distance.
Voice A, Voice B The two channels, Network Participation Groups 12 and 13,
respectively, that are used by JTIDS units for secure
digitized voice transmissions.
VORTAC (1) A transmitter that combines the functions of a military

TACAN system and a civilian VOR to provide VOR
azimuth, TACAN azimuth, and TACAN distance to an
airborne interrogator.
Weapons The Network Participation Group (NPG 18) during which

Coordination commands are transmitted for employing tactical weapons.
Word For Link-16, a sequence of 75 bits.
APP_D_2001 26 9/21/1, 3:12 PM

Appendixes
Appendix E
Index
Appendix E Index E-1
APP_E_2001 1 9/21/1, 3:40 PM

LGN 135-02-002
A
Access Modes 6-19
Contention 6-21 ff.
Dedicated 6-19
Time slot reallocation 6-24
Access Rate 6-23
Address
JU 1-19
PU 1-7
Air Control 7-14, 6-8 ff.
Backlink 6-8 ff.
Future enhancements 7-15
Handovers 7-15
Multilink A-20
Stacked net 1-17 (fig.)
Uplink 6-8 ff.
Antennas
E-2C 3-18
F-14D 3-28
Reception 2-33
Shipboard 2-32
Antijam
E-2C antenna 3-18
Margin 5-30, 5-43, 5-51
Architecture
Command-and-response 1-7
Link-11 1-6
Link-16 1-14 ff., 5-2, 5-17
Link-4A 1-7
Netted 1-6
TDMA 5-2 ff., 5-21
Areas 1-22, 7-10
E-2 Appendix E Index
APP_E_2001 2 9/21/1, 3:40 PM

Appendixes
B
Backlink. See Air Control
Battery Assembly 2-28
BIT
Initiation 2-30
Terminal function 2-18
Blind Relay 6-52, 6-58
Broadcast 3-4
C
C2 Unit 3-2, 6-18
C2P 2-11ff.
Data forwarding 4-8, 6-33, App A
Major functions 2-12 (fig.)
Message conversion 4-8
Operator entries 2-13
Version 0 2-3
Version 1 2-7
Chipping sequence 5-38 ff., 5-42 (fig.)
Class-1 Terminal 1-4
Class-2 Terminal 1-4. See also JTIDS Terminal
Coarse Synchronization. See Synchronization
Combat Override of IPF 5-66
Common Carrier Messages 4-11
Common Track Number A-17
Common variable mode 6-57
Communication Modes 5-52
Concurrent Interface Unit A-12
Concurrent Operations A-10 ff.
Contention Access 6-21 ff.
Continuous Phase Shift Modulation 2-25, 5-41
APP_E_2001 3 9/21/1, 3:40 PM

LGN 135-02-002
Control Panels
Indicator 2-30
Keyer 2-31
Stand-alone 4-32
Crypto Nets 6-62
Crypto Period Designator 6-55, 6-56 (fig.)
Cryptovariable Logical Label 6-54 ff.
Cryptovariables 1-15, 2-31, 5-40, 6-54 ff.
Common 6-57
Default 6-57
Partitioned 6-57
Current Crypto Period Designator 6-55
Cyclic Code Shift Keying 5-38 ff.
D
Data
Filters A-9
Flow 2-35 ff.
Forwarding A-2 ff.
Granularity 1-22
Normalized 4-4
Packing options 5-45
Update request A-19
Data Link Reference Point 1-24
Data Rates
Comparison 1-11 (fig.)
Serial 5-27
Data Silent 6-11, 6-32, 6-49
Data Storage Unit 3-28
Data Transfer Blocks 4-2, 4-20 ff.
Navigation data 4-25
Received message 4-23
Status 4-24
Transmitted message 4-23
Dedicated Access 6-19
APP_E_2001 4 9/21/1, 3:40 PM

Appendixes
Demodulation
Data flow 2-37
Digital Data Processor 2-23
Digital Data Processor Group 2-22, 2-24 (fig.)
Distance Measuring Equipment 5-53, 5-56, 5-60
Double Pulse 5-43, 5-49 (fig.)
Header 5-45
Synchronization 5-44
Time refinement 5-44
E
E-2C 3-10 ff.
Antennas 3-18
Broadcast 3-4
Crew 3-12
Description 3-2, 3-3 (fig.), 3-10, 3-12
Displays and controls 3-15 (fig.), 3-16 (fig.)
Equipment configuration 3-12, 3-13 (fig.), 3-14 (fig.)
Mission 3-10
Mission computer 3-14
TACAN 3-17
Terminal initialization 3-18
Electronic Cabinet Assembly 2-21
Electronic Warfare 1-2, 6-11, 7-7
Multilink A-21
Parametrics 7-7
Products 7-7
Encryption 2-25, 4-26
Epoch 5-3
Error Detection and Correction 5-25, 5-39
Exercise Indicator 7-12
Exercise Override of IPF 5-66
Extended Range 5-21
Effect on time slot structure 5-51
APP_E_2001 5 9/21/1, 3:40 PM

LGN 135-02-002
F
FAA 5-58
F-14D 3-19 ff.
Antennas 3-28
Crew 3-20
Description 3-2, 3-3 (fig.), 3-19, 3-20
Displays and controls 3-24, 3-25 (fig.), 3-26 (fig.)
Equipment configuration 3-21 (fig.), 3-22 (fig.)
Mission 3-19
Mission computer 3-23
TACAN 3-23
Terminal initialization 3-28
Fighter Advisory 6-13
Fighter-to-Fighter 6-13
Filters 4-16, 7-11, A-9
Fine Synchronization. See Synchronization
Fixed-Format Messages 5-23 ff, 5-24 (fig.)
Flood Relay 6-50, 6-51 (fig.)
Force Training 7-12 ff.
Forwarding
Alternate FJU A-4
C2P A-3
Filters A-9
FJU A-3
FJUA 6-33
FJUB 6-33
for Distance A-6
Multiple FJUs A-5
TADIL A A-4
TADIL B A-4, A-8
Frame 5-8
Free-Text Messages 5-22, 5-27 (fig.)
APP_E_2001 6 9/21/1, 3:40 PM

Appendixes
Frequency
Hopping 1-8, 5-44, 5-52, 5-55, 6-57
Interference 5-61, 5-62
Intermediate 2-25
JTIDS 5-54, 5-55 (fig.), 5-60 (fig.)
Spectrum 5-53 (fig.)
TACAN/DME 5-56, 5-57 (fig.)
G
Geodetic Positioning 1-23, 6-29, 6-42
Global Memory 2-24
H
Handovers 7-15, 7-16
Header 5-22, 5-28, 5-45
Type field 5-46
Type modifier 5-46
High Power
Amplifier group 2-26, 5-66
Authorization 5-66
Host 4-9
Housekeeping Words 4-2, 4-26 ff., 4-27 (fig.)
I
Identification. See PPLI
IFF 5-54, 5-58, 5-59 (fig.)
APP_E_2001 7 9/21/1, 3:40 PM

LGN 135-02-002
IJMS 1-4, 6-14

Indicator Control Panel 2-30
Indirect PPLI 6-12
Information Exchange
Automating tactical functions 7-3
Between the host and the SICP 4-9, 4-14, 4-19
Between the Link-16 components 4-3 (fig.)
Between the PTP and NICP 4-26
Between the SICP and NICP 4-20
Comparison of Link-11 and Link-16 1-26 (fig.)
Standardization 7-3
Within the DDP 4-28
Initial Entry JU 6-29
Intelligence Reporting 7-9
Interface Unit 2-22
Concurrent A-12
Interference 5-61
Interference Protection Feature 5-63
Combat override 5-66
Exercise override 5-66
Normal 5-64
Peacetime Constraints 5-63, 5-67 (fig.)
Summary 5-65 (fig.)
Time slot duty factor 5-64, 5-66, 6-50
Interleaving
Sets 5-3
Symbols 5-30
Intermediate Frequency 2-25
Interrupt
MUX data transfer complete 4-13, 4-19
End of slot 4-22
IOC 3-3
APP_E_2001 8 9/21/1, 3:40 PM

Appendixes
J
J-Series Messages 4-2, 4-6
Catalog 4-7 (fig.)
Continuation word 4-11, 4-16, 5-23, 5-24 (fig.)
Extension word 4-11, 4-16, 5-23, 5-24 (fig.)
Fixed-format 5-23
Initial word 4-11, 4-16, 5-23, 5-24 (fig.)
No Statement word 5-23
Standards 5-23
Jitter 5-19, 5-33, 5-47 ff.
JTIDS 1-2
Antennas 2-32
Architecture 1-14 ff.
Bilingual terminal 1-4
Emissions requirements 5-62
Features of the architecture 1-14
Frequencies 5-54, 5-55 (fig.)
RF signal 5-52 ff.
Security 1-15
Shipboard terminal 2-14
JTIDS Network Library 2-31, 3-18, 3-28, 6-25
JTIDS Terminal 2-14 ff.
Airborne 3-6
Components 2-19, 2-20 (fig.), 3-6
Controls and indicators 2-29
Initialization 2-31, 3-18, 4-11, 6-26
Message buffering 6-16
Navy variants 3-6
TACAN function 3-6, 4-32
JU
Addresses 1-19
Forwarding 6-33, A-3
Initial Entry 6-29
APP_E_2001 9 9/21/1, 3:40 PM

LGN 135-02-002
K
Keyer Control Panel 2-31
L
L Band 5-53
Land points 1-25
Line of sight 3-7
Lines 1-22, 7-10
Link-11
Architecture 1-6 (fig.)
Backward implementation 7-4
Data exchange 1-10
Link-16 1-2
Air control 7-14
Airborne equipment 3-1 ff.
Antennas 2-32, 3-18, 3-28
Architecture 1-8, 1-9 (fig.), 1-44 ff.
Autonomous operation 7-2
Capabilities 1-18 ff.
Data exchange 1-10
Data flow 2-35
Design goals 7-2 ff.
Features 1-5, 1-13 (fig.)
Implementation 1-27
Messages 5-22 ff.
Model 4 2-3
Model 5 2-6
Number of participants 1-19
Platforms App B
Range 3-7
Shipboard equipment 2-1
Track numbers 1-20
APP_E_2001 10 9/21/1, 3:40 PM

Appendixes
Link-4A
Air control 7-14
Architecture 1-7 (fig.)
Data exchange 1-10
Long Term Transmit Inhibit 6-32, 6-49
Loopback ID 4-11
Low Probability of Intercept 5-44
Lx Band 5-53
M
Machine Receipt 6-44
MDCTI 4-13, 4-19
Message security 1-15
Messages
Buffering 6-16
Common carrier 4-11
Filtering by the FJU A-9
Filtering by the tactical system 7-11
Filtering by the terminal 4-16
Fixed format 5-22, 5-23, 5-24 (fig.)
Free text 5-22, 5-27 (fig.)
Header 5-22, 5-28
IJMS 6-14
J-series 4-2, 4-6 ff.
Link-16 5-22 ff.
Loopback of 4-23
M-series 1-10
N-series 4-2, 4-4 ff.
P 6-14
Packing formats 5-28, 5-45
Packing limitations 5-50
R-series 1-10
Round-trip timing 5-22
APP_E_2001 11 9/21/1, 3:40 PM

LGN 135-02-002
Residual 6-14
Standardization 7-3
T 6-14
Terminal-initiated 2-37
TIMs 4-2, 4-9
TOMs 4-2
Translation in the C2P 4-8
V-series 1-10
Variable format 5-22, 5-26 (fig.)
Voice 5-27
MIDS 1-2
Mission Management 6-8
Model 4 2-3
AEGIS equipment configuration 2-4
CDS equipment configuration 2-5
Model 5 2-6
AEGIS equipment configuration 2-6
ACDS equipment configuration 2-7
Airborne platforms 3-2, 3-5
Normalized data 4-4
Mode S IFF 5-58
Modes
Communication 5-52
EW 7-7, A-21
Modulation
Carrier 5-41, 5-42 (fig.)
CCSK 5-38
CPSM 2-25, 5-41
Data flow 2-36
FSK 5-41
Multilink
Capability 3-4
Data forwarding A-3
Functions A-14
Operations A-2
Platform status A-20
APP_E_2001 12 9/21/1, 3:40 PM

Appendixes
Multinetting 6-58 ff.

Multiple nets 6-59
Stacked nets 1-8, 1-17, 5-16, 6-60
Multipath Interference 5-44
Multiplex Cycle 4-19
N
N-series Messages 4-4 ff.
Navigation
Controller 6-30, 6-42
DTBs 4-25
Geodetic 1-23, 4-18, 6-29
Relative 1-24, 2-16, 4-18, 6-5, 6-7, 6-30, 6-39
Secondary Controller 6-31
Systems 5-56
Needline Participation Groups 6-3
Net Crypto 6-62
Entry 6-5, 6-29, 6-35 ff.
Multiple 5-16, 5-17 (fig.)
Single 5-16
Stacked 1-8, 1-17, 5-16, 6-60
Net Entry Control Terminal 6-29
Net Number 5-16, 6-40, 6-59
Default 6-57
Dial-a-net 6-61. See also Stacked Nets
Net Time Reference 5-18, 6-5, 6-35
Network
Design 6-25
Functional structure 6-1 ff.
Management 7-17, 6-26
Manager 6-34
Multiple 6-62
Participation groups 6-2 ff.
Physical structure 5-1 ff.
Roles 6-27 ff.
APP_E_2001 13 9/21/1, 3:40 PM

LGN 135-02-002
Network Participation Groups 1-16, 6-2 ff., 6-15 (fig.)

Air Control 6-8
Buffering 6-16
Electronic Warfare 6-11, 7-7
Fighter-to-Fighter 3-2, 6-13
Indirect PPLI 6-12
Initial Entry 6-5
Joint PPLI 6-13
Mission Management 6-8
Network Management 6-6
PPLI 6-6, 6-7
Residual Message 6-14
Round Trip Timing 5-33, 6-5
Status 6-6, 6-7
Surveillance 6-7, 7-7
Voice Group A 6-11
Voice Group B 6-12
Weapons Coordination 6-12
Network Time Reference 6-28
NICP 2-23, 3-6, 4-20
No Statement 5-23, 5-28
Node 1-14
NonC2 Unit 3-2, 6-18
Normal IPF 5-64
Normal Range 5-51
Notch Filter Assembly 2-26, 2-27 (fig.), 5-59
O
OPTASK LINK 2-31, 5-66, 6-25, 6-27
APP_E_2001 14 9/21/1, 3:40 PM

Appendixes
P
Packed-2 5-28, 5-30, 5-45
Double pulse 5-49 (fig.), 5-51
Single pulse 5-48 (fig.)
Packed-4 5-28, 5-30, 5-45, 5-50 (fig.)
Packing Structures 5-46 (fig.)
Formats 5-46 (fig.)
Limitations 5-50
Packed-2 5-28, 5-30, 5-45, 5-48 (fig.), 5-49 (fig.)
Packed-4 5-28, 5-30, 5-50 (fig.)
Standard 5-28, 5-30, 5-47 (fig.)
Upper packing limit 5-51
Parametrics 7-7
Parity 5-25, 5-29 (fig.)
Participation Groups 6-3 (fig.).
See also Network Participation Groups
Partitioned variable mode 6-57
Passive Synchronization 6-32, 6-37, 6-42
Peacetime Constraints 5-63, 5-67 (fig.)
Plain Text Processor 4-26
Platforms App B
Position. See also PPLI
Geodetic 1-23, 6-29, 6-42
IJMS 6-14
Quality 6-42, 6-43
Reference 6-29, 6-42
Relative 6-30, 6-42
Power
High 2-26, 5-66
Low 2-25, 2-26, 5-66
TACAN/DME 5-57
Power Interface Units 2-28
Powers of 2 5-5 (fig.)
APP_E_2001 15 9/21/1, 3:40 PM

LGN 135-02-002
PPLI 2-16, 6-6, 6-7, 7-5, 6-38 ff.

and Passive synchronization 6-37
for Link-11 units 6-12
Joint 6-13
Primary User 6-32
Product
Data 7-7
Mode A-21
Propagation 5-21
Pseudorandom Noise 5-40
Pulses. See also Symbol
Double 5-43
Encoding 5-41
Single 5-43
Synchronization 5-44
Time refinement 5-44
Push-to-Talk Protocol 4-29
Q
Quality
Position 6-42, 6-43 (fig.)
Reported in TOM 4-18
Time 5-18, 5-32, 5-33, 6-28, 6-41 (fig.)
R
Radio Horizon 3-2
Distance to 3-7, 3-8 (fig.), 3-9 (fig.)
and Effective earth radius 3-7
Radio Path Length 3-9 (fig.)
Radio Silence. See Long Term Transmit Inhibit
Range
Extended 5-21, 5-51, 6-63
Line-of-sight 3-7, 3-8
Normal 5-21, 5-51
APP_E_2001 16 9/21/1, 3:40 PM

Appendixes
Raymond Cassette 3-18

Receipt/Compliance 6-39, 6-44 ff.
Receiver/Transmitter 2-25
Reception
Antenna 2-33
Default 6-57
Voice 4-30
Recurrence Rate Number 5-6, 5-7
Reed-Solomon
Codeword 5-25, 5-28, 5-31 (fig.)
Encoding 5-25, 5-29 (fig.)
Notation 5-25
Reference Points 1-25
Relative Navigation 1-24, 2-16, 6-5, 6-7, 6-30, 6-42
Relay 3-7, 6-46 ff.
Blind 6-52
Conditional 6-50
Delay 6-47, 6-48 (fig.)
Flood 6-50, 6-51 (fig.)
Hop count 6-52
Hops 6-46
Paired slot 6-47
Pairs 6-46
Repromulgated 6-52, 6-53 (fig.)
Suspended 6-50
Types of 6-49 ff.
Unconditional 6-49
Reporting Responsibility 7-6, A-12, A-17
Repromulgated Relay 6-52, 6-53 (fig.)
Residual Message 6-14
RF Limiter 2-26
RF Signal 5-1 ff.
Communication modes 5-52 ff.
Roles 6-27 ff.
APP_E_2001 17 9/21/1, 3:40 PM

LGN 135-02-002
Round-Trip Timing
Calculation 5-37 (fig.)
Interrogation 5-33
Message formats 5-34 (fig.)
NPGs 5-33
Reply 5-34
S
Satellite communications 6-63
Secondary Navigation Controller 6-31
Secondary User 6-32
Secure Data Unit 2-25, 2-31, 5-28, 5-34
Secure voice 2-17
Security
Communications 6-54 ff.
Crypto period designator 6-55, 6-56 (fig.)
Cryptovariables 6-54
Cryptovariable Logical Label 6-54 ff.
Message 1-15, 6-57
Secure Data Unit 2-25, 2-31, 5-28, 5-34
Transmission 1-15, 5-40, 6-57
Set 5-3
SICP 2-22, 4-9, 6-16
Signal Power 2-25
Simulation indicator 7-12
Single Pulse 5-43
Packed-2 5-48 (fig.)
Packed-4 5-50 (fig.)
Slot Index 5-3
Source Track Number 6-39
Spread Spectrum 5-38
APP_E_2001 18 9/21/1, 3:40 PM

Appendixes
Stacked Net 1-8, 1-17, 5-16, 6-60

Air control 6-8 ff.
Fighter-to-fighter 6-13
RTT 5-33
Voice 6-11
Stand-Alone Control Panel 4-32
Standard Packing 5-28, 5-30, 5-45
Format 5-47 (fig.)
Status
BIT function 4-26
Friendly aircraft 1-21
Net numbers 6-40
NICP 4-24
PTP 4-26
SICP 4-24
Terminal 4-14, 4-16, 4-17, 4-20
Voice channel 4-24
Platform 6-6, 6-7, 7-5
Surveillance 6-7, 7-6, 7-7
Symbol
Double pulse packet 5-43
Interleaving 5-30, 5-31 (fig.)
Packet 5-19, 5-29 (fig.), 5-38 ff.
Single pulse packet 5-43
Transmission 5-40
Synchronization 2-17, 5-18
Active 6-36 ff.
Coarse 5-18, 6-5, 6-36
Pulses 5-19, 5-44
Fine 5-18, 6-5, 6-36
Passive 6-32, 6-37, 6-42
PPLI 6-7
Round-trip timing 5-32
System capacity 1-12
System Time 5-18, 6-28
APP_E_2001 19 9/21/1, 3:40 PM

LGN 135-02-002
T
TACAN
Control 4-32
Description 5-56, 5-57 (fig.)
Frequencies 5-53, 5-56
Terminal function 3-6, 3-17, 3-23
TOM 29 4-18
Tactical Data System 2-8 ff.
Certification 2-10
TADIL 1-2
TAMPS 3-18, 3-28
Tape Recording 4-14
TDMA 5-2 ff., 5-21
Terminal Input Messages 4-9 ff.
Terminal Output Messages 4-14 ff.
Time
of Arrival 5-34 ff.
Quality 5-18, 5-32, 5-33, 6-28, 6-41 (fig.)
Refinement 5-20, 5-44
Slice 5-17
System 5-18, 6-28
Time Slot 5-3
Access modes 6-19 ff.
Anatomy 5-38 ff.
Assignment 5-10, 6-4, 6-17 ff.
Components 5-19
Data 5-20
Donated 6-45
Duration 5-3
Header 5-20, 5-22, 5-28, 5-43
Index 5-3
Interleaving 5-3
APP_E_2001 20 9/21/1, 3:40 PM

Appendixes
Intervals between 5-7 (fig.)

Jitter 5-19
Packing structures 5-28 ff.
Paired 6-46
Propagation 5-20
Range 5-21
Sets of 5-3
Synchronization 5-19, 5-44
Time refinement 5-20, 5-44
Time Slot Block 5-10, 5-15
Time Slot Duty Factor 5-68
100/50 5-66, 6-50
40/20 5-64, 6-50
Time Slot Reallocation 6-24
Today/tomorrow pairs 6-55
Track
Blocks A-15
Common A-17
Exercise 7-12
Identification 1-21
Land 1-25
Number association A-18
Numbers 1-20, 5-34
Quality 1-21
Reporting 7-6
Simulated 7-13
Source 6-39
Status 1-21
Track Block
Data forwarding A-16
High A-15
Low A-15
Training 7-12 ff.
Transmission
APP_E_2001 21 9/21/1, 3:40 PM

LGN 135-02-002
Transmission
Inhibit 6-32
Security 1-15, 5-40
Symbol 5-40
Type 5-46
Type Modifier 5-46
U
UHF 5-52
Unit Types 6-18 (fig.)
Uplink. See Air Control
Upper Packing Limit 5-51
Users 6-32
V
Variable-Format Messages 5-22, 5-26 (fig.)
Voice 4-29 ff.
Channel selection 3-17
Channel status 4-24
Data rates 4-31 (fig.)
Free-text messages 5-27
Group A 6-11
Group B 6-12
Receive processing 4-30
Transmit processing 4-30
VOR 5-56
VORTAC 5-56
APP_E_2001 22 9/21/1, 3:40 PM

Appendixes
W
Weapons Coordination 6-12, A-20
Word
CCSK code 5-39 (fig.)
Continuation 4-11, 4-16, 5-23, 5-24 (fig.)
Extension 4-11, 4-16, 5-23, 5-24 (fig.)
Initial 4-11, 4-16, 5-23, 5-24 (fig.)
No Statement 5-23
R-S code 5-25 ff.
APP_E_2001 23 9/21/1, 3:40 PM

08-0117
Comments,
Suggestions,
and Ordering
Northrop Grumman is interested in your comments concerning this

guidebook, Understanding Link-16. Please send them to:
Attention: Guidebooks
Northrop Grumman Corporation
Communication & Information Systems Division
4010 Sorrento Valley Boulevard
San Diego, California 92121-1498, USA
Facsimile: (858) 455-7589
E-mail: guidebook@northropgrumman.com
Additional guidebooks may be ordered by calling

(800) 274-1330 x7280.
All major credit cards are accepted.
NCTSI POINTS OF CONTACT
Headquarters
Navy Center for Tactical Systems Interoperability
CAPT Ian Fetterman, Commanding Officer
53690 Tomahawk Drive, Suite A125
San Diego, California 92147-5082
Telephone: 619-553-7304 FAX: 619-553-9366
(DSN 553)
Fleet Support
LCDR James Darenkamp
Telephone: 619-553-0768
FAX: (619)553-0767 (DSN 553)
Detachments Detachments
Pacific Fleet: Atlantic Fleet:
NCTSI Detachment ONE NCTSI Detachment TWO
OIC LCDR Randall Peters OIC LCDR Dan Wessman
53610 Catalina Boulevard 1911 "D" Avenue
San Diego, California 92147-5086 Naval Station, Norfolk, Virginia 23511-3798
Telephone: 619-553-0264 (DSN 553) Telephone: 757-444-5509 (DSN 564)
FAX: 619-553-0260 FAX: 757-445-4036 (DSN 565)
NCTSI Detachment FIVE NCTSI Detachment FOUR

OIC LT Thomas Felten OIC LT Rick Callesen
Fleet Activity, Yokosuka, Japan NAS Sigonella, Italy
PSC-473, Box 73 FPO AE 09627-3110
FPO AP 96349-3003 Telephone: 011-39-095-86-5645
Telephone: 011-81-311-734-7941 (DSN (314) 624-5645)
(DSN 243-7941)
FAX: 011-39-095-86-5610
FAX: 011-81-311-734-7943
NCTSI
nctsi_back 2 8/8/2, 5:17 PM

Understanding Link 16

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Understanding Link 16

Uploaded by

Copyright:

Available Formats

Understanding

Distributed by: NCTSI

First Revision: September 1996

Northrop Grumman Corporation

1_LK16_title-NCTSI 1 8/8/2, 2:06 PM

■ Illustrations Figures and diagrams are intended to complement the

Recommended procedures are highlighted

In this guidebook, we present extensive information on the Navy

2_INTRO_TOC 1 9/19/1, 12:23 PM

Chapter 2 The Shipboard Link-16 Equipment

Chapter 3 The Airborne Link-16 Equipment

Chapter 4 Messages and Interfaces

Chapter 5 Building the JTIDS RF Signal

2_INTRO_TOC 2 9/19/1, 12:23 PM

Chapter 7 Link-16 Operations

2_INTRO_TOC 3 9/19/1, 12:23 PM

LK16 CH1 1 9/20/1, 5:55 PM

All Those Names: Link-16, TADIL J,

1-2 Section A Background

LK16 CH1 2 9/20/1, 5:55 PM

Link-16 uses the Joint Tactical Information Distribution

Host Class 2 Class 2 Host

Section A Background 1-3

LK16 CH1 3 9/20/1, 5:55 PM

Throughout this guidebook, the term “Link-16” refers to the tactical

Link-16, using the JTIDS data terminal, represents major

1-4 Section A Background

LK16 CH1 4 9/20/1, 5:55 PM

Figure 1-2. While Link-16 is functionally similar to the combined capabilities

Section A Background 1-5

LK16 CH1 5 9/20/1, 5:55 PM

Figure 1-3. Link-11 uses a netted architecture and a polling protocol in

1-6 Section B Comparison to Link-11 and Link-4A

LK16 CH1 6 9/20/1, 5:55 PM

The Link-11 net is normally operated according to a protocol called

Link-4A uses a command-and-response protocol and the principle of

CTL A/C CTL A/C CTL A/C CTL

Figure 1-4. Link-4A uses time division multiplexing and a command-and-

Section B Comparison to Link-11 and Link-4A 1-7

LK16 CH1 7 9/20/1, 5:55 PM

Link-16 uses the principle of Time Division Multiple Access

Multiple nets can be “stacked” by allowing time slots to be

1-8 Section B Comparison to Link-11 and Link-4A

LK16 CH1 8 9/20/1, 5:55 PM

Section B Comparison to Link-11 and Link-4A 1-9

LK16 CH1 9 9/20/1, 5:55 PM

The Link-4A message exchange is divided between control

In Link-16, either 3, 6, or 12 Link-16 words can be transmitted

The effective tactical data rates of Link-16 are 26,880, or

All of these rates are technically correct. The appropriate rate

1-10 Section B Comparison to Link-11 and Link-4A

LK16 CH1 10 9/20/1, 5:55 PM

Message Data Rates (kbps)

Link-4A TDM Command/Response V-Series 3.06 – –

Link-11 Netted Polling by Net Control M-Series Fast 1.80 – 2.250

Section B Comparison to Link-11 and Link-4A 1-11

LK16 CH1 11 9/20/1, 5:56 PM

that approximately 20 different nets can be collocated without

The actual increase in the rate at which tactical data is

It is sometimes useful to estimate the system capacity of

Techniques for increasing capacity, such as data compression

1-12 Section B Comparison to Link-11 and Link-4A

LK16 CH1 12 9/20/1, 5:56 PM