Title: HF Industry Association HFIA meeting
1HF Industry Association (HFIA) meeting
- 22 June 2000
- Washington, DC
2Outline
- Link 22 Background
- Link 22 Overview
- Nile Project Organization
- Design and Development Schedule
- Link 22 System Architecture
- Performance Requirements
- Potential Media improvement
- Link 22 Comparison with Link 11
- Link 22 Comparison with Link 16
- Compatibility Testing
- NRS / Media Simulator capability
- Interoperability Testing
- In-Service Support Phase
3Link 22 Background
- Multi-National Program
- Canada, France, Germany, Italy, Netherlands, UK
and US (Host Nation) - Responsibility
- Steering Committee - NILE Nations
- ? Ensure Provisions of MOU are Met Guide PM
Evaluate Project Status Approve Budgetary
Proposals Resolve National Disclosure Policy
Issues Endorse Release of RFP, Contracts and
Amendments to Contracts - Program Management Office (PMO) Space and Naval
Warfare Systems Command (PMW 159E) - Manage Project Resources Ensure successful
Completion of Phased Activity Oversee Contracted
Activity Interface with Contracting Officer
Liaise with NATO Agencies
4Link 22 Background
- Phases
- 1989/92 Project Development Phase
- ? Established Media, Message Standard,and OSI
Requirements - 1992/96 Design and Development Phase One
- ? Developed Link 22 System and Sub-System
Specifications and Nile Reference System
Requirements - 1996/01 Design and Development Phase Two
- ? Contract Award Logicon DataMat, ViaSat, Sema
Group and DataSciences - ? Develop SNC Software, NRS (Compatibility
Tester) and MLTT(Interoperability Tester) - 2001/11 In-Service Support Phase (Pending)
5NILE PROJECT ORGANIZATION
Steering Committee
- Development teams
- LOGICON (US) Prime gt NRS SG
- DATA SCIENCES (UK) gt SNC CT function
- DATAMAT (IT) gt SNC MF function
- VIASAT (US) gt NRS MS HW
- SEMA GROUP (FR) gt QA, CM, Test activities
Procurement NILE System Network Controller (SNC)
NILE Reference System (NRS) Options for
production NILE Multi Link Test Tool (MLTT)
PMO
LOGICON
SEMA
ViaSat
Data Sciences
Datamat
6DESIGN DEVELOPMENT SCHEDULE
7Link 22 Background
- NATO Improved Link Eleven (NILE) Conceived to
Ameliorate Several Major Deficiencies in Link
Eleven - Lack of Electronic Protection Measures
- Insufficient Capacity in Terms of Tactical
Message Throughput - Insufficient Robustness
- Insufficient Error Detection and Correction
- Inflexible and Slow Data Link Procedures
8Link 22 Background
- Program Requirements
- Operational NATO Staff Requirement, Revised Mar
90 - System, Functional and Performance NATO
Elementary Requirements Document 12 December 94 - Program Goals
- Replace Link 11 (Eventually)
- Complement Link 16
- Improve Allied Interoperability
- Enhance Commanders War-fighting Capability
9Link 22 Background
- Development Approach
- Integrate Existing Link 11 Modems, Radios and
Ancillary Equipment to Fulfill Fixed Frequency
Media Requirements - Use Commercial Off The Shelf Computers as Host
and Target Platforms - Use Existing Encryption Engine (CTIC-DS101
Hybrid) to Provide COMSEC Protection - Emphasis is on System Design and Architecture
Versus Hardware Implementation - COMSEC Devices to be Procured via Foreign
Military Sales - Integration, Production and Implementation of
Link 22 is Nations Responsibility
10Link 22 Background
- Some Link 22 Features are
- EPM Resistance to Jamming and Deception
- Improved Communications and Transmission Security
- Increased Network Capacity in Terms of
Participating Units and Tactical Data Throughput - Automated Network Management to Provide Greater
Flexibility and a Priority Interrupt Transmission
Capability - Gapless Range Coverage HF to 300 nm Extendible
to 1000nm UHF to LOS Extendible to 300 nm - Increased System Availability (TDMA)
- Facilitate Data Forwarding
11Link 22 Overview
- Interconnect Air, Surface, Subsurface and Ground
Based Tactical Data Systems to Support - Tactical Picture Compilation
- Weapon Engagement and Status Management
- Command and Control
- Link 22 Associated Environmental Requirements
- Blue Water Confined Water and Coastal Scenarios
- All Latitudes
- Range Coverage up to 1000 nm
- Normal and Jammed Channel Conditions
12Link 22 Overview
- OPTASKLINK Message Critical to Setup and
Operation of Link 22. Defines - NILE Unit (NU) Information Name, Platform Type,
L22 Address, NU Role, Capacity Need, Access
Delay, Network Membership, Mode of Operation - Network Information Crypto Parameters, Crypto
Day, DTDMA Enabled/Disabled, Initialization
Method, Operational Start/Stop Time - Media Information Media Type, Crypto Integrity,
Frequency, Hop Set, Media Setting Number - Network Cycle Structure Media Fragmentation
Rate, Number of Time Slots, Time Slot Size, Time
Slot Ownership
13Link 22 Overview
- Time Division Multiple Access (TDMA)
- All NILE Units or NUs are pre-assigned Time Slots
- Interrupt Slot Available for Injection of High
Priority Messages - Time Slots or Portions thereof Dynamically
Exchanged or Modified
14Link 22 Overview
- Up to Four (4) Link 22 Networks Operate
Concurrently - Each on a Different Fixed Frequency
- Each Hopping on Predetermined Frequencies (Pseudo
Random Pattern)
NU12
NU1
NU7
NU17
NU8
NU18
NU5
NU7
NN1 - HF
NN3 - HF
NU9
NU3
NU16
Interrupt Slot
IS
NU2
NU6
NU9
NU17
NU12
NU6
NU16
IS
NU17
NU24
NU10
NU2
NU20
NN2 - HF
NN4 - UHF
NU9
NU11
NU19
NU9
NU13
NU15
NU14
NU15
NU 23
NU21
15Link 22 Overview
- Up to Thirty Two (32) Mission Area Sub Networks
May be Established - According to Operational Mission and Capabilities
- To Effect a Better Usage of Available Resources
NILE NETWORK 2
MASN 1
SUPER NETWORK
MASN 2
NILE NETWORK 1
NILE NETWORK 3
MASN 3
16Link 22 Overview
- Roles Designated to NILE Units (NU)
- Super Network Management Unit (SNMU) and Standby
- Network Management Unit (NMU) and Standbys
- Relay Units
- Modes of Operation
- Radio Silence
- Receive Only
- Active NU
17Link 22 Overview
- Relay Routing Used to Extend Range and Reach
Units BLOS
RELAY
RELAY
RELAY
RELAYERS SELECTED ON BASIS OF CONNECTIVITY
18Link 22 Overview
- Late Network Entry (LNE) Protocol
SNMU
NU4
NU6
NU3
NU5
NU8
NU1
NU2
LNE SLOT
NU7
Supporting Unit
LNE Unit (NU 9)
SNMU
NU9
NU6
NU4
NU5
NU3
NU1
NU2
NU8
NU7
19Link 22 Overview
- Tactical Messages Executed on Basis of Attributes
- Message Priority (1 4)
- Address Type (Machine Receipt and Non-Machine
Receipt) - Single NU Point to Point
- Broadcast
- Mission Area Sub Network (MASN)
- Dynamic List (2 5 NUs)
- Reliability
- Priority Injection
- Perishable Message Indicator
- NILE Address of Originator
20Link 22 Overview
- Message Standard
- Fixed Format Tactical Messages Link 16 Derived
- Independent
- Consist of Multiple 72 Bit Data Words (1 to 8)
- Data Words Are Dependent
- Link 16 Data Element Dictionary
- Tactical Messages Report Following Information
- Participant Location Information (PLI)
Surveillance Electronic Warfare (Reporting,
Coordinating and Emergency) Intelligence
Information Management Threat Warning Weapons
Coordination and Management External Network
Management.
21Link 22 System Architecture
Link 22
NCE
Radio
SPC
Radio
SPC
TDS
LLC
SNC
DLP
Radio
SPC
Radio
SPC
NRS
National development
National development
22Link 22 System Architecture
- Data Link Processing (DLP)
- Interfaces with National TDS (CCS or CDS)
- Services Tactical Data (STANAG 5522)
- Formats/Generates Tactical Messages Appends
Necessary Attributes to Tactical Data Transmits
and Receives Data per Rules Provide Tactical
Updates Perform Correlation and R2 - Data Forwards to Other TADILS (STANAG 5616)
- Interfaces with the System Network Controller
23Link 22 System Architecture
- System Network Controller (SNC)
- Provides Message Delivery Service via
Communications Transport function - Message Delivery, End to End Delivery, Leg
Delivery, Network Injection - Provides SN, NN and NU Management Capabilities
via Management Function - Generates Technical Messages
- Performs Configuration Management Performance
Monitoring Security Management and Fault
Management
24Link 22 System Architecture
- System Network Controller (SNC)
- Performs Dynamic TDMA and Relay Routing
- Interfaces DLP, SNC and Time of Day Source
- Portable to standard COTS hardware
- PC / Station
- Windows NT / HP-UX / Solaris
25Link 22 System Architecture
- Link Level Communications Security (LLC)
- Network Security (NETSEC) is Provided by a
Cryptographic Device (LLC) - Time Of Day and User Address Encryption
- Data Integrity Verification
- Thornton Algorithm
- Transmission Security (TRANSEC) is Provided by
Frequency Hopping Radios
26Link 22 System Architecture
- Signal Processing Controller
- Perform Modulation and Demodulation Functions
- Performs Error Detection and Correction
- Transmits/Receives Data
- HF FF _at_ 1200 to 3600 bps
- HF EPM _at_ 1200 to 3600 bps
- UHF FF _at_ 16 kbps
- UHF EPM _at_ 16 kbps
27Link 22 System Architecture
- Signal Processing Controller
- HF FF 18 Waveforms QPSK/8PSK, RS Coding
- UHF FF 3 Waveforms, 16 Kbps NRZ FM, RS (96,76)
- HF EPM 4 Waveforms, QPSK, Dual RS Coding
- UHF EPM 4 Waveforms, 16 Kbps NRZ FM, Convol. 1/2
28Performance Requirements
- LINK 22 SYSTEM
- Addresses up to 125 units (NU) 4 Networks
- NCS(2 to 19 NUs) 10 sec (20 to 40 NUs) 20 sec
1024 MS (max) - Priority response time 2.5 sec
- Probability Correct Message Reception 80, 90,
100 - UMER 10-4
- Throughput HF FF/FH 36/26 (12/6) UHF FF/FH
130/ 116(120/90) words/sec - Range HF 300 to 1000 nm UHF 200 to 300 nm
- 95 Relay over 3 legs
29Performance Requirements
- LINK 22 SYSTEM (CONTINUED)
- 70 to 75 Traffic Routine Updates
- 90 Traffic RF Broadcast
- 1 Traffic High Reliability
- 1 Traffic - Interrupt Slot
- 10 Traffic - Priority One
- TOD accuracy 0.5 msec.
- FF BER goal 5 min 3
- FH Blocked Channels goal 50 min 30
30Performance Requirements
- DATA LINK PROCESSOR (DLP)
- Generate 50 Transmission Service Requests per
second - Variable processing time required to generate 50
(72) bit words - Extrapolates data to time of injection (MTV)
- 4 Priority Levels
- Addressing PTP, RF Neighbor, Totalcast, Dynamic
List, MASN - Perishability 15, 31, 63, 511 seconds
- 15 bit Addressing
31Performance Requirements
- SYSTEM NETWORK CONTROLLER
- TDMA HFFF (4 - 16 MS) HFFH (4 -32 MS) UHF
FF/FH (4 - 32 MS) - Process 300 TSR each 8 (72 bit) words long
- Pass single pair of duplicate messages out of
1000 messages - Technical messages do not exceed 10 traffic
- Errors lt1/1000 msg MR, GD, originator Id,
delineation, MTV, reassembled - NP Processing 4 NPs per 25 msec.
32Performance Requirements
- LINK LEVEL COMSEC
- Supports 3 HF 1UHF medium concurrently
- Process (UHF (20.18) HF (38.33)) 45.17 NPs per
sec. - Two byte Integrity Checksum
- Max encryption and decryption latency 13.1 and
15.8 ms - TOD Data Encrypt/Decrypt
- Supports Data Transfer Rates 4800 bps to 115.2
Kbps - Supports 64 Traffic Encryption Keys (TEK)
33Performance Requirements
- SIGNAL PROCESSING CONTROLLER
- Data Rates HF 1200 to 3600 bps UHF 2400 to
10000 bps - HFFF MCF 270 sym GT 67 sym PR 203 sym
- UHF FF MCF 607 bits PR 255 bits GT 161 bits
Tx GT 352 bits - HF EPM MCF 270 sym HTT/AGC/IT 92 sym GT 60 sym
- RADIOS (EXISTING)
- HF (2 -30 MHz) UHF (224-400 MHz)
34Media Status
- HF FF Medium
- SPC SS (NILE WP35)
- Draft STANAG 4539 .......Pending
- Including NILE WP35
- UHF FF Medium
- SPC SS (NILE WP36)
- UHF EPM Medium
- STANAG 4372 Chap IV (Link22)... Updated
- SPC SS...Updated
- STANAG (Ed 4)....... Ratification
Process Y00-01 - HF EPM Medium
- STANAG 4444 ..Ratification Process
- Including NILE Requirements / TSD
35Potential Media Improvement
- New HF Waveforms
- Improved Throughput under Good Propagation
Conditions (More than three (3) times the current
number of messages for the same Minislot
Duration) - (Reference Feasibility of Higher Link 22
Throughput by Using a waveform that is Similar to
STANAG 5066, Annex G. GAC Presentation ULM, GE
December 98) - Use of 8 PSK 16, 32 and 64 QAM Modulation with
RS Coding - Under Consideration for Implementation during In
Service Support Phase of the Link 22 Program
36Link 22 Comparison With Link 11
- Similarities
- Operate in Both HF and UHF Fixed Frequency Modes
- Utilize Single Tone Waveforms
37Link 22 Comparison With Link 11
- Differences
- Provides Jam Resistance by Operating in EPM Mode
in HF and UHF - Operator Selectable Waveforms Used to Optimize RF
Channel Conditions - Provides Beyond Line of Sight Coverage
- Provides Improved Security Through Encryption of
Both Tactical and Management Messages - Increased Throughput and Granularity of
Information Exchange - Improved Network Access through TDMA Architecture
and Interrupt Slots
38Link 22 Comparison With Link 11
- Differences(Continued)
- Messages can be Prioritized and Addressed to
Specific Units - Truly Nodeless With No Dependency on Net
Controller Station - Employs Concurrent Multiple Networks (Four) and
Mission Area Networks (32) - Hosts Larger Number of Participants (125), Five
Character Alphanumeric Track Number, and Higher
Track Quality - Low Probability of Intercept Features Tx Power
Control, Radio Silence, Data Integrity
Verification - Efficient Message Standard
- Facility to Perform Relay Routing
39Link 22 Comparison With Link 16
- Similarities
- Jam Resistant - Employs Frequency Hopping
- Improved Security - Encryption of Network Control
Messages - Increased Granularity of Information
- Message Standard Permits Exchange of J-Series
Data Elements - Increased Availability via Time Division Multiple
Access (TDMA) Protocol - Operation Over Multiple Networks (8 NN 32 MASNs)
40Link 22 Comparison With Link 16
- Similarities(Continued)
- Two Levels of Security NETSEC/TRANSEC
- Mission Area Sub Networks Support Multiple L16
Network Participation Groups - Common Track Numbering Scheme 19 Bit with Two
(2) Alphanumeric and Three (3) Octal Numbers - Supports Data Forwarding (L11/L16/L22)
- Transmission of Participant Location and
Identification (PLI)
41Link 22 Comparison With Link 16
- Differences
- L22 Provides Connectivity Using an Improved HF
and UHF Frequency Diversity Transmission Scheme - L22 Performs Connectivity in both Fixed Frequency
Frequency Hopping Modes of Operation - L22 Provides Beyond Line of Sight (BLOS) Coverage
without the use of Relays in HF - Relay via Multi-Netting Provides BLOS in UHF
- Performs Permanent and Temporary Timeslot
Re-allocation Dynamically in TDMA (ATOC, PTOC,
HO, SWAP)
42Link 22 Comparison With Link 16
- Differences (Continued)
- L22 is Truly Nodeless, in that, it does not rely
or Depend on a Network Time Reference (NTR) - Multi-Media, Multi-waveform Selection
- Tactical Message Independence
- Interrupt Slots to Report High Priority Messages
- Low Probability of Intercept Features Tx Power
Control, Radio Silence, Data Integrity
Verification
43Compatibility Interoperability Testing
OPERATIONAL EFECTIVENESS
INTEROPERABILITY
TECHNICAL DATA EXCHANGE
COMPATIBILITY
MEDIA SIMULATOR
TDS
TDS
DLP
DLP
SNC/LLC
LLC/SNC
STANAG 5522 DATA ELEMENTS
TACTICAL DATA EXCHANGE
44Compatibility Testing
45Compatibility Testing
- NILE Reference System (NRS) Used to Perform
- SNC Verification Testing Assesses Performance
against System Requirement Specifications and
Interface Requirement Specifications - Remote Compatibility Testing Assesses Performance
against System Specifications - System Simulation Assesses Performance of Four
(4) Link 22 Networks Comprising 125 NUs - Multiple Unit Testing of up to Five Link 22
Units, each made of an SNC integrated with a LLC
46Compatibility Testing
- Common Test Tool and Reference Test Scenarios
(RTSs) - Over 40 RTSs Available to Validate Protocols
- RTSs have Associated Outcomes, Expected Responses
and Results - Mostly Deterministic and Repeatable
- Limited to SNC Compatibility Testing
- Verify Interfaces Are Implemented IAW
Specifications - Perform Tests
- Test Unit Remotely Located
- Test Unit Physically Separated in excess of 500
47Media Simulator Capability
- The Media Simulator can
- Simulate up to 4 Independent Channels
- Simulate Connectivity Effects of Platform Motion
- Simulate Varying Propagation Losses/Conditions
- Simulate LLC SPC Interface
- Simulate Message Error Rate Statistic for Each
NU Pair
48Media Simulator Capability (continued)
- MS and MS? Control
- LLC Management
- RF Channel Simulation
- SPC Management
- Interfaces with SG, SNC ?, LLC UUT, TOD
49Media Simulator Capability (continued)
- RF Channel Simulation
- Manages the Propagation Loss Calculations (PLC),
Bit Error Rate (BER) Calculations and Link
Reception Quality (LRQ) Determination for the RF
Channel Simulation and Provides NU Connectivity
Snapshot. - SPC Management
- Maintains State Machine Functions for each SPC
- Processes SPC/LLC Messages
- Performs Collision Detection Evaluation
- External Time Source
- Master-Slave Digital Clock card (PCI bus card)
distributing Standard Time Message (STM) and 1PPS
over RS-422. - TOD, TFOM, Leap Indicators
50Interoperability Testing
51Interoperability Testing
- Multi-Link Test Tool Used
- Remotely Test Link 22 Units Via the Internet
- Remotely/Locally Support System Integration
Testing (SIT) of a Host/DLP, SNC, LLC, SPC and
Radio - Land Based Test of Link 22 Systems Conformance
to STANAG 5522, when Actual LLC Devices, SPCs and
Radios Are Interconnected - Support Testing With Live Platforms
52Link 22 Program Test Status
- SG and MS CSCI Dry Run and Qualification Testing
Completed - SNC Dry Run Testing Currently Underway at Datamat
in Rome, Italy - SNC CSCI Qualification Testing Scheduled for mid
July 00 - NRS System Qualification Testing Scheduled for
August 00 - SNC System Qualification Testing Scheduled for
August 00
53In-Service Support Phase
- Memorandum of Understanding Presently Under
Negotiation by the Current NILE Nations - Scope of Work Consists Of
- Software Maintenance
- Configuration Management
- System Testbed
- Technical/Operational Data Exchange
- Annual Budget Estimated at 1,750,000
- PMO to Be Staffed With a PM and 2 National
Representatives