Atch_01_NGMP_PS_09June16.docx

PERFORMANCE SPECIFICATION

UNITED STATES SPECIAL OPERATIONS COMMAND

(USSOCOM)

For The Next Generation Manpack Radio

(NGMP)

09 June 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 in to 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.

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). 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 device kit:

· Two Channel Receiver/Transmitter with integrated ISR receiver 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.

· 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. The NGMP shall tune continuously from 30 – 2,600 MegaHertz (MHz).

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

· One USB and one Ethernet Interface Cables to connect to laptop, tablet, etc.

· 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 conformal external battery power sources, e.g., battery conformal NSN: 6140-01-622-5688, P/N: MB-CWB-150-1-LIT.

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

· Retransmission Cable.

· Cloning Cable.

· VMS Installation Kit, Mounting Brackets, Power Supply, Amplifiers, Cables, Antennas, Remote Control Device capable of controlling both channels simultaneously.

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

3.2 NGMP Architecture

3.2.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 or later.

3.2.2 Hardware Architecture

3.2.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.2.3 End User Device (EUD)

The NGMP shall be able to interface with a 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.2.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 the following capabilities:

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

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

3.2.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.2.3.1.4 Send/receive text messages; point-to-point or broadcast.

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

3.2.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.2.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.2.3.1.8 Capture real-time video and simultaneously distribute the video via the NGMP MANET waveform either point-to-point or broadcast.

3.3 Channel Types

3.3.1 Channel Configuration and Definition

3.3.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.3.1.1.1 The radio shall be capable of supporting both channels and the ISR receiver with crossbanding of the ISR video to one of the two embedded wideband channels simultaneously.

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

3.3.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.3.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.3.2 Guard Channels

3.3.2.1 The NGMP 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 NGMP shall have a Guard mode of operation with the following characteristics:

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

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

3.3.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.3.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.3.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.3.2.2.6 Monitoring of the Guard channels shall resume within two to five seconds after the last reception or transmission.

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

3.3.3 Channel Scanning

3.3.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.3.3.2 The Scan capability of the NGMP shall have the following characteristics:

3.3.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.3.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.3.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.3.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.3.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.3.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.3.3.2.7 Channel scanning shall resume within two to five seconds after the last activity on the primary communications channel.

3.3.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.4 Multifunctional Capabilities:

3.4.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.4.1.1 Provide detection and location of SOI at significantly relevant stand-off distances.

3.4.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.4.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.4.1.4 Improved Force Protection with enhanced situational awareness (early identification of potential threats).

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

3.4.2 Situational Awareness

3.4.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.4.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) and SA from the MUOS and Netted Iridium networks (O).

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

3.4.3.1 The NGMP shall be able to; scan, detect, intercept and recognize SOI transmitting on frequencies from 30 to 2,600 MHz (T). 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.4.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.4.3.3 The NGMP, when receiving an SOI, shall provide both an audio and visual alarm to the operator.

3.4.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 an EUD.

3.4.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.4.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.4.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.4.4 ISR Video Receive Capability / Interoperability

The NGMP ISR capability, when integrated into the NGMP as an optional feature, 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 and commercial encryption (FIPS 140-2). All specifications in Table 1 are considered Threshold unless specifically identified as Objective (O).

Table 1 – ISR Video Receiver

3.4.5 Intelligence, Surveillance & Reconnaissance (ISR)

3.4.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, e.g. Common Core) and commercial AES encrypted formats.

3.4.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.4.6 Simultaneous Channel Operation

The NGMP shall support three functions; any combination of narrowband and wideband waveforms as stipulated in paragraph 3.3.1.1 above as well as an ISR receiver.

3.4.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.4.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.5 Communications Range

3.5.1 NGMP Range

3.5.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, Second-Generation Anti-Jam Tactical UHF Radio for NATO (SATURN), 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.5.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.5.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.5.3 The NGMP in the dismounted profile, when configured for Mobile User Objective System (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.

3.6 Interoperability

3.6.1 Legacy Devices

3.6.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.6.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.6.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.6.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 2 and a Trunked Radio capability is desired (O).

3.7 Mobile Ad Hoc Networking (MANET) Waveforms

3.7.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.7.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.7.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 are Threshold (T) unless otherwise identified as Objective (O).

Table 2 – MANET Performance

3.7.1.2.1 PTT Voice over the Network desired features

Up to 16 independent digital voice channels using AMR 5.9All units with same TEK shall receive voice G.711 Codec for Radio-over-IP (RoIP) interoperability Session Initiation Protocol (SIP)

3.7.1.2.2 IP Data over the Network

Connects to external PC applications via Ethernet or USB Multicast any IP data – ideal for file transfer or streaming media Share data with anyone in your network Provide layer 2 network connectivity

802.11 a/b/g/n/ac AP compatible Integrated serial-to-Ethernet capability Cursor-on-Target (CoT) output Dynamic Link Exchange Protocol (DLEP) Certified Integrated DHCP server Advanced multicast algorithm Remote Driver Interface Specification (RNDIS)

3.7.1.2.3 Selecting Frequencies

Configurable to operate anywhere within 224-450 MHz and 1,300-2,600 MHz (T) 4,800-5,500 MHz (O).

Occupied bandwidth configurable from 1 to 40 MHz

3.7.1.2.4 Encryption

Top Secret and Below.

Over the air zero (OTAZ) Over the air rekey (OTAR) Set distinct encryption keys on each channel, voice only (T).

3.7.1.2.5 Security Features

Tamper detection Unit has certificates-based secure web services access (HTTPS)

3.7.1.2.6 Node Tactical Networking Configuration

Self-Configuring: Nodes automatically establish links on the move Self-forming: Units automatically join into a network Self-healing: adapt to network topology change without impact to active network traffic such as real time video (urban terrain, ship, caves, bunkers, mountain, desert, open ocean and jungle propagation challenged environments)

3.7.1.2.7 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

3.7.1.2.8 Global Positioning System (GPS)

Military Grid Reference System (MGRS) or LAT/LONG/ALT coordinate output Embedded SAASM receiver available through the NGMP or external receiver Real Time network PLI tracking

3.7.1.2.9 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 Graphically displayed network monitoring

3.7.1.2.10 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.1.2.11 Operate as Standalone or Member Device

3.7.1.2.11.1 Standalone: The NGMP shall function as legacy narrowband LOS and Beyond-Line-of-Sight (BLOS) secure/non-secure voice and data communications systems. The NGMP shall support LOS and/or BLOS range extension and BLOS to LOS relay/retransmission.

3.7.1.2.11.2 Member: The NGMP and shall function as a member or master station in the establishment and participation in a secure (Suite A & B) and non-secure MANET network. The network shall be capable of distribution of tactical SA information between and among all members.

3.7.1.2.11.3 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.1.2.11.4 Multicast: The NGMP shall be capable of joining shared networks and distributing and receiving multicast traffic. The MANET shall support multicast video distribution, full motion video, voice, & data; provide tactical Situational Awareness (SA) and cursor on target (CoT) capabilities.

3.7.1.2.11.5 Internet Protocol: The NGMP shall support IP Versions 4 and 6 (IPv4/6)) with the implementation supporting Unicast (point-to-point) and Multicast (communications with multiple members of a device group).

3.7.1.3 Network Management

3.7.1.3.1 Planning: The NGMP 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.

3.7.1.3.2 Execution: System management software shall be provided that performs all NGMP 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.1.3.3 Simple Network Management Protocol Version 3 (SNMPv3): The SNMPv3 as an interoperable standards-based protocol for network management interface shall be implemented in the NGMP.

3.7.2 Soldier Radio Waveform (SRW)

The NGMP shall support all of the mandatory SRW implementation requirements. The SRW shall be integrated into the NGMP in Soldier System Domain Combat Communications (SS/CC) mode (JTN SRW v1.01.1, or later).

3.7.3 Wideband Networking Waveform (WNW)

The NGMP will support all the mandatory requirements for implementing WNW as required for both dismounted and vehicle mounted platforms (O). The WNW may be provided as a Mission Module or integrated into the NGMP.

3.8 Waveform Requirements

3.8.1 Waveform Selection

3.8.1.1 The NGMP 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 in place to prevent instantiating a waveform to an improperly configured channel.

3.8.1.3 The NGMP shall allow operators/platforms to access and edit operating parameters loaded in the radio.

3.8.1.4 The NGMP shall support the waveform capabilities identified below. The NGMP shall support simultaneous two channel operation and the ISR receiver as described in paragraph 3.3.1.1 using any combination of the narrowband and wideband waveforms. NGMP Threshold waveforms are identified in Table 3 and the Objective waveforms are identified in Table 4. Those Threshold and/or Objective waveforms that may be integrated into the radio, provided as an embedded but removable MM, or provided as an attachable MM are indicated by an asterisk (*).

Table 3 – Threshold NGMP Waveforms Threshold Waveforms

Table 4 – Objective NGMP Waveforms

3.8.2 Retransmission, Routing, and Crossbanding

3.8.2.1 The NGMP shall have a black retransmit capability and shall provide the physical and electrical interfaces to support narrowband retransmission/relay operations with another like device. The NGMP shall support wideband retransmission/relay operations between two radios one of which supporting TSM-X and the other supporting SRW.

3.8.2.2 The NGMP shall be able to crossband the ISR data over to the MANET channel and be able to crossband all narrowband to narrowband, narrowband to wideband and wideband to wideband waveforms.

3.8.3 Waveform Storage

3.8.3.1 All waveforms configured in a NGMP shall be down-loadable, locally or over the air, and stored in non-volatile memory.

3.8.3.2 The NGMP 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 NGMP shall each be able to store and instantiate all of the Threshold waveforms specified in Table 3.

3.8.4 Additional Waveform Descriptions

3.8.4.1 Advanced Special Communications Mode (ASCM) Enhanced

The NGMP utilizing ASCM shall be able to communicate in the presence of Improvised Explosive Devices (IED) jammers in narrowband LOS and BLOS modes.

3.8.4.2 MUOS

3.8.4.2.1 The NGMP shall comply with MIL-STD-188-187 regarding the MUOS Common Air Interface (CAI)…