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

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
Where
Core Network › 5G Core
Specifications
26 specs
Also in
Security, Radio Access Network, Services
PEI Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define PEI. 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 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
Rel-16 20 changes

+ 14 more changes

Rel-17 5 changes
  • Correct PEI used for MUSIM and network subscriptions TS 23.501CR3469
  • PEI for UE not supporting any 3GPP access technologies TS 24.501CR2978
  • PEI handling for the MUSIM UE TS 24.501CR4160
  • PEI Information TS 29.503CR0932
  • Correction of Paging with PEI TS 38.300CR0747
Rel-18 2 changes
Rel-19 8 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 Request for RACS TS 24.501CR7106
  • PEI in Monitoring Reports TS 29.503CR1514

+ 2 more changes

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 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 29.256 vk10 UAS-NF NEF Service Protocols Rel-20 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.511 vk00 N5g-eir Service Based Interface Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.525 vk10 UE Policy Control Service Rel-20 read
TS 29.571 vk10 5G Common Data Types Rel-20 read
TS 29.890 vg00 CT3 5G System Technical Report Rel-16 read
TS 32.255 vk30 5G Data Connectivity Converged Charging Rel-20 read
TS 32.256 vk10 5G Connection and Mobility Charging Rel-20 read
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read
TS 33.126 vj30 Lawful Interception Requirements Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TR 33.857 vh10 Enhanced Security for Non-Public Networks Rel-17 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19 read
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19 read
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18 read