Description
The 3GPP AAA Server is a pivotal component in the 3GPP architecture for secure interworking with non-3GPP access networks, such as Wireless Local Area Networks (WLAN), WiMAX, or fixed broadband. It operates as the primary security gateway and policy enforcement point for subscribers connecting via these untrusted or trusted non-3GPP IP accesses. The server's functionality is tripartite: Authentication verifies the identity of the user/device, typically using credentials stored in the Home Subscriber Server (HSS) via the SWx or STa interfaces, employing protocols like EAP-AKA or EAP-AKA'. Authorization determines what network resources and services the authenticated user is permitted to access, based on subscription profiles retrieved from the HSS and local policies. Accounting collects data for billing and network usage analysis, generating start, interim, and stop records for sessions. Architecturally, the 3GPP AAA Server often resides in the home network (HPLMN) but can also be deployed in visited networks for roaming scenarios. It communicates with the access network's AAA proxy or client (e.g., a WLAN Access Point) using the Diameter protocol over the STa (for trusted non-3GPP access) or SWa (for untrusted access) interfaces. For trusted accesses, it may also interact with the Packet Data Network Gateway (PGW) via the S6b interface to enable seamless IP session continuity. Its role extends beyond simple access control; it is integral to enabling secure, seamless mobility (e.g., via S2a/b/c interfaces) and consistent service experience across heterogeneous networks.
Purpose & Motivation
The 3GPP AAA Server was introduced to address the growing need for secure and seamless integration of non-3GPP access technologies (primarily WLAN) with 3GPP mobile core networks. Prior to its standardization, operators lacked a standardized, scalable mechanism to authenticate mobile subscribers using their SIM credentials on WLAN hotspots, leading to fragmented and insecure solutions. Its creation was motivated by the 3GPP 'Interworking WLAN' (I-WLAN) work in Release 6 and later expanded for broader non-3GPP access in EPS (Release 8). It solves several key problems: it provides a unified authentication framework leveraging the robust security of the 3GPP subscription (SIM/USIM), enables operators to extend their services and billing models to non-cellular accesses, and forms the security anchor for network-based mobility protocols like PMIP or GTP in the Evolved Packet Core (EPC). By centralizing AAA functions, it allows operators to maintain consistent security policies and subscriber management across diverse access technologies, a critical requirement for the success of early 'Wi-Fi offload' and later converged fixed-mobile offerings.
What changed in its specifications
The latest release-to-release comparison of specifications that define 3GPP AAA Server. Each summary describes the whole specification, not only this term.
Added QoS provisioning for 3GPP/WLAN interworking, IMS emergency call support over WLAN, private network access, external AAA server authentication/accounting, and external AAA server initiated tunnel disconnection.
Full comparison in TS 23.234 →Rel-18 added MPS subscription handling, DSCP QoS differentiation, and overload exemptions for WLAN access. It also extended WLAN Selection Policy for SNPN access mode with provisioning and discovery of SNPN-advertising networks.
Full comparison in TS 23.402 →Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
Security functions and anchors · Security
- Phase 1 AuC
- R99 HLR/AuC
- Rel-5 HSS
- Rel-6 3GPP AAA Server, BSF
- Rel-8 ASME, MME
- Rel-9 HSS-FE
- Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
- Rel-16 AAnF
- 3GPP AAA Server counterpart in another generation: AUSF (not stated verbatim in the specifications)
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 12 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in Rel-6 (release dating of the term; no individual change cited).
The 3GPP AAA Server is specified for the first time in Rel-8 with its roles in trust determination, access authentication and authorization, IP mobility mode selection, and HSS interactions over SWx, STa and SWa.
- “the 3GPP AAA Server determines the HPLMN's trust relationship with the non-3GPP access network and communicates it to the non-3GPP access network” TS 29.273 v8.16.0
- “For a trusted non-3GPP access, the 3GPP AAA Server may perform IP mobility mode selection.” TS 29.273 v8.16.0
- “Once the UE has been successfully authenticated by the 3GPP AAA server, the 3GPP AAA Server sends a UE Registration Request” TS 23.402 v8.10.0
The PDN GW Identity Notification procedure is now stated as used only for PDN GW registration, no longer for both registration and de-registration.
- “This procedure is used for PDN GW registration.” TS 23.402 v9.13.0
The 3GPP AAA Server gained new behaviour: it performs IP mobility mode selection between NBM and HBM, supports GTPv2 flags, and marks and sends trust relationship to the PDN GW.
- “The 3GPP AAA Server may perform IP mobility mode selection between NBM or HBM as specified in subclause 4.1.3.2 of 3GPP TS 23.402 [3].” TS 29.273 v10.13.0
- “the 3GPP AAA Server shall decide whether the access network is handled as Trusted or Untrusted and set the value of the AN-Trusted AVP” TS 29.273 v10.13.0
- “the 3GPP AAA Server marks the trust relationship as "untrusted" with the User Identity.” TS 29.273 v10.13.0
The 3GPP AAA Server gained new roles for trusted WLAN access: authorizing EPC-routed and/or non-seamless WLAN offload, selecting the IP mobility mode (NBM or HBM), and handling TWAN-Access-Info.
- “the 3GPP AAA Server may either only authorize the user to access to EPC via S2a (i.e. EPC-routed service only)” TS 29.273 v11.11.0
- “the 3GPP AAA Server may perform IP mobility mode selection between NBM and HBM.” TS 29.273 v11.11.0
- “if no TWAN-Access-Info AVP was received from the HSS in the user's subscription, the 3GPP AAA Server shall consider that access to EPC” TS 29.273 v11.11.0
The 3GPP AAA Server gained new behaviour for Trusted WLAN: it selects the TWAN connection mode (TSCM, SCM or MCM), signals the selection to the TWAN, and authorizes EPC access via S2a or WLAN-only access.
- “the 3GPP AAA Server shall select the TWAN connection mode, i.e. either TSCM, SCM or MCM” TS 29.273 v12.9.0
- “the 3GPP AAA Server shall reply to the first DER message it receives with a result code set to DIAMETER_MULTI_ROUND_AUTH” TS 29.273 v12.9.0
The 3GPP AAA Server gained new behaviour: storing and deleting WLAN Location Information, returning the Mobile Equipment Identity to the TWAN, and handling emergency-services indications with preferential treatment.
- “the 3GPP AAA Server should store this information for the duration of the WLAN session of the UE” TS 29.273 v13.8.0
- “The 3GPP AAA Server shall give preferential treatment to UEs which access the EPC for emergency services” TS 29.273 v13.8.0
- “the 3GPP AAA Server shall send the user's Mobile Equipment Identity to the TWAN, if this information is available.” TS 29.273 v13.8.0
The 3GPP AAA Server gained new behaviour in Rel-14: supporting IMS emergency sessions over TWAN/WLAN, including IMEI checks, authorizing unauthenticated emergency attach, and updating the HSS with the PDN GW used for emergency services.
- “If the 3GPP AAA Server supports IMS Emergency sessions over WLAN (see clause 4.5.7.2 of 3GPP TS 23.402 [3]), the 3GPP AAA Server shall proceed as specified above” TS 29.273 v14.5.0
- “If the IMEI-Check-Required-In-VPLMN bit is set in the DER-Flags AVP of the first Authentication and Authorization Request message and the TWAN is in the VPLMN, the 3GPP AAA Server shall:” TS 29.273 v14.5.0
- “For emergency services, the 3GPP AAA server may update the HSS with the PDN GW currently in use for emergency services.” TS 23.402 v14.7.0
The ePDG may now update the 3GPP AAA Server with a new UE local IP address on an outer IP address change, and the 3GPP AAA Server may authorize NBM based on operator policy.
- “- update the 3GPP AAA Server with the new UE local IP address; and” TS 29.273 v15.4.0
- “Based on operator policy, the 3GPP AAA Server may also authorize the use of NBM” TS 29.273 v15.4.0
The 3GPP AAA Server's behaviour on PERMANENT_TERMINATION was extended so it also applies when Core Network Restrictions no longer allow EPC access, with the server starting network-initiated de-registration.
- “or the Core Network Restrictions do not allow access to EPC anymore. The HSS shall clear the user's 3GPP AAA Server name” TS 29.273 v16.2.0
- “The 3GPP AAA Server should start the network initiated de-registration towards the user.” TS 29.273 v16.2.0
TS 29273 adds a NOTE on routing SUCI-based signalling to an NSWOF instead of the 3GPP AAA Server, and updates the AAA Server's SWa/SWd scope to EPS.
- “enables to route the signaling towards an NSWOF, as opposed to sending it to a 3GPP AAA Server” TS 29.273 v17.6.0
- “The SWa reference point is defined between the untrusted non-3GPP IP access and the 3GPP AAA Server or Proxy in EPS.” TS 29.273 v17.6.0
The 3GPP AAA Server gained requirements to give priority (MPS) treatment to UEs on non-3GPP/TWAN access, based on HPA_Configured and MPS-Priority AVPs, and to discontinue that treatment under defined conditions.
- “the 3GPP AAA Server shall treat the command and all subsequent commands (if authentication is successful) for the UE with priority as specified in Annex C and Annex D.” TS 29.273 v18.6.0
- “The 3GPP AAA Server shall discontinue priority treatment for the UE if the 3GPP AAA Server receives a Non-3GPP-User-Data AVP” TS 29.273 v18.6.0
Defining Specifications
3GPP specifications that define or reference 3GPP AAA Server, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 read |
| TS 23.402 vj00 | EPC for Non-3GPP Access (PMIP) | Rel-19 read |