Introduction To Tactical Data Links

7/22/2019 Introduction To Tactical Data Links

1/99

2012 IBM Corporation

Introduction to Tactical Data Links


2/99

2012 IBM CorporationINTERNAL IBM USE ONLY

Course Objectives

Provide Pre-delivery instruction to training development, POC,

engineering and information development teams, in:

Link-11 theory and operations

HCM-specific data link operations

Link-11 to Link-16/Link-22 translationsLink-11 test and debugging techniques

Configuring and starting data link operations

Training and Simulation of data link


3/99


Introduction to Tactical Data Links

V1 January 2012


4/99


Course Objectives

An introduction to Tactical Data LinksFor those who have little or no previous exposureIntended to bring team members from unaware to basic

understanding of the purpose, personnel, development,

testing, delivery and operational impacts of tactical datalinks

Briefly covers the history of Canadian and Allied data linksystems

Provides a glimpse of Canadian Data Link systems

Applicable to Airborne, Maritime and Ground Environments


5/99


Segment Outline

Reasons for TDLs

History of TDLs

Platforms using Links

Different types of Links

Link-1 Link-4 Link-14 Link-11/11B Link-16

Future Links Link-22 Link-21

Others ATDL TACFIRE Link-10 VMF

Link operations

TDL Development

TDL Integration

TDL Migration strategies

Interoperability assurance

Testing

Training

Future Projects

Link Vendors

Message Standards Roles STANAGs

ADatP MIL-STDs

International Cooperation DLWG NILE MIDS

Int. Data Link Society


6/99


Instructor

Jeffrey Jobb

Military Data Links experience

Link-11

Link-16

Link-22 Standards Development NATO Data Link Working Group(s) 1987-1996

Data Link Systems experience

ADLIPS, Halifax-CCS, Iroquois-CCS, AOR-TDLS, RSAOC, Aurora, & MHP

IBMs DLPS for Halifax Class Modernization (since Apr 2011)

Message definition, requirements analysis, design, code, test and interoperability

analysis


7/99 2012 IBM CorporationINTERNAL IBM USE ONLY

Sources

Data Link Standard Operating Procedures (SOPs) ADatP-11, ADatP-16, ADatP-22, ADatP-33

Data Link Message Standards STANAG 5511, STANAG 5516, STANAG 5522

STANAG 5616, STANAG 5601, STANAG 5602 Canadian Forces Document

CFCD 111

US Documents CJCSM-6120.01C - Joint Multi-TADIL SOP USMC Ref Pub 3-25C - Intro to TADIL & Quick Reference MIL-STD 6011, MIL-STD 6016

Vendor Documents LMS-11PC User Guide (NG-MS) MDM-2002 DTS User Manual (Rockwell-Collins) Understanding Link-11 (NG-MS)



Terms & Definitions

Tactical

particular to the local operations of a force, and specifically with

regard to the employment of weapons - AAP-6

Data Linkthe layer of network operations most concerned with bit-oriented data,

packet manipulation, error checking and marshalling ISO/IEC-7498-

1:1994 OSI Network Model

Interoperability

the ability of Allied forces to employ services and work together toachieve the mission - AAP-6



The Reason for Tactical Data Links

NATO mandate - ADatP-31

To achieve the highest level of information exchange possible using

standard radio and telecommunications services, to provide for

command and control of forces, dissemination of the common

operational picture and resolution of information differences, withoutloss of meaning or impact.

Recent experience OP TELLIC

the main factor in our success was that we were able to function as

one team, in one fight, with one data link network.

Air Vice Marshall Dalton RAF speaking at IDLS 2003



Brief History of Tactical Data Links

Before TDLs (1920-1949)Still using Visual Signalling

Morse Code CW

New UHF Voice radios

RATT (1938-present)

Originally perforated tape

Morse printers

Became 5-bit Baudot code



Before Data Link - Manual Plotting

Local radar and voice reports plotted in

grease pencil

Based on Voice radio reporting procedures

Required strict radio discipline

Cannot exchange the picture

Operators had to write backwards


12/99


Before the data links


13/99


What does the data link do? Automation of Information Exchange


14/99


Basic Tactical Data Exchange

Who (is the contact) (Friend, Foe, Unknown)

What (is it) (Air, Surface, Sub, Land)

Where (is it)

When (was it detected)

Whither (is it going)

Why .

Isnt someone attacking it?


15/99


Technology limited

Pre-1970 Combat Operations were Pre-planned and Units Operated

Autonomously

Cooperative Tactics Limited

Available Data Limited and Often Outdated Data Obtained By:

Text message reports

Voice (Radio) Communications

Visual Observations

Voice Communications Subject to Misinterpretation

Inter-service and International Operations Limited and Lacked Coordination


16/99


First Automatic Data Link

NTDS WD Link - 1961

U.S.S. Enterprise

UNIVAC computerWeight 308 lbs

Translated radar plot data intoteletype link

Became NATO Link in 1967Link-14

Fitted in RCN Tribal Class

1970

CCS-280Required manual plotting when

received


17/99


Computer Technology Assisted

1970s brought Computer control ofmodem and radiosFirst NATO Standard protocolsBased on same procedures as

voice and teletype exchange

Automatic plotting of local radar andlink track positions

Campfire DisplaysADLIPS-STACOs shown in

service in Portuguese Navy


18/99


Computer Assisted Data Link Plotting

Canadian-built CCS-280 system one

of NATOs first fully capable link

systems

Link-14 transmit

Link-11 transmit & receiveAutomatic Data Link Plotting System

(ADLIPS) 1978

Halifax CCS 330 1989 ->


19/99


Modern Tactical Data Links

TDL used to refer to most Bit-Oriented Radio Links integrated with

Weapons control or Command systems

In Canada, as in NATO, referred to by NATO Designator example Link-

14 In US, until recently, referred to as TADILs (Tactical Digital Information

Link) plus message designator

example TADIL-A = Link-11, TADIL-B = 11B


20/99


What are TDLs?

A TDL is an automated, interoperable information exchange method used

by allied units to provide data of tactical import for use in situation

appreciation and Command and Control.

A TDL system is comprised of computer hardware, software, media(radio), controllers, encryption devices, message standards, standard

operating procedures, sensors and operators.


21/99


What Makes a system Interoperable?

Proced

ures

Standardization

Training

Softw

are

INTEROPERABILITY


22/99


Choosing the Right TDL

Platform Type

Concept of Operations (CONOPS)

Determines what warfare areas the

system will participate in

Information Exchange requirements

Determines what data links and

messages the system will use


23/99


Different Types of Links

Some Links are Real-Time...

no appreciable delay between sensor report and TDL update

Some Links are Non-Real-Time

where the time-of-report and time-of-observation are required forappreciation of the quality of the information - commonly teletype data

links


24/99


NATOs In-Service Links

NRT Links

Link-1

Link-14 (End 2010)

Phasing OutLink-10 (End 2002?)

RT Links

Link-11/11B

Link-16

Link-22 (IOC 2011)

Phasing Out

IJMS (End 2005)

Link-4A/4C

Others

ATDL-1HAWK


25/99


Link-1

Link 1 is a duplex digital data link primarily used by NATOs Air Defence GroundEnvironment (NADGE). It was designed in the late 60s to cater for point-to-point datacommunication by wire.

exchange of air surveillance data between Sector Operation Centres (SOCs) and has a datarates of 600, 1200, 2400 bit per second (bps). It is not crypto secure and has a message set(S-series) limited to air surveillance and link management data.

Documents are STANAG 5501 & ADatP 31.

Recently been provided to NATO PfP Nations in Mobile CRCs (USAF).

Message Data

S-Series messages 128 bit packet 98 bits of Data

Uses Fixed and Unique Site Addresses

Example Site #31 = ALBORG, Denmark


26/99


Link-4 (Phasing-out)

Link 4 is a non-secure data link used for providing vector commands to fighters. It is a netted, time divisionlink operating in the UHF band at 5,000 bits per second. There are two separate "Link 4s": Link 4A andLink 4C. Link4A is not encrypted. Fitted in F-14, F-16, F-18 and aircraft control units.

Link 4A is the controller to aircraft data link. Link 4C is a fighter-to-fighter data link which complementsLink 4A although the two links do not communicate directly with each other.

It is planned that Link 16 will assume Link 4A's role in AIC and ATC operations and Link 4C's role infighter-to-fighter operations. However Link 16 is not currently capable of replacing Link 4A's ACLSfunction and it is likely that Naval aircraft will remain equipped with Link 4A to perform carrier landings.


Message Data

V & R Series messages 36 bits of Data

Addresses assigned at Mission Load 3 Number Octal

MIL-STD-6004 & MIL-STD-188-203-3


27/99


Link-14

Link 14 is a broadcast teletype link for maritime units to transfer surveillance informationfrom ships with a computer data processing capability to non-tactical data processing ships.

provides the capability to broadcast picture compilation and status information for use inunits unable to receive Link-11 transmissions either direct or via an interface, e.g. non-Tactical Data System (TDS) units. The Link can be either HF, VHF or UHF dependent onunit-communication fits. There are some auto-plot systems capable of receiving andcharting the contacts.

Each nation within NATO has its own Link 14 transmission formats which are promulgated inADatP-14. Message protocol is defined in STANAG 5514

Message Data Character-based sequences 4-40 characters

No addressing Broadcast data

Source ID is IMO Call-Sign Example HALIFAX is CGFN


28/99


Link-11

Link-11 is based on 1960s technology and is a relatively slow link which normally operates on apolling system with a Net Control Station polling each participant in turn for their data. In addition tothis "Roll Call" mode, Link-11 may be operated in broadcast modes in which a single datatransmission or a series of single transmissions is made by one participant. Link-11 is, therefore, a fullduplex link operated in half-duplex mode. Link-11 is secure but not ECM-resistant.

Link-11 is designed for HF (300 NM) or UHF radios (25NM), satellite media or land-line (Link-11B -

fibre-optic has been tested).

Link-11 supports the exchange of air, surface and subsurface tracks, EW data and limited commanddata among C2 units.

Within NATO Link-11 is primarily used as a Maritime Data Link. However, Link-11 will be adapted tocater for Theatre Missile Defence information exchange requirements, consequently Ground BasedSAM Systems are or will be equipped with Link-11 (or Link-11B).

Messages M-Series 48 bits of Data

Addresses assigned at Mission Load 3 digit octal numbers


29/99


Link-11B

Link-11B uses a dedicated, point-to-point, full-duplex digital data link using serialtransmission frame characteristics. Data is exchanged over a fully automatic, phase-continuous, full-duplex, frequency-shift-modulated data link operating at a standard rate of1200 bps with optional capabilities of 600 and 2400 bps.

Within NATO Link-11B is used to integrate Ground Based SAM C&C and Fire ControlCentres into the Air Defence Ground Environment using CRC SAM Interfaces (CSI). Within

the US, and some other NATO Nations (e.g. France), Link-11B is used as the primary datalink for ground based TACS (e.g. USAF MCE, and USMC TAOC).

Message standards for both Link-11 and Link-11B are defined in STANAG 5511 whilestandard operating procedures are laid down in ADatP 11.

Messages and Addressing as per Link-11 (with differences)

MIL-STD-6011 & MIL-STD-188-203-1A (MIL-STD-188-202 for L11B)


30/99


IJMS (Phasing out)

Interim JTIDS Message Specification - came into existence because the hardwarefor JTIDS was available before the TADIL-J message standard (on which Link 16is based). Provides an initial JTIDS operating capability for the USAF and wasimplemented in the NATO E-3A, UK E-3D and French E-3F.

It is based on Link-11 messages packaged to fit into the JTIDS architecture. Samefunctionality as Link-11 but with a greater capacity and ECM-resistance.

IJMS is implemented in the UK ground environment for commonality with NATOE-3As, and the UK E-3D, while within NATO only limited IJMS capabilities havebeen implemented in NADGE CRCs. Some US fighters have a dual IJMS/Link16capability.


31/99


Link-16

JTIDS and MIDS supports three message standards: Link 16, IJMS and Variable MessageFormat (VMF). MIDS/JTIDS uses a Time Division Multiple Access (TDMA) architecture onUHF radios or Satellite.

Link 16 optimizes the use of the MIDS/JTIDS architecture. Link 16 has been developed tomeet the information exchange requirements of all tactical units, supporting the exchange of

surveillance data, EW data, mission tasking, weapons assignments and control data.TheLink 16 message standard uses J-series messages and completely meets the requirementsfor C2 functionality and aircraft control.

Numerous platforms have been or will be equipped with Link 16 (Airborne Surveillance andIntelligence Systems, C2 Systems, Fighter and Bomber Aircraft, SAM Systems, Ships, etc).


Messages J Series Variable Length using 75-bit packets

Dynamic Addressing and relay capability 2 Alphanumeric, 3 octal AA001

MIL-STD-6016


32/99


NATOs Developing Links

Link-21 (also Link in Support of ACCS, or LISA) 2005+

landline, packet switched variant of Link-16 data elements, inter-site

message stream

Link-22 (also NATO Improved Link Eleven or NILE) 2010+Fixed-length variant of Link-16 data elements, adds HF wave-form for

over horizon link

JRE (JTIDS Range Extension) 2004+

Satellite and alternate transfer of Link-16 data

MIL-STD-3011 protocol


33/99


TDL Comparisons

Feature Link-11 Link-22 Link-16

Data Functions Surveillance,

Position, EW,

MM/WC

Surveillance, PPLI,

EW, MM/WC

Surveillance, PPLI,

EW, MM/WC, Air

Control

Voice Functions No No 2 Secure Voice126 Nets/Voice

Spectrum HF/UHF HF/UHF UHF(Lx-Band)

System Throughput 1.8 Kbits/Sec 2.2 Kbps HF, 12.8

UHF

54.0 Kbits/Sec

Access Protocol NCS Polling DTDMA TDMA

Jam Resistance No Yes Yes

Secure Yes Yes Yes

Beyond-Line-of-Sight Yes (HF) Yes Yes (Relay)

Messages M-Series F, FJ-Series J-Series


34/99


Other TDLs in use (1)

Army Tactical Data Link-1 (ATDL-1)

Exchange of air and surface tracks in real time

Fire Control orders

B-series, 56-bit messages on multi-channel radio or land-line

PATRIOT Digital Information Link - PADIL

Missile Battery Data Link - MBDL

HAWK Missile Battery Links

Ground-Link, Inter-Battery Link


35/99


Other TDLs in use (2)

TACFIRE

Army Air defense Artillery link

Character-based fire mission

messages

Being phased out in 2008 by VMFmessage standard

VMF

Link-16 data elements in text or bit-

stream format

MIL-STD-6040

Link-10 (NATO Phase out)Link-14-like message set in a

two-way radio communicationssystem

Implemented by Netherlands,Belgium and Greece in 1970sReplacing with Link-11 (Finally)


36/99


Sensor Data Links

Typically single or multi-sensor package data links, used for UAVs (Video, Infra-red)

Requires multi-channel radios for uplink (sensor control) and downlink (data)

Common Data Link (CDL)

US standard since 1991, secure 10.7 MBps downlink

Tactical Common Data Link (TCDL)Developed for Manned and UAVs - 1995 radar, imagery, video and other sensor information at rates from

1.544Mbps to at least 10.7 Mbps over ranges of 200km

High Integrity Data Link (HIDL)UK development for air and surface terminals to handle 100Kbps in

jamming environments - 1999


37/99


Data Link Operations

Basic theory of operations

System Architectures

Component examples

Messages and structure

Warfare areas supported


38/99


Basic Tactical Data Exchange

Automate the Sensor data exchange with Friendly forces

Who, What, When, Where, Whither, Why

Extend the range of Situational Awareness by putting symbols on other units

displays

Send status information on Own Unit Sensors and Weapons

Coordinate Engagements

0373 R

7701

BAD GUY

17:14:15Z

ENGAGE 2

FIRING


39/99


Link-11 Theory, Architecture and

Components

MHP Data Link Operations Course

Day 1


40/99


Link-11 Network Operation

Net Control Station

polls PU sequence (Roll Call

mode)

as per OPTASK msg

Participating Units respond to poll

Other Modes

Broadcast, Short Broadcast

Radio Silent

Sync, Test

Single Hierarchy

all inclusive net

some addressed msgs (Commands)

not Jam resistant


41/99


Link-11 Network (1)

Net Control Station

(NCS) polls 1st

Participating Unit

(PU)

PU transmits Own

Location


42/99


Link-11 Network (2)

PU transmits track

reports and supporting

information

NCS polls next unit in

sequence


43/99


Link-11 Network (3)

NCS transmits its

data and restarts the

sequence


44/99


Link-11 System Architecture

Includes Host Tactical Data system (TDS) or Data Link Processor (DLP), Crypto

device, Data Terminal Set (DTS)

several commercial vendors of DTS

Some systems integrate DLP into Host TDS


45/99


Link-11 Components

Host TDS

Embedded DLP (Aurora) with ATDS interface card Integrated into TDS CCS-330 Halifax class CCS

New Halifax Class Modernization (HCM) project CCS (SAAB 9LV)

Data Link processor

Airborne DLP Rockwell-Collins

MLP Ultra

IBM Multi-Link DLPS

Encryption Device

KG-40A Aurora, HCM

KG-40AR

Multi-Link Encryptor (MLE) - MHP

Data Terminal Set (DTS)

Rockwell Collins MDM-2202 Airborne Tactical Data Systems (ATDS) interface

DRS MX-512PV - HCM

Link-11 Radio


46/99


Link-11 Host TDS

AOR CTDLS

COTS Item delivered for Gulf War

Combines Radar and Data Link

processing in one console

Host and DLP combined

Small-scale system

Halifax Class CCS-330

Host TDS built entirely around Link-11

tactical data

TDS with integrated data link

processing

Distributed database, multiple operator

action

One UYK-507 processor dedicated to

Link-11 configuration, operations,diagnostics and monitoring

Reconfigurable to load software into a

standby processor

Shedding load of ARP


47/99


Modernized Halifax Class CCS

New Multi-Function CCS Consoles

SAAB ACCS-9LV CCS System

New Radars, IFF and Fire Control systems

Harpoon Missiles Upgrade

ESM System Upgrade

Internal Communications system replaced

New Multi-Link Data Link Processor

(IBM)

Infra-Red Search and Track system Extended Sea Sparrow Missiles Upgrade


48/99


Tactical Data System functions in TDL

Navigation data

Sensor data

Link Network operational parameters

DLRPPU Numbers

Track Block

Filters

Display of tactical data

Correlation of local sensor data

Track release


49/99


Link-11 Data Link Processor

DLP Functions Encode and Decode of Link-11

messages

Support TDS tactical functions

such as correlation, Identity conflict

detection and resolution, Gridlock

Link network monitoring Terminal interfaces, some include

terminal control

Airborne DLPs

ADLP-100 Rockwell-Collins

MLP Ultra Ship DLPs

C2P Northrop-Grumman

DLPS - IBM

DLIP - Thales


50/99


DLP Functions in TDL

Correlation parameters per STANAG

Gridlock reference unit

Gridlock mode

Released tactical data

Applies Local/Remote Correlation

Applies Filters

Applies Conflict rules


51/99


Link-11 Encryption Device

Encryption Device KG-40A and Remote Control Aurora

NTDS Parallel interface

ATDS Serial interface

KG-40AR Replacement

US Navy purchase Ultra

Fit, form ,functional replacement for

NTDS devices

MLE Ultra

Initial offering for MHP ATDS

MLEp with RS-422 interface

Candidate for TDE 3-box solution

Crypto Operator Entries

Keylist

Mode

Fill

Erase

Indicators


52/99


Link-11 Data Terminal Set (the modem)

DTS Functions

Tactical data systems interface control Link protocol control Signal modulation/demodulation Generation of Link-11 protocol control

codes Error detection and correction Doppler/RF Error Detection

Audio interface to radios Keylinecontrol

Airborne DTS MDM-2202 Rockwell-Collins (Aurora) MDM-2202N Rockwell-Collins (MHP) MDM-2402 Rockwell-Collins

Ship DTS MDM-2002 Rockwell-Collins MX-512PV or USQ-125 DRS (Halifax

class)


53/99


DTS Entries

Net Mode

Roll-call, Broadcast, Short Broadcast, Net Sync, Net Test

Radio Silent

Station Mode

NCS, Picket

Sideband Select

Auto, LSB, USB, Diversity

Data Rate

Fast, Slow

Doppler Correction

On, Off

Other Settings


54/99


Link-11 Radios

HF 2 to 30 MHz

UHF 225 to 400 MHz

UHF ARC-210 Multi-mode

Meet Link-11 Requirements Switches quickly between Tranmsit

and Receive

Audio bandpass is wider than

voice bandpass

Transmitter keying required before

data arrives at radio Fast AGC attack and release times

Internal frequency standard

Multi-tone or single-tone capable

Restricted phase jitter and

envelope delay tolerances


55/99


Link-11 Data Exchange

MHP Data Link Operations Course

Day 1


56/99


M-Series Messages

48 bits of data in 2-24 bit Frames Plus 6 EDAC Bits per Frame

sequences required to build data objects

T/R Acknowledgement and compliance rules

Message #, M.8, frame switches add overhead

stringent Illegal value processing

23 22 21 20 19 18 17 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

TRACK

QUALITY

S

I

PRI

AMPID TRACK NUMBER MESSAGE #

47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24

Y COORDINATE X COORDINATE


57/99


Link-11 Identity Matrix (Air)

Unknown (0) Friend (1) Hostile (2) Friend (3)

Pending General No Statement Special Mission

Unknown Helo - Strike / Support / Bomber

Assumed Friend - - Interceptor / Fighter

Suspect - - -


58/99


Link-11 Mission Areas Supported

Participating Unit location & ID

Surveillance

Air, Surface Subsurface, ESM

Points (No Lines, a few Areas)

ESM Parametric and Coordination

Mission status

Aircraft Handover

Command and Control

National Messages

Text Message


59/99


Link-11 Messages (1)

M.0 Test Message (NT/DM)

M.1 Data Reference Position Message

M.81 Data Reference Position Amplify Message

M.2 Air Track Position Message

M.82 Air Position Amplify Message

M.3 Surface Track Position Message

M.83 Surface Position Amplify Message

M.4A ASW Primary Message

M.84A ASW Amplify Message

M.4B ASW Secondary Message

M.4C ASW Primary Acoustic Message

M.84C ASW Primary Acoustic Amplify Message

M.4D ASW Bearing Message

M.84D ASW Bearing Amplify Message

M.5 Special Points Position Message

M.85 Special Points Amplify Message


60/99



M.6A ECM Intercept Data Message

M.6B Electronic Support Measures PrimaryMessage

M.86B Electronic Support Measures Amplify Message

M.6C Electronic Support Measures Parametric

Message

M.86C Electronic Support Measures Parametric AmpMessage

M.6D Electronic Warfare Coordination and Control Msg

M.86D Electronic Warfare Coordination and ControlAmplify

M.9A Management Message (Information)

M.9B Management Msg (Pairing/ Association/ Correlation)

M.9C Management Message (Pointer)

M.9D Management Message (Link 11 Monitor)

M.9E Management Message (Supporting Information) M.9F (AC=0) Area of Probability Basic Message

M.89F(AC=0) Area of Probability Basic Amp Msg

M.9F (AC=1) Area of Probability Secondary Message

M.9G Data Link Reference Point Position Message


61/99



M.10A Aircraft Control Message

M.11B Aircraft Mission Status Message

M.11C ASW Aircraft Status Message

M.11D IFF/SIF Message

M.11M EW/Intelligence Message

M.811M EW/Intelligence Amplify Message

M.12 National Message

M.12.2 US Navy National Message

M.12.2.3 NATO Text Message

M.12.28 Canadian National Message

M.12.31 Timing Message

M.13 Worldwide National Message

M.14 Weapon/Engagement Status Message

M.15 Command Message


62/99


Link-16


63/99


Link-16 Development

Link-16 development started in mid-1980s with message standard and

Joint Tactical Information Distribution System (JTIDS) Class I terminals

JTIDS and later Multi-Function Information Distribution System (MIDS)

terminals combine network control, encryption and radio functions into

one device

Additional features added to JTIDS Class II and MIDS functions include

digital Link-16 voice, TACAN and IFF blanking features.

Terminals are initialized from pre-sets defined by Network planning

systems

Link-16 operational features include TDMA, so no Net Control station, jam

resistant, frequency hopping, relative navigation, secure voice and

increased data capacity over legacy data links


64/99


Link-16 Network Operation

UHF, Frequency Hopping Time Division Multiple Access (TDMA)

Automatic Relay, Voice Capability

TACAN, System Encryption


65/99


TDMA Architecture


66/99


Link-16 Relay

Usually based on Net Participation

Groups (NPG)

May be divided by area

Configured at mission load or

dynamically Lengthens time slot assignments

for relay units

Assigned by Frequency within time

slots


67/99


Link-16 Net Participation Groups

NPGs are stacked by time-slot allocations

May include Frequency hops

Usually assigned at Mission load

Air Control Fighter

Air Control Strike Fighter Back-link

Ground Air Defence

Surveillance NPG is used by all


68/99


Link-16 System Architecture

In most cases L16 requires a newData Link Processor (DLP) insertedbetween the Host CCS and the JTIDSand L11 terminals.

Called a C2P in the US

requires a system upgrade to interfaceto C2P

most C2Ps, DLPs do data forwarding


69/99


JTIDS Terminal Interfaces

JTIDS Class II Terminal

3 variants Shipboard (rack-mount) Airborne High-power Airborne

Host (or C2P) interface 1553B for data and control

Discrete interfaces Blanking, TACAN, IFF, SAHRS,

Timing

2 Voice channels


70/99


JTIDS Class 2 Terminal

JTIDS Class 2 Terminal

200 Watts RF Output

Up to 238 KBS Data Throughput

Dual Antenna Ports with

Dynamic Switching

2 Channels Digital Voice

(2.4 and/or 16 KBS)

Geodetic and Relative

Navigation

Integral TACAN

Current Applications

F-15

F-14

Tornado (UK)

JSTARS

Rivet Joint

MCE

USN Submarines


71/99


JTIDS Class 2M (Ground Terminal)

Single Unit with Integral Receiver Transmitter Data Processing X.25 Interface Cooling System

Same Performance as basic Class 2except: No Voice No TACAN

Current Applications FAAD THAAD Patriot


72/99


MIDS LVT 1

MIDS Low Volume Terminal

Smaller, Less Costly

200 watts

Up to 238 Kbps of data

Dual Antennae ports

2 channel Digital voice2.4 and/or 16 Kbps

Geodetic and Relative navigation

70 pound weight saving


73/99


MIDS-on-Ship

Shipboard variant of MIDS terminal

MIDS-LVT housed in 2nd lowest

drawer

Power supply and conditioner

Interface unit

Control panel and indicators

Crypto and parameter fill ports

High-power RF amplifier and TACAN

interface units - optional


74/99


MIDS-JTRS

Joint Tactical Radio System (JTRS)

variant of MIDS-LVT

Removes and replaces legacy MIDS

cards, and uses spare card-slots

Retains existing MIDS capability

Adds two Software-Defined Radio

modules

Programmable UHF channels

Enhances Link-16 digital voice

channels

More robust power supply


75/99


Other Link-16 Terminals

MIDS LVT 2 Fighter Data Link

50 watt terminal, Voice not integrated but capable

SHAR Terminal UK Sea King Whiskey AEW, RAF Tornado

200 watt RF output, Voice, but no TACAN

Fitting in UK ASTOR, NIMROD, Tanker, Tornado, Harriers


76/99


Link-16 Messages

300-fold increase in information over Link-11System Information Exchange and Network ManagementPrecise Participant Location and Identification (PPLI)Surveillance

Air, Surface (Maritime), Land, Space, Electronic Surveillance

Points, Lines and Areas, including Multi-segment shapesElectronic Warfare IntelligenceMission ManagementWeapons Coordination and ManagementCommand & Control Information Management

Precision Aircraft Control and Weapon guidancePlatform and Airfield status


77/99


J-Series Messages

75 bit Words (70 Data Bits, 5 EDAC)

Extension Words provide additional amplifying data

Continuation Words provide optional data

Stringent error checking

Single message to establish track with attributes

24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

SIM

I

SP

I

EMG

I

FT

IPP

Ex

I

MSG

Length

Sub-

LabelLabel - J

Word

FMT49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25

Alt

SRCStrength Track Number

74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50

SI

IIdentity

ID

Confidence

Track

QualityID

DI Altitude


78/99


J-Messages More Information

Can Report:

Platform Type

Values 0 62

Platform Activity; or

Values 0 126Specific Type

Values 0 4095

Air UNK Civil Air

Or

Air UNK 767

Also Nationality

Identity Amplifier

Pending

Unknown

Assumed Friend

Friend Faker, Joker

Neutral

Suspect

Hostile


79/99


Link-16 Message Packing

ORDNANCE MISSIONFUELHEADINGLONGID SPEEDLAT ALT

IDHEADINGLONSOURCE SPEEDLAT ALTTRACKING

NO.

3 4 5 61SLOTS


80/99


J-Series messages

Used in JTIDS and MIDS

Variable length messages

Add words to send all available info

about a track (IFF, intelligence)

Latitude/Longitude instead of

Coordinate references

Example - J3.2 Air Track message

can include:

J3.2 Initial

J3.2 Extension

J3.2 Continuation

Data Precision and completeness

more than 10 Link-11 messages

and amplifying messages

P ki d D R


81/99


Packing and Data Rates

Effective tactical data rates of Link-16 are 26,880, or 53,760, or 107,520bits per second, depending on the data packing structure used.

Either 3, 6, or 12 words can be transmitted in a time slot, depending onwhether the Standard, Packed-2, or Packed-4 data packing (timing)

structure is used. Dense packing impacts data rate, throughput and time-slots available for

relays.


82/99


Link-22

Li k 22 I l t ti


83/99


Link-22 Implementation

Link-22 is also known as NATO Improved Link Eleven (NILE)

Development started in late 1980s as improvements to Link-11

Created as a replacement for Link-11 using Link-16s J-series message data, infixed format messages needed for HF radio networks

As in Link-16, the NILE system will require a new DLP or C2P interfacing with theNILE equipment and software

USN intends to implement as a sub-set of their Link-16 system interface with aC2P upgrade

NATO IOC date is 2010

MHP and Aurora are designated Royal Canadian Air Force Link-22 growthplatforms

Royal Canadian Navy is implementing Link-22 with the Halifax ClassModernization program, with IBMs DLPS

Li k 22 O ti


84/99


Link-22 Operation

Dynamic Time-Division Multiple Access (DTDMA)

Up to 4 NILE Networks per Super-Network

Mission Area Sub-Networks can cross Network boundaries

Offers automated Relay and connection management features

NILE program delivering Software only, uses existing standard maritime radios

Li k 22 A hit t


85/99


Link-22 Architecture

Li k 22 E i t (NCE)


86/99


Link-22 Equipment (NCE)

NILE Communications Equipment

Could be a Data Link

Processor (DLP) such as the

Link-11 MLEmp ->

Upgraded with new DTS/SPCHost the SNC Software

Host the DLP Software

Interface to LLC and Time of

Day (TOD)

IBMs DLPS & Link 22


87/99


IBMs DLPS & Link-22

IBMs DLPS hosts the SNC Software

Interfaces to the crypto system (LLC)

DLPS performs Link-22 message

exchange and Data Forwarding to

other Links

IBM has been involved in Link-22

studies and development since 1996

Link 22 Messages


88/99


Link-22 Messages

Like the Link-16 MessagesUsing J-Series Data elementsPacked into 72-bit Data WordsEight Words per Transmit Service Request (TSR) via the

SNCPacket EncryptedService Delivery Request

Normal Reliability High

Guaranteed Delivery


89/99


MULTI-LINK Operations

MULTI Link Operations


90/99


MULTI-Link Operations

Forwarder - Multi-link system capable of automatic re-transmission of data from

one link to another.

Concurrent Operator - Multi-link system capable of concurrently operating on both

links, using local data.

Link 11/11B to/from Link 16


91/99


Link-11/11B to/from Link-16

Forwarding Participating Unit (FPU) interfaces data from Link-11 to Link-11B units

Forwarding Reporting Unit (FRU) interfaces data from Link-11B units to others ina Daisy-chain.

Forwarding JTIDS Unit (FJU) interfaces data from Link-16 to Link-11 units

Typically used in Ground Air-Defence and Strike (Forward OBS) systems

STANAG 5616 Volume 1

Link 22 Link 16 and Link 11


92/99


Link-22, Link-16 and Link-11

Forwarding between Link-16, Link-22 and Link-11 is defined in STANAG 5616

Link-22 Data is based on Link-16 data elements, so data translation schema will

still be used between these two links

Some nations have expressed need to keep Link-11 in service with Link-22

Halifax Class DLPS does Forwarding on All Links

Aurora and MHP have translation requirements for the DMS/MDMS

IBMs DLPS Data Forwarding


93/99


IBM s DLPS Data Forwarding

Controlled by Operator using

Integrated Network Management

(INMT) Software

Operator selects Forwarding using

Graphical User Interface Link-16 to Link-11, Link-22, JRE

Link-22 to Link-11, Link-16, JRE

Link-11 to Link-16, Link-22, JRE

JRE to Link-11, Link-16, Link-22


94/99


Canadian TDL Platforms

Canadian Platforms with TDL (1)


95/99



Navy

IROQUOIS Class Destroyers (4)

(photo right)

TRUMP-CCS Link-11

2 fitted with Stand-Alone Link-

16Since 1991

HALIFAX Class Frigates (12)

CCS-330 Link-11

Link-14 removed

Since 1992

Modernizing under HCMprogram



96/99



Navy Contd

PRESERVER AOR

EDO NTDLS COTS Systems

1991 - 1

3 Since 1995 (photo left)

Air Force NORAD

ROCC-AWACS Data Link (RADIL)

Since 1986

Phasing Out 2006?



97/99



Air Force CP-140 AURORA (18)

Link-11Since 1982 (photo right)

Army ADATs Battery CP (4)

Link-11BAcquired ADSI system from USArmySince 2004

Navy - Ashore MULTOTS test system Link-11

Since 1995

New Canadian TDL Systems


98/99


New Canadian TDL Systems

CH-148 Cyclone Maritime Helicopter

Mission system by General Dynamics

Canada (photo left)

Link-11 System (DLP, embedded Crypto and

DTS) by Ultra Electronics (UK)

Link-11 only

Future Upgrade to Link-22 CP-140 Aurora Data Management System

Upgrade

Mission System by General Dynamics

Canada (photo next slide)

Link-11 DLP by Rockwell-Collins France

Embedded within DMS

Legacy Crypto and DTS Future Upgrade to Link-16, Link-22

New CP-140 Aurora DMS


99/99

New CP 140 Aurora DMS

Introduction To Tactical Data Links

Documents

Transcript of Introduction To Tactical Data Links