Description
Network Provided Location Information (NPLI) refers to the architectural paradigm and set of functionalities where the cellular network infrastructure is responsible for estimating the geographical position of a User Equipment (UE). Unlike UE-based or UE-assisted methods where the mobile device plays an active role in the positioning calculation (e.g., using embedded GPS), in NPLI the network acts as the primary computing entity. The core network entity that orchestrates this service is the Gateway Mobile Location Centre (GMLC), which interfaces with the UE's serving core network nodes (like the MSC or MME) and positioning systems in the Radio Access Network (RAN).
The technical process begins when a Location Service (LCS) client—which could be an external application, an emergency services network, or a network operator's own service—sends a location request to the GMLC. The GMLC authenticates the client and determines the serving node for the target UE. It then forwards the request to the appropriate node (e.g., MSC for circuit-switched, MME for packet-switched). This node, in conjunction with the RAN (e.g., a Base Station Controller (BSC) or an evolved NodeB (eNB)), initiates the positioning procedure. The network collects necessary measurements without relying on the UE's computational capabilities for the final fix.
Key positioning methods under the NPLI umbrella include Cell-ID (the simplest form, providing the location of the serving cell), Timing Advance (TA), Uplink Time Difference of Arrival (U-TDOA), and Enhanced Cell ID (E-CID) which combines cell identity with timing, angle, and power measurements. For U-TDOA, specialized Location Measurement Units (LMUs) in the network measure the time of arrival of signals from the UE at multiple points. All measurement data is sent to a central node, often a Serving Mobile Location Centre (SMLC) or an Evolved SMLC (E-SMLC) in the RAN, which calculates the position estimate using algorithms like multilateration. The calculated location (latitude, longitude, and uncertainty) is then routed back through the core network to the authorized LCS client. This architecture ensures location services work even for UEs without GPS capability and provides a network-controlled mechanism vital for regulatory services like emergency caller location.
Purpose & Motivation
NPLI was developed to meet critical requirements for determining a mobile subscriber's location independently of the capabilities or cooperation of the handset. The primary drivers were regulatory mandates for emergency services (such as E911 in the USA and E112 in Europe) and the commercial need for location-based services (LBS) like fleet tracking, navigation, and location-aware advertising. Prior to standardized network-based positioning, location could only be roughly estimated by the serving cell site, which was insufficient for emergency response where a caller might be unable to provide their location verbally.
The creation of NPLI addressed the limitation of relying solely on handset-based GPS, which was not universally available, could be disabled by the user, and often performed poorly indoors or in urban canyons. A network-centric solution ensures that the operator can fulfill its regulatory obligation to provide caller location for emergency services for *all* handsets on its network, regardless of their make, model, or feature set. It also provides a reliable fallback or supplement to UE-based methods.
Furthermore, NPLI enables network operators to maintain control and ownership of the location data, creating a service platform for third-party LCS clients. It solves the problem of providing location for services where the end-user's explicit consent or device interaction might not be feasible or desired, such as in asset tracking for logistics or certain lawful interception scenarios. The standardization in 3GPP, particularly from Release 11 onwards with enhanced LTE positioning, provided a unified, interoperable framework for NPLI across global networks, moving beyond vendor-specific implementations.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (76 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-11, normative work from Rel-15.
In Release 15, the primary enhancement for the Network Provided Location Information (NPLI) function involved clarifications. These clarifications specifically addressed the procedures for deriving location information and delivering it.
- Clarifications on the Location information derivation and delivery TS 33.128CR0020
In Release 16, enhancements to NPLI focused on improving location reporting procedures and binding information. Specifically, the release introduced enhanced AMF location update reporting with Dual Connectivity and provided additional details on location updates at the AMF. It also clarified procedures for LMF and GMLC event reporting and updated binding information to include the PCF set ID and PCF instance ID.
- Annex B, IMS Session Modification, provisioning of service information TS 29.513CR0113
- Annex B, Provisioning of SIP signalling flow information at IMS Registration TS 29.513CR0117
- Correction to binding information procedures TS 29.513CR0140
- Binding information: PCF set ID and PCF instance ID TS 29.513CR0148
- Binding of PCC rules to a QoS flow considering TSCAI information TS 29.513CR0150
- Update Serving System and support of Subscriber Record Change and Cancel Location (x)IRIs TS 33.128CR0147
+ 4 more changes
In Release 17, the NPLI function was enhanced with clarifications and updates to procedures including the subscription procedure, location reporting, and ID mapping for location delivery. Specific technical improvements included enabling the retrieval of NPLI within a MESSAGE request, aligning packet header information reporting across stage 2 and stage 3 specifications, and providing clarifications for location translation and the payload direction field. Furthermore, updates were made for alignment on N3GPP access location and to the default behavior for the Location Type at the MDF.
- Update of binding information subscription procedure TS 29.513CR0347
- Separated Location Reporting TS 33.128CR0273
- Clarification on ID Mapping Location Delivery TS 33.127CR0107
- Correction to enable retrieval of Network Provided Location information in a MESSAGE request TS 29.513CR0335
- BSF storage information for TSC TS 29.513CR0354
- Update of stage 2 language for packet header information reporting TS 33.127CR0144
+ 6 more changes
In Release 18, the NPLI function was expanded with new capabilities including support for location acquisition interfaces for the EPC and alignment between 5G and EPC procedures, as well as location-only reporting for EPS. It also introduced new reporting types such as Cell Site Information for IQF responses, a new location type for IMS, and the addition of Access Network Information to IMS records. Furthermore, the release added features for intermediate location LALS, location reporting for Identity Association Records, and support for NTN-related information.
- Completion of LBO roaming information TS 29.513CR0515
- Procedures update for checking mechanism of clock quality information received from UDM and AF TS 29.513CR0536
- Location acquisition architectures TS 33.127CR0176
- Support of location information request for both T2P and P2T requests in alignment with TS 33.128 TS 33.127CR0180
- Location acquisition interfaces for the EPC TS 33.127CR0206
- Intermediate Location LALS TS 33.127CR0210
+ 36 more changes
In Release 19, the NPLI function was enhanced with new capabilities for acquiring location based on measurement reporting and for incorporating richer radio information, including the addition of Cell Radio Information and coarse location to location structures. It also expanded support for integrated access and backhaul (IAB) networks by defining the transport of extra IAB information and a Mobile IAB Authorized Indicator in key procedures. Furthermore, the release introduced support for Non-3GPP device information handling and the proxying of information via the LIPF from the LICF.
- Support of Non-3GPP device information handling procedures TS 29.513CR0599
- Location acquisition based on measurement reporting TS 33.127CR0241
- Extra IAB information in stage 2 related to Downlink NAS transport and to UE CONTEXT MODIFICATION REQUEST TS 33.127CR0255
- Location acquisition based on measurement reporting TS 33.128CR0664
- Mobile IAB Authorized Indicator and UE differentiation information in Initial Context Setup Request, NAS transport initial Information with mobile IAB TS 33.128CR0678
- Addition of Cell Radio Information to location structures TS 33.128CR0701
+ 5 more changes
Explore further
Broader topics and technologies where NPLI plays a role.
Defining Specifications
3GPP specifications that define or reference NPLI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 23.842 vb00 | NPLI Architecture Study for IMS | Rel-11 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.128 vj50 | 3GPP TS 33.128: Lawful Interception Protocols | Rel-19 |