Главная Manuals TADIL J INTRODUCTION TO TACTICAL DIGITAL INFORMATION LINK J AND QUICK REFERENCE GUIDE (JUNE 2000)
|
|
|
(a) The KGV-8B requires the KYK-13 and LCU for key loading.
(b) The KGV-8B has storage capacity for eight keys and is loaded using DTD.
It can be loaded with either red (normal unencrypted) or black (encrypted) keys and
does not require a keyer control panel (KCP) or USN LCU for loading keys.
(2) Employment. SDU employment is shown in Figure B-1.
2. Key Distribution
TADIL J crypto key distribution and handling are essentially the same as traditional
procedures for crypto, except for long-term electronic storage, multiple segments of
keys in the DTD, and the requirement to load two days crypto into the SDU at one time.
Use of the LCU or KCP is required for the KGV-8 (E2) and KGV-8A. All models of the
KGV-8 can use the same key material short titles. In addition, the KGV-8B can also use
the encrypted versions of those short titles.
3. Secure Data Unit Functions
a. Message Transmission. The terminal provides the plain text message to the SDU
that encrypts the message and provides the encrypted message to the terminal DPG.
The DDP draws a pseudorandom sequence pattern from the key located in the SDU.
This pattern provides the pseudorandom frequency-hopping pattern, the time jitter, and
the frequency spreading to the JTIDS terminal for antijam, low probability of
exploitation and low probability of intercept operations. The SDU provides a
pseudorandom code bit stream to the terminal to encrypt the message for TSEC.
b. Message Reception. The terminal accomplishes uncovering of the message
(TSEC) with the position reference code stream obtained from the SDU. It then passes
the message to the SDU for MSEC decryption and obtains the plain text message from
the SDU for exchange with the host system.
c. Common Variable Mode (CVM). In the CVM, the terminal to generate the
pseudorandom sequence for TSEC operations, and to provide MSEC, uses one
cryptographic variable (key). The operator selects a network design and a single crypto
variable logic label (CVLL) is assigned for both MSEC and TSEC operations. This is the
common means of operation.
USN
KGV-8 (E2)
KGV-8B
USAF
KGV-8A
USMC
KGV-8A and
KGV-8C
USA
KGV-8B
Figure B-1. SDU Employment
B-2
d. Partitioned Variable Mode (PVM). In the PVM, the terminal to generate the
pseudorandom sequence for encryption of the message (MSEC) uses one cryptographic
variable (key). A separate cryptographic variable is used to generate the pseudorandom
sequence for transmission of the message.
e. PVM Relay (Blind Relay). Messages received for PVM relay are TSEC-uncovered,
error corrected and coded, and then TSEC-covered for retransmission. These messages
are not MSEC decrypted.
4. Secure Data Unit Setup
The JTIDS terminal can use up to four pairs of crypto keys (today/next day), which
reside in eight SDU memory locations. The SDU (KGV-8) provides—
a. Pseudorandom frequency-hopping pattern.
b. Pseudorandom noise-spreading encryption.
c. Pseudorandom jitter time (STD and P2SP packing modes).
d. Message encryption
5. Cryptographic Variable Logical Label
Each TADIL J network design has a network description that specifies the number
and use of cryptographic variables used within the network design. Cryptographic
variables are used to establish crypto nets and are assigned reference labels called
CVLL. Circuits or groups of circuits called NPGs are established to operate by using
predetermined MSEC and TSEC cryptographic variables. Each NPG is assigned two
CVLLs during network design. The planned SDU location of the crypto keys
corresponding to the CVLLs is also established for each network platform participant.
The CVLL is a seven-bit number ranging from 1 to 127.
6. Cryptographic Net Isolation
Configuring the JTIDS terminal’s cryptographic variables creates crypto net
isolation between networks or network users. Differences in terminal loads isolate that
terminal from all other terminals with differing crypto loads. Use of cryptographic
variables to establish isolation of single or multiple units can provide NPG isolation,
blind relays, multinetting of functions (frequency division multiple access), and multiple
networks.
a. Blind Relays. Units designated as blind relays can receive and retransmit
information on assigned NPGs, but are unable to decode the information. Decoding is
accomplished by providing the TSEC key list to the relaying unit, but denying the relay
unit the MSEC key list.
b. Multinetting. Several transmission waveform parameters, including the
frequency-hopping pattern of a network, are pseudorandomly selected based upon the
B-3
encryption key. This allows two NPGs to use the same time slots because each NPG
uses a different frequency-hopping pattern. Different frequency-hopping patterns
ensure that, at any moment in time, the groups would not interfere with one another.
This frequency multiple access expands system capacity beyond any single-terminal
capacity.
c. Multiple Networks. When two or more user groups are geographically
collocated, i.e., within line-of-sight, isolation between the groups can be achieved by
using different crypto keys. This ensures that TADIL J units use different frequency-
hopping patterns, even if each network uses the same TADIL J network design.
7. Daily Cryptographic Rekey Standard
The US and NATO adopted a convention that stipulates that Class 2 JTIDS
terminals are to be rekeyed once a day. Class 2 JTIDS terminals can be loaded with
crypto keys sufficient for two days of operation, with an automatic capability to roll
over, i.e., switch from today’s key to tomorrow’s key at a preset time. Unless otherwise
stipulated in the OPTASKLINK message, encryption devices are rekeyed at 2400 Zulu.
a. Cryptographic Period Designator (CPD). JTIDS Class 2 terminals have eight
memory locations to store crypto keys in the SDU (KGV-8). These memory locations are
numbered “0” through “7”.
(1) For a normal (24-hour) crypto period, memory locations are assigned in pairs
designated as “0 and 1”, “2 and 3,” “4 and 5,” and “6 and 7.” Accordingly, locations 0, 2, 4,
and 6 represent one set of concurrently operating locations called the even locations
and are given the CPD of “0.” Locations 1, 3, 5, and 7 are referred to as the odd locations
and are assigned the CPD of “1.”
(2) To load two days’ keys into the SDU, the operator must determine whether
the key goes into the even location or the odd location. A convention has been accepted
by the US and NATO which defines 1 January 1985 as an odd or O day. Each subsequent
day is defined as odd or even based on this convention.
b. Cryptographic Rollover. At the end of a crypto period, all of the keys that have
been in use, i.e., odd or even, are automatically erased in the SDU and the current CPD
is changed. During the next crypto period, the terminal selects the complimentary set of
keys in the other memory locations for the same time slot assignment. The CVLL used
in the current and next crypto period is the same to permit operation across the crypto
period boundary without a requirement to reinitialize time slot assignments.
8. Key Loading Devices
a. KYK-13 Electronic Transfer Device. A hand-carried, battery-operated electronic
transfer device capable of storing up to six keys.
b. KOI-18 General Purpose Tape Reader. The KOI-18 is a battery-powered device
that reads an eight-level punched tape and converts the information to a serial output
that can be loaded into a KYK-13 or DTD.
B-4
c. LCU. A USN-unique device for loading specific SDU memory locations of the
KGV-8 (E-2) and KGV-8A. It is used in conjunction with the KYK-13 transfer device.
d. Key Control Panel. A USA device similar to the LCU.
e. AN/CYZ-10 DTD. A hand-held portable computer used to store and transfer keys.
The DTD can store up to 1,000 keys and is authorized for long-term storage. It can be
used to transfer keys into other DTDs or directly into the KGV-8 (E-2) or KGV-8B. The
DTD can accept black keys from a computer using JTIDS PC application software. A key
load status log data base and an audit trail data base, internal to the DTD,
automatically keep track of the different crypto keys loaded into and from the DTD.
Either database can be reviewed by the DTD user or uploaded into a PC for storage and
viewing.
B-5
Appendix C
NETWORK DESIGN FACILITIES
JOINT TACTICAL INFORMATION DISTRIBUTION SYSTEM
NETWORK DESIGN LIBRARY
Headquarters US Army Forces Command
ATTN: AFOP-TJ
Building 1283
Anderson Way, SW
Fort McPherson, Georgia 30330-6000
Message Address: CDRFORSCOM GN/AFOP-JT// FT MCPHERSON
POC
DSN Phone CommercialPhone Electronic Mail
LtCoI Bayer or
367-4636
(404) 464-4636
bayerw@ftmcphsn-emh1.army.mil
John Cary
Mr. Neil Hesser
367-3146
(404) 464-3146
hessern@ftmcphsn-emh1.army.mil
Mr. Steve Frolen
367-4744
(404) 464-4744
frolens@ftmcphsn-emh1.army.mil
FAX Nonsecure
367-3148
(404) 464-4608
SERVICE NETWORK DESIGN FACILITIES
US Army
PEO AMD
P.O. Box 1500
ATTN: SFAE-AMD-TSD
Huntsville, AL 35807-3801
Message Address: PEO MISSILE DEFENSE //ALIISFAE-AMD-TSD-C4//
HUNTSVILLE AL 35807-3801
POC
DSN Phone Commercial Phone Electronic Mail
Duty phone
645-5398
(205) 955-5398
md.redstone.army.mil
FAX Nonsecure
645-4446
(205) 955-4446
C-1
US Air Force
Headquarters Air Combat Command
AF JTIDS Network Design
XOYG
205 Dodd Blvd. Suite 101
Langley AFB, VA 23665-2789
Message Address: HQ ACC LANGLEY AFB, e-mail: af.jtids@langley.af.mil
POC
DSN Phone
Commercial Phone
MSGT David White
574-8328/29
(757) 764-8328/29
FAX Secure
574-8461
FAX Nonsecure:
DSN: 574-8460
US Navy
NCCOSC/NRaD
Code 331
53560 Hull Street
San Diego, CA 92152-5001
Message Address: NCCOSC/NRaD Div. Det, SAN DIEGO CA/452N45211451 2/I
POC
DSN Phone Commercial Phone Electronic Mail
Mr. Robert Nydam 553-0525
(619) 553-0525
nydam@manta.nosc.mil
Ms. Kelly Sobon
553-3887
(619) 553-3887
ksweeney@manta.nosc.mil
Mr. Dan Slack
553-3980
(619) 553-3980
(619) 294-8743
slack@nosc.mil
FAX Nonsecure
(619) 553-6165
US Navy Center for Tactical Systems Interoperability (NCTSI) Code 21
53690 Tomahawk Drive Suite A125
San Diego, CA 92147-5082
Message Address: NCTSI SAN DIEGO CA//NO1//
POC
DSN Phone Commercial Phone Electronic Mail
CMD D.W. Daugherty
553-7332
(619) 553-7332
daughert@nosc.mil
Mr. Mike Gregory
553-7297
(619) 553-7297
gregory@manta.nosc.mil
LCDR David Leingang
553-7298
(619) 553-7298
liengang@manta.nosc.mil
LCDR Jesse Prothro
553-7223
(619) 553-7323
Duty phone number
553-9327
(619) 553-9327
FAX Secure
553-7294
(619) 553-7294
FAX Nonsecure
553-9366
(619) 553-9366
C-2
US Marine Corps
Marine Corps Tactical Systems Support Activity (MCTSSA)
Air Defense Systems Division (AD-09)
Marine Corps Base, Camp Pendleton, CA 92055-5171
Message Address: MCTSSA CAMP PENDLETON CA/ADSD/AD-0911
POC
DSN Phone Commercial Phone Electronic Mail
Mr. Daniel Nygren
365-2585
(760) 725-2585
daniel.nygren©mctssa.usmc.mil
Duty phone number
365-2617
(760) 725-2617
FAX Nonsecure
365-9512
(760) 725-9512
C-3
Appendix D
ARMY TACTICAL DATA LINK-1
1. General Description
Army Tactical Data Link-1 (ATDL-1) is a dedicated, point-to-point, duplex, digital
data link employed to exchange real-time tactical data between a C2 land unit and a
surface-to-air missile (SAM) system or between multiple SAM systems. Units that
exchange data via ATDL-1 are designated supporting units (SUs).
2. Operational Characteristics
a. Communications Medium. ATDL-1 can be transmitted over landlines (wire or
fiber optic cable), single-channel radios, or multichannel radios. Multichannel radios
may be established within LOS, use troposcatter techniques for over-the-horizon
communications, or employ satellite communications. Both ends of the ATDL-1 link
must use a compatible communications system. US forces employ two basic
communications systems: the direct current (DC) digital form and the quasi-analog
form.
(1) The USMC tactical air operations center (TAOC) and battery command post
(BCP), the Army Adaptable Surface Interface Terminal (ASIT) and joint TADIL A
distribution system, and the Air Force control and reporting center (CRC) use the quasi-
analog transmission design (TD), which uses TD 1089 or TD 1316 modulator/
demodulator (modems).
(2) USA air defense artillery (ADA) C2 systems operate using a quasi-analog
form. Transmission and reception of ATDL-1 data, however, is accomplished using DC
digital form and bulk encryption. Conversion is accomplished using an air defense
interface to convert analog signals to digital signals (or vice versa) for transmission and
receipt over the mobile subscriber equipment (MSE) net. Data transmissions are bulk-
encrypted by the MSE. USA ADA units that directly interface with USAF or USMC C2
facilities provide the necessary communications equipment for both ends of the ATDL-1
link. MSE provide bulk encryption. NATO or allied agencies provide no point-to-point
(line) encryption devices. USAF, USMC, or, when available, USA signal units must
provide any required encryption devices where MSE connectivity cannot be established
with USA ADA C2 systems due to unit locations, range, communications equipment
(radio, satellite communications).
b. Communications Architecture. SAM units that use ATDL-1 can be linked
together to form a chain (round-robin) or use a single forwarding unit as a hub with
multiple units tied through the hub. The round-robin mode permits data to be
circulated within three Hawk batteries using ATDL-1 formatted messages. It is used
only in the absence of higher echelons. In the normal mode, ATDL-1 communications
require a separate, dedicated link between each SU that simultaneously transmits and
receives data on two channels—one dedicated transmit line and one dedicated receive
line. When data messages are not being transmitted, each unit transmits a continuous
standby signal to maintain time synchronization.
D-1
c. Data Encryption. ATDL-1 is normally operated in the secure mode using
encryption devices provided by the tactical unit. The configuration of encryption
devices at both ends of the ATDL-1 links must be compatible. Configuration of
encryption devices may be accomplished by means of strapping (physical) or
initialization (electrical). The configuration means used are dependent on the tactical
data system (TDS) configuration. When MSE communications are used to provide the
ATDL-1 link, secure mode operations are accomplished through bulk encryption of data
transmissions by the MSE nodes. NATO or allied ADA C2 units provide the necessary
equipment for data compatibility with USAF or USMC C2 facilities. When ATDL-1 is
transmitted over landlines (wire or fiber-optic cable), single-channel radios, or
multichannel radios, KG-30 (analog) or KG-84 (digital) single-channel data encryption
devices are used. Both the KG-30 and KG-84 use two key cards; one for transmitted
data and one for received data. Encryption keys for the KG-30, KG-84, and KG-94A/KG-
194A are loaded with KYK-13 or KOI-18 devices.
d. Data Rates. ATDL-1 can be transmitted at 600, 1200, or 2400 bits per second
(bps). If the quasi-analog transmission scheme is used, the audio signals are modulated
using frequency shift keying.
e. Message Standard. ATDL-1 uses a B-series message and transmits the data in an
81-bit message frame, which consists of a start group, seven data groups, and a check
group. ATDL-1 messages are defined in Military Standard (MIL-STD) 6013.
f. Coordinate Reference Convention. ATDL-1 units exchange positional information
on units, tracks, strobes, and points by transmitting an X and a Y coordinate that is
measured from the SU’s system coordinate center (SCC). An SU’s location is reported to
other interfaced units by transmitting its X and Y coordinates measured from the data
link reference point (DLRP). Once an SU’s position is known, all positional information
received from that SU is displayed in relation to the SCC.
g. Transmission Structure.
(1) Test Message. Once the ATDL-1 link has been initialized, a test message is
transmitted. The continuing operational status of the link depends upon the exchange
of the B-series ATDL-1 test message. This is a special message that is transmitted on a
periodic basis by both ATDL-1 TDSs. Failure to receive this message for a specific
period of time causes the ATDL-1 link to lose its operational status. When the link
status drops to less than operational, all data exchange ceases except for the idle
pattern (no information signal) and the ATDL-1 test message.
(2) Idling Condition. Once the link is established and no information is to be
transmitted, the system automatically assumes an idling condition. The idle signal
consists of alternating marks and spaces (1 0 1 0) and is continuously transmitted by
each unit on the ATDL-1 link. This signal permits the two modems to remain in time
synchronization and is interrupted only for transmission of a data message, termination
of the link by operator action, or equipment malfunction. The modem indicates when a
good idle pattern is received. This standby signal, or idle pattern, always starts with a
(1) and ends with a (1) bit set to distinguish it from the beginning of a start code.
(3) Data Message. ATDL-1 uses an 81-bit message frame that consists of—
D-2
(a) Start Group - Nine bits; all set to (0).
(b) Data Group - Seven data groups of nine bits, each immediately following
the start group, with the first bit of each data group set to (1) and the next eight bits
consisting of the B-series message.
(c) Check Group - One check group completes each transmission frame and
comprises one fixed bit, followed by eight check bits.
(4) Contiguous Data Message Grouping. B-series message-transmit rules in MIL-
STD 6013 for ATDL-1 require transmission of multiple message sets. These message
sets are transmitted as a contiguous set with no requirement for an idle pattern to be
transmitted between messages. In a contiguous set, messages are transmitted back-to-
back with no time delay between sets. Contiguous message sets occur with message
start codes immediately following the last bit of the previous message’s check group. It
is therefore possible to have extended interruptions of the “no information signal” (idle
pattern).
(5) Noncontinuous Data Message. A noncontinuous message set is a group of
multiple messages separated by the insertion of a “no information signal,” rather than
transmission of messages back-to-back. When a “no information signal” (idle pattern) is
inserted between messages, the “no information signal” always starts with a (1) bit and
ends with a (1) bit.
h. Unit Address. Each unit reporting on the ATDL-1 link is assigned a unique
station address. This address or TN is assigned in OPTASKLINK message and consists
of two alpha characters that represent the station address and a three-digit octal
number, 000 to 777. The first alpha character can be from A to N, P and Q. The second
alpha character can be from A to H. A unit operating on multiple ATDL-1 links uses the
same address for all links. An SU (fire unit) is assigned a track number (TN) by its
reporting unit (RU).
(1) Restrictions. The address AA000 is used to indicate no statement/unknown.
AA and QH are illegal values for use as station addresses. If the address of the directly
tied unit changes, the data link requires reinitialization.
(2) SUs. Units operating on a single ATDL-1 link are designated SUs. C2 units
operating on multiple links (ATDL-1 and TADIL B) are designated forwarding reporting
units (FRUs). Units operating on TADIL A and/or TADIL B and ATDL-1 are designated
forwarding participating units (FPUs). For an FPU, a single two-digit address is used in
place of the normal three-digit address for RUs. This restriction is imposed by the
TADIL A data terminal set (DTS), which only allows a two-digit octal address from 01 to
76. The ATDL-1 address used by an FRU or FPU is required to be two alpha characters
and three octal digits.
i. TNs. An ATDL-1 TN consists of two alphabetical characters and three octal
digits. An ATDL-1 TN derives its two alphabetical characters from the station address of
the unit initiating the track and a unique three-digit octal number derived from the TN
block assigned to the unit. The Hawk BCP/platoon command post reserves TNs XY001
through XY006 for the following specific uses where X represents the values A to N, P
and Q, and Y. represents the values A to H.
D-3
XY001 and XY002
reserved to report Hawk fire sections.
XY003 through XY004
used to report engaged electronic
countermeasure emitters.
XY005 through XY006
used to report center bearings of high-
power illuminator sector scan or center
bearing of low-altitude simultaneous
Hawk engagement zone.
(1) The unique address AA000 is used to indicate no statement/unknown.
(2) The unique address QH is used only as a general address. QH is illegal for use
as a station address.
j. Link Initialization.
(1) Full Data Transmit (FDT) Mode. Once the operator has designated an ATDL-
1 link, it is physically activated. Upon activation, the ATDL-1 standby signal is
transmitted along with the periodic ATDL-1 test message. The ATDL-1 test message
contains the data link address of the transmitting unit, which provides a capability to
perform a loop-back check of the communications path, data path, and encryption path.
The FDT mode provides for automatic reporting of all tracks and information as soon as
the link is operational.
(2) Limited Data Transmit (LDT) Mode. When an ATDL-1 SU requests to
initialize its ATDL-1 link, it may be directed to enter the LDT mode as a means of
resolving dual designations prior to activating its FDT mode. Only one unit shall be in
LDT mode for a single link. This allows the reception of track reports but inhibits the
transmission of local air tracks until an operator or system action is taken to switch to
the FDT mode. The unit in the LDT mode shall begin transmitting its surveillance
tracks after the operator has determined that all necessary correlations are complete,
or a maximum time limit has elapsed since the transition to an operational link state.
(3) Loop-Back Check. ATDL-1 loop-back is performed by patching the transmit
output of the ATDL-1 modem into the receive input of the ATDL-1 modem. When the
ATDL-1 link is activated in the loop-back configuration, the modem receives its own
signal, the ATDL-1 link is activated, and test messages are transmitted by the TDS. The
TDS recognizes its data link address contained in the ATDL-1 test message and displays
to the operator the status of the loop-back condition. Loop-back can be performed at
various points throughout the ATDL-1 link and includes establishing loop-back at the
system’s own modem or switching the cable connection at the other end of the ATDL-1
link, i.e., at the remote TDS. This provides a positive means of isolating system
problems.
(4) Automatic Link Initialization. Once valid test messages are received at both
TDSs, automatic link initialization occurs. When required information elements have
been exchanged, the link becomes operational. Data messages are then transmitted by
both TDSs. Failure to receive an ATDL-1 test message for a specified time period causes
the link to be removed from the operational status until a valid test message is
received. This initiates automatic link reinitialization. The ATDL-1 test message is
essential for maintaining an operational ATDL-1 link.
(5) Link States. ATDL-1 has two link states: normal and round-robin.
D-4
k. System Employment. USAF, USMC, NATO, and allied C2 and SAM units employ
ATDL-1. Table D-1 provides the ATDL-1 capabilities and equipment of each Service
system.
3. Planning and Operations
a. US Message Text Formats. Two US message text formats—the tactical
operational data (TACOPDAT) message and the OPTASKLINK message—are used for
planning operations. The data elements and data fields are contained in MIL-STD 6040
(1) TACOPDAT Message. Information required to establish air defense
responsibilities in a tactical area and supplementary orders for a specific area of
responsibility are published in TACOPDAT message.
(2) OPTASKLINK Message. Detailed instructions to establish tactical data link
communications are distributed in the OPTASKLINK message. The OPTASKLINK
message provides tasking, coordinating instructions, and technical parameters for the
TDS and data and voice communications systems. The OPTASKLINK message uses the
entry lists shown in Table D-2. For ATDL-1, sets 42 through 53 of the OPTASKLINK
message are used. These sets were originally designed for TADIL B (Link-11B) but can
be used to provide data for ATDL-1 link operations. See Table D-3.
b. Coordination Communications. Under tactical conditions, initial communication
between two ATDL-1 units is normally established on single-channel tactical voice
radios. These radios provide a means of engineering the communications path; i.e.,
aligning the directional antennas of the data radios used for ATDL-1 communications.
Once multichannel circuits are established, ATDL-1 units begin the coordination
function. This includes confirming the OPTASKLINK data in preparation for link
initialization, coordinating link initialization over voice circuits, and monitoring the
tactical situation. Voice circuits between ATDL-1 units include both engineering and
tactical voice circuits.
c. Data Communications. ATDL-1 communications are normally transmitted over
tactical radios. If a multichannel radio is used, a directional antenna is normally
employed and aimed at the receiving antenna, either LOS, reflected off the troposphere,
or relayed by an orbiting satellite. Communications personnel normally engineer ATDL-
1 circuits. ATDL-1, when using multichannel radios or multiplexing to provide a duplex
circuit for data exchange, provides additional channels that are normally available on
data radios for voice communications between directly tied units. Once directional
communications are established between two units, a voice channel is used to
coordinate the initialization of data communications.
d. TDS. While directional communications are being established, the TDS is
initialized with OPTASKLINK data and any unique system data required to establish
data link communications and conduct operations. At this time, a system may perform
internal loop-back checks to verify connectivity between the TDS, encryption
equipment, and modems. Once tactical communications are established, the unit is
ready to perform an end-around loop-back. This is a loop-back check of the entire
communications path by patching the modem of the remote unit and receiving its own
signal back at its own site. Each unit can perform this end-around loop-back check to
adjust system levels and evaluate system performance.
D-5
Table D-1. ATDL-1 Systems
Weapon
Nation
Service
System/Weapon
TADIL
Equipment
USA
Army
Army Air and Missile
A, B, J, fighter data link
Air defense system
Defense Command
(FDL), ATDL-1
integrator
USA
Army
Brigade fire direction
A, B, J, FDL, ATDL-1
ADSI
center
USA
Army
Battalion Patriot
A, B, J, Patriot Air
Information control
(MIM-104)
Defense Information
center
Link (PADIL), ATDL-1
(AN/MSQ-116)
USA
Army
Battalion FAAD
FDL, B, J
Air battle
management
operations center
(AN/TSQ-182)
USA
Army
Battalion FAAD
FDL, B, J
Air avenue
command and
control
(AN/TSQ-182)
USA
Army
Battery FAAD
FDL
Command post
(AN/TSQ-182)
USA
Marine
Tactical air operations
A, B, C, J, NATO
AN/TYQ-23
Corps
center
Link-1, ATDL-1
USA
Marine
Battery command
ATDL-1
AN/MSW-21
Corps
post
USA
Air
Control and reporting
A, B, C, J, NATO
AN/TYQ-23
Force
element
Link-1, ATDL-1
Denmark *
Hawk MIM-23A/B
NATO Link-1
Egypt
Army
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
France
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Germany *
Army
Hawk MIM-23A/B
B, ATDL-1, NATO
Link-1
Greece *
Hawk MIM-23A/B
Iran
Army
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Israel
Army
Hawk MIM-23A/B
Italy *
Hawk MIM-23A/B
B, ATDL-1, NATO
AN/TYQ-73
Link-1
Japan
Hawk MIM-23A/B
Jordan
Army
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Korea
Army
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Kuwait/Iraq
Army
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Netherlands *
Hawk MIM-23A/B
NATO Link-1
Norway *
Army
NASAM/AMRAAM
NATO Link-1
AIM-120
Hawk MIM-23A/B
Portugal *
NATO Link-1
Saudi Arabia
Hawk MIM-23A/B
B, ATDL-1
AN/TYQ-73
Spain *
Hawk MIM-23A/B
NATO Link-1
Sweden
Hawk MIM-23A/B
Taiwan
Hawk MIM-23A/B
Thailand
Hawk MIM-23A/B
Turkey *
Hawk MIM-23A/B
A, ATDL-1, NATO
Link-1
United
Kingdom
(UK)
Note: NATO Air Defense Ground Environment (NADGE) participants denoted by *. France and the UK interface
with NADGE.
D-6
Table D-2. OPTASKLINK Message Entry Lists
List Number
Title
List Number
Title
11
Location
137
Ship type
211
Interface unit designation
513
Aircraft type
551
Duty assignment
941
Data net operations
2506
Link duty
Table D-3. OPTASKLINK Message Sets
Set
Description
Parameter
42
Link-11B
ATDL-1
43
Period
Start time
Stop time
44
Duty
Unit designation
Duties assigned to the unit
45
Link RU data
Unit designation
Unit call sign
RU/SU number
TN block
NATO track number root for unit reporting tracks
Unit location
46
Link connectivity data
First RU/SU number
Second RU/SU number
Speed of data transmitted 600/1200/2400 bps
Type of connectivity
Name of cryptographic equipment
47
Unit filter
Unit responsible for active filter
Filter direction: transmit or transmit/receive
Type of filter area
Track filter environment
Track filter identity
Track filter special conditions: special processing unit/exercise
48
Area
Geographic area of filter
49
Circle
Center of circular filter
50
Rectangle
Location of first corner of rectangular filter
Location of second corner of rectangular filter
Location of third corner of rectangular filter
Location of fourth corner of rectangular filter
51
Boundary
Filter area boundary term
Lower limit of filter boundary
Upper limit of filter boundary
52
General text
Link filter details
Free text
53
Link frequencies
Purpose of link establishment
Frequency or control unit designator
Radio frequency
Priority of circuit
Code for specific mission designator
Intended purpose of frequency; data/voice
D-7
e. Link Operations. Once ATDL-1 data communications are established, the
encryption device is prepared. This synchronizes the time signal between units. When
the link is activated, the input/output channel of the TDS is initialized, which transmits
the initial sequence of messages. The successful exchange of these messages triggers the
transmission of track reports, which initializes the two-way exchange of data between
SUs. Track data is now exchanged between the systems, depending on the whether the
systems are in the FDT or LDT mode. Only one unit shall be in the LDT mode for a
single link. The two-way data exchange is maintained as long as valid test messages are
exchanged.
D-8
Appendix E
NORTH ATLANTIC TREATY ORGANIZATION LINK-1
1. GeneralDescription
NATO Link-1 is a point-to-point, digital data link employed for the automatic data
exchange of real-time tactical air defense and control information between land-based
air defense and aircraft control units. NATO Link-1 can be used as a one way (simplex)
or two-way (duplex) link.
2. Operational Characteristics
a. Communications Medium. NATO Link-1 is normally transmitted over landlines
(telephone) but can be transmitted over multichannel radios. Multichannel radios may
be established within LOS, use troposcatter techniques for over-the-horizon
communications, or employ satellite communications. Both ends of the link must use a
compatible communications system.
(1) USMC and USAF TDSs and USN buffers use differential frequency shift
keying (DFSK) with transmission design 1316 modulator/demodulator (modems) to
interface on NATO Link-1.
(2) Point-to-point (line) encryption devices are not normally used with NATO
Link-1, though standards are provided in Annex A of Standardization Agreement
(STANAG) 5501.
b. Communications Architecture. NATO Link-1 units are normally fixed land-based
centers that are assigned a geographic area of responsibility called an area of
operational interest (AOI). Within the AOI, a track production area (TPA) is established.
Information exchange is between two adjacent centers for the purpose of cross-telling
tracks that transit from one AOI to another. To prevent TPA overlap, a track continuity
area (TCA) is established. A TCA is a belt on either side of the common boundary of two
TPAs of adjacent centers or some other area positioned to ensure that continuity of
tracking is established. All tracks within the TCA are automatically transmitted (cross-
told) with the exception of:
(1) Tracks being cross-told in the opposite direction.
(2) Tracks whose cross-telling is inhibited either locally or by request message.
(a) This employment concept is normally supported by a communications
architecture using fixed landlines that provide both voice and data communications
between adjacent centers. Tactical multichannel radios can be used in place of fixed
landlines.
(b) NATO Link-1 communications require a separate, dedicated link between
each RU, which simultaneously transmits and receives data on two channels—one
dedicated transmit and one dedicated receive line for duplex operations. When data
messages are not being transmitted, each unit transmits a continuous standby signal
E-1
(idling period) to maintain time synchronization. Land-based USAF and USMC TDSs
have a NATO Link-1 capability and can link directly with a NATO site. USN mobile
TDSs (ships and aircraft) operate on TADIL A, TADIL J, and Link-14 and use a ground
based buffer to forward data to NATO Link-1 or TADIL B.
(c) Airborne early warning (AEW) aircraft are integrated into NATO Link-1
through a data forwarder and have AEW ground target areas designated in which air
defense information is forwarded from a ground air defense site to the AEW aircraft.
c. Data Encryption. NATO Link-1 data is not normally encrypted and is normally
exchanged between NATO centers over dedicated telephone lines. Due to this
limitation, US systems that forward TADIL A, TADIL B, or TADIL J data to NATO
Link-1 are required to activate a special processing indicator (SPI) filter to ensure
classified data is not compromised when forwarded to NATO Link-1.
d. Data Rates. NATO Link 1 is operated at a basic speed of 1200 bps with alternate
speeds of 600 and 2400 bps using a DFSK modulated serial bit stream with a
synchronous transmission mode. Phase shift keying may be used by mutual agreement
between two adjacent sites.
e. Message Standard. NATO Link-1 uses S-series messages and transmits data in
pairs as a single 98-bit data message. Messages fall into various functional groups:
(1) Air surveillance.
(2) Strobe information.
(3) Management.
(4) Test.
(5) Frame filler.
f. Information Exchange Scheme. NATO Link-1 units exchange positional
information on strobes, tracks, and points by transmitting X and Y coordinates.
Measurements are made with respect to a system coordinate center agreed upon
between the transmitting site and the receiving site, if authorized by the proper
national configuration manager. The transmitting site transmits information referenced
to the system coordinate center of the specific Link-1 interface. Normally a NATO
Link-1 site uses the center of its data storage area (DSA) as the coordinate center. A
DSA is the maximum area within which an automated air defense facility is able to store
tracks in its computers. The DSAs of adjacent air defense facilities must overlap one
another.
g. Track Data. Track data is assigned priority for transmission (telling).
h. NATO Track Numbers (NTNs). NTNs consist of two alpha characters and three
octal numbers. The alpha characters are assigned from A, E, G, H, J, K, L and M, and
the three digit octal numbers range from 001 to 777. When tracks with non-NTNs are
forwarded to NATO Link-1, the forwarding unit or buffer is normally assigned a TN
block using the prefix AA. This TN prefix indicates to the NATO Link-1 units that the
track source is from a data forwarder.
E-2
i. Transmission Structure.
(1) Idling Condition. When no information is to be transmitted, the system
automatically assumes an idling condition by transmitting a continuous series of binary
ones. This signal, or idle pattern, always ends with a (1) bit set to distinguish it from the
beginning of a start code; i.e., eight zeros. Transmission of information can be resumed
at any time by transmitting a start code. An idling period may occupy an integral
number of bit positions.
(2) Data Message. NATO Link-1 uses a 49-bit message that consists of the
following:
(a) Start group - One start group begins a message frame. It contains 8 start
bits, all set to (0).
(b) Data Group - Fourteen data groups of 8 bits each include 1 single, fixed bit
to ensure synchronism, followed by 7 information bits.
(c) Check Group - One check group completes the transmission frame. It
contains 1 single, fixed bit, followed by 6 check bits, followed by 1 final bit that
completes the transmission frame. This results in an information message of 49 bits
comprised of a 6-bit label and 43 information bits.
(3) Message Frame. A message contains 98 message bits divided into two
messages, each of which is divided into seven message groups of 7 bits each.
(4) Transmission Frame. A transmission frame consists of 128 transmission bits
divided into 16 transmission groups of 8 bits each.
(5) NATO Link-1 Test Message. Label 101110 identifies a test message. It is
generated by repeating a pattern consisting of the 6 label bits and a value of zero in bit
position 7 in each message group. The test message is transmitted in pairs every 10
seconds (+ or -1 second) each transmit cycle.
j. Link Transmission Cycle. Under normal conditions (all tracks can be told during
the cycle), the information on each track is updated at a fixed rate. This rate may be the
same as the radar antenna scan rate or 10 seconds. When there are more tracks to be
told than can be accomplished in this fixed cycle, the cycle is extended to ensure telling
of all tracks with mandatory transmission.
k. Multiple Transmission Operation. The message source synchronizes and staggers
start groups on various circuits when necessary to use a number of circuits in parallel
between NATO centers. This permits the transfer of tracks within one 10-second cycle
and permits interleaved operation of data processing equipment.
l. System Employment. NATO Link-1 is used by the USN, USMC, USAF, and NATO
centers. NATO centers include NATO Air Defense Ground Environment, United
Kingdom Air Defense Ground Environment, Spanish Air Defense System, Italian
System for Point Air Defense, and German Air Defense Ground Environment sites.
NATO Link-1 capabilities and the equipment of each US service system are provided in
Table E-1.
E-3
Table E-1. NATO Link-1 Capabilities
Tactical Data
Nation
System
System
Equipment
Link Capabilities
Belgium
NATO Air Defense
Sector Operations
Ground Environment
Center
France
Systeme de
AWACS
Link-1, Link-11,
Traitement et
AEGIS
Representation des
Informations de
Defense
Germany
German Air Defense
Sector Operations
Link-1, Link-11,
Ground Environment
Center
Link-11B, AEGIS
Iceland
Islandic Air Defense
Sector Operations
Link-1, Link-11
System
Center
Italy
System for Point Air
Link-1, Link-11
Defense
Norway
NATO Air Defense
Sector Operations
Ground Environment
Center
Netherlands
Sector Operations
Link-1, Link-11
Center
Portugal
Portuguese Air
Sector Operations
Command and
Center
Control System
Spain
Spanish Air Defense
Sector Operations
System
Center
UK
Improved United
Sector Operations
Link-1, Link-11,
Kingdom Air Defense
Center
Link-16, United
Ground Environment
Kingdom AEGIS
US
Joint Tactical Air
USAF-AOC
AN/TYQ-23
TADIL-A, TADIL-B,
Operations
USAF- CRC/CRE
AN/TYQ-51
NATO Link-1
USMC-TACC
AN/TYQ-23
TADIL-A, TADIL-B,
USMC-TAOC
TADIL-C, ATDL-1,
USN- Ship Shore
NATO Link-1,
Ship Buffer
TADIL-A, TADIL-B,
NATO Link-1
TADIL-A, TADIL-B,
TADIL-C, ATDL-1,
NATO Link-1
TADIL-A, NATO
Link-1
An ADSI is used in
the USAFE CAOC at
Vicenza, Italy. They
receive an IJMS feed
from an AF CRC.
m. NATO Link-1 Operation. Each unit reporting on NATO Link-1 is assigned a
unique address. This address, or TN, is assigned in the OPTASKLINK message and is
two alpha characters and three octal numbers ranging from 001 through 777. A unit
operating on multiple NATO Link-1 interfaces uses the same address for all NATO
Link-1 links. Units operating on a single NATO Link-1 are designated RUs. Units
forwarding between TADIL A, TADIL B, or TADIL J and NATO Link-1 are designated
forwarding RUs. Additionally, the USN employs a land-based buffer that forwards
between TADIL A or TADIL J and NATO Link-1 or TADIL B. Buffer units forward data
E-4
to and from NATO Link-1 and are designated FPUs in US terminology. The TN assigned
to a track by a NATO unit specifies track origin as the two-character alphabetical code.
(1) NATO Link-1 Link Initialization. Once an operator designates a NATO
Link-1, it is physically activated. Upon activation, the NATO Link-1 test message is
transmitted.
(2) Loop-Back Check. NATO Link-1 loop-back is performed by patching the
transmit output of the NATO Link-1 modem into the receive input of the NATO Link-1
modem. When the NATO link is activated in the loop-back configuration, the modem
receives its own signal and the NATO link is activated. Loop-back can be performed at
various points throughout the NATO link. It includes establishing loop-back at the
system’s own modem, or switching the cable connection at the other end of the NATO
link; i.e., at the remote TDS. This provides a positive means of isolating system
problems.
(3) Link Initialization. Once the TDS receives valid test messages, link
initialization occurs and both TDSs transmit data messages.
n. References. NATO Standing Agreements (STANAG) define the message standard
and provide the protocols required for message exchange. NATO allied data processing
publications provide standing operating procedures. Since these are dynamic
publications, the operator should procure the most recent prior to NATO operations.
3. Planning and Operations
Information required to establish NATO Link-1 communications between centers is
distributed in the OPTASKLINK message. The message provides information on the
TDS, data filtering, data, and voice communications parameters. For NATO Link-1 sets
12 through 23 of the OPTASKLINK message are used. See Table E-2.
a. Coordination Communications. Under tactical conditions, initial communications
between two NATO Link-1 units is normally established on single-channel tactical voice
radios. These radios provide a means of engineering the communications path; i.e.,
aligning the directional antennas of the data radios used for NATO Link-1
communications. Once a multichannel circuit is established, NATO units coordinate
over voice circuits to monitor the tactical situation and begin the coordination function,
which confirms the OPTASKLINK data in preparation for link initialization. Voice
circuits between NATO centers include both engineering and tactical voice circuits.
b. Data Communications. NATO Link-1 communications are normally transmitted
over landlines (telephone circuits). If a multichannel radio is used, a directional
antenna is normally employed. It is aimed at the receiving antenna, whether LOS,
bounced off the troposphere, or relayed by an orbiting satellite. Communications
personnel normally engineer NATO Link-1 circuits. When using NATO Link-1
multichannel radios or multiplexing for a duplex circuit data exchange, engineers
should provide additional channels, which are normally available on radios for voice
communications between directly tied NATO centers. Once communications are
established between two units, voice coordination is used to initialize data
communications.
E-5
Table E-2. OPTASKLINK Message Entry Lists
Set
Description
Parameter
12
Link-1
1
13
Period
Start time
Stop time
14
Duty unit designation
Duties assigned to the unit
15
Link RU data
Unit designation
Unit call sign
RU number
TN block
NTN root for unit reporting tracks
Unit location
16
Link connectivity data
First RU number
Second RU number
Speed of data transmitted 600/1200/2400 bps
Type of connectivity
17
Unit filter
Unit responsible for active filter
Filter direction: transmit or transmit/receive
Type of filter area
Track filter environment
Track filter identity
Track filter special conditions: SPI/exercise
18
Area
Geographic area of filter
19
Circle
Center of circular filter
20
Rectangle
Location of first corner of rectangular filter
Location of second corner of rectangular filter
Location of third corner of rectangular filter
Location of fourth corner of rectangular filter
21
Boundary
Filter area boundary term
Lower limit of filter boundary
Upper limit of filter boundary
22
General text
Link filter details
Free text
23
Link frequencies
Purpose of link establishment
Frequency or control unit designator
Radio frequency
Priority of circuit
Code for specific mission designator
Intended purpose of frequency; data/voice
c.
TDS. While directional communications are being established, the TDS is
initialized with OPTASKLINK data and any unique system data required to establish
data link communications and conduct operations. At this time, a system may perform
internal loop-back checks to verify connectivity between the TDS, encryption
equipment, if used, and modems. Once communications are established, the unit is
ready to perform an end-around loop-back, which is a loop-back check of the entire
communications path. This is accomplished by patching the modem of the remote unit
and ensuring that it receives the signal back at its site. Each unit can perform this end-
around loop-back check to adjust system levels and evaluate system performance.
E-6
Appendix F
QUICK REFERENCE GUIDE
This guide contains published service-, joint-, and contractor-developed reference
manuals, handbooks, guides, and pamphlets. Some are still in draft stages. The guide
also contains the addresses of web sites that provide additional information.
1. Reference Documents
Publication Title
Air Force Concept of Link-16 Employment (COLE)
Publisher
USAF Operational Interoperability Requirements
Date
October 1997 Final
Group, AC2ISRC/C2FT,
Version Revision:
Langley AFB, VA
Point of Contact
ASC2A/C2FT, Langley AFB, VA
Executive Summary
This document presents the COLE for AI, CAS, DCA, OCA, and SEAD missions. The
(Abstract)
concept discusses information that will be exchanged, how it will be used to support
each mission, and the data link architecture that will be employed.
Abbreviated
Employment
Strike Packages
Table of Contents
OCA
Intelligence
DCA
Data Link Architecture
AI
Integration
SEAD and CAS
Working Group
Opinion
Publication Title
Joint Multi-Tactical Digital Information Link (TADIL) Operating Procedures* (JMTOP)
Publisher
CJCSM 6120.01B
Date
15 July 1999
Revision: B
Point of Contact
Mr. Ken Bray, Joint Interoperability and Engineering Organization (JIEO)
Commercial: (703) 735-3525 Fax: (703) 735-3256 e-mail: brayk@ncr.disa.mil
Executive Summary
This manual provides planning guidance and operating procedures for deployment of
(Abstract)
Joint TADIL C4I systems within DOD.
Abbreviated
Chapter 1 Introduction
Appendix A Classified Supplement
Table of Contents
Chapter 2 Joint TADIL Interface
Appendix B OPTASKLINK Message
Chapter 3 Responsibilities for Interface
Summary
Chapter 4 Interface Planning
Appendix C TADIL A
Chapter 5 Interface Operating Procedures
Appendix D TADIL J
Chapter 6 Air Control Procedures
Appendix E TADIL B
Chapter 7 Interface Training Procedures
Appendix F IJMS Message Specs
Appendix G TADIL C
Appendix H ATDL-1
Working Group
A comprehensive reference manual tailored to the ICO position. Highly recommended
Opinion
for anyone desiring in-depth information pertaining to JMTOP.
F-1
Publication Title
MIL-STD 6016, DOD Interface Standards, TADIL J Message Standard
Publisher
JIEO
Date
7 February 1997
Revision:
Point of Contact
Mr. Ken Bray (JIEO) Commercial: (703) 735-3525 Fax: (703) 735-3256
e-mail: brayk@ncr.disa.mil
Executive Summary
Describes approved standards to achieve TADIL J compatibility and interoperability
(Abstract)
between C3 systems and equipment of US military forces employed or intended to be
employed in joint tactical operations. This publication is complemented by CJCSM
6120.01, JMTOP, which provides for planning and common procedures to be used by
forces in the joint tactical environment using TADIL J as the basis for information
exchange.
Abbreviated
Chapter 1 Introduction
Appendix A Minimum Implementation
Table of Contents
Chapter 2 General Requirements
Appendix B Data Element Dictionary
Chapter 3 Definitions
Appendix C Data Forwarding
Chapter 4 General Requirements
Appendix D System Implementation
Chapter 5 Detailed Requirements
Appendix E Interface Computer Program
for TADIL J
Repository
Working Group
Highly technical document designed for J-series TADIL message implementation
Opinion
programmers/coders.
Publication Title
Joint Tactical Air Operations (JTAO) Interface Interoperability Handbook (Confidential)
Publisher
US Forces Command (FORSCOM)
Date
October 1995
Revision:
Point of Contact
AFOP-JT, Fort McPherson, GA 30330-6000
DSN: 367-4606 Commercial: (404) 752-4606
Executive Summary
This handbook provides system operators with technical parameters and tactical
(Abstract)
procedures for exchange of real-time data via a TADIL. These procedures are
employed in training, exercises, and combat
Abbreviated
Section 1 Interface Management and Coordination
Table of Contents
Section 2 JTAO Interface Systems and Capabilities
Section 3 Data Link Operating Procedures
Section 4 Data Link Interface Operator Fidelity Drills
Section 5 Data Link Digital Messages
Section 6 JTIDS
Section 7 Joint Theater Missile Defense
Working Group
Opinion
Publication Title
Joint Tactical Data Link Management Plan
Publisher
DOD Assistant Secretary of Defense for C3I
Date
6 June 1996
Revision:
Point of Contact
Dr. Charles Dunhan, Chairman TDLWG DISA/JIEO
Executive Summary
To provide warfighters with improved battlespace SA through standardized tactical C4I
(Abstract)
data links.
Abbreviated
Chapter 1 Overview
Chapter 4 Data Link Migration and
Table of Contents
Chapter 2 Policy Directive
Adoption
Chapter 3 Capabilities
Chapter 5 Summary and
Assessment
Recommendations
Appendixes
Working Group
This document sets forth DOD policy on tactical data links. The policy emphasizes
Opinion
getting away from many unique noninteroperable data links to a common joint tactical
data link based on the J message (JTIDS) standard
F-2
Publication Title
Navy Pamphlet on JTIDS
Publisher
Naval Command, Control, and Ocean
Date
Revision:
Surveillance Center, RDT&E Division,
San Diego, CA 92152-5001
Point of Contact
Executive Summary
An entry-level guide for those with no knowledge of JTIDS.
(Abstract)
Abbreviated
Chapter 1 What is JTIDS
Table of Contents
Chapter 2 How JTIDS is used by the Navy
Chapter 3 TADILs and Host Systems
Chapter 4 The Navy JTIDS Program
Working Group
A pocket-size pamphlet. Good for orienting complete novices.
Opinion
Publication Title
Understanding Link-16: A Guidebook for New Users
Publisher
PMW/PMA 159/LOGICON/US Navy Center for
Date
September 1996
Tactical Systems Interoperability
Revision: 1
Point of Contact
FORSCOM Joint Interoperability Division
LOGICON - (800) 274-1330 or (619) 597-7150
Executive Summary
An in-depth source to understanding the equipment, signal structure, communications
(Abstract)
protocol, and operational considerations of Link-16.
Abbreviated
Chapter 1 Introduction to Link-16
Chapter 5 Building the JTIDS
Table of Contents
Chapter 2 Shipboard Link-16 Equipment
RF Signal
Chapter 3 Airborne Link-16 Equipment
Chapter 6 Structuring the
Chapter 4 Messages and Interfaces
Link-16 Network
Chapter 7 Link-16 Operations
Working Group
Book and compact disc are the same! A great reference manual for the more informed
Opinion
user. Written for the Navy’s shipboard and airborne platforms, but can be related to
multi-service use.
Publication Title
Understanding TADIL Planning and Operations:
A Guidebook for Operators, Planners, and Managers
Publisher
LOGICON/Tactical Systems Division,
Date
Revision:
FORSCOM/NCTSI
October 1996
Point of Contact
(619) 597-7150/(800) 274-1330 FAX: (619) 552-1021
e-mail: guidebook@logicon.com
Executive
Guidebook for reference and review of the operational aspects of TADILs A, B, C, and J,
Summary
including planning and execution.
(Abstract)
Abbreviated
Chapter 1 TADIL Interface
Chapter
9 Information Management
Table of Contents
Chapter 2 Voice Nets
Chapter 10 Intelligence Reporting
Chapter 3 Personnel Responsibilities
Chapter 11 USW
Chapter 4 Planning
Chapter 12 EW Operations
Chapter 5 Execution
Chapter 13 WC
Chapter 6 Self Reporting
Chapter 14 Training
Chapter 7 Reporting Tracks
Appendixes:
Chapter 8 Reporting Reference
TADIL A platforms
Points, Lines, and Area
Acronyms and Abbreviations
Glossary, Index
Working Group
Fourth book in LOGICON TADIL series (Link 4A, Link 11, Link 16). A 400-page detailed
Opinion
introduction for all TADILs (A, B, C, J). Heavy in pictures to aid in understanding. Cannot
be read in one sitting.
F-3
Publication Title
USMC Tactical Data Systems Reference Guide
Publisher
Marine Corps Systems Command
Date
September 1999
C4I Directorate, Quantico
Revision:
MCTSSA Headquarters Interoperability Office
Version 5.2
Camp Pendleton, CA
LOGICON Communications Technology Group
Point of Contact
USMC SYSCOM, C4I Directorate, Quantico, VA
MCTSSA Headquarters Interoperability Office, Camp Pendleton, CA
LOGICON (619) 597-7243/(540) 657-4511
Executive Summary
Guidebook for reference and review of the operational aspects of TADILs A, B, C,
(Abstract)
and J, including planning and execution.
Abbreviated
Types of data links/capabilities
Table of Contents
TDSs/capabilities
Types of message series
US and NATO references
Glossary
Working Group
Opinion
Publication Title
F/A-18 TADIL J Interoperability Reference Book
Publisher
Naval Air Warfare Center
Date
1997
Aircraft Division
Revision:
Patuxent, MD
Point of Contact
Rich Simchak
(30l) 757-0723
Executive Summary
Compilation of TADIL-J system information from the USN F/A-18 project office; used
(Abstract)
as an aid to compatibility/interoperability.
Abbreviated
Information on each current TADIL-J player unit type.
Table of Contents
Working Group
Good TADIL-J reference with emphasis on non-C2 implementation differences
Opinion
available to government agencies, including mobile training.
Publication Title
OPNAV INST C3120.44, TADIL Standard Operating Procedures
Publisher
Chief of Naval Operations (N62)
Date
1997 Revision:
Change 1
Point of Contact
NCTSI
Executive Summary
Provides Navywide standard operating procedures for TADILs A, C and J. Complete
(Abstract)
initialization, operating, and troubleshooting information; some architecture planning
information; limited techniques; discussion of platform-unique capabilities and
limitations.
Abbreviated
Table of Contents
Working Group
Very well done operator and maintainer publication. Accurate but limited discussion of
Opinion
techniques and management procedures. Very limited joint information.
F-4
Publication Title
Link 16 Communications Planning Users Guide
Publisher
PMW 159
Date
1 November 1998
Naval Command, Control and Ocean Surveillance
Revision:
Center
RDT&E Division
Warminster, PA 18974
Point of Contact
PMW 159
(703) 602-4335
Executive Summary
A quick-reference source for Link-16 planning and writing of OPTASKLINK (16)
(Abstract)
Abbreviated
Section 1 Network Design and Naming Convention
Table of Contents
Section 2 OPTASKLINK Message Preparation and Assignments
Section 3 Network Selection and Assignment
Section 4 Participant’s Assignments
Section 5 Participant’s Roles
Section 6 Network Descriptions
Working Group
Well written and easily readable. Examples and “how-to” sections ensure full
Opinion
comprehension. Reasonably simple to complex in detail. Recommended for all
knowledge levels
2. Web Sites Addresses
Organization
URL
DISA TADIL Web Server
DISA Link 16 Home Page
FORSCOM MAJIC
Joint Network Design Library
Link 16 Fleet Support Site
(For access password: link16@spawar.navy.mil)
TACS on the Net, USAF JTIDS
USAF Link-16 Integration Home
Page
US Navy Center for Tactical Systems
Interoperability
F-5
REFERENCES
Joint
CJCSM 6120.01A, Joint Multi-Tactical Digital Information Link Operation Procedures (JMTOP),
24 October 1997.
Military-Standard (MIL-STD)-6016, DOD Interface Standards, TADIL J Message Standard, 7 February 1997.
Joint Tactical Air Operations (JTAO) Interface Interoperability Handbook, October 1995.
Department of Defense, Joint Tactical Data Link Management Plan (JTDLMP), 6 June 1996.
Marine Corps
USMC Tactical Data Systems Reference Guide Version 5.2, September 1999.
F/A-18 TADIL J Interoperability Reference Book.
Navy
Navy JTIDS Pamphlet.
Understanding Link-16, A Guidebook for New Users, September 1996.
Understanding TADIL Planning and Operations, A Guidebook for Operators, Planners and Managers,
October 1996.
OPNAV INST C3120.44, TADIL Standard Operation Procedures (TSOP).
Link 16 Communications Planning Users Guide, 1 November 1998.
Air Force
Air Force Concept of Link-16 Employment (COLE) (DRAFT), October 1997.
References-1
GLOSSARY
PART I - ABBREVIATIONS AND ACRONYMS
A
AADC
area air defense commander
ABCCC
airborne battlefield command and control center
AC2ISRC
Aerospace Command and Control, Intelligence, Surveillance, and
Reconnaissance Center
ACDS
advanced combat direction system (formerly NTDS)
ADA
air defense artillery
ADSI
air defense systems integrator
AEGIS
Airborne Early Warning Ground Environment Integration
Segment
AEW
airborne early warning
AF
Air Force
AFAPD
Air Force Application Program Development
AFB
Air Force base
AFTTP
Air Force tactics, techniques, and procedures
AI
air interdiction
AIC
air intercept control
ALSA
Air Land Sea Application
AOC
air operations center
AOI
area of operational interest
ARTC
Airborne Early Warning Ground Environment Integration
Segment Training and Readiness Center
ASCIET
All Services Combat Identification Evaluation Team
ASIT
adaptable surface interface terminal
ATDL-1
Army Tactical Data Link-1
AW
air warfare
AWACS
Airborne Warning and Control System
B
BCP
battery command post
BP
battery pack
bps
bits per second
C
C2
command and control
C2P
command and control processor
C2W
command and control warfare
C3
command, control, and communications
C3I
command, control, communications, and intelligence
C4I
command, control, communications, computers, and intelligence
CA
California
CAS
close air support
CDS
computer display system
CG
guided missile cruiser
Glossary-1
CJCSI
Chairman, Joint Chiefs of Staff Instruction
CJCSM
Chairman, Joint Chiefs of Staff Manual
COLE
concept of link employment
CPD
cryptograhic period designator
CRC
control and reporting center
CRE
control and reporting element
CSAR
combat search and rescue
CTP
consistent tactical picture
CV
aircraft carrier
CVLL
crypto variable logic label
CVM
common variable mode
CVN
aircraft carrier (nuclear propulsion)
D
D
dimensional
DC
direct current
DCA
defensive counterair
DDP
digital data processor
DDPG
data display processing group
DFSK
differential frequency shift key
DISA
Defense Information Systems Agency
DJRU
dedicated Joint Tactical Information Distribution System relay unit
DL
data link
DOD
Department of Defense
DPG
digital processing group
DSA
data storage area
DSN
defense switching network
DTD
data transfer device
DTG
date time group
DTS
data terminal set
E
ECM
electronic countermeasures
EPLRS
Enhanced Position Location System
ES
electronic support
EW
electronic warfare
F
FAA
Federal Aviation Administration
FAAD
forward area air defense
FDL
fighter data link
FDT
full data transmit
FJU
forwarding Joint Tactical Information Distribution System unit
FJUA
forwarding Joint Tactical Information Distribution System unit -
TADIL J to TADIL A
FM
frequency modulation; field manual
FORSCOM
US Army Forces Command
FPU
forwarding participating unit
Glossary-2
FRU
forwarding reporting unit
FU
forwarding unit
G
GBDL
ground based data link
GEOGRID
geodetic grid
GPS
Global Positioning System
H
HF
high frequency
HIT
Hughes improved terminal
HMMWV
high-mobility multipurpose wheeled vehicle
I
ICC
information coordination center
ICO
interface control officer
IDM
improved data modem
IEJU
initial entry Joint Tactical Information Distribution System Unit
IFF
identification friend or foe
IJMS
interim Joint Tactical Information Distribution System message
standard
IOC
initial operational capability
IU
interface unit
J
JDN
joint data network
JDS
Joint Tactical Information Distribution System deconfliction server
JFACC
joint force air component commander
JFC
joint force commander
JICO
joint interface control officer
JIEO
Joint Interoperability and Engineering Organization
JM
Joint Tactical Information Distribution System module
JMTOP
Joint Multi-Tactical Digital Information Link Operating Procedures
JNDL
Joint Tactical Information Distribution System Network Design
Library
JSTARS
Joint Surveillance Target Attack Radar System
JROC
Joint Requirements Oversight Council
JTAO
Joint Tactical Air Operations
JTF
joint task force
JTIDS
Joint Tactical Information Distribution System
JU
Joint Tactical Information Distribution System unit
K
kbps
kilobits per second
KCP
key control panel
kHz
kilohertz
Glossary-3
L
LCU
load control unit
LDT
limited data transmit
LHA
amphibious landing ship, assault
LHD
amphibious landing ship, dock
LOS
line of sight
M
MACCS
Marine Air Command and Control System
mbs
megabits per second
MCCDC
US Marine Corps Combat Developments Command
MCM
multi-command manual
MCTSSA
Marine Corps Tactical System Support Activity
MHz
megahertz
MIDS
Multifunctional Information Distribution System
MIL-STD
military standard
MM
mission management
MSE
mobile subscriber equipment
MSEC
message security
MTTP
Multi-Service tactics, techniques, and procedures
N
NADGE
North Atlantic Treaty Organization Air Defense Ground Environment
NATO
North Atlantic Treaty Organization
NC
navigation controller
NCS
net control station
NCTSI
US Navy Center for Tactical Systems Interoperability
NDF
network design facility
NDL
network design load
NICPNINICP
network interface computer program
NPG
network participation group
NPS
network participation status
NTDS
naval tactical data system
NTN
North Atlantic Treaty Organization track number
NTR
net time reference
NWDC
Navy Warfare Development Command
O
OCA
offensive counterair
OIC
officer-in-charge
OPR
office of primary responsibility
OPSPEC
operation specification
OPTASKLINK operational tasking data link
P
PADIL
phased-array tracking to intercept of target digital information link
Glossary-4
PATRIOT
phased-array tracking to intercept of target
PC
personal computer
PKTPKT
picket station
POC
point of contact
PPLI
precise participant location and identification
PU
participating unit
PVM
partitioned variable mode
R
R-C
receipt-compliance
RELGRID
relative grid
RELNAV
relative navigation
RF
radio frequency
R/T
receiver/transmitter
RTT
round trip timing
RTT-B
round trip timing-broadcast
RU
reporting unit
S
SA
situational awareness
SADL
situational awareness data link
SAM
surface-to-air missile
SCC
system coordinate center
SDU
secure data unit
SEAD
suppression of enemy air defenses
SICP
subscriber interface computer program
SINCGARS
single-channel ground and airborne radio system
SPI
special processing indicator
STANAG
standardization agreement
STN
system track number
STW
strike warfare
SU
supporting unit
SUW
surface warfare
T
TACC
tactical air command center
TACOPDAT
tactical operational data
TACS
Theater Air Control System
TADIL
tactical digital information link
TAOC
tactical air operations center
TAOM
tactical air operations module
TCA
track continuity area
TD
transmission design
TDLWG
TADIL J Working Group
TDMA
time division multiple access
TDS
tactical data system
TN
track number
TPA
track production area
Glossary-5
TQ
track quality
TRADOC
US Army Training and Doctrine Command
TSDF
time slot duty factor
TSEC
transmission security
TTP
tactics, techniques, and procedures
U
UHF
ultrahigh frequency
US
United States
USA
United States Army
USAF
United States Air Force
USJFCOM
United States Joint Forces Command
USMC
United States Marine Corps
USN
United States Navy
USW
undersea warfare
V
VA
Virginia
VHF
very high frequency
W
WC
weapons coordination
WILCO
will comply
Glossary-6
PART II TERMS AND DEFINTIONS
This Glossary provides the definitions of terms used in this MTTP or likely to be
encountered in TADIL J interface operations
acknowledge. The act of notifying a unit transmitting a message that the message has
been received as a valid message
active synchronization. A procedure used by a JTIDS terminal to effect and maintain
fine synchronization with system time based on the Round-Trip-Timing (RTT) process
address. A number applied to an Interface Unit to associate information and directives
with interface units or tracks for both digital and voice communications
air surveillance. The systematic area observation of air space by electronic, visual or
other means, primarily for the purpose of identifying and determining the movements
of aircraft and missiles, friendly and enemy, in the air space under observation. (Joint
Pub 1-02)
airborne early warning. The detection of enemy air or surface units by radar or other
equipment carried in an airborne vehicle, and the transmitting of a warning to friendly
units.
(Joint Pub 1-02)
area of responsibility. A geographic area assigned to a command and Control System
for track reporting purposes and conduct of tactical operations
association. The automatic or manual establishment of a relationship between two or
more tracks when the information on them is deemed to pertain to the same contact
bit. A binary digit. In the binary system of numbering, each digit can have only one of
two values (0 or 1)
blind relay. A JTIDS terminal programmed to relay data but not initialized to access
the data
category. The environment in which the associated track is operating; i.e., air, surface,
subsurface, land, or space
common track. A track on which two or more interface units locally enter positional
information
coarse synchronization. The state of synchronization with system time that allows a
terminal to receive and process messages and to achieve fine synchronization.
(System
Segment Specification for JTIDS Class 2 Terminal)
combat air patrol. An aircraft patrol provided over an objective area, over the force
protected, over the critical area of a combat zone, or over an air defense area, for the
purpose of intercepting and destroying hostile aircraft before they reach their target.
(Joint Pub 1-02)
combat direction system. Synonymous with Tactical Data System (TDS)
Glossary-7
command and control. The exercise of authority and direction by a properly
designated commander over assigned forces in the accomplishment of his mission.
Command and control functions are performed through an arrangement of personnel,
equipment, communications, facilities, and procedures employed by a commander in
planning, directing, coordinating, and controlling forces and operations in the
accomplishment of the mission.
(Joint Pub 1-02)
command and control interface unit (C2 IU). Any JU, PU, or RU except a nonC2 JU
command and control JTIDS unit (C2 JU). A JTIDS unit with command and control
(C2) capability
contention access mode. A transmit access mode in which a given time slot block is
assigned to more than one JU. Each JU will transmit at a specified rate in the time slot
block by selecting time slots for transmission pseudo-randomly
control. The near-real-time direction of weapons systems and supporting platforms for
the accomplishment of assigned missions
correlation. The determination that a system track or local sensor track data report
represents the same object or point as another track and/or the process of combining
two such tracks/data under one track number
data forwarding. The process of receiving data on one digital data link and outputting
the data, using proper format and link protocols, to another type of digital data links. In
the process, messages received on one link are translated to an appropriate message on
another link. Data forwarding is accomplished by selected forwarding units
simultaneously participating on more than one type of data link. Data that is forwarded
is based on the data received and is not dependent upon the local system data of the
data forwarding unit or its implementation of the received message or forwarded
message
data link. The means of connecting one location to another for the purpose of
transmitting and receiving data. See also Tactical Digital Information Link.
(Joint Pub
1-02)
data link reference point. A fixed geographic reference point specified by appropriate
authority from which a PU/RU can calculate the relative position of own unit and local
tracks (the DLRP is the X-Y grid origin of the TADIL Interface)
data silent mode. A mode of JTIDS/MIDS terminal operation where the terminal
receives but does not transmit fixed word format or variable message format messages
decorrelation.
(1) the determination that locally held track data for a given track
number does not represent the same object or point as a track data being received in a
remote track report for the same track number
(2) the process of establishing a new track number for a local track
when a remote track report with the same track number as the local track is
determined to represent a different object
Glossary-8
dedicated access mode. A JTIDS transmit access mode in which time slots are
assigned to an individual JU for that JU’s exclusive use
drop track. In air intercept, the unit having reporting responsibility for a particular
track is dropping that track and will no longer report it. Other units holding an
interest in that track may continue to report it.
(Joint Pub 1-02)
dual designation. The same track being reported by two or more IUs using two or
more different track numbers
duplicate track numbers. The same track number used by two or more IUs for two or
more different tracks
electronic countermeasures. Actions taken to prevent or reduce an enemy’s effective
use of the electromagnetic spectrum; includes electronic jamming and electronic
deception, including manipulative deception, simulative deception, and imitative
deception
environment/category. The environment in which the associated track is operating;
e.g., air, space, surface, subsurface
epoch. A JTIDS TDMA 12.8-minute time interval consisting of 98,304 time slot
intervals, each of 7.8125 milliseconds duration. The time slots in each epoch are
organized into three sets (A, B, or C) of 32,768 time slots each. There are 112.5 epochs
in a 24-hour period.
(Derived from System Segment Specification for JTIDS Class 2
Terminal)
filter. A process of inhibiting data from transmission on a data link and/or inhibiting
data received on a data link from entry into a unit data base
fine synchronization. The state of synchronization with system time that allows a
JTIDS terminal to transmit messages. A terminal may utilize a passive or active
synchronization procedure to achieve fine synchronization.
(System Segment
Specification for JTIDS Class 2 Terminal)
fixed word format. A 70-bit structure consisting of formalized arrangement of
predefined fields of fixed length and sequence
fixed word format message. A TADIL J message utilizing FWF. An FWF message is
started by an initial word which may then be followed by one or more extension and/or
continuation words
force tell. The process whereby data that are being inhibited by a filter are allowed to
be transmitted or received
forwarding JTIDS unit. A JTIDS unit that translates and forwards data among IUs
using J-series messages and M-series messages. An FJU can function in one of the
configurations defined for FJUA, FJUB, and FJUAB
forwarding JTIDS unit A. A JU communicating on both TADIL A and TADIL J while
forwarding information between TADIL A and TADIL J participants
Glossary-9
forwarding JTIDS unit AB. A JU communicating on TADIL J, TADIL A, and TADIL B
while forwarding information among TADIL J, TADIL A, and TADIL B participants
forwarding JTIDS unit B. A JU communicating on both TADIL B and TADIL J while
forwarding information between TADIL B and TADIL J participants
forwarding participating unit. A PU that is forwarding data between TADIL A and
one or more RUs
forwarding reporting unit free text message. An RU which is forwarding data
between two or more RUs bit-oriented messages whose information bits may be used to
represent digitized voice, teletype, and other forms of free text information
gridlock. A procedure for determining data registration corrective values (pads) by
comparing remote tracks received from a designated Gridlock Reference Unit (GRU) to
local data
hand over. The passing of control authority of an aircraft or other air vehicle from one
control agency to another control agency; hand over action is complete when the
receiving controller acknowledges assumption of control authority
initial entry JTIDS unit (IEJU). Any JTIDS unit that transmits the Initial Entry
message in the appropriate time slot
initial entry. The procedure by which a subscriber JTIDS terminal becomes a system
participant initially and may achieve coarse synchronization with system time.
(System
Segment Specification for JTIDS Class 2 Terminal)
initial slot number (ISN). The number assigned to the first time slot in a block of time
slots relative to the beginning of an epoch
interface unit (IU). A generic term that applies to JTIDS Units (JUs), Participating
Units (PUs), and Reporting Units (RUs) providing information on the interface. The
term C2 IU includes PUs, RUs, and C2 JUs, but not nonC2 JUs
interleaving. A pattern of orienting the data symbols of a message for transmission,
applicable to Modes 1 and 2. A fixed interleaving pattern is used for Mode 4
jitter. A pseudorandom time period for varying the start of a JITDS pulse. Gives
JTIDS additional resistance to jamming
Joint Tactical Information Distribution System (JTIDS). A joint-Service system
which provides an Integrated communications, Navigation, and Identification (ICNI)
capability. The JTIDS provides a reliable, secure, jam-resistant, high-capacity, ICNI
capability through the use of direct-sequence, spread-spectrum, frequency-hopping, and
error detection and correction techniques
JTIDS net. One of 128 time-division structures comprising a JTIDS network. Each net
consists of a continuous stream of time intervals (time slots) with 98,304 time slots per
12.8-minute epoch, during which digital data whose signal characteristics are
Glossary-10
determined by a cryptographic variable in conjunction with a unique net number are
distributed
JTIDS network. The JTIDS structure having a total usable capacity of 98,304 time
slots per epoch per net and 128 nets. All nets are synchronized so that each time slot of
each net is time-coincident with the corresponding time slot (same set and number) of
every other net. The signal characteristics of all data distributed within a specified
multinetted structure are determined by a cryptographic variable in conjunction with a
set of net numbers that define the structure
JTIDS Unit (JU). A unit communicating directly on TADIL J
JU response time. The time from new information availability at the JU to the
transmission of the information on the link. This is defined for each message in the
MIL-STD-6016
local track. A track established within an interface unit based on locally entered
positional information. Amplifying data associated with the track may be derived
locally, from supporting units, or from data links
navigation controller. The navigation controller establishes the origin and north
orientation of the U, V relative grid for the relative navigation function
net control station.
(1) a TADIL A station which, through switch selection on the Data
Terminal Set, acts as the interrogating station in the roll call mode of operation
(2) a communications station designed to control traffic and enforce
circuit discipline within a given net. Also called NCS.
(Joint Pub 1-02)
net cycle time (NCT). The time required for one TADIL A net cycle; i.e., for all PUs to
be polled at least once in the TADIL A roll call mode
net number. A seven-bit code that identifies each net as a decimal number (0 through
127).
(System Segment Specification for JTIDS Class 2 Terminal)
net sync. A TADIL A net mode of operation for synchronizing all stations that are on
the link
net. See “JTIDS Net”
network. See “JTIDS Network”
network management concepts. A set of operational concepts that deals with the
allocation and assignment of JTIDS resources and functions to satisfy user
requirements
network management function. An action or activity affecting the relationships,
actions, or activities of the various elements of the network
network management tools. The procedures employed by a network manager to
ensure effective and efficient use of the JTIDS message transmission capacity
Glossary-11
network participation group. A unique list of applicable messages used to support an
agreed-upon technical function without regard to subscriber identities; this list is a
means of transmitting a common set of messages to all interested users
network time reference. A subscriber terminal that is assigned as the reference for
system time for each synchronized netted system. The NTR terminal’s clock time is
never updated by system information and is the reference to which all other terminals
synchronize their own clocks. There is only one NTR
noncommand and control JTIDS unit (nonC2 JU). A JU without command and
control (C2) capability
participating unit (PU). A unit communicating directly on TADIL A
pool. One or more time slot blocks that can be used to satisfy a particular functional
requirement or the total JTIDS capacity that can be divided into pools to satisfy all
functional requirements
pulse (JTIDS). A 6.4-microsecond burst of carrier frequency continuous phase, shift
modulated at a 5-megabit-per-second rate by the transmission symbol
radio relaying. A function for extending radio coverage based on time delay relaying
where a message received during one time slot is subsequently retransmitted in
another time slot
reception quality (RQ). A number from 0 through 7 which represents the quality of
data reception from a particular IU by a particular IU.
0 represents no reception and 7
represents perfect reception
relative navigation. A procedure used by a terminal to determine its position and
velocity in a common reference coordinate system by passive observations of position
and status messages transmitted by other terminals
relay. An automatic function of the JTIDS terminal that provides retransmission of
received information to extend the range beyond line of sight
relay block. One to 64 time slot blocks assigned to independently specified nets for the
relay of messages. The number of time slots selected for message reception must equal
the number of time slots selected for message transmission. Each block is described by
set (A, B, or C), a specific time slot in the block, and the recurrence rate
remote data. Data that are derived from data link reports from another unit
remote track. A track established within an interface unit based upon positional
information derived from a data link report or reports. Amplifying data associated with
the track may be derived locally, from supporting units, or from data links
reporting responsibility. The requirement for the IU with the best positional data on
a track to transmit track data on the interface
Glossary-12
reporting unit (RU). A unit communicating directly on TADIL B
round-trip-timing (RTT). The process used by a JTIDS terminal to directly determine
the offset between its clock and that of another JTIDS terminal. This is used to achieve
and maintain fine synchronization and to improve the terminal’s time quality. This
process involves the exchange of RTT interrogation and reply messages
RTT message. A short, 35-bit message used by the Active synchronization method,
either an RTT Interrogation message or RTT Reply message
secondary user. The general category for the majority of JTIDS subscriber terminals.
Secondary user terminals generally utilize the Passive synchronization procedures for
synchronizing in the Relative Navigation community.
(System Segment Specification for
JTIDS Class 2 Terminal) Secondary users may use RTT messages when improved time
quality is needed to maintain position quality
stacked net. The coordinated use of specific blocks of time slots on different nets in a
JTIDS network by different communities of users
static network management. Management of the TADIL J network in accordance
with a preplanned scheme not subject to changes by a network manager during
operations
subscriber. A participant in the use of the system, either actively (transmission of
information) or passively (receiver of information only), or both
supporting unit (SU). A unit operating in support of a JU, a PU, or an RU which is
providing data for the interface but which is not specifically identified as a data source
tactical data system (TDS). An automated real-time computer system in which
tactical data are entered for storage, calculation, and/or display
tactical digital information link. A Joint Staff approved, standardized
communications link suitable for transmission of digital information. Current practice
is to characterize a tactical digital information link (TADIL) by its standardized
message formats and transmission characteristics. TADILs interface two or more
command and control or weapon systems via a single or multiple network architecture
and multiple communication media for exchange of tactical information
a. TADIL A a secure, half-duplex, netted digital data link utilizing
parallel transmission frame characteristics and standard message formats at either
1364 or 2250 bits per second. It is normally operated in a roll-call mode under control of
a net control station to exchange digital information among airborne, land-based, and
shipboard systems. NATO’s equivalent is Link 11
b. TADIL B a secure, full-duplex, point-to-point digital data link
utilizing serial transmission frame characteristics and standard message formats at
either 2400, 1200, or of 600 bits per second. It interconnects tactical air defense and air
control units. NATO’s equivalent is Link 11B
Glossary-13
c. TADIL C a unsecure, time-division digital data link utilizing serial
transmission characteristics and standard message formats at 5,000 bits per second
from a controlling unit to controlled aircraft. Information exchange can be one-way
(controlling unit to controlled aircraft) or two-way. NATO’s equivalent is Link 4
d. TADIL J a secure, high capacity, jam-resistant, nodeless data link
which uses the Joint Tactical Information Distribution System (JTIDS) transmission
characteristics and the protocols, conventions, and fixed-length message formats
defined by the MIL-STD-6016. NATO’s equivalent is Link 16
e. Army Tactical Data Link 1 (ATDL-1) a secure full-duplex, point-to-
point digital data link utilizing serial transmission frame characteristics and standard
message formats at a basic speed of 1200 bits per second. It interconnects tactical air
control systems and Army or Marine surface-to-air missile systems
f. Interim JTIDS Message Specification (IJMS) a secure high capacity,
jam-resistant, nodeless interim message specification that uses the MIL-STD-6016
transmission characteristics and the protocols, conventions, and fixed-length message
formats defined by the IJMS. See also Data Link.
(Joint Pub 1-02) The transmission
characteristics and standards for the TADILs are set forth in the following documents:
TADIL-A = MIL-STD-6011 and MIL-STD-188-203-1A.
TADIL-B = MIL-STD-6011 and MIL-STD-188-212.
TADIL-C = MIL-STD-6004 and MIL-STD-188-203-3.
TADIL-J = MIL-STD-6016.
ATDL-1 = MIL-STD 6013
NATO Link 1 = STANAG 5501
TADIL J message. A functionally oriented, variable-length string of one or more 70-bit
words in either fixed word format or variable message format
terminal (JTIDS). The integrated equipment comprised of hardware, firmware, and
software elements used as the means for participating as a system subscriber
test mode. A mode of terminal operation whereby a terminal is required to transmit
Test messages
time (system). The time maintained by the terminal assigned as the Network Time
Reference (NTR) to which all other participating terminals are synchronized.
(System
Segment Specification for JTIDS Class 2 Terminal)
time (terminal). The estimate of time derived by a terminal as a result of executing
either the active or a passive synchronization procedure
time slot. A 7.8125-millisecond time interval during which messages may be
transmitted
time slot assignment. The designation to the JTIDS terminal of the specific time slot
blocks in which it will transmit or receive messages
Glossary-14
time slot number. A 17-bit code that identifies each full time slot, the code consisting
of a 2-bit set field (set A, B, or C) and a 815-bit slot field representing the decimal
numbers zero to 32,767
time slot reallocation. A transmit access mode in which each Access Mode participant
periodically assigns itself time slots from a shared pool of time slots. A participant
assigns transmit time slots after transmitting a Time Slot Reallocation (TSR) message
and receiving TSR message and receiving TSR messages from other participants
time slot block. A collection of time slots spaced uniformly in time over each epoch and
belonging to a single time slot set. A block is defined by indexing time slot number (0 to
32,767), set (A, B, or C), and a recurrence rate number (0 to 15)
time slot reuse. A method to increase the JTIDS network capacity by allowing more
than one terminal to transmit in a single time slot on a single net number. This is
appropriate for JUST in proximity to each other that have information to exchange;
receivers will lock onto the message with the shortest time of arrival
track.
(1) the graphic and/or alphanumeric representation of an object, point, or
bearing whose position and/or characteristics are collated from sensors and/or other
data sources
(2) a collated set of data associated with a track number for the purpose of
representing the position and/or characteristics of a specific object, point, or bearing
track number (TN). The unique numeric or alphanumeric octal identifier associated
with a specific set of track data representing a vehicular object, point, line of bearing,
fix, or area of probability
track quality (TQ). A numerical value assigned to a track computed from data related
to the past tracking performance on the track, representing the accuracy of the track
position
transmit block. A time slot block assigned for the transmission of messages
variable message format. A message structure using predefined fields of fixed length
employing internal syntax and a header extension. The internal syntax specifies the
presence, absence, and recurrence of fields as selected by the user
Glossary-15
|