Description
Authentication Authorization Request (AAR) is a Diameter protocol message used in 3GPP networks to request authentication and authorization decisions from a server, typically a Policy and Charging Rules Function (PCRF) or an Authentication, Authorization, and Accounting (AAA) server. In the 3GPP context, AAR is most commonly associated with the Rx interface, where an Application Function (AF) sends an AAR to the PCRF to request policy and charging control (PCC) decisions for an application session. The PCRF responds with an Authentication Authorization Answer (AAA), which may include authorized QoS, charging rules, and other policy instructions.
The AAR message carries a Session-Id, which identifies the Diameter session, along with application-specific attributes such as the AF Application Identifier, media type, media description, and requested QoS. The PCRF uses this information to bind the application session to an IP-CAN session, apply policy rules, and authorize the requested resources. If the request is authorized, the PCRF may install or modify PCC rules toward the Policy and Charging Enforcement Function (PCEF) in the gateway. If not authorized, the PCRF returns an error or a restricted authorization.
TS 29.806 specifies the Diameter application for the Rx interface, including the AAR and AAA messages, their attribute-value pairs (AVPs), and the state machine for the AF-PCRF interaction. TS 29.826 specifies the Diameter application for the Nt interface, which is used between the Network Exposure Function (NEF) and the Policy Control Function (PCF) in 5G, and includes AAR-like authorization request mechanisms adapted to the 5G service-based architecture.
AAR is a request-response message: the AF sends AAR, and the PCRF replies with AAA. The message can be used to initiate a session (initial AAR), modify an existing session (update AAR), or terminate a session (via a Session-Termination-Request, STR). The AAR includes the Auth-Application-Id and the specific AVPs required by the Rx application. The PCRF may also send Re-Auth-Request (RAR) messages to the AF to request re-authorization or to notify the AF of policy changes.
In 5G, the Diameter-based Rx interface is largely replaced by the service-based Npcf_PolicyAuthorization service, but AAR concepts persist in the authorization request flows. The AAR mechanism is fundamental to ensuring that application sessions receive appropriate QoS and charging treatment, and that network resources are used in accordance with operator policy and subscriber entitlements.
Purpose & Motivation
AAR exists to provide a standardized way for application functions to request authentication and authorization from the network's policy infrastructure. Before AAR, application-level QoS and charging requests were handled in a proprietary or inconsistent manner, making it difficult for operators to enforce policy and for application providers to obtain predictable service quality. The Rx interface and its AAR message standardized this interaction, enabling AFs to request dedicated bearers, QoS guarantees, and charging rules in a consistent way.
The motivation is to enable policy-controlled application delivery. For example, an IP Multimedia Subsystem (IMS) AF can use AAR to request a dedicated bearer for a voice call, ensuring appropriate QoS. A video streaming AF can request bandwidth guarantees. The PCRF, as the policy decision point, evaluates the request against subscriber policy and network conditions, and authorizes or rejects it. This separation of policy decision and enforcement is a core principle of 3GPP PCC architecture.
In 5G, the AAR concept evolved into service-based authorization requests, but the fundamental need remains: applications must be able to request and receive authorization for network resources in a standardized, interoperable way. AAR and its successors ensure that policy control scales with the diversity of applications and services in modern networks.
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.
Defining Specifications
3GPP specifications that define or reference AAR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.806 vc10 | P-CSCF Restoration Analysis & Solutions | Rel-12 read |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 read |