Description
The International Mobile station Equipment Identity and Software Version number (IMEISV) is an extended identifier for mobile equipment. It is a 16-digit number that builds upon the standard 15-digit IMEI by appending a two-digit Software Version Number (SVN). The first 14 digits are the Type Allocation Code (TAC, 8 digits) and Serial Number (SNR, 6 digits), identical to the IMEI. The 15th digit is a check digit (CD) calculated using the Luhn algorithm. The critical addition is the 16th digit, the SVN, which identifies the software or firmware version loaded on the device. This identifier is reported by the User Equipment (UE) to the network and is utilized by various network functions.
Within the network architecture, the IMEISV is processed by core network elements and, in some cases, the Radio Access Network (RAN). As per specifications like 24.501 (NAS) and 33.401 (security), the UE can provide the IMEISV during registration or security procedures. The core network, such as the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF), can forward this information to an Equipment Identity Register (EIR) or other management systems. The EIR can maintain policies based not only on the hardware TAC but also on the SVN, allowing for granular control. For instance, a network could restrict access for devices running outdated, vulnerable software versions.
The SVN component transforms the IMEI from a static hardware identifier into a dynamic one that reflects the device's current software state. This is crucial for modern device management. Operators and manufacturers use it to track firmware rollout compliance, ensure devices have critical security updates before allowing access to sensitive services, and enable or disable specific features based on software capabilities. In the RAN, as referenced in specs like 36.413 and 38.423, the IMEISV may be used for radio resource management optimizations tailored to specific device-software combinations. The IMEISV provides a complete picture of the device's identity, encompassing its manufacturing origin, unique unit, and operational software layer, making it a powerful tool for security, provisioning, and network optimization.
Purpose & Motivation
The IMEISV was introduced to address the limitation of the standard IMEI, which only identifies hardware. As mobile devices became more complex with updatable firmware and software, network operators and manufacturers needed a way to identify the exact software version running on a device. This was driven by the need for precise remote device management, security vulnerability mitigation, and ensuring service compatibility.
Historically, without the SVN, a network could only know the device model (via TAC) but not whether it had been updated with a patch that fixed a critical security flaw or enabled a new protocol feature. This gap made it difficult to enforce security policies or guarantee quality of service. The IMEISV solves this by binding the software state to the device's permanent identity. It allows for policies that can, for example, bar devices with known vulnerable software versions from accessing the network or redirect them to a service portal for mandatory updates.
Its purpose expanded with the rise of Over-The-Air (OTA) updates and the Internet of Things (IoT). For IoT deployments with thousands of devices, managing firmware versions is paramount. The IMEISV provides the necessary identifier for automated management systems to inventory software versions and target updates. In later releases like Rel-17 and Rel-18, its role is reinforced in the context of 5G security (33.501) and network automation, where understanding the device's software capabilities is integral to dynamic policy enforcement and network slice selection.
What changed in its specifications
The latest release-to-release comparison of specifications that define IMEISV. Each summary describes the whole specification, not only this term.
Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.
Full comparison in TS 24.501 →Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.
Full comparison in TS 33.401 →Technology family
Subscriber and device identifiers · User Equipment
- Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
- Phase 2 IMEISV
- R96 TLLI
- R97 P-TMSI
- R98 CTSMSI
- Rel-5 IMPI, IMPU, Temporary Public User Identity
- Rel-8 GUTI, M-TMSI
- Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
- Rel-16 GCI, GLI, Truncated 5G-S-TMSI
- IMEISV builds on IMEI
“The SVN is a separate field from the IMEI, although it is associated with the IMEI. When the network requests the IMEI from the MS, it may also request that the SVN is also sent towards the network.” TS 22.016
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 sourcesDocumented changes in 6 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.
Introduced in Phase 2 (release dating of the term; no individual change cited).
S1AP gained a Masked IMEISV IE, carried in INITIAL CONTEXT SETUP REQUEST and HANDOVER REQUEST, which the eNB uses to determine UE characteristics.
- “If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST the target eNB shall, if supported, use it to determine the characteristics of the UE” TS 36.413 v12.7.0
- “This information element contains the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment.” TS 36.413 v12.7.0
5GS NAS and NGAP specifications define IMEISV as a supported PEI format, let the AMF request it in Security Mode Command/Complete, and add a Masked IMEISV IE used for UE characteristics.
- “If the AMF indicated in the SECURITY MODE COMMAND message that the IMEISV is requested, the UE shall include its IMEISV in the SECURITY MODE COMPLETE message.” TS 24.501 v15.7.0
- “If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it” TS 38.413 v15.13.0
- Introduce IMEISV to addition request to Xn TS 38.423CR0050
The UE and 5G-RG handling of IMEISV changed: IMEISV is requested and returned in SECURITY MODE COMPLETE, MAC address or EUI-64 replaces it when unavailable, and the RAN uses Masked IMEISV for CIoT UEs.
- “the UE shall include its IMEISV in the IMEISV IE of the SECURITY MODE COMPLETE message; or” TS 24.501 v16.15.0
- “shall be able to provide an IMEI and an IMEISV upon request from the network.” TS 24.501 v16.15.0
- “the NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.” TS 38.413 v16.18.0
IMEISV handling was extended in Rel-17: masked IMEISV was added for UEs using CP CIoT optimisation over NG and S1 interfaces, and a missing IMEISV was corrected in N1N2 Message Subscription.
Defining Specifications
3GPP specifications that define or reference IMEISV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 read |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |
| TS 37.320 vj40 | MDT Overall Description (Stage 2) | Rel-19 read |