Showing posts with label SMS System Structure. Show all posts
Showing posts with label SMS System Structure. Show all posts
Tuesday, November 6, 2012
Structure of the scheduling center
Structure of the scheduling center
Read more...

- MO processIn the MO process, after a mobile subscriber submits an SM to the SMCAPP, the BillCreater generates an MO bill, and the SMCAPP determines whether SMs to be delivered to the called party are stored in the FDB. If yes, the SMCAPP saves the SM to the FDB. Otherwise, the SMCAPP attempts to deliver the SM.
- MT processIn the MT process, the SMCAPP attempts to deliver an SM to a mobile subscriber, and the BillCreater generates an MT bill. If the SM fails to be delivered and is pending redelivery, or is successfully delivered but requires a status report, the SMCAPP saves the SM to the FDB. If the SM is deleted after the final delivery attempt fails, or is successfully delivered but requires no status report, the BillCreater generates a charging bill and history bill, and the DBDaemon saves the SM to the history database.
CDMA MAP Server
CDMA MAP Server
The CDMA MAP Server is a part of the SMSC. 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 SMCAPP. 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 SMCAPP, implementing the conversion between the CDMA MAP signaling and messages of the internal format.
Features of the CDMA MAP Server:
Serial No Function
Serial No Function
1
|
The SM signaling in the CDMA network
|
2
|
The signaling flow of CDMA MSs submitting SMs to the MAP Server,
and forwarding the submitted SMs to the SMCAPP |
3
|
The signaling flow of the SMCAPP delivering SMs in the CDMA network
to the MAP Server, and returning delivery results to the SMCAPP |
4
|
The signaling flow the HLR sending the Alert_SC message to the SMCAPP,
and supporting sending the message to the SMCAPP |
5
|
The message forwarding flow among SMCs for the CDMA network
|
6
|
The delivery of multiple SMs in batches to increase the network efficiency
|
7
|
The monitoring of the running status of the system
|
8
|
The monitoring of the resources of the CDMA MAP Server
|
9
|
The query of the MS location
|
10
|
The monitoring of the message exchange between the MAP Server and
the SMCAPP, and between the MTI Server and the MAP Server |
11
|
The E1/T1 signaling link
|
12
|
The SIGTRAN signaling
|
13
|
Multiple signaling points (SPs)
|
14
|
Supporting the interconnection of equipment for the GSM, CDMA, and
TDMA networks at the headquarters of the China Unicom |
15
|
MSC-located time zones
|
16
|
The sending of Alert_SC messages to several specified SMCs at the
same time |
GSM MAP Server
GSM MAP Server
The GSM MAP Server is the GSM G/IW gateway of the SMSC. It processes the MAP signaling of the SMSC, converts the MAP signaling into the message of internal format, and then forwards it to SMCAPP.
The GSM MAP Server connects with the MTI Server as the client, processing the MAP signaling. Meanwhile, the GSM MAP Server connects with the SMCAPP as the server, implementing the conversion between the MAP signaling and the message of internal format.
Features of the GSM MAP Server
Serial No.
|
Function
|
---|---|
1
|
Supporting multiple-module processing
|
2
|
Supporting Phase 1, Phase 2 and Phase 2+ SM signaling
|
3
|
Supporting the identification of MAP session version in the GSM network
|
4
|
Implementing the signaling flow of submitting SMs from GSM MSs, and transferring the submitted SMs to the SMCAPP
|
5
|
Implementing the signaling flow of delivering SMs from the GSM SMSC, and returning the delivery results to the SMCAPP
|
6
|
Implementing the ALERT_SC signaling flow from the HLR to the SMSC, and sending the corresponding information to the SMCAPP
|
7
|
Supporting the function of sending multiple SMs to improve the network efficiency
|
8
|
Version number of MAP signaling being configurable
|
9
|
Monitoring the running status of the system
|
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 SMSC, MTI Server and MAP Server
|
13
|
Supporting 2 Mbit/s 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 SMSC in the networking of multiple MAP Servers
|
21
|
Supporting MSC-located time zones
|
MTI Server
MTI Server
The MTI Server is the interface layer between the MAP layer and the TCAP layer in the signaling system number 7 (SS7). The main functions are as follows:
- Processing the conversion between signaling at the TCAP layer and that at the MAP layer
- Processing basic dialogs processes, including dialog creation, release, and maintenance, at the MAP layer
- Distributing signaling at the MAP layer among the application modules, including the MAP Server, USSD Gateway and so on, of the MAP layer
- Connecting the application modules at the MAP layer, and distributing messages according to the AC_NAME and SSN of messages
As the server, the MTI Server connects the MAP Server, USSD Gateway, and the signaling access gateway.
When receiving the MAP dialog request at the TCAP layer from the wireless network, the MTI Server sends the request to the corresponding MAP processing module. For dialog requests initiated from the modules of the MAP layer, the MTI Server distributes them to the corresponding signaling access gateway according to a proportion.
SMS System Structure
SMS System Structure
The architecture of the SMSC.
The SMSC is designed with the modularized concept. This system can be divided into several parts according to different functional categories, which can be selected during the construction of the system depending on the actual needs to provide services of different levels. The system architecture is shown.
SMSC architecture


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 SMSC
|
infoX: infoX-SMS GW
|
FCC: Flow Control Center
|
EMP: Extend Message Platform
|
ENUM Server: Electronic Numbering Server
|
NPProxy: Number Portable Proxy
|
Logical Structure
Logical Structure
The design concept of the SMSC.
In logical functions, the SMSC can be divided into the NMS subsystem, service subsystem, access subsystem, scheduling subsystem, and charging subsystem. Here is shows the logical structure.
The functions of each subsystem are as follows:
Access Subsystem
The access subsystem accesses the SMSC to external systems, which include:
- 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
Physically, the access subsystem includes:
- Signaling processing module composed of the access gateway (such as USAU or ASAU), MTI Server and MAP Server
- SMSC Interfaces adopting different protocols (such as SMPP interface)
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 SMCAPP, FDB, historical database, DBDaemon, and so on.
Service Subsystem
The service subsystem implements the service functions such as SM forwarding and enhanced status report provided by the SMSC.
Physically, the service subsystem is composed of the SMCAPP, CCM, UserProxy, the ICCWebServer, and so on.
Subscribe to:
Posts (Atom)