Академический Документы
Профессиональный Документы
Культура Документы
Table of Contents
Table of Contents
Table of Contents
Chapter 1 System Overview .................................................................................................... 1-1 1.1 Basic Concepts............................................................................................................. 1-1 1.2 System Overview .......................................................................................................... 1-1 1.2.1 Functions of the SMS System ............................................................................. 1-1 1.2.2 System Features................................................................................................. 1-2 1.3 infoX-SMS System in the Network................................................................................. 1-6 1.3.1 System Architecture............................................................................................ 1-6 1.3.2 Position of the SMS System in the Network......................................................... 1-9 1.4 External Interfaces ........................................................................................................ 1-9 Chapter 2 System Architecture ............................................................................................... 2-1 2.1 Design Concept of the SMS system .............................................................................. 2-1 2.2 SMS System Architecture.............................................................................................. 2-3 2.2.1 Signaling Gateway .............................................................................................. 2-4 2.2.2 MTI Server.......................................................................................................... 2-4 2.2.3 GSM MAP Server ............................................................................................... 2-5 2.2.4 CDMA MAP Server ............................................................................................. 2-5 2.2.5 SMSC................................................................................................................. 2-5 2.2.6 Dual System Management Module...................................................................... 2-7 2.2.7 MT Module.......................................................................................................... 2-9 2.2.8 Alert Server........................................................................................................2-10 2.2.9 Information Security Monitoring System .............................................................2-10 2.2.10 Report Processing System...............................................................................2-11 2.2.11 Network Management System..........................................................................2-11 2.3 Hardware Structure ......................................................................................................2-13 Chapter 3 System Functions and Implementation.................................................................. 3-1 3.1 Basic Service Supporting Functions .............................................................................. 3-1 3.1.1 SM Submission................................................................................................... 3-1 3.1.2 SM Delivery ........................................................................................................ 3-1 3.1.3 Status Report...................................................................................................... 3-1 3.1.4 Information Security Authentication ..................................................................... 3-2 3.1.5 Authentication and Charging ............................................................................... 3-2 3.1.6 Multiple Coding Schemes.................................................................................... 3-3 3.1.7 Number Conversion According to the Fields of TON, NPI, ADDRESS and PID.... 3-4 3.1.8 Authenticating Subscribers.................................................................................. 3-4 3.1.9 Delivery of Long SMs.......................................................................................... 3-5 3.1.10 Delivery of SMs to Multiple Destinations............................................................ 3-6 3.1.11 Delivery of Multiple SMs to a Destination........................................................... 3-6 3.1.12 Virtual SMC Authentication................................................................................ 3-7 3.1.13 Universal Flow of Authentication and Number Conversion................................. 3-7
Huawei Technologies Proprietary ii
Table of Contents
3.1.14 Virtual SMC ...................................................................................................... 3-8 3.1.15 Muitiple MAP Servers Function ......................................................................... 3-8 3.1.16 Multiple Schedule Modes .................................................................................. 3-9 3.1.17 Message Exchange Between the CDMA Network and TDMA Network .............. 3-9 3.1.18 UserAck Messages ........................................................................................... 3-9 3.1.19 Distinguishing Subscriber Network Attributes According to Different Number Segments...................................................................................................................3-10 3.1.20 PUSH Messages of the WAP Service...............................................................3-10 3.1.21 PUSH Messages in the MMS Service...............................................................3-10 3.1.22 PRL Function ...................................................................................................3-11 3.1.23 IRDB................................................................................................................3-11 3.1.24 Supporting UCP 4.0 .........................................................................................3-11 3.1.25 SMs Without Calling Number ...........................................................................3-12 3.1.26 Time Zone Features.........................................................................................3-12 3.1.27 Supporting SMPP 3.3.......................................................................................3-12 3.1.28 Supporting SMPP 3.4.......................................................................................3-13 3.2 Core Scheduling Functions ..........................................................................................3-13 3.2.1 Basic Functions .................................................................................................3-13 3.2.2 Basic Scheduling Processing .............................................................................3-14 3.2.3 SM Priority Processing.......................................................................................3-15 3.2.4 Validity Period Processing..................................................................................3-17 3.2.5 Repeated SM Redelivery Processing .................................................................3-20 3.2.6 Scheduling Mode Processing .............................................................................3-21 3.2.7 Entity-Based Scheduling Processing ..................................................................3-22 3.2.8 Multidimensional Intelligent Scheduling ..............................................................3-23 3.2.9 L2CacheDaemon Processing.............................................................................3-25 3.2.10 Threshold Processing ......................................................................................3-26 3.2.11 Functions of the GSM MAP Server...................................................................3-27 3.2.12 Functions of the CDMA MAP Server ................................................................3-28 3.3 Basic Services .............................................................................................................3-29 3.3.1 MO SMs ............................................................................................................3-29 3.3.2 MT SMs .............................................................................................................3-29 3.3.3 Shortcut Messages ............................................................................................3-29 3.3.4 Twinkle SMs ......................................................................................................3-30 3.3.5 Alert Notification Service ....................................................................................3-31 3.3.6 EMS SMs...........................................................................................................3-31 3.3.7 Prepaid SMs ......................................................................................................3-31 3.4 Management Functions................................................................................................3-32 3.4.1 Logs and Alarms................................................................................................3-32 3.4.2 Bill Statistics and Browsing ................................................................................3-33 3.4.3 System Parameter Setting .................................................................................3-33 3.4.4 System Status Monitoring ..................................................................................3-33 3.4.5 Database Maintenance ......................................................................................3-33
Huawei Technologies Proprietary iii
Table of Contents
3.4.6 Network Management ........................................................................................3-33 3.4.7 Report Statistics.................................................................................................3-33 3.5 Operation and Maintenance .........................................................................................3-34 3.5.1 Authenticating OMC Subscribers........................................................................3-34 3.5.2 Configuring SMS System Parameters ................................................................3-34 3.5.3 Pre-defined SMs ................................................................................................3-35 3.5.4 Setting Authentication and Number Conversion Parameters...............................3-35 3.5.5 SMSC Account Management .............................................................................3-36 3.5.6 Setting Route Tables..........................................................................................3-36 3.5.7 PPS Route Number Segments...........................................................................3-36 3.5.8 Other Operators Number Segment Management...............................................3-36 3.5.9 SMSC Monitoring and Tracing ...........................................................................3-37 3.5.10 SM Test ...........................................................................................................3-38 3.5.11 Exporting SMs to Files .....................................................................................3-38 3.5.12 SM Subscriber Management ............................................................................3-39 3.5.13 Multidimensional Schedule Parameter Management ........................................3-40 3.5.14 L2Cache Management.....................................................................................3-41 3.5.15 Checking the Running Status of the SMS System with MSs .............................3-41 Chapter 4 Charging Function and Implementation................................................................. 4-1 4.1 Charging for the SMS Postpaid................................................................................. 4-1 4.2 Charging for the SMS Prepaid .................................................................................. 4-1 4.2.1 PPS Authentication and Charging Flow............................................................... 4-2 4.2.2 SCP Interconnection Authentication and Charging Flow ...................................... 4-5 4.2.3 MDSP Charging Flow.......................................................................................... 4-6 4.2.4 UTIns Unicom PPS Charging Flow...................................................................... 4-6 4.3 Charging for Long SMs ................................................................................................. 4-8 4.4 Individual Number PPS Function................................................................................... 4-9 Chapter 5 Reliability and Availability Design.......................................................................... 5-1 5.1 Reliability Design .......................................................................................................... 5-1 5.1.1 Dual System Running Mode................................................................................ 5-1 5.1.2 Network Running Mode....................................................................................... 5-2 5.1.3 Flow Control ....................................................................................................... 5-3 5.1.4 Alarm Detection .................................................................................................. 5-3 5.1.5 Security Authentication ....................................................................................... 5-3 5.2 Availability Design......................................................................................................... 5-3 5.3 Extendibility Design....................................................................................................... 5-4 5.3.1 Overall Design .................................................................................................... 5-4 5.3.2 Product Upgrade Capability ................................................................................ 5-4 5.3.3 Function Extendibility .......................................................................................... 5-5 5.3.4 Performance Extendibility.................................................................................... 5-5 Chapter 6 Typical System Applications .................................................................................. 6-1 6.1 Service Networking ....................................................................................................... 6-1
Huawei Technologies Proprietary iv
Table of Contents
6.2 Service Description ....................................................................................................... 6-2 6.3 Processing Flow............................................................................................................ 6-2 Chapter 7 Technical Indexes and Specifications.................................................................... 7-1 7.1 Hardware Specifications................................................................................................ 7-1 7.2 Performance Specifications........................................................................................... 7-2 7.3 International Standard Followed by the SMS System..................................................... 7-2
Mobile originated (MO) messages Mobile terminated (MT) messages Access through SMPP 3.3 and SMPP 3.4 SMs encoded in Unicode
Implements SM exchange between the GSM 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.
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.
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.
l
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.
It adopts the standard protocol interface which meets various networking demands of operators with the SSP, IP, and STP.
l
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.
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.
Huawei Technologies Proprietary 1-2
& Note: TELLIN-USAU developed by Huawei Technologies Co., Ltd. is used as:
l l
the front end equipment for switching and accessing the signaling processing equipment of the SMS system
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.
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.
V. Supporting MDEST
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.
The stable and optimized database processing mechanism adopted by the SMS system greatly improves the SM processing performance and capability.
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.
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.
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.
l l
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.
GSM Network
SMS
CDMA/TDMA Network
NSS
PSTN/ISDN/ PSPDN HLR/AUC/ EIR MSC/VLR
NSS
HLR/AUC/ EIR
MSC/VLR
OMC
DCN
BSC
BSS
BSS
DCN
BSC
OMC
MS
MS
SMS System: Short Message Service System HLR: Home Location Register EIR: Equipment Identity Register VLR: Visitor Location Register BSS: Base Station Subsystem BSC: Base Station Controller BTS: Base Transceiver Station MS: Mobile Station
NSS: Network SubSystem AUC: Authentication Center MSC: Mobile Switching Center PSTN: Public Switched Telephone Network ISDN: Integrated Services Digital Network PSPDN: Packet Switched Public Data Network OMC: Operation & Maintenance Center
I. NSS
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:
l
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.
l
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.
l
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.
l
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:
l
The BSC is responsible for radio network resource management, cell configuration data management, power control, location and switchover. It implements powerful communication control function.
l
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:
l
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.
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.
l
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.
l
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.
infoX-SMS GW
MT interface
SMAP interface MDSP SMPP interface SMPP+ interface WAP GW infoXSMS Bill interface Bill interface SS7 interface Report system MS BOSS system SCP
SMS System: Short Message Service System SMPP: Short Message Peer-to-Peer protocol MMSC: Multimedia Messaging Service WAP GW: Wireless Application Protocol Gateway MS: Mobile Station BOSS: Business and Operation Support System SCP: Service Control Point SMAP: Service Management Access Protocol NMS: Network Management System
Figure 1-2 External interfaces of the infoX-SMS system Table 1-3 introduces the interfaces in details. Table 1-3 Interfaces with external entities Interface Description 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. Protocol
NMS interface
MML
Interface MT interface
Description The MT console communicates with the SMS system with this interface, conducting monitoring, management, and maintenance on the SMS system. 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:
Protocol MT protocol
SMPP interface
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.
The infoX-SMS system interacts with the MDSP through this interface to authenticate and computing fee for the subscribers of the SMS. The infoX-SMS system interacts with the SCP through this interface to authenticate and charge the subscribers of the SMS.
SMAP1.3
SMPP+2.0 FTP & Note: Besides, the BOSS system can also use the NETBIOS protocol in the Windows operating system, obtaining charging bills through network mapping hard disk.
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.
Interface
Description 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).
Protocol
SS7 interface
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.
l
SS7
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.
NMS subsystem
SS7 network
Access subsystem
BOSS system
Figure 2-1 SMS system architecture The functions of each subsystem are as follows:
I. Access subsystem
The access subsystem accesses the SMS system to external systems, which include:
l l l
SS7 network through the signaling access gateway Service network through the SMPP 3.3 or SMPP 3.4 protocol Charging network through SMAP 1.3, SMPP 2.0, files and internal protocols
Signaling processing module composed of the access gateway (such as USAU), MTI Server, and MAP Server SMSC Interfaces adopting different protocols (such as SMPP interface)
V. NMS subsystem
The NMS subsystem implements such functions as network management, maintenance and test, statistics, report generation, and alarming. Physically, the NMS subsystem is composed of the MT console, MT Server, I2000, AlertServer, alarm console, reporting system, and so on.
& Note: For detailed description of the modules of the subsystem, refer to section 2.2 SMS System Architecture.
ClusterMng
MTI Server
DBDaemon
FileMirror TELLIN-USAU
L2Cache Daemon
MS
MT Server: Maintenance and Test Server MAP Server: Mobile Application Part Server MTI Server: Message Transfer Interface Server CCM: Customer Care Module ICC: Intellectual Control Center which is the infoX-SM Assistant system Alert Server: connected with various modules of the SMS system Huawei Technologies Proprietary 2-3
infoX: infoX-SMS GW
FCC: Flow Control Center
& Note: In Figure 2-2 the CCM 1 is connected with the SMCAPP to process called-related services. The CCM 2 is connected with the infoX-SMS GW to handle calling-related services. In addition, the CCM can be directly connected with the SMCPP to handle calling-related services. For detailed information, refer to section . In this figure, the modules in the dotted line box are the service modules of the SMS system; the modules out of the dotted line box are peripheral modules connecting with the SMS system.
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
Huawei Technologies Proprietary 2-4
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.
2.2.5 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 modules such as the CDMA MAP Server, GSM MAP Server. 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 modules comply with the standard SMPP protocol.
Huawei Technologies Proprietary 2-5
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.
I. ClusterMng
ClusterMng is responsible for monitoring and maintaining specific application modules of the SMS system, such as SMCAPP.
l
Dual system management in the Linux operating system In the Linux operating system, the ClusterMng implements the dual system functions of the SMS system together with the VCS management software. The VCS manages and switches the floating IP address and VGs. Meanwhile, the VCS software on the active host is responsible for monitoring the running of each process of the Oracle database (DB2 database), and the ClusterMng. The ClusterMng is responsible for monitoring and maintaining the running of each application module of the SMS system. For example, the running of the scheduling process. If the VCS software on the active host finds that the network running is abnormal, the Oracle database (DB2 database) is abnormal, or the ClusterMng process is abnormal and fails to be restarted, the VCS performs a switchover automatically. If the ClusterMng finds that an exception occurs on a module, it tries to restart the module for several times. When the exception cannot be removed, the ClusterMng decides whether to perform a 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.
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.
2.2.7 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.
MT Console
MT Server
SMSC
MAP Server
MTI Server
Mobile Application Part Server Short Message Scheduling Center Maintenance and Test Server Message Transfer Interface Server Maintenance and Test Console
Figure 2-3 Networking of the MT modules The maintenance and test (MT) system consists of the MT console and MT Server.
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:
l l l
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.
l l
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.
& 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.
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
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.
APP Oracle
APP Oracle
SMC Node1
Disk array
SMC Node2
Figure 2-4 SMS system installed together with the database 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.
APP
APP
SMC Node1
Disk array
SMC Node2
Oracle
Oracle
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.
STP1
STP2
USAU1
USAU2
MTI Server1
MTI Server2
MTI Server3
MTI Server4
MAP Server1
MAP Server2
MAP Server3
MAP Server4
SMSC2 SMSC1
SMSC3 SMSC4
Figure 2-6 Multiple MAP Servers In the mode of multiple MAP Servers, the MAP Server and MTI Server of each SMSC can be installed together with the SMSC or can be installed independently. The MAP Servers and MTI Servers of the multiple sets of SMS systems form a crossover network with the SMSC.
3.1.1 SM Submission
The infoX-SMS system supports the submission of SMs by mobile subscribers and ESMEs.
l
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.
3.1.2 SM Delivery
The infoX-SMS system 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.
l
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.
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:
l l
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 system needs the ICC to manage and support the service of the enhanced status report.
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. When the 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.
MSG_ENCODING Field 00000 00001 00010 00011 00100 00101 00110 00111 01000 01001 8
(see iv) 7 7 16 8 or 16 8 or 16 8 8 7
Latain/Hebrew [28] Latain [27] GSM 7-bit default alphabet [37] All other values are reserved
3.1.7 Number Conversion According to the Fields of TON, NPI, ADDRESS and PID
The system supports three number conversion points: number conversion before NP authentication, number conversion before PPS authentication and number conversion before delivery. At each number conversion point, the number conversion strategies are configurable, thus meeting 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.
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.
Huawei Technologies Proprietary 3-4
For details of number authentication, refer to section 3.1.13 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):
l
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.
l l l
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.
& 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.
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.
l
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.
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.
& Note: Currently, only the GSM part of the SMS system supports the virtual SMC function.
The multiple MAP networking is a typical mode using FCC for load distribution. In this networking mode, if connection between the MAP Server and the SMSC is fine, and the SMSC is overloaded, the distribution function of MAP Server is enabled. The FCC can distribute SMs evenly according to the current SM processing capability of the MAP Server and the SMSC. The FCC can also adjust the License of SMSC dynamically, thus realize the SMs traffic distribution between multiple SMS systems in the network SM mode.
For detailed description of the schedule modes, refer to section 1.2.2 System Features.
3.1.17 Message Exchange Between the CDMA Network and TDMA Network
The system supports the function that the home SMS system of the called party delivers SMs to the destination MS. If the calling party and called party of the SM do not belong to the same SMS system, the home SMS system of the calling party forwards the SM to the home SMS system of the called party. In the CDMA network, the home SMS system of the called party, after sending the SM to the destination MS, sends a status confirmation message to the home SMS system of the calling party, notifying the delivery result, thus ensuring the charging accuracy.
& Note: The status confirmation flow complies with the CDMA network only. If the SMS systems of other manufacturers do not support the preceding specifications, the SMS system of the calling number forwards the SM to the home SMS system of the called number. There is no status acknowledgement flow.
& Note: This function applies to the CDMA/TDMA network only. According to the protocol, the function is developed in the SMS system of this version. This function needs the support of the MS. Currently, there is no application in the network.
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.
& Note: This function is applied in the CDMA network only and is applied in the current network.
3.1.23 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.
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:
l l l l l l l l l
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
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.
Description Queries the details of special SMs Adds users Deletes users Modifies users Queries subscriber Information Handshake messages
MS-to-MS SM
SM type
SM flow The ESME sends an SM to the SMS system through the SMPP interface. The SMSC schedules the SM according to the scheduling strategy and delivers it through the MAP Server at an appropriate time. If the SM fails to be delivered before its life cycle is reached, it will be moved to the SM historical database. Through the MAP Server, the MS submits the SM to the SMSC, which schedules the SM according to the scheduling strategy and then delivers it to ESME through the SMPP protocols. The SM will be interpreted by the ESME. This method is adopted when the MS sends the information service request to the SM information platform.
ESME-to-MS SM
MS-to-ESME SM
For an SM of high priority, the SMSC delivers it forcibly (that is, the SMSC attempts to deliver it once even if the MS is temporarily absent or has no more storage capacity).
When delivering to the recipient, the SMSC delivers SMs of high priority first. For an SM of ordinary priority, the SMSC first decides if the MS is reachable and if it has enough storage capacity. If not, the SMSC does not deliver the SM to the recipient any longer until it receives the Alert_SC message from the network or its redelivery mechanism is started.
In the multidimensional scheduling, the SMSC subdivides the priority of SMs into five levels: Common, Important 2, Important 2, VIP 2 and VIP 1. The operation for each level of the SM varies.
Serial No.
Priority of ordinary SMs The system determines the priorities of the calling number and called number according to the above-mentioned method, obtains the priority of the SM according to the priority strategy table, and delivers the SM to the priority queue corresponding to the called for scheduling. For the following two types of SMs: l The SM with high priority which is submitted to the SMSC by service subscriber. l The pointed-to-point SM submitted to the SMSC by MS subscriber when the SMSC starts the quick deliver function. l The SMSC obtains the priority of the SM according to the preceding method, and then delivers the SM to the queue of one-level higher in priority for scheduling. If the priority of the SM is already the highest priority (VIP1), its current priority does not need to be upgraded. & Note: If the priority strategy table does not exist or the corresponding SM priority of the calling number and called number priorities is not configured in the priority strategy table, the higher one of the priorities of the calling number and called number is used as the priority of an SM. l Priority of status report When the called party of an SM is an ordered entity, the priority of the status report is normal. When the called party of an SM is a free entity, the priority level of status report is the same as that of the SM. l Priority of SMs that are datagram message mode and transaction message mode For SMs in the datagram message mode and transaction message mode, the priority is VIP1. Their scheduling strategy is the first priority even when other SMs with VIP1 priority are in the SM queue.
& Note:
l
You can query the SM priority in historical bills, charging bills, MO bills, historical database and memory of the SMS system. The SM priority is the combination of original priority and scheduling priority of the SM. The original priority, which is set value in bit4, takes the first four bits. The scheduling priority, which is set value of in bit0, bit1 and bit2, takes the next four bits. The value of the SM priority in the query result may be from 0 to 4 and from 16 to 20. The 0 to 4 corresponds to original priority 0, and corresponds to schedule priority that is from 0 to 4. The 16 to 20 corresponds to original priority 1, and corresponds to schedule priority that is from 0 to 4.
The SM priority in MT bills is of two values. The value 0 indicates normal priority, and 1 indicates high priority.
Start
(1)Status report?
Yes
No (2)SM service type specifies validity period? No (3)Service schedule strategy table specifies validity period? No Yes Get validity period Yes Get validity period Yes Get validity period Change to the maximum validity period Yes
(7)Longer than the maximum validity period? No Validity period is not changed
No (5)Service attribute table specifies validity period? No Get validity period Yes Get validity period
Yes
Figure 3-1 Judging validity period flow Table 3-7 Description of judging validity period Serial No. 1 2 Description The validity period of the status report is the default value of the system. If the SM is not a status report, the SMS system judges whether the validity period of the SM service type is configured. If yes, the SMS system adopts the validity period. If not, it proceeds to the next step. The SMS system obtains the validity period of the SM through the service schedule strategy table. If not, it proceeds to the next step. The SMS system judges whether the validity period is contained in the SM. If yes, the SMS system adopts the validity period. If not, it proceeds to the next step. The SMS system obtains the validity period of the SM through the service attribute table. If not, it proceeds to the next step.
Serial No. 6
Description The SMS system judges whether the calling party is registered. If yes, the SMS system adopts the validity period in the registered information. If not, the SMS system adopts the validity period by default. The validity period is adopted after step 1 to 6. The SMS system judges whether the validity period is longer than the maximum validity period of the system. If yes, the validity period is changed to the maximum validity period of the system. If not, the validity period is unchanged.
2) 3)
The infoX-SMS system schedules and delivers the SM. The infoX-SMS system determines the timeout deletion mode of the SM according to the MT error code returned by the wireless network when the SM delivery fails, and accordingly judges whether the SM meets the conditions for timeout deletion. The following are the timeout deletion modes. Each MT error code corresponds to a deletion mode.
Deletion before timeout When a called entity receives a response to delivery of an SM or a delivery failure occurs, the SMSC views whether any SM will time out. If the result of the current time plus the time interval for next delivery is larger than the SM validity time, this SM will time out. The SMSC deletes it immediately whether the SMSC ever delivered it or not.
Deletion after timeout After the SMSC delivers an SM of a called entity, if there is a new SM submission which triggers the delivery of SMs in the called entity in non-work status or the time for redelivering an SM is up in non-work status, the SMSC views whether any SM is time out. If there is, the SMSC deletes it.
& Note: If the validity period is equal to the timeout period, the SMS system recognizes the SM as not timed out, and continues to schedule the SM.
4)
The infoX-SMS system deletes the SM if it meets the conditions for timeout deletion, and then records it into the historical information database.
Caution:
l
For non point-to-point SMs, their validity period, deletion before timeout and deletion after timeout are carried out strictly according to the methods described in the preceding.
For all point-to-point SMs, if they fail to be delivered, the SMS system cannot delete the SM in ten minutes during the redelivery interval. If the validity period is less than ten minutes or the redelivery interval configured, the SMS system reconfigures the validity period of the SM to one hour.
A: scheduling mode specified by the SP when the SM is submitted B: scheduling mode specified in the attributes of the account through whose interface the SM is submitted C: scheduling mode specified in the registration information of the calling party of the SM
Table 3-10 SM scheduling mode Serial No. 1 Description The default scheduling mode, that is, the store and forward mode, is used as the scheduling mode of an SM submitted by an MS through the Gateway (MAP Server) interface. For an SM submitted by a service, if factor A or factor B specifies the default scheduling mode (store and forward), the infoX-SMS system adopts the scheduling mode specified by the other factor. If different scheduling modes are specified by factor A and factor B, and that neither factor A nor factor B specifies the default scheduling mode (store and forward), the infoX-SMS system adopts the default scheduling mode. In case that the scheduling mode cannot be determined by using the preceding methods, the scheduling mode is determined by factor C. In case that the scheduling mode cannot be determined by using the preceding methods, the default scheduling mode is adopted (store and forward).
2)
The infoX-SMS system schedules and delivers an SM according to its scheduling mode.
Table 3-11 Entity-based scheduling processes Serial No. Description After receiving SMs, the SMS system adopts the following methods to create SMEs:
l
The SMS system creates ordered entities by default if the called numbers are MS numbers. Because the SMS system can only delivers an SM to the MS at a same time, the MSISDN cannot be a free entity. If the called numbers are configured in the service attribute table, the SMS system creates free entities or ordered entities according to the specified delivery mode (free delivery or ordered delivery) in the service attribute table of the called numbers. The SMS system creates free entities by default if the called numbers are not registered service numbers, that is, if the called numbers are neither in the service attribute table nor registered numbers or MS numbers. If the number of free entities in the memory exceeds the maximum value set in the License file, the SMS system creates ordered service entities.
For SMs corresponding to different SME type, the SMS system adopts different scheduling strategies in delivering SMs.
l
For SMs sent to ordered entities, The SMS system sequences the SMs according to their priority and submission time, and then put them into the same message queue for scheduling. The system delivers an SM at one time, and delivers the next SM after the delivery of the first one is finished (on receiving the ACK message or timeout message). The SMS system creates ordered entities for MS numbers by default because only one SM can be sent to mobile subscriber at one time. For SMs sent to free entities, The SMs are delivered independently and concurrently. The system does not wait for sending the next message after the delivery of the first one.
busy-hour mode, idle-hour mode, and festival mode, the system administrator can set different scheduling strategies (Redeliver, Write into L2Cache, Delete, Delete all, and Redeliver SM of high priority) for SMs with different MT error codes. Therefore, the SMSC adopts different scheduling strategies for SMs failed to be delivered for different reasons. For each MT error code, the SMS system can configure SM processing strategies of up to 20 levels (Level 1 - level 20). If the SM fails to be delivered after being processed by the processing strategy of the current level, and the system returns the same MT error code, the system adopts the processing strategy of the next level. The SM is deleted from the memory if it is not delivered successfully after being processed by processing strategies of 20 levels.
The system selects the multidimensional scheduling strategy for SMs according to the service scheduling strategy table. l If there are no matched multidimensional scheduling strategies in the service scheduling strategy table, the system decides the multidimensional scheduling strategy according to the priority queue scheduling decision table and the priority of SMs. l The system adopts the default multidimensional scheduling strategy if no matched multidimensional scheduling strategy is found after the preceding methods are used. & Note: It is configurable whether the system adopts the service scheduling strategy table first or the priority queue scheduling decision table first to decide the multidimensional scheduling strategy.
The infoX-SMS system schedules and delivers the SMs. If the delivery fails, the infoX-SMS system determines the scheduling strategy of the SMs according to the current running mode (common mode, busy-hour mode, or festival mode) of the system, the MT error codes returned by the system and the multidimensional strategy of the SMs.
l
4
l
If the delivery fails again and the system returns the same MT codes, the system adopts the processing strategy of the next level in the next delivery. If the SMs still cannot be delivered successfully after being processed by the processing strategies of 20 levels, the system deletes them from the memory. If the system returns different MT error codes, adopt a different scheduling strategy as instructed in step 3.
Writing SMs into the L2CacheDaemon database When the writing conditions are met, the SMSC notifies the L2CacheDeamon to write SMs in the non-work status that meet writing conditions into the L2CacheDaemon database. Table 3-13 lists the conditions on which the SMs are written into the L2CacheDaemon database.
Table 3-13 Modes of writing SMs into L2CacheDaemon database Mode Processing If the SM delivery fails, and the scheduling strategy is Write into L2Cache according to the multidimensional scheduling strategy and the MT error code returned by the system, the SMSC writes the SM into the L2CacheDaemon database. Conduct the operation of Export SMs in memory on the MT console of the infoX-SMS system. Then, the system writes the SMs waiting in the memory because of delivery failure and scheduled time into the L2CacheDaemon database. The system adopts the corresponding threshold processing strategy when the ratio between the actual value of a parameter (for example, MO Speed, MT Speed, or Memory SM number) in the system and that specified in the License file reaches the threshold. If the threshold processing strategy is Write into L2Cache, the SMs that meet the condition are written into the LaCacheDaemon database.
& Note: When the function of writing SMs into the L2CacheDaemon database is triggered, only SMs whose priorities are lower than or equal to Message Queue of Highest Priority in L2Cache are written into the L2CacheDaemon database. The highest priority of SMs that are written into the L2CacheDaemon database is configurable.
Table 3-14 lists the three conditions on which SMs are read back from the L2CacheDaemon database. Table 3-14 Modes of reading back SMs from the L2CacheDaemon database Mode Processing The SMSC periodically judges whether SMs in the L2CacheDaemon database can be read back. When the read-back conditions are met, the SMSC initiatively notifies the L2CacheDaemon, and then the L2CacheDaemon reads back the SMs from the L2CacheDaemon database. The SMSC then creates the SM in the memory and schedules it according to a certain scheduling strategy. When the SMSC receives the ALERT_SC message (the MS is activated or is capable of receiving SMs), the L2CacheDaemon reads back the corresponding SM from the L2CacheDaemon database. If SMs in the L2CacheDaemon database expire, they are forwarded to the expiry partition, read back and then deleted in ten minutes.
Table 3-15 Threshold processing Procedure Description The system adopts a specific threshold processing strategy, for example, distributing flow and indicating busy, rejecting new MO SMs, and writing messages into the L2Cache, when the ratio between the actual value of a parameter (MO Speed, MT Speed, or Memory SM number) in the system and that specified in the License file reaches the threshold. The system stops using the threshold processing strategy when the ratio between the actual value of a parameter in the system and that specified in the License file decreases and reaches the threshold value for stopping the processing strategy.
10) Monitoring resources of the MAP Server 11) Providing the function of querying the location of an MS 12) Monitoring the message exchange between the MAP Server and SMS system, MTI Server and MAP Server 13) Supporting 2M signaling link 14) Supporting SIGTRAN signaling 15) Signaling the feature of multiple signaling points 16) Supporting obtaining delivery routes from different HLRs according to different number segments 17) Receiving SRI messages and Forward MT messages by simulating HLR and MSC 18) Supporting SM interception
19) Supporting networking of multiple MAP Servers, and message distribution by percentage, by calling number segment, and by the ending digits of the called number 20) Supporting testing the normal running of the SMS system in the networking of multiple MAP Servers
10) Supporting monitoring the message exchange between the MAP Server and the
3.3.2 MT SMs
The MT refers to the process that the SMS system sends an SM to the objective MS according to the schedule, and then receives an acknowledgement message from the MS.
& Note: Only the SMS system of the GSM network supports the shortcut messages.
The shortcut message is a kind of SM. After a shortcut message is received, it is displayed on the screen of the MS immediately, while an ordinary short message is displayed only after the subscriber chooses to read it. After the subscriber reads the shortcut message, he can choose whether to save it. If he chooses not to save it, the next SM will overwrite this one. For example, the data coding scheme (DCS) of the UCS2 coding shortcut SM is 24, which is different from the ordinary SM. If the MS supports the shortcut message service, it checks the DCS value after receiving an SM. If the value is 24, the SM is displayed on the screen of the MS immediately. If the MS does not support the shortcut message service, it processes the received SM as an ordinary SM.
& Note: Only the SMS system of the GSM network supports the twinkle messages.
l l l
If the DCS of an SM is 16, the SM is a shortcut SM of 7bit coding. If the DDS of an SM is 20, the SM is a shortcut SM of 8bit coding. If the DDS of an SM is 24, the SM is a shortcut SM of USC2 coding.
The SMS system supports changing the ordinary SMs into shortcut SMs. The subscriber can set calling numbers and time segments as conditions for changing SMs (to be received) into shortcut SMs. For SMs that meet the conditions, the SMS system changes the DCS value of SM attribute, thus changes ordinary SMs into shortcut SMs, and then sends the shortcut SMs to the subscriber.
& Note: NOKIA MS is the product of the NOKIA Corporation. For details of the product, refer to relevant technical materials of the NOKIA Corporation. The NOKIA Corporation reserves all rights of the trade marks and copyrights of its company name, product names and documentation mentioned in this manual.
& Note:
l l
If the UDHI of an SM is 1, the SM has a special SM head. It is an EMS SM. If UDHI is 0, the SM is an ordinary SM.
After the SMS system receives SMs submitted by the prepaid subscribers, the SMS system sends charging petitions to the SCP, and then carries out the processes according to the charging results. For the SMs charged successfully but failed to be delivered, the SMS system notifies the SCP to reimburse the subscriber for the undelivered SMs. The inform modes fall into instant inform and reimbursement bill inform. They are reliable.
The SMS system supports alarms for system resources. For the Windows and UNIX operating systems, the alarms are described in Table 3-17. Table 3-17 Alarms for system resources Serial No. 1 2 3 4 5 Description Alarm monitoring of CPU occupation of the whole system Alarm monitoring of CPU occupation of single process Alarm monitoring of the memory occupation Alarm monitoring of the disk occupation Alarm monitoring of the system disk and the network card failures
the SMS system the operation so as to perform analysis and make decisions, greatly facilitating the management on the SMS system by the operator.
Default SM life cycle Digit adding plan Time-out duration of waiting for ACK
Parameter
Deletion mode
l
Deletion before timeout When a called entity receives a response to delivery of an SM or a delivery failure occurs, SMSC views whether any SM will time out. If the result of the current time plus the time interval for next delivery is larger than the SM validity time, this SM will time out. SMSC deletes it immediately whether SMSC ever delivered it or not. Deletion after timeout After the SMSC delivers an SM of a called entity, if there is a new SM submission which triggers the delivery of SMs in the called entity in non-work status or the time for redelivering an SM is up in non-work status, SMSC views whether any SM is time out. If there is, SMSC deletes it.
IP address of the alarm server PID of each module Mask bit of the alarm function of each module
IP address of the alarm server Process identification of each module It indicates whether to mask the alarm of the corresponding module.
Authentication mode: blacklist or whitelist Whether to convert numbers on a specific number conversion point Number conversion mode: number head conversion or number tail conversion
You can set the calling and called authentication number segments for different SMC addresses and accounts, and the number conversion data on different number conversion points in the infoX-SMS system.
Monitoring System resource This function is used to monitor the system resources shown in Table 3-19.
Table 3-19 Monitored system resources Monitored resource CPU Rate Occupancy Description CUP usage of the server where the SMSC is located Memory usage of the server where the SMSC is located Number of running threads of the SMSC servers can be displayed in real time so that the operation information of the SMSC can be known Number of running processes of the SMSC servers can be displayed in real time so that the operation information of the SMSC can be known Number of SMs in L2Cache currently Number of SMs that the SMSC sent to the L2Cache Number of SMs in the memory of the SMSC currently Number of subscribers registered in the SMSC Number of SMEs in the memory of the SMSC currently. Number of SM entities
l
Process count Number of SMs in L2Cache Number of SMs sent to L2Cache Number of SMs in the memory Number of registered subscribers
An SME is a dynamic object created during the running of the SMSC. The dynamic relationship between SMs and registered SM subscribers is stored on SME.
Monitoring SMs This function is used for subscribers to observe the specific SM status of a specified number in the SMSC and SMEs and SMs on SMEs in the memory. This function includes querying specified subscribers and MO SMs in specified time segment, querying specified subscribers and MT SMs in specified time segment, querying specified subscribers MO SMs in the memory, and querying specified subscribers MT SMs in the memory.
3.5.10 SM Test
This function is used to test the SM transmission, completely set various attributes of the SM, edit the SM contents in the hex system, and display the transmission status and error codes. With the function of SM test, all parameters for transmitting an SM can be set. The parameters include:
l l l l l l l l l l l l l l l l l l l l l l
MSC Address SC Address Dispatching Mode Original Address Original Address Numbering Type Original Address Numbering Plan Destination Address Destination Address Numbering Type Destination Address Numbering Plan Priority RD RP UDHI SR Message Index PID DCS Default SM UDL Periodical Duration Timeout Duration SM Content
This function opens all SM parameters and provides the open SM test function.
Starting exporting SMs into files This operation is to export SMs in the memory of the SMSC into files. The SMs of one or more types shown in Table 3-20 can be exported simultaneously.
Huawei Technologies Proprietary 3-38
Table 3-20 SM types to be exported SM type Point to point Point to service Point to operators other Description SMs sent between mobile subscribers of a same network. SMs sent from local mobile subscribers to SPs. SMs sent from mobile subscribers of one operator to those of other operators. SMs sent from SPs to local mobile subscribers. SMs sent from mobile subscribers of other operators to those of one operator.
Stopping exporting SMs into the files This operation is to stop exporting SMs into the files.
Browsing and tracing SM subscribers This function is used to query and browse the registered SM subscribers in the SMSC, and trace their states (such as "idle", "wait due to delivery failure", "wait due to timed messages", wait due to flow control).
Defining SM subscribers There are three ways to define SM subscribers: defining a single subscriber, defining subscribers in batch, and read from files.
Deleting SM subscribers This function is used to delete subscribers whose numbers are out of service. Modifying subscriber information This function is used to modify the registered information of subscribers with the changes in the subscriber information.
& Note: In addition to SM subscriber management on the MT console, the subscribers can also open accounts, deregister accounts, and change attributes through SMs and website.
Configuring the service attribute table The service attribute table is used to configure the delivery mode (Deliver freely or Deliver orderly), maximum number of submission and delivery and calling validity period for service subscribers.
Managing the group number segments The group number segment means to define a group name, collect one or more number segments and put it/them into the defined group. In this case, the group number segments can be used conveniently in the management of the service schedule decisions, route and the PPS route.
Managing multidimensional scheduling strategies This functions is used to manage the processing mechanism of SMs that are delivered unsuccessfully.
Configuring parameters of authentication and number conversion This function is used to configure rules of authentication and number conversion, set the data of number conversion and authentication, and test rules of authentication and number conversion.
Managing the priority strategies It is used to manage the SM priority strategies that are used to determine the SM priority according to the calling and called number priorities.
Managing the number segment priority It is used to manage the number segment priority. The number segment priority table determines the number priority of subscribers who have not registered in the SMSC.
Managing service schedule decisions It is used to manage the service schedule decision table. The table determines the scheduling strategy of the specified calling service for called number segments and enhances the quality disparity among different services.
Managing the priority queue schedule decisions This function is used to manage default scheduling strategies for different priority queues.
Configuring festival parameters This function is used to configure the time points of each festival (maximum ten festivals), so that the SMSC can schedule the SMs accordingly.
Configuring parameters for busy hour of each week This function can be used to configure the busy hour on each day of a week so that the SMSC can schedule the SMs accordingly.
Configuring idle parameters of each week This function is used to configure the time segments of each week during which flow is light. In these time segments, the SMS system schedules SMs according to the schedule strategy of the idle mode. A maximum of two idle time segments can be configured each day.
Configuring multidimensional schedule parameters It is used to configure parameters for multidimensional scheduling on the SMS system.
Configuring global parameters of the counters This function is to configure basic parameters required by counters. These basic parameters are valid for all counters. Global parameters of the counters include: attributes of the counters, rules of adjusting MO or MT success rate, MO or MT error code, and groups whose delivery delay needs to be counted.
Managing statistic groups This function is to configure information of statistic groups for counters. Managing counters This function is used to configure counters and counter condition for sorting and counting SMs.
You can configure relevant parameters for the SMSC to read SMs from the L2Cache database. In addition, you can compare and synchronize L2Cache parameters of different SMS systems.
l
You can read the L2Cache file in the remote loading directory of the L2Cache module to the memory of the L2Cache module, and then write them from the L2Cache module to the L2Cache database.
l
You can export SMs from the memory of the SMS system to the L2Cache.
l l
Stopping exporting SMs from the memory You can stop SMs from the memory of the SMS system to the L2Cache.
3.5.15 Checking the Running Status of the SMS System with MSs
The maintenance personnel can use an MS to send a test SM to a called number. When receiving the SM, the GSM MAP Server sends it to the specified SMS system
Huawei Technologies Proprietary 3-41
according to the called number. After receiving the test SM, the SMS system returns a message to the calling party, indicating that the SMS system is running normally.
SCP1 SMPP+
SCP3
SMSC
SCP2
1)
For the duration of the MO authentication of an SM, the SMSC forwards authentication and charging requests to the SCP of the corresponding PPS number segment based on the PPS number segment table.
2)
If the SCP returns a message indicating the success of the authentication and charging, the SMSC continues to handle and deliver the SM. Otherwise, the SMSC declines the submission of the SM.
& Note: If the SCP authentication fails and an error code is returned, the SMSC determines whether the calling or the called party passes the authentication according to the configurations in session SCP Code Map in smscppsconfig.ini.
3)
After the delivery of the SM, the SMSC, based on the requirements of the SCP, identifies whether to notify the SCP of the delivery result. If the SMSC forwards the result to the SCP, the SCP identifies whether the pre-deduction in the authentication procedure is valid based on the delivery result. For an invalid deduction, the pre-deduction fee is returned to the subscriber.
& Note: The PPS authentication and charging flows of point-to-point, point-to-service, and service-to-point SMs are the same, but their submission and delivery procedures are different from each other. Here the PPS authentication and charging flow of a point-to-point SM is introduced as an example.
Figure 4-2 shows the basic PPS authentication and charging flow.
MSC 1
SMS_IWMSC
SMSC
SCP
HLR
MSC 2
Forward_SM Message Transfer PPS_USER_CHECK PPS_USER_ CHECK_RESP Message Transfer Send_Routing _Info_For_sm Send_Routing_In fo_For_sm_Ack Forward_SM Delivery Report Delivery Report PPS_CHARGE _NOTIFY PPS_CHARGE_ NOTIFY_RESP
Figure 4-2 PPS authentication and charging flow The flow is described as follows: 1) 2) 3) After the MS submits the SM to the MSC 1, the MSC 1 forwards it to the interworking MSC for short message service (SMS-IWMSC). The SMS-IWMSC submits the SM to the SMSC (Message Transfer). The SMSC identifies whether to authenticate the called party, calling party or charge party based on the route table of the PPS number segment. If no, the handling operation continues. Otherwise, the authentication request message is sent to the corresponding SCP (PPS_USER_CHECK).
& Note: For each object to be authenticated, the SMSC sends an authentication request message (PPS_USER_CHECK) to the SCP. For example, the SMSC queries the PPS number segment table. If it determines that both the calling party and the called party of an SM must be authenticated, it sends two authentication request messages to the SCP for authenticating them respectively.
4)
The SCP identifies whether the subscriber is valid (including such factors as whether it is in the activated status and whether the balance is enough). The SCP then conducts the pre-deduction and returns the authentication response
Huawei Technologies Proprietary 4-3
message (PPS_USER_CHECK_RESP, including the authentication result and notification mode) to the SMSC.
l
Authentication result The value 0 is returned with a successful authentication; otherwise, the error code indicating the failure cause is returned.
Notification mode indicates whether to notify the SCP of the delivery result after an SM is delivered from the SMSC. It can happen in the following four cases: Notifying the SCP no matter the sending of the SM succeeds or not. Notifying the SCP if the sending of the SM fails. Notifying the SCP if the sending of the SM succeeds. Not notifying the SCP no matter the sending of the SM succeeds or not.
5)
The SMSC analyzes the PPS_USER_CHECK_RESP message indicating the authentication result. If the authentication fails, the SMSC declines the submission of the SM. Otherwise, the SMSC continues to handle the SM and submits the message transfer request to the gateway MSC for short message service (SMS-GMSC).
6) 7) 8) 9)
The SMS-GMSC queries the routing information for sending the SM from the HLR (Send_Routing_Info_For_SM) The HLR sends the routing information for sending the SM to the SMS-GMSC (Send_Routing_Info_For_SM_Ack). The SMS-GMSC forwards the SM to the MSC2 where the subscriber is located (Forward_SM) After delivering the SM to the subscriber, the MSC2 returns the delivery report to the SMS-GMSC (Delivery report)
10) The SMS-GMSC forwards the delivery report to the SMSC (Delivery report) 11) Based on the SCP-required notification mode and delivery result, the SMSC identifies whether to forward the short message result notification request message to the SCP. If yes, the SMSC forwards the short message result notification request message to the SCP (PPS_CHARGE_NOTIFY).
& Note: The SMSC writes the reimbursement bill if an exception of the interface between the SMSC and the SCP leads to the failure in the SMSC sending the short message result notification request message.
12) The SCP identifies whether the deduction in the authentication procedure is valid based on the delivery result. If no, the pre-deduction fee is returned to the subscriber. The SCP then forwards the short message result notification response message to the SMSC (PPS_CHARGE_NOTIFY_RESP).
SCP1
SCP2
Figure 4-3 SCP interconnection authentication and charging flow The flow is described as follows: 1) Based on the PPS number segment route table, the SMSC determines that the SCP has to authenticate Subscriber A. Because the SMSC is not directly connected to SCP2 where Subscriber A is located, the SMSC forwards authentication request message to the SCP directly connected with the SMSC (PPS_USER_CHECK). 2) Based on the MSISDN of Subscriber A, SCP1 finds that the SCP where Subscriber A is located is SCP2 and forwards authentication request message to SCP2 (PPS_USER_CHECK). 3) SCP2 identifies whether Subscriber A is valid (including such factors as whether it is in the activated status and whether the payment amount is enough). The SCP then conducts the pre-deduction and returns the authentication response message (PPS_USER_CHECK_RESP, including authentication results and notification modes) to SCP1. 4) 5) SCP1 forwards the authentication response message to the SMSC. (PPS_USER_CHECK_RESP). The SMSC sends the SM. Based on the SCP1-required notification mode and delivery result, the SMSC identifies whether to forward short message result notification request message to SCP1. If yes, the SMSC forwards the short
message result notification request message to SCP1 (PPS_CHARGE_NOTIFY). 6) 7) SCP1 then forwards the short message result notification request message to SCP2 (PPS_CHARGE_NOTIFY). SCP2 identifies whether the deduction in the authentication procedure is valid based on the delivery result. If no, the pre-deduction fee is returned to the subscriber. SCP2 then forwards the short message result notification response message to SCP1 (PPS_CHARGE_NOTIFY_RESP). 8) SCP1 then forwards the short message result notification response message to the SMSC (PPS_CHARGE_NOTIFY_RESP).
& Note: The infoX-MDSP is a data service product that is developed by Huawei and has the full intelligent right. It is a platform used for implementing integrated management and uniform access of the data service on the basis of the mobile communications network.
The SMSC connects to the MDSP through the SMPP+1.0 or SMPP+2.0 protocol. It transmits all point-to-point messages to the MDSP which judges whether a subscriber is a prepaid service or postpaid service subscriber.
l
If the subscriber is a prepaid service subscriber, the MDSP sends a charging request directly to the SCP. If the subscriber is a postpaid service subscriber, the MDSP notifies the SMSC of that, and then the SMSC marks the message as a PPS message in the charging bill, so as to facilitate the charging system to sort the bills required to be charged.
SMG1...n
CM PP
UTIns/conversion module HTTP PP
SMSC1...n
PP SM
Figure 4-4 Connection between the SMSC and the Siemens payment platform
II. The charging flow from the SMSC to the HTTP payment platform through UTIns
The processing flow is as shown in Figure 4-5.
SMSC UTIns PP
(1) Authentication request (2) Charging request (3) Charging ACK (4) Authentication ACK (5) Result Notification (6) Reimbursement request (7) Reimbursement ACK (8) Result Notification ACK
Figure 4-5 Unicom PPS flow for the SMSC 1) Upon receiving SMPP messages from the SMSC, the UTIns converts them into HTTP 1.0 messages, and delivers them to the payment platform.
2)
Upon receiving HTTP 1.0 messages from the payment platform, the UTIns converts them into SMPP messages, and sends them to the SMSC.
III. The charging flow from the SMG to the HTTP payment platform through UTIns
The processing flow is as shown in Figure 4-6.
SMG CMPP (1) sm-chg-req UTIns HTTP PP
(2) Charging request (3) Charging ACK (4) sm-chg-rsp (5) sm-cnfm-req (6) Reimbursement request (7) Reimbursement ACK (8) sm-cnfm-rsp
Figure 4-6 Unicom PPS flow for the SMG 1) 2) Upon receiving CMPP messages from the SMG, the UTIns converts them into HTTP 1.0 messages, and delivers them to the payment platform. Upon receiving HTTP 1.0 messages from the payment platform, the UTIns converts them into CMPP messages, and sends them to the SMG.
& Note: There are two types of messages: charging and reimbursement.
For postpaid subscribers The infoX-SMS system generates a charging bill for each packet of a long SM. The charging system charges the postpaid subscriber according to the charging bills and specific charging policy.
For prepaid subscribers The infoX-SMS system sends the authentication and charging message to the SCP for each packet of a long SM. The SCP authenticates and charges the prepaid subscriber in real time.
For postpaid subscribers The infoX-SMS system generates a charging bill only for the first packet of a long SM. That is to say, it regards that all subsequent packets of the long SM are free. The charging system charges the postpaid subscriber according to the charging bill and specific charging policy.
For prepaid subscribers The infoX-SMS system sends the authentication and charging message to the SCP only for the first packet of a long SM. For all subsequent packets of the long SM, the infoX-SMS system does not send authentication and charging messages to the SCP. That is to say, it regards that all subsequent packets are free. The SCP authenticates and charges the prepaid subscriber in real time.
Active host
Accessible
Figure 5-1 Software composition of the dual system In the dual system running mode, kernel components of the system can be backed up. When the active host is faulty, the system automatically switches to the standby host. The data in the stabdby host are consistent with those on the active host before the fault. The dual system running mode costs less than others and does not need a special operating system. You only need to install the corresponding dual system software in an ordinary operating system. Both nodes of the dual system can still run independently. This mode affects the performance of applications at a lower degree, and it can be used more flexibly.
Huawei Technologies Proprietary 5-1
LSTP1
LSTP2
SG1
SG2
SG3
MAP Server1
MAP Server2
MAP Server3
Ba
ck up
Back
up
SMSC1
SMSC2 SMPP
SMSC3
infoX-SMS GW
SG Signaling Gateway LSTP Low Level signaling Transfer Point SMPP Short Message Peer to Peer Real line: indicates direct connection. Dotted line between an MAP Server and an SG: indicates non-direct connection. Real line between an MAP Server and an SMSC: indicates that the SMSC is the active one. Dotted line between an MAP Server and an SMSC: indicates that the SMSC is the standby one.
Figure 5-2 Networked SMS networking diagram This networking mode associates all infoX-SMS systems within a certain range. It distributes partial flow of heavy-loaded infoX-SMS systems to infoX-SMS systems with lower load for processing, thus sharing resources, reducing the load of the infoX-SMS system overloaded, and enhancing the disaster tolerance capability.
Huawei Technologies Proprietary 5-2
The system conducts flow control at the interface and account levels. It limits the number of submitted SMs but it does not limit that of delivered SMs. The system monitors the actual values of such parameters as the number of SMs, number of SMEs, MO speed, and MT speed in real time. Once the actual value of one of the parameters exceeds the threshold for starting the threshold processing strategy, the corresponding threshold processing strategy is triggered. When the actual value is lower than the threshold value for terminating the threshold processing, the system automatically stops using the threshold processing strategy.
I2000 maintenance mode that supports remote centralized operations In this mode, the I2000 NMS can manage and monitor all network devices in the
remote centralized way, and connect with superior NMS devices through SNMP. Besides common configuration operations, this mode supports the realtime collection of alarm information and statistics data. Alarm information helps users to know the current running status of the system. By analyzing statistics data, users can have an idea about the submission and delivery of SMs.
l
MT console maintenance mode that supports short-distance maintenance In this mode, you can quickly conduct query and setting operations, for example, creating accounts and routes. The modification to configuration information takes effect immediately without the restart of programs. In addition, the batch processing function is provided for some primary operations to increase the operation efficiency.
through the networked SMS system function. For details, refer to section 5.1.2 Network Running Mode. The advanced telecom application environment (ATAE) architecture of hardware provides powerful expandability. The SMS system can run on a single board. You can add SMS systems by adding boards.
Figure 6-1 Networking mode for the SMS system accessing the mobile network
Figure 6-2 MO signaling flow in the GSM network The flow is described as follows: 1) 2) 3) 4) The MS submits an access request and possible authentication message to the VLR. The MS submits an SM to the MSC. The MSC forwards the SM to the SMS-IWMSC (IWMSC: interworking MSC, responsible for processing SMs submitted by an MS). The SMS-IWMSC transfers the SM to the SMS system.
5) 6) 7)
The SMS system sends an acknowledgement (success or error) back to the SMS-IWMSC. The SMS-IWMSC sends the acknowledgement back to the MSC. The MSC sends the acknowledgement back to the MS.
(3) Forward_ ShortMessage (4) SendInfoFor_ MT_SMS (5) Message Transfer (7) Forward_ ShortMessage_ACK (6) ACK
(8) ACK
Figure 6-3 MT signaling flow in the GSM network The flow is described as follows: 1) 2) 3) 4) The SMS system submits the message transfer request to the SMS-GMSC (GMSC: Gateway MSC, responsible for processing delivered SMs). The SMS-GMSC queries from the HLR about the routing information for sending. The SMS-GMSC forwards the SM to the MSC. The MSC queries from the VLR about the routing information for sending, and from the HLR gets back the international mobile subscriber identity (IMSI) of the subscriber and the number of the MSC where the current subscriber is located. 5) 6) 7) 8) The MSC transfers the SM to the MS. The MS sends the acknowledgement back to the MSC. The MSC sends the forwarding report back to the SMS-GMSC. The SMS-GMSC sends the acknowledgement back to the SMS system.
MSC BS
VLR
HLR
MC
Originator SME
(2) REGNOT
(5) regnot
(9) SMSREQ
(8) SMSREQ
(12) smsreq
Figure 6-4 MO and MT signaling flows in the CDMA or TDMA network The flow is described as follows: 1) 2) 3) 4) The destination MS makes itself recognized by other MSCs through registration or other system access. The MSC sends the REGNOT message to the VLR to notify it of the MS location. The VLR forwards the REGNOT message to the HLR to which the MS belongs. The HLR records the SM destination address of the MS, and returns the REGNOT message to the VLR. The attribute information of the MS is contained in the message. 5) 6) The VLR forwards the REGNOT message to the MSC. The originator MS submits an SM through the SMDPP operation to the SMS system, that is, the MS initiates an MO operation.
7) 8)
The SMS system returns the smdpp positive acknowledgement message to the originator MS. If the SMS system does not have the temporary SM routing address of the destination MS, it conducts step 8 to step 13. The SMS system sends the SMSREQ message containing the information of the MS whose route is to be queried to the HLR to which the MS belongs.
9)
The SMS system conducts step 9 to step 12 if the HLR does not have the temporary SM routing address of the destination MS. The HLR forwards the SMSREQ message to the VLR that provides services for the MS.
10) The VLR forwards the SMSREQ message to the MSC providing services for the destination MS. 11) The MSC sends the smsreq message containing the temporary SM routing address of the destination MS to the VLR. 12) The VLR forwards the smsreq message to the HLR. 13) The HLR forwards the smsreq message to the SMS system. 14) The SMS system uses the temporary SM routing address of the destination MS to send the SM through the SMDPP operation to the MSC of the destination MS. 15) The MSC and base station (BS) send the SMD-REQUEST message to the destination MS through an air interface. 16) The destination MS sends the SMD-ACK message to the MSC and the BS, indicating that it receives SMD-REQUEST. 17) The MSC converts SMD-ACK into the smdpp positive acknowledge message, and then sends it to the SMS system.
ITP/STP
CDMA-SMS
CDMA-HLR
CDMA-MSC
(2) SRI (3) SRI_RESP (4) SRI_RESP (5) FOWORD_MT (6) FOWORD_MT (7) SMS_REQ (8) SMS_REQ_RESP (9) SMDPP (10) SMDPP_RESP (11) FOWORD_RESP
(12) FOWORD_RESP
Figure 6-5 Flow of a GSM subscriber sending an SM to a CDMA subscriber The flow is described as follows: 1) After the GSM-SC receives the SM from the calling party, the SM is processed according to the normal flow. Then, the GSM-SC obtains the route for the CDMA subscriber, and sends the SRI message to the signaling gateway, that is, ITP or STP. 2) 3) The signaling gateway forwards the SRI message to the CDMA-SMS. The CDMA-SMS processes the SRI message by simulating the GSM-HLR, uses the SMC number for the CDMA network, and returns the SRI_RESP message to the signaling gateway. 4) 5) 6) 7) The signaling gateway returns the SRI_RESP message to the GSM-SC. The GSM-SC delivers the MT message to the signaling gateway because it has obtained the CDMA-SC number. The signaling gateway forwards the MT message to the CDMA-SMS. The CDMA-SMS delivers the MT message, and the message is processed according to the normal flow. Then, the CDMA-SMS sends the SMS-REQ message to the CDMA-HLR for obtaining the route. 8) 9) The CDMA-HLR returns the SMS-REQ-RESP message, which contains MSC information. The CDMA-SMS delivers the SM to the CDMA-MSC, and the latter delivers the SM to the mobile phone. 10) The CDMA-MSC returns the SMDPP_RESP message.
11) The CDMA-SMS returns the FORWARDMESSAGE_RESP message to the signaling gateway according to the delivery result. 12) The signaling gateway forwards the FORWARDMESSAGE_RESP message to the GSM-SC.
IV. Flow of forwarding SMs between SMS systems for the GSM network
Figure 6-6 shows the flow.
Home SMS system of the Calling party calling party (1) MO-FowardSM (2) MO-FowardSM _Resp Home SMS system of the called party
HLR
Called party
(10) Send the status report message (11)Receives the status report response message (13) Forward the status report message (14 )Receive the status report response message (12)Write the charging bill according to the status report
Figure 6-6 Flow of forwarding SMs between SMS systems for the GSM network The flow is described as follows: 1) 2) 3) Subscriber A (calling party) sends an SM to subscriber B (called party). The message is submitted to the SMS system. The home SMS system of the calling party returns the Mo-ForwardSM-resp message. After finding that subscriber B does not belong to the local SMS system, the SMS system queries the home SMC address of the called party, and starts the SM forwarding flow. If the SMS system cannot find the home SMC address of the
Huawei Technologies Proprietary 6-7
called party in the configuration file, it delivers the SM according to the traditional delivery mode of home SMS system of the calling party. 4) 5) The home SMS system of the calling party forwards the SM to the home SMS system of the called party by sending the Mo-ForwardSM message. Upon receiving the SM forwarded by the home SMS system of the calling party, the home SMS system of the called party checks whether the opposite SMS system is an authentication SMS system. If not, it rejects the SM. Upon receiving the SM, the home SMS system of the called party returns the Mo-ForwardSM-resp message. 6) The home SMS system of the called party queries route information of the called party from the HLR of the called party by sending the sendRoutingInfoForSM message. 7) 8) 9) The HLR of the called party returns route information of the called party to the home SMS system of the called party. The home SMS system of the called party delivers the Mt-ForwardSM message to subscriber B. Subscriber B returns the Mt-ForwardSM-resp to the home SMS system of the called party. 10) After the forwarded SM is delivered successfully or unsuccessfully, for example, the SM has not been delivered successfully yet after its life cycle ends, the home SMS system of the called party generates a final status report and forwards it to the home SMS system of the calling party by sending the MT-ForwardSM message. 11) The home SMS system of the calling party obtains the final delivery status of the SM from the received final status report. 12) The home SMS system of the calling party records the charging bills of SMs according to the status report. 13) The home SMS system of the calling party forwards the status report to the calling party if required. 14) The called party returns a response upon receiving the status report.
After a CDMA subscriber sends an SM to a GSM subscriber, the SM is first submitted to the SMS system for the CDMA network. Two subsequent flows are available: The CDMA-SMS directly obtains the route from the GSM-HLR by simulating the SMS system for the GSM network, and delivers the SM through the GSM-MSC. In this case, the CDMA-SMS does not exchange messages with the GSM-SC.
The CDMA-SMS delivers an MO message to the GSM-SC by simulating the GSM-MSC, and the GSM-SC delivers the SM.
Figure 6-7 illustrates the flow of a CDMA subscriber sending an SM to a GSM subscriber.
GSM-MSC GSM-HLR (2) SRI (3) SRI_RESP (4) SRI_RESP (5) ForwardMessge(MT) ITP/STP (1) SRI CDMA-MC
Figure 6-7 Flow of a CDMA subscriber sending an SM to a GSM subscriber The flow is described as follows: 1) After the CDMA-SMS receives the SM from the calling party, the SM is processed according to the normal flow of processing GSM SMs. Then, the CDMA-SMS obtains the route for the GSM subscriber, and sends the SRI message to the signaling gateway, that is, ITP or STP. 2) 3) 4) 5) 6) 7) 8) The signaling gateway forwards the SRI message to the GSM-HLR. The GSM-HLR returns the SRI-RESP message, which contains the current serving MSC number of the called party. The signaling gateway forwards the SRI_RESP message to the CDMA-SMS. The CDMA-SMS sends the MT message to the signaling gateway according to the obtained route. The signaling gateway sends the MT message to the GSM-MSC. The GSM-MSC sends the message to the called party through the wireless network, and returns the MTACK message to the signaling gateway. The signaling gateway forwards the MTACK message to the CDMA-SMS.
VI. Flow of the CDMA signaling processing module of the SMS system submitting the MO message to the SMS system for the GSM network by simulating the GSM-MSC
Figure 6-8 illustrates the message flow.
GSM-MSC
GSM-HLR
GSM-SC
ITP/STP
(2) ForwardMessage (MO) (3) ForwardMessage _Resp (MOACK) (5) SRI (6) SRI_Resp (7) ForwardMessage (MT) (8) ForwardMessage _Resp (MTACK)
Figure 6-8 Flow of the CDMA signaling processing module of the SMS system submitting the MO message to the SMS system for the GSM network by simulating the GSM-MSC The flow is described as follows: 1) Upon receiving the SM submitted by the calling party, the CDMA-SMS sends an MO message to the signaling gateway, that is, ITP or STP by simulating the GSM-SMC. 2) 3) 4) 5) 6) 7) 8) The signaling gateway forwards the MO message to the GSM-SC. Upon receiving the MO message, the GSM-SC returns the MOACK message to the signaling gateway. The signaling gateway forwards the MOACK message to the CDMA-SMS. The GSM-SC processes the SM according to the normal delivery flow, and obtains the route from the GSM-HLR. The GSM-HLR returns route information to the GSM-SC. The GSM-SC sends the SM to the GSM-MSC according to the MSC number. The GSM-MSC delivers the SM to the destination GSM mobile phone through the wireless network, and returns the MTACK message to the GSM-SC. You can flexibly select one of the preceding-mentioned schemes of sending SMs from the CDMA network to the GSM network according to actual situations.
& Note: You can replace the CDMA network with the TDMA network in the preceding description because the signaling flow on the MAP layer in the CDMA network is the same as that in the TDMA network.
VII. Flow of forwarding SMs between SMS systems for the CDMA network
Figure 6-9 shows the flow.
MC(A)
MC(B)
MS(B)
(2) smdpp
(3) SMDPP
(4) smdpp
(7) SMDPP
(8) smdpp
Figure 6-9 Flow of forwarding SMs between SMS systems for the CDMA network The flow is described as follows: 1) 2) 3) 4) 5) 6) 7) 8) Subscriber A submits an SM to SMS system A. SMS system A sends an smdpp message to subscriber A, indicating submission success. The destination subscriber B does not belong to SMS system A, so SMS system A sends the SM to SMS system B through the SMDPP operation. SMS system B sends an smdpp message to SMS system A, indicating forwarding success. SMS system B sends the SM to subscriber B. Subscriber B sends an smdpp message to SMS system B, indicating delivery success. SMS system B sends the SM delivery status notification to SMS system A through the SMDPP operation. SMS system A sends an smdpp message to SMS system B, responding to the SM delivery status notification.
High: 46U (1U=44.45 mm, 46U=2044.70 mm) Width: 19 inch (1 inch=25.4 mm, 19 inch=482.6 mm) Depth: 750 mm
N610-22 assembly cabinet uses -48V DC power, and working power input ranges between -40V and -57V. The cabinet has working grounding, protection grounding and lightning protection grounding. The host cabinet and standby cabinet use power supply of double load sharing mode. Power consumption is 4230w when N610-22 assembly cabinet in full configuration. Table 7-1 shows the consumption of respective equipment. Table 7-1 Description of equipment consumption Device Power distribution box Fan module frame LAN Switch KVM Switcher ATCA frame CPCI frame 20 60 2 x 30 180 130 2800 600 Power consumption (W)
Device Memory device Tape drive (optional) Total consumption 480 500 4830
YD/T 1039-2000 900/1800MHz TDMA Digital Cellular Mobile Communications Network Short Message Center Equipment Specifications, Volume I Point-to-Point Short Message Service
YD/T 1040-2000 900/1800MHz TDMA Digital Cellular Mobile Communications Network Short Message Center Equipment Test Specifications, Volume I Point-to-Point Short Message Service
YD/T 1094-2000 900/1800MHz TDMA Digital Cellular Mobile Communications Network, Interface Protocols for the Connection of External Short Message Entities (ESMEs) to Short Message Centers (SMCs)
Part I GB 13000.1-93 Information Technology Universal 8-BIT Coding Character Set (UCS): Architecture And Multi-Language Plane YD/T 910.4-1997 Technical Specifications for 900/1800MHz TDMA Digital Cellular Mobile Communications Network Mobile Application Part (MAP) Phase II
ETSI GSM Specifications 03.38 (5.2.0): European Digital Cellular Communications System; Character and Specific Language Information ETSI GSM Specifications 03.40 (4.9.1): European Digital Cellular Communications System; Point-to-Point Short Message Service Technique Implementation
ETSI GSM Specifications 04.11 (4.8.0): European Digital Cellular Communications System; Support of Point-to-Point Short Message Service at the Radio Interface
ETSI GSM Specifications 03.47(5.0.0): European Digital Cellular Communications System; Example of Protocol Stack for Interoperability Between the Service Center and Mobile Switching Center
ETSI GSM Specifications 09.02(6.3.0): ETSI GSM 09.02 Version 6.3.0: Mobile Application Part Specification (Phase 2+) 800 MHz CDMA Digital Cellular Mobile Communications Network, Interface Protocols for the Connection of External Short Message Entities (ESMEs) to Short Message Centers (SMCs)
800 MHz CDMA Digital Cellular Mobile Communications Network Short Message Center Equipment Specifications, Point-to-Point Short Message Service
YD/T 1031-1999 800 MHz CDMA Digital Cellular Mobile Communications Network, Technical Specification for Signaling System Mobile Application Part (MAP)
ANSI T1.114-1988 Signaling System Number7 (SS7)-Transaction Capabilities Application Part (TCAP) Short Message Service for Spread Spectrum Systems (ANSI/TIA/EIA-637-A) ANSI/TIA/EIA-41-D-1997, Cellular Radio telecommunications Intersystem Operations ANSI/TIA/EIA-841, TIA/EIA-41-D Based Network Enhancements for MDN Based Message Centers IS824 CDMA Cell Broadcast Short Message Service Specifications
l l