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.
Key Features
- Globally unique identifier for UE hardware
- Permanently stored in device non-volatile memory
- Used for device authentication, separate from subscriber identity
- Enables Equipment Identity Register (EIR) functionality for blacklisting
- Supports IoT and non-USIM based network access
- Essential for regulatory compliance and lawful interception
Evolution Across Releases
Introduced as the Permanent Equipment Identifier for 5G systems, formally defining its role in device identification and authentication. It was established as a key parameter for registration, especially for UEs without a USIM, and integrated with the 5G core network architecture involving the AMF and UDM.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.003 | 3GPP TS 23.003 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 29.256 | 3GPP TS 29.256 |
| TS 29.503 | 3GPP TS 29.503 |
| TS 29.507 | 3GPP TS 29.507 |
| TS 29.511 | 3GPP TS 29.511 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.518 | 3GPP TS 29.518 |
| TS 29.525 | 3GPP TS 29.525 |
| TS 29.571 | 3GPP TS 29.571 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 32.255 | 3GPP TR 32.255 |
| TS 32.256 | 3GPP TR 32.256 |
| TS 32.291 | 3GPP TR 32.291 |
| TS 33.126 | 3GPP TR 33.126 |
| TS 33.127 | 3GPP TR 33.127 |
| TS 33.501 | 3GPP TR 33.501 |
| TS 33.857 | 3GPP TR 33.857 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.304 | 3GPP TR 38.304 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.410 | 3GPP TR 38.410 |
| TS 38.470 | 3GPP TR 38.470 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.869 | 3GPP TR 38.869 |