Joint Tactical Radio System

1
Joint Tactical Radio System

• March, 2000
• Daniel G. Mock
• JTRS Commercial Acceptance Working Group
• Raytheon C3I / Communications Systems Division
• Fort Wayne, Indiana
• [phone]
• dmock_at_ftw.rsc.raytheon.com

2
Raytheon Consortium
3
DoD Vision for JTRS

• Develop a family of affordable, high-capacity
  tactical radios to provide both LOS and BLOS C4I
  capabilities to the warfighter.
• Interoperable, affordable, and scaleable family
  of radios shall be built upon a common open
  architecture that promotes software reuse.
• Migrate legacy systems to JTRS architecture.
• Defined by Quadrennial Defense Review (QDR), JTRS
  Mission Needs Statement (MNS), and Operational
  Requirements Document (ORD)
• See http//www.jtrs.sarda.army.mil/

4
New Capabilities Achieve Information Superiority
Today
Transmit, Receive, Bridge, and Gateway Between
Similar and Diverse Waveforms Over Multiple
Communications Media and Tactical Networks
JTRS Family

• Single Frequency
• Single Waveform
• Not Capable of Simultaneous Voice, Data, Video
• Low to Medium Data Rates
• Limited Routing, Networking, Network Management
• Can Not Automatically Adjust Performance
• Not Capable of Simultaneous Operation With Other
  Systems in Same or Other Domains
• Lacks Adequate Frequency Flexibility to Operate
  Globally

• Multi-band, Multi-mode, Secure, Non-secure
  (Voice, Video Data)
• Operate in 2 MHz to 2 GHz
• Dynamic Bandwidth Management
• Retransmit/Cross Band Between Frequency Bands and
  Waveforms
• Software Reprogrammable
• Network Between Across Geographical
  Organizational Boundaries
• Backwards Compatible With Legacy Systems

5
JTRS ORD Waveforms
FY00
FY01
FY02
FY03
FY04
UHF DAMA/DASA
VHF MSRT (v)
KPP
SATCOM (MIL-STD-
EPLRS (a, v)
188-181/182/183
Wideband Digital Waveform (a, v, d)
Compliant) (m/f, a)
SINCGARS (d)
SINCGARS SIP/ASIP ( d)
HF ISB (w/ALE)
Threshold
Link 11 (TADIL-A)
ATC HF Data Link
HCLOS
SINCGARS
HF SSB (w/ALE)
STANAG 4285 (HF)
ATC VHF Data Link
SATURN
VHF for ATC
SINCGARS SIP/ASIP
STANAG 4529
JTT/CIBS-M
DWTS
HQ I/II
VHF AM
Link4A (TADIL-C)
Cellular Radio
GPS - Commercial
INMARSAT
VHF FM Public Service
Link 11B (TADIL-B)
Link 16
UHF LOS HDR
Soldier Radio
(Land Mobile Radio)
UHF FM Public Service
VMF Translation to
UHF AM/FM PSK LOS
(Land Mobile Radio)
Link 16
UHF SATCOM (MDR)
GPS - (US Govt Encrypted)
STANAG 4231
(UHF SATCOM)
Objective
HF ISB (w/ALE)
ATC HF Data Link
Mode S Level 4
Link 11 (TADIL-A)
HF SSB (w/ALE)
ATC VHF Data Link
Link 22
STANAG 4285 (HF)
UHF LOS HDR
JTT/CIBS-M
STANAG 4529
SINCGARS SIP/ASIP
Cellular Radio
SATURN
Domain Legend a - airborne m/f -
maritime/fixed v - vehicular d - dismounted h
- handheld
Soldier Radio
HCLOS
VHF AM
VMF Translation to Link 16
VHF FM
VHF FM Public Service
MELP
(Land Mobile Radio)
PCS
UHF AM/FM PSK LOS
MSS
UHF SATCOM (MDR)
STANAG 4231
DWTS
INMARSAT
6
JTRS Program Plan

• Structured to accelerate earliest practical
  fielding - -
• Step 1 - Baseline Architecture Definition
• Three Consortia funded for Architecture Study in
  1st QTR 99
• Architecture developed by Raytheon Consortium was
  selected in June 99 as a framework for the Step
  2 effort
• Step 2 - Complete Architecture Development
• Step 2A
• Completes, implements and validates JTRS
  Architecture
• Competitive award made October 1999 to Raytheon
  Consortium
• Steps 2B and 2C
• Acquires JTRS-compliant hardware/software from
  3rd-party suppliers
• Undergoing final proposal evaluation
• Step 3 - Field JTRS-Compliant Radios Systems
• Convert Legacy Capabilities to JTRS
• Support Certify Service Procurements
• Promote Broad Industry Use

7
JTRS Step 2A Schedule
8
Step 2A Objectives

• Develop the Software Communications Architecture
  (SCA)
• Mature the Step 1 Architecture Definition
• Set a Standard SCA for Future DoD Commercial
  Radios
• Validate the SCA
• Demonstrate Industry Can Implement Compliant
  Radios
• Demonstrate Interoperability With Legacy Systems
• Permit the Earliest Practical Fielding of JTRS
  Radios
• Implement ORD Waveforms, Applications, and Crypto
• Address Critical Issues for JTRS Step 3 Success
• Obtain Widespread Industry Acceptance
• Security / MLS
• Affordability Assessment (CAIV)
• Logistics Planning

9
SCA Development Plan
Network Definition
Security Definition
SDRF meetings
CF Interface Definition
3/13
5/3
2/14
3/6
4/28
12/3
4/3
SCAS v1
1.0
1.x
0.4
0.1
0.2
0.3
11/3
SCAS v2
2.0
Use Case Analysis
Validation
10
Approach to Step 2A
11
Baseline Prototypes
12
Raytheon JTRS Validation Demonstration Model
13
Consortium Organization
Executive Management
Program Office
Consortium Management Committee
- IPRs - CAIV Mgmt. Plan - Commercial
Acceptance - CM
System Engineering IPT
Architecture IPT
Validation IPT
Prototype IPT
- SCA Specification - CCB - Support /
Rational Document -
JTRS Support Plan - MLS Plan
- Validation Plan / Procedure -
Demonstrations - Validated Architecture
- Prototypes - CF - 4 Domains -
Integrated OE - Applications - Waveforms
- Networking
14
Architecture IPT
Architecture IPT

Phil Eyermann Jim Grabill Rich Finley Dave
Olesen Raytheon ITT Rockwell
Marconi TBD M. ODonnell,
webmaster Government
Hardware ITT Jim Drohan Rockwell Alan
Erickson Marconi Dave Olesen Phil
Coralnick Racal Xetron Govt
Networking Raytheon George
Vardakas ITT John Cruz Joe
Visvader Rockwell Jim Stevens Marconi Tony
Gallo J.J. Garcia Govt
Support Raytheon Tony Thieme Alycia
Smith Rockwell Konstantinos
Katsiris Marconi John Porteous Sun Qualcomm
Govt
Security Raytheon Al Greenberg Rob
Branch Roberta Gottfried ITT
Charlie Haight Rockwell Mike Weller Marconi
Jeff Anders Consultant Lori Fritsch Sun Govt
15
JTRS Architecture Vision

• The JTRS Architecture will be a clearly defined,
  open framework
• Software
• The JTRS Operating Environment (JOE)
• POSIX-compliant operating system (OS)
• CORBA / Interface Definition Language (IDL)
• JTRS Core Framework (JCF)
• Object-Oriented Modeling / Unified Modeling
  Language (UML)
• Hardware
• Classes (Operations and Interfaces)
• Rules for Implementation
• How the Architecture is applied to products
• Result A catalog of certified HW SW
  components available for use in subsequent
  procurements

16
JTRS Architecture Framework
17
Hardware Architecture Approach

• Physical commonality across all domains is
  impossible
• Object-Oriented approach used to represent
  hardware with classes
• Accommodates single framework definition
• Framework is partitioned into classes
• Class attributes extend framework to all domains
• Behavior
• Interfaces
• Rule Set provides implementation guidance

18
JTRS Software Structure
19
JTRS Hardware Module Class Structure
20
Core Framework Development Tools Supportand
Run-Time Components
CF Development Tools
runs off-line
scenarios
manages
Creates profile
radio ops
of HW/SW properties
CF Run-Time Components
reports
installs
events / alarms
radio
sw
uses
21
Deployment View Example