Description
An AF Session is a concept defined in the 3GPP policy and charging control (PCC) architecture. The Application Function (AF) is the functional element that represents the application layer — for example an IMS core, a streaming server, or a third-party application provider — and it interacts with the Policy and Charging Rules Function (PCRF, later PCF) to request network resources and policies for its sessions. An AF session is established by an application-level signalling protocol offered by the AF that requires a session set-up with an explicit session description before the service is used. The canonical example given in the specifications is an IMS session, where SIP signalling establishes the session and negotiates media parameters before media flows begin.
The explicit session description is central to the concept. Before the AF can request appropriate network resources, it must know what the session will look like — the media types, codecs, bandwidth requirements, and IP addresses and ports involved. This information is typically exchanged during application-level signalling (for example in SIP SDP offer/answer negotiation). Once the session description is available, the AF can map the application session onto one or more service data flows and signal the relevant information to the PCRF/PCF over the Rx (or N5 in 5G) reference point. The PCRF/PCF then formulates policy and charging rules that are installed in the PCEF/PGW or SMF/UPF, ensuring that the bearer or QoS flow is established with the correct characteristics.
The AF session is documented in specification 23.207 (End-to-end QoS concept and architecture) and 29.214 (Policy and charging control over Rx reference point). 23.207 describes how end-to-end QoS is achieved across the network, with the AF session providing the application-level anchor for QoS requests. 29.214 defines the Rx protocol — the Diameter-based interface between the AF and the PCRF — including the session establishment, modification, and termination procedures that carry the AF session information. In 5G, the equivalent interaction occurs over the N5 reference point between the AF and the PCF, using HTTP-based signalling.
The lifecycle of an AF session mirrors the application session: it is established when the application session is set up, modified when the session description changes (for example when media parameters are renegotiated), and terminated when the application session ends. Each AF session is identified by an AF session identifier, and the AF can associate multiple service data flows with a single AF session. This association allows the network to apply coherent policy across all flows belonging to the same application session, and to correlate charging information.
The AF session concept is important because it bridges the application layer and the network layer. Applications do not need to understand the internals of bearer or QoS flow management; they simply describe their session requirements, and the PCC architecture translates those requirements into network-level policies. This separation of concerns enables a wide range of services — IMS voice and video, rich media, and emerging 5G applications — to obtain appropriate QoS and charging treatment in a standardised way.
Purpose & Motivation
The AF Session concept exists to provide a standardised bridge between application-level signalling and the network's policy and charging control architecture. Applications such as IMS need to communicate their session requirements — media type, bandwidth, QoS class — to the network so that appropriate bearers or QoS flows can be established. Without a defined concept of an application session with an explicit description, the network would have no reliable basis for mapping application requirements onto network resources, and policy decisions would be guesswork.
Before the PCC architecture and the AF session concept were standardised, QoS support in 3GPP networks was largely static and tied to subscription information, with limited ability for applications to dynamically request resources. The introduction of the AF session in Release 8 (building on earlier policy work) allowed applications to dynamically signal their needs over a standardised interface (Rx), enabling on-demand QoS, service-aware charging, and better resource utilisation. The requirement for an explicit session description before service use ensures that the network has complete information at the right time, avoiding race conditions where media might start before resources are ready.
The concept has proven durable, carrying through from Release 8 to Release 20 with only a wording refinement in Release 20 that generalises the definition to an 'application level session'. This longevity reflects the fundamental soundness of the design: separating application session description from network policy enforcement allows the architecture to evolve — from Diameter-based Rx to HTTP-based N5 in 5G — while preserving the core abstraction. The AF session thus remains a cornerstone of how 3GPP networks deliver application-aware QoS and charging.
What changed in its specifications
The latest release-to-release comparison of specifications that define AF Session. Each summary describes the whole specification, not only this term.
Rel-7 replaced PDF/Go/Gq with PCRF-based policy control, added new Gx/Rx interfaces, and introduced PCC terminology.
Full comparison in TS 23.207 →Rel-19 adds IMS disaster prevention and restoration enhancements, including PCEF failure detection and a new PC-Session-Recovery-Status AVP. It also adds Multimedia Priority Service for Messaging support and satellite access charging with a Serving-Satellite-Identity AVP.
Full comparison in TS 29.214 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference AF Session, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |