System Functions and Implementation
This chapter introduces the scheduling processing functions of the SMSC, as well as
the basic service functions, system management functions, and system maintenance
functions of the infoX-SMS system.
Reading this chapter enables you to get an understanding of the functions and
features of the infoX-SMS system.
Basic Service Supporting Functions
The basic service supporting functions support the basic services of the infoX-SMS
system. This chapter covers the basic service supporting functions.
SM Submission
The infoX-SMS system supports the submission of SMs by mobile subscribers and
ESMEs.
- After an SM is submitted to the SMS system and is confirmed as valid, it is inserted into the short message queue and an acknowledgment message is sent back to the originator.
- If the SM is invalid or cannot be processed by the SMS system temporarily, the SMS system sends to the originator a message indicating submission failure.
SM DeliveryWhen the infoX-SMS system runs in the SMC mode, it delivers SMs submitted to it.
The SMS system automatically adjusts the delivery frequency according to the
number of SMs waiting to be delivered, regularly takes out the SM that must be
delivered, and ensures that only one SM is sent to one MS at one time.
- If the SM is successfully delivered, it is moved to the historical information database for query and bill statistics.
- If the SM fails to be delivered, the SMSC adopts specific scheduling strategy and performs subsequent scheduling on the SM according to the error code returned and the current scheduling mode of the SMSC.
- If the SM has not been delivered successfully yet after its life cycle ends, it is moved to the historical information database with the failure cause recorded.
SM Delivery in the FDA ModeWhen the infoX-SMS system runs in the FDA mode, it attempts to deliver SMs
submitted to it only for one time.
When the SMS system runs in the FDA mode, the system forwards the SM to the
SMS system with the function of storing SMs:
- The SM is submitted to the FDA,
- The first delivery of the SM fails, and
- The scheduling strategy of the SM is Forward.
Compared with the SMPP 3.4, two TLVs are added to the interface protocol used for
forwarding SMs. One is used for carrying the SM ID, and the other is used for carrying
the relevant account.
Status ReportThe subscriber can obtain the status of an SM he or she sends through the report
returned by the system.
The infoX-SMS system generates status report according to the configuration
(whether status report is needed), and notifies the subscriber of the submission result
of the SM.
The message status includes the following:
- Forwarding notification (forwarding success)
- Forwarding failure notification (permanent failure)
In addition, the MS can select the requirement for the enhanced status report. The
SMS System returns an SM indicating the SM transfer status to the MS. The contents
of the enhanced status report are editable.
Information Security AuthenticationThe information security authentication means filtering the SMs submitted to the SMS
system in real time for information security and refusing those SMs not satisfying the
requirements.
1) After receiving an SM, the infoX-SMS system forwards it to the information
security module.
2) The information security module authenticates the SM, for example, it checks
whether the SM contains sensitive words or whether it is a junk SM, and then
returns the authentication result to the infoX-SMS system.
3) The infoX-SMS system processes the SM if it passes the authentication.
Otherwise, it rejects the SM.
Authentication and ChargingThe SMS system supports the authentication of PPS service subscribers and Mobile
Virtual Private Network (MVPN) service subscribers.
- When a PPS subscriber sends or receives an SM, the infoX-SMS system sends the information of the PPS subscriber to the IN SCP for authentication and charging according to the PPS routing information. The infoX-SMS system supports roaming charging of PPS subscribers. Whenthe SMS system performs PPS authentication and fee deduction on a PPS subscriber who sends or receives an SM, it sends the authentication message with the MOMSC address to the SCP. The SCP determines the charging rate of an SM according to the MOMSC address (the SCP checks whether the MOMSC address indicates a local MSC), and charges roaming PPS subscribers and non-roaming PPS subscribers differently. The PPS roaming charging supports charging rollback.
- MVPN is a special mobile virtual private network, and allows VPN subscribers to send and receive SMs using short numbers. When processing this type of SMs, the SMS system needs to convert the short number to the actual MSISDN, therefore, it needs to obtain the actual MSISDN corresponding to the short number from the IN network.
The authentication mode and route for the number segments of the local PPS service
and local MVPN service should be flexibly set according to the actual requirements.
Multiple Coding SchemesThe infoX-SMS system supports multiple coding schemes, thus supporting multiple
languages.
I. GSM coding schemes that the system supports- 7-bit compressed coding
- 8-bit coding
- Unicode coding (16bit)
II. CDMA coding schemes that the system supportsThe system supports the following five coding schemes of the CDMA network: 00000,
00010, 00011, 00100, and 01001.
Coding schemes that the TDMA network defines.
| CHARi Encoding Type | MSG_ENCODING Field | Length of CHARi (bits) |
| Octet,unspecified | 00000 | 8 |
| Extended Protocol Message [21] | 00001 | (see iv) |
| 7-bit ASCII [25] | 00010 | 7 |
| IA5 (Table 11 OF [31]) | 00011 | 7 |
| UNICODE [29]i | 00100 | 16 |
| Shift-JIS [30]ii | 00101 | 8 or 16 |
| Korean [33]iii | 00110 | 8 or 16 |
| Latain/Hebrew [28] | 00111 | 8 |
| Latain [27] | 01000 | 8 |
| GSM 7-bit default alphabet [37] | 01001 | 7 |
III. TDMA coding schemes that the system supportsThe system supports the following three coding schemes of the TDMA network:
00001, 00010, and 00100.
Coding schemes that the TDMA network defines.
| Value | Function |
| 00001 | IRA |
| 00010 | User specific |
| 00011 | Latain 1, as specified in ISO-8859-1 |
| 00100 | BMP, as specified in ISO-10646 |
| 00101 | Hebrew, as specified in ISO-8859-8 |
Number Conversion According to the Fields of TON, NPI, ADDRESS and PIDThe SMC supports the following number conversion points: beforeNP, beforeSCP,
beforeDeliver, OnDeliverG, OnDeliverCT, OnAlertSCG, and OnAlertSCCT. At each
number conversion point, the number conversion strategies are configurable. This
meets the requirements of related service flows.
At each number conversion point, the system converts the calling and called numbers
according to their attributes, including the PID before number conversion, TON before
number conversion, NPI before number conversion, referential number and number
conversion strategies. The converted number is used for routing and delivering SMs.
SM Filter Service of the Called PartySubscribers can set a filtration list, for example, SPs of advertisement or some
MSISDNs, and no-interruption period through website, thus realizing the SM filtration
and the no-interruption service.
- Blacklist filter function. After receiving an SM, the SMS system first checks whether the called party has subscribed to the blacklist filter service. If yes, the SMS system then checks whether the calling party is in the blacklist of the called party. If yes, the SMS system filters the SM and does not send the SM to the called party.
- No interruption function. After receiving an SM, the SMS system first checks whether the called party has subscribed to the no-interruption service. If yes, the SMS system checks whether the current time is within the no-interruption period set by the subscriber. If yes,the SMS system stores the SM and delivers the SM to the called party when theno-interruption period ends.
Authenticating SubscribersFor MO service, the SMSC conducts calling and called number authentications.
There are two types of authentication: subscriber authentication and number segment
authentication.
- Subscriber authentication. According to all the SMs submitted from an interface, the system checks whether the calling party or the called party is a registered subscriber of the SMSC. If not, the SM is rejected.
- Number segment authentication. According to all the SMs submitted from an interface, the system checks whether the calling party or the called party meets the authentication requirements of the number segment defined in the account attributes or SMC address.
For details of number authentication, refer to section
"Universal Flow of Authentication and Number Conversion."The following shows the
authentication flow of the SMs submitted by the
CDMA/TDMA subscribers (Number segments of the CDMA/TDMA subscribers are
configurable):
Calling number authentication: If the calling number is registered in the local SMS system, it passes the
authentication. The system processes the SM as the one submitted by the local
subscriber.
If the calling number is not registered, the system authenticates the SM
according to the authentication data corresponding to the gateway accounts for
the CDMA or TDMA network or that corresponding to the virtual SMC address for
the CDMA/TDMA networks. If it passes the authentication, the system processes
the SM as the one submitted by the local subscriber. Otherwise, the system
regards that the SM is forwarded from another SMS system. If it is configured in
the SMS system that calling number authentication is conducted on the
forwarded SM, the system checks the calling number of the SM in the home SMS
system list. If the number is found in the list, it is an authorized forwarded SM.
Otherwise, the SM is rejected.
Called number authentication: The system first checks the called number in the home SMS system list. If the
called number is found in the list, it indicates that the called party belongs to
another SMS system. The SM is then forwarded according to the forwarding
mode configured in the table.
If the called number is not found in the list, it is authenticated in the local SMS
system. If the called number is registered in the local SMS system, it passes the
authentication, and the system processes the SM as the one delivered to the
local subscriber. If the called number is not registered in the local SMS system and it is a subscriber in the CDMA/TDMA networks, the system checks whether
the called number is a local number by referring to the calling authentication
number segment corresponding to the CDMA/TDMA gateway accounts or virtual
SMC address. If yes, the SM is delivered directly. If no, the SM is forwarded. If
the called number is the GSM subscriber, called number authentication is
conducted according to the authentication data corresponding to gateway
accounts for the CDMA/TDMA networks or that corresponding to virtual SMC
address. If the called number does not pass the authentication, the SM is
rejected.
