Glossary term · Identifier

PEI

Permanent Equipment Identifier

Identifier →

PEI is a globally unique, permanent identifier for 3GPP User Equipment, used for device identification, registration, security, and authentication.

Introduced
Rel-15
Specifications
26 specs
Category
Identifier
Introduced
Rel-15
Specifications
26 specs
PEI Description Purpose Related Classification Detected Changes Specifications

Description

The Permanent Equipment Identifier (PEI) is a fundamental identifier within the 3GPP system, designed to uniquely and permanently identify the physical User Equipment (UE) hardware. It is defined as a separate entity from subscriber-based identities like the SUPI, ensuring a clear distinction between the device and the user. The PEI is provisioned into the UE's non-volatile memory during manufacturing and is intended to remain unchanged for the lifetime of the device, barring hardware replacement. Its primary architectural role is within the core network, specifically in interactions with the Access and Mobility Management Function (AMF) and the Unified Data Management (UDM) for registration and authentication procedures.

In operation, the PEI is used during initial network registration and authentication. For 5G systems, the PEI can be included in the Registration Request message sent from the UE to the AMF. The AMF may then use this identifier, particularly for UEs that do not have a Universal Subscriber Identity Module (USIM), to authenticate the device itself. The PEI is also a key parameter for network functions like the Equipment Identity Register (EIR), which uses it to check the device's status (e.g., blacklisted, grey-listed, or white-listed) to prevent the use of stolen or unauthorized devices on the network. This check helps in mitigating fraud and protecting network resources.

The identifier itself can take different forms depending on the device type. For traditional cellular devices, it is typically the International Mobile Equipment Identity (IMEI) or IMEISV. For IoT and other devices, it may be defined differently as per 3GPP specifications. The PEI is a critical element for security, management, and regulatory compliance. It supports functions such as device authentication for network access (especially for non-USIM based authentication in IoT scenarios), lawful interception mandates, and equipment theft deterrence. Its handling is governed by strict privacy and security specifications to prevent unauthorized tracking, with protocols ensuring it is not transmitted unnecessarily over the air.

Purpose & Motivation

The PEI was created to provide a standardized, permanent, and globally unique method for identifying telecommunications equipment independent of the subscriber. This solves several critical problems: it enables network operators to authenticate devices, not just subscribers, which is vital for IoT deployments and scenarios without USIMs. It addresses the issue of device theft and fraud by allowing networks to blacklist stolen devices via an Equipment Identity Register (EIR), preventing their use. Historically, before standardized permanent equipment identifiers, tracking stolen devices or managing device-specific access policies was inconsistent and less effective across different networks and regions.

Its introduction and formalization in 3GPP specifications, particularly from Release 15 onward with 5G, were motivated by the expanding Internet of Things (IoT) ecosystem and the need for more robust device management. IoT devices often use simplified authentication schemes or may not use a traditional SIM card, making a reliable device identifier essential for network security and access control. The PEI also fulfills regulatory requirements for lawful interception and equipment registration in many jurisdictions. It provides a stable anchor for network management functions, charging systems, and security protocols that need to correlate activities with a specific physical device over time.

Classification

Part ofIMEI
Related approachesSUPI

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
Rel-16 13 changes

+ 7 more changes

Rel-17 3 changes
  • Correct PEI used for MUSIM and network subscriptions TS 23.501CR3469
  • PEI Information TS 29.503CR0932
  • Correction of Paging with PEI TS 38.300CR0747
Rel-19 7 changes
  • PEI Requested in monitoring event configuration TS 29.503CR1484
  • Timestamp in EE immediate event report for "SUPI-PEI association" events TS 29.503CR1491
  • Old PEI in Nudm_EE TS 29.503CR1523
  • Enabling GPSI/PEI-based ID Association Query – Stage 2 TS 33.127CR0304
  • PEI in Monitoring Reports TS 29.503CR1514
  • Correction on PEI and LP-WUS subgrouping TS 38.300CR1090

+ 1 more changes

Explore further

Broader topics and technologies where PEI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vk00 Numbering, Addressing and Identification Rel-20
TS 23.501 vk20 5G System Architecture Stage 2 Rel-20
TS 24.501 vk00 5G System (5GS) Non-Access Stratum (NAS) Protocol Rel-20
TS 29.256 vk00 UAS-NF Nnef Service Based Interface Stage 3 Rel-20
TS 29.503 vk00 UDM Service Based Interface Stage 3 Rel-20
TS 29.507 vk00 Access and Mobility Policy Control Service Stage 3 Rel-20
TS 29.511 vk00 N5g-eir Service Based Interface Rel-20
TS 29.514 vk00 3GPP TS 29514 vk00: Policy Authorization Service Rel-20
TS 29.518 vk00 3GPP TS 29518 vk00: Namf Service Based Interface Rel-20
TS 29.525 vk00 UE Policy Control Service Stage 3 Rel-20
TS 29.571 vk00 Common Data Types for 5G SBI APIs Rel-20
TS 29.890 vg00 CT3 5G System Technical Report Rel-16
TS 32.255 vk20 5G Data Connectivity Charging Rel-20
TS 32.256 vk00 5G Connection and Mobility Charging Rel-20
TS 32.291 vk00 3GPP TS 32.291 vk00: Service Based Interface for Charging Rel-20
TS 33.126 vj30 Lawful Interception Requirements Rel-19
TS 33.127 vj70 Lawful Interception Architecture and Functions Rel-19
TS 33.501 vk20 5G Security Architecture and Procedures Rel-20
TR 33.857 vh10 Enhanced Security for Non-Public Networks Rel-17
TS 38.300 vj30 NR and NG-RAN Overall Description Rel-19
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19
TS 38.331 vj30 NR Radio Resource Control Protocol Specification Rel-19
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18