The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Short Messaging communication services and how the interfaces and protocols comply to standards.
This section describes the standards compliance for the communication services for Parlay X 2.1:
The Parlay X 2.1 interface complies with ETSI ES 202 391-4 Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 2).
See Table 1-12, "Short Messaging Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.
Table 8-1 Statement of Compliance, Parlay X 2.1 Short Messaging
| Method | Compliant? | Comment |
|---|---|---|
|
Interface: SendSms |
NA |
NA |
|
sendSms |
Yes |
NA |
|
sendSmsLogo |
Yes |
Note: The image is not scaled. |
|
sendSmsRingtone |
Yes |
Note: Ringtones must be in either SmartMessaging or EMS (iMelody) format |
|
getSmsDeliveryStatus |
Yes |
NA |
|
Interface: SmsNotification |
NA |
NA |
|
notifySmsReception |
Yes |
NA |
|
notifySmsDeliveryReceipt |
Yes |
NA |
|
Interface: ReceiveSms |
NA |
NA |
|
getReceivedSms |
Yes |
NA |
|
Interface: SmsNotificationManager |
NA |
NA |
|
startSmsNotification |
Yes |
NA |
|
stopSmsNotification |
Yes |
NA |
The SMPP plug-in for Parlay X 2.1 Short Messaging and for the Extended Web Services (Binary SMS) acts as an External Short Message Entity (ESME) that connects to an SMSC over TCP/IP.
The plug-in instance binds itself to the SMSC either as ESME Transmitter and an ESME Receiver or as an ESME Transceiver.
The bindings occurs when the plug-in transitions from state inactive to active. It will not reach state active until it has bound. The plug-in unbinds itself prior to becoming inactive.
When an application sends an SMS with one recipient submit_sm PDU is used and when sending an SMS with 2 or more recipients submit_sm_multi is used.
Window size is configurable.
For application-initiated requests, the plug-in supports segmented SMSs using either 7-, 8-, or 16 bit data coding. The maximum length of an SMS segment is:
160 Characters for 7 bit data coding (SMSC default alphabet).
140 Characters for 8 bit data coding (ASCII).
70 Characters for 16bit coding (UCS2).
For network-triggered requests, the plug-in supports segmented SMSs in the same way as for application-initiated requests if the SMPP parameter short_message contains the user data. If short_message is empty the parameter message_payload, which can contain up to 64KB of data, is used.
For network-triggered requests, the SMS is propagated to the application through the Parlay X Short Messaging interface if the SMPP parameter data_coding equals 0x00, 0x01, 0x03, 0x05, 0x06, 0x07, 0x08, 0x0A, 0x0D, or 0x0E. In other cases, the SMS is forwarded to the application through the Binary SMS interface.
This plug-in complies with the Short Message Peer to Peer, Protocol Specification. See "Audio Call Specification Compliance Table" for the supported versions of this specification and links to their locations.
Note:
The Platform Test Environment interface supports both SMPP 3.4 and 5.0 specifications, but silently ignores any 5.0-specific fieldsTable 8-2 Statement of Compliance, SMPP v3.4/5.0 for Parlay X 2.1 Short Messaging
| Protocol Data Units (PDUs) | Compliant(Yes | No) | Comment |
|---|---|---|
|
Plug-in originated PDUs: |
NA |
NA |
|
bind_transmitter |
Yes |
NA |
|
bind_receiver |
Yes |
NA |
|
unbind |
Yes |
NA |
|
submit_sm |
Yes |
NA |
|
submit_multi |
Yes |
NA |
|
deliver_sm_resp |
Yes |
NA |
|
cancel_sm |
Yes |
NA |
|
enquire_link |
Yes |
NA |
|
enquire_link_resp |
Yes |
NA |
|
generic_nack |
Yes |
NA |
|
bind_transceiver |
Yes |
NA |
|
data_sm |
No |
NA |
|
data_sm_resp |
No |
NA |
|
query_sm |
No |
NA |
|
replace_sm |
No |
NA |
|
interface_version |
Yes |
Only with a value of 5.0. |
|
ussd_service_operation |
Yes |
NA |
|
SMSC originated PDUs: |
NA |
NA |
|
bind_transmitter_resp |
Yes |
NA |
|
bind_receiver_resp |
Yes |
NA |
|
unbind_resp |
Yes |
NA |
|
submit_sm_resp |
Yes |
esm_classes:
|
|
submit_multi_resp |
Yes |
NA |
|
deliver_sm |
Yes |
NA |
|
cancel_sm_resp |
Yes |
NA |
|
enquire_link |
Yes |
NA |
|
enquire_link_resp |
Yes |
NA |
|
generic_nack |
Yes |
NA |
|
bind_transceiver_resp |
Yes |
NA |
|
outbind |
No |
NA |
|
data_sm |
No |
NA |
|
data_sm_resp |
No |
NA |
|
query_sm_resp |
No |
NA |
|
replace_sm_resp |
No |
NA |
|
alert_notification |
No |
NA |
The Parlay X 2.1 Short Messaging and EWS Binary SMS communication services support the following features, which are defined in the Short Message Peer-to-Peer Protocol Specification. Services Gatekeeper supports these features as tunneled parameters.
Table 8-3 SMPP v5.0 for Parlay X 2.1 Short Messaging Tunneled Parameters
| Parameter | Section in Specification | Comments |
|---|---|---|
|
billing_identification |
4.8.4.3 |
NA |
|
ussd_service_operation |
4.8.4.64 |
Version 5.0 added support to deliver_sm for bidrectional USSD. |
|
interface_version |
4.7.13 |
The Native SMPP Service accepts 5.0 as well as 3.4 as the interface version number. |