1 / 9

CDG GHRC R-UIM Doc #142 Rev 1.0 Status Update

CDG GHRC R-UIM Doc #142 Rev 1.0 Status Update. September 11, 2007 Toronto. Prepared by: Patricia Feng Senior Technical Consultant, Gemalto Email: patricia.feng@gemalto.com Phone: 972-930-6005. GHRC R-UIM Doc #142 v1.0 Status. Release 0.9 Published in April 2007

otto
Download Presentation

CDG GHRC R-UIM Doc #142 Rev 1.0 Status Update

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. CDG GHRC R-UIM Doc #142 Rev 1.0Status Update September 11, 2007 Toronto • Prepared by: • Patricia Feng • Senior Technical Consultant, Gemalto • Email: patricia.feng@gemalto.com • Phone: 972-930-6005

  2. GHRC R-UIM Doc #142 v1.0 Status • Release 0.9 Published in April 2007 • Support of the R-UIM handset requirements • Support of the Dynamic R-UIM handset requirements • Core Team • Gemalto • Qualcomm • Nokia • Motorola • Telus • TATA • Mobile 8 • Telecom New Zealand • Ongoing Discussion for Release 1.0 • Evolving CDMA R-UIM-based handsets to a unified configuration model • Allow operator specific data and application configuration parameters to be customized on the R-UIM

  3. OTA Configurable Configuration 1 Configuration 2 Generic R-UIM handset model Unified Configuration Model for the R-UIM Handsets • Purpose: • Reduce Time to the Market • Eases handsets renewal • Reduces life cycle of handsets • Subscription (R-UIM) life cycle longer than ME • Lower development cost for OEMs • Tighter coupling to the operator services • Additional Application Parameters to be defined • BREW • BROWSER • JAVA • MMS • LBS • FOTA

  4. New Requirements on #142 v1.0 (1/4) • Carrier Customization • Service Provider Name display • Image (home screen & carrier’s logo) • OMA Device Management (OMA-DM) • Over-the-Air (OTA) Provisioning and Firmware • CCAT Data Download • FOTA • OTASP/OTAPA (next phase) • SMS Capabilities • Max number of Segments • SMS Retry Period • Retry Interval • Max Text Size • SMS Flags (MO-SMS sent over Access Channel/Traffic Channel) • SMS Default Service Option

  5. New Requirements on #142 v1.0 (2/4) • 3G Packet Data • MobileIP Flags • SimpleIP User Profile Parameters Extension • MobileIP User Profile Parameters Extension • IPv6 Capabilities • TCP Configurations • Data Generic Configuration • Browser • Browser Connectivity Parameters • Browser Bookmarks

  6. New Requirements on #142 v1.0 (3/4) • MMS • MMS Configuration • Max Message Size • Max Text Size • Max number of slides • Retry Times • Retry Interval • MMSC Timeout • MMS Implementation Field • Addition of HTTP implementation of MMS • Java • Preloaded on-card Java Application on the R-UIM • Java Application on the device • Java Download URL

  7. New Requirements on #142 v1.0 (4/4) • BREW • BREW Download • BREW Teleservice ID • BREW Subscriber ID • LBS • gpsOne XTRA Assistance • LBS XTRA Configuration • LBS XTRA Server URLS • LBS V2 User Plane • LBS V2 Configuration • LBS V2 PDE Address • LBS V2 MPC Address

  8. Next Steps

  9. Success Key Factors for Generic R-UIM Handset Models • Competitive with the GSM handset model • Join the R-UIM core team discussion by conference call • Contact Patricia Feng patricia.feng@gemalto.com • Carriers’ & Industry Review and Feedback • Standardize the requirements by 3GPP2 • Adopt the R-UIM #142 v1.0 requirements

More Related