Description
The Application Function (AF) / Application Server (AS) is a critical architectural component in 3GPP's Service-Based Architecture (SBA), particularly from 5G onwards. It represents the entity that hosts application logic and requires interaction with the 5G Core Network (5GC) to support its services. The AF/AS is not part of the 3GPP-defined core network itself but is a trusted external entity that communicates with core network functions, primarily the Network Exposure Function (NEF) and the Policy Control Function (PCF), via standardized service-based interfaces.
Architecturally, the AF/AS interfaces with the 5G Core through the NEF, which acts as a secure gateway and abstraction layer. The NEF exposes 3GPP network capabilities and events to the AF in a controlled manner, while also aggregating and translating AF requests for internal network functions. For direct, trusted communication (within an operator's domain), the AF may also interface directly with the PCF. The primary protocols used are HTTP/2 with JSON payloads, following the 3GPP service-based interface principles defined in TS 29.500 series.
How it works involves several key interactions. The AF can provide session-related information to the PCF, such as the required bandwidth, latency, or jitter for a specific application flow. This allows the PCF to create appropriate Policy and Charging Control (PCC) rules. The AF can also subscribe to network events (e.g., UE location change, loss of connectivity) via the NEF. When such an event occurs, the NEF notifies the AF, enabling the application to react dynamically. Furthermore, the AF can influence traffic routing by requesting specific Data Network Names (DNNs) or Network Slice selection, enabling application-aware connectivity.
Its role extends to enabling network capabilities for vertical industries and third-party service providers. Through the AF/AS interface, applications can request guaranteed bit rate services for critical communications, trigger network-triggered service requests for IoT devices, or access analytics information. The AF/AS is central to the 5G vision of network programmability and exposure, transforming the network from a pure connectivity pipe into a programmable platform that can be tailored to diverse application needs, from enhanced mobile broadband to ultra-reliable low-latency communications and massive IoT.
Purpose & Motivation
The AF/AS concept was created to bridge the gap between application-layer services and the underlying mobile network capabilities. Historically, applications ran 'over-the-top' with limited visibility or control over network conditions. This led to suboptimal user experiences, as applications could not adapt to network congestion, latency, or mobility events. The AF/AS provides a standardized, secure mechanism for applications to communicate their requirements and receive network intelligence, enabling optimized service delivery.
A key problem it solves is the static nature of traditional QoS and policy control. Previously, network policies were largely operator-defined and generic. The AF/AS allows for dynamic, application-driven policy control. For example, a cloud gaming service can request a low-latency, high-bandwidth flow for a user's session only when the game is active, improving resource efficiency. It also addresses the need for network exposure to foster innovation, allowing third-party developers to create network-aware applications without requiring deep knowledge of 3GPP internals.
The motivation stems from the diverse requirements of 5G use cases. Vertical industries like automotive, healthcare, and industrial IoT require specific network behaviors (e.g., guaranteed latency, high reliability) that cannot be satisfied with a one-size-fits-all network. The AF/AS, in conjunction with network slicing and policy control, provides the interface for these verticals to 'talk' to the network and ensure their service level agreements are met. It transforms the network from a closed system into an open platform supporting a vast ecosystem of innovative services.
Key Features
- Dynamic application-influenced policy control via interaction with the PCF
- Subscription and notification of network events (e.g., UE mobility, connectivity status) via the NEF
- Influence on traffic routing and network slice selection for application sessions
- Secure exposure of network capabilities to trusted external applications
- Support for application-aware QoS, including guaranteed bit rate and latency targets
- Enables network-triggered service requests for efficient IoT device communication
Evolution Across Releases
Introduced the consolidated AF/AS entity within the 5G Service-Based Architecture with enhanced capabilities. It formally defined the interaction with the Network Exposure Function (NEF) for all third-party AF communication, providing authentication, authorization, and API translation. Key initial capabilities included providing application session information to the PCF for dynamic policy control, subscribing to UE mobility events, and influencing UPF selection and traffic routing.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.527 | 3GPP TS 23.527 |
| TS 29.532 | 3GPP TS 29.532 |