Delivery of Long SMs
The following lists the lengths of ordinary SMs when different coding schemes are
adopted:
Unicode coding: 70 characters
8-bit coding: 140 characters
7-bit coding: 160 characters
The SMs with the length larger than the maximum length are defined as long SMs.
When the MS and the SMS G/IW MSC support Phase 2, the SMS system supports
the delivery of the long SMs which can be 35,700 bytes long at most (the SM length
after coding includes the additional information).
After receiving long SMs, the infoX-SMS system segments them to several packets
and sends them to subscribers.
Note:
To enable the GSM network to forward long SMs, the MS and the radio network must
support the PHASE2 protocol.
Delivery of SMs to Multiple Destinations
The SMS system supports the sending of an SM to multiple destinations.
1) The ESME submits a Submit_multi message to the infoX-SMS system through
the SMPP 3.4 interface.
2) After receiving the Submit_multi message, the infoX-SMS system creates SMs
according to the attributes of the Submit_multi message (SM content, number of
destination addresses, and destination address list). The system creates one SM
for each destination address.
3) The infoX-SMS system delivers the SMs according to the system scheduling
strategies.
Delivery of Multiple SMs to a Destination
When the network supports Phase 2, the SMS system can deliver multiple SMs to a
subscriber simultaneously (in this case, the GMSC obtains the routing information
from the HLR only once, and the session with the MSC is maintained during the
delivery). In this way, the load of the SS7 network can be greatly alleviated.
Note:
To enable the GSM network to forward multiple SMs, the MS and the radio network
must support PHASE2.
When the infoX-SMS system delivers multiple SMs to one subscriber, the GMSC
obtains routing information from the HLR only once, and the SMS system keeps
interacting with the MSC until the SMs are successfully sent or a fault occurs.
Virtual SMC Authentication
When an MS submits an SM to the SMS system, the SMS system judges whether the
SMS system address of the SM is the virtual address of the SMS system and decides
whether the subscriber can use the SM services provided by the SMS system. If a
subscriber who is not in the service range of the SMS system submits an SM to the
SMS system, the SMS system rejects the SM.
Universal Flow of Authentication and Number Conversion
The SMS system supports the universal flow of authentication and number
conversion. That is, subscribers can set suitable rules, authentication and number
conversion data, and customize proper policies of authentication and number
conversion as required.
I. Number conversion flow
The SMS system has three number conversion points: Before NP, Before SCP and
Before Deliver. These four points are distributed in the following MO flow and MT flow:
Before NP: converts the number before querying the attribute of NP.
Before SCP: converts the number before querying the attribute of the subscriber.
Before Deliver: converts the number by the end of MT process.
Change Deliver: converts the number when SM is delivering.
Number conversion in the change deliver point is effective to ordinary SMs and status
reports.
At each point, the rule of number conversion can be configured as Not Convert
Number, Number Head Conversion and Number Tail Conversion. The number
conversion strategies are configurable, thus meeting the requirements of related
service flows.
The number conversion at each point includes the number conversion according to
accounts and SMC addresses. The number conversion according to accounts
precedes the number conversion according to SMC addresses. The relationship
between the two types can be configured.
Number conversion according to accounts: converting numbers according to the
account name; numbers to be converted; the attribute of the calling or called
number; PID value, TON value and NPI value of the number before conversion;
and number conversion policies. The converted number is used for routing.
Number conversion according to SMC addresses: converting numbers
according to the SMC address; numbers to be converted; the attribute of the
calling or called number; PID value, TON value and NPI value of the number
before number conversion; and number conversion policies. The converted
number is used for routing.
II. Authentication flow
The SMS system authenticates the calling or called SMs after all number conversions
are finished. It checks whether the calling or called parties are valid subscribers and
decides whether to provide SM services for them.
The SMS system supports blacklist authentication and whitelist authentication.
Blacklist authentication: If a number is not in the configured authentication data,
it passes the authentication. If the number is in the configured authentication
data, it is authenticated according to the found authentication data.
Whitelist authentication: If a number is not in the configured authentication data,
it fails the authentication. If the number is in the configured authentication data, it is authenticated according to the found authentication data.
Virtual SMC
The SMS system supports virtual SMC. One SMS system can provide SMS for 16
local mobile networks. The SMS system can configure multiple SMC numbers. Each
SMC number is corresponding to a local mobile network. The physical SMS system
entity occupies multiple logical SMC numbers, and the specific numbers are subject
to the actual situation of the local network.
Note:
Currently, only the GSM part of the SMS system supports the virtual SMC function.
