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

Glossary term · Security

PUK

PIN Unblocking Key

Security →

PUK is the eight-digit key used to unblock a USIM PIN that has been blocked after three consecutive incorrect PIN entries.

Introduced
Rel-6
Where
User Equipment › SIM/USIM
Specifications
2 specs
PUK Description Purpose What changed Neighbours Specifications

Description

3GPP TS 21.111 specifies how a USIM protects access with a PIN. After three consecutive incorrect entries the relevant PIN is blocked, even if the UICC has been removed, the USIM deselected or the mobile switched off between attempts. Once a PIN is blocked, further PIN verifications are denied.

The USIM supports a mechanism for unblocking a blocked PIN: unblocking is performed using the relevant PIN Unblocking Key, also called the Unblock PIN. It consists of eight decimal digits and cannot be changed by the user. TS 31.101 confirms that the number of digits of an UNBLOCK PIN is always eight.

After ten consecutive incorrect entries the Unblock PIN itself is blocked, and unblocking of the blocked PIN is then no longer possible.

Purpose & Motivation

The PUK allows a PIN that was blocked after repeated incorrect entries to be unblocked, while limiting the number of unblocking attempts (3GPP TS 21.111, clause 5).

What changed in its specifications

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

TS 31.101Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 31.101: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 31.101 →

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.

Rel-6 Initial

Introduced the standardized PIN Unblocking Key (PUK) procedures for USIM applications in the context of 3G/WCDMA. Defined the fundamental architecture where the PUK is stored on the UICC, the unblocking process via the terminal, and the consequences of PUK failure, establishing the core security and recovery mechanism.

Minor refinements and maintenance of UICC security specifications. Ensured backward compatibility and clarity in PUK-related procedures as part of broader USIM and card application toolkit enhancements.

Maintained PUK functionality for the new EPS/LTE ecosystem. The USIM for LTE continued to use the same PUK mechanisms, ensuring security continuity for subscribers migrating to 4G services.

Continued support within evolving UICC standards. No major changes to the core PUK concept, as it remained a stable and essential subscriber security feature.

Ongoing inclusion in UICC and security specifications. The PUK mechanism was considered mature and continued to be mandated for USIM applications.

Maintenance of the feature as part of the broader 3GPP security framework. Ensured interoperability for new device form factors and embedded SIM (eSIM) considerations began to emerge.

Support for PUK in the context of Machine-Type Communication (MTC) where remote SIM provisioning might be used, though the fundamental local unblocking procedure remained unchanged.

Continued specification maintenance. The PUK remained a baseline security requirement for traditional UICCs.

Enhanced support for remote management and provisioning with the formal introduction of the eSIM (embedded UICC) architecture in 3GPP. While the PUK concept persisted, new remote SIM provisioning protocols could offer alternative recovery methods.

Integration into the 5G security architecture for 5G SIM (5G USIM). The PUK remains a required feature for the UICC hosting the 5G USIM application, ensuring subscriber recovery for 5G devices.

Further evolution of eSIM and IoT security. PUK support is maintained for compliance and backward compatibility, even as some IoT devices might use alternative credential management systems.

Ongoing specification support within the 5G-Advanced timeline. The PUK is a legacy but vital feature supported in modern UICCs for consumer devices.

Maintenance and potential clarifications within the security specifications. The PUK mechanism is considered a stable, long-term part of the subscriber identity module security suite.

Continued inclusion in 3GPP specifications to ensure interoperability for all devices using UICC-based authentication, including those for 5G-Advanced and beyond.

Defining Specifications

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

SpecificationTitleRelease
TS 21.111 vj00 USIM and UICC Requirements for 3G Rel-19 read
TS 31.101 vj00 UICC-Terminal Interface Specification Rel-19 read