Description
Authentication, Authorization, and Accounting (AAA) is a comprehensive security and management framework defined by 3GPP to control access to network resources, enforce policies, and record usage data. In the 3GPP architecture, AAA functions are primarily implemented within the Core Network, often interacting with the Home Subscriber Server (HSS) or Unified Data Management (UDM) for credential verification and user profile data. The framework is protocol-agnostic in concept but is commonly realized using the Diameter protocol (specified in 3GPP TS 29.229 and related specs) for communication between network functions, such as between a Policy and Charging Rules Function (PCRF) and an Online Charging System (OCS).
The process begins with Authentication, where a user or device proves its identity to the network, typically by presenting credentials (like an IMSI and a shared secret) that are verified against data stored in the HSS/UDM. This step ensures the entity is who it claims to be. Following successful authentication, Authorization determines what services, data rates, or network resources the user is permitted to access based on their subscription profile, current network policies, and service agreements. This is enforced by network elements like the Policy Control Function (PCF).
Finally, Accounting involves the collection of resource consumption data for purposes of billing, trend analysis, or capacity planning. This can be done in real-time (online charging) or as a batch process after the session (offline charging). The AAA framework integrates deeply with the 3GPP Policy and Charging Control (PCC) architecture, where authorization and accounting policies are dynamically applied and updated during a user session. Its role is critical not just for basic access but for enabling sophisticated service differentiation, secure network slicing, and flexible business models like sponsored data.
Purpose & Motivation
The AAA framework was created to address the fundamental requirements of commercial telecommunications networks: ensuring that only legitimate, paying subscribers can access services, that they use only the services they are entitled to, and that their usage can be accurately measured and billed. Prior to standardized AAA, early mobile networks had simpler, less scalable mechanisms for access control and billing. The formalization of AAA in 3GPP, beginning with Release 4, provided a structured, interoperable, and scalable model that could support the transition from circuit-switched voice to packet-switched data services and the complex service portfolios of 3G and beyond.
Its creation was motivated by the need for a unified security and management layer that could work across diverse access technologies (e.g., GPRS, WLAN interworking, 5G NR) and service types. It solves the problem of fragmented access control by providing a centralized point for credential verification and policy decision-making. Furthermore, it enables advanced business operations by supporting flexible charging models (pre-paid, post-paid, volume-based, time-based) and detailed auditing trails, which are essential for regulatory compliance and fraud prevention. In essence, AAA is the cornerstone that transforms a raw connectivity pipe into a secure, billable, and manageable commercial service.
Key Features
- Centralized user authentication against HSS/UDM credentials
- Dynamic authorization based on subscriber profiles and network policies
- Real-time (online) and batch (offline) accounting and charging
- Integration with Policy and Charging Control (PCC) architecture
- Support for access-agnostic security (3GPP and non-3GPP access)
- Enables detailed usage reporting for billing and analytics
Evolution Across Releases
Introduced the foundational AAA framework for packet-switched domains in 3GPP networks. It established the core concepts of Authentication (verifying the subscriber), Authorization (granting access rights), and Accounting (tracking resource usage) as integral parts of the GPRS and UMTS core network architecture, primarily using protocols like RADIUS and later Diameter for server communication.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.258 | 3GPP TS 22.258 |
| TS 22.935 | 3GPP TS 22.935 |
| TS 22.937 | 3GPP TS 22.937 |
| TS 22.978 | 3GPP TS 22.978 |
| TS 22.980 | 3GPP TS 22.980 |
| TS 23.141 | 3GPP TS 23.141 |
| TS 23.218 | 3GPP TS 23.218 |
| TS 23.234 | 3GPP TS 23.234 |
| TS 23.271 | 3GPP TS 23.271 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.234 | 3GPP TS 24.234 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 28.204 | 3GPP TS 28.204 |
| TS 28.402 | 3GPP TS 28.402 |
| TS 28.601 | 3GPP TS 28.601 |
| TS 28.602 | 3GPP TS 28.602 |
| TS 28.611 | 3GPP TS 28.611 |
| TS 28.879 | 3GPP TS 28.879 |
| TS 29.201 | 3GPP TS 29.201 |
| TS 29.229 | 3GPP TS 29.229 |
| TS 29.234 | 3GPP TS 29.234 |
| TS 29.329 | 3GPP TS 29.329 |
| TS 29.336 | 3GPP TS 29.336 |
| TS 29.806 | 3GPP TS 29.806 |
| TS 29.817 | 3GPP TS 29.817 |
| TS 29.826 | 3GPP TS 29.826 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.833 | 3GPP TR 32.833 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.117 | 3GPP TR 33.117 |
| TS 33.203 | 3GPP TR 33.203 |
| TS 33.210 | 3GPP TR 33.210 |
| TS 33.234 | 3GPP TR 33.234 |
| TS 33.320 | 3GPP TR 33.320 |
| TS 33.402 | 3GPP TR 33.402 |
| TS 33.545 | 3GPP TR 33.545 |
| TS 33.820 | 3GPP TR 33.820 |
| TS 33.822 | 3GPP TR 33.822 |
| TS 33.926 | 3GPP TR 33.926 |
| TS 33.978 | 3GPP TR 33.978 |
| TS 37.870 | 3GPP TR 37.870 |
| TS 38.810 | 3GPP TR 38.810 |
| TS 43.318 | 3GPP TR 43.318 |
| TS 43.901 | 3GPP TR 43.901 |
| TS 43.902 | 3GPP TR 43.902 |
| TS 44.318 | 3GPP TR 44.318 |