1 / 11

IMSI and 1xEV-DO CDG IRT – Las Vegas

IMSI and 1xEV-DO CDG IRT – Las Vegas. 11/30/2005 Bryan Cook bcook@qualcomm.com. Agenda. 1xEV-DO terminology 1xEV-DO architecture and interfaces IMSI and 1xEV-DO devices 1xEV-DO and MN ID Billing impacts of 1xEV-DO IMSI and MN ID IMSI_T and 1xEV-DO Roaming Issues Conclusions.

tyrone-mooney
Download Presentation

IMSI and 1xEV-DO CDG IRT – Las Vegas

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. IMSI and 1xEV-DOCDG IRT – Las Vegas 11/30/2005 Bryan Cook bcook@qualcomm.com

  2. IMSI and 1xEV-DO November 30, 2005 Agenda • 1xEV-DO terminology • 1xEV-DO architecture and interfaces • IMSI and 1xEV-DO devices • 1xEV-DO and MN ID • Billing impacts of 1xEV-DO IMSI and MN ID • IMSI_T and 1xEV-DO • Roaming Issues • Conclusions

  3. IMSI and 1xEV-DO November 30, 2005 1xEV-DO Terminology

  4. IMSI and 1xEV-DO November 30, 2005 1xEV-DO Interfaces

  5. IMSI and 1xEV-DO November 30, 2005 IMSI and 1xEV-DO Devices • IS-95/CDMA2000 MS uses IMSI/MIN for RAN signaling • 1xEV-DO AT uses UATI (Unicast Access Terminal Identifier) for RAN signaling • An 1xEV-DO-only AT does not require an IMSI/MIN • 1xEV-DO hybrid devices use an IMSI/MIN for 1xRTT access

  6. IMSI and 1xEV-DO November 30, 2005 1xEV-DO and Mobile Node Identification (MN ID) • 1xEV-DO device identified by MN ID on A8/A9 and A10/A11 interfaces • MN ID is same field as IMSI/MIN for 1xRTT • If A12 authentication is used, a consistent MN ID (Callback-ID attribute) is returned from AN-AAA • Otherwise a pseudo IMSI is generated per session (different each time) • If A12 authentication used, and MN ID = 1xRTT IMSI/MIN • 1xEV-DO<->1x handoffs optimized for same PDSN • No PPP re-negotiation required • If MIP used, no binding update is required

  7. IMSI and 1xEV-DO November 30, 2005 Billing impacts of 1xEV-DO IMSI and MN ID • Important packet data billing field is MSID (IMSI or MIN) • Exists as A1 attribute in accounting UDR • Delivered as an airlink record for 1xRTT (a1 attribute) • A1 is populated by MN ID for 1xEV-DO • A12 authentication required for MN ID to be same as MSID

  8. IMSI and 1xEV-DO November 30, 2005 IMSI_T and 1xEV-DO • For 1xRTT, IMSI_T issues are already being addressed • For 1xEV-DO, the MN ID is whatever is provisioned in MN-AAA • Up to the operator to provision MN-AAA according to preference • If MN ID = IMSI_T, then that will be used for 1xEV-DO billing • MN ID = MSID required for optimized handoffs • Not sure if MSID will be IMSI_T or IMSI_M

  9. IMSI and 1xEV-DO November 30, 2005 Roaming Considerations • A12 authentication is required for 1xEV-DO roaming • Will ensure optimized handoffs available while roaming • Will ensure consistent billing field available while roaming (MSID, A1 attribute)

  10. IMSI and 1xEV-DO November 30, 2005 Conclusions • If A12 used, no 1xEV-DO roaming issue • Potential issue regarding IMSI_T • Provision MN ID in MN-AAA with IMSI_M or IMSI_T • Could affect handoffs and/or billing

  11. Thank You bcook@qualcomm.com

More Related