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

Glossary term · Services

SEAL-UU

Service Enabler Architecture Layer for Verticals, Universal UE-network interface

Services →

SEAL-UU is the universal UE-to-network interface within the Service Enabler Architecture Layer for Verticals, providing a common API framework for vertical applications to access network services consistently across different access technologies.

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

Description

The Service Enabler Architecture Layer for Verticals, Universal UE-network interface (SEAL-UU) is a key component of the 3GPP Service Enabler Architecture Layer (SEAL) framework, defined in specifications such as 23.434 and 23.700. SEAL is designed to provide vertical industries—such as automotive, public safety, industrial IoT, and media—with a common set of service enablers that can be reused across different vertical applications. SEAL-UU specifically defines the universal interface between the user equipment (UE) and the network, abstracting the underlying access technology and providing a consistent set of APIs for vertical applications running on the UE.

The SEAL architecture consists of several enablers, including location management, group management, configuration management, identity management, and key management. Each enabler provides specific services to vertical applications. SEAL-UU acts as the unified interface through which the UE-side vertical application client communicates with these enablers. It defines the protocols, message formats, and procedures for the UE to request services, report status, and receive notifications. By providing a universal interface, SEAL-UU ensures that vertical applications can operate seamlessly over different access networks, including 5G NR, LTE, Wi-Fi, and future access technologies.

One of the core principles of SEAL-UU is the separation of concerns between the vertical application and the underlying network. The vertical application does not need to know whether the UE is connected via 5G, LTE, or Wi-Fi; it simply interacts with SEAL-UU, which handles the translation to the appropriate network protocols. This abstraction is achieved through a set of standardized APIs, typically based on RESTful principles or other web technologies, that are independent of the access stratum. The SEAL-UU interface is defined at the application layer, allowing it to be deployed over any IP-capable access network.

SEAL-UU supports both UE-initiated and network-initiated procedures. In UE-initiated procedures, the vertical application client requests a service, such as obtaining its location or joining a group. SEAL-UU processes the request, interacts with the relevant SEAL enabler on the network side, and returns the result. In network-initiated procedures, the network can push notifications or commands to the UE, such as group communication invitations or configuration updates. The interface also supports security functions, including authentication and authorization of the UE with the SEAL enablers, ensuring that only authorized vertical applications can access sensitive services.

The introduction of SEAL-UU in Release 19 reflects the growing demand for vertical-specific services in 5G and beyond. Previous releases defined SEAL enablers and their network-side interfaces, but the UE-network interface was often fragmented or left to implementation. SEAL-UU standardizes this interface, enabling interoperability between different UE vendors and network operators. It also facilitates the development of a vibrant ecosystem of vertical applications that can be deployed across multiple networks without modification. For telecom engineers, SEAL-UU represents a crucial step towards making 5G a platform for vertical industries, rather than just a connectivity service.

Purpose & Motivation

SEAL-UU was created to address the fragmentation of UE-network interfaces for vertical applications in 3GPP networks. Before its introduction, each vertical service enabler (e.g., mission-critical push-to-talk, location services) defined its own UE-to-network protocols, leading to duplicated effort, inconsistent security models, and limited interoperability. Vertical application developers had to implement multiple interfaces, and network operators had to support a patchwork of protocols. SEAL-UU solves this by providing a single, universal interface that all vertical applications can use to access SEAL services.

The motivation for SEAL-UU also stems from the need to support diverse access technologies. Vertical industries often operate in environments where multiple access networks coexist—for example, a factory may use 5G for high-reliability communication and Wi-Fi for best-effort traffic. SEAL-UU abstracts these differences, allowing the vertical application to remain agnostic to the underlying access. This is essential for ensuring consistent service delivery and simplifying application development.

Furthermore, SEAL-UU enables the 3GPP system to expose network capabilities to vertical applications in a controlled and secure manner. By standardizing the interface, 3GPP ensures that security mechanisms, such as authentication and authorization, are uniformly applied. This is particularly important for critical verticals like public safety and autonomous vehicles, where security and reliability are paramount. The introduction of SEAL-UU in Release 19 marks a maturation of the SEAL framework, moving from network-side enablers to a complete end-to-end service architecture.

What changed in its specifications

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

TS 23.434Rel-18 → Rel-19

Rel-19 adds enhanced location services (adaptive reporting, tracing, geofencing, location sharing) to TS 23.434, plus satellite SEAL services with store-and-forward, metaverse QoS and spatial anchor clauses, device triggering via the NRM server, and VAL network resource modification APIs.

Full comparison in TS 23.434 →

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-19 Initial

Initial definition of SEAL-UU, establishing the universal UE-network interface for the Service Enabler Architecture Layer for Verticals. This release specified the API framework, procedures, and security mechanisms for vertical applications to access SEAL services.

Defining Specifications

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

SpecificationTitleRelease
TS 23.434 vk10 Service Enabler Architecture Layer (SEAL) for Verticals Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read