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

Glossary term · Security

EIR

Equipment Identity Register

Security →

EIR is a security database in mobile networks that stores and validates device identities (IMEIs) to check if they are blacklisted, gray-listed, or white-listed, preventing unauthorized or problematic devices from accessing the network.

Introduced
Phase 1
Where
Core Network
Specifications
17 specs
Also in
Services
EIR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Equipment Identity Register (EIR) is a critical security entity within the core network of GSM, UMTS, LTE, and 5G systems. It functions as a centralized database that maintains lists of International Mobile Equipment Identities (IMEIs), which are unique identifiers assigned to mobile devices. The EIR classifies IMEIs into three lists: a white list for known valid devices, a black list for devices reported as stolen, barred, or technically faulty, and a gray list for devices under observation (e.g., with anomalies). When a user equipment (UE) attempts to attach to the network, the Mobility Management Entity (MME) in 4G or the Access and Mobility Management Function (AMF) in 5G queries the EIR to verify the device's IMEI.

The EIR works by receiving IMEI check requests via standardized interfaces, such as the S13 interface in LTE (between MME and EIR) or the N5g-eir service-based interface in 5G (between AMF and EIR). Upon receiving a request, the EIR searches its database and returns a response indicating the list status of the IMEI. Key components include the database engine for storing IMEI records, authentication and authorization modules to secure access, and synchronization mechanisms to update lists from external sources like the Central Equipment Identity Register (CEIR) or operator inputs. In 5G, the EIR is implemented as a network function (NF) that can be deployed in cloud-native environments, offering scalability and flexibility.

In the network architecture, the EIR plays a defensive role against device-related fraud and theft. By blocking blacklisted devices, it deters the use of stolen phones and reduces insurance claims. It also helps maintain network integrity by preventing faulty devices from causing interference or service degradation. The EIR's integration with other security functions, such as the Authentication Server Function (AUSF) and Unified Data Management (UDM), enhances overall network security posture. Its operations are governed by specifications like 29.272 and 29.273 for interfaces and 33.857 for security aspects, ensuring interoperability across different generations of mobile networks.

Purpose & Motivation

The EIR was created to combat the rising issue of mobile phone theft and cloning in early GSM networks. Before its introduction, stolen devices could be easily reused on networks, leading to financial losses for users and operators, and encouraging crime. The EIR provides a standardized mechanism to track and block such devices, thereby protecting consumers and reducing the incentive for theft. Its development was driven by the need for a global, interoperable system to share stolen device information, facilitated by entities like the GSMA's Central Equipment Identity Register (CEIR).

Historically, without an EIR, operators had limited means to verify device legitimacy, relying on manual reporting and local blacklists. The EIR automated this process, enabling real-time checks during network attachment. Over releases, its purpose expanded to address device faults and regulatory requirements, such as blocking non-compliant or counterfeit devices. In 5G, the EIR evolved to support new service-based architectures and integrate with network slicing, ensuring device security per slice. It solves problems of device fraud, network abuse, and supports lawful interception by providing reliable device identification, thereby enhancing trust in mobile communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define EIR. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 29.272Rel-18 → Rel-19

Rel-19 TS 29.272 adds disaster roaming in EPS handling, including attach indication and HSS authentication changes. It also adds a PLMN-RAT-Usage-Control AVP for RAT usage restrictions and MPS for Messaging support in the ULR procedure.

Full comparison in TS 29.272 →

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF

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 9 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

R99 specification text

EIR is specified for the first time in this spec version, including its MAP IMEI-check service, operation package, application contexts and the MSC/SGSN-to-EIR interfaces.

  • “6.1.3.6 The Equipment Identity Register (EIR)” TS 29.002 v3.20.0
  • “This operation package includes the operations required for equipment management procedures between EIR and MSC or between EIR and SGSN.” TS 29.002 v3.20.0
  • “This application context is used for equipment checking between MSC and EIR or between SGSN and EIR.” TS 29.002 v3.20.0
Rel-4 specification text

TS 52.402 v4.1.0 first specifies EIR performance measurements, including IMEI check requests and white, grey, black and unknown answers, in a new section on the EIR measurement function.

  • “B.6.1 EIR Measurement Function” TS 52.402 v4.1.0
  • “A. This measurement provides the number of IMEI check requests received by the EIR.” TS 52.402 v4.1.0
  • “A. This measurement provides the number of white answers transmitted by the EIR.” TS 52.402 v4.1.0
Rel-5 specification text

The EIR can now be asked to return the BMUEF, and the Equipment Management application context gains version 3 on the SGSN-EIR interface.

Rel-6 specification text

MAP check IMEI handling toward the EIR gained error handling: the MSC relays EIR errors on protocol fallback and returns System Failure to the VLR when the EIR dialogue fails or the result is badly formed.

  • “If the dialogue with the EIR failed, or the EIR returned a badly formed result, the MSC sends a System Failure error to the VLR” TS 29.002 v6.17.0
Rel-8 specification text

TS 29.272 defines the S13/S13' Diameter interfaces for the ME Identity Check between MME/SGSN and the EIR, and MAP CheckIMEI is extended to IWF-EIR in EPS.

  • “This specification defines the Diameter application for the MME-EIR, S13 reference point, and for the SGSN-EIR, S13' reference point.” TS 29.272 v8.14.0
  • “When receiving an ME Identity Check request, the EIR shall check whether the mobile equipment is known.” TS 29.272 v8.14.0
  • “MAP services that are defined for use between SGSN and EIR are also used in an Evolved Packet System (EPS) between IWF and EIR.” TS 29.002 v8.22.0
Rel-13 specification text

The EIR gained Diameter message priority handling per RFC 7944: it must comply with the DRMP AVP mechanism, handle requests by priority level and may modify the priority level in responses.

  • “When the HSS, the CSS or the EIR supports the Diameter message priority mechanism, the HSS, the CSS, or the EIR shall comply with IETF RFC 7944 [57].” TS 29.272 v13.12.0
  • “When the HSS, the CSS, or the EIR receives a request, it shall handle the request according to the received DRMP AVP priority level.” TS 29.272 v13.12.0
Rel-14 specification text

TS 29.273 specifies a new 3GPP AAA Server/Proxy – EIR reference point with an ME Identity Check procedure, and TS 29.272 adds DRMP priority handling for the EIR.

  • “The 3GPP AAA Server/Proxy – EIR reference point is used to check the Mobile Equipment's identity status” TS 29.273 v14.5.0
  • “The Mobile Equipment Identity Check Procedure shall be used between the 3GPP AAA Server and the EIR if the TWAN or ePDG is in the HPLMN” TS 29.273 v14.5.0
  • “When the HSS, the CSS, or the EIR receives a request, it shall handle the request according to the received DRMP AVP priority level.” TS 29.272 v14.9.0
Rel-15 1 CR

The EIR service OpenAPI (TS 29.511) was corrected so that it reuses existing data types, which changes the interface definition of the EIR.

  • Reuse of data types in EIR OpenAPI TS 29.511CR0014

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 29.272 vj60 MME and SGSN Diameter interfaces to HSS/CSS/EIR Rel-19 read
TS 29.273 vj20 EPS AAA Reference Points and Procedures Rel-19 read
TS 29.511 vk00 N5g-eir Service Based Interface Rel-20 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TR 33.857 vh10 Enhanced Security for Non-Public Networks Rel-17 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read