Local Area Data Network

Description

A Local Area Data Network (LADN) is a 5G system feature defined from 3GPP Release 15 onwards. It enables the provisioning of a Data Network (DN) that is accessible to a User Equipment (UE) only when the UE is located within a specific geographical area, known as the LADN service area. This is a key enabler for localized services such as private networks, industrial IoT, and campus networks. The core network, specifically the Access and Mobility Management Function (AMF), is responsible for managing the UE's registration and session establishment context with respect to LADN availability. When a UE registers with the network, the AMF provides it with a list of configured LADNs and their corresponding service areas. The UE uses this information to determine its eligibility to access a particular LADN based on its current location.

The architecture involves the AMF, the Session Management Function (SMF), and the User Plane Function (UPF). The AMF stores the LADN configuration, including the Data Network Name (DNN) and the associated service area, which is defined as a set of Tracking Areas (TAs). When a UE initiates a Protocol Data Unit (PDU) Session establishment request for a LADN DNN, the AMF checks the UE's reported location against the LADN service area. If the UE is outside the area, the AMF rejects the session establishment, preventing unnecessary resource allocation and signaling. If inside, the request is forwarded to the SMF, which proceeds with normal PDU Session establishment procedures, potentially selecting UPFs that are local to the LADN for optimal routing.

LADN works by integrating location awareness into the core network's session management logic. The UE is not required to continuously monitor its location for LADN purposes; instead, it relies on the network's registration area updates and the AMF's knowledge. The service area is configured in the network and provided to the UE via non-access stratum (NAS) signaling. This mechanism ensures that PDU Sessions for a LADN are only active when the UE is within the designated zone, and they are deactivated or become inaccessible when the UE moves out. This model supports efficient network slicing for localized services, as a network slice instance can be associated with a specific LADN, ensuring resources are utilized only where needed.

Key components include the LADN DNN, which is a special DNN identifier, and the LADN service area definition. The AMF's role is central, as it performs the authorization check. The SMF is responsible for managing the PDU Session context and interacting with the Policy Control Function (PCF) and UPF. From a UE perspective, LADN awareness involves storing the received service area information and using it to conditionally attempt PDU Session establishment. This feature is crucial for enabling 5G to support vertical industry applications that require bounded, low-latency connectivity within a confined geographical footprint without impacting the wider public network.

Purpose & Motivation

LADN was created to address the need for efficient, geographically restricted data services in 5G networks. Prior to 5G, providing localized network access (like a private corporate network) often required overarching network configurations or dedicated infrastructure that wasn't tightly integrated with the mobile core. This could lead to inefficient use of core network resources, as sessions might be maintained even when a user was far from the service location, causing unnecessary signaling and user plane traffic across the network.

The motivation stems from the 5G vision to support diverse industry verticals, such as smart factories, ports, and campuses. These environments require guaranteed, high-performance connectivity that is logically and physically confined to a specific area. LADN solves this by making the core network itself area-aware, allowing it to dynamically grant or deny access to a specific data network based on real-time user location. This solves the problem of network resource sprawl and enables true network slicing for localized services, where a slice's resources are only consumed when a user is physically present in the relevant area. It provides a standardized, core-network-native method for service area restriction, moving beyond older, less efficient methods like cell-based access control or overlay networks.