Description
Elliptic Curve Diffie–Hellman Ephemeral (ECDHE) is a cryptographic key-agreement mechanism in which two parties generate temporary (ephemeral) elliptic-curve key pairs, exchange their public keys, and independently derive a shared secret. Because the private keys are discarded after the handshake, the resulting session keys are not recoverable from the long-term credentials of either party. This property, known as perfect forward secrecy (PFS), ensures that compromise of a long-term key does not retroactively expose previously recorded sessions. In 3GPP specifications, ECDHE is referenced as a mandatory or recommended cipher suite component for securing IP-based interfaces, particularly in TLS for the Service Based Architecture (SBA) and in IKEv2 for IPsec tunnels.
Within the 5G core network, the SBA relies on HTTP/2 over TLS to protect signaling between Network Functions (NFs). 3GPP TS 33.501 and the security profiles in TS 33.210/33.310 define the use of TLS 1.2/1.3 with ECDHE-based cipher suites, such as TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256. The ephemeral key exchange is performed during the TLS handshake, after which the NFs authenticate each other using certificates. The derived keys protect the confidentiality and integrity of NF-to-NF messages, including N1/N2 signaling forwarded by the AMF and SMF. ECDHE is also used in the N3 interface security when IPsec is deployed, with IKEv2 negotiating ECDHE-based key exchange for the child security associations.
In the radio access network, ECDHE is not used directly at the physical layer, but it secures the backhaul and control-plane interfaces. For example, the F1, E1, and NG interfaces can be protected with IPsec or TLS using ECDHE. The use of elliptic curves (e.g., secp256r1, secp384r1, Curve25519) provides strong security with shorter keys than finite-field Diffie–Hellman, reducing computational and bandwidth overhead on constrained network elements. 3GPP TS 33.703 specifies the security architecture for the 5G core, and TS 33.841 provides the security assurance specification for ECDHE-based TLS implementations, including requirements for ephemeral key generation, certificate validation, and handshake failure handling.
Operationally, ECDHE requires a reliable source of randomness for ephemeral key generation. Network elements must implement secure random number generators and protect private keys in secure storage. The handshake also involves certificate chain validation and, in some deployments, mutual authentication. 3GPP defines profiles for TLS and IPsec that mandate ECDHE for forward secrecy, and operators are encouraged to disable static RSA key exchange. The ephemeral nature of the keys means that session resumption mechanisms must be carefully configured to avoid undermining PFS; TLS 1.3's PSK resumption with ECDHE is preferred.
In summary, ECDHE is a foundational security primitive in 3GPP networks, enabling forward-secret key agreement for TLS and IPsec. Its integration into 5G SBA and transport security ensures that signaling and user data remain protected even if long-term keys are compromised. The specifications provide detailed profiles and assurance requirements to ensure interoperable and secure implementations.
Purpose & Motivation
ECDHE exists to solve the key-distribution problem in symmetric cryptography without requiring pre-shared secrets, while providing perfect forward secrecy. Earlier approaches such as static RSA key transport or static Diffie–Hellman allowed an attacker who obtained a long-term private key to decrypt all recorded sessions. ECDHE mitigates this by generating ephemeral key pairs per session, so that compromise of long-term credentials does not expose past traffic. This is critical in 3GPP networks where long-lived certificates are used for NF authentication and where recorded signaling could reveal sensitive subscriber information.
The adoption of ECDHE in 3GPP was motivated by the need for strong, efficient cryptography in virtualized and cloud-native 5G core deployments. Elliptic-curve cryptography offers equivalent security to finite-field Diffie–Hellman with much smaller key sizes, reducing CPU and bandwidth consumption. As 5G SBA introduced HTTP/2-based signaling over TLS, 3GPP specified ECDHE-based cipher suites to ensure forward secrecy and interoperability. The specifications also address the need for mutual authentication and certificate management, which are essential in multi-vendor and multi-operator environments.
Furthermore, ECDHE supports regulatory and privacy requirements by protecting signaling metadata and user data in transit. Its inclusion in 3GPP security assurance specifications (TS 33.841) reflects the importance of correct implementation and testing. Overall, ECDHE provides a standardized, efficient, and forward-secret key agreement mechanism that underpins trust in 5G and beyond.
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.
Initial introduction of ECDHE in 3GPP security specifications for 5G SBA and transport security. TS 33.703 defined the security architecture for the 5G core, mandating TLS with ECDHE-based cipher suites for NF-to-NF communication, while TS 33.841 established security assurance requirements for ECDHE implementations.
Defining Specifications
3GPP specifications that define or reference ECDHE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.703 vk10 | Post-Quantum Cryptography for 3GPP Systems | Rel-20 read |
| TR 33.841 vg10 | Security aspects; Study on 256-bit algorithms for 5G | Rel-16 read |