Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

ER

EAP Re-authentication

Security →

ER is a security protocol extension that enables efficient re-authentication without a full EAP exchange, reducing signaling overhead and latency for fast handovers and reconnections in mobile networks.

Introduced
Rel-7
Where
Services › Codecs
Specifications
6 specs
Also in
Core Network
ER Description Purpose What changed Neighbours Specifications

Description

EAP Re-authentication (ER) is a mechanism defined within the Extensible Authentication Protocol (EAP) framework, specifically standardized by the IETF and adopted by 3GPP. It allows a supplicant (e.g., a UE) and an authenticator (e.g., a network access point) to perform a streamlined re-authentication based on previously established cryptographic material from a full EAP authentication. The process leverages an EAP Re-authentication Protocol (ERP) and uses derived keys like the rRK (re-authentication Root Key) and rMSK (re-authentication Master Session Key) to secure the exchange. Architecturally, ER involves the EAP peer, the EAP authenticator, and the EAP server, with the ERP messages typically transported within EAP-Initiate and EAP-Finish messages. The ER server, often collocated with the EAP server, manages the re-authentication state and keying material. This mechanism is integrated into 3GPP systems to support seamless mobility, especially in non-3GPP access networks interworking with the 5G Core, by minimizing authentication latency during handovers. It works by the peer initiating re-authentication with an EAP-Initiate/Re-auth-Start message, leading to a mutual authentication and key derivation without involving backend authentication servers for full credential verification. Key components include the ERP key hierarchy, the ER server's state management, and the use of cryptographically secure sequence numbers to prevent replay attacks. Its role is critical in scenarios requiring frequent authentication, such as in dense urban deployments or for IoT devices with limited power, ensuring continuous secure access with reduced signaling load on core network elements.

Purpose & Motivation

ER was created to address the performance limitations of full EAP authentication procedures, which are computationally intensive and generate significant signaling traffic. In mobile networks, especially during handovers between access points or reconnections after brief disconnections, performing a full EAP exchange each time introduces unacceptable latency and impacts user experience. Historically, without ER, each re-authentication required a round-trip to the home authentication server, increasing handover delays and potentially causing service interruptions. The motivation stemmed from the need for faster, more efficient security mechanisms in evolving network architectures like 3GPP's integration of non-3GPP access (e.g., Wi-Fi) and the demands of 5G low-latency services. ER solves these problems by enabling a lightweight re-authentication that reuses previously established trust, reducing both time and resource consumption. It addresses limitations of earlier approaches where security and efficiency were often traded off, providing a standardized method to maintain robust authentication without sacrificing performance, crucial for real-time applications and massive IoT deployments.

What changed in its specifications

The latest release-to-release comparison of specifications that define ER. Each summary describes the whole specification, not only this term.

TS 23.003Rel-18 → Rel-19

Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.

Full comparison in TS 23.003 →
TS 29.273Rel-18 → Rel-19

Rel-19 adds management aspects of RedCap features to TS 29.273. It also edits trusted non-3GPP access (TWAN) behaviour and authorization text around UE access priority.

Full comparison in TS 29.273 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Introduced ER as part of EAP framework adoption for non-3GPP access interworking, providing initial architecture for re-authentication to reduce full EAP exchanges during mobility events. Defined basic ERP message flows and key hierarchy for efficiency.

Defining Specifications

3GPP specifications that define or reference ER, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 22.826 vh20 Study on 5G for Critical Medical Applications Rel-17 read
TS 23.003 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.802 v700 Enhanced End-to-End QoS Architecture Rel-7 read
TR 26.922 vj00 Video Telephony Robustness Improvements Study Rel-19 read
TS 29.273 vj20 EPS AAA Reference Points and Procedures Rel-19 read