infoX-SMS: Supporting SMPP 3.4

Supporting SMPP 3.4

The SMS system is compatible with SMPP 3.4 interface protocol. Table 1 shows commands of the SMPP 3.4 protocol supported by the SMS system. Table 2 shows TLV of the SMPP 3.4 supported by the SMS system.

Table 1 Commands of the SMPP 3.4 protocol supported by the SMS system

Command	Description
BIND_RECEIVER	Applies to connect with the SMS system
BIND_TRANSMITTER	Applies to connect with the SMS system
BIND_TRANSCEIVER	Applies to connect with the SMS system
QUERY_SM	Queries SMs
SUBMIT_SM	Submits SMs
DELIVER_SM	Sends SMs
REPLACE_SM Replaces	SMs
CANCEL_SM	Deletes a CBSM
OUTBIND	Applies the SME to enable links to receive SMs
ENQUIRE_LINK Handshake
SUBMIT_MULTI	Delivers SMs
ALERT_NOTIFICATION	Status report messages
DATA_SM	Submits SMs

Table 2 TLV supported by the SMS system

Tag	Value	Wireless Network Technology
payload_type	0x0019	Generic
additional_status_info_text	0x001D	Generic
ms_msg_wait_facilities	0x0030	GSM
user_message_reference	0x0204	Generic
source_port	0x020A	Generic
destination_port	0x020B	Generic
sar_msg_ref_num	0x020C	Generic
sar_total_segments	0x020E	Generic
sar_segment_seqnum	0x020F	Generic
SC_interface_version	0x0210	Generic
dpf_result	0x0420	Generic
set_dpf	0x0421	Generic
ms_availability_status	0x0422	Generic
network_error_code	0x0423	Generic
message_payload	0x0424	Generic
delivery_failure_reason	0x0425	Generic
more_messages_to_send	0x0426	GSM

infoX-SMS: Supporting SMPP 3.3

Supporting SMPP 3.3

The SMS system is compatible with the SMPP 3.3 interface protocol. Table 3-3 shows
commands of the SMPP 3.3 protocol supported by the SMS system.

SMPP 3.3 protocol supported by the SMS system

Command	Description
BIND_RECEIVER_SM	Applies to connect with the SMS system
SUBMIT_SM	Submits SMs
DELIVER_SM	Sends SMs
QUERY_SM	Queries SMs
CANCEL_SM Deletes SMs
REPLACE_SM Replaces	SMs
REPLACE_SM_EX	Replaces SM extensions
QUERY_SMS	Queries SMs
QUERY_SM_DETAILS	Queries the details of special SMs
ADD_SUB	Adds users
DEL_SUB	Deletes users
MOD_SUB	Modifies users
ENQUIRE_SUB	Queries subscriber Information
ENQUIRE_LINK Handshake	Messages

infoX-SMS: IRDB, SMs Without Calling Number

IRDB

The SMS system supports the IRDB service. The IRDB service provides the
refreshment service of operator list for roaming TDMA MSs. An IRDB delivery tool is
installed together with the SMS system. The delivery tool loads IRDB information list
from files and then sends the messages to the TDMA MSs as the flow specified by
EIA/TIA 136-730.

Note:
This function is applied in the TDMA network only and is applied in the current
network.

Supporting UCP 4.0

Connecting with the UCPGateWay, the SMS system processes ESME messages
which support the UCP protocol in the X.25 network or TCP network. The SMPP 3.4
protocol is adopted between the UPT and SMSC, and the UCP 4.0 protocol is
adopted between the UCPGateWay and ESME. The protocol contains the following
commands:

Session management: sending connection request SMs
Multiple address call input: sending SMs in batches
Submit Short Message: submitting SMs
Delivery Short Message: sending SMs
Delivery notification: status notification SMs
Modify Short Message: replacing SMs
Inquiry message: querying SMs
Delete message: deleting SMs
MT alert: status notification SMs

SMs Without Calling Number

Some devices do not carry a calling number when submitting the submit_sm
message through the SMPP interface. The SMS system can process the SM by
adding a called number according to the configuration.

Time Zone Features

The SMS system can process information of different time zones.

• The SMS system can deliver SMs with time zone information, which guarantees that the time information in the SMs received by roaming subscribers is correct.
• The SMS system can process MO SMs with time zone information.

infoX-SMS: Messages of the WAP Service

PUSH Messages of the WAP Service

The SMS system supports PUSH messages of the WAP service. The MS has a very
strict limit for the content of WAP PUSH messages. The value of
SMS_TELESERVICEID (a parameter of the MAP layer in the CDMA network, which
is used to identify special SM services) varies with different WAP services. The SP
identifies the service type of the PUSH message through the ServiceType parameter
in the SMPP message. The SMS system can flexibly convert ServiceType into
SMS_TELESERVICEID needed by the MS, and code the SM content. Then the MS
can receive the SM. The push flow of the WAP service is thus implemented.

Note:
This service is only supported in the CDMA network.

PUSH Messages in the MMS Service

The SMS system supports PUSH messages in the MMS service. The PUSH messages in the MMS service of the CDMA network conforms to the WDP259 protocol. The SMS system adds a special message head before the SM content and then delivers it to the MS. The value of SMS_TELESERVICEID is specially set for the PUSH messages in the MMS service. The SMS system converts ServiceType at the SMPP interface into SMS_TELESERVICEID needed by the MS, and codes the SM content. Then the MS can receive the SM. The push flow of the MMS service is thus implemented.

Note:
This function is only supported in the CDMA network. In the GSM network, the PUSH
messages in the MMS service are transferred transparently by the SMS system.

PRL Function

The SMS system supports the preferred roaming list (PRL) service. The PRL service provides the refreshment service of operators for roaming CDMA MSs. A PRL delivery
tool is used together with the SMS system. The delivery tool loads PRL information list from files and then sends the messages to the CDMA MSs as the flow specified by
ANSI IS683.

Note:
This function is applied in the CDMA network only and is applied in the current
network.

infoX-SMS: Distinguishing Subscriber Network Attributes

Distinguishing Subscriber Network Attributes According to Different Number Segments

The SMS system supports number heads for the GSM, CDMA, and TDMA networks.
If the subscriber belongs to the non-target network (Subscriber attributes can be
distinguished by number segment), the SMS system distinguishes the subscriber
network type according to the configured number head of the subscriber, and adopts
corresponding scheduling strategy and coding scheme for the successful delivery of
the SM. For detailed scheduling strategy, refer to section Multidimensional Intelligent Scheduling.”

NP Function

The SMS system supports the NP function. For subscribers in the target network, the
system cannot distinguish from GSM subscribers, CDMA subscribers, and TDMA
subscribers, as well as subscribers of the local operator from those of other operators Because the subscriber can transfer between operators without changing its
MSISDN). The SMS system provides registration function for subscribers. The
attributes of registered subscribers contain information on subscriber network type,
which helps the SMS system distinguish from the GSM subscribers, CDMA subscribers, and TDMA subscribers. For unregistered subscribers, the SMS system regards them as the subscribers of other operators. The SMS system adopts different scheduling strategies and scheming codes according to the network types of subscribers for the successful delivery of the SMs. For subscribers belong to other operators, the SMS system forcibly forwards the SMs to a certain account, which is usually connected with another interworking gateway (not an infoX-SMS GW). The gateway then forwards the SMs to SMS systems of other operators. Meanwhile, the SMS system provides realtime registration interface, which is used to refresh subscriber information in the database.

Note:
Being different from the NP function of the SMS system for the GSM network, the SMS system for the CDMA, GSM and TDMA networks is connected with the NP Server. Instead, it distinguishes the subscriber attributes according to subscriber information in the subscriber list, and forcibly forwards SMs which are sent to subscribers of other operators to the interworking gateway. This function is applied in the current SMS system.