SyntheSys

Introduction to JTIDS/MIDS Link 16

St. Hilda’s Business Centre

The Ropery
Whitby
North Yorkshire
YO22 4ET

tel: +44 (0)1947 821464

fax: +44 (0)1947 603301
email: training@synthesys.co.uk
web: www.synthesys.co.uk

29/09/2015 F12803 Slide No.1

Introduction to JTIDS/MIDS Link 16

Welcome to IDLS 2015

29/09/2015 F12803 Slide No.2

Introduction to JTIDS/MIDS Link 16

Introduction to JTIDS/MIDS
Link 16

29/09/2015 F12803 Slide No.3

 Introduction

• Paul Czajkowski (Ski)

• Training Consultant & Systems Engineer

Introduction to JTIDS/MIDS Link 16

• Retired Royal Air Force 22 years

• Involved in TDLs all my career

• Conduct TDL training all over the world

29/09/2015 F12803 Slide No.4
 Scope

• Main Features and Supporting Documentation

• JTIDS/MIDS Nations & Platforms

Introduction to JTIDS/MIDS Link 16

• Basic Architecture

• Initialisation and Synchronising to a Network

• Basic exchange of J-Series Messages

29/09/2015 F12803 Slide No.5
 JTIDS/MIDS Link 16 Terminology

• Joint Tactical Information Distribution System (JTIDS)

• Term to describe software/hardware and R/F equipment on
first generation terminals
Introduction to JTIDS/MIDS Link 16

• Multi Functional Information Distribution System

(MIDS)
• Term to describe same requirement on second generation
terminals

• JTIDS/MIDS is the Bearer and Link 16 is the language

29/09/2015 F12803 Slide No.6
 JTIDS/MIDS Link 16 Terminology

• MIDS uses J-Series messages

• MIDS/Link 16 supports approximately 525,000 objects

Introduction to JTIDS/MIDS Link 16

• MIDS uses UHF

• MIDS utilises 51 discrete frequencies

• MIDS IU is known as a JTIDS Unit (JU)

• C2 or NonC2
29/09/2015 F12803 Slide No.7
 JTIDS/MIDS Main Features

Increased
Transmission
Granularity
Security (TSEC)
(WGS-84)
Introduction to JTIDS/MIDS Link 16

Message Security Data exchange in

(MSEC) more environments

JTIDS/MIDS
Link 16

29/09/2015 F12803 Slide No.8

 Documentation

• Technical specification of TDLs and procedures for

their operation are defined by both national and
NATO documents
Introduction to JTIDS/MIDS Link 16

• Standardised NATO Agreement (STANAG)

• ‘NATO Standards’

• Most TDLs are initially designed to

US requirements
• US Military Standards (MIL-STDs)

29/09/2015 F12803 Slide No.9

 Documentation

Message Operator
Terminal
Standard Procedures
Introduction to JTIDS/MIDS Link 16

MIL-STD STANAG
JMTOP
-6016 4175

STANAG
MIDS SSS ADatP-33
5516

29/09/2015 F12803 Slide No.10

 Nations & Platforms

• There are approximately 43 Nations and it is used on a

variety of platforms
Introduction to JTIDS/MIDS Link 16

• Some platforms are Multi-TDL equipped

I can do Link 1, I can only do
11A/B and 16 Link 22

• Endless issues/problems of interoperability

29/09/2015 F12803 Slide No.11
 Basic Architecture

• JTIDS/MIDS uses Time Division Multiple Access

(TDMA)
Introduction to JTIDS/MIDS Link 16

• In a JTIDS/MIDS network each JTIDS Unit (JU) is

allocated a portion of time known as a Time Slot (TS)

• Each TS is 7.8125ms in duration and there are 1536 TS

available

• Which adds up to a 12 second repeating cycle known

as a frame
29/09/2015 F12803 Slide No.12
 TDMA

• Each 24 hour day is divided in to 112.5 epochs

24
HOURS
Introduction to JTIDS/MIDS Link 16

• Each epoch has 64 frames

• Each frame has 1536 Time Slots

• Terminal simply follows the same 12 second cycle

29/09/2015 F12803 Slide No.13
 Basic Architecture

• Network can support up to

128 nets Net 127
Introduction to JTIDS/MIDS Link 16

• Each net number supports a

different Frequency Hopping
Pattern (FHP) controlled by TSEC
Net 3

• Each JU is allocated TS on a net Net 2

number to either Tx, Rx or Relay
Net 1

Net 0
• But a JU can only operate on one
net in any given TS
29/09/2015 F12803 Slide No.14
 Initialising a Terminal

• When a JU wishes to join a network it requires a load

file
Introduction to JTIDS/MIDS Link 16

• To create a load file specific parameters are needed

• Mission Specific Parameters (MSP)

• Each JU is allocated an address and maybe a track block

• Network Specific Parameters (NSP)

• Time Slots and net number(s) to operate on

29/09/2015 F12803 Slide No.15

 Initialising a Terminal

• Platform Specific Parameters (PSP)

• Factors that are particular to a platform e.g. ‘cable delays’
Introduction to JTIDS/MIDS Link 16

• PSP are normally stored within

• Initialisation Data Preparation Facility (IDPF) or a Mission
Support System (MSS)

• An operator will load both the NSP and MSP on to the

IDPF/MSS and create a load file

• Then transfer the load file to the terminal/host

29/09/2015 F12803 Slide No.16
 Initialising a Terminal
Network Specific
Parameters (NSP)
Network Design

Mission Initialisation
Introduction to JTIDS/MIDS Link 16

Specific Data HOST

Parameters Preparation
(MSP) Facility (IDPF)
OPTASK Link NSP/MSP/PSP
Track Block all create the
JU Load File
MIDS Duties

Platform Specific
Parameters (PSP)
Cable lengths
29/09/2015 F12803 Slide No.17
 Synchronising to a Network

• For a terminal to successfully synchronise to an

established network it requires
• Correct Crypto
Introduction to JTIDS/MIDS Link 16

• Correct Time
• Line of Sight

• Crypto is supplied prior to operations but correct

system time needs to be found

• System time is supplied by Network Time Reference

(NTR) which defines the beginning of each frame
29/09/2015 F12803 Slide No.18
 Synchronising to a Network

• Synchronisation is when a joining unit acquires and

then maintains system time either actively or
passively
Introduction to JTIDS/MIDS Link 16

• Automatic process I would like to join the

network

• Achieved in a two part process

• First part is to achieve Coarse synchronisation
• Second part is to achieve Fine synchronisation

29/09/2015 F12803 Slide No.19

 Synchronising to a Network

• To achieve Coarse synchronisation, a joining unit must

receive an error free J0.0 Initial Entry Message (IEM)
I Tx IEM at the start
Introduction to JTIDS/MIDS Link 16

of the frame
I estimate system time
Great I found it 

IEM NTR

29/09/2015 F12803 Slide No.20

 Synchronising to a Network

• To achieve Fine synchronisation a joining unit then

exchanges several Round Trip Timing (RTT) messages
Introduction to JTIDS/MIDS Link 16

• Allowing a joining unit to Fine synch 

refine its clock Now I can transmit
messages

• After that a terminal continues to

exchange RTT messages to support
a value known as Time Quality

29/09/2015 F12803 Slide No.21

 Exchanging J-Series Messages

• Various J-Series messages exist to support tactical

data exchange and commands
Introduction to JTIDS/MIDS Link 16

• J-Series messages are transmitted and/or received

dependent upon the type of platform

• J-Series messages are ‘grouped’ for transmission to a

Network Participation Group (NPG)

• Currently 31 are defined for use by their function

29/09/2015 F12803 Slide No.22

 Exchanging J-Series Messages

• Time Slots are allocated to an NPG dependent upon

the requirements of the network
NPG 2 & 3 Round Trip Timing
Introduction to JTIDS/MIDS Link 16

NPG 4 Network Management

NPG 5 & 6 Precise Participant Location & Identification (PPLI)
NPG 7 Surveillance
NPG 8 Mission Management & Weapons Coordination
NPG 9 Control
NPG 10 Electronic Warfare
NPG 12 & 13 Voice
NPG 19 & 20 Fighter-to-Fighter A&B

• All platforms will transmit and receive NPG 6 PPLI

messages
29/09/2015 F12803 Slide No.23
 Exchanging J-Series Messages

We each Tx a
J2.2 Air PPLI
Introduction to JTIDS/MIDS Link 16

I Tx a J2.5 Land I Tx a J2.3

Point PPLI Surface PPLI

29/09/2015 F12803 Slide No.24

 Exchanging J-Series Messages

• Generally the largest exchange of data within a

network is for Surveillance
Introduction to JTIDS/MIDS Link 16

• C2 units are defined as those that Tx surveillance data

• All units need to receive the surveillance data to

maintain situational awareness

• There are 21 surveillance messages primarily

supporting the transmission of track data and track
management
29/09/2015 F12803 Slide No.25
 Exchanging J-Series Messages

Thanks for the

Introduction to JTIDS/MIDS Link 16

warning

I detect an air track and Tx a

J3.2 Air Track message

29/09/2015 F12803 Slide No.26

 Exchanging J-Series Messages

I detect an air track and Tx a

J12.6 Target Sorting Message
Introduction to JTIDS/MIDS Link 16

It is in the It is in the
network lets network lets
correlate correlate

29/09/2015 F12803 Slide No.27

 Summary

JTIDS/MIDS is the bearer and Link 16 is the language

Operates over 51 frequencies and 128 nets

Introduction to JTIDS/MIDS Link 16

Primary documents are MIL-STD-6016 & STANAG

5516

JTIDS/MIDS operates on a 12 second repeating cycle

A JU can only operate on one net in any given TS

29/09/2015 F12803 Slide No.28
 Summary

Terminal needs MSP/PSP/NSP to create a load file

Terminal requires Time/LOS/Crypto to synchronise

Introduction to JTIDS/MIDS Link 16

Synchronisation is a two part process – Coarse & Fine

Lots of J-Series message exist to support the

transmission of tactical data and commands

29/09/2015 F12803 Slide No.29

 Introduction to JTIDS/MIDS Link 16

29/09/2015
F12803
Slide No.30
Introduction to JTIDS/MIDS Link 16

Mr Paul Czajkowski
paul_czajkowski@synthesys.co.uk

Tel: +44 (0) 1947 821464

Mob: +44 (0)7507866253
www.synthesys.co.uk
29/09/2015 F12803 Slide No.31