Description
CNAV, or Civil Navigation, is a standardized service within 3GPP that facilitates the delivery and processing of civil navigation data, such as from Global Navigation Satellite Systems (GNSS) like GPS, Galileo, GLONASS, and BeiDou, over mobile networks. It operates as part of the positioning framework, where the network assists user equipment (UE) in acquiring and interpreting satellite signals to determine geographic location. The architecture involves components like the Location Management Function (LMF) in 5G or the Enhanced Serving Mobile Location Centre (E-SMLC) in LTE, which generate assistance data—including ephemeris, almanac, and timing information—and transmit it to UEs via control plane or user plane protocols. This assistance reduces the Time to First Fix (TTFF) and improves accuracy, especially in challenging environments like urban canyons or indoors where satellite signals are weak.
In terms of how it works, CNAV leverages specifications such as 3GPP TS 36.355 for LTE Positioning Protocol (LPP) and TS 37.355 for NR Positioning Protocol (NRPP), which define the messages exchanged between the UE and network for positioning. The UE requests or receives unsolicited assistance data, processes it to correlate with received satellite signals, and computes its position using methods like Assisted GNSS (A-GNSS). Key components include the UE's GNSS receiver, the network's positioning server (e.g., LMF), and interfaces like the LTE Positioning Protocol Annex (LPPa) for communication between network nodes. CNAV's role is to enable efficient, network-aided positioning that enhances performance beyond standalone GNSS, integrating seamlessly with cellular connectivity for real-time location services.
The service supports various positioning techniques, including A-GNSS, Observed Time Difference of Arrival (OTDOA), and Enhanced Cell ID (E-CID), with CNAV focusing on the GNSS aspects. It includes features like real-time integrity monitoring, where the network can provide data on satellite health or errors, and support for multiple constellations to increase robustness. In 5G systems, CNAV evolves with New Radio (NR), incorporating higher accuracy requirements for applications like autonomous vehicles and industrial IoT. The integration with network slicing allows tailored positioning services for different use cases, ensuring low latency and high reliability. Overall, CNAV is a foundational element in 3GPP's positioning ecosystem, bridging satellite navigation and mobile communications to deliver ubiquitous location awareness.
Purpose & Motivation
CNAV was created to address the need for reliable, accurate, and fast positioning services in mobile devices, leveraging the widespread deployment of GNSS. Prior to its standardization, standalone GNSS receivers in phones often suffered from long acquisition times, poor performance in signal-challenged areas, and high power consumption. By integrating civil navigation data into 3GPP networks, CNAV solves these issues by providing network assistance that reduces TTFF, enhances accuracy in urban or indoor environments, and conserves device battery life through optimized signal processing. This was motivated by growing demand for location-based applications, regulatory requirements for emergency caller location (e.g., E911 in the US), and the expansion of IoT services requiring precise tracking.
Historically, early mobile positioning relied on network-based methods like Cell ID, which offered limited accuracy. The introduction of CNAV in 3GPP Release 8 marked a shift towards hybrid approaches, combining GNSS with cellular assistance to meet stricter accuracy mandates. It addressed limitations of previous approaches by standardizing protocols for assistance data delivery, enabling interoperability across devices and networks, and supporting multiple GNSS constellations for global coverage. Over releases, CNAV has evolved to support emerging needs such as high-accuracy positioning for automotive and industrial use, driven by advancements in satellite technology and 5G's low-latency capabilities. Its purpose extends beyond basic navigation to enable critical services like emergency response, logistics optimization, and location-aware computing in the modern connected world.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the CNAV (OTDOA) function was enhanced with the introduction of IMU (Inertial Measurement Unit) support for OTDOA positioning. It also introduced the OTDOA Assistance Data Request procedure for NR (New Radio) and added the TDD UL/DL configuration to the OTDOA assistance data. Furthermore, the release included signaling clarifications and corrections for capabilities and SFN (System Frame Number) handling within the OTDOA framework.
In Release 16, the CNAV function was enhanced through updates to A-GNSS assistance data for the BDS system, specifically by introducing support for the new B1C signal and updating the B1I signal to its ICD version 3.0. The release also introduced support for Inertial Measurement Unit (IMU) integration to aid OTDOA positioning and added the capability to signal TDD UL/DL configuration within OTDOA assistance data. Furthermore, it included corrections and clarifications to OTDOA parameters, capabilities, and the SFN timestamp within Signal Measurement Information.
In Release 17, the key new development for the CNAV function was the introduction of support for Inertial Measurement Unit (IMU) data to enhance OTDOA positioning. This was complemented by the addition of OTDOA assistance data request procedures specifically for NR (New Radio) and the inclusion of TDD UL/DL configuration within the OTDOA assistance data. Furthermore, the release introduced new OTDOA capabilities and provided clarifications and corrections to various OTDOA parameters and signaling procedures.
- Clarifying Galileo NAV message in the GNSS Navigation model to clarify SSR clock correction signal reference TS 37.355CR0412
In Release 18, the CNAV (A-GNSS) function introduced corrections to the signaling support for GNSS almanac and UTC model parameters in assistance data. These updates specifically refined the **GNSS-AlmanacSupport** and **GNSS-UTC-ModelSupport** information elements to ensure greater accuracy and reliability for assisted satellite-based positioning.
- Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning TS 37.355CR0518
In Release 19, the CNAV (Civil Navigation) function introduced support for new global navigation satellite systems within the A-GNSS framework. Specifically, this included the introduction of NavIC L1 SPS for A-GNSS in the LPP protocol and the addition of the B2b signal for the BDS system in A-GNSS. These enhancements expanded the constellation signals available for assisted positioning without introducing changes to the existing OTDOA procedures detailed in the grounding context.
Explore further
Broader topics and technologies where CNAV plays a role.
Defining Specifications
3GPP specifications that define or reference CNAV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 44.031 vj00 | Radio Resource LCS Protocol (RRLP) | Rel-19 |