Application Function

Description

An Application Function is a logical 3GPP network function that represents a service application or an application server that can provide application-level information to the core network. It is called a function rather than a physical node because it may be implemented inside an IMS application server, a media resource function controller, a policy client, a charging client, or an external service platform. Its main role is to bridge the service layer and the network control layer, allowing applications to influence policy, charging, quality of service, and network exposure without directly controlling lower-layer radio or transport resources. In the architecture, the AF interacts with core network functions through standardized interfaces. In IMS and pre-5G systems, an AF can communicate with the Policy and Charging Rules Function, or with charging collection functions, to request or provide application-level parameters such as service identifier, media type, session description, codec information, required bandwidth, latency, jitter, or charging characteristics. In 5G systems, the AF can interact with the Policy Control Function directly or through the Network Exposure Function. The AF may be located inside the operator domain or outside it, and the NEF can provide security, authorization, and abstraction when the AF is external. The AF works by translating application semantics into network policy inputs. For example, a voice over IP application may inform the network that a session requires conversational voice treatment, while a video application may request streaming video with guaranteed bitrate. The AF does not usually schedule radio resources itself; instead, it supplies information that the policy function uses to create or update PCC rules. These rules may be applied by the session management function, packet gateway, or user plane function to enforce QoS, traffic filtering, charging, and policy control. The AF can also receive notifications about network events, such as connection state changes or policy rule installation, depending on the deployment. Key components associated with the AF include the application server or service logic, the policy client interface, the charging interface, and, in 5G, the service-based interface toward the PCF or NEF. The AF may carry identifiers such as application identifiers, service identifiers, subscriber-related context, and session correlation information. In some architectures, the AF is trusted within the operator domain and can communicate directly with policy functions. In other cases, it is treated as an external entity and must be authorized and secured before it can request network capabilities. The importance of the AF lies in service-aware network control. Without it, the core network would have to infer application requirements from generic packet flows, which can be inaccurate for encrypted or dynamic traffic. By allowing applications to declare their needs, the AF enables more precise QoS enforcement, charging, lawful intercept assistance, and network exposure. It also supports separation of concerns: the application layer defines service intent, while the network layer decides how to realize that intent using radio, transport, and policy resources.

Purpose & Motivation

The Application Function exists to give service applications a standardized way to interact with the 3GPP core network. In early IP-based mobile networks, application requirements were often handled by static profiles or by lower-layer packet inspection, which could not reliably distinguish between different services or adapt to session-specific needs. As IMS, LTE, and later 5G introduced richer services, operators needed a logical entity that could convey application-level intent to policy and charging systems without requiring every application to understand radio resource control, bearer management, or user plane configuration. The AF addresses the limitations of purely transport-level policy. A packet gateway can see IP flows, but it may not know whether a flow represents voice, video, gaming, or enterprise traffic, especially when traffic is encrypted or dynamically allocated. It also may not know the service context required for charging or lawful intercept. By introducing an AF, 3GPP created a bridge between the service plane and the control plane. The AF can provide service descriptors, media parameters, application identifiers, and session context, enabling the network to apply more accurate QoS and charging policies. Historically, the AF became central to Policy and Charging Control in Rel-4 and later evolved with LTE and 5G. In 5G, its role expanded because the core network is service-based and more open. External AFs can request network capabilities through the NEF, while internal AFs can communicate with the PCF. This allows application-aware networking while preserving security and network control. The AF therefore solves the problem of service-to-network translation, supporting differentiated services, network exposure, and efficient use of network resources.