1 © NILE PMO 2002 IDLS 2003 Newbury, UK 30 Sep – 2 Oct 2003 LINK 22 NILE Program Management Office 2 © NILE PMO 2003 LINK 22 PRESENTATION CDR Antonio

1© NILE PMO 2002

IDLS 2003Newbury, UK

30 Sep – 2 Oct 2003

LINK 22NILE Program Management Office

2© NILE PMO 2003

LINK 22 PRESENTATIONLINK 22 PRESENTATION

CDR Antonio Scarciglia CDR Antonio Scarciglia Italian Representative To The Italian Representative To The

NILE PMONILE PMO

Dr. Kevin BuckDr. Kevin BuckNILE Program ManagerNILE Program Manager

INFORMATION NOT RELEASEABLE FOR COMMERCIAL USE OR BEYOND IMMEDIATE AUDIENCE WITHOUT PRIOR PERMISSION OF THE NILE PMO


30 Sep – 2 Oct 2003


3© NILE PMO 2003

OUTLINEOUTLINE

LINK 22 Background

Functional Architecture

Operational Characteristics

Technical Characteristics

LINK 22 On-The-Air Test


30 Sep – 2 Oct 2003


4© NILE PMO 2003

LINK 22 BACKGROUNDLINK 22 BACKGROUND

OBJECTIVE OF THE NILE PROGRAM

Design a New Tactical Data Link System (Link 22) Consisting of a Computer to Computer Digital Data Link Among Tactical Data Systems Equipped Ships, Submarines, Aircraft and Shore Sites, which will Meet the Requirements of the NATO Staff Requirement, Dated 09 March 1990.


30 Sep – 2 Oct 2003


5© NILE PMO 2003

REQUIREMENTS

• Operational: NATO Staff Requirement, Revised Mar 90

• System, Functional and Performance: NATO Elementary Requirements Document, 12 December 94

GOALS

• Replace Link 11 (Eventually)

• Complement Link 16

• Improve Allied Interoperability

• Enhance Commanders’ War-fighting Capability

LINK 22 BACKGROUND (Cont.)LINK 22 BACKGROUND (Cont.)


30 Sep – 2 Oct 2003


6© NILE PMO 2003

LINK 22 BACKGROUND (Cont.)LINK 22 BACKGROUND (Cont.)

The Link 22 Has Been Developed Collaboratively by Seven Nations Under the Aegis of a Memorandum of Understanding (MOU)

Six of the Seven NILE Nations Are Conducting The In-Service Support (ISS) Phase Under a New MOU That Came Into Effect on July 2002

The Current ISS MOU Will Remain in Effect for Five (5) Years, Until July 2007

Spain Has Applied to Join NILE

United States Is Host Nation


30 Sep – 2 Oct 2003


7© NILE PMO 2003

NILE/LINK 22 SCHEDULENILE/LINK 22 SCHEDULE


30 Sep – 2 Oct 2003


8© NILE PMO 2003

NATIONAL LINK 22 PROGRAMSNATIONAL LINK 22 PROGRAMS

NATION IN SERVICE DATE

CANADA 2006

FRANCE 2006

GERMANY 2006

ITALY 2006

NETHERLANDS 2007

UNITED KINGDOM 2007

UNITED STATES 2006


30 Sep – 2 Oct 2003


9© NILE PMO 2003

OUTLINEOUTLINE

LINK 22 Background






30 Sep – 2 Oct 2003


10© NILE PMO 2003

LINK 22 FUNCTIONAL ARCHITECTURELINK 22 FUNCTIONAL ARCHITECTURE

NILE Communications Equipment (NCE)

Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment

National Development

NILEProducts

NILE Products


30 Sep – 2 Oct 2003


11© NILE PMO 2003

LINK 22 FUNCTIONAL ARCHITECTURELINK 22 FUNCTIONAL ARCHITECTURE Tactical Data System (TDS)

– National Development Activity

Data Link Processor (DLP)– National Development Activity (Based on Common

Interoperability Requirements)

System Network Controller (SNC)– Development Complete – Software Available Through NILE

PMO and NILE Nations

Link Level COMSEC Device (LLC)– Available By December 2003

– LLC Simulator Available


30 Sep – 2 Oct 2003


12© NILE PMO 2003



Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment



30 Sep – 2 Oct 2003


13© NILE PMO 2003

LINK 22 FUNCTIONAL ARCHITECTURE LINK 22 FUNCTIONAL ARCHITECTURE

Data Link Processing (DLP)

Interfaces with National TDS

Services Tactical Data (STANAG 5522)

Implements ADatP-22 Procedures

Interfaces with the SNC


30 Sep – 2 Oct 2003


14© NILE PMO 2003



Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment



30 Sep – 2 Oct 2003


15© NILE PMO 2003


SYSTEM NETWORK CONTROLLER (SNC) Common Software Development Ensures Interoperability

Provides Message Delivery Service

Provides Network Management Capabilities via Management Function (MF)

Performs Dynamic TDMA, Relay & Routing, Late Network Entry

Interfaces: DLP and LLC

Portable to Standard COTS Hardware

– Tested in WinNT, HPUX and Solaris Operating Environments


30 Sep – 2 Oct 2003


16© NILE PMO 2003



Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment



30 Sep – 2 Oct 2003


17© NILE PMO 2003


LINK LEVEL COMSEC (LLC) Provides Communications Security (COMSEC)

Data Integrity Checksum Guards Against Undetected Message Errors

Chipset Commonality with Link-16

Each LLC Supports up to 4 Nile Networks (NN) Using Same KEY

SNC supports up to 4 LLCs with Same/Different KEY


30 Sep – 2 Oct 2003


18© NILE PMO 2003



Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment



30 Sep – 2 Oct 2003


19© NILE PMO 2003


SIGNAL PROCESSING CONTROLLER (SPC)

National Development Responsibility

Performs Modulation/Demodulation, EDAC (Error Detection and Correction) and Reception Quality Assessment

Interface: LLC, Radio and Time Of Day Standard

– TOD must be accurate to within 1 millisecond of UTC

Transmits/Receives Data:– HF FF @ 1493 to 4053 bps STANAG-4539– HF EPM @ 500 to 2200 bps STANAG-4444– UHF FF @ 12,667 bps STANAG-4205– UHF EPM @ Classified STANAG-4372


30 Sep – 2 Oct 2003


20© NILE PMO 2003



Link 22 System

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC Radio

MLTT & NRS

NationalDevelopment



30 Sep – 2 Oct 2003


21© NILE PMO 2003

LINK 22 FUNCTIONAL ARCHITECTURELINK 22 FUNCTIONAL ARCHITECTURERADIO SYSTEMS HF FF and UHF FF Utilize Existing Link 11 Radios

– HF FF: 3 KHz Upper Sideband Audio Port on HF Radios

– UHF FF: 16 Kbps (KY-58) Port on UHF Radios

HF EPM and UHF EPM Require Frequency Hopping Radio Systems: National Development Responsibility

– Link 22 Requirements Incorporated into EPM Radio STANAGs (4444 And 4372)

– EPM Radios require Transmission Security (TRANSEC) Device to Control Frequency Hopping Patterns

– EPM Radios May Require Interface to Time Of Day Standard


30 Sep – 2 Oct 2003


22© NILE PMO 2003

OUTLINEOUTLINE

LINK 22 Background






30 Sep – 2 Oct 2003


23© NILE PMO 2003

IMPROVEMENT OF LINK 11IMPROVEMENT OF LINK 11

Link 22 Overcomes The Following Link 11 Limitations:

– Lack of Electronic Protection Measures (EPM)

– Insufficient Capacity in Terms of Tactical Message Throughput

– Insufficient Robustness (esp. Reliance on NCS)

– Insufficient Error Detection and Correction

– Inflexible and Slow Data Link Procedures

– Message Standard Limitations

– Limited Routing


30 Sep – 2 Oct 2003


24© NILE PMO 2003

LINK 11 OPERATION VICE LINK22LINK 11 OPERATION VICE LINK22

Differences– Link 22 Has No Net Control Station

– Link 11 Does Not Distiguish Between Urgent and Routine Information

– Link 22 Has Built In Relay

Commonalities– The Same Frequencies (HF And UHF Fixed Frequency)

– The Same Radios (HF And UHF FF)

– That’s It!

Link 22 Has More In Common With Link 16 Than Link 11


30 Sep – 2 Oct 2003


25© NILE PMO 2003

Link 11 Roll CallLink 11 Roll Call

64

56 64 64 04

NCS

56

04


30 Sep – 2 Oct 2003


26© NILE PMO 2003

Multi-Network

Multi-Network Membership

LINK 22 OPERATIONSLINK 22 OPERATIONS

NU15 NU21NU19

NU10NU24NU17

NU9NU 23

NU20

NU13 NU14NU9

NU16ISNU6

NU11

NU2

NU2 NU6NU9

NU7NU12NU1

NU3Interrupt Slot

NU5

NU9 NU17IS

NU18NU26NU8

NU16NU24

NU7

NU15

NN1 - HF

NN2 – HF EPM NN4 – UHF EPM

NN3 - UHF

Multi-Media

SN


30 Sep – 2 Oct 2003


27© NILE PMO 2003

LINK 22 OPERATIONAL CHARACTERISTICSLINK 22 OPERATIONAL CHARACTERISTICS

KEY FEATURES

Dynamic Time Division Multiple Access

Dynamic Congestion Management

Multi-Media/Multi-Network

Routing and Relay

Mission Area Sub Networks

Late Network Entry

Dynamic Reconfiguration/Initialization


30 Sep – 2 Oct 2003


28© NILE PMO 2003

Time Division Multiple Access (TDMA)

– NILE Units (NUs) Have Pre-assigned Time Slots

– Interrupt Slot Available for Injection of High Priority Messages

– Time Slots Can be Dynamically Exchanged or Modified (DTDMA)


NU2 NU7NU8

NU3NU4NU6

NU5

NU1Interrupt Slot

NU3


30 Sep – 2 Oct 2003


29© NILE PMO 2003


The Group of all NUs is Known as the Super Network (SN)

A SN Can Consist of a Maximum Number of 125 NILE Units (NU)

SN Consists of up to 8 NILE Networks (NN)

A NU Can Participate in up to 4 NN on Same Media/Different Media

The Link 22 Message Consists of 72 bits

Each Tactical Message Is Based on Link 16Data Elements (STANAG 5522)


30 Sep – 2 Oct 2003


30© NILE PMO 2003

LINK 22 OPERATIONAL CHARACTERISTICSLINK 22 OPERATIONAL CHARACTERISTICS Dynamic Congestion Management

Too much information for the available capacity

Ask for more capacity (DTDMA)

Ask the DLP for message cancel authorization

Use alternative route

Revise the amount of data to betransmitted


30 Sep – 2 Oct 2003


31© NILE PMO 2003

LINK 22 OPERATIONAL CHARACTERISTICSLINK 22 OPERATIONAL CHARACTERISTICS Automatic Routing and Relay

Control of Relayers Available

NN 3NN 1


30 Sep – 2 Oct 2003


32© NILE PMO 2003


Up to Twenty Three (23) Mission Area Sub Networks May be Established

MASNs are an Addressing Scheme

SUPER NETWORK

NILE NETWORK 3

NILE NETWORK 2

NILE NETWORK 1

MASN 1

MASN 3

MASN 2


30 Sep – 2 Oct 2003


33© NILE PMO 2003


Late Network Entry (LNE)

– The Purpose of LNE Is to Allow Units Which Were Not Present at the Start of a NN/SN to Join

– LNE is Used when a NU is Completely New, i.e. It Was Not Listed in the Optask Link Message (OLM) and/or when Media Parameters Have Changed From That in the OLM

– LNE Includes Now a “Silent Join” Option that Allows a Unit to Join the Network Without Making Any Transmission

– Operator Input is Minimal

– Considered to be an Automated Background Activity


30 Sep – 2 Oct 2003


34© NILE PMO 2003


Dynamic Reconfiguration– Each NN can be reconfigured:

DTDMA (On or Off) Network Cycle Structure (NCS)

– The SN/NN Will Keep Operating During The Above Reconfigurations

Re-Initialization– New NNs can be started after SN Initialization

– Each NN can change Frequency, Waveform and Crypto Integrity Mode


30 Sep – 2 Oct 2003


35© NILE PMO 2003

NU 1: CN=LOWAD=SHORT

NU 2: CN=MED-LOW AD=MED-SHORT

NU 3: CN=MED-LOW AD=MED-SHORT

NU 4: CN=MED-HIGH AD=MED-SHORT

NETWORK CYCLE NETWORK CYCLE STRUCTURESTRUCTURE

CASE 1CASE 1

23 MSNCT = 2.59 sec


30 Sep – 2 Oct 2003


36© NILE PMO 2003

NU 1: CN=HIGHAD=SHORT

NU 2: CN=MED-HIGH AD=MED-SHORT

NU 3: CN=MED-LOW AD=MED-LONG

NU 4: CN=LOW AD=LONG

NETWORK CYCLE NETWORK CYCLE STRUCTURESTRUCTURE

CASE 2CASE 2

30 MSNCT = 3.375 sec


30 Sep – 2 Oct 2003


37© NILE PMO 2003

NCS COMPUTATION RESULTSNCS COMPUTATION RESULTS

NU # CN AD

1 LOW SHORT

2 MED-LOW MED-SHORT

3 MED-LOW MED-SHORT

4 MED-HIGH MED-SHORT

NU # CN AD

1 HIGH SHORT

2 MED-HIGH MED-SHORT

3 MED-LOW MED-LONG

4 LOW LONG

23 MSNCT = 2.59 sec

30 MSNCT = 3.375 sec


30 Sep – 2 Oct 2003


38© NILE PMO 2003


Multiple Link 22 Networks Supplement Link 16.

Link 22 Extends Multi-media Communication Capabilities to HF and UHF Frequency Bands.

Link 22 Provides Enhanced Networking Capabilities.

Link 22 and Link 16 Utilize Common Data Structures.


30 Sep – 2 Oct 2003


39© NILE PMO 2003


Multiple Link 22 Networks Complement Link 16

– Link 16 Is Primarily an AAW Data Link Frequently Relies on Airborne Relays

– Link 22, Originally Defined as Primarily Maritime (ASW/ASUW), Is More a General Purpose Data Link

Extended Surface Wave and Long Range Sky Wave HF

Ship-Ship Relay Networking Extends Connectivity – Link 22 Can Free up Additional Capacity for Link 16

Conversely, Link 22 Is Essential for Carrying Data that will Be “Pushed Off” of Link 16 During High Intensity Conflicts


30 Sep – 2 Oct 2003


40© NILE PMO 2003


Extends Multi-Media Communication Capabilities to HF and UHF Frequency Bands:

– Cost Effective Use of Existing Link 11 HF and UHF Radios

– Relaying via Multiple Link 22 Networks Remains Available When Airborne Relay Unavailable Also provides Time/Frequency/Angle-of-Arrival Diversity

– Anti-jam capability via STANAG Compliant HF-EPM and UHF-EPM Radios (optional)


30 Sep – 2 Oct 2003


41© NILE PMO 2003


Link 22 Provides Enhanced Networking Capabilities

– Nodeless TDMA, Continues to Operate Without Network Managers

– Enhanced Connectivity, Via Automatic Routing and Relay

– Interrupt Slots to Report High Priority Messages

– On-going Capacity Reallocation Via Dynamic TDMA

– Automated Optimization of Time Slot Allocations

– Automated Link Establishment and Re-configuration

– Automated Late Net Entry


30 Sep – 2 Oct 2003


42© NILE PMO 2003


Link 22 and Link 16 Utilize Common Data Structures:

– Most are FJ-series Messages (Same as J-Series)

– Efficient F-series Messages Use Many Common Data Elements

– Common JU/NU and Track Number (TN) Schemes.

– Supports Participant Location and Identification (PLI) Tracks

– Same Geodetic Coordinate System

– No Complicated Link 16 to/from Link 22 Data Translations


30 Sep – 2 Oct 2003


43© NILE PMO 2003

OUTLINEOUTLINE

LINK 22 Background






30 Sep – 2 Oct 2003


44© NILE PMO 2003

LINK 22 TECHNICAL CHARACTERISTICSLINK 22 TECHNICAL CHARACTERISTICS

Media Types: HF FF, HF EPM, UHF FF and UHF EPM

Coverage: Up to 1000 nautical miles

Jam Resistance: Signal Processing with Error Detectionand Correction, Network PacketEncryption (COMSEC) and ECMresistance (TRANSEC)

System Error Resistance: Goal of Bit Error Rate in Order of 10 -4

Robustness: Non-nodal, Relay Available, Multiple Sub-Nets and Dynamic Route Selection

Medium Access: Dynamic Time Division Multiple Access


30 Sep – 2 Oct 2003


45© NILE PMO 2003

BLOS TACTICAL DATA LINKSBLOS TACTICAL DATA LINKS

Link-16 Line of Sight

Link 22 UHF LOS

JRE

Link 22 HF BLOS

Link 22 Routing & Relay


30 Sep – 2 Oct 2003


46© NILE PMO 2003

LINK 22 TECHNICAL CHARACTERISTICSLINK 22 TECHNICAL CHARACTERISTICSThroughput: HF FF (QPSK max) 31 messages/sec

(8PSK max) 45 messages/sec

UHF FF Approx 150 messages/sec

(Multi-Network Capability Makes These Numbers Bigger)

User Data Rate: HF FF: 1493 – 4053bps

HF EPM: 500 – 2200bps

UHF FF: 12667bps

UHF EPM: Classified

It’s a Good Data Rate Considering a Narrow Bandwidth (W) and a Noisy Channel (Shannon Theorem Tells Us What is the Best We Can Do)

N

SWC 1log2


30 Sep – 2 Oct 2003


47© NILE PMO 2003


HF FF: 6 Waveforms QPSK/8PSK, RS Coding

UHF FF: 3 Waveforms, 16 Kbps NRZ FM, RS Coding

HF EPM: 4 Waveforms, QPSK, Dual RS Coding

UHF EPM: 4 Waveforms, Convolutional Coding 1/2, 16 Kbps NRZ FM


30 Sep – 2 Oct 2003


48© NILE PMO 2003


4 Different Modems, 4 Different Radio Systems, 17 Different Waveforms Make The Link 22 a Good Customer For JTRS

The Modem And The Radio Can Be Combined in a Software Radio Based System With a Complete NILE Waveforms Library

Link 22 With JTRS Will Make Easier The Enhancement of The NILE Waveforms


30 Sep – 2 Oct 2003


49© NILE PMO 2003

HOW IMPLEMENT LINK 22 IN JTRS?HOW IMPLEMENT LINK 22 IN JTRS?

LLC

SNCDLPTDS

RadioSPC

SPC Radio

SPC Radio

SPC RadioJTRSJTRSJTRS


30 Sep – 2 Oct 2003


50© NILE PMO 2003

OUTLINEOUTLINE

LINK 22 Background






30 Sep – 2 Oct 2003


51© NILE PMO 2003

HF LINK 22 ON-THE-AIR TESTHF LINK 22 ON-THE-AIR TEST

•Test Conducted From 6 Nov To 8 Nov 2001

•2 Radio Stations Located In Southern California

•4 Test Frequencies Available

•Link 11 Compatible Transmitters (500W – 1KW) Available At The Radio Stations


30 Sep – 2 Oct 2003


52© NILE PMO 2003


Several Variables Of The Test Environment Are Difficult To Control And The Test Results Are Non-Repeatable:

– Solar Activity

– Geometry Of The Radio Link : Terrain/Superstructure Blockages

– Relative Strength Of The Skywave And Groundwave (Multipath)

– Electromagnetic Interferences From Other Radio Transmissions And Noise Level

– Antenna/Radio Efficiency Status


30 Sep – 2 Oct 2003


53© NILE PMO 2003


• 8-Minute Test Scenario Running On The NRS SG Server

• 2 Active NUs Each Assigned 5 Minislots

• Net Cycle Time Of 1.25 Sec

• 75 Tracks Per NU


30 Sep – 2 Oct 2003


54© NILE PMO 2003


0.0

20.0

40.0

60.0

80.0

100.0

-1 0 1 2 3 4 5 6

LINK 22 MEDIA SETTING NUMBER (MSN)

PE

RC

EN

T O

F M

ES

SA

GE

S R

EC

EIV

ED

OK

: S

SC

-SD

2.2 MHz 5.4 MHz 8 MHz 12 MHz PLOMA Average

LINK 11

CLEW

LINK 11

SLEW

AVERAGE FOR SSC-SD

Freq.:


30 Sep – 2 Oct 2003


55© NILE PMO 2003

Access to NILE InformationAccess to NILE Information

NILE Nations: Contact Steering Committee Member

Non NILE Nations: Contact Program Manager

Dr. Kevin Buck

Phone: (619) 524 7718

Fax: (619) 524 7856

E-mail: [email protected]


30 Sep – 2 Oct 2003


56© NILE PMO 2003

QUESTIONSQUESTIONS??

Documents

1 © NILE PMO 2002 IDLS 2003 Newbury, UK 30 Sep – 2 Oct 2003 LINK 22 NILE Program Management Office 2 © NILE PMO 2003 LINK 22 PRESENTATION CDR Antonio