Link 22 F ili i ti amiliarization Familiarization

NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
F ili i ti
Familiarization
LCDR Peter Duffley
Third Party Sales Officer / CAN Rep
Mr. Vincenzo Sferra – Northrop Grumman
INFORMATION NOT RELEASEABLE FOR COMMERCIAL USE OR BEYOND
IMMEDIATE AUDIENCE WITHOUT PRIOR PERMISSION OF THE NILE PMO
Slide 1
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Link 22 Overview
1. Solves the shortcomings of
Link 11
2 Beyond Line of Sight (BLOS)
2.
HF Sky-wave Capability
3. Automatic Routing and Relay of
all media types provides
Extended Range
4 TDMA access and Dynamic
4.
Bandwidth allocation
5. Simplified Planning and
Operations, more automated
than Link 16
6. Allows Late Network Entry and
Dynamic Network Changes
Slide 2
Link 11
1950
1960
Link 16
1970
1980
1
Late
Network
Entry
1990
2
Link 22
2000 2010
3
NU4
NU6
NU3
NU5
TIME
NU1
NU2
NU8
NU7
NILE PMO
Link 22
Familiarization
Link 22 Overview, cont
1.
2.
3
3.
Slide 3
Link 22 interconnects
air, surface, subsurface,
and ground-based
tactical data systems
systems,
and it is used for the
exchange of tactical data
among the military units
Link 22 will be deployed
in peacetime, crisis, and
war to support NATO
and Allied warfare
tasking
Link 22 will complement
Link 16 and replace
Link 11
IDLS 2009
2 – 4 December
Vienna,, Austria
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Message
g Family
y & Data Dictionary
y
1. Link 22 message set is
part of the J-family,
easing Data Forwarding
and avoiding loss of
information
2. Most messages are
FJ-series
3 F-series messages are
3.
formatted to allow
higher track update per
second
4. Same Track Numbering
as Link 16 (> Link 11)
Link 16
Link 22
16
22
A Link 22 message can
contain a complete Link 16
message
Slide 4
16
16
22
OR
A Link 22 message can
contain parts of Link 16
messages
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Message
g Format and Processing
g
1. Link 22 uses F and FJ messages
2 Future expansion available – Capability of
2.
transmitting other information formatted into 70-bit
message words
3. Link 22 does not require the knowledge of tactical
data content beyond the DLP
F-Series Link 22
Tactical Messages Series Indicator
SER IND = 0
Unique F-Series Message Word
SER IND = 1
Non-Unique F-Series Message Word
PMI = 0
Packed J-Series Message Word
Slide 5
PMI = 1
Reserved for Future Expansion
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Granularity and Alignment
1. Link 22 uses Geodetic Coordinates as Link 16
2. Link 11 uses Cartesian Coordinate limiting
accuracy and “Playing Area”
3 Link
3.
Li k 22 uses Geodetic
G d ti Registration
R i t ti
Li k
Link
Slide 6
M th d
Method
Link 22
Geodetic Registration
Link 16
Remote IU Registration
Link 11
Gridlock
Link 11B
Site Registration
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
NILE PMO
Quality of Service (QoS)
1. Link 22 allows to define
several QoS
a. Priority
Pi i
Message
Time of
Validity
b. Reliability
i.i
St d d
Standard
ii. High
iii. Guaranteed Delivery
c. Data Originator
Identification
d. Perishability
e. Indicator Flags
f. Addressing
Slide 7
P i it
Priority
Data
Originator
Addressing
Perishability
Message
Contents
email
Reliability
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Addressing
1. Totalcast: All link 22 units
2 Neighborcast: All Radio Frequency (RF)
2.
neighbors on each NILE Network on which
the NILE unit operates
3. Mission Area Sub Network (MASN): A logical
group of units that has been previously
d fi d
defined
4. Dynamic List: A list of two to five units that
are specified
ifi d in
i the
th requestt
5. Point-to-Point: A single unit that is specified
i the
in
th requestt
Slide 8
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Super Network and Networks
1.
A Super Network may include up to 8 Networks and 125 NILE
Units
2.
A Single unit can be part of 4 networks at the same time,
which can be any combination of
a. HF FF
b. UHF FF
c. HF Frequency
Hopping
d. UHF Frequency
Hopping
Slide 9
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 uses TDMA
1. No single point of Failure, with up to 125 units
2 Access to the Network is deterministic
2.
deterministic, with
High Priority messages taking precedence
over Lower Priority messages
Slide 10
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
(Operational) Network Cycle Structure (ONCS)
1. The ONCS can be defined in the OLM as input
parameters or as detailed below.
2. The ONCS input requires
a. Number of Units in the Network
i.
Capacity Need
ii. Access Delay
b Tolerance
b.
T l
c. Efficiency
d Media Type
d.
e. Media Setting Numbers
f
f.
Fragmentation Rate (1-3)
g. DTDMA Setting
Slide 11
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Management
1. The SNMU and, in some cases the NMU, can
order certain management changes
a. Starting a new NILE Network
b. Shutdown of a NILE Unit, Network or Super Network
c. Optimization of Network performance
d. Controlling Management Roles
Super Network
S
N t
k
(Only One)
NILE Networks
(One for Each Network)
Slide 12
SNMU
NMU
NMU
NMU
NMU
NetworkMembers
Members
Network
Network
Members
No
Role
NoMembers
Role
Network
No
Role
No Role
Standby
SNMU
Standby
Standby
Standby
NMU
Standby
NMU
NMU
NMU
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Automatic Relay
1. Relay roles are automatically updated based on
Connectivity changes and Network Membership
2. Messages are repeated to achieve the desired
level of reliability, attempting to overcome bad
propagation conditions or jamming
Slide 13
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Automatic Relay Path Definition
3
Path 2
Path 2
Path 2
Path 1
1
Path 1
4
6
Path 3
Path 3
5
PRNU
2
Slide 14
RPRNU
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Secure Communications
1. Uses same Link 16 chip, with an added layer
to address spoofing and jamming
2. One LLC allows multiple Networks
3. A new modernized MLLC is being procured to
satisfy NSA Crypto modernization
requirements
Slide 15
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Resilience
1. Distributed Protocols
2 Automated Fault Management
2.
3. Increased Security Protection
4. No Single Point of failure, different from
Link 11

Net
Control
Station
(NCS)

Slide 16








NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Initialization
PLANNING (Fundamental Parameters)
Production of the OPTASK Link Message
1. NILE Unit Initialization
2. Network Initialization
OPTASK Link
Message
OPTASK Link Message distribution
Platform Initialization
Initialize CRYPTO
Initialize Each SPC & Radio For Each
NN
INITIALIZATION (Control)
DLP
SNC
LLC
LLC
LLC
LLC
FEEDBACK (Status)
Slide 17
SPC
SPC
SPC
SPC
Radio
Radio
Radio
Radio
NILE PMO
Link 22
Familiarization
Fundamental Parameters
1. Operational Tasking (OPTASK)
2 SN Directory
2.
3. SNC Initialization
4. Network Initialization
OPTAS
SK Link Me
essage
5. Platform data set
set-up
up
Slide 18
IDLS 2009
2 – 4 December
Vienna,, Austria
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Frequency
1. Link 22 uses Military HF & UHF bandwidth
simplifying the frequency clearance restrictions
restrictions,
supporting both Line of Sight (LOS) and Beyond
LOS (BLOS)
(
)
Ionosphere
Slide 19
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
NILE PMO
Data Transfer & Radio
1. Link 22 has higher bandwidth than Link 11
2. Link 22 will work in environments where Link 11 will
not work at all
3. Current UHF FF and HF FF radio are compatible with
Link 22
Link 11 HF/UHF
1,090 or 1,800
Link 16 JTIDS
26,880-107,250
Link 22 HF
Link 22 UHF
(Fixed Frequency)
(Fixed Frequency)
1,493 - 4,053
12,666
4 E
4.
Example
l off available
il bl bandwidth
b d idth using
i
Multiple
M lti l
Networks
* Currently using 2 LLCs
Slide 20
3 HF and 1 UHF
2 HF and 2 UHF
(Fixed Frequency)
(Fixed Frequency)*
24,825
33,438
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
NILE PMO
Automated Congestion
g
Management
g
1. Multiple ways to address and solve Congestion
Management
a. Routing/Relay: congestion avoidance
b. Dynamic TDMA
Congestion Management Can Reallocate Unused Capacity
NU
1
NU
2
NU
3
Congested
Slide 21
NU
6
NU
8
NU
10
Nearly Congested
NU
1
NU
2
NU
3
NU
6
Not Congested
NU
8
NU
10
Link 22
Familiarization
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Automated Congestion
g
Management,
g
, cont
2. Link 22 provides new automated Network
Management including congestion control
Congestion
NO Congestion
Reduce the Flow of Transmission
Service Requests (TSRs)
TSR
Queue

Slide 22
AND / OR
Allocate More Transmission
Capacity on Network
TSR
Queue

NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Protocol Summary
1.
2.
3.
4.
5.
6.
7.
8.
9
9.
10.
11
11.
Slide 23
Entering and Leaving a Network or the Super Network
g Network/Late Network Entry
y
Join an existing
Initialize New Networks
Closing a Network or the Super Network
Re-Initialization/Reconfiguration
Congestion Assessment and Dynamic TDMA
Multiple Quality of Service (QoS) and Automatic Relay
Role Management
R di Silence
Radio
Sil
Security and Key Management
Performance Monitoring & Fault Management
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 as Satellite Alternative
1. Complimentary with Link 16, shares the same
Data Element Dictionary simplifying Data
F
Forwarding
di
2. Link 22 BLOS and Relay can be an alternative
to Satellite for interconnecting separate Link
16 Networks
Slide 24
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
System Architecture – Layer Approach
National
Responsibility
Tactical Data System /
Data Link Processor
System Network Controller
Link Level COMSECs
Joint
Development
Signal Processing Controllers
Radios
National
Responsibility
Slide 25
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Layered Communications Architecture
Slide 26
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 vs. Link 11
1. Link 11 uses Roll Call protocol
a. Net Control Station (NCS) is a single Point of Failure
b. All units needs to be in direct connectivity with the NCS,
unless Satellite is used which increases the Access Delay
c. Access Delay to the Network increases with the number of
units (max 62) and traffic
d. Uses a Single Network, while Link 22 can have up to 8
Networks seamless interconnected
e. Weak security, Susceptible to Intercept, Spoofing,
Jamming
Slide 27
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Link 22 vs. Link 11, cont
2. Link 11 message set is limited and may no
longer be updated together with Link 16 and
Link 22 J-family set
g encryption,
yp
, stronger
g coding
g
3. Link 22 has strong
and can also use up to 4 media type: UHF/HF,
including Frequency Hopping
Good Conditions
Link 11


Link 22
Slide 28
Bad Conditions
Link 11


Link 22
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Guidebook – 3 Versions
1. Overview
a. Chapter 1
b. Appendix A; E-G
2. Overview & Operations
a Chapter 1 & 2
a.
b. Appendix A-B; E-G & Index
3. Complete Version
Slide 29
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Guidebook – Table of Contents
1. Chapter 1 - Link 22 Overview
a. Section
A
Introduction
b. Section
B
Features
c. Section
C
Benefits
d. Section
D
Acquisition
2. Chapter 2 - Link 22 Operations
Slide 30
a. Section
A
Overview
b. Section
B
Planning
c. Section
C
Link 22 Operations
d. Section
D
Tactical Messages
e. Section
S ti
E
Li k 22 iin a M
Link
Multilink
ltili k E
Environment
i
t
Link 22
Familiarization
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Guidebook – Table of Contents (cont)
1 Chapter
1.
Ch t 3 - Link
Li k 22 T
Technical
h i l
a. Section
A
Architecture
b Section
b.
S ti
B
E t
External
l Protocols
P t l
c. Section
C
Internal Protocols
2 Appendices
2.
a. Appendix A
Integration and Test Tools
b Appendix B
b.
Troubleshooting
c. Appendix C
Minimum DLP-SNC Interface Implementation
d Appendix D
d.
Initialization Parameter Generation
e. Appendix E
Acronyms and Abbreviations
f.
Glossary
Appendix F
g. Appendix G
Slide 31
References
NILE PMO
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
Planning & Design
1. Reduced need for a Design tool
Operational
Requirements
Unit Capabilities/
Limitations
OPTASK Link
Message
Planning
Slide 32
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 Concept
p of Operation
p
1. Link 22 can be used to interconnect
geographically dispersed Networks
Slide 33
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
NILE REFERENCE SYSTEM
(NRS)
&
Multiple Link System Test and
Training Tool
(MLST3)
Slide 34
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 Integration and Test Tools
1. NRS is used in the following ways:
a. SNC
SNC-to-SNC
to SNC compatibility testing
b. Verification and Validation of requirements
c Automated regression testing
c.
d. LLC and SPC Verification and Validation support
2. NRS software components can be installed
in COTS HW
3. NRS is distributed by the NILE PMO
4 It allows several configurations
4.
Slide 35
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 Integration and Test Tools
1. MLST3 supports the development and testing of
national DLPs in the following areas:
a. Conformance to Tactical Standards
b. Interoperability, in both single and multi-link environments
c. National DLP Integration and Testing
2. MLST3 supports several links including Link 16,
Link 11,
11 Link 22,
22 JREAP,
JREAP Link 4A
4A, …
a. MLST3 with Link 22 option requires NRS components
b MLST3 with Link 22 allows fully functional NRS configurations
b.
3. MLST3 is distributed by SPAWAR (SSC Pacific
Code 591))
4. NRS Components are distributed by the NILE PMO
Slide 36
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22 Integration and Test Tools
1. NRS and MLST3 use the following
components:
a. DLP Simulation
b SNC Diamond (SNC♦) – can simulate multiple SNCs
b.
i. NRS up to 125
ii. MLST3 up to 32
c. LLC Simulator – can simulate multiple
p LLCs
d. Media Simulator – simulates SPCs/Radios
i.i Real SPCs can also be mixed with Simulated one using
MLST3
Slide 37
NILE PMO
Link 22
Familiarization
NRS Configurations
1. SNC Verification
2 Multiple Units Under Test (MUUT)
2.
3. System Simulation
4 Media
4.
M di Simulator
Si l t (MS) Standalone
St d l
Slide 38
IDLS 2009
2 – 4 December
Vienna,, Austria
NILE PMO
Link 22
Familiarization
SNC Verification
1. SNC Verification is the
primary NRS configuration
used to verify
f the
functionality of the SNC
2. SNC Verification involves
a single SNC UUT being
tested with up to 124
simulated units
Slide 39
IDLS 2009
2 – 4 December
Vienna,, Austria
Link 22
Familiarization
NILE PMO
MUUT with Real SPCs
1. Example of
NRS use
2. Radio can be
replaced
p
by
ya
COTS serial
Connectivity
Device
Slide 40
IDLS 2009
2 – 4 December
Vienna,, Austria
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations
1.
2.
3.
4.
5.
Multiple Units
Live Link
System Simulation
NCE Simulation
Single
Note: MLST3 supports only a single SNC  for 32 simulated units and
up to 5 live Units, depending on the configuration
Slide 41
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations – Multiple Units
1. The main purpose of this configuration is to test
national DLPs using a real SNC, with the MLST3
providing the remainder of the test environment
a. Up to five Host/DLP & SNC UUTs
b. Up to 32 simulated units provided by the SNC
Slide 42
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations – Live Link
1. Similar to the Multiple Units configuration
a. Real SPCs are used on any Live Network
b. Simulated Networks and Real Networks can be combined, but not on
the same Network
c.
Slide 43
Onlyy two units can be p
present p
per Live Network,, one being
g simulated byy
the MLST3 and the other being a real DLP or a MSLT3 Single
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations – System Simulation
1. Lightweight configuration that requires just the
SNC, MS and the MLST3 SW
a.
Simulation for up to 32 units
b. These three applications can all run on a single PC without any extra
p
), making
g this configuration
g
hardware ((such as serial rocketports),
portable and rapidly deployable
c.
Slide 44
Active MLST3 data recording can be
used to verify tactical traffic and the
DLP-SNC• interface
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations – NCE Simulation
1. Extension of the System Simulation configuration
2 MLST3 provides a proxy layer by assigning up to
2.
five Host/DLPs to their own unique simulated
SNCunit
3. This proxy layer is transparent to the DLP because
it connects to the MLST3 exactly
th same way as it would
the
ld an
SNC UUT
4 Lightweight DLP-SNC
4.
DLP SNC interface
testing environment for a DLP
Slide 45
NILE PMO
Link 22
Familiarization
IDLS 2009
2 – 4 December
Vienna,, Austria
MLST3 Configurations – Single
1. MLST3 can also be used as a single unit DLP
2. Real DLPs and MLST3 Single
g can be combined to
provide a Link 22 environment
Slide 46
NILE PMO
Link 22
Familiarization
QUESTIONS?
Slide 47
IDLS 2009
2 – 4 December
Vienna,, Austria