OMA Client Provisioning Device Management Architecture

  • Article

4/8/2010

When configuring through WAP Push, three components — the Short Message Service (SMS) Router, Push Router, and Configuration Manager — all work together to configure the device.

This section describes how Windows Mobile handles device configuration at the various component levels.

The following diagram illustrates the architecture for device management through over-the-air (OTA) device configuration using the WAP Protocol.

Bb737519.604e7394-8e61-4644-96dd-b0737c53759c(en-us,MSDN.10).gif

An external source, such as the mobile operator, can use the preceding component architecture to update the configuration of Windows Mobile devices. These updates may be generated from the automated billing and provisioning systems that the mobile operator uses.

Note

Microsoft does not provide an OMA Client Provisioning server. The OEM, Operator, or a third party must create their own server. For information about server requirements, see Server Requirements for OMA Client Provisioning.

  1. The Short Message Service (SMS) Router receives the incoming SMS messages from the network and determines the final destination for the message.
  2. The SMS Router delivers the message to the appropriate software component on the device for processing. SMS messages move from the SMS Router to the appropriate layers of the Wireless Application Protocol (WAP) stack. The SMS Router is designed to route messages to one client per provider.
  3. The WAP component decodes the WAP push message and sends it to the Push Router.
  4. The Push Router accepts and processes push messages from a Wireless Session Protocol (WSP) push source.
  5. When the Push Router receives a new message, it is forwarded to the Security Module for authentication and role assignment. After the Security Module processes the message, it sends the message back to the Push Router Core, and the Push Router Core routes the message, which is a configuration request that is encoded in an XML document format, to the Configuration Manager.
    For more information, see Push Router, and Routing Messages for Mobile Operators, and Security for Windows Mobile Devices.
    For more information, see Push Router, and Routing Messages for Mobile Operators.
  6. The configuration manager is the hub of activity for over-the-air (OTA) configuration, downloads, and configuration updates generated by the local applications. This single point of configuration processes a configuration request internally, enables configuration security to be enforced, and enables the control mechanisms to avoid configuration conflicts. The configuration request is encoded in an XML document format. Configuration Manager accepts XML configuration requests from the Push Router.
  7. Configuration manager routes the command to the specific Configuration Service Provider. The Configuration Service Provider processes the command and sends processing result back to the Configuration Manager.

See Also

Other Resources

OMA Client Provisioning