Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Messages are sent from the Push Proxy Gateway (PPG) over the air
to Windows Mobile devices with the WAP Push Over The Air (OTA)
Protocol. The device uses connectionless unsecured push; thus, a
push session does not need to be established before a message can
be delivered. For more detailed information about WAP Push OTA
Protocol, see the Open Mobile Alliance (OMA) specification: Push
Over The Air (OMA-WAP-TS-PushOTA-V2_1-20051122-C), available from
this
The following table shows the Push OTA Protocol features used by the OTA provisioning architecture.
WAP Push OTA Protocol feature | Description |
---|---|
OTA-CL-C-001 Connectionless Push |
Connectionless push is implemented as described in "Connectionless Push" in the OMA Push Over The Air Specification. |
OTA-CL-C-002 Nonsecure Port Used for Connectionless Push |
A nonsecure port is used for connectionless push, as described in "Connectionless Push" in the OMA Push Over The Air Specification. |
OTA-WSP-C-006 Application Addressing |
Push content is delivered to an application as described for a connectionless push in "Application Addressing" in the OMA Push Over The Air Specification. |
OTA-WSP-C-007 Application Dispatching |
Push content is dispatched to an application as described for a connectionless push in "Application Dispatching" in the OMA Push Over The Air Specification. |
OTA-WSP-C-008 Initiator Authentication |
The Push Initiator is authenticated as described in "Initiator Authentication" in the OMA Push Over The Air Specification. |