MEI

Mobile Equipment Identity

Identifier →
Introduced in Rel-8

MEI is the globally unique identifier for a mobile device, used by the network for equipment identification, tracking, and security functions like blacklisting.

Category
Identifier
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
1 specs
MEI Description Purpose Related Classification Detected Changes Specifications

Description

The Mobile Equipment Identity (MEI) is a critical identifier in 3GPP systems that uniquely distinguishes the physical User Equipment (UE) hardware from the subscriber identity (IMSI) stored on the UICC/SIM card. It is a permanent, factory-programmed identifier for the mobile terminal itself. The most common and standardized form of the MEI is the International Mobile Equipment Identity (IMEI), a 15-digit decimal number that includes a Type Allocation Code (TAC), a Serial Number (SNR), and a check digit. The network can request the MEI from the UE during procedures like attachment, location update, or at the network operator's discretion, typically via the Equipment Identity Register (EIR) query process.

Architecturally, the MEI is used by core network functions, particularly the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5GC. When a UE attaches to the network, the MME/AMF may send an MEI check request to the Equipment Identity Register (EIR). The EIR maintains lists (white, gray, black) of MEIs. The network uses this check to verify if the equipment is reported as stolen, faulty, or otherwise restricted from accessing the network. This provides a layer of security and management separate from subscriber authentication. The MEI is transmitted in dedicated NAS and RRC messages, such as the Attach Request or UE Capability Information.

How it works is integral to device management and security policies. Upon receiving an MEI, the EIR returns a response indicating the equipment's status. If the MEI is on a blacklist, the network may deny service or limit the services available to that device, even if the subscriber's credentials are valid. This helps combat handset theft and fraud. Furthermore, the MEI is used for statistical purposes, device type identification, and to support features like lawful interception. Its role ensures that network access control can be enforced at both the subscriber (SIM) and equipment (device) levels, providing operators with granular management capabilities.

Purpose & Motivation

The MEI was standardized to solve the problem of equipment-based fraud and theft, which subscriber-based identifiers like the IMSI could not address. Before its widespread adoption, a stolen mobile phone could simply be used with a different SIM card, making the device itself untraceable by the network for denial-of-service purposes. The MEI provides a immutable hardware identity that allows network operators to blacklist specific devices, rendering them unusable on their networks and thus reducing the incentive for theft.

Its creation was also motivated by the need for accurate equipment identification for regulatory, technical, and commercial reasons. Regulators may require tracking of device types for certification or compliance. Technically, knowing the exact device model (via the TAC part of the IMEI) helps in managing network compatibility and optimizing radio resource usage for specific device capabilities. Commercially, it aids in inventory management, warranty tracking, and understanding device penetration in the network. The MEI, as a cornerstone of the EIR system, introduced a vital equipment-centric layer to the overall network security and management framework.

Classification

Part ofIMEI
Related approachesEIR

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the specifications introduced procedures for using the Mobile Equipment Identity (MEI) for emergency and RLOS (Restricted Local Operator Services) attached User Equipment, particularly when the UE is UICCless or when the IMSI is not authenticated. Specifically, the MEI is mandated to be included on the S2a/S2b interface from the TWAN/ePDG under these emergency attachment conditions, allowing for identification where a subscriber identity is unavailable. This provides a critical identifier for network procedures when traditional authentication is not possible.

  • Temporary identity in Idle mode mobility using N26 TS 29.274CR1884
  • Extended EPS Bearer Identity for INOBEAR TS 29.274CR1900
Rel-17 2 changes

In Release 17, the MEI function was enhanced to support specific emergency and non-authenticated scenarios. The specification now mandates that the ME Identity (MEI) IE shall be included on the S2a/S2b interface if the UE is emergency attached and UICCless, or if the UE is emergency attached and the IMSI is not authenticated. Furthermore, for all other cases, the TWAN/ePDG shall include the MEI on the S2a/S2b interface if it is available.

  • Transferring Alternative IMSI between MMEs TS 29.274CR2048
  • MSC Server Identity in Forward Relocation Response during SRVCC handover TS 29.274CR2060

Explore further

Broader topics and technologies where MEI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.274 vj50 GTPv2-C Control Plane Protocol Specification Rel-19