An Overview of the Extended Web Services WAP Push Communication Service
The SOAP Service Facade WAP Push communication service implements the Oracle Extended Web Services WAP Push interface. Although the specific interface is not standardized, it uses standardized elements. For more information on these elements, see “Appendix A: Standards and Specifications” in Concepts and Architectural Overview, another document in this set.
Note:
The RESTful Service Facade WAP Push interfaces provide RESTful access to this same functionality. The internal representations are identical, and for the purposes of creating SLAs and reading CDRs, etc., they are the same.
Using the WAP Push communication service, an application can:
Send a WAP Push message
Send a replacement WAP Push message
Ask to be notified asynchronously of the status of WAP Push messages that have been sent. The possible values returned include:
Rejected: The message was not accepted
Pending: The message is in process
Delivered: The message was successfully delivered to the end-user
Undeliverable: The message could not be delivered because of a problem
Expired: The message reached the maximum age allowed by server policy or could not be delivered by the time specified in the push submission
Aborted: The mobile device aborted the message
Timeout: The delivery process timed out
Cancelled: The message was cancelled through the cancel operation
Unknown: The server does not know the state of the message
Note:
The result notification message is only sent if the initial push submission was accepted for processing. One result notification message is sent per destination address.
Supported Network Protocols
Off the shelf, the Extended Web Services WAP Push communication service can be configured to support the following network protocol:
When Oracle Communications Services Gatekeeper is configured to use this protocol, the EWS WAP Push communication service supports a subset of its operations including:
push-message: Submits a message to be delivered. This operation is also used to send a replacement message
push-response: The response to the push-message operation. This response includes a code specifying the immediate status of the message submission, of the following general types:
1xxx Success: The action was successfully received, understood, and accepted
2xxx Client Error: The request contains bad syntax or cannot be fulfilled
3xxx Server Error: The server failed to fulfil an apparently valid request
4xxx: Service Failure: The service could not be performed. The operation may be retried
resultnotification-message: Specifies the final outcome of a specific message for a specific recipient. Sent only if the initial request includes the URL to which this notification is to be delivered. Includes both textual indication of state and a status code including the following general types:
1xxx Success: The action was successfully received, understood, and accepted
2xxx Client Error: The request contains bad syntax or cannot be fulfilled
3xxx Server Error: The telecom network node failed to fulfil an apparently valid request
4xxx: Service Failure: The service could not be performed. The operation may be retried
5xxx: Mobile Device Abort: The mobile device aborted the operation.
resultnotification-response: The response to the result notification. This response includes a code specifying the status of the notification
1xxx Success: The action was successfully received, understood, and accepted
2xxx Client Error: The request contains bad syntax or cannot be fulfilled
badmessage-response: A response indicating that request is unrecognizable or is of a protocol version that is not supported. This response contains either a 3002 code (Version not supported) or a 2000 code (Bad Request). In the case of Bad Request, a fragment of the unrecognizable message is included in the response
See “Appendix A: Standards and Specifications” in Concepts and Architectural Overview for the exact version of the protocol standard Oracle Communications Services Gatekeeper supports.
Configuration Specifics for the WAP Push Communication Service
Communication services share many common features, covered in “Introducing Communication Services” in Concepts and Architectural Overview, but each one has a few characteristics that are specific only to that service. This section describes those specific features for the WAP Push communication service, including:
Table 14-1 Event types emitted by the EWS WAP Push Message communication service
EdrId
Meaning
14001
sendPushMessage
14002
sendResultNotificationMessage
Statistics
Table 14-2 outlines the correlation between the methods being invoked from either the application (in application-initiated requests) or the telecom network (in network-initiated requests) and the transaction type collected by the statistics counters in Oracle Communications Services Gatekeeper for the Parlay X 2. Multimedia Messaging communication service:
Note:
Method names for network-initiated requests are specified by the internal Gatekeeper name, which is not necessarily the same as the message from the network.
Table 14-2 Transaction types for EWS WAP Push Message communication service
Method
Transaction type
sendPushMessage
TRANSACTION_TYPE_MESSAGE_SENDER_SEND
sendResultNotificationMessage
TRANSACTION_TYPE_MESSAGE_SENDER_NOTIFY
Supported Address Schemes
The EWS WAP Push Message communication service supports the tel: and wapuser: address schemes.
