59606186 InfoX SMS V300R002 System Description

8/18/2019 59606186 InfoX SMS V300R002 System Description

1/102

infoX-SMS System Description Table of Contents

Huawei Technologies Proprietary

i

infoX SMS V300R002

System Description (V1.00)

Huawei Technologies Co., Ltd.

All rights reserved.

PDF !"# "pdfFactory Pro" $#%&'( www.fineprint.cn

http://www.fineprint.cn/http://www.fineprint.cn/


2/102



ii

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




3/102



iii

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




4/102



iv

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 Operator s 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




5/102



v

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




6/102

infoX-SMS System Description Chapter 1 System Overview


1-1

Chapter 1 System Overview

This chapter describes the basic features of the infoX-SMS system. Taking the Global

System for Mobile Communications (GSM) and Code Division Multiple Access

(CDMA) networks for example, this chapter covers the position of the SMS system in

the mobile network, as well as the functions and compliant specifications of the

infoX-SMS system.

You can learn about the features of the SMS system through reading this chapter.

1.1 Basic Concepts

The infoX-SMS system is a service processing system independent of the wireless

network. It is responsible for submitting, storing, and forwarding short messages

(SMs). It implements the interconnection with such networks as the public switched

telephone network (PSTN), integrated services digital network (ISDN) and packet

switched public data network (PSPDN) so as to transfer SMs between extended short

message entities (ESMEs) and mobile stations (MSs).

The basic services of the SMS system include:

l Mobile originated (MO) messages

l Mobile terminated (MT) messages

l Access through SMPP 3.3 and SMPP 3.4

l SMs encoded in Unicode

1.2 System Overview

The SMS system:

l Implements SM exchange between the GSM and CDMA networks.

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

1.2.1 Functions of the SMS System

The functions of the SMS system are as follows:

l Providing value-added services (VASs) and obtaining profits




7/102



1-2

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 Improving quality of service (QoS)

Mobile subscribers have high requirements for timely information transfer. In many

cases such as channel busy, masking or network coverage problems, communication

is difficult and information cannot be exchanged. With the SMS system, subscribers

can get information at the earliest time and smooth information transmission is

ensured.

1.2.2 System Features

I. High performance in handling signaling

The SMS system supports the TELLIN-USAU universal signaling access unit serving

as the signaling access gateway.

The TELLIN-USAU has the features as shown in Table 1-1.

Table 1-1 Features of TELLIN-USAU

Feature Description

Highperformancein linkaccessing andhandling

It provides powerful signaling handling capacity for the SMSsystem.

Open protocolinterface

It adopts the standard protocol interface which meets variousnetworking demands of operators with the SSP, IP, and STP.

Modularizeddesign andsmoothexpansion

l The modularized superimposing structure is employed inhardware design. The expansion of processing frames in themode of building blocks (frames are interconnected throughLAN switch) meets increasing capacity requirements of

subscribers.l The processing capability can meet the capacity expansion

requirement. The busy hour call attempt (BHCA) of the USAUreaches 39,000,000, with sufficient space for service extension,can meet the incremental service requirements of subscribers.

l In addition, the system supports the online smooth capacityexpansion which does not influence the service running of theexisting modules.

High reliability

The high reliability rests on the hot backup of components,redundancy configuration, and excellent software protection, anderror tolerance, support of the congestion control of signaling andsystem failure test or isolation. All these factors guarantee the

signaling handling capacity of the system.




8/102



1-3

& Note:

TELLIN-USAU developed by Huawei Technologies Co., Ltd. is used as:

l the front end equipment for switching and accessing

l the signaling processing equipment of the SMS system

II. Modularized design and smooth expansion

Adopting TELLIN-USAU, the signaling gateway (SG) supports 104 links of 2 Mbps

links or 1664 links of 64 Kbps. The infoX-SMS system adopts the modularized design

and networking SMS system mode. The system distributes SMs among multiple MAP

Servers and FCCs. Multiple SMS systems form a networking SMS system. SMs aredistributed dynamically among different SMS systems, thus enhancing the reliability

and fault tolerance of the whole system. The flexible networking mode enables you to

choose from multiple MAP Servers networking, FCC flow distribution networking, and

so on.

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

networks

The TELLIN-USAU connects with signaling devices of the CDMA, TDMA, and GSM

networks at the same time, implementing the signaling access of SMs in the CDMA,

TDMA, and GSM networks, and thus processing and scheduling SMs in the three

networks uniformly. One set of the SMS system processes all the SM services of the

three networks uniformly. CDMA, TDMA, and GSM SMs of the same operator do not

need to be forwarded through another SMS system. Meanwhile, the SMS system can

process SMs of a single network by separating signaling processing units (SPUs). It

has the same functions as the Huawei-developed SMS system for the GSM, CDMA,

or TDMA network, but has more powerful processing capability.

IV. Flexible scheduling modes

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

Table 1-2 Description of scheduling modes

Scheduling mode Description

Store and ForwardMessage Mode

If an SM is delivered unsuccessfully, the short messagescheduling center (SMSC) redelivers it until it is successfullydelivered or it is time-out. The delivery interval depends onthe error code returned from the NSS or the service system,and it can be set. The SM with high priority can be deliveredfirst.




9/102



1-4

Datagram MessageMode

The SMSC returns the response message to the externalentity as soon as it receives the SM submitted by the externalentity.

The SMSC delivers the SM only once regardless of the

delivery result (success or failure). If the SMSC fails to deliverthe SM due to flow control, however, the SMSC attempts todeliver it again.

TransactionMessage Mode

The SMSC immediately delivers an SM submitted by theESME, and returns the delivery result to the ESME in theresponse 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 externalconditions on SM transmission into consideration on the basis of basic scheduling

mechanism. The feature parameters of the system environment, such as time,

message flux, system kernel parameters, are regarded as factors that can affect the

scheduling algorithm, and are taken into consideration of scheduling strategies. The

SMS System dynamically adjusts scheduling strategies according to these

parameters so as to provide different services for different subscribers.

VI. Supporting L2Cache processing

When the SMSC is busy, some SMs can be temporarily stored in the

L2CacheDaemon database, and they will not be scheduled in real time.

When the system load becomes lower, the SMSC reads the stored SMs from the

L2CacheDaemon database to the memory of the SMSC so that the SMs can be

scheduled.

This method reduces the pressure of the busy SMSC, and improves the SM storing

capability of the SMS System, the success rate of the SM transmission and the

customer satisfaction rate.

VII. Supporting threshold processing

When the rate of a parameter value in the system over the corresponding parameter

value in the License reaches the specified threshold, the system starts the threshold

processing. It reduces the current SMS system load by distributing flow and indicating

busy, ensuring the stability and security of the system and successful SM

transmission.

VIII. Powerful service processing capability

The service processing system is a LAN system. An ordinary hub or a switched hub

can be used for transmission of service data and voice data.




10/102



1-5

The stable and optimized database processing mechanism adopted by the SMS

system greatly improves the SM processing performance and capability.

IX. Quick and accurate report processing capability

The SMS report system makes statistics of SM bill records, and outputs accurate and

visual statistics reports. The operator thus can know various data of the SMS

operation so as to perform analysis and make decisions, greatly facilitating the

management on the SMS system by the operator.

X. Excellent function of bill statistics

Users can make statistics of flow information of specified SMs by configuring the

counter and statistic groups, and export the information to total traffic bills, service

traffic bills and delivery delay bills. It greatly helps to analyze various SM services.

The SMS system supports two types of bills: charging bill and statistic bill.

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

l 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 trafficbill and delivery delay bill. These bills can be used by users to analyze the

running condition of the SMS system.

XI. Excellent adaptability to the telecom network

Huawei-developed SMS system can interconnect with the GSM and CDMA networks

of other suppliers, fully satisfying the subscribers' requirements. Meanwhile, the SMS

system can realize SM exchange between different operators through the infoX-SMS

GW, and realize the connection between the charging interfaces of the infoX-SMS

system and the IN of Siemens.

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

The maintenance and test (MT) system of the SMS system provides the functions of

routine maintenance and test, including traffic measurement and recording, SM

processing times measurement, statistics of traffic congestion, quality of service and

performance and SMS test.

The management of performance, maintenance, configuration and reports can be

implemented through the SM manager. At the same time, the system has perfect

functions of system maintenance and test, fault detecting and solving.




11/102



1-6

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 throughthe NMS. In addition, the SMS system provides the MT console which can conduct

maintenance and management on multiple SMS systems.

XIII. Comprehensive system security mechanism

l The system's key components adopt the active/standby working mode. They can

conduct switchover automatically.

l The system has perfect fault detecting and solving function.

l The system is designed with independent functional modules, and the abnormity

inside a functional module cannot affect the normal running of other modules.

l 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 The system performs a strict syntax check on the input man-machine operation

command, rejects incorrect commands and returns prompts for errors.

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

l The system supports network management and monitoring through the

iManager I2000 NMS.

1.3 infoX-SMS System in the Network

This section describes the architectures of the GSM, CDMA, and TDMA networks, as

well as the position and functions of the infoX-SMS system in the three networks.

1.3.1 System Architecture

The system architectures of the CDMA, TDMA, and GSM networks are quite similar.

Each of the three network systems is composed of the following four parts: network

subsystem (NSS), base station subsystem (BSS), operation and maintenance center

(OMC), and a great many mobile stations (MSs), as shown in Figure 1-1. There are

interfaces between various subsystems and functional entities within the subsystems.

The specifications in the CDMA, TDMA, and GSM networks stipulate standard

interfaces and communication protocols through which the functional entities can

implement communications coordinately. Adopting different interface specifications

and protocols, the three mobile networks are independent of each other.




12/102



1-7

MS MS

MSC/VLR MSC/VLRHLR/AUC/

EIR

HLR/AUC/

EIR

BSC

BTS

DCN

Operation

ConsoleOMC Server

BSC

BTS

OMC Server

SMS

Operation

Console

DCN

GSM Network CDMA/TDMA Network

BSSBSS

NSSNSS

OMCOMC

PSTN/ISDN/

PSPDN

SMS System: Short Message ServiceSystem

NSS: Network SubSystem

HLR: Home Location Register AUC: Authentication CenterEIR: Equipment Identity Register MSC: Mobile Switching CenterVLR: Visitor Location Register PSTN: Public Switched Telephone NetworkBSS: Base Station Subsystem ISDN: Integrated Services Digital NetworkBSC: Base Station Controller PSPDN: Packet Switched Public Data NetworkBTS: Base Transceiver Station OMC: Operation & Maintenance Center

MS: Mobile Station

Figure 1-1 Mobile network

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.




13/102



1-8

l 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 settingup 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 Base station controller (BSC)

The BSC is responsible for radio network resource management, cell configuration

data management, power control, location and switchover. It implements powerful

communication control function.

l Base transceiver station (BTS)

The BTS is the radio interface equipment, which is controlled by the BSC. It handles

the radio connection, conversion between radio signals and landline signals, radio

diversity, radio channel encryption, frequency hopping, and so on.

III. OMC

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

networks.

IV. MS

The MS is the mobile subscriber's device. It consists of the following two parts:

l Mobile terminal (MT)

The MT implements such functions as voice coding, channel coding, information

encryption, information modulation and demodulation, information transmission

and reception.




14/102



1-9

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

1.3.2 Position of the SMS System in the Network

The position of the SMS system in the network is as shown in the circle in Figure 1-1.

The physical entities related to the SMS system are the MSC, VLR and the HLR. Their

functions in the SM transmission are as follows:

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

1.4 External Interfaces

Figure 1-2 shows the external interfaces of the infoX-SMS system.




15/102



1-10

NMS interface

SS7 interface

infoX-

SMS

MT interface

SMPP interface

SMPP interface

SMPP interface

SMPP+ interface

infoX-SMS GW

MMSC

WAP GW

NMS

MT console

MDSP

BOSS systemMS

Bill interface

Report system

Bill interface

SCP

SMAP interface

SMS System: Short Message Service SystemSMPP: Short Message Peer-to-Peer protocol

MMSC: Multimedia Messaging ServiceWAP GW: Wireless Application Protocol GatewayMS: Mobile StationBOSS: Business and Operation Support SystemSCP: Service Control PointSMAP: Service Management Access ProtocolNMS: 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 Protocol

NMSinterface

The NMS connects to and interacts with theinfoX-SMS system through this interface to collectsuch network element information as alarm,performance and configuration, thus implementingsuch network management functions as topologymanagement, performance management, faultmanagement, and configuration management. In thisway, the NMS is able to monitor, maintain and managethe infoX-SMS system.

MML




16/102



1-11


MTinterface

The MT console communicates with the SMS systemwith this interface, conducting monitoring,management, and maintenance on the SMS system.

MT protocol

SMPPinterface

The infoX-SMS system supports the standard SMPP3.3 and SMPP 3.4 protocols. Therefore, theinfoX-SMS system can be interconnected with anyservice module supporting SMPP, thus expanding theservice functions of the infoX-SMS system. Forexample:

l The SMS GW communicates with the infoX-SMSsystem through SMPP, providing various extendedshort message services for terminal users.

l The WAP GW communicates with the infoX-SMSsystem through SMPP, sending push messages to

MS subscribers through the infoX-SMS system.

l The MMSC communicates with the infoX-SMSsystem, implementing the SM notification tosubscribers in some MMSC service flows.

SMPP 3.3

Or SMPP 3.4

SMAPinterface

The infoX-SMS system interacts with the MDSPthrough this interface to authenticate and computingfee for the subscribers of the SMS.

SMAP1.3

SMPP+interface

The infoX-SMS system interacts with the SCP throughthis interface to authenticate and charge thesubscribers of the SMS.

SMPP+2.0

Billinterface

l The charging system obtains charging bills fromthe infoX-SMS system through this interface, andthen conducts further processing.

l Through this interface, the report server obtainsstatistics bills from the infoX-SMS system, makesstatistics on bill records and generates statisticsreport.

FTP

& Note:

Besides, theBOSSsystem canalso use theNETBIOS protocol inthe Windowsoperatingsystem,obtainingcharging billsthroughnetworkmapping harddisk.




17/102



1-12


SS7interface

It is the interface between the infoX-SMS system andMSs, which does not exist physically. The infoX-SMSsystem and MSs communicate through the mobile

network. Therefore, the interface is the externalinterface of the signaling access gateway(TELLIN-USAU).

The TELLIN-USAU can access the narrowband SS7and the IP-based broadband SS7, so it has two kindsof signaling interfaces: the TDM-based signalinginterface and the IP-based signaling interface.

l The TDM-based signaling interface adopts E1physical interface, and it can access 64-Kbps and2-Mbps signaling links.

l The IP-based signaling interface adopts the FEinterface of the 10M/100M Ethernet.

SS7




18/102

infoX-SMS System Description Chapter 2 System Architecture


2-1

Chapter 2 System Architecture

This chapter introduces the design concept and software architecture, as well as the

hardware architecture of the infoX-SMS system.

Reading this chapter helps you get an understanding of the working mechanism of the

infoX-SMS system.

2.1 Design Concept of the SMS system

In logical functions, the SMS system can be divided into the NMS subsystem, service

subsystem, access subsystem, scheduling subsystem, and charging subsystem.

Figure 2-1 shows the logical structure.

SS7 network

Network management,

MT functions, Report

generation, Alarming

BOSS system

Service network

infoX-SMS

NMS

subsystem

Service

subsystem

Access

subsystem

Scheduling

subsystem

Charging

subsystem

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 SS7 network through the signaling access gateway

l Service network through the SMPP 3.3 or SMPP 3.4 protocol

l Charging network through SMAP 1.3, SMPP 2.0, files and internal protocols




19/102



2-2

Physically, the access subsystem includes:

l Signaling processing module composed of the access gateway (such as USAU),

MTI Server, and MAP Server

l

SMSC Interfaces adopting different protocols (such as SMPP interface)

II. Scheduling subsystem

The scheduling subsystem realizes the function of SM scheduling, which includes the

SM storing, forwarding, backup, and routing management and so on.

Physically, the scheduling subsystem is composed of the SMSC, L2CacheDaemon,

historical database, DBDaemon, and so on.

III. Service subsystem

The service subsystem implements the service functions such as SM forwarding and

enhanced status report provided by the SMS system.

Physically, the service subsystem is composed of the SMSC, CCM, UserProxy, the

ICCWebServer, and so on.

IV. Charging subsystem

The charging subsystem conducts charging related functions such as bill creation and

pre-deduction of PPS subscribers.

Physically, charging subsystem is composed of the BillCreater, PPS processing

module of the SMSC, and UTIns.

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




20/102



2-3

2.2 SMS System Architecture

The SMS system is designed with the modularized concept. This system can be

divided into several parts according to different functional categories, which can beselected during the construction of the system depending on the actual needs so as to

provide services of different levels. The system architecture is shown in Figure 2-2.

BillCreater

FileMirror

ClusterMng

To another node of

dual system

Backup

Daemon

DBDaemon

Report

ServerSelector

SMC database

infoX SMS

GW

Mobile network

No.7

TELLIN-USAU

MTI Server

GSM MAP

Server

SMCAPP

MT Server

MT terminal

/NMC

SP ICCWebServer

service database

MS

Alert Server UserProxy

WWW Client

L2Cache

Daemon

Informationsecurity module

CDMA MAP

Server

MT Server: Maintenance and Test Server

MAP Server: Mobile Application Part ServerMTI 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

PDF !"# "pdfFactory Pro" $#%&'( ) www.fineprint.cn

http://www.fineprint.cn/http://www.fineprint.cn/http://www.fineprint.cn/http://www.fineprint.cn/


21/102



2-4

infoX: infoX-SMS GW

FCC: Flow Control Center

Figure 2-2 infoX-SMS system architecture

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

Functions of the modules are detailed in the following sections.

2.2.1 Signaling Gateway

The TELLIN-USAU can be used as the SG of the SMS system. The TELLIN-USAU is

located between the signaling network and the internal processing module of the SMS

system. As the SG, the TELLIN-USAU implements the signaling interaction between

the SMS system and the MSC and the HLR, and accomplishes signaling access andconversion necessary for the information interaction between the MS and the SMS

system.

2.2.2 MTI Server

The MTI Server is the interface layer between the MAP layer and the TCAP layer in

the signaling system number 7 (SS7). The main functions are as follows:

l Processing the conversion between signaling at the TCAP layer and that at the

MAP layer

l Processing basic dialogs processes, including dialog creation, release, and

maintenance, at the MAP layer

l Distributing signaling at the MAP layer among the application modules, including

the MAP Server, USSD Gateway and so on, of the MAP layer

l 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




22/102



2-5

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.3 GSM MAP Server

The GSM MAP Server is the GSM G/IW gateway of the SMS system. It processes the

MAP signaling of the SMS system, converts the MAP signaling into the message of

internal format, and then forwards it to SMSC.

The GSM MAP Server connects with the MTI Server as the client, processing the

MAP signaling. Meanwhile, the GSM MAP Server connects with the SMSC as the

server, implementing the conversion between the MAP signaling and the message of

internal format.

2.2.4 CDMA MAP Server

The CDMA MAP Server is a part of the SMS system. It converts the signaling between

layers TCAP and CDMA MAP, and converts CDMA MAP signaling into messages of

the internal format and forwards them to the SMSC. The CDMA MAP Server, as a

client, connects with the CTI Server directly; or as the server, connects with the USAU

directly; and as the superior level of the signaling access gateway, processes the

CDMA MAP signaling. At the same time, the CDMA MAP Server, as the server, is

connected with the SMSC, implementing the conversion between the CDMA MAP

signaling and messages of the internal format.

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




23/102



2-6

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 readsback 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 theBackupDaemon, 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.




24/102



2-7

When the system load is lower, the SMCAPP, together with the L2CacheDaemon,

reads back the SMs into the memory of the SMSC for rescheduling.

2.2.6 Dual System Management Module

The dual system management module provides dual system management functions

for key system components, enhancing the system stability and security.

I. ClusterMng

ClusterMng is responsible for monitoring and maintaining specific application

modules of the SMS system, such as SMCAPP.

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.

l Dual system management in the Windows system

Under the Windows operating system, ClusterMng and Serverselectoraccomplishes 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.




25/102



2-8

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




26/102



2-9

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 MTI Server MAP Server

MAP Server

Mobile Application Part Server

SMSC Short Message Scheduling CenterMT Server Maintenance and Test Server

MTI Server

Message Transfer Interface Server

MT Console 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 Running in the dual system mode with high stability and reliability

l Supporting NM alarms.

l Supporting report of alarms to the Alert Server through TCP/IP

The functions of the MT Server are as follows:

l Implementing the authentication for maintenance and test.

l Ensuring the connection with the service module.

l Providing the message transmission between the service module and the MT

console.

l Providing the operations on the accounts of MT users.




27/102



2-10

l Notifying the MT console of the connection status with the service module.

l Notifying the service module of the abnormality in connection with the MT

console.

l Providing the interface with the iManager I2000 network management system

(NMS).

l Authenticating the IP addresses of the devices (such as the network

management system, MT console, SMCAPP) that request for connection to the

MT Server.

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

2.2.8 Alert Server

As the local alert server of the SMS system, the Alert Server communicates with the

alarm source modules (such as SMCAPP) through the Inner Message of TCP/IP. It

receives alarms from alarm source modules and prompts alarms through the sound

box and audio/visual alarm console of the alarm subsystem.

The Alert Server receives alarms from each module of the SMS system. Then it

reports the alarms to the NMS through the MT Server.

On the Web operation platform of the Alert Server, you can query the historical alarms,

clear alarms, filter alarms, set validity period, and so on.

2.2.9 Information Security Monitoring System

The information security monitoring system obtains bills from the SMS system,

implements the analysis and statistics of the bill files, notifies relevant personnel of

questionable subscribers and SPs, gives alarms and records them into the database.

Operators can, according to those data, restrict questionable subscribers (or SPs) to

normalize the SM-related behaviors of SM subscribers (or SPs).

For details of the information security monitoring system, refer to corresponding

Online Help.




28/102



2-11

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

2.2.10 Report Processing System

The SMS report system, through the statistics of the SM bills, outputs accurate and

visual statistics reports for subscribers, thus facilitating operators in the management

of the SMS system. The SMS report system consists of the pre-statistics system and

the report system.

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

l 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

2.2.11 Network Management System

The HUAWEI iManager I2000 Intelligent network management system interacts with

the MT Server of the SMS system through MML, implementing the network monitor of

the SMS system. The iManager I2000 provides the following functions:

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

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




29/102



2-12

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

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

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




30/102



2-13

2.3 Hardware Structure

Different hardware structures are adopted by the SMS system according to the

different SM service flows.

I. A Single SMS system installed together with the database

When the SM service flow and number of subscribers are small, a single dual system

serves as the hardware platform for the kernel programs and database of the SMS

system, as shown in Figure 2-4.

Disk arraySMC Node2

APP

Oracle

SMC Node1

Oracle APP

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.

II. A single SMS system installed separately with the database

When the SM service flow and number of subscribers are large, two dual systems are

adopted. One serves as the hardware platform for the kernel programs, and the other

as the hardware platform for database, as shown in Figure 2-5.

Disk array

Disk array

SMC

Node2

APP

SMC

Node1

APP

Oracle Oracle

Database Server1 Database Server2

Figure 2-5 SMS system installed separately with the database

PDF !"# "pdfFactory Pro" $#%&'( dwww.fineprint.cn

http://www.fineprint.cn/http://www.fineprint.cn/http://www.fineprint.cn/


31/102



2-14

In this mode, all programs of the SMS system run on the two nodes of the dual system.

Bill data are stored in the shared array of the dual system. Database runs on the two

nodes of the dual system. Subscriber data, historical SMs are saved in the shared

disk array of the dual system. The active host provides services externally.

When error occurs on the active node, ClusterMng notifies all programs of switchover.

The original standby node provides services externally, ensuring the normal running

of services.

III. Multiple SMSCs with Multiple MAP Servers

When the SM service flow is large, the network of multiple MAP Servers is adopted.

SMSC1

SMSC2

SMSC4

MTI

Server1

MAP

Server1

MTI

Server2

MTI

Server3

MTI

Server4

MAP

Server2

MAP

Server3

MAP

Server4

USAU2USAU1

STP1 STP2

SMSC3

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.




32/102

infoX-SMS System Description Chapter 3 System Functions and Implementation


3-1

Chapter 3 System Functions and Implementation

This chapter introduces the scheduling processing functions of the SMSC, as well as

the basic service functions, system management functions, and system maintenance

functions of the infoX-SMS system.

Reading this chapter enables you to get an understanding of the functions and

features of the infoX-SMS system.

3.1 Basic Service Supporting Functions

The basic service supporting functions support the basic services of the infoX-SMS

system. This chapter covers the basic service supporting functions.

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.

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

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

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

3.1.3 Status Report

The subscriber can obtain the status of an SM he or she sends through the report

returned by the system.




33/102



3-2

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 Forwarding notification (forwarding success)

l Forwarding failure notification (permanent failure)

In addition, the MS can select the requirement for the enhanced status report. The

SMS System returns an SM indicating the SM transfer status to the MS. The system

needs the ICC to manage and support the service of the enhanced status report.

3.1.4 Information Security Authentication

The information security authentication means filtering the SMs submitted to the SMS

system in real time for information security and refusing those SMs not satisfying the

requirements.

1) After receiving an SM, the infoX-SMS system forwards it to the information

security module.

2) The information security module authenticates the SM, for example, it checks

whether the SM contains sensitive words or whether it is a junk SM, and then

returns the authentication result to the infoX-SMS system.

3) The infoX-SMS system processes the SM if it passes the authentication.

Otherwise, it rejects the SM.

3.1.5 Authentication and Charging

The SMS system supports the authentication of PPS service subscribers and Mobile

Virtual Private Network (MVPN) service subscribers.

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

l 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,




34/102



3-3

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.

3.1.6 Multiple Coding Schemes

The infoX-SMS system supports multiple coding schemes, thus supporting multiple

languages.

I. GSM coding schemes that the system supports

l 7-bit compressed coding

l 8-bit coding

l Unicode coding (16bit)

II. CDMA coding schemes that the system supports

The system supports the following five coding schemes of the CDMA network: 00000,

00010, 00011, 00100, and 01001.

Table 3-1 shows the coding schemes that the CDMA network defines.

Table 3-1 Coding schemes that the CDMA network defines

CHARi Encoding Type MSG_ENCODING FieldLength of CHARi

(bits)

Octet,unspecified 00000 8

Extended Protocol Message[21]

00001 (see iv)

7-bit ASCII [25] 00010 7

IA5 (Table 11 OF [31]) 00011 7

UNICODE [29]i 00100 16

Shift-JIS [30]ii 00101 8 or 16

Korean [33]iii 00110 8 or 16

Latain/Hebrew [28] 00111 8

Latain [27] 01000 8

GSM 7-bit default alphabet[37]

01001 7

All other values are reserved




35/102



3-4

III. TDMA coding schemes that the system supports

The system supports the following three coding schemes of the TDMA network:

00001, 00010, and 00100.

Table 3-2 shows the coding schemes that the TDMA network defines.

Table 3-2 Coding schemes that the TDMA network defines

Value Function

00001 IRA

00010 User spccific

00011 Latain 1, as specified in ISO-8859-1

00100 BMP, as specified in ISO-10646

00101 Hebrew, as specified in ISO-8859-8

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

3.1.8 Authenticating Subscribers

For MO service, the SMSC conducts calling and called number authentications.

There are two types of authentication: subscriber authentication and number segment

authentication.

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

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




36/102



3-5

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 areconfigurable):

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.

l 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 forwardingmode 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.

3.1.9 Delivery of Long SMs

The following lists the lengths of ordinary SMs when different coding schemes are

adopted:




37/102



3-6

l Unicode coding: 70 characters

l 8-bit coding: 140 characters

l 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 mustsupport the PHASE2 protocol.

3.1.10 Delivery of SMs to Multiple Destinations

The SMS system supports the sending of an SM to multiple destinations.

1) The ESME submits a Submit_multi message to the infoX-SMS system through

the SMPP 3.4 interface.

2) After receiving the Submit_multi message, the infoX-SMS system creates SMs

according to the attributes of the Submit_multi message (SM content, number of

destination addre

59606186 InfoX SMS V300R002 System Description

Documents

Transcript of 59606186 InfoX SMS V300R002 System Description