Atch_01_NGMP_PS_21Nov16.docx

PERFORMANCE SPECIFICATION

UNITED STATES SPECIAL OPERATIONS COMMAND

(USSOCOM)

For The Next Generation Manpack Radio

(NGMP)

21 November 2016

Prepared for:

Mr Arthur D. Coon

USSOCOM, SOF AT&L, PEO-C4-TC

7701 Tampa Point Boulevard MacDill AFB, FL 33621-5323

UNCLASSIFIED

UNCLASSIFIED

This page intentionally left blank.

Table of Contents

LIST OF TABLES

viii

1.0 INTRODUCTION

1.1 Scope

This specification defines performance requirements for the Next Generation Manpack (NGMP) radio. The NGMP shall be capable of being configured for dismounted (primary configuration) and mounted operations. The mounted configuration, Vehicle Mounted System (VMS), shall be capable of being installed/configured on three basic platforms, Ground, Airborne, and Maritime. The NGMP shall provide the flexibility and adaptability necessary to support the wide range of unique mission requirements. A general description of the NGMP is provided in the following paragraphs.

1.2 Background

The NGMP, as an element of the larger Command, Control, Communications, Computers Intelligence Surveillance and Reconnaissance (C4ISR) architecture, shall support a diverse set of operational conditions and concepts.

Operations are principally characterized by small units operating in a highly decentralized fashion. United States Special Operations Command (USSOCOM) personnel operate in all of the aforementioned environmental domains. They operate in restricted propagation environments such as dense urban areas, underground structures and in maritime vessels. Alternatively, USSOCOM can operate in isolated areas, distant from other friendly forces, and with no existing C4ISR infrastructure. When operating as 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 Next Generation Manpack Radio (NGMP)

The concept of employment for the NGMP is the same as for current manpack radios, e.g., the AN/PRC- 117G. The NGMP shall support simultaneous channel operation, with each channel capable of supporting both wideband Mobile Ad hoc Networking (MANET) waveforms and narrowband channels. An ISR video receive capability shall be included either integrated (Government preferred) into the NGMP or provided as a separate Mission Module (MM). If the ISR capability is integrated into the radio or provided as a MM, the NGMP shall support both channels and the ISR receiver simultaneously. The NGMP shall be optimized for use in a dismounted role with its primary source of power being battery. The NGMP 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.

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

2.1.1.2 Federal Standards

2.1.1.3 Military Standards

2.1.1.4 Military Handbooks

2.1.2 National Security Agency (NSA) Regulations and Specifications

2.1.3 Department of Defense (DOD) Standards and Specifications.

2.1.4 Other Government Documents, Drawings, and Publications.

Applications Program Interface Supplement to the SCA, 17 November 2001

Applications Program Interface Supplement to the SCA, 20 August 2015

2.2 Industry Standards

2.2.1 American National Standards Institute (ANSI).

2.2.2 Institute of Electrical and Electronic Engineers (IEEE).

2.2.2 International Telecommunications Union (ITU).

2.3 Order of Precedence

In the event of a conflict between this Specification and the aforementioned Standards and References, the Standards take precedence.

3.0 SYSTEM REQUIREMENTS

All requirements stated herein are Threshold (T) unless specifically identified as an Objective (O). However, some Threshold requirements are highlighted separately for purposes of clearly highlighting (T) vs (O) for certain capabilities. The Objective waveforms and capabilities identified in Appendix C are listed in descending order of importance.

3. 1 NGMP Description

3.1.1 NGMP System Components

The Major Components that shall be part of the NGMP kit include:

· Two Channel Receiver/Transmitter with integrated ISR receiver (Government preferred) or separate ISR MM

· Battery Box that holds either one rechargeable or one non-rechargeable battery that shall be able to provide the required power to both channels of the radio and separate MM

· One Accessory Pack/Carrying Case for the radio kit including the following ancillaries.

· A selection of Line-of-Sight (LOS) narrowband and wideband antennas that support any combination of wideband and narrowband channels operating simultaneously. The gain of the antennas should be as close to 0 dBi, or better, as possible. 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. Each NGMP channel shall be able to tune contiguously from 30 – 512 MegaHertz (MHz) and tune to waveform specific bands implemented in the radio from 512 MHz - 2,600 MHz.

· One Military Standard (MIL-STD) MOPP-IV H-250 Handset and one Lapel Speaker/Microphone

· One Red/Black USB cable and one Ethernet Interface Cable to connect to laptop, tablet, etc.

· One Unique 2 Channel Headset/Microphone assembly capable of connecting to the NGMP providing channel select transmit and receive functions for each channel separately and independently

· One Operator Manual, Laminated Quick Reference Guide and Inter-Active CD

3.1.2 Accessories

· Battery Eliminator providing power to the NGMP, via an Alternating Current/Direct Current (AC/DC) power source (9-32 VDC and 110-220 VAC, 50 to 440 Hz, when not configured in a Vehicle Mount System (VMS)

· Battery Adapter with NGMP interface cables to allow connection to various external battery power sources, e.g., conformal, BB-2590, and etc.

· PC Programming Software with PC to NGMP USB and Ethernet Cables

· Retransmission Cable

· Cloning Cable

· VMS Installation Kit, Mounting Brackets, Power Supply, 2 Channel High Power/Low Noise Amplifier, Cables, 2 Channel Powered Amplified Speaker, Antennas, Remote Control Unit w/Display capable of controlling both channels simultaneously

· Special Purpose Antenna Array for single-node Angle of Arrival (AOA) determination

3.2 NGMP Configuration Parameters

The NGMP shall completely load all required configuration files from cold (zeroized) to fully operational no longer than 10 minutes (T) / 7 minutes (O).

3.2.1 Unified Networking Configuration Tool

3.2.1.1 The NGMP is a network intensive radio with the ability to crossband in numerous different configurations; narrow band to wide band and wide band to wide band with many different possible combinations. It is imperative that the toolset used to configure the radios networking architecture is available as an application that is not web based and capable of operating standalone (no connection to a NGMP). The network configuration tool shall be capable of interfacing every waveform contained in the radio that is available for crossbanding in order to simplify the network configuration experience.

3.2.1.2 The only exception to this requirement is waveforms that are currently required to be configured through the use of the Joint Tactical Radio System (JTRS) Enterprise Network Manager (JENM) such as SRW, MUOS, and WNW. These waveforms must have a configuration file output from JENM that is easily importable into the Unified Networking Configuration Tool. All aspects of the radio configuration are configurable by a single user interface including SRW, MUOS, and WNW (O).

3.2.1.3 The user interface shall contain a topology view for network architecture planning. The tool shall present an in-depth plan validation upon completion while not only identifying errors, but also taking the user to the error. The user shall have the ability to accept the mission plan with errors if they choose to. The tool shall allow for offline manipulation of the mission plan that can be exported to the functional network. The tool shall allow for auto configuration of simple plans and detailed configuration of more complex plans. All configurations must be savable and exportable for archiving and reuse. All firmware upgrades shall come from OEM for any feature contained within the radio. The interface shall be loadable by Red USB and Red ETH (T). Must have the ability to build a functional mission profile and load it into in any position available for wideband communications (O).

3.2.2 Unified Radio Configuration Application

3.2.2.1 The NGMP application available to configure all aspects of radio that pertain to waveform communications to include any Mission Module shall be configurable from a single user web based interface. The only exceptions to the single configuration environment are waveforms currently configurable through JENM (SRW, MUOS, and WNW). The user interface shall have the ability to auto generate a comms wheel (a circular configuration diagram for each preset or waveform, e.g. if 16 configurations, there would be a circle with 16 descriptions and settings) for mission planning which shall allow for customizable fields to be arranged (Freq/Modulation/COMSEC/etc…).

3.2.2.2 The user interface shall contain a network mapping and monitoring capability similar in nature to SolarWinds. The interface shall allow for the auto generation of AES keys. The application shall allow for auto configuration of simple plans and detailed configuration of more complex plans. All date fields shall have a calendar pop up option eliminating formatting mismatches. All configurations must be savable and exportable for archiving and reuse. The application shall allow for seamless manipulation of radio presets (e.g. if changing preset 1 to 5 the program won’t move everything else around, it shall have arrow toggles to move presets up or down from their current position).. The interface shall be loadable by USB and Ethernet (ETH) (T). As an Objective the interface will be loadable by removable memory card and the Wideband Personal Area Network (WPAN) (O).

3.2.2.3 The single configuration environment shall have a user interface allowing on the fly configuration of features that are common to adjust during operation such as frequency, channel selection, cross banding capability, FMV distribution, and cyphertext mode.

3.2.2.4 The single configuration environment shall have an additional administrator/maintainer interface allowing full access to all features of the radio. This interface shall be available to any user on the fly while in operation as well as while offline. The requirement to enter this configuration mode shall be through either a username and password combination or a keypad sequence from the radio display either directly attached to the radio or by remote access.

3.3 NGMP Architecture

3.3.1 Software Communications Architecture (SCA)

The NGMP shall be compliant with the applicable Joint Tactical Radio System (JTRS) SCA specification(s), Version 2.2.2 (T), SCA 4.1 (O).

3.3.2 Hardware Architecture

3.3.2.1 The NGMP design approach shall implement industry Open Systems Architecture (OSA) standards and interfaces, and be designed to facilitate integration of Objective waveforms via software upgrade. The NGMP design approach shall implement OSA to enhance system interoperability and the ability to integrate new capabilities without redesign of entire systems or large portions of the system. The NGMP design approach shall adopt open standards supporting a modular, loosely coupled, and highly cohesive system structure that includes the publishing of key interfaces within the system and relevant design disclosure. At a minimum, the design approach shall comply with the Global Information Grid (GIG) Technical Guidance Federation, DoD Information Technology Standards Registry (DISR) On-Line dated 24 October 2014 and approved 13 December 2014.

3.3.2.2 Networking Architecture

3.3.2.2.1 The NGMP shall provide access control lists between data that traverses between wideband channels as well as Ethernet data links. The access lists shall be configurable to match an IP address and port number, IP address only, or port number only.

3.3.2.2.2 Routing protocols in the NGMP shall adhere to Internet Engineering Task Force standards.

3.3.2.2.3 The NGMP shall allow paths between wideband interfaces, such as wideband RF waveforms, to be configured as either routed or switched interfaces. In either case, the ability to apply access control lists shall be available.

3.3.2.2.4 The NGMP shall provide the capability to create static routes. Routes shall include the ability to modify the administrative distance. This would allow the administration of the routing metric to shape the traffic to where you want the traffic to basically go to (e.g., which gateway you want the traffic to flow to and stopping traffic going further in the network). Allows you to make manual pathing vs automatic pathing.

3.3.2.2.5 The NGMP shall adhere to Differentiated Services Field markings as per IETF RFC 2474.

3.3.2.2.5 The NGMP shall provide a dynamic host configuration protocol server with user configurable internet protocol scopes.

3.3.2.2.7 The NGMP shall provide the ability to modify the time to live of packets egressing an interface.

3.3.2.2.8 The NGMP shall provide for the reflection of multicast traffic to a different IP and Port number.

3.3.2.2.9 The NGMP shall provide for static Network Address Translation and Port Address Translation.

3.3.2.2.10 The NGMP shall provide for port overloaded Network Address Translation.

3.3.3 End User Device (EUD)

The NGMP shall be able to interface with a non-rooted, non-custom kernel EUD. The EUD shall require interfaces providing Internet Protocol (IP), serial, USB/USB "On the Go", or other protocols as determined to meet the NGMP threshold functionality requirements.

3.3.3.1 The NGMP shall provide an interface protocol to support control from the EUD, however, the user shall also have the ability to configure and control the NGMP via the 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 EUD in addition to a "packaged solution" (i.e. users have the option to include vendor-provided EUD device or utilize Government Furnished Equipment (GFE) EUDs and installing vendor-provided applications as required). The NGMP interface to the EUD shall provide the necessary support for EUD Tactical Assault Kit (TAK) applications (e.g., Windows TAK (WINTAK), Android TAK (ATAK), IOS TAK (ITAK)) and other third party applications through an open NGMP API to provide at a minimum, but not limited to, the following:

3.3.3.1.1 Configure/program/operate the NGMP to include placing the radio in standby or sleep/suspend mode.

3.3.3.1.2 View imagery received by NGMP and displayed on the EUD.

3.3.3.1.3 Overlay real time received Situational Awareness (SA)/Blue Force Tracking (BFT)/Position Location Information (PLI) onto a digital map displayed by the EUD.

3.3.3.1.4 Send/receive text messages; point-to-point or broadcast.

3.3.3.1.5 Share map overlays, routes, drawings, etc., with other users via the NGMP MANET.

3.3.3.1.6 Send text messages utilizing a voice-to-text mechanism (e.g. user speaks into the EUD and audio is converted to text and transmitted via the NGMP).

3.3.3.1.7 Place the NGMP in silent audio mode to allow the operator to view "closed-caption" text of received voice messages on a EUD.

3.3.3.1.8 Capture real-time video and simultaneously distribute the video via the NGMP MANET waveform either point-to-point or broadcast.

3.4 Channel Types

3.4.1 Channel Configuration and Definition

3.4.1.1 The NGMP shall have at least two configurable channels (each configurable for wideband or narrowband channels) and capable of supporting either two wideband waveforms, two narrowband waveforms or one wideband and one narrowband waveform simultaneously.

3.4.1.1.1 The radio shall also be capable of supporting both channels and the ISR receiver with crossbanding of the encrypted or unencrypted (bypass) ISR video to one of the two embedded wideband channels simultaneously.

3.4.1.2 The NGMP shall allow any channel configuration/reconfiguration within the specified combinations of waveforms identified in Table 3. When configured for two channel operation each channel shall operate independently and simultaneously with one another.

3.4.1.2.1 The device shall be able to use any combination of narrowband waveforms and wideband waveforms without any performance degradation or co-site interference with appropriate frequency management practices and utilization of appropriately filtered antennas.

3.4.1.2.2 The Government prefers a shared key concept where both channels can use the same Transmission Encryption Keys (TEK) without having to load the same TEK separately for each channel.

3.4.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 via the radio front panel or EUD.

3.4.1.4 A failure in one channel, e.g., power amplifier, shall not degrade the operation of the other channel(s) provided primary power is still being applied to the channel.

3.4.1.5 The NGMP 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) shall be visible on the device display and a connected EUD. The operator shall be able to enable or disable the audible alarm.

3.4.2 Guard Channels

3.4.2.1 The NGMP shall be able to receive and transmit on the international distress frequencies in both unencrypted beacon and voice modes.

3.4.2.2 Guard Mode Operations. The NGMP shall have a Guard mode of operation with the following characteristics:

3.4.2.2.1 The guard channel shall be selectable by front panel controls or via the remote control port.

3.4.2.2.2 The NGMP shall alternately monitor the guard channel when selected and operational communications channel/frequencies.

3.4.2.2.3 The NGMP shall monitor the main channel and the guard channel for a time duration sufficient to detect a signal on either channel but not to exceed 0.50 seconds when not in transmit or un-squelched receive.

3.4.2.2.4 The guard mode shall automatically tune the transmitter and the main receiver to the guard channel and disable the guard scan mode when receiving.

3.4.2.2.5 Scanning of the Guard channels shall stop when a signal is detected on the main channel or guard channel, or when the NGMP is transmitting.

3.4.2.2.6 Monitoring of the Guard channels shall resume within two to five seconds after the last reception or transmission.

3.4.2.2.7 Guard mode may occupy one of the two configurable channels in the NGMP.

3.4.3 Channel Scanning

3.4.3.1 The NGMP shall be able to establish a scan plan to monitor selected voice channels of interest (hostile or friendly). The NGMP shall scan predefined channels from 30 to 2,600 MHz.

3.4.3.2 The Scan capability of the NGMP shall have the following characteristics:

3.4.3.2.1 The NGMP shall monitor from 2 to 10 preset scan channels for a time not to exceed 0.50 seconds before moving to the next channel. Scanning shall cease when the device is transmitting or receiving.

3.4.3.2.2 The NGMP shall also be capable of general scan. In general scan, the frequency search criteria shall consist of a collection of frequency intervals, where the intervals are of a bandwidth that may be significantly larger.

3.4.3.2.3 If the transmit preset has not been entered for the channels being scanned, the operator cannot transmit on any channel being scanned and communications shall be limited to the scan channels only.

3.4.3.2.4 If a transmit preset has been entered for the channels being scanned, the operator can transmit on the scan channel in response to received signal.

3.4.3.2.5 If the NGMP is in Cipher Text (CT), and locks on a scanned channel that is in Plain Text (PT) mode, the scan function allows the operator to Push-To-Talk (PTT) on a PT channel even if the home channel is CT.

3.4.3.2.6 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.

3.4.3.2.7 Channel scanning shall resume within two to five seconds after the last activity on the primary communications channel.

3.4.3.2.8 The NGMP shall use the default 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.5 Multifunctional Capabilities:

3.5.1 Situational Awareness (SA) and Force Protection (FP)

The NGMP shall support multifunctional operations providing SA and FP. Compatibility and interoperability with other systems/devices such as tactical sensors shall provide rudimentary intelligence capabilities not found in current manpack radios. The NGMP shall be capable of receiving friendly/hostile signals and determining Line of Bearing (LOB) to Signals of Interest (SOI).

3.5.1.1 Provide detection and location of SOI at significantly relevant standoff distances.

3.5.1.2 Simple & Efficient user interface includes audible alert & visual indicators on the display or a separate tethered/connected display unit (laptop, tablet, etc.)

3.5.1.3 Relay relevant data via communications network for informational reporting or enhanced processing. The NGMP shall support single-node Angle of Arrival (AOA).

3.5.1.4 Improved Force Protection with enhanced situational awareness (early identification of potential threats).

3.5.1.5 Flexible mission planning with updates via keypad or PC download.

3.5.2 Situational Awareness

3.5.2.1 The NGMP shall be able to receive Full Motion Video (FMV) from platforms such as, Predator, Reaper, Gray Eagle, Shadow Tactical and other select Unmanned Aerial Vehicle (UAV) platforms, Apache and other select manned aircraft, as well as targeting pods (e.g., Sniper and Litening) in Standard Definition (SD) and High Definition (HD). This capability shall be comparable to and fully interoperable with the Remotely Operated Video Enhanced Receiver (ROVER) version VI (ROVER VI) and the Video Oriented Transceiver for Exchange of Information (VORTEX).

3.5.2.2 The NGMP shall be capable of presenting a SA picture on an external display such as a handheld or laptop computing device. As an Objective, the NGMP shall have a display that can project Position Location Information (PLI) in Military Grid Reference System (MGRS) format from the Mobile User Objective System (MUOS) and Netted Iridium networks (O).

3.5.3 Signals Based Threat Warning / Situational Awareness (SBTW/SA)

3.5.3.1 The NGMP shall be able to; scan, detect, intercept and recognize SOI transmitting on frequencies from 30 to 2,600 MHz (T). As an Objective (O) the SBTW/SA receiver shall operate in the background and not interfere with the simultaneous two channel operation of the NGMP. The NGMP shall also be able to transfer and relay these signals for further evaluation to a remote processing center. As an Objective, limited processing of such signals shall be done within the radio itself and displayed without being connected to an external device (O).

3.5.3.2 The NGMP shall include programmable on-board generic classifiers. For digital modulations these shall include the modulation type (e.g. M-ary PSK, M-ary QAM, and M-ary FSK), symbol rate, known signal (e.g. pre/mid/post ambles), and periodicity, at a minimum. Common analog modulations shall also be included (e.g. AM/ FM), including the ability to automatically tune.

3.5.3.3 The NGMP, when receiving an SOI, shall provide both an audio and visual alarm to the operator.

3.5.3.4 The NGMP shall, without external assistance be able to provide radio Direction Finding (DF) of SOI by combining LOB information and display it to the operator on the NGMP display or on a EUD.

3.5.3.5 It shall take no more than three NGMP 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.

3.5.3.6 The range and bearing information shall be shared among the NGMP devices with the location information presented on the EUD and the NGMP display. At a minimum, the data displayed shall include an estimated bearing and range from current position of the radio to the SOI.

3.5.3.7 The NGMP Interface Control Document (ICD), including pin outs, protocols, etc., shall provide the necessary information (hardware / electrical interfaces and software protocols) to allow for an external mobile device to display the location of other NGMP devices in the network, display the LOB data derived from the intercepted signal and the frequency / mode of the intercepted signal, Position Location Information (PLI), display the LOB data derived from the intercepted signal, the frequency / mode of the intercepted signal and any other data received and processed by the NGMP. The sharing of this data shall be accomplished on a prearranged narrowband or wideband (MANET) channel/frequency. The NGMP shall be able to intercept signals of interest across its entire tuning range (30 to 2,600 MHz).

3.5.4 ISR Video Receive Capability / Interoperability

The NGMP ISR capability shall be able to receive the waveforms and provide the performance as specified in Table 1 and compatible with NSA approved Suite A/B encryption. All specifications in Table 1 are considered Threshold (T) unless specifically identified as Objective (O).

Table 1 – ISR Video Receiver

UHF (O)

VNW: 5 Mbps and below (T) BE-CDL Rev B: 44 Mbps (T) Tactical 466ER: 466 kbps, 1.6, 3.2, 6.4 Mbps (O)

3.5.5 Intelligence, Surveillance & Reconnaissance (ISR)

3.5.5.1 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 unique ISR assets both in the unencrypted, US Type 1 (NSA approved ISR encryption, the Crypto Core Modernization (CCM) Generation 2 (KIV-700A)), the CCM-700, and commercial AES encrypted formats.

3.5.5.2 The NGMP, when configured with the ISR feature, shall be able to receive the ISR data and simultaneously distribute (crossband) the imagery over the NGMP MANET capability.

3.5.5.3 ISR video receive capability shall have the ability to encode video received from an analog data link. Encoded analog video source shall be able to be cross banded on to either NGMP channel.3.5.5.4 User shall be able to store the configuration of a data link as a preset with no more than three button presses (T), one button press (O) when a data link is detected on EUD and HMI.

3.5.5.4 User shall have the ability on the EUD or HMI to selectively flood data from ISR receiver or control, which streams pass when crossbanding is enabled if multiple video streams are detected.

3.5.6 Simultaneous Channel Operation

The NGMP shall support three primary functions simultaneously; any combination of narrowband and wideband waveforms as stipulated in paragraph 3.1.1 above as well as an ISR receiver that is crossbanding received data over one of the wideband channels.

3.5.6.1 The NGMP shall be able to crossband the ISR data onto the MANET and crossband the narrowband to narrowband, wideband to wideband and wideband to narrowband waveforms.

3.5.6.2 The NGMP shall be capable of dual-net operation where the operator shall be able to receive and transmit on two nets simultaneously.

3.6 Communications Range

3.6.1 NGMP Range

3.6.1.1 The NGMP shall have a minimum line of sight (terrain dependent) transmit/receive range of 8 Kilometer (km) (T) for the Land Mobile Radio (LMR), SINCGARS, Have Quick, and MANET waveforms. When the NGMP is installed in a platform with a High Performance Amplifier/Low Noise Amplifier (HPA/LNA) and higher gain antenna(s) it shall have a minimum transmit/receive range of 32 km for all narrowband waveforms

3.6.1.2 The NGMP shall have a minimum transmit/receive LOS range of 30 km (T), air to ground (Ultra High Frequency (UHF) band) with the aircraft at a height of 3,000 (T), feet for all the legacy narrowband and networking waveforms.

3.6.2 The NGMP when configured for UHF Satellite Communications (SATCOM), transmitting at 20 Watts, with a GFE UHF SATCOM antenna (minimum gain of +9 dBi), shall provide the necessary Effective Isotropic Radiated Power (EIRP) to meet link margin requirements contained in MIL-STD-188-181C/182B/183B).

3.6.3 As an Objective the NGMP in the dismounted profile, when configured for MUOS operation with its organic MUOS capable Omni-directional antenna, shall provide the necessary EIRP to meet link margin requirements contained in MIL-STD-188-187 while at the halt or on the move. The NGMP in dismount mode shall connect to the MUOS antenna with a single RF coaxial cable.

3.7 Interoperability

3.7.1 Legacy Devices

3.7.1.1 When the NGMP instantiates a waveform, it shall be over the air interoperable with legacy/current radios transmitting the same waveform. The NGMP shall be fully interoperable with the wideband MANET waveform (Tactical Scalable MANET-eXtreme (TSM-X)) provided with the Next Generation Handheld (NGHH) radio.

3.7.1.2 The functionality, performance, protocols, and interface controls of the NGMP shall be designed to minimize integration requirements with platforms and applicable operator training.

3.7.1.3 The NGMP 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.7.2 Land Mobile Radio (LMR) Interoperability

The NGMP shall be interoperable with commercial LMR and be compatible in the 136-174MHz, 403-470 MHz frequency range and 746-869 MHz with the full range of sub-audible tones, Continuous Tone-Coded Squelch System (CTCSS), required for interoperability with LMR commercial repeaters. APCO 25 Phase 1 and 2 (including Trunked Radio capability is required (T)).

3.8 Mobile Ad Hoc Networking (MANET) Waveforms

3.8.1 TSM-X

The NGMP primary MANET is TSM-X and it shall support multiple video streams, voice, and data and will be available to the user simultaneously or selectively at the user’s discretion, with the legacy narrowband capability. Users shall have the ability to connect to 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 100 nodes (no maximum number of nodes) with two video streams (either in HD or SD), voice and SA over the MANET network supporting a minimum of eight hops where bandwidth and throughput will adapt as shown in Table 2 “Data Rate.” Performance in restricted propagation environments and high multipath environments shall be implemented in the MANET solution.

3.8.1.1 The NGMP MANET shall provide a modulation scheme (Optimized Waveform for Restricted Propagation Environments) 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 tunnel including 90 degree turns. Operation within maritime vessels requires maintaining voice, video, and data between nodes within and external to a ship. Urban canyons criteria include maintaining voice, video, and data between nodes internal, and external to multi-story buildings.

3.8.1.2 The information contained in Table 2 and subsequent paragraphs represents the optimal features and specifications for the NGMP TSM-X MANET waveform. All values specified in Table 2 and subsequent 3.8.1.2.1 through 3.8.1.2.9 paragraphs are Threshold (T) unless otherwise identified as Objective (O).

Table 2 – MANET Performance