The WAP Push over SMPP Web
service implementation provides a Web service that accepts requests
for sending WAP Push messages, that control various checks which are
done to ensure that the requests are valid. It will then forward the
requests to the appropriate network elements for downstream processing.
The WAP Push service implementation will then forward the delivery
receipt notifications to the appropriate sender applications.
WAP Push over SMPP asynchronous
call flow
The following steps show an example of the Asynchronous
sendWAPPushSI call flow.
- The client application invokes a sendWAPPushSI operation.
- The request will be queued in the JMS Que for further processing.
- WAP Push over SMPP sends
the WAPPush message request through the JCA adapter to the SMSC using
a submit_sm (for a single target) or submit_sm_multi (for
multiple targets) PDUs.
- The SMSC returns a submit_sm_resp or submit_sm_multi_resp PDU
response through the SMPP JCA adapter to the WAP Push over SMPP service.
- The WAP Push over SMPP service
returns a Transaction ID to the client application.
- The SMSC then forwards the WAPPush message to the targeted mobile
device.
- If the confirm delivery option is opted, a delivery_sm PDU
will be sent by the SMSC with a final delivery status through the
JCA adapter to the WAP Push over SMPP.
- The WAP Push over SMPP service
invokes a notifyWAPPushDeliveryReceipt Web service
call on the notification client application.
WAP Push over SMPP synchronous
call flow
The following steps show an example of the Synchronous
sendWAPPushSI call flow.
- The client application invokes a sendWAPPushSI operation.
- The WAP Push over SMPP sends
the WAPPush message request through the JCA adapter to the SMSC using submit_sm (for
a single target) or submit_sm_multi (for multiple
targets) PDUs.
- The SMSC returns a submit_sm_resp or submit_sm_multi_resp PDU
response through the SMPP JCA adapter to the WAP Push over SMPP service.
- The WAP Push over SMPP service
returns a network ID as response to the client.
- The SMSC then forwards the WAPPush message to the targeted mobile
device.
Interfaces
- SendWAPPush
Note: The SendWAPPush interface is provided as a Web service.
- sendWAPPushSI
- Sends a WAP Push message request.
- sendWAPPushSL
- Not supported.
- sendWAPPushCO
- Not supported.
- getWAPPushDeliveryStatus
- Retrieves the status request for the previous WAP Push delivery.
- WAPPushNotification
Note: The WAPPushNotification interface is used as a client only.
- notifyWAPPushDeliveryReceipt
- Notifies the application when a WAP Push message is delivered,
when a message is delivered to the terminal of the recipient, or when
delivery is impossible.
SMPP operations
The SMPP JCA adapter supports the following SMPP operations:
- bind_transceiver: The SMPP supports the bind_transceiver operation, with which an ESME can bind to an SMSC as a transceiver (called an ESME transceiver).
- bind_transmitter: The SMPP supports the bind_transmitter operation, with which an ESME can bind to an SMSC as a transmitter (called an ESME transmitter).
- bind_receiver: The SMPP supports the bind_receiver operation, with which an ESME can bind to an SMSC as a receiver (called an ESME receiver).
- unbind: Registers an ESME instance of SMSC, which informs the SMSC of the discontinued use of the network connection for the submission of delivery messages.
- generic_nack: A generic negative acknowledgement to an SMPP PDU submitted with an incorrect message header.
- submit_sm: Uses the ESME to submit short messages to the SMSC for onward transmissions of a specified SME. This operation does not support the transaction message mode.
- submit_multi: Can be used to submit an SMPP message for the delivery of one or multiple recipients to a distribution list. This operation does not support the transaction message mode.
- deliver_sm: Issued by the SMSC to send a message to an ESME. Using this command, the SMSC can route a short message to the ESME for delivery confirmation.
- enquire_link: A message that can be sent by either an ESME or an SMSC to provide a confidence check of the communication path between the ESME and the SMSC. On receipt of this request, the receiving party should respond with an enquire_link_resp. This verifies that the application-level connection between the ESME and the SMSC is functioning.
Note: Enquire_link requests sent to the servers in a cluster are handled by only one server in that cluster.