SMPP PICS

Short Message Peer-to-Peer (SMPP) API 
Abbreviated SMPP Protocol Implementation Conformance Statement (PICS)

Contents

3Short.*

Introduction


This document describes the SMPP implementation used in the services operated by HSL Mobile.

Operations Supported

Item

Functional Unit/Description

SMPP REF.

Supported
YES / NO

PDU-OUTBIND

Is the outbind PDU supported?

4.1.7

NO

PDU-BIND-TRANSMITTER

Is the bind transmitter PDU supported?

4.1.14.1.2

YES

PDU-BIND-RECEIVER

Is the bind receiver PDU supported?

4.1.34.1.4

YES

PDU-BIND-TRANSCEIVER

Is the bind transceiver PDU supported?

4.1.54.1.6

YES

PDU-UNBIND

Is the unbind PDU supported?

4.2.1
4.2.2

YES

PDU-ESME-GENERIC-NACK

Is the generic_nack PDU initiated by the EMSE supported?

4.3.1

YES

PDU-SMSC-GENERIC-NACK

Is the generic_nack PDU initiated by the SMSC supported?

4.3.1

YES

PDU-SUBMIT-SM

Is the submit_sm PDU supported?

4.4.1
4.4.2

YES

PDU-SUBMIT-MULTI

Is the submit_multi PDU supported?

4.5.1
4.5.2

NO

PDU-DELIVER-SM

Is the deliver_sm PDU supported?

4.6.1
4.6.2

YES

PDU-ESME-DATA

Is the data_sm PDU initiated by the EMSE supported?

4.7.1

YES

PDU-SMSC-DATA

Is the data_sm PDU initiated by the SMSC supported?

4.7.1

YES

PDU-QUERY

Is the query_sm PDU supported?

4.8.1
4.8.2

YES

PDU-CANCEL

Is the cancel_sm PDU supported?

4.9.14.9.2

YES

PDU-REPLACE

Is the replace_sm PDU supported?

4.10.14.10.2

NO

PDU-ESME-ENQUIRE-LINK

Is the enquire_link PDU initiated by the EMSE supported?

4.11.1
4.11.2

YES

PDU-SMSC-ENQUIRE-LINK

Is the enquire_link PDU initiated by the SMSC supported?

4.11.1
4.11.2

YES

PDU-ALERT

Is the alert_notification PDU supported?

4.12.1

NO

BIND PDU

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

BIND-1

Is sc_interface_version field supported in a response to the operation?

4.1.2, 4.1.4 4.1.6

YES

BIND-2

Is the interface_version field supported in the bind_transceiver operation?

Errata, 4.1.5

YES

SUBMIT_SM PDU

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

SUBMIT-1

Is the use of different values in the service_type field allowed?

5.2.11

YES

SUBMIT-2

Is the use of default values in the source_addr fields supported?

5.2.8

YES

SUBMIT-3

Is scheduled_delivery supported?

5.2.15

YES

SUBMIT-4

Is the replace_if_present functionality supported?

5.2.18

YES

SUBMIT-5

Are pre-defined short messages supported?

5.2.23

NO

SUBMIT-6

Is the use of the validity_period field supported?

5.2.16

YES

SUBMIT-7

Is the user_message_reference field supported?

5.3.2.17

YES

SUBMIT-8

Is the source_port field supported?

5.3.2.20

NO

SUBMIT-9

Is the destination_port field supported?

5.3.2.21

NO

SUBMIT-10-1

Is the sar_msg_ref_num, field supported?

5.3.2.22

NO

SUBMIT-10-2

Is the sar_total_segments field supported?

5.3.2.23

NO

SUBMIT-10-3

Is the sar_segment_seqnum field supported?

5.3.2.24

NO

SUBMIT-11

Is the more_messages_to_send field supported?

5.3.2.34

NO

SUBMIT-12

Is the message_payload field supported?

5.3.2.32

NO

SUBMIT-13

Is the privacy_indicator field supported?

5.3.2.14

NO

SUBMIT-15

Is the source_subaddress field supported?

5.3.2.15

NO

SUBMIT-16

Is the dest_subaddress field supported?

5.3.2.16

NO

SUBMIT-20

Is the ms_validity field supported?

5.3.2.27

NO

SUBMIT-21

Is the number_of_messages field supported?

5.3.2.39

NO

SUBMIT-22

Is the alert_on_msg_delivery field supported?

5.3.2.41

NO

SUMBIT-26

What is the maximum length of message_payload data supported?

5.3.2.32

N/A

SUMBIT-27

Is the payload_type field supported?

5.3.2.10

NO

SUMBIT-28

Is the source_addr_subunit field supported?

5.3.2.2

NO

SUMBIT-29

Is the dest_addr_subunit field supported?

5.3.2.1

NO

SUMBIT-30

Is the ms_msg_wait_facilities field supported?

5.3.2.13

NO

DELIVER_SM PDU

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

DELIVER-1

Is the use of different values in the service_type field allowed?

5.2.11

YES

DELIVER-2

Is the user_message_reference field supported?

5.3.2.17

YES

DELIVER-3

Is the source_port field supported?

5.3.2.20

YES

DELIVER-4

Is the destination_port field supported?

5.3.2.21

YES

DELIVER-5-1

Is the sar_msg_ref_num field supported?

5.3.2.22

YES

DELIVER-5-2

Is the sar_total_segments field supported?

5.3.2.23

YES

DELIVER-5-3

Is the sar_segment_seqnum fields supported?

5.3.2.24

YES

DELIVER-6

Is the user_response_code field supported?

5.3.2.18

NO

DELIVER-7

Is the privacy_indicator field supported?

5.3.2.14

NO

DELIVER-8

Is the message_payload field supported?

5.3.2.32

YES

DELIVER-9

Is the callback_num field supported?

5.3.2.38

NO

DELIVER-10

Is the source_subaddress field supported?

5.3.2.15

NO

DELIVER-11

Is the dest_subaddress field supported?

5.3.2.16

NO

DELIVER-12

Is the network_error_code field supported?

5.3.2.31

YES

DELIVER-13

Is the its_session_info field supported?

5.3.2.43

NO

DELIVER-15

Is the message_state field supported?

5.3.2.35

YES

DELIVER-16

What is the maximum length of message_payload data supported?

5.3.2.32

160

DELIVER-17

Is the payload_type field supported?

5.3.2.10

NO

DELIVER-18

Is the receipted_message_id field supported?

5.3.2.12

YES

QUERY_SM PDU

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

QUERY-1

Is the use of default values in the source_addr fields supported?

4.8

YES

CANCEL_SM PDU

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

CANCEL-1

Is the use of default values in the source_addr fields supported?

4.1.9

YES

CANCEL-2

Is the message_id of NULL, and thus cancelling a group of messages supported?

4.1.9

NO

Functional Items

Forward Compatibility Issues

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

FORWARD-1

If the application receives an unknown PDU does it return a generic_nack?

3.3

YES

FORWARD-2

Are unsupported and unrecognised optional fields ignored?

3.3

YES

FORWARD-3

Are all ‘reserved’ values in parameters interpreted as the default value ?

3.3

NO

FORWARD-4

Are unrecognised values in parameter value fields treated as an error ?

3.3

YES

FORWARD-5

Is an inconsistent Optional parameter combinations counted as an error?

3.3

NO

FORWARD-6

Do invalid parameter lengths cause the PDU to be rejected?

3.3

YES

Backward Compatibility Issues

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

BACK-1

Is it possible to make this implementation only support the v3.3 and not use any v3.4 features?

3.4

YES

Implementation Issues

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

IMP-1

What is the maximum value for the PDU header field command_length which is supported by the implementation?

3.2.1

2048

IMP-2

Are all the optional parameters processed in an order independent manner?

3.2.4

YES

Overall Message Types Supported

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

TYPE-1

Are normal data messages transmitted?

2.11

YES

TYPE-2

Can SMSC Delivery Receipts be requested and obeyed?

2.11

YES

TYPE-3

Are intermediate notifications supported?

2.11

NO

TYPE-4

Are SME Delivery acknowledgements (Read receipts) supported?

2.11

N/A

TYPE-5

Are SME Manual/User acknowledgements supported?

2.11

NO

TYPE-6

Are Conversational Aborts supported?

2.11

NO

Timers

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

TIMER-1

Is the SMPP session_init_timer implemented?

7.2

YES (60 secs)

TIMER-2

Is the SMPP enquire_link_timer implemented?

7.2

YES (60 secs)

TIMER-3

Is the SMPP inactivity_timer implemented?

7.2

YES (60 secs)

TIMER-4

Is the SMPP response_timer implemented?

7.2

YES (60 secs)

SMSC Specific

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

SMSC-1

Can a Store and Forward method of final delivery be used?

2.10

YES

SMSC-2

Can a Datagram method of final delivery be used?

2.10

NO

SMSC-3

Can a Transaction mode method of final delivery be used?

2.10

NO

SMSC-4

Can this initiate a session by using the outbind operation sequence?

2.2.1

NO

SMSC-5

What is the maximum length of message_id supported in operations?

5.2.23

16

Implementation Issues

SMSC Issues

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

IMP-SMSC-1

Is information in a bind PDU is used for access control?

YES

IMP-SMSC-2

Can the information in the bind PDU be used for routing messages to the ESME?

YES

IMP-SMSC-3

In a cancel_sm received from an ESME, must the service_type field be set to the same value as the original message which is being canceled?

5.2.12

NO

IMP-SMSC-4

In a replace_sm received from an ESME, must the service_type field be set to the same value as the original message which is being replaced?

5.2.12

N/A

Link Usage

ITEM

Functional Unit/Description

SMPP REF.

Support
YES / NO

LINK-1

Is it possible to have multiple links to the same SMSC using the same access control information?

YES

LINK-2

Is it possible to have multiple links to the same SMSC using different access control information?

YES

Data Fields


Bind Fields


Item


Issue and question


SMPP REF.


Answer

Bind-Field1

Are there any character or other limitations imposed upon values used in the system_id field?

5.2.1

As provided in account configuration.

Bind-Field2

Are there any character or other limitations imposed upon values used in the system_type field?

5.2.2

As provided in account configuration.

Bind-Field3

Are there any character or other limitations imposed upon values used in the password field?

5.2.3

As provided in account configuration.


SUBMIT_SM Fields


SMPP field


Issue and question


SMPP REF.


Answer

Submit-Field1

What, if any restrictions are imposed upon the value used in the service_type field?

5.2.11

Must be null (i.e. empty)

Submit-Field2

What values in the esm_class field are supported, and in what circumstances?

5.2.12

UDHI

Submit-Field3

What values in the protocol_id field are supported, and in what circumstances?

5.2.13

All valid GSM values

Submit-Field4

What values in the priority field are supported, and in what circumstances?

5.2.14

0, 1

Submit-Field5

What, if any restrictions are imposed upon the value used in the schedule_delivery_time field?

5.2.15

None

Submit-Field6

What, if any restrictions are imposed upon the value used in the validity_period field?

5.2.16

None

Submit-Field7

Which values in the registered_delivery field are supported?

5.2.17

0,1

Submit-Field8

Are there any restrictions set upon the values specified in the data_coding field?

5.2.19

No

Submit-Field10

What dest_network_type and source_network_type values are supported?

5.3.2.35.3.2.4

N/A

Submit-Field11

What dest_bearer_type, dest_telematics_id, source_bearer_type, source_telematics_id values are supported?

5.3.2.55.3.2.65.3.2.75.3.2.8

N/A

Submit-Field12

What payload_type values are supported?

5.3.2.10

N/A

Submit-Field13

What ms_msg_wait_facilities values are supported?

5.3.2.13

N/A


DELIVER_SM Fields


SMPP field


Issue and question


SMPP REF.


Answer

Deliver-Field1

What, if any restrictions are imposed upon the value used in the service_type field.

5.2.11

None

Deliver-Field2

What values in the esm_class field are supported, and in what circumstances?

5.2.12

Default message type
SMSC Delivery Receipt
UDHI Indicator set

Deliver-Field3

What values in the protocol_id field are supported, and in what circumstances?

5.2.13

All valid GSM values

Deliver-Field4

What values in the priority field are supported, and in what circumstances?

5.2.14

None

Deliver-Field5

Which values in the registered_delivery field are supported?

5.2.17

None

Deliver-Field6

Are there any restrictions set upon the values specified in the data_coding field?

5.2.19

None

Deliver-Field7

What payload_type values are supported?

5.3.2.10

N/A


E&OE