UPU

UE Parameters Update

Security →
Introduced in Rel-15

UPU is a 5G security procedure where the network updates sensitive authentication parameters in the UE's USIM, triggered by policy changes or compromised credentials to ensure key freshness.

Category
Security
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
3 specs
UPU Description Purpose Detected Changes Specifications

Description

The UE Parameters Update (UPU) is a critical security maintenance procedure defined in the 5G System (5GS). Its primary function is to allow the network's authentication server function (AUSF), in conjunction with the Unified Data Management (UDM), to proactively and securely update the authentication credentials stored within a UE's USIM application. The key parameters subject to update are the long-term secret key (K) and the associated sequence number (SQN) used in the 5G Authentication and Key Agreement (5G-AKA) and Extensible Authentication Protocol (EAP)-AKA' protocols. The procedure is architecturally centered on the AUSF, which generates the new cryptographic material, and the UDM, which stores the subscriber's authentication credentials.

The UPU procedure is initiated by the AUSF/UDM, typically based on operator security policies—such as periodic key rotation, detection of potential credential compromise, or a change in cryptographic algorithms. The network sends a UPU message to the UE, transported securely via the serving AMF over the N1 reference point. This message contains the new authentication parameters (the new key K_new and SQN) encrypted and integrity-protected using security keys derived from the *current* credentials shared between the USIM and the UDM. This ensures that only the legitimate UE can decrypt and process the update. Crucially, the message includes a MAC (Message Authentication Code) that the UE verifies.

Upon receipt, the UE's USIM verifies the MAC. If valid, it replaces the old key (K) and SQN with the new values. The USIM then sends a confirmation back to the network. This entire transaction occurs transparently to the user and the UE's main processor, as it is handled within the secure environment of the USIM. Specifications 29.509 and 29.573 detail the service-based interfaces (Nausf_UEAuthentication, Nudm_UEAuthentication) used for this process, while 33.701 covers the security architecture and procedures. The UPU mechanism ensures that the fundamental root of trust for network access can be renewed without requiring physical SIM replacement, thereby maintaining the long-term security integrity of the subscriber identity.

Purpose & Motivation

UPU was introduced in 5G Release 15 to address a significant security limitation in previous cellular generations: the static nature of the long-term secret key (K) stored on the SIM/USIM. In 2G, 3G, and 4G, this key was typically provisioned once and never changed throughout the subscription's lifetime unless the physical SIM card was replaced. This static nature created risks, including the potential for key compromise through cryptographic attacks over time (key wear-out) and the inability to efficiently respond if a key was suspected to be breached.

The creation of UPU solves these problems by enabling remote, over-the-air rekeying of this foundational secret. This is motivated by the need for stronger, proactive security in 5G, which supports critical infrastructure and services. UPU allows operators to enforce key rotation policies, mitigating the risk of attacks that exploit long-term key usage. It also provides an efficient remediation path if a particular key generation algorithm is found to be weak or if a specific batch of credentials is potentially compromised, without the logistical and customer experience nightmare of mass SIM card replacement. It represents a shift towards dynamic, manageable security lifecycle for subscriber credentials.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the UE Parameters Update (UPU) function was newly introduced, including support for the procedure itself. This release defined a specific AUSF UPU Protection service where the AUSF calculates security material—namely the UPU-MAC-I AUSF and a Counter UPU—to protect the update data, and can optionally compute a UPU-XMAC-I UE for UE acknowledgement verification.

  • UE parameters update support (indicated as C4-190618 + C4-190618_rev7I) TS 29.509CR0046
Rel-16 1 change

In Release 16, the new UPU function introduced a dedicated protection service in the AUSF to compute security material for UE Parameters Update procedures. This service allows a consumer like the UDM to request the generation of a UPU-MAC-I AUSF and a Counter UPU to protect the update data from tampering, and optionally a UPU-XMAC-I UE to verify the UE's correct receipt of the data. The service is exposed via a new POST operation on the `/ue-upu` resource for a given subscriber.

  • Add UPU protection in AUSF functionality TS 29.509CR0072
Rel-17 2 changes

In Release 17, the UPU function was enhanced to support a new **UPU Transparent Container** format for delivering update data and introduced the explicit handling of a **UPU Header within the UPU Data Protection** procedure. These additions allowed the AUSF to receive and process the UE Parameters Update Information as a single, pre-encoded container and to incorporate a dedicated header element into the security material computation.

  • UPU Transparent Container TS 29.509CR0162
  • UPU Header within UPU Data Protection TS 29.509CR0130

Explore further

Broader topics and technologies where UPU plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.509 vj50 AUSF Service Based Interface Protocol Rel-19
TS 29.573 vj50 PLMN/SNPN Interconnection Interface Stage 3 Rel-19
TS 33.701 vj00 Study on mitigations against bidding down attacks Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.