Credit: Lisa Perdue, Orolia
WHAT'S THE DEAL?
M-Code – it is here. Public Law 111-383, Section 913 requires all military GPS user equipment purchased after FY 2017 to be M-Code capable, unless a waiver is issued the Secretary of Defense.
With Military GPS User Equipment (MGUE), or M-Code receivers, becoming available to vendors, now is the time to start getting serious about integration and performance testing of MGUE and systems that rely on it.
Currently there are two GPS security architectures – and both are available only to authorized users. The first, Selective Availability Anti-Spoofing Module (SAASM), has been required for all newly fielded DoD GPS systems as of October 2006. It uses the GPS Precise Position Service, which is provided using encrypted signals (P(Y) Code) on two frequencies – L1 (1575.42MHz) and L2(1227.6MHz).
MGUE is the second one, utilizing the M-Code signals. As one aspect of the GPS modernization program, M-Code is also an encrypted signal provided on L1 and L2 frequencies.
M-CODE ENABLED TIMING & SYNC SOLUTIONS
Flexible, Resilient PNT for Every Environment
• M-Code capabilities for SecureSync® DISA approved time server
• Versa mobile PNT platform for rugged, small SWaP-C requirements
• Improved resistance to jamming and interference
• Advanced security features
• More accurate performance
Orolia offers an easy, cost-effective upgrade from SAASM to M-Code.
The Versa Platform supports M-Code for mobile military missions.
WHAT IS MNSA?
M-Code includes new cryptography: Modernized Navstar Security Algorithm (MNSA), to ensure the system is secure. The key management has been designed to make the system easier to use and manage by the end users. The encrypted details are kept very restricted and are not available to most people. MNSA M-Code is currently being transmitted on 19 satellites today, and MGUE is available from several providers, so let’s get started!
Advanced Encryption Standard
Simulator Data Set
Modernized Navstar Security Algorithm
M-CODE TESTING METHODS
Before today, other test methods were necessary to allow users to integrate the MGUE without access to MNSA information.
AES M-Code – Rather than using the MNSA encryption, it is possible to use a known AES encryption method for testing purposes only. This method is useful to test integration, performance and specific user scenarios in an unclassified setting.
M-Code SDS – Simulator Data Sets are signals created with MNSA for replay in authorized simulators. The simulator vendor does not need to know the MNSA methods to incorporate the SDS into their simulators. This method is useful for testing the security algorithms and is a replay of already created data, so no user inputs are specified.
MNSA M-Code – Full testing of both the performance and the security features of the MGUE are possible. The user has full control over scenario settings with the real encryption used on the M-Code signal. This method is developed by simulator manufacturers with cooperation of the SMC Production Corps. It is only available to authorized users.
THE REAL-DEAL FOR SIMULATION
BroadSim MNSA is a fully flexible implementation of the Modernized NavStar Security Algorithm. Any aspect of your scenario can be changed, such as time, date, location, constellation, downlink data, signal configuration, and visible satellites.
BroadSim MNSA is compatible with all of the existing capabilities that the Skydel simulation engine supports – including jamming, spoofing, and more. No additional hardware is required.
Approved by the SMC Production Corps.