HF in the USN An Update

1
HF in the USN An Update
Note Recommend Viewing as Slide-Show to
Understand Briefing Flow
2
Briefing Outline

• Battle Force Email 66
• Past Present
• Planned Improvements
• Higher Data Rates using ISB
• Automatic Data Rate Control
• IP Over HF Networking
• Completing the HF Data System
• ALE
• Network capable
• JTRS Ready

3
HF in the US Navy Communications Organizational
Hierarchy

• Battle Force E-mail use used primarily between
  U.S. and Allied/Coalition forces
• STANAG 5066 ARQ Protocol from Collins
• Half-Duplex Carrier Sense Multiple Access (CSMA)
• 19.2 Kbps MIL-STD-188-110B HF modem from Harris
• MS Exchange LAN/Email Support

4
US Navys BFEM66 Program History

• NATO Standard adopted for use 12 Nov 1999
• 2 years prior to NATO member ratification
• 1st US Navy ship installation in 22 April 2000
• Unfunded upgrade meant capability/cost trades
• Began with a bare bones support infrastructure
• By 22 Dec 00 the system had been deployed into
  4 Battlegroups/ ARGs, 6 Mine Sweepers, and 1
  Command ship
• By FY01 the US Navy had system
• installed into 8 Battlegroups/
• ARGs and 4 Command Ships
• Infrastructure support had to be
• built into the program
• Training and logistics support
• became a top priority in FY02
• POM funded in FY03 beyond

System Deployments (Cum.)
5
Current Battle Force E-Mail 66 System Diagram

• Provides inter-ship user-to-user Secure data
  transfer service using box level encryption

Shipboard HF Transmitter
Shipboard HF Receiver
Receive Audio Line
Transmit Audio Line
Black Audio Interface
Crypto
Red Multi-Circuit Patch Panel
Black Multi-Circuit Patch Panel
6
Battle Force Email 66 Capabilities Growth Plan

• Near Term Upgrade Efforts
• Combine Modem Firmware and Installation Upgrade
  to Implement 19.2 Kbps Operation
• Conduct Ground test with P-3 and Surface Ship
• Move to Windows 2000 Operating System
• Upgrade STANAG 5066 (HFM3.2) Software
• JITC Test for backward compatibility and
  interoperability prior to fielding
• Integrate Adaptive Modem datarate control
  mechanism
• Implement Interoperable Transmission Control
  Protocol (TCP)/Internet Protocol (IP) Capability
• Stretch Goals for Further Capabilities
• Develop Multiple Soft-link Channel Access
  Protocol (CAP)

• Next page has more details

7
Break-Thru Efforts IP Over HF/CAP

• IP client (middleware) has been developed
• Assured system and component architecture via lab
  test in April, 2002
• Collaborated through HFIAs ICM to make the
  freeware product available on NATO C3 Agency
  website
• Satisfactory 1st at sea field test Dec 02
• Still working on enhancements, to leverage the IP
  client as middleware service for user
  applications
• Multiple Softlink Channel Access Protocol (CAP)
  in development with NC3 Agency and the ICM
  membership
• Node, platform and network requirements
  definition phase

8
BFEM 66 within the Combined Enterprise Regional
Information Exchange System (CENTRIXS)
Present BFEM66
Future HFDS
BFEM66 BEFORE CONVERSION
Baseband and RF details not included for clarity
sake
BFEM66 Svr
MS Exch
CIC
Hub
Main Comm./Radio
BFEM66 Client
Supply Spaces
BFEM66 GW SVR
Main Comm./Radio
BFEM 66 Modem

• Isolated from LAN/WAN
• Interop. w/ NATO Allies
• 19.2 Kbps datarates

• Point to Point CDMA service
• HF E-mail

9
Further Expansions (gt FY03) to HFDS (upgraded
BFEM66)

• Integrate into Shipboard LAN as selectable
• communication pathway
• Retain BFEM computers as unit level coalition
  network
• Modify Lotus Domino software so that unit level
  ship can talk either via HF or INMARSAT depending
  on scenario/range
• Configure selected ships to relay from HF to
  INMARSAT
• Accelerate fielding of 200 systems towards
  meeting inventory objectives of 396 ships
• Multiple Softlink coupled with FY03 efforts will
  promulgate mesh network over HF
• Expand HFRG system activation
• ALE Is Supported in the HFRG ORD and in the
  requirements for JTRS
• Expeditionary Warfare Making Big Push for ALE
• LHD 4-7 Received ALE with the Now Digital URC-109
  System
• URC-131 HFRG Upgrade for ALE Has Been Scoped
• Implementation of HFDS into CENTRIXS will set the
  stage for JTRS upgrades in out-years

10
Summary

• HF use for allied/coalition naval
  interoperability is a recognized need
• Higher speed modems are increasing operational
  utility
• STANAG 5066 utility coupled with MPA community
  recognizing the need
• Breakthrough efforts in IP over HF and Multiple
  Softlink/Channel Access Protocol technologies
  have shown S-5066 has a network compatibility
• Improvements in the RF infrastructure is adaptive
  to JTRS implementation