Kelly SobonSSC-SD 24502

kelly.sobon@navy.mil(619) 524-7741

DynamicNetworks

Presented to

IDLS 200330 September 2003

2

Agenda

• Why Dynamic Network Management• Link 16 Dynamic Network Management Program

– Network Controller Technology• Joint Interface Control Officer (JICO) Support

System (JSS)– Time Slot Reallocation– Stochastic Unified Multiple Access (SHUMA) Protocol

• Future Initiatives– Dynamic Network Controller– Dynamic Multi-netting

• Summary

Why Dynamic Network Management

4

Why Dynamic Network Why Dynamic Network ManagementManagement

• Network defines who can transmit when and how

• Network Timeslot Allocation Fixed

• Platforms cannot dynamically join

• Inefficient use of existing throughput

Network Design Facilities

• Combatant Commanders must accurately define:

• Force mix• Network Requirements• Communicate changes

• Network Design Facilities must rapidly develop and transmit new networks

• In-Theater Network SwitchesNetwork Designer F/A-18

Mission Planner

(Brick)

NCTSI, Pt LomaNavy

Langley AFB, VA – AF

MCTSA, Camp Pendleton, CA Marines

Redstone Arsenal, Huntsville, AL – Army

Fort Mcpherson, Atlanta, GA JNDF

Combined Forces NDFBelgium

5

Link-16 Platforms Fielded

9966 11999977 11999988 11999999 22000000 22000011 22000022 22000033 22000044 22000055 22000066 22000077 22000088 22000099 2200110011

MIDS Nations & 3rd PartyArmyArmy USAFUSAF USMCUSMC USNUSN

250

500

750

1,000

1,250

1,500

1,750

2,000

0099

MIDS Third Party Potential: 7625

Now

Number of Link-16 platforms continues to increaseNumber of Link-16 platforms continues to increase

Use of current static network structure will continue to degrade connectivityUse of current static network structure will continue to degrade connectivity

Number of Link-16 platforms continues to increaseNumber of Link-16 platforms continues to increase

Use of current static network structure will continue to degrade connectivityUse of current static network structure will continue to degrade connectivity

6

• Link-16 Tactical Communications

– Operation Iraqi Freedom

• Iraq

– Operation Enduring Freedom

• Afghanistan

– Kosovo Campaign

• Kosovo

Operational Link-16Link-16 in

Operation Iraqi Freedom

X

Iraq

Link-16 inOperation Enduring Freedom

X

Afghanistan

MULTS

TF EAGLE

74 ACS

REDCROWN

LEYTE GULF

TRBG

FOCH TGSNFLSNFMED

IVN TG

E-3 SOUTH

RJ/JSTARS

E-2

E-3 NORTH

E-3 CENTRE

Serbia

Link-16 in Operation Allied Force

Kosovo

Link 16 Dynamic Network Management Program

8

Current network architecture (Static Design, Paired Slot Relay)

Dynamic Access Protocols (TSR, SHUMA)

JRE and TSR/SHUMA

JRE, TSR/SHUMA, Multi-Nets

115 KBPS

Link 16 Effective Throughput

Increased efficiency. (Mitigates

wasted capacity)

Predicted, pre-

allocated capacity often is unused.

BLOS Connectivity

requires almost half

of the capacity for

relay

JRE eliminatesthe need for relay capacity

No one Protocol will solve all of the problems.

Multi-Netting and

Spatial Reuse

Allow fornon-

interferingsimultaneous

networks

9

Dynamic Reconfiguration of Link-16 - Address 6.2 research issues- Beyond scope of planned LINK-16 improvements- Advanced 6.2 networking technologies

PMW 101/159 and ONR Partnership

Transition to PMW 101/159

Far TermNear TermCurrent

• 240 Navy Platforms

• LINK-16 designed in the 1970s

• 408 Navy Platforms• Increase Terminal

Throughput• Compression Algorithms -

Imagery, Data & Voice• Joint Range Extension• Satellite relay• TSR

• 1,340 Navy Platforms

• RELNAV Optimization

• Design/Implement Multi/Stacked Network

• Integrated Antenna Adaptive Beam Forming/Steering

PMW 101/159

LINK-16 Program

Office

6.2 Research Issues• Dynamic Time Slot

Allocation Management• Dynamic Network

Configuration/ Management

- Dynamic Network Participation Groups

ONR

Dynamic Reconfiguration

of Link-16

Future Naval Capabilities (FNC)

10

Components of DNM

• Network Controller Technology– NPG Augmentation

– Dynamic Entry and Egress of Platforms

– Real Time Network Monitoring

• Network Access Modes– Dedicated

– Dynamic Reservation

• TSR

– Random Access

• Contention

• SHUMA

• Multi Net Operations (MNO)

Throughput Efficiency and Flexibility

Link 16 Dynamic Network Management

Network Controller Technology

12

Network ControllerTechnology

Network Operator

Human - Computer Interaction (HCI)

Technology

Decision Support Technology

Automation of network

management decisions

Link-16 Network(large terminal environment 100+ terminals)

Link-16 Network Representation

Technology

System Time Slot Capacity

Representation

Link-16 Network Monitoring Technology

Link-16 Network

Management Message Interface

J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ...

Network Controller Capabilities

- Unplanned Link-16 Platform Network Entry- Dynamic Time Slot Allocation- Multi-net Switching

Link-16Network Controller Technology

13

Unplanned F-14 Platform

PreplannedLink-16 Network

Link-16 Network

Controller

Current Link-16 Environment F-14 cannot communicate

with other platforms

New capabilityenables addition of

"unplanned" platforms to Link-16

Additional Capabilities- Dynamic Time Slot Allocation- Multinet Switching

LMS-16 with Network Controller Technology

Link-16 Network Controller Example Operation

14

Network Controller

Network Operator

Human - Computer Interaction (HCI)

Technology

Decision Support Technology

Automation of network management decisions

Link-16 Network(large terminal environment 100+ terminals)

Link-16 Network Representation Technology

System Time Slot Capacity

Representation

Link-16 Network Monitoring Technology

Link-16 Network Management

Message Interface

J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ...

Demonstration Network

Controller

Comprehensive Link-16 Test Lab

System Integration Facility

SSC-SD

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 TerminalMIDs

Shipboard Link-16

Terminal

LMS-16 with Network Controller Technology

Added transmit capability to

LMS-16

Link-16 System Integration Facility (SIF) Test & Demonstration

15

PMW 101/159 Operational FleetTest & Demonstration

Network Controller

Network Operator

Human - Computer Interaction (HCI)

Technology

Decision Support Technology

Automation of network management decisions

Link-16 Network(large terminal environment 100+ terminals)

Link-16 Network Representation Technology

System Time Slot Capacity

Representation

Link-16 Network Monitoring Technology

Link-16 Network Management

Message Interface

J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ...

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Link-16 Terminal

Demonstration Network

Controller

Stennis Battle group Testing

- Current plan- November 2003

- Dynamic network control

Link-16 Terminal

USS John C. Stennis LMS-16 with Network Controller Technology

PMW 101/159 Goal: Operational

Capability in FY04

16

Manual DNM (Phase 0 JSS):IJSS with NCT

LMS-MT with Dynamic Network Controller Technology

AN/GRR-43(C)Specially Instrumented Receive-Only Terminal

Within the Front End System (FES)

Host C2P Active TAPDual-1553 CCD

ShipboardLink-16 Terminal

1553 1553

Ethernet

Link 16 Dynamic Network Management

Time Slot Reallocation

18

Time Slot Reallocation (TSR)

• Current USN TSR Status– Link 16 USN terminals (MIDS and JTIDS Class II)

– Interoperable with but not identical to the Joint Host Demand Algorithm

• Benefits– On Demand Capacity Redistribution

– Common Time Slot Assignments

– Allows for large number of Platforms

– Algorithms (within terminal) will redistribute time slots based on need

• Current Limitations– Requires pre-planning to determine bandwidth of TSR pool

– No reallocation of time slots to different NPGs or platform types

– Limited to two NPGs per terminal

Currently Implemented on E-2C, C2P and F/A-18Currently Implemented on E-2C, C2P and F/A-18

19

TSR Fleet Introduction

• TSR extensively tested in System Integration Facility

• Test and demonstrate TSR with STENNIS BG November 2003– NDF will be able to distribute networks with TSR on USN

Surveillance pool

• Follow-on testing required to verify performance with E-2C and F/A-18 in FY 04

• Follow-on testing required to verify correct implementation of JHDA into Common Link Integration Processing (CLIP)

PMW 101/159 Goal: Operational Capability in FY04

Link 16 Dynamic Network Management

Stochastic Unified Multiple Access (SHUMA) Protocol

21

Stochastic Unified Multiple Access (SHUMA)

• New Network Protocol Algorithm• ONR Funded through FY04• Expected to provide benefits across various

NPGs– Effort underway to identify targeted applications– Compare to Dedicated, Contention Access, and TSR

• Primarily Lab effort through FY04• Host impact study to determine scope of any

changes required

22Earth curvature

T

LOS

Line of Sight(LOS)

960 MHz to 1215 MHz

Beyond LOS Relays

T

LOS

Link 16

Distribution of control information is challenging

Impractical in large-scale networks

• Broadcast message delivery• Best effort

• LOS propagation• Beyond LOS with relays

• Wide geographic area• Transmission noise• Jamming• Mobile terminals

• Dynamic topology• Dynamic connectivity

Protocol Objectives

• Robust• Consistent• Scalable• Dynamic entry and exit• Simplified preplanning• Efficiently share channel• Throughput• Delay• Backwards compatible• Implement in all terminals

Link 16Protocol Issues

Protocol Research

23

Technologies

Dynamic reservation protocols–Reservation

»Channel access requests»Requests coordinated and resolved

–Data transmission

Dedicated access protocols - Dedicated resources

Random access protocols - Local control info - Stochastic processes - Examples: Ethernet CSMA/CD ALOHA Slotted ALOHA

Link 16

Limited terminal processing capability

Dedicated Access existing access

mode

"Stochastic": Random Access"Unified": Unifies Dedicated Access & Random Access"Multiple Access": n users

Networking technologies applied to Link-16

Distribution of control information

is challenging

No distributed control Local info only

Scalable to 100+ terminals

Dynamic entry and exit

Can be implemented in all

terminals

Mobile terminals Dynamic network

topology

Noisy channel

Jamming

Insensitive to Topology

Robust

Protocol Research

Stochastic Unified Multiple Access (SHUMA) Protocol

Link 16 Protocol Research

24

User np = probability of

transmission

TerminalMessage Queues

User 9

User 1

User 8

User 7

User 6

User 5

User 4

User 3

User 2

Every user can transmit on every

time slot...Time

Slots

128 time slots/sec7.8125 msec

...

p

p

p

p

p

p

p

p

p

p

...

p

p

p

p

p

p

p

p

p

p

...

p

p

p

p

p

p

p

p

p

p

...

p

p

p

p

p

p

p

p

p

p

Local info onlyno distributed control

p = 1/n + (1-1/n)(1- (1-1/n)B)adaptive to load

Stochastic Unified Multiple Access (SHUMA) Protocol

25

• Test & evaluate BAE & CSSA SHUMA implementations• Insure implementation according to protocol design

Link-16 Terminal

SHUMA

Host

Focus on SHUMA code implementation

in single terminal

Evaluate & Test SHUMA Protocol Mechanisms

- Adaptation to "n"- Adaptation to load

High load p = 1/n

HeuristicXi = 1, packet to send in ith time slotXi = 0, no packetIf Xi = 0, with p = 1/n increment B by 1 if < Kmax

If Xi = 1, transmit with p = 1/n or, otherwise, transmit and decrement B with p= 1-(1-1/n)B

p = 1/n + (1-1/n)(1- (1-1/n)B)adaptive to load

111

11

)( *

0

np

nn

nnj

njKE

jnjn

j

SHUMA Conformance Testing

26

Hosts

TADIL-J Message Traffic

8 real terminals

SHUMA operation in eight terminal environment

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Link-16 Terminal

SHUMA

Host

Evaluate & Test SHUMA Protocol Network Operation

- TADIL-J message traffic- Host interactions- Adaptation to “n” & load

Network of real Link 16 terminals

RF Environment

SHUMA Link 16 Network Testing

27

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

…

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

…

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

Link-16

Terminal

SHUMA

Host

…

…

RF EnvironmentEnvironment

- 100+ terminals- 100+ hosts- SHUMA protocol- Real RF transmit- TADIL-J traffic

- Instrumented- Collect performance parameters

Real and Emulated Terminals

SHUMA Large Scale Link 16 Network Testing

Link 16 Dynamic Network Management

Future Initiatives

29

Multi-net Solution

Random OperationalEvents

Participant Topologies& Traffic Volume

•Demonstrate J0.3 multi-capability•Create representative data sets test

•Sensor to Weapon (WDL, MST)•Demonstrate Manual Capability•Develop automated capability based on representative data sets / topologies

Net 1

Net 2

Net N

••

Net M

Predictive Analysis Processes

30

Notional Dynamic Network

Commandmessagesand other

very stringent

R/C exchangesDedicated

HUR PPLIF/F TargetingSensor Nets

SHUMA (HUR)C2 PPLI reportingNon-C2 to C2 PPLI reporting

Air Control backlink reportingEW coordination/exchange,

Engagement Status reportingSHUMA

Surveillance track reportingCorrelation

TSR

Different Access Modes can be allocated within single network

Multi-Net Operations

31

Summary

• DNM (NCT, SHUMA, TSR) technology development and test underway

• PMW 101/159 Goal: Initial Operational Capability of TSR and NCT in FY 04

• Coordination with Joint and Allied Services is essential– Acceptance– Leverage existing capabilities

No one technology or protocol is the solution to Link 16 DNM