14 Extended Web Services WAP Push

The following chapter describes the standard Oracle Communications Services Gatekeeper communication services and how the interfaces and protocols complies to standards.

• Extended Web Services WAP Push

• WAP Push for Extended Web Services WAP Push

Extended Web Services WAP Push

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 shall adhere to:

• WAP Service Indication Specification, as specified in Service Indication Version 31-July-2001 Wireless Application Protocol WAP-167-ServiceInd-20010731-a.

• WAP Service Loading Specification, as specified in Service Loading Version 31-Jul-2001 Wireless Application Protocol WAP-168-ServiceLoad-20010731-a.

• WAP Cache Operation Specification, as specified in Cache Operation Version 31-Jul-2001 Wireless Application Protocol WAP-175-CacheOp-20010731-a.

See http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html for links to the specifications.

WAP Push for Extended Web Services WAP Push

The WAP Push plug-in for Extended Web Services WAP Push acts as an Push Initiator towards 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 towards the Location Server.

Standards Compliance

The plug-in complies to Push Access Protocol, WAP Forum™, WAP-247-PAP-20010429-a.

The specification is found on http://www.openmobilealliance.org

Table 14-1 Statement of Compliance, WAP Push for Extended Web Services WAP Push

Operation	Compliant(Yes | No)	Comment
push-message	Y
push-response	Y
cancel-message	N
cancel-response	N
resultnotification-message	Y
resultnotification-response	Y
statusquery-message	N
statusquery-response	N
ccq-message	N
ccq-response	N
badmessage-response	Y