Topic Keywords: OMA Client Provisioning, OTA, PHP
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.
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...