Update settings sent via OMA or OTA

Update settings sent via OMA or OTA SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » Update settings sent via OMA or OTA « Previous || Next »
Author Message
Bjoern Michalik
New member
Username: Mastergeneric

Post Number: 3
Registered: 09-2004
Posted on Tuesday, April 26, 2005 - 02:46 pm:   

Hi there,

is there any way to "update" a setting sent in a former provisioning SMS (OMA).
I mean for example:
- In the first SMS I send SyncML settings for Contacts
- In the second SMS I send SyncML settings for Contacts and Calendar.
--> Result: I have just one profile with settings for Contacts and Calendar

In a way this is also something like "overriding" existing settings.

I made a couple of tests (all with Nokia devices) with Bootstrap etc. as described in some Nokia documents but always got a second profile/setting (with the same name of cause) entered in the Sync application.

It also didn’t work to delete a setting from a Nokia device by just sending the same Bootstrap as in the provisioning document of the profile which shall be deleted. With a Motorola device it worked fine.

Hope anybody can help me!


Ps.: In addition to this, what about the OTA standard?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4407
Registered: 10-2002
Posted on Tuesday, April 26, 2005 - 08:07 pm:   

Hi Bjoern,

I can only confirm that this seems to be a problem with Nokia Series 60 devices (and possibly some others).

Maybe someone else will be able to offer more insight ...

I see the same behaviour when sending SyncML settings to that device.

And with browser settings, it appends "(01)", "(02)" to the name, creating more additional settings.

The Nokia OTA docs don't mention any support for the BOOTSTRAP/NAME parameter, while it is mentioned in Motorola's OTA docs. (And the ability to delete a setting which is defined in the Motorola docs is specific to their implementation, as there is no mention in the OMA Provisioning Content spec about this.)

Ideally, if the client receives settings with a name that is already in use for existing settings, it should prompt to ask if the user wishes to "replace existing settings".

But unfortunately, most client OTA implementations are less than the ideal.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics