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.

infoX-SMS: System Functions and Implementation

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.

Huawei infoX-SMC System Description: System Functions and Implementation

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 Delivery

When 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 Mode

When 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 Report

The 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 Authentication

The 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 Charging

The 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 Schemes

The 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 supports

The 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 supports

The 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 PID


The 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 Party

Subscribers 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 Subscribers

For 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.

Huawei infoX-SMC System Description: SMS System Architecture

SMS System Architecture

The SMS system is designed with the modularized concept. This system can be
divided into several parts according to different functional categories, which can be
selected during the construction of the system depending on the actual needs so as to
provide services of different levels.

Signaling Gateway

The TELLIN-USAU can be used as the SG of the SMS system. The TELLIN-USAU is
located between the signaling network and the internal processing module of the SMS
system. As the SG, the TELLIN-USAU implements the signaling interaction between
the SMS system and the MSC and the HLR, and accomplishes signaling access and
conversion necessary for the information interaction between the MS and the SMS
system.

MTI Server

The MTI Server is the interface layer between the MAP layer and the TCAP layer in
the signaling system number 7 (SS7). The main functions are as follows:
Processing the conversion between signaling at the TCAP layer and that at the
MAP layer
Processing basic dialogs processes, including dialog creation, release, and
maintenance, at the MAP layer
Distributing signaling at the MAP layer among the application modules, including
the MAP Server, USSD Gateway and so on, of the MAP layer
Connecting the application modules at the MAP layer, and distributing messages
according to the AC_NAME and SSN of messages
As the server, the MTI Server connects the MAP Server, USSD Gateway, and the
signaling access gateway.
When receiving the MAP dialog request at the TCAP layer from the wireless network,
the MTI Server sends the request to the corresponding MAP processing module. For
dialog requests initiated from the modules of the MAP layer, the MTI Server distributes them to the corresponding signaling access gateway according to a
proportion.

GSM MAP Server

The GSM MAP Server is the GSM G/IW gateway of the SMS system. It processes the
MAP signaling of the SMS system, converts the MAP signaling into the message of
internal format, and then forwards it to SMSC.
The GSM MAP Server connects with the MTI Server as the client, processing the
MAP signaling. Meanwhile, the GSM MAP Server connects with the SMSC as the
server, implementing the conversion between the MAP signaling and the message of
internal format.
Functions of the GSM MAP Server are as follows:

  • Supporting multiple-module processing
  • Supporting Phase 1, Phase 2 and Phase 2+ SM signaling
  • Supporting the identification of MAP session version in the GSM network
  • Implementing the signaling flow of submitting SMs from GSM MSs, and transferring the submitted SMs to the SMSC
  • Implementing the signaling flow of delivering SMs from the GSM SMS system, and returning the delivery results to the SMSC
  • Implementing the ALERT_SC signaling flow from the HLR to the SMS system, and sending the corresponding information to the SMSC
  • Supporting the function of sending multiple SMs so as to improve the network efficiency
  • Version number of MAP signaling being configurable
  • Monitoring the running status of the system
  • Monitoring resources of the MAP Server
  • Providing the function of querying the location of an MS
  • Monitoring the message exchange between the MAP Server and SMS system, MTI Server and MAP Server
  • Supporting 2M signaling link
  • Supporting SIGTRAN signaling
  • Signaling the feature of multiple signaling points
  • Supporting obtaining delivery routes from different HLRs according to different number segments
  • Receiving SRI messages and Forward MT messages by simulating HLR and MSC
  • Supporting SM interception
  • Supporting networking of multiple MAP Servers, and message distribution by percentage, by calling number segment, and by the ending digits of the called number
  • Supporting testing the normal running of the SMS system in the networking of multiple MAP Servers
CDMA MAP Server

The CDMA MAP Server is a part of the SMS system. It converts the signaling between
layers TCAP and CDMA MAP, and converts CDMA MAP signaling into messages of
the internal format and forwards them to the SMSC. The CDMA MAP Server, as a
client, connects with the CTI Server directly; or as the server, connects with the USAU
directly; and as the superior level of the signaling access gateway, processes the
CDMA MAP signaling. At the same time, the CDMA MAP Server, as the server, is
connected with the SMSC, implementing the conversion between the CDMA MAP
signaling and messages of the internal format.
Functions of the CDMA MAP Server are as follows:
  • Supporting SM signaling in the CDMA network.
  • Supporting the signaling flow of CDMA MSs submitting SMs to the MAP Server, and forwarding the submitted SMs to the SMSC.
  • Supporting the signaling flow of the SMSC delivering SMs in the CDMA network to the MAP Server, and returning delivery results to the SMSC.
  • Supporting the signaling flow the HLR sending the Alert_SC message to the SMSC, and supporting sending the message to the SMSC.
  • Supporting the message forwarding flow among SMS systems for the CDMA network. Supporting delivering multiple SMs in batches to increase the network efficiency.
  • Supporting monitoring the running status of the system.
  • Supporting monitoring the resources of the CDMA MAP Server.
  • Supporting to query the MS location.
  • Supporting monitoring the message exchange between the MAP Server and the SMSC, and between the MTI Server and the MAP Server.
  • Supporting 2M signaling link.
  • Supporting the SIGTRAN signaling.
  • Supporting multiple signaling points (SPs).
SMSC

The SMSC is responsible for scheduling, storing and forwarding SMs in the SMS
system. Its basic functions include submission, delivery, and scheduling of SMs,
maintenance of SM subscriber data, subscriber authentication, system flow control,
management of external interfaces, generation of SM historical records, generation of
realtime SMS bills and provision of external standard interfaces (such as SMPP 3.3
and SMPP 3.4 interface). As the kernel module of the SMS system, the SMSC provides system interfaces for
the CDMA MAP Server, GSM MAP Server, manual station, automatic station, short
message information service station, and voice mail box.
The interface between the SMSC and the GSM MAP Server complies with the
protocol ETSI GSM 03.40 Version 4.8.1: European digital cellular
telecommunications system (Phase 2); Technical realization of the Short Message
Service (SMS) Point to Point (PP).
The interface between the SMSC and the CDMA MAP Server complies with the
protocol EIA/TIA IS637A protocol and the EIA/TIA IS637B.
The interfaces between the SMSC and the service systems such as manual station,
automatic station, short message information service station, and voice mail box
comply with the standard SMPP protocol.
The SMSC consists of five modules, SMCAPP, BillCreater, DBDaemon,
BackupDaemon, and L2CacheDaemon. The SMCAPP and other modules access
data of each other through memory sharing.

Their functions are as follows:

I. SMCAPP

The SMCAPP module is responsible for receiving, scheduling and delivering SMs,
managing all the SMEs connected to the SMS system and providing the interface for
the maintenance and test of the SMSC operation.

II. BILLCreater

The BILLCreater module is responsible for generating realtime SMS bills which are
used for the query and statistics by the charging system and report system.

III. DBDaemon

The DBDaemon module is responsible for backing up and restoring the memory data
in the SMSC, such as the management on subscriber data, historical data and
predefined SMs.

IV. BackupDaemon

The BackupDaemon module implements the backup and restoration of the memory
data in the SMSC. The BackupDaemon backs up SMs in the memory of SMCAPP in
real time. When the SMCAPP is restarted by ClusterMng after abnormal exist, it reads
back SMs from the BackupDaemon, recovering SMs during the abnormity of the
SMCAPP.
In the dual system mode, the BackupDaemon module has the functions of backing up
and restoring data of the active and standby hosts. The BackupDaemon of the
standby host backs up SMs from that of the active host, ensuring the consistency of
SM data in the memories of the active host and standby host. When switchover happens, the original standby host changes into the active host,
while the SMCAPP of the original standby host turns into the Master status.
Meanwhile, the SMCAPP of the current active host reads back messages from the
BackupDaemon, ensuring the consistency of SM data in the memories of the two
hosts.
At the startup of an SMS system, it first loads pre-defined SMs and subscriber
information into the memory of the SMSC through DBDaemon, and then recovers the
SMs from the BackupDaemon.

V. L2CacheDaemon

During the peak hour, some of the SMs are saved into the L2CacheDaemon.
Temporarily, these SMs are not scheduled in real time.
When the system load is lower, the SMCAPP, together with the L2CacheDaemon,
reads back the SMs into the memory of the SMSC for rescheduling.

Dual System Management Module

The dual system management module provides dual system management functions
for key system components, enhancing the system stability and security.

I. ClusterMng

ClusterMng is responsible for monitoring and maintaining specific application
modules of the SMS system, such as SMCAPP.
  • Dual system management in the AIX system Under the UNIX operating system, ClusterMng implements the dual system functions of the SMS system together with the HACMP management system of the IBM AIX system. HACMP manages and switches the floating IP address and vg. Meanwhile, HACMP of the active host is responsible for monitoring the running of Oracle processes and ClusterMng. If the active HACMP finds the network running is abnormal, or the Oracle and ClusterMng processes are abnormal and fail to be restarted, it conducts switchover automatically. The ClusterMng tries to start a module for many times if it finds that the module works abnormally. If the abnormity persists, it determines whether to conduct dual system switchover according to the configuration.
  • Dual system management in the Solaris system In the Solaris system, the ClusterMng implements the dual-system functions of the SMS system together with the SUN Cluster of the Solaris system. The SUN Cluster manages and switches the floating IP address, disk array, and Oracle. Meanwhile, the SUN Cluster of the active server is responsible for monitoring the running of the Oracle processes and ClusterMng. The ClusterMng takes the server where the floating IP is as the active server, and it monitors and maintains the running of specific application modules of the SMS System, such as the SMCAPP module. If the SUN Cluster on the active server finds the network running is abnormal, or the Oracle and ClusterMng processes are abnormal and fail to be restarted, the SUN Cluster conducts switchover automatically. The ClusterMng tries to start a module for many times if it finds that the module works abnormally. If the abnormity persists, it determines whether to conduct dual system switchover according to the configuration.
  • Dual system management in the Windows system Under the Windows operating system, ClusterMng and Serverselector accomplishes dual system functions of the SMS system. ClusterMng takes the server where the floating IP is as the active server, and it is responsible for monitoring and maintaining the running status of specific application modules of SMs, such as the running status of the SMCAPP module. The ClusterMng tries to start a module for many times if it finds that the module works abnormally. If the abnormity persists, it determines whether to conduct dual system switchover according to the configuration.
  • In the Windows operating system, the NTCluster is also adopted to perform dual system management, database monitoring, and dual system switchover.
II. FileMirror

According to the configuration, the FileMirror conducts the synchronization of the
configuration files of the dual system, ensuring the consistency of data at the active
and standby hosts. In this case, the data on the two hosts are consistent after the
switchover. Such configuration files as account files, route files, the configuration file
of the MAP Server, the configuration file of the MTI Server need synchronization.
The FileMirror can detect the change of configuration files on the active host, and
synchronize the file after change into the standby host, ensuring the data consistency
on the two nodes of the dual system. In this case, when switchover occurs, the
standby host is switched over to the active host, and the data configuration on it is
consistent with that of the original active host before the switchover.
Currently, the FileMirror supports only synchronization of a single file or that of files in the same directory.

FCC

FCC is the flow control center. As the kernel management control module of the SMS
system, the FCC can improve the flow distribution processing capacity of the system
and enhance its redundancy capability.
The FCC includes two types: local FCC and inter-office FCC. They can be
distinguished by configuration items. The inter-office FCC only applies to network SM networking mode and supports the connection to the local FCC. As the higher FCC of
the local FCC, the inter-office FCC provides the function of distributing flow to every
office by percentage. The local FCC can be connected to the MAP Server and the
SMSC. It provides functions of redundancy route, load distribution and license
floating.

I. Local FCC

The local FCC supports the connection to the MAP Server and the SMSC to
implement the following functions:
  • Redundancy route The FCC can function as a redundancy route between the MAP Server and the SMSC. When the MAP Server is disconnected from the SMSC or the SMSC indicates busy, the MAP Server can use the FCC as a redundancy route and send SMs to the FCC. The FCC then forwards the SMs to the destination SMSC. Taking the FCC as a redundant route, the SMSC sends SMs which are originally sent to this MAP Server to the FCC, which then forwards them to the destination MAPServer in one of the following cases:
- The SMSC is disconnected from the MAP Server.
- The MAP Server is not available.
- The MAP Server is heavy loaded.
- Abnormal connection between the MAP Server, MTI Server, and USAU
  • Load sharing. When the local FCC processes SMs from the MAP Server, the SMSC or other offices through the inter-office FCC, it can dynamically adjust the flow distribution through the internal flow distribution algorithm. The adjustment is based on the running and load status of each SMSC or MAP Server. Thus the local FCC can effectively balance the flow distribution of each SMSC or MAP Server. For SMs exceeding the current processing capability of the system, the local FCC follows the direction of the inter-office FCC. That is, it transfers some of the SMs to the inter-office FCC for processing while the others are still processed locally.
  • License floating The FCC can automatically adjust the running license of the SMS system according to the running condition of the system. The floating range is within the network license based on the total license of the system. Thus the total license of the whole system can be fully ensured. Software license с running license с (software license + network license). For example, there are three SMS systems. Each SMS system has 1200 software license and 500 network license. Therefore, each SMS system has 1200 initial running license and the system has 3600 license in total. In case an SMS system fails, the FCC automatically adjusts the license of the other two SMS systems to 1700.
Note:
  • Software license: license when the SMS system runs normally.
  • Network license: floatable license.
  • Running license: license used in practical running.
  • Hardware license: the maximum license when the SMS system is running. It is the sum of software license and network license.
  • License: refers to submission speed and delivery speed.
II. Inter-office FCC

The inter-office FCC applies to network SMs. It supports connection to the local FCC.
It can also automatically adjust the overload flow distribution in different offices
through the internal flow distribution algorithm. The adjustment is based on the flow
distribution proportion of distribution-connected offices and the current remaining
processing capability of the systems in different offices. Thus the normal running of
the systems can be ensured.
For example, office A shares the flow of office B and office C in the ratio of 1: 2.
Assume the remaining processing capability of office A is 600 MO SMs/s, the flow
need to be distributed in office B and office C is 500 MO SMs/s and 700 MO SMs/s
respectively. Then the flow actually distributed to office A is 200 MO SMs/s for office B
and 400 MO SMs/s for office C.

MT Module

The MT modules of the SMS system include the Maintenance and Test Server (MT
Server) and the Maintenance and Test Console (MT console), as shown in Figure 2-3.
Through them, you can perform the maintenance, management, and test operations
on the SMS system.

I. MT Server

The MT Server is an intermediate service layer for the interaction of the MT console
and the maintained modules. It has such functions as authentication, MT user
management, message distribution, and status monitoring.
The MT Server has the following features:
  • Running in the dual system mode with high stability and reliability
  • Supporting NM alarms.
  • Supporting report of alarms to the Alert Server through TCP/IP
The functions of the MT Server are as follows:
  • Implementing the authentication for maintenance and test.
  • Ensuring the connection with the service module.
  • Providing the message transmission between the service module and the MT console.
  • Providing the operations on the accounts of MT users.
  • Notifying the MT console of the connection status with the service module.
  • Notifying the service module of the abnormality in connection with the MT console.
  • Providing the interface with the iManager I2000 network management system (NMS).
  • Authenticating the IP addresses of the devices (such as the network management system, MT console, SMCAPP) that request for connection to the MT Server.
  • Monitoring and recording the MT operations implemented by MT subscribers for later query.

II. MT Console

The MT console is an indispensable part of the SMS system. As the maintenance
management terminal of the SMS system, it is responsible for the operation,
maintenance and management of the system. It is also the interface between the
whole system and subscribers, providing friendly graphical user interface (GUI) and
easy operations.
Subscribers can query the status, configure data, and performs monitoring and
tracing respectively on the SMSC, GSM MAP Server, CDMA MAP Server, and MTI
Server through the MT console.

CCM

The Customer Care Module (CCM) stores the value-added service attributes of
subscribers. Interacting with the SMSC, the CCM provides personalized SMSs such
as enhanced status reports, blacklist service, SM forwarding service, and signature
service of the calling and called parties. For example, when the SM delivery succeeds
or fails, the “CCM generates a personalized message to notify the VIP subscriber:
“The message you sent to subscriber 13500001234 at 14: 30 on March, 30th 2006 is
successfully sent to the receiver.”

Alert Server

As the local alert server of the SMS system, the Alert Server communicates with the
alarm source modules (such as SMCAPP) through the Inner Message of TCP/IP. It
receives alarms from alarm source modules and prompts alarms through the sound
box and audio/visual alarm console of the alarm subsystem.
The Alert Server receives alarms from each module of the SMS system. Then it
reports the alarms to the NMS through the MT Server.
On the Web operation platform of the Alert Server, you can query the historical alarms,
clear alarms, filter alarms, set validity period, and so on.

Information Security Monitoring System

The information security monitoring system obtains bills from the SMS system,
implements the analysis and statistics of the bill files, notifies relevant personnel of
questionable subscribers and SPs, gives alarms and records them into the database. Operators can, according to those data, restrict questionable subscribers (or SPs) to
normalize the SM-related behaviors of SM subscribers (or SPs).
For details of the information security monitoring system, refer to corresponding
Online Help.
Note:
Information security monitor differs from information security authentication.
Information security authentication means filtering SMs submitted to the SMS system
in real time for security regards and rejecting the SMs which do not meet
requirements. Information security monitor means monitoring and normalizing the
SM-related actions of subscribers or SPs through after-the-fact statistics.

Report Processing System


The SMS report system, through the statistics of the SM bills, outputs accurate and
visual statistics reports for subscribers, thus facilitating operators in the management
of the SMS system. The SMS report system consists of the pre-statistics system and
the report system.
  • The pre-statistics system is responsible for the resolution and statistics of
original bill records according to the user-defined rules. Then it generates the
statistics table, and writes the statistics table into the report database for the
report system and the network management.
  • The report system is responsible for generating, displaying and outputting SMS
reports. It takes the statistics table generated by the pre-statistics system from
the report database, and generates service reports using the user-defined
templates.
For specific contents of SMS reports, refer to Report System User Manual and
Prestatistics System User Manual

Network Management System

The HUAWEI iManager I2000 Intelligent network management system interacts with
the MT Server of the SMS system through MML, implementing the network monitor of
the SMS system. The iManager I2000 provides the following functions:
  • Topology management: The system reflects in topological views the configurations of SM equipments, the network architecture of the SMS system, and the topological connection between the SM equipments in the local network and that in other networks.
  • Configuration management: The system searches and selects configuration information related to the SM equipments within the local network, functional entities staying on the equipments and the online SMS services. When configuration information is changed, the network management system will obtain information about configuration changes and mark them. In addition, the system manages the automatic update of the information.
  • Fault (Alarm) management: In the network management system, the fault daemon receives in real time alarms of the SM equipments, such as the SMSC, MAP Server, MTI Server and MT server. The alarm foreground displays in real time the alarms.
  • Performance management: The SMSC performance management part provides such performance analyses as CPU occupation statistics, memory occupation statistics, hard-disk operation statistics, mobile termination (MT) failure statistics, mobile origination (MO) failure statistics, flow statistics, Service Report Table A statistics, Service Report Table B statistics and Service Report Table B statistics.
  • Security management: The system controls the network management user authority.
For specific contents of the network management, refer to iManager I2000 Intelligent
Network Management System User Manual.

Hardware Structure

Different hardware structures are adopted by the SMS system according to the
different SM service flows.

I. A Single SMS system installed together with the database

When the SM service flow and number of subscribers are small, a single dual system
serves as the hardware platform for the kernel programs and database of the SMS
system.

In this mode, all programs and database of the SMS system run on the two nodes of
the dual system. Subscriber data, historical SMs are stored on the shared disk array.
The active node of the dual system provides services externally.
When error occurs on the active node, ClusterMng notifies all programs of switchover.
The original standby node provides services externally, ensuring the normal running
of services.

II. A single SMS system installed separately with the database

When the SM service flow and number of subscribers are large, two dual systems are
adopted. One serves as the hardware platform for the kernel programs, and the other
as the hardware platform for database.

In this mode, all programs of the SMS system run on the two nodes of the dual system.
Bill data are stored in the shared array of the dual system. Database runs on the two
nodes of the dual system. Subscriber data, historical SMs are saved in the shared
disk array of the dual system. The active host provides services externally.
When error occurs on the active node, ClusterMng notifies all programs of switchover.
The original standby node provides services externally, ensuring the normal running
of services.

III. Multiple SMSCs with Multiple MAP Servers

When the SM service flow is large, the network of multiple MAP Servers is adopted.
For the GSM network in the mode of multiple MAP Servers, the GAM MAP Server and
MTI Server of each SMSC can be installed together with the SMSC or can be installed
independently. The GSM MAP Servers and MTI Servers of the multiple sets of SMS systems form a crossover network with the SMSC. The FCC conducts route
redundancy and flow distribution. For the CDMA network, the CDMA MAP Server and MTI Server of each SMSC can be installed together with the SMSC or can be installed independently. The CDMA MAP Servers and MTI Servers of the multiple sets of SMS systems form a crossover network with the SMSC. The FCC is installed independently on a minicomputer on dual system so that to realize hardware redundancy.

Huawei infoX-SMC System Description: System Overview

This chapter describes the basic features of the infoX-SMS system. Taking the GSM
and CDMA networks for example, this chapter covers the position of the SMS system
in the mobile network, as well as the functions and compliant specifications of the
infoX-SMS system.
You can learn about the features of the SMS system through reading this chapter.

Basic Concepts

The infoX-SMS system is a service processing system independent of the mobile
network. It is responsible for submitting, storing, and forwarding short messages
(SMs). It implements the interconnection with such networks as the public switched
telephone network (PSTN), integrated services digital network (ISDN) and packet
switched public data network (PSPDN) so as to transfer SMs between extended short
message entities (ESMEs) and mobile stations (MSs).
The SMS system supports the SMC running mode and the FDA running mode. The
license decides which running mode is used in the SMS system. In the SMC running
mode, the SMS system stores and forwards the SMs. In the FDA running mode, the
SMS system does not store the SMs. Instead, the SMS system delivers the SM once
only. When a delivery fails, the system forwards the SM to the SMS system with the
function of storing SMs.
The basic services of the SMS system include:
Mobile originated (MO) messages
Mobile terminated (MT) messages
Access through SMPP 3.3 and SMPP 3.4
SMs encoded in Unicode
Alert notification service
SM signature service

System Overview

The SMS system:
Implements SM exchange between the GSM, TDMA and CDMA networks.
Communicates with the PSTN, ISDN, and PSPDN, so as to transmit SMs from
other short message entities (SMEs) such as the manual station and the
automatic station. It is responsible for the SM reception, scheduling, storing,
routing, backing up, forwarding, and delivering; implements the management on
the SMEs connected to the SMS system.

System Overview

Besides all the features of the version V300R001, the SMS system of this version is
applied to the CDMA, TDMA, and GSM networks, providing the SM exchange among
the CDMA, GSM and TDMA networks.

Functions of the SMS System

The functions of the SMS system are as follows:
Providing value-added services (VASs) and obtaining profits
As a basic telecom service of the mobile communication network, the SMS enables
subscribers to transmit information through SMs and obtain such useful information
as stock market, weather, sports and bank information, which greatly facilitates
subscribers in getting information and gets subscribers into a better and closer
relationship with operators. At the same time, operators can get direct revenue by
providing VASs based on the SMS service.
Improving quality of service (QoS)
Mobile subscribers have high requirements for timely information transfer. In many
cases such as channel busy, masking or network coverage problems, communication
is difficult and information cannot be exchanged. With the SMS system, subscribers
can get information at the earliest time and smooth information transmission is
ensured.
Improving connectivity and reducing congestion of the mobile network
According to statistics, over 30% of calls or faxes cannot be charged due to busy line
or no reply, resulting in the waste of network resources. As a solution to this problem,
the SMS system can connect incoming calls manually or automatically and record the
information subscribers want to transmit, thus dredging the network. In addition, the
SMS system can reduce false load which is caused by repetitive dialing to an MS
switched off, thus reducing network congestion.

System Features

I. High performance in handling signaling

The SMS system supports the TELLIN-USAU universal signaling access unit serving
as the signaling access gateway.
The TELLIN-USAU has the features as shown in Table 1-1.

Feature Description
High performance in link accessing and handling
It provides powerful signaling handling capacity for the SMS
system.
Open protocol interface
It adopts the standard protocol interface which meets various
networking demands of operators with the SSP, IP, and STP.
High reliability The high reliability rests on the hot backup of components,
redundancy configuration, and excellent software protection, and
error tolerance, support of the congestion control of signaling and
system failure test or isolation. All these factors guarantee the
signaling handling capacity of the system.
Modularized design and smooth expansion The modularized superimposing structure is employed in
hardware design. The expansion of processing frames in the
mode of building blocks (frames are interconnected through
LAN switch) meets increasing capacity requirements of
subscribers.
 The processing capability can meet the capacity expansion
requirement. The busy hour call attempt (BHCA) of the USAU
reaches 39,000,000, with sufficient space for service extension,
can meet the incremental service requirements of subscribers.
In addition, the system supports the online smooth capacity
expansion which does not influence the service running of the
existing modules.


Note:
TELLIN-USAU developed by Huawei Technologies Co., Ltd. is used as:
  • the front end equipment for switching and accessing
  • the signaling processing equipment of the SMS system


II. Modularized design and smooth expansion

Adopting TELLIN-USAU, the signaling gateway (SG) supports 112 links of 2 Mbps
links or 1792 links of 64 Kbps. The infoX-SMS system adopts the modularized design
and networking SMS system mode. The system distributes SMs among multiple MAP
Servers and FCCs. Multiple SMS systems form a networking SMS system. SMs are
distributed dynamically among different SMS systems, thus enhancing the reliability
and fault tolerance of the whole system. The flexible networking mode enables you to
choose from multiple MAP Servers networking, FCC flow distribution networking, and
so on.

III. Complete integration of SMS services in the GSM, CDMA, and TDMA
networks


The TELLIN-USAU connects with signaling devices of the CDMA, TDMA, and GSM
networks at the same time, implementing the signaling access of SMs in the CDMA,
TDMA, and GSM networks, and thus processing and scheduling SMs in the three
networks uniformly. One set of the SMS system processes all the SM services of the
three networks uniformly. CDMA, TDMA, and GSM SMs of the same operator do not
need to be forwarded through another SMS system. Meanwhile, the SMS system can
process SMs of a single network by separating signaling processing units (SPUs). It
has the same functions as the Huawei-developed SMS system for the GSM, CDMA,
or TDMA network, but has more powerful processing capability.

IV. Flexible scheduling modes

The SMS system provides three scheduling modes for different services, which are
described in Table 1-2.

Table 1-2 Description of scheduling modes
Scheduling mode Description
Store and Forward Message Mode
If an SM is delivered unsuccessfully, the short message
scheduling center (SMSC) redelivers it until it is successfully
delivered or it is time-out. The delivery interval depends on
the error code returned from the NSS or the service system,
and it can be set. The SM with high priority can be delivered
first.
Datagram Message Mode The SMSC returns the response message to the external
entity as soon as it receives the SM submitted by the external
entity.
The SMSC delivers the SM only once regardless of the
delivery result (success or failure). If the SMSC fails to deliver
the SM due to flow control, however, the SMSC attempts to
deliver it again.
Transaction Message Mode The SMSC immediately delivers an SM submitted by the
ESME, and returns the delivery result to the ESME in the
response to the submission request.


V. Supporting MDEST

Description
If an SM is delivered unsuccessfully, the short message
scheduling center (SMSC) redelivers it until it is successfully
delivered or it is time-out. The delivery interval depends on
the error code returned from the NSS or the service system,
and it can be set. The SM with high priority can be delivered
first.
The SMSC returns the response message to the external
entity as soon as it receives the SM submitted by the external
entity.
The SMSC delivers the SM only once regardless of the
delivery result (success or failure). If the SMSC fails to deliver
the SM due to flow control, however, the SMSC attempts to
deliver it again.
The SMSC immediately delivers an SM submitted by the
ESME, and returns the delivery result to the ESME in the
response to the submission request. The SMS system supports the multidimensional enhanced schedule technology
(MDEST, short message Qos technology), which takes influences of different external
conditions on SM transmission into consideration on the basis of basic scheduling
mechanism. The feature parameters of the system environment, such as time,
message flux, system kernel parameters, are regarded as factors that can affect the
scheduling algorithm, and are taken into consideration of scheduling strategies. The
SMS System dynamically adjusts scheduling strategies according to these
parameters so as to provide different services for different subscribers.

VI. Supporting L2Cache processing

When the SMSC is busy, some SMs can be temporarily stored in the
L2CacheDaemon database, and they will not be scheduled in real time. When the system load becomes lower, the SMSC reads the stored SMs from the
L2CacheDaemon database to the memory of the SMSC so that the SMs can be
scheduled.
This method reduces the pressure of the busy SMSC, and improves the SM storing
capability of the SMS System, the success rate of the SM transmission and the
customer satisfaction rate.

Note:
When the system runs in the FDA mode, it does not support the L2Cache processing.

VII. Supporting threshold processing

When the rate of a parameter value in the system over the corresponding parameter
value in the License reaches the specified threshold, the system starts the threshold
processing. It reduces the current SMS system load by distributing flow and indicating
busy, ensuring the stability and security of the system and successful SM
transmission.

VIII. Powerful service processing capability

The service processing system is a LAN system. An ordinary hub or a switched hub
can be used for transmission of service data and voice data.
The stable and optimized database processing mechanism adopted by the SMS
system greatly improves the SM processing performance and capability.

IX. Quick and accurate report processing capability

The SMS report system makes statistics of SM bill records, and outputs accurate and
visual statistics reports. The operator thus can know various data of the SMS
operation so as to perform analysis and make decisions, greatly facilitating the
management on the SMS system by the operator.

X. Excellent function of bill statistics

Users can make statistics of flow information of specified SMs by configuring the
counter and statistic groups, and export the information to total traffic bills, service
traffic bills and delivery delay bills. It greatly helps to analyze various SM services.
The SMS system supports two types of bills: charging bill and statistic bill.
Charging bill
Charging bills include ordinary charging bills and CalledFee bills.
After the creation of charging bills, the BillServer obtains charging bills from the
charging bill directory periodically. And after some analysis, submits information of postpaid subscribers to the charging center for fee deduction. The information
in charging bills can satisfy various charging requirements.
Statistic bill
It includes nine types, namely, historical bill, MT bill, MO bill, Alert_SC bill,
performance bill, information security statistic bill, total traffic bill, service traffic
bill and delivery delay bill. These bills can be used by users to analyze the
running condition of the SMS system.

XI. Excellent adaptability to the telecom network


Huawei-developed SMS system can interconnect with the GSM and CDMA networks
of other suppliers, fully satisfying the subscribers' requirements. Meanwhile, the SMS
system can realize SM exchange between different operators through the infoX-SMS
GW, and realize the connection between the charging interfaces of the infoX-SMS
system and the IN of Siemens.

XII. Perfect functions of maintenance, test, management and alarm

The maintenance and test (MT) system of the SMS system provides the functions of
routine maintenance and test, including traffic measurement and recording, SM
processing times measurement, statistics of traffic congestion, quality of service and
performance and SMS test.
The management of performance, maintenance, configuration and reports can be
implemented through the SM manager. At the same time, the system has perfect
functions of system maintenance and test, fault detecting and solving.
For the system faults of switching equipment, database, computer network and host
software, hierarchical audible/visual located alarms can be provided through the
alarm box, and detailed alarm information can be provided.
The SMS system supports uniform remote maintenance and management through
the NMS. In addition, the SMS system provides the MT console which can conduct
maintenance and management on multiple SMS systems.

XIII. Comprehensive system security mechanism


The system's key components adopt the active/standby working mode. They can
conduct switchover automatically.
The system has perfect fault detecting and solving function.
The system is designed with independent functional modules, and the abnormity
inside a functional module cannot affect the normal running of other modules.
The system can implement realtime status tracing and monitoring, and the
operator responsible for system maintenance is informed in time through
audible/visual multimedia alarms, thus ensuring the normal running of the
system.
The system performs a strict syntax check on the input man-machine operation
command, rejects incorrect commands and returns prompts for errors.

The user accounts of the system are uniformly allocated by the system
administrator. Strict encryption and security measurements are taken on
accounts to prevent the access of invalid users.

The system supports network management and monitoring through the
iManager I2000 NMS.

infoX-SMS System in the Network

This section describes the architectures of the GSM, CDMA, and TDMA networks, as
well as the position and functions of the infoX-SMS system in the three networks.

System Architecture

The system architectures of the CDMA, TDMA, and GSM networks are quite similar.
Each of the three network systems is composed of the following four parts: network
subsystem (NSS), base station subsystem (BSS), operation and maintenance center
(OMC), and a great many mobile stations (MSs), as shown in Figure 1-1. There are
interfaces between various subsystems and functional entities within the subsystems.
The specifications in the CDMA, TDMA, and GSM networks stipulate standard
interfaces and communication protocols through which the functional entities can
implement communications coordinately. Adopting different interface specifications
and protocols, the three mobile networks are independent of each other.

In the mobile network, the NSS implements the switching function and database
function. The database function is necessary for subscriber data management,
mobility management and security management. The NSS includes the following
functional entities:
MSC
The MSC controls calls, manages the communication service of MSs within the local
network and with other networks (such as PSTN/ISDN/PSPDN, and other mobile
networks), and provides the charging information. Besides, in order to set up call
routes to MSs, the MSC can also function as the GMSC, that is, querying location
information of MSs.
VLR
The visitor location register (VLR) stores the relevant information of registered
subscribers in the control area, and provides the mobile subscribers with necessary
conditions for call connection. It can be regarded as a dynamic database.
HLR
The home location register (HLR) is the central database of a mobile network. It
stores the information of all mobile subscribers in the control area. The HLR stores
two kinds of information: subscriber data, and location information of MSs for setting
up call routes to the MSs.
AuC
The AuC stores authentication algorithm and encryption key, which prevent illegal
subscribers from accessing the system, thus ensuring the security of the mobile
subscribers' communications through the radio interface.
EIR
The EIR stores the International Mobile Equipment Identity (IMEI.). Generally the AuC
and the EIR are integrated physically.
Generally, the MSC and the VLR are integrated physically; and the AUC, EIR and
HLR are integrated physically.

II. BSS

The BSS is the system equipment, which is controlled by the MSC and communicates
with MSs in the specific radio coverage area. It is responsible for radio transmission and reception, and radio resource management. The BSS consists of the following
two functional entities:
Base station controller (BSC)
The BSC is responsible for radio network resource management, cell configuration
data management, power control, location and switchover. It implements powerful
communication control function.
Base transceiver station (BTS)
The BTS is the radio interface equipment, which is controlled by the BSC. It handles
the radio connection, conversion between radio signals and landline signals, radio
diversity, radio channel encryption, frequency hopping, and so on.

III. OMC

The OMC is responsible for managing and controlling the whole GSM and CDMA
networks.

IV. MS

The MS is the mobile subscriber's device. It consists of the following two parts:
Mobile terminal (MT)
The MT implements such functions as voice coding, channel coding, information
encryption, information modulation and demodulation, information transmission
and reception.
Subscriber identity module/user identity module card (SIM/UIM card)
The SIM/UIM card is an intelligent card, which keeps the subscriber identity
information and the management data related to the subscriber and network. An
MT with an SIM card inside can access the telecom network.

Position of the SMS System in the Network

The position of the SMS system in the network is as shown in the circle in Figure 1-1.
The physical entities related to the SMS system are the MSC, VLR and the HLR. Their
functions in the SM transmission are as follows:
MSC
Short messages submitted by the MS pass the BSS and reach the MSC. Then the
MSC forwards them to the corresponding SMS system.
After receiving the SMs delivered by the SMS system, the MSC queries the VLR and
the HLR for the related routing and subscriber information, and then delivers them to
subscribers through BSS.
VLR
The VLR stores the temporary information of a subscriber roaming in the local MSC
area. The subscriber must pass the authentication through the VLR before sending an SM, and the MSC queries the route of a subscriber through the VLR before delivering
an SM.
HLR
The HLR is a database for mobile subscriber management. It stores the
subscription information, position information, mobile station international ISDN
number (MSISDN), and international mobile station identity (IMSI) of a
subscriber. Before delivering SM, the SMS system finds which MSC the
subscriber belongs to through the HLR.

External Interfaces

Interface Description Protocol
NMS interface The NMS connects to and interacts with the
infoX-SMS system through this interface to collect
such network element information as alarm,
performance and configuration, thus implementing
such network management functions as topology
management, performance management, fault
management, and configuration management. In this
way, the NMS is able to monitor, maintain and manage
the infoX-SMS system.
MML
MT interface The MT console communicates with the SMS system
with this interface, conducting monitoring,
management, and maintenance on the SMS system.
MT protocol
SMPP interface The infoX-SMS system supports the standard SMPP
3.3 and SMPP 3.4 protocols. Therefore, the
infoX-SMS system can be interconnected with any
service module supporting SMPP, thus expanding the
service functions of the infoX-SMS system. For
example:
The SMS GW communicates with the infoX-SMS
system through SMPP, providing various extended
short message services for terminal users.
The WAP GW communicates with the infoX-SMS
system through SMPP, sending push messages to
MS subscribers through the infoX-SMS system.
The MMSC communicates with the infoX-SMS
system, implementing the SM notification to
subscribers in some MMSC service flows.
SMPP 3.3
Or SMPP 3.4
SMAP interface The infoX-SMS system interacts with the MDSP
through this interface to authenticate and computing
fee for the subscribers of the SMS.
SMAP1.3
SMPP+ interface The infoX-SMS system interacts with the SCP through
this interface to authenticate and charge the
subscribers of the SMS.
SMPP+2.0
Bill interface The charging system obtains charging bills from
the infoX-SMS system through this interface, and
then conducts further processing.
Through this interface, the report server obtains
statistics bills from the infoX-SMS system, makes
statistics on bill records and generates statistics
report
FTP
SS7 interface It is the interface between the infoX-SMS system and
MSs, which does not exist physically. The infoX-SMS
system and MSs communicate through the mobile
network. Therefore, the interface is the external
interface of the signaling access gateway
(TELLIN-USAU).
The TELLIN-USAU can access the narrowband SS7
and the IP-based broadband SS7, so it has two kinds
of signaling interfaces: the TDM-based signaling
interface and the IP-based signaling interface.
The TDM-based signaling interface adopts E1
physical interface, and it can access 64-Kbps and
2-Mbps signaling links.
The IP-based signaling interface adopts the FE
interface of the 10M/100M Ethernet.
SS7