1.) OMA (Open Mobile Alliance) Provisioning Content (root XML element “wap-provisioningdoc”)
2.) OMA (Open Mobile Alliance) DRM Rights Objects (root XML element “o-ex:rights”)
3.) WAP Push Service Indication, Service Load and Cache Operation (root XML element “si”, “sl”, or “co”)
4.) OMA (Open Mobile Alliance) E-Mail Notification (EMN) (root XML element “emn”)
5.) Nokia/Ericsson Over The Air Settings (OTA) Specification (root XML element ”CHARACTERISTIC-LIST”)
6.) Nokia/Ericssson SyncML OTA or Wireless Village Settings (root XML element “SyncSettings” or “WVSettings”)
There are three different types of PINs, depending on the “OTA PIN Type” ($otapintype) setting.
The simplest “OTA PIN Type” is “USERPIN” (User PIN). This setting indicates that a short PIN code (often 4 digits) is supplied as the “OTA PIN”. When the user receives the OTA settings message, they will need to supply this PIN code in order to be able to open the message and apply the settings. If a “PINValue” is specified, but a “PINType” is not, then USERPIN will be assumed.
“NETWPIN” (Network PIN) indicates the PIN is a network PIN code. In the GSM environment, this is the IMSI number associated with the SIM card in the device. (Hint, if you want to experiment with determining the PIN card associated with a SIM, you can put the SIM into a GSM modem and the AT+CIMI command to return the IMSI. However, not all GSM modems support the AT+CIMI command.) When the device receives the settings, if the NETWPIN does not match the IMSI, the settings will be discarded.
An additional type of PIN, known as “USERNETWPIN” also exists, which indicates a combination of the USERPIN and NETWPIN types. To use this OTA PIN type, specify the OTA PIN as the IMSI number associated with the SIM card in the device, followed by a “:” character, followed by a USERPIN (e.g., 1234567889012345:1234). When the device receives the settings, the user will be prompted for a PIN. This user supplied PIN, and the SIM card IMSI, must match in order for the settings to be accepted.
Related pages:
- Send OMA Client Provisioning (OTA XML Settings) from the Command Line Three years ago on our discussion board we posted a simple Windows JScript that could be used to send an...
- Send XML Settings The “Send XML Settings” Document provides greater flexibility for the sending out of custom XML Settings documents, above and beyond...
- Sending XML Settings Documents and Objects To send an XML Settings Document via a menu driven interface, please see the help section titled Web Menu Interface....
- Creating a Bookmark using OMA Client Provisioning A recent posting on the NowSMS discussion board raised an interesting question. How do you use OMA Client Provisioning to...
- Send OMA OTA Settings NowSMS supports sending OTA (Over-the-Air) configuration information to mobile phones that are compatible with the Open Mobile Alliance (OMA) Provisioning...
- Send WAP OTA Settings NowSMS supports sending OTA (Over-the-Air) configuration information to mobile devices in order to configure some phone settings, such as internet...
- Sending OMA Provisioning Content OTA Messages Sending OMA Provisiong Content over HTTP To send an OMA Provisioning Content OTA message via a menu driven interface, please...
- Provisioning MMS Short Codes on the NowSMS MMSC When using the NowSMS MMSC as an operator MMSC, one frequently asked question is how to provision short codes for...
- Query NowSMS Server Status Starting with the NowSMS 2008 release, an XML-based status query interface is available which reports information similar to what is...
- Send Voice Mail Notification Voice Mail Notification Messages are special SMS messages that are used to tell the user that they have voice mail...
Topic Category: OMA Client Provisioning, OTA, PHP
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...

Click here to download a free trial version of NowSMS & MMS Gateway, NowSMS Lite or NowWAP Gateway.
Learn more about NowSMS Lite.