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

Glossary term · Services

Vertical application

Vertical Application

Services →

Vertical application is an application tailored to a specific industry vertical, leveraging 5G/6G capabilities to deliver domain-specific services with dedicated performance requirements.

Introduced
Rel-19
Where
Services
Specifications
2 specs
Vertical application Description Purpose What changed Neighbours Specifications

Description

A vertical application is a software application designed to serve the specific needs of a particular industry or business sector — often called a 'vertical' — such as automotive, manufacturing, energy, healthcare, media, or public safety. Unlike generic consumer applications, vertical applications have domain-specific requirements in terms of latency, reliability, throughput, security, and data locality. In the 3GPP context, vertical applications are typically hosted on application servers that interact with the 5G System (5GS) through the Application Function (AF) to influence network behavior, request QoS, or access network exposure services.

The architecture supporting vertical applications in 3GPP is centered on the Service Enabler Architecture for Verticals (SEAL) and the Vertical Application Enabler (VAE) framework, specified in TS 23.434. SEAL provides common capabilities such as group management, location management, configuration management, identity management, and key management that are reusable across different verticals. The VAE layer, built on top of SEAL, provides vertical-specific enablers (e.g., for mission-critical services, railway, or factory automation). This layered approach allows vertical applications to reuse standardized enablers while focusing development effort on domain-specific logic.

Vertical applications interact with the 5G core network primarily through the AF, which can be an internal network function or an external entity. The AF can request QoS for specific flows, subscribe to events (e.g., location changes, PDU session status), and influence traffic routing. In Rel-19 and beyond, the integration of vertical applications with network slicing allows each vertical to be served by a dedicated slice with tailored performance characteristics. The Network Exposure Function (NEF) mediates external AF access, ensuring security and policy enforcement.

From a deployment perspective, vertical applications can be hosted at various locations: in the cloud, at the edge (MEC), or on-premises. Edge deployment is particularly important for latency-sensitive verticals like industrial automation or V2X, where the application server must be close to the UE. The 3GPP architecture supports edge computing through mechanisms like Uplink Classifier (ULCL) and IPv6 Multi-Homing, enabling traffic to be steered to local data networks (LDNs) hosting vertical applications.

In Rel-19, the definition of vertical application is formalized in TS 23.434 as 'an application catering to a specific vertical.' This concise definition reflects the broad scope of the term, encompassing any application that serves a particular industry sector. The accompanying specification TS 29.549 defines the Service Enabler Architecture for Verticals (SEAL) APIs, which provide RESTful interfaces for vertical applications to access common services. Together, these specifications enable a standardized, interoperable ecosystem where vertical applications can be developed once and deployed across multiple 5G networks.

Purpose & Motivation

The concept of vertical applications exists to address the diverse and specialized communication needs of different industries that cannot be met by a one-size-fits-all network service. Traditional mobile networks were designed primarily for consumer voice and data, with uniform QoS and best-effort delivery. However, industries such as manufacturing, automotive, and healthcare require guaranteed latency, ultra-reliability, deterministic behavior, and data isolation — requirements that generic network services cannot fulfill.

Before the formalization of vertical application enablers, each vertical had to develop its own proprietary solutions for group communication, location tracking, and identity management, leading to fragmentation and high development costs. The 3GPP SEAL and VAE frameworks solve this by providing reusable, standardized enablers that verticals can build upon. This reduces time-to-market and ensures interoperability across vendors and operators.

Furthermore, the integration of vertical applications with network slicing and edge computing allows operators to offer tailored connectivity services as part of a broader vertical solution. This transforms the operator's role from a mere connectivity provider to a service enabler, opening new revenue streams in the B2B segment. The Rel-19 definition and specifications solidify this vision by providing a clear architectural framework for vertical applications within the 5G ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define Vertical application. 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 →
TS 29.549Rel-18 → Rel-19

Rel-19 added application data analytics enablement APIs, three LM server location services, metaverse digital asset/media management, and SEAL data delivery HTTP methods and types. It also added satellite coverage and store-and-forward event APIs.

Full comparison in TS 29.549 →

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

Initial definition introduced in TS 23.434 and TS 29.549: 'An application catering to a specific vertical.' This release formalized the SEAL and VAE frameworks, providing standardized enablers and APIs for vertical applications to interact with the 5G System.

The definition text carried over unchanged from Rel-19. The term continues to be used in the same architectural context, with ongoing enhancements to SEAL and VAE specifications but no revision to the core definition.

Defining Specifications

3GPP specifications that define or reference Vertical application, 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 29.549 vk10 SEAL Service APIs Rel-20 read