The Extended Web Services Binary SMS Web Service allows for the sending and receiving of any generic binary content via SMS. Both application-initiated and network-triggered requests are supported. The binary content can be other than the Logos and Ringtones as specified by Parlay X Short Messaging. An example would be a vCard.
The BinarySMS interface and service use the namespaces:
The BinarySmsNotificationManager interface and service use the namespaces:
In addition, Extended Web Services Binary SMS uses common data type definitions common for all Extended Web Services interfaces, see Extended Web Services Common.
Fault definitions are according to ETSI ES 202 391-1 V1.2.1 (2006-10) Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2).
The endpoint for the BinarySMS interface is: http://<host:port>/ews/binary_sms/BinarySms
The endpoint for the BinarySmsNotificationManager interface is: http://<host:port>/
ews/binary_sms_notification/BinarySmsNotificationManager
The values for host and port depend on the specific Oracle Communications Services Gatekeeper deployment.
The following diagram shows the general message sequence for sending a binary SMS message from an Extended Web Services Binary SMS application to the network. In this message sequence the application also receives a notification from the network indicating the delivery status of the SMS, that is that the message has reached its destination. It also displays how an application can query the delivery status of the message.
The interaction between the network and Oracle Communications Services Gatekeeper is illustrated in a protocol-agnostic manner. The exact operations and sequences depend on which network protocol is being used.
Note: | The delivery notifications are sent from the Parlay X 2.1 Short Messaging implementation. |
The following diagram shows the general message sequence for receiving a binary SMS message from the Network using Oracle Communications Services Gatekeeper. In this message sequence the application also subscribes for a notifications on network triggered short messages.
The interaction between the network and Oracle Communications Services Gatekeeper is illustrated in a protocol-agnostic manner. The exact operations and sequences depend on which network protocol is being used.
The following data structures are used in the Extended Web Services Binary SMS Web Service.
Defines the binary payload of the SMS for application-initiated messages.
Defines the binary payload of the SMS for network-triggered messages.
Defines the TP-User Data (TP-UD). For a description of TP-User Data (TP-UD), TP-User-Data-Header-Indicator (TP UDHI), see 3GPP TS 23.040 V6.5.0, Technical realization of the Short Message Service (SMS) at
http://www.3gpp.org/ftp/Specs/html-info/23040.htm.
|
|||
Operations to send SMSs with binary content.
Sends an SMS with any binary data as content.
An array comprised of UDH elements and message elements, see BinaryMessage structure.
|
|||
TP-Protocol-Identifier (TP-PID) according to 3GPP TS 23.040 V6.5.0, Technical realization of the Short Message Service (SMS) at
http://www.3gpp.org/ftp/Specs/html-info/23040.htm.
|
|||
Operations to start and stop subscriptions for notifications for short messages with binary content.
Starts a subscription for notifications for short messages that have content in the form of binary data. A correlator is provided in the request. This correlator is used when stopping the subscription.
Stops a previously started subscription for notifications for short messages that have content in the form of binary data. A correlator is provided in the request. This correlator was provided when the subscription was started, see Operation: StartBinarySmsNotification.
This interface shall be implemented by the application. It is used by Oracle Communications Services Gatekeeper to deliver short messages with binary content to an application. Only messages that match a previously started subscription for notifications are delivered.
Note: | Notifications on delivered short messages are delivered using the Parlay X 2.1 Short Messaging SmsNotification interface, using the method NotifySmsDeliveryReceipt. |
Oracle Communications Services Gatekeeper calls this methods on
The notification is used to send a short message with binary content to the application. The notification occurs if the short message matched the criteria specified when starting the notification. See Operation: StartBinarySmsNotification.
The method must be implemented by a Web Service at the application side. It is be invoked by Oracle Communications Services Gatekeeper when it receives a short message with binary content form the network and the criteria is fulfilled.
The document/literal WSDL representation of the interfaces can be retrieved from the Web Services endpoints, see Endpoints.
The notification interface can be downloaded from:
http://host:port/ews/binary_sms_notification/wsdls/ews_binary_sms_notification_service.wsdl
http://host:port/ews/binary_sms_notification/wsdls/ews_binary_sms_notification_interface.wsdl
Where host and port are depending on the Oracle Communications Services Gatekeeper deployment.
The following error codes are defined for SVC0001: Service error:
The following error codes are defined for EPOL0001: Policy error:
BinarySmsService service = new BinarySmsService_Impl(“http://localhost:8001/ews/binary_sms/BinarySms?WSDL”);
BinarySms port = service.getBinarySms();
com.bea.wlcp.wlng.schema.ews.binary_sms.local.SendBinarySms parameters =
new com.bea.wlcp.wlng.schema.ews.binary_sms.local.SendBinarySms();
URI[] addresses = new URI[1];
addresses[0] = new URI("tel:1234");
parameters.setAddresses(addresses);
parameters.setDcs((byte)0);
parameters.setProtocolId((byte)0x7b);
parameters.setSenderName("tel:7878");
parameters.setValidityPeriod("020610233429000R");
com.bea.wlcp.wlng.schema.ews.binary_sms.BinaryMessage[] binaryMessages =
new com.bea.wlcp.wlng.schema.ews.binary_sms.BinaryMessage[1];
binaryMessages[0] = new com.bea.wlcp.wlng.schema.ews.binary_sms.BinaryMessage();
byte[] udh = {0};
byte[] message = {0x4d, 0x61, 0x64, 0x65, 0x20, 0x69, 0x6e, 0x20, 0x2e};
binaryMessages[0].setUdh(udh);
binaryMessages[0].setMessage(message);
parameters.setBinaryMessage(binaryMessages);
port.sendBinarySms(parameters);