DOCSLIB.ORG

MEID and EUIMID Migration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
MEID and EUIMID Migration MEID and EUIMID Migration 1 MEID and EUIMID Migration 1 1 Executive Summary 2 3 • Issue. The recent (September 2007) TIA ESN Report predicts that ESN 4 manufacturer code address space for handsets will exhaust by Q1 2008. The 5 UIMID manufacturer code space for R-UIMs (a subset of the same resource) will 6 also exhaust. In fact, UIMID assignments are continuing only because the ESN 7 administrator has been able to continue to reclaim codes from older technologies 8 (AMPS analog and TDMA digital) and transfer them to the UIMID administrator. ® 9 • Industry Response. In response to these events, the cdma2000 industry is 10 migrating handsets from ESN to MEID-based addressing, and R-UIMs from 11 UIMID- to EUIMID-based addressing. 12 o Non-unique values, known as pESN (pseudo-ESN) or pUIMID 13 (pseudo-UIMID), will be used in ESN/UIMID fields, previously 14 depended upon to be unique 15 • Potential Impact. If there are no steps taken in the network and back-end 16 systems to accommodate this change, possible impacts include: 17 o Crosstalk, interference and dropped calls 18 o Misaddressed air interface messaging (e.g. SMS received by wrong 19 user) 20 o Inability to provision and/or bill some subscribers 21 o Spurious Fraud Detection alerts 22 • Migration Status. The migrations have already started ® 23 o Several major cdma2000 operators have already upgraded their 24 network and deployed MEID-based handsets 25 o EUIMID-based R-UIMs have already been deployed by at least one 26 major R-UIM vendor ® 27 • Recommended Actions. All cdma2000 operators are recommended to 28 o Upgrade their network to support C.S0072 to minimize PLCM collisions 29 o Remove any requirement in their back-end systems for a unique 30 ESN/UIMID value 31 o Use MEID-equipped devices 32 o Choose either Long or Short EUIMID format and provision in all new R- 33 UIMs ii MEID and EUIMID Migration 1 Contents 2 1 Executive Summary ......................................................................................................................... ii 3 2 The Need for Migration ....................................................................................................................1 4 2.1 Exhaust Impacts – Consequences of Inaction ......................................................................1 5 2.1.1 ESN Usage ...............................................................................................................2 6 2.1.2 Duplication Impact....................................................................................................3 7 2.1.3 Collision Impact ........................................................................................................4 8 2.1.4 MEID Support...........................................................................................................5 9 2.2 Resource Utilization and Timelines........................................................................................5 10 2.2.1 Predicted Timelines .................................................................................................5 11 2.2.2 Current Resource Utilization ...................................................................................6 12 2.2.3 Migration Activities ...................................................................................................7 13 2.3 Likelihood of Impacts...............................................................................................................7 14 2.3.1 Basic Duplication Probability ...................................................................................7 15 2.3.2 Duplications in a group of cards/devices................................................................7 16 2.3.3 PLCM Collision Probability ......................................................................................8 17 3 Hardware Identifiers Involved.......................................................................................................10 18 3.1 Identifier Relationships..........................................................................................................10 19 3.2 Existing Identifiers .................................................................................................................10 20 3.2.1 Electronic Serial Number (ESN) ...........................................................................10 21 3.2.2 User Identity Module Identifier (UIMID) ................................................................12 22 3.2.3 Integrated Circuit Card Identifier (ICCID) .............................................................13 23 3.3 New Identifiers .......................................................................................................................14 24 3.3.1 Mobile Equipment Identifier (MEID)......................................................................14 25 3.3.2 Expanded UIMID (EUIMID) ...................................................................................16 26 3.4 Derived Identifiers..................................................................................................................16 27 3.4.1 Secure Hash Algorithm 1 (SHA-1)........................................................................17 iii MEID and EUIMID Migration 1 3.4.2 Pseudo-ESN (pESN) .............................................................................................17 2 3.4.3 Pseudo-UIMID (pUIMID) .......................................................................................18 3 4 Standards Involved.........................................................................................................................20 4 4.1 MEID.......................................................................................................................................20 5 4.1.1 Requirements .........................................................................................................20 6 4.1.2 Administration.........................................................................................................20 7 4.1.3 Billing.......................................................................................................................20 8 4.1.4 Air Interface ............................................................................................................21 9 4.1.5 ANSI-41 MAP Updates ..........................................................................................22 10 4.1.6 Over-the-Air Activation...........................................................................................23 11 4.1.7 Interoperability and Testing ...................................................................................23 12 4.2 Expanded UIMID (EUIMID) ..................................................................................................24 13 4.2.1 Requirements .........................................................................................................24 14 4.2.2 Administration.........................................................................................................24 15 4.2.3 CDMA R-UIM..........................................................................................................25 16 4.2.4 CDMA SIM Application ..........................................................................................25 17 5 EUIMID Migration Options.............................................................................................................26 18 5.1 Long-Form EUIMID ...............................................................................................................26 19 5.2 Short-Form EUIMID...............................................................................................................27 20 5.3 CDMA Card Application Toolkit (CCAT) ..............................................................................28 21 5.4 Device Compatibility with EUIMID........................................................................................29 22 6 Recommendations..........................................................................................................................30 23 6.1 Operators with non-R-UIM-equipped handsets...................................................................30 24 6.2 Operators with R-UIM-equipped handsets ..........................................................................33 25 7 Scenarios .........................................................................................................................................37 26 7.1 Device / R-UIM Combinations of Interest ............................................................................37 27 7.2 Non-R-UIM Operator .............................................................................................................38 28 7.2.1 Basic Operation......................................................................................................39 29 7.2.2 Data Services .........................................................................................................45 30 7.2.3 Lost/Stolen Phone..................................................................................................46 31 7.2.4 Over the Air Service Provisioning .........................................................................46 iv MEID and EUIMID Migration 1 7.2.5 Roaming..................................................................................................................49 2 7.3 R-UIM Operator – existing R-UIM in MEID device..............................................................51
Load more

Recommended publications
  • MEID-EUIMID Operator Test Plan, Ver 1.3, January 11, 2010
    1 2 MEID-EUIMID Operator Test Plan 3 Version 1.3 4 11 January 2010 5 CDMA Development Group 6 575 Anton Boulevard, Suite 560 7 Costa Mesa, California 92626 8 PHONE +1 888 800-CDMA 9 +1 714 545-5211 10 FAX +1 714 545-4601 11 http://www.cdg.org 12 [email protected] 13 14 Notice 15 Each CDG member acknowledges that CDG does not review the disclosures or 16 contributions of any CDG member nor does CDG verify the status of the 17 ownership of any of the intellectual property rights associated with any such 18 disclosures or contributions. Accordingly, each CDG member should consider all 19 disclosures and contributions as being made solely on an as-is basis. If any CDG 20 member makes any use of any disclosure or contribution, then such use is at 21 such CDG member's sole risk. Each CDG member agrees that CDG shall not be 22 liable to any person or entity (including any CDG member) arising out of any use 23 of any disclosure or contribution, including any liability arising out of infringement 24 of intellectual property rights. 1 Contents 2 1. Introduction ......................................................................................................................................1 3 1.1 Acronyms and Abbreviations ..................................................................................................1 4 1.2 Referenced Documents ..........................................................................................................3 5 2. Mobile Hardware Identifiers ...........................................................................................................4
    [Show full text]
  • MEID EUIMID Migration 2
    MEID and EUIMID Migration 7. Scenarios 1 7.2.2 Data Services ® 2 7.2.2.1 CDMA2000 Packet Data 3 Some operators use a Network Access Identifier (NAI) of the format ESN@realm. 4 Default provisioning of this value should be changed to a unique value, such as 5 MEID@realm. 6 Origination and PLCM assignment is as for voice. 7 Either MEID or pESN (or both) is included in the airlink record sent from the PCF to 35 8 the PDSN , and included in the PDSN UDR sent to the AAA. If MEID is sent, the 9 receiving entity must be capable of accepting it (and if the pESN is absent the 10 receiving entity must not consider it required). 11 7.2.2.2 1xEV-DO Packet Data 12 An AT can provide its Hardware ID in response to a HardwareIDRequest Message. 13 When the AT is provisioned with an MEID, it will include this value as its Hardware- 14 ID, with a specific HardwareIDType. 15 In order to include this identifier on the A12 interface, the AN must recode the 16 HardwareIDType to the value specified in A.S0008-A. in other words, the AN cannot 17 simply pass the information received from the AT transparently – it must explicitly 18 understand the “MEID” HardwareIDType, and recode this to the “Type of Identity” 19 coding for MEID, as specified in A.S0016-C (referenced from A.S0008-A Annex E) 20 in order to build a properly formatted A12 message. 21 Only the MEID is available to be included into an airlink record and subsequently 22 into the PDSN UDR (assuming derivation of the pESN is not performed).
    [Show full text]
  • MEID and EUIMID Migration
    MEID and EUIMID Migration CDG Document 158 Version 2.0 30 September 2008 CDMA Development Group 575 Anton Boulevard, Suite 560 Costa Mesa, California 92626 PHONE +1 888 800-CDMA +1 714 545-5211 FAX +1 714 545-4601 http://www.cdg.org [email protected] Notice Each CDG member acknowledges that CDG does not review the disclosures or contributions of any CDG member nor does CDG verify the status of the ownership of any of the intellectual property rights associated with any such disclosures or contributions. Accordingly, each CDG member should consider all disclosures and contributions as being made solely on an as-is basis. If any CDG member makes any use of any disclosure or contribution, then such use is at such CDG member’s sole risk. Each CDG member agrees that CDG shall not be liable to any person or entity (including any CDG member) arising out of any use of any disclosure or contribution, including any liability arising out of infringement of intellectual property rights. 1 1. Executive Summary 2 3 • Issue. It has been known for several years that the ESN numbering resource, 4 used for both the handset’s Electronic Serial Number and for R-UIM UIMID 5 codes, is close to exhaustion. Due to stringent conservation and reclamation of 6 codes the life of the resource was extended several years beyond the first 7 predictions. However, the last virgin (never before assigned) ESN code is 8 expected to be assigned later in 2008 and reclaimed codes are expected to last 9 only a few months longer (perhaps through 2009).
    [Show full text]
  • MEID and EUIMID Migration
    MEID and EUIMID Migration CDG Document 158 Version 2.0 30 September 2008 CDMA Development Group 575 Anton Boulevard, Suite 560 Costa Mesa, California 92626 PHONE +1 888 800-CDMA +1 714 545-5211 FAX +1 714 545-4601 http://www.cdg.org [email protected] Notice Each CDG member acknowledges that CDG does not review the disclosures or contributions of any CDG member nor does CDG verify the status of the ownership of any of the intellectual property rights associated with any such disclosures or contributions. Accordingly, each CDG member should consider all disclosures and contributions as being made solely on an as-is basis. If any CDG member makes any use of any disclosure or contribution, then such use is at such CDG member’s sole risk. Each CDG member agrees that CDG shall not be liable to any person or entity (including any CDG member) arising out of any use of any disclosure or contribution, including any liability arising out of infringement of intellectual property rights. 1 1. Executive Summary 2 3 • Issue. It has been known for several years that the ESN numbering resource, 4 used for both the handset’s Electronic Serial Number and for R-UIM UIMID 5 codes, is close to exhaustion. Due to stringent conservation and reclamation of 6 codes the life of the resource was extended several years beyond the first 7 predictions. However, the last virgin (never before assigned) ESN code is 8 expected to be assigned later in 2008 and reclaimed codes are expected to last 9 only a few months longer (perhaps through 2009).
    [Show full text]
  • C.S0023-D V2.0
    3GPP2 C.S0023-D Version 2.0 December 2011 Removable User Identity Module for Spread Spectrum Systems © 2011 3GPP2 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. 3GPP2 C.S0023-D v2.0 Revision History Revision Description Date C.S0023-0 v2.0 Initial Release, Version 2 July 2000 C.S0023-0 v4.0 Initial Release, Version 4 June 2001 C.S0023-A v1.0 Release A September 2002 C.S0023-A v2.0 Release A Version 2 February 2004 C.S0023-B v1.0 Release B May 2004 C.S0023-A v3.0 Release A Version 3 January 2005 C.S0023-C v1.0 Release C June 2006 C.S0023-C v2.0 Release C Version 2 October 2008 C.S0023-D v1.0 Release D June 2009 C.S0023-D v2.0 Release D Version 2 December 2011 3GPP2 C.S0023-D v2.0 1 CONTENTS 2 1 GENERAL.........................................................................................................................1-1 3 1.1 Scope ........................................................................................................................1-1 4 1.2 Requirements Language ...........................................................................................1-1 5 1.3
    [Show full text]