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