OTA Provisioning Whitepaper

Version 5




0

Technical Manual

---

Copyright © 2007, Motorola, Inc. All rights reserved. This documentation may be printed and copied solely for use in developing
products for Motorola products. In addition, two (2) copies of this documentation may be made for archival and backup purposes.
Except for the foregoing, no part of this documentation may be reproduced or transmitted in any form or by any means or used to
make any derivative work (such as translation, transformation, or adaptation) without express written consent from Motorola, Inc.
Motorola reserves the right to make changes without notice to any products or services described herein. "Typical" parameters,
which may be provided in Motorola Data sheets and/or specifications, can and do vary in different applications and actual
performance may vary. Customer's technical experts will validate all "Typicals" for each customer application.
Motorola makes no warranty in regard to the products or services contained herein. Implied warranties, including without limitation,
the implied warranties of merchantability and fitness for a particular purpose, are given only if specifically required by applicable law.
Otherwise, they are specifically excluded.
No warranty is made as to coverage, availability, or grade of service provided by the products or services, whether through a service
provider or otherwise. No warranty is made that the software will meet your requirements or will work in combination with any
hardware or application software products provided by third parties, that the operation of the software products will be uninterrupted
or error free, or that all defects in the software products will be corrected.
In no event shall Motorola be liable, whether in contract or tort (including negligence), for any damages resulting from use of a
product or service described herein, or for any indirect, incidental, special or consequential damages of any kind, or loss of revenue
or profits, loss of business, loss of information or data, or other financial loss arising out of or in connection with the ability or inability
to use the Products, to the full extent these damages may be disclaimed by law.
Some states and other jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, or limitation on
the length of an implied warranty, therefore the above limitations or exclusions may not apply to you.
This warranty gives you specific legal rights, and you may also have other rights, which vary from jurisdiction to jurisdiction.
Motorola products or services are not designed, intended, or authorized for use as components in systems intended for surgical
implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure of the
Motorola product or service could create a situation where personal injury or death may occur.
Should the buyer purchase or use Motorola products or services for any such unintended or unauthorized application, the buyer
shall release, indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against all
claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury
or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent regarding the
designing or manufacturing of the product or service.
Motorola recommends that if you are not the author or creator of the graphics, video, or sound, you obtain sufficient license rights,
including the rights under all patents, trademarks, trade names, copyrights, and other third party proprietary rights.
If this documentation is provided on compact disc, the other software and documentation on the compact disc are subject to the
license agreement accompanying the compact disc.
OTA Provisioing Whitepaper
Version 5
June 2007
For the latest version of this document, visit http://developer.motorola.com

Motorola, Inc.
http://www.motorola.com

---

Contents
Introduction ............................................................................................................................................ 4
Summary .......................................................................................................................................... 4
References ....................................................................................................................................... 5
Revision History ............................................................................................................................... 6
Definitions, Abbreviations, Acronyms .............................................................................................. 6
Chapter 1:
Bootstrap Process ............................................................................................................ 7
Chapter 2:
Configuration..................................................................................................................... 8
Feature Availability........................................................................................................................... 8
Whitelist............................................................................................................................................ 9
User Options .................................................................................................................................... 9
Master Clear..................................................................................................................................... 9
User Handset Experience .............................................................................................................. 10
Chapter 3:
OTA Provisioning Security Mechanism—Authentication........................................... 13
NETWPIN and USERNETWPIN Authentication ............................................................................ 14
Chapter 4:
OTA Provisioning of Browser........................................................................................ 16
Code Example................................................................................................................................ 16
Operating Constraints .................................................................................................................... 18
Modification/Deletion of Provisioned Session by Operator............................................................ 19
Chapter 5:
OTA Provisioning of MMS .............................................................................................. 21
Code Example................................................................................................................................ 21
Operating Constraints .................................................................................................................... 21
Chapter 6:
OTA Provisioning of SyncML Data Synchronization .................................................. 23
Code Example................................................................................................................................ 23
Operating Constraints .................................................................................................................... 24
Chapter 7:
OTA Provisioning of Email............................................................................................. 25
Code Example................................................................................................................................ 25
Operating Constraints .................................................................................................................... 35
Chapter 8:
OTA Provisioning of Other Applications ...................................................................... 38
KJava ............................................................................................................................................. 38
“Always-On” ................................................................................................................................... 38
Streaming....................................................................................................................................... 38
Page 2
OTA Provisioning Whitepaper

---

Chapter 9:
Error Conditions.............................................................................................................. 39
Common Issues ............................................................................................................................. 39
Chapter 10:
WAP Provisioning Data Format..................................................................................... 40
Media Type Parameter................................................................................................................... 40
String in Text Format...................................................................................................................... 41
String in Token Format................................................................................................................... 42
Headers (Optional Fields)........................................................................................................ 43
Provisioning Document............................................................................................................ 43
Adapting to GSM SMS Format ................................................................................................ 48
Examples ................................................................................................................................. 50
Appendix A:
Parameter Mapping......................................................................................................... 53
Browser .......................................................................................................................................... 53
MMS: .............................................................................................................................................. 54
SyncML Data Synchronization:...................................................................................................... 54
Email: ............................................................................................................................................. 55
Appendix B:
Compliancy Matrix .......................................................................................................... 57

Page 3
OTA Provisioning Whitepaper

---

Introduction
Summary
Over-the-air (OTA) provisioning (OTAP) is the ability to download and install content over a wireless
network, usually on demand. This whitepaper describes:
• Bootstrap
process
• Configuration
• User Handset Experience
• OTA Provisioning Security Mechanism
• OTA Provisioning of Browser
• OTA Provisioning of MMS
• OTA Provisioning of SyncML Data Synchronization
• OTA Provisioning of Email
• OTA Provisioning of Other Applications
• Error
Conditions
• WAP Provisioning Data Format
• Parameter Mapping
• OMA Static Conformance Requirements Matrix

For more information on OTAP, refer to the OMA Client Provisioning 1.1 specifications:
http://www.openmobilealliance.org/release_program/index.html
Page 4
OTA Provisioning Whitepaper

---

References
• Provisioning Bootstrap Version 1.1, Open Mobile Alliance, OMA-WAP-ProvBoot-v1_1-200211120-C
http://www.openmobilealliance.org
• Provisioning Content Version 1.1, Open Mobile Alliance, OMA-WAP-ProvCont-v1_1-20021112-C
http://www.openmobilealliance.org
• Provisioning User Agent Behavior Version 1.1, Open Mobile Alliance, OMA-WAP-ProvUAB-V1_1-
20021113-C http://www.openmobilealliance.org
• Provisioning Smart Card Specification Version 1.1, Open Mobile Alliance, OMA-WAP-ProvSC-V1_1-
20021112-C http://www.openmobilealliance.org
• Wireless Session Protocol Specification, Open Mobile Alliance, WAP-230-WSP-20010705-a
http://www.openmobilealliance.org
• Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message
Service (SMS), Point-to-Point (PP)
• Digital Cellular Telecommunication System (Phase 2+), Specification of the Subscriber Identity
Module—Mobile Equipment (SIM-ME) interface (GSM11.11 version 7.2.0 Release 1998)
• Secure Hash Standard, NIST FIPS PUB 180-1, National Institute of Standards and Technology, U.S.
Department of Commerce, April 1995.
• HMAC: Keyed-Hashing for Message Authentication, Krawczyk, H., Bellare, M., and Canetti, R.,
February 1997—http://www.ietf.org/rfc/rfc2104.txt
• 3rd Generation Partnership Project, Technical Specification Group Core Network; Mobile radio
interface layer 3 specification, Core Network Protocols—Stage 3 (Release 4), v 4.5.0 (2001-12)
Page 5
OTA Provisioning Whitepaper

---

Revision History
Version
Date
Name
Reason
0.1
October 20, 2003
Adam Grabowski
Initial Draft
1.0
November 3, 2003
Adam Grabowski
Baseline
1.1
January 25, 2005
James Hu
Updated sections for clarity.
2.0
February 8, 2005
Doug Michau
Baseline
2.1
July 5, 2005
Sreenivasulu Rayanki
Updated with SyncML Data Synchronization
3.0
July 6, 2005
Sreenivasulu Rayanki
Baseline
3.1
July 8, 2005
Andrey Vostrikov
Updated with Email
4.0
August 24, 2005
Sreenivasulu Rayanki
Baseline
5.0
May 16, 2007
Shannon Ayres
Converted into new template
Minor updates made
Appendix C removed and relocated to
website, where it can be updated as needed.
Definitions, Abbreviations, Acronyms
Acronym
Description
BCD
Binary Coded Decimal
IMSI International
Mobile Subscriber Identity
MAC
Message Authentication Code
MIB
Motorola Internet Browser
MT Mobile
Terminated
SIM
Subscriber Information Module
OMA
Open Mobile Alliance
OTA Over-the-Air
OTAP Over-the-Air
Provisioning
SEC Security
TID Transaction
Identifier
WBXML
Wireless Binary Extensible Markup Language
SyncML DM
SyncML Device Management
SyncML DS
SyncML Data Synchronization
Web Session
Contains Internet connection settings. Also known as Internet Settings.
OMNA
Open Mobile Naming Authority
IANA
Internet Assigned Numbers Authority
Page 6
OTA Provisioning Whitepaper

---

Chapter 1: Bootstrap Process
The OTAP feature enables carriers and users to provision their handsets for Internet access any time
after purchase. The provisioning server uses the SMS bearer to push the data to the handset. Motorola’s
implementation of the OTAP feature is based on the OMA Provisioning 1.1 specifications. To see the
compliance matrix, refer to Appendix B. The WAP provisioning framework specifies mechanisms that take
a terminal from an unconfigured to a fully configured state (Figure 1):

Figure 1.
WAP Provisioning Framework
Motorola supports the Bootstrap Process to take a handset from the “Unconfigured State” directly to the
“Provisioned State where TPS is undefined.” Motorola does not support the Continuous Provisioning
Process. However, Motorola does support alternate means of continuous provisioning such as OMA
Device Management (a.k.a. SyncML DM).
In the Bootstrap Process, it is imperative that security parameters (such as user pin) are set to prevent
unauthorized provisioning documents from configuring the phone.
Page 7
OTA Provisioning Whitepaper

---

Chapter 2: Configuration
The carrier can configure many aspects of the OTA Provisioning process. The configuration is set up
through handset flexing that is done at the time of manufacture. Although the content developer doesn’t
have control over these settings, he or she should be aware of them because the configuration affects the
OTAP availability, security, and user flow.
The user can also configure some OTA Provisioning options. This chapter discusses both carrier and
user configurations.
Feature Availability
To enable OTAP support, the carrier must configure and enable the following features:
• Browser Messages Folder—Stores provisioning messages.
• Browser Provisioning—Determines whether provisioning messages are processed or discarded.
The following features control other aspects of OTAP:
• Whitelist—Additional security (see Whitelist on page 9)
• Provision Factory Sessions—Determines whether an OTAP session can update or delete sessions
that were provisioned at the time of manufacture. For this to happen, the BOOTSTRAP/NAME in the
OTAP session must match the factory session. For more details, see Modification/Deletion of
Provisioned Session by Operator on page 19.
• Disable Default Session—The carrier can set a default session and disable the user from setting a
different session as the default.
• Set Default Session—This setting is only applicable if the user can change the default session.
Possible settings are:

Off—The OTA provisioning of a new session has no affect on the default browser session.

Automatic—The new session created by OTAP is set as the default browser session.

Manual—The user is prompted as to whether he or she wishes to set the new session—created
by OTAP—as the default browser session.
• Number of Browser Sessions—The maximum limit is thirty, but the carrier can configure fewer
sessions.
• SIM Provisioning—If this feature is enabled and a browser session resides on the SIM, then this
session becomes the new default session. SIM sessions are read-only, so this feature is not
discussed in this document.
Page 8
OTA Provisioning Whitepaper

---

Whitelist
The Whitelist feature provides an additional layer of security. The feature protects against untrusted
parties “spamming” the device with provisioning messages. The Whitelist is a database that contains up
to ten pairs of Originating (TP-OA) / SMSC (MT-SMSC) addresses. Basically, it restricts push (including
provisioning) messages to these addresses. A push message that originates from an unauthorized
Originating or SMSC Address (not in the Whitelist) is discarded.
The carrier can also configure just an SMSC address range check meaning that SMSC must send a push
message from within a specified range of addresses for the message to be accepted.
User Options
The carrier can configure the handset to allow the user to have some control over browser messages—
both push and provisioning messages.
• Browser Message Service—this feature is available only if the carrier has not turned on the Whitelist
It allows the user to screen incoming messages using the following options:

Off—all browser messages are discarded

Receive All—all browser messages are accepted

Restricted—only browser messages that are sent from a specified SMSC are accepted.
• OTAP Session Deletable—if the carrier sets this feature,the user can delete provisioned browser
session entries.
• MMS Session Editable—if the carrier sets this feature,the user can edit the MMS session entries.
• MMS Session Deletable—if the carrier sets this feature,the user can delete the MMS session entries.
Master Clear
A Master Clear operation (under Initial Setup) deletes all of the OTAP and user-configured browser and
MMS sessions. Only the factory-configured sessions (or OTAP updates of the factory sessions) are
preserved.

Page 9
OTA Provisioning Whitepaper

---

Document Outline

• OTA Provisioning Whitepaper, Version 5
  • ÿ
    • ÿ
    • ÿ
  • ÿ
    • ÿ
    • ÿ
  • ÿ
  • ÿ
    • ÿ
  • ÿ
    • ÿ
  • • ÿ
  • ÿ
    • ÿ
  • • ÿ
    • 
    • ÿ
  • • ÿ
  • • ÿ
    • ÿ
      • ÿ
      • ÿ
  • • ÿ
    • ÿ
  • ÿ

---