Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

LUN

Local USS Network

Services →

LUN is a Rel-18 Local USS Network concept for hosting UAV-specific USS services locally near the radio edge, enabling low-latency, localized drone traffic management and reducing backhaul dependency for UAS operations.

Introduced
Rel-18
Where
Services
Specifications
2 specs
LUN Description Purpose What changed Neighbours Specifications

Description

The Local USS Network (LUN) is a Rel-18 concept introduced in the context of Unmanned Aerial System (UAS) support in 3GPP networks. USS stands for UAS Service Supplier, an entity defined in the broader UAS ecosystem (notably by FAA/EU regulators) that provides services such as flight authorization, traffic deconfliction, and remote identification to drone operators. In earlier releases, the 3GPP network interacted with a USS through the UAS-NF (Network Function) over the UUAA (UAS UAV Authentication and Authorization) framework, but the USS itself was typically a centralized, cloud-hosted entity. The LUN concept recognizes that many UAS services — particularly those involving low-latency command-and-control, local geofencing, or dense urban air mobility — benefit from being hosted close to the radio access edge.

Architecturally, the LUN is a localized deployment of USS functionality, potentially co-located with an edge computing platform (such as an Edge Application Server environment or a local UPF anchor). The 3GPP network exposes service APIs to the LUN so that the LUN can query network-provided information (e.g., UAV location, connectivity status, or radio conditions) and can request network actions (e.g., QoS adjustments or policy enforcement) relevant to the UAV. The LUN itself may be operated by a third party or by the mobile network operator, and it interfaces with the UAS-NF and other core network functions. Study work captured in 23.700 (the UAS study) and normative API work in 29.257 (UAS NF service APIs) define the interactions.

The key motivation for LUN is latency and locality. Centralized USS services may be hundreds of milliseconds away, which is problematic for safety-critical drone operations such as detect-and-avoid or dynamic geofence updates. By placing USS logic locally, the round-trip time between the drone, the network, and the service logic is minimized. This also reduces backhaul load and allows the LUN to make decisions based on fresh, locally relevant network data (e.g., cell load, local weather, or temporary flight restrictions).

In operation, the LUN registers with the UAS-NF and subscribes to relevant events. When a UAV attaches and is authenticated for UAS services, the UAS-NF can inform the LUN of the UAV's presence and provide authorized service parameters. The LUN can then push local flight rules or receive telemetry. The LUN may also interact with edge computing infrastructure to host application logic. Security is a major consideration: the LUN must be authenticated, and its API access must be authorized and encrypted, as defined in the relevant security specifications.

The LUN is expected to evolve in Rel-19 and Rel-20 as UAS support matures, with tighter integration into network slicing (dedicated slices for UAS), edge computing frameworks, and potentially with the integration of UTM (UAS Traffic Management) standards from aviation bodies. It represents a convergence of telecom and aviation-domain service delivery at the network edge.

Purpose & Motivation

The LUN exists to solve the latency and locality problem in UAS service delivery. In earlier releases, the USS was a remote, centralized entity, which meant that drone traffic management decisions — such as flight authorization, geofence enforcement, and deconfliction — could be delayed by network round-trip times and were based on potentially stale data. For safety-critical operations, this is unacceptable.

By localizing USS functionality at the network edge, the LUN enables near-real-time interaction between the drone, the network, and the service logic. It also allows the USS to leverage fresh, locally relevant network context (cell load, local radio conditions, edge compute availability) that a centralized USS could not easily obtain. This improves both the accuracy and the responsiveness of UAS services.

Historically, 3GPP's UAS work began in Rel-17 with basic UAV identification and authorization. Rel-18's LUN concept extends this by acknowledging that the service layer itself must be distributed. The LUN addresses the limitation that a single centralized USS cannot scale to serve dense, latency-sensitive urban air mobility scenarios, and it provides a standards-based way for operators and third parties to deploy USS logic close to where the drones actually fly.

What changed in its specifications

The latest release-to-release comparison of specifications that define LUN. Each summary describes the whole specification, not only this term.

TS 29.257Rel-18 → Rel-19

CAPIF Phase 3 is OAuth2 scope definitions, requires granted scope authorization and operation limits, and removes the Client Credentials-only restriction.

Full comparison in TS 29.257 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-18 Initial

Initial introduction of the Local USS Network concept in the UAS study (23.700) and definition of UAS NF service APIs (29.257). Establishes the architecture for localized USS deployment and its interaction with the 3GPP core network.

The definition text carried over unchanged from Rel-18; Rel-19 work focuses on refining UAS support and integration with edge computing and network slicing rather than redefining the LUN term itself.

The definition text carried over unchanged from Rel-18; Rel-20 continues maturation of UAS services with the LUN concept retained as defined.

Defining Specifications

3GPP specifications that define or reference LUN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 29.257 vk10 UAS Application Enabler Server APIs Rel-20 read