1 MEID (Mobile Equipment Identifier) in TSG-C WG2 WG-II February 13, 2004 Notice ©2004 Third Generation Partnership Project Two (3GPP2). All rights reserved. Permission is granted for copying, reproducing, or duplicating this document only for the legitimate purposes of 3GPP2 and its organizational partners. No other copying, reproduction, or distribution is permitted.

2 Why MEID ? ESN (Electronic Serial Number) –ESN uniquely identifies Mobile Station (MS) ESN field is 32 bits –32 bits not enough for future growth of subscribers –Prediction is that all ESN numbers would be used by Dec Need to expand terminal identifier –MEID (Mobile Equipment Identifier) is the new MS identifier MEID –56 bit number, compatible with GSM IMEI (International Mobile Equipment Identity) »IMEI is 14 digits coded BCD (decimal digits) –Can use a MEID/IMEI for multimode GSM/CDMA/WCDMA terminals »CDMA-only terminals use hexadecimal encoding –cdma2000 Release D MS will have MEID as identifier (ESN not used) –MEID ranges assigned to manufacturers by administrators approved by 3GPP2

3 Pseudo-ESN MS with MEID generates pseudo-ESN –Pseudo-ESN = 0x80xxxxxx, where xxxxxx is 24 bit hash of MEID –Pseudo-ESN not unique »2 MEIDs may map to same Pseudo-ESN Pseudo-ESN is used in places where ESN is used –RN_HASH_KEYs (same as ESN) –IMSI_M and IMSI_T (if not configured, last 4 digits derived from ESN) –Authentication (CAVE input) –ESN based PLCM (Public Long Code Mask) »only with legacy BS (P_REV < 11) –Pseudorandom Number Generator - Used in timer based registration –ESN in status/status response/extended status response message –LAC header on r-csch

4 PLCM Generation BS decides which PLCM type to be used (signals in ECAM, UHDM) BS assigned PLCM –BS to ensure no PLCM collision MEID based PLCM –No signaling overhead (need not include PLCM bits in signaling message) –Probability of PLCM collision less than pseudo-ESN based PLCM, but not zero IMSI based PLCM –Use IMSI_S (34 bits) in PLCM –No signaling overhead –No collision when used in home network »IMSI_T case: IMSI_S unique in a given MCC & MNC »IMSI_M case: IMSI_S unique in given MCC and operator ESN based PLCM –For backward compatibility (P_REV < 11)

5 PLCM Format BS assigned and MEID based PLCM –Currently unused value used for bits Ensures no PLCM collisions with legacy PLCM generation procedures –Bit 39 indicates »BS assigned PLCM »MEID based PLCM Ensures no PLCM collision between 2 PLCM generation options. IMSI based PLCM –Currently unused value used for bits Ensures no PLCM collisions with legacy PLCM generation procedures –Bit 34 indicates »IMSI_M based PLCM »IMSI_T based PLCM Ensures no PLCM collision between 2 PLCM generation options

6 MEID based PLCM PLCM Format … BS Assigned PLCM BS assigned 39 bits bits from MEID hash

7 PLCM Format … IMSI_T based PLCM IMSI_M based PLCM IMSI_O_S (34 bits) IMSI_O_S (34 bits)

8 LAC Addressing LAC r-csch address – –MS uses MSID_TYPE based on PREF_MSID_TYPE (overhead) –New MSID types containing IMSI_S not added in Rel D –2 MSID types having MS identifier »IMSI_S+ESN »IMSI+ESN New EXT_PREF_MSID_TYPE in overhead –EXT_PREF_MSID_TYPE = 00 »PREF_MSID_TYPE=IMSI+ESN means IMSI+pseudo-ESN –EXT_PREF_MSID_TYPE = 01 »PREF_MSID_TYPE=IMSI+ESN means IMSI+MEID

9 LAC Addressing - UIM and MEID r-csch LAC address When R-UIM (usage indicator = use UIM_ID) is plugged in –UIM_ID is carried in ESN field »PREF_MSID_TYPE=IMSI+ESN means IMSI+UIM_ID Otherwise –ESN or MEID based on EXT_PREF_MSID_TYPE »PREF_MSID_TYPE=IMSI+ESN means IMSI+pseudo-ESN or IMSI+MEID based on EXT_PREF_MSID_TYPE EXT_PREF_MSID_TYPE = 11 in overhead –Both UIM_ID and MEID are included in LAC address when R-UIM is plugged in –Only MEID is included in LAC address when R-UIM is not plugged in

10 LAC Address Types New LAC r-csch address types –MEID –IMSI + MEID –IMSI + ESN + MEID (ESN field carries UIM_ID) New LAC f-csch address types –MEID

11 Status Request BS can get MEID from MS –From LAC address (based on PREF_MSID_TYPE and EXT_PREF_MSID_TYPE ) –Status Request/Status Response Message –MEID in Origination, Page Response and Registration messages based on MEID_REQD overhead flag. »MS includes MEID in these messages, even if PREF_MSID_TYPE do not require MEID in r-csch messages MSC/VLR may check status of MEID in the Equipment Identity Register (EIR) for tracking stolen MS –EIR would return status of MEID »Normal (While List) »Block (Black List) »Track (Gray List) »Unknown