Network Provided Location Information

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.