1 / 31

Kelly Sobon SSC-SD 24502 kelly.sobon@navy.mil (619) 524-7741

Dynamic Networks. Presented to IDLS 2003 30 September 2003. Kelly Sobon SSC-SD 24502 kelly.sobon@navy.mil (619) 524-7741. Agenda. Why Dynamic Network Management Link 16 Dynamic Network Management Program Network Controller Technology

jolie
Download Presentation

Kelly Sobon SSC-SD 24502 kelly.sobon@navy.mil (619) 524-7741

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dynamic Networks Presented to IDLS 2003 30 September 2003 Kelly Sobon SSC-SD 24502 kelly.sobon@navy.mil (619) 524-7741

  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

  3. Why Dynamic Network Management

  4. Why Dynamic Network Management • Network defines who can transmit when and how • Network Timeslot Allocation Fixed • Platforms cannot dynamically join • Inefficient use of existing throughput Network Design Facilities Combined Forces NDF Belgium MCTSA, Camp Pendleton, CA Marines Langley AFB, VA – AF Fort Mcpherson, Atlanta, GA JNDF NCTSI, Pt Loma Navy Redstone Arsenal, Huntsville, AL – Army • Combatant Commanders must accurately define: • Force mix • Network Requirements • Communicate changes • Network Design Facilities must rapidly develop and transmit new networks • In-Theater Network Switches (Brick) Network Designer Mission Planner F/A-18

  5. 2,000 MIDS Nations & 3rd Party Army USAF USMC 1,750 USN 1,500 Now 1,250 1,000 750 500 250 0 1 9 9 6 1 9 9 7 1 9 9 8 1 9 9 9 2 0 0 0 2 0 0 1 2 0 0 2 2 0 0 3 2 0 0 4 2 0 0 5 2 0 0 6 2 0 0 7 2 0 0 8 2 0 0 9 2 0 1 0 MIDS Third Party Potential: 7625 Link-16 Platforms Fielded Number of Link-16 platforms continues to increase Use of current static network structure will continue to degrade connectivity

  6. Operational Link-16 Link-16 in Operation Iraqi Freedom Link-16 in Operation Enduring Freedom Iraq 74 ACS MULTS X E-3 NORTH X Serbia Afghanistan TF EAGLE Link-16 in Operation Allied Force RJ/JSTARS REDCROWN E-3 CENTRE LEYTE GULF E-3 SOUTH E-2 Kosovo TRBG SNFL SNFMED FOCH TG IVN TG • Link-16 Tactical Communications • Operation Iraqi Freedom • Iraq • Operation Enduring Freedom • Afghanistan • Kosovo Campaign • Kosovo

  7. Link 16 Dynamic Network Management Program

  8. Link 16 Effective Throughput JRE eliminates the need for relay capacity Multi-Netting and Spatial Reuse Allow for non-interfering simultaneous networks Increased efficiency. (Mitigates wasted capacity) 115 KBPS Predicted, pre-allocated capacity often is unused. BLOS Connectivity requires almost half of the capacity for relay JRE, TSR/SHUMA, Multi-Nets JRE and TSR/SHUMA Dynamic Access Protocols (TSR, SHUMA) Current network architecture (Static Design, Paired Slot Relay) No one Protocol will solve all of the problems.

  9. PMW 101/159 and ONR Partnership Current Near Term Far Term • 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 Dynamic Reconfiguration of Link-16 - Address 6.2 research issues - Beyond scope of planned LINK-16 improvements - Advanced 6.2 networking technologies ONR Dynamic Reconfiguration of Link-16 Transition to PMW 101/159 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

  11. Link 16 Dynamic Network Management Network Controller Technology

  12. Link-16Network Controller Technology Network Operator Network Controller Technology Human - Computer Interaction (HCI) Technology Network Controller Capabilities - Unplanned Link-16 Platform Network Entry - Dynamic Time Slot Allocation - Multi-net Switching Link-16 Network Representation Technology Link-16 Network Management Message Interface J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ... Decision Support Technology Automation of network management decisions System Time Slot Capacity Representation Link-16 Network Monitoring Technology Link-16 Network (large terminal environment 100+ terminals)

  13. LMS-16 with Network Controller Technology Link-16 Network Controller Example Operation Current Link-16 Environment F-14 cannot communicate with other platforms New capability enables addition of "unplanned" platforms to Link-16 Unplanned F-14 Platform Additional Capabilities - Dynamic Time Slot Allocation - Multinet Switching Link-16 Network Controller Preplanned Link-16 Network

  14. Network Operator Network Controller Human - Computer Interaction (HCI) Technology Shipboard Link-16 Terminal Link-16 Network Representation Technology Link-16 Network Management Message Interface J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ... Decision Support Technology Automation of network management decisions MIDs System Time Slot Capacity Representation Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Network Monitoring Technology Link-16 Network (large terminal environment 100+ terminals) LMS-16 with Network Controller Technology Link-16 System Integration Facility (SIF) Test & Demonstration Comprehensive Link-16 Test Lab System Integration Facility SSC-SD Demonstration Network Controller Added transmit capability to LMS-16

  15. Network Operator Link-16 Terminal Link-16 Terminal Network Controller Human - Computer Interaction (HCI) Technology Link-16 Terminal Link-16 Network Representation Technology Link-16 Network Management Message Interface J.0.0, J0.1, J.0.3, J.0.4, J.0.5 ... Decision Support Technology Automation of network management decisions Link-16 Terminal Link-16 Terminal System Time Slot Capacity Representation Link-16 Network Monitoring Technology Link-16 Network (large terminal environment 100+ terminals) LMS-16 with Network Controller Technology PMW 101/159 Operational Fleet Test & Demonstration • Stennis Battle group Testing • Current plan • November 2003 • - Dynamic network control PMW 101/159 Goal: Operational Capability in FY04 Link-16 Terminal Demonstration Network Controller USS John C. Stennis

  16. Manual DNM (Phase 0 JSS):IJSS with NCT AN/GRR-43(C) Specially Instrumented Receive-Only Terminal Within the Front End System (FES) LMS-MT with Dynamic Network Controller Technology Ethernet 1553 1553 Host C2P Active TAP Dual-1553 CCD Shipboard Link-16 Terminal

  17. 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-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

  20. 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

  22. T T LOS LOS Protocol Research Protocol Objectives Link 16 Protocol Issues Link 16 • Broadcast message delivery • Best effort • Robust • Consistent • Scalable • Dynamic entry and exit • Simplified preplanning • Efficiently share channel • Throughput • Delay • Backwards compatible • Implement in all terminals • LOS propagation • Beyond LOS with relays • Wide geographic area • Transmission noise • Jamming • Mobile terminals • Dynamic topology • Dynamic connectivity Distribution of control information is challenging Impractical in large-scale networks Beyond LOS Relays Line of Sight (LOS) 960 MHz to 1215 MHz Earth curvature

  23. Link 16 Protocol Research Networking technologies applied to Link-16 Protocol Research Stochastic Unified Multiple Access (SHUMA) Protocol Technologies Link 16 "Stochastic": Random Access "Unified": Unifies Dedicated Access & Random Access "Multiple Access": n users Dedicated access protocols - Dedicated resources Dedicated Access existing access mode Distribution of control information is challenging No distributed control Local info only Random access protocols - Local control info - Stochastic processes - Examples: Ethernet CSMA/CD ALOHA Slotted ALOHA Insensitive to Topology Robust Mobile terminals Dynamic network topology Noisy channel Jamming Dynamic entry and exit • Dynamic reservation protocols • Reservation • Channel access requests • Requests coordinated and resolved • Data transmission Scalable to 100+ terminals Limited terminal processing capability Can be implemented in all terminals

  24. User n User 2 User 4 User 5 User 6 User 3 User 8 User 1 User 9 User 7 p = 1/n + (1-1/n)(1- (1-1/n)B) p p p p adaptive to load ... ... ... ... 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 ... Stochastic Unified Multiple Access (SHUMA) Protocol Local info only no distributed control p = probability of transmission Terminal Message Queues Every user can transmit on every time slot Time Slots 7.8125 msec 128 time slots/sec

  25. p = 1/n + (1-1/n)(1- (1-1/n)B) adaptive to load SHUMA Focus on SHUMA code implementation in single terminal Link-16 Terminal Heuristic Xi = 1, packet to send in ith time slot Xi = 0, no packet If 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 Host High load p = 1/n SHUMA Conformance Testing • Test & evaluate BAE & CSSA SHUMA implementations • Insure implementation according to protocol design Evaluate & Test SHUMA Protocol Mechanisms - Adaptation to "n" - Adaptation to load

  26. SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Host Host Host Host Host Host Host Host SHUMA Link 16 Network Testing RF Environment 8 real terminals TADIL-J Message Traffic Hosts Evaluate & Test SHUMA Protocol Network Operation - TADIL-J message traffic - Host interactions - Adaptation to “n” & load Network of real Link 16 terminals SHUMA operation in eight terminal environment

  27. … … … SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA SHUMA Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Link-16 Terminal Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host Host SHUMA Large Scale Link 16 Network Testing RF Environment • Environment • 100+ terminals • 100+ hosts • SHUMA protocol • Real RF transmit • TADIL-J traffic • Instrumented • Collect • performance • parameters … Real and Emulated Terminals

  28. Link 16 Dynamic Network Management Future Initiatives

  29. Multi-net Solution Random Operational Events Participant Topologies & Traffic Volume Predictive Analysis Processes Net M Net N • • • 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 2 Net 1

  30. Notional Dynamic Network HUR PPLI F/F Targeting Sensor Nets SHUMA (HUR) Multi-Net Operations C2 PPLI reporting Non-C2 to C2 PPLI reporting Air Control backlink reporting EW coordination/exchange, Engagement Status reporting SHUMA Command messages and other very stringent R/C exchanges Dedicated Surveillance track reporting Correlation TSR Different Access Modes can be allocated within single network

  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

More Related