Atch_1_Draft_STC_HH_Specification_1_APR_14.docx
DOCX document 249 KB Posted
- Solicitation number
- H92222-14-R-0017
- Issued by
-
United States Special Operations Command
About this file
Performance Specification Draft
View the file
Other files
Show all 33
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Performance Specification Draft for Comment
PERFORMANCE SPECIFICATION
UNITED STATES SPECIAL OPERATIONS COMMAND
(USSOCOM)
SPECIAL OPERATIONS FORCES (SOF) TACTICAL COMMUNICATIONS
(STC)
for the Handheld Device
Prepared for:
Mr Arthur D. Coon
USSOCOM, SORDAC-PEO-C4-STC
7701 Tampa Point Boulevard MacDill AFB, FL 33621-5323 Submission Date: XX XXX 2013
01 April 2014
| SUBMITTED BY: _____________________ | DATE: XX XXXX XXXX | ||
| Mr. Arthur D. Coon | |||
| STC Deputy Program Manager | |||
| SORDAC-PEO-C4-STC |
| APPROVED FOR USE AS A | ||
| FUNCTIONAL BASELINE BY: ______________________ | DATE: XX XXXX XXXX | |
| Mr. Anthony J. Davis | ||
| PEO C4 | ||
| SORDAC-PEO-C4 |
UNCLASSIFIED
UNCLASSIFIED
This page intentionally left blank.
Table of Contents
| 1.0 | INTRODUCTION | 1 |
| 1.1 | Scope | 1 |
| 1.2 | Background | 1 |
| 1.2.1 | Handheld (HH) Device | 1 |
| 1.3 | Threat | 1 |
| 2.0 | APPLICABLE DOCUMENTS | 2 |
| 2.1 | Government Documents | 2 |
| 2.1.1 | Specifications, Standards, and Handbooks. | 2 |
| 2.1.2 | National Security Agency (NSA) Regulations and Specifications | 4 |
| 2.1.3 | Department of Defense (DOD). | 4 |
| 2.1.4 | Other Government Documents, Drawings, and Publications. | 4 |
| 2.2 | Industry Standards | 5 |
| 2.2.1 | American National Standards Institute (ANSI). | 5 |
| 2.2.2 | Institute of Electrical and Electronic Engineers (IEEE). | 6 |
| 2.3 | Order of Precedence | 6 |
| 3.0 | SYSTEM REQUIREMENTS | 6 |
| 3.1 | STC HH Description | 6 |
| 3.1.1 | HH System Components | 6 |
| 3.1.2 | Universal Accessories | 7 |
| 3.2 | STC HH Architecture | 7 |
| 3.2.1 | Software Communications Architecture (SCA) | 7 |
| 3.2.2 | Hardware Architecture | 7 |
| 3.2.3 | Android Interface | 7 |
| 3.3 | Channel Types | 8 |
| 3.3.1 | Channel Configuration and Definition | 8 |
| 3.3.2 | Guard Channels | 8 |
| 3.3.3 | Channel Scanning | 9 |
| 3.4 | Multifunctional Capabilities: | 9 |
| 3.4.1 | Situational Awareness (SA) | 10 |
| 3.4.2 | Signals Based Threat Warning / Situational Awareness (SBTW/SA) | 10 |
| 3.4.3 | ISR Video Receive Capability / Interoperability | 11 |
| 3.4.4 | Intelligence, Surveillance & Reconnaissance (ISR) | 12 |
| 3.4.5 | Simultaneous Channel Operation | 12 |
| 3.5 | Communications Range | 12 |
| 3.5.1 | HH Range | 12 |
| 3.6 | Interoperability | 12 |
| 3.6.1 | Legacy Devices | 12 |
| 3.7 | Mobile Ad Hoc Networking (MANET) Waveforms | 13 |
| 3.7.1 | General Characteristics | 13 |
| 3.7.2 | Soldier Radio Waveform (SRW) | 13 |
| 3.7.3 | Wideband Networking Waveform (WNW) | 13 |
| 3.7.4 | Commercial and Proprietary Waveforms | 13 |
| 3.7.5 | Encryption | 15 |
| 3.7.6 | Mobility | 16 |
| 3.7.7 | Operate as Standalone or Member Device | 16 |
| 3.7.8 | Network Management | 16 |
| 3.8 | Waveform Requirements | 17 |
| 3.8.1 | Waveform Selection | 17 |
| 3.8.2 | Retransmission and Routing | 18 |
| 3.8.3 | Waveform Storage | 18 |
| 3.8.4 | Additional Waveforms | 19 |
| 3.9 | Global Positioning System (GPS) | 20 |
| 3.9.1 | Internal GPS Receiver | 20 |
| 3.9.2 | External GPS Receiver | 20 |
| 3.10 | Voice Operations | 20 |
| 3.10.1 | Voice Activation | 20 |
| 3.10.2 | Listening Silence | 20 |
| 3.11 | Information Security (INFOSEC) | 21 |
| 3.11.1 | Classification Levels | 21 |
| 3.12 | Cryptographic Requirements. | 21 |
| 3.12.1 | General | 21 |
| 3.12.2 | Key Management | 22 |
| 3.12.3 | Key Retention | 22 |
| 3.12.4 | Handling and Storage | 22 |
| 3.12.5 | Radio / Cryptographic Zero Function | 23 |
| 3.12.6 | Equipment Level Security Requirements | 23 |
| 3.13 | Power-On Criteria | 24 |
| 3.13.1 | Boot Time | 24 |
| 3.13.2 | Continuous BIT | 24 |
| 3.13.3 | Faults | 24 |
| 3.14 | Power Requirements | 25 |
| 3.14.1 | Battery Power | 25 |
| 3.14.2 | Battery Chargers: | 25 |
| 3.14.3 | Fixed Mount Power | 26 |
| 3.14.4 | Loss / Restoration of Power | 26 |
| 4.0 | Physical Characteristics | 26 |
| 4.1 | Device Size (Including Battery Box) | 26 |
| 4.1.1 | HH | 26 |
| 4.1.2 | Fixed Mount | 26 |
| 4.2 | Device Weight (Including Battery Box) | 27 |
| 4.2.1 | HH | 27 |
| 4.2.6 | Fixed Mount | 27 |
| 4.3 | Interfaces | 27 |
| 4.3.1 | Fixed Mount Configuration | 27 |
| 4.3.2 | Antennas | 27 |
| 4.3.3 | Electrical | 28 |
| 4.4 | Environmental | 28 |
| 4.4.1 | Altitude | 28 |
| 4.4.2 | Temperature | 29 |
| 4.4.3 | Humidity | 29 |
| 4.4.4 | Salt-fog | 29 |
| 4.4.5 | Rain | 29 |
| 4.4.6 | Sand and Dust | 29 |
| 4.4.7 | Explosive Atmosphere | 29 |
| 4.4.8 | Vibration | 30 |
| 4.4.9 | Shock | 30 |
| 4.4.10 | Ballistic Shock | 30 |
| 4.4.11 | Immersion | 30 |
| 4.4.12 | Acoustic Noise | 30 |
| 4.4.13 | Fungus | 30 |
| 4.5 | Human-Machine Interface (HMI)-Control/Display | 31 |
| 4.5.1 | Controls | 31 |
| 4.5.2 | Displays | 31 |
| 4.5.3 | Connectors | 31 |
| 4.5.4 | Human Engineering (HE) | 32 |
| 5.0 | Electrical Characteristics and Performance | 33 |
| 5.1 | Electromagnetic Interference & Compatibility (EMI/C) | 33 |
| 5.1.1 | Dismounted | 33 |
| 5.1.2 | Fixed Mount/Platform | 34 |
| 5.2 | Electromagnetic Environmental Effects (E3) Survivability | 34 |
| 5.2.1 | High Altitude Electromagnetic Pulse (HEMP) | 34 |
| 5.2.2 | Near Strike Lightening (NSL) | 34 |
| 5.2.3 | Electro-Static Discharge (ESD) | 35 |
| 5.3 | Receiver Performance | 35 |
| 5.3.1 | FM Reference Sensitivity | 35 |
| 5.3.2 | AM Sensitivity | 35 |
| 5.3.3 | Signal Displacement Bandwidth | 35 |
| 5.3.4 | Adjacent Channel Rejection | 35 |
| 5.3.5 | Spurious Response Rejection | 36 |
| 5.3.6 | Inter-modulation Rejection | 36 |
| 5.3.7 | Audio Frequency Response | 36 |
| 5.3.8 | Hum and Noise Ratio | 36 |
| 5.3.9 | Receiver Attack Time | 36 |
| 5.3.10 | Receiver Closing Time | 36 |
| 5.3.11 | Receiver Front End Performance | 36 |
| 5.3.12 | Frequency Accuracy | 36 |
| 5.4 | Transmitter Performance | 37 |
| 5.4.1 | Overload Protection | 37 |
| 5.4.2 | Transmitter Power Controls. | 37 |
| 5.4.3 | Radiated Spurious Emissions | 37 |
| 5.4.4 | Audio Distortion | 37 |
| 5.4.5 | Conducted Spurious Emissions | 37 |
| 5.4.6 | Carrier Output Power Rating | 38 |
| 5.4.7 | Carrier Frequency Stability | 38 |
| 5.4.8 | Modulation Limiting | 38 |
| 5.4.9 | Carrier Attack Time | 38 |
| 5.4.10 | Audio Frequency Response | 38 |
| 5.4.11 | Acoustic Microphone Sensitivity | 38 |
| 5.4.12 | Radiated Spurious Emissions | 38 |
| 5.4.13 | Conducted Spurious Emissions | 38 |
| 5.4.14 | Adjacent Channel Power Ratio | 38 |
| 5.4.15 | Average Radiated Power Output | 39 |
| 5.4.16 | Transmitter Stability into Voltage Standing Wave Ratio (VSWR) | 39 |
| 5.4.17 | Receive-to-Transmit Transition | 39 |
| 5.4.18 | Receiver/Transmitter Protection | 39 |
| 5.4.19 | Continuous Tone Controlled Squelch System | 39 |
| 5.4.20 | 150 Hz Squelch Tone | 39 |
| 6.0 | Logistics | 40 |
| 6.1 | Maintainability | 40 |
| 6.1.2 | Maintenance Concept | 40 |
| 6.2 | Reliability | 40 |
| 6.2.1 | Mean Time Between Mission Critical Failure (MTBMCF) | 40 |
| 6.2.2 | Inherent Availability (Ai) | 40 |
| 6.3 | Personnel | 40 |
| 6.3.1 | Manpower and Personnel Integration (MANPRINT). | 41 |
| 6.3.2 | Training | 41 |
| 7.0 | Safety | 41 |
| 7.1 | System Safety | 41 |
| 7.1.1 | Electrical Safety | 41 |
| 7.1.2 | Mechanical Safety | 42 |
| 7.1.3 | Safety Markings and Labels | 42 |
| 7.1.4 | Microwave, RF and X-Radiation Safety | 43 |
| 7.1.5 | Chemical Hazards | 43 |
| 7.2 | Hazards of Electromagnetic Radiation | 43 |
| 7.2.1 | Hazards of Electromagnetic Radiation to Personnel (HERP) | 43 |
| 7.2.2 | Hazards of Electromagnetic Radiation to Ordnance (HERO) | 43 |
| 7.2.3 | Hazards of Electromagnetic Radiation to Fuel (HERF) | 43 |
| 8.0 | Workmanship | 44 |
| 8.1 | Colors and Finishes | 44 |
| 8.2 | Fasteners and Covers | 44 |
| 8.3 | Handling, Installation and Mounting | 44 |
| 8.3.1 | Handling | 44 |
| 8.3.2 | Installation and Mounting | 44 |
| 8.4 | Markings and Nameplate Data | 45 |
| 8.4.1 | Markings | 45 |
| 8.4.2 | Unique Item Identification (UID) | 45 |
| 8.4.3 | Contractor and Government Entity (CAGE) Code | 45 |
| 9.0 | Quality Assurance | 45 |
| 9.1 Quality Conformance Verification | 46 | |
| 9.1.1 | Inspection (I) | 46 |
| 9.1.2 | Analysis (A): | 46 |
| 9.1.3 | Demonstration (D): | 46 |
| 9.1.4 | Test (T): | 46 |
| 10.0 | ENVIRONMENTAL TEST REQUIREMENTS | 46 |
| 10.1 | Test Methods and Procedures | 46 |
| 10.1.1 | Altitude (Low Pressure) | 46 |
| 10.1.2 | Temperature | 46 |
| 10.1.3 | Humidity | 47 |
| 10.1.4 | Salt Fog | 47 |
| 10.1.5 | Rain | 47 |
| 10.1.6 | Sand and Dust | 47 |
| 10.1.7 | Explosive Atmosphere | 47 |
| 10.1.8 | Vibration | 47 |
| 10.1.9 | Shock | 47 |
| 10.1.10 | Immersion | 47 |
| 10.1.11 | Blowing/Freezing Rain | 48 |
| 10.1.12 | Acoustic Noise (Susceptibility) | 48 |
| 11.0 | Other Test Requirements | 49 |
| 11.1 | The Mean Time to Repair (MTTR) | 49 |
| 11.2 | Reliability | 50 |
| 11.3 | Production Acceptance Test (PAT) | 50 |
| 11.4 | Product Qualification Test (PQT) | 50 |
| Appendix A. STC / Legacy Waveform Interoperability | 1 | |
| Appendix B. Acronym List | 1 | |
| Appendix C. Glossary | 1 |
LIST OF TABLES
| Table 1 - STC Waveforms | 19 |
| Table 2 - HE Factors | 33 |
| Table 3 - Dismounted EMI/C Test Requirements | 35 |
| Table 4 - Fixed Mount EMI/C Test Requirements | 35 |
| Table 5 - Near Strike Lightning | 36 |
| Table 6 - Personnel-Borne ESD Environment | 36 |
| Table 7 - Radiated Spurious Emissions | 38 |
| Table 8 - Test Methods and Procedures | 48 |
vii
| 1.0 | INTRODUCTION |
| 1.1 | Scope |
This specification defines performance requirements for Special Operations Forces (SOF) Tactical Communications (STC) capability consisting of five software-programmable and hardware-configurable communications devices. The STC Handheld (HH) device is addressed herein. The HH can be configured in three basic SOF platforms, Ground, Airborne and Maritime. Two HH variants are required, Urban and Maritime, both of which shall be configurable as a component in all platform packages. The devices provide the flexibility and adaptability necessary to support the wide range of Special Operations Forces (SOF) unique mission requirements. A general description of the HH is provided in the following paragraphs.
1.2 Background
The STC HH system, as an element of SOF’s larger Command, Control Communications, Computers Intelligence Surveillance and Reconnaissance (C4ISR) architecture, must support a diverse set of operational conditions and concepts. However, there are common operating principles and requirements that are shared by all SOF forces.
Operations are principally characterized by small units operating in a highly decentralized fashion. SOF personnel operate in all environmental domains – ground, maritime, air. They operate in restricted propagation environments such as dense urban areas, underground structures and in maritime vessels. Alternatively, SOF can operate in isolated areas, distant from other friendly forces, and with no existing C4ISR infrastructure. Because SOF normally operates in small, strategically-placed teams, they must be capable of leveraging key national and defense C4ISR assets for both the information and intelligence they need for mission planning and/or execution.
1.2.1 Handheld (HH) Device
The concept of employment for the HH is the same as for the current SOF handheld radios, e.g., the AN/PRC- 148, AN/PRC-148B, AN/PRC-152 and AN/PRC-152A, both Urban and Maritime. However, the HH shall support simultaneous 2 channel operation, one wideband channel (a Mobile Ad hoc Networking (MANET) waveform) and one narrowband channel as well as an ISR video receive capability either integrated into the radio or attached to it in the form of a mission module (MM). As an Objective (O), it will support advanced LPI/LPD/LPE waveforms that transmit and receive voice and data. The HH device shall be optimized for use in a dismounted role, able to be carried and operated from a rucksack, attached to the operator's Load Bearing Equipment (LBE) with or without its organic holster. Its primary source of power is battery. The HH shall be designed to fit into mobility platforms, communications facilities, and transit cases (deployable packages) using installation kits, amplifiers, antenna systems and power supplies appropriate to the space/weight budgets of the particular configuration. When installed in a Fixed Mount System (FMS) the HH shall be designed with a "jerk and run" capability.
1.3 Threat
For detailed threat assessments refer to the following documents: The Military Satellite Communications (MILSATCOM) System Threat Assessment Report (STAR) (U); NASIC-1574-0367-05, March 2005, The Capstone System Threat Assessment (STA) for Army Special Operations Communications and Information Systems (U), United States (U.S.) Army Special Operations Command, 01 November 2007; Information Operations Capstone Threat Assessment (U), Volume 1-10, DI-1577-33-06, January 2006; Land Capstone Threat Assessment (U), NGIC-1100-0359-08, November 2008; applicable National Air and Space Intelligence Center (NASIC) documents: and; Future Threat to U.S. Special Operations Ground Forces; NGIC-1137-0297-05, 23 Nov 2004.
| 2.0 | APPLICABLE DOCUMENTS |
| 2.1 | Government Documents |
| 2.1.1 | Specifications, Standards, and Handbooks. |
2.1.1.1 Military Specifications
| MIL-DTL-64159B |
| Camouflage Coating, Water Dispersible Aliphatic Polyurethane, Chemical Agent Resistant, 24 January 2011 |
| MIL-DTL-53039D |
| Coating, Aliphatic Polyurethane, Single Component, Chemical Agent Resistant, 24 January 2011 |
2.1.1.2 Federal Standards
| FIPS PUB 140-2/CN2 |
| Federal Information Processing standards Publication 140-2, Security Requirements for Cryptographic Modules, 12 March 2002 |
| FIPS PUB 180-4 |
| Secure Hash Standard (SHS), March 2012 |
| FIPS PUB 186-3 |
| Digital Signature Standard, 9 June 2009 |
| FIPS PUB 197 |
| Advanced Encryption Standard (AES), 26 November 2001 |
2.1.1.3 Military Standards
| MIL-STD-130N(1) |
| Identification Marking of U.S. Military Property, 16 November 2012 |
| MIL-STD-188-114A/Notice 1 |
| Electrical Characteristics of Digital Interface Circuits, 13 December 1991 |
| MIL-STD-188-141C |
| Interoperability And Performance Standards for Medium and High Frequency Radio Systems, 27 December 2011 |
| MILSTD-188-181C |
| Interoperability Standard for Access to 5-kHz and 25-kHz Ultra High Frequency (UHF) Satellite Communications Channels, 2 June 2008 |
| MILSTD-188-182B(1) |
| Interoperability Standard for DAMA Orderwire Messages and Protocols, 18 December 2009 |
| MILSTD-188-183B |
| Interoperability Standard for Multiple-Access 5-kHz and 25-kHz UHF Satellite Communications Channels, 2 June 2008 |
| MIL-STD-188-220D(1) |
| Interoperability Standard for Digital Message Transfer Device Subsystems, 23 June 2008 |
| MIL-STD-188-241 |
| RF Interface Requirements for Very High Frequency (VHF) Frequency Hopping Tactical Radio Systems |
| MIL-STD-188-241-1 |
| Single Channel Ground and Airborne Radio System (SINCGARS) Waveform Specification, 10 February 1989, (SECRET) |
| MIL-STD-188-241-2 |
| Interoperability/Performance Standard for Tactical Single Channel Very High Frequency (VHF) Radio Equipment, 24 September 1999, (SECRET) |
| MIL-STD-188-241-2 |
| Appendix B, Interoperability/Performance Standard for Tactical Single Channel Very High Frequency (VHF) Radio Equipment, 24 September 1999, (SECRET) |
| MIL-STD-188-241-1/2 |
| Single Channel Ground and Airborne Radio System (SINCGARS) Waveform Specification, 10 February 1989, (SECRET) |
| MIL-STD-188-242 |
| Interoperability and Performance Standards for Tactical Single Channel Very High Frequency (VHF) Radio Equipment, 20 June 1985 |
| MIL-STD-188-243 |
| Interoperability and Performance Standards For Tactical Single Channel Ultra High Frequency (UHF) Radio Communications, 15 March 1989 |
| MIL-STD-461F |
| Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, 10 December 2007 |
| MIL-STD-464C |
| Electromagnetic Environmental Effects Requirements for Systems, 1 December 2010 |
| MIL-STD-704F/CN2 |
| Aircraft Electrical Power Characteristics, 25 October 2013 |
| MIL-STD-810G |
| Environmental Engineering Considerations and Laboratory Tests, 31 October 2008 |
| MIL-STD-1472G |
| Design Criteria Standard: Human Engineering, 11 January 2012 |
| MIL-STD-2169B/1 |
| High Altitude Electromagnetic Pulse (HEMP) Environment, 19 January 2012 |
| MIL-STD-6016E |
| Tactical Data Link (TDL) 16 Message Standard, 20 July 2012 |
| MIL-STD-6017C |
| Variable Message Format (VMF), 31 May 2012 |
| 2.1.1.4 | Military Handbooks |
| MIL-HDBK-454B | |
| General Guidelines for Electronic Equipment, 15 April 2007 |
| MIL-HDBK-781A |
| Reliability Test Methods, Plans and Environments for Engineering Development, Qualification, and Production, 01 April 1996 |
| 2.1.2 | National Security Agency (NSA) Regulations and Specifications |
| EKMS 308F* | |
| Data Tagging & Delivery Standard, 16 April 2008 |
| EKMS 322 Rev C |
| Firefly Specification (U), 1 October 2010 |
| CNSSAM TEMPEST 01-02 |
| NONSTOP Evaluation Standard (U), October 2002, |
| NSTISSAM TEMPEST 1-92 (C) |
| Compromising Emanations Laboratory Test Requirements-Electro-magnetic (U), 15 December 1992, |
| TEMPEST 2/95A |
| RED/BLACK Installation Guidance, 3 February 2000 |
| 2.1.3 | Department of Defense (DOD). |
| DCB79S4000C | |
| JTIDS System Segment Specification (SSS) |
| DISR Baseline Release 04-2.0 |
| DOD Information Standards Registry, 22 February 2002 |
| JIEO 9120A |
| Technical Interface Specification for Second generation Anti-Jam Tactical UHF Radio for NATO" (SATURN) Waveform, July 1992 |
| JTC3A9001C |
| SINCGARS Frequency Hopping Waveform Specification (SECRET) |
| 2.1.4 | Other Government Documents, Drawings, and Publications. |
| MSRC-5000SCA-V4.0 | |
| Software Communications Architecture Specification, Version 4.0 28 February 2012 |
| MSRC-5000SEC-V1-1 |
| Security Supplement to the Software Communications Architecture, 17 November 2001. |
| MSRC – 5000API -V1-1 |
| Applications Program Interface Supplement to the SCA, 17 November 2001. |
| ICD-GPS-154C |
| GPS Interface Specification, 10 December 2002 |
| ICD-GPS-222A |
| NAVSTAR GPS User Equipment Auxiliary Output Chip (Secret), Rev. A, & D, 20 April 1990 |
| ICD-GPS-225 |
| NAVSTAR GPS Selective Availability and Anti-Spoofing Host Application Equipment Design Requirements (Secret), 1 August 1991 |
| ITT-AC/D A3214186-Rev C |
| System Engineering Document for the Ground Radio SINCGARS System Improvement Program (SIP and ASIP), May 13 2005 |
| ITT-A/CD 35740/Z004-2 |
| SINCGARS SIP Product Specification for Generic Receiver-Transmitter, Radio RT-1523C/D(C)/U (Volume 2 of 2) |
| ITT A/CD 95-3886 |
| SINCGARS SIP Frequency Hopping Waveform Specification (SECRET) |
| ITT-A/OD No. 1260/ICD-5 |
| SINCGARS System Engineering Document - Ground Radio System (Final), 28 July 1989 |
| ITT 8224936 |
| Soldier Radio Waveform Software Requirements Specification (SRS) Revision G, July 2009 |
| ITT 8181466 |
| BOWMAN MOD-ASIP VHF Waveform Fixed & Hopping Frequency, Rev C8, 9 October 2003 |
| 55210-WFA-ASCM-SRS-0001-1.0 |
| Advanced Special Communications Mode (ASCM) Software Requirements Specification (SRS), May 17, 2012 |
| STANAG 4372 |
| Second-Generation Anti-jam UHF Radio for NATO |
| MUOS-GD-62-P54050T |
| Waveform Design Specification for the MUOS CAI Waveform |
| SRW-SPSV1.8 |
| Soldier Radio Waveform, System Performance Specification Version 1.8, 19 March 2008 |
| eCOBRA |
| Signal Architecture Standard for the Collection of Broadcasts From Remote Assets (eCOBRA), Release 2.01, 02 August 2000 |
| 2.2 | Industry Standards |
| 2.2.1 | American National Standards Institute (ANSI). |
| ANSI/TIA/EIA-603-D-2010 | |
| TIA/EIA Standard for Land Mobile FM or PM Communications Equipment Measurement and Performance Standards, December 2010 |
| ANSI/TIA/EIA-Z535.4-2007 |
| Product Safety Signs and Labels, June 6 2002: |
| 2.2.2 | Institute of Electrical and Electronic Engineers (IEEE). |
| ANSI/IEEE C95.3-2002 | |
| Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz |
2.3 Order of Precedence
In the event of a conflict between this Specification and the aforementioned Standards and References, this specification takes precedence.
| 3.0 | SYSTEM REQUIREMENTS |
| 3.1 | STC HH Description |
| 3.1.1 | HH System Components |
The Major Components that shall be part of the device kit:
· One Receiver/Transmitter (Maritime or Urban version)
· Two Rechargeable Battery Packs
· Non-rechargeable Batteries with cassette that attaches to the radio like the battery packs
· One Receiver/Transmitter Holster
· One Accessory Pack/Carrying Case
· One set of Line-of-Sight (LOS) antennas composed of one antenna for each of the following bands: one 30-88 Megahertz (MHz), one 136-174 MHz, one 225-400 MHz and one 403-470 MHz and one 30-512 MHz. Antenna gain shall be no less than 0 dB. Reducing the number of antennas by combining two or more into a single antenna is preferred provided the combined antenna(s) deliver the same performance.
· Applicable antennas for APCO 25 (138-174, 406-512 &r 746-869 MHz.), SRW (225-400 MHz and 1350-2500 MHz) and Netted Iridium (1616 - 1626.5 MHz). Netted Iridium and MUOS antenna gain shall be no less than 31 dBi. Other wideband antennas for operating from 225MHz to 2.5 GHz.
· H-250( )/U handset or equivalent
· External GPS Antenna Cable, 3 meters in length
· USB Interface Cable
· Cloning Cable
· PC Programming Software with PC to HH USB Cable
· Single Station AC Battery Charger
· One Operator Manual, Operator Card, and Inter-Active CD
3.1.2 Universal Accessories
· STC Power Adapter Interface (PAI) and Direct Current (DC) and Alternating Current (AC) Input Cables
· Retransmission Cable
· FMS Installation Kit, Mounting Brackets, Power Supply, Amplifiers, Cables, and Antennas
· Six-Station AC/DC Battery Charger
· Six-Station AC Only Battery Charger
| 3.2 | STC HH Architecture |
| 3.2.1 | Software Communications Architecture (SCA) |
All of the STC devices shall be compliant with the current Joint Tactical Radio System (JTRS) SCA specification(s) including the HH. This includes SCA version 4.1 for wideband waveforms, e.g., SRW.
3.2.2 Hardware Architecture
3.2.2.1 The HH shall employ a hardware Open Systems Architecture (OSA) using common open interfaces to all Line Replaceable Units (LRU) and designed to allow for technology insertions, both hardware, firmware and software.
3.2.2.2 The HH design approach shall implement industry open systems standards and interfaces and at a minimum comply with the Department of Defense (DOD) Information Technology Standards Registry (DISR).
3.2.3 Android Interface
The HH shall be able to interface with an Android computing device. The Android computing device shall require interfaces providing IP, serial, USB/USB "On the Go", or other protocols as determined to meet the STC threshold functionality requirements. The HH shall be controlled from the Android device however, the user shall also have the ability to configure and control the STC device via front panel screen and keypad. Users shall have the ability to power off, or temporarily suspend, any of the capabilities not needed based on the mission in order to conserve battery power, lower Radio Frequency (RF) spectrum presence, etc. The intent is for the end users to be able to select their own preference of Android device in addition to a "packaged solution" (i.e. users have the option to include vendor-provided Android device or utilize Government Furnished Equipment (GFE) Android devices and installing vendor-provided applications as required). The capabilities described in paragraphs 3.2.3.3 and 3.2.3.5 shall be provided by the Android Tactical Assault Kit (ATAK) application which is a Government owned mapping application that provides multiple Application Programming Interfaces (APIs) for integration. Operators shall be able to perform the following tasks via the Android computing device:
| 3.2.3.1 | Configure/program/operate the HH to include placing the STC in to standby or sleep/suspend mode. |
| 3.2.3.2 | View imagery received by HH and displayed on the Android device. |
| 3.2.3.3 | Overlay real time Situational Awareness (SA)/Blue Force Tracking (BFT)/Position Location Information (PLI) onto a digital map received by the HH. |
| 3.2.3.4 | Send/receive text messages; point-to-point or broadcast. |
| 3.2.3.5 | Share map overlays, routes, drawings, etc., with other users via the MANET provided |
by the HH.
| 3.2.3.6 | Send text messages utilizing a voice-to-text mechanism (e.g. user speaks into the Android device and audio is converted to text and transmitted via the HH). |
| 3.2.3.7 | Place the HH in silent audio mode and view "closed-caption" text of received voice messages. |
| 3.2.3.8 | Capture real-time video and simultaneously distribute the video via the HH MANET waveform either point-to-point or broadcast. |
| 3.3 | Channel Types |
| 3.3.1 | Channel Configuration and Definition |
| 3.3.1.1 | The HH shall have at two configurable channels (one channel for narrowband waveforms and one for a wideband waveform) in addition to an integrated SAASM GPS receiver. As an Objective each channel can be support both wide and narrowband channels. |
| 3.3.1.2 | The HH shall allow channel configuration/reconfiguration within the specified combinations of waveforms identified Table 1. When configured for two channel operation each channel shall operate independently and simultaneously with one another. The device shall be able to use any combination of narrowband waveforms when the wideband channel is in operation without any performance degradation or co-site interference. |
| 3.3.1.3 | The operator shall be able to change the channel operating parameters, monitor channel performance, and turn a channel on/off without affecting the operation of the other channel. |
| 3.3.1.4 | A failure in one channel shall not degrade the operation of the other channel(s) provided primary power is still being applied to the channel. |
| 3.3.1.5 | The HH shall alert the operator/platform to a critical change in radio system status by providing an audible and visual alarm. The status or failure code(s) will be visible on the device display and a connected (Personal Digital Assistant (PDA) or laptop. The operator shall be able to enable or disable the audible alarm. |
| 3.3.2 | Guard Channels |
3.3.2.1 The HH shall be able to receive and transmit on the international distress frequencies in both unencrypted beacon and voice modes.
3.3.2.2 Guard Mode Operations. The HH shall have a Guard mode of operation with the following characteristics:
a. The guard channel shall be selectable by front panel controls or via the remote control port.
b. The HH shall alternately monitor the guard channel when selected and operational communications channel/frequencies.
c. The HH shall monitor the guard channel for a time duration of 0.25 to 0.50 seconds when not in transmit or un-squelched receive.
d. The HH shall provide an emergency guard mode that automatically tunes the transmitter and the main receiver to the guard channel and disables the guard scan mode when activated.
e. Scanning of the Guard channels shall stop when a signal is detected on the main channel or guard channel, or when the HH is transmitting.
f. Monitoring of the Guard channels shall resume within five seconds after the last reception or transmission.
3.3.3 Channel Scanning
3.3.3.1 The HH shall be able to establish a scan plan to monitor selected channels of interest (hostile or friendly) both data and voice.
3.3.3.2 The Scan characteristics of the HH shall have the following characteristics:
a. The HH shall monitor from 2 to 10 preset scan channels for a time of 0.25 to 0.50 seconds before moving to the next channel. Scanning will cease when the device is transmitting or receiving.
b. If the transmit preset has not been entered for the channels being scanned then the operator cannot transmit on any channel being scanned and communications will be limited to the scan channels only
c. If a transmit preset has been entered for the channels being scanned then the operator can transmit on the scan channel in response to received signal.
d. If the HH is in Cipher Text (CT), the device shall only transmit on the frequency of the preset channel being actively monitored independent of any transmit presets selected.
e. Channel scanning shall be stopped when a signal is detected on one of the scan channels or when the device is transmitting or receiving on the primary communications channel. Channel scanning shall resume within five to eight seconds after the last activity on the primary communications channel.
f. The HH shall use the default Transmission Encryption Keys (TEK) and encryption type if one has not been entered as part of the selected preset for scan operations in CT mode (friendly channels).
3.4 Multifunctional Capabilities:
The HH shall support multifunctional operations providing SA and Force Protection (FP). The HH shall be capable of providing/exchanging voice, video and data between one another. Compatibility and interoperability with other systems/devices such as tactical sensors shall provide rudimentary intelligence capabilities not found in current radios. The HH shall be capable of receiving friendly/hostile signals and determining Lines of Bearing (LOB) to the signals of interest.
· Provide detection and location of Signals of Interest (SOI) at significantly relevant stand-off distances
· Simple & Efficient user interface includes audible alert & visual indicators on the display or a separate remote, wrist worn display unit
· Relay relevant data via communications network for informational reporting or enhanced processing
· Improved Force Protection with enhanced situational awareness (early identification of potential threats)
· Flexible mission planning with updates via keypad or PC download
| 3.4.1 | Situational Awareness (SA) |
| 3.4.1.1 | The HH shall be capable of transmitting Friendly Force Tracking (FFT) signals (e.g., Enhanced Collection of Broadcasts from Remote Assets (eCOBRA)) either in the deliberate mode (priority over C3 functions) or in the background on a non-interference basis with C3 functions. As an Objective (O) the HH will be able to receive and locally re-transmit FFT signals. |
3.4.1.2 The HH shall be able to receive Full Motion Video (FMV) from Predator, and other select Unmanned Aerial Vehicle (UAV) platforms in Standard Definition (SD) and as an Objective (O) High Definition (HD). This capability will be comparable to and fully interoperable with the Remotely Operated Video Enhanced Receiver (ROVER) and the Video Oriented Transceiver for Exchange of Information (VORTEX).
3.4.1.3 The HH shall be capable of presenting a SA picture on an external display such as the Android or laptop. As an Objective (O) the HH shall have a display that can project the same picture. This includes PLI and SA from the MUOS and Netted Iridium networks.
3.4.1.4 As an Objective (O) HH will be able to receive and re-transmit information to and from select threat warning systems/sensors. The ability to receive information from such systems is limited to the tuning/frequency range of the HH.
3.4.1.5 The HH shall be capable of receiving, relaying and/or processing sensor collected information from sensors on pre-arranged frequencies/channels. The information shall be displayed in text and/or visual format using an Android or laptop. As an Objective the HH will present this information on its display.
3.4.2 Signals Based Threat Warning / Situational Awareness (SBTW/SA)
3.4.2.1 The HH shall be able to; scan, detect, intercept and recognize SOI transmitting on frequencies from 2 to 2,000 MHz. Limited processing/evaluation of such signals shall be done locally on an Android or laptop connected to the HH. The HH shall also be able to transfer and relay these signals for further evaluation to a remote processing center. Ideally, limited processing of such signals may be done within the radio itself and displayed without being connected to an external device.
3.4.2.2 The HH when receiving a SOI shall provide both an audio and visual alarm to the operator. The HH shall also be capable of receiving, relaying threat information received from friendly threat warning systems and display the information (text or image) on an Android or laptop.
3.4.2.3 The HH shall, without external assistance, be able to provide radio Direction Finding (DF) of signals of interest by combining LOB information and display it to the operator. It shall take no more than three HH devices arranged in an appropriate pattern and receiving the same signal (out to a radial distance of at least 5 kilometers) to provide location of the signal within 50 meters accuracy. The range and bearing information shall be shared among the HH devices with the location information presented on the HH display.
3.4.2.4 The location of the receiving HH devices, LOB to the intercepted signal and its location shall be collected, processed, and displayed on an external mobile device along with the frequency and mode of the intercepted signal. The sharing of this data shall be accomplished on a prearranged common channel/frequency. The ability to intercept signals of interest will be limited by the tuning range of the HH.
3.4.3 ISR Video Receive Capability / Interoperability
The HH ISR capability (either integrated into the HH or as a Mission Module) shall be able to receive both the Common Data Link (CDL) and Digital Data Link (DDL) waveforms supporting both U.S. Type I, Suite A encryption (KGV-135A) as well as AES, Suite B, NSA Approved commercial encryption.
The following table summarizes the potential performance expected.
| Features |
| Specifications |
| Frequency Bands |
| L, S, C and Ku |
| Frequency Ranges |
| 400-470, 1625-1850, 2200-2500, 4400-5000, 5250-5858 MHz |
| Position Location |
| GPS Compatible |
| Security |
| KGV-135A / AES-128/256 |
| Maximum Data Rate |
| Up to 4.5 Mbps |
| Input Power |
| 6-16 Volts DC |
| Radio Configuration |
| PC Configuration Tool Kit |
| Data Types |
| IP, Wi Fi, Streaming Video |
| Data Rate |
| Up to 10.71 Mbps |
| Bandwidth |
| 22MHz at 1dB, 27MHz at 3 dB |
| Video Format |
| NTSC, H.261, H.264 (Rover / Vortex compatible) |
| Video Resolution |
| 640x480 pixels at 15 frames per second |
| Compression |
| MPEG-2, MPEG-4, MJPEG |
| Frequency Resolution |
| 1 MHz |
| Peripherals |
| Connects to external devices for viewing video |
| MESH Network |
| Yes |
| Waveforms |
| CDL, DDL, & STANAG 7085 |
| Interoperability |
| Works with most legacy video transmission systems |
3.4.4 Intelligence, Surveillance & Reconnaissance (ISR)
3.4.4.1 SOF users require the ability to receive ISR feeds, providing both Standard Definition (SD) and High Definition (HD) still motion imagery and FMV directly from National and SOF-unique ISR assets both in the unencrypted and US Type 1 (KGV-135A) and commercial AES encrypted formats. The HH shall be able to receive the ISR data and simultaneously distribute the imagery utilizing the HH MANET capability. This may be accomplished by having the ISR capability integrated into the HH or provided as an attachable mission module.
3.4.5 Simultaneous Channel Operation
The HH will provide secure simultaneous legacy narrow-band communications, MANET, and LOS ISR-receive capabilities to the user. The operator shall be able to simultaneously communicate on one legacy narrowband communications channel (voice or data), over the MANET waveform in both voice and data/IP and receive on at least one ISR video channel. Moreover, the HH shall be capable of dual-net audio where the operator shall be able to receive audio on two voice nets simultaneously, e.g., legacy narrowband and MANET voice. The operator shall have the ability to selectively transmit on either net or both nets simultaneously.
| 3.5 | Communications Range |
| 3.5.1 | HH Range |
3.5.3.1. The HH shall have a minimum transmit/receive range of 5 km for the Land Mobile Radio (LMR), SINCGARS, Have Quick, and the SRW waveforms. The objective is 15 km. When the HH is installed in a platform with a HPA/LNA and higher gain antenna(s) it shall have a minimum transmit/receive range of 32 km for all channels. As an Objective (O) a 60 km range is preferred.
3.5.3.2. The HH shall have a minimum transmit/receive LOS range of 16 km air to ground (Ultra High Frequency (UHF) band) with the aircraft at a height of 3,000 feet for all the legacy narrowband and networking waveforms. Objective is 30 km at 5,000 feet.
3.5.3.3 The HH when configured for UHF Satellite Communications (SATCOM) with applicable HPA/LNA and antenna(s) shall provide the necessary Effective Isotropic Radiated Power (EIRP) to meet link margin requirements contained in MIL-STD-188-181C/182B/183B).
| 3.6 | Interoperability |
| 3.6.1 | Legacy Devices |
| 3.6.1.1 | When the HH instantiates a waveform it shall be over the air interoperable with legacy/current radios running the same waveform. |
| 3.6.1.2 | The functionality, performance, protocols, and interface controls of the HH shall be designed to minimize integration requirements with platforms and applicable operator training. In this regard, the HH shall provide a functional interface to platform host equipment not requiring changes to platform host equipment. |
| 3.6.1.3 | The HH voice and data input/output, receiver and transmitter characteristics shall be the same, or better than, the legacy radios/waveforms being replaced or emulated. |
| 3.6.2 | Land Mobile Radio (LMR) Interoperability |
The HH shall be interoperable with commercial LMR and be compatible with the full range of sub-audible tones, Continuous Tone-Coded Squelch System (CTCSS), required for interoperability with LMR commercial repeaters. A Trunked Radio capability is the objective.
| 3.7 | Mobile Ad Hoc Networking (MANET) Waveforms |
| 3.7.1 | General Characteristics |
MANET solutions shall be incorporated into the HH and be available to the user simultaneously, or selectively at the users discretion, with the legacy narrowband capability. Users shall have the ability to connect a mobile device capable of receiving unicast and multicast IP traffic in order to display SA while simultaneously communicating via legacy narrowband waveforms. The MANET shall be able to support a minimum of two video feeds, voice and SA over the MANET network with no limitations on numbers of nodes or hops. Performance in restricted propagation environments and high multipath environments shall be implemented in the MANET solution. Initially the MANET encryption shall be no less than AES 256 / FIPS 140-2 utilizing NSA approved Suite B algorithms. NSA certified US Type I, Suite A encryption is desired however.
3.7.2 Soldier Radio Waveform (SRW)
The HH shall support all of the mandatory SRW implementation requirements.
3.7.3 Wideband Networking Waveform (WNW)
As an Objective the HH will support all the mandatory requirements for implementing WNW as required for both dismounted and vehicle mounted platforms.
3.7.4 Commercial and Proprietary Waveforms
The HH shall be capable of integrating / porting commercial and/or proprietary networking waveforms as such technologies evolve. This is consistent with the OSA requirement.
3.7.4.1 For instance two commercial MANET waveforms that the HH might support are the Trellisware Tactical Scalable MANET-enhanced (TSMe) and the Persistent Systems Wave Rely MANET waveforms, as a mission module or integrated into the device. Other MANET waveforms that can support multiple video streams, voice and data will be considered.
The information contained in the following table and subsequent paragraphs represents the optimal SOF features and specifications for commercial MANET waveform.
| Features |
| Specifications |
| Transmit Power |
| 2 Watt Peak (selectable 100 mW, 250 mW, 500 mW, 1 W, and 2 W) |
| Frequency Ranges |
| 224-450 MHz, 1775 - 1815 MHz , 2312-2507 MHz |
| Relay Support |
| Up to 8 hops for voice and data |
| Position Location |
| Integrated or external GPS |
| Security |
| Suite B, AES-256 |
| Maximum Data Rate |
| Up to 37 Mbps UDP, 27 Mbps TCP (20 MHz channel) 4 voice channels |
| Minimum Data Rate |
| Minimum of 560 Kbps guaranteed to 8 hops (4 voice channels) |
| Input Power |
| 6-18 Volts DC |
| Radio Configuration |
| Frequencies / crypto / network parameters from web application |
| Data Types |
| AMR 5.9 voice, IPv4 or IPv6 data, streaming video |
| Audio Channels |
| User configurable: 2, 4, 8, 12, 16 independent voice channels |
| Audio Latency |
| 3 Hop < 275 ms; 8 Hop < 400 ms |
| Net Entry Time |
| < 5 sec |
| Occupied Bandwidth |
| User configurable 1, 5, 10, 20, 40 MHz |
| IP Support |
| UDP, TCP, Multicast, Broadcast, Unicast |
PTT Voice over the Network Up to 16 independent AMR 5.9 voice channels All units with matching crypto keys will receive voice G.711 Codec for Radio-over-IP (RoIP) interoperability
IP Data over the Network Connects to external PC applications via Ethernet just like any wireless network card Multicast any IP data – ideal for file transfer or streaming media Share data with anyone in your network Seamless layer 2 network connectivity 802.11a/b/g AP compatible with MANET Integrated serial-to-Ethernet capability Cursor-on-Target Dynamic Link Exchange Protocol (DLEP) Certified Integrated DHCP server Advanced multicast algorithm
Selecting Frequencies Configurable to operate anywhere within the 1775 to 1815 MHz frequency range Occupied bandwidth configurable from 20MHz down to 4MHz
AES Encryption AES-CTR-256 with SHA-512 HMAC Over the air zero (OTAZ) Over the air rekey (OTAR) COMSEC keys automatically zero if battery removed for longer than 90 sec Set distinct AES-256 encryption keys on each channel Integrated hardware cryptographic accelerator FIPS 140-2 (Up to level 2) Utilizes all Suite B algorithms AES-CTR-256 with SHA-512 HMAC Security Features Tamper detection Unit has certificates-based secure web services access (https)
No Tactical Networking Configuration:
Nodes automatically establish links on the move Units automatically join into a network Self-forming / healing
Tones and Alerts (Activated use with external headset only) PTT Voice in/out - Beep when pressing and releasing PTT Voice Channel Occupied - Continuous Beep when pressing PTT Crypto keys not compatible – No audio Voice prompts alert an operator of system and network status
Global Positioning System (GPS) Embedded Ublox 6 GPS chip or external GPS through NB MGRS or LAT/LONG/ALT coordinate output over JSON interface Real Time network PLI tracking available via KML or JSON interface
MANET Mission Configuration Browser-based application supported on all operating systems Used for configuring frequency, power level, security settings, & applying new software updates Secure web management interface Network wide management and configuration functionality Google Earth based network monitoring
| 3.7.5 | Encryption |
| 3.7.5.1 | The HH shall be capable of functioning as a subscriber in a MANET using NSA Commercial Solutions for Classified (CSFC) approved Type II, Suite B encryption algorithms. The HH shall also be capable of using Type I, Suite A encryption. |
| 3.7.5.2 | The HH shall be capable of using the existing/legacy key load and mission load devices such as the Data Transfer Device (DTD), Simple Key Loader (SKL), DTD2000, Data Management Device (DMD), CYZ-10, KOI-18 and KYK 13. |
| 3.7.6 | Mobility |
The MANET capability shall be able to function in various mobile environments including foot, ground, maritime and airborne (fixed and rotary wing). Subscribers shall be able to move/roam from group to group without loss of communications.
| 3.7.7 | Operate as Standalone or Member Device |
| 3.7.7.1 | Standalone: The HH shall function as legacy LOS and Beyond Line of Sight (BLOS) secure/non voice and data communications systems. The HH shall support LOS and/or BLOS range extension and BLOS to LOS relay/retransmission. |
| 3.7.7.2 | Member: The HH and shall function as a member or master station in the establishment and participation in a secure (Suite B) and non-secure MANET network. The network shall be capable of distribution of tactical SA information between and among all members. The HH, when properly configured, shall provide BLOS range extension for the other members in the network. |
| 3.7.7.4 | Capability: The MANET shall be incorporated into fixed and mobile environments associated with vehicular, maritime, and airborne fixed and rotary wing platforms. Members in one network must be able to roam and join other like-networks as they become available. The MANET shall support a multicast data and video distribution and tactical situational awareness. |
| 3.7.7.5 | Multicast: The HH shall be capable of operating as Master Subscriber Terminal (MST) to join shared networks supporting a multicast capability. The MANET shall support multicast video distribution, FMV, voice and data; provide tactical SA and Cursor on Target (CoT) capabilities. |
| 3.7.7.6 | Internet Protocol: The HH shall implement as a minimum IP Version 6 (IPv6). The IPv6 implementation shall support Unicast (point-to-point), Anycast (communications with the closest member of the device group), and Multicast (communications with multiple members of a device group). |
| 3.7.8 | Network Management |
| 3.7.8.1 | Planning: The HH shall be designed to use existing legacy network management capabilities and the SRW Network Manager for network planning, monitoring and control or a commercial network management/control for other MANET waveforms. The Wideband Networking Waveform (WNW) Network Management System (WNMS) will be implemented in the HH as an Objective (O). |
| 3.7.8.2 | Execution: System management software shall be provided that performs all HH management requirements not performed by the legacy management systems. The system management software shall include, as a minimum, initial assignment of waveforms and their associated waveform data to be stored in the radio, routing, and retransmission configuration information, Information Assurance (IA) configuration and authentication information to allow local and remote management of the device. |
| 3.7.8.5 | Simple Network Management Protocol Version 3 (SNMPv3): As an Objective (O) the SNMPv3 as an interoperable standards-based protocol for network management interface will be implemented in the HH. |
| 3.8 | Waveform Requirements |
| 3.8.1 | Waveform Selection |
| 3.8.1.1 | The HH shall allow an operator to select a waveform from memory and instantiate it on any properly configured channel supporting the waveform. |
| 3.8.1.2 | Provisions shall be provided to prevent instantiating a waveform to an improperly configured channel. |
| 3.8.1.3 | The HH shall allow operators/platforms to access and edit operating parameters loaded in the radio. |
| 3.8.1.4 | The HH shall support the waveform capabilities identified below. The HH shall support simultaneous two channel operation using the integral narrowband and wideband channels; a combination of the narrowband waveforms or; any of the mission modules with the wideband channel. As an Objective (O) the HH shall be able to support the operation of the wideband channel with a MANET mission module simultaneously. STC Threshold and Objective waveforms are identified in Table 1. |
Table 1 - STC Waveforms
| NARROWBAND WAVEFORMS |
| Threshold |
| Objective |
| SINCGARS ESIP (VHF-FM Military) |
| X |
BOWMAN VHF
X
| HAVE QUICK II (UHF-AM/FM/PSK) |
| X |
| UHF SATCOM. MI-STDs 188-181C/182B/183B |
| X |
Transformation l Communications MILSATCOM (TCM)
X
Enhanced Position Location Reporting System (EPLRS) 3
X
| Enhanced Collection Of Broadcasts from Remote Assets (eCOBRA) |
| X |
Second-Generation Anti-Jam Tactical UHF Radio for NATO (SATURN)
X
| Data Control Waveform (MIL-STD-188-184A) |
| X |
| VHF FM Military Tactical |
| X |
| GPS SAASM |
| X |
| Advanced Special Communications Mode (ASCM) |
| X |
| VHF FM for ATC |
| X |
| VHF AM ATC |
| X |
| VHF/UHF FM LMR |
| X |
| VHF ATC Data Link Next Generation Air/Ground Communications (NEXCOM) |
| X |
| UHF AM/FM PSK Military Tactical |
| X |
| Land Mobile Radio (APCO-25) 2 |
| X |
Netted Iridium3
X
| WIDEBBAND WAVEFORMS |
| Threshold |
| Objective |
| Soldier Radio Waveform (SRW) |
| X |
| Other Commercially Available Waveforms (e.g., TSMe or Wave Relay) 3 |
| X |
Link 16 / TADIL-J3
X
Wideband Networking Waveform (WNW) 1/3
X
4G/LTE
X
Wireless Local Area Network (WLAN)
X
MUOS-CAI3
X
Integrated Broadcast Service (IBS) 3
X
Integrated Survey Program3
X
| ISR Receiver (CDL & DDL) 3 |
| X |
1 Only certain modes and capabilities of the WNW will be implemented in the HH.
2 APCO-25 defines a standard for migrating from the current bandwidth of 25 kHz to a reduced bandwidth of 12.5 kHz using FDMA digital technology in Phase 1 and TDMA in Phase 2.
3 These waveforms likely mission module candidates.
3.8.1.5 When configured for two channel operation the HH shall have the capability of automatic protocol conversion within like modes and between frequency bands or waveforms for which it is configured.
3.8.2 Retransmission and Routing
3.8.2.1 The HH shall have a retransmit capability and shall provide the physical and electrical interfaces to support narrowband retransmission/relay operations with another like device. As an objective the HH will support wideband retransmission/relay operations
3.8.2.2 The two channel capability shall provide reroute signals when waveform capabilities are changed, for example, when switching from SRW to another MANET waveform. As an Objective (O) the HH will be configurable for RF switching capabilities to perform automatic retransmission, cross-banding and routing operations between channels in both secure and non-secure modes.
3.8.2.3 As an Objective (O) the HH will be capable of operating as a non-CCI repeater.
3.8.3 Waveform Storage
3.8.3.1 All waveforms configured in a HH shall be down-loadable, locally or over the air, and stored in non-volatile memory.
3.8.3.2 The HH shall have safeguards to reduce the possibility of unintentional reprogramming, preclude the possibility of software storage errors, and provide the minimum controls (software, hardware, or both) that allows or prohibits over the air waveform and/or Communications Security (COMSEC) keys download. Waveforms/keys shall be authenticated when they are locally or over the air downloaded.
3.8.3.3 The operator shall be notified when a local or over the air download was successfully completed or failed.
3.8.3.4 The HH shall each be able to store and instantiate at least ten waveforms of those specified in Table 1.
3.8.4 Additional Waveforms
3.8.4.1 Optimized Waveform for Restricted Propagation Environments: The HH shall include a waveform and modulation scheme that allows for continuous communications and situational awareness in restricted propagation areas such as tunnels, inside and on various levels of maritime vessels, and within buildings. Operating under these conditions still requires maintaining voice, video, and data communications between nodes in a 1000 foot tunnel including up to 90 degree turns. Operation within maritime vessels requires maintaining voice, video, and data between nodes within and external to a ship for 500 feet. Urban canyons criteria include maintaining voice, video, and data for 1500 feet between nodes internal, and external to multi-story buildings
3.8.4.2 Commercial Broadcast Downlinks Via XM (No Modulation) Radio Channels: As an Objective (O) the HH shall receive commercial broadcast from XM Radio-like channels at a medium data rate.
3.8.4.3 MUOS: As an objective the HH will be interoperable with the MUOS waveform.
3.8.4.4 Advanced Special Communications Mode (ASCM): The HH utilizing ASCM shall be able to communicate in the presence of SOF Improvised Explosive Devices (IED) jammers.
3.8.4.5 Netted Iridium: As an Objective (O) the HH will be as capable as the Distributed Tactical Communications Systems (DTCS) handheld devices that operate over Iridium constellation. As with the DTCS the HH will provide secure push to talks (PTT) voice and data communications and simultaneous voice and data on the same channel. The HH, like DTCS, will provide PLI information and access real time SA. It is desired that the capability provides the ability for users to transmit their PLI, data and voice from anywhere on the globe. The ability to transmit PLI is configurable at the discretion of the user. The minimum PLI transmit modes are::
• Time – transmit PLI based on preconfigured time intervals
• Displacement – transmit PLI based on movement
• Push-to-talk – transmit PLI based on a PTT session
• Global ping – request a PLI update from users in a denied area
3.8.4.6 Radio Frequency (RF)-Netted Communications: The HH shall support secure (Suite A and B) and non-secure RF-netted communications. A RF netted capability provides information sharing for direction finding and locating potentially hostile and friendly RF emissions.
| 3.9 | Global Positioning System (GPS) |
| 3.9.1 | Internal GPS Receiver |
3.9.1.1 The HH shall include an internal SAASM GPS receiver and integrated antenna as well as the ability to connect to a remote antenna up to 3 meters from the device. The GPS receiver shall have a Precise Time & Time Interval (PTTI) output and shall also provide a 1 Pulse per Second (1 PPS) output that shall be used to provide timing to select waveforms such as SINCGARS, Have Quick (HQ) I/II, ASCM and eCOBRA.
3.9.1.2 The HH shall display its own GPS…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .