Description
Network – Real-Time Kinematic (N-RTK) is a positioning service standardized by 3GPP that delivers Real-Time Kinematic correction data from a network server to User Equipment (UE) to achieve centimeter-level positioning accuracy. Unlike standalone GNSS (Global Navigation Satellite System) which provides meter-level accuracy, RTK corrects for errors like satellite orbit and clock inaccuracies, ionospheric delays, and tropospheric delays by using a reference station at a known location. The N-RTK service integrates this correction data delivery into the mobile network architecture, allowing UEs to receive corrections via control or user plane protocols, typically using LPP (LTE Positioning Protocol) or its NG-RAN counterpart in 5G. The service involves a Location Management Function (LMF) or an equivalent positioning server that obtains RTK correction streams from reference networks or service providers and formats them for transmission to the UE.
The architecture of N-RTK involves several key components: the UE with GNSS and RTK-capable receiver, the Radio Access Network (RAN – LTE or 5G NR), the core network elements (like the Mobility Management Entity (MME) in LTE or Access and Mobility Management Function (AMF) in 5G), and the positioning server (e.g., LMF or E-SMLC). The positioning server acts as the gateway between the RTK correction infrastructure (often external networks like CORS – Continuously Operating Reference Stations) and the mobile network. It authenticates the UE, determines its approximate location to select appropriate correction data (since corrections are spatially correlated), and delivers the corrections efficiently, considering bandwidth and latency requirements. The corrections can be broadcast to multiple UEs in an area or delivered via unicast sessions tailored to individual UE requests.
N-RTK works by establishing a positioning session initiated by the UE or network. The UE indicates its capability to support RTK in positioning capabilities exchanged with the network. Upon request, the positioning server acquires RTK correction data relevant to the UE's coarse location (derived from cell-ID or other methods). These corrections, which include measurements like carrier-phase corrections and code-phase corrections, are transmitted to the UE over the cellular link. The UE then applies these corrections to its own GNSS measurements (e.g., from GPS, Galileo, BeiDou) in real-time, performing double-difference calculations to eliminate common errors and compute its precise position. The service supports various RTK formats and can adapt correction delivery based on UE mobility and accuracy requirements.
In the network, N-RTK plays a critical role in enabling high-accuracy location-based services (LBS) for 5G and beyond. It is part of the broader 3GPP positioning framework that includes other methods like OTDOA, A-GNSS, and sensor-based positioning. By integrating RTK into the network, 3GPP allows mobile operators to offer premium positioning services without requiring UEs to have direct internet connectivity to external RTK services, ensuring reliability, security, and quality of service. The service is defined in both LTE (E-UTRA) and NR contexts, with specifications covering procedures, signaling, and data formats to ensure interoperability across generations.
Purpose & Motivation
N-RTK was introduced to address the growing demand for high-precision positioning in commercial and industrial applications where meter-level GNSS accuracy is insufficient. Prior to its standardization, high-accuracy positioning relied on proprietary or industry-specific RTK systems that required dedicated receivers, direct connections to reference stations via radio links (e.g., UHF), or internet-based NTRIP (Networked Transport of RTCM via Internet Protocol) streams, which were not optimized for mobile cellular environments. These approaches often suffered from limited coverage, high cost, complex setup, and lack of integration with mobile network authentication and billing systems.
The creation of N-RTK within 3GPP was motivated by the emergence of use cases like autonomous vehicles, drone navigation, precision agriculture, and augmented reality, which require continuous, reliable, and centimeter-accurate positioning. By leveraging the existing cellular infrastructure, N-RTK provides ubiquitous coverage, seamless mobility support, and inherent security through network authentication. It solves the problem of delivering RTK corrections efficiently over wide areas without requiring additional hardware on the UE beyond a capable GNSS chipset, enabling mass-market adoption of high-accuracy positioning.
Historically, RTK was primarily used in geodesy, surveying, and construction. 3GPP's standardization in Release 15 integrated it into the mobile ecosystem as part of the 5G positioning enhancements, recognizing that future services would depend on precise location. N-RTK addresses limitations of previous A-GNSS (Assisted GNSS) which only improved time-to-first-fix and sensitivity but not absolute accuracy. It also complements other 3GPP high-accuracy methods by providing a standardized network delivery mechanism for correction data, ensuring interoperability across operators and device manufacturers.
Key Features
- Delivers real-time GNSS correction data (e.g., RTCM format) via cellular network to UE
- Enables centimeter-level positioning accuracy in suitable conditions
- Supports both LTE and 5G NR access technologies through unified positioning protocols
- Integrates with 3GPP positioning architecture (LMF/E-SMLC) for session management
- Provides unicast and potential broadcast delivery modes for correction data
- Includes support for various GNSS constellations (GPS, GLONASS, Galileo, BeiDou)
Evolution Across Releases
Introduced N-RTK as part of the 5G positioning framework. Defined initial architecture integrating RTK correction delivery via the LMF (Location Management Function) in the 5G core network. Specified support in both LTE (via E-UTRA) and NR using enhanced LPP protocol for transporting correction data.
Defining Specifications
| Specification | Title |
|---|---|
| TS 36.305 | 3GPP TR 36.305 |
| TS 38.305 | 3GPP TR 38.305 |