US Navy Brieifng to HFIA

1
HF in the US Navy Update
2
Briefing Outline

• Present Battle Force Email 66 Status
• Upgrades
• 19.2Kbps Data Rates using ISB
• I.T. updates Adaptive controls
• Evolving the HF Data System (HFDS)
• IP Over HF
• Multicast Networking
• Summary

3
HF Data System in the US Navys SPAWAR
Organization
Networked RF Communications

SatCom
Littoral Communications
Digital Wideband Transmission System
HF Data System (BFEM66)
Liaison to JTRS Digital Modular Radio
4
US Navys BFEM66 Present Status

• Purpose BFEM66 provides a secure tactical
  information link with NATO and Coalition Allies
  supports non-time critical information exchanges
  at sea
• Complementing satellite based communications
  resources where cost or connectivity warrants it
• Fielding
• 187 Systems Installed Afloat as of Mar 03 with a
  target of 195 by 2004 (includes undersea assets)
• Extensive Foreign Military Sales
• (FMS) this last year with NATO/
• Coalition demand continuing to
• grow

of U.S. Ships
5
Performance Service to the Fleet
Average Data Rates
Down Time Reports
Pre-Set Modem Speeds for Shipboard Systems
lt12 SNR
12-16 SNR
14-22 SNR
gt22 SNR
If Modem SNR
MIL110B
MIL110B
MIL110B-F
MIL110B-F
With Function
4.8 Kbps
9.6Kbps
12.8Kbps
19.2Kbps
At Datarate
253K Word
12.2 minutes
10.9 Minutes
7.0 Minutes
3.0 minutes
document
259K PDF File
15.2 minutes
13.7 minutes
10.0 minutes
7.1 minutes
SNR Signal to Noise Rating on modem front
panel
Requirements
Interoperability Level
6
Battle Force Email 66 Capabilities Growth Plan
into HFDS

• Near Term Upgrade Efforts
• FY03 - FY04
• Combine Modem (RF5710A) Firmware and Installation
  Upgrade to Implement 19.2 Kbps Operation
• Move to Windows 2000 Operating System upgrade
  STANAG 5066 (to HFM3.2) Software
• JITC Test for backward compatibility and
  specification compliance prior to fielding to
  begin soon
• Combine HF Data System capabilities with a LAN
  enclave
• FY04 - FY06
• Integrate Communications Pathway Controller
  Design
• Advances capability toward hands-free operation
• Implement HF Internet Protocol Capability
  (HF-IPC)
• IRQ Chat Environment Distributed Database
  Replication
• Goal Develop Multiple Soft-link Channel Access
  Protocol (CAP) for Mesh Network with
  U.S./Allied/Coalition Forces

7
Technical Roadmap for BFEM66
Increment I
Increment II
Increment III
Border Protection Device
19.2 Kbps Modem
HFDS
Basic BFEM66
Efficient Effective Information Movement
Effective Effective Information Movement
Effective Effective Information Movement
Higher Datarates
Automatic Connectivity
Effective Effective Information Movement
STANAG 5066 (HFM 3.2) Upgrade
Modem Device Driver

• Higher Data Speed
• Software Compliance to Requirements (JITC)
• Resolve Software Obsolescence
• Software Performance

• Real-time messaging
• Open Architecture Software
• Conforming to Info. Tech. Standards (JITC)
• Goes Beyond E-Mail

• Hands-Free Controls
• Higher Data Throughput
• Transition to Network links instead of Point to
  Point

8
Resource Limited Goals within the U.S. Navys HF
Program

• Complete fielding of 200 systems towards
• meeting inventory objectives of 396 ships
• Add HFDS utility into airborne platforms pending
  Joint Staff authorizations for HFDS Program
• Automated Fault Isolation, OJT ILS enhancements
  
• Automated (hands-off) modem control operation
• Combining HFDS with non-HF Allied
  Interoperability systems to set the stage for
  JTRS interoperability in out-years

HF Data System (BFEM66) utility in an
Joint/Allied Interoperability environment will
drive the degree of authorized improvements in
the U.S. Navy
9
Summary

• HF Data (IP Based) use for allied/coalition naval
  interoperability is a recognized need
• Higher speed modems/S-5066s Comm. Pathway
  Control is increasing operational utility
• HFDS used with Military IT architectures is
  addressing the U.S. Navys needs for data speed,
  hands-free utility and HF networking
• Goals within the Navys HF programs are
  compatible with JTRS implementation

10
Backup Pages
11
RD Efforts IP Over HF/CAP

• IP client (HF-IPC) has been developed
• Assured system and component architecture via lab
  test in April, 2002
• Satisfactory three node 1st at sea field test
  Dec 02 with two reach back points via
  Satellite
• Prototype design (Increment II) software
  completed in March 2004
• Collaborated through HFIAs ICM to make the
  prototype product available on NATO C3 Agency
  website
• Multiple Softlink Channel Access Protocol (CAP)
  in development
• NC3 Agency and the ICM membership involved
• Node, platform and network requirements
  definition phase
• Edition 2 of STANAG 5066 drafted and out for
  coordination via ICM

Back