Donald Kallgren

1
HF RDTE at NC3A

• presented by
• Donald Kallgren
• Communication and Information Systems Division
• 31 70 374 3442
• don.kallgren_at_nc3a.nato.int

2
(No Transcript)
3
Agenda

• IP over HF operation
• STANAG 5066 Edition 2
• prototype/reference-system development
• JWID 2004
• US Coalition Interoperability Trial 02.10 -
  AHFWAN66
• NATO AHFWAN66
• partners

4
Evolutionary Pressures for Development of a
Second Edition of STANAG 5066

• NATO SC calls for further standardization of
  clients for end-to-end interoperability
• Vendor Developments (e.g., compressed file
  transfer)
• National calls for inclusion of specific
  capabilities (e.g., mandatory IP interface)
• Adoption by National Navies for Allied
  Interoperability in Intra-task Group Nets and
  NATO Expanded Task Force
• BiSC MOR for Wireless WAN/LAN
• BiSC MOR for Interoperable Communication System
  Architecture for Mobiles
• NATO / national calls for improved responsiveness
  (implies multiple-soft-link operation and
  enhanced media access control)
• Integration with other RF media (e.g., VHF/UHF)
• Lessons learned from operational deployments and
  vendor implementations (tweaks/clarifications)

5
Design Constraints for Future Editions

• PRESERVE interoperability in currently defined
  point-to-point and netted random-access modes
• NO CHANGE to existing STANAG 5066 PDUs
• NO CHANGE to existing STANAG Subnetwork Interface
  Primitives
• NO CHANGE to STANAG 5066 Communications Equipment
  Interface
• Implement new capabilities using
• new Engineering Order Wire (EOW) message
  definitions
• new Type-6 Management Message definitions

6
Multiple-Soft-Link ImplementationQuasi-Separable
Issues

• The following can be considered in some degree of
  isolation
• implementation of the independent ARQ-state
  machines and link-management routines for each
  soft-link
• these can be completely separated using the
  remote-node address (and, possibly, remote-client
  SAP_ID) as an index-key to access the independent
  peer-attribute-record associated with the soft
  link
• implementation of channel-/media- access controls
  that permit operation of multiple soft links
  without one interfering unduly with another
• transmit-collisions in multiple-access channel an
  issue
• solutions depend on likelihood of hidden
  terminals and any requirement to mitigate their
  detrimental effects
• for random-access-based solutions modulation of
  timing parameters as a function of the number of
  soft-links instantiated may be required

7
Multiple Soft-Link Cache of Peer-Attribute
Records (v1 -gt ICM 17)
8
Prototype Implementation
9
Rationale for Enhanced Media Access Control
Functionality in STANAG 5066

• Current Edition 1
• evolved from point-to-point requirements in
  Maritime BLOS / Broadcast, Maritime-Rear-Link,
  Ship-Shore and Applications
• has been deployed in random-access intra-task
  group environments
• has been named as a core technology in the B-SC
  MOR for Wireless WAN/LAN
• has been rejected by nations looking for this
  functionality and finding it lacking
• has been identified as a candidate core
  technology in subnetwork-relay solutions
• Proposed Edition 2
• enhanced capability for collision avoidance in
  random-access networks
• new capability for structured media access using
  token-ring controls
• focus has been on definition of
  engineering-orderwire (EOW) message catalog for
  the new functionality that is backwards
  compatible with the current broadcast, multicast,
  and point-to-point modes

10
MAC-Layer Object Functionality
11
Token Passing WTRP Operational Concepts(via
NMSU)
Net Entry
Normal
Floating
Merge Rings (executed)
Merging Rings (detected)
Merge Rings (requested)
12
Wireless Token-Ring Protocol (WTRP) Token
Design

• token implemented as a Type-6 DPDU Extended EOW
  Message
• based on the UC Berkeley WTRP IERs
• UCB-WTRP used wireless Ethernet MAC addresses (6
  bytes)
• this design uses 4-byte STANAG 5066 addresses,
  (w/ variable-length source and destination
  addresses)
• WTRP token fields
• FC - frame control
• DA - destination address
• SA - source address
• RA - ring address (I.e., address of the node that
  instantiated the ring)
• SN - sequence number
• GSN - generation sequence number

13
Wireless Token-Ring Protocol

• Head-End Token Placement

modem
crypto
WTR-Tok
DPDU(2)
DPDU(N)
Previous_node
Composition delay
modem
crypto
WTR-Tok
DPDU(2)
DPDU(N)
Current_node
Tx_delay
Slack_time gt 0

• Tail-End Token Placement

modem
crypto
WTR-Tok
DPDU(1)
DPDU(2)
Previous_node
Composition delay
modem
crypto
WTR-Tok
DPDU(1)
DPDU(2)
Current_node
Slack_time 0
Tx_delay
14
IP-client summary - via S5066 Annex F Amendment
1

• Address Mapping
• IP Multicast Address mapped to STANAG 5066
  Multicast Address, and must invoke non-ARQ
  transmission mode
• IP Unicast Address mapped to STANAG 5066 Unicast
  Address,
• ARQ / non-ARQ modes as directed by QoS/TOS-byte
  mappings
• Precedence
• mapping of 3-bit IP precedence to 4-bit 5066
  priority TBD
• Reliability
• for IP invokes ARQ mode
• Delay
• low-delay specification invokes non-ARQ
  transmission mode for STANAG 5066
• delay dont care, then can invoke either ARQ or
  non-ARQ mode
• Throughput
• mapping TBD, because of non-linear tradeoffs and
  cross-over in performance
• Proxy-management / capabilities
• needs to be standardized

15
AHFWAN66 - NATO JWID Objectives

• Provide new, technical solutions to permit and
  facilitate information sharing between coalition
  information environments
• demo emulates the NATO Maritime Communications
  Architecture
• use of a low-cost, low-bandwidth, Wide-Area
  Network for maritime coalition forces using
  optimized IP-over-HF protocols from STANAG 5066
  Edition 2, plus
• simulated SATCOM (live-SATCOM optional if NATO-IV
  capacity available), and
• simulated pier-side connections
• mobile-IP roaming

16
AHFWAN66 - US JWID Objectives

• Objective 2- (Situational Awareness)
• Prove an enhanced situation awareness capability,
  scalable in both time of delivery and spectrum of
  users, while spanning multiple information
  domains This objective will be trialed through
  the integration of the Allied HF WAN (AHFWAN66)
  consisting of 4 nodes communicating via IPv4
  over the STANAG 5066 HF Data Communications
  Profile (S'5066 Edition 2).
• Objective 3 (Database Fusion)
• prove a capability for database
  replication/fusion over low-bandwidth/high-latency
  bearer service, as an integral part of a
  full-sprectrum coalition network.
• Objective 4 ( ISR Dissemination)
• Prove a capability for ISR Dissemination over
  low-bandwidth/high-latency bearer service, as an
  integral part of a full-sprectrum coalition
  network.
• Objective 1 (Multi level security/Security
  across information domains)
• Prove a capability for affordable participation
  in a multinational /multiple-security-domain
  coalition network, through provision of an
  capable Allied HF WAN.

17
AHFWAN66 - System Description

• Provides an IPv4-over-HF network capability
  (using S5066 Edition 2)
• integrated and demonstrated within a
  full-spectrum network of high-speed SATCOM , LAN,
  and WAN bearers.
• Affords low-end coalition platforms access to
• situational awareness (COP/RMP) , logisitcs,
  command control, intelligence, and surveillance
  information within the inherent limitaitons of a
  low-bandwidth/high-latency bearer service.
• Employs performance-enhancing proxies at the
  edges of the AHFWAN66 system
• for messaging (using compressed SMTP e-mail
  direct to the HF),
• using web/database -caching and
  background-replication services,
• proxies for selected network services (e.g.,
  address-resolution, routing-update-frequency
  management and group-management services) and
• QoS management to conserve bandwidth for user
  applicaitons traffic.
• Demo with the AUSCANNZUKUS Multinational Naval
  Task Group CIT.
• AUSCANNZUKUS MNTG is the origin of ACP200 -
  Allied Communication Procedures for Maritime
  Tactical Wide-Area Networking
• NATO evaluating/adopting-in-principle ACP200
  NC3A has Tasking to review/develop requirements
  for ACP200 NATO Supplement

18
AHWAN66 OV-1

• Operational Concept
• NATO Maritime Communications Architecture
• as a deployed NATO Expanded Task Force (NETF) (w/
  IP mobility pre/ during/ post deployment)
• as an IP-based wireless wide area network
• as a mix of large-deck/small-deck platforms
• Seamless Tactical Wireless WAN connectivity
  amongst shore-based HQ and Deployed Maritime
  Forces

19
AHWAN66 SV-1

• Notional View (s)
• NATO Maritime Communications Architecture
• as a deployed NATO Expanded Task Force (NETF) (w/
  IP mobility pre/during/post deployment)
• as an IP-based wireless wide area network
• as a mix of large-deck/small-deck platforms
• Node-Edge-to-Node-Edge
  System-to-System Interfaces
• SHF SATCOM (real via NATO-IV or simulated)
• NATO In-Port Connector (100 Mbs FO-link)
• Allied HF Wide-Area-Network using S5066 Ed. 2
• High-speed HF (S4539, MS188-100B/F)
• Wireless token ring protocol
• IP-over-HF w/ performance enhancing proxies

20
Technical Overview

• System Capabilities
• Capability 1 - IPv4 over-HF service using
  STANAG 5066 Edition 2 in an Allied HF WAN
• Capability 2- IP-over-HF bearer service
  operation within a full-spectrum Multinational
  Naval Task Group Wide Area Network
• Capability 3 - performance-enhancing proxy
  operation for low-bandwidth/high-latency
  subnetworks
• Capability 4 - mobile-IP networking for tactical
  platforms with variable IP-attachment points
• Core Services
• Support to Maritime C2 Functional Area
• Basic (Document Handling, Web Browsing)
• Maritime C2 (MCCIS/ICC)
• Data Exchange(Messaging,
• Directory Services,
• Multipoints Collaboration Tools (multi-cast
  chat), whiteboard ...,
• Web Information Portal,
• File-Sharing/File-Transfer,
• Database Replication)
• Security( IP/line Encryption)
• System Management(Configuration Management)

21
Data Flows
22
JWID-2004 - At Sea Demo

• No real ships available/volunteered at present
• gt Simulated Environment
• Locations
• Deployed Maritime Forces Communications
  Architecture Tested NC3A-The Hague
• Live HF links between NC3A-The Hague and
  Staelduinen remote site
• MNTG sites accessible via the CWAN/CFBLNet

23
The Target STANAG 5066 support for Wireless
Wide-Area Networking

• Eventual support for basic data-link requirements
  for HF subnet relay using STANAG 5066 Protocols
  defined in Edition 2
• use of HF BLOS links in Wireless Wide-Area
  Network
• as backups for IP links for e-mail /
  attachments as low-speed/low-cost back-links
  in a high-speed broadcast architecture using
  asymmetric IP networking as entry-level for
  low-end coalition members
• Inclusion of VHF/UHF media at higher data rates a
  potential