Академический Документы
Профессиональный Документы
Культура Документы
i
1-1
1-1
1-4
1-4
1-4
1-5
1-5
1-5
1-7
1-8
2-1
2-1
2-2
2-3
2-3
2-4
2-6
2-6
2-6
2-7
2-8
2-9
2-10
2-10
2-10
2-11
2-12
2-13
2-13
2-13
2-14
2-14
2-15
2-15
2-15
2-15
2-16
2-16
2-16
2-17
2-17
2-18
2-18
2-18
3-1
3-1
3-1
3-1
3-2
3-3
4-1
4-1
4-3
4-3
4-3
4-4
4-4
4-4
4-5
4-5
4-5
4-5
4-6
4-6
4-7
5-1
5-1
5-1
5-2
5-3
5-4
5-4
5-5
5-5
5-5
5-6
5-7
5-7
5-8
5-9
5-9
5-9
5-10
5-10
5-11
5-12
5-12
5-13
5-13
5-13
5-14
6-1
6-1
6-1
6-2
6-5
6-5
6-8
6-11
6-11
6-11
6-12
6-13
6-13
6-14
6-14
6-15
6-16
6-17
6-17
Hardware Architecture
Table of Contents .........................................................................................
Chapter 1 General Introduction ....................................................................
1.1 Overview of Hardware Architecture ..................................................
1.2 Hardware Architecture Features .......................................................
1.2.1 Modular Design ........................................................................
1.2.2 Dual Network and Dual Plane ..................................................
i
1-1
1-1
1-3
1-3
1-3
1-7
1-7
2-1
2-1
2-1
2-1
2-1
2-1
2-2
2-2
2-2
2-2
2-5
2-6
2-7
2-8
2-8
2-10
2-13
2-14
2-17
2-21
2-22
3-1
3-1
3-2
3-2
3-3
3-5
3-7
3-11
3-18
3-22
3-23
4-1
4-1
4-1
5-1
5-1
5-1
5-2
5-5
5-5
6-1
6-1
6-2
6-2
6-3
6-3
6-4
6-4
6-4
6-5
6-5
Software Architecture
Table of Contents .........................................................................................
Chapter 1 Overview ......................................................................................
1.1 Architecture and Functions ...............................................................
1.1.1 Overall Architecture ..................................................................
1.1.2 Functions ..................................................................................
1.2 Features ............................................................................................
1.2.1 Features of Host Software ........................................................
1.2.2 Features of OMC Software .......................................................
Chapter 2 Host Software ..............................................................................
2.1 General Structure..............................................................................
2.2 Operating System .............................................................................
2.3 Communication Mode .......................................................................
2.3.1 HDLC Link Communication ......................................................
2.3.2 Bus Communication .................................................................
2.3.3 Serial Port Communication .......................................................
2.3.4 TCP/IP Communication ............................................................
2.4 Data Management ............................................................................
2.4.1 Database Structure ...................................................................
2.4.2 Central Database, Controlling Database and SPM
Database ...........................................................................................
2.4.3 VLR Database ..........................................................................
2.5 Resource Management.....................................................................
2.5.1 Types of Shared Resources .....................................................
2.5.2 Resource Management Task ...................................................
i
1-1
1-1
1-1
1-2
1-4
1-4
1-5
2-1
2-1
2-2
2-3
2-4
2-4
2-4
2-4
2-5
2-5
2-7
2-8
2-9
2-10
2-10
2-11
2-12
2-12
2-12
2-14
2-15
3-1
3-1
3-2
3-2
3-3
3-4
3-6
3-6
3-7
3-7
3-7
3-7
3-7
3-8
3-8
3-8
3-9
3-9
3-10
MSC Functions
Table of Contents .........................................................................................
Chapter 1 Mobile Services ...........................................................................
1.1 Basic Telecommunication Services ..................................................
1.1.1 Teleservices .............................................................................
1.1.2 Bearer Services ........................................................................
1.2 Supplementary Services (SS) ...........................................................
1.2.1 Line Identification SS ................................................................
1.2.2 Call Forwarding SS ...................................................................
1.2.3 Call Completion SS ..................................................................
1.2.4 Multiparty SS ............................................................................
1.2.5 Community of Interest SS.........................................................
1.2.6 AoC Supplementary Services...................................................
1.2.7 Call Barring SS .........................................................................
i
1-1
1-1
1-1
1-3
1-5
1-5
1-6
1-6
1-7
1-7
1-8
1-8
1-9
1-10
1-10
1-11
1-12
2-1
2-1
2-1
2-1
2-2
2-2
2-3
2-3
2-4
2-5
2-5
2-6
2-7
2-9
2-10
2-11
2-12
3-1
3-1
3-1
3-2
3-5
3-13
3-16
3-24
3-28
3-34
3-38
3-38
3-40
3-40
3-41
3-42
3-45
3-45
3-46
3-47
3-50
3-52
4-1
4-1
4-1
4-2
4-4
4-4
4-4
4-5
4-6
4-6
4-8
4-8
4-10
4-11
4-12
4-13
4-14
4-14
4-16
4-17
4-19
4-20
SSP Functions
Table of Contents .........................................................................................
Chapter 1 Introduction to WIN ......................................................................
1.1 Concept of Wireless Intelligent Network ...........................................
1.2 Features of Wireless Intelligent Network ..........................................
1.3 Services of Wireless Intelligent Network ...........................................
1.3.1 Pre-Paid Service .......................................................................
1.3.2 Familiarity Number Service ......................................................
1.3.3 Cell and Time Discount ............................................................
1.3.4 Wireless Advertisement Service ...............................................
1.3.5 UCB Service .............................................................................
Chapter 2 WIN Functions .............................................................................
2.1 Standard CAMEL Phase 2 WIN ........................................................
2.1.1 Networking Structure of Standard CAMEL Phase2 WIN ..........
2.1.2 Service Triggering of Standard WIN .........................................
i
1-1
1-1
1-2
1-3
1-3
1-4
1-4
1-4
1-4
2-1
2-1
2-1
2-3
2-4
2-5
2-6
2-7
2-8
2-8
2-9
2-11
3-1
3-1
3-1
3-8
3-12
3-12
3-13
4-1
4-1
4-1
4-1
4-2
4-2
4-3
4-3
4-10
4-10
5-1
5-1
5-2
5-3
5-5
5-7
5-8
5-11
i
1-1
1-1
1-1
1-2
1-2
1-2
1-2
1-4
1-6
1-6
1-7
1-9
1-9
1-10
1-11
1-11
1-13
1-14
1-15
1-15
1-16
1-17
1-19
1-19
1-20
1-21
1-23
1-24
1-25
1-25
1-27
1-27
1-27
1-28
1-29
1-30
1-32
1-32
1-32
1-33
Appendix
Table of Contents .........................................................................................
A-1
A-1
A-6
B-1
C-1
HUAWEI
1. System Description
2. Hardware Architecture
3. Software Architecture
4 MSC Functions
5. SSP Functions
6. Operation and Maintenance
Functions
7. Appendix
M900/M1800 MSC/SSP/IP
Technical Manual
V610
M900/M1800 MSC/SSP/IP
Technical Manual
Manual Version
T2-030255-20040304-C-6.22
Product Version
V610
BOM
31025755
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Trademarks
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Organization
This manual introduces the system architecture, outstanding features, technical indices,
functions and external interfaces of M900/M1800 MSC/SSP/IP, which are the basis for
understanding other manuals. It is divided into 7 modules:
z
briefs the main functions, features, architecture, external interfaces, technical indices
and reliability design of the product.
z
details the functions and features of the hardware system in aspects of cabinets,
frames and boards. The structure of power supply system and clock system is also
introduced here.
z
describes the composition, functions and features of the software system, along with
some typical service procedures.
z
focuses on the service features, network functions, mobile application protocols and
service procedures of the product.
z
introduces the O&M functions of the product in terms of authority setting, alarm
mechanism, data configuration, performance measurement, charging, routine
maintenance, etc.
z
Module 7 Appendix
lists the abbreviations and terms used in this manual, along with the technical
specifications observed by the product.
Intended Audience
The manual is intended for the following readers:
z
Marketing staff
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Arial Narrow
Boldface
Courier New
Description
Boldface
italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... } *
[ x | y | ... ] *
Description
<>
Button names are inside angle brackets. For example, click the <OK>
button.
[]
Window names, menu items, data table and field names are inside square
brackets. For example, pop up the [New User] window.
Description
<Key>
Press the key with the key name inside angle brackets. For example,
<Enter>, <Tab>, <Backspace>, or <A>.
<Key1+Key2>
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
keys should be pressed concurrently.
<Key1, Key2>
Press the keys in turn. For example, <Alt, A> means the two keys should
be pressed in turn.
V. Mouse operation
Action
Description
Click
Press the left button or right button quickly (left button by default).
Double Click
Drag
Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
System Description
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Table of Contents
Table of Contents
Chapter 1 Overview ....................................................................................................................... 1-1
1.1 Mobile Network Where M900/M1800 MSC/SSP/IP Resides ............................................ 1-1
1.2 Functional Units ................................................................................................................. 1-4
1.2.1 Mobile Switching Center (MSC) .............................................................................. 1-4
1.2.2 Service Switching Point (SSP) ................................................................................ 1-4
1.2.3 Intelligent Peripheral (IP)......................................................................................... 1-5
1.3 Networking Modes ............................................................................................................. 1-5
1.3.1 Networking of Visited MSC (VMSC)........................................................................ 1-5
1.3.2 Networking of Gateway MSC (GMSC).................................................................... 1-7
1.3.3 Networking of M900/M1800 MSC/SSP/IP as Independent SSP ............................ 1-8
Chapter 2 System Features .......................................................................................................... 2-1
2.1 Large Capacity................................................................................................................... 2-1
2.2 High Integration and Low Power Consumption ................................................................. 2-2
2.3 High Reliability ................................................................................................................... 2-3
2.4 Support of STM-1 SDH Optical/Electrical Interfaces ......................................................... 2-3
2.5 Provisioning of IWF to Support WAP Access .................................................................... 2-4
2.6 Powerful Signal Tone Function.......................................................................................... 2-6
2.7 Rich Services ..................................................................................................................... 2-6
2.7.1 Wireless Intelligent Services Triggered by Number Segment ................................ 2-6
2.7.2 Customized Value-Added Services......................................................................... 2-7
2.8 Interception Function ......................................................................................................... 2-8
2.9 Flexible Route Selection .................................................................................................... 2-9
2.10 Powerful Number Adaptation Capability........................................................................ 2-10
2.11 Flexible Allocation of Roaming Numbers....................................................................... 2-10
2.12 Virtual Multi-SP Function ............................................................................................... 2-10
2.12.1 Expanded Links between Signaling Points ......................................................... 2-11
2.12.2 Expanded Speech Channels between Signaling Points..................................... 2-12
2.13 Support of 2Mbit/s High-Speed Signaling Link .............................................................. 2-13
2.14 MAP Policing and SCCP Policing.................................................................................. 2-13
2.15 Capability of Serving as LSTP ....................................................................................... 2-13
2.16 Excellent Signaling Compatibility................................................................................... 2-14
2.16.1 MAP Signaling Compatibility ............................................................................... 2-14
2.16.2 CAP Signaling Compatibility ............................................................................... 2-15
2.16.3 TUP Signaling Compatibility................................................................................ 2-15
2.16.4 ISUP Signaling Compatibility .............................................................................. 2-15
2.16.5 CAS Compatibility ............................................................................................... 2-15
2.16.6 Signaling Interworking......................................................................................... 2-16
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Table of Contents
2.17 PRA Interface for Connection with ISDN Users ............................................................ 2-16
2.18 Provisioning of Gs Interface for Connection with GPRS System .................................. 2-16
2.19 Support of SSP Access in Different Countries .............................................................. 2-17
2.20 Convenient Operation Terminal..................................................................................... 2-17
2.21 Smooth Upgrading......................................................................................................... 2-18
2.21.1 Software Patching ............................................................................................... 2-18
2.21.2 Online Capacity Expansion ................................................................................. 2-18
Chapter 3 System Architecture.................................................................................................... 3-1
3.1 Modular Structure .............................................................................................................. 3-1
3.2 System Architecture........................................................................................................... 3-1
3.2.1 Hardware Architecture ............................................................................................ 3-1
3.2.2 Software Architecture.............................................................................................. 3-2
3.3 System Configuration ........................................................................................................ 3-3
Chapter 4 External Interfaces....................................................................................................... 4-1
4.1 Overview ............................................................................................................................ 4-1
4.2 A-interface.......................................................................................................................... 4-3
4.3 C-interface ......................................................................................................................... 4-3
4.4 D-interface ......................................................................................................................... 4-3
4.5 Interfaces between MSCs.................................................................................................. 4-4
4.6 F-interface.......................................................................................................................... 4-4
4.7 G-interface ......................................................................................................................... 4-4
4.8 Gs-interface ....................................................................................................................... 4-5
4.9 L-interface .......................................................................................................................... 4-5
4.10 O&M Interface.................................................................................................................. 4-5
4.11 Billing Interface ................................................................................................................ 4-5
4.12 PRA Interface................................................................................................................... 4-6
4.13 Interface to Fixed Network............................................................................................... 4-6
4.14 LICI .................................................................................................................................. 4-7
Chapter 5 System Reliability ........................................................................................................ 5-1
5.1 Hardware Reliability Measures .......................................................................................... 5-1
5.1.1 Distributed Processing ............................................................................................ 5-1
5.1.2 Multiprocessor Redundancy Technique.................................................................. 5-2
5.1.3 Board-level Hot Standby ......................................................................................... 5-3
5.1.4 Mutual-Aid Operation Mode .................................................................................... 5-4
5.1.5 Fault Detection and Handling.................................................................................. 5-4
5.2 Software Reliability Measures ........................................................................................... 5-5
5.2.1 Preventive Measures .............................................................................................. 5-5
5.2.2 Error Tolerance ....................................................................................................... 5-5
5.2.3 Fault Monitoring and Handling ................................................................................ 5-6
5.3 System Load Control ......................................................................................................... 5-7
5.3.1 Principle of Load Control......................................................................................... 5-7
ii
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Table of Contents
iii
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
Chapter 1 Overview
This chapter describes the system architecture of M900/M1800 MSC/SSP/IP, including
its functional units and networking application. With this chapter, readers can have a
basic and overall understanding of the product.
SCP
M900/M1800
MSC/SSP/IP
PSTN/ISDN
/PSPDN
Internet
/Intranet
BTS BSC
MS
HLR/AUC/EIR
PCU
SGSN
GGSN
Datacom
Network
Billing Center
OMC
Technical Manual
M900/M1800 MSC/SSP/IP
z
System Description
Chapter 1 Overview
The MSC implements call control and manages the communication services of the
MSs within the local network as well as those with other networks such as PSTN, ISDN,
PSPDN and other mobile networks. It also provides charging information.
z
Implementing CAP signaling interface with SCP, SSP/IP can transit intelligent calls
from MSC and GMSC, perform corresponding intelligent call handling according to
different services and provide powerful CAMEL service support.
Generally, SSP/IP and MSC are physically incorporated into one entity.
z
HLR is the central database of the GSM system. It stores the related data of all the MSs
within the control area of this HLR.
z
The AuC stores authentication algorithms and ciphering key to prevent illegal
subscribers from accessing the system, thus ensuring the mobile subscriber
communication security over the radio interface (Um).
z
EIR stores the International Mobile Equipment Identity (IMEI) of the mobile equipment.
It puts the IMEI in one of the three lists: white list, gray list and black list.
Generally, the AuC, EIR and HLR are physically incorporated into one entity.
z
GGSN is a new network element introduced to provide the GPRS services for the MSs
in the GSM network. It provides the routing and encapsulation of data packets between
the GPRS network and external data communication network. The selection of GGSN
is determined by the Access Point Name (APN) subscribed and requested by the
subscriber.
z
SCP stores service control logic for corresponding intelligent services, sends call
control command to the related Service Switching Point (SSP) according to the control
logic and implements flexible control over wireless intelligent services.
z
1-2
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
The BSC has powerful service control function. It is responsible for the wireless
network resources management, cell configuration data management, power control,
location and handover, etc.
z
PCU is a processing unit added to the BSS in the GSM network for the provisioning of
GPRS services. It is in charge of packet service processing and packet radio channel
resource management at the BSS side.
z
The VLR stores the related information of registered subscribers in the control area. It
provides necessary conditions for call connection of mobile subscribers and can be
regarded as a dynamic database.
Generally, the MSC and VLR are physically incorporated into an entity.
z
The OMC is responsible for managing and controlling the GSM network. One end of
the OMC is connected to the GSM network equipment (MSC/SSP/IP, MSC, BSC and
HLR), while the other to the computer console serving as the man-machine interface.
Through OMC, one can monitor the function modules of the GSM network, report
status and locate faults.
Note:
M900/M1800 MSC/SSP/IP integrates functions of MSC/SSP/IP entities. OMC can implement operation
and maintenance over the equipment through BAM (Background Administration Module)
The MS is the mobile device of subscribers and consists of Mobile Terminal (MT) and
Subscriber Identity Module (SIM).
MT completes such functions as speech coding, channel coding, information
encryption, information modulation and demodulation, and information transmitting and
receiving.
SIM is an intelligent module, which stores the subscriber identity information, and
subscriber and network management data. An MT can access the telecom network
1-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
only when it has a SIM inside. This feature allows the separation of the MT and the SIM;
i.e. the SIM can be used in different MTs.
It offers switching functions for all the mobile terminals in the local area, including call
handling, routing, echo cancellation and overload control. It also collects charging
information, performs traffic management, and supports teleservice, bearer service,
supplementary service and intelligent service.
By providing interfaces between the functional entities (BSC, HLR/AUC/EIR, SGSN) of
the mobile network, and between fixed network and other mobile networks, MSC
enables the communication between mobile subscribers, and between fixed network
subscribers and mobile subscribers, as shown in Figure 1-1.
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
Note:
When serving as the VMSC, the M900/M1800 MSC/SSP/IP provides the functions of both MSC and VLR.
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
TMSC
HLR
SCP
CSI triggering
BSS
VMSC/SSP/IP
PSTN
GMSC
II. Serving as VMSC and Overlay SSP/IP equipment in the local network in the
Overlay WIN
The networking mode of the M900/M1800 MSC/SSP/IP serving as the VMSC in the
Overlay mobile intelligent network is shown in Figure 1-3.
SCP
Trigger by
number
segment
Other MSC
OVERLAY
BSS
HLR
VMSC/SSP/IP
GMSC
PSTN
Figure 1-3 Networking of M900/M1800 MSC/SSP/IP serving as the VMSC & Overlay SSP/IP equipment
in local network
1-6
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
Internet
PLMN
HLR
SS7
network
GGSN
SGSN
VMSC
PCU
BSS
Serving as the GMSC and Overlay SSP/IP of the local network in the Overlay WIN
Figure 1-5 shows the networking of the M900/M1800 MSC/SSP/IP serving as the
GMSC of the Overlay WIN.
1-7
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
SCP
HLR
Number
segment
triggering
BSS
VMSC
OVERLAY
PSTN
GMSC/SSP/IP
Figure 1-5 Networking of M900/M1800 MSC/SSP/IP serving as the GMSC and Overlay SSP/IP of the
local network
2)
With strong processing capability and high reliability, the M900/M1800 MSC/SSP/IP is
compliant with integrated STP indices. It can serve as the integrated STP at the same
time. The networking mode is shown in Figure 1-6.
HSTP
LSTP
LSTP
SP
SP
SP
SP
GMSC/LSTP
MSC/SP
LS/SP
MSC/SP
1-8
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 1 Overview
of one or multiple local networks. Thus, the wireless intelligent services can be
provided without upgrading all the network elements (NEs) in the network.
SCP
SCP
SCP
SS7 network
SSP/IP
overlay incoming
BSS
overlay incoming
VMSC
GMSC
PSTN
1-9
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
2-1
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
Note:
The switching structure of three-T network (T % T % T) is composed of GSNU and GCNU boards, that is,
skirt switching GSNU X central switching GCNU X skirt switching GSNU.
Total
(kW)
20
0.7
0.7
0.4
3.8
40
0.7
1.9
0.9
1.1
0.5
5.1
60
0.7
1.9
0.9
1.15
0.55
0.6
6.8
80
0.7
1.9
0.9
1.3
0.6
1.8
0.9
8.`
100
0.7
1.9
0.9
1.4
0.8
1.9
0.9
0.9
0.7
10.`
2-2
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
2-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
M900/M1800
MSC/SSP/IP
GSTU
GSTU
GSTU
OET
STM-1 Optical interface
SDH
NE
622M/
2.5G/
10G
2-4
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
provides 9600bit/s data rate to the subscriber. With CSD as the bearer, it has the
following three networking modes.
1)
Figure 2-2 shows the networking mode. To connect PLMN and PSTN, MSC must
provide InterWorking Function unit (IWF). The M900/M1800 MSC/SSP/IP provides
IWF to accomplish the following functions:
z
Functions
oriented
to
fixed
network,
including
V.23-compliant
Um
M900/M1800 MSC/SSP/IP
BSS
Switch
ISP/RAS
WAP Server
IWF
PSTN
PLMN
BSS: Base Station Subsystem
IWF: InterWorking Function unit
ISP/RAS: Internet Service Provider/ Remote Access Server
Internet: Internet
Internet
In this networking mode, ISDN is used to substitute for PSTN, and IWF is not
mandatory.
M900/M1800 MSC/SSP/IP supports the WAP networking via supporting V.110
transparent and non-transparent mode. In transparent mode, the IWF is not required;
while in non-transparent mode, IWF is required.
3)
In this networking mode, the MSC directly connects with the Internet Service Provider
(ISP) via digital trunk. The ISP is connected with WAP Server in the Internet. The ISP
here should be capable of CSD-IP conversion.
2-5
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
Powerful functions of signal tone generation board: each board can provide 252
channels of tones with the total duration of 8000 seconds.
Signal tone board software can support multiple languages by loading syntax
analysis module. Signal tone board can support 8 languages by loading 8 syntax
analysis modules.
Supporting online board software loading from OMC, Operator can record speech
files by himself, but for each language, one syntax analysis module file should be
loaded.
2-6
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
2-7
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
SCP
CAP
VMSCA/GMSCA
VMSC
A/GMSC A
ISUP
ISUP
SSP
VMSCBB
VMSC
ISUP
AIP
Note:
In the RBT service networking, the AIP and the SSP can also connect each other through other MSC
instead of connecting directly.
2-8
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
parameters comply with G.703 standards. The signaling mode of X3 interface is TUP or
ISUP signaling.
M900/M1800 MSC/SSP/IP also provides the SOSM system for Commonwealth of
Independent States.
Routing according to number length. When the call prefixes are same, but the
called numbers are of different lengths, the MSC will select route according to the
number length.
Routing according to call type. When the called numbers are same, but the calls
are of different types (e.g. one is a common called number, the other is a
forwarded-to number), the MSC will select route according to the type of the call.
Routing according to calling subscriber attribute. When the called numbers are the
same, but the calling subscribers are of different attributes, the MSC will select
route according the attributes of the calling subscriber. The attributes include
subscriber type (common subscriber, preference subscriber), roaming attributes
(local mobile subscriber, National HPLMN subscriber, international HPLMN
subscriber, other national PLMN subscriber, other international PLMN subscriber)
and service attributes (PPS, AOC, HOTBILL and other customized services),
The route can be regarded as all paths that a call has to pass from one destination to
another destination. Each path or the combination of part of the paths between two
points is called a subroute. M900/M1800 MSC/SSP/IP selects speech channels based
on the configuration of routes/subroutes, traffic distribution and the state of these
subroutes (available/unavailable).
M900/M1800 MSC/SSP/IP also provides the function avoiding alternate routing among
the same level of exchanges, which may results in information storm or exhaustion of
circuit resources.
2-9
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
Processing and conversion of numbers for incoming calls and outgoing calls.
The designated roaming number and the handover number use different or the
same prefix/suffix number segments
The length of the subscriber number in the roaming number can be set
The roaming numbers in either the international or the national number format can
be allocated.
2-10
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
Signalling point 1
.....
Signalling point 2
Signalling point n
Other exchange
M900/M1800 MSC/SSP/IP
Figure 2-4 Networking of Multiple SPs
SLS/SLC
OPC
DPC
24
24
First-sent bits
2-11
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
total number of links between this node and remote SPs can reach N X 16. This fully
meets the demand for large traffic.
Virtual multi-SP is a logic definition where one physical node has multiple independent
SPs. Each logic SP can fulfill the same functions as one physical SP. For messages to
the same destination, they can be shared between signaling points.
M900/M1800
MSC/SSP/IP
implements
multi-SP
through
route
control
and
CIC
4
12
OPC
DPC
24
24
First-sent bits
2-12
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
2-13
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
The second level, LSTP, is responsible for transferring signaling messages from the
third level SP. It can use standalone STP equipment, or integrated STP equipment
incorporated with exchange (SP). When standalone STP equipment is adopted, it
should satisfy all functions defined in MTP. When integrated STP equipment is used,
besides functions of standalone STP, its SP should satisfy all functions of SS7 TUP.
The third level, SP, transfer the signaling messages of original point or destination point.
It should satisfy MTP and TUP functions.
M900/M1800 MSC/SSP/IP also provides signaling transfer functions, whose
performance satisfies the requirements for an LSTP. In the network, it can also serve as
LSTP.
The performance indices of M900/M1800 MSC/SSP/IP serving also as LSTP are listed
below:
z
Supporting
three
kinds
of
addressing
DPC+GT+SSN.
2-14
methods:
GT,
DPC+SSN
and
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
The addressing method of various MAP function flows can be specified through
data configuration.
The support of ISUP specifications in specific country can be set through data
configuration.
2-15
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
For the combined location update or IMSI attach generated by GPRS MS,
M900/M1800 MSC/SSP/IP accomplishes the functions requested by SGSN, sets
up and maintains correlation with SGSN.
Identify the combined location update message from SGSN and update the
SGSN-MSC correlation status.
For the MS in correlated state, MSC cooperates with the SGSN to generate
combined paging.
2-16
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
Enhanced intelligent call processing capability in case of SSP and SCP signaling
link failure;
2-17
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 2 System Features
2-18
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 3 System Architecture
M900/M1800 MSC/SSP/IP
Modules
Frames
Circuit boards
3-1
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 3 System Architecture
3-2
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 3 System Architecture
terminal software on RWS (Remote WorkStation). The iGWB software runs on the
iGWB.
For detailed information about software structure and functions of M900/M1800
MSC/SSP/IP, please refer to Module 3 of this manual.
3-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
4.1 Overview
The technical specification for the GSM system (GSM Phase2 and GSM Phase 2+)
provides detailed definitions for interfaces and protocols of MSC and other network
entities. The M900/M1800 MSC/SSP/IP is designed in accordance with these
specifications.
As a physical entity in WIN, M900/M1800 MSC/SSP/IP supports interconnection with
other related entities on the network, and interconnection with the entities and users on
other networks (PSTN/ISDN/PSPDN)
M900/M1800 MSC/SSP/IP is integrated with MSC, VLR and SSP/IP functions.
Figure 4-1 shows the interfaces related with M900/M1800 MSC/SSP/IP serving as
MSC/VLR/SSP.
4-1
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
LIC
SGSN
ISDN
ISDN
subscriber
BSS
SCP
GS
PSTN/ISDN
PSPDN
LICI
PRI
MSC/VLR/SSP
VLR
C/D/F
MSC
WS
HLR/AUC/EIR
Billing center
Connected Entity
MSC--BSC
BSSAP
MSC--VLR
Internal protocol
MSC--HLR
MAP
VLR--HLR
MAP
MSC--MSC
MAP, TUP/ISUP
MSC--EIR
MAP
VLR--VLR
MAP
MSC--PSTN/ISDN/PSPDN
TUP/ISUP/CAS
SSP--SCP
CAP
Gs
MSC--SGSN
BSSAP+
PRI
MSC--ISDN user
DSS1
4-2
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
Interface Name
Connected Entity
O&M Interface
MSC--WS
Internal protocol
LICI
MSC--LIC
Internal protocol/SOSM
Billing Interface
FTAM, FTP
4.2 A-interface
A-interface is the interface between MSC and BSC. It includes speech channel and
signaling channel. Speech and data are transmitted via the speech channel. The
signaling messages transmitted via the signaling channel are compliant with the
BSSAP of SS7. The MS management, BSS management, mobility management and
call processing are implemented at A-interface.
Two kinds of messages are transmitted over A-interface, namely, BSSMAP and DTAP
messages. BSSMAP messages are in charge of service flow control. They should be
processed by corresponding internal A-interface functional module. To DTAP
messages, A-interface is only a transport channel. DTAP messages are directly
transmitted to the radio channel at the BSS side. At the MSS side, they are transmitted
to corresponding functional processing unit. Therefore, DTAP messages are
transparent to A-interface.
4.3 C-interface
C-interface is the interface between MSC and HLR. Here, MAP protocol of SS7 is
adopted by the MSC, via which the Gateway Mobile Switching Center (GMSC) queries
the route information of the called MS from the HLR of the called subscriber in the
Mobile Terminated Call (MTC).
4.4 D-interface
D-interface refers to the interface between VLR and HLR. It exchanges the location
information and subscriber management information of the MS between HLR and VLR.
MAP protocol of the SS7 is used by the VLR at this interface for signaling transfer. And
the following functions are supported:
Authentication
Location update;
Subscriber data retrieval during call establishment.
Supplementary service
VLR restoration
4-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
During MS call setup, data are to be exchanged between VLR and HLR. For example,
VLR notifies HLR of the current location information of its mobile subscriber and HLR
sends all related service data of that MS to VLR. If MS moves to another VLR area,
HLR will delete the location information and service data of the MS in the previous VLR.
In addition, the modification request of the subscriber for the used services and the
modification on subscriber data by the operator require the exchange of data via
D-interface.
According to the MAP Phase2+ specification, D-interface is also used to transmit
CAMEL-related subscriber information from HLR to VLR. It is also used in the CAMEL
service to suppress the announcement so as to support intelligent services.
4.6 F-interface
F-interface is the interface between MSC and EIR. When MSC needs to check the
validity of IMEI (International Mobile Equipment Identity), it will exchange information
about IMEI with EIR via F-interface. MAP protocol in the SS7 is used to provide the
above function.
4.7 G-interface
G-interface is the interface between VLRs. The signaling interworking here is
implemented via the MAP protocol. Via this interface, the following functions are
accomplished.
4-4
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
Location update: When a mobile subscriber roams to a new VLR area, the new
VLR requests IMSI from the original VLR.
Authentication: The authentication triplet is sent from the original VLR to current
VLR.
4.8 Gs-interface
Gs interface is the interface between MSC and SGSN. BSSAP+ protocol of SS7 is
adopted here for signaling interworking. SGSN implements the mobility management
function on MS by cooperating with MSC through Gs interface, including attach/detach
and routing/location area update operations. SGSN also receives the circuit paging
information from MSC to page MS via PCU (Packet Control Unit). For Class-C MS,
services will not be affected whether the Gs interface is provided or not. For Class-A
and Class-B mobile stations, however, Gs interface is essential to the provision of
GSM/GPRS services. If Gs interface is not provided, Class-B MS will be degraded to
Class-C MS.
4.9 L-interface
L-interface is the interface between SSP and SCP. CAP protocol of SS7 is adopted
here for signaling interworking. SCP implements intelligent call connection by
controlling SSP via the L-interface.
4-5
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
The iGWB supports two bill collection modes, the active mode and the passive mode.
In the passive collection mode, the iGWB opens the directory item, user name and
password for the storage of bill files, and the Billing Center logs on to the iGWB to get
bills actively. In the active collection mode, the Billing Center opens the directory, user
name and password for the storage of bill files in the bill collector, and the iGWB will
automatically send the bill files to the bill collector.
The iGWB supports local and remote connections with the Billing Center. The Billing
Center can obtain bills from the iGWB via LAN or WAN by adopting the FTAM or FTP
protocol.
If FTP is adopted, the iGWB works as the Server of FTP in passive collection mode and
as the Client in active collection mode.
FTAM is the recommended protocol in the industry.
In passive collection mode, the iGWB works as the Responder of FTAM.
FTAM supports the following protocol stacks:
UTS-TCP protocol stack (FTAM over TCP/IP)
UTS-LAN protocol stack (FTAM over IEEE802.3)
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 4 External Interfaces
4.14 LICI
If the Lawful Interception Center (LIC) is the SPBX equipment provided by Huawei, the
interface adopts the protocol made by Huawei based on relevant interception
standards of GSM. The Lawful Interception Center Interface (LICI) includes three
interfaces, namely X1, X2 and X3. X1 is a control channel, transferring control
commands and relevant responses between LIC and MSC. X2 is a data channel, via
which the LICI system transmits the activity event reports and outputs the short
messages contents of the monitored subscriber in specified format, and outputs LICI
alarm information. X.25 or TCP/IP protocol is adopted for X1 and X2 interfaces. X3 is
used to output the session contents of the monitored subscriber in real time. It is a
digital interface with a rate of 2048kbit/s. And the interface parameters comply with
G.703 standard. The signaling mode of X3 interface is TUP or ISUP.
If M900/M1800 MSC/SSP/IP is used in the mobile networks of Commonwealth of
Independent States, where Control Point (CP) is used as the LIC, the SOSM protocol is
adopted for interface. In terms of function, there are still three interfaces between MSC
and CP. The difference lies in that the short messages sent and received by the
monitored subscriber and the alarm information of the CP are reported via the X1
interface.
For detailed information about LICI, refer to the M900/M1800 MSC/SSP/IP Lawful
Interception User Manual.
4-7
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
5-1
Technical Manual
M900/M1800 MSC/SSP/IP
z
System Description
Chapter 5 System Reliability
VLR: The distributed database storing the information of all the subscribers in its
serving area. Physically, it has two GVDPs (GSM Visitor Location Register Data
processor) working in active/ standby mode.
Shared Resource Module (SRM): SRM provides all kinds of shared resources
shared by M900/M1800 MSC/SSP/IP, including Dual-Tone Multi Frequency
Transceiver (DTMF), Multi-Frequency Compelled Transceiver (MFC), conference
(CONF) and signal tone (SIG) resources.
Line Interface Module (LIM): LIM provides line interfaces (E1 and SDH
optical/electrical interfaces) for the interconnection between M900/M1800
MSC/SSP/IP system and other network equipment. It is also responsible for the
interconnection among SRM, SPM and CNET.
Central Processing Module (CPM): CPM stores and handles system configuration
data and resource data.
Alarm box: The alarm box will generate visible and audible alarms in case of
system fault.
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
5-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
Note:
The heartbeat detection circuits are used for detecting whether the CPU of the board is in normal
operational state or not. The CPU regularly outputs impulses to the heartbeat detection circuits through a
universal I/O pin. If the board is normal, the CPU will output impulses. If any fault is detected or the CPU is
out of service, the CPU will output a fixed electrical level. Thus the validity of the board switchover
mechanism and the percentage of fault detection coverage are improved.
5-4
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
switching network and interface circuits, 70% of the faults can be located precisely to
individual board, 90% to 2 boards and 100% to 3 boards.
5-5
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
I. Switchover mechanism
In case of critical faults, the system resets and will start the switchover mechanism.
After restarting, the record of reset reason is output and relative materials can be
printed. For low-level reloading, the system interruption is no more than 30 seconds.
For level-4 reloading, the system interruption is no more than 3 minutes.
5-6
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
III. Isolation
Isolation means that when an entity fails to complete a function, services of this part will
be transferred to other entities for operations. The precondition for isolation is to check
whether a function can be enabled and whether the service transfer condition is
provided.
IV. Restart
For the board with single function, when it can not perform its main function, fault may
occur and then board will be restarted. For example, the main function of the BCC
board is to handle the communication of the same Service Processing Frame. If the
BCC can not perform bus control, BCC board will be restarted. If the GCPC board finds
that some channel can not be used for transmission, it will reset these channels. If all
links are faulty or the communication with the GSPC board fails, this GCPC board will
be reset.
5-7
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
case the load is reduced, the service level will be increased by one level. Alarm
information will be generated for each load control operation.
III. Flow control according to the amount of bills in the bill pool
A storage space is designed in the GSPC board for storing the original bills generated
during calls. The storage space is called the bill pool. Bills generated will be first
5-8
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
stored in the bill pool and then sent to iGWB (Charging Gateway), which implements
storage and backup of bills and sends bills to the Billing Center.
In abnormal cases (such as the temporary communication interruption between MSC
and iGWB), the system may not be able to send the bills in the bill pool to bill
administration unit in the real time. If no measure is taken in this case, the bill pool
might get overflow (bills can not be stored) and some bills get lost.
To avoid this situation, the M900/M1800 MSC/SSP/IP system is designed with the
hierarchical call-barring function. When the occupancy of the bill pool exceeds certain
limit, the system will generate alarms and start the hierarchical call barring function. In
case of bill pool full, all calls will be barred and no calls will be connected.
Monitoring the MAP operations sent from the signaling point. MSC can decide
whether to carry out the MAP operation according to the operation code, version
and SSN.
When MAP operation is rejected, MSC will report the detailed information of MAP
operation in the event alarm.
In this way, the network resources can be prevented from unauthorized use, and the
data can be protected against unauthorized modification. Thus, the operators and
subscribers' profits are protected.
This function can prevent the unauthorized use of the network resource, so that the
network security can be greatly enhanced.
5-9
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
board. Both the active and the standby GSPCs are configured with network ports. They
are connected to the active and standby iGWB servers via LAN switches respectively.
IV. Dual configuration of physical links (including network adapter and LAN
Switch) between MSC and iGWB
Both the active and the standby iGWB servers are configured with two network
adapters. They are connected to the active and standby GSPC boards via LAN
switches respectively. Both the active and the standby iGWB servers are connected to
the Billing Center and WSs via LAN switches respectively.
5-11
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
Bill data are saved in two separate Raid 5 disks. If one of them is damaged, no
charging data will be lost.
Redundant hard disk is placed in disk array. In normal conditions, the redundant
hard disk is not in use. In the case of damages occurred to a serving hard disk, the
redundant hard disk will automatically take over the job of the damaged disk.
5-12
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
5-13
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
BAM, O&M can be performed over the system through the emergency workstation,
thus preventing O&M inconvenience caused by the BAM failure.
The Emergency Workstation is connected to the BAM via the network. It synchronizes
the BAM server contents once at certain interval (4 hours by default). Once the BAM
server stops working due to faults, the emergency workstation might be immediately
started to exercise the BAM functions. The contents to be synchronized in the BAM
server may be set at the time of installing the server of the Emergency Workstation.
These contents mainly include data configuration files, system backup files, etc.
To cut the load of the BAM, the remote server program used for supporting the remote
dialup access is generally installed in the Emergency Workstation.
5-14
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 5 System Reliability
arrive at the remote maintenance proxy. Thus, the maintenance messages will be
protected from illegal modification. The remote maintenance proxy can also restrict the
IP address of the remote maintenance terminal, thus preventing illegal access.
5-15
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Index
6,000 k
48,000 Erl
1,024 links
0.8 Erl
307,200 MSU/s
Capacity of GT table
60,000
GT translation capability
46,080 GTT/s
Index
4,800 k
30,000 Erl
1,024 links
0.8 Erl
307,200 MSU/s
VLR capacity
1,000,000 subscribers
6-1
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Item
Index
Capacity of GT table
60,000 items
GT translation capability
46,080 GTT/s
Index
10,584
Index
Availability
0.99999513
102,600 hours
0.5 hours
0.04267 hours
At least 90% trunks can be used for incoming calls and outgoing calls.
6-2
Technical Manual
M900/M1800 MSC/SSP/IP
z
System Description
Chapter 6 Technical Indices
Board reliability
Method I Case I/II of Bellcore Reliability Prediction Procedure for Electronic Equipment
z
System reliability
Note:
The reliability prediction for units and system adopts RELEX software kits.
Resource
cabinet
Service
processing
cabinet
Integrated
Management
Cabinet
Interface
cabinet
X10 /h
GCKS
3,851
11,553
86,558
GCKD
2,494
7,481
133,672
GBAC
6,462
19,385
51,586
GFSN
8,321
24,963
40,059
GCPC
3,618
10,855
92,123
GCNU
7,062
21,187
47,199
GSNU
8,067
24,201
41,321
GBDR
746
2,238
446,828
6-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Reliability Indices
Name of Unit
GQSI
4,429
13,287
75,262
CDP
3,618
10,855
92,123
GE16
4,361
13,084
76,429
GETS
4,361
13,084
76,429
GPWS
4,332
4,332
230,840
NCC
3,618
10,855
92,123
AMP
3,618
10,855
92,123
IWC
3,000
24,000
41,667
IWF
3,000
24,000
41,667
BCP
3,618
10,855
92,123
GSPT
3,000
9,000
111,111
GSRC
3,000
9,000
111,111
GMHI
3,000
9,000
111,111
GVDP
3,000
9,000
111,111
GSPC
3,000
9,000
111,111
BCC
3,618
10,854
92,132
CNB
100
100
10,000,000
LPB
100
100
10,000,000
CKB
100
100
10,000,000
LIB
100
100
10,000,000
SRB
100
100
10,000,000
IWB
100
100
10,000,000
SPB
100
100
10,000,000
LAN Switch
100
Server
200,000
Inverter
100
Inverter
controller
(Availability is 0.9)
10,000,000
600,000
1,667
10,000,000
6-4
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Mean time to repair (MTTR) includes fault detection time, isolation time, unit replacing
time and recovery time. Field test proves MTTR=0.5 hour. The availability (A) of system
is:
A=
M TBF
M TBF + M TTR
102600
102600 + 0.5
= 0.99999513
6.1.3 Maintainability
Maintainability: the capability of recovering to specific status when the product is
maintained under specific condition and within specific time according to stated
procedure and method.
MTTR (Mean Time To Repair) is an important index that measures the maintainability of
product. With special techniques adopted (such as improved fault detection/isolation
rate, hot standby, optimized maintenance channel), M900/M1800 MSC/SSP/IP
enables MTTR to be less than 0.5 hour.
AMP board of M900/M1800 MSC/SSP/IP is responsible for centralized maintenance
over boards. AMP is connected to BAM to implement the functions such as board reset,
status query and version query.
In addition, M900/M1800 MSC/SSP/IP provides a serial port path (emergency serial
port line) between Central Processing Module (SPM) frame and other frames used for
reporting alarm information and maintaining the device in emergency. At present, it is
mainly used for reporting data of GPWS status and alarm data of GAMD. The Alarm
Box can provide audible and visible alarm information.
6-5
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Note:
There are some cabinets that may not be in full configuration when the system supports one million
subscribers, so the total power consumption of cabinets in full configuration is not e equal to the value
when the system supports one million subscribers.
CNET frame (one group of GSNU boards, 4 GPWS boards, other boards fully
configured) 370W. The power consumption will increase by 80W each time one
group of GSNU boards are added. The power consumption of the frame
configured with 7 groups of GSNU boards is 920W.
z
Power consumption of CCM frame (one group of GFSN boards) 140W. The power
consumption will increase by 40W each time one group of GFSN boards are
added.
The power consumption of the LIM frame fully configured with GE16 boards is
about 260W. When half of the frame is configure with GE16 boards, the power
consumption is 140W.
The power consumption of the LIM frame fully configured with GETS boards is
about 260W. When half of the frame is configure with GETS boards, the power
consumption is 140W.
The power consumption of LIM frame fully configured with GSTU is about 210W.
When half of the frame is configure with GSTU boards, the power consumption is
160W.
The power consumption of the LIM frame fully configured with GECP boards is
about 270W.
6-6
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
195W when fully configured with 2 GSPC boards, 16 GCPC boards and 2 GPWS
boards.
210W when fully configured with 4 GSPC boards, 14 GCPC boards and 2 GPWS
boards.
225W when fully configured with 6 GSPC boards, 10 GCPC boards and 2 GPWS
boards.
240W when fully configured with 8 GSPC boards, 6 GCPC boards and 2 GPWS
boards.
The power consumption of the LIM frame fully configured with GE16 boards is
about 260W. When half of the frame is configure with GE16 boards, the power
consumption is 140W.
The power consumption of the LIM frame fully configured with GETS boards is
about 260W. When half of the frame is configure with GETS boards, the power
consumption is 140W.
The power consumption of LIM frame fully configured with GSTU is about 210W.
When half of the frame is configure with GSTU boards, the power consumption is
160W.
6-7
Technical Manual
M900/M1800 MSC/SSP/IP
z
System Description
Chapter 6 Technical Indices
The power consumption of the LIM frame fully configured with GECP boards is
about 270W.
The power consumption of the SPM frame depends on the boards configured in the
frame.
z
195W when fully configured with 2 GSPC boards, 16 GCPC boards and 2 GPWS
boards.
210W when fully configured with 4 GSPC boards, 14 GCPC boards and 2 GPWS
boards.
225W when fully configured with 6 GSPC boards, 10 GCPC boards and 2 GPWS
boards.
240W when fully configured with 8 GSPC boards, 6 GCPC boards and 2 GPWS
boards.
6-8
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Item Name
Pull-in range
1
Clock
input
parameters
Stratum-2 clock:!4%10-7
Stratum-3 clock: !4.6%10-6
Stratum-2 clock: Can be synchronized with the
clock with accuracy of !4%10-7
Stratum-3 clock: Can be synchronized with the
clock with accuracy of !4.6%10-6
Maximum
frequency offset
Initial maximum
frequency offset
Ideal
status
operation
Long-term
phase variation
Stratum-2 clock:
a=0.5, b=1.16%10-5, c=1000
Stratum-3 clock:
a=10, b=2.3%10-4, c=1000
Clock operation
mode
Redundancy of
clock
There are two independent clocks with the same performance. If one
clock fails, the other can function immediately.
Clock
maintainability
Protective
switchover
frequency
reference
There are two input interfaces i.e. active interface and standby
interface of synchronization link for stratum-2 or stratum-3 clock.
After the active frequency reference is input, for the switching
equipment with stratum-2 clock, the clock switches to the holdover
operation mode automatically. For the switching equipment with
stratum-3 clock, the clock switches to the standby frequency
reference automatically, if the standby frequency reference fails too,
the clock switches to the holdover mode automatically.
Alarm function
of
Alarms can be generated when the clock system fails. Warning will
be given when the clock frequency deviates from phase-lock loop
adjustable range by three-quarters due to aging of the clock crystals.
6-9
Technical Manual
M900/M1800 MSC/SSP/IP
Serial No.
System Description
Chapter 6 Technical Indices
Item Name
Display function
Control function
10
Input
tolerance
jitter
Note:
Minimum accuracy: the long-term (20 years) maximum offset value compared with the nominal frequency,
when there is no external frequency reference (free-run).
Maximum frequency offset: the maximum value of relative clock frequency variation in the unit time during
a continuous process.
Pull-in range: the maximum frequency bandwidth of the input signal that can be locked by the clock.
MRTIE: the maximum peak- peak time delay change of a tested clock compared with an actual reference clock
during the test period.
Y(UI)
10 2
A 0 =36.9
10 1
Slope of 20Db/10 octave
A 1 =1.5
1
A 2 =0.2
10 -1
1.2 10 -5 10
20
2.4k
18 k 100 k
f (Hz)
Figure 6-2 Max. input jitter allowable and lower limit of wandering
Suppose the jitter frequency of an input signal is 1kHz, its range is over 1.5UI and the
system still works normally, then the input signal satisfies the requirements.
6-10
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Specification
Assembled cabinet
B68-21 cabinet
Assembled cabinet
B68-21 cabinet
The parameters of these components meet all related international standards such as
IEC801-2 15KV (Air Discharge), IEC801-4 40A(2.5kHz), IEC801-5 1.2/50" AC V" s 4KV
8/20" AC V" s 150A.
2)
Catching diode array is adopted at the logic side of the transformer to protect TPN3021
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Each optical channel provides eight 16.384Mbit/s (256 timeslots) traffic HWs and
two 2.048Mbit/s HWs (can be expanded to 4).
Note:
The following aspects should be noted in terms of the technical issues of STM-1 interface provided by
M900/M1800 MSC/SSP/IP:
1) It is necessary to firstly confirm the parameters of peer optical module when Interconnecting optical
ports. Light attenuator should be used to avoid damage of optical components when the transmitted
optical power of any side is larger than the receiving saturation power of the other side.
2) GSTU optical module adopts double-SC socket. The terminal of optical jumper connected with GSTU is
SC/PC, the other end is determined by the terminal type of connected device. The length of optical jumper
is determined by the distance between the connected devices.
3) Remote optical power should be tested to check whether it meets the requirement of minimum
sensitivity when direct optical transmission distance is longer than 15km.
4) SMB connector is used in GSTU electric interface. When it is connected with transmission equipment,
155M high-speed coaxial cable should be used. In addition, the coaxial electric cable should be no longer
than 70m. Before the connection, the voltage of the SMB connector shell (at 155M electric interface) and
that of the 155M electric interface shell of the transmission equipment should be measured. And the
voltage difference should be no larger than 2V. Otherwise, the grounding resistance of the
transmission/switching equipment should be decreased.
6-12
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
I. General principles
z
The switching system shall adopt joint grounding; the grounding cables of the
cabinets of the same module shall be securely jointed to form an equipotential
body.
For the select grounding, Huawei primary power supply and DC distribution
cabinet are ion of DC power supply and corollary equipment for recommended to
realize the overcurrent protection of DC power for each module and for reliability of
the grounding cable connection.
For AC distribution system, the user should provide a standalone AC safety GND
and disconnect the PGND offered by the AC power network. The use of power
lightning protection device can prevent interfering signals from the AC electrical
network and ensure the normal operation of the AC distribution system.
6-13
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
6.4.3 Cleanness
I. Operation environment
The
system
meets
the
requirements
"Temperature-controlled locations":
Falling dust
1.5 mg/m2h
Suspending dust
0.2 mg/m3
Sands
30 mg/m3
6-14
of
EUROPEAN
ETS
300
019-1-3
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
20 mg/m2h
Suspending dust
5.0 mg/m3
Sands
300 mg/m3
3.0 mg/m2h
Suspending dust
No requirements
Sands
100 mg/m3
6.4.4 Lighting
I. Operation environment
The
system
meets
the
requirements
of
EUROPEAN
ETS
300
019-1-3
6-15
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
system
meets
the
requirements
of
EUROPEAN
ETS
300
019-1-3
"Temperature-controlled locations":
Air pressure
70 ~106kPa
Wind speed
5.0m/s
Sulfur Dioxide
0.3~1.0 mg/m3
Hydrogen Sulfide
Cl2
HCl
NOx
NH3
HF
O3
70 ~106kPa
Wind speed
30 m/s
Sulfur Dioxide
0.3~1.0 mg/m3
Hydrogen Sulfide
Cl2
HCl
NOx
NH3
HF
O3
6-16
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
0 ~106kPa
Wind speed
20 m/s
Sulfur Dioxide
1.0 mg/m3
Hydrogen Sulfide
0.5 mg/m3
HCl
0.5 mg/m3
Nox
1.0 mg/m3
NH3
3.0 mg/m3
HF
0.03 mg/m3
O3
0.1 mg/m3
I. EMI indices
z
Frequency range
Average
Peak
79
66
79
60
73
6-17
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
0.02~0.50MHz
0.50~30MHz
Average
Peak
40~30
53~43
30
43
30~230
50
230~1000
67
Note:
The measurement point should be at a distance of 10 m from the switching equipment.
This index mainly aims at 48V DC power cable terminals and part of signal terminals
(tested only when the cable between ports exceeds 3m long)
Table 6-6 Conduction sensitivity indices
Port
Frequency range
Voltage class
Performance class
(AC/DC) port
3V
3V
Signal port
Frequency range
Voltage class
Performance class
80 MHz ~ 1 GHz
3 V/m
6-18
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
These indices are applicable to hands or other electrostatic sources affecting parts of
the product such as boards, frames, cabinet shell, etc.
Table 6-8 Electrostatic discharge indices
ESD mode
Air discharge
Voltage class
Performance class
4 kV
15 kV
6 kV
8 kV
Contact discharge
The EFT indices are mainly applicable to DC ports and partial signal ports (when the
line connecting the ports is over 3 m long).
Table 6-9 EFT indices
Port
Voltage class
Performance class
DC port
1 kV
Signal port
0.5 kV
Surge
The index mainly aims at DC power cable terminals and part of signal terminals (such
as indoor signal cable terminals and E1 terminals).
Table 6-10 Surge indices
Port
Signal
port
Voltage class
0.5 kV
6-19
Performance
class
C
Technical Manual
M900/M1800 MSC/SSP/IP
System Description
Chapter 6 Technical Indices
Note:
Performance class A: The M900/M1800 MSC/SSP/IP can withstand the test without being damaged and
can normally operate within the specific range without bringing any change to the software data or related
data (all data saved in the storage unit or data in process) of the measured switching equipment or
degrading the performance.
Performance class B: The M900/M1800 MSC/SSP/IP can withstand the test without being damaged.
There is no change to the software data or data saved in the storage unit. The communication
performance has somewhat decreased but the established communication links are not interrupted within
the tolerable range (depending on the product definition). After the test, the system can automatically
restore to the pre-test normal performance without any intervention from the operator.
Performance class C: The M900/M1800 MSC/SSP/IP functions are temporarily affected during the test
process but can be automatically restored to normal within a certain period after the test (generally the
shortest time needed for system restart). There should be no physical damage or deterioration of the
system operating software.
Performance class R: After the test, there should be no physical damage or fault (including software
damages) to the M900/M1800 MSC/SSP/IP. Damages to the protection device caused by external
interference signals are allowable. The equipment can operate normally after the protection device is
replaced and new operational parameters are set.
6-20
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
Hardware Architecture
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Table of Contents
Table of Contents
Chapter 1 General Introduction ................................................................................................... 1-1
1.1 Overview of Hardware Architecture ................................................................................... 1-1
1.2 Hardware Architecture Features........................................................................................ 1-3
1.2.1 Modular Design ....................................................................................................... 1-3
1.2.2 Dual Network and Dual Plane ................................................................................. 1-3
1.2.3 Resource Sharing and Centralized Management ................................................... 1-7
1.3 Functional Modules............................................................................................................ 1-7
Chapter 2 Cabinet.......................................................................................................................... 2-1
2.1 Physical Characteristics..................................................................................................... 2-1
2.1.1 Cabinet Type ........................................................................................................... 2-1
2.1.2 Design Features ...................................................................................................... 2-1
2.1.3 Cabinet Material ...................................................................................................... 2-1
2.1.4 Dimensions and Weight .......................................................................................... 2-1
2.1.5 Other Features ........................................................................................................ 2-2
2.1.6 Cabinet Installation.................................................................................................. 2-2
2.2 System Configuration ........................................................................................................ 2-2
2.2.1 Standard Configuration of M900/M1800 MSC/SSP/IP as VMSC ........................... 2-2
2.2.2 Compact Configuration of M900/M1800 MSC/SSP/IP............................................ 2-5
2.2.3 Configuration of M900/M1800 MSC/SSP/IP as GMSC .......................................... 2-6
2.2.4 Configuration of M900/M1800 MSC/SSP/IP with Lawful Interception Function ..... 2-7
2.3 Configuration of Functional Cabinets................................................................................. 2-8
2.3.1 Main Control Cabinet .............................................................................................. 2-8
2.3.2 Interface Cabinet................................................................................................... 2-10
2.3.3 SPM Cabinet ......................................................................................................... 2-13
2.3.4 Resource Cabinet ................................................................................................. 2-14
2.3.5 Integrated Management Cabinet........................................................................... 2-17
2.3.6 SPLIM Cabinet ...................................................................................................... 2-21
2.3.7 XPTU Cabinet ....................................................................................................... 2-22
Chapter 3 Frame ............................................................................................................................ 3-1
3.1 Physical Characteristics..................................................................................................... 3-1
3.2 Function and Configuration................................................................................................ 3-2
3.2.1 Clock Module (CKM) Frame.................................................................................... 3-2
3.2.2 Communication Control Module (CCM) Frame....................................................... 3-3
3.2.3 Central Processing Module (CPM) Frame .............................................................. 3-5
3.2.4 Central Switching Network (CNET) Frame ............................................................. 3-7
3.2.5 Line Interface Module (LIM) Frame....................................................................... 3-11
3.2.6 Service Processing Module (SPM) Frame............................................................ 3-18
i
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Table of Contents
ii
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
BITS
PSTN
GMSC
TMSC
VMSC
STP
HLR
BSC
SCP
CLK
CKM
IWF
CLK
E1
STM-1
E1
(2M Link)
CNET
LIM
393M HOFL
LAN/WAN
LIM
SRM
Billing center
iGWB
393M
HOFL
LAN/WAN
SPM
SPM
LAN
VDB
BAM
XPTU
OMC
LIC
CPM
CDB
HDLC
HDLC
HDLC
HDLC
HDLC
HDLC
CCM
1-1
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
LIM supports two types of external trunks interfaces, namely, STM-1 optical/electrical
interface and E1 interface. LIM separate the service data and the control data from
these external trunks and the other modules (IWF or SRM). The service data are
delivered by LIM to CNET for timeslot switching, while the control data are delivered to
CCM through the HDLC channels of the signaling HW.
CCM implements HDLC frame switching of the control data for inter-module
communication.
IWF frame is in charge of the data service communication between PLMN and other
networks (such as PSTN and ISDN). Each IWF frame is configured with two IWF units.
The IWF unit accomplishes Rate Adaptation (RA), Radio Link Protocol (RLP/L2R)
processing, Facsimile Adaptation (FA), etc. It interworks with other networks by
providing 3.1kHz audio PCM signal.
SPM processes various global services and Common Channel Signaling (CCS) links. It
supports the 64kbit/s signaling link. The service processing capability of the entire MSC
system can be improved by adding boards and expanding SPM capacity. The VLR
Database (VDB) is embedded in the SPM frame with plug-in board, which facilitates
smooth expansion according to users demands.
SRM-provided resources including call resources such as signal tones, dual tone
number transceiver, multi-frequency compelled number transceiver, and conference
call resources are globally shared resources. Trunk resources and echo cancellation
resources in LIM are also globally shared resources. All these resources can be
configured flexibly.
CDB in CPM manages and allocates the shared resources on a unified basis. In
addition, CPM maintains and manages the equipment of the entire system.
CKM implements the tracing and phase locking of external clock reference source or
the 8kHz clock signal extracted from the trunk by LIM, and generates 32 channels of
8kHz or 2MHz clock signals synchronized with the clock reference source. These clock
signals are transmitted to other modules via the separate clock signal lines to
implement the clock synchronization of the whole system.
BAM provides communication interface between the WS and SPM/CPM. It is in charge
of the equipment maintenance, data configuration, performance management and
alarm management, etc.
iGWB is responsible for bill management, and provides billing interface.
X Protocol Transfer Unit (XPTU) is in charge of the mutual translation between the
protocols used in X1/X2 interface for communicating with LIC and the internal protocols
used in M900/M1800 MSC/SSP/IP.
1-2
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
LIM
Voice
GE16/GSTU
E1/STM-1
G
Q
S
I
393M
HOFL
LIM
393M
HOFL
CNET
G
Q
S
I
E1/STM-1
GE16/GSTU
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
LIM
Common channel
signaling
G
Q
S
I
GE16/GSTU
E1/STM-1
393M
HOFL
LIM
393M
HOFL
semipermanent
connection
G
Q
S
I
SPM
GMHI
2M HW
GCPC
LIM
Call resource
E1/STM-1
GE16/GSTU
CNET
G
Q
S
I
393M
HOFL
LIM
393M
HOFL
CNET
G
Q
S
I
SRM
GMHI
8M HW
GSRC/GSPT
1-4
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
LIM
Circuit data
BSS
E1/STM-1
GE16/
GSTU
G
Q
S
I
LIM
PSTN/
ISDN
E1/STM-1
GE16/
GSTU
IWF
CNET
IWF
393M
HOFL
393M
HOFL
393M
HOFL
G
Q
S
I
CNET
393M
HOFL
I
W
C
2M HW
LIM
G
Q
S
I
GCDI
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
IWF
CNET
G
S
N
U
LIM
E1
GE16
STM-1
Serial
port Q
G
C
N
U
G
C
N
U
BUS
S
I
GSTU
I
Serial
W
port
C
IWF
GBDR
G
S
N
U
LIM
G
Q
S
I
BUS
NCC
HDLC
HDLC
Serial port
SRM
GCDI
Serial port
GSRC
GMHI
Traffic HW
HDLC
GSPT
CCM
HDLC
E1
HDLC
HDLC
SPM
HDLC
HDLC
Serial
port
CPM
G
H
N
7
G
S
P
C
G
V
D
P
G
C
P
C
B
C
C
BUS
BUS
B
C
P
C
D
P
A
M
P
C
D
P
Serial
port
G
A
L
M
CKM
G
C
K
S
LAN
BAM
iGWB
HDLC
Serial port
BUS
LAN
Traffic HW
1-6
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 1 General Introduction
Frame name
CKM
Clock frame
CCM
CPM
CNET
LIM
SRM
SPM
IWF
1-7
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
Chapter 2 Cabinet
This chapter gives a brief introduciton to the structure and characteristics of
M900/M1800 MSC/SSP/IP cabinets, and describes their typical configurations.
2-1
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
Width: 550mm
Depth: 40mm
Weight: 224kg (when empty), 310kg (in full configuration)
2-2
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
subscribers. And the demand for IWF channels is lower than 28. The recommended
configuration is shown in Figure 2-1.
DC distribution cabinet
IMM cabinet
Power distribution box
LAN Switch
Cable rack
LAN Switch
LIM cabinet
Fan box
Power distribution box
SPM cabinet
AM cabinet
SRM cabinet
Fan box
Power distribution box
Fan
box
Power distribution
box
SPM
LIM
Fan box
Power distribution
box
CNET
IWF
IWF
IWF
Dummy panel
Fiber rack
DC distribution cabinet
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
LIM
SPM
Fiber rack
LIM
SPM
Fiber rack
LIM
Inverter
Controller
Inverter
SPM
Fiber rack
Fan box
Fan box
Panel
CNET
SRM
Fiber rack
CPM
LIM
Fiber rack
CKM CCM
LIM
Fiber rack
Fan box
Fan box
2-3
Technical Manual
M900/M1800 MSC/SSP/IP
DC distribution cabinet
IMM cabinet
Power distribution box
LAN Switch
Cable rack
LAN Switch
Hardware Architecture
Chapter 2 Cabinet
LIM cabinet
Fan box
Power distribution box
LIM
SPM cabinet
AM cabinet
SRM cabinet
LIM cabinet
SPM cabinet
Fan box
Power distribution box
Fan box
Power distribution
box
Fan box
Power distribution box
Fan box
Power distribution box
IWF
LIM
Fan box
Power distribution
box
SPM
CNET
IWF
IWF
SPM
Dummy panel
Fiber rack
DC distribution cabinet
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
LIM
Fiber rack
LIM
Fiber rack
LIM
Inverter
Controller
Inverter
Fiber rack
Fan box
Panel
CNET
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Fiber rack
SRM
LIM
Fiber rack
Fiber rack
CPM
LIM
LIM
Fiber rack
CKM CCM
LIM
Fiber rack
Fan box
Fan box
Fiber rack
LIM
Fiber rack
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
2-4
Technical Manual
M900/M1800 MSC/SSP/IP
DC distribution cabinet
IMM cabinet
Hardware Architecture
Chapter 2 Cabinet
LIM cabinet
LAN Switch
Cable rack
LAN Switch
SPM cabinet
AM cabinet
Fan box
Fan
box
Power
distribution
box
SPM
LIM
LIM cabinet
SRM cabinet
Fan box
Power distribution box
Fan
box
box
Power
distribution
CNET
LIM cabinet
SPM cabinet
Fan box
Fan box
Fan box
LIM
IWF
IWF
SPM cabinet
Fan box
Power distribution box
IWF
SPM
LIM
Empty
Fiber rack
Dummy panel
Dummy Fiber rack
Fiber rack
DC distribution cabinet
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
LIM
SPM
Fiber rack
Panel
CNET
LIM
LIM
SPM
Inverter
Inverter
Controller
Fiber rack
Fan box
Fan box
LIM
SRM
Dummy Fiber rack
Fiber rack
Fiber rack
LIM
LIM
Fiber rack
Fiber rack
CKM CCM
LIM
LIM
Fan box
SPM
Fiber rack
Fiber rack
CPM
Dummy Fiber rack
Fiber rack
Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Fan box
LIM
Fiber rack
LIM
Fiber rack
LIM
Fiber rack
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
IMM cabinet
Power distribution box
LAN Switch
Cable rack
LAN Switch
AM cabinet
Fan box
Fan box
Power
distribution
box
SPM
CNET
IWF
SRM cabinet
Fan
box
box
Power
distribution
IWF
IWF
Dummy panel
Dummy Fiber rack
DC distribution cabinet
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
SPM
Dummy Fiber rack
LIM
Fiber rack
LIM
Inverter
Inverter
Controller
Fiber rack
Fan box
Panel
CNET
SRM
Fiber rack
CPM
LIM
Fiber rack
CKM CCM
LIM
Fiber rack
Fan box
Fan box
2-5
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
The capacity expansion of less than 200,000 subscribers can be realized by adding the
Service Processing and Line Interface Module (SPLIM) cabinet beside the SRM
cabinet. Figure 2-5 shows expanding to 800,000 subscribers by way of this
configuration.
DC distribution cabinet SPLIM cabinet
IMM cabinet
Power distribution box
LAN Switch
Cable rack
LAN Switch
SPLIM cabinet
SPLIM cabinet
SRM cabinet
Fan box
Fan box
Fan box
box
Power
distribution
SPM
SPM
SPM
Fan box
Fan box
Power
distribution
box
SPM
SPLIM cabinet
AM cabinet
Fan box
CNET
IWF
IWF
IWF
Dummy panel
Dummy Fiber rack
DC distribution cabinet
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
SPM
Dummy Fiber rack
LIM
Fiber rack
LIM
Controller
Inverter
Inverter
Fiber rack
Fan box
Panel
CNET
SRM
Fiber rack
CPM
LIM
Fiber rack
CKM CCM
LIM
Fiber rack
Fan box
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
LIM
LIM
LIM
Fiber rack
Fiber rack
Fiber rack
LIM
LIM
LIM
Fiber rack
Fiber rack
Fiber rack
Fan box
Fan box
Fan box
2-6
Technical Manual
M900/M1800 MSC/SSP/IP
IMM cabinet
Hardware Architecture
Chapter 2 Cabinet
DC distribution
LIM cabinet SPM cabinet
cabinet
AM cabinet
SRM cabinet
Fan box
Fan box
Fan
box
LAN Switch
Cable rack
LAN Switch
Power distribution
box
SPM
LIM
Fan
box
Power distribution
box
CNET
Fan box
Fan box
Fan box
SPM
LIM
SRM
IWF
Fan box
IWF
LIM
Empty
Dummy panel
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
Fiber rack
DC distribution
cabinet
BAM Server
LIM
Panel
CNET
SPM
Fiber rack
LIM
Fiber rack
LIM
SPM
Inverter
Fiber rack
Fiber rack
SPM
SPM
Fiber rack
LIM
Fiber rack
LIM
Fan box
Fan box
Fiber rack
LIM
LIM
Fiber rack
Fan box
Fiber rack
LIM
SPM
LIM
Fiber rack
Fan box
Fiber rack
LIM
CKM CCM
Fan box
CPM
LIM
SRM
Fiber rack
SPM
Fiber rack
Fiber rack
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
DC distribution
LIM cabinet SPM cabinet
cabinet
AM cabinet
Fan box
Fan box
Fan
box
LAN Switch
Cable rack
LAN Switch
Power distribution
box
LIM
SPM
CNET
IWF
Fan
box
Power distribution
box
Fan box
Fan box
LIM
IWF
IWF
SPM
Dummy panel
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
DC distribution
cabinet
XPTU cabinet
BAM Server
Inverter
Inverter
Controller
Fiber rack
LIM
Fiber rack
LIM
Fiber rack
LIM
Fiber rack
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Panel
CNET
LIM
SRM
Fiber rack
CPM
LIM
Fiber rack
CKM CCM
LIM
Fiber rack
LIM
Fiber rack
LIM
Fiber rack
Fan box
Fiber rack
Fiber rack
Fan box
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Figure 2-7 Configuration of M900/M1800 MSC/SSP/IP with lawful interception function for 800,000 subscribers
2-7
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
2-8
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
Cooling Fan
Power Distribution
G
P
W
S
0 1
G G G GG GG G G N
C C C CC CC C B C
N N N NN NN N D C
U U U UU UU U R
0 0 1 12 23 3
G
P
W
S
0 1
G
P
W
S
G
P
W
S
Frame 3
CNET
Frame 2
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
G
P
W
S
Frame 1
CPM
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
GG P
CC W
KK C
DD
G
C
K
S
G
P
W
S
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
C C CC B B
D D DD C C
P P PP P P
0 0 11
G
C
K
S
GA A
AMM
LP P
M
P
W
C
0 1
G
P
W
S
G
P
W
S
0 1
N GG G G G G GG G
C B C C C C C CC C
C DN N N N N NN N
RU U U U U UU U
4 4 5 5 6 67 7
G
P
W
S
G GG
F FF
S SS
N NN
GG GG G
BB FF F
AA SS S
CC NN N
G
P
W
S
Frame 0
CKM/CCM
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Cooling Fan
2-9
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
2-10
Technical Manual
M900/M1800 MSC/SSP/IP
G
P
W
S
G
S
T
U
G
G
PP
W
W
SS
0
0
1
1
G
G
PP
W
W
SS
0
0
1
1
G
P
W
S
Hardware Architecture
Chapter 2 Cabinet
G
Q
S
G
Q
S
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G G
E Q
1 S
6
I
6
5
7 8 9 10
6
7
8
G
E
1
6
G
E
1
6
6
5
7 8 9 10
6
7
8
G
E
1
6
G
S
T
U
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
10
11
11 12 13 14
9 10 11 12
G G
E Q
1 S
6
I
10
14
15
13
14
15
G G GG
Q E E E
S 1 1 1
6 6 6
I
11 12 13 14
9 10 11 12
13
11
13
14
G
P
W
S
G
S
T
U
G G GG
Q E E E
S 1 1 1
6 6 6
I
GG GG G G G G G
EE EE E E E E Q
CC CC C C C C S
PP PP P P P P
I
12
G
S
T
U
15
16
G
E
1
6
16
G
E
1
6
16
17
18
G
E
1
6
G
E
1
6
17
18
G
E
1
6
G
E
1
6
17
18
19
G
E
1
6
19
G
E
1
6
19
20
21
22
23
20
21
22
23
21
22
23
G GGG G G G G G
Q EEE E E E EE
S CCC C C C C C
PPP P P P PP
I
12
13
14
15
16
17
18
19
20
21
23
24 25
2-11
LIM
24 25
G
P
W
S
22
LIM
24 25
G
P
W
S
G
E
1
6
20
24 25
G
P
W
S
G
E
1
6
LIM
LIM
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
GG
W
W
Q
S
P
W
G GG
G
P E E
W T
1 1T
S S
6 6S
GG G G
P EE
W CC
S PP
10
11 12
13 14
15 16 17 18 19
20 21 22 23 24 25
G GG GG
GG G
G G G GG G G GG G G
E EE E E E Q
Q E E E E E EE E EE
G
P
1T T
1 T1 1T S
1 1T T
1 1T
1 1T 1T T1 T1 T
S T
1 T
6 6S
6 6S 6S S6 S6 S
I S
6 S
6S S
6 S6 6S
6 6S S
G GG GG GG
P E E E E E E
W T T T T T T
S S S S S S S
10
15 16 17 18 19
GG GG GG G
E E E E EE E
T T S
T T T T TT T
S S
S S S S SS S
10
11 12
13 14
15 16 17 18 19
G G GG G G
Q EEE E E
S C CC C C
I PPP P P
10
11 12
13 14
15 16 17 18 19
LIM
20 21 22 23 24 25
E E Q
CC C CCC S
PP P P P P I
13 14
GG G
GG G G GG G
EE E E E E Q
11 12
LIM
LIM
20 21 22 23 24 25
G GG
E EE
C CC
P PP
20 21 22 23 24 25
2-12
LIM
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
G
S
P
C
0
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
S
P
C
0
G
S
P
C
1
10
11
12
13
14
G
S
P
C
2
15
GBBG G
C CCC V
P CCP D
C
C P
0
1
G
S
P
C
1
G
S
P
C
1
GBBG G
H CCH S
N CCN P
7 C
7
0
1 2
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
G
S
P
C
0
G
S
P
C
1
G
S
P
C
0
G
S
P
C
0
G
G
P
P
W
W
S
S
G
S
P
C
0
10
11
12
13
14
17
G
V
D
P
15
16
18 19
G
C
P
C
7
17
G
S
P
C
3
20
GG
CC
PP
CC
65
18 19
20
GG
HH
NN
7 7
3 2
21
22
23
G
P
W
S
24
GG G
CC C
PP P
CC C
4 3 2
21
22
23
10
11
12
13
14
15
10
11
12
13
14
16
17
16
20
21
22
GGGGG
CCCCC
PPPPP
CCCCC
7 6 5 4 3
G
S
P
C
2
15
18 19
17
18 19
20
21
22
23
24
SPM
25
G
P
W
S
24
G
C
P
C
2
23
SPM
25
G
P
W
S
G B B G G G G G G GG G G G
C C C C CC C C C CC C C C
P CCP PP P P P PP P P P
C
C CC C C C CC C C C
0
1 1110 9 8 7 6 5 4 3 2
GBBG G
C CCC S
P CCP P
C
C C
0
1 2
16
G
S
P
C
3
SPM
25
G
P
W
S
24
25
2-13
SPM
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
2-14
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
G
G I I I I I I I I I I
P
P W WW WWW W WW W
W
W F F F F CC F F F F
S
S
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
P
W
S
GG GG G G G G
MM MM M M M M
HH HH H H H H
I I I I I I I I
11
12
13
14
15
16
17
18 19
20
21
22
23
24
10
11
12
G
Q
S
I
G
Q
S
I
10
11
12
11
13
G
Q
S
I
G
Q
S
I
10
13
12
13
14
15
16
17
18 19
20
21
22
23
15
16
17
18 19
20
21
22
23
15
16
17
18 19
20
21
25
24
22
23
24
LIM
25
G
P
W
S
G G GG G G G G
M M MM M M M M
H H HH HH H H
I I I I I I I I
14
SRM
G
P
W
S
G G GG G G G G
M M MM M M C C
H H HH HH D D
I I I I I I I I
14
24
IWF
25
G G G G G G G G G G G G G G G G G G G GG
S S S S S S S S S S S S S S S S S S S SS
P P P P P P P P P P P P R R R R R R R RR
T T T T T T T T T T T T C C C C C C C CC
GG GG G G G G
MM MM M M M M
HH HH H H H H
I I I I I I I I
10
I I I I I I I I I I G
W WW W W WW WW W P
F F F F C CF F F F W
S
LIM
25
2-15
Technical Manual
M900/M1800 MSC/SSP/IP
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
G
G
P
P
W
W
S
S
Hardware Architecture
Chapter 2 Cabinet
G
P
W
S
G
P
W
S
G G G G G G G G G G G G G G G G G G G GG
S S S S S S S S S S S S S S S S S S S SS
P P P P P P P P P P P P R R R R R R R RR
T T T T T T T T T T T T C C C C C C C CC
GG GG G G G G
MM MM M M M M
HH HH H H H H
I I I I I I I I
11
12
13
14
15
16
17
18 19
20
21
22
23
24
25
G G G G G G G G G G G G G G G G G G G GG
S S S S S S S S S S S S S S S S S S S SS
P P P P P P P P P P P P R R R R R R R RR
T T T T T T T T T T T T C C C C C C C CC
GG GG G G G G
MM MM M M M M
HH HH H H H H
I I I I I I I I
10
SRM
10
11
12
G
Q
S
I
G
Q
S
I
10
11
12
11
13
G
Q
S
I
G
Q
S
I
10
13
12
13
14
15
16
17
18 19
20
21
22
23
15
16
17
18 19
20
21
22
23
15
16
17
18 19
20
21
22
23
2-16
24
24
LIM
25
G
P
W
S
G G GG G G G G
M M MM M M M M
H H HH HH H H
I I I I I I I I
14
25
G
P
W
S
G G GG G G G G
M M MM M M M M
H H HH HH H H
I I I I I I I I
14
24
SRM
25
LIM
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
2-17
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
POWER
ON
OFF
SYN
INVERTER
FAULT
BATL/H
POWER
ON
FAULT
BATL/H
OFF
SYN
INVERTER
FAULT
BATL/H
ALARM
ON
OFF
Notes :
M900/M1800 MSC/SSP/IP provides two types of IMM cabinet. One is for DC power supply, the other is for
AC power supply.
The core of integrated management cabinet is BAM server and the iGateway bill
servers (iGWB). BAM server is the bridge for communication between MSC and OMC.
2-18
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
GSPCn
AMP
CDP1
CDP2
MSC
Active Stdby Active Stdby Active Stdby Active Stdby Active Stdby
......
LAN Switch
LAN Switch
Remote
maintenance WS
Serial part
heartbeat path
BAM Server
Emergency WS
x.25
DDN
iGWBServer
(Standby)
iGWBServer
(Active)
LAN Switch
Internet
Internet Gateway
Router
LAN Switch
Router
WS
WS
x.25
DDN
Router
Router
HUB
M2000
Server
Billing Center
RWS
RWS
Billing Center
2-19
Hub
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
GSPC, AMP and CDP boards of M900/M1800 MSC/SSP/IP are connected with two
Ethernet LAN switches via network cables. One LAN Switch is connected to all the
active boards and the other to all the standby boards.
The three servers, BAM and the active/standby iGWB servers are connected to both
LAN Switches through network cables.
These two LAN Switches themselves are also connected via network cables.
The O&M of MSC can be implemented in two ways: connected with WS via LAN switch
(local maintenance mode), or with M2000 via WAN (centralized maintenance mode). In
centralized maintenance mode, M2000 can be connected to other Huawei GSM
communication equipment (such as MSC and BSC) to attain centralized maintenance
over various equipment.
To lower the cost of OMC remote maintenance (as the cost of dial-up access through
Modem is quite high), M900/M1800 MSC/SSP/IP remote maintenance terminals can
access the network via the Internet. In this way, the data is no longer transmitted on
private toll lines; instead, they are transmitted via Internet.
The active and standby iGWB servers are connected to the Billing Center in two modes:
local connection and remote connection. They themselves are also connected through
the serial ports in standby heartbeat connection to help them keep track of the running
status of each other. Each of the servers has a disc array (non-sharing) to store the
bills.
OMC system also has a computer that functions as the emergency WS. This WS is
connected to the LAN Switch at client end and synchronizes data with BAM regularly.
When BAM server fails, connect the emergency WS via network cable to the LAN
Switch (shown as the dotted lines in Figure 2-16) which connects with the active board,
and change its IP address to that of BAM (172.20.200.200), then the WS can function
as BAM.
The emegency WS can also act as a dial-up server that performs remote maintenance
over the equipment.
Note:
iGWB servers adopt dual network and dual system working in hot backup to ensure the security and
reliability of bill management. To ensure normal communication between the two systems, it is required to
apply multiple heartbeat paths, each of which be of different priority. Not until a path of higher priority
interrupts will the heartbeat path of lower priority be activated. Normally, the two systems adopt two
heartbeat paths, the network interface and serial port, with the network interface usually of higher priority.
2-20
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
G
S
P
C
0
G
G
P
P
W
W
S
S
G
P
W
S
G
S
P
C
0
G
G
P
P
W
W
S
S
G
S
P
C
0
5 6
G
E
1
6
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
GG
EE
11
66
G
S
P
C
1
5 6
10
G
E
1
6
11
12
13 14 15
GBBG G
C CCC V
P CCP D
C P
C
1
0
G
S
P
C
1
GG G
EEE
1 1 1
6 6 6
GBBG G
C CCC S
P CCP P
C
C C
1 2
0
10
G
E
1
6
11
12
13 14 15
G
Q
S
I
G
Q
S
I
G
E
1
6
G
S
P
C
2
G
S
P
C
3
16 17 18 19
G
V
D
P
G
E
1
6
GG
CC
PP
CC
3 2
20 21 22
G GG
C CC
P PP
C CC
7 65
16 17 18 19
GG
EE
11
66
G
S
P
C
3
23
G
P
W
S
24
GGG
CCC
PPP
CCC
4 3 2
20 21 22
23
SPM
25
G
P
W
S
24
SPM
25
G
P
W
S
GGGG
EEEE
1 1 1 1
6 6 6 6
LIM
G
P
W
S
GG
EE
11
66
G
E
1
6
GG G
EEE
1 1 1
6 6 6
G
E
1
6
G
E
1
6
10
11
G
Q
S
I
10
12
13 14 15
G
Q
S
I
11
12
G
E
1
6
16 17 18 19
GG
EE
11
66
G
E
1
6
20 21 22
23
24
25
G
P
W
S
GGGG
EEEE
1 1 1 1
6 6 6 6
LIM
13 14 15
16 17 18 19
20 21 22
23
2-21
24
25
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 2 Cabinet
2-22
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
Chapter 3 Frame
This chapter gives a brief introduction to the structure of M900/M1800 MSC/SSP/IP
frames and a detailed introduction to their functional features and configurations. The
function and configuration of various boards are also described.
(10)
(5)
(9)
(8)
(6)
(7)
3-1
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
PG
W
P
C
W
S
G
C
K
S
G
C
K
S
G
C
K
D
G
C
K
D
P
W
C
10
11
3-2
12
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
AMP
AMD
8k0
8k31
2M0
2M31
8k0
8k31
2M0
2M31
-48V
Reference source
--48V
PWC
+5V
PWC
GCKS
8kHz
2.048MHz
2.048Mbit/s
GCKD
8kHz
2.048MHz
GCKD
CKM
Technical Manual
M900/M1800 MSC/SSP/IP
G
P
W
S
13
14
Hardware Architecture
Chapter 3 Frame
G
F
S
N
15
16
G
F
S
N
17
G
F
S
N
18
G
B
A
C
G
B
A
C
G
F
S
N
G
F
S
N
G
F
S
N
19
20
21
22
23
G
P
W
S
24
25
Note:
Each signaling HW has a transfer rate of 2.048Mbit/s. It can bear one or more HDLC channels, each of
which transmits signalings at the rate of n64kbit/s (n=1, 2, ..., 32). The total transfer rate of all HDLC
channels does not exceed 2.048Mbit/s.
3-4
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
Configuration buses
CCB
GPWS
GFSN
GFSN
GFSN
GBAC
GBAC
GFSN
GFSN
GFSN
GPWS
Switching buses
-48V
-48V
56 X 2M HW
8K, 2M
8K, 2M
Clock signaling Clock signaling
56 X 2M HW
G
G
P
P
W
W
S
S
1 2
G
P
W
S
C C CC B B
D D DD C C
P P PP P P
GA A
AMM
L P P
M
10 11 12 13 14
15 16 17 18 19 20 21 22 23 24 25
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
GPWS (Secondary Power Supply Board): Supplies +5V power for the boards. GPWSs
work in load-sharing mode. Maximum power consumption of a GPWS is 300W.
GALM (Alarm Board): Collects various power alarm and fan alarm, and forwards them
to the main control board AMP.
AMP (AM Processing Board): AM maintenance and equipment management centre,
who is in charge of board data configuration, equipment status information collection,
and module status broadcasting, etc.
AMP communicates with:
z
Boards equipped with HLDC links in other modules through HDLC links via CCM;
Boards such as GPWS and GAMD without HDLC links through serial ports via
GALM board;
AMP also receives the maintenance commands from OMC, processes AM-related
commands and transfers other commands. The two AMP boards work in
active/standby mode.
CDP (Central Database Processing) board: Manages trunk resources and various
shared global resources including: synchronous signal tones, dual tone number
receiver, dual tone number sender, MFC signal transceiver, echo canceller pool and
network interworking function resources.
CDP boards work in active/standy mode. M900/M1800 MSC/SSP/IP is usually
configured with two pairs of CDPs, one for trunk cable selection and the other for
shared resources management. CDP board function can be set dynamically at OMC.
BCP (Bus Control Processing) board: Controls CPM backplane, transfers message
packets between CDP and AMP boards, enables the bus communication of boards.
Packet transfer capacity of BCP board is 5000 packets per second.
Note:
AMP, CDP and BCP boards are all GCPC boards physically, but differ in their functions with different
softwares loaded.
3-6
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
Emergency serial port
CPM
-48V
Serial port
Serial
port
G
P
w
s
Emergency serial
port
Backplane bus
+5V
G
A
L
M
Serial
port
A
M
P
C
D
P
C
D
P
B
C
P
Serial
port
2MHz clock
8KHz clock
10M
LAN
TO CKM frame 2M Signaling
HW X 2
10M
LAN
2M Signaling
HW X 2
10M
LAN
2M Signaling
HW X 2
2M Signaling
HW X 2
3-7
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
GCNU0
15
FROM GQSI
4K single-T
network31#
QT
8K
single-T
network
15#
4K single-T
network31#
1 256TS
393Mbit/s
15
QT
256TS 1
15
QT
256TS 1
15
QT
256TS 1
15
QT
256TS 1
15
4K single-T
network30#
QT
4K single-T
network30#
1 256TS
4K single-T
network29#
15
4K single-T
network27#
QT
8K
single-T
network
14#
4K single-T
network29#
1 256TS
4K single-T
network27#
15
TO GQSI
256TS 1
QT
393Mbit/s
QT
GSNU7
GCNU7
GSNU7
1 256TS
15
15
QT
256TS 1
single-T
network
1#
4K single-T
network 3#
15
8K
4K single-T
network 3#
1 256TS
QT
32
256TS 1
16
4K single-T
network 2#
15
32
4K single-T
network 2#
1 256TS
QT
8K
single-T
network
0#
GSNU0
4K single-T
network 1#
15
4K single-T
network 1#
QT
16
1 256TS
FROM GQSI
256TS
15
QT
393Mbit/s
256TS 1
15
4K single-T
network 0#
QT
4K single-T
network 0#
1 256TS
GSNU0
393Mbit/s
15
QT
TO GQSI
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
16
32
48
64
80
96
112
128
G
G
P
P
W
W
S
S
1 2
G
G
P
P
W
W
S
S
G
C
N
U
0
G
C
N
U
0
G
C
N
U
1
GG
CC
NN
UU
1 2
G
P
W
S
1 2
GG
SS
NN
UU
0 0
G
C
N
U
2
G
S
N
U
1
G
C
N
U
3
GG
CB
ND
UR
3 0
G
S
N
U
1
10
N
C
C
0
N
C
C
0
GG
BC
DN
RU
0 4
G
C
N
U
4
G
C
N
U
5
GGG
CCC
NNN
UUU
5 6 6
GG
CC
NN
UU
7 7
G
P
W
S
11 12 13 14
15 16 17 18 19 20 21 22 23 24 25
GG
SS
NN
UU
22
GGGG
SSSS
NNNN
UUUU
3 3 4 4
GG
SS
NN
UU
5 5
11 12 13 14
10
G
S
N
U
6
G
S
N
U
6
GG
SS
NN
UU
7 7
G
P
W
S
G
P
W
S
15 16 17 18 19 20 21 22 23 24 25
3-9
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
The number of GPWSs depends on the number of GSNUs. Listed below is the
correspondence between the numbers of GSNUs and GPWSs:
z
GSNU 4, GPWS=4;
GSNU>12, GPWS=6.
The GPWS boards configured on the left and on the right are independent of each other,
and supply power respectively to the left and the right half of the CNET frame.
NCC (Network Communication Control) board: Manages and allocates the network
resources of CNET, and maintains and manages all the boards in CNET frame.
NCC boards work in active/standby mode. They drives the two control buses through
GBDR boards. Each bus is responsible for the communication between NCC and the
boards (GCNUs and GSNUs) in half of the CNET frame.
GBDR (Bus Drive Board): Facilitates NCC in controling the central switching network.
GBDR boards drive data buses, address buses and control buses controlled by NCC
boards, divides them into two groups: one used for communication between NCC and
network boards in the left half of CNET frame, and the other for communication
between NCC and network boards in the other half of the frame
GCNU (Central Switching Network Unit) board: Constitues the central switching
network of CNET and achieves level 2 switching. 8 pairs of GCNU boards shall be
configured regardless of the switching capacity of CNET.
GSNU (Skirt Switching Network Unit) board: Constitutes the skirt switching network of
CNET, performing switching of levels 1 and level 3.
Note:
NCC board is defined logically according to the actual function of the board. It is physically a GSPC board.
3-10
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
2M, 8k
Left clock
-48V
2Mbit/s X2
CCM
NCC
G
P
W
S
G
P
W
S
G
P
W
S
G
P
W
S
G
P
W
S
G
P
W
S
GBDR
Left-half frame bus
G
C
N
U
0
393Mbit/s X4
LIM
G
S
N
U
0
G
C
N
U
7
G
S
N
U
7
393Mbit/s X4
LIM
3-11
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
3-12
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
The configuration of LIM frame depends on the types of external interfaces, the number
of SRM frames, and the use of ECM frame functions. Figure 3-11 illustrates the LIM
frame fully configured with GE16 boards. Figure 3-12 illustrates the LIM frame fully
configured with GSTU boards. Figure 3-13 illustrates the LIM frame fully configured
with with GETS boards. Figure 3-14 illustrates the LIM frame fully configured with
GECP boards. And Figure 3-15 illustrates the LIM frame fully configured with GMHI
boards.Figure 3-16 shows the LIM frame that is half configured with GECS boards and
half with GE16 boards. Figure 3-17 shows the LIM frame configured with 7 pairs of
GMHI boards and 1 pair of GCDI boards.
G
G
PP
W
W
SS
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
Q
S
I
10
G
Q
S
I
11
12
13
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
14
15
16
17
18
19
20
21
G
P
W
S
22
23
24
25
G
G
PP
W
W
SS
G
S
T
U
G
Q
S
I
G
S
T
U
10
G
Q
S
I
11
12
G
S
T
U
13
14
G
S
T
U
15
16
17
18
G
P
W
S
19
20
21
22
23
24
25
G
G
PP
W
W
SS
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
Q
S
I
10
G
Q
S
I
11
12
13
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
G
E
T
S
14
15
16
17
18
3-13
G
E
T
S
19
G
E
T
S
20
G
P
W
S
G
E
T
S
21
22
23
24
25
Technical Manual
M900/M1800 MSC/SSP/IP
G
G
PP
W
W
SS
Hardware Architecture
Chapter 3 Frame
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
Q
S
I
G
Q
S
I
10
11
12
13
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
G
E
C
P
14
15
16
17
18
G
E
C
P
19
G
E
C
P
G
E
C
P
20
21
G
P
W
S
G
P
W
S
22
23
24
25
G
G
PP
W
W
SS
G
M
H
I
G G G G
M M M M
H H H H
I I I I
G
Q
S
I
G
Q
S
I
G G G
M M M
H H H
I I I
10
11
12
G
M
H
I
13
14
G G G G
M M M M
H H H H
I I I I
15
16
17
18
G
P
W
S
G G G
M M M
H H H
I I I
19
20
21
22
23
24
25
G
G
P
P
W
W
S
S
G
E
C
S
G
E
C
S
G
E
C
S
G
E
C
S
G
E
C
S
G
E
C
S
G
E
C
S
G
E
C
S
G
Q
S
I
10
G
Q
S
I
11
12
13
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
G
E
1
6
14
15
16
17
18
19
20
21
Figure 3-16 LIM frame half configured with GE16 and half with GECS
3-14
G
P
W
S
22
G
P
W
S
23
24
25
Technical Manual
M900/M1800 MSC/SSP/IP
G
G
PP
W
W
SS
Hardware Architecture
Chapter 3 Frame
G
M
H
I
G
M
H
I
G
M
H
I
G
M
H
I
G
M
H
I
G
M
H
I
G
M
H
I
G
M
H
I
G
Q
S
I
10
G
Q
S
I
11
12
13
G
M
H
I
G
M
H
I
G
M
H
I
14
15
16
G
P
W
S
G G G G G
M M M C C
H H H D D
I I I I I
17
18
19
20
21
22
23
24
25
Figure 3-17 LIM frame configured with 7 pairs of GMHI boards and 1 pair of GCDI boards
The functions of the boards are as follows:
GPWS (Secondary Power Supply bBoard): Supplies +5V power for the boards. The
maximum power consumption of a GPWS is 300W.
The power consumption of the LIM frame is great when fully configured with GSNU
boards. In this case, 4 GPWS boards are configured. In other cases, only two GPWS
boards are needed, working in 1+1 backup mode.
GE16 (16-port E1 Interface Board): Provides 16 E1 interfaces. It performs the HW
multiplexing and demultiplexing for the 16 external E1 signals and the 2 internal 16M
service HWs.
GETS (16-port E1/T1 Interface Board): Provides 16 E1/T1 interfaces. It performs the
HW multiplexing and demultiplexing of the 16 external E1/T1 signals and the 2 internal
16M service HWs. Meanwhile, GETS performs link layer protocol processing on the
digital signalings.
GSTU (SDH interface board): Provides one standard STM-1 optical interface. It
performs the transformation between one 155Mbit/s STM-1 optical signals and 8
internal 16M service HWs.
GECP (8-channel echo cancellation board): Provides EC-POOL, and performs echo
cancellation to 8 E1s through the network board.
GECS (16-channel echo cancellation trunk board): provides the echo cancellation
function on the basis of GE16 board. It cancels the signal echo while leading 16
channels of E1 signals into the MSC.
GMHI (Multi-HW Interface Board): Performs the transformation between the internal
16M traffic HWs and the external 2M/8M traffic HWs.
The 2M service HWs are used to transmit SS7 signalings, DSS1 signalings and R2
signalings. They are connected to the GCPC boards that are in charge of protocol
processing of the SPM frame.
3-15
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
The 8M service HWs are used to transmit the speech channel resources desired by the
resource channels, and provide HDLC links for data transmission between GMHI
boards and GSRC/GSPT boards. They are connected to the GSRC/GSPT boards in
the SRM frame.
The GMHI boards work in active/standby mode.
GCDI (Circuit Data-service Interface board): It performs the transformation between
the internal 16M traffic HWs and the external 2M traffic HWs. The 2M traffic HW is
connected with the IWC in IWF frame, transferring circuit data service. At the same
time, the GCDI communicates with the IWF frame via its internal communication serial
port. The GCDI boards work in active/standby mode.
GQSI (High-speed Signal Interface Board): Performs code rate conversion to the
internal 16M service HWs received from various service interface boards in the frame,
multiplexes them into two pairs of 393Mbit/s high-speed optical fibres, and transmits
them to the CNET. The 2M signaling HWs received from the service interface boards
will also be converged into 8 2M signaling HWs (4 for each plane) and transmitted to
the CNET.
Meanwhile, GQSI performs code rate conversion over the high-speed signals sent by
CNET, distributes the signaling data sent by the CCM, and sends the signals and data
to the service interface boards of the frame. GQSI board also performs management
and control over the service interface boards via the serial ports.
The functional blocks of LIM frame are shown in Figure 3-18.
3-16
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
LIM
16MHW 4
SLOT23
2MHW 2
16M , 8k
Clock signal
2MHW 4
CCM#0
2MHW 4
CCM#1
SLOT22
187.5k
Asynchronous
serial port
G
Q
S
GSNU
I
16MHW 4
SLOT3
2MHW 2
8K , 2M Clock
16M 8k
16M,
Clock signal
SLOT2
187.5k
Asynchronous
serial port
16M service HWs on the four backplanes to transfer service data (including the
speech, data, call resource and signaling) to the GQSI board,;
2M signaling HWs on the two backplanes to transfer to the GQSI boards the
control data sent to the service interface boards (e.g., the GSRC/GSPT board
control data sent to the GMHI board and the IWF frame control data sent to GCDI
board);
The GQSI board performs code rate conversion to the received 16M internal service
HWs, multiplexes them into two pairs of 393Mbit/s high-speed optical fibers and sends
them to the CNET.
3-17
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
GQSI also converges the received 2M signaling HWs, demultiplexes them together
with the board information received from the serial port and the internal signaling HWs
of the GQSI board into 8 2M signaling HWs (four on each plane), and sends them to the
CCM.
At transmitting side, GQSI performs the following functions:
z
Performing code rate conversion over the high-speed signals sent from the CNET,
and sending them to various service interface boards of the frame through the
service HWs
Distributing the external control data sent by the CCM to each service interface
board through the signaling HWs
Distributing the data of the GQSI board sent by the CCM to each service interface
board through the serial port.
The service interface board performs code rate conversion and signal adaptation over
the control data and signaling data received to form E1, STM-1 and external HW
signals, and sends them to other modules or equipment.
Note:
1) "Service Interface Board" refers to an interface board (other than GQSI) that is able to perform certain
service functions, including GE16, GSTU, GCDI, GMHI, GETS and GECP.
2) Because GE16, GSTU, GECP, GETS and GECS do not get control data from external signals, when a
LIM frame is configured only with the above boards, GQSI board will only transmit to CCM the control data
related to the frame. In this case, only two signaling HWs (one for each plane) are needed for GQSI-CCM
communication.
3-18
Technical Manual
M900/M1800 MSC/SSP/IP
G
S
P
C
0
G
G
P
P
W
W
S
S
Hardware Architecture
Chapter 3 Frame
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
G
C
P
C
0
B
C
C
0
B
C
C
0
G
C
P
C
1
G
C
P
C
11
G G
C C
P P
C C
10 9
G
C
P
C
8
G
C
P
C
7
G
C
P
C
6
G
C
P
C
5
G
C
P
C
4
G
C
P
C
3
G
C
P
C
2
10
11
12
13
14
15
17
18
19
20
21
22
23
16
G
P
W
S
24
25
Figure 3-19 SPM frame in full configuration (with 2 pairs of GSPC boards)
G
S
P
C
0
G
G
P
P
W
W
S
S
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
G
C
P
C
0
B
C
C
0
B
C
C
0
G
C
P
C
1
10
11
12
13
G
S
P
C
2
14
G
S
P
C
2
15
16
17
G
C
P
C
7
G
C
P
C
6
G
C
P
C
5
G
C
P
C
4
G
C
P
C
3
G
C
P
C
2
18
19
20
21
22
23
G
P
W
S
24
25
G
G
P
P
W
W
S
S
G
S
P
C
0
G
S
P
C
0
1 2
G
S
P
C
1
G
S
P
C
1
G
C
P
C
0
B
C
C
0
B
C
C
0
G
C
P
C
1
G
S
P
C
2
10 11 12 13 14
G
S
P
C
2
G
S
P
C
3
G
S
P
C
3
G
C
P
C
3
G
C
P
C
2
G
P
W
S
15 16 17 18 19 20 21 22 23 24 25
3-19
Technical Manual
M900/M1800 MSC/SSP/IP
0
25
G
S
P
C
0
G
S
P
C
0
G
G
P
P
W
W
S
S
Hardware Architecture
Chapter 3 Frame
G
S
P
C
1
G
S
P
C
1
G
C
P
C
0
10
B
C
C
0
11
B
C
C
0
G
V
D
P
0
G
C
P
C
1
12
13
14
15
16
G
C
P
C
6
G
C
P
C
7
G
V
D
P
0
17
18
G
C
P
C
5
G
C
P
C
4
19
20
G
C
P
C
2
G
C
P
C
3
21
22
G
P
W
S
23
24
Figure 3-22 SPM frame in full configuration (with 2 pairs of GSPCs and 1 pair of GVDPs)
If SPM frame is required to support 2Mbit/s high-speed signaling links, GHN7
(High-Speed SS7 Link Processing board) should be configured. The configuration is
similar with that of GSPC, as shown in Figure 3-23.
G
S
P
C
0
G
G
PP
W
W
SS
G
S
P
C
1
G
S
P
C
1
G
S
P
C
0
G
H
N
7
0
B
C
C
0
B
C
C
0
G
H
N
7
1
10
11
12
13
G
S
P
C
2
14
G
S
P
C
3
G
S
P
C
2
15
16
17
18
G
S
P
C
3
19
20
21
G
H
N
7
2
G
H
N
7
3
22
23
G
P
W
S
24
25
Figure 3-23 SPM frame in full configuration (with 4 pairs of GSPCs and 4 GHN7s)
The functions of the boards are as follows:
GPWS (Secondary Power Supply Board): Provides +5V power supply for the boards.
GPWS boards work in active/standby mode. Maximum power of a GPWS is 300W.
GSPC (Service Processing Board): Implements protocol processing of various layers
above the link layers of SS7 signaling, DSS1 signaling and R2 signaling, so as to
realizes the various services of the mobile switching system.
GCPC (Central Processing Board) :Implements the link layer protocol processing of
SS7 signaling, DSS1 signaling and R2 signaling. Each GCPC board processes 4
channels of SS7 signaling or 16 channels of PRA signaling. The signaling link rate
supported is 64kbit/s.
GHN7 (High-Speed SS7 Link Processing Board): Providing 2Mbit/s high-speed
signaling E1 interface, it processes the signals in 2Mbit/s signaling link layer. Each
GHN7 processes one 2Mbit/s signaling.
3-20
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
Note:
BCC board is defined logically according to the actual function of the board. It is physically GCPC.
SPM
-48 V
Emergency port
Backplane bus
+5 V
G
S
P
C
B
C
C
G
C
P
C
2MHz clock
8KHz clock
10 M
LAN
2M Signaling HW2
3-21
2M Signaling HW2
2M Service HW
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
G
G
PP
W
W
SS
G
P
W
S
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
P
T
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
G
S
R
C
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Note:
Slots 4~24 can be configured with either GSPT or GSRC boards.
3-22
25
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
GPWS (Secondary Power Supply Board): Provides +5V power supply for the boards.
GPWS boards work in load-sharing mode. Maximum power consumption of a GPWS is
300W.
GSPT (Special Voice Board): Provides the signal tone resources needed in call
connections. Each GSPT board provides in total 256 channels connected to the GMHI
boards via two 8Mbit/s HWs. The first 4 TSs of the 256 channels serve as HDLC links
for data transfer, and the other 252 for voice signals. The first 64 channels among the
252 channels of the first two GSPT boards are usually configured to transfer
asynchronous tones, while the others synchronous tones. For other GSPT boards, all
the channels are used to transfer synchronous tones.
GSPT board tones can be loaded online. 8192 pieces of tones can be retrieved. The
maximum recording duration totals as long as 130 minutes.
The GSRC provides Dual-Tone Receiver (DTR), Dual-Tone Sender (DTMF-S),
Multi-Frequency Compelled (MFC) Transceiver and conference (CONF) resources.
Each GSRC provides four DSPs that are independent of each other and can be loaded
with different DSP programs to provide different resources. Each DSP provides 64
resource channels. Therefore, each GSRC board provides 256 channels connected to
the GMHI boards through two 8Mbit/s HWs. Among these 256 channels, 4 timeslot
channels serve as HDLC links for control data transfer, and the others for resource
signals transfer. When M900/M1800 MSC/SSP/IP serves as GMSC, tone number
sender resources are not configured.
In the SRM frame, the resource boards work independently of one another, and
perform the management and allocation of the resource channels with the help of CDB.
3-23
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
G
G I I I I I I I I I I
PP W W W W W W W W W W
W
W F F F F C C F F F F
SS
10
11
I I I I I I I I I I
W W W W W W W WW W
F F F F C C F F F F
12
13
14
15
16
17
18
19
20
21
22
23
G
P
W
S
24
25
AMD
Serial port
Secondary power supply alarm
-48V
GCDI
Serial port
2MHW2
2MHW2
IWF frame
+5V
GPWS
IWC
2MHW2
IWC
2MHW2
Serial Serial
port
port
I
W
F
0
I
W
F
7
3-24
2MHW2
2MHW2
Serial Serial
port
port
I
W
F
8
I
W
F
15
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 3 Frame
One IWF frame is configured with two IWF units, each of which consists of 1 pairs of
IWCs and 8 IWF boards. The IWC evenly allocates one 2M HW from GCDI to 8 IWF
boards. Each IWF board performs interworking process of the two channels of the 4
timeslots allocated, and then sends them back to IWC. The IWC converges the HWs
from the 8 IWF boards into one, and sends it to the switching network via GCDI and
GQSI.
The GCDI communicates with the IWC/IWF boards in IWF frame via serial port in
master-slave node mode. Among them, the communication with IWF should be
transferred via IWC.
The GPWS in IWF frame is different from those in other frames. Its secondary power
supply alarm is collected via secondary power cable by the AMD in the cabinet, where
the IWF frame is located.
Note:
1. In an IWF unit, each IWF board processes only the first two channels of the 4 timeslots allocated by IWC,
i.e. the timeslots 0, 1, 4, 5, 8, 9, 12, 13, 16, 17, 20, 21, 24, 25, 28 and 29 of a HW. Since timeslots 0 and 16
do not transfer service, one IWF unit can process 14 IWF channels only.
2. When M900/M1800 MSC/SSP/IP serves as GMSC, IWF frame need not be configured.
3-25
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 4 Board
Chapter 4 Board
This chapter gives a brief introduction to the structure and common characteristics of
M900/M1800 MSC/SSP/IP boards.
Each board is built with advanced integrated circuits, such as ASIC, EPLD and
FPGA, which features high integrity and reliability.
All the boards follow unified hardware design regulations and mature existing
circuit design techniques.
Boards have built-in Watchdog that can automatically reset boards in case of
severe problems.
4-1
Technical Manual
M900/M1800 MSC/SSP/IP
(1) Indicator
(4) Handle
Hardware Architecture
Chapter 4 Board
(2) Panel
(5) Board name
4-2
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 4 Board
RUN
FAIL
(1)
(2)
1 2 3 4
ON
(3)
4-3
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 5 Power Supply System
5.1 Structure
M900/M1800 MSC/SSP/IP adopts a multi-level distributed feed system, as shown in
GND
PGND
DC power supply
-48V
DC power system
AC power supply
Figure 5-1.
-48V
GND
PGND
Frame 1
Frame 2
Frame 3
-48V
GND
PGND
Power distribution
box of cabinet n1
Frame 4
Busbar
5-1
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 5 Power Supply System
The line voltage wavelength distortion rate of the diesel engine generator group
usually should be less than 5%, and in any case should not exceed 10%.
Stabilize the voltage to ensure that the switching equipment works steadily.
Storage energy: when the mains supply fails, the storage battery can supply
power for a period of time so that system service will not be interrupted.
Filter noise and prevent mains frequency from interfering the system.
Voltage at
each
battery
terminal
Mains supply
state
Charge/discharg
e storage battery
DC voltage value
When the
mains supply
is normal
Floating charge
the storage
battery by a
rectifier
Floating charge
voltage 53.5V
2.23V
When the
mains supply
is off
Discharge
batteries
Discharge voltage
43.2V
1.8V
Automatically
charging the
storage battery
(loaded)at 10
ampere hour
When the
charging voltage
reaches 56.4V,
constant voltage
charging starts
(the charge status
is changed into
floating charge
automatically)
DC -48V
When the
mains supply
is on again
5-2
Number of
batteries in
each group
24
2.35V
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 5 Power Supply System
Multiple rectifiers can work in parallel, with flow equalization devices between
them.
The output voltage of a rectifier should satisfy the initial charging requirements of
storage battery, namely, 2.35 % 24=56.4V in case of DC-48V.
The rectifier efficiency should be more than 85% and the power coefficient more
than 0.8.
The rectifier is designed with natural cooling feature and can work continuously in
o
The output noise voltage (value measured by the noise meter plus weighted
network) of a rectifier should satisfy the requirements shown in Table 5-2.
Index
-48V
-40V~-57V
Noise voltage
0~300Hz
300~3400Hz
3.4kHz~150kHz
Effective value of
single frequency
5mV
150kHz~200kHz
Effective value of
single frequency
3mV
200kHz~500kHz
Effective value of
single frequency
2mV
Effective value of
broadband 100mV
Effective value of
150kHz~30MHz
30mV
Effective value of
single frequency
1mV
500kHz~30MHz
5-3
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 5 Power Supply System
1000 V
.
100 V
10V
1V
0.1 V
A
0.1
s 1
10
100
s 1000
5-4
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 5 Power Supply System
5-5
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 6 Clock Synchronization System
6.1 Overview
M900/M1800 MSC/SSP/IP clock synchronization system adopts digital phase-locked
loop and reliable software phase lock mode, which ensures the synchronization of the
system clock with that of upper level. The clock synchronization system has the
following features:
z
There are several stratums of clocks available, such as international stratum 2 and
stratum 3 (including Class A and Class B) and Building Integrated Timing Supply
(BITS) system. The indices of M900/M1800 MSC/SSP/IP clock synchronization
system are up to or superior than corresponding international standards, and can
satisfy the requirements of such exchanges as GMSC, TMSC, VMSC, etc.
Two phase-lock modes (PDH and SDH) are available. In SDH mode, the clock
system can reliably lock timing signals (pointer adjustment as high as 153) which
take SDH transmission system as inter-exchange timing transmission link. The
clock signals will be "purified" to ensure the service quality. When the quality of
timing signals transmitted between exchanges is satisfactory, PDH mode can be
adopted.
Powerful software function is provided. The clock system provides status display,
alarm, and operation & maintenance system. Internal parameters of the clock can
be set directly via the OMC.
GE16/
GECS
GETS
GSTU
8k Clock
8k Clock
CC
KK
MM
8k0, 2M0
8k31, 2M31
Other modules
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 6 Clock Synchronization System
Note:
Currently, only the 32 channels of 2MHz signal is used as the synchronous signal among modules.
6-2
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 6 Clock Synchronization System
WS
LAN
BAM
LAN
AMP
Serial port
GCKS
WS: WorkStation
AMP: AM Processing Board
LAN: Ethernet
BAM: Back Administration Module
6-3
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 6 Clock Synchronization System
Note:
8k0
8k31
2M0
2M31
8k0
8k31
2M0
2M31
Currently, only the 32 channels of 2MHz signal is used as the synchronous signal among modules.
8K0
8K1
2MB0
2MB1
GCKS
GCKD
GCKD
2M0
2M1
8kHz
2.048MHz
CKM
DT8K clock extracted from the trunk, used when synchonization with the
upper-level exchange is necessary.
2MHz and 2Mbit/s clock signals from other devices (e.g. BITS).
Technical Manual
M900/M1800 MSC/SSP/IP
Hardware Architecture
Chapter 6 Clock Synchronization System
6-5
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
Software Architecture
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Table of Contents
Table of Contents
Chapter 1 Overview ....................................................................................................................... 1-1
1.1 Architecture and Functions ................................................................................................ 1-1
1.1.1 Overall Architecture................................................................................................. 1-1
1.1.2 Functions................................................................................................................. 1-2
1.2 Features............................................................................................................................. 1-4
1.2.1 Features of Host Software ...................................................................................... 1-4
1.2.2 Features of OMC Software..................................................................................... 1-5
Chapter 2 Host Software............................................................................................................... 2-1
2.1 General Structure............................................................................................................... 2-1
2.2 Operating System .............................................................................................................. 2-2
2.3 Communication Mode........................................................................................................ 2-3
2.3.1 HDLC Link Communication..................................................................................... 2-4
2.3.2 Bus Communication ................................................................................................ 2-4
2.3.3 Serial Port Communication ..................................................................................... 2-4
2.3.4 TCP/IP Communication........................................................................................... 2-4
2.4 Data Management ............................................................................................................. 2-5
2.4.1 Database Structure ................................................................................................. 2-5
2.4.2 Central Database, Controlling Database and SPM Database ................................ 2-7
2.4.3 VLR Database ......................................................................................................... 2-8
2.5 Resource Management ..................................................................................................... 2-9
2.5.1 Types of Shared Resources.................................................................................. 2-10
2.5.2 Resource Management Task ................................................................................ 2-10
2.6 Equipment Management.................................................................................................. 2-11
2.7 Switching Network Management ..................................................................................... 2-12
2.7.1 Software Modules Related with Switching Network Operation............................. 2-12
2.7.2 Functions of Switching Network Control Module .................................................. 2-12
2.8 Call Control ...................................................................................................................... 2-14
2.9 Signaling Processing ....................................................................................................... 2-15
Chapter 3 OMC Software .............................................................................................................. 3-1
3.1 General Structure............................................................................................................... 3-1
3.2 BAM Software .................................................................................................................... 3-2
3.2.1 Functions of BAM Software..................................................................................... 3-2
3.2.2 Features of BAM Software ...................................................................................... 3-3
3.2.3 Structure of BAM Software...................................................................................... 3-4
3.3 O&M Terminal Software .................................................................................................... 3-6
3.3.1 Service Maintenance System.................................................................................. 3-6
3.3.2 Alarm Console......................................................................................................... 3-7
i
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Table of Contents
ii
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 1 Overview
Chapter 1 Overview
This chapter introduces the software structure of M900/M1800 MSC/SSP/IP and
functions of each part.
Foreground (MSC)
Background (OMC)
Local
Maintenance
system
iManager M2000
Mobile network management
system
Host software
iGWB software
1-1
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 1 Overview
1.1.2 Functions
I. Host software
The Host software controls the hardware resources of the MSC, performs signaling
processing and call handling, etc. It comprises the following parts:
z
This module is responsible for the status management of various boards and the
communication between the Host software and OMC software. It is the hub of the
whole system. AMP is directly connected with BAM through 10M/100M Ethernet
interface.
z
This module is responsible for the application and release of global resources and
shared resources. It also performs such functions as trunk selecting, signal tone
resources management, dual-tone receiver/sender resources management, MFC
resource management, echo cancellation pool resource management, and data traffic
channel management.
Two CDP boards form a pair, working in active/standby mode. The MSC can be
equipped with max. 7 pairs of CDP boards (usually 2 pairs are configured) to complete
different tasks. One pair performs trunk selection, and the remaining pairs manage
other resources.
z
This module controls the whole CNET frame, and performs time slot allocation, online
operation, and the communication with other modules.
z
Being called VLR module, it is used to store the information of subscribers in the local
MSC. The information is useful to call connection, routing, provision of basic and
supplementary services as well as mobility management. This module is only used in
M900/M1800 MSC/SSP/IP serving as VMSC.
Two GVDP boards form a pair, working in active/standby mode. Each pair of GVDP
boards can store the information of 250,000 subscribers. CDP is responsible for the
1-2
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 1 Overview
dynamic distribution of subscriber data on various GVDPs. When one pair of GVDPs
fails, the other GVDPs will store the subscriber data and perform relevant processing.
BAM software
As the Client of the Client/Server structure, the O&M terminal software operates on WS
connected with BAM. It is a graphic display terminal based on MML, and is easy to use.
The following maintenance functions can be achieved through the O&M terminal:
operation and maintenance, equipment management, signaling and interface tracing,
data configuration, alarm management, traffic measurement management.
z
It includes two software tools: the communication gateway at BAM and iGate. Running
on BAM or WS connecting with alarm box, the communication gateway at BAM
accomplishes the protocol conversion between BAM software and alarm box protocol.
Running on the remote access server, the iGate enables the communication between
remote maintenance terminal and BAM.
1-3
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 1 Overview
the basic information for charging subscribers. The iGWB also provides the charging
interface (supporting FTP protocol or FTAM protocol) to the Billing Center.
The software also provides Web interface, i.e., through Web browser on any WS, users
can view, query and backup bills, and can monitor some of the operation status (such
as disk space and bill server switchover) of the bill administration unit.
1.2 Features
1.2.1 Features of Host Software
Features of M900/M1800 MSC/SSP/IP Host software include:
z
Built-in real-time multi-task PSOS operating system ensures reliable and efficient
task dispatching, message management, timer management and memory
management.
Critical parts (such as AMP, NCC, CDP and GSPC) work in hot standby mode,
and corresponding software supports hot standby and immediate switchover. This
ensures normal service processing and system reliability in case of failure of some
parts.
The software supports the use of Flash memory device to permanently store the
program and static data. The recovery time is less than 3 minutes without the need
of reloading.
The software can be either loaded or firmed on the system. Online patching allows
patch loading, activation, and emergency switchback operations during system
operating, which minimizes upgrading risk.
1-4
Technical Manual
M900/M1800 MSC/SSP/IP
z
Software Architecture
Chapter 1 Overview
Both charging system and O&M system adopts Client/Server structure. BAM and
iGWB are both carrier-level servers. The Server and Client respectively run
Windows NT and Windows 95/98. They use C++ Language as the programming
language, and adopt such advanced techniques as Object-Oriented Program
(OOP) design, distributed management and multi-window visual display.
It supports the local or remote maintenance of MSC via local maintenance system,
and centralized management of the overall GSM equipment of Huawei via M2000.
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Service
Service
Service
Service
Service
Communication
Communication
Communication
Communication
Communication
System support
System support
System support
System support
System support
NCC
GSPC
GVDP
CDP
AMP
Resource
Background (OMC)
Maintenance
Interface
Equipment
management
Subscriber
database proxy
management
Subscriber
Data
management
System
Support layer
Call
control
Signaling
process
Switching
Function
layer
Network control
Foreground (host)
OMC
software
BAM, iGWB, WS
2-1
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Which are referred to in general as the service processing module and is the core in
realizing various services of the mobile switch. The call control module is classified into
ordinary call control module and intelligent call control module. Serving the call control
module, the signaling processing module coordinates with the software module in
GCPC to process SS7 signaling, DSS1 signaling and Channel Associated Signaling
(CAS).
GVDP board is equipped with subscriber data management module, which forms the
distributed-database storing subscriber information.
CDP board is equipped with resources management module and subscriber database
proxy module, managing the resources shared by the whole system, such as trunks,
signal tones, dual tone number transceivers, multi-frequency compelled transceivers,
echo cancellation pool and data service channels.
AMP board is equipped with equipment management module and maintenance
interface, which can obtain and record the status of boards and their interfaces, and
inform the corresponding serving layer and service layer of the changes. AMP board
provides maintenance interface to BAM.
2-2
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
operation through the recovery fault tolerance process. This kind of task is given the
highest priority.
The operating system of M900/M1800 MSC/SSP/IP Host is a real-time system in the
embedded application environment. It provides the following functions:
z
Program loading: To load program & data from OMC terminal or BAM onto GMPU
and boot the system.
Task dispatch: To dispatch tasks by priority and allocate related resources (the
processor and memory) in a multi-task real-time system.
Clock management: Manages the system time, including date, time, day, week,
hour, minute and second.
System load control: The operating system monitors the processor load in real
time. When the load reaches the preset upper limit, overload control will initiate to
stop some tasks of lower priority temporarily to relieve the processor load. When
the load drops to the preset lower limit, the overload control will be active. By
setting the upper & lower (overload and release) thresholds, system load is
smoothed and the Quality of Service is ensured.
System fault tolerance: When operating system finds any abnormalities in system
operations and task executions, such as addressing overflow, dead program loop,
memory or processor fault, then it will take measures to restore the system to
normal operating condition.
2-3
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
2-4
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Central Database
This database is in CDP board. It keeps the status information of shared channels and
all trunk circuits, and provides information for routing and resources selection in the call
control process.
z
Controlling Database
SPM Database
Located in GSPC board, this database keeps GSM service data, intelligent service data,
signaling data, charging data and hardware configuration information, and office data
and global link data. GSPC board also keeps the trunk circuit status and number
analysis route data of this module, enabling intra-module routing when the module is
isolated.
z
Subscriber Database
The location information, basic data and related service data of subscribers are stored
on GVDP board. The data in this database will update in accordance with the move of
subscribers.
2-5
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
2-6
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
I. Data dictionary
The relational table structure is described by the data dictionary, which itself is a
relational table and comprises two tables: table description table and field description
table.
The table description table mainly describes the information of each data table. The
field description table defines each field in the relational table.
Direct index table: The table is directly accessed via the tuple number. But the
tuple number is not a part of the relational table. Insertion and deletion of tuples
will not affect the sorting of the table.
Sequential search table: All tuples in the table are stored in sequence. The search
starts from the first tuple and continues in sequence. Newly added tuples are
placed at the end of the table.
Sorting table: Tuples in the relational table are sorted according to the key word
values. Two tuples with the same sorting fields (key fields) are not allowed in the
same table. Each key field can specify a sorting mode (ascending or descending)
and sorting number. Tuples with small sorting numbers are sorted first. The sorting
table adopts binary search mode. Insertion and deletion of tuples will result in the
displacement of subsequent tuples.
2-7
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
I. Basic functions
The VLR in M900/M1800 MSC/SSP/IP system offers the following functions:
z
Storing subscriber data. The subscriber data stored include IMSI, MSISDN,
location area, HLR address, subscriber type, subscriber status, subscribed
services, etc. In addition, authentication and encryption data are also stored here.
Retrieving subscriber data. During the call setup, VLR provides subscriber
information to MSC upon its request according to IMSI, TMSI or MSRN. In general,
when the MS is the calling party, IMSI or TMSI is referred. When the MS is the
called party, MSRN is referred.
Allocating MSRN. When the MS is the called party, VLR can flexibly allocate
MSRN according to its current location area and number segment.
Allocating handover number (HON). VLR provides HON to MSC during inter-MSC
handover and releases HON after the new call is set up.
Allocating TMSI. VLR supports the encryption of TMSI and the reallocation of
TMSI in each location update and call setup.
Technical Manual
M900/M1800 MSC/SSP/IP
z
Software Architecture
Chapter 2 Host Software
Purging MS. VLR actively deletes relative data of a mobile subscriber and informs
HLR of the deletion when the MS has made no connection with the network within
the specified period.
Restoring VLR data. Upon restarting, VLR deletes all the IMSI record and TMSI
number of the affected users. When the VLR receives the MSRN allocation and
location update requests, it will start the data restoration process.
Hot standby and real-time switchover are adopted for all parts of it, ensuring high
reliability.
Real time backup of subscriber data and automatic switchover of database. When
a subscriber is updating his location or modifying data, the subscriber data will be
backed up automatically in real time, and the active/standby databases are kept
consistent. If the active database is faulty, system can switch over to the standby
database without interrupting the services.
2-9
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Trunk circuits: The global shared trunk circuit resources mainly include
TUP/ISUP/CAS trunk circuits.
Note:
1) Each GSRC board has four resource units, each with 64 channels (of which the first four channels of the
first one unit are used for communications, instead of serving as resource channels). One resource unit
may be DTR, DTMF_S, MFC or conference call unit. The DTR, DTMF_S and MFC resources are
managed by CDP board, and conference call resource is managed by NCC board.
2) GSPT board has two types of resources, divided into asynchronous signal tone channel and
synchronous signal tone channel. The asynchronous signal tone is managed by NCC board while
synchronous signal tone is managed by CDP board. Each GSPT board has 252 resource channels in total,
of which the first 64 can be set as asynchronous signal tone channels.
3) Each GECP board has 8 resource units, each with 32 channels and independent faulty/normal status.
4) Each IWF board provides two channels, each of which has independent faulty/normal status. The CDP
board is in charge of IWF channel management.
2-10
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Supporting test on the specified channels of GSRC board, GSPT board and
GECP board for the location of problems.
The above tasks are relevant with specific hardware platforms and in low level in the
whole software system. They mainly provide service support to call processing tasks.
AMP: In the main control frame, and at the highest level of equipment
management, this board is responsible for the status management and data
management of all boards in the system, and the notification and report of
abnormal events.
GQSI: Reporting to AMP the status of all boards in the interface frame in two ways:
regular reporting and event-triggered reporting.
BCC: Reporting to AMP the status of all boards in the service processing frame in
two ways: regular reporting and event-triggered reporting.
GMHI: Reporting to AMP the status of its inferior boards, including such resource
boards as GSRC and GSPT.
GCDI: Reporting to AMP the status of its inferior boards, including IWC and IWF.
NCC: Responsible for the status report and management of all the boards in the
central switching network frame.
As the core of system equipment management, AMP board improves stability of the
system through active/standby hardware configuration and real-time backup of data.
2-11
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
Response
Networking
application
GSPC
Response
Switching network
control module
Response
Task
transmission
Speech channel
application control
module
Networking
operation
application
Networking operation
support layer
Service Processing
Module
NCC
2-12
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
GSNU
GCNU
GSNU
GE16/GSTU/
GETS/GECS
E1/STM-1
E1/STM-1
GSNU
GCNU
GSNU
E1/STM-1
2-13
GCPC
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 2 Host Software
GCNU
GSNU
GE16/GSTU/
GETS/GECS
E1/
STM-1
2-14
Technical Manual
M900/M1800 MSC/SSP/IP
z
Software Architecture
Chapter 2 Host Software
This module completes called number analysis and route selection under the support
of the database. In the number analysis process, it should judge whether the calling or
called subscriber is an intelligent subscriber. In case of an intelligent subscriber, the
intelligent call control module is triggered. Otherwise, the call will be handled as an
ordinary call.
z
This module is responsible for the interworking of the system with SCP (Service Control
Point) and for the completion of call proceeding under the control of SCP to implement
the monitoring over the call proceeding of intelligent subscribers.
2-15
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
iManager M2000
Superior NM system
O&M
terminal
software
BAM
Software
BAM
Communication
gateway
iGWB software
Foreground (host)
iGWB
WS
Charging center
Background (OMC)
3-1
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
management. The iGWB software enables the bills generated by the host to be stored,
maintained, and provided to the interface of the billing center.
The software of local maintenance system comprises BAM software, WS software and
communication gateway software. BAM communicates with the host and WS via
TCP/IP, accomplishing the interaction with the host via MML commands. The
communication gateway enables the access of the alarm box, and the
telecommunication of WS and BAM via Internet.
3-2
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
Host
LAN
Network segment 1
NIC
NIC
NIC
LAN
BAM
Network segment 2
...
WS
WS
3-3
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
commands to realize remote maintenance over the MSC by using Telnet or the
MML-based graphical terminal.
V. Open system
The system adopts the standard TCP/IP protocol and the distributed database
technology, and is in conformity with the ISO/OSI (Open System Interworking)
standards. Meanwhile, the system can be connected with large-scale databases to
enable transparent access and various value-added and intelligent services. It can be
connected with a number of peripherals such as CD-ROM drive, hard disk array, tape
drive and printer. Expansion of the Maintenance and Operation terminal can easily be
realized.
BAM provides the log function to record the operations made by each operator.
The separation of the private network from the public network makes Host invisible
to the outside.
The invisibility of the configuration data to the user ensures data safety.
3-4
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
Security
BAM
Service
Management
Server
Service
Processing
Server
Stats
Server
Maintain
Server
Communication
Server
Security
Manager
Warn
Server
MML
Server
Database
Dataman
Server
Logman
Server
Exchange
Server
SQL SERVER
Server
Operating
System
WINDOWS 2000
SQL Server: Storing various service data and providing database support to
various service servers.
Alarm Server: Processing the MSC alarm information and BAM internal alarm
information, providing WS with the function of alarm report, alarm information
query and alarm box driving.
Data Management Server: Processing configuration data and data backup, such
as call prefix data and equipment data.
Log Management Server: Recording operation log and providing Client with the
function of log query and malicious operation tracing.
BAM Service: Monitoring Security Manager module and restarting BAM computer
in due time.
3-5
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
Note:
Users can access the iGWB through Web browser, so there is no need to install special software on the
operation terminal to view or backup bills.
The MML navigation module provides basic operation command sets of the
M900/M1800 MSC/SSP/IP in tree structure. The command sets provided are classified
in tree structure according to their attributes. By expanding an MML command tree you
can find the MML command node. Double clicking the MML command node can open
the MML command input window and the MML prompt window. The user only needs to
input the command and parameters, the MML module can automatically create the
command report and issue it. Through the MML, various operations over the host can
be completed, including data configuration, performance management, subscriber
management, etc.
z
3-6
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
3-7
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
3.6.1 Functions
The iGWB software mainly provides the following functions:
I. Bill storage
Storing bill in respective directories according to its type. The iGWB can periodically
and automatically backup the bill data from the hard disk to the other servers in TCP/IP
network.
3-8
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
V. Bill maintenance
The iGWB and bill console adopt the Client/Server mode, with the former acting as
server to support the maintenance of the latter.
VI. Backup
The iGWB provides powerful and convenient backup function, including automatic
backup and manual backup. The iGWB can periodically backup the charging data from
the hard disk to other servers in the network. Through the iGWB, user can perform such
backup-related operations as browsing the files in backup media, checking the
available space of backup media, and manual backup of bills.
3.6.2 Features
I. Powerful processing capability
The iGWB can process 1,500 bills per second.
3-9
Technical Manual
M900/M1800 MSC/SSP/IP
Software Architecture
Chapter 3 OMC Software
Service failure
Program malfunction
3.6.4 Structure
The iGWB software is running on Windows NT Operating System. It is composed of
3-10
iGWB
Software
Billing Center
Web
Browser
Maintenance Module
FTP/FTAM
Module
Back Storage
Module
Intermediate
Module
Front Storage
Module
MSC
Host
Communication
Module
Technical Manual
M900/M1800 MSC/SSP/IP
z
Software Architecture
Chapter 3 OMC Software
Host communication module: Communicating with the MSC and packing the
received bills before sending it to the front saving module.
Front storage module: Storing the original bills received from the Host
communication module in file and sending them to the intermediate module for
processing.
Back storage module: Saving the final bill in respective directory according to its
type.
Note:
When M900/M1800 MSC/SSP/IP provides lawful interception function, the OMC software also includes a
software module XPTU software. XPTU software communicates with the LIC via TCP/IP or X.25, and
performs conversion between X1, X2 interface protocols and internal interception protocol.
Communicating with the Lawful Interception Center (LIC) via TCP/IP or X.25, the XPTU
software enables the conversion between X1/X2 interface protocol and internal
interception protocol.
3-11
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
MSC Functions
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Table of Contents
Table of Contents
Chapter 1 Mobile Services............................................................................................................ 1-1
1.1 Basic Telecommunication Services ................................................................................... 1-1
1.1.1 Teleservices ............................................................................................................ 1-1
1.1.2 Bearer Services....................................................................................................... 1-3
1.2 Supplementary Services (SS)............................................................................................ 1-5
1.2.1 Line Identification SS .............................................................................................. 1-5
1.2.2 Call Forwarding SS ................................................................................................. 1-6
1.2.3 Call Completion SS ................................................................................................. 1-6
1.2.4 Multiparty SS ........................................................................................................... 1-7
1.2.5 Community of Interest SS ....................................................................................... 1-7
1.2.6 AoC Supplementary Services ................................................................................. 1-8
1.2.7 Call Barring SS........................................................................................................ 1-8
1.2.8 Unstructured Supplementary Service ..................................................................... 1-9
1.2.9 Explicit Call Transfer (ECT)................................................................................... 1-10
1.2.10 ODB Supplementary Services ............................................................................ 1-10
1.2.11 Self-defined Supplementary Services................................................................. 1-11
1.3 Value-Added Services ..................................................................................................... 1-12
Chapter 2 Network Functions ...................................................................................................... 2-1
2.1 Security .............................................................................................................................. 2-1
2.1.1 Authentication.......................................................................................................... 2-1
2.1.2 User Information Ciphering ..................................................................................... 2-1
2.1.3 TMSI Re-allocation.................................................................................................. 2-2
2.1.4 Equipment Identification.......................................................................................... 2-2
2.2 Mobility Management......................................................................................................... 2-3
2.2.1 Location Management............................................................................................. 2-3
2.2.2 Handover................................................................................................................. 2-4
2.3 Call Handling...................................................................................................................... 2-5
2.3.1 Call Connection Function ........................................................................................ 2-5
2.3.2 Number Storage and Translation Function ............................................................. 2-6
2.3.3 Route Analysis Function ......................................................................................... 2-7
2.3.4 Echo Control............................................................................................................ 2-9
2.3.5 Tone Sending Function ......................................................................................... 2-10
2.3.6 IWF Function ......................................................................................................... 2-11
2.3.7 Number Receiving Delay Function........................................................................ 2-12
Chapter 3 Mobile Application Protocols ..................................................................................... 3-1
3.1 SS7 System ....................................................................................................................... 3-1
3.1.1 Structure.................................................................................................................. 3-1
i
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Table of Contents
ii
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
1.1.1 Teleservices
These services provide the subscriber with basic capabilities to communicate with
other subscribers. It includes speech service, short message service and facsimile
service.
I. Speech service
Speech services include telephony and emergency calls.
z
Telephony
Provide automatic telephone service and various special services for the mobile
subscribers to communicate with PSTN subscribers, ISDN subscribers and PLMN
subscribers.
z
Emergency Calls
When the subscriber presses the emergency key or dials the number of emergency
service center, the call will be connected to the nearest emergency center. It can be
generated without SIM card. The network operator can decide whether to charge the
subscribers for such calls.
1-1
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 1 Mobile Services
Note:
Short message broadcast service has nothing to do with MSC.
1-2
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
In the case both speech and facsimile services are needed, M900/M1800 MSC/SSP/IP
supports the communication of speech followed by facsimile.
1-3
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
Packet
NT-mode adopts RLP. On the basis of forward error correction mechanism provided by
radio interface transmission scheme, messages can be resent if the peer end does not
receive the message correctly. In the mode, the throughput varies with the basic
transmission quality and transmission delay (the higher the error probability is, the
lower throughput will be). Measured by residual error codes, its transmission quality is
much better than that of T-mode.
3)
According to service codes, bearer services can be grouped into the following
categories:
BTS2X provides asynchronous data transmission at various rates, and supports both
3.1 kHz audio and PAD access. PLMN can interconnect with PSPDN with PSTN/ISDN
as the transmission network. The communication between PLMN and PSTN can only
be done through 3.1 kHz audio, while the communication between PLMN and ISDN
can be done through various modes including 3.1 kHz audio.
z
1-4
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
BS4X allows a simple terminal to communicate with the X.25 terminals on PSPDN
through dedicated PAD. Compared with BS2X, these services do not need ISDN or
PSTN. BS4X only supports mobile originated calls.
z
BS5X provides the packet bearer services for which PLMN directly connects to PSPDN
through PH. The communication between MSC and PH employs X.32 protocols. BS5X
supports non-transparent bearer services only.
Note:
The following supplementary services are provided only when M900/M1800 MSC/SSP/IP serves as
VMSC (Visited MSC). When it serves as GMSC (Gateway MSC), it only performs corresponding
procedure processing.
CLIP is a Supplementary Service provided to the called party. When the mobile
subscriber receives a call, the network will display the calling number.
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 1 Mobile Services
CLIR is a Supplementary Service provided to the calling party. When the mobile
subscriber makes a call, the network will not display the calling number to the called
party.
z
COLR is a supplementary service provided to the called party. When the subscriber
(registered with this service) accepts the call, the network will not display his number to
the calling subscriber.
When a mobile subscriber is called, he can forward all calls to a pre-selected third party
unconditionally by activating this service. The third party here can be the subscriber of
PLMN, PSTN and ISDN, or service stations like voice mailbox.
z
When a mobile subscriber is busy in calling and a new call is coming, the new call will
be forwarded to a pre-selected third party.
z
When a mobile subscriber rings for a long time and the called does not answer, the call
will be forwarded to a third party after the expiry of No Reply Timer.
z
When the radio channel connection between the network and the mobile station is
interrupted, the call to this MS will be forwarded to a third party. The "unreachable"
condition includes no response to paging, radio channel assignment failure and MS
switch-off.
CW (Call Waiting)
1-6
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
The Call Waiting Service permits a mobile subscriber to be notified of an incoming call
(as per basic call procedures) while the traffic channel is not available for the incoming
call and the mobile subscriber is engaged in an active or held call. Subsequently, the
subscriber can accept, reject, or ignore the incoming call.
z
1.2.4 Multiparty SS
The group of Multiparty supplementary services consists of one supplementary service:
Multi-Party Service (MPTY).
MPTY provides a mobile subscriber with the ability to have a multi-connection call, i.e.
a simultaneous communication with more than one party. However, multi-party service
requires the mobile subscriber to have subscription to call hold service.
1-7
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
Incoming & Outgoing calls barred within a CUG: The subscribers with this feature
cannot make or receive calls from other members in the group.
CUG with outgoing access (OA): The subscribers with this feature can make calls
outside the CUG.
CUG with incoming access (IA): The subscribers with this feature can receive calls
from subscribers outside this CUG.
CUG with IA and OA: The subscribers with this feature can make calls to and receive
calls from the outside CUG.
AoCI allows immediate display of charges on the termination of the call. If the
subscriber registers AoCI service, the network side will send charging rate to the MS
which automatically calculates and display the charge amount for each call.
z
Besides the functions of AoCI, AoCC also supports leased MS service and PPS. These
services require the MS supporting Phase 2 standards and special SIM card.
BIC-Roam (Barring of Incoming Calls when Roaming outside the home PLMN
country)
With this service, the calls to this subscriber will be barred when he is roaming outside
the home PLMN country.
z
1-8
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
With this service, all calls made by this subscriber will be barred except for the
emergency calls.
z
With this service, all international calls made by this subscriber will be barred.
z
This barring service will only allow calls towards a party in the country of subscription.
When the subscriber is roaming in home PLMN country, calls to subscribers in other
countries will be barred. When the subscriber is roaming outside home PLMN country,
only the calls to subscribers of local country and home country are allowed.
supplementary
service
mainly
refers
to
USSD
(Unstructured
MSC
BSS
HLR
SS7 network
USSD Center
USSD Center
INTERNET/PSTN/PSPDN/ISDN
Figure 1-1 Devices related to USSD
1-9
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
The subscriber can send certain service request to the network by entering SS
operation commands on MS, or the network side initiates USSD command to perform
certain services. USSD service may be provided by GSM network, or provided by other
networks with GSM network as the bearer for transparent transmission.
With USSD center, the following services are available:
z
Stock information.
Sports information
Besides obtaining public information, USSD can also be used for the query and
management of subscriber service data in the mobile network. For example,
z
The subscriber can use the USSD service to manage intelligent services once
MSC is connected with WIN.
The subscriber can query data in VLR and HLR (such as the query of the
subscriber MSISDN number)
1-10
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
Firstly, the service state of ODB subscribers is controlled by the network operator, while
for the call barring SS, the status can be controlled by either the subscriber or the
operator.
Secondly, ODB service is activated once it is provided, but call barring SS should be
activated by the subscriber after being provided.
M900/M1800 MSC/SSP/IP supports the following ODB services:
z
Barring outgoing international calls except those directed to the home PLMN
country
Barring of outgoing calls when roaming outside the home PLMN country
Barring incoming calls when roaming outside the home PLMN country
Zone Code is a kind of subscription data in HLR, which can be used to restrict the
roaming area of the subscriber. MSC can define the Location Areas (LAs) contained in
each Zone Code. In this way, the area that allows mobile subscriber roaming can be set
flexibly.
z
MSC can provide roaming restriction function based on LA without the cooperation of
HLR. For this type of roaming restriction, subscriber group and area No. (one area No.
may correspond to one or more LA) should be defined first. And then the
correspondence between the subscriber group and area No. should be defined, so that
the area in which roaming is forbidden for this subscriber group can be established.
z
VLR table contains a kind of subscription data in HLR, which defines the roaming area
of the subscriber with the unit of VLR area. MSC enables this roaming restriction under
the cooperation of HLR.
1-11
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 1 Mobile Services
Note:
Another value-added service UCB (USSD Call Back) provided by M900/M1800 MSC/SSP/IP is introduced
in Module 5 SSP Functions.
1-12
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
2.1 Security
GSM security has two main purposes: one is to prevent the access of unauthorized
subscribers; the other is to provide security for communications to authorized
subscribers.
Checking subscriber identities can prevent the access of unauthorized subscribers. For
subscribers security, TMSI is attached to an MS and this TMSI is used for call
connections instead of IMSI, so that subscriber ID will be safe. Ciphering is applied for
the personal conversation security i.e. nobody can hear the subscribers
communication.
Security measures include authentication, user information ciphering, TMSI
re-allocation, equipment identification, etc.
2.1.1 Authentication
The authentication decides whether the subscriber is authorized to access the PLMN
network or not. The specific method is: VLR stores three unused parameters of each
MS from AUC, which includes random number (RAND), response number (SRES) and
ciphering key (Kc).
When MS requests to access PLMN, MSC sends the authentication request message,
which contains RAND. Subscriber authentication key (Ki) stored in SIM card is
calculated with RAND by algorithm A3 to generate SRES. Then SRES is sent to VLR
where it is compared with the one in VLR. If both SRESs are the same, the
authentication succeeds. Otherwise, MS is not allowed to access the network.
2-1
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
code. And Kc is obtained from RAND in the authentication request message and Ki
through algorithm A8.
In each location update, MSC/SSP/IP assigns a new TMSI to the subscriber. The old
TMSI in the mobile equipment is deleted and new TMSI is recorded.
z
Before the service access of each subscriber, MSC/SSP/IP assigns a new TMSI to the
subscriber. The subscriber will use the new TMSI for service accessing until next TMSI
re-allocation.
2-2
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
For the MS in the grey list, the MSC determines whether to let it access the network or
whether to play prompt tone according to data configuration.
Equipment identification is an optional function, and different operators may have
different requests for it, therefore, M900/M1800 MSC/SSP/IP provides the
customization of equipment identification, which includes:
z
Reuse of IMEI.
Selection of whether to let the MS access when the status of MS is unknown (No
such IMEI is found in EIR).
Location registration
The normal location registration (also called location update) of the mobile subscriber
takes place when MS is powered on or MS is roaming to a new area.
z
Through periodical location registration (location update), PLMN can keep track of the
present status of the MS. The PLMN operator can set the location update period and
protection time according to specific traffic.
z
MS switch-off
When the mobile subscriber switches off his / her MS, MS will originate the DETACH
process and MSC will set the subscriber status as IMSI-detached. If the MS is called,
MSC will inform the calling party of the switch-off (MS is absent) status of the called
party via HLR, when HLR asks for the roaming number of the MS.
z
2-3
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
Deletion of the subscriber records from VLR includes the subscriber data deletion
because of subscriber roaming to other MSC or because of no operation for a long time.
It also refers to the deletion of invalid subscriber records by the system operator.
Serving as VMSC, M900/M1800 MSC/SSP/IP can provide Gs interface for connecting
SGSN. Gs interface adopts SS7 BSSAP+ protocol. Through Gs interface, MSC and
SGSN can mutually update the MS location information stored in the database, thus
reducing air signaling and facilitating MSC to page through Gs interface the Class-B
mobile station currently engaged in GPRS service.
Note:
MS is of three classes:
1) Class-A mobile station can implement the GPRS service and GSM services.
2) Class-B mobile station can complete simultaneous attachment, activation monitor of GPRS service and
GSM service, but only one type of services can be implemented at one time (GPRS service or GSM
service).
3) Class-C mobile station separates GPRS service and GSM service. When it needs to use other type of
service, it should re-attach and re-initialize first.
2.2.2 Handover
The handover function allows a continuous quality conversation when the subscriber
moves from one cell to another or from one channel to another channel.
BSS (Base Station Subsystem) makes handover decision according to the MS
receiving level, quality and distance between the current BTS (Base Transceiver
Station) & the mobile subscriber as given in the measurement reports from the MS. Cell
traffic and maintenance requirements are also important factors in the handover
determination. BSS originates different handover requirements according to these
decision. In case of traffic congestion, NSS (Network & Switching Subsystem) can
request BSS to modify the handover algorithm according to traffic information to
forcefully handover some calls from congested cell to other cells.
There are intra-BSS, inter-BSS and inter-MSC handovers. Inter-BSS handover and
inter-MSC handover are implemented by MSC. Intra-BSS handover is normally
controlled by BSS or it can be controlled by MSC.
M900/M1800 MSC/SSP/IP supports inter-channel handover of the subscriber
during/after the call setup due to power receiving level, channel, quality, distance and
traffic. This is to ensure the satisfactory communication quality for the subscriber or to
reduce partial congestion of the system.
2-4
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
Handover controlled by MSC (Mobile Switching Center) can be classified into MSC
internal handover, basic handover and subsequent handover.
MSC internal handover (intra-MSC handover) refers to the handover when MS roams
from one BSC (Base Station Controller) to another BSC in the same MSC area. The
whole handover process is controlled by one MSC.
Basic handover is the handover process when MS roams from one MSC (MSC-A) to
another MSC (MSC-B). Two MSCs are involved in such a handover.
Subsequent handover refers to the inter-MSC handover in the subsequent
communication process after the basic handover of the mobile subscriber is succeeded.
According to different handover destinations, subsequent handover is of two types i.e.
subsequent handover to the controlling MSC (MSC-A) and subsequent handover to the
third party MSC.
Making the calling mobile subscriber access the network and allocating relevant
traffic channel according to his/her calling request.
Querying the actual location of the called mobile subscriber according to the
MSISDN number and connecting to the visited MSC (VMSC) with the location
information.
2-5
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 2 Network Functions
Initiating paging according to the IMSI/TMSI of the called mobile subscriber and
his current BTS location.
Making the called subscriber access and allocating relevant traffic channel
according to the paging response of the called subscriber.
Setting up the call between the calling subscriber and the called subscriber after
the called subscriber answers. After the conversation is over, it is capable of
releasing relevant call resources in time.
Accomplishing the tandem of the call among TUP signaling, ISUP signaling and
CAS.
Sending the calling number and calling subscriber type to other MSC or PSTN.
Supporting the alarm function for emergency calls & malicious calls defined by
users and sending information, such as calling number, called number and start &
end time of communications.
Supporting the delayed ringing function so that the calling subscriber can cancel
the operation within a certain period after wrongly dialing some special service
numbers.
When the call is not successful, the circuit can be instantly released. Appropriate
recorded announcement can be sent to the calling subscriber according to specific
failure reason.
It can accept and store 24-digit numbers and support the analysis of max. 16-digit
number.
It can receive numbers sent in the group code sending mode and the overlay
code-sending mode.
It enables various number conversions (both the contents and the nature of the
call) of incoming number (including calling number, called number and original
called number), according to the calling number/called number/original called
number or the correlation among them.
It can restrict common calls and forwarding calls according to the nature of the call,
such as the location of the calling subscriber, calling number, called number and
original called number, etc.
2-6
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 2 Network Functions
It supports the restriction of min. and max. number length. Operators can define
the subsequent processing that will only be conducted when the digits of the called
number are up to the desired min. number length, and when such digits exceed
the desired value, the restriction of max. number length can be used to cut the
number to a desired length.
It enables various number conversions (both the format and the contents of the
call) of various outgoing number (including calling number, called number and
original called number), according to the nature of calling number/called
number/original called number or the correlation among them.
It supports the handling of irregular numbers at MAP signaling interface and CAP
signaling interface, e.g. the MSISDN during MSCs addressing of HLR, the MSRN
or forwarded-to number returned by HLR, the hand-over number used in handover
and number used in SCP interaction.
Internal routing
MSC determines to allocate a speech channel according to the current location of the
called MS. The location information is represented as the BSC signaling point code in
MSC.
z
Internal routing
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
MSC/SSP/IP also provides enhanced routing function for more flexibly routing. When
this function is activated, instead of obtaining the route selection code from number
analysis result, MSC obtains the route selection code via enhanced routing function
after number analysis. The enhanced routing process includes:
z
Routing according to number length, i.e setting different route selection codes in
the case that call prefixes are same, but the called numbers are of different
lengths.
Routing according to call type, i.e. setting different route selection codes in the
case that the called numbers are same, but the calls are of different types (e.g.
one is a common called number, the other is a forwarded-to number).
According to the route selection source code and the route selection code, MSC can
decide the route to the called subscriber. The route can be simply taken as all the paths
for travel from one place to another. And the combination of every path or part of the
path between the two sites is called the sub-route. MSC can dynamically select the
route according to the inter-exchange route/sub-route configuration, traffic distribution
and sub-route working state (available/unavailable).
M900/M1800 MSC/SSP/IP has two routing alternatives: sequential routing and
percentage routing. According to the principles of route hierarchy, the routes with the
same destination can be subdivided into direct route, alternative route and basic route.
The direct route will be selected first, then the alternative route and then the basic route.
The following route will only be selected when the previous one has no circuit available.
However, in another case where load sharing is required for the traffic to the upper two
or more tandem offices, or routes should be selected in proportion according to the
amount of trunk circuits, percentage routing of M900/M1800 MSC/SSP/IP may be
called into play.
z
2-8
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
2-9
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
either incoming or outgoing time slot), as is shown in Figure 2-2. That is, the standalone
echo cancellation equipment implements the provision of global shared echo
cancellation resource by occupying more system resources than the built-in echo
cancellation equipment.
CNET
E1
GE16/
GSTU
GE16/
GSTU
E1
GECP
CNET
E1
GE16/
GSTU
GECS
E1
Failure tone-sending corresponds to calls of failed connection. When the call fails,
the system informs the calling party of the specific failure cause through record
tones. The system provides a set of default tone-playing modes to enable the
one-to-one correspondence between the tone and failure cause. If the operator
thinks the default tone is different from expected tone, modification can be made
through data configuration.
2-10
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
In theory, each signal tone can be set in the synchronous or asynchronous sending
mode. In actual applications, some regular signal tones, such as the busy tone (450Hz,
-103dBm0, 0.35s on/0.35s off), ring-back tone (450Hz, -103dBm0, 1.0s on/4.0s off)
and congestion tone (450Hz, -103dBm0, 1.7s on/0.7s off) generally take the
asynchronous sending mode. Irregular signal tones generally take the synchronous
sending mode.
M900/M1800 MSC/SSP/IP supports the loading of voice files, which can be recorded in
the independent recording equipment and converted in format through specific
software. Voice files after conversion can be loaded on the announcement play
equipment via the WS. After configuring relative data, the newly recorded
announcement can be played.
2-11
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
PSTN
Facsimile machine
M900/M1800 MSC/SSP/IP
BSS
IWF
Internet
MS
Computer
ISDN
Laptop
2-12
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 2 Network Functions
2-13
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
3.1.1 Structure
Signaling System No.7 (SS7) is designed to meet the challenges of high-speed data
networks. The system is designed to control not only the call setups but also
non-speech services. SS7 is a multifunctional modular system and is suitable for
various applications of telecommunication networks (analog, digital telephone network,
mobile telephone network and circuit switched data network, etc.).
According to the basic architecture of ITU-T Signaling System No.7, the whole
signaling system mainly includes Message Transfer Part (MTP), Signaling Connection
and Control Part (SCCP), Telephone User Part (TUP), ISDN User Part (ISUP) and
Transaction Capability Application Part (TCAP).
To meet the requirements of diversified services, Mobile Application Part (MAP), BSS
Application Part (BSSAP) and CAMEL Application Part (CAP) are also developed.
Their architecture and division of functions is closely related to the Open System
Interconnection (OSI) 7-layer reference model.
SS7 architecture of M900/M1800 MSC/SSP/IP is illustrated in Figure 3-1.
3-1
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
OMAP
CAP
MAP
TCAP
B
S
S
A
P
I
S
U
P
T
U
P
SCCP
MTP
BSSAP: Base Station System Application Part
ISUP: ISDN User Part
TCAP: Transaction Capability Application Part
MTP: Message Transfer Part
3.1.2 MTP
I. Overview
The MTP (Message Transfer Part) of M900/M1800 MSC/SSP/IP Signaling Processing
Module fully complies with ITU-T Q.701-710 recommendations.
The main function of MTP is to ensure reliable signaling message transfer in the
signaling network. In case of system and/or signaling network faults, it can take
measures to avoid or reduce the loss, repetition and loss of order of messages.
MTP comprises three functional levels, including Signaling Data Link Function,
Signaling Link Function and Signaling Network Function.
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
CNET
GE16/GSTU
SPC
GCPC
HDLC communication
HDLC communication
Bus comm.
Active GSPC
3-3
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Message distribution
Message
discrimination
Message routing
The Message Routing (MRT) is used to determine the outgoing route. It uses the
information in the routing label (Destination signaling Point Code also known as DPC
and Signaling Link Selection code known as SLS) to select a signaling link for the
signaling message so that the signaling message can be sent to the destination
signaling point.
z
The Message Discrimination (MDC) receives the message from the second layer to
determine if the destination of the message is the local signaling point. If the destination
is the local signaling point, the MDC sends the message to Message Distribution (MDT).
If not, the MDC sends the message to the MRT.
z
The Message Distribution (MDT) distributes the messages sent by the MDC to the
corresponding user parts, the signaling network management and testing &
maintenance parts.
2)
3-4
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
The Signaling Traffic Management (STM) is used to transit the signaling flow from one
link/route to another or multiple available links or routes when the signaling network
fails. It is also used to temporarily reduce signaling traffic in case of congestion at the
signaling point.
z
The Signaling Link Management (SLM) is used to recover, start up or exit the signaling
link in the signaling network and ensure the provision of certain pre-determined link
sets. The connection between the Signaling Data Link and the signaling terminal is
normally established by the man-machine commands. Operations in the signaling
system cannot automatically change the above connections.
z
The Signaling Route Management (SRM) is used to ensure the reliable exchange of
signaling route availability information between Signaling Points so as to block or
unblock signaling routes. SRM mainly comprises procedures, such as transfer
prohibited, transfer allowed, controlled transfer & restricted transfer, signaling route
group test and signaling route group congestion test. These procedures are used only
when the signaling services from the originating terminal reach the destination via the
Signaling Transfer Point.
Besides the functions described above, MTP also supports multi-SP function and
2Mbit/s signaling link function. The multi-SP function makes possible the signaling links
between local SP and other SP much more than 16 and the trunk circuits between local
office and other office more than 4,096. While 2M signaling link function makes the rate
of the signaling link reach 2Mbit/s, which enables the signaling exchange flow between
signaling points beyond the limit of 16%64kbit/s. When 2Mbit/s signaling link function is
adopted, GHN7 board will accomplish the MTP function in signaling data link layer and
signaling link function layer, and directly lead in the E1 cable transferring 2M signaling
link.
3.1.3 SCCP
I. Overview
The Signaling Connection and Control Part (SCCP) is introduced to strengthen the
functions of MTP. It is the third layer of OSI and enables virtual circuits and data report
packet switching functions.
MTP only transfers messages to nodes and enables the transmission of
connectionless messages. But SCCP adopts the Destination Point Code (DPC) and
3-5
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
the Sub-System Number (SSN) to provide the addressing ability in order to identify
each SCCP user in the node. SCCP also provides another addressing mode and
Global Title (GT), to compensate for the shortcomings of MTP signaling point codes.
The SCCP of M900/M1800 MSC/SSP/IP fully complies with ITU-T Q0.711-716
recommendations.
SCCP is adopted for the realization of the following functions:
New services and functions in the Intelligent Network, mobile communications and
intelligent management.
Inter-working between signaling networks (STP)
SCCP User
Connectionless
primitive
Network
service
function
Connectionless
control
Connection
-less
message
Route
failure
Management
primitive
Connection-oriented
primitive
Connection
-oriented
control
Connection
-oriented
message
Management
control
Route failure
Routing function
Unavailable
subsystem message
SCCP
MTP transport primitive
MTP
Figure 3-4 SCCP functional modules
1)
There are four different classes of protocols corresponding to SCCP network services:
z
3-6
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Class-0 and class 1 protocols are oriented to connectionless services, while Class 2
and Class-3 protocols are defined for connection-oriented services.
In connectionless service, users do not establish the signaling connection before data
transmission, but use the Routing function of SCCP and MTP to transfer data
information directly in the signaling network. This type of services is flexible and simple,
applicable to the transfer of small amount of data. Clsss-0 service does not guarantee
the sequential transfer of messages. Class-1 service guarantees the sequential
transfer of messages depending on the co-ordination of SLS (Signaling Link Selection)
and MTP.
Connectionless services transfer user data by adopting the Unit Data message (UDT)
and Extended Unit Data message (XUDT). UDT messages do not have data
segmentation/concatenation ability and can transfer only a small amount of user data.
XUDT messages have the segmentation/ concatenation ability and can transfer up to
2K octets user data.
Connection-oriented services require the establishment of signaling connection (virtual
connection) between the originating point and the destination point before the transfer
of signaling information. In such cases, there is no need to select routes by using the
SCCP Routing function when transferring data; instead, the data is transferred through
the established signaling connection. When the data transfer is completed, the
signaling connection can be released by the user with N_DISCONNECT_REQ
primitive. This type of service applies to the transfer of large volumes of data. The
invalid transmission of batches of data can be prevented in this case, as the destination
point confirms its data receiving ability before the data transmission. At the same time,
the pre-established connection results in no SCCP routing for the subsequent data
transmission. So, the time delay for the transmission of data batches can be effectively
reduced.
The basic process of the connection-oriented service comprises three phases,
connection setup, data transmission, and connection release. M900/M1800
MSC/SSP/IP provides local reference function of freezing local node to avoid
connection confusion when releasing local connection resources.
2)
Routing function
SCCP routing function is mainly used for addressing for DPC+SSN and GT address
messages.
SCCP Routing function refers to the route addressing for SCCP address messages
that are more general than signaling point codes.
The following specific address information can be found in SCCP message:
z
DPC
GT+(SSN)
3-7
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Management function
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
and
its
upper-layer
include
connectionless
service
primitives,
N_NOTICE: Notice primitive, used in connectionless service to notify that the message
at message source point cannot be sent to destination point. It includes N_NOTICE
indication only.
z
N_NOTICE Indication: SCCP notifies the originating user that the message can
not reach the destination.
2)
N_CONNECT Indication: Sent by SCCP of the called node (where the called party
locates) to called SCCP, requesting to establish signaling connection with the
calling party.
N_CONNECT Response: Response to local SCCP and sent by called SCCP user
on called party reply, notifying SCCP that the called party agrees to establish the
signaling connection.
3-9
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 3 Mobile Application Protocols
N_DATA Request: SCCP user requests SCCP transfer data on the established
signaling connection.
N_DATA Indication: SCCP notifies SCCP user that data from peer end has been
received on the established signaling connection.
N_EXPEDITED DATA Indication: SCCP notifies SCCP user that the expedited
data from peer end has been received.
N_DISCONNECT Indication: SCCP notifies SCCP user that the peer end rejects
the establishment of signaling connection or disconnects the connection
established.
N_RESET: If protocol class includes flow control, this primitive may appear during
data transfer process to suppress all other activities, so that SCCP can reinitialize
and adjust the sequence number.
3)
N_COORD: Coordinate primitive, used for service coordination between active and
standby subsystems in SCCP management. It includes N-COORD Request,
N-COORD Indication, N-COORD Response and N-COORD Acknowledgement.
z
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
4)
MTP_TRANSFER: Transfer primitive, used for the data transfer between MTP and
SCCP. It includes MTP_TRANSFER Request and MTP_TRANSFER Indication.
z
MTP_RESTART Indication: At the end of MTP restart, MTP notifies local MTP
user (SCCP is a user of MTP) of the completion of MTP restart, and indicates the
availability or unavailability of a SP.
3-11
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Route flag
Message type
Essential para. A
M
Essential para. I
Para. M indicator
M
Para. P indicator
Optional items start indi.
Para. M length indicator
Para. M
M
Para. P length indicator
Para. P
Para. name X
Para. X length indicator
Para. X
M
Para. name Z
Optional items
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
3.1.4 TCAP
I. Overview
In the fast growing era of telecommunication innovation, new services/applications
need changes in the structure of the existing networks. To overcome this, TCAP
(Transaction Capability Application Part) is introduced to provide generic services to a
large variety of such applications.
TCAP and ISP (Intermediate Service Part) constitute Transaction Capability (TC). In
connectionless services, TC includes only TCAP, and directly utilizes the
connectionless service of SCCP to transfer data. At present, TC is widely applied in
connectionless services; so in connectionless services, TCAP refers to TC.
TC refers to a series of communication capabilities that provide the interface between
applications and a network service. It provides a public regulation, which is unrelated to
specific applications. In SS7 network, MTP and SCCP are adopted as the network
service provider of TC.
TC supports two types of data services provided by SCCP, connection-oriented and
connectionless services. Connectionless services are used when the information is
small in amount and the demand for real-time is critical. Connection-oriented services
are adopted when the information is big in amount and the real-time feature is not
needed.
To be all services connection-oriented, TCAP makes the information exchange
between different nodes into an operation and the core of TCAP is to execute remote
operations. The basic unit of TCAP message corresponds to an operation or an
operation response component, whose information and sequence should be defined by
TC users. Related components make up a dialog and the process of the dialog can be
used to implement the procedure of an application service.
3-13
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Application Process
TC user
TCAP service
T
TC primitives
CSL
C
A
P
TSL
Network service
N primitives
SCCP
MTP
3-14
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Label: Composed by one or multiple 8-digit group numbers. It includes three parts:
type, format and label code.
Length: Indicates the number of the 8-digit groups of the content field.
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
TCAP system handles the normal and abnormal processes of component and dialog
messages by strictly following the TCAP Signaling Process described in Q.774. It
manages the dialog label, component usage label and transaction processing label. It
also ensures the correctness of TCAP signaling processing.
In the mobile network, the signaling interworking process of a typical call is shown in
Figure 3-7.
TCAP
TCAP
TC_begin
Initial DP
TC_continue
Connect to resources
TC_continue
Broadcast announcement
TC_continue
Specialized resource report
TC_continue
Prompt and collect user information
TC_continue
Result
TC_continue
Clear forward connection
TC_end
Release call
3.1.5 MAP
Note:
The following description applies to the case when M900/M1800 MSC/SSP/IP is used as GMSC or VMSC.
I. Overview
MAP (Mobile Application Part) protocol defines the mode of information exchange
between GSM network entities to enable MS roaming. GSM network entities include
MSC, VLR, EIR, HLR and SCP. In the GSM network, B, C, D, E, F, G, Gs and J
interfaces can be used to transmit MAP messages, as illustrated in Figure 3-8.
3-16
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
SCP
J
D
HLR
EIR
MSC
F
E
VLR
VLR
B
Gs
MSC
SGSN
Security
management,
including
authentication,
encryption
and
TMSI
re-allocation.
z
Call handling, including access of calling & called subscribers, capturing routing
information and providing roaming number (MSRN).
Supplementary
services,
including
call-related
and
non-call
related
supplementary services.
z
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
invoke ID, which is the unique identifier for an operation in the MAP dialog process. To
distinguish invoke ID, a component can be "translated" into the corresponding MAP
service message. The translation of message between MAP and TCAP is made by
MAP Protocol State Machine (MAPPM).
Positions of the MAP signaling part in the SS7 protocol stack and in the link message
are shown in Figure 3-9 and Figure 3-10.
MSC
HLR
MAP
MAP
TCAP
TCAP
SCCP
SCCP
MTP
MTP
MTP message
SCCP message
TCAP message
MAP message
Operation
Purpose
0x02
UpdateLocation
0x03
CancelLocation
Used by HLR to delete the subscriber data of the previous VLR in location
update, or independent location deletion caused by subscriber data
modification, or deletion of subscriber location information by operator.
0x04
ProvideRoamin
gNumber
Used by HLR to get the roaming number from VMSC, so that GMSC can
address the call to the present location of the called subscriber to set up
the call.
3-18
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Code
Operation
Purpose
0x07
InsertSubscriber
Data
Used by HLR to insert the subscription data during location update and
subscriber data modifications.
0x08
DeleteSubscrib
erData
0x09
SendParameter
s
Phase1 operation used to get the identity & authentication set of the
subscriber from the previous VLR, to get authentication set from HLR and
for Phase1 data restoration request & inserting subscriber data.
0x0A
RegisterSS
0x0B
EraseSS
0x0C
ActiveSS
0x0D
DeactiveSS
0x0E
InterrogateSS
Used for the interrogation of line identification, call forwarding, call barring
and CW supplementary services.
0x11
RegisterPasswo
rd
0x12
GetPassword
0x13
ProcessUnstruc
tureSS-Data
0x16
SendRoutingInf
ormation
0x1C
PerformHandov
er
0x1D
SendEndSignal
0x1E
PerformSubseq
uentHandover
0x21
ProcessAccess
Signaling
0x22
ForwardAccess
Signaling
0x25
Reset
Used to inform VLR about the location update originated to HLR when the
subscriber is active.
0x2B
checkIMEI
0x2C
mt-forwardSM
0x2E
mo-forwardSM
3-19
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Code
Operation
Purpose
0x30
NoteSubscriber
Present
0x37
sendIdentificatio
n
Used to get the IMSI and authentication set from the original HLR.
0x38
SendAuthentica
tionInfo
0x39
RestoreData
Used by VLR to get the subscription data from HLR when the called HLR
requests VLR for the roaming number but VLR does not contain the
subscriber data.
0x3A
SendIMSI
0x3B
ProcessUnstruc
turedSS-Rreque
st
0x3C
UnstructuredSS
-Rrequest
0x3D
UnstructuredSS
-Notify
0x42
ReadyForSM
0x43
PurgeMS
Used by VLR to report to the HLR about its subscriber deletion operation.
0x44
PrepareHandov
er
0x45
PrepareSubseq
uentHandover
0x46
ProvideSubscrib
erInfo
Type-2 operations: Confirmation will be returned only when the operation fails.
When MAP initiates a remote operation, the operational time limit is provided. If no
response is returned before the timer expiration, different measures will be taken
according to different operation types. For Type-1 or Type-3 operations, the operations
3-20
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
are regarded as failed. For Type-2 or Type-4 operations, the operations are regarded
as successful.
Location update
After receiving the location update request, VLR will determine the location area. If the
updating is not in the same VLR location area, the location update request will be sent
to HLR. Otherwise, no request will be sent. When HLR returns the confirmation
message, the HLR number is attached.
The location update process might involve the processes of gettting subscriber identity
from the Previous VLR (PVLR), getting authentication information from HLR, location
deletion process and inserting subscriber data.
z
After receiving the location update request from MSC/SSP/IP, if the subscriber
roaming-to MSC/SSP/IP number is changed, HLR will originate the location
deletion process from PVLR in order to delete the subscriber information in PVLR.
The processes of getting subscriber identity and authentication information from PVLR,
getting authentication information from HLR, location deletion in PVLR, inserting
subscriber data and D-interface location update are all relatively independent. They
co-ordinate each other to complete the location update process of the subscriber in
HLR. D-interface location update and inserting subscriber data are necessary, while
the other three processes are triggered only when conditions are met.
The location update procedure is shown in Figure 3-11.
3-21
Technical Manual
M900/M1800 MSC/SSP/IP
MS
MSC Functions
Chapter 3 Mobile Application Protocols
BSS
MSC/SSP/IP
HLR
PVLR
A_LU_REQUEST
MAP_SEND_IDENTIFICATION
MAP_SEND_IDENTIFICATIONack
MAP_UPDATE_LOCATION
MAP_CANCEL_LOCATION
MAP_CANCEL_LOCATION ack
MAP_INSERT_SUBSCRIBER_DATA
MAP_INSERT_SUBSCRIBER_DATAack
MAP_UPDATE_LOCATION ack
A_LU_CONFIRM
The SRI process requires the co-ordination of getting the roaming number. When HLR
receives the request for SRI from GMSC, and the subscriber is in the inactive status,
the forwarded-to number or absent subscriber message will be returned directly;
otherwise a request will be originated to obtain the roaming number from the VLR
where the subscriber is located. And corresponding response will be returned to GMSC
according to the returned result from VLR.
If the called subscriber is a CAMEL subscriber and GMSC supports CAMEL standards,
two SRI processes will be experienced. In first process, GMSC sends the SRI message
to the called HLR. If the called subscriber is a pre-paid subscriber, the subscription
information T-CSI will be returned. GMSC gets the called SCP address according to the
called T-CSI message. SCP will determine the communication duration and charging
rate according to the called subscriber account. In the second process, GMSC sends
the SRI message to the called HLR for the second time. The SRI message suppresses
T-CSI to get the called MSRN. MSC implements call proceeding according to the called
MSRN.
The flow of SRI procedure is shown in Figure 3-12.
3-22
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Network
GMSC
I_IAM
HLR
VLR
MAP_SEND_ROUTING_I
NFORMATION
MAP_PROVIDE_SUBSCRIBER_IN
FORMATION
MSC
MAP_PROVIDE_SUBSCRIBER_IN
FORMATION ack
MAP_SEND_ROUTING_I
NFORMATION ack
MAP_SEND_ROUTING_I
NFORMATION
MAP_PROVIDE_ROAMING_
NUMBER
MAP_PROVIDE_ROAMING_
NUMBER ack
MAP_SEND_ROUTING_I
NFORMATION ack
I_IAM
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
X. Data restoration
When HLR gets the roaming number from VLR, if the subscriber data does not exist or
the location acknowledgement label is repositioned, VLR will send the data restoration
request to HLR to re-insert the subscriber data in VLR. The process of getting roaming
number triggers the data restoration process. The executions of two processes are
independent and will not influence each other.
3.1.6 BSSAP
Note:
The following description applies to the case when M900/M1800 MSC/SSP/IP is used as VMSC.
I. Overview
BSSAP protocol is used as the A-interface protocol. It describes two types of messages,
BSSMAP messages and DTAP messages.
The BSSMAP message is responsible for service process control and For the DTAP
message, A-interface functions as a transparent channel. At BSS side, DTAP
3-24
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
messages are sent directly to radio channel, while at NSS side, DTAP messages are
transmitted to the corresponding functional units.
BSSAP protocol is implemented according to ETSI GSM 08.08 and GSM 04.08
specifications.
2)
Ciphering messages include cipher mode command and cipher mode command
completed.
3-25
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Number of available idle radio resources, which can be used in the traffic channel
in BSS.
3-26
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Handover required
Due to the following reasons, BSS will send "handover required" message to MSC to
implement handover for a MS with assigned dedicated resources:
z
MSC starts the handover candidate query program. MS is waiting for the
handover.
Due to the congestion, the serving cell should be changed during call setup, such
as directed retry.
The "handover required" is transmitted once after an interval until one of the following
conditions occurs:
z
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Flow control
The flow control is adopted to prevent the entity from entering unstable status due to
overload. The flow control on the A-interface is implemented by controlling traffic at the
traffic source. 15-level flow control is provided. Flow control can be executed according
to user levels.
Classmark update
The purpose of classmark update is to inform the receiving entities of the classmark
information received by MS. In general, BSS receives the classmark information from
MS and then informs MSC. It is also possible that MSC sends the corresponding MS
classmark information to the new BSS via the A-interface after the handover is
completed.
Cipher mode control
The cipher mode control process allows MSC to send the cipher mode control
information to BSS, and startup user equipment and signaling cipher equipment with
correct key.
Queue indication
The purpose of the program is to inform MSC that BSS is to delay the allocation of
necessary radio resources. The program is valid only when traffic channel assignment
and traffic channel handover in BSS use the queuing function.
Load indication
The purpose of load indication is to inform the traffic status of a cell to all adjacent BSS
so that the handover service in a MSC can be under control. Within the valid time,
adjacent BSS will consider the traffic status of neighboring cells during handover.
3.1.7 TUP
I. Overview
When SS7 is used as telephone call control signaling, TUP (Telephone User Part)
specifies the necessary telephone signaling functions.
TUP can be used to control the switching of circuits used in connections. M900/M1800
MSC/SSP/IP also provides all functions according to the requirement of a mobile
network including handover and international roaming number.
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
telephone control signaling of TUP and must be processed by TUP. The length of the
SIF is variable, which can be determined by label, header code and signaling
information.
Each telephone message must include a label so that the message discrimination
function of MTP can determine whether it is a local message or a transfer message. If it
is a transfer message, the message routing function will select the proper signaling
route. TUP also uses the label to identify circuit numbers.
F
CK
16
SIF
8 n
SIO
LI
FIB FSN
BIB
BSN
n2
Header code
Signal
information H1
8n
H0
Label
Label
The label is an item of information, which forms part of every signaling message. It is
used by the message routing function at Message Transfer Part level 3 to select the
appropriate signaling route and by the User Part function to identify the particular
transaction (e.g. the call) to which the message pertains. The structure of TUP
message label is shown in Figure 3-14.
CIC
4
12
OPC
24
DPC
24
3-29
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Circuit Identification Code (CIC) identifies a speech circuit among multiple speech
circuits between DPC and OPC. CIC codes are allocated to telephone circuits
according to the principle negotiated or pre-determined:
For 2048kbit/s data channels, the lowest 5 bits of the 12-bit CIC identifies the speech
channel time slots (TS). The other 7 bits are number of the PCM system between the
Signaling Points of DPC and OPC.
For 8448kbit/s data channels, the lowest 7 bits of the 12-bit CIC identifies for the
channel time slots. The other 5 bits are number of the PCM system between the
Signaling Points of DPC and OPC.
2)
Header code
All telephone signaling messages include headers, each of which comprises the
header code H0 and header code H1. H0 identifies message group. H1 includes one
message code, or identifies the format of messages in complicated cases.
Messages are determined by header codes H0 and H1, as shown in Table 3-2.
Table 3-2 TUP messages
H0
H1
Message Type
Remarks
0001
0001
IAM
0001
0010
IAI
0001
0011
SAM
0001
0100
SAO
0010
0001
GSM
0010
0011
COT
Continuity signal
0010
0100
CCF
0011
0001
GRQ
0010
0001
ACM
0100
0010
CHG
Charging message
0101
0001
SEC
Switching-equipment-congestion signal
0101
0010
CGC
0101
0100
ADI
0101
0101
CFL
Call-failure signal
0101
0110
SSB
0101
0111
UNN
0101
1000
LOS
0101
1001
SST
3-30
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
H0
H1
Message Type
Remarks
0101
1010
ACB
0101
1011
DPN
0101
1100
MPR
0101
1111
EUM
0110
0000
ANU
0110
0001
ANC
0110
0010
ANN
0110
0011
CBK
Clear-back signal
0110
0100
CLF
Clear-forward signal
0110
0101
RAN
Reanswer signal
0110
0110
FOT
Forward-transfer signal
0110
0111
CCL
0111
0001
RLG
Release-guard signal
0111
0010
BLO
Blocking signal
0111
0011
BLA
Block-acknowledgement signal
0111
0100
UBL
Unblocking signal
0111
0101
UBA
Unblocking-acknowledgement signal
0111
0110
CCR
Continuity-check-request signal
0111
0111
RSC
Reset-circuit signal
1000
0001
MGB
1000
0010
MBA
1000
0011
MGU
1000
0100
MUA
1000
0101
HGB
1000
0110
HBA
1000
0111
HGU
1000
1000
HUA
1000
1001
GRS
3-31
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
H0
1000
H1
1010
Message Type
GRA
Remarks
Circuit group reset-acknowledgement message
LS
GMSC
VMSC
IAM
GRQ
GSM
IAI
ACM
ACM
Ring-back tone
ANC
ANC
Conversation
CBK
CBK
CLF
CLF
RLG
RLG
RLG
RLG
Figure 3-15 Proceeding of calls from fixed subscriber to idle mobile subscriber
IAM is the first message of a call set up. It contains the information of calling subscriber
category and the called mobile subscriber number (not including calling number).
After receiving the IAM, the GMSC requests for calling number (through GRQ
message). The calling number will be returned by the exchange through GSM
3-32
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
message. The GMSC assembles the IAM and calling number into IAI and sends it to
VMSC. When the address is completely received and the subscriber is idle, ACM is
sent back to the calling party. After the called party picks up the phone, the answer
signaling is sent back. Once the conversation is finished and the calling party clears
first, the outgoing MSC sends clearing message. The incoming MSC receives the
clearing message and will release the line immediately. It returns RLG message. If this
MSC is a tandem MSC, the clearing message will be forwarded to the next MSC.
2)
GMSC
VMSC
IAI
IAI
SSB, LOS, SST
SSB , LOS, SST
VMSC
Reject
call
CLF
CLF
RLG
RLG
UNN
CLF
RLG
GMSC
Reject
call
Controlling the duration of each timer in TUP signaling via data configuration.
3-33
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 3 Mobile Application Protocols
Controlling whether to send ST (Signal Terminal) signal after all types of numbers
in the signaling message are transmitted via data configuration.
Controlling whether to enable the special attributes specified in the national TUP
specifications of Thailand via software parameters, such as using ANU message
for charging, not supporting IAM and IAI message, using CON and FRL messages,
etc.
3.1.8 ISUP
I. Overview
ISUP (ISDN User Part) defines signaling messages, functions and processes that are
needed in the control of speech and non-speech services (such as circuit switching
data communication).
ISUP enables functions of TUP (Telephone User Part) & DUP (Data User Part) and
provides wide-range ISDN services.
ISUP protocol supports the basic bearer services, i.e. the establishment, monitoring
and release of 64 kbit/s circuit switching network connection between exchanges. In
addition, ISUP also supports the following supplementary services:
z
3-34
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Code
00000110
00001001
Block (BLO)
00010011
Block-acknowledgement (BLA)
00010101
00011101
00011100
00011110
00101100
Charging (CRG)
00110001
00011000
00011010
00010111
00101001
00011001
00011011
00101010
00101011
00101111
Connect (CON)
00000111
00000101
00010001
00100111
00100000
Feature (FAC)
00110011
00100001
00011111
00001000
00110110
00110111
Information (INF)
00000100
00000011
3-35
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Message Type
Code
00000001
00100100
00110010
00110000
Pass (PAM)
0010100
Release (REL)
00001100
00010000
00010010
Restore (RES)
00001110
00111000
00000010
Suspend (SUS)
00001101
Unblock (UBL)
00010100
00010110
00101110
00110101
00110100
00101101
3-36
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
MSC
GMSC
IAM
LS
IAM
ACM
ACM
ANM
ANM
Conversation
Calling party clears
REL
REL
RLC
RLC
REL
REL
RLC
RLC
On the reception of SETUP message from the calling subscriber, the MSC selects the
route according to the called number, the required connection type and network
signaling capability. Then it generates the IAM message and sends it to the GMSC. In
case of overlay codes, one or multiple SAM messages should also be transmitted.
The GMSC serves mainly in signaling relaying.
When the LS receives IAM and SAM messages, it sends the SETUP message to the
called party, which returns ALERT to the LS and rings if idle.
The LS sends back ACM and GMSC forwards it to the originating MSC. MSC sends
ALERT to the calling line after receiving ACM to inform the calling subscriber that the
called subscriber has been alerted.
The called subscriber answers the call and returns CONNECT message to the LS,
which sends back ANM.
GMSC forwards the ANM. The originating exchange sends the CONNECT message to
the calling subscriber after receiving ANM, informing the calling subscriber that the
called subscriber has replied and the call has been successfully established.
z
3-37
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
In the case of calling party clears, it sends the RELEASE message to the MSC. The
MSC forwards REL to GMSC, which sends back RELEASE_COMPLETE to release
the trunk. At the same time, it sends forward the REL. On receipt of REL, the LS sends
back RLC and releases the trunk, and notifies the called subscriber the end of the call.
In the case called party clears, LS sends backward REL. On receiving the REL, GMSC
sends back RLC to release the trunk, and sends backward REL. On receiving REL,
MSC sends back RLC to release the trunk, and notifies the calling party of the end of
the call.
Setting the parameter codes contained in the ISUP message and fields contained
in the parameters via data configuration.
Controlling the value of the field contained in the parameters and the
correspondent between the value and its logical meaning via data configuration.
Enabling random arrangement of the parameters in the ISUP message via data
configuration.
Enabling forced setting of certain fields of parameters in the ISUP message via
data configuration.
Creating the correspondence between the cause value and its logical meaning of
the ISUP message via data configuration.
Enabling the selection of ISUP abnormal clear procedure via data configuration.
Enabling the selection of number sending mode and format in ISUP signaling via
data configuration.
Controlling the duration of the timer in ISUP signaling via data configuration.
3.2 DSS1
This section describes ISDN network structure and the signaling used, applications of
DSSI supported by M900/M1800 MSC/SSP/IP, followed by functions, hierarchical
structure and signaling process of DSS1.
3-38
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
In general, the network only provides lower layer (layers 1~3 in the OSI model)
capabilities. In case, some value-added services need the higher layer (layers 4 ~7 in
the OSI model) functions inside the network, the higher layer functions can be realized
inside the ISDN network or provided by an independent service center.
The basic structure of the ISDN network is shown in Figure 3-18. ISDN Terminal
Equipment (TE) accesses the ISDN network via the standard user-network interface.
Packet switching
User-network
interface
TE
ISDN
LE
Circuit switching
ISDN
LE
User-network
interface
TE
Non-switching
connection
Common channel
signaling
3-39
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
SS7 (ISUP)
DSS1
User terminal
DSS1
MSC
MSC
SS7 (ISUP)
PABX
SS7 (ISUP)
ISDN switching equipment
Speech/trunk channel
Signaling channel
Layer 4-7
Layer 3
Network layer
Layer 2
Link layer
Layer 1
Physical layer
OSI Mode
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
D-channel: 16 kbit/s (D16) or 64 kbit/s (D64) signaling channel used to transmit the
circuit-switched signaling and packet data.
The physical channel of PRA interface adopts the PCM structure. It has the same rate
as the PCM primary group rate, which is 2048kbit/s. Twisted pair cables are used as
transmission media.
In the 30-channel PCM, each frame is divided into 32 basic Time Slots (TS). TS0 is
used for frame synchronization & error control and TS16 is used for signaling
transmission.
In M900/M1800 MSC/SSP/IP, PRA interface link layer signaling is processed in the
GCPC board. When the digital trunk board enters the working state, Semi-Permanent
Connection is set up between TS16 of PCM and a HDLC channel TS on GCPC board.
As PRA interface is the data communication interface, no multi-frame synchronization
exists in TS16 of PCM, which functions as the signaling link.
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 3 Mobile Application Protocols
The transmission error, format error and operation error on the data link are
checked.
The working speed between the receiver and the transmitter is coordinated.
In this mode, frames carrying user data are not numbered and no acknowledgement is
needed after the transfer.
z
Processes layer-3 messages and communicates with call control & resource
management entities of the exchange to implement call handling.
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 3 Mobile Application Protocols
Common part
Protocol discriminator
0
1 Byte
1 Byte
Call reference
Max. 2 bytes
Message type
1 Byte
Information unit
Information unit
.
.
.
3-43
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Calling
terminal
Originating
LE
Called
terminal B
Called
terminal A
Terminating
LE
SETUP
SETUP ACK
INFORMATION
CALL PROCEEDING
SETUP
SETUP
ALERTING
ALERTING
ALERTING
CONNECT
CONNECT
CONNECT ACK
RELEASE
CONNECT ACK
RELEASE COMPLETE
Data transmission
DISCONNECT
RELEASE
DISCONNECT
RELEASE
RELEASE COMPLETE
RELEASE COMPLETE
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
requirements (for example, if the bearer service features are the same, whether lower
layer protocols & higher layer protocols are consistent, whether they are compatible
with calling terminal types and whether the sub-address is in conformity).
In a call, several terminals might be compatible with the information in the SETUP
message. These terminals (such as called terminal A and called terminal B in the figure)
send the ALERTING message back to the network and a ringing tone to the subscriber.
The first ALERTING message is transferred to the originating exchange by the
terminating exchange and finally reaches the calling terminal, which will then send the
ring-back tone to the calling subscriber (or display the ALERTING information).
When one of the called terminals (terminal B in the example) replies, the terminal will
immediately send the CONNECT message to the network. The terminating exchange
transfers this message to the calling side and sends the CONNECT ACK message to
the terminal. The B-channel selected by the switches for the subscriber will be
immediately connected. The circuit connection from the calling subscriber to the called
subscriber at B is set up and can be adopted to transmit user information.
At the same time, the terminating exchange releases the other terminals like A that
were ringing and had not replied. As shown in Figure 3-22, the terminating exchange
sends the RELEASE message to the called terminal A. Terminal A stops ringing and
sends back the RELEASE COMPLETE message.
3.3 CAS
This part introduces the structure, functions, codes and signaling procedure of CAS,
and the support and realization of CAS by M900/M1800 MSC/SSP/IP.
3.3.1 Overview
Channel Associated Signaling system is still widely used in many countries. To
maintain the good interworking among equipment and protect operator's investment,
CAS system is essential in modern exchanges.
According to functions, CAS can be classified into line signaling and register signaling.
Line signaling is used to transmit the status information of trunk cables and subscribers,
for example, trunk line idle, seizure request, seizure acknowledgement, calling party
hook-on or called party hook-on, etc.
Register signaling is used to request and send the calling and called number, and to
send calling subscriber category, called subscriber status, and call type.
M900/M1800 MSC/SSP/IP CAS system can coordinate with SS7, including CASTUP,
TUPCAS, CASISUP, ISUPCAS.
3-45
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
The access of CAS is shown in Figure 3-23. GE16 and GSTU handle line signaling and
decimal pulse register signaling, GSRC provides register resources, and GSPC
completes service processing.
CNET
Oth er exch an ges
MFC
GE16/ GSTU
DL
Semi-permanen t
connection
GSRC
Active GSPC
Supports E1
M900/M1800 MSC/SSP/IP CAS system can maintain circuit and circuit group via
Man-Machine Line (MML), including such functions as blocking, unblocking, resetting
and status query. In the case of circuit hardware fault and recovery, hardware-oriented
blocking/unblocking can be automatically performed.
3-46
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Forward
Backward
Free/release
Seizure
Seizure acknowledgment
Answer
Clear backward
Clear forward
Block
Signal
symbol
I-1
Digit 1
I-2
Digit 2
I-3
Digit 3
I-4
Digit 4
I-5
Digit 5
I-6
Digit 6
I-7
Digit 7
I-8
Digit 8
I-9
Reserved
digit)
Digit 9
10
I-10
Discrimination digit
Meaning of signal
c
Remark
d
(discrimination
3-47
Digit 0
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Combina
tion
Signal
symbol
11
Meaning of signal
c
12
I-11
I-12
Remark
e
Connects to the
incoming
operator (code
11)
1) Connects to
the
delay
operator (code
12)
2) Request not
accepted
13
I-13
1) Connects to
test equipment
(code 13)
2) Not contains
satellite circuit
14
I-14
1) Requires the
incoming echo
canceller
2)
Contains
satellite circuits.
1) End of pulse
15
I-15
Unused signal
2)
End
identification
of
Signal symbol
Meaning of signal
Remark
II-1
Ordinary subscriber
II-2
Preferential subscriber
II-3
Maintenance equipment
II-4
Reserved
II-5
Operator
II-6
Data transmission
3-48
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Combination
Signal symbol
Meaning of signal
Remark
II-7
II-8
Data transmission
II-9
Preferential subscriber
10
II-10
11
II-11
12
II-12
13
II-13
14
II-14
15
II-15
Signal symbol
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
10
A-10
11
A-11
12
A-12
13
A-13
14
A-14
15
A-15
Meaning of signal
3-49
to
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Signal symbol
Meaning of signal
B-1
B-2
B-3
Subscriber busy
B-4
B-5
Unallocated number
B-6
B-7
B-8
B-9
10
B-10
11
B-11
12
B-12
13
B-13
14
B-14
15
B-15
3-50
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
Originating
exchange
Transit
exchange
Terminating
exchange
Seizure
Seizure ACK
P
A1
Q
A1
R
Seizure
Seizure ACK
A1
A
A1
B
A1
C
A1
D
A3
KD
B6
Reply
Disconnect (calling)
Disconnect(called)
Idle indicate
Reply
Conversation
Disconnect(calling)
Disconnect(called)
Idle indicate
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 3 Mobile Application Protocols
exchange analyzes the number and selects the outgoing trunk. Once the path between
the incoming trunk and outgoing trunk is established, the exchange will not longer
participate the transfer procedure of register signals, and the subsequent register
signals are transferred by the originating exchange to terminating exchange directly.
Controlling the duration of the timer in CAS signaling via data configuration.
3-52
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
MS
MSC
BSS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Call setup: The mobile subscriber originates the call and sends the setup message
to MSC, including the service information (BCIE: Bearer Capacity) and the called
number.
4-1
Technical Manual
M900/M1800 MSC/SSP/IP
2)
MSC Functions
Chapter 4 Mobile Service Procedures
Call proceeding: MSC first checks the BCIE requested by the mobile subscriber to
see if the network supports the call. If yes, data of the calling subscriber will be
retrieved from the VLR database for checking the subscriber attributes. After
confirming that the subscriber is authorized for the service, the call proceeding
message will be returned to the mobile subscriber.
3)
4)
5)
Alerting: MSC sends the alerting message to the calling subscriber and the calling
subscriber hears the ring-back tone.
6)
Answer (connect): MSC transfers the connect message to the calling party.
7)
After the call is finished, a Mobile Originated Call (MOC) bill will be generated.
4-2
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
MS
BSS
MSC
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Paging: MSC sends the paging information to the called mobile subscriber, which
mainly contains the IMSI/TMSI and the location area of the called mobile
subscriber. If the called MS does not response immediately, MSC/VLR may
resend the paging for several times.
2)
3)
Call setup (setup): MSC sends the call setup message to the called mobile
subscriber.
4)
Call confirmation (call_confirm): The called mobile subscriber returns the call
confirmation message.
5)
6)
7)
Called subscriber alerted (alerting): The called MS rings and sends the alerting
message to MSC.
8)
Called subscriber answering (connect): The called mobile subscriber hooks off to
answer the call, and sends the CONNECT message to MSC.
9)
Calling
subscriber
acknowledgement
(connect_ack):
MSC
sends
the
4-3
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
(2)
(1)
(4)
HLR
MSC
(3)
(5)
MSC /VLR
(6)
After accessing the mobile calling subscriber, MSC analyzes the called number. If
it is MSISDN, based on the called number, MSC will send a message to HLR
requesting route information.
2)
On receiving the request for route information from MSC, HLR sends a message
to the MSC where the subscriber is currently located (i.e. MSC/VLR) for fetching
MSRN.
3)
4)
5)
MSC sends initial address message to MSC/VLR according to the MSRN in the
route information message.
6)
When a fixed network subscriber calls a mobile subscriber, the above inter-office call
processing procedure will also occur to MSC.
4-4
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
For example, the tandem process where M900/M1800 MSC/SSP/IP acts as the GMSC
with TUP as incoming office and ISUP as outgoing office is shown in Figure 4-4.
MSC
/VLR
TUP
GMSC
ISUP
IAI
LS
IAM
ACM
ACM
ANM
ANC
Conversation
CLF
RLG
REL
RLC
When receiving an IAI message of TUP from MSC, GMSC sends the IAM of ISUP
to the fixed LS (fixed local switch) after route analysis and selection.
2)
When receiving the ACM message of ISUP from LS, GMSC translates it into ACM
message of TUP via signaling transfer and sends it to MSC.
3)
When receiving the ANM message of ISUP from LS, GMSC translates it into ANC
message of TUP via signaling transfer and sends it to MSC.
4)
5)
On receiving the calling party clear message (CLF) of TUP from MSC, GMSC
translates it into REL message of ISUP via signaling transfer and sends it to LS.
6)
TUP and ISUP release respective circuits and the communication is over.
The handover function of the mobile network is to maintain the established connection
of the subscriber when the mobile subscriber moves from one cell to another cell or
from one channel of a cell to another channel. BSS decides the handover according to
measurement reports from the MS.
4-5
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
BSS determines the handover according to the MS receiving level, receiving quality
and distance between the current BTS and the mobile subscriber. Cell traffic and
maintenance requirements are also important factors in handover determination. BSS
originates different handover requirements according to the determination results.
Handover controlled by MSC can be classified into intra-MSC handover, basic
handover and subsequent handover.
The location information about the current MS can be obtained from the Cell Global
Identity (CGI).
z
The location to be camped on by the mobile subscriber can be obtained from the CGI.
The controlling MSC (MSC-A) determines the destination MSC (MSC-B) code
4-6
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
according to the destination location information and initiates the handover request to
MSC-B.
Mobile class (Classmark2)
The mobile class identifies radio access features of the mobile subscriber such as
power level. It is used for the controlling MSC to inform the destination BSS to prepare
resources for MS access.
The signaling process of a basic handover is shown in Figure 4-5.
MS
MSC-A/
VLR
BSS-A
(1)
MSC-B/
VLR
BSS-B
MS
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
BSS-A is not satisfied with the MS radio channel quality and checks the nearby
location information. It requests MSC-A to control the handover with the suitable
nearby location area code as the destination information.
2)
MSC-A analyzes the handover request message to find that the destination is
within the coverage area of MSC-B. It requests BSS-B to prepare for MS access.
3)
MSC-B receives the handover request from MSC-A and asks for the handover
number from VLR as the addressing information for setting up the circuits from
MSC-A to MSC-B.
4)
5)
MSC-A selects the TUP route between MSC-A and MSC-B according to the
handover number and sends the initial address message to MSC-B.
6)
MSC-B receives the initial address message and confirms the handover number
before returning the address-complete message to MSC-A.
7)
4-7
Technical Manual
M900/M1800 MSC/SSP/IP
8)
MSC Functions
Chapter 4 Mobile Service Procedures
9)
10) MSC-B completes the connection and informs MSC-A of the successful setup and
handover through the TUP message.
As the controlling MSC, MSC-A plays the role as the controlling party in the whole MS
communication process (including the process after the handover succeeded).
4-8
Technical Manual
M900/M1800 MSC/SSP/IP
z
MSC Functions
Chapter 4 Mobile Service Procedures
CFU
CFU allows all the calls to this subscriber be forwarded to a third-party unconditionally
when this service is activated. The third-party here may be any subscriber of PLMN,
PSTN or ISDN, or a service station like voice mailbox
z
CFB
CFB allows the call to this subscriber be forwarded to a third-party if the called mobile
subscriber is busy. GSM specification defines Network Determined User Busy (NDUB)
and User Determined User Busy (USUB).
NDUB means that the subscriber status recorded by the network is busy (e.g. the
subscriber is engaged in a call). USUB means when the subscriber rejects the call after
being alerted.
z
CFNRc
CFNRc allows the call to a mobile subscriber be forwarded to a third party when the
radio channel connection between the network and the mobile station is interrupted.
The "unreachable" condition includes no response to paging, radio channel assignment
failure and MS switch-off.
z
CFNRy
When a mobile subscriber is alerted for a long time and the subscriber does not answer,
the call will be forwarded to a third party after the No Reply Timer expired.
When the call forwarding service is activated by a mobile subscriber, the call to such
subscriber will be forwarded to a third-party subscriber if the forwarding conditions are
satisfied. The detailed call setup procedure is the same as that of basic service call.
When subscribing to the forwarding service, the subscriber needs to register the
forwarded-to number. In addition, the service will not be available until it is activated.
The operation contrary to activation is deactivation, and the operation contrary to
registration is erasure. By default, the service is activated on registration.
The procedure of call forwarding registration and erasure is shown in Figure 4-6, which
is familiar to the procedure of activation and deactivation.
4-9
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
MS
Register CF
MSC
VLR
HLR
Register CF
Register CF
Register CF
Acknowledge
Acknowledge
Release complete
\Facility
Erase CF
Erase CF
Erase CF
Erase CF
Acknowledge
Acknowledge
Release complete
\Facility
The Call Hold (HOLD) service allows a served mobile subscriber, who is provisioned
with this supplementary service, to hold an active call and then, if desired, resume the
call. The Call Hold service is activated and available on registration.
The processing procedure of call hold is shown in Figure 4-7.
4-10
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
MSC/
VLR
MSa
MSb
Call going on
Hold request
Facility (notify)
Hold ack
Hold call
Retrieve request
Facility (notify)
Retrieve ack
Retrieve call
Note:
The subscriber whose call is held cannot have conversation with the subscriber who holds the call.
However, the call is still kept and charged.
The Call Wait (CW) service allows the subscriber to connect another incoming call
during an ongoing conversation. When there is another call waiting, prompt information
and buzzer sound will be given. The call wait service must be activated before it is
available.
The processing procedure of Call Wait service is shown in Figure 4-8.
4-11
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
MSa
MSC/
VLR
MSd
MSb
Call going on
Access request
and possible authentication
Set up
Set up
Call proceeding
Call confirm
Assign command
Assign complete
Alerting (Second
call waiting)
2)
3)
MSa performs 3+SEND operation to apply for a three-party call among MSa,
MSb and MSd. MSC sends the multiparty call messages to MSd, MSb and MSa
respectively.
4)
5)
MSa can also originate calls to other subscribers (e.g. MSc) to establish a four
party call through 3+SEND operation.
4-12
Technical Manual
M900/M1800 MSC/SSP/IP
MSa
MSC Functions
Chapter 4 Mobile Service Procedures
MSC/
VLR
MSd
MSb
Facility
(Build Mpty notify)
Facility
(Build Mpty ack)
Three-party call: MSa, MSb and MSd.
2)
3)
4)
MSC/VLR performs service check on MSa. If MSa passes the service check
successfully, MSC/VLR puts MSa-MSd and MSa-MSb through.
5)
6)
7)
4-13
Technical Manual
M900/M1800 MSC/SSP/IP
MSa
MSC Functions
Chapter 4 Mobile Service Procedures
MSC/
VLR
MSd
MSb
MSb answers or is
alerted
Facility
(Retrieve notify)
Facility
(ECT notify)
Facility
(ECT notify)
DISCONNECT/RELEASE/RELEASE COMPLETE
In the process of point-to-point short message transfer, a logic entity called Short
Message Gateway/Interworking MSC (SMS-G/IWMSC) plays an important role. This
functional module can be located in SMC or in MSC, depending on the specific
networking of the SMC.
4-14
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
In the point-to-point short message services, the MS interworks with MSC/VLR via BTS
and BSC by adopting the SAPI=3 connection on the L2 link (please refer to ETSI GSM
04.08 and 04.06 Specifications). BTS and BSC are responsible to set up the bearer
channel for short message interaction. End-to-end connection control and protocol
information element processing between MS and MSC/VLR are conducted according
to relative definitions in ETSI GSM 04.11.
Relative logic control in short message transfer is executed on the basis of ETSI GSM
09.02 among MSC/VLR, HLR and SMS G/IW MSC/VLR.
M900/M1800 MSC/SSP/IP forwards the short messages (including mobile originated
and mobile terminated short messages) submitted by the BSS side to the short
message service interworking module (SMS-IWMSC) and returns responses to BSS. It
also transfers the short messages sent by the SMS-GMSC to BSC and returns the MS
response to the SMS-GMSC. At the same time, it transmits the available messages
saved in the short message memory of the MS to VLR.
VLR provides the subscriber data related with short message services, checks the
subscribers short message service authority, and implements basic management
operations during the short message connection, including paging, search, encryption
and authentication.
Mobile Station Not Reachable Flag (MNRF) related with short message services
maintained in VLR can be set to record the short message transmission failure caused
by mobile subscriber unreachable, so as to maintain and manage the cooperation
function of the short message repeat mechanism.
Network entities involved in the cell broadcast short message service are slightly
different from those in point-to-point short message services. They mainly include:
z
In the cell broadcast short message service, the MS receives public broadcast
messages in a unidirectional manner. As it is different from the bi-directional
acknowledgement feature of the point-to-point short message service, its system
structure is also relatively simple.
CBC and BSC can be connected through SS7 and X.25 interfaces. However, ETSI only
provides some protocol stacks (ETR GSM 03.49) as the bearer layer of the broadcast
short message service between CBC and BSC. The communication protocols for the
end-to-end broadcast short message service between CBC and BSS is specified in
ETSI GSM 03.41.
In the actual operation, relative interface coordination is provided between CBC and
other public information sources (CBE, i.e. Cell Broadcast Editing console). When
constructing Short Message Center (SMC) and CBC, it is suggested that the interfaces
4-15
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
between SMC and other information source entities should be able to bear these two
different services.
SC
SMC G/IW
MSC
Message transfer
HLR
MSC/
VLR
MS
Delivery report
SM Delivery
Report Status
When the SMC receives a short message destined to a MS and the message can
be sent, or when it receives the short message re-transmission triggering
message, it will send the short message transmission request (including
transmission priority levels and multi-short message transmission flags) to
SMS-G/IW MSC through an interface, which then returns response.
2)
SMS-G/IW MSC originates SMMT route query (Send Routing Info For SM)
request to HLR in compliance with MAP protocol (ETSI GSM 09.02). It then
decides whether to send the ForwardShortMessage to the MSC serving the MS
according to the route information returned by HLR. If the route information is
returned, it will forward the short message to VMSC according to the MSC number
contained in the route information and wait for response. If the route information
query failure message is returned, it will send the error message to the SMC
together with the corresponding cause value so that the SMC can decide on the
short message re-transmission strategy. The transmission of this short message
will also be terminated.
3)
4-16
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
subscriber, whether to send the DTAP message (SAPI=3) containing the short
message directly to BSC, or whether to return the corresponding transmission
failure cause to SMS-G/IWMSC. In addition, if a failure cause of subscriber
unreachable type (e.g. no paging response) is received, MRNF will be marked in
VLR, so that VLR can send to HLR the ReadyForSM message to complete the
instant communication function when mobile subscriber appears the next time
(updating location or making calls).
If VMSC originates paging to MS and receives response, it will implement the same
procedures as in the ordinary MTC process, such as authentication, encryption and
TMSI re-allocation. In case of abnormalities, the sending of the short message will be
interrupted, and corresponding error cause will be returned to SMS-G/IW MSC. If the
MS access succeeds, VMSC will further send the short message to MS.
If VMSC issues the short message to MS via BSC and BTS, it will enter the state of
waiting for MS response. After receiving response from MS, including success/failure
message (together with failure cause value such as mobile subscriber memory
overflow and transmission protocol error), VMSC will send the response message to
the SMC step by step according to the above procedures.
4)
4-17
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
SMC G/IW
MSC
SC
HLR
MSC/
VLR
MS
Access request
Message transfer
2)
After receiving the short message, MSC will first query VLR the subscribers
current service attributes and check if this subscriber has subscribed to the short
message service or ODB (Operator Determined Barring) services. If there is any
restriction, MSC will return the corresponding error cause to MS, and the MS fails
in originating the short message. Otherwise, this short message will be sent (MO
forward short message) to SMS-G/IWMSC by MSC via MAP protocol (ETSI GSM
09.02). Meanwhile, MSC will wait for response from IWMSC about the short
message. MSC will return response to the MS according to the returned response
(the failure cause should be attached if the transmission failed).
3)
After receiving the short message sent from MSC, IWMSC will send the short
message to the SMC and wait for response. It will then transfer the response
returned from the SMC to MSC.
4)
The SMC will make the authentication as required after receiving the short
message submitted by IWMSC. If the authentication is passed, the short message
will be inserted in the real-time dispatching queue, and the success message will
be returned to IWMSC by the SMC. Otherwise, it will return the submission failure
message to IWMSC. Successfully submitted short messages will be placed in the
queue waiting for transmission and enter the aforesaid mobile-terminated short
message transmission process.
4-18
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
In the first case, when the SMC receives a short message with high priority, it will
directly attempt to send the message regardless of the current subscriber status. In
addition, SMS-G/IWMSC will attach the priority flag when querying HLR about the route
information. After receiving the route query request regarding the short message with
high priority, HLR will return the route information and necessary MWI state information
to SMS-G/IWMSC regardless of whether the MNRF and MCEF are repositioned as
MWI indicates. SMS-G/IWMSC will then send the short message to MSC. If the short
message transmission is successful, as SMS-G/IWMSC knows the subscriber MNRF
or MCEF is repositioned in HLR or non-empty SMC address queue exists in MWD
(MessageWaitingData), SMS-G/IWMSC will send the short message delivery status
report (ReportSMSDeliveryStatus) to HLR to indicate that the short message has been
successfully delivered. This will activate HLR to clear relative flags and alert SMC in
order to inform the SMC (or several centers) to make message re-transmission.
In the second case, when the mobile subscriber powers on the MS to make location
update or perform relative service operations such as Mobile Originated Call (MOC),
MSC will find out that the MNRF is repositioned and send the ReadyForSM message to
HLR together with the cause value of MS presence. After receiving the message, HLR
will clear the MNRF in MWI and alert the SMC (with AlertServiceCenter), which will
send the message to relevant SMS-G/IWMSC.
In the third case, if the subscriber deletes a short message when the short message
memory overflows, the MS will generate a ShortMessageMemoryAvailable message
and report it to MSC. The access of the message is the same as that of SMMO
(ShortMessageMemoryOverflow).
When
MSC/VLR
receives
the
SMMA
Technical Manual
M900/M1800 MSC/SSP/IP
MSC Functions
Chapter 4 Mobile Service Procedures
sent and put the message into the delivery queue to re-enter the mobile-terminated
short message process. Hence the short message service can be received by the
target MS within the shortest time and instant communications be ensured.
Compared with periodic re-transmission, the instant triggering has many obvious
advantages. It can reduce the SS7 signaling load in the PLMN system and send short
messages to subscribers in time. While periodic re-transmission is not likely to achieve
the instant communication effect, furthermore, increasing re-transmission frequency
would greatly increase signaling load on the network.
M900/M1800 MSC/SSP/IP has all the MSC functions in the three cases described
above.
(3)
HLR - A
HLR -B
(6)
( 4)
(2)
(9)
(7)
MSC/VLR1
(10)
( 5)
( 11)
GMSC
(8)
MSC/VLR2
(12)
(1)
MS1
MS2
Area A
Area B
2)
4-20
Technical Manual
M900/M1800 MSC/SSP/IP
3)
MSC Functions
Chapter 4 Mobile Service Procedures
After querying database, HLR-A finds that MS2 is roaming to area B. Thus, it
queries HLR-B for routing information.
4)
Upon receiving the request for routing information, HLR-B asks MSC/VLR2 for
MSRN.
5)
6)
7)
HLR-A
allocates
virtual
roaming
number
MSRN_V,
and
stores
the
9)
4-21
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
SSP Functions
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Table of Contents
Table of Contents
Chapter 1 Introduction to WIN ..................................................................................................... 1-1
1.1 Concept of Wireless Intelligent Network ............................................................................ 1-1
1.2 Features of Wireless Intelligent Network ........................................................................... 1-2
1.3 Services of Wireless Intelligent Network............................................................................ 1-3
1.3.1 Pre-Paid Service ..................................................................................................... 1-3
1.3.2 Familiarity Number Service ..................................................................................... 1-4
1.3.3 Cell and Time Discount ........................................................................................... 1-4
1.3.4 Wireless Advertisement Service ............................................................................. 1-4
1.3.5 UCB Service............................................................................................................ 1-4
Chapter 2 WIN Functions.............................................................................................................. 2-1
2.1 Standard CAMEL Phase 2 WIN......................................................................................... 2-1
2.1.1 Networking Structure of Standard CAMEL Phase2 WIN ........................................ 2-1
2.1.2 Service Triggering of Standard WIN ....................................................................... 2-3
2.2 WIN in OVERLAY Mode .................................................................................................... 2-4
2.2.1 Networking of WIN in Overlay Mode ....................................................................... 2-5
2.2.2 Service Triggering of Overlay WIN - Number Segment Triggering......................... 2-6
2.2.3 Smooth Evolution of WIN in OVERLAY Mode ........................................................ 2-7
2.3 Services Triggering via Access Code Mode...................................................................... 2-8
2.4 Access of gsmSRF Resource............................................................................................ 2-8
2.5 Supporting Virtual Roaming Number ................................................................................. 2-9
2.6 Supporting Overseas SSP Feature ................................................................................. 2-11
Chapter 3 Intelligent Call Handling.............................................................................................. 3-1
3.1 Overview ............................................................................................................................ 3-1
3.2 IN Basic Call State Model .................................................................................................. 3-1
3.3 Detection Point (DP) .......................................................................................................... 3-8
3.4 Triggering of Intelligent Service - TDP and Service Keys................................................ 3-12
3.5 Standard WIN Service Triggering - CSI Triggering ......................................................... 3-12
3.6 Description of CAMEL Subscriber Data .......................................................................... 3-13
Chapter 4 WIN Application Protocols.......................................................................................... 4-1
4.1 Introduction to CAP............................................................................................................ 4-1
4.2 CAP Protocol ..................................................................................................................... 4-1
4.2.1 GSM Protocol Family of CAMEL Phase 2 .............................................................. 4-1
4.2.2 Basic Principles of CAP Protocol ............................................................................ 4-2
4.2.3 CAP Protocol and MAP Protocol............................................................................. 4-2
4.3 CAP Operation................................................................................................................... 4-3
4.3.1 CAP Operation Types ............................................................................................. 4-3
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Table of Contents
ii
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 1 Introduction to WIN
1-1
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 1 Introduction to WIN
SMS is a computer system and normally provides service logic management, service
data management, subscriber data management, service monitoring and traffic
management. A new service logic created in SCE is input to SMS by the service
provider and then installed in SCP by SMS. In this way, the new service is available on
the communication network. A complete SMS system can change the execution
process of service logic by modifying the service data after receiving the service control
instructions from remote users. Generally, a provincial WIN is configured with one
SMS.
SCE generates new service logic according to the customer requirements and provides
friendly graphic editing interfaces for service designers. Users can use various
standard primitives to design the new service logic and define corresponding data for it.
After the designing, the service must pass strict verification and simulation tests,
ensuring not to affect the existing services on the communication network. After that,
the new service logic is sent by SCE to SMS and then operates after being loaded by
SMS to SCP.
IP is the special resources that assist to provide intelligent services. It normally enables
various speech functions, for example voice synthesis, play announcement, receiving
Dual-Tone Multi-Frequency dialing, and voice identification. IP may function as
independent physical equipment or as part of SSP. It is controlled by SCP and operates
as SCP service logic designates. IP is usually expensive and configured independently
on WIN because it is not economical to configure IP in every switching node of the
network.
1-2
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 1 Introduction to WIN
It supports SS7 signaling, and configuration of 14-bit and 24-bit signaling points.
It provides digital trunks and can coordinate with switching equipment of different
vendors.
It supports the basic switching service as well as the IN service in compliance with
CAMEL protocol.
These features are the objectives of WIN as well, that is, depending on the standard
communication between service-independent functional modules and functional
entities, to make efficient use of existing resources to provide various new services in a
quicker, simple and flexible manner.
1-3
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 1 Introduction to WIN
1-4
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 1 Introduction to WIN
roaming subscriber can use USSD function as long as the mobile network abroad to
which he/she roams supports USSD function. The mobile originated call can be
implemented through the following procedure: The PPS subscriber originates a USSD
request first. Then the home HLR forwards the request containing the subscribers
USSD service code and the called number to the home SCP. The SCP sets up calls to
the calling party and the called party respectively through the SSP. When both parties
answer the call, the SCP will connect the two calls.
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
2-1
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
HLR
MAP
gsmSCF
MAP
CAP
MAP
MAP
CAP
GMSC
gsmSSF
VLR
CAP
gsmSSF
MSC
gsmSRF
GMSC: Gateway Mobile Switching Center
VLR: Visitor Location Register
CAP: CAMEL Application Part
GsmSCF: GSM Service Control Function
GsmSRF: GSM Specialized resource Function
I. HLR
The HLR stores the data of subscribers requiring CAMEL support relevant to the
current subscription regarding O-CSI, T-CSI, TIF-CSI, U-CSI and SS-CSI. The
UG-CSI is stored as global data applicable to all CAMEL subscribers. The O-CSI is
sent to the VLR in case of Location Update or if the O-CSI is updated. The SS-CSI is
sent to the VLR in case of Location Update or if the SS-CSI is updated. The O/T-CSI
is sent to the GMSC when the HLR responds to a request for routing information. The
TIF-CSI, U-CSI and the UG-CSI are stored in the HLR only. The HLR may provide an
interface towards the gsmSCF for the Any Time Interrogation procedure.
II. GMSC
When processing the calls for subscribers requiring CAMEL support, the GMSC
receives an O/T-CSI from the HLR, indicating the GMSC to request instructions from
the gsmSSF. The GMSC monitors on request the call states (events) and informs the
gsmSSF of these states during processing, enabling the gsmSSF to control the
execution of the call in the GMSC.
III. MSC
When processing the calls for subscribers requiring CAMEL support, the MSC
receives a O-CSI from the VLR indicating the MSC to request instructions from the
2-2
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
gsmSSF. The MSC monitors on request the call states (events) and informs the
gsmSSF of these states during processing, enabling the gsmSSF to control the
execution of the call in the MSC. When processing an invocation of any of the
supplementary services ECT, CD and MPTY, the MSC receives a SS-CSI from the
VLR, indicating that a notification of the invocation of the supplementary service shall
be sent to the gsmSCF.
SCP Address: Address to be used to access the SCP registered for a particular
subscriber. The address is an E.164 number to be used for routing.
Service Key: The Service Key identifies the service logic to the SCP. Different
Service Keys may be associated to different TDPs.
2-3
Technical Manual
M900/M1800 MSC/SSP/IP
z
SSP Functions
Chapter 2 WIN Functions
Default Call Handling: The Default Call Handling indicates whether the call shall
be released or continued as requested in case of error in the SSP to SCP
dialogue. A default call handling is associated to each Service Key.
TDP (Trigger DP) List: The TDP List indicates on which detection point triggering
shall take place. O-CSI adopts only DP2 and T-CSI adopts only DP12.
DP Criteria: The DP criteria indicate whether the SSP shall request the SCP for
instructions.
For MO calls, when the call setup request is generated, MSC/gsmSSF obtains O-CSI
from VLR to trigger DP2. MSC/gsmSSF suspends the call and provides suitable
information to gsmSCF to wait for instructions from gsmSCF. According to the
instructions, MSC/gsmSSF will implement corresponding charging activity and
activate other control service events of the call. It makes processing to allow
continuous call handling, or release the call, or implement call connection according
to the SCP modified destination route address.
For MT calls, when the incoming call request is generated, GMSC/gsmSSF obtains
the subscriber T-CSI from HLR to trigger DP12. GMSC/gsmSSF suspends the call
handling and provides suitable information to GMSC/gsmSSF to wait for prompt from
gsmSCF. According to the instructions, MSC/gsmSSF will implement corresponding
charging and activate other control service events of the call. It makes processing to
release the call, or allow continuous call handling, or implement call handling with
modified information.
For MF calls,if call forwarding is generated in GSMC/gsmSSF, first GMSC/gsmSSF
obtains the subscriber T-CSI and O-CSI from HLR, then GMSC/gsmSSF triggers
DP12 processing procedure according to T-CSI, finally GMSC/gsmSSF triggers DP2
processing procedure according to O-CSI. If call forwarding is generated in
VSMC/gsmSSF, first GMSC/gsmSSF triggers DP12 according to MT processing
procedure, then GMSC/gsmSSF routes the call to VMSC/gsmSSF according to
MSRN from HLR, finally VMSC/gsmSSF queries O-CSI stored in VLR and triggers
DP2.
2-4
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
HLR
SCP
PSTN
SSP/IP
GMSC
MSC
MSC
MSC
MSC: Mobile Switching Center
HLR: Home Location Register
IP: Intelligent Peripheral
2-5
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
Note:
In actual networking, the SSP/IP is normally combined with MSC and GMSC. One or several MSC or
GMSC in the network can function as SSP/IP. In the above OVERLAY networking, M900/M1800
MSC/SSP/IP can serve as the independent SSP/IP, or as a MSC in the network while functioning as the
SSP/IP in the OVERLAY mode.
2-6
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
When SSP/IP receives the MT call from MSC, it will judge whether the called
subscriber is in the special number segment for intelligent subscribers according to
the called number. If the called number is in the special number segment for
intelligent subscribers, SSP/IP obtains the called service key and SCP address
information of the called subscriber by querying the data cofiguration with the number
segment. It obtains the location information of the calling subscriber according to the
special prefix of the called number. SSP/IP obtains the MSRN of the called subscriber
from the called HLR, which can be used to get the location information of the called
subscriber to trigger the called intelligent service process. The trigger point is set as
DP12. The SSP/IP reports the service key, calling number, called number & calling
location information to SCP and complete MT intelligent call according to the SCP call
control command.
When SSP/IP receives the incoming forwarding call from MSC, it will judge whether
the called subscriber is an intelligent subscriber according to the original called
number. If the original called number is in the special number segment for intelligent
subscriber, SSP/IP will obtain the calling service key and SCP address of the original
called subscriber by querying the data configuration according to the number
segment. Then it triggers forwarding intelligent service process. The trigger point is
set as DP2. Then SSP/IP reports the service key, calling number, called number &
forwarded-to location information to SCP and complete MF intelligent call according
to the SCP call control command.
For the forwarding call occurred at SSP/IP, SSP/IP will trigger DP12 according to MT
process. When call is forwarded in local office, SSP/IP will query the data
configuration again according to the called number to obtain the calling service key of
the called subscriber. Then it triggers forwarding intelligent service process. The
trigger point DP is set as DP2. The SSP/IP reports the service key, calling number,
called number, forwarded-to number and forwarded-to location information to SCP.
And the MF intelligent call will be completed according to SCP call control commands.
Note:
In the OVERLAY WIN mode, the operators may not mark the location of the calling party by adding
prefix in front of the called number, or mark the intelligent service subscriber by special number segment.
However, the service triggering principle is the same.
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
extra alternate routing of intelligent calls, thus increasing the operation cost of the
network. For this reason, the wireless intelligent network in OVERLAY mode should
be upgraded to the standard CAMEL Phase 2 wireless intelligent network.
M900/M1800 MSC/SSP/IP supports the smooth evolution to the standard wireless
intelligent network. Its step-by-step procedure for the evolution is described as
follows:
STEP 1: In the early stage of the construction of a wireless intelligent network,
M900/M1800 MSC/SSP/IP can be used as the tandem exchange in OVERLAY mode
to handle the intelligent calls from the MSC and GMSC that do not support CAMEL
feature.
STEP 2: According to the plan of the operator, MSC, GMSC and HLR in the network
can be upgraded to support CAMEL feature and reduce the mobile intelligent calls of
M900/M1800 MSC/SSP/IP tandem exchange.
STEP 3: When MSC, GMSC and HLR in the network have been upgraded to support
CAMEL feature, M900/M1800 MSC/SSP/IP can end the support of the wireless
intelligent network in OVERLAY mode and exists as an MSC/SSP/IP with CAMEL
feature. Alternatively, It can be modified into GMSC or independent IP.
2-8
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
SCP
gsmSCF
CAP
Internal
Interface
gsmSSF
gsmSRF
gsmCCF
SSP/IP
CAP: CAMEL Application Part
gsmSSF: GSM Service Switching Function
gsmCCF: GSM Call Control Function
SSP: Service Switching Point
2-9
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
MAP PHASE2+
HLR
2
MAP_PHASE2
MSC1
6
7
MSC2
10
12
1
A
MAP_PHASE2
11
GMSC/SSP
B
MAP PHASE2+
2)
MSC1 asks HLR for the roaming number of subscriber B. Since MSC1 does not
feature CAMEL function, it cannot get TCSI from HLR.
3)
4)
MSC1 connects to local GMSC/SSP via TUP signaling according to this virtual
roaming number.
5)
The local GMSC/SSP queries HLR with this virtual roaming number for the
routing information of subscriber B.
6)
7)
8)
The follow-up operations of HLR getting roaming number from MSC2 is same
with the standard procedure of MAP getting route information.
Identify the real MSISDN of the called party returned by HLR at MAP interface.
2)
Use the real MSISDN of the called subscriber, instead of the virtual roaming
number, to trigger the intelligent network service; and to originate the MAP
process to get the real route.
If the MAP version of the originating MSC of SRI is PHASE2+ or lower, and the
called subscriber has T_CSI, HLR will return virtual roaming number to HLR.
Based on the virtual roaming number, HLR can enable the MSC to access the
nearest GMSC/SSP via data configuration.
2)
If the MAP version of the originating GMSC/SSP of SRI is PHASE2+, and the
called number is a virtual roaming number, HLR will return T_CSI and subscriber
status information according to specified process on one hand; on the other hand,
2-10
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 2 WIN Functions
it returns the real MSISDN of the called subscriber to GMSC/SSP via the D
interface modified.
Enhancing the intelligent call processing when SSP and SCP signaling links are
faulty. When SSP and SCP signaling link are faulty, or call is barred at SCP,
M900/M1800 MSC/SSP/IP enables the cut-off or maintain the intelligent call
according to the operator's demands.
2-11
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
3-1
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
SC F
S LPI A
<Information flow>
SS F
IN Switching Manager
IN Switching State Model Inst.
< IN-SSM >
< IN-SSM events>
< Reso urce C ontrol>
Function
Group/Entity
Managed Data
Function Group Not
Required in INCS-1
<X XX> Header to Be Marked
Interactions that can be
specified by the provider
BC M
Bearer Control
C CA F
BCM manages all calls. For intelligent calls, a basic call state model (BCSM) is built
to manage them. In addition, it has a Detection Point (DP) mechanism. With the DPs,
the related events during a call can be reported to the intelligent layer and the
responses from the intelligent layer can be received.
z
FIM is responsible for judging whether the call information sent from BCM is an
intelligent call. If it is an intelligent call, it is sent to IN-SM for processing. If not, it is
sent to the non-IN feature manager for processing.
z
IN-SM is responsible for converting the call information identified inside the exchange
and reported from FIM/DPP into the standard CAP message and sending it to SCF, or
converting the standard CAP message into the call information identified inside the
exchange and sending it to FIM/DPP. It is the interface between SSF and SCF.
3-2
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
SCF
SSF/CCF
IN Switching Manager(IN-SM)
Non-IN Event Indicator
Non-IN Event Indicator
IN Control Request
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
actions of CCF required to establish and maintain the communication path for users.
It specifies a set of basic call and connection actions for CCF and indicates how these
actions are combined together to process a basic call and connection.
A BCSM component is composed of four elements: Point In Call (PIC), Detection
Point (DP), Transitions and Events, as shown in Figure 3-3.
Transition
Event 1
Event n
DP
PIC
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
example, it is possible that the home SCP of the calling party and that of the called
party are not the same in a PPS call. In this case, a call is controlled simultaneously
by two SCPs that control the originating BCSM and the terminating BCSM of SSP
separately.
V. Originating BCSM
DP10
O_Exception
O_Abandon
DP2
Collected_Info
Route_Select_
Failure
Analyse, Routing
O_Busy
& Alerting
O_No_Answer
O_Answer
DP9
DP4
DP5
DP6
DP7
O_Active
O_Disconnect
Null means the originating BCSM is in idle state without call information.
Authorize_Origination_Attempt means the exchange has detected a call originated
by the calling party and is performing authentication on the calling party.
z
When a call proceeds to DP2, it indicates SSP has analyzed and decided that the
calling party is an intelligent subscriber, and it reports the related information of this
call to SCP (through IDP information). SCP returns the configuration of other DPs, the
call duration for the calling party and other related information. The exchange routes
the call according to the called number. If it is successful, the call will be connected to
the called subscriber through Um interface or trunk signalling, and both the calling
and the called parties will be alerted.
3-5
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
If DP4 is encountered, it indicates the routing failed (for example, there is no idle
outgoing trunk). If DP5 is encountered, it indicates the called party is busy or not
reachable. If DP6 is encountered, it indicates ringing timeout for the called subscriber.
These DPs indicate important call events happened, causing failure of the call, and as
a result, the call state would enter Exception.
If DP7 is encountered, it indicates the called subscriber has hooked off to answer, that
is, the calling and the called parties will be connected through.
Before the calling party is connected with the called, DP10 will be generated if the
calling subscriber hooks on, indicating premature release by the calling party.
z
O_Active
Active means the calling party and the called party are connected and session starts.
If DP9 is encountered, it indicates calling party release or called party release, the call
is disconnected and BCSM is to enter the idle state.
3-6
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
T_Exception
T_Null
DP18
T_Abandon
DP12
Terminating_Attempt_Authorised
T_Busy
T_No_Answer
T_Disconnect
T_Answer
DP17
DP13
DP14
DP15
T_Active
T_Null
It indicates the terminating BCSM is in idle state. When a call proceeds to DP12, it
indicates the authentication of the called subscriber is completed. In this state, SSP
requests HLR for the subscription information of the called party and analyzes the
subscription information (if available) obtained.
z
It indicates the exchange has processed the subscription information of the called
party and will select a route to the called subscriber. SSP triggers the intelligent PPS
service at the called end according to the subscription information at DP12, and
reports the information related to the call. SCP returns the configuration of the related
DP, the call duration for the called party, etc. SSP selects the route according to the
called routing information. If the routing is successful, the called subscriber will be
alerted.
If DP13 is encountered, it indicates that a busy indication is received from the
destination exchange, or not reachable event is detected, or attempt to select the
route for the terminating leg fails. If DP14 is encountered, it indicates ringing timeout
3-7
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
for the called party. If DP15 is encountered, it means the called party hooks off and
answers the call.
z
T_Active
Active means the calling party is connected to the called party and the conversation
starts.
If DP17 is encountered, it means the subscriber has hooked on and the call is
disconnected.
Note:
The originating BCSM and the terminating BCSM are two models built by SSP for a call. The two models
describe the same call. For example, if the called subscriber hooks off to answer, DP7 will be generated
in the originating BCSM and DP15 will be generated in the terminating BCSM at the same time. For the
detailed description of every PIC at the originating end and the terminating end, refer to ETSI GSM
Phase 2+ 03.78 Specification.
1)
TDP
TDP is statically armed through the Data Management Console. TDP remains valid
until the data configuration makes it invalid.
The trigger detection of TDP depends on certain criteria which has a validity range.
The criteria used for TDP detection in IN CS (Capability Set) -1 phase include service
type, feature code, specified character string and access number. The selection
of criteria to trigger and detect an intelligent call requires setting the data related to
this criterion.
3-8
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
There are three arming routes in each criterion available for selection. One is
subscriber line/trunk line-based. When a TDP criterion is valid only for the intelligent
calls originated from a subscriber line or trunk line, this arming rule apply. The second
is group-based. When a TDP criteria is valid only for the intelligent calls originated by
subscribers in specified subscriber group, this arming rule apply. The third one is
office-based. When a TDP criteria is valid for the mobile intelligent calls originated
from any trunk source of the access system, this arming rule apply.
M900/M1800 MSC/SSP/IP uses the office-based validity range. That is why there is
an Office TDP Configuration Table in SSP data configuration.
2)
EDP
EDP is dynamically armed by the service logic during an intelligent call. When IN
service relationship has been built between SCF and SSF, it is configured dynamically
by means of sending CAP message.
The following disarming rules apply:
z
If an EDP is met that causes the release of the related leg, then all EDPs related
to that leg are disarmed.
If a call is released, then all EDPs related to that call are disarmed.
II. Types of DP
If an armed DP is met and it satisfies the DP criteria, a relationship can be
established between SSF and SCF.
A relationship between the gsmSSF/CCF and the gsmSCF for the purpose of
all/service logic processing is considered to be a CAMEL relationship. There are two
types of CAMEL relationships:
z
A CAMEL control relationship if the gsmSCF is able to influence the call handling
via the relationship.
A CAMEL monitor relationship if the gsmSCF is not able to influence the call
handling via the relationship.
For CAMEL control relationship, the information flow provided by SSF can start a
control relationship because a DP is met. This relationship can be in the context of the
existing control relationship or the context of the existing monitor relationship.
A relationship between the gsmSSF/CCF and the gsmSCF for the purpose of
management is considered to be a service management and control relationship.
If an armed DP is met, and it satisfies the DP criteria and is configured as CAMEL
control relationship, SSF can stop the call handling temporarily to allow SCF to affect
the subsequent call handling. When the call handling is suspended, SSF sends an
3-9
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
information flow to SCF and waits for response. This kind of detection point is called
Detection Point - Request (DP_R).
If an armed DP is met, and it satisfies the DP criteria and is configured as CAMEL
monitor relationship, SSF will not stop the call handling temporarily. SSF only sends
an information flow to SCF and does not wait for its response. This kind of detection
point is called Detection Point - Notification (DP_N).
Based on the above attributes, four types of DPs are identified:
z
CAMEL
control
relationship
Static
According to
the specified
DP
Enable control
relationship
Yes
All
Dynamic
None
Within existing
control
relationship
Yes
Call distribution,
call
re-routing
distribution
None
Within existing
control
relationship
No
Charging of any
services,
call
registration
and
call queuing
DP type
Configurati
on mode
TDP-R
EDP-R
EDP-N
Dynamic
Temporary
suspension
Service example
Note: The DP type used for service management relationship needs further study.
DP Type
Description
DP2 Collected_Info
TDP - R
DP4
Route_Select_Failure
EDP - N, EDP R
3-10
Technical Manual
M900/M1800 MSC/SSP/IP
CAMEL DP
SSP Functions
Chapter 3 Intelligent Call Handling
DP Type
Description
Indication that:
EDP - N, EDP R
DP6 O_No_Answer
EDP - N, EDP R
DP7 O_Answer
EDP - N, EDP R
DP9 O_Disconnect
EDP - N, EDP R
DP10 O_Abandon
EDP - N
DP5 O_Busy
DP Type
TDP-R
Description
Indication that the T-CSI is analyzed.
Indication that:
DP13 T_Busy
EDP-N,
EDP-R
DP14 T_No_Aanswer
EDP-N,
EDP-R
DP15 T-Answer
EDP-N,
EDP-R
DP17 T_Disconnect
EDP-N,
EDP-R
DP18 T_Abandon
EDP-N
3-11
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
SCP Address: Address to be used to access the SCP registered for a particular
subscriber. The address is an E.164 number to be used for routing.
Service Key: The Service Key identifies the service logic to the SCP. Different
Service Keys may be associated to different TDPs.
Default Call Handling: The Default Call Handling indicates whether the call shall
be released or continued as requested in case of error in the SSP to SCP
dialogue. A default call handling is associated to each Service Key.
TDP (Trigger DP) List: The TDP List indicates on which detection point triggering
shall take place. O-CSI adopts only DP2 and T-CSI adopts only DP12.
DP Criteria: The DP criteria indicate whether the SSP shall request the SCP for
instructions.
For MO calls, when the call setup request is generated, MSC/gsmSSF obtains O-CSI
from VLR to trigger DP2. MSC/gsmSSF suspends the call and provides suitable
information to gsmSCF to wait for instructions from gsmSCF. According to the
instructions, MSC/gsmSSF will implement corresponding charging activity and
activate other control service events of the call. It makes processing to allow
continuous call handling, or release the call, or implement call connection according
to the SCP modified destination route address.
For MT calls, when the incoming call request is generated, GMSC/gsmSSF obtains
the subscriber T-CSI from HLR to trigger DP12. GMSC/gsmSSF suspends the call
handling and provides suitable information to GMSC/gsmSSF to wait for prompt from
gsmSCF. According to the instructions, MSC/gsmSSF will implement corresponding
3-12
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 3 Intelligent Call Handling
charging and activate other control service events of the call. It makes processing to
release the call, or allow continuous call handling, or implement call handling with
modified information.
O/T-CSI includes:
SS-CSI includes:
Notification criteria. This data indicates for which supplementary service notifications
shall be sent. The supplementary services that may be indicated are ECT, CD and
MPTY.
gsmSCF address. Address to be used to access the gsmSCF for a particular
subscriber. The address shall be an E.164 number to be used for routing.
3)
An indication that the HLR shall send the location information of the called subscriber.
An indication that the HLR shall send the subscriber state of the called subscriber.
3-13
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
GSM02.78
GSM03.78
GSM09.78
GSM09.02
GSM03.18
GSM02.78 protocol defines the service features that CAMEL can realize, and
describes the basic principles of realizing charging, roaming and supplementary
service coordination for CAMEL technique.
GSM03.78 protocol specifies the distribution of CAMEL function entities and the state
transition of individual function entities.
GSM09.78 specifies in detail the CAP operations between CAMEL function entities as
well as TCAP coordination, error handling and dialogue negotiation mechanism.
GSM09.02 protocol is an original protocol of GSM protocol family. In order to support
CAMEL, MAP Phase II+ 09.02 protocol has been expanded to support the operations
related to CAMEL.
4-1
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
For SSF, SCF, SRF and SDF function entities acting as the corresponding physical
entities, there are several different interfacing schemes. In Huawei TELLIN system, the
communication between SCF and SSF or SRF is made by using the TCAP message
based on the connectionless service SCCP, as shown in Figure 4-1.
gsmSCF
gsmSSF
TC_BEGIN (InitialDP)
TC_CONTINUE(RequestReportBCSMEvent)
TC_CONTINUE (ApplyCharge)
TC_CONTINUE (Connect)
......
TC_END (ReleaseCall)
Figure 4-1 CAP Message sent by using TCAP message based on connectionless service SCCP
4-2
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
Mobile Application Part (MAP) provides GSM system with the necessary signaling
functions. These functions are required by Signaling System No.7 (SS7) to provide the
necessary services (such as the speech and non-speech application in PLMN). In GSM
Phase 2+, a group of MAP operations are added and some of the existing MAP
operations are modified especially to meet the requirements of CAMEL network.
Both CAP and MAP are protocols on the application layer and are the users of TCAP.
Their positions in SS7 are shown in Figure 4-2.
M900/M1800 MSC/SSP/IP communicates with SCP through the TCAP of SS7 and
uses SCCP connectionless service for transmission. Its application protocol follows
CAP protocol.
OMAP
CAP
MAP
B
S
S
A
P
Layers
6
5
4
Layers
3
2
1
TCAP
I
S
U
P
T
U
P
SCCP
MTP
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
The correspondence between the operations and the information flows is listed in Table
4-1.
Table 4-1 CAP operations and their types
Information Flow
Operation
Type
Same
Apply Charging
Same
Same
Same
Same
Same
Cancel
Same
Connect
Same
Connect to Resource
Same
Continue
Same
Same
Same
Same
Same
Initiate DP
Same
Release Call
Same
Same
Reset Timer
Same
Play Announcement
Same
Same
Same
Activity Test
Activity Test Response
4-4
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
Note:
"Same" in the operation column means the operation name is the same as the name of the information
flow.
detects
that
the
call
period
duration
indicated
in
parameter
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
CallInformationReport
This operation is used to send specific call information for a single call party as
requested by the gsmSCF in a previous CallInformationRequest operation. The report
is sent at the end of a call/call party connection, which is indicated by one of the events
specified below.
If a gsmSSF is requested by gsmSCF to report a call information event, gsmSSF
contains the suspended call information report. If gsmSSF reports the call information
event, the call information report suspension will be released.
CallInformationRequest
This operation is used to request the gsmSSF to record specific information about a
single call party and report it to the gsmSCF using the CallInformationReport operation.
When the call information is collected according to the requirement of service
operations and management, gsmSCF can send the "CallInformationRequest"
message to gsmSSF to collect the following call related information:
z
Release Cause
4-6
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
ConnectToResource
This operation is used to connect a call from the gsmSSF to a specialized resource.
After successful connection to the gsmSRF, the interaction with the caller can take
place. The gsmSSF relays all operations for the gsmSRF and all responses from the
gsmSRF.
Continue
This operation is used to request the gsmSSF to proceed with call processing at the DP
at which it previously suspended call processing to await gsmSCF instructions. The
gsmSSF continues call processing without substituting new data from the gsmSCF.
DisconnectForwardConnection
This operation is used in the following two cases:
To clear a connection to a gsmSRF:
This operation is used to explicitly disconnect a connection to a resource (gsmSRF)
established previously with a ConnectToResource operation. It is used for a forward
disconnection from the gsmSSF. An alternative solution is the backward disconnect
from the gsmSRF, controlled by the "DisconnectFromIPForbidden" parameter in the
PlayAnnouncement and PromptAndCollectUserInformation operations.
To clear a connection to an assisting SSF:
This operation is sent to the non-assisting gsmSSF involved in an assist procedure. It is
used to disconnect the temporary connection between the gsmSSF & the assisting
SSF and the assisting SSF & its associated gsmSRF.
EstablishTemporaryConnection
This operation is used to create a connection between a gsmSSF and an assisting SSF
as part of a service assist procedure. It can also be used to create a connection
between a gsmSSF and a gsmSRF, for the case where the gsmSRF exists in a
separately addressable PE (an IP).
Note that assistingSSPIPRoutingAddress should contain routing digits, a correlationID
and an scfID for the establishment of temporary connection between PLMNs. No
bilateral agreement exists between the involved network operators to transfer
correlationID and SCFiD as separate parameters.
EventReportBCSM
This operation is used to notify the gsmSCF of a call related event previously requested
by the gsmSCF in a RequestReportBCSMEvent operation. The monitoring of more
than one event could be requested with a RequestReportBCSMEvent operation, but
each of these requested events is reported in a separate EventReportBCSM operation.
4-7
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
FurnishChargingInformation
This operation is used to send charge related information to a logical call record. This
logical call record is CAMEL specific. The first FCI of a call leg leads to the generation
of a logical call record. Receipt of subsequent FCIs on the same leg shall overwrite the
contents of the logical call record. When additional FCIs are to be used, an EDP-R shall
be armed in order to be able to apply FCI before the termination of the call record
generation.
If an FCI operation is received for the called party when the gsmSSF is in state
'Monitoring', or is suspended in one of the following DPs, then the charging information
shall be included in the logical call record for the leg that has been or is to be
established:
z
Collected_Info,
O_Answer,
Terminating_Attempt_Authorised, or
T_Answer
If an FCI operation is received for the called party when the gsmSSF is suspended in
any other DP, then the charging information shall be included in the logical call record
created for the last failed or disconnected called party.
Initial DP
This operation is sent by the gsmSSF after detection of a TDP-R in the BCSM, to
request the gsmSCF for instructions to complete the call. The "Initial DP" operation
contains various information needed by gsmSCF, including the calling number, called
number, calling subscriber location information, called subscriber location information
and subscriber status.
PlayAnnouncement
This operation is sent to gsmSSF/gsmSRF from gsmSCF. It is used for the user
interaction process of intelligent call proceeding. gsmSCF instructs gsmSRF to play
announcement to the user. gsmSSF functions as the signaling trunk in the process.
Upon receiving the operation, gsmSSF will transfer the operation to relative gsmSRF.
PromptAndCollectUserInformation
This operation is sent to gsmSSF/gsmSRF from gsmSCF. It is used for the user
interaction process of intelligent call proceeding. gsmSCF instructs gsmSRF to play
announcement to the user via this operation to require the subscriber to input relative
information (for example, account information and user password). After collecting the
input of the subscriber, gsmSRF sends message "Prompt And Collect User
Information" to gsmSCF. gsmSSF functions as the signaling trunk in the process. Upon
receiving the operation, gsmSSF will transfer the operation to the controlled gsmSRF.
4-8
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
ReleaseCall
This operation is sent to gsmSSF from gsmSCF.
This operation is used by the gsmSCF to tear down an existing call at any phase of the
call for all parties involved in the call. The operation can only be sent within a control
relationship and is not allowed in a monitor relationship. This operation shall not be sent
to an assisting gsmSSF.
RequestReportBCSMEvent
This operation is sent to gsmSSF from gsmSCF.
It is used to request the gsmSSF to monitor for a call-related event (e.g., BCSM events,
such as busy or no answer) and then send a notification back to the gsmSCF when the
event is detected.
ResetTimer
This operation is sent to gsmSSF from gsmSCF.
It is used by the gsmSCF to refresh the TSSF application timer, in order to avoid the
TSSF time-out at the gsmSSF.
SendChargingInformation
This operation is sent to gsmSSF from gsmSCF.
This is used to send e-parameters from the gsmSCF to the gsmSSF. If charge advice
information is received from the gsmSCF, it shall replace the Charge Advice
Information (CAI) which would be generated by the MSC and inhibit any further
generation of CAI by the MSC. Further processing of the CAI by the MSC shall be in
accordance with the GSM Advice of Charge Supplementary Service.
Note:
If charge advice information is received from the gsmSCF after charge information has been generated by
the MSC and sent to the MS, the behavior of the service may be unpredictable or incorrect; the service
designer should therefore ensure that the first set of CAI is sent to the gsmSSF before charge information
is sent to the MS.
SpecializeResourceReport
This operation is sent to gsmSCF from gsmSRF.
This operation is used as the response to a PlayAnnouncement operation when the
announcement completed indication is set.
4-9
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
Connect to Resource
Apply Charging
Continue
Release Call
Play announcement
Active Test
PortConnected
ProvideAvailDN/AvailDNProvided
BridgePorts / PortBridged
ConnectOnePort
II. ProvideAvailDN/AvailDNProvided
Issued by gsmSCF to gsmSRF, this operation is used to apply for an available DN
number from gsmSRF, as the only identity for a call to connect to SRF. As the response
to ProvideAvailDN operation, AvailDNProvided is used to report the DN allocated by
GsmSRF to gsmSCF.
4-10
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 4 WIN Application Protocols
III. ConnectOnePort
Issued by gsmSCF to gsmSRF, this operation requests gsmSRF to connect the call to
the resource obtained via Provide Avail DN operation.
IV. PortConnected
This operation is issued by gsmSRF to gsmSCF. It will be executed after the
ConnectOnePort operation is successfully executed.
V. BridgePorts / PortBridged
This operation is sent to gsmSRF from gsmSCF. The gsmSRF is requested to bridge
the speech timeslots corresponding to the DNs according to the two DNs in the
operation. As the response to the BridgePorts operation, PortBridged reports the
operation result.
4-11
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
When receiving the call, MSCa/SSP/IP will analyze the called number. If it is an
MSISDN, MSCa/SSP/IP will send SRI message to HLRb of the called subscriber,
so as to get the MSRN of the called subscriber.
2)
MSCa/SSP/IP analyzes the calling number. If the calling party is a PPS subscriber,
it will convert the called number prefix into the toll area code representing the
actual location of the caller and place it in the parameter Location Number in IDP
message. It then queries the correspondence between the number segment and
SCP, and sends IDP message to SCPa.
3)
After receiving IDP message, SCPa will analyze the account of the calling party. If
it is a valid account, SCPa will determine the charging rate of the caller according
to the caller location and the called number, make out the maximum call duration
based on the card balance, and send RRBE, AC and Continue messages to
MSCa/SSP/IP.
4)
When MSCa/SSP/IP receives Continue message, it will connect the call according
to the MSRN of the called party. When the conversation is over and the calling
party or the called party hooks on, MSCa/SSP/IP will submit the charging report
and the hook-on event.
5-1
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
MSCa/SSP/IP
SCPa
HLRb
MSCb/VLR
IAM
SRI
SRI_ack(MSRN)
triggering by
number segmet
IDP
Charging the
calling part
RRBE
AC
Continue
IAM(MSRN)
ACM
ANM
...
ACR
ERB
RC
CAP message
MAP message
ISUP message
IAM: Initial Address Message
SRI_ACK: SRI Acknowledge
RRBE: Request Report BCSM Event
ACM: Address Complete Message
ACR: Apply Charging Report
RC: Release Call
Figure 5-1 Call procedure (PPS subscriber calling ordinary PLMN subscriber)
When MSCa/SSP/IP receives the call, it analyzes the calling number. If the calling
party is a PPS subscriber, it will convert the called number prefix into the toll area
code representing the actual location of the caller, place it in the parameter
Location Number in IDP message. Then it will find the corresponding SCP
address according to the calling number segment and send IDP message to
SCPa.
5-2
Technical Manual
M900/M1800 MSC/SSP/IP
2)
SSP Functions
Chapter 5 WIN Service Procedures
When SCPa receives the IDP message, it will analyze the caller account first. If
the account is valid, it will determine the charging rate according to the actual
location (Location Number) of the caller and the toll area code of the called party,
make out the maximum call duration based on the charging rate, and send RRBE,
AC and Continue messages to MSCa/SSP/IP.
3)
4)
When the calling party or the called party hooks on and the session is ended,
MSCa/SSP/IP submits the charging report and the hook-on event.
MSC/SSP/IP
SCPa
HLRb
PSTN
IAM
Triggering by
number segmen
IDP
RRBE
Charging the
calling party
AC
Continue
IAM
ACM
ANM
...
ACR
ERB
RC
CAP message
MAP message
ISUP message
IAM: Initial Address Message
RRBE: Request Report BCSM Event
ACM: Address Complete Message
ACR: Apply Charging Report
RC: Release Call
IDP: Initial DP
AC: Apply Charging
ANM: Answer Message
ERB: Event Report BCSM
Figure 5-2 Call procedure (Overlay PPS subscriber calling PSTN subscriber)
5-3
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
the service will be triggered by number segment. The call processing procedure is
shown in Figure 5-3.
1)
When receiving the call from other exchange in Overlay mode, MSCa/SSP/IP will
analyze the called number first. If it is an MSISDN, MSCa/SSP/IP will send SRI
message to HLRb of the called subscriber, so as to get the MSRN of the called
subscriber.
2)
MSCa/SSP/IP analyzes the called number. If the called party is a PPS subscriber,
it will convert the called number prefix into the toll area code representing the
actual location of the caller, place it in the parameter Location Number in IDP
message. Then it will query the number segment-SCP correspondence and send
IDP message to SCPb.
3)
When the SCPb receives the IDP message, it first analyzes the account of the
called subscriber. If it is a valid account, SCPb will determine the charging rate of
the called party according to the actual location and the home location of the called
party, make out the maximum call duration based on the card balance, and send
RRBE, AC and Continue messages to MSCa/SSP/IP.
4)
When MSCa/SSP/IP receives Continue message, it will connect the call according
to the MSRN of the called party. When the conversation is over and the calling
party or the called party hooks on, MSCa/SSP/IP will submit the charging report
and the hook-on event.
5-4
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
MSC/SSP/IP
SCPb
IAM
HLRb
MSCb/VLR
SRI
SRI_ack(MSRN)
Triggering by
number segment
IDP
Charging the
called party
RRBE
AC
Continue
IAM(MSRN)
ACM
ANM
...
ACR
ERB
RC
CAP message
MAP message
ISUP message
IAM: Initial Address Message
SRI_ACK: SRI Acknowledge
RRBE: Request Report BCSM Event
ACM: Address Complete Message
ACR: Apply Charging Report
RC: Release Call
Figure 5-3 Call procedure (PSTN subscriber or ordinary GSM subscriber Calling Overlay PPS subscriber)
When receiving the call from other exchange in Overlay mode, MSCa/SSP/IP will
analyze the called number first. If it is an MSISDN, MSCa/SSP/IP will send SRI
message to HLRb of the called subscriber, so as to get the MSRN of the called
subscriber.
2)
MSCa/SSP/IP analyzes the calling number. If the calling party is a PPS subscriber,
it will convert the called number prefix into the toll area code representing the
5-5
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
actual location of the calling party, place it in the parameter Location Number in
IDP message. Then it will query the number segment-SCP correspondence and
send IDP message to SCPa.
3)
When SCPa receives the IDP message, it will analyze the caller account first. If it
is a valid account, SCPa will determine the charging rate of the caller according to
the caller location and the called number, make out the maximum call duration
based on the card balance, and send RRBE, AC and Continue messages to
MSCa/SSP/IP.
4)
5)
When the SCPb receives the IDP message, it will analyze the account of the
called subscriber. If it is a valid account, SCPb will determine the charging rate of
the called party according to the actual location and the home location of the called
party, make out the maximum call duration based on the card balance, and send
RRBE, AC and Continue messages to MSCa/SSP/IP.
6)
When MSCa/SSP/IP receives Continue message, it will connect the call according
to the MSRN of the called party. When calling party or the called party hooks on
and the conversation is ended, MSCa/SSP/IP submits the charging report and the
hook-on event to SCPa and SCPb respectively.
5-6
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
MSCa/SSP/IP
IAM
SCPa
SCPb
HLRb
MSCb/VLR
SRI
SRI_ack(MSRN)
Triggering by calling
number sement
IDP
Chargingthe calling party
RRBE
AC
Continue
IDP
RRBE
AC
Continue
IAM(MSRN)
ACM
ANM
...
ACR
ERB
RC
ACR
ERB
RC
CAP message
MAP message
ISUP message
Figure 5-4 Call procedure (Overlay PPS subscriber calling Overlay PPS subscriber)
5-7
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
SCP
MSC/SSP/IP
IDP
ACM
ANM
Connect To Resource
Prompt And Collect User Info
PC Result
Play Announcement
Announcement ......
Specialized Resource Report
Release Call
IDP: Initial DP
ACM: Address Complete Message
The PPS subscriber dials the recharging service number. After SSP analyzes the
called number and knows it is a hotline number, it will trigger IDP for the home
SCP of the PPS subscriber.
2)
When SCP checks that the called number is a hotline number, it will send
3)
4)
ConnectToResource to SSP.
6)
5-8
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
GMSC
SSP
SCPa
HLRa
Continue
ANM
ERB(DP7,LEG ID=1)
ProvideAvailDN
AvailDNProvided
ConnectOnePort
PortConnected
ICA(MSISDN B)
IAM(MSISDN B)
RRBE(DP7-R,LEG ID=2)
Continue
ANM
ERB(DP7,LEG ID=1)
ProvideAvailDN
AvailDNProvided
BridgePorts
PortsBridged
Communication
REL
ACR
ERB(DP9)
RC
ACR
ERB(DP9)
REL
RC
MAP signaling
CAP signaling
ISUP signaling
Technical Manual
M900/M1800 MSC/SSP/IP
1)
SSP Functions
Chapter 5 WIN Service Procedures
Subscriber A originates USSD request to the home HLR. The USSD request
contains USSD service code and the MSISDN of subscriber B.
2)
Via analyzing USSD service code, the home HLR knows that subscriber A is
applying for UCB service. So it transfers the USSD request to SCPa.
3)
The SCPa checks whether the subscriber has the authority to use UCB and sends
USSD response containing the check result to subscriber A via the home HLR.
4)
If the subscriber has the UCB authority, SCP will analyze the account of
subscriber A. If it is a valid account, SCPa will determine the charging rate
according to the home location and the current location of subscriber A, make out
the maximum call duration based on the card balance. Then it sends ICA, RRBE
and Continue messages to SSP, asking SSP to set up call with subscriber A.
5)
6)
After subscriber A answers, SSP sends ERB message to SCPa, reporting DP7
(O_answer).
7)
8)
9)
10) Upon receiving the ConnectOnePort message, SSP connects the call (to
subscriber A) with the multiparty service resource. At the same time, it plays music
prompting subscriber A to wait for the connection to subscriber B. After it is
successfully connected, SSP sends OnePortConnected message to SCPa,
informing the successful operation.
11) SCPa sends ICA, RRBE and Continue messages to SSP, asking SSP to set up
call with subscriber B.
12) Based on the address information of subscriber B contained in ICA message, SSP
originates call to subscriber B via GMSC.
13) When the MS of subscriber B rings, SSP sends ERB message to SCPa, reporting
DP7 (O_answer).
14) Upon receiving ERB message, SCPa sends ProvideAvailDN message to SSP.
15) After receiving ProvideAvailDN message, SCP allocates multiparty service
resources and relevant DN for the call to subscriber B, and reports the
AvailDNProvided message containing the DN allocated to SCP.
16) Based on the ConnectOnePort message issued via AvailDNProvided, SCP
requests the SSP to connect the call (to subscriber B) to the resource obtained via
Provide Avail DN operation.
17) Upon receiving the ConnectOnePort message, SSP connects the call (to
subscriber B) with the multiparty service resource. After the connection is
5-10
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
5.6.1 RBT
B is a RBT subscriber and the calling party is a PSTN or GSM subscriber. The RBT
service is implemented through OVERLAY. Figure 5-7 shows its service signaling flow.
MSCa/SSP/IP
IAM1
SCPb
HLRb
MSCb/VLR
AIP
SRI
SRI_ack(MSRN)
Triggering by
number segment
IDP
Connect
IAM2(AIP accees code)
IAM3(MSRN)
ACM2
ACM3
ANM2
Timeslot bridge
connection
ACM1
CPG
Playing ring
back tone
ANM3
Timeslot bridge
disconnection
ANM1
...
REL
RLC
CAP message
MAP message
ISUP message
5-11
Technical Manual
M900/M1800 MSC/SSP/IP
SSP Functions
Chapter 5 WIN Service Procedures
Note:
The signaling flow between the AIP and the SCP is not included in the above flow.
1)
Upon receiving the RBT call through OVERLAY from another MSC, the
MSCa/SSP/IP analyzes whether the called number is MSISDN first. If so, the
MSCa/SSP/IP sends the SRI message to the called HLRb to obtain the called
MSRN;
2)
The MSCa/SSP/IP analyzes the called number. If the called number falls within
the range of number segment of RBT service, it triggers the RBT service and
sends the IDP message to the SCPb;
3)
Upon receiving the IDP message from the MSCa/SSP/IP, the SCPb judges
whether the subscriber has subscribed to the RBT service. If so, the SCPb sends
the Connect message to the MSCa/SSP/IP. In the message the SCPb provides
the corresponding AIP of the subscriber and indicates that the subscriber has
registered to the RBT service.
4)
The MSCa/SSP/IP sends the IAM message to the MSCb/VLR of the called party.
Meanwhile, it sends the IAM message to the AIP according to the AIP access code,
requiring connecting with the AIP;
5)
Upon receiving the ACM message returned from the MSCb/VLR, the
MSCa/SSP/IP saves this message and waits for the connection with the AIP;
6)
Upon receiving the ANM message returned by the AIP, the MSCa/SSP/IP
establishes bridge connections
7)
The MSCa/SSP/IP sends the CPG message to the AIP, informing the AIP to play
the customized ringback tone. It also sends the saved ACM message to the
forward MSC;
8)
AIP directly plays the customized ringback tone or enables the voice detect
function according to the CPG message. The voice detect function is used to
check the ringback tone sent by the MSCb/VLR on the forward circuit from the
MSCa/SSP/IP to the AIP. When the ringback tone is detected, the AIP plays the
customized ringback tone on the backward circuit from the AIP to the
MSCa/SSP/IP;
9)
Upon receiving the ANM message sent by the MSCb/VLR, the MSCa/SSP/IP
disconnects the AIP and releases the corresponding resource. The follow-up flow
is the same as the normal conversation flow.
5-12
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
Technical Manual
M900/M1800 MSC/SSP/IP
Table of Contents
Chapter 1 Operation and Maintenance Functions ..................................................................... 1-1
1.1 Setting User Authorities ..................................................................................................... 1-1
1.1.1 Command Group..................................................................................................... 1-1
1.1.2 Management of User Account................................................................................. 1-2
1.1.3 Logon Time ............................................................................................................. 1-2
1.2 Data Configuration and Management................................................................................ 1-2
1.2.1 Data Configuration .................................................................................................. 1-2
1.2.2 Data Operation and Management........................................................................... 1-4
1.3 Alarm.................................................................................................................................. 1-6
1.3.1 System Structure..................................................................................................... 1-6
1.3.2 Reporting of Hardware Alarm Information .............................................................. 1-7
1.3.3 Reporting of Software Alarm Information................................................................ 1-9
1.3.4 Alarm Box and Alarm Console ................................................................................ 1-9
1.3.5 Alarm Level and Type ........................................................................................... 1-10
1.4 Performance Measurement ............................................................................................. 1-11
1.4.1 Structure of Performance Measurement System.................................................. 1-11
1.4.2 Types of Performance Measurements.................................................................. 1-13
1.4.3 Functions and Features of Performance Measurement System .......................... 1-14
1.4.4 Standard Compliance............................................................................................ 1-15
1.5 Charging .......................................................................................................................... 1-15
1.5.1 Structure of Charging System ............................................................................... 1-16
1.5.2 Bill Storage ............................................................................................................ 1-17
1.5.3 Bill Types............................................................................................................... 1-19
1.5.4 Bill Format ............................................................................................................. 1-19
1.6 Routine Maintenance....................................................................................................... 1-20
1.6.1 Equipment Maintenance and Control.................................................................... 1-21
1.6.2 Trunk/Signaling Management and Control ........................................................... 1-23
1.6.3 Real-time Tracing and Query ................................................................................ 1-24
1.6.4 VLR Subscriber Management ............................................................................... 1-25
1.6.5 Other Maintenance Functions ............................................................................... 1-25
1.7 Software Patching............................................................................................................ 1-27
1.7.1 Basic Concepts ..................................................................................................... 1-27
1.7.2 Features of Software Patch................................................................................... 1-27
1.7.3 Structure of Software Patching System ................................................................ 1-28
1.7.4 Software Patching Operation ................................................................................ 1-29
1.8 System Testing ................................................................................................................ 1-30
1.9 Task Management ........................................................................................................... 1-32
Technical Manual
M900/M1800 MSC/SSP/IP
ii
Technical Manual
M900/M1800 MSC/SSP/IP
Technical Manual
M900/M1800 MSC/SSP/IP
Technical Manual
M900/M1800 MSC/SSP/IP
z
Frame description data: configuration data of frames, such as frame type, frame
number and physical location.
Board description data: data of boards, such as board type, slot position, frame
where the board resides, and configuration information required for fulfilling some
board functions.
Office direction: when the trunk lines of local office are directly connected to
another switching equipment, the route to this system is called office direction.
Sub-route: a subset of route, indicating the physical path to and from another
switching equipment. It is composed of trunk groups which can be distributed to
different modules, that is, sub-route can span modules.
Trunk circuit: each E1 line contains 64kbit/s 32 timeslots, and each timeslot can be
used as a speech channel. Such channel is called a trunk circuit.
Local office information: signaling point network ID of local office, MSC number,
provisioning of SP or STP functions.
1-3
Technical Manual
M900/M1800 MSC/SSP/IP
Signaling link: it is made up of signaling data link and signaling terminals. The
signaling link functions, together with a signaling data link as bearer, provide a
signaling link for reliable transfer of signaling messages between two directly
connected signaling points. It is a basic unit forming signaling link set and
signaling route.
GT (Global Title): used for identifying a signaling point or sub-system within the
global range.
VIII. Others
Besides the data described above, there are many other system parameters such as
software parameter and timers. However, they involve many aspects and can only be
modified by system administrator (super user), the configuration of such data is not
described here.
1-4
Technical Manual
M900/M1800 MSC/SSP/IP
And DB_?.DAT is the data file to be loaded in SPM, where "?" indicates the module
number (1~160). Different SPMs are loaded with different data files.
Functions about data operation management include data format conversion, data
setting, CRC, data backup, and automatic format setting during BAM restart.
1-5
Technical Manual
M900/M1800 MSC/SSP/IP
V. Continue of data format conversion and data setting during BAM restart
There may be unfinished data format conversion and data setting tasks when BAM is
shut down in abnormal conditions (for example power failure). When BAM restarts, the
system will check if there are unfinished tasks and will automatically continue these
tasks.
1.3 Alarm
M900/M1800 MSC/SSP/IP provides perfect alarm system, which is responsible for
monitoring the operation of the equipment, collecting fault information, and alerting
maintenance engineers.
Peer fault
Clock fault
Channel fault
Online/offline status
The logical errors that can not be found through hardware detection can be checked
through software detection, including:
z
CRC check
Memory check
1-6
Technical Manual
M900/M1800 MSC/SSP/IP
Other software
module
MSC
Alarm service
module
Alarm module
Alarm
console
WS
Alarm
box
BAM
Board status indicators (for the meanings of indicators on boards, please refer to
Maintenance System Online Help or M900/M1800 MSCMSC/SSP/IP Hardware
Description Manual)
1-7
Technical Manual
M900/M1800 MSC/SSP/IP
The fault information of iGWB (Charging Gateway) is firstly sent to GSPC board for
handling, and then reported by GSPC.
The reporting path of hardware fault information and alarm information is shown in
Figure 1-2.
AMP
(Active)
BAM
BCP
CCM (GBAC\GFSN)
NCC
GCNU
/GSNU
/GBDR
GQSI
BCC
GMHI
LIM Frame
GPWS
GSRC
GE16/GECS/
GECP/GOBC/
GSTU
CDP
GCPC
GCKS
GALM
AMP
(standby)
non-LIM
Frame
GPWS
GSPC
GAMD
GCKD
PWC
iGWB
GSPT
Alarm information of clock and power supply reported through GALM serial port.
Level 1: CCM
Level 2: master nodes (boards with HDLC link processing function, such as NCC,
GQSI and BCC, etc.)
Level 3: slavery nodes (boards communicating with CCM through master nodes,
for example, GMHI is the slavery node of GQSI, GCPC of BCC, etc.)
All boards in the system are intelligent, i.e., they can monitor their status, operation
conditions and their external interfaces, test and indicate operation status, and report
abnormality to higher-level devices.
Higher-level devices automatically monitor the operation status of devices of lower
level, report detected abnormality to higher-level, and meantime perform proper
handling, such as path blocking, active/standby switchover, system reconstruction and
hierarchical reset, etc.
1-8
Technical Manual
M900/M1800 MSC/SSP/IP
Visible and audible alarm information of 4 levels on real-time basis: critical, major,
minor and warning, which can be easily distinguished from the sound.
English voice prompt, whose volume can be manually adjusted. Alarm sound for
major, minor and warning can be turned off, while alarm sound for critical alarm
can not be shut down.
Remote alarming and remote control over alarm sound. Alarm sound can be sent
to remote loudspeaker connected (30m away). Alarm sound can be turned on or
off through remote switch, which can be set at a distance 30m from the alarm box.
These two functions allow users to operate and control alarm box remotely.
For detailed explanation and usage of the alarm box, please refer to Universal Alarm
Box User Manual.
1-9
Technical Manual
M900/M1800 MSC/SSP/IP
Detailed explanation of alarm records and real time display of alarm tips.
Print of displayed alarm information (in detailed explanation format) and real time
print function.
For detailed explanation and operation related to alarm console, please refer to online
help of alarm console.
Recovery alarm: alarm generated when the failed equipment or abnormal function
recovers and becomes normal. It is in one-to-one correspondence to the fault
alarm.
Critical alarm: Fault alarm or event alarm which may lead to the system down,
such as the faults in main control board (e.g. BCP, CDP, AMP), network board (e.g.
1-10
Technical Manual
M900/M1800 MSC/SSP/IP
GSNU, NCC, GBDR), communication control board (GBAC, GFSN) and clock
board (e.g. GCKS, GCKD), Bus Communication Control (BCC) board, etc.
z
Major alarm: Board/line fault alarm and event alarm which affects a certain range,
such as Service Processing board (GSPC) failure, interface board (GQSI, GE16,
GSTU, GMHI) failure, GCPC failure, and communication link failure.
Minor alarm: Ordinary fault alarm and event alarm that describes the operation
state of boards or lines, such as resource board (GSRC, GSPT, GECP) fault, PCM
failure, application failure/seizure timeout of shared resource, MFC code
transceiving error/timeout.
Warning: Prompt that will not affect system performance, such as board
switchover
The maintenance engineers can handle the alarms by referring to the alarm information,
troubleshooting methods, and online help displayed on the alarm console.
1-11
Equipment
information
.
.
.
Signaling
processing
Signaling
information
AMP
Performance
service module
Service module
Call processing
information
Maintenance
interface
Call control
Technical Manual
M900/M1800 MSC/SSP/IP
BAM
GSPC
Other software
modules of MSC
Event
Counter
Measurement
task
management
Time
management
Event
1-12
BAM
performance
service module
Technical Manual
M900/M1800 MSC/SSP/IP
VLR Measurement
Technical Manual
M900/M1800 MSC/SSP/IP
BSSMAP Measurement
Explicit report function. The user can select any measurement items in the same
measurement function type for the same measurement object, and register them
in the same measurement task.
Supporting 3 time segments per day. Measurement period can be defined by day,
week or month, with the range of 1~100 days. For example, one measurement
task can be set to be executed at 9:00~11:00, 13:00~16:00 and 20:00~21:00 on
Sundays and Saturdays.
For both call times and traffic, the real-time scanning method of meter and traffic is
adopted to enable the real-time measurement of call times and traffic. Scanning
accuracy of 1m and 1s for traffic measurement ensures the correctness of
measurement.
1-14
Technical Manual
M900/M1800 MSC/SSP/IP
Providing template. The user can self define template with certain special
measurement task, measurement item set, measurement time and measurement
object. With those self-defined templates, the user can perform similar
maintenance operation promptly.
Providing operation wizard. With the operation wizard, the user can easily perform
relevant O&M tasks, such as registering measurement task, querying
measurement result, outputting query result and self defining measurement item,
etc.
The measurement of GSM basic services at NSS side specified in GSM 12.04.
1.5 Charging
For each call, M900/M1800 MSC/SSP/IP collects call detailed record to generate the
original bill and sends them to the Billing Center. The Billing Center uses the
information in the bill to generate detailed bills for charging subscribers and for
inter-network accounting. In this process, M900/M1800 MSC/SSP/IP only provides
necessary charging information to the network operator, instead of calculating the
charges for the calls.
1-15
Technical Manual
M900/M1800 MSC/SSP/IP
Call
control
module
Billing
Center
iGWB
Bill pool
MSC
WS
MSC/SSP/IP
Charging System
1-16
Technical Manual
M900/M1800 MSC/SSP/IP
Original bills
Host bill pool
Bill sorting
Bill format
conversion
Final bills
Billing Center
1-17
Technical Manual
M900/M1800 MSC/SSP/IP
Max. size of bill file: 100kB---infinite. But it should not be more than 2M bytes
considering the security when transmitting on WAN.
The structure of the bill file name is: "Prefix" + "Date" + "_" + "Path No." + "_" +
"Sequence No." + "."+ "Suffix":
The prefix and suffix can be defined by the user. "Date" and "Path No." are optional
items. In "Date" item, the "Year" is 4 digits, "Month" is 2 digits and "Day" is 2 digits.
"Path No." is 2 digits, "Sequence No." is 8 digits (with the range from 00000000 to
99999999). The files under each path are numbered separately.
For example:
Shenzhen20000609_01_00000088.dat
Means the bill generated in Path 1 in Shenzhen office on June 9, 2000.
After the billing center obtains the bills, the bills in iGWB can be deleted actively or
passively. Correspondingly, there are two kinds of directories for storing of bill files.
1)
Bills will not be deleted actively after the billing center obtain the bills
E:\BillBack\backdata\chl_x\Date\
This directory is read-only for the Billing Center, and the directory name cannot be
modified. Root directory is set freely by user when installing the system. "x" is the Path
No. The bills files are put under different directories of the path according to date, and
the files under respective paths are numbered separately.
For example:
E:\BillBack\backdata\chl_1\20000505\Shenzheng20000609_01_00000000.dat
In this case, the billing center will not delete those bill files in iGWB already obtained.
The iGWB is responsible for deleting such bill files under the directory "\backdata"
when the max. period (usually, 7 days) set by user is due.
2)
After collecting the bill files or iGWB actively sends bill files to billing center, the
billing center actively delete the bill files in iGWB.
1-18
Technical Manual
M900/M1800 MSC/SSP/IP
There are two directories. One is the same as the one described above. It is read-only
for the Billing Center and the name cannot be modified.
The other directory is E:\BillBack\backdatabak\chl_x\
This directory is read-write allowable for the Billing Center, and the directory name
cannot be modified. The directories under the path are not defined according to dates.
Instead, all files are put together.
For example:
E:\BillBack\backdatabak\chl_1\Shenzheng20000609_01_00000000.dat
In this case, the billing center will delete the bill files under the directory of \backdatabak
after iGWB actively sends these bill files.
Mobile Originating Call (MOC) bill: bill generated when local mobile subscriber
originates calls.
Mobile Terminating Call (MTC) bill: bill generated when local mobile subscriber is
the called party.
Gateway Incoming (GWI) bill: bill generated when the calling party is a subscriber
of foreign network and the called is a subscriber of local network.
Gateway Outgoing (GWO) bill: bill generated when the calling party is a subscriber
of local network and the called is a subscriber in foreign network.
Transit bill: bill generated when both the calling and the called parties are not in
local office, and local office serves as TMSC (Transit MSC).
Call Forwarding (CFW) bill: bill generated for the called party when the called party
is mobile subscriber in local office and call forwarding occurs.
Short Message Service (SMS) bill: bill generated for short message originating
and terminating services.
1-19
Technical Manual
M900/M1800 MSC/SSP/IP
Use of basic services (based on originating point, destination, date, duration, and
bearer service).
AMP
NCC
GSPC
CDP
Commands for NCC and CDP (such as query and release of control memory in
NCC, CDP resource and channel state query, release status query etc.) are
transmitted transparently by AMP to NCC and CDP, which directly reply the
maintenance commands from BAM.
1-20
Technical Manual
M900/M1800 MSC/SSP/IP
Real-time tracing and query: including tracing & monitoring, connection query, port
signaling tracing, subscriber status tracing, interface tracing, subscriber interface
tracing, etc.
Switchover control
1-21
Technical Manual
M900/M1800 MSC/SSP/IP
Switchover procedure
Switchover of the boards in auto switchover mode is decided by the system. The
switchover of the boards in controlled switchover mode can be implemented via the
man-machine command. When switchover occurs, system will generate an
autonomous message and return the switchover result. If switchover fails, failure cause
will be returned.
During switchover process, smooth processing and traffic restructuring will be
implemented by the system automatically.
2)
Board reset
3)
Various board information can be queried, including board status and board type.
4)
Board loading
Status query: Status query of control memory, port, circuit and clock output of
specific GE16/GETS board.
Control operation: GE16/GETS port reset, GE16 2K network board reset; starting
frame self-loop, local-loop and remote-loop, release of self-loop, etc.
1-22
Technical Manual
M900/M1800 MSC/SSP/IP
Note:
GSPT board software can support different languages by loading syntax analysis module. With 8 syntax
analysis modules loaded, it can support 8 languages.
V. Semi-permanent connection
Maintenance functions concerning SPC include:
z
Query of SPC information according to the module No., SPC start No. and end No.
Suspending SPC without releasing the TS (Time Slot) occupied by the subscriber.
Stopping SPC and releasing the TS occupied by the subscriber (not deleting from
database).
enables
real-time
dynamic
tracing
and
monitoring
on
the
receiving/sending and processing of TUP, MTP, ISUP and SCCP messages on SS7
signaling links. Information about the status of the SS7 signaling link and coordination
of signalings between exchanges can also be obtained.
2)
This function enables the query of status information of SS7 signaling link, destination
and route, and provides the operation status of SS7 signaling system.
4)
Technical Manual
M900/M1800 MSC/SSP/IP
Continuity test of speech channels using SS7 signaling can be implemented to judge
the operation status of the speech channels.
5)
Query of TUP and ISUP SS7 signaling system status, unblock, block and reset of SS7
signaling circuit, and query of circuit status.
6)
SCCP Management
The receiving/sending and processing of line signaling and register signaling can be
dynamically traced and monitored in real time. Thus, the information about the status of
the CAS link and the coordination of signalings between exchanges can be obtained.
2)
The user can unblock, block or reset CAS circuits and query circuit status.
1-24
Technical Manual
M900/M1800 MSC/SSP/IP
analysis of signaling messages. The other is binary mode. The file saved in this mode
can be opened in the service maintenance system and displayed as same as that when
the signaling is traced. The message tracing function is very useful in routine
maintenance. It helps to quickly locate connection failure, remove faults, and view
inter-exchange coordination.
Load control
1-25
Technical Manual
M900/M1800 MSC/SSP/IP
Note:
Calculation of CPU occupancy:
CPU occupancy = 1
2)
Setting of loading
When a module has the software fault that is unable to recover, hierarchical reset and
restart function can be implemented via man-machine commands to remove the fault
and restore the system to normal operations. To change the software version and
reload data, the restart function can also be used. (This function is particularly useful in
case of remote maintenance.)
There are four levels of restart:
z
Level 2: Bills will be kept. Subscribers in communication and under connection will
be affected. No data and program will be loaded.
Level 3: Bills will be kept. Subscribers in communication and under connection will
be affected. Data will be loaded. No program will be loaded.
Level 4: Bills will be kept. Subscribers in communication and under connection will
be affected. Data and program will be loaded.
3)
This is to set the backup mode of the system. Two modes can be adopted: no backup
and normal backup.
Query of operation status: Query the status of GCKS reference source (including
frequency offset and status) and GCKS error interval.
1-26
Technical Manual
M900/M1800 MSC/SSP/IP
z
Parameter setting: The system administrators can set the GCKS stratum,
phase-locked loop mode, operational mode, reference source, and available
reference sources.
Any software patch is developed based on a basic version, and can be used only for
that basic version. When the patches for a basic version reach certain amount,
software upgrading is needed, and the patches for the new version may be released.
2)
For each error, one or more patches may be developed, and each patch is assigned a
patch No. The patch No. starts from 1, and the theoretical largest number is 65535
(actually it is limited by memory space).
A patch file includes all the patches for the same basic version. Patches are released
by means of patch files.
1-27
Technical Manual
M900/M1800 MSC/SSP/IP
Corresponding patch explanation file is also provided together with the patch file. It
describes the detailed information of each patch, such as the problems to be solved by
this patch file, and patching precautions, etc.
3)
Simple operation
Note:
Because online software patching directly affects the operation of software in CPU, only system
administrator can perform such operation.
4)
Self-healing capability
In case abnormality occurs, such as system power failure or restart, patched modules
in M900/M1800 MSC/SSP/IP can automatically restore to previous patched status
without manual intervention.
The function of patching creation tools is to organize one or more patches and create a
patch file for certain software version. The creation of patch file is completed offline.
2)
BAM patch management module is a part of BAM software, its main functions include:
z
Providing users with command interface for managing and maintaining patches.;
Maintaining module patch configuration table and module patch status table to
keep them consistent with that in MSC according to related patch operation
commands of the user and returned information from MSC.
3)
MSC patch management module is a part of Host software, its main functions
include: Processing related patch commands from BAM and maintenance
interface.
Maintaining module patch status table to keep it consistent with that in BAM
according to users operation commands.
1-28
Technical Manual
M900/M1800 MSC/SSP/IP
Deactivated state: patch is in patch area but not activated and can not be
executed.
Activated state: patch is activated and can be executed, this is a trial running state.
Running state: patch is running and can not be deactivated, only removing can be
done.
Idle state
Deactivated
state
RMV
RMV
Running state
ACT
RMV
RUN
DEA
Activated state
Running state is formal running state. When system restarts, only the patches in
running state can be integrated in system operation. As activated state is a temporary
state, the patch in this state will not be put into operation.
When system does not need the patches any more, they can be removed with
command RMV PATCH.
1-29
Technical Manual
M900/M1800 MSC/SSP/IP
Test of Central Switching Network: including switching network chip test, check of
the connection between switching network chips, CNET frame bus test.
Through test of speech path: including the speech paths between SPM and CNET,
GSRC and CNET, GSPT and CNET, and the information exchange path between
GCPC and CNET.
Test of speech path BER: test the quality of speech paths on equipment delivery.
1-30
Technical Manual
M900/M1800 MSC/SSP/IP
Test task 1
Create
Test components
Execution
command
Test commands
Record
.
Configuration
command
Test commands
.
Parallel test
control
.
WS
Test data
Test task n
Create
MSC
Configuration
command
Execution
command
Record
Test report
Test task
Each user can set up several test tasks. Each test task includes timing parameter,
configuration command, execution command and test report.
Test tasks include routine test tasks and immediate test tasks. Immediate test task does
not need timing parameter and is executed immediately after setup. While routine test
task includes timing parameter and is executed automatically and periodically.
2)
Configuration command
Each test task has a configuration command specified to test multiple similar devices
numbered in sequence, such as subscriber circuit test, board test and self-test of test
system.
3)
Execution command
When the time specified for the routine test task is due, routine test will be started to
generate several execution commands. Execution commands are generated on the
basis of configuration command. If one configuration command is specified to test N
devices, the configuration command will be extended to generate N corresponding
execution commands. Each command is responsible for testing one device and
generating test record. After execution, routine test task automatically deletes the
execution command.
4)
Test report
Each routine test task has several test reports. Each time the routine test is started, a
test report will be generated. And the test records generated by execution commands
will be added item by item to the test report.
5)
1-31
Technical Manual
M900/M1800 MSC/SSP/IP
M900/M1800 MSC/SSP/IP provides one set of test equipment for certain number of
hardware devices.
As one test task can submit several thousand execution commands at a time, many
parallel test queues are set in Parallel Test Control module. Each queue corresponds to
one set of test equipment. Parallel Test Control module can queue execution
commands of all tasks. The commands using the same test equipment are put in the
same queue and tested one by one. The commands using different test equipment are
put in different queues and are not related to one another, these tests can be executed
at the same time to increase the service efficiency of test equipment.
6)
Immediate test
Immediate test is a special task, which makes diagnosis test on the specified device to
obtain results as soon as possible. Therefore, after the user adds a configuration
command to immediate test task, the system immediately generates execution
commands to start tests. The test data will be displayed immediately on the Client.
1-32
Technical Manual
M900/M1800 MSC/SSP/IP
occurs. And on-line modification of command script is possible. The user can also
specify a fixed time to execute batch command.
1.9.3 Macro
The system records the MML commands executed by the user within certain time
interval in command script and names it. The command script defined is a macro. The
macros defined will be added to the macro navigation tree, from which the user can
select and execute it in batch process mode.
1-33
HUAWEI
M900/M1800 MSC/SSP/IP
Technical Manual
Appendix
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Table of Contents
Table of Contents
Appendix A Standard Compliance ..............................................................................................A-1
A.1 ITU-T Recommendations ..................................................................................................A-1
A.2 ETSI Specifications ...........................................................................................................A-6
Appendix B Terminology..............................................................................................................B-1
Appendix C Abbreviations and Acronyms .................................................................................C-1
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
exchanges
G.165 (03/93) Echo cancellers
G.168 (04/97) Digital network echo cancellers
G.703 (10/98) Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44
736 kbit/s hierarchical levels
G.711 (11/88) Pulse code modulation (PCM) of voice frequencies
G.722 (11/88) 7 kHz audio-coding within 64 kbit/s
G.744 (11/88) Second order PCM multiplex equipment operating at 8448 kbit/s
Q.700 (03/93) Introduction to CCITT Signaling System No.7
Q.701 (03/93) Functional description of the message transfer part (MTP) of Signaling
System No.7
Q.702 (11/88) Signaling data link
Q.703 (07/96) Signaling link
Q.704 (07/96) Signaling network functions and messages
Q.705 (03/93) Signaling network structure
Q.706 (03/93) Message transfer part signaling performance
Q.707 (11/88) Testing and maintenance
Q.708 (03/99) Assignment procedures for international signaling point codes
Q.709 (03/93) Hypothetical signaling reference connection
Q.710 (11/88) Simplified MTP version for small systems
Q.711 (07/96) Functional description of the Signaling Connection Control Part
Q.712 (07/96) Definition and function of signaling connection control part messages
A-1
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
performance
Q.721 (11/88) Functional description of the Signaling System No.7 Telephone User
Part (TUP)
Q.722 (11/88) General function of telephone messages and signals
Q.723 (11/88) Formats and codes
Q.724 (11/88) Signaling procedures
Q.725 (03/93) Signaling performance in the telephone application
Q.730 (09/97) ISDN User Part supplementary services
Q.731.3 (03/93) Calling line identification presentation (CLIP)
Q.731.4 (03/93) Calling line identification restriction (CLIR)
Q.731.5 (03/93) Connected line identification presentation (COLP)
Q.731.6 (03/93) Connected line identification restriction (COLR)
Q.732.2 (07/96) Call diversion services: - Call forwarding busy - Call forwarding no
reply - Call forwarding unconditional - Call deflection
Q.732.7 (07/96) Explicit Call Transfer
Q.733.1 (02/92) Call waiting (CW)
Q.733.2 (03/93) Call hold (HOLD)
Q.733.3 (06/97) Completion of calls to busy subscriber (CCBS)
Q.733.4 (03/93) Terminal portability (TP)
Q.734.1 (03/93) Conference calling
Q.734.2 (03/93) Three-party service
Q.735.1 (03/93) Closed user group (CUG)
Q.735.3 (03/93) Multi-level precedence and preemption
Q.741 (11/88) Signaling System No.7 - Data user part
Q.750 (06/97) Overview of Signaling System No.7 management
A-2
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
Q.751.1 (10/95) Network element management information model for the Message
Transfer Part (MTP)
Q.751.2 (06/97) Network element management information model for the signaling
Connection Control Part
Q.751.3 (09/97) Network element information model for MTP accounting
Q.751.4 (05/98)
accounting verification
Q.752 (06/97) Monitoring and measurements for Signaling System No.7 networks
Q.754 (06/97) Signaling System No.7 management Application Service Element (ASE)
definitions
Q.755 (03/93) Signaling System No.7 protocol tests
Q.755.1 (05/98) MTP Protocol Tester
Q.755.2 (09/97) Transaction capabilities test responder
Q.756 (06/97)
(OMAP)
Q.761 (09/97) Signaling System No.7 - ISDN User Part functional description
Q.762 (09/97) Signaling System No.7 - ISDN user part general functions of messages
and signals
Q.763 (09/97) Signaling System No.7 - ISDN user part formats and codes
Q.764 (09/97) Signaling System No.7 - ISDN user part signaling procedures
Q.765 (05/98) Signaling system No.7 - Application transport mechanism
Q.766 (03/93)
application
Q.767 (02/91) Application of the ISDN user part of CCITT signaling system No.7 for
international ISDN interconnections
Q.771 (06/97) Functional description of transaction capabilities
Q.772 (06/97) Transaction capabilities information element definitions
Q.773 (06/97) Transaction capabilities formats and encoding
Q.774 (06/97) Transaction capabilities procedures
Q.775 (06/97) Guidelines for using transaction capabilities
Q.780 (10/95) Signaling System No.7 test specification - General description
A-3
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
aspects
Q.941 (03/93) ISDN user-network interface protocol profile for management
A-4
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
A-6
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
Service
accessibility".
GSM02.24: "Digital cellular telecommunications system (Phase2);
Description of
"Digital
cellular
telecommunication
system
(Phase2);
"Operator
determined barring".
GSM02.60: "Digital cellular telecommunications system (Phase 2+); General Packet
Radio Service (GPRS); Service description, Stage 1".
GSM02.78: "Digital cellular telecommunication system (Phase 2+); "Customized
Applications for Mobile network Enhanced Logic (CAMEL); Service definition (Stage
1)".
GSM02.81: "Digital cellular telecommunication system (Phase 2); Line identification
supplementary services - Stage 1".
GSM02.82: "Digital cellular telecommunication system (Phase 2); Call Forwarding (CF)
supplementary services - Stage 1".
GSM02.83: "Digital cellular telecommunication system (Phase 2); Call Waiting (CW)
and Call Hold (HOLD) supplementary services - Stage 1".
GSM02.84: "Digital cellular telecommunication system (Phase 2); MultiParty (MPTY)
supplementary services - Stage 1".
GSM02.85: "Digital cellular telecommunication system (Phase 2); Closed User Group
(CUG) supplementary services - Stage 1".
A-7
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
"Digital
cellular
telecommunication
system
(Phase
2);
Network
architecture".
GSM03.03: "Digital cellular telecommunications system (Phase 2); Numbering,
addressing and identification".
GSM03.04: "Digital cellular telecommunication system (Phase 2); Signaling
requirements relating to routing of calls to mobile subscribers".
GSM03.05: "Digital cellular telecommunication system Technical performance
objectives".
GSM03.07: "Digital cellular telecommunication system (Phase2); Restoration
procedures".
GSM03.08: "Digital cellular telecommunication system (Phase2); Organization of
subscriber data".
GSM03.09:
"Digital
cellular
telecommunication
system
(Phase2);
Handover
procedures".
GSM03.10: "Digital cellular telecommunication system (Phase2); GSM Public Land
Mobile Network (PLMN) connection types".
GSM03.11: "Digital cellular telecommunication system (Phase 2); Technical realization
of supplementary services".
GSM03.12: "Digital cellular telecommunication system (Phase 2); Location registration
procedures".
GSM03.14: "Digital cellular telecommunication system (Phase 2); Support of Dual Tone
Multi-Frequency signaling (DTMF) via the GSM system".
GSM03.15: "Digital cellular telecommunication system (Phase 2); Technical realization
of operator determined barring".
GSM03.16: "Digital cellular telecommunication system (Phase 2); "Subscriber data
management - Stage 2".
A-8
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
GSM03.18: "Digital cellular telecommunications system (Phase 2); Basic call handling;
Technical realization".
GSM03.20: "Digital cellular telecommunication system; Security related network
functions".
GSM03.40: "Digital cellular telecommunications system (Phase 2); Technical
realization of the Short Message Service (SMS) Point-to-Point (PP)".
GSM03.41: "Digital cellular telecommunications system (Phase 2); Technical
realization of Short Message Service Cell Broadcast (SMSCB)".
GSM03.42: "Digital cellular telecommunications system (Phase 2); Compression
algorithm for text messaging services".
GSM03.44: "Digital cellular telecommunication system (Phase 2); Support of teletex in
a GSM Public Land Mobile Network (PLMN)".
GSM03.45: "Digital cellular telecommunications system (Phase 2); Technical
realization of facsimile group 3 transparent".
GSM03.46: "Digital cellular telecommunication system (Phase 2); Technical realization
of facsimile group 3 non-transparent".
GSM03.47: "Digital cellular telecommunication system (Phase 2); Example protocol
stacks for interconnecting Service Center(s) (SC) and Mobile-services Switching
Center(s) (MSC)".
GSM03.50: "Digital cellular telecommunications system (Phase 2); Transmission
planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN)
system".
GSM03.54: "Digital cellular telecommunications system (Phase 2); Description for the
use of the shared Inter Working Function (SIWF) in a GSM PLMN; Stage 2".
GSM03.60: "Digital cellular telecommunications system (Phase 2); General Packet
Radio Service (GPRS); Service description; Stage 2".
GSM03.66: "Digital cellular telecommunications system (Phase 2); Support of Mobile
Number Portability; Technical Realization; Stage 2".
GSM03.78: "Digital cellular telecommunications system (Phase2+); Customized
Applications for Mobile network Enhanced Logic (CAMEL) Phase 2; Stage 2".
GSM03.79: "Digital cellular telecommunications system (Phase 2); Support of Optimal
Routing (SOR); Technical realization".
GSM03.81: "Digital cellular telecommunication system (Phase 2); Line identification
supplementary services - Stage 2".
A-9
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
GSM03.82: "Digital cellular telecommunication system (Phase 2); Call Forwarding (CF)
supplementary services - Stage 2".
GSM03.83: "Digital cellular telecommunication system (Phase 2); Call Waiting (CW)
and Call Hold (HOLD) supplementary services - Stage 2".
GSM03.84: "Digital cellular telecommunication system (Phase 2); MultiParty (MPTY)
supplementary services - Stage 2".
GSM03.85: "Digital cellular telecommunication system (Phase 2); Closed User Group
(CUG) supplementary services - Stage 2".
GSM03.86: "Digital cellular telecommunication system Advice of Charge (AoC)
supplementary services - Stage 2".
GSM03.88: "Digital cellular telecommunication system (Phase 2); Call Barring (CB)
supplementary services - Stage 2".
GSM03.90: "Digital cellular telecommunication system (Phase 2); Unstructured
supplementary services operation - Stage 2".
GSM03.91: "Digital cellular telecommunication system (Phase 2); "Explicit Call
Transfer (ECT) supplementary service - Stage 2".
GSM03.96: "Digital cellular telecommunications system (Phase 2); Name identification
supplementary services; Stage 2".
GSM03.97: "Digital cellular telecommunications system (Phase 2); Multiple Subscriber
Profile (MSP) (Phase 1); Stage 2".
GSM 04 Series
GSM04.02: "Digital cellular telecommunication systems (Phase 2); GSM Public Land
Mobile Network (PLMN) access reference configuration".
GSM04.08: "Digital cellular telecommunications system (Phase2); Mobile radio
interface layer 3 specification".
GSM 08 Series
GSM08.01: "Digital cellular telecommunications system (Phase 2); Base Station
System - Mobile Services Switching Center (BSS - MSC) Interface; General aspects".
GSM 08.02: "Digital cellular telecommunications system (Phase 2); Base Station
System - Mobile-services Switching Center (BSS - MSC) interface; Interface
principles".
GSM 08.04: "Digital cellular telecommunications system (Phase 2); Base Station
System - Mobile-services Switching Center (BSS - MSC) interface; Layer 1
specification".
A-10
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
GSM 08.06: "Digital cellular telecommunications system (Phase 2); Signaling transport
mechanism specification for the Base Station System - Mobile-services Switching
Center (BSS - MSC) interface".
GSM 08.08: "Digital cellular telecommunications system (Phase 2); Mobile Switching
Center - Base Station System (MSC - BSS) interface Layer 3 specification".
GSM 08.20: "Digital cellular telecommunications system (Phase 2); Rate adaptation on
the Base Station System - Mobile-services Switching Center (BSS - MSC) interface".
GSM 09 Series
GSM09.01: "Digital cellular telecommunication system (Phase 2); General network
interworking scenarios".
GSM09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application
Part (MAP) specification".
GSM09.03: "Digital cellular telecommunication system (Phase 2); Signaling
requirements on interworking between the Integrated Services Digital Network (ISDN)
or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network
(PLMN)".
GSM09.04: "Digital cellular telecommunication system (Phase 2); Interworking
between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data
Network (CSPDN)".
GSM09.05: "Digital cellular telecommunication system (Phase 2); Interworking
between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data
Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access".
GSM09.06: "Digital cellular telecommunications system (Phase 2); Interworking
between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data
Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet
switched data transmission services".
GSM09.07: "Digital cellular telecommunications system (Phase 2); General
requirements on interworking between the Public Land Mobile Network (PLMN) and
the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network
(PSTN)".
GSM09.10: "Digital cellular telecommunication system (Phase 2); Information element
mapping between Mobile Station - Base Station System and BSS - Mobile-services
Switching Center (MS - BSS - MSC) Signaling procedures and the Mobile Application
Part (MAP)"
GSM09.11: "Digital cellular telecommunication system (Phase 2); Signaling
interworking for supplementary services".
A-11
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
A-12
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix A Standard Compliance
A-13
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix B Terminology
Appendix B Terminology
HW
The high-speed signal cable used in M900/M1800 MSC/SSP/IP equipment. HW cables
include traffic HW and Signaling HW according to the different messages they carry.
Traffic HW: Used to carry various traffic data, including tone, circuit, call resource, etc.
Signaling HW: Used to carry various equipment internal control messages on the basis
of HDLC protocol.
Host
The aggregate of core functional boards for system management and traffic handling in
the M900/M1800 MSC/SSP/IP system, such as AMP, CDP and GSPC boards.
Foreground/Background
Foreground
refers
to
the
Host.
Background
mainly
refers
to
BAM.
B-1
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
A3
Authentication algorithm A3
A5/1
A5/2
AC
Application Context
ACM
ACM
ACMM
ADI
ADM
AE
Application Entity
AM /CM
AMP
ANC
ANN
ANU
AoCC
AoCI
ASE
ASN.1
AU
Access Unit
AuC
Authentication Centre
B
B-interface
BAIC
BAOC
BAM
BCC
C-1
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
BCD
BCP
BCIE
BCM
BCSM
BHCA
BI
BIC-Roam
Barring of Incoming Calls when Roaming outside the home PLMN country
BO
BOIC
BOIC-exHC
BS
BS
Bearer Service
BSG
BSC
BSM
BSS
BSSAP
BSSMAP
BTS
C
C-interface
CA
Cell Allocation
CAI
CAMEL
CAP
CBK
CC
Country Code
CC
Call Control
CCBS
CCF
CCF
C-2
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
CCM
CDB
Center DataBase
CDP
CF
CFB
CFNRc
CFNRy
CFL
CFU
CGC
CI
Cell Identity
CI
CUG Index
CKM
ClocK Module
CKSN
CKV
Clock Driver
CLF
CLI
CLIP
CLIR
CM
Connection Management
Connection Module
CM
Call Manager
CNET
COLI
COLP
COLR
CONNACK
CONNect Acknowledgement
COT
Continuity signal
CPM
CSD
CSM
CUG
CW
Call Waiting
C-3
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
D
D-interface
DB
DataBase
DET
DETach
DISC
DISConnect
DP
Detection Point
DPC
DSS1
DTR
E
E-interface
EC
Echo Canceller
ECI
EIR
ETS
ETSI
F
F-interface
FAM
FAM
FCS
FEAM
FIM
FN
Frame Number
FR
Full Rate
FSM
FSM
FTC
Ftn
forwarded-to number
C-4
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
GALM
GAMD
GBAC
GBDR
GCDI
GCKD
GCKS
GCTN
GCNU
GCPC
GE16
GECP
GECS
GFSN
GGSN
GHN7
G-interface
G/IW MSC
Gateway/Interworking MSC
GMHI
GRQ
GMSC
GPWS
GQSI
GSNU
GSPC
GSPT
GSRC
GSTU
GSM,
GSM900,
GSM1800
gsmSCF
gsmSRF
gsmSSF
GT
Global Title
C-5
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
GUI
GVDP
H
HDB
HLR DataBase
HDLC
HLC
HLR
HO
HandOver
HOLD
Call Hold
HOFL
HPLMN
Home PLMN
HR
Half Rate
HW
High Way
HWC
I
IAM
IAI
IC
ICB
ID
IDentification / IDentity
iGWB
iGateway Bill
IMEI
IMM
IMSI
IN
Intelligent Network
IN-SM
IN-Switching Manager
ISDN
IP
Intelligent Peripheral
ITU-T
ISUP
IWC
IWF Controller
C-6
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
IWF
Interworking Function
IWMSC
InterWorking MSC
IWU
InterWorking Unit
K
Kc
Ciphering key
Ki
L
L1
Layer 1
L2ML
L2R
Layer 2 Relay
L3
Layer 3
LA
Location Area
LAC
LAI
LAN
LAN Switch
LAP
LAPD
LIM
LLC
LPLMN
Location PLMN
M
MAP
MCC
MM
Mobility Management
MML
MNC
MO
Mobile Originated
MoU
Memorandum of Understanding
MPTY
C-7
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
MS
Mobile Station
MSC
MSC-A
MSC-B
MSC-B
MSISDN
MSM
MSRN
MT
Mobile Terminated
MTP
MVPN
N
NCC
NDUB
NE
Network Equipment
NF
Network Function
NM
Network Management
NMC
O
ODB
OET
Optical-Electrical Transformer
OFL
O&M, OM
OMAP
OMC
OMU
OOP
OPC
OPT
OSI
C-8
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
P
PABX
PCH
Paging Channel
PCM
PCU
PH
Packet Handler
PIC
Point in Call
PLMN
PPS
PrePaid Service
PRI
PSPDN
PS
PassWord
PSTN
PWC
Q
QoS
Quality of Service
R
RBT
RAND
REJ
REJect (ion)
REL
RELease
REQ
REQuest
RLP
RLG
RR
Radio Resource
RSC
RSZI
S
SAP
SAM
C-9
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
SAO
SC
SC
Service Code
SCCP
SCE
SCF
SCP
SDF
SDH
SDP
SLB
SLPI
SM
Switching Module
SMAF
SMAP
SMC
SMF
SMP
SMS
SMS
SMSCB
SN
Subscriber Number
SPC
SPLIM
SPM
SOA
SRF
SRM
SRME
SRSM
SS
Supplementary Service
SSF
SSP
SS7
C-10
Technical Manual
M900/M1800 MSC/SSP/IP
Appendix
Appendix C Abbreviations and Acronyms
SSME
STB
STM
STP
T
TC
Transcoder
TCAP
TCSM
TMSI
TRAU
TUP
U
UI Client
Um
USSD
V
VDB
VLR DataBase
VLR
VM
Voice Mailbox
VMSC
Visited MSC
VPLMN
Visited PLMN
W
WAD
Wireless Advertisement
WAN
WAP
WS
Work Station
WSS
C-11