Description
A Local service (also called Localized service) is a 3GPP Rel-18 concept defined in TR 23.700-08 as a service that is localized — i.e., provided at a specific or limited area — and/or can be bounded in time. The service may be realized via applications (such as live or on-demand audio/video streaming, electronic gaming, or IMS) or via connectivity (such as UE-to-UE communication or UE-to-Data Network connectivity). This definition captures a broad class of services whose value depends on being delivered close to the user or within a constrained temporal window.
Architecturally, local services leverage the 5G System's edge computing capabilities, including Edge Application Server (EAS) discovery, Local Area Data Network (LADN) support, and User Plane Function (UPF) deployment at the network edge. The service is anchored to a specific geographic area or network slice, and the network must ensure that the UE is served by an appropriate edge application instance or local data path. The 5G Core (5GC) uses mechanisms such as DNAI (Data Network Access Identifier) and traffic influence procedures to steer traffic to local application instances. Time-bounded aspects may be enforced through session management policies, QoS flow timers, or application-level scheduling.
Key components include the Policy Control Function (PCF) which provides area and time constraints, the Session Management Function (SMF) which selects UPF and enforces local breakout, and the Network Exposure Function (NEF) which exposes service-specific capabilities to application functions. The UE may also be configured with local service area information via the Access and Mobility Management Function (AMF). Security considerations are addressed in TR 33.858, covering authentication and authorization for local service access, privacy of location information, and protection of edge application traffic.
In operation, when a UE requests a local service, the network verifies the UE's location and time constraints, selects an appropriate edge application server or local UPF, and establishes a PDU session with local breakout. The service may be delivered via unicast, multicast, or broadcast depending on the application. For UE-to-UE local services, the network may use direct device-to-device communication or a local UPF anchor. The service can be bounded in time by session duration limits or by scheduled availability windows.
Local services are significant because they enable low-latency, high-bandwidth applications that cannot tolerate backhaul to a centralized data center, and they support emerging use cases such as immersive gaming, live event broadcasting, and industrial IoT within a campus. They also provide a standardized framework for operators to offer localized connectivity and application hosting as a commercial service.
Purpose & Motivation
Local services exist to address the need for low-latency, high-bandwidth, and location-specific applications that cannot be efficiently served by centralized data networks. Traditional mobile networks route all traffic through a central core, which introduces latency and backhaul costs unsuitable for real-time interactive services like cloud gaming, live video, or local industrial control. By defining local services, 3GPP provides a standardized way to deploy application and connectivity services at the network edge, close to the user.
The concept also addresses time-bounded services, such as temporary events (sports, concerts) or scheduled industrial processes, where service availability must be constrained to specific windows. Previous approaches lacked a unified framework for area and time constraints, leading to fragmented implementations. Rel-18's local service definition integrates with network slicing, edge computing, and policy frameworks to offer a cohesive solution.
Furthermore, local services support new business models for operators, such as venue-specific broadcasting, campus networks, and localized IoT, by enabling them to offer differentiated services with guaranteed locality and timing. This aligns with the broader 5G vision of ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB) in localized contexts.
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Local service, Localized service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 33.858 vi10 | Technical Report | Rel-18 read |