RuimTools: EUIMID Migration

EUIMID Migration: How To

Overview

Existing hardware identifiers, ESN (Electronic Serial Number) and UIMID (User Identity Module Identifier), are almost completely depleted
A replacement mobile device hardware identifier is available – MEID (Mobile Equipment Identifier)
A replacement RUIM (Removable User Identification Module) identifier is available – EUIMID (Expanded UIMID)
Networks need to be upgraded to support these new identifiers
New devices, such as phones and RUIMs must be capable of supporting these new identifiers
Operators must provision phones, RUIMs, back office systems and network databases with the new identifiers

New Identifier: EUIMID

EUIMID – New identifier designed to address the exhaust of the UIMID resource
Two different formats of EUIMID
- Short Form EUIMID (SF_EUIMID)
  – Share the same address space as the MEID. RUIM card manufacturers are allocated MEID manufacturer codes in the same manner, and from the same range, as handset manufacturers
- Long Form EUIMID (LF_EUIMID)
  – This is equal to the value of the ICCID of the card

SF_EUIMID: Short Form EUIMID

Advantages Disadvantages

Familiarity
- SF_EUIMID represents a minimum change from current operation, where the UIMID overrides the device ESN

Retrievable
- Available from MS in either the Status Response Message, or the Extended Protocol Capability Response Message (both methods require the device itself to have an MEID)

Common Identifier
- Both the card and device can be managed by a commonly formatted and administered 56 bit identifier

Card requirement
- Cards which do not support SF_EUIMID will not be able to override the device MEID

Stolen Phone
- Device MEID is unlikely to be transmitted to the network, it is not possible to take advantage of the new X.S0008 CheckMEID operation to track lost/stolen phones through communications with an EIR

LF_EUIMID: Long Form EUIMID

Advantages Disadvantages

Simplicity
- ICCID already existed in the card
- No new storage requirements in terms of files on the RUIM to support LF_EUIMID
- Administration procedures are already established for ICCID

Backward compatibility
- As no new data structure, current cards (that may not support C.S0023-C) can simply have pUIMID programmed into the EFRUIMID file on the cards

EIR Support
- Device MEID remains available to the network, use of LF_EUIMID allows the implementation of an Equipment Identity Register to track/block lost/stolen device

Not retrievable
- This can have impact on OTASP session, where there may be a need to receive a unique card identifier in order to access card specific information
- New standards is currently in progress to retrieve the LF_EUIMID over the air

Long Identifier
- 72 bit ICCID, if used to track the card, will require separate handling from the device MEIDs

Manufacturer Code Limitations
- Countries with 3 digit telephony country codes are restricted to only 100 unique manufacturer codes. 2 digits – 1000, 1 digit – 10,000

pUIMID (Pseudo-UIMID)

Derivation of the pUIMID

Authentication