Location Application Function

Description

The Location Application Function (LAF) is a network function defined within the 5G core network's Service-Based Architecture (SBA). It resides in the service exposure layer and acts as the primary interface for authorized external Application Functions (AFs) or third-party application servers to request location information for User Equipments (UEs). The LAF provides a standardized, secure API (often based on HTTP/2 and JSON) through which applications can submit location requests, such as for a single immediate location fix or for periodic or triggered location reporting. It is a key component of the Location Services (LCS) architecture, translating application-level location service requests into network-specific procedures.

Architecturally, the LAF interacts with other core network functions to fulfill location requests. Its main counterpart is the Gateway Mobile Location Centre (GMLC), which is the traditional core node for location services. In 5G, the LAF typically communicates with the GMLC using the standardized Le interface or its service-based equivalent (e.g., Nlg interface). The LAF may also interact with the Network Exposure Function (NEF) for policy enforcement, authentication, and authorization of the external application's request. The LAF handles aspects like validating the application's subscription, checking privacy regulations (e.g., user consent via the GMLC), and managing the location request session.

How it works involves a sequence of steps. First, an external AF sends a location request to the LAF's API, specifying parameters like the target UE identifier (e.g., MSISDN, External Identifier), required QoS (e.g., accuracy, response time), and type of service (e.g., immediate, deferred). The LAF authenticates the AF and authorizes the request. It then forwards the request to the GMLC. The GMLC interacts with the UE's serving AMF and, ultimately, location determination functions in the Access Network (e.g., using LTE Positioning Protocol (LPP) via the AMF and NG-RAN) to obtain the location estimate. The resulting location data (e.g., geographic coordinates) is routed back through the GMLC to the LAF, which formats and delivers it to the requesting external AF.

Key components of the LAF include its service-based interface (e.g., Nlaf), its logic for request session management, and its integration with the NEF for exposure security. The LAF's role is to abstract the complexities of the underlying network location technologies (e.g., GNSS, OTDOA, E-CID) from the application, providing a simple, web-friendly API. This enables a wide range of services, including emergency caller location (E911/E112), location-based charging, fleet management, and personalized services. It plays a critical role in making 5G network capabilities, specifically precise location, securely available to the application ecosystem.

Purpose & Motivation

The LAF was created to modernize and standardize how external applications access mobile network location services. In pre-5G architectures, location services for applications were often provided through proprietary or legacy interfaces to the GMLC, which could be complex and lack the flexibility required for modern cloud-native applications. The proliferation of IoT and advanced location-based services demanded a more agile, API-driven approach.

The introduction of the LAF in the 5G SBA addresses this by providing a dedicated, service-based function for application exposure of location services. It solves the problem of tight coupling between applications and network-specific protocols. By offering a RESTful or HTTP/2-based API, it allows application developers to easily integrate location capabilities without deep knowledge of telecom protocols. Furthermore, it centralizes authentication, authorization, and policy control for location requests through integration with the NEF, enhancing security and privacy compliance. This evolution supports the 5G vision of network programmability and service exposure, enabling new business models and efficient support for critical services like enhanced emergency services.

Key Features

• Provides standardized API (e.g., RESTful/HTTP2) for external applications to request UE location
• Integrates with the Gateway Mobile Location Centre (GMLC) to execute location procedures
• Supports various location request types: immediate, periodic, and triggered
• Enforces application authentication, authorization, and privacy policies (often via NEF)
• Abstracts underlying network positioning technologies from applications
• Enables emergency services, lawful intercept, and commercial LBS applications

Evolution Across Releases

Defining Specifications