1 / 14

Las Vegas, November 30 2005

Las Vegas, November 30 2005. MEID - Roaming Impacts. Background. 32-bit ESN resource running out MEID is new 56-bit identifier to replace ESN MEID hashed back to fit in ESN field for backwards compatibility This Pseudo-ESN (pESN) may not be unique! Lots of information already available:

ziarre
Download Presentation

Las Vegas, November 30 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Las Vegas, November 30 2005 MEID - Roaming Impacts

  2. MEID – Roaming Impacts, November 30, 2005 Background • 32-bit ESN resource running out • MEID is new 56-bit identifier to replace ESN • MEID hashed back to fit in ESN field for backwards compatibility • This Pseudo-ESN (pESN) may not be unique! • Lots of information already available: • http://www.tiaonline.org/standards/meid/ • http://www.cdg.org/members_only/teams/IntRoaming/document_archive.asp#meid • http://www.cdg.org/news/events/CDMASeminar/050207_MEID_Workshop/index.asp • http://www.3gpp2.org/Public_html/specs/alltsgscfm.cfm

  3. MEID – Roaming Impacts, November 30, 2005 What is the Problem? • ESN assumed to be unique • Used to generate Public Long Code Mask (PLCM) on traffic channel • May also be used as MS address on paging channel • May be used by back end systems to identify handset make/model or unique MS • Fraud systems may assume uniqueness • Crosstalk, dropped calls, other bad things can happen if two mobiles with same pESN in same cell • This presentation will try to focus on Roaming issues only • Lots of work for carriers to do in other areas!

  4. MEID – Roaming Impacts, November 30, 2005 Some Key Standards • MEID “officially” introduced in IS-2000 Rev D • Protocol revision 11 Mobiles required to have MEID • MEID can be used in MS address if both BS and MS are Rev D • MEID can be requested even if UIM_ID is used for ESN • “Interim Solution” published as C.S0072 / TIA-1082 • Changes to IS-2000 rev 0, A, B, C • Uses Station Class Mark to identify MS support • Addresses PLCM collision issue by allowing non ESN-based PLCM for MEID equipped mobiles • MEID can be retrieved from the mobile on demand • ANSI-41 support in X.S0008 • Adds MEID parameter to many operations • Adds EIR lookup of MEID • IOS updates under development • Currently in V&V

  5. MEID – Roaming Impacts, November 30, 2005 Handset and Network Configurations • Handsets may be • ESN Provisioned • MEID Provisioned, pre-Rev D (“pESN only”) ? • MEID Provisioned, pre-Rev D with C.S0072 support (“C.S0072 MS”) • Rev D • Networks may be • Pre-Rev D • Pre-Rev D with C.S0072 support (“C.S0072 network”) • Rev D • Capable/not capable of MEID in CDR, ANSI-41, Radius • Roaming may introduce unintended combinations

  6. MEID – Roaming Impacts, November 30, 2005 Roaming – not a closed system any more • Key Principles – same for many new capabilities • Serving carrier can’t control arrival of MEID-equipped roamers in their network • Home carrier can’t control MEID handling capability of serving network for their roamers • “Do Nothing” approach can’t avoid possibility of pESN clash • Even if carefully screen own network handset purchases – other carriers’ mobiles may clash • Probability of collision • See whitepaper on CDG site for some maths • By birthday problem, with ~4800 pESNs, 50% chance of duplication • Roamer distribution not uniform in network – main cities/attractions • Chance is low, but consequences may be high, and may repeat

  7. MEID – Roaming Impacts, November 30, 2005 PLCM Collision Scenarios • “Do Nothing” operator has pre-Rev D network with no C.S0072 support, and MEID-equipped MSs, screened to avoid pESN clash among own MSs • Industry communication of status is important

  8. MEID – Roaming Impacts, November 30, 2005 Air Interface Issues • Air Interface Addressing • Interim Solution does not allow use of MEID as part of MS address on air interface • ESN (Only) is a valid Paging Channel ADDR_TYPE • Even with Interim Solution deployed, clashes can occur if ESN addressing is used • Carriers should check their network configuration to ensure ESN addressing is not used • PLCM_TYPE • C.S0072 allows 4 new mechanisms for setting PLCM: • BS specified • 2 x IMSI-derived • MEID-derived • IMSI-based PLCMs not allowed outside home MCC, and MEID-based requires Status Request Message first • Recommend use of BS-assigned PLCM

  9. MEID – Roaming Impacts, November 30, 2005 ANSI-41 Issues • ANSI-41 support may lag behind air interface interim solution • Is this a problem? • PLCM transfer for Intersystem Handoff already supported • If HLR expects MEID but doesn’t receive it • Chance of “pseudocloning”: • Criminal has access to large number of MEID handsets • Observes valid pESN usage over-the-air • Searches inventory for a matching pESN, and programs IMSI • Authentication is effective against pseudocloning, and is not weakened by pESN • RSP Support • Will RSPs transfer MEID? • Will RSPs accept non-unique pESN?

  10. MEID – Roaming Impacts, November 30, 2005 R-UIM Issues • UIM_ID uses same resource as ESN – also subject to exhaustion • Standards discussion on Expanded/Extended UIM_ID is ongoing • Placeholder defined in IS-2000 Rev D • Stage 1 requirements published • See ftp.3gpp2.org • TSG-C WG1.4 • TSG-S Numbering Ad Hoc • TSC-X WG2-CSN • Philosophical questions on role of UIM_ID and need for uniqueness • See next presentation for more detail J

  11. MEID – Roaming Impacts, November 30, 2005 Voice Billing Issues • Does C.S0072 support necessarily include MEID in the CDR? • Check with your network vendor • CIBER format apparently updated to support MEID • New value of ESN/IMEI Indicator? • Carrier Billing system and Clearinghouse support for • MEID in CIBER • Non-unique ESN • Will any Home Carriers require MEID? • Problematic if serving carrier doesn’t support

  12. MEID – Roaming Impacts, November 30, 2005 Packet Data Roaming • ESN and MEID are defined in IS-835 as VSAs for Accounting Records • Similar issues to voice – can Carriers/CRX providers send/receive/transfer • MEID • Will it be required by any Home operators? • Non-unique ESN • Any other issues?

  13. MEID – Roaming Impacts, November 30, 2005 Summary • Roaming may expose operators to MEID issues before they planned to deal with them • C.S0072 can address PLCM collision issues before Rev D • ESN addressing needs to be considered as well • May need to consider differing levels of MEID support between Home and Serving operators on internetwork interfaces (ANSI-41, voice/data billing)

  14. MEID – Roaming Impacts, November 30, 2005 Thank You! • Daniel Salek • dsalek@qualcomm.com

More Related