You are here

Military GNSS Data Server



OBJECTIVE: Develop a Military GNSS Data Service that gathers GNSS ephemeris, clock, health, status, and other key information, ensures the trustworthiness of the data, and is capable of delivering data to military data networks. 

DESCRIPTION: *** The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with section 5.4.c.(8) of the solicitation and within the AF Component-specific instructions. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws. Please direct questions to the AF SBIR/STTR Contracting Officer, Ms. Kristina Croake, * * * * * * * * * * * * * Traditionally, military users have relied on access to the navigation data message from the GPS signal in space to obtain current ephemeris, clock, satellite health, and other important data necessary for Positioning, Navigation, and Timing (PNT) from GPS. Due to the slow data rate of the Navigation Data Message (NDM) and an average age of data of 12 hours, the resiliency and performance of military receivers is actually, in some cases, worse than consumer devices. Billions of cell phones with inexpensive GPS chip sets benefit from Assisted GPS (A-GPS), which provides current ephemeris and timing data that enables rapid acquisition of the GPS signal and, in many cases, more accurate positioning and timing. No joint military A-GPS capability exists today. Typical Time-to-First-Fix (TTFF) requirements for military receivers are specified in tens of seconds or minutes, compared to less than 6 seconds for a typical A-GPS equipped cell phone. A key technical challenge is developing open data standards and interfacing with diverse DoD networks while providing a high degree of trust and resilience against cyberattacks. Additionally, as military users migrate to multi-GNSS, there is a need to provide near real-time notification of anomalies to users over available datalinks. The focus of this topic is developing a Military GNSS Data Service, drawing data from GPS and GNSS monitoring systems, suitable for integration with operational networks in an Area of Operations, that supports three enhancements to traditional satellite navigation. First, improved resiliency is obtained by assisted-GPS/GNSS data that improves initial synchronization performance. Second, enhanced accuracy is achieved by delivering Zero Age of Data (ZAOD) to the user, reducing the position and timing errors associated with satellite clock and ephemeris errors. Third, improved integrity is supported by providing users with near real-time notification of GPS or GNSS anomalies. Together, these capabilities provide a powerful enhancement to GPS and multi-GNSS use on the battlefield, leveraging existing tactical data links, and with little to no modification of military receivers. The primary goal of this effort is to develop the data service, including the architecture, protocols, interfaces, and information assurance features necessary to deliver trusted GNSS data to military users. Consideration should be given to extracting data from multiple monitoring sources such as the GPS control segment, National Geospatial-Intelligence Agency, the Jet Propulsion Laboratory, and other government and commercial sources. New monitoring stations are not within the scope of this topic, although leveraging new or emerging monitoring receiver and monitoring station initiatives is encouraged. The ultimate goal for a Military GNSS Data Service is a joint capability that services air, land, sea, space, and cyber domains. However, for this SBIR topic, demonstration of the capability for a single domain is acceptable, providing the solution is scalable to support diverse applications across all domains. 

PHASE I: Develop an architecture and preliminary design for a Military GNSS Data Service to support a single domain, with a plan for demonstrating the capability for a targeted application in Phase II. 

PHASE II: Implement and demonstrate a prototype Military GNSS Data Service for the targeted application, including GPS and Galileo data. The prototype should provide a real-time demonstration of the benefits of Military Assisted GNSS, including acquisition, accuracy, and integrity warning. 

PHASE III: Develop a Joint Military GNSS Data Service that supports multiple domains, and can be integrated into a theater command and control system. 


1. Van Diggelen, Frank, A-GPS: Assisted GPS, GNSS, and SBAS. Boston: Artech House, 2009.; 2. Vallina-Rodriguez N., Crowcroft J., Finamore A., Grunenberger Y., Papagiannaki K. When Assistance Becomes Dependence: Characterizing the Costs and Inefficiencies of A-GPS. SIGMOBILE Mob. Comput. Commun. Rev. 2013;17:3–14.; 3. DoD CIO, “Department of Defense Information Technology Environment,” August 2016.; 4. Djuknic, George M., Richton, Robert E., “Geolocation and Assisted GPS”, Communications, February 2001, PP 123-125.

KEYWORDS: GNSS Data Service, A-GPS, Alternate-GPS 

US Flag An Official Website of the United States Government