Share via

Push Router

  • Article

The Push Router component of the device management scheme is the central location for receiving, authenticating, and forwarding all of the incoming push provisioning messages. The Push Router is responsible for determining the type of incoming push message and for passing the message to the matching client application to run the provisioning file.

Push Router tasks include the following:

  • Accept push provisioning messages, and authenticate the origin by using the Security Module that is part of the Push Router component.
  • Assign a security role to the message, through the Security Module, based on the origin of the push message and authentication method.
  • Forward the relevant message with the assigned security role to the client application.
  • The Push Router can accept data over the air through the Push Proxy Gateway (PPG) over the Global System for Mobile Communications (GSM) Short Message Service (SMS) network, or as a download through Microsoft® Pocket Internet Explorer.

The following diagram illustrates the Push Router architecture for Windows Mobile™-based Smartphone and Pocket PC.

  • SMS Router
    The Short Message Service (SMS) Router is the first OS-level software component to receive incoming SMS messages from the network. It accepts SMS messages, determines their final destination, and delivers them 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. For more information, see SMS Router.

  • WAP Stack
    The WAP component decodes the WAP push message and sends it to the Push Router.

  • WSP Push Source
    The Push Router can be configured to accept and process push messages from a Wireless Session Protocol (WSP) push source. This entry point receives push messages and passes information to the Push Router Core by means of the Source Interface.

    The WSP push source accepts only Wireless Application Protocol (WAP) connectionless nonsecure push messages that conform to the WAP push message format. For more information about the WAP Push Message, see WAP Push Message Format.

  • Push Router Core
    The push router core is initially processes an incoming push message, routes the message, and exposes the communication interfaces for the client and source components.

    When the Push Router Core 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.

  • Security Module
    This an autonomous component within the Push Router Core. It authenticates an incoming push message and assigns a security role to it. The Push Router handles submissions to the Security Module.

    As a guideline, Smartphone and Pocket PC use all authentication methods defined in the WAP Provisioning Bootstrap Specification, WAP-184-PROVBOOT, Version 14-March-2001. This specification is at https://www.wapforum.org/.

    After the Security Module processes the message, it sends the message back to the Push Router Core. For more information, see Security Overview.

  • Client application
    Client applications receive and execute push messages. Client Applications receive the push payloads with the assigned security role through the Client Interface of the Push Router Core.

  • Configuration Manager
    This is the hub of activity for over-the-air (OTA) configuration, downloads, and configuration updates generated by the local settings control panel. 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. For more information, about the Configuration Manager, see Data from Push Router and Configuration Manager.

See Also

Device Management for Windows Mobile Devices | WAP Push Message Format | Setting Push Router Policies | WAP Push OTA Protocol Features | Provisioning OTA Through a WAP Push

Send feedback on this topic to the authors.

© 2005 Microsoft Corporation. All rights reserved.