![]() ![]() ![]() ![]() ![]() ![]() |
The Extended Web Services Binary SMS Web Service allows for the sending of any generic binary content via SMS. The binary content can be other than the Logos and Ringtones as specified by Parlay X SMS Web service. An example would be a vCard.
Applications can poll for the delivery status of a message sent using this interface using GetSmsDeliveryStatus as specified in Parlay X 2.1 Part 4: Short messaging, Interface: SendSms.
Applications can receive asynchronous delivery notifications for messages sent using this interface by implementing NotifySmsDeliveryReceipt as specified in Parlay X 2.1 Part 4: Short messaging, Interface: ReceiveSms.
The BinarySMS 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 values for host and port depend on the specific Network 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 Network 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 data structures are used in the Extended Web Services Binary SMS Web Service.
Defines the binary payload of the SMS.
The following describes the interfaces and operations that are available in the Extended Web Services Binary SMS Web Service.
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).
|
|||
The document/literal WSDL representation of the BinarySms interface can be retrieved from the Web Services endpoint.
Where host and port are depending on the Network 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);
![]() ![]() ![]() |