HF in the USN – An Update - HFIA

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 ReadyPage 2HFIA 16 Jan ’03 (JLM)

HF in the US Navy CommunicationsOrganizational HierarchyNetworked RF CommunicationsSatComLittoral CommunicationsFielding Status:t150 Systems* InstalledAfloat as of Dec ‘02Target is 168 by 1 Oct.‣FY03 – 18 SystemsForeign Military Sales(FMS) Case SystemsExpanding‣ i.e. Australia,Germany, SpainNote: Interoperates with 85+ Allied shipsfrom 11 Nations (4 PAC, 7 LANT) whichwere acquired directly (Non-FMS)Digital Wideband Transmission SystemHF Data System (BFEM66)JTRS & Digital Modular Radio* Battle Force E-mail use used primarily betweenU.S. and Allied/Coalition forces– STANAG 5066 ARQ Protocol from Collins‣ Half-Duplex Carrier Sense MultipleAccess (CSMA)– 19.2 Kbps MIL-STD-188-110B HF modemfrom Harris– MS Exchange LAN/Email SupportPage 3HFIA 16 Jan ’03 (JLM)

US Navy’s BFEM66 Program History NATO Standard adopted for use 12 Nov 1999– 2 years prior to NATO member ratification 1 st 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 4Battlegroups/ ARGs, 6 Mine Sweepers, and 1 Command shipBy FY’01 the US Navy had system25installed into 8 Battlegroups/20ARGs and 4 Command Ships– Infrastructure support had to be 15built into the programTraining and logistics supportbecame a top priority in FY’025System Deployments (Cum.)Mine Sweepers10 Command ShipsUS BG/ARGs POM funded in FY’03 & beyond 0 FY'00 FY'01 FY'02Page 4HFIA 16 Jan ’03 (JLM)

Current Battle Force E-Mail 66System DiagramProvides inter-ship user-to-user Secure datatransfer service using box level encryptionBattle Force Email 66 SystemEthernet LANShipboardHF ReceiverShipboardHFTransmitterClient PCMS-ExchangeMail ServerAnd Client PCBattle Force Email 66 ServerReceiveAudio LineTransmitAudioBlack Audio Interface Line10/100 HUB High Speed HFCryptoModemRed Multi-CircuitPatch PanelBlack Multi-CircuitPatch PanelPage 5HFIA 16 Jan ’03 (JLM)

Battle Force Email 66 CapabilitiesGrowth Plan Near Term Upgrade Efforts:– Combine Modem Firmware and Installation Upgrade toImplement 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 priorto 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 detailsPage 6HFIA 16 Jan ’03 (JLM)

Break-Thru Efforts: IP Over HF/CAP IP client (middleware) has been developed– Assured system and component architecture vialab test t in April, 2002‣ Collaborated through HFIA’s ICM to make thefreeware product available on NATO C3 Agencywebsite– Satisfactory 1 st “at sea” field test – Dec ‘02– Still working on enhancements, to leverage the IPclient as middleware service for user applications Multiple Softlink Channel Access Protocol(CAP) in development with NC3 Agency andthe ICM membership– Node, platform and network requirementsdefinition phasePage 7HFIA 16 Jan ’03 (JLM)

ProNET CNX 600RNGOTXRX ABFDDIFAULTSYSTEMUPTXRXCPPORT1 0ETHERNETDUAL0123CPRXUPTXETHERNETQUADRNGOTXRX ABFDIBFEM 66 within the Combined Enterprise RegionalInformation Exchange System (CENTRIXS)Present BFEM66BFEM66 BEFORE CONVERSIONBaseband and RF details not included for clarity sakeBFEM66 SvrMS ExchCIC:BFEM66 ClientSupply SpacesBFEM66 GW SVRMain Comm./RadioHubMain Comm./RadioBFEM 66 ModemIsolated from LAN/WANInterop. t w/ NATO Allies19.2 Kbps dataratesPoint to PointCDMA serviceHF E-mailFuture HFDSCENTRIX Block 0 Increment I (Increment II)DOMINO ServerGOT-D 4.1.1.2 W/SMain Comm/Radio5 Client workstationsPDC, DNS, IIS Svr,GOTS-D 4.1.1.2 SvrSametime Chat ClientCIC10Port HubMain Comm / RadioBDC, DNS, IIS Svr,GOTS-D 4.1.1.2 SvrSametime Chat ClientTactical Space (TBD)BFEM66 GW SVRSametime Chat ClientMain Comm/RadioPage 8Red Patch PanelAllied Crypto(KG-84/KIV7)SATCOMWOABADNS RackProteon RouterMain Comm/RadioCoalition INETACLANE KG175Main Comm/RadioCisco 2611 RTRMain Comm/RadioGOT-D 4.1.1.2BFEM 66 WorkstationCICTempest HubMain Comm/RadioBlack Patch PanelHF ModemTransmitter/ReceiverSwitchboardsTransmitterReceiverHFIntegrated LAN/WAN Interop. w/ NATO AlliesHigh h Speed HF E-19.2Kbps dataratestmail, IP, Chat, etc. (see Adaptive baud ratenext slide)Point to Multi-point(stretch goal)HFIA 16 Jan ’03 (JLM)

Further Expansions (> FY’03) toHFDS (upgraded BFEM66)Integrate into Shipboard LAN as selectablecommunication pathway– Retain BFEM computers as unit level coalition network– Modify Lotus Domino software so that unit level l ship can talkeither via HF or INMARSAT depending on scenario/range– Configure selected ships to relay from HF to INMARSATAccelerate fielding of 200 systems towards meetinginventory objectives of 396 ships– Multiple Softlink coupled with FY’03 efforts will promulgate“mesh network” over HFExpand HFRG system activation– ALE Is Supported in the HFRG ORD and in the requirementsfor 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 ScopedImplementation of HFDS into CENTRIXS will set the stage forJTRS upgrades in out-yearsPage 9HFIA 16 Jan ’03 (JLM)

Summary HF use for allied/coalition navalinteroperability is a recognized need Higher speed modems are increasingoperational utility STANAG 5066 utility coupled with MPAcommunity recognizing g the need– Breakthrough efforts in IP over HF and MultipleSoftlink/Channel Access Protocol technologieshave shown S-5066 has a network compatibility Improvements in the RF infrastructure isadaptive to JTRS implementationtiPage 10HFIA 16 Jan ’03 (JLM)