The following chapter describes the standard Oracle Communications Services Gatekeeper Extended Web Services WAP Push communication services and how the interfaces and protocols comply to standards.
This section describes the standards compliance for the communication services for Extended Web Services WAP Push:
The Extended Web Services interface is an interface defined by Oracle, but it is based on the patterns present in the Parlay X 2.1 interfaces.
The payload of a WAP Push message adhere to the specifications listed in Table 1-17, "WAP Push Communication Service Specifications". See that table for a list of the supported specifications and links to their locations.
The WAP Push plug-in for Extended Web Services WAP Push acts as an Push Initiator toward a Push Proxy Gateway using the PAP interface. The plug-in connects to the Push proxy Gateway using HTTP.
The plug-in always acts as one single Push Initiator toward the Location Server.
The plug-in complies to Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. See Table 1-1, "Audio Call Specification Compliance Table" for the supported specification and a link to its location.
Table 16-1 Statement of Compliance, WAP Push for Extended Web Services WAP Push
| Operation | Compliant? | Comment |
|---|---|---|
|
push-message |
Yes |
NA |
|
push-response |
Yes |
NA |
|
cancel-message |
No |
NA |
|
cancel-response |
No |
NA |
|
resultnotification-message |
Yes |
NA |
|
resultnotification-response |
Yes |
NA |
|
statusquery-message |
No |
NA |
|
statusquery-response |
No |
NA |
|
ccq-message |
No |
NA |
|
ccq-response |
No |
NA |
|
badmessage-response |
Yes |
NA |