Share via

Bluetooth AllowedProfiles Example for OMA Client Provisioning

  • Article

4/8/2010

The NetworkPolicy Configuration Service Provider example below can be used to enable only the Bluetooth network interface or interfaces which are specified through the AllowedProfiles characteristic and corresponding parameter values.

In this example, three Bluetooth network interfaces are enabled corresponding to the parameter values "{0000111F-0000-1000-8000-00805F9B34FB}", "{0000110A-0000-1000-8000-00805F9B34FB}", and "{0000110C-0000-1000-8000-00805F9B34FB}".

Code Example

<characteristic type="NetworkPolicy">
  <characteristic type="Bluetooth">
    <characteristic type="AllowedProfiles">
      <parm name="{0000111F-0000-1000-8000-00805F9B34FB}" value=""/>
      <parm name="{0000110A-0000-1000-8000-00805F9B34FB}" value=""/>
      <parm name="{0000110C-0000-1000-8000-00805F9B34FB}" value=""/>
    </characteristic>
  </characteristic>
</characteristic>

Remarks

One provisioning XML file typically contains configuration information for multiple configuration service providers. To use this example, you must replace the values as appropriate, and add the node as a child of the wap-provisioningdoc element in an OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

The example above is treated as an Add operation, as opposed to a Replace operation, so this means that if some profiles were already configured to be in the allowed profile list, then this operation would add additional profiles to the list.

Parameter values can also be deleted from the allowed profile list. For more information on deleting profiles from the allowed profile list, see Remove Bluetooth AllowedProfiles Example for OMA Client Provisioning.

See Also

Reference

NetworkPolicy Configuration Service Provider

Concepts

NetworkPolicy Configuration Service Provider Examples for OMA Client Provisioning