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 Family 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 →

Technology family

Subscriber and device identifiers · User Equipment

  1. Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
  2. Phase 2 IMEISV
  3. R96 TLLI
  4. R97 P-TMSI
  5. R98 CTSMSI
  6. Rel-5 IMPI, IMPU, Temporary Public User Identity
  7. Rel-8 GUTI, M-TMSI
  8. Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
  9. Rel-16 GCI, GLI, Truncated 5G-S-TMSI
  • PEI builds on IMEI
    “a PEI type: in this release of the specification, it may indicate an IMEI or IMEISV, a MAC address or an IEEE Extended Unique Identifier (EUI-64)” TS 23.003

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

5GS specifies the PEI for the first time: UEs supporting NG-RAN hold a PEI (IMEI or IMEISV), include it in registration and identity procedures, and the network can reject it with cause #5.

  • “Each UE supporting NG-RAN contains a permanent equipment identifier (PEI) for accessing 5GS-based services.” TS 24.501 v15.7.0
  • “If the UE does not have a valid 5G-GUTI and it does not have a valid SUCI, then the UE shall populate the5GS mobile identity IE with its PEI.” TS 24.501 v15.7.0
  • Definition of PEI TS 23.003CR0512
Rel-16 specification text

PEI formats were extended beyond IMEI/IMEISV to include MAC address with usage restriction indication and EUI-64 for non-3GPP UEs, 5G-RG and FN-RG, with new signalling rules.

  • “the IMEI, the IMEISV, the MAC address together with the MAC address usage restriction indication and the EUI-64 are the only PEI formats supported by 5GS” TS 24.501 v16.15.0
  • “shall have a PEI in the form of the Extended Unique Identifier EUI-64 [48] of the access technology the UE uses to connect to the 5GC” TS 24.501 v16.15.0
  • “It is also used by the consumer NF (HSS) to update the PEI in the AMF 3GPP Access Registration context” TS 29.503 v16.18.0
Rel-17 specification text

PEI handling changed in Rel-17: MUSIM UEs use a separate PEI per USIM, UEs without 3GPP access use EUI-64 as non-IMEISV PEI, and PEI is stored and reported in UDR and LI.

  • “If a UE is a MUSIM UE, the UE shall use a separate permanent equipment identifier (PEI) for each USIM” TS 24.501 v17.18.1
  • “the UE shall include its EUI-64 in the non-IMEISV PEI IE of the SECURITY MODE COMPLETE message” TS 24.501 v17.18.1
  • “the UDM shall also use the PeiInfo resource of the UDR to store the received PEI” TS 29.503 v17.22.0
Rel-18 1 CR

Rel-18 changes PEI handling: MUSIM UEs keep a PEI per USIM during registration, 5G-RGs acting for AUN3 devices use the MAC address as PEI, and ProSe remote UEs can be identified by PEI.

  • “When the UE is registered with a network by using a USIM or an entry of "list of subscriber data", and has provided a PEI” TS 24.501 v18.14.0
  • “The 5G-RG, when acting on behalf of an AUN3 device, shall use the MAC address provided by the AUN3 device as a PEI.” TS 24.501 v18.14.0
  • Remote UE identified by PEI TS 24.501CR5704
Rel-19 specification text

PEI handling extended in Rel-19: UDM monitoring events can request and report PEI, including previous PEI and change timestamp, and the network may request the PEI from any UE rather than only RACS-capable UEs.

  • “this IE indicates that PEI is requested to be included if available as part of the monitoring reports for UDM detected events.” TS 29.503 v19.7.0
  • “The previous PEI, if available, prior to the reception of the new PEI by UDM” TS 29.503 v19.7.0
  • “the network may send an IDENTITY REQUEST message to the UE to retrieve the PEI, if not available in the network.” TS 24.501 v19.8.0

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