3GPP2 TSG-C SWG1.4 TITLE: Clarifications for IOTA Proposal SOURCE: Nick J. Mazzarella 1960 Lucent Lane Naperville, IL (630) Sanjeev Mahajan 1960 Lucent Lane Naperville, IL, (630) ABSTRACT: The following proposal clarifies the role that IOTA will play in IP OTA mobile bootstrapping and provisioning with the existing networks while utilizing text oriented protocols such as HTTP and XML. RECOMMENDATION: Review and discuss for improvement, and adopt the recommended changes. Lucent Technologies grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Lucent Technologies is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by Lucent Technologies to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Lucent Technologies. Lucent Technologies specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Lucent Technologies other than provided in the copyright statement above. Tom Hiller 1960 Lucent Lane Naperville, IL, (630) C XX

2 Recommendations for CDG IOTA Stage 2/3 proposal 1.IS-683-B enhancements will deliver the primary SMS message to the un- provisioned mobile. 2.An un-provisioned mobile sends an IS-683 Ack and then establishes Simple IP or Mobile IP service. WAP provisioning will run over service option SO33 using HTTP and XML with WAP encoding. Clarification Requested: What is NAI and shared secret for Mobile IP or Simple IP service? Should the MS be permitted to only use HTTP with the TPS URL to avoid fraud? 3.Changes will be required for ANSI-41 to meet objectives 4, 5 in slide 3. 4.IOTA stage 2/3 needs review in TSG-N and TSG-P 5.The current OTA method will be a parallel method for IP provisioning. The packet data connection shall be used for Subscriber Information Collection in the absence of a Voice Call and current SMS based OTA would be used for provisioning.

C XX3 IOTA Call Flow (User Initiated – No Voice Call) MSC OTAF 1. User dials IOTA *FC0X 2. Origination including ESN, MSID and *FC0X 3. Serving MSC assigns Temporary Reference Number (TRN) 4. Serving MSC recognizes *FC0X as request to initiate TPS_URL download sequence. *** 5. Serving MSC sends TPS URL Request containing TRN to OTAF TPS_URL_REQ(TRN) * * New ANSI-41 capabilities ** New IS683x capability ***New MSC Functionality 6. Attach (TRN) 7. Response (ESN, MSID) 8. Release( TRN) 9. Confirm *FC = *729 (IOTA Not Voice Assisted ) (Assumed) 11. TPS_URL_Info** 12. TPS_URL_Info_Ack** 10. SMDPP(TPS_URL_Info )* 13. smdpp(TPS_URL_Info_Ack) *

C XX4 IOTA Call Flow (Network Initiated) MSC OTAF * New IS725x capability ** New IS683x capability 1. SMSREQ(MSID) 2. smsreq (SMSADDR) *FC = *729 (IOTA Not Voice Assisted ) (Assumed) 4. TPS_URL_Info** 5. TPS_URL_Info_Ack** 3. SMDPP(TPS_URL_Info )* 6. smdpp(TPS_URL_Info_Ack)* HLR

C XX5 IOTA Simple or Mobile IP scenarios RAN PDSN TPS MIP (optional) PPP HTTP (URL) HA RP SO33 Orig. 1) 2) 3) 4)