Technical - Manual MSC M1800 PDF

System Description
Table of Contents .........................................................................................

Chapter 1 Overview ......................................................................................
1.1 Mobile Network Where M900/M1800 MSC/SSP/IP Resides ............
1.2 Functional Units ................................................................................
1.2.1 Mobile Switching Center (MSC) ...............................................
1.2.2 Service Switching Point (SSP) .................................................
1.2.3 Intelligent Peripheral (IP) ..........................................................
1.3 Networking Modes ............................................................................
1.3.1 Networking of Visited MSC (VMSC) .........................................
1.3.2 Networking of Gateway MSC (GMSC) .....................................
1.3.3 Networking of M900/M1800 MSC/SSP/IP as Independent
SSP ...................................................................................................
Chapter 2 System Features .........................................................................
2.1 Large Capacity ..................................................................................
2.2 High Integration and Low Power Consumption.................................
2.3 High Reliability ..................................................................................
2.4 Support of STM-1 SDH Optical/Electrical Interfaces ........................
2.5 Provisioning of IWF to Support WAP Access ...................................
2.6 Powerful Signal Tone Function .........................................................
2.7 Rich Services ....................................................................................
2.7.1 Wireless Intelligent Services Triggered by Number
Segment ............................................................................................
2.7.2 Customized Value-Added Services ..........................................
2.8 Interception Function ........................................................................
2.9 Flexible Route Selection ...................................................................
2.10 Powerful Number Adaptation Capability .........................................
2.11 Flexible Allocation of Roaming Numbers ........................................
2.12 Virtual Multi-SP Function ................................................................
2.12.1 Expanded Links between Signaling Points .............................
2.12.2 Expanded Speech Channels between Signaling Points.........
2.13 Support of 2Mbit/s High-Speed Signaling Link ...............................
2.14 MAP Policing and SCCP Policing ...................................................
2.15 Capability of Serving as LSTP ........................................................
2.16 Excellent Signaling Compatibility ....................................................
2.16.1 MAP Signaling Compatibility ..................................................
2.16.2 CAP Signaling Compatibility ...................................................
2.16.3 TUP Signaling Compatibility ...................................................
2.16.4 ISUP Signaling Compatibility ..................................................
2.16.5 CAS Compatibility ...................................................................
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.6 Signaling Interworking ............................................................

2.17 PRA Interface for Connection with ISDN Users ..............................
2.18 Provisioning of Gs Interface for Connection with GPRS System ....
2.19 Support of SSP Access in Different Countries ................................
2.20 Convenient Operation Terminal ......................................................
2.21 Smooth Upgrading ..........................................................................
2.21.1 Software Patching ..................................................................
2.21.2 Online Capacity Expansion ....................................................
Chapter 3 System Architecture ....................................................................
3.1 Modular Structure .............................................................................
3.2 System Architecture ..........................................................................
3.2.1 Hardware Architecture ..............................................................
3.2.2 Software Architecture ...............................................................
3.3 System Configuration........................................................................
Chapter 4 External Interfaces .......................................................................
4.1 Overview ...........................................................................................
4.2 A-interface .........................................................................................
4.3 C-interface ........................................................................................
4.4 D-interface ........................................................................................
4.5 Interfaces between MSCs .................................................................
4.6 F-interface .........................................................................................
4.7 G-interface ........................................................................................
4.8 Gs-interface ......................................................................................
4.9 L-interface .........................................................................................
4.10 O&M Interface .................................................................................
4.11 Billing Interface ...............................................................................
4.12 PRA Interface ..................................................................................
4.13 Interface to Fixed Network ..............................................................
4.14 LICI .................................................................................................
Chapter 5 System Reliability ........................................................................
5.1 Hardware Reliability Measures .........................................................
5.1.1 Distributed Processing ..............................................................
5.1.2 Multiprocessor Redundancy Technique ...................................
5.1.3 Board-level Hot Standby ...........................................................
5.1.4 Mutual-Aid Operation Mode......................................................
5.1.5 Fault Detection and Handling ...................................................
5.2 Software Reliability Measures ...........................................................
5.2.1 Preventive Measures ................................................................
5.2.2 Error Tolerance .........................................................................
5.2.3 Fault Monitoring and Handling ..................................................
5.3 System Load Control ........................................................................
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.3.1 Principle of Load Control ..........................................................

5.3.2 Measures of Load Control ........................................................
5.4 Signaling Policing Function ...............................................................
5.4.1 MAP Policing Function .............................................................
5.4.2 SCCP Policing Function ...........................................................
5.5 Reliability Measures for Charging System ........................................
5.5.1 Active/Standby Operation Mode ...............................................
5.5.2 Reliable Storage of Charging Data ...........................................
5.5.3 Error Tolerance of Bill Storage Disk .........................................
5.5.4 User Access Security Measures ...............................................
5.6 Reliability Measures for O&M System ..............................................
5.6.1 BAM Disk Error Tolerance & Network Adapter Binding............
5.6.2 Emergency Workstation ...........................................................
5.6.3 User Access Security Design ...................................................
Chapter 6 Technical Indices .........................................................................
6.1 Product Performance ........................................................................
6.1.1 Availability.................................................................................
6.1.2 Reliability Indices ......................................................................
6.1.3 Maintainability ...........................................................................
6.1.4 Power Consumption .................................................................
6.1.5 Clock Indices ............................................................................
6.2 Physical Features of the Cabinet ......................................................
6.3 Features of External Physical Interfaces ..........................................
6.3.1 E1 Interface ..............................................................................
6.3.2 SDH Optical Interface ...............................................................
6.4 Environmental Requirements............................................................
6.4.1 Grounding Requirements .........................................................
6.4.2 Ambient Temperature and Relative Humidity ...........................
6.4.3 Cleanness.................................................................................
6.4.4 Lighting .....................................................................................
6.4.5 Atmospheric Condition .............................................................
6.4.6 Floor Bearing Capacity .............................................................
6.4.7 EMC (Electromagnetic Compatibility) .......................................
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
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.2.3 Resource Sharing and Centralized Management.....................

1.3 Functional Modules ...........................................................................
Chapter 2 Cabinet ........................................................................................
2.1 Physical Characteristics ....................................................................
2.1.1 Cabinet Type ............................................................................
2.1.2 Design Features .......................................................................
2.1.3 Cabinet Material .......................................................................
2.1.4 Dimensions and Weight............................................................
2.1.5 Other Features .........................................................................
2.1.6 Cabinet Installation ...................................................................
2.2 System Configuration........................................................................
2.2.1 Standard Configuration of M900/M1800 MSC/SSP/IP as
VMSC ................................................................................................
2.2.2 Compact Configuration of M900/M1800 MSC/SSP/IP .............
2.2.3 Configuration of M900/M1800 MSC/SSP/IP as GMSC ............
2.2.4 Configuration of M900/M1800 MSC/SSP/IP with Lawful
Interception Function .........................................................................
2.3 Configuration of Functional Cabinets ................................................
2.3.1 Main Control Cabinet ................................................................
2.3.2 Interface Cabinet ......................................................................
2.3.3 SPM Cabinet ............................................................................
2.3.4 Resource Cabinet .....................................................................
2.3.5 Integrated Management Cabinet ..............................................
2.3.6 SPLIM Cabinet .........................................................................
2.3.7 XPTU Cabinet...........................................................................
Chapter 3 Frame ..........................................................................................
3.1 Physical Characteristics ....................................................................
3.2 Function and Configuration ...............................................................
3.2.1 Clock Module (CKM) Frame .....................................................
3.2.2 Communication Control Module (CCM) Frame ........................
3.2.3 Central Processing Module (CPM) Frame ................................
3.2.4 Central Switching Network (CNET) Frame ...............................
3.2.5 Line Interface Module (LIM) Frame ..........................................
3.2.6 Service Processing Module (SPM) Frame ...............................
3.2.7 Shared Resource Module (SRM) Frame ..................................
3.2.8 InterWorking Function (IWF) Frame .........................................
Chapter 4 Board ...........................................................................................
4.1 Functions and Features ....................................................................
4.2 Board Structure .................................................................................
Chapter 5 Power Supply System .................................................................
5.1 Structure ...........................................................................................
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.2 AC Power Supply System .................................................................

5.3 DC Power Supply System .................................................................
5.4 DC Power Distribution Cabinet .........................................................
5.5 Cabinet Feed System .......................................................................
Chapter 6 Clock Synchronization System ....................................................
6.1 Overview ...........................................................................................
6.2 Architecture of Clock Synchronization System .................................
6.2.1 Configuration of Clock Module (CKM) Frame...........................
6.2.2 Control Structure of Clock System ...........................................
6.2.3 Allocation of Clock System Signals ..........................................
6.3 Hardware Configuration of Clock Synchronization System ..............
6.3.1 Clock Reference Source ...........................................................
6.3.2 Configuration for Extracting Clock Source from Trunk .............
6.3.3 Configuration for Leading in Clock Signals from BITS .............
6.4 Parameter Configuration of Clock Synchronization System .............
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
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.6 Equipment Management ...................................................................

2.7 Switching Network Management ......................................................
2.7.1 Software Modules Related with Switching Network
Operation ...........................................................................................
2.7.2 Functions of Switching Network Control Module ......................
2.8 Call Control .......................................................................................
2.9 Signaling Processing ........................................................................
Chapter 3 OMC Software .............................................................................
3.1 General Structure..............................................................................
3.2 BAM Software ...................................................................................
3.2.1 Functions of BAM Software ......................................................
3.2.2 Features of BAM Software .......................................................
3.2.3 Structure of BAM Software .......................................................
3.3 O&M Terminal Software ....................................................................
3.3.1 Service Maintenance System ...................................................
3.3.2 Alarm Console ..........................................................................
3.3.3 Traffic Statistics Console ..........................................................
3.4 Communication Gateway ..................................................................
3.4.1 Communication Gateway at BAM Side (Convert) ....................
3.4.2 Remote Maintenance Proxy (iGate) .........................................
3.5 M2000 Software ................................................................................
3.6 iGWB Software .................................................................................
3.6.1 Functions ..................................................................................
3.6.2 Features ...................................................................................
3.6.3 Dual-system of iGWB ...............................................................
3.6.4 Structure ...................................................................................
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
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.2.8 Unstructured Supplementary Service .......................................

1.2.9 Explicit Call Transfer (ECT) ......................................................
1.2.10 ODB Supplementary Services ................................................
1.2.11 Self-defined Supplementary Services ....................................
1.3 Value-Added Services ......................................................................
Chapter 2 Network Functions .......................................................................
2.1 Security .............................................................................................
2.1.1 Authentication ...........................................................................
2.1.2 User Information Ciphering .......................................................
2.1.3 TMSI Re-allocation ...................................................................
2.1.4 Equipment Identification ...........................................................
2.2 Mobility Management ........................................................................
2.2.1 Location Management ..............................................................
2.2.2 Handover ..................................................................................
2.3 Call Handling .....................................................................................
2.3.1 Call Connection Function .........................................................
2.3.2 Number Storage and Translation Function ...............................
2.3.3 Route Analysis Function ...........................................................
2.3.4 Echo Control .............................................................................
2.3.5 Tone Sending Function ............................................................
2.3.6 IWF Function ............................................................................
2.3.7 Number Receiving Delay Function ...........................................
Chapter 3 Mobile Application Protocols .......................................................
3.1 SS7 System ......................................................................................
3.1.1 Structure ...................................................................................
3.1.2 MTP ..........................................................................................
3.1.3 SCCP ........................................................................................
3.1.4 TCAP ........................................................................................
3.1.5 MAP ..........................................................................................
3.1.6 BSSAP ......................................................................................
3.1.7 TUP ..........................................................................................
3.1.8 ISUP .........................................................................................
3.2 DSS1 .................................................................................................
3.2.1 Introduction to ISDN Network ...................................................
3.2.2 Structure of DSS1.....................................................................
3.2.3 Physical Layer ..........................................................................
3.2.4 Data Link Layer ........................................................................
3.2.5 Network Layer ..........................................................................
3.3 CAS...................................................................................................
3.3.1 Overview ...................................................................................
3.3.2 Line Signaling ...........................................................................
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.3.3 Register Signaling ....................................................................

3.3.4 Signaling Procedure .................................................................
3.3.5 CAS Multi-nation Adaptation ....................................................
Chapter 4 Mobile Service Procedures ..........................................................
4.1 MOC and MTC Processing Procedure .............................................
4.1.1 MOC Processing Procedure .....................................................
4.1.2 MTC Processing Procedure .....................................................
4.2 Office Direction Call Processing Procedure ......................................
4.2.1 Mobile Terminated Inter-office Call Processing Procedure ......
4.2.2 Tandem Call .............................................................................
4.3 Handover Procedure .........................................................................
4.3.1 Intra-MSC Handover Procedure ...............................................
4.3.2 Basic Handover Procedure .......................................................
4.3.3 Subsequent Handover Procedure ............................................
4.4 CF Processing Procedure .................................................................
4.5 Call Hold Processing Procedure .......................................................
4.6 Call Wait Processing Procedure .......................................................
4.7 Multiparty Service Processing Procedure .........................................
4.8 Explicit Call Transfer (ECT) Processing Procedure ..........................
4.9 SMS Processing Procedures ............................................................
4.9.1 Introduction to SMS ..................................................................
4.9.2 Short Message Service (MT/PP) ..............................................
4.9.3 Short Message Service (MO/PP) .............................................
4.9.4 Instant Triggering after SMS-MT Failure ..................................
4.10 Virtual Roaming Service (VRS) Processing Procedure ..................
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
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.2 WIN in OVERLAY Mode ...................................................................

2.2.1 Networking of WIN in Overlay Mode ........................................
2.2.2 Service Triggering of Overlay WIN-Number Segment
Triggering ..........................................................................................
2.2.3 Smooth Evolution of WIN in OVERLAY Mode ..........................
2.3 Services Triggering via Access Code Mode .....................................
2.4 Access of gsmSRF Resource ...........................................................
2.5 Supporting Virtual Roaming Number ................................................
2.6 Supporting Overseas SSP Feature...................................................
Chapter 3 Intelligent Call Handling ...............................................................
3.1 Overview ...........................................................................................
3.2 IN Basic Call State Model .................................................................
3.3 Detection Point (DP) .........................................................................
3.4 Triggering of Intelligent Service-TDP and Service Keys ...................
3.5 Standard WIN Service Triggering-CSI Triggering .............................
3.6 Description of CAMEL Subscriber Data ............................................
Chapter 4 WIN Application Protocols ...........................................................
4.1 Introduction to CAP ...........................................................................
4.2 CAP Protocol ....................................................................................
4.2.1 GSM Protocol Family of CAMEL Phase 2 ................................
4.2.2 Basic Principles of CAP Protocol ..............................................
4.2.3 CAP Protocol and MAP Protocol ..............................................
4.3 CAP Operation ..................................................................................
4.3.1 CAP Operation Types...............................................................
4.3.2 Common CAP Operations ........................................................
4.3.3 Extended CAP Operations .......................................................
Chapter 5 WIN Service Procedures .............................................................
5.1 PPS Subscriber Call Ordinary PLMN Subscriber .............................
5.2 PPS Subscriber Call PSTN Subscriber.............................................
5.3 PSTN Subscriber or Ordinary GSM Subscriber Call Overlay PPS
Subscriber ...............................................................................................
5.4 Call between PPS Subscriber in Overlay Mode ................................
5.5 PPS Subscriber Recharging/Query Procedure .................................
5.6 UCB (USSD Call Back) Service Procedure ......................................
5.6.1 RBT ..........................................................................................
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
Operation and Maintenance Functions

Chapter 1 Operation and Maintenance Functions ........................................
1.1 Setting User Authorities ....................................................................
1.1.1 Command Group ......................................................................
i
1-1
1-1
1-1
1.1.2 Management of User Account ..................................................

1.1.3 Logon Time ...............................................................................
1.2 Data Configuration and Management ...............................................
1.2.1 Data Configuration ....................................................................
1.2.2 Data Operation and Management ............................................
1.3 Alarm .................................................................................................
1.3.1 System Structure ......................................................................
1.3.2 Reporting of Hardware Alarm Information ................................
1.3.3 Reporting of Software Alarm Information .................................
1.3.4 Alarm Box and Alarm Console .................................................
1.3.5 Alarm Level and Type...............................................................
1.4 Performance Measurement ..............................................................
1.4.1 Structure of Performance Measurement System .....................
1.4.2 Types of Performance Measurements .....................................
1.4.3 Functions and Features of Performance Measurement
System ...............................................................................................
1.4.4 Standard Compliance ...............................................................
1.5 Charging ...........................................................................................
1.5.1 Structure of Charging System ..................................................
1.5.2 Bill Storage ...............................................................................
1.5.3 Bill Types ..................................................................................
1.5.4 Bill Format ................................................................................
1.6 Routine Maintenance ........................................................................
1.6.1 Equipment Maintenance and Control .......................................
1.6.2 Trunk/Signaling Management and Control ...............................
1.6.3 Real-time Tracing and Query ...................................................
1.6.4 VLR Subscriber Management ..................................................
1.6.5 Other Maintenance Functions ..................................................
1.7 Software Patching .............................................................................
1.7.1 Basic Concepts .........................................................................
1.7.2 Features of Software Patch ......................................................
1.7.3 Structure of Software Patching System ....................................
1.7.4 Software Patching Operation ....................................................
1.8 System Testing .................................................................................
1.9 Task Management ............................................................................
1.9.1 Scheduled Task Management ..................................................
1.9.2 Batch Command .......................................................................
1.9.3 Macro ........................................................................................
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
Appendix A Standard Compliance ...............................................................

A.1 ITU-T Recommendations .................................................................
A.2 ETSI Specifications ..........................................................................
Appendix B Terminology ..............................................................................
Appendix C Abbreviations and Acronyms ....................................................
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
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.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2004 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
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.
About This Manual

Release Notes
The product version corresponds to the manual is M900/M1800 MSC/SSP/IP.
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
Module 1 System Description
briefs the main functions, features, architecture, external interfaces, technical indices
and reliability design of the product.
z
Module 2 Hardware Architecture
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
Module 3 Software Architecture
describes the composition, functions and features of the software system, along with
some typical service procedures.
z
Module 4 MSC Functions
focuses on the service features, network functions, mobile application protocols and
service procedures of the product.
z
Module 5 SSP Functions
focuses on the Wireless Intelligent Network (WIN) features, network functions,

application protocols and service procedures of the product.
z
Module 6 Operation and Maintenance Functions
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
Installation engineers & technicians
Operation & maintenance personnel
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface
Headings are in Boldface.
Courier New
Terminal Display is in Courier New.
II. Command conventions

Convention
Description
Boldface
The keywords of a command line are in Boldface.
italic
Command arguments are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by vertical bars.

One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets and separated

by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by vertical bars. A

minimum of one or a maximum of all can be selected.
[ x | y | ... ] *
Optional alternative items are grouped in square brackets and separated

by vertical bars. Many or none can be selected.
III. GUI conventions

Convention
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.
Multi-level menus are separated by forward slashes. For example,

[File/Create/Folder].
IV. Keyboard operation

Format
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
Press the left button twice continuously and quickly.
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:
Caution, Warning, Danger: Means reader be extremely careful during the

operation.
Note, Comment, Tip, Knowhow, Thought: Means a complementary description.
HUAWEI
Technical Manual
System Description
Technical Manual
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
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
System Description
Table of Contents
5.3.2 Measures of Load Control....................................................................................... 5-8

5.4 Signaling Policing Function................................................................................................ 5-9
5.4.1 MAP Policing Function ............................................................................................ 5-9
5.4.2 SCCP Policing Function.......................................................................................... 5-9
5.5 Reliability Measures for Charging System....................................................................... 5-10
5.5.1 Active/Standby Operation Mode ........................................................................... 5-10
5.5.2 Reliable Storage of Charging Data ....................................................................... 5-11
5.5.3 Error Tolerance of Bill Storage Disk...................................................................... 5-12
5.5.4 User Access Security Measures ........................................................................... 5-12
5.6 Reliability Measures for O&M System ............................................................................. 5-13
5.6.1 BAM Disk Error Tolerance & Network Adapter Binding ........................................ 5-13
5.6.2 Emergency Workstation ........................................................................................ 5-13
5.6.3 User Access Security Design................................................................................ 5-14
Chapter 6 Technical Indices......................................................................................................... 6-1
6.1 Product Performance......................................................................................................... 6-1
6.1.1 Availability ............................................................................................................... 6-1
6.1.2 Reliability Indices..................................................................................................... 6-2
6.1.3 Maintainability.......................................................................................................... 6-5
6.1.4 Power Consumption................................................................................................ 6-5
6.1.5 Clock Indices ........................................................................................................... 6-8
6.2 Physical Features of the Cabinet..................................................................................... 6-11
6.3 Features of External Physical Interfaces ......................................................................... 6-11
6.3.1 E1 Interface ........................................................................................................... 6-11
6.3.2 SDH Optical Interface ........................................................................................... 6-12
6.4 Environmental Requirements .......................................................................................... 6-13
6.4.1 Grounding Requirements ...................................................................................... 6-13
6.4.2 Ambient Temperature and Relative Humidity ....................................................... 6-14
6.4.3 Cleanness ............................................................................................................. 6-14
6.4.4 Lighting.................................................................................................................. 6-15
6.4.5 Atmospheric Condition .......................................................................................... 6-16
6.4.6 Floor Bearing Capacity.......................................................................................... 6-17
6.4.7 EMC (Electromagnetic Compatibility) ................................................................... 6-17
iii
Technical Manual
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.
1.1 Mobile Network Where M900/M1800 MSC/SSP/IP Resides

Huawei provides complete set of mobile network communication equipment including
M900/M1800 MSC/SSP/IP for more effective work and convenient life of people.
Coordinating with other related equipment, M900/M1800 MSC/SSP/IP can implement
all of Phase 1 and Phase 2 services and part of Phase2+ services specified in ETSI
standards (including GPRS services and intelligent services complying with CAMEL
Phase2 specifications). It also provides various value-added services and customized
supplementary services upon subscribers requirements.
Integrating the functions of MSC/SSP/IP entities, M900/M1800 MSC/SSP/IP is an
important component of GSM mobile intelligent network, shown as Figure 1-1.
Other
MSC/VLR
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
AUC: Authentication Centre

BTS: Base Transceiver Station
GGSN: Gateway GPRS Support Node
MS: Mobile Station
PCU: Packet Control Unit
PSPDN: Packet Switched Public Data Network
SGSN: Serving GPRS Support Node
ISDN: Integrated Services Digital Network
OMC: Operation and Maintenance Center
BSC: Base Station Controller

EIR: Equipment Identity Register
HLR: Home Location Register
MSC: Mobile Switching Center
Public Land Mobile Network
PSTN: Public Switched Telephone Network
VLR: Visitor Location Register
SCP: Service Control Point
Figure 1-1 M900/M1800 MSC/SSP/IP in GSM network

1-1
Technical Manual
z
System Description
Chapter 1 Overview
Mobile Switching Center (MSC)
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
Service Switching Point/Intelligent Peripheral(SSP/IP)
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
Home Location Register (HLR)
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
Authentication Center (AuC)
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
Equipment Identity Register (EIR)
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
Serving GPRS Support Node (SGSN)
SGSN is responsible for MSs access control, mobility management, session

management, etc. It also provides the channels for the MS to access the external
Internet by creating PDP context of the MS.
z
Gateway GPRS Support Node (GGSN)
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
Service Control Point (SCP)
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
Base Station Controller (BSC)
1-2
Technical Manual
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
Base Transceiver Station (BTS)
BTS is controlled by BSC. It is responsible for radio connection. It performs functions

such as radio and wired signal conversion, radio diversity, radio channel encryption and
frequency hopping.
z
Packet Control Unit (PCU)
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
Visitor Location Register (VLR)
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
Operation & Maintenance Center (OMC)
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)
Mobile Station (MS)
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
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.
1.2 Functional Units

The M900/M1800 MSC/SSP/IP not only provides GMSC and MSC functions, but also
integrates the functions of the two components of the Intelligent Network (IN): Service
Switching Point (SSP) and Intelligent Peripheral (IP). It can be regarded as a physical
entity in the Wireless Intelligent Network (WIN). The connection relationships among
M900/M1800 MSC/SSP/IP and other physical entities in local network and other
network are shown in Figure 1-1.
1.2.1 Mobile Switching Center (MSC)

M900/M1800 MSC/SSP/IP provides the functions of an MSC.
As the core switching equipment in the Network SubSystem (NSS) of PLMN, MSC is in
charge of setting up mobile calls:
z
Between mobile network and fixed network (PSTN/ISDN, PSPDN)
Between local mobile network and other mobile networks
Within local mobile network.
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.
1.2.2 Service Switching Point (SSP)

M900/M1800 MSC/SSP/IP supports the CAMEL Phase2 functions defined in ETSI
GSM Phase2+. It is also compatible with the lower phase CAP protocols.
As an intelligent function unit, Service Switching Point is integrated in MSC,
responsible for participating and implementing switching function related to CAMEL
services.
M900/M1800 MSC/SSP/IP can work as a SSP defined in CAMEL Phase 2 with
corresponding SCP to provide various wireless intelligent services. In addition, it also
supports OVERLAY networking mode for wireless intelligent network, and has
capability of triggering mobile intelligent services by number segment.
1-4
Technical Manual
System Description
Chapter 1 Overview
1.2.3 Intelligent Peripheral (IP)

In M900/M1800 MSC/SSP/IP system, both IP and SSP are built in MSC physical entity
as network function units. IP provides SSP with special resource functions via internal
interface to achieve operations under intelligent network. When M900/M1800
MSC/SSP/IP serves as IP, it can receive SCP instruction through standard CAP
signaling and broadcast signal tones or announcements to specific SSP.
IP provides special resources required for implementing intelligent services. It supports
the CAMEL Phase2 functions defined in ETSI GSM Phase2+ and is compatible with
the lower-phase protocols.
1.3 Networking Modes

With multiple functions and large capacity, the M900/M1800 MSC/SSP/IP is suitable for
various network and Wireless Intelligent Network (WIN). To meet various requirements
for network construction, service expansion and network capacity, M900/M1800
MSC/SSP/IP supports various networking modes.
1.3.1 Networking of Visited MSC (VMSC)

The M900/M1800 MSC/SSP/IP can be used as the Visited Mobile Switching Center
(VMSC) in ordinary GSM network, or as the VMSC featuring SSP/IP functions, or as
VMSC and Overlay SSP/IP equipment of the local network, or as VMSC for combined
networking with GPRS.
Note:
When serving as the VMSC, the M900/M1800 MSC/SSP/IP provides the functions of both MSC and VLR.
The latter three networking modes will be introduced as below:
I. Serving as the VMSC with SSP/IP functions (VMSC/SSP/IP) in the standard

wireless intelligent network
The networking mode of M900/M1800 MSC/SSP/IP serving as the VMSC/SSP/IP in
the standard Wireless Intelligent Network (WIN) is shown in Figure 1-2.
1-5
Technical Manual
System Description
Chapter 1 Overview
TMSC
HLR
SCP
CSI triggering
BSS
VMSC/SSP/IP
PSTN
GMSC
BSS: Base Station Subsystem

SSP: Service Switching Point
GMSC: Gateway MSC
TMSC: Tandem MSC

IP: Intelligent Peripheral
VMSC: Visited MSC
CSI: CAMEL Subscription Information
Figure 1-2 Networking of M900/M1800 MSC/SSP/IP serving as VMSC/SSP/IP
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: Gateway MSC
GMSC
PSTN

VMSC: Visited MSC
Figure 1-3 Networking of M900/M1800 MSC/SSP/IP serving as the VMSC & Overlay SSP/IP equipment
in local network
III. Networking with GPRS

The VMSC has standard Gs interface to support GPRS network. The networking
GPRS is shown in Figure 1-4.
1-6
Technical Manual
System Description
Chapter 1 Overview
Internet
PLMN
HLR
SS7
network
GGSN
SGSN
VMSC
PCU
BSS

PCU: Packet Control Unit

SS7: Signaling System No.7
GGSN: Gateway GPRS Support Node
VMSC: Visited MSC
Figure 1-4 Combined networking with GPRS
1.3.2 Networking of Gateway MSC (GMSC)

The M900/M1800 MSC/SSP/IP can serve as the Gateway Mobile Switching Center
(GMSC) of the ordinary GSM network, or as GMSC and Overlay SSP/IP equipment of
the local network, or as GMSC and integrated STP simultaneously.
The latter two networking modes are described as follows:
1)
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
System Description
Chapter 1 Overview
SCP
HLR
Number
segment
triggering
BSS
VMSC
OVERLAY
PSTN
GMSC/SSP/IP

SSP: Service Switch Point
GMSC: Gateway MSC

VMSC: Visited MSC
Figure 1-5 Networking of M900/M1800 MSC/SSP/IP serving as the GMSC and Overlay SSP/IP of the
local network
2)
Serving as GMSC and integrated STP
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
HSTP: High-level STP

SP: Signaling Point
GMSC: Gateway MSC
LSTP: Low-level STP

LS: Local Switch
Figure 1-6 Networking of M900/M1800 MSC/SSP/IP serving as GMSC and LSTP
1.3.3 Networking of M900/M1800 MSC/SSP/IP as Independent SSP

The M900/M1800 MSC/SSP/IP can trigger intelligent network service by number
segment, so as to support the Overlay WIN networking mode. In this mode, the
M900/M1800 MSC/SSP/IP serves as an independent SSP, processing intelligent calls
1-8
Technical Manual
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
SSP: Service Switch Point

GMSC: Gateway MSC
PSTN

VMSC: Visited MSC
Figure 1-7 Networking of the M900/M1800 MSC/SSP/IP serving as an independent SSP
1-9
Technical Manual
System Description
Chapter 2 System Features

This chapter introduces the advantages and features of M900/M1800 MSC/SSP/IP in
terms of system capacity, services, external physical interface, operation and
maintenance interfaces, etc.
2.1 Large Capacity

M900/M1800 MSC/SSP/IP features powerful non-blocking switching and traffic
handling capability, and provides abundant external interfaces and powerful signaling
link access capability. It also provides an excellent internal control system. Such
features provide the basis for large capacity switching.
I. Traffic handling capability

M900/M1800 MSC/SSP/IP handles services in decentralized processing mode. Its
basic service processing unit is SPM (Service Processing Module). The total
processing capability of the system is the sum of all individual SPMs.
SPM is composed of two GSPC boards working in active and standby mode. GSPC
boards feature strong CPU processing capability and large memory capacity.
When M900/M1800 MSC/SSP/IP serves as VMSC, its max. BHCA (Busy Hour Call
Attempts) is 4,800k, and the maximum traffic volume supported is 30,000 Erl. When it
serves as GMSC, its maximum BHCA is 6,000k, and the maximum traffic volume
supported is 48,000 Erl.
II. Circuit switching capability

Circuit switching function of M900/M1800 MSC/SSP/IP is implemented by the Central
Switching Network (CNET) which is of T%T%T structure. It is a fully-available switching
network composed of skirt switching network and central switching network, with
maximum switching capacity of 128k%128k.
The maximum trunks supported by M900/M1800 MSC/SSP/IP are 4,096 PCMs (i.e.
120,000 trunk lines).
2-1
Technical Manual
System Description
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.
2.2 High Integration and Low Power Consumption

With modified functional modules and circuit boards using chips with powerful
processing capability, M900/M1800 MSC/SSP/IP features high integration, low power
consumption and higher system reliability.
If M900/M1800 MSC/SSP/IP serves as GMSC, nine cabinets (1 Integrated
management cabinet, 3 interface cabinet, 3 service processing cabinet, 1 main control
cabinet and 1 resource cabinet, besides the power distribution cabinet) can support
120,000 trunk lines.
If M900/M1800 MSC/SSP/IP serves as VMSC, five cabinets (integrated management
cabinet, interface cabinet, service processing cabinet, main control cabinet and
resource cabinet, besides the power distribution cabinet) can support 400,000
subscribers. With another two cabinets (one service processing cabinet and one
interface cabinet), 800,000 subscribers can be supported. In full configuration (another
one service processing cabinet and one interface cabinet is needed), 1,000,000
subscribers can be supported.
High integration and wide application of low voltage components reduces the power
consumption of the system. Table 2-1 lists the power consumption of cabinets with
different capacities.
Table 2-1 Relationship between Cabinet Consumption and System Capacity.
Subscriber
IMM
LIM
SPM
AM
SRM
LIM
SPM
LIM
SPM
Capacity (ten Cabinet Cabinet Cabinet Cabinet Cabinet Cabinet Cabinet Cabinet Cabinet
thousand)
(kW)
(kW)
(kW)
(kW)
(kW)
(kW)
(kW)
(kW)
(kW)
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
System Description
2.3 High Reliability

The reason behind the popularity of the M900/M1800 MSC/SSP/IP is its smooth and
reliable performance. Proper measures are taken to ensure its reliability, including
board backup, load sharing and redundancy configuration. System maintainability is
improved by optimizing boards and the system fault detection/isolation technology.
In terms of software, such measures as periodic detection, task monitoring, storage
protection and data check are taken for essential resources to improve system error
tolerance. Switchover and flow control techniques are employed to ensure the reliability
of the software. The design, development and testing of software strictly follows CMM
regulations.
The MTBF (Mean Time Between Failures) of M900/M1800 MSC/SSP/IP is 4,275 days
(10,2600 hours), and yearly mean system-down time is 2.56 minutes (calculated
according to general practice of the industry).
2.4 Support of STM-1 SDH Optical/Electrical Interfaces

The transmission networks currently in service mainly adopt SDH optical rings. The
switching equipment and SDH equipment are connected as follows: The PCM from the
switching equipment is connected to ADM which implements multiplexing. Then it is
connected to SDH optical rings. This PCM connection method is of low integration and
requires several ADMs between the switching equipment and the transmission network.
Such disadvantages boost equipment cost, especially in case of large-capacity
networks.
M900/M1800 MSC/SSP/IP provides SDH optical/electrical interface compliant with
STM-1 standard, which can connect and transit large-capacity trunks through public
transmission network and improves networking flexibility. It also saves the ADMs
between the switching equipment and SDH equipment, which greatly reduces cost for
network operators. The use of STM-1 optical/electrical interface is determined by the
transmission distance. Figure 2-1 shows three application modes of the interface.
2-3
Technical Manual
System Description
M900/M1800
MSC/SSP/IP
STM-1 Optical interface

( Distance < 30km)
GSTU
GSTU
STM-1 Electrical interface

(Distance < 70m)
GSTU
OET
STM-1 Optical interface
SDH
NE
622M/
2.5G/
10G
STM-1 Electrical interface

(Distance < 70m)
( Distance < 30km)
SDH: Synchronous Digital Hierarchy

OET: Optic-Electric Transducer
STM-1: Synchronous Transfer Mode 1

GSTU: SDH interface board
Figure 2-1 Application modes of STM-1 interface

The functions of STM-1 are implemented by the GSTU in the interface frame. Each
interface frame can be configured with 4 GSTU boards at most, i.e. each interface
frame can provide 4 STM-1 interfaces (with the trunk capacity of 252 E1s).
2.5 Provisioning of IWF to Support WAP Access

Wireless Application Protocol (WAP), similar to Internet Protocol, is a series of
specifications used to develop the application of mobile network. It is customized for
the wireless environment, where the MS is of limited storage capacity and low
processing capability with small screen, narrow bandwidth and high delay.
WAP can provide secure, quick, flexible, online and interactive services to mobile
subscribers, such as train timetable querying, customer service, message
announcement, call management, E-mail, message transfer, commerce, mapping &
positioning, news, sports information and bank services, address & number querying,
enterprise network, etc.
Featuring wide applicability and high compatibility, WAP is available to all the current
wireless bearer services and those in plan. In GSM network, there are three services
that can serve as WAP wireless bearer data service, namely, Circuit Switched Data
(CSD) service, Short Message Service (SMS) and Unstructured Supplementary
Service Data (USSD) service. M900/M1800 MSC/SSP/IP supports these three
services.
I. CSD bearer mode

It is the most common mode of the three. M900/M1800 MSC/SSP/IP supports the
BS2X (including 3.1kHz audio and UDI mode) of CSD as the bearer of WAP, which
2-4
Technical Manual
System Description
provides 9600bit/s data rate to the subscriber. With CSD as the bearer, it has the
following three networking modes.
1)
With PLMN, PSTN and Internet as communication path
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
Adaptation of data transmission rate.
Error correction under non-transparent mode.
Functions
oriented
to
fixed
network,
including
V.23-compliant
modulation/demodulation and audio generation function.
Um
BSS
Switch
ISP/RAS
WAP Server
IWF
PSTN
PLMN
IWF: InterWorking Function unit
ISP/RAS: Internet Service Provider/ Remote Access Server
Internet: Internet
Internet

Um: Air interface
WAP Server: WAP server
Figure 2-2 WAP networking based on CSD

2)
With PLMN, ISDN and Internet as communication path
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)
With PLMN and Internet as communication path
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.
II. SMS bearer mode

In SMS bearer mode, the Short Message Center (SMC) will connect with the WAP
Server, serving as the wireless datagram gateway.
M900/M1800 MSC/SSP/IP supports the SMS bearer mode.
2-5
Technical Manual
System Description
III. USSD bearer mode

Different from SMS, USSD is not a service based on store-and-forward switching, but a
session oriented service. Therefore, the response time for one USSD interaction is
shorter that of SMS.
In USSD bearer mode, the Unstructured Supplementary Service Data Center (USSDC)
will connect with the WAP Server, serving as the wireless datagram gateway.
2.6 Powerful Signal Tone Function

To be fully adaptive to different countries, M900/M1800 MSC/SSP/IP provides powerful
signal tone function and syntax analysis function of multiple languages, featuring:
z
Powerful functions of signal tone generation board: each board can provide 252
channels of tones with the total duration of 8000 seconds.
Multiple language playback support for basic synchronous tone, asynchronous

tone and intelligent voice.
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.
Playback of prompt tones during call proceeding.
2.7 Rich Services

M900/M1800 MSC/SSP/IP not only provides basic services such as speech, bearer
and supplementary services, but also provides rich intelligent services and customized
value-added services.
2.7.1 Wireless Intelligent Services Triggered by Number Segment

M900/M1800 MSC/SSP/IP supports SSP/IP functions compliant with ETSI CAMEL
Phase2 specifications, and provides CAP-conformed signaling interface. It is also
compliant with CAMEL Phase1 specifications.
To satisfy different conditions, M900/M1800 MSC/SSP/IP also supports the networking
mode of Overlay WIN, in which the intelligent services are triggered by number
segments. Therefore, taking the advantage of its large capacity, the M900/M1800
MSC/SSP/IP used as the GMSC can also serve as the Overlay SSP in one or several
local networks, which enables a quicker provisioning of intelligent services without
upgrading the whole network.
2-6
Technical Manual
System Description
Working with Huawei TELLIN intelligent network system, M900/M1800 MSC/SSP/IP

can support or provide Prepaid Service PPS, familiarity number service, Cell and Time
Discount and Wireless Advertisement (WAD).
2.7.2 Customized Value-Added Services

With the separation of network switching and service processing, and powerful
processing capability, M900/M1800 MSC/SSP/IP is much quicker in implementing and
providing new services. Besides the basic telecom services, supplementary services
and intelligent services, M900/M1800 MSC/SSP/IP also provides various personalized
Value-Added Services (VAS) according to operators' requests, such as USSD Call
Back (UCB), customized RingBack Tone (RBT) service, etc.
The UCB service supports intelligent subscribers to originate calls when roaming
abroad. Usually, if there is no connection/interworking between the home mobile
intelligent network and the mobile network the intelligent subscriber roams to, the
intelligent subscriber cannot originate any call, because the MSC in roaming region
cannot interwork with the home SCP. However, by providing UCB function,
M900/M1800 MSC/SSP/IP enables intelligent subscribers to originate calls when
roaming abroad. The procedure goes like this: The intelligent subscriber sends 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 in turn sets up
calls to the calling party and the called party respectively through the SSP. When both
sides answer, the SCP connects the two call segments. In this way, the intelligent
subscriber can originate calls when roaming abroad as long as USSD function is
supported in the region he roams to.
RBT service is ordered by the called party. With this service, a piece of sweet-sounding
music or a greeting is played to the calling party instead of the common ringback tone.
In the RBT service solution provided by Huawei, when the calling party calls the RBT
subscriber, the MSC A/GMSC A routes the call to the SSP. Under the control of the SCP,
the SSP connects with the Advanced Intelligent Peripheral (AIP) while establishing a
connection with the called party. When the VMSC B of the called party plays the
ringback tone, the SSP routes it to the AIP and indicates the AIP to play the ringback
tone ordered by the called party to the calling party through the SSP. Figure 2-3 shows
the networking:
2-7
Technical Manual
System Description
SCP
CAP
VMSCA/GMSCA
VMSC
A/GMSC A
ISUP
ISUP
SSP
VMSCBB
VMSC
ISUP
AIP
GMSC: Gateway MSC

AIP: Advanced Intelligent Peripheral
CAP: CAMEL Application Part (Signaling)
VMSC: Visited MSC

ISUP: ISDN User Part (Signaling)
Figure 2-3 RBT service networking
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 Interception Function

The interception function of M900/M1800 MSC/SSP/IP is implemented by its functional
subsystem Lawful Interception Center Interface (LICI). Without affecting the security of
the MSC and related subscriber services, the LICI can trace and intercept all the
activities (including session activities and non-session activities) of specific subscriber
within its serving area in real time.
Compliant with relevant ETSI specifications, LICI provides X1, X2 and X3 interfaces
between MSC and Lawful Interception Center (LIC), receives and processes LIC
commands. It also stores and manages the data related to LICI function (set by LIC)
and LIC communication. Together with LIC, the LICI implements real-time interception
of the specified subscriber, which includes facsimiles, short messages, data service,
change in location and status, and conversation. Among the MSC-LIC interfaces, X1 is
a control channel, transferring control commands and related responses between LIC
and MSC. X2 is a data channel, via which the LICI system transfers the activity event
reports of the intercepted subscriber, outputs contents of the short messages in
specified format, and generates alarm information of LICI system. X.25 or TCP/IP can
be adopted for X1 and X2 interfaces. X3 is used to output the conversation contents of
the intercepted object in real time. It is a 2048kbit/s digital interface and interface
2-8
Technical Manual
System Description
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.
2.9 Flexible Route Selection

M900/M1800 MSC/SSP/IP also provides flexible routing function. It can select the
route for connection according to the result of number analysis and calling subscriber's
information. The information of the calling subscriber refers to the location information.
For a local subscriber, it refers to the local area or cell, or the trunk circuit when the
calling party is the subscriber of other exchange.
Besides, M900/M1800 MSC/SSP/IP provides enhanced process of routing to
accomplish the following functions:
z
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
System Description
2.10 Powerful Number Adaptation Capability

To meet the numbering plan which may vary in different countries and different network
operators, M900/M1800 MSC/SSP/IP provides powerful number adaptation capability,
including:
z
Conversion of calling number, called number, third-party number, connected

number and original called number.
Conversion of number format and number attributes.
Conversion based on information such as calling/called number, calling party

location and calling party category.
Processing and conversion of numbers for incoming calls and outgoing calls.
Supporting the conversion of forwarded-to number, redirected number and

handover number.
Conversion of numbers on call bills.
Conversion of CLIP number format.
Supporting various number conversion modes.
2.11 Flexible Allocation of Roaming Numbers

The roaming number allocation of M900/M1800 MSC/SSP/IP has the following
features:
z
Several number segments can be set to control the prefixes/suffixes of roaming

numbers
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.
The roaming number can be allocated according to subscriber's current location

area.
The allocation mode of roaming numbers can be dynamically modified.
2.12 Virtual Multi-SP Function

With the development of networks and the increasing of subscribers, there is higher
demand for processing capability. However, restricted by ITU-T specifications and local
standards, the number of links and speech channels between two exchanges (each of
which has only one signaling point) is limited (number of links
16, speech channels
4096). To solve such issue, the concept of virtual multi-SP is introduced in

M900/M1800 MSC/SSP/IP. It is the best solution for large-capacity trunks and for
heavy traffic links between exchanges.
2-10
Technical Manual
System Description
The networking of multiple SPs is shown in Figure 2-4.
16 links, 4096 speech channels
Signalling point 1
.....
Signalling point 2
Signalling point n
16 links, 4096 speech channels
Other exchange
Figure 2-4 Networking of Multiple SPs
2.12.1 Expanded Links between Signaling Points

There is a route flag for identifying signaling route in the messages of SS7 signaling
protocols. For 24-digit signaling point code network, the format of flag is shown in
Figure 2-5.
SLS/SLC
OPC
DPC
24
24
OPC: Original Signaling Point Code

SLC: Signaling Link Code
First-sent bits
DPC: Destination Signaling Point Code

SLS: Signaling Link Selection Code
Figure 2-5 Route Flag

From Figure 2-5, we can know that there are only 4 bit positions in SLC/SLS identifying
circuits between signaling points. Therefore, the number of signaling links between two
signaling point codes can not exceed 24 = 16. The demand for SS7 signaling links
keeps growing along with the rise of its traffic. In the actual networking, the demand for
large traffic in SS7 network may not be satisfied due to the limitation of 16 links
between two signaling points. Although physical equipment can be added to satisfy
such requirements, it will significantly increase the investment.
M900/M1800 MSC/SSP/IP introduces the concept of virtual multi-SP, that is, one
physical node can be logically divided into multiple SPs, and each SP can connect with
other SPs independently. If one physical node is logically divided into N SPs, then the
2-11
Technical Manual
System Description
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
management functions of SCCP connectionless services.

With virtual multi-SP, the address of local office is not unique any longer. When local
SCCP subscribers originate calls, SCCP will select calling address according to
signaling status, signaling route relationship and traffic amount. That is, it will select an
OPC of local office and the link between this OPC and DPC to send messages, thus
achieving traffic sharing between SPs. Messages can be sent through other available
links from OPC to DPC if one link fails.
SCCP also has the capability to manage multi-SP of local office. When the route
between DPC and one SP of local office is congested or fails, it will not affect the
service between the DPC and other SPs.
2.12.2 Expanded Speech Channels between Signaling Points

There is a flag for identifying traffic route in the messages of TUP and ISUP. For 24-digit
signaling point code network, the format of flag is shown in Figure 2-6.
CIC
4
12
OPC
DPC
24
24
First-sent bits
OPC: Original Signaling Point Code

CIC: Circuit Identification Code
DPC: Destination Signaling Point Code
Figure 2-6 Telephone Flag

From Figure 2-6, we can know that there are only 12 bit positions in CIC identifying
circuits between signaling points, thus the number of trunk lines between two signaling
point codes can not exceed 212=4096. In actual network implementation, one office
direction usually corresponds to one DPC, therefore, the trunks between two offices
are actually the maximum trunks between two destination signaling points.
M900/M1800 MSC/SSP/IP supports virtual multi-SP at both local office and peer office,
enabling one office direction to have multiple signaling point codes. The trunks
between offices is greatly increased (multifold of 4,096 trunks) to support very large
traffic.
2-12
Technical Manual
System Description
Adopting database route selection mode, M900/M1800 MSC/SSP/IP can implement

traffic sharing between virtual signaling points of local office to achieve full utilization of
resources.
With virtual multi-SP introduced, the call processing and signaling procedures of TUP
and ISUP messages are still compliant with related TUP, ISUP specifications and ITU-T
recommendations.
2.13 Support of 2Mbit/s High-Speed Signaling Link

The maximum signaling flow of current signaling link is 64kbit/s, and the maximum flow
between two signaling points is 16%64kbit/s. However, with provision of more and
more new functions and services, and popularization of SMS and wireless intelligent
services, the development of the broadband mobile telecommunication in the future,
the signaling flow between signaling points will exceed 16%64kbit/s. Too meet such
demands, M900/M1800 MSC/SSP/IP supports 2 Mbit/s high-speed signaling links, with
interface electrical attributes conforming to G.703 specifications and frame structure
conforming to G.744 specifications.
2.14 MAP Policing and SCCP Policing

M900/M1800 MSC/SSP/IP supports the MAP Policing function, through which MSC
can intercept the MAP message sent from specified OSP, and reject certain MAP
operations according to the set conditions. In this way, the network resources can be
prevented from unauthorized use, and the data can be protected against illegal
modification. Thus, the operators and subscribers' profits are protected.
In addition, M900/M1800 MSC/SSP/IP supports SCCP Policing function, via which
certain message can be shielded according to the combined conditions of calling and
called address in SCCP message. This function can prevent the unauthorized use of
the network resource on one hand. On the other hand, it ensures that SCCP messages
are transmitted though the specified route.
2.15 Capability of Serving as LSTP

The signaling network in some countries (like China) adopts multi-level structure. The
first level is the highest level called High-level Signaling Transfer Point (HSTP). The
second is Low-level Signaling Transfer Point (LSTP). The third level is Signaling Point
(SP), which is composed of various exchanges and special service centers (service
control points, network management centers, etc.). The first level, HSTP, is responsible
for transferring signaling messages from LSTP and the third level SP. It adopts
standalone STP equipment, satisfying all functions defined in SS7 Message Transfer
Part (MTP) specifications.
2-13
Technical Manual
System Description
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
Maximum number of signaling links: 1024.
Signaling processing capability: 307,200 MSU/s.
Number of signaling linksets: 64k
Amount of routing areas: 64k
2.16 Excellent Signaling Compatibility

The signaling interfaces of M900/M1800 MSC/SSP/IP features excellent compatibility.
M900/M1800 MSC/SSP/IP supports GSM900MHz and DCS1800MHz, and shows
excellent interworking capability with the equipment of other vendors on the network.
To support ISUP signaling standard and Channel Associated Signaling (CAS) standard
in different countries, M900/M1800 MSC/SSP/IP features excellent compatibility for
circuit signaling (including ISUP signaling and CAS), and can transit TUP, ISUP, DDS1
and CAS signaling.
2.16.1 MAP Signaling Compatibility

The MAP signaling compatibility of the M900/M1800 MSC/SSP/IP is mainly presented
in the following aspects:
z
The signaling interface conforms to GSM Phase 2+ (Release 98) specifications.
Compatible with MAP Phase 1 and Phase 2 specifications
Supporting MAP version dialog negotiation mechanism.
Supporting handover commands compliant with MAP Phase1 specifications.
Supporting CAMEL Phase 2 and full compliance with CAMEL Phase 1.
Supporting four kinds of network indicators: national network, national standby

network, international network and international standby network.
Supporting
three
kinds
of
addressing
DPC+GT+SSN.
2-14
methods:
GT,
DPC+SSN
and
Technical Manual
System Description
Supporting three GT coding schemes: E.164, E.212 and E.214.
The addressing method of various MAP function flows can be specified through
data configuration.
2.16.2 CAP Signaling Compatibility

The CAP signaling compatibility of the M900/M1800 MSC/SSP/IP is mainly presented
z
The signaling interface conforms to CAMEL Phase 2 specifications.
Compatible with CAMEL Phase 1 specifications
Supporting various CAP signaling standards of different countries.
Supporting number-segment triggered and subscription-information triggered

intelligent services
Supporting special intelligent service flows of Thailand, Russia, India, etc.
Supporting the interworking with analog mobile networks.
2.16.3 TUP Signaling Compatibility

The TUP signaling compatibility of the M900/M1800 MSC/SSP/IP is mainly presented
z
Supporting ITU-T 89, ITU-T 93 and ITU-T 97 TUP signaling specifications.
Supporting ETR 256 (TUP+) specifications.
Supporting TUP specifications of Thailand, Brazil, etc.
2.16.4 ISUP Signaling Compatibility

The ISUP signaling compatibility of the M900/M1800 MSC/SSP/IP is mainly presented
z
Supporting ITU-T 87, ITU-T 92 and ITU-T 97 signaling specifications.
Supporting ISUP specifications of Russia, Thailand, Algeria, Uzbekistan, India,

Indonesia, Bangladesh, Spanish, Nigeria, Brazil, Hong Kong, etc.
The support of ISUP specifications in specific country can be set through data
configuration.
2.16.5 CAS Compatibility

The Channel Associated Signaling (CAS) compatibility of the M900/M1800
MSC/SSP/IP is mainly presented in the following aspects:
z
Supporting ITU-T 87, ITU-T 93, ITU-T 97 and ITU-T 99 R2 signaling

specifications.
Supporting R2 signaling specifications of Thailand, Algeria, India, Brazil, Kenya,

Zimbabwe, Bulgaria, etc.
2-15
Technical Manual
System Description
Supporting Signaling System No.5 specifications.
Supporting the CAS specifications of Russia, Iran, Pakistan, etc.
The support of channel-associated signaling specifications in specific country can

be set through data configuration.
2.16.6 Signaling Interworking

M900/M1800 MSC/SSP/IP features excellent signaling transfer functions, and can
achieve the interworking among TUP, ISUP, PRA and other channel-associated
signaling.
2.17 PRA Interface for Connection with ISDN Users

The PRA interface of M900/M1800 MSC/SSP/IP is fully compliant with ITU-T
specifications, and can connect various ISDN users supporting DSS1 signaling, such
as PBX and dial-up server.
2.18 Provisioning of Gs Interface for Connection with GPRS

System
M900/M1800 MSC/SSP/IP also supports the interconnection with GPRS and provides
standard Gs interface to connect with SGSN (Serving GPRS Support Node). For GSM
and GPRS subscribers, M900/M1800 MSC/SSP/IP fully supports the coordination with
SGSN in basic traffic handling such as mobility management, circuit paging and short
message services, and implements the management of VLR and SGSN correlation,
thus effectively improves the utilization of radio channels shared by the GSM and
GPRS systems.
M900/M1800 MSC/SSP/IP mainly provides the following functions to support GPRS
services:
z
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.
Identify and send MSC-SGSN correlation management message (including

non-GPRS alarm, GPRS detach, information acquisition, fault removal and
reachability notification), and update the SGSN-MSC correlation.
For the MS in correlated state, MSC cooperates with the SGSN to generate
combined paging.
2-16
Technical Manual
System Description
2.19 Support of SSP Access in Different Countries

M900/M1800 MSC/SSP/IP supports SSP access in different countries.
SSP implements CAP signaling interface with SCP, transit intelligent calls from MSC
and GMSC, performs related call processing operations, and provide powerful service
support for intelligent subscriber in OVERLAY wireless network. It is designed with the
following features for overseas market:
z
Enhanced intelligent call processing capability in case of SSP and SCP signaling
link failure;
Supporting such special requirements as twice announcement playback and free

phone in countries like Thailand;
Supporting overseas CAP features;
Filling of CAC (Charging Area Code) in initial DP messages.
2.20 Convenient Operation Terminal

M900/M1800 MSC/SSP/IP provides graphical display terminals based on MML. From
the Client which communicates with the MSC through BAM, various operation and
maintenance functions can be implemented, including data configuration, equipment
maintenance, status tracing, performance measurement, fault monitoring and user
management.
MML (Man-Machine Language) refers to the commands sent from the Client to BAM.
The protocol between the Client and BAM is quite simple. The communication between
them is conducted in form of pure character streams, through which various functions
such as batch processing of commands and command authority management can be
easily achieved. However, pure characters make the display a little insensible. To
overcome this disadvantage, M900/M1800 MSC/SSP/IP employs the O&M terminal
using both MML and GUI the graphic display terminal based on MML. This makes
operations more reliable and makes access to remote network management system
easier.
For bill management, operators may use any Web browser (e.g. IE) to visit the
Charging Gateway connected to the MSC, and perform operations and maintenance
(such as browsing and backup) over the bills. No special Client software is needed.
2-17
Technical Manual
System Description
2.21 Smooth Upgrading

2.21.1 Software Patching
M900/M1800 MSC/SSP/IP supports software patching function. After the equipment is
put into service, some modifications may be needed for the software. In this case,
software patching is useful, without affecting the normal service of the system.
Software patches include general patch and special patch. The former aims to solve
the problems common to all users, while the later is to solve user-specific issues.
When software defect is found, the patch creation tool may be used to organize one or
more patch (aimed at software defects) and to create the patch file based on certain
version. The adding of software patches can be executed through MML commands
during system operation.
2.21.2 Online Capacity Expansion

M900/M1800 MSC/SSP/IP employs modular design by separating network switching,
service processing and system resources. Each module is relatively independent and
corresponds to one frame. The configuration of modules can be determined based on
actual requirements.
M900/M1800 MSC/SSP/IP supports online capacity expansion, which means the users
can modify equipment configuration during system operation, and enter/exit services
through activation or separation operations. This online capacity expansion function
protects the benefits of the network operator, and does not affect the normal provision
of services.
2-18
Technical Manual
System Description
Chapter 3 System Architecture

M900/M1800 MSC/SSP/IP adopts modular structure. This chapter focuses on its
modular structure and the basic functions of various modules.
3.1 Modular Structure

The hardware system of the M900/M1800 MSC/SSP/IP has a 4-level hierarchical
structure, as shown in Figure 3-1.
The lowest level comprises several circuit boards. Various circuit boards are combined
together to form frame units. Each frame unit accomplishes specific functions. Frame
units with various functions are combined together to form a module and respective
modules can implement specific functions independently. Different modules are
combined together to form the M900/M1800 MSC/SSP/IP system.
Modules
Frames
Circuit boards
Figure 3-1 Hierarchical structure of M900/M1800 MSC/SSP/IP

The modular design makes the installation and expansion of M900/M1800
MSC/SSP/IP convenient & flexible, i.e., new functions and technologies can be
introduced by just adding/removing functional frames.
3.2 System Architecture

3.2.1 Hardware Architecture
M900/M1800 MSC/SSP/IP employs modular structure to achieve the separation of
network switching, external interfaces and service processing.
3-1
Technical Manual
System Description
Network switching is completed by CNET (Central Switching Network). CNET is a T %

T % T switching network, with all three levels fully utilized and the maximum capacity of
128k. It is the data switching core of M900/M1800 MSC/SSP/IP. CNET is composed of
GCNU and GSNU boards. CNET switching capacity can be smoothly expanded from
16k % 16k to 128k % 128k by adding GSNU boards.
Service processing is implemented by SPM (Service Processing Module). SPM can
implement various service processing and signaling link processing. One group of
GSPC boards form a SPM. The overall service processing capability of the system can
be enhanced by adding GSPC cards.
System resources are provided by SRM (Shared Resource Module), LIM (Line
Interface Module), IWF (Interworking Function unit), etc. SRM is composed of GSPT
and GSRC boards, and provides call resources such as signal tones, DTMF
transceivers, MFC transceivers, and conference call resources, etc. When LIM is
configured with GE16, GECP, GECS boards, it provides trunk resources and echo
cancellation resources. IWF frame provides IWF resources. These resources are
shared within the whole system and can be configured flexibly.
The capacity of network switching, service processing and system resources can be
expanded through simple physical overlay. Thus, system stability can be maintained
while capacity expansion is achieved.
For detailed information about hardware structure and functions of M900/M1800
MSC/SSP/IP, please refer to Module 2 of this manual.
3.2.2 Software Architecture

M900/M1800 MSC/SSP/IP software includes two parts: Host software and OMC
software.
Host software refers to the software of the five key boards (NCC board, GSPC board,
CDP board, GVDP board and AMP board). They control the hardware resources of the
MSC, perform signaling processing and call handling, and fulfill MSC, SSP and IP
functions of the system.
OMC software includes local O&M system, iMangager M2000 mobile network
management system, and iGWB (Charging Gateway) software. It fulfils such functions
as MSC operation and maintenance, office data configuration, performance
measurement, alarm management, charging management, etc.
The local O&M system includes BAM software, operation and maintenance terminal
software on WS, the communication gateway software on BAM or WS, and remote
maintenance gateway. M2000 system is optional. It includes the M2000 server
software and Adapter software running on M2000 server, and centralized O&M
3-2
Technical Manual
System Description
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 System Configuration

M900/M1800 MSC/SSP/IP can serve as network elements like GMSC/SSP,
TMSC/LSTP and SSP/IP.
The standard configurations of M900/M1800 MSC/SSP/IP includes Main Control
cabinet, Service Processing cabinet, Resource cabinet, Interface cabinet, Integrated
Management cabinet and Power Distribution cabinet.
The cabinets, frames and boards can be configured flexibly to meet different
requirements of subscriber capacity, trunk amount and services.
For detailed information about cabinet configuration, please refer to Section 2, Module
2 of this manual.
3-3
Technical Manual
System Description
Chapter 4 External Interfaces

The chapter describes the signaling interfaces between M900/M1800 MSC/SSP/IP
and other network entities. After reading this section, readers may have a basic idea
about interface names, functions and the signaling protocols employed. For the
message structure and application of various signaling, please refer to Module 4 and
Module 5 of this manual.
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
System Description
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
AUC: Authentication Center

EIR: Equipment Identity Register
PSPDN: Packet Switched Public Data Network
LIC:Lawful Interception Center

WS: WorkStation
LICI:Lawful Interception Center Interface
Figure 4-1 External interfaces of M900/M1800 MSC/SSP/IP

The interfaces and their meanings are listed in Table 4-1.
Table 4-1 M900/M1800 MSC/SSP/IP external interfaces
Interface Name
Connected Entity
Signaling and Protocol
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
System Description
Interface Name
Connected Entity
Signaling and Protocol
O&M Interface
MSC--WS
Internal protocol
LICI
MSC--LIC
Internal protocol/SOSM
Billing Interface
MSC iGWB--Billing Center
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
System Description
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.5 Interfaces between MSCs

The interface between MSCs includes two parts. One part is the mobile service
interface that employs MAP, which is used to accomplish the following functions.
Handover
SMS (Short Message Service)
Call control after inter-MSC handover
MAP signaling messages control the handover between MSCs of adjacent areas.
When the MS moves from the area controlled by one MSC to the area controlled by
another MSC during conversation, handover is to be started and performed between
two MSCs in order to maintain communications.
Another part of signaling messages transmitted via the signaling channel is TUP/ISUP
signaling message, which is used to accomplish the following functions during MOC
and MTC procedures:
Establishment of calls from MSC-A to MSC-B.
Call release depending on call establishment direction.
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
System Description
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.10 O&M Interface

M900/M1800 MSC/SSP/IP supports remote/local maintenance and centralized
maintenance.
BAM (Back Administration Module) of M900/M1800 MSC/SSP/IP local operation and
maintenance system is a functional unit connecting the MSC and local/remote
workstations (WS). As a server, BAM responds to the operation and maintenance
commands from WS (Client), and forwards the commands to MSC. The O&M interface
between BAM and WS is the MML using ASCII character stream. Binary GUI is also
employed to display equipment status and call connection tracing results on WSs.
Connected to M2000 system, BAM helps the user to know the running condition of the
equipment, and provides data access interface for the upper-level TMN.
4.11 Billing Interface

Charging information generated by the M900/M1800 MSC/SSP/IP is sent to the billing
gateway (iGWB) via the bill pool. The iGWB provides the interface to the Billing Center
to transmit bills in the standard bill format.
4-5
Technical Manual
System Description
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)
4.12 PRA Interface

PRA interface (PRI) refers to the interface between MSC which serves as ISDN
network part and ISDN user part. It is employed to meet the demands for heavy traffic.
PRA interface is of 30B+D. B-channel is 64 kbit/s user information channel fully
compliant with G.711 and G.722 Recommendations. It enables circuit switching, packet
switching and SPC (Semi-Permanent Connection). D-channel is 64 kbit/s signaling
channel used to transmit the circuit-switched signaling or packet data information.
Signaling messages are transferred by means of Digital Subscriber Signaling No.1 of
the link layer and network layer.
M900/M1800 MSC/SSP/IP supports hybrid networking of DSS1, SS7 and CAS. One
signaling link of PRA interface can control multiple PCMs. The users at each PRA
interface can be divided into different groups assigned with different authorities and the
right of selecting B-channels.
4.13 Interface to Fixed Network

The M900/M1800 MSC/SSP/IP supports the interconnection with the switching
equipment of the fixed network. The interface is the same as the external interface
provided by the switching equipment in the fixed network, which controls incoming and
outgoing calls via the TUP/ISUP or CAS.
The functions achieved through this interface include:
4-6
Technical Manual
System Description
Call establishment between mobile subscribers and fixed subscribers.

Call clear.
Circuit management.
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
System Description
Chapter 5 System Reliability

This chapter introduces the reliability measures of M900/M1800 MSC/SSP/IP in terms
of hardware, software, charging system and O&M system.
5.1 Hardware Reliability Measures

The M900/M1800 MSC/SSP/IP adopts the distributed system architecture. Proper
measures are taken to ensure its reliability, including active/standby configuration,
load-sharing and redundancy configuration of boards. System maintainability is
improved through board optimization and system fault detection/isolation technique.
The distributed power supply technique is applied. The high-frequency DC/DC
Secondary Power Module is used for each plug-in frame or functional module, which
guarantees high efficiency and excellent stability. The secondary power supply adopts
the active/standby redundancy design to ensure the reliability of the power supply.
In board design, advanced integrated circuits such as ASIC, PLD and FPGA are
adopted, which result in high system integration, excellent processing capability and
high reliability. All network chips in the boards are the ASICs designed by Huawei.
These ASIC components provide complete and efficient chip-level fault detection
measures and reporting mechanism. The +5V/-48V power input and external
interfaces (e.g. E1 interface) of boards are provided with over-voltage/over-current
protection measures in compliant with ITU-T G.703 Recommendation Annex B and
relative specifications.
In terms of manufacturing techniques, all components are strictly selected and have
passed the burn-in test. The assembly of hardware is under strict quality control. So the
long-term excellent performance is guaranteed.
The following sections introduce in detail the hardware reliability measures of
M900/M1800 MSC/SSP/IP.
5.1.1 Distributed Processing

The M900/M1800 MSC/SSP/IP realizes the distributed processing through modular
design. The functional modules are relatively independent of one another. For detailed
description of cabinets and frames, please refer to Module 2 of this manual.
M900/M1800 MSC/SSP/IP includes the following modules:
5-1
Technical Manual
z
System Description
Central Switching Network (CNET): CNET is a T%T%T switching network with

max. Capacity of 128k%128k. The capacity of CNET can be flexibly expanded (at
a unit of 16k%16k) based on actual requirements.
Service Processing Module (SPM): SPM is responsible for the processing of

various services of the system, and the link-layer processing of SS7 signaling and
DSS1 signaling.
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.
Clock Module (CKM): CKM ensures the synchronization of clock of M900/M1800

MSC/SSP/IP with higher-level network, and provides time reference for the
modules in the system.
Communication Control Module (CCM): CCM transfers communication control

data among various modules of the system.
Back Administration Module (BAM): BAM is located in the Integrated Management

Cabinet. It helps implementing operation and maintenance over M900/M1800
MSC/SSP/IP and provides centralized fault alarm. It provides network interfaces
for connecting terminals and remote/centralized maintenance.
X Protocol Transfer Unit (XPTU): It is in charge of the transfer between the

protocol used in X1/X2 interface for communicating with LIC and the internal
protocol used in M900/M1800 MSC/SSP/IP.
Charging Gateway (iGWB): The iGWB is located in the Integrated Management

Cabinet. It receives and stores bills of M900/M1800 MSC/SSP/IP, and creates
charging files. It provides interface to the Billing Center.
Alarm box: The alarm box will generate visible and audible alarms in case of
system fault.
5.1.2 Multiprocessor Redundancy Technique

The service processing part is critical in M900/M1800 MSC/SSP/IP. It is composed of
multiple processors (modules) with redundancy configuration. When one of the
modules fails, the other modules will take over the work so the normal operation of the
system can be ensured.
5-2
Technical Manual
System Description
I. Service Processing Part

The service processing part consists of several SPMs. Each SPM contains two GSPC
boards working in active/standby mode. Usually, the traffic at one office direction
should be configured on at least 2 SPMs. In case one SPM fails, the SPM serving the
same office direction can bear all the work to minimize the call loss at this direction.
II. VLR part

VLR part contains several VLR modules. Each module is composed of two GVDP
boards working in active/standby mode, and can store the information of up to 250000
subscribers. Usually, each MSC should be configured with at least two VLR modules. If
one module fails, the other module can process all the data.
5.1.3 Board-level Hot Standby

Board-level Hot Standby is the most commonly used method in large equipment to
improve the system reliability. Two boards work in the active and standby modes
respectively. On detecting any abnormality, the system will automatically perform
switchover so that the standby board is put into the active state.
The active/standby method is mainly applied to service processing, equipment
management, resource management, etc. The actual effect of board-level Hot Standby
can be measured by board switchover success ratio, and the key to switchover
success depends on the board fault detection rate and switchover mechanism.
I. Board fault detection

When the board is powered on, the memory and key internal chips (such as the
network chip) will perform self-checks. Online monitoring is executed on key signals of
the boards (e.g. 8kbit/s signals). Loop-back check is made on service code streams at
idle hours.
II. Switchover mechanism

The switchover between the active and standby boards are enabled via two
cross-connect signals between them. The two signals are the local board valid signal
(output signal) and the peer board valid signal (input signal). The local board valid
signal is generated by the heartbeat detection circuit.
5-3
Technical Manual
System Description
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.1.4 Mutual-Aid Operation Mode

Mutual aid, also referred to as load-sharing, means that two or multiple boards share
related functions in normal working. In case one board fails, the other boards complete
the task of the failed board.
Load sharing is mainly applied to the secondary power module, signaling processing
board and trunk board. For example, in normal working, each GPWS board bears half
of the load. In case one GPWS board fails, the other normal board will bear all the
loads.
5.1.5 Fault Detection and Handling

I. Fault detection meansures
The M900/M1800 MSC/SSP/IP provides the functions to automatically detect and
diagnose software and hardware faults as well as to print and store the fault
information.
Hardware fault detection function provides fault localization, isolation of failed hardware
or automatic switchover to the spare hardware.
In case of software failures, the system provides certain automatic error correction
measures and automatic recovery functions, including restarting and reloading
operations. For the major faults, fault indication signals are also given in addition to
recording and printing the fault information.
The system will confirm each hardware fault through repeated detection to avoid the
system reconfiguration or service quality degradation caused by occasional faults.
II. Precision of fault location

For trunk circuits and signal equipment, localization of faults can be made precisely to
each circuit. For circuits of common control parts such as service processing unit,
5-4
Technical Manual
System Description
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.2 Software Reliability Measures

5.2.1 Preventive Measures
The software reliability of the M900/M1800 MSC/SSP/IP is constructed in different
phases, from system requirement analysis, system design to testing.
Starting from requirement analysis, the software development process is implemented
under the guidance of CMM (Capability Maturity Model) to minimize the errors at the
initial phase.
In the software design phase, design methods and implementation are emphasized.
The software adopts the modular design approach and the design of each module is
based on the loose coupling mechanism, so that the failure of one module will not affect
other modules. In addition, error detection, error isolation and error recovery measures
are used to improve system reliability. Code walk-through, inspection and testing in
different phases are effective means to improve reliability.
Testing is an essential for product quality. From software project definition, test
personnel are fully involved in the software development process. From unit testing to
system testing, the plan is made by strictly following the specified process. The
perfection of planning ensures the improvement of software reliability. As the testing
plan is optimized during testing, the reliability of the testing plan is continuously
improved as a part of the software.
5.2.2 Error Tolerance

The error tolerance capability of the software system can prevent total system failure in
case of a small software fault. That is, the system should have self-healing capability in
case of errors.
The error tolerance capability of the software mainly includes:
I. Timed check of key resources

For software resources in the system (such as network board resources), the long-time
occupation check mechanism is added between modules. In case of resources
hang-up due to software abnormality, the fault will last only a short time. The check
mechanism can ensure the release of hang-up resources and the output of logs and
alarms.
5-5
Technical Manual
System Description
II. Task monitoring

In software operations, output channels are provided for internal software errors and
part of hardware errors. This is called the monitoring procedure. This procedure can
monitor the running state of tasks, handle system abnormalities and report to the
external devices.
III. Data check

For the consistency of BAM data and Host data or the consistency of data on different
processing boards, timed or event-driven consistency checks are implemented. Data
consistency can be recovered selectively or according to priority. Related logs and
alarms can be output.
IV. Saving of operation log information

BAM records the users operations within a period and saves the records in the system
operation log. For unknown errors in the system, the operation log can be used to trace
back to the normal condition so as to localize the fault or to restore the data operation.
5.2.3 Fault Monitoring and Handling

The software system reliability, to a large extent, depends on the fault monitoring
system and proper fault handling procedures especially after the software is
incorporated into products.
The system processing mainly includes the following:
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.
II. Communication bypass

When the GSPC board of the SPM can not set up LAN connection with the iGWB, other
paths may be used to deliver the messages. When the active GSPC board can not set
up LAN connection with the iGWB, then the standby GSPC will be used to set up the
LAN connection.
5-6
Technical Manual
System Description
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.3 System Load Control

Load control is adopted in case of CPU overload and resource congestion. By smoothly
adjusting traffic, system down caused by overload can be avoided.
The M900/M1800 MSC/SSP/IP adopts fully decentralized group-CPU control
technique. The CPU has powerful processing capability. When serving as the GMSC, it
supports a maximum of 6,000k BHCA. When serving as the VMSC, M900/M1800
MSC/SSP/IP supports a maximum traffic volume of 30,000 Erl and a maximum of
4,800k BHCA.
The CPU load under the normal operation state is far lower than the threshold to start
load control. In some cases, system load might be suddenly increased and the system
will automatically start the load control function in order to restore the system to
normality.
5.3.1 Principle of Load Control

The M900/M1800 MSC/SSP/IP adopts the source control strategy to ensure the
smooth adjustment of traffic flows.
The procedure of load control is: The system checks the CPU load and resource
utilization, and starts the flow control mechanism when the load reaches certain
threshold, and restricts part of system operations and user operations (i.e. degrade the
service level). At the same time, the system continues to check the elements. In case
the load is increased, the service level will be degraded by one level. On the contrary, in
5-7
Technical Manual
System Description
case the load is reduced, the service level will be increased by one level. Alarm
information will be generated for each load control operation.
5.3.2 Measures of Load Control

To ensure the safe operations of the system in peak hours, the M900/M1800
MSC/SSP/IP adopts the following measures:
I. Load control according to CPU load

The default threshold to trigger load control of the system is 80% CPU load and the end
threshold is 70% CPU load. The maintenance personnel can use the MML commands
to modify the start and end threshold values according to their requirements. To enable
the smooth adjustment of traffic flows, the load-control start threshold should be higher
than the end threshold. Once the load control is started, it ends only when the CPU load
is decreased to the end threshold, so as to avoid the frequent start or stop of flow
control operation within a short period of time.
The M900/M1800MSC/SSP/IP implements multi-level load control via various
interfaces, such as A-interface, C/D interface and TUP/ISUP/CAS signaling interface.
(For example, A-interface flow control is of 15 levels adopting the sliding window
strategy. In correspondence to levels 1-15, the allowed traffic is 1% - 100%).
Services restricted by the load control of the interfaces are:
z
A-interface: restricting the call services of intra-MSC MOC and MTC.
C/D interface: restricting location update, supplementary services and short

message service by restricting MAP messages.
TUP/ISUP/CAS signaling interface: restricting incoming calls by restricting TUP

messages.
II. Load control according to trunk circuit occupancy

The number of reserved circuit of the M900/M1800 MSC/SSP/IP trunk group can be
flexibly set through the Client (WS) as the condition to start load control. Once the
system finds that idle circuits are less than the reserved circuits, it will start load
control. The control is only orients to ordinary subscribers, that is, the system will reject
calls of ordinary subscribers. Preferential subscribers can still make normal calls. The
meaning of reservation is that the circuits are reserved for preferential subscribers.
This function guarantees the communications of preferential subscribers in peak hours.
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
System Description
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.
5.4 Signaling Policing Function

5.4.1 MAP Policing Function
The MAP Policing function of M900/M1800 MSC/SSP/IP features:
z
Determining the OSP to be monitored according to OPC or GT.
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.
5.4.2 SCCP Policing Function

The SCCP Policing function of M900/M1800 MSC/SSP/IP features:
z
The corresponding information can be shielded according to the calling address,

or the called address, or the combination of the calling & called addresses.
The SCCP message can be shielded according to the 24 ways of combination

formed by the elements of the calling/called addresses' DPC, SSN, GT and GTT
(GT Translation).
It offers the traffic measurement for the SCCP policing function.
This function can prevent the unauthorized use of the network resource, so that the
network security can be greatly enhanced.
5-9
Technical Manual
System Description
5.5 Reliability Measures for Charging System

The charging system of the M900/M1800 MSC/SSP/IP is responsible for collecting
detailed call data, generating the bills and sending them to the Billing Center as the
reference for charging subscribers or inter-network accounting.
The charging system consists of the related modules in MSC and the iGateway Bill
(iGWB). The call control module in MSC generates detailed charging information
according to call types and saves them in a buffer area (bill pool) of the GPSC board.
Between the GSPC board and the iGWB is the network connecting them. Through the
sliding window protocol, the bills of the bill pool are securely delivered to the iGWB.
The iGWB saves these bills and makes further processing. The iGWB sets up local or
remote connection with the Billing Center using FTAM or FTP to deliver the bills to the
Billing Center. The user may view the bills of the iGWB through the bill console of the
WSs.
Two connection modes are adopted between iGWB and the Billing Center: near-end
mode and far-end mode.
In the near-end connection mode, the bill collector of the Billing Center connects to the
iGWBs via LAN and makes data collection and preprocessing, then sends the bill
information to the Billing Center via DDN or X.25 network.
In the far-end connection mode, the bill connector of the Billing Center connects to the
local routers via DDN or X.25 network for the data collection. The user may browse and
query the bills from the local WSs or remote WSs.
5.5.1 Active/Standby Operation Mode

I. Power supply
Redundancy configuration is available for power supply: -48V DC is adopted for
guaranteed safety.
II. Active/standby iGWB servers

High-performance enterprise-level servers are adopted with two servers working in the
active/standby mode. Up to 5 heartbeat paths can be supported between the active
and standby servers (generally two paths are adopted), thus ensuring the correct
switchover between the active and standby servers in abnormal cases.
III. Active/standby GSPC boards

When the active GSPC board is working abnormally or its communication with the
iGWB is abnormal, the service will be automatically switched over to the standby GSPC
5-10
Technical Manual
System Description
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.5.2 Reliable Storage of Charging Data

From the completion of a call to the sending of the bill information to the Billing Center,
the charging data experiences four-level buffering to avoid loss due to abnormalities.
The four levels of buffering are: Host bill pool buffering, original bill file buffering, final
bill file buffering and automatic or manual MO disk backup.
I. Host bill pool buffering

The buffering area provided by each group of GSPC boards is 53 MB. It can store
about 260,000 original bills.
II. Buffering of original bill files

After the original bills are sent through the self-defined sliding window protocol to iGWB
from the bill pool, they will be immediately saved to the hard disk (Level 2 buffering).
The iGWB assigns each charging data packet a unique and continuous packet number
to ensure the security of each data packet. The iGWB will save the original charging
data and send the confirmation information to the Host. At the same time, it will record
the current bill confirmation status in detail to make sure no bill is lost or repeated. By
saving the number of the data packet and via the recovery process based on the packet
number after each starting, the consistency of data between original bills and final bills
can be guaranteed.
III. Buffering of final bill files

After the iGWB has processed the original bills according to the configuration, it will
save the final charging data that are provided to the Billing Center to the hard disk
(Level 3 buffering).
5-11
Technical Manual
System Description
IV. Network backup function

The iGWB can periodically copy the charging data from the disk to specified computer
via TCP/IP network. It can also accept operation commands to achieve manual backup
of charging data.
5.5.3 Error Tolerance of Bill Storage Disk

Original bills and final bills are saved in the disk of the iGWB server. To improve disk
error tolerance, the Raid 5 and hot spare techniques are adopted.
z
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.5.4 User Access Security Measures

The iGWB of the M900/M1800 MSC/SSP/IP is the server storing and processing bills.
As the Client terminal, the bill console is the JAVA and Web-based application. The
authorized user may start the bill console through any Web browser (e.g. IE5.0) and
access the iGWB server. To ensure the charging data security of the iGWB, security
design has been adopted for the user access.
I. Separation of public network from private network

In the iGWB server, multiple network adapters are distributed in different network
sections. No message will be transferred in between. External users are separated
from internal private network.
II. Protection by user name and password

To log on to the bill console, user name and password are needed. The user can be
automatically logged out in case there is no operation in a certain time, so unauthorized
operations by other persons can be avoided.
III. Operation restriction of the bill console

At the bill console, users can only perform browse operations on charging data, logs
and alarms. No deletion and modification can be made through it. The safety of
charging data is hence ensured.
5-12
Technical Manual
System Description
IV. Restriction of IP address of the bill console

By configuring the Web Server in the iGWB, the IP address of the bill console can be
restricted to prevent the access by unauthorized nodes.
5.6 Reliability Measures for O&M System

The O&M system of the M900/M1800 MSC/SSP/IP is mainly composed of the O&M
module, the BAM and WSs.
The O&M module includes the alarm submodule, performance measurement
submodule and equipment maintenance submodule.
The BAM is the core of the O&M system. It is composed of a high performance
enterprise-class server. As the server end of the TCP/IP, one end of the BAM responds
to the Client terminal requests and completes the analysis and processing of the
commands from the Client terminals, the other end responds to the connection request
from the MSC and completes such tasks as receiving alarm information from the MSC
and request for data loading.
5.6.1 BAM Disk Error Tolerance & Network Adapter Binding

I. Disk error tolerance
In the BAM server, SQL server program and BAM server program are installed and key
data necessary for the system operation such as office data, performance
measurement data and alarm information are stored. Therefore, high reliability of the
disk is required.
In the aspect of disk error tolerance, the Raid 1 disk array is adopted. If one disk of the
array is damaged, no data will be lost.
II. Binding of network adapters

To ensure the reliability of the communication between the BAM and the active/standby
boards of the MSC (including GSPC, AMP and CDP), the network adapter binding
technique is adopted with redundancy backup (2 network adapters). After the two
network adapters connected to the MSC are bound, the fault of one network adapter
will not affect the communication between the BAM and the Host.
5.6.2 Emergency Workstation

The Emergency Workstation (WS) has the functions of a simple BAM server as well as
the Client terminal functions of a local workstation. When an abnormality occurs to the
5-13
Technical Manual
System Description
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.6.3 User Access Security Design

M900/M1800 MSC/SSP/IP is well designed for the security of user access, thus
ensuring safe operation and maintenance on the system.
I. Separation of public network and private network

The BAM-host communication network adapter and the BAM-WS communication
network adapter are in different network sections. No message will be transferred in
between. External users and internal private network are separated.
II. Protection by user name and password

To log into WS, user name and password are needed. The user will automatically log
out when there is no operation within a certain period of time. In this way, the access of
unauthorized user can be avoided.
III. Hierarchical management on WS authorities

In M900/M1800 MSC/SSP/IP, the operation & maintenance (O&M) system performs
hierarchical management on the authority of users and WSs. An MML command can
only be executed in the O&M system when both the operator and WS have the
authority. This authority management mode features that one user cannot perform all
operations on all workstations even he is a super-user. Usually, workstations are
geographically distributed; therefore, such mechanism can provide centralized control
of important commands based on decentralized management, ensuring system safety
without the loss of flexibility.
IV. Security management of remote maintenance terminal

When WS is operated and maintained via Internet, the remote maintenance terminal
will encrypt the commands issued. The commands will be decrypted only when they
5-14
Technical Manual
System Description
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
System Description
Chapter 6 Technical Indices

This chapter describes the main technical indices of the M900/M1800 MSC/SSP/IP,
including system capacity, performance, physical features of external interfaces,
environmental requirements, etc.
6.1 Product Performance

6.1.1 Availability
Availability: The usable or workable state of the product when it is started.
I. Performance indices when M900/M1800 MSC/SSP/IP serves as GMSC

Item
Index
Maximum BHCA (Busy Hour Call Attempt)
6,000 k
Maximum traffic volume
48,000 Erl
Maximum number of supported trunks
4,096 PCM links
Maximum number of SS7 links to be supported
1,024 links
Maximum load of SS7 signaling link
0.8 Erl
Maximum message processing capability
307,200 MSU/s
Capacity of GT table
60,000
GT translation capability
46,080 GTT/s
II. Performance indices when M900/M1800 MSC/SSP/IP serves as VMSC

Item
Index
Maximum BHCA (Busy Hour Call Attempt)
4,800 k
Maximum traffic volume
30,000 Erl
Maximum number of subscribers
1,000,000 (0.03 Erl per subscriber)
Maximum number of SS7 links to be supported
1,024 links
Maximum load of SS7 signaling link
0.8 Erl
Maximum message processing capability
307,200 MSU/s
VLR capacity
1,000,000 subscribers
6-1
Technical Manual
System Description
Item
Index
Capacity of GT table
60,000 items
GT translation capability
46,080 GTT/s
III. Support of intelligent service

Item
Index
Maximum number of intelligent subscribers supported
1,000,000 subscribers (3 kinds of intelligent

services per subscriber)
Amount of resources and channels (tone resource,

DTMF transceivers, MFC registers, conference call)
10,584
6.1.2 Reliability Indices

Reliability: The capability of completing specific task under specific conditions and
within specified period.
Item
Index
Availability
0.99999513
MTBF (Mean time between failures)
102,600 hours
MTTR (Mean time to repair)
0.5 hours
Mean system down time per year
0.04267 hours
I. The definition of "system down"

"System down" means the system failure (due to hardware or software fault, operating
system fault, office data error or program error) lasting over 30 seconds, during which
subscriber cannot make, complete or receive calls.
Mean system down time: the mean value of all system down times (lasting over 30
seconds) in a period, during which the system can not handle any calls.
System down starts on the loss of originating services or terminal services of all
subscribers or trunks. For fully decentralized-control switching system, system down
starts when 50% subscribers or 50% trunk loses the originating or terminal services.
System down is ended on any of the following three conditions:
z
At least 90% subscriber lines serve originating calls or terminating calls.
At least 90% trunks can be used for incoming calls and outgoing calls.
6-2
Technical Manual
z
System Description
At least 90% switching system recovers the capability of call handling.
II. Reliability prediction

The following methods are used for the prediction of system reliability.
z
Board reliability
Method I Case I/II of Bellcore Reliability Prediction Procedure for Electronic Equipment
z
System reliability
Markov model for repairable system.
Note:
The reliability prediction for units and system adopts RELEX software kits.
III. M900/M1800 MSC/SSP/IP reliability prediction

The system reliability model is shown in Figure 6-1.
Main
control
cabinet
Resource
cabinet
Service
processing
cabinet
Integrated
Management
Cabinet
Interface
cabinet
Figure 6-1 M900/M1800 MSC/SSP/IP system reliability model

Predicted results of unit reliability are listed in Table 6-1.
Table 6-1 Indices of unit reliability
Reliability Indices
Name of Unit
Hardware and software

-9
failure rate X10 /h
Hardware failure rate

-9
X10 /h

MTBF(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
System Description
Reliability Indices
Name of Unit

-9
failure rate X10 /h
Hardware failure rate

X10- 9 /h

MTBF(h)
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
Predicted result of system reliability MTBF==102,600 hours (4,275 days)
6-4
Technical Manual
System Description
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
Unavailability U=1-A=0. 00000487

Mean system down time per year = 8,760 % 0.00000487 = 0.04267 hours
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.1.4 Power Consumption

Each cabinet is configured with power distribution box and fans:
Power consumption of the power distribution box: 20W
Power consumption of the fan block: 130W
The maximum power consumption of various cabinets in full configuration is given
below.
6-5
Technical Manual
System Description
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.
I. Main control cabinet

The power consumption of Main Control cabinet includes the consumption of Power
Distribution Box, fan, CNET frame, CPM frame, Clock frame and CCM frame.
The power consumption of each frame is as follows:
z
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 CPM frame in full configuration 130W.
Power consumption of Clock frame 46W.
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.
II. Interface cabinet

The power consumption of Interface cabinet mainly includes the power consumption of
Power Distribution Box, fans and 4 LIM frames.
The power consumption of the LIM frame depends on the boards configured in the
frame.
z
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
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
System Description
III. Resource cabinet

The power consumption of Resource Cabinet includes the power consumption of Power
Distribution Box, fans, 2 LIM frames and 2 SRM frames.
The power consumption of SRM frame is 175W when it is fully configured with
GSPT/GSRC boards.
The power consumption of the LIM frame is 210W when it is fully configured with GMHI
boards.
IV. Power consumption of service processing cabinet

The power consumption of Service Processing Cabinet includes the power
consumption of Power Distribution Box, fans and 4 SPM frames.
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.
boards.
boards.
boards.
V. Power consumption of service processing and line interface cabinet

cabinet
The power consumption of Service Processing Cabinet includes the power
consumption of Power Distribution Box, fans, 2 LIM frames and 2 SPM frames.
The power consumption of the LIM frame depends on the boards configured in the
frame.
z
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
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
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
z
System Description
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
boards.
boards.
boards.
boards.
VI. Integrated management cabinet

Power consumption of Integrated Management Cabinet is about 700W.
6.1.5 Clock Indices

The reliability of M900/M1800 MSC/SSP/IP clock system is ensured by the
Active/Standby structure. Phase locking Technology adopts Digital Phase-lock Loop
and reliable software phase locking to achieve clock synchronization.
M900/M1800 MSC/SSP/IP clock system is fully compliant with related international
standards including Bellcore GR-1244-CORE, ITU-T G.812 G.823 G.703, etc.
The clock system extracts and recovers clock signals from the clock reference offered
by BITS equipment or high-level switching equipment. The signal form of clock
reference source may be E1 (2.048Mbit/s), 2.048MHz or 8kHz, the types of output
signals include 2.048MHz and 8kHz differential signals. The clock stratum supported
may be stratum 2 or stratum 3. There are four operating modes available, including fast
pull-in, locked, holdover and free-run. The system provides the functions of coarse
frequency tuning or fine tuning, which can be done on-site. It also provides reference
switchover function.
The technical indices of the lock system are listed in Table 6-2.
6-8
Technical Manual
System Description
Table 6-2 Technical indices of clock system

Serial No.
Item Name
Indices and Functions

Minimum
accuracy
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
Stratum-2 clock: 5%10-10/day
Initial maximum
frequency offset
Stratum 2 clock: <5%10-10/day
Ideal
status
operation
Stratum-3 clock: 2%10-8/day
Stratum-3 clock: <1%10-8/day

MRTIE 1ms
MRTIE (ns) a%s+(1/2) %b%s2+c
Long-term
phase variation
Where S denotes time (with the unit of

second), the unit of MRTIE is ns.
Holdover
operation status
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
Fast pull-in, locked, holdover and free-run.
Redundancy of
clock
There are two independent clocks with the same performance. If one
clock fails, the other can function immediately.
Clock
maintainability
Coarse adjustment and fine adjustment of clock frequency are

available for each stratum, and it can be done on-site.
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
Serial No.
System Description
Item Name
Indices and Functions
Display function
Operation mode of the clock (fast pull-in, locked, holdover or

free-run) can be displayed. The frequency reference and clock in
use, last switchover time of frequency reference and manually forced
status can be displayed.
Control function
Clock operation mode can be selected. Frequency reference and

clock can be switched.
10
Input
tolerance
Refer to Figure 6-2
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)
Peak-peak jitter and wander degree

(logarithmic scale)
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
System Description
6.2 Physical Features of the Cabinet

Item
Cabinet dimensions (depth x
width x height) (mm)
Weight of a cabinet (kg)
Specification
Assembled cabinet
880(with side panels)%550%2100(with top

cover)
B68-21 cabinet
800(with side panels)%600%2100(with top

cover)
Assembled cabinet
310kg (in full configuration)
B68-21 cabinet
440kg (in full configuration)

4 (for 0.2 million subscribers)
Number of cabinets (not including Power

Distribution Cabinet)

9 (for 1 million subscribers)
6.3 Features of External Physical Interfaces

6.3.1 E1 Interface
Through GE16/GETS/GECS boards in Interface cabinet, M900/M1800 MSC/SSP/IP
provides E1 interfaces which can connect with 75: coaxial cable or 120: twisted pair.
Input/output E1 signal of related boards are isolated from external E1signal by
transformer, whose isolating voltages is up to 500Vrms.
The boards also offer the following protective measures:
1)
Transient high-voltage protection circuit at the side of E1 line
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
from the damage by transient low voltage

The parameters are:
z
Continuous peak backward voltage:18V
Continuous peak positive current:12A
Backward leakage current: 2 "AC V" A
Signal frequency: 2.048MHz.
Transmission signal code: HDB3.
Transmission distance: <=1200m.
Clock jitter: <=3ns.

6-11
Technical Manual
System Description
6.3.2 SDH Optical Interface

The functions of STM-1 SDH optical/electrical interface are implemented by the GSTU
in the Interface Frame.
Each GSTU board provides 63 uplink/downlink E1s to the SDH network via the STM-1
(155Mbit/s) interface. Data and signaling will be first separated from the downlink E1
signals, and then respectively be multiplexed into eight 16.384MBit/s HWs for service
signals and two 2.048MBit/s HWs for inter-module signaling. Then the GQSI converges
them and sends the service signals to the CNET and the signaling to the CPM. The
signals sent to STM-1 are processed in reverse direction.
Each GSTU board occupies two slots, and each LIM frame can provide at most four
STM-1 interfaces.
z
Optical link rate of the optical interface: 155.52Mbit/s.
Each optical channel provides eight 16.384Mbit/s (256 timeslots) traffic HWs and
two 2.048Mbit/s HWs (can be expanded to 4).
Transmission wave length: 1310nm
Average transmitted optical power: -8~-14dBm
Minimum extinction ratio: 8.2dB
Minimum sensitivity of optical interface: -28dBm
The electrical interface indices comply with requirements stated in G.703.
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
System Description
6.4 Environmental Requirements

M900/M1800 MSC/SSP/IP meets the following environmental requirements:
z
GR-63-CORE Network Equipment-Building System (NEBS) Requirements:

Physical Protection
ETS 300 019-2-1(~3) Environmental Conditions and environmental tests for

telecommunications Equipment
IEC60721-3-1(~3)Classification of groups of environmental parameters and their

seventies
ETS 300 753 Acoustic noise emitted by telecommunications equipment
6.4.1 Grounding Requirements

M900/M1800 MSC/SSP/IP has three groundings, namely work grounding, protection
grounding and lightning protection grounding. The grounding conditions should meet
the grounding specifications of Huawei equipment.
I. General principles
z
The grounding conductor, as coarse and short as possible, shall be made of

copper conducting wire so as to minimize high-frequency impedance.
The grounding terminal should be treated with anti-corrosive measures, and

secured with bolts to ensure good contact.
To reduce mutual interference, the grounding cables shall not be in parallel or

wound up with signal cables.
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.
To install the M900/M1800 MSC/SSP/IP, the equipment buyer should provide

three types of grounding cables, i.e. work grounding cables, protection grounding
cables and lightning protection grounding cables. Since the protection grounding
cables were already there during the general building construction, the other two
types of grounding cables are still needed. If only two of them are available, then
one should be used as the lightning protection grounding cables and the other as
work grounding cables.
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
System Description
II. Grounding resistance

The grounding resistance should be less than 1 ohm.
III. Grounding inside the system

To reduce the mutual interference between analog signals and digital signals, the PCB
is so designed that the analog signal grounding points are separated from the digital
signal grounding points and they are connected together to a single point inside the
power distribution box. The terminals +5VGND and GND are already connected upon
factory delivery to act as the work grounding cables.
To effectively reduce the system noise of M900/M1800 MSC/SSP/IP and suppress the
external interference, it is required that the M900/M1800 MSC/SSP/IP cabinet be
directly connected to its work grounding cables.
6.4.2 Ambient Temperature and Relative Humidity

I. Operation environment
The temperature range for short-term (safe) operation is -5C~+55C, and humidity
range is 5%~95%(1~29g/m3). The temperature range for long-term (normal) operation
is +5C ~+45C, and humidity range is 5%~85%(1~25g/m3).
II. Storage environment

The temperature range for storage is -40C ~+70C, and humidity range is
10%~100%.
III. Transportation environment

The temperature range for transportation is -40C ~+70C, and humidity range is
5%~100%.
6.4.3 Cleanness
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
System Description

The system meets the requirements of EUROPEAN ETS 300 019-1-1 "not
Temperature-controlled storage":
Falling dust
20 mg/m2h
Suspending dust
5.0 mg/m3
Sands
300 mg/m3

The system meets the requirements of EUROPEAN ETS 300 019-1-2 "Class 2.3 public
transportation":
Falling dust
3.0 mg/m2h
Suspending dust
No requirements
Sands
100 mg/m3
6.4.4 Lighting
The
system
meets
the
requirements
of
EUROPEAN
ETS
300
019-1-3
"Temperature-controlled locations". During normal operation of the system, the sun

radiation should be no more than 700W/m2 and heat radiation no more than 600W/m2.
Comfortable and reasonable lighting is required.

Temperature-controlled storage". For safe storage, the sun radiation should be no
more than 1120W/m2, and heat radiation no more than 600W/m2.

transportation". For safe transportation, the sun radiation should be no more than
1120W/m2, and heat radiation no more than 600W/m2.
6-15
Technical Manual
System Description
6.4.5 Atmospheric Condition

The
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
0.1 ~0.5 mg/m3
Cl2
0.1 ~0.3 mg/m3
HCl
0.1 ~0.5 mg/m3
NOx
0.5 ~1.0 mg/m3
NH3
1.0 ~3.0 mg/m3
HF
0.01 ~0.03 mg/m3
O3
0.05 ~0.1 mg/m3

Temperature-controlled storage".
Air pressure
70 ~106kPa
Wind speed
30 m/s
Sulfur Dioxide
0.3~1.0 mg/m3
Hydrogen Sulfide
0.1 ~0.5 mg/m3
Cl2
0.1 ~0.3 mg/m3
HCl
0.1 ~0.5 mg/m3
NOx
0.5 ~1.0 mg/m3
NH3
1.0 ~3.0 mg/m3
HF
0.01 ~0.03 mg/m3
O3
0.05 ~0.1 mg/m3
6-16
Technical Manual
System Description

transportation".
Air pressure
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
6.4.6 Floor Bearing Capacity

The bearing capacity of the floor for M900/M1800 MSC/SSP/IP should be 400kg/m2.
6.4.7 EMC (Electromagnetic Compatibility)

M900/M1800 MSC/SSP/IP satisfies the specifications defined in ETSI EN 300 386
V1.2.1 (2000-03). The following party gives the indices of Electromagnetic Interference
(EMI) and Electromagnetic Sensitivity (EMS).
I. EMI indices
z
Conductive Emission (CE)
Table 6-3 Conductive interference limit of -48V power supply port

Limit value (dB V)
Frequency range
Average
Peak
0.02 MHz ~ 0.15 MHz
79
0.15 MHz ~ 0.50 MHz
66
79
0.50 MHz ~ 30 MHz
60
73
Radiation Emission (RE)
6-17
Technical Manual
System Description
Table 6-4 Radiation interference of 48V communication port

Frequency band (MHz)
Limit value (dBV)
0.02~0.50MHz
0.50~30MHz
Average
Peak
40~30
53~43
30
43
Table 6-5 Radiation interference limit

Frequency band (MHz)
Quasi-peak value limit (dBV/m)
30~230
50
230~1000
67
Note:
The measurement point should be at a distance of 10 m from the switching equipment.
II. EMS indices

z
Conduction Sensitivity (CS)
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
150 kHz ~ 80 MHz
3V
3V
Signal port
Radiation Sensitivity (RS)
This is a system-level index.

Table 6-7 Emission sensitivity indices
Frequency range
Voltage class
Performance class
80 MHz ~ 1 GHz
3 V/m
Electro-Static Discharge (ESD)
6-18
Technical Manual
System Description
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
Electronic fast transient pulse burst (EFT)
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
Indoor (system internal

cabling)
Voltage class
0.5 kV
6-19
Performance
class
C
Technical Manual
System Description
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
Technical Manual
Technical Manual
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
Table of Contents
3.2.7 Shared Resource Module (SRM) Frame .............................................................. 3-22

3.2.8 InterWorking Function (IWF) Frame...................................................................... 3-23
Chapter 4 Board............................................................................................................................. 4-1
4.1 Functions and Features ..................................................................................................... 4-1
4.2 Board Structure.................................................................................................................. 4-1
Chapter 5 Power Supply System ................................................................................................. 5-1
5.1 Structure ............................................................................................................................ 5-1
5.2 AC Power Supply System.................................................................................................. 5-1
5.3 DC Power Supply System ................................................................................................. 5-2
5.4 DC Power Distribution Cabinet .......................................................................................... 5-5
5.5 Cabinet Feed System ........................................................................................................ 5-5
Chapter 6 Clock Synchronization System .................................................................................. 6-1
6.1 Overview ............................................................................................................................ 6-1
6.2 Architecture of Clock Synchronization System.................................................................. 6-2
6.2.1 Configuration of Clock Module (CKM) Frame ......................................................... 6-2
6.2.2 Control Structure of Clock System .......................................................................... 6-3
6.2.3 Allocation of Clock System Signals......................................................................... 6-3
6.3 Hardware Configuration of Clock Synchronization System ............................................... 6-4
6.3.1 Clock Reference Source ......................................................................................... 6-4
6.3.2 Configuration for Extracting Clock Source from Trunk............................................ 6-4
6.3.3 Configuration for Leading in Clock Signals from BITS............................................ 6-5
6.4 Parameter Configuration of Clock Synchronization System.............................................. 6-5
ii
Technical Manual
Chapter 1 General Introduction

This chapter introduces briefly the hardware architecture and features of M900/M1800
MSC/SSP/IP, and the correspondence between respective functional modules and
frames.
1.1 Overview of Hardware Architecture

M900/M1800 MSC/SSP/IP is developed on the basis of the hardware platform of
Huawei C&C08 switching system. Its hardware architecture is shown in Figure 1-1.
8k0~8k31
2M0~2M31
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
CKM: Clock Module

CNET: Central Switching Network Frame
SRM: Shared Resource Module
VDB: VLR Database
HOFL: High speed Optical Fiber Link
OMC: Operation & Maintenance Center
SPM: Service Processing Module
XPTU: X Protocol Transfer Unit
IWF: InterWorking Function module
CCM: Communication Control Module

LIM: Line Interface Module
CLK: Clock signal
2M Link: 2Mbit/s high-speed signaling link
HDLC: High-level Digital Link Control Procedure
BAM: Back Administration Module
STM-1 Synchronous Transfer Mode 1
CPM: Central Processing Module
CDB: Central Database

WS: WorkStation
LAN: Local Area Network
E1: Primary rate
WS: WorkStation
WAN: Wide Area Network
iGWB: Charging Gateway
LIC: Lawful Interception Center
Figure 1-1 Hardware architecture of M900/M1800 MSC/SSP/IP

CNET is a T%T%T 3-level fully-utilized central switching network. It is the service data
switching core of M900/M1800 MSC/SSP/IP. The capacity of CNET can be smoothly
expanded from 16%16k to 128k%128k (in step of 16k%16k) by adding boards. CNET is
connected to LIM by the 393Mbit/s HOFL.
1-1
Technical Manual
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
1.2 Hardware Architecture Features

1.2.1 Modular Design
The modular design of M900/M1800 MSC/SSP/IP hardware achieves the seperation of
the functional entites of network switching, service processing and resource provision,
enabling smooth capacity expansion by simple physical overlay without disturbing
system stability.
To expand the capacity of the Central Switching Network (CNET) module, just add
GSNU boards. To expand the capability of the Service Processing Module (SPM ), add
SPM modules. To enlarge the number of external trunks of the system resource module,
add LIM frames.
1.2.2 Dual Network and Dual Plane

M900/M1800 MSC/SSP/IP has two switching networks: service data switching network
and control data switching network. The control data switching network consists of two
highly reliable network planes which work in load-sharing mode..
I. Service data switching network

By connecting CNET, the core of the service data switching network, to the GQSI
boards of LIM frame with the 393Mbit/s optical fibres, the service data switching
network is formed.
Service switching network is also connected to the other external trunks or modules via
the other interface boards of LIM frame, forming an integrated swtiching system that
provides circuit swithing for trunk, signaling and service resources.
Voice switching is directly accomplished by LIM and CNET, as shown in Figure 1-2.
CNET
LIM
Voice
GE16/GSTU
E1/STM-1
G
Q
S
I
393M
HOFL
LIM
393M
HOFL
CNET
Figure 1-2 Voice switching

1-3
G
Q
S
I
E1/STM-1
GE16/GSTU
Technical Manual
The processing of common channel signaling is accomplished by establishing

semi-permanent connection between GCPC board and the common signaling channel
of a trunk, as shown in Figure 1-3.
CNET
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
Figure 1-3 Processing of common channel signaling

The processing of call resource is accomplished through timeslot switching between
the resource board (GSRC/GSPT) in SRM and the speech channel of the network
board, as shown in Figure 1-4.
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
Figure 1-4 Processing of call resource

IWF is also need at the switching side of the circuit data, as shown in Figure 1-5.
1-4
Technical Manual
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
Figure 1-5 Switching of circuit data
II. Control data switching network

By connecting CCM, the core of the control data switching network, to various modules
with the HDLC links (signaling HW), the control data switching network is formed.
Control data switching network is in charge of inter-module frame switching of control
data and inter-module communication.
Control data switching network, backplane bus communication, serial port
communication and network interface communication form the control system of
M900/M1800 MSC/SSP/IP, as shown in Figure 1-6.
1-5
Technical Manual
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
(2Mbit/s signaling link)
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
Figure 1-6 Communication control system

The control data switching network consists of two planes, each of which transmits
control data according to specific load-sharing rules. When one plane fails partially or
completely, the other will take over all loads automatically.
The control data switching network is in charge of inter-module communication (bus
communication and serial port communication).
iGWB and BAM communicate with the MSC via the Ethernet. iGWB communicates
with GSPC board only, while BAM communicates with CDP, AMP and GSPC boards.
Note that the communication between LIM and SRM does not adopt special signal
cables to transmit control data, but employs 4 timeslots in the service HW that transmits
service data, as shown by the dotted line in Figure 1-6.
In addition, AMP communicates through GALM with PWC, GPWS and GAMD boards
via the emergency serial port.
1-6
Technical Manual
1.2.3 Resource Sharing and Centralized Management

Various resources needed for service processing in M900/M1800 MSC/SSP/IP include:
signal tone, dual tone number receiver, dual tone number sender, multi-frequency
compelled transceiver, echo cancellation pool and network interworking resource.
These resources do not belong to any service processing module, but are shared
globally. They are managed by the Central Database (CDB) of the CDP board on a
unified and centralized manner. When an SPM needs these resources, it must apply to
CDB for them.
System maintenance and equipment management of M900/M1800 MSC/SSP/IP are
implemented by the pair of active/standby AMP boards of the Central Processing
Module (CPM).
AMP board handles all maintenance commands from BAM. It communicates with
various boards via HDLC links, buses, serial ports, etc. to perform board data
configuration, equipment status information collecting, equipment alarm processing,
and module status broadcasting, etc.
1.3 Functional Modules

Each functional module of M900/M1800 MSC/SSP/IP system usually corresponds to a
specific frame, as shown in Table 1-1. BAM and iGWB correspond respectively to BAM
server and charging gateway server in the Integrated Management (IMM) cabinet.
Table 1-1 Correspondence between functional units and frames
Module name
Frame name
CKM
Clock frame
CCM
Communication Control frame
CPM
Central Processing frame
CNET
Central Switching Network frame
LIM
Line Interface frame
SRM
Shared Resource frame
SPM
Service Processing frame
IWF
InterWorking Function frame
1-7
Technical Manual
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 Physical Characteristics

2.1.1 Cabinet Type
M900/M1800 MSC/SSP/IP cabinets include: main control (AM) cabinet, interface (LIM)
cabinet, service processing (SPM) cabinet, resource (SRM) cabinet and integrated
management (IMM) cabinet. The AM cabinet, LIM cabinet, SPM cabinet and SRM
cabinet are assembled cabinets, while the IMM cabinet is B68-21 cabinets.
2.1.2 Design Features

The side panels of assembled cabinets and B68-21 cabinets adopt suspended
quick-assembly structure, while the front and back doors adopt latch locking structure
that enables easy assembling and disassembling. The cabinets are designed with
upper and lower outlet holes for convenient cable routing.
2.1.3 Cabinet Material

The cabinets are made of cold rolled steel plates. The fire-proof performance of internal
materials is in compliance with the UL standard 94.V0.
2.1.4 Dimensions and Weight

I. Assembled Cabinet
Cabinet dimensions:
Length: 800mm (without side panels)
Width: 550mm
Height: 2100mm (with top cover)/1,945mm (without top cover)
Side panel dimensions:
Height: 2100mm
2-1
Technical Manual
Chapter 2 Cabinet
Width: 550mm
Depth: 40mm
Weight: 224kg (when empty), 310kg (in full configuration)
II. B68-21 Cabinet

Cabinet dimensions:
Length: 600mm (without side panels)
Width: 800mm
Height: 2100mm (with top cover)/1976.5mm (without top cover)
Weight: 130kg (when empty)
2.1.5 Other Features

M900/M1800 MSC/SSP/IP cabinet features excellent shielding, wiring, dust prevention
and heat radiation performance.
The assembled cabinet has three fans at the top and three at the bottom to form a
closed cooling system. The B68-21 cabinet adopts natural cooling mode, i.e. wind
enters from the front and the bottom of the cabinet and is discharged from the back and
the top.
2.1.6 Cabinet Installation

The assembled cabinets and the B68-21 cabinets can be installed on cement floors or
on antistatic floors. An accessory code and operation instructions are provided for each
support. The cabinets also provide special mounting holes for shockproof
reinforcements and supports are provided.
Each assembled cabinet has mounting holes for fastening bolts for combination.
2.2 System Configuration

2.2.1 Standard Configuration of M900/M1800 MSC/SSP/IP as VMSC
I. Standard configuration for 400,000 subscribers
This configuration is applicable to the capacity expansion or the newly established
exchange of M900/M1800 MSC/SSP/IP with the maximum capacity of 400,000
2-2
Technical Manual
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
SPM cabinet
AM cabinet
SRM cabinet
Fan box
Fan
box

Power distribution
box
SPM
LIM
Fan box

Power distribution
box
CNET
IWF
IWF
IWF
Integrated management cabinet
Dummy panel
Fiber rack
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
Dummy Fiber rack
LIM
SPM
Fiber rack
Dummy Fiber rack
LIM
SPM
Fiber rack
Dummy Fiber rack
LIM
Inverter
Controller
Inverter
CKM: Clock Module frame

CPM: Central Processing Module frame
LIM: Line Interface Module frame
IWF: InterWorking Function frame
LAN Switch: Ethernet Switch
SPM
Fiber rack
Dummy Fiber rack
Fan box
Fan box
Panel
Dummy Fiber rack
CNET
SRM
Fiber rack
Dummy Fiber rack
CPM
LIM
Dummy Fiber rack
Fiber rack
CKM CCM
LIM
Dummy Fiber rack
Fiber rack
Fan box
Fan box
CCM: Communication Control Module frame

CNET: Central Network transfer and switch frame
SPM: Service Processing Module frame
SRM: Shared Resource Module frame
Figure 2-1 Standard configuration for 400,000 subscribers
II. Standard configuration for 800,000 subscribers

exchange of M900/M1800 MSC/SSP/IP with the capacity between 400,000 and
800,000 subscribers. And the demand for IWF channels is lower than 28. The
recommended configuration is shown in Figure 2-2. Compared with the standard
configuration for capacity less than 400,000 subscribers, this configuration is added
with one LIM cabinet and one SPM cabinet.
2-3
Technical Manual
IMM cabinet
LAN Switch
Cable rack
LAN Switch
Chapter 2 Cabinet
LIM cabinet
Fan box
LIM
SPM cabinet
AM cabinet
SRM cabinet
LIM cabinet
SPM cabinet
Fan box
Fan box

Power distribution
box
Fan box
Fan box
IWF
LIM
Fan box

Power distribution
box
SPM
CNET
IWF
IWF
SPM
Dummy panel
Fiber rack
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
Dummy Fiber rack
CNET
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Dummy Fiber rack
Fiber rack
SRM
LIM
Fiber rack
Dummy Fiber rack
Fiber rack
CPM
LIM
LIM
Dummy Fiber rack
Fiber rack
CKM CCM
LIM
Dummy Fiber rack
Fiber rack
Fan box
Fan box
Fiber rack
LIM
Fiber rack
Fan box
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box

III. Standard configuration for 1000,000 subscribers

exchange of M900/M1800 MSC/SSP/IP with the capacity between 800,000 and
1000,000 subscribers. And the demand for IWF channels is lower than 28. The
recommended configuration is shown in Figure 2-3. Compared with the standard
configuration for capacity between 400,000 and 800,000 subscribers, this configuration
is added with one LIM cabinet and one SPM cabinet.
2-4
Technical Manual
IMM cabinet
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
Fan
box
box
Power
distribution
CNET
LIM cabinet
SPM cabinet
Fan box
Fan box
Fan box
LIM
IWF
IWF
SPM cabinet
Fan box
IWF
SPM
LIM
Empty
Fiber rack
Dummy Fiber rack
Dummy panel
Dummy Fiber rack
Fiber rack
BAM Server
PC switcher
Dummy panel
LCD platform
Dummy panel
iGWB Server
(Active)
iGWB Server
(Standby)
LIM
SPM
Fiber rack
Panel
CNET
Dummy Fiber rack
LIM
Dummy Fiber rack
LIM
SPM
Inverter
Inverter
Controller
Fiber rack
Dummy 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
Dummy Fiber rack

Fan box
Fan box
SPM
Fiber rack
Fiber rack
Dummy Fiber rack
CPM
Dummy Fiber rack

Fiber rack
Fiber rack
Dummy 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

2.2.2 Compact Configuration of M900/M1800 MSC/SSP/IP

The compact configuration is applicable to the capacity requirement of less than
200,000 subscribers, as shown in Figure 2-4.
DC distribution cabinet SPLIM cabinet
IMM cabinet
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
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
Dummy Fiber rack
SRM
Fiber rack
Dummy Fiber rack
CPM
LIM
Dummy Fiber rack
Fiber rack
CKM CCM
LIM
Dummy Fiber rack
Fiber rack
Fan box
Fan box

SPLIM: Service Processing and Line Interface Module
Figure 2-4 M900/M1800 MSC/SSP/IP compact configuration
2-5
Technical Manual
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
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
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

Dummy Fiber rack
Panel
CNET
SRM
Fiber rack
Dummy Fiber rack
CPM
LIM
Dummy Fiber rack
Fiber rack
CKM CCM
LIM
Dummy Fiber rack
Fiber rack
Fan box
Fan box
Dummy Fiber rack
SPM
Dummy Fiber rack
Dummy Fiber rack
SPM
Dummy Fiber rack
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

SPLIM: Service Processing and Line Interface Module
Figure 2-5 Capacity expansion by adding the SPLIM cabinet
2.2.3 Configuration of M900/M1800 MSC/SSP/IP as GMSC

The configuration of M900/M1800 MSC/SSP/IP as GMSC is shown in Figure 2-6. The
numbers of LIM cabinets, SPM cabinets and SRM frames are subject to actual
conditions.
2-6
Technical Manual
IMM cabinet
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
Integrated management Controller

cabinet
Inverter
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
Dummy Fiber rack
LIM
Panel
CNET
SPM
Fiber rack
Dummy Fiber rack
LIM
Fiber rack
Dummy Fiber rack
LIM
SPM
Inverter
Fiber rack
Fiber rack
SPM
SPM
Fiber rack
LIM
Dummy Fiber rack

Fan box
Fiber rack
LIM
Dummy Fiber rack
Fan box
Fan box
Fiber rack
LIM
Dummy Fiber rack
LIM
Fiber rack
Fan box

CNET: Central Switching Network frame
Fiber rack
LIM
Dummy Fiber rack
SPM
LIM
Fiber rack
Dummy Fiber rack
Fan box
Fiber rack
LIM
CKM CCM
Dummy Fiber rack
Fan box
Dummy Fiber rack
CPM
Dummy Fiber rack
LIM
SRM
Fiber rack
SPM
Fiber rack
Dummy Fiber rack
Fiber rack
Fan box
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box

SRM Shared Resource Module frame
Figure 2-6 Standard configuration of M900/M1800 MSC/SSP/IP as GMSC
2.2.4 Configuration of M900/M1800 MSC/SSP/IP with Lawful Interception

Function
Compared with the configuration of M900/M1800 MSC/SSP/IP without lawful
interception function, one XPTU cabinet is added in this configuration. The
configuration of M900/M1800 MSC/SSP/IP with lawful interception function supporting
800,000 subscribers is shown in Figure 2-7.
XPTU cabinet IMM cabinet
DC distribution
cabinet
AM cabinet
Fan box
Fan box
Fan
box
LAN Switch
Cable rack
LAN Switch
Power distribution
box
LIM
SPM
CNET
IWF
SRM cabinet LIM cabinet SPM cabinet
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
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
Panel
CNET
Dummy Fiber rack
LIM
SRM
Fiber rack
Dummy Fiber rack
CPM
LIM
Dummy Fiber rack
Fiber rack
CKM CCM
LIM
Dummy Fiber rack

Fan box

Fiber rack
LIM
Fiber rack
LIM
Fiber rack
Fan box
Fiber rack
Fiber rack
Fan box
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
SPM
Dummy Fiber rack
Fan box
XPTU: X Protocol Transfer Unit
Figure 2-7 Configuration of M900/M1800 MSC/SSP/IP with lawful interception function for 800,000 subscribers
2-7
Technical Manual
Chapter 2 Cabinet
2.3 Configuration of Functional Cabinets

2.3.1 Main Control Cabinet
The frames configured in the main control cabinet inlcude: Clock Module (CKM) frame,
Communication Control Module (CCM) frame, Central Processing Module (CPM)
frame and Central Switching Network (CNET) frame.These frames are responsible for
system clock synchronization, module communication, equipment maintenance,
resource management, network switching, etc., which constitute the core of
M900/M1800 MSC/SSP/IP system functions.
The configuration of the main control cabinet is shown in Figure 2-8, where CNET
module takes up two standard frames.
2-8
Technical Manual
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
GGG GGGGGGGGG GGGG

SSS SSSSSSSSS SSSS
NNN NNNNNNNNN NNNN
UUU UUUUUUUUU UUUU
0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7
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
Figure 2-8 Configuration of main control cabinet
2-9
Technical Manual
Chapter 2 Cabinet
2.3.2 Interface Cabinet

When fully configured, the interface cabinet is equipped with 4 Line Interface Modules
(LIMs) to provide line interfaces between the system and other network equipment.
Line interfaces include E1 interface, STM-1 optical interface and STM-1 electrical
interface.
The interface cabinet also provides echo cancellation function.
The interface cabinet can be configured in two ways: the configuration without
supportting Channel Associated
Signaling (CAS), as shown in Figure 2-9, and
configuration supporting CAS, as shown in Figure 2-10.
2-10
Technical Manual
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
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
Figure 2-9 Configuration of interface cabinet (not supporting CAS)
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
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
Figure 2-10 Configuration of interface cabinet (supporting CAS)
2-12
LIM
Technical Manual
Chapter 2 Cabinet
2.3.3 SPM Cabinet

When fully configured, the SPM cabinet is equipped with 4 SPMs to achieve the service
processing and the link layer protocol processing of signaling (including SS7, DSS1
and CAS signalings). In addition, one distributed database is embedded in the SPM
cabinet. When M900/M1800 MSC/SSP/IP serves as VMSC, the database will function
as VLR, storing VLR subscriber data. SPM also supports 2 Mbit/s high-speed signaling
links, and provides directly the E1 interface for the high-speed signaling links.
The configuration of the service processing cabinet is shown in Figure 2-11.
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
Figure 2-11 Configuration of service processing cabinet
2-13
SPM
Technical Manual
Chapter 2 Cabinet
2.3.4 Resource Cabinet

When fully configured, each resource cabinet is equipped with 2 LIM frames, 1 SRM
frame and 1 IWF frame. The SRM frame provides resources such as signal tones, dual
tone number receiver, dual tone number sender, MFC transceiver and conference call
resources required for the service processing. The IWF frame enables the interworking
with other networks (ISDN/PSTN). One IWF frame provides 28 IWF channels.
The configuration of the resource cabinet is shown in Figure 2-12.
2-14
Technical Manual
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
Figure 2-12 Configuration of resource cabinet (for VMSC)

When M900/M1800 MSC/SSP/IP serves as GMSC, two SRM frames should be
configured, since network interworking function is not needed, instead, the demands
for call resources increase. The configuration is shown in Figure 2-13.
2-15
Technical Manual
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
Chapter 2 Cabinet
G
P
W
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
25
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
Figure 2-13 Configuration of resource cabinet (for GMSC)
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
Chapter 2 Cabinet
2.3.5 Integrated Management Cabinet

Intergrated management cabinet is equipped with 3 severs (BAM server and the two
active/standby iGateway Bill (iGWB) servers), one LCD integrated control platform
(consisting of keyboard, mouse and LCD) and one power supply system (consisting of
power distribution box, two inverters and one inverter controller) and some auxiliary
devices (including switcher, disk array and LAN Switch).
IMM cabinet is shown in Figure 2-14 and Figure 2-15.
(1) Power distribution box

(4) Dummy panel
(7) Dummy panel
(10) rear view
(2) Dummy panel

(5) LCD integrated control platform
(8) Dummy panel
(11) LanSwitch
(3) BAM server

(6) Cross cabling troughs
(9) iGWB server
Figure 2-14 Assembly of integrated management cabinet (for DC power supply)
2-17
Technical Manual
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
(1) Rack of B68-21 server cabinet

(5) Ethernet switch
(9) LCD integrated control platform
(13) Wiring terminal
(2) Dummy panel

(3) Veneer plywood (4) Power distribution box
(6) Cross wiring trough
(7) Inverter
(8) Inverter controller
(10) Industrial PC switcher (11) BAM server
(12) iGWB Server
Figure 2-15 Assembly of integrated management cabinet(for AC power supply)
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
Chapter 2 Cabinet
Through BAM server, operations such as equipment maintenance, data configuration,

performance and alarm management can be performed.
The iGWB server accesses, stores and processes the bills generated by the MSC.
Meanwhile, it provides interfaces for bill management and to the Billing Center.
The networking of OMC system is shown in Figure 2-16.
GSPC1
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
AMP: AM Processing board

WS: WorkStation
BAM: Back Administration Module iGWB: iGateway Bill
HUB: Network hub
X.25: ITU-T X.25 protocol network
CDP: Central Database Processing board
Figure 2-16 Logical diagram of OMC Networking
2-19
Hub
GSPC: Service Processing board

DDN: Digital Data Network
Technical Manual
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
Chapter 2 Cabinet
2.3.6 SPLIM Cabinet

The Service Processing and Line Interface module (SPLIM) cabinet is used on the
MSC of which new capacity requirement or capacity expansion is less than 200,000
subscribers. The SPLIM cabinet can provide the trunk interface as the LIM cabinet and
the service processing ability as the SPM cabinet. However, the trunk capacity and the
service processing ability provided by the SPLIM are only half of that provided by the
LIM cabinet and the SPM cabinet respectively. The configuration of the SPLIM cabinet
is shown in Figure 2-17.
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
Figure 2-17 Configuration of SPLIM cabinet
2-21
24
25
Technical Manual
Chapter 2 Cabinet
2.3.7 XPTU Cabinet

As an independent cabinet, XPTU cabinet is used to meet the requirements for lawful
interception in different networking mode. For detailed description of its configuration,
please refer to the M900/M1800 MSC/SSP/IP Lawful Interception User Manual
2-22
Technical Manual
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.
3.1 Physical Characteristics

M900/M1800 MSC/SSP/IP frames include: CNET frame, CPM frame, CCM frame,
CKM frame, LIM frame, SRM frame SPM frame and IWF frame. CCM frame and CKM
frame are placed into one frame, each taking up half of the frame. Other frames (except
for CNET frame, which takes up two frame space) takes up one frame each.
A frame consists of circuit boards, backplane, front & back beams, side plates and
guide rails, as shown in Figure 3-1.
(2)
(1)
(3)
(4)
(10)
(5)
(9)
(8)
(6)
(7)
(1) Upper front beam

(5) Right side plate
(9) Lower front beam
(2) Left side plate

(6) Guide rail
(10) Board name strip
Figure 3-1 Frame structure
3-1
(3) Guide rails

(7) Dummy handle bar
(4) Upper back beam

(8) Plug-in board
Technical Manual
Chapter 3 Frame
3.2 Function and Configuration

The frame integrates the circuit boards into an independent functional unit, forming one
or multiple functional modules.
3.2.1 Clock Module (CKM) Frame

CKM provides 2.048 MHz clock and 8 kHz frame synchronization signals for the MSC
to synchronize it with the entire network. CKM has the following features:
I. Provision of Stratum 2 and Stratum 3 clocks

CKM provides Stratum 2 and Stratum 3 clocks, satisfying the requirements of different
exchanges such as GMSC, TMSC, VMSC, etc. The indices of this clock
synchronization system are up to or superior than corresponding international
standards, including ITU-T G.812 and G.823.
II. Extraction of clock reference signals from SDH

CKM provides two phase-locked modes: PDH and SDH. In SDH mode, the clock
system can reliably lock timing signals (pointer adjustment as high as 15) which take
SDH transmission system as inter-exchange timing transmission link, and "purify" the
clock signals to ensure service quality. When the timing signal quanlity transmitted
among exchanges is good, PDH mode is adopted.
III. Supporting Various clock reference sources

M900/M1800 MSC/SSP/IP system can either extract 8kHz clock from trunk E1 or SDH
or adopt the 2Mbit/s and 2MHz signals from peripheral clock equipment (such as BITS)
as its clock reference source. The equipment interface meets ITU-T G.703 standard.
CKM frame configuration is shown in Figure 3-2.
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
Figure 3-2 CKM frame configuration
3-2
12
Technical Manual
Chapter 3 Frame
The functions of the boards are as follows:

PWC (Secondary Power Supply Board): Supplies +5V power for boards. PWC boards
work in load-sharing mode. Maximum power consumption of the board is 100W.
GCKS (Clock Board): Traces and phase-locks the clock reference source and outputs
clock signals of the same frequency and phase characteristics as the reference source.
GCKD (Clock Drive Board): Drives clock signals generated by GCKS, and generates
32 channels of 8kHz and 2MHz clock signals.
AMP
AMD
8k0
8k31
2M0
2M31
8k0
8k31
2M0
2M31
The functional blocks of CKM frame are shown in Figure 3-3.
-48V
Reference source
--48V
PWC
+5V
PWC
GCKS
8kHz
2.048MHz
2.048Mbit/s
GCKD
8kHz
2.048MHz
GCKD
CKM
Figure 3-3 Functional blocks of CKM frame

In CKM frame, the tracing and phase-locking of external clock reference source and the
generation of 8kHz and 2MHz synchronization clock signals are performed by GCKS
boards.
GCKD board drives the clock signals and generates 32 channels of 8kHz signals and
32 channels of 2MHz clock signals, transmitting them to other modules of the MSC via
dedicated clock signal lines.
3.2.2 Communication Control Module (CCM) Frame

The Communication Control Module in CCM frame is in charge of inter-module data
transmission. CCM has two planes, each of which provides 56 signaling HWs. In total,
a CCM plane can provide interfaces for a maximum of 448 64kbit/s~2.048Mbit/s HDLC
channels and a maximum communication bandwidth of 112Mbit/s. The signaling HWs
and HDLC channels of CCM can be allocated dynamically.
The configuration of CCM frame is shown in Figure 3-4.
3-3
Technical Manual
G
P
W
S
13
14
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
Figure 3-4 CCM frame configuration

Each GBAC board, with its adjacent group of GFSN boards, constitute a CCM plane.
The two CCM planes work in load-sharing mode.
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.
GBAC board (Bus Administration Configuration Board): Performs bus arbitration,
configuration of signaling HWs and HDLC channels, and monitors board status on
CCM planes. GBAC boards also provide frame switching and 8 2M signaling HWs and
64 HDLC channels.
GFSN (Frame Switching Network Board): Controled by GBAC board, GFSN boards
perform the configuration of HDLC frame switching for the signaling HWs. One GFSN
board provides 16 2M signaling HWs and 128 HDLC channels.
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.
The functional blocks of CCM frame are shown in Figure 3-5.
3-4
Technical Manual
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
Figure 3-5 Functional Blocks of CCM frame

GBAC boards are responsible for the allocation and management (according to OMC
configuration) over the GFSN boards on a plane, and the signaling HWs and HDLC
channels of the frame switching part of the GBAC boards via backplane buses.
The frame switching part of GFSN and GBAC boards performs HDLC frame switching
via backplane buses. GBAC is also responsible for bus arbitration and dispatching.
3.2.3 Central Processing Module (CPM) Frame

The Central Processing Module in the CPM frame is responsible for the maintenance
and management of the boards in AM, and provides interfaces for OMC operation &
maintenance commands.
The Central Database (CDB) of CPM implements the management over trunk
resources and shared resources.
CPM frame configuration is shown in Figure 3-6.
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
Figure 3-6 CPM frame configuration

3-5
Technical Manual
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;
Other boards in the frame via the bus;
Boards such as GPWS and GAMD without HDLC links through serial ports via
GALM board;
CKM module via the control serial port.
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.
The functional blocks of CPM frame are shown in Figure 3-7.
3-6
Technical Manual
Chapter 3 Frame
Emergency serial port
CPM
-48V
Serial port
Serial port driving
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
Figure 3-7 Functional blocks of CPM frame

The GALM board is responsible for the collection of information on power supply and
fan alarms, and the communication between GAMD, GPWS and AMP.
AMP is in charge of AM maintenance and equipment management, receiving
maintenance commands from BAM, processing most AM-related commands, and
forwarding other commands.
CDP is responsible for the management of trunk resources and various shared global
resources.
The communication between AMP and CDP is achieved via backplane buses. BCP
manages and controls these buses and transfers message packets for AMP-CDP
communication.
3.2.4 Central Switching Network (CNET) Frame

The CNET module in CNET frame is in charge of the service switching of the system.
CNET capacity can be expanded in step of 16K%16K. The maximum capacity of CNET
is 128k %128k.
The main features of CNET are as follows:
3-7
Technical Manual
Chapter 3 Frame
I. TTT three-level fully utilized switching network

The structure of M900/M1800 MSC/SSP/IP switching network is shown in Figure 3-8.
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
QT: Quick Transducer
Figure 3-8 Central switching network

GSNU (Skirt Network Unit) boards constitute the Skirt Switching Network, performing
switching of Level 1 and Level 3. GCNU (Central Network Unit) boards constitute the
Central Switching Network, performing Level 2 switching.
Each GSNU consists of 4 receiving units, each of which is connected to a GQSI board
via LIM with a HOFL (High-speed Optical Fibre Link) with the rate of 393Mbit/s.
Uplink HOFL is divided into 16 16Mbit/s HWs (each sub-divided into 256 timeslots) by
Quick Transducer (QT) for Level 1 switching in the 4k single-T network board. After the
switching, the 16Mbit/s HWs are cross-connected with the 16 8k switching network
units of the 8 GCNU boards. Each 8k switching network unit performs Level 2 switching
for 32 16Mbit/s HWs.
Then the downlink 16Mbit/s HWs are cross-connected with the sending switching-units
of GSNUs. After Level 3 switching, they are multiplexed by QT into downlink HOFL
before being sent to GQSI boards.
3-8
Technical Manual
Chapter 3 Frame
II. Large capacity and smooth expansion

CNET in full configuration provides a switching capacity of 128k%128k. The capacity of
CNET is scalable within 16k%16k and 128k%128k by adding or removing GSNUs.
However, 8 pairs of GCNU boards should be configured regardless of CNET frame
capacity. The correspondence between the number of GSNU boards and the switching
capacity of CNET frame is shown in Table 3-1.
Table 3-1 Correspondence between the number of GSNU boards and the capacity of CNET frame
Number of GSNUs (pair)
CNET frame capacity (kts)
16
32
48
64
80
96
112
128
III. Hot backup of boards for switching network reliability.

The boards NCC, GBDR, GCNU and GSNU configured in CNET frame work in
active/standby mode. GPWS boards work in N+1 backup mode.
The configuration of CNET frame is shown in Figure 3-9.
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
Figure 3-9 CNET frame configuration

GPWS (Secondary Power Supply Board) : Provides +5V power supply for the boards.
The maximum power consumption of a GPWS is 300W.
3-9
Technical Manual
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;
6 GSNU 12, GPWS=5;
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.
The functional blocks of CNET frame are shown in Figure 3-10.
3-10
Technical Manual
Chapter 3 Frame
2M, 8k
Right clock -48V

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
Right-half frame bus
G
C
N
U
7
G
S
N
U
7
393Mbit/s X4
LIM
Figure 3-10 Functional Blocks of CNET frame

The driving of data buses, address buses and control buses managed by the NCC
boards are implemented by the GBDR boards. These buses are divided into two
groups. Through these buses, the NCC boards manage and control the GSNU and
GCNU boards in the left and right half of the CNET frame respectively to achieve
timeslot switching.
3.2.5 Line Interface Module (LIM) Frame

Line interface module in the LIM frame provides line interfaces for communication
between the MSC and other network equipment, achieving interconnection of
communication equipment.
LIM is also in charge of the interconnection between SRM and other modules in the
MSC, the provision of links for sigaling processing, and the provision of echo
cancellation.
The main characteristics of LIM frame are as follows:
3-11
Technical Manual
Chapter 3 Frame
I. Abundant transmission line interfaces

When configured with GE16 (16-port E1 Interface Boards), the LIM frame provides E1
interfaces. Each GE16 board provides 16 E1 interfaces. In total, a LIM frame fully
configured with 16 GE16 boards provides 256 E1 interfaces.
When configured with GETS (16-port E1/T1 Interface Boards), the LIM frame provides
E1/T1 interfaces. Each GETS board provides up to 16 E1/T1 interfaces. In total, a LIM
frame fully configured with 16 GETS boards provides 256 E1/T1 interfaces.
When configured with GSTU (SDH Interface Unit), the LIM frame provides STM-1
optical/electrical interface. Each GSTU provides one STM-1 optical/electrical interface.
One channel of STM-1 signal equals to 63 E1 signals. In total, a LIM frame fully
configured with 4 GSTUs provides 4 STM-1 optical/electrical interfaces.
II. Echo Cancellation

The LIM frame supports two types of echo cancellation equipment. One is the built-in
Echo Canceller equipment - GECS (16-port Echo Canceller Trunk Board) and the other
is the standalone Echo Canceller equipment - GECP (8-port ECHO canceller Board).
The GECS provides 16 E1 interfaces and implements echo cancellation for the 16 E1s
led in. The GECP provides echo cancellation for 8 E1s and can perform echo
cancellation on any lines of MSC through the switching network. GECS can act as
GECP by loading with GECP software.
III. Unified physical interface for various call resources

In resource cabinet, two LIM frames are specially configured to lead in various call
resources. Multi-Highway Interface board (GMHI) and Circuit Data-service Interface
board (GCDI) are configured in the LIM frame. The GMHI interconnects the
GSRC/GSPT in the SRM frame with other modules, and provides signaling link
resources for GCPC to process signaling.
When GMHI connected only to GSRCs/GSPTs, each pair of GMHIs can be connected
to 4 GSRCs/GSPTs. When GMHI connected only to GCPC, each pair of GMHIs can be
connected to 16 GCPCs. When GMHI connected to both GSRCs/GSPTs and GCPCs,
each pair of GMHIs can be connected to 3 GSRCs/GSPTs and 8 GCPCs.
GCDI is in charge of interconnecting the IWF frame with other modules in the resource
cabinet. It also manages and controls the IWF frame. A pair of GCDIs can connect with
two IWF frames.
To reduce inter-cabinet wiring, LIM frames and the network interworking frame & SRM
frame that provide call resources can be placed in the same cabinet.
3-12
Technical Manual
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
Figure 3-11 LIM frame fully configured with GE16 boards
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
Figure 3-12 LIM frame fully configured with GSTU boards
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
Figure 3-13 LIM frame fully configured with GETS boards
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
G
G
PP
W
W
SS
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
Figure 3-14 LIM frame fully configured with GECP boards
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
Figure 3-15 LIM frame fully configured with GMHI boards
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
G
G
PP
W
W
SS
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
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
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
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
393M Optical fiber
I
16MHW 4
393M Optical fiber
SLOT3
2MHW 2
8K , 2M Clock
16M 8k
16M,
Clock signal
SLOT2
187.5k
Asynchronous
serial port
Figure 3-18 Functional blocks of LIM frame

The service interface boards extract and seperate the service data and control data in
the E1, STM-1 and exernal HW signals. Boards in two ajacent slots (slot 2 and 3, slot 4
and 5, ...slot 22 and 23) work as a pair, which communicate with the GQSI board by the
following means:
z
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);
187.5kbit/s asynchronous serial port to report board information to the GQSI

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
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.2.6 Service Processing Module (SPM) Frame

The Service Processing Module in the SPM frame is in charge of processing various
system services, and SS7 signaling, DSS1 signaling and R2 signaling. In addition, one
distributed database is embedded in the SPM cabinet. When M900/M1800
MSC/SSP/IP serves as VMSC, the database will function as a VLR, storing VLR
subscriber data. SPM also supports 2 Mbit/s high-speed signaling links, and directly
provides the E1 interface for the high-speed signaling links.
The configuration of SPM frame in full configuration is shown in Figure 3-19, Figure
3-20 and Figure 3-21.
3-18
Technical Manual
G
S
P
C
0
G
G
P
P
W
W
S
S
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
Figure 3-20 SPM frame in full configuration (with 3 pairs of GSPCs)
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
Figure 3-21 SPM frame in full configuration (with 4 pairs of GSPCs)

When embedded with database, SPM cabinet should be configured with GVDP board.
The configuration is similar to that of GSPC, as shown in Figure 3-22.
3-19
Technical Manual
0
25
G
S
P
C
0
G
S
P
C
0
G
G
P
P
W
W
S
S
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)
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
Chapter 3 Frame
GVDP (VLR Data Processor): When M900/M1800 MSC/SSP/IP serves as VMSC, it is

configured in SPM to function as a VLR, storing VLR subscriber's data. GVDP boards
work in active/standby mode. Each pair of GVDPs can store 250,000 VLR subscribers
data. When GVDPs are used to store VLR subscribers data, one more pair of GVDPs
should be configured for n+1 standby.
BCC (Bus Communication Control Board): Controls the backplane buses of SPM frame,
and transfers message packets between GSPC, and GCPC boards to realize
inter-board bus communication. Packet transfer capability of BCC is 5000
packets/second.
In addition, BCC is responsible for the communication between GCPC, BCC and CCM.
HDLC communication capability of BCC is 5000 frames/second. BCC boards work in
active/standby mode.
Note:
BCC board is defined logically according to the actual function of the board. It is physically GCPC.
The functional blocks of SPM frame are shown in Figure 3-24.
SPM
-48 V
Serial port drive

Serial port
G
P
w
s
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
Figure 3-24 The functional blocks of SPM frame
3-21
2M Signaling HW2
2M Service HW
Technical Manual
Chapter 3 Frame
The GSPC board processes various system services.

The GCPC board is responsible for the link processing of SS7 and DSS1 signalings.
The GVDP stores and manages VLR subscribers data. GSPC, GCPC and GVDP
communicate with each other via the backplane buses. The BCC board manages and
controls the backplane buses, and transfers message packets between GSPC and
GCPC, and between GVDP and GCPC. It is also responsible for the management of
GCPC and the communication with CCM. The GSPC, BCC and GVDP communicate
with CCM via the 2M signaling HWs. The GCPC connects with the GMHI in LIM frame
via the 2M traffic HWs.
The rate of SS7 signaling link processed by GCPC is 64kbit/s. When the SPM frame is
required to support 2Mbit/s high signaling link, GHN7 should be configured in stead of
the GCPC. The GHN7 provides E1 interface of 2Mbit/s high-speed signaling and
performs 2Mbit/s signaling link layer processing. The signaling user part is sent to the
GSPC, the upper level board of GHN7, via backplane bus for processing. The GHN7
also supports n x 64kbit/s (1<n<32) high-speed signaling link.
3.2.7 Shared Resource Module (SRM) Frame

The shared resource module in the SRM frame provides various call resources needed
in serivce processing, such as signal tones, dual tone receiver, dual tone transceiver,
MFC transceiver and conference call resource, etc.
The configuration of SRM frame is shown in Figure 3-25.
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
Figure 3-25 SRM frame configuration
Note:
Slots 4~24 can be configured with either GSPT or GSRC boards.
3-22
25
Technical Manual
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.2.8 InterWorking Function (IWF) Frame

Corresponding to the IWF module of the system, the IWF frame is in charge of the data
and service communication between PLMN and other networks (such as PSTN and
ISDN).
Figure 3-26 shows the IWF frame in full configuration.
3-23
Technical Manual
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
Figure 3-26 Configuration of IWF frame

GPWS (Secondary Power Supply Board): It provides +5V power supply for the boards.
GPWS boards work in load-sharing mode. Maximum power consumption of a GPWS is
300W.
IWC (IWF controller Board): It accomplishes the interface adaptation between GCDI
and the 8 IWF boards under its control. IWCs work in active/standby mode. One pair of
IWCs and the 8 IWF boards under their control form an IWF unit. Each IWF unit
provides 14 IWF channels. Each IWF frame is configured with two IWF units.
IWF (InterWorking Function board): It accomplishes Rate Adaptation (RA), Radio Link
Protocol (RLP/L2R) processing, Facsimile Adaptation (FA) for data traffic channel. It
interworks with other networks by providing 3.1kHz audio PCM signal. IWF unit
supports services in transparent/non-transparent (T/NT) connection mode.
The functional blocks of IWF frame are shown in Figure 3-27.
GCDI
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
Figure 3-27 Functional blocks of IWF frame
3-24
2MHW2
2MHW2
Serial Serial
port
port
I
W
F
8
I
W
F
15
Technical Manual
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
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.
4.1 Functions and Features

Boards in the M900/M1800 MSC/SSP/IP system have the following common features:
z
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.
Hot plug/unplug function is provided.
Boards have built-in Watchdog that can automatically reset boards in case of
severe problems.
Online software loading of board is available.
The serial port printing function and reset switch is provided.
4.2 Board Structure

M900/M1800 MSC/SSP/IP system boards are of the same size: 280mm (length) %
233.35mm (width) % 2.0mm (PCB thickness). The structure of the board is shown in
Figure 4-1.
4-1
Technical Manual
(1) Indicator
(4) Handle
Chapter 4 Board
(2) Panel
(5) Board name
(3) Flexible locking latch needle

(6) Connector
Figure 4-1 Sketch of the board

Most of the functional boards contains only one PCB board, and occupies only one slot.
Whereas some PCB boards have one or two back plates attached at the back, and
generally these boards occupy two slots, such as GQSI, GPWS and GSPC, etc.
The panels of most boards can be opened to display the components on the front, such
as the reset button, DIP switches and serial port. The maintenance engineer can
implement operations on the board without pulling out the board. The front of the board
with panel opened is shown in Figure 4-2.
4-2
Technical Manual
Chapter 4 Board
RUN
FAIL
(1)
(2)
1 2 3 4
ON
(3)
(1) Serial port
(2) DIP switches
Figure 4-2 Board panel (GSRC)
4-3
(3) Reset button
Technical Manual
Chapter 5 Power Supply System

This chapter details the power supply system of M900/M1800 MSC/SSP/IP.
5.1 Structure
M900/M1800 MSC/SSP/IP adopts a multi-level distributed feed system, as shown in
GND
PGND
DC power distribution cabinet
DC power supply
-48V
DC power distribution cabinet
DC power system
AC power supply
Figure 5-1.
-48V
GND
PGND
-48V GND PGND

Power distribution
box of cabinet 1
Frame 1
Frame 2
Frame 3
-48V
GND
PGND
Power distribution
box of cabinet n1
Frame 4
Busbar
Cabinet feed system
Figure 5-1 M900/M1800 MSC/SSP/IP power supply system

M900/M1800 MSC/SSP/IP power supply system includes AC power supply system,
DC power supply system, DC power distribution cabinet and cabinet feed system. The
cabinet feed system includes cabinet distribution boxes and busbars.
The DC power supply converts AC power supply into -48V DC via a rectifier and
allocates it to the DC power distribution cabinet. Besides, it provides a storage battery
circuit as spare DC supply. The DC power distribution cabinet is responsible for
allocating power to various cabinets and connecting grounding cables. The cabinet
feed system is responsible for power allocation of various frames and connecting the
grounding cables within a cabinet.
5.2 AC Power Supply System

The mains supply is recommended as a main AC power supply. Reliable and stable AC
mains supply and inlet are of vital importance to guaranteed communication and
convenient maintenance. A diesel engine generator should be equipped as the spare
power supply. To ensure safe power supply, two mains supplies can be used for
high-capacity toll exchanges and local exchanges.
5-1
Technical Manual
AC voltage and fluctuation requirements:

z
Three-phase 380V ! 10%, frequency: 50Hz ! 5%, line voltage wavelength

distortion rate less than 5%.
Single-phase 220V ! 10%, frequency: 50Hz ! 5%, line voltage wavelength

distortion rate less than 5%.
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%.
5.3 DC Power Supply System

A DC power supply system includes the storage battery, rectifier, DC power distribution,
control panel, etc.
I. Requirements for storage battery

The storage battery plays an important part in a DC power supply. It can
z
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.
Work as a large capacitor to absorb any surging voltage from a rectifier.
Filter noise and prevent mains frequency from interfering the system.
The storage battery is charged/discharged in constant low-voltage charging mode,

whose requirements are listed in Table 5-1.
Table 5-1 DC charge/discharge status and voltage requirements
Power
supply
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
II. Requirements for rectifier (primary power supply)

The rectifier is responsible for rectifying AC power supply and should satisfy the
following requirements:
z
Multiple rectifiers can work in parallel, with flow equalization devices between
them.
There should be some current limiting device for a rectifier.
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.
A DC voltmeter and ammeter should be equipped for the rectifier.
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
full load within 0~40 C.

z
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.
Table 5-2 Voltage indices of DC power supply

Item
Index
Nominal value (V)
-48V
Voltage fluctuation range (V)
-40V~-57V
Noise voltage
0~300Hz
400mV peak value
300~3400Hz
2mV weighted noise of noise meter
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
III. Requirements for DC power distribution and control panel

Each control panel can be connected with at least two battery groups. Thus, if any fault
occurs to one group and this group cannot supply power normally, the other group can
function normally.
5-3
Technical Manual
Each control panel can be connected with at least 5 rectifiers.

The power equipment should be fully automatic and can work normally when
unattended.
In addition, there are also strict requirements for random transient noise, including
abnormal operating noises caused by external magnetic interference, local equipment
and grounding cables. For transient noise, the shorter a transient pulse lasts, the higher
its allowable value is. For the allowable value, please refer to Figure 5-2.
V
1000 V
.
100 V
10V
1V
0.1 V
A
0.1
s 1
10
100
s 1000
Figure 5-2 Requirements for allowable value of transient noise

When a rectifier charges the storage batteries in floating charge mode, the number of
rectifiers to be put into operation depends on load volume. When any fault occurs to a
rectifier, this rectifier will be disconnected and the spare rectifier will be put into
operation automatically.
If the mains supply fails, the storage batteries discharge. When the mains supply
resumes, the storage batteries will be charged automatically at 10 ampere hour. When
the charging voltage reaches 56.4V, constant voltage charging will function
automatically.
When a storage battery is fully charged, the charging state will be changed into floating
charge automatically.
IV. Other requirements

When the power supply equipment is faulty and cannot work normally, audible and
visible alarm indications will be given. Power supply alarm information is sent to the
Operation and Maintenance Center (OMC).
When a tributary of the power supply system is short-circuited, the power distribution
system will not be affected by sharp voltage decrease. The peak voltage in the course
of arch starting should not cause any exchange fault.
5-4
Technical Manual
5.4 DC Power Distribution Cabinet

DC power distribution cabinet is used for distributing -48V DC power supply and
connecting grounding cables. The DC power distribution cabinet is the same as the
MSC cabinet.
The DC power distribution cabinet contains no power distribution box but a monitor
frame and some power distribution frames (the number of power distribution frames
depends on the number of total cabinets). A DC power distribution cabinet can be
equipped with up to 4 power distribution frames, each of which supports up to 8 DC
supplies.
There is an over-current protection switch in each power supply. Frames 1 and 3,
frames 2 and 4 constitute respective two power supply systems. That is, a DC
distribution cabinet can provide up to 2 % 16 outputs and actual configurations depend
on practical conditions.
5.5 Cabinet Feed System

The cabinet feed system comprises of the power distribution box at the top and the
busbars at both sides of the cabinet. The power distribution box has a through-flow
capability of 50A and the busbars can carry 30A current. To improve the
anti-interference capability of power feeder and reduce the characteristic impedance,
the busbar adopts parallel copper strips isolated with epikote as the conductor. All
connectors are plug-connected, which makes installation and maintenance convenient.
5-5
Technical Manual
Chapter 6 Clock Synchronization System

This chapter briefly introduces the features, structure and principles of the clock
synchronization system of M900/M1800 MSC/SSP/IP, and details its installation and
configurations.
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.
Diversified benchmark reference source input signals are available, including

8kHz, 2MHz, 2Mbit/s, etc.
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.
The structure of M900/M1800 MSC/SSP/IP clock synchronization equipment is shown

in Figure 6-1.
E1
STM-1
GE16/
GECS
GETS
GSTU
External clock source
8k Clock
8k Clock
CC
KK
MM
8k0, 2M0
8k31, 2M31
Figure 6-1 Structure of clock synchronization equipment

6-1
Other modules
Technical Manual
M900/M1800 MSC/SSP/IP clock synchronization system is connected to the 8kHz

clock provided by GE16/GETS board or GSTU board. In addition, it provides 2.048MHz
and 2.048Mbit/s interfaces to external clock source (for example, BITS) equipment.
The "purified" clock is driven to form 32 channels of differential timing signals, which
are sent to various system modules via dedicated clock cable.
6.2 Architecture of Clock Synchronization System

M900/M1800 MSC/SSP/IP clock synchronization system is implemented by
synchronization clock frame. The synchronizatin clock frame keeps synchronized with
the upper-level clock source and provides the whole system with the stratum 2 or
stratum 3 clock. If there is no external input reference source, the clock frame can
provide stratum 2 or stratum 3 clock in free-run mode. The selection of stratum 2 or
stratum 3 clock depends on the location of home exchange and the accuracy of the
clock source provided by the upper-level exchange. Usually, the clock can only provide
reference source for clocks of lower stratum or same stratum.
If the upper-level exchange uses a stratum 2 clock, the home exchange can be
configured with stratum 2 clock. If the upper-level exchange uses stratum 3 clock, the
home exchange can only be configured with stratum 3 clock. If the home exchange
synchronizes itself with the stratum 3 clock of an upper-level exchange with stratum 2
clock frame, out-of-sync may occur because the stratum 3 clock is far less accurate
than the stratum 2 clock. When the clock of the upper-level exchange goes beyond the
specified range, the clock board of the home exchange will lose the reference source
and enter holdover status.
6.2.1 Configuration of Clock Module (CKM) Frame

The CKM frame is equipped with PWC, GCKS and GCKD boards.
PWC provides the boards with +5V/10A power supply. Two PWC boards work in
load-sharing mode.
GCKS board supports both stratum 2 and stratum 3 clocks, and outputs the clock
signals synchronized with the upper-stratum clock or BITS clock.
GCKD board is responsible for driving the clock signals output by GCKS board, and
outputs 32 channels of 8kHz and 32 channels of 2MHz signals.
Note:
Currently, only the 32 channels of 2MHz signal is used as the synchronous signal among modules.
6-2
Technical Manual
6.2.2 Control Structure of Clock System

The control structure of a clock system is shown in Figure 6-2. The WS (Workstation)
communicates with AMP through BAM and Ethernet. AMP communicates directly with
GCKS via serial port.
WS
LAN
BAM
LAN
AMP
Serial port
GCKS
WS: WorkStation
AMP: AM Processing Board
LAN: Ethernet
GCKS: Clock Board
Figure 6-2 Control structure of the clock system
6.2.3 Allocation of Clock System Signals

The allocation of clock signals of the clock system is shown in Figure 6-3.
GCKS provides 6 reference source input interfaces for two channels of DT8K
differential signals (8K0 and 8K1) from the interface frame, and for 2Mbit/s signals
(2MB0 and 2MB1) and 2MHz signals (2M0 and 2M1) from other devices (e.g. BITS).
GCKS checks the access and quality of various clock reference sources, and
automatically selects a reference source as the clock reference according to the
configured data or setting of DIP switches on the board. Through software
phase-locking, GCKS board manages to fast pull-in and lock the reference source, so
that the clock signals output by the GCKS board have the same frequency and phase
features as the reference source.
GCKD board drives the clock signals output by GCKS board and outputs 32 channels
of 8kHz signals and 32 channels of 2MHz signals for other modules.
6-3
Technical Manual
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
Figure 6-3 Allocation of clock signals
6.3 Hardware Configuration of Clock Synchronization

System
6.3.1 Clock Reference Source
The clock reference sources of M900/M1800 MSC/SSP/IP clock synchronzation
system include:
z
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).
6.3.2 Configuration for Extracting Clock Source from Trunk

M900/M1800 MSC/SSP/IP can use two DT8K clock cables to lead in active/standby
upper-stratum reference clock from the trunk interface that provides clock reference
source. One end of these clock cables are 4PIN connectors connected respectively to
JC1 and JC2 of the clock frame backplane. The connection of the other end of the
cables depends on trunk interfaces:
If the trunk interface of the upper-level exchange is provided by GE16/GETS board,
DT8K clock cable with one end being RJ11 plug should be selected. The RJ11 plug
6-4
Technical Manual
should be connected to JP5 of DRC board corresponding to GE16/GETS (JP5 is a

RJ11 socket between cabling troughs). Then, configure (with ADD BOSRC command)
the E1 port of GE16/GETS board from which clock is extracted.
If the trunk interface of the upper-level exchange is provided by GSTU board, DT8K
clock cable with one end being 8%3PIN plug should be selected. The 8%3PIN plug
should be connected to 1-8 rows of pins of JP2 on the TMC board corresponding to
GSTU. Then, configure (with ADD BOSRC command) the E1 port of GSTU board from
which clock is extracted.
6.3.3 Configuration for Leading in Clock Signals from BITS

I. Lead-in of 2MHz clock signals
The clock synchronization cables are 75-ohm coaxial cables, connected to J3 and J4
on the clock frame backplane. In this case, the S3 DIP switch on the GCKS board
should be set as follows: S3-1=OFF, S3-2=ON, S3-3=OFF, S3-4=ON.
II. Lead-in of 2Mbit/s clock signals

The clock synchronization cables are 75-ohm coaxial cables, connected respectively to
J1 and J2 on the clock frame backplane. In this case, the DIP switches S1 and S2 on
GCKS board should be set as follows: S1-1=ON, S1-2=ON, S1-3=OFF, S1-4=OFF,
S2-1=ON, S2-2=ON, S2-3=OFF, S2-4=OFF.
6.4 Parameter Configuration of Clock Synchronization

System
The configuration of phase-locked mode of the clock system is as follows:
When all the SDHs are synchronized, the PDH or SDH clock reference source should
be phase-locked (PDH phase-lock). When some of the SDHs are not yet synchronized,
the 8kHz clock reference source extracted by the trunk board from the service code
stream should be phase-locked, i.e., the SDH clock reference source is phase-locked
(SDH phase-lock).
The clock operational mode should be configured as "Automatic".
6-5
HUAWEI
Technical Manual
Technical Manual
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
Table of Contents
3.3.3 Traffic Statistics Console......................................................................................... 3-7

3.4 Communication Gateway................................................................................................... 3-7
3.4.1 Communication Gateway at BAM Side (Convert)................................................... 3-7
3.4.2 Remote Maintenance Proxy (iGate)........................................................................ 3-7
3.5 M2000 Software................................................................................................................. 3-8
3.6 iGWB Software .................................................................................................................. 3-8
3.6.1 Functions................................................................................................................. 3-8
3.6.2 Features .................................................................................................................. 3-9
3.6.3 Dual-system of iGWB.............................................................................................. 3-9
3.6.4 Structure................................................................................................................ 3-10
ii
Technical Manual
Chapter 1 Overview
Chapter 1 Overview
This chapter introduces the software structure of M900/M1800 MSC/SSP/IP and
functions of each part.
1.1 Architecture and Functions

1.1.1 Overall Architecture
M900/M1800 MSC/SSP/IP software includes two parts: Host software and OMC
software, as shown in Figure 1-1.
Foreground (MSC)
Background (OMC)
Local
Maintenance
system
iManager M2000
Mobile network management
system
Host software
iGWB software
Figure 1-1 Overall architecture of M900/M1800 MSC/SSP/IP software

Host software refers to the software running on the five key boards (NCC board, GSPC
board, GVDP board, CDP board and AMP board). They control the hardware resources,
perform signaling processing and call handling, and fulfill WIN functions of the
M900/M1800 MSC/SSP/IP.
OMC software includes local O&M system, OMC centralized O&M system, and iGWB
(iGateway Bill) software. It fulfills such functions as MSC operation and maintenance,
data configuration, performance measurement, alarm management, charging
management, etc. iGWB software runs on iGWB. The local O&M system includes BAM
software, WS operation and maintenance terminal software, and the communication
gateway software on BAM and/or WS. The iManager M2000 mobile network
management system (M2000 for short) is optional. It includes M2000 server software
running on M2000 Server, M2000 operation & maintenance terminal software running
on WS and ADAPTER software.
1-1
Technical Manual
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
AMP board software module
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
CDP board software module
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
NCC board software module
This module controls the whole CNET frame, and performs time slot allocation, online
operation, and the communication with other modules.
z
GSPC board software module
This module is responsible for call proceeding, signaling processing, location

management, security management, and the fulfillment of various GSM services
(including teleservices, supplementary services, bearer services, intelligent services
and value-added services).
Two GSPC boards form a pair, working in active/standby mode. A maximum of 20 pairs
of GSPC boards can be configured, depending on the traffic requirement.
z
GVDP board software module
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
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.
II. Local O&M system software

The local O&M system software enables MSC operation and maintenance, data
configuration, traffic measurement, alarm management and charging management.
The local O&M system software includes the following parts:
z
BAM software
BAM software integrates Communication Server and Database Server software. It is

the core of the local O&M system.
All operation and maintenance tasks are executed in Client/Server mode. As a server,
BAM software supports simultaneous data setting and other operations from multiple
remote/local O&M terminals. BAM forwards the O&M commands from terminals to
MSC, and directs MSC responses to corresponding terminals after processing. At the
same time, it stores and transfers Host software, office data, alarm information, and
performance measurement data. Through BAM, users can complete the interactions
with the MSC, and important data can be saved to the hard disk or transferred to the
MO disc or Network Server.
Data storage in BAM is executed by an efficient Database Management System
(DBMS). By controlling the storage procedure, transaction and various authorities, data
consistency, uniqueness and security can be ensured.
z
O&M terminal 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
Communication gateway software
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.
III. iGWB software

The iGWB software is the core of the charging system. It saves and backups the bills
generated by various service processing modules to physical disks. These bills provide
1-3
Technical Manual
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.
IV. iManager M2000 mobile network management system

For details about the software of M2000, refer to relevant manual of M2000 Mobile
Network Management System.
1.2 Features
1.2.1 Features of Host Software
Features of M900/M1800 MSC/SSP/IP Host software include:
z
Host software is designed according to the requirements of software engineering

in a top-down layered modular programming mode. Strict documentation control
and detailed test cases are implemented to ensure the reliability. The design
philosophy of software integration has been abided. The codes are generated with
SDL language and CASE tool to ensure the controllability of target codes.
Therefore, the software system features high reliability, easy maintenance and
excellent extendibility. The Host software mainly adopts C language as its
programming language, thus making the source code easy to read and the system
easy to maintain.
Built-in real-time multi-task PSOS operating system ensures reliable and efficient
task dispatching, message management, timer management and memory
management.
The service processing software adopts distributed-processing technique. The

demands for processing capability and data storage due to the increase of
subscribers can be met by adding GSPCs.
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
z
Chapter 1 Overview
Unified management over all shared resources of the M900/M1800 MSC/SSP/IP

ensures a maximum utilization of resources.
1.2.2 Features of OMC Software

The OMC software of M900/M1800 MSC/SSP/IP has the following features:
z
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.
Access to the IGWB through Web browser is possible, so there is no need to

install special software on the WS to view or backup bills.
1-5
Technical Manual
Chapter 2 Host Software

This chapter details the structure and functions of M900/M1800 MSC/SSP/IP Host
software. With this chapter, readers can have basic knowledge on how the modules
coordinate to realize the services and functions specified in GSM Specifications.
2.1 General Structure

M900/M1800 MSC/SSP/IP Host software is mainly divided into the system support
layer and function layer, running respectively on the five key boards in the Host (NCC
board, GSPC board, GVDP board, CDP board and AMP board). The software of each
board is composed of different functional modules, as shown in Figure 2-1.
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
Figure 2-1 Structure of Host software

System support layer mainly refers to the operating systems running on respective
boards, which perform functions such as system task dispatching, memory
management and timer management.
Function layer is the combination of functional modules running on respective boards,
performing communication, services (including data management, alarm management,
performance measurement and operation maintenance) and service layer processing.
NCC board is mainly equipped with switching network operation module assigning and
controlling the timeslots in the whole central switching network frame. The call control
module on GSPC board is related to network operations.
GSPC board is composed of call control module and signaling processing module.
2-1
Technical Manual
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 Operating System

The operating system refers to the program that manages other Programs. Programs
under management are called Application Programs.
The operating system executes functions such as task dispatching, management of
memory, file, peripheral, patch and user interface.
Classified according to task dispatching strategies, the operating system is of three
types: batch processing operating system, timing operating system and real-time
operating system. These three types of operating systems are applied in different
conditions. In the mobile switching area, real-time response to events is required and
the real-time operating system must be adopted. "Real-time" means that responses are
made to external events within a certain period at a very quick speed. In addition, the
real-time operating system also features priority dispatch, fault detection, seizure, etc.
Priority dispatch means that in a multi-task real-time system, the processor executes
tasks according to the priority levels so that higher priority tasks shall be executed first.
"Seizure" means that when an event occurs, the on-going task will be interrupted
forcibly. After the running sequence is protected, the processor will turn to process the
task corresponding to the event at hand.
Fault detection means that the operating system has the ability to monitor the running
conditions of various tasks. In abnormal conditions, the system can keep its normal
2-2
Technical Manual
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
System initialization: To initialize and reconfigure the software and hardware of

the whole system.
Program loading: To load program & data from OMC terminal or BAM onto GMPU
and boot the system.
Interrupt management: Completes the setting of interrupt vector table and

manage call-interrupt processing program.
Task dispatch: To dispatch tasks by priority and allocate related resources (the
processor and memory) in a multi-task real-time system.
Packet management: As the communication carrier between tasks, packets are

sent by the operating system or a task to activate or drive another task for
consequential processing.
Memory management: To allocate and release memory resources of the

processor.
Timer management: To initialize, activate or deactivate scheduled tasks.
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.
Patch management: it refers to the self-upgrading function of the software

provided by the operating system. When the whole software system requires
functional improvements, the online upgrading can be implemented through patch
management so as to minimize the risk of software upgrading.
2.3 Communication Mode

According to the physical bearing media, communication modes between M900/M1800
MSC/SSP/IP devices can be classified into four types: HDLC link communication, Bus
communication, Serial port communication and TCP/IP communication.
2-3
Technical Manual
2.3.1 HDLC Link Communication

HDLC link communication is suitable for the communications between boards with
large traffic. With CCM as the center, these boards are connected with CCM directly via
HDLC. CCM addresses the message from HDLC link and forwards it to its destination.
The address flags are the module numbers assigned to the boards by the system.
To ensure the communication reliability, the system has two communication planes
working internally in a load-sharing mode, enabling the system to process services as
usual even if one communication plane fails. HDLC links exist between CCM and the
following boards: BCC, GSPC, GVDP, CDP, AMP, GQSI and NCC.
2.3.2 Bus Communication

Bus communication is normally adopted between boards in the same frame.
In the service processing frame, main control frame and central switching network
frame, each board (except the power supply board), has its own mailbox connected
with the bus. The bus communication control board is connected directly to the bus and
realizes the message communication between the boards in the frame by reading out
and writing in the mailbox on each board. For example, in the central switching network
frame, NCC board accesses GSNU and GCNU boards in the frame via the bus to
achieve the control and management over these two boards.
2.3.3 Serial Port Communication

For boards with small traffic, the serial communication mode is adopted for message
communication with superior boards.
Generally, all the superior boards of these boards have HDLC links, enabling these
boards to communicate via CCM with other boards equipped with HDLC links. The
superior boards act as master nodes and the boards with less traffic acts as the slave
nodes of their superior boards. The equipment management center manages the slave
nodes through their master nodes. In M900/M1800 MSC/SSP/IP system, it is in the
serial communication mode that AMP manages the slave node GCKS via GALM board
and manages the slave nodes GE16 and GSTU boards via GQSI.
2.3.4 TCP/IP Communication

The AMP, GSPC and CDP are connected with the BAM via network cables,
communicating via TCP/IP protocol. Operation and maintenance commands are sent
to AMP by BAM; loading information is sent to AMP, GSPC and CDP by BAM; while
alarm and performance measurement information is sent to BAM by AMP and GSPC.
2-4
Technical Manual
2.4 Data Management

M900/M1800 MSC/SSP/IP employs distributed relational databases to manage system
configuration data, resource state data and subscriber data.
According to the physical entities where databases are located, the Host database can
be classified into:
z
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
In AMP board, this database stores configuration information of system hardware,

including frame, board, module, communication link and clock.
z
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.4.1 Database Structure

Before or during the operation of the system, users can input data from the service
maintenance system on WS. BAM serves to interpret commands, convert the data into
the Host-acceptable format and set the data to the corresponding board in the Host
through the SQL Server storage process. The data to AMP is converted into DB_0.DAT,
the data to CDP into DB_C.DAT, and the data to GSPC into DB_1.DAT, DB_2.DAT, ,
and DB_N.DAT respectively according to the module to which the data belongs. The
relationship between the databases in the foreground and background is shown in
Figure 2-2. To realize the distributed management of subscribers' data on multiple
GVDP boards, the subscriber location parameters, location/cell configuration
information and subscribers' subscription information will be sent directly to CDP, which,
after processing the data, will send it to GVDP.
2-5
Technical Manual
Figure 2-2 Relationship between databases in foreground and background

The database comprises multiple relational tables loaded by BAM to the Host memory
and duplicated in Flash Memory. The DBMS accesses the database through RAM and
no disk file operation is needed. In this way, the query speed is faster. Modifications of
the data can be instantly backed up to the Flash Memory to ensure that the data is not
lost after power-off.
The database occupies a segment of the continuous address space in the Host
memory. Its space distribution is shown in Figure 2-3.
System data
Data dictionary (system table)
Data table
Figure 2-3 Database space distribution
M900/M1800 MSC/SSP/IP database is the aggregation of data relations formed by
multiple two-dimensional tables. These two-dimensional tables are called relational
tables. One dimension (row) is called a tuple and the other dimension (column) is called
a domain. A tuple corresponds to a logical "record", while each domain corresponds to
a specific "attribute" and can be regarded as a data item in a logical record. Thus, the
number of domains is determined by the logical complexity of the relation.
In the Relational Database, data is queried according to key domain. In general, each
key domain comprises one or several domains.
2-6
Technical Manual
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.
II. Table type

In M900/M1800 MSC/SSP/IP database, the following three types of relational tables
are used.
z
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.4.2 Central Database, Controlling Database and SPM Database

I. Central database
The central database is on CDP board. It assists other software on CDP to manage the
resources such as GSRC, GSPT, GECP and trunk resources.
The resource management will be detailed in the following sections.
II. Controlling database

The controlling database, located on AMP board, stores equipment configuration
information and provides initial data and intermediate data variable to application layer
module such as the equipment management module on AMP board.
2-7
Technical Manual
III. SPM database

The Service Processing Module (SPM) database is on GSPC board and interfaces with
signaling processing module, call control module and other databases. It provides the
functions such as number analysis, trunk routing and interface circuit management.
2.4.3 VLR Database

In M900/M1800 MSC/SSP/IP system, the Visitor Location Register (VLR) is a real-time
database built in the same equipment entity with MSC. It consists of multiple groups of
GVDP boards physically. It is responsible for storing and managing the information of
the mobile subscriber currently moving in the MSC/VLR area. The subscriber
information is used to set up calls, provide basic services and supplementary services,
and perform mobility management and subscriber security management.
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.
Supporting IMSI attach/detach.
Performing location registration. When a mobile subscriber appears in a new

location, or location update message is received from the MS, VLR will initiate the
location update to the HLR and retrieve the relevant subscriber information from
the HLR or the previous VLR.
Performing authentication. VLR obtains and stores the authentication triplet

(RAND/SRES/Kc) from AUC or obtains authentication parameters from the
previous VLR during location registration. In addition, the VLR supports the MS
authentication at the request of the MSC.
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.
Restricting regional subscription. When the user location is to be updated, it

decides if the location update is allowed in the area according to the Zone Code
List of the subscriber.
2-8
Technical Manual
z
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.
II. Performance and features

VLR has the following features:
z
It is embedded with distributed boards (GVDP). A pair of GVDPs constitute a VLR

module, which can support maximum 0.25 million subscribers. The system can
support maximum 5 VLR modules and support smooth expansion. Featuring high
reliability design, it can manage maximum a million mobile subscribers. Reference
load: call handling 1.5 times per subscriber per hour; mobility management 8.5
times per subscriber per hour.
Time delay of information retrieve 1000ms. Time delay of registration in

VLR 2000ms.
System parameters such as the number of subscribers can be flexibly configured

through the MML commands according to the subscribers requirements.
MSRN can be allocated flexibly via MML commands according to subscribers

requirements.
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.5 Resource Management

M900/M1800 MSC/SSP/IP adopts the mode that combines distributed and centralized
processing to complete resource management. CDP manages the resources shared
by the whole system.
The system can be configured with multiple groups of CDPs as required, each
responsible for different resource management functions. This provides flexible
scalability to the whole system. When the system is running, the central database on
CDP updates the resource status managed by it according to the equipment status
reported from the equipment management module, and informs the service processing
modules pertaining to resources if necessary.
2-9
Technical Manual
2.5.1 Types of Shared Resources

In M900/M1800 MSC/SSP/IP, the resources shared by the whole system include:
z
Trunk circuits: The global shared trunk circuit resources mainly include
TUP/ISUP/CAS trunk circuits.
Dual Tone Transceiver (DTR): Provided by GSRC boards.
Dual Tone Multi Frequency_Sender (DTMF_S): Provided by GSRC boards.
Multi-Frequency Compelled (MFC) transceivers: Provided by GSRC boards.
Conference call resources: Provided by GSRC boards.
Signal tones: Provided by GSPT boards.
EC Pool: Provided by GECP boards.
InterWorking Function resource: Provided by IWF boards.
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.5.2 Resource Management Task

The resource management tasks of CDP includes:
z
Description and initiation of hardware resources.
Dynamic online setting of hardware resources. Supporting such maintenance

commands as board-level isolation, forced isolation, isolation cancellation and
activation. With these isolation commands, the board will not be removed until
subscriber releases resources, which affects no subscriber in a conversation.
During the isolation, you can use isolation cancellation command to return to
activated status. As for a new board, activation command must be used to inform
CDP board to assign resources normally. The data of resource board can be
dynamically added and deleted.
2-10
Technical Manual
Resources application and release.
Supporting test on the specified channels of GSRC board, GSPT board and
GECP board for the location of problems.
Resources channel maintenance. Supporting the channel maintenance of GSRC

board, GSPT board GECP board and IWF board, including querying, blocking,
unblocking and resetting resource channels according to frame and slot numbers.
Processing of channels in abnormal state. Executing the consistency check on the

overtime occupation of ECPOOL channel and IWF channel to prevent the channel
from being suspended in abnormal cases.
Maintenance of board faulty/normal status. Processing the status commands of

resource board level or resource unit level from AMP, and informing GSPC board
to execute anti-disconnect command to conclude the ongoing service if the
managed resources shift from normal to faulty.
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.
2.6 Equipment Management

In M900/M1800 MSC/SSP/IP system, equipment management is focused on boards,
which has the following functions:
z
Examining board status and informing relevant module of any changes.
Providing data necessary for the normal running of boards.
Indicating abnormal cases occurring to the system.
In M900/M1800 MSC/SSP/IP system, boards are managed in hierarchical mode,

involving mainly the following boards:
z
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
2.7 Switching Network Management

M900/M1800 MSC/SSP/IP switching network comprises user-level switching network
and central switching network. The user-level switching network appears as single
T-network on the interface boards (e.g. GE16 and GSTU boards) connecting other
offices. The central switching network is a three-level network, constructed as a
full-availability network with skirt network + central network + skirt network. The skirt
network is on GSNU board and the central network is on GCNU board.
2.7.1 Software Modules Related with Switching Network Operation

All the commands for networking operations are originated by the service processing
module on GSPC board and processed by the networking operation support layer and
speech channel application control module, before the switching network control
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
module actually performs the networking, as shown in Figure 2-4.
NCC
Figure 2-4 Networking related software modules

The networking operation support layer serves to shield the software and hardware
details of the actual network disconnecting and connecting, and provides a uniform
network operation interface to service layer. The speech channel application control
module is mainly used for the application and release of speech channels between
control modules.
2.7.2 Functions of Switching Network Control Module

Switching network control module not only implements the speech channel networking
between service processing modules and the networking of various signaling links
(including SS7 signaling, DSS1 signaling and CAS) but also supports the management
of such global network resources as signal tones, number receiving and conference
call.
2-12
Technical Manual
I. Speech channel networking function

The service processing module designates two speech channel timeslots needing
connection, i.e. certain speech channel timeslot of E1 or STM-1 led in via the interface
of GE16/GSTU. According to the fixed relationship between the speech channel
timeslot and the switching network timeslot, the switching network control module
determines the netchip timeslots needing connection and performs networking in the
way designated by the service processing module. The schematic diagram of speech
channel networking is shown in Figure 2-5 (boards without switching capability such as
GQSI are neglected in this figure). The networking modes include bi-directional
networking, forward networking and backward networking. Accordingly, switching
network control module supports bi-directional network disconnecting, forward network
disconnecting, backward disconnecting, and timeslot release.
GE16/GSTU/
GETS/GECS
GSNU
GCNU
GSNU
GE16/GSTU/
GETS/GECS
E1/STM-1
E1/STM-1
Figure 2-5 Schematic diagram of speech channel networking
II. Signaling link networking function

The signaling link provided by GCPC board, passing GMHI and GQSI, are mapped to
certain fixed timeslot of the central switching network. After data are configured and
loaded to related signaling links, the switching network control module will set up a
semi-permanent connection in the switching network between the netchip timeslots,
corresponding to the signaling link timeslot and signaling timeslot of trunk (e.g. the
signaling timeslots of E1 or STM-1 led in via GE16/GSTU). Figure 2-6 shows the
networking of the signaling links (the boards without switching capability, such as GQSI
and GMHI, are omitted here).
GE16/GSTU/
GETS/GECS
GSNU
GCNU
GSNU
E1/STM-1
Figure 2-6 Schematic diagram of signaling link networking
2-13
GCPC
Technical Manual
III. Semi-permanent connection of asynchronous signal tone

The switching network control module supports semi-permanent connection for
asynchronous signal tone. Because the central switching network is a three-level
blocking T-network, a semi-permanent connection must be established for signal tone
to ensure the successful tone sending even in high traffic. During initialization, NCC
board will provide asynchronous signal tone connection to the necessary signal tone to
help the asynchronous signal tone occupy the netchip in the rightmost level of GSNU.
During the calling, the networking of signal tone only involves the networking on the
rightmost level, as shown in Figure 2-7.
GSPD
GSNU
GCNU
GSNU
GE16/GSTU/
GETS/GECS
E1/
STM-1
Figure 2-7 Schematic diagram of asynchronous signal tone networking
IV. Management of shared resources

The switching network control module can operate the networking for the resources
shared by the whole system (including the conference call resources in GSRC, number
sending resources, synchronous tone resources in GSPT, etc.) in compliance with
corresponding instructions. Its theory is similar to signaling link networking.
2.8 Call Control

The call control module of M900/M1800 MSC/SSP/IP is an integrated system
compliant with ITU-T and ETSI standards. As the core of service processing, it is an
application sub-system based on the operating system and the database management
system.
The call control module implements the called number analysis and finds the route to
the called party. It also applies for shared resources such as network and trunk, and
generates initial bill information.
M900/M1800 MSC/SSP/IP supports the intelligent services in OVERLAY mode and its
call control module is divided into two parts:
2-14
Technical Manual
z
Ordinary call control sub-module
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
Intelligent call control sub-module
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.9 Signaling Processing

The signaling processing module of M900/M1800 MSC/SSP/IP is responsible for the
transmission and reception of various standard signaling during call proceeding. It
supports the interworking among mobile networks and the interworking with other
communications network (e.g. PSTN and ISDN). The signaling processing module
converts the received signaling and sends it to the call control module. And then the
signaling will be processed by the call control module and sent out by the signaling
module.
The signaling system supported by M900/M1800 MSC/SSP/IP is fully compliant with
relevant standards and specifications, including ITU-T specifications and signaling
standards, and ETSI specifications.
As for the internal connection of GSM, M900/M1800 MSC/SSP/IP has single interface
to other equipment. That is, SS7 signaling is adopted to support the inter-equipment
signaling exchange.
M900/M1800 MSC/SSP/IP usually adopts SS7 signaling as priority when connecting
with other communication networks. In addition, M900/M1800 MSC/SSP/IP supports
Channel Associated Signaling and DSS1 signaling in order to meet some special
requirements when connecting with other networks.
2-15
Technical Manual
Chapter 3 OMC Software

This chapter details the structure and functions of M900/M1800 MSC/SSP/IP OMC
software. With this chapter, readers can have basic knowledge on how the software
realizes system operation and maintenance, performance measurement, bill
management, etc.
3.1 General Structure

M900/M1800 MSC/SSP/IP OMC software comprises local maintenance system,
iManager M2000 mobile network management system and iGWB software. The local
maintenance system and iGWB software are mandatory part of M900/M1800
MSC/SSP/IP, while the M2000 is optional. The overall structure of OMC software is
shown in Figure 3-1.
iManager M2000
Superior NM system
mobile network management

system
Local maintenance system

Host
software
O&M
terminal
software
BAM
Software
BAM
Communication
gateway
iGWB software
Foreground (host)
iGWB
WS
Charging center
Background (OMC)
Figure 3-1 OMC software structure

The local maintenance system is in charge of the operation and maintenance of
individual equipment of M900/M1800 MSC/SSP/IP, while M2000 is responsible for the
centralized operation and maintenance of all the Huawei network entities in the mobile
network. Besides, the M2000 also provides interface for the superior network
3-1
Technical Manual
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 BAM Software

BAM software runs on Back Administration Module (BAM) and provides the function of
maintenance and management of MSC data, performance measurement data and
alarm information needed for the normal operation of the MSC/SSP/IP system.
The M900/M1800 MSC/SSP/IP provides a complete set of effective maintenance
methods and tools, which are important to ensure the normal operation of the system,
to reduce operational costs and to improve service quality.
3.2.1 Functions of BAM Software

BAM is the core of the Operation and Maintenance Center (OMC). As the Server of the
TCP/IP protocol, one end of it responds to the connection request from the Client (WS)
of OMC and the NMC and sets up connection, so that it can makes analysis and other
processing to the commands from the Client. The other end responds to the connection
request from the Host, sets up connection, and implements communications between
BAM and the Host.
BAM is connected with the active and standby boards of the Host (including GSPC,
AMP and CDP) through a network section (a closed LAN connected with the Host). The
connection between BAM and the Client is implemented in another network section (an
open O&M LAN). These two network sections are invisible to each other. Thus the
network security is ensured.
The networking of BAM is shown in Figure 3-2.
3-2
Technical Manual
Host
LAN
Network segment 1
NIC
NIC
NIC
LAN
BAM
Network segment 2
...
WS
WS

NIC: Network Card
WS: Work Station

LAN: Local Area Network
Figure 3-2 Networking of BAM
3.2.2 Features of BAM Software

I. High reliability
Carrier-level server and SQL Server are adopted to serve as the large-scale relational
database system. With RAID5 and Hot spare technologies and programs of multi-level
self-supervision functions, data backup and restoration can be easily realized.
II. Client/Server structure

BAM integrates the communication server and the database server. Maintenance and
operation tasks are executed in the Client/Server mode. It supports simultaneous local
and remote multiple-point data configuration, which makes maintenance operations
very convenient.
III. Remote maintenance function

BAM enables easy remote maintenance, supports flexible networking and can connect
to the remote maintenance system through multiple means such as DDN, E1, Frame
Relay and X.25 network.
Remote maintenance by means of dial-up access is also possible.
In this way, modem and remote access service must be installed in BAM or emergency
workstation, and modem and dial-up network in WS as well. After a user successfully
accesses the remote WS through dial-up networking, BAM server will assign to this WS
user an IP address. With this IP address as the IP address of a Client, workstation will
be added and its authority configured. And then the user can log on the Client and send
3-3
Technical Manual
commands to realize remote maintenance over the MSC by using Telnet or the
MML-based graphical terminal.
IV. MML and GUI interfaces available

MML command line interface and visual GUI in compliance with ITU-T standard are
provided.
Data configuration, performance management and operation and maintenance can be
implemented in MML mode. MML integrated operation interface and multi-window
operation interface are available, providing more means of maintenance.
Alarm information management, signaling and interface tracing, and equipment state
review can be realized easily in GUI mode.
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.
VI. Excellent security measures

z
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.
Regular backup of data improves the system capability to withstand fatal

damages.
3.2.3 Structure of BAM Software

The structure of the BAM software is shown in Figure 3-3:
3-4
Technical Manual
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
Figure 3-3 Structure of BAM software

As shown in Figure 3-3, BAM software includes the following parts:
z
SQL Server: Storing various service data and providing database support to
various service servers.
MML Server: Implementing communications with WS, operator authority

management, WS input command interpretation and WS command distribution.
Exchange Server: Implementing communications with the Host, distribution of

information returned from the Host, and loading of the Host program and data.
Stats Server (Traffic Measurement Server): Processing the performance data,

such as traffic measurement task registration and result storage.
Maintenance Server: Processing the Host maintenance commands, such as

patching the Host program and tracing signaling.
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.
Security Manager: As the management function module of the whole Host

software, managing other service processing modules, including monitoring their
operational state.
BAM Service: Monitoring Security Manager module and restarting BAM computer
in due time.
3-5
Technical Manual
3.3 O&M Terminal Software

The O&M terminal of M900/M1800 MSC/SSP/IP can be in local or remote WS to realize
local/remote O&M function by communicating with BAM. WS can communicate with
BAM over LAN or WAN or via serial port.
The O&M terminal of M900/M1800 MSC/SSP/IP and BAM form the Client/Server
structure and serve as Client, providing user-oriented O&M interface. With MML-based
graphical terminal and multi-window operation interface, the O&M terminal software
provides user with abundant operation and maintenance measures, including service
maintenance system, alarm console and traffic measurement report system.
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.
3.3.1 Service Maintenance System

The MML-based graphical terminal software includes the following functional modules:
z
MML navigation module
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
Maintenance navigation module
The maintenance navigation module provides maintenance command sets in tree

structure to the user. The maintenance operations include tracing operations and
maintenance operations on equipment state panel. The system provides multiple
tracing methods. Double clicking on a node can open the corresponding tracing
interface. The equipment state panel presents the equipment state (normal or faulty),
through which the user can perform maintenance and operations over all boards.
3-6
Technical Manual
3.3.2 Alarm Console

The alarm console can accurately and clearly presents the alarm information recorded
in the BAM in real-time. The user can query and browse all the alarm information via
the alarm console, and implement management over the alarms.
The alarm information includes alarm name, alarm generation (& recovery) time, alarm
level (severity), alarm location information, recovery suggestions, etc.
3.3.3 Traffic Statistics Console

Traffic measurement is also called performance measurement.
The traffic statistics console provides GUI interface for the user to implement operation
and maintenance of performance measurement. In addition, it provides wizard function,
guiding the user to accomplish operation & maintenance tasks, such as registering
measurement task, querying measurement result, outputting query result, self-defining
measurement item, etc. It also provides templates to help the user promptly complete
the operations similar to those defined in the template.
3.4 Communication Gateway

The software of communication gateway comprises the communication gateway at
BAM side (Convert) and remote maintenance proxy (iGate), which enable the access
of the alarm box, and the remote maintenance of WS via Internet.
As a tool, the communication gateway enables BAM and WS to communicate in
another mode - serial port communication (BAM and WS are connected through serial
port cable) other than Ethernet communication. In addition, the communication
gateway at BAM side supports the access of alarm box.
3.4.1 Communication Gateway at BAM Side (Convert)

With alarm box access function, the communication gateway at BAM side (Convert)
can be installed in BAM or WS depending on the location of alarm box. If the alarm box
is placed near BAM, the Convert should be installed in BAM. And in WS if near WS.
3.4.2 Remote Maintenance Proxy (iGate)

The iGate runs on the remote access server. As the communication proxy, it transfers
messages between BAM and the WS, where the remote maintenance via Internet is
conducted. It ensures the security of remote maintenance by encrypting and decrypting
the messages transferred and controlling the IP address of the remote-maintained WS.
3-7
Technical Manual
3.5 M2000 Software

Please refer to attached documentation of iManager M2000 Mobile Network
Management Maintenance System for details.
3.6 iGWB Software

The iGWB software runs in iGWB, forming the Client/Server structure with the bill
console. As the server in the structure, it provides such functions as bill storage, format
conversion, bill filtering and charging interface. The iGWB software supports
dual-server system, which greatly improves software operation reliability.
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.
II. Format conversion

Converting the original binary format bill into text format bill. The bill text format can be
set, including bill contents, width domains, filler, and separator between domains after
format conversion. Besides, user can define domains, for example, add '(' before each
bill and ')' at the end of each bill.
III. Bill filtering

The bills filtered from the unpacked bill packets from bill pool are stored in respective
directory according to their types. The bill type can be dynamically configured
according to the value relation (logic relation such as greater than, smaller than and
equal to) of any domain and the combination of relation (AND, OR). Calling bill and
called bill can be specifically classified according to their call prefixes.
IV. Charging interface

The iGWB provides charging interface. User can select FTP or FTAM as the charging
interface protocol. If FTAM is selected, different low layer protocols (FTAM over TCP/IP
or FTAM over IEEE802.3) are available; if FTP is selected, user can determine whether
to let the iGWB to automatically send bills.
3-8
Technical Manual
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.
II. High reliability

The iGWB software supports dual-server system, and adopts advanced software
program to prevent bill repetition or loss under abnormal conditions.
III. Flexible bill format conversion, sorting and filtering

The bill format conversion, sorting and filtering can be flexibly set through configuration
tools in the iGWB to obtain final bill in particular format and storage directory for the
Billing Center.
IV. Various backup modes available

The iGWB software assists user to improve data security, that is, it supports both
manual backup and automatic backup.
3.6.3 Dual-system of iGWB

To improve the bill reliability, the iGWB adopts Active/Standby server structure, of which
the functions and features are as follows:
I. Using multiple heartbeat paths to realize stable dual-server communications

The dual-server system can support as many as five heartbeat paths, of which the
physical media may be serial port or network adapter.
3-9
Technical Manual
II. Monitoring function

Controlling the running of service (e.g. FTP/FTAM service), the dual-system would
send out alarm and perform switching if a service fails.
III. Virtual IP function

The Client can communicate with the dual-server via single IP. In the single-IP mode, if
one sever of the dual-system is transparent to a user, the user can communicate with
the active server via the same IP address.
IV. Comprehensive fault detection and reliable switchover strategy

When the active server is faulty, the dual-system will send out alarm and automatically
switch the work to the other normal server. The dual system can detect the following
faults:
z
Writing file failure
Abnormal communication with MSC
Hard disk full
Network card fault
Hard disk fault
Service failure
Program malfunction
3.6.4 Structure
The iGWB software is running on Windows NT Operating System. It is composed of
Figure 3-4 Structure of iGWB software

The functions of various modules are as follows:
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
several functional modules, as shown in Figure 3-4.
Technical Manual
z
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.
Intermediate module: Implementing sorting and format conversion of the original

bills and sending the final bills to the back storage module.
Back storage module: Saving the final bill in respective directory according to its
type.
FTP/FTAM module: providing interface to the Billing Center.
Maintenance module: Providing interface to bill console, enabling user to

implement relevant maintenance through the bill console; converting the iGWB
alarm information and forwarding it to the Host communication module.
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
Technical Manual
MSC Functions
Technical Manual
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
MSC Functions
Table of Contents
3.1.2 MTP......................................................................................................................... 3-2

3.1.3 SCCP ...................................................................................................................... 3-5
3.1.4 TCAP..................................................................................................................... 3-13
3.1.5 MAP....................................................................................................................... 3-16
3.1.6 BSSAP .................................................................................................................. 3-24
3.1.7 TUP ....................................................................................................................... 3-28
3.1.8 ISUP ...................................................................................................................... 3-34
3.2 DSS1................................................................................................................................ 3-38
3.2.1 Introduction to ISDN Network................................................................................ 3-38
3.2.2 Structure of DSS1 ................................................................................................. 3-40
3.2.3 Physical Layer ....................................................................................................... 3-40
3.2.4 Data Link Layer ..................................................................................................... 3-41
3.2.5 Network Layer ....................................................................................................... 3-42
3.3 CAS.................................................................................................................................. 3-45
3.3.1 Overview ............................................................................................................... 3-45
3.3.2 Line Signaling........................................................................................................ 3-46
3.3.3 Register Signaling ................................................................................................. 3-47
3.3.4 Signaling Procedure.............................................................................................. 3-50
3.3.5 CAS Multi-nation Adaptation ................................................................................. 3-52
Chapter 4 Mobile Service Procedures......................................................................................... 4-1
4.1 MOC and MTC Processing Procedure .............................................................................. 4-1
4.1.1 MOC Processing Procedure ................................................................................... 4-1
4.1.2 MTC Processing Procedure .................................................................................... 4-2
4.2 Office Direction Call Processing Procedure ...................................................................... 4-4
4.2.1 Mobile Terminated Inter-office Call Processing Procedure .................................... 4-4
4.2.2 Tandem Call ............................................................................................................ 4-4
4.3 Handover Procedure.......................................................................................................... 4-5
4.3.1 Intra-MSC Handover Procedure.............................................................................. 4-6
4.3.2 Basic Handover Procedure ..................................................................................... 4-6
4.3.3 Subsequent Handover Procedure........................................................................... 4-8
4.4 CF Processing Procedure.................................................................................................. 4-8
4.5 Call Hold Processing Procedure...................................................................................... 4-10
4.6 Call Wait Processing Procedure ...................................................................................... 4-11
4.7 Multiparty Service Processing Procedure........................................................................ 4-12
4.8 Explicit Call Transfer (ECT) Processing Procedure......................................................... 4-13
4.9 SMS Processing Procedures........................................................................................... 4-14
4.9.1 Introduction to SMS............................................................................................... 4-14
4.9.2 Short Message Service (MT/PP)........................................................................... 4-16
4.9.3 Short Message Service (MO/PP) .......................................................................... 4-17
4.9.4 Instant Triggering after SMS-MT Failure............................................................... 4-19
4.10 Virtual Roaming Service (VRS) Processing Procedure................................................. 4-20
ii
Technical Manual
MSC Functions
Chapter 1 Mobile Services

M900/M1800 MSC/SSP/IP fully complies with ETSI GSM Phase 2 and GSM Phase 2+
specifications, and provides basic telecommunication services (including Teleservice
and Bearer service), supplementary services, data services and intelligent services.
1.1 Basic Telecommunication Services

Basic telecommunication services include Teleservice and Bearer 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.
II. Short message service

Short Message Services include Point-to-Point (PP) SMS and point-to-multipoint SMS.
Point-to-Point SMS consists of short message Mobile Originated service (MO/PP) and
short message Mobile Terminated service (MT/PP).
Point-to-multipoint service refers to short message cell broadcast service.
z
Short message MO/PP
Mobile subscriber sends short messages to Short Message Center (SMC).
1-1
Technical Manual
z
MSC Functions
Short message MT/PP
SMC sends a short message to a mobile subscriber.

z
Short message cell broadcast
SMC sends a short message to mobile subscribers in the specified cell(s).

Short Message Service is the only Teleservice that can be carried only with signaling
channel. It can be provided concurrently with speech service.
This service provides the GSM mobile subscribers with a simple, practical and
extendable platform for exchanging text information. The Point-to-Point SMS performs
the function of bi-directional paging between the mobile subscribers. Short message
cell broadcast service provides the mobile subscribers with public broadcast text
information. Therefore, the Short Message Service is a new channel for communication,
improving the information exchange capability for the network.
As defined in ETSI GSM 03.40 and ETSI GSM 03.41, the point-to-point short message
allows subscribers to send or receive short messages any time, while the broadcast
short message allows subscribers to receive various public information regularly and
selectively.
The operator can change the service attribute of the subscriber through the subscriber
management system. For example, the operator can bar the SMS of a particular
subscriber, so that the subscriber can neither send nor receive short messages. The
mobile subscriber can also perform service barring operation provided in the
Supplementary Service, to temporarily suspend the sending and receiving of short
messages.
Different information source entities can be connected to service platform by expanding
the application database interface of the short message center (SC), so as to provide
connection channels for the mobile subscribers and the information exchange system
and to expand external services of mobile communication. Information source entities
can be Internet server, changing system, paging system, fax service center, voice
mailbox, etc. Then information other than from PLMN network (such as e-mail, fax and
paging messages) could be sent or received by mobile station.
Note:
Short message broadcast service has nothing to do with MSC.
1-2
Technical Manual
MSC Functions
III. Facsimile service

This service allows the connection of group 3fax apparatus to the mobile stations of
GSM PLMN. Facsimile connection may be established from PSTN/ISDN to GSM
PLMN or inside GSM PLMN.
z
Automatic facsimile group 3
The Teleservice supports facsimile group 3 autocalling/autoanswering function.

z
Alternate speech/facsimile group 3
In the case both speech and facsimile services are needed, M900/M1800 MSC/SSP/IP
supports the communication of speech followed by facsimile.
1.1.2 Bearer Services

Data communication (especially Internet) is becoming more and more popular. Data
service is also becoming one of the major services provided by GSM operators.
Besides the above-described facsimile services, M900/M1800 MSC/SSP/IP also
supports the following bearer services.
Bearer Service provides the capability to transmit information between the terminal
access reference points. This capability includes some low-layer functions,
corresponding to layers 1~3 of the OSI reference model.
1)
According to access modes, bearer services include:
3.1kHz audio (external to PLMN)
PSTN provides subscribers with a channel capable of transmitting 3.1kHz analog

speech signals, while in GSM PLMN, the signals transmitted between the mobile
terminals and the networks are all digitized. Therefore, a special audio MODEM is
needed at the connection point between GSM PLMN and PSTN to fulfill this
conversion.
For the data communication between PLMN subscribers and PSTN subscribers, only
3.1kHz audio mode can be adopted. While for the data communication between PLMN
subscribers and ISDN subscribers, 3.1kHz audio mode or Unrestricted Digital Information
(UDI) mode can be used.
This mode supports multiple subscriber rates including 300bit/s, 1200bit/s,
1200/75bit/s, 2400bit/s, 4800bit/s and 9600bit/s.
z
PAD (Packet Assembly/Disassembly)
MSC (Mobile Switching Center) provides an asynchronous connection to PAD

equipment. This enables PLMN subscribers to access a packet network
(PSPDN/ISDN).
1-3
Technical Manual
MSC Functions
This mode supports multiple subscriber rates, including 300bit/s, 1200bit/s,

1200/75bit/s, 2400bit/s, 4800bit/s and 9600bit/s.
z
Packet
Basic packet access provides a synchronous connection that enables PLMN

subscriber to access a packet network (PSPDN/ISDN). In this case, the mobile
subscriber can only be a calling party.
This mode supports multiple subscriber rates, including 1200bit/s, 2400bit/s, 4800bit/s
and 9600bit/s.
2)
According to transmission mode, bearer services can be grouped into the

following categories:
Transparent transmission mode (T-mode)
T-mode is a transmission scheme in which error correction is completed by the forward

error correction mechanism provided by radio interface transmission scheme. The
available throughput and transmission delay is fixed. T-mode does not apply Radio Link
Protocol (RLP).
z
Non-transparent transfer mode (NT-mode)
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:
Asynchronous circuit bearer services(BS2X)
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
Basic packet bearer services (BS3X)
BS3X provides full-duplex circuit-switched synchronous data transmission at various

rates to achieve data exchange among packet terminals. BS3X supports:
communication between mobile subscribers and packet terminals in PSTN/ISDN,
access of PLMN to AU (Access Unit) of PSPDN through PSTN, access of PLMN to PH
(Packet Handler) of PSPDN through ISDN, or directly to PSPDN through PH of ISDN.
z
Dedicated PAD Access (BS4X)
1-4
Technical Manual
MSC Functions
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
Dedicated packet bearer services (BS5X)
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.
1.2 Supplementary Services (SS)

When M900/M1800 MSC/SSP/IP serves as GMSC, it does not take subscribers, but it
provides corresponding processing and support when it gets route information through
HLR, if the mobile subscriber subscribes to certain supplementary services such as
CFU and CFNRc. When the subscriber owns CAMEL subscription data and subscribes
to CFU/CFNRc services, GMSC performs MOC procedure.
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.
A Supplementary Service modifies or enhances a basic Teleservice and hence, cannot

be offered to a subscriber alone. It must be offered together or in association with a
basic telecommunication service. The same supplementary service may be offered
with a number of different Teleservices.
M900/M1800 Digital Cellular Mobile Switching System provides Line Identification, Call
Forwarding, Call Barring, Call Completion, Multiparty, Community of Interest, Advice of
Charge, and Unstructured supplementary services.
Besides the above services defined in GSM specifications, M900/M1800 MSC/SSP/IP
also provides self-defined services to meet customer demands.
1.2.1 Line Identification SS

Line Identification supplementary services include CLIP, CLIR, COLP and COLR.
z
CLIP (Calling Line Identification Presentation)
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
z
MSC Functions
CLIR (Calling Line Identification Restriction)
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
COLP (Connected Line Identification Presentation)
COLP is a Supplementary Service provided to the calling party. When a mobile

subscriber makes a call, there may be the case that the connected subscriber is not the
called party because the called party activates his call forwarding SS. At this time the
network will display the connected number to the calling subscriber.
z
COLR (Connected Line Identification Restriction)
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.
1.2.2 Call Forwarding SS

Call Forwarding supplementary services include CFU, CFB, CFNRy and CFNRc.
z
CFU (Call Forwarding Unconditional)
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
CFB (Call Forwarding on Mobile Subscriber Busy)
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
CFNRy (Call Forwarding on Mobile Subscriber No Reply)
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
CFNRc (Call Forwarding on Mobile Subscriber Not Reachable)
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.
1.2.3 Call Completion SS

Call Completion supplementary services include Call Waiting (CW) and Call Hold
(HOLD).
z
CW (Call Waiting)
1-6
Technical Manual
MSC Functions
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
HOLD (Call Hold)
The Call Hold Service allows a mobile subscriber to interrupt communication of an

ongoing call so as to initiate a new call or switch over to another call being held, and
then subsequently, if desired, resume the call just interrupted. When a call is on hold,
the MS temporarily being disconnected will hear prompt tone and music.
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.2.5 Community of Interest SS

The group of Community of Interest supplementary services includes one
supplementary service: Closed User Group (CUG).
CUG (Closed User Group) service is for a group, which can be of single subscriber or
several subscribers with the same attributes. CUG service allows one subscriber to join
in different closed user groups (max. 10).
CUG service can successfully meet the demands of both small groups of a few
members or large organizations with thousands of subscribers.
CUG can use all telecommunication services except emergency call, short message,
dedicated PAD access and dedicated packet access.
Closed User Group service has the following options:
CUG calls only: The subscribers with this feature can originate calls to or receive calls
from other members of the same group.
Incoming calls barred within a CUG (icb): The subscribers with this feature cannot
receive calls but can make calls to other members in the group.
Outgoing calls barred within a CUG (ocb): The subscribers with this feature cannot
originate calls but can receive calls from other members in the group.
1-7
Technical Manual
MSC Functions
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.
1.2.6 AoC Supplementary Services

The Charging supplementary services comprise two services: Advice of Charge
(Information) and Advice of Charge (Charging).
z
AoCI (Advice of Charge, Information)
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
AoCC (Advice of Charge, Charging)
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.
1.2.7 Call Barring SS

The call barring SS defined in GSM specification comprises barring of incoming calls
and barring of outgoing calls.
Barring of incoming calls includes Barring of All Incoming Calls (BAIC) and Barring of
Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam).
Barring of outgoing calls includes Barring of All Outgoing Calls (BAOC), Barring of
Outgoing International Calls (BOIC) and Barring of Outgoing International Calls except
those directed to the Home PLMN Country (BOIC-exHC).
z
BAIC (Barring of All Incoming Calls)
With this service, the calls to this subscriber will be barred.

z
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
BAOC (Barring of All Outgoing Calls)
1-8
Technical Manual
MSC Functions
With this service, all calls made by this subscriber will be barred except for the
emergency calls.
z
BOIC (Barring of Outgoing International Calls)
With this service, all international calls made by this subscriber will be barred.
z
BOIC-exHC (Barring of Outgoing International Calls except those directed to the

Home PLMN Country)
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.
1.2.8 Unstructured Supplementary Service

Unstructured
supplementary
service
mainly
refers
to
USSD
(Unstructured
Supplementary Service Data)

USSD is adopted to provide information to subscribers in the interaction mode. It is
implemented in two modes: one is that GSM network is used to provide information
services concerning subscribers; the other is that GSM network is the bearer network
and information services are provided by the special information center, which is called
the "USSD Center".
The equipment related to USSD are shown in Figure 1-1.
MSC
BSS
HLR
SS7 network
USSD Center
USSD Center
INTERNET/PSTN/PSPDN/ISDN
Figure 1-1 Devices related to USSD
1-9
Technical Manual
MSC Functions
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
Flight schedule or other information service.
Stock information.
Foreign exchange information
Sports information
Ticket booking services.
Bank account 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)
It facilitates the creation and provisioning of new services.
1.2.9 Explicit Call Transfer (ECT)

ECT is a call forwarding service determined by the mobile subscriber. The subscriber
who has registered ECT service can temporarily cut off an undergoing call and
originate a new call via call hold (HOLD) function. After the new call is successfully
connected, the subscriber can trigger the ECT service to enable the conversation
between the party involved in the original call and the called party in the new call. At the
same time, he quits the service himself. However, to implement ECT service, the
mobile subscriber must have subscribed to call hold service.
1.2.10 ODB Supplementary Services

ODB (Operator-Determined Barring) function means that the PLMN operator can
regulate the subscribers access to certain GSM services. It is fulfilled through the
management of data in HLR (Home Location Register).
ODB applies to all subscriber services and Bearer Services except emergency calls. It
takes precedence over the Supplementary Services described above. When there is
conflict between the two, the Supplementary Service will be restricted.
ODB is similar to call barring SS, with the difference described as follows:
1-10
Technical Manual
MSC Functions
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 calls
Barring outgoing international calls
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
Barring incoming calls when roaming outside the home PLMN country
Barring of Roaming outside the home PLMN country
Barring of outgoing Premium Rate Calls (Information)
Barring of outgoing Premium Rate Calls (Entertainment)
Barring of Supplementary Services Management
1.2.11 Self-defined Supplementary Services

To meet specific customer requirements, M900/M1800 MSC/SSP/IP also provides
some self-defined supplementary services, including subscriber roaming area
restriction, LA-dependant roaming area restriction and subscriber roaming restriction.
z
Roaming area restriction (through Zone Code)
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
LA-dependant roaming area restriction
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
Subscriber roaming restriction (through VLR table)
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
MSC Functions
1.3 Value-Added Services

M900/M1800 MSC/SSP/IP provides Location Service (LCS).
LCS refers to the location-related services provided to the mobile subscriber by the
mobile network operator who determines the geographical location of the mobile
station by use of specialized mobile location techniques. The location services locate
the mobile terminal to the cell level.
The applications of LCS cover multiple aspects ranging from security to charging and
from information service to tracing management, such as public security services (e.g.
emergency services and emergency alarm services), location-based charging and
tracing services, and location-based information services (e.g. navigation, sightseeing,
broadcast to designated area, and mobile yellow page).
M900/M1800 MSC/SSP/IP provides Virtual Roaming Service (VRS). The subscriber
-Mobile V- who has registered for the VRS owns one MSISDN respectively in each
network of both countries/regions. The VRS can be implemented via special service
procedure: When a subscriber in Country/Area A calls the Mobile V, he only needs to
dial Mobile V's MSISDN in the network of Country/Area A. Likewise, when a subscriber
in Country/Area B calls the Mobile V, he only needs to dial Mobile V's MSISDN in the
network of Country/Region B.
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
MSC Functions
Chapter 2 Network Functions

This chapter covers the functions of M900/M1800 MSC/SSP/IP as a physical entity on
the wireless network, including security management, mobility management and call
handling, which support the realization of system services.
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.2 User Information Ciphering

Since radio is an unsecured medium for transmission, to ensure the personal
communication security, the user data is encrypted before transmission and the same
is decrypted at the receiver end. Kc (which is negotiated by MS and network) and the
current pulse string frame number are calculated by algorithm A5 to generate ciphering
2-1
Technical Manual
MSC Functions
code. And Kc is obtained from RAND in the authentication request message and Ki
through algorithm A8.
2.1.3 TMSI Re-allocation

TMSI is the temporarily allocated subscriber identity in VLR to strengthen the system
security. It is in unique correspondence with IMSI in a VLR area. TMSI and IMSI have
no long-term fixed relation. TMSI is under the management of MSC/SSP/IP and is used
to replace IMSI for transmission through radio channel in order to prevent the third party
from identifying and tracing the mobile subscriber. The correspondence relationship
between TMSI and IMSI is saved in VLR of the visited location area of MS. The latest
allocated TMSI will be saved in the SIM card of MS.
The implementation of TMSI re-allocation can be executed during subscriber location
update, call setup and Supplementary Service processes.
z
TMSI re-allocation during location update
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
TMSI re-allocation during service access
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.1.4 Equipment Identification

Based on the International Mobile Equipment Identity (IMEI) of the MS, MSC checks
the MS status from the EIR and determines whether to provide service to the MS
according to the MS status returned. This process is equipment identification.
IMEI is the unique identification number for each GSM MS, and each MS must have
one. It is used to prevent the illegal use of stolen MS or the MS not supported by GSM
network due to technology factors. The MS manufacturer should be responsible for the
uniqueness of IMEI and provide detailed information about it.
The IMEI of MS is saved in EIR, which has three equipment registers, namely white list,
grey list and black list. The white list stores the IMEIs of all the usable MSs. The black
list stores the IMEIs of all the forbidden MSs. The grey list stores the IMEIs of all the
MSs, which are not forbidden but need to be traced.
During the security check (including authentication, user information ciphering,
equipment identification and TMSI re-allocation) in location updating or call setup, MSC
queries MS status from EIR upon the IMEI obtained. Based on the information returned,
the MSC allows the access of the MS in the white list and rejects the MS in the black list.
2-2
Technical Manual
MSC 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
Flow selection of equipment identification.
Reuse of IMEI.
Selection of whether to perform equipment identification when EIR is unavailable.
Selection of whether to let the MS access when the status of MS is unknown (No
such IMEI is found in EIR).
Selection of whether to let the MS access or whether to play announcement when

it is in grey list.
Selection of whether to perform equipment identification according to IMSI.
2.2 Mobility Management

2.2.1 Location Management
The location management function of M900/M1800 MSC/SSP/IP is fulfilled through the
logical cooperation of the entities including HLR (Home Location Register) and
MSC/VLR. HLR stores the current location information of an MS and all the subscriber
data. VLR (Visitor Location Register) stores the related subscriber data of an MS
roaming to its location area. MSC handles the location registration of the MS, makes
session with it and exchange information with HLR and VLR.
The location management function includes location registration, periodical location
registration, MS power-off and subscriber data deletion.
z
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
Periodical location registration
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
Subscriber records deletion
2-3
Technical Manual
MSC 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
MSC 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.
2.3 Call Handling

M900/M1800 MSC/SSP/IP provides flexible call handling function for the connections
of various types of calls.
According to service types, calls can be classified into two types: ordinary service calls
and intelligent service calls. The processing of ordinary service calls is the basic call
handling function. Intelligent service call handling is the call handling function based on
ordinary services and with intelligent service features.
Basic call handling functions include call connection, number storage and decoding,
routing, echo cancellation and tone sending functions.
2.3.1 Call Connection Function

M900/M1800 MSC/SSP/IP enables incoming and outgoing call handling for valid
subscribers in its range, including internal call, outgoing call, incoming call and transit
call. That is, M900/M1800 MSC/SSP/IP can serve as one of the following network
entities: GMSC, VMSC, integrated VMSC/GMSC, or TMSC. The following are some
basic functions provided by MSC:
z
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.
Allocating MSRN flexibly to the called mobile subscriber according to operators

request.
2-5
Technical Manual
z
MSC 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 Special Service calls defined by the operator.
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.
Supporting the establishment of 64kbit/s SPC (Semi-Permanent Connection) via

man-machine commands.
Supporting the checks on the incoming access and outgoing access,
Supporting the forced disconnection of ongoing illegal calls.
Supporting the forced disconnection of calls with MML command.
2.3.2 Number Storage and Translation Function

M900/M1800 MSC/SSP/IP features powerful capability to analyze numbers, from
which abundant applications are derived.
z
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
z
MSC 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 enables various conversions of the outgoing forwarded-to number and the

number to be connected.
It enables the conversions of CLIP number and various numbers in bills.
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.
It supports the number conversion operations at specified location in plain or

inverted sequence, such as deleting, modifying, escaping or extracting number,
etc.
2.3.3 Route Analysis Function

Routing includes internal routing (routing to the BSC of the MSC. The called subscriber
is a mobile subscriber of the local MSC) and inter-exchange routing (routing to another
exchange. The called subscriber is a mobile subscriber of another MSC or PSTN
subscriber).
z
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
M900/M1800 MSC/SSP/IP provides rich routing functions, i.e. to select connection

paths according to the information of the calling and called subscribers.
The calling subscriber information mainly refers to the location information of the calling
subscriber. For the mobile subscriber of the local MSC, the information is the current
location area or cell. If the calling subscriber belongs to another MSC, it refers to the
trunk circuit occupied by the call. All the calling location information is abstracted into a
route selection source code.
The called subscriber information refers to the location information of the called
subscriber, which is directly included in the called number. The information is
abstracted into a route selection code after number analysis. M900/M1800
2-7
Technical Manual
MSC 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).
Routing according to calling subscriber attribute, i.e. setting different route

selection codes in the case that the called numbers are same, but the calling
subscribers are of different attributes. For example, 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) or service attributes (PPS,
AOC, HOTBILL and other customized services).
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
M900/M1800 MSC/SSP/IP can prevent alternative routing between offices of the

same-level. Abnormal circumstances occurring to the network may bring about
message storm between the same-level offices and exhaustion of circuit
resources. In M900/M1800 MSC/SSP/IP, however, this fault can never happen.
2-8
Technical Manual
MSC Functions
2.3.4 Echo Control

I. Principle of echo generation
Echo is generated in PSTN. Echo comprises electronic echo and acoustic echo.
Electronic echo is generated due to the non-matching resistance of 2-wire/4-wire
conversion (hybrid) at PSTN end. Acoustic echo is generated due to the poor insulation
of receiver and transmitter of the fixed telephone.
When the echo path delay is more than 30ms, echo is generated, which can be noticed
by remote subscribers and will affect the communication quality. Echo delay path can
be up to 64ms when the MS is connected with the PSTN subscriber. Therefore, the
echo cancellation equipment is essential for GSM system to suppress this effect.
Major reasons for echo in the radio path are:
z
Time delay of transmission information in the radio link.
Time delay due to BTS or MS equalizing adopted to overcome multi-path delay.
Time delay generated by TRAU (Transcoder/Rate Adaptation Unit) to realize code

conversion.
II. Echo cancellation equipment

M900/M1800 MSC/SSP/IP provides two types of echo cancellation equipment: built-in
echo cancellation equipment and standalone echo cancellation equipment.
Built-in echo cancellation equipment is based on the idea of resources monopolization,
i.e. each trunk circuit occupies a set of echo cancellation equipment. The GECS is a
built-in echo cancellation equipment and cancels echo while leading in 16 channels of
E1 signals to MSC.
Standalone echo cancellation equipment is based on the idea of resources sharing.
The echo cancellation devices are placed in ECPOOL (Echo Cancellation Pool) and
will only be occupied through application process on demand. And one will be released
immediately after use so as to be available for other connections. The amount of
standalone echo cancellation equipment may be configured flexibly according to the
amount of trunk equipment that is likely to generate echo and the volume of traffic, so
as to maximize resource sharing. One GECP board can provide global shared
ECPOOL for 256 E1s.
In terms of system resource occupation, GECP needs to occupy slot in interface frame.
For a service connection in need of echo cancellation, standalone echo cancellation
equipment, if applied, would occupy four switching timeslots in the Central Switching
network (one for incoming E1 timeslot, one for outgoing E1 timeslot and the other two
for echo cancellation equipment), as is shown is Figure 2-1. However, only two
switching time slots are needed for built-in echo cancellation equipment (with each for
2-9
Technical Manual
MSC 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
Figure 2-1 Occupation of network resources by standalone echo cancellation equipment
CNET
E1
GE16/
GSTU
GECS
E1
Figure 2-2 Occupation of network resources by built-in echo cancellation equipment
2.3.5 Tone Sending Function

I. Number initial tone-sending and failure tone-sending
With respect to call connection, M900/M1800 MSC/SSP/IP provides two types of
tone-sending, i.e. number initial tone-sending and failure tone-sending.
z
Number initial tone-sending corresponds to successfully connected calls. The

operator can decide whether to send tones for some special dialed numbers
through data configuration.
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
MSC Functions
II. Synchronous and asynchronous tone-sending

With respect to the playback mode of signal tones, M900/M1800 MSC/SSP/IP provides
two tone-sending modes: synchronous tone-sending and asynchronous tone-sending.
z
The synchronous tone-sending starts from the beginning and is immediately

stopped after a certain period of time as set. The synchronous announcement
voice file can be optionally modified and re-recorded by loading when it is running,
making voice more clear to subscribers. Additionally, the convenient loading
function facilitates users in different places to optimize the network according to
their local actual conditions. This mode requires more tone-sending channels (in
general, one call occupies exclusively one tone-sending channel).
The feature of asynchronous tone-sending is that there is no start or end position

of the play. The subscriber may not listen to the record tone from its real starting
position. The play can be random. This mode requires less tone-sending channel
resources (multiple calls can share a tone-sending channel).
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.
III. Tone-sending in multiple languages

The tone board software of M900/M1800 MSC/SSP/IP can support multiple languages
by loading syntax analysis modules. The tone board can support eight types of
languages with eight types of syntax analysis modules loaded.
2.3.6 IWF Function

M900/M1800 MSC/SSP/IP enables the interworking with PSTN, ISDN and Internet via
IWF (Network Interworking Function unit) to provide diversified data services to mobile
subscribers. The position of IWF in the system is shown in Figure 2-3.
2-11
Technical Manual
MSC Functions
PSTN
Facsimile machine
BSS
IWF
Internet
MS
Computer
ISDN
Laptop
ISDN phone set

Internet: Internet
IWF: InterWorking Function unit

Figure 2-3 Position of IWF in system

Data services here refer to the combination of bearer services and part of telecom
services (G3 facsimile). The implementation of data services in the GSM system is
much different from that of speech services, which is mainly presented in the MS
access, radio channel coding/decoding, TRAU frame processing and IWF module that
enables the interworking function.
First of all, MS supports data services through data terminals. The data terminal (such
as portable PC) can connect to the MS via the interface provided by the PC Card and
corresponding software attached to the data terminal, or via the serial port or infrared
interface. MS generally simulates the MODEM function to enable asynchronous
character access or realizes the synchronous bit access function via software.
BTS implements channel coding function and rate adaptation of RA1', RA1, RA2 and
RAA. TC (Transcoder) enables the conversion between data TRAU frame and V.110
frame.
IWF implements processing of the interworking protocol and provides MODEM POOL
or corresponding rate adaptation process according to different interworking networks.
The idea of the IWF protocol is to cater the high error rate and limited bandwidth of the
GSM radio interface to enable the transparent transmission between the mobile
subscriber and the interworking network. The GSM section between the mobile
subscriber and IWF can be regarded as the interconnection of extended digital terminal
equipment and digital communication equipment. The networks interworking with IWF
include PSTN, ISDN and PSPDN.
2.3.7 Number Receiving Delay Function

The number analysis process starts when the called number is up to the length of the
min. number determined by the data configuration.In data configuration, the minimum
length of the called prefix is difficult to determine due to the uncertainty of the called
2-12
Technical Manual
MSC Functions
number length. As a result, intelligent service, roaming number fetching or route

outgoing may be enabled before the called number is complete yet.
The number receiving delay function, an optional function of M900/M1800 MSC/SSP/IP,
ensures that the number analysis starts after the complete called number is received.
The delay time is determined by the data configuration.
2-13
Technical Manual
MSC Functions
Chapter 3 Mobile Application Protocols

This section describes the mobile application protocols used by M900/M1800
MSC/SSP/IP serving as GMSC and VMSC, including Signaling System No.7 (SS7),
Digital Subscriber Signaling System No.1 (DSS1) and Channel Associated Signaling
(CAS). For WIN application protocols, please refer to Module 5 SSP Functions of this
manual.
3.1 SS7 System

This part introduces the structure, functions, signaling procedure of SS7, and the
support and realization of SS7 by M900/M1800 MSC/SSP/IP.
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
MSC Functions
ITU-T Signaling System No.7 users
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
CAP: CAMEL Application Part

SCCP: Signaling Connection and Control Part
TUP: Telephone User Part
OMAP: Operation & Maintenance Application Part
Figure 3-1 SS7 structure
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.
II. Signaling Data Link Function (MTP Layer-1)

Signaling data link serves as the path for signaling transmission. It comprises
bi-directional data paths with the same transmission rate.
Through the Central Switching Network (CNET), the SS7 signaling processing board
GCPC can establish a semi-permanent connection with a timeslot in PCM of the digital
trunk board (GE16. GSTU, etc.), to serves as 64 kbit/s signaling data link. The
establishment of SS7 signaling data link is shown in Figure 3-2.
The advantage of SPC is that any TS (except the synchronization TS0) can be used as
the Signaling Data Link.
3-2
Technical Manual
MSC Functions
CNET
GE16/GSTU
SPC
GCPC
HDLC communication
HDLC communication
Bus comm.
Active GSPC
Figure 3-2 Establishment of M900/M1800 MSC/SSP/IP signaling data link
III. Signaling Link Function (MTP Layer-2)

Signaling Link Function (layer-2) sends the signaling to the data link and together with
the first layer provide reliable signaling message transfer link between two directly
connected signaling points.
Functions of Layer 2 include signaling unit bordering, signaling unit orientation, error
detection, error correction, initial orientation, processor fault, Layer-2 flow control and
signaling link error rate monitoring. The GCPC board executes the above functions.
IV. Signaling Network Function (MTP Layer-3)

Signaling Network Functions (Layer 3) refer to the functions and procedures that
transfer management information between Signaling Points to guarantee the reliable
transfer of signaling information when the signaling links and Signaling Transfer Points
in the signaling network fail. Signaling network functions include signaling message
processing and signaling network management.
1)
Signaling Message Processing
Signaling Message Processing functions send signaling messages to the

corresponding signaling links or user parts (such as TUP and ISUP) on the basis of
message label analysis.
Signaling Message Processing functions comprise three parts: Message Routing
(MRT), Message Discrimination (MDC) and Message Distribution (MDT).
The proceeding process is shown in Figure 3-3.
3-3
Technical Manual
MSC Functions
MTP user part
Message distribution
Message to local of fice

Message to other signal points
Message
discrimination
Message routing
MTP layer-3 signaling message processing
MTP level-2 signaling link function
Figure 3-3 Signaling message processing

z
Message Routing (MRT)
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
Message Discrimination (MDC)
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
Message Distribution (MDT)
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)
Signaling Network Management
The function of Signaling Network Management is to re-structure the signaling network

and to keep & recover the normal transfer capability of the signaling unit when the
signaling network fails.
3-4
Technical Manual
MSC Functions
Signaling Network Management comprises three parts: Signaling Traffic Management,

Signaling Link Management and Signaling Route Management.
z
Signaling Traffic Management (STM)
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
Signaling Link Management (SLM)
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
Signaling Route Management (SRM)
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
MSC Functions
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)
II. SCCP Functions

Major functions of SCCP include Network Service function, Routing function and
Management function, as shown in Figure 3-4.
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 management primitive
MTP
Figure 3-4 SCCP functional modules
1)
Network Service function
There are four different classes of protocols corresponding to SCCP network services:
z
Class-0: Basic connectionless service.
Class-1: Sequential connectionless service.
Class-2: Basic connection-oriented service.
Class-3: Flow control connection-oriented service.
3-6
Technical Manual
MSC Functions
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
DPC+SSN or GT (or both)
GT+(SSN)
3-7
Technical Manual
MSC Functions
DPC is the Destination Point Code used by MTP in addressing.

SSN (Sub-System Number) is used to identify different SCCP users in the same node,
such as ISUP, MAP and TCAP. In this way, the lack of MTP users can be compensated
and the addressing range can be expanded to meet the requirements of future new
services.
GT (Global Title) is a dialed number, such as international and national telephone
numbers, ISDN numbers and E.214 numbers that are unique in GSM (mobile GT
numbering mode). It does not represent routing information in the signaling network
directly and can be obtained only via GT code translation. DPC is meaningful only in
the designated signaling network, as compared to GT's global range. The address
range of GT is far larger than that of DPC, which enables the transfer of information
unrelated to circuits between any two Signaling Points in the global range. The
powerful addressing ability of GT codes is an important feature of SCCP.
M900/M1800 MSC/SSP/IP SCCP Routing function enables all types of GT code
translation. The following types of address information can be translated according to
requirements: DPC+SSN, DPC+ old GT, DPC+ new GT and DPC.
Upon the receiving of a message from MTP, SCCP route control analyzes the called
address. If the local node is the destination of the message, the message will be
assigned to the target user. Otherwise, the address will be translated into new routing
label or possible new called address to be sent to MTP.
Upon the receiving of a connection-oriented or connectionless message, SCCP
implements route analysis and sends the message to MTP, connection-oriented part or
connectionless part for processing.
3)
Management function
SCCP Management (SCMG) is to keep the network functionality by re-routing or

adjusting traffic in case of network faults or congestion. This function is achieved by
transferring SCCP management messages and primitives. Its management messages
adopt Class-0 UDT.
SCCP management includes Signaling Point management, sub-system management,
active/standby sub-system switchover, state information broadcasting and faulty
sub-system state test.
M900/M1800 MSC/SSP/IP provides friendly man-machine interfaces for SCCP
maintenance. Functions to be implemented include the query and setting of the status
of Signaling Points and sub-system, GT code testing and message tracing.
III. Support of multi-SP

Besides the above functions, M900/M1800 MSC/SSP/IP also supports multi-SP
function.
3-8
Technical Manual
MSC Functions
IV. SCCP Primitives

In OSI reference model, layer N+1 is the user of layer N, while layer N-1 is the service
provider of layer N. Requested by layer N+1, layer N, through the connection provided
by layer N-1, communicates with the peer layer N of another network node according to
specified protocols of layer N to complete information exchange between N+1 layers.
The essential messages for the interaction between adjacent layers are called service
primitives.
The service interface between SCCP and its upper-layer (SCCP user), and that
between SCCP and MTP are described in primitives. The primitives used between
SCCP
and
its
upper-layer
include
connectionless
service
primitives,
connection-oriented service primitives and SCCP management primitives. MTP

oriented primitive comprises MTP service primitive and MTP management primitive.
1)
Connectionless service primitive
N_UNITDATA: Unit data primitive, used in connectionless service to transfer data

message. It includes N_UNITDATA Request and N_UNITDATA Indication.
z
N_UNITDATA Request: SCCP user requests SCCP transfer data to SCCP of

another node.
N_UNITDATA Indication: SCCP indicates the arrival of user data.
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)
Connection-oriented service primitive
N_CONNECT: Connection setup primitive, used in connection-oriented service for

connection setup. It includes N_CONNECT Request and N_CONNECT Indication.
z
N_CONNECT Request: Sent by calling SCCP user to SCCP, requesting to start

connection establishment procedure so as to establish signaling connection.
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.
N_CONNECT Acknowledgement: Sent by SCCP of the calling node (where the

calling party locates) to the calling party, notifying the calling party to acknowledge
the establishment of signaling connection.
N_DATA: Data primitive, used in connection-oriented service for transferring data

messages. It includes N_DATA Request and N_DATA Indication.
3-9
Technical Manual
z
MSC Functions
N_DATA Request: SCCP user requests SCCP transfer data on the established
N_DATA Indication: SCCP notifies SCCP user that data from peer end has been
received on the established signaling connection.
N_EXPEDITED: Expedited data primitive, used in Class 3 protocol to transfer

emergency data. It includes N_EXPEDITED DATA Request and N_EXPEDITED DATA
Indication.
z
N_EXPEDITED DATA Request: SCCP user requests SCCP transfer expedited

data to SCCP of another node.
N_EXPEDITED DATA Indication: SCCP notifies SCCP user that the expedited
data from peer end has been received.
N_DISCONNECT: Disconnection primitive, used in connection-oriented service for

disconnection. It includes N_DISCONNECT Request and N_DISCONNECT Indication.
z
N_DISCONNECT Request: SCCP user requests SCCP reject signaling

connection or disconnect the connection established.
N_DISCONNECT Indication: SCCP notifies SCCP user that the peer end rejects
the establishment of signaling connection or disconnects the connection
established.
N_RESET: Reset primitive, used in Class 3 protocol to transfer connection reset

message.
z
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)
SCCP management primitive
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
N-COORD Request: Originating user requests SCCP management allows service

interruption.
N-COORD Indication: SCCP management notifies originating user of the backup,

and the originating user enters service interruption.
N-COORD Response: Originating user backup owns sufficient resources to allow

the originating user entering service interruption.
N-COORD Acknowledgement: Notification to the originating user that it can enter

service interruption.
N_STATE: State primitive, used in SCCP management to transfer subsystem state

information. It includes N-STATE Request and N-STATE Indication.
z
N-STATE Request: Notification to SCCP management of the status of originating

user.
N-STATE Indication: Notification to related SCCP user of the status of a user.

3-10
Technical Manual
MSC Functions
N_PCSTATE: Signaling Point state primitive, used in SCCP management to inform

local subsystem of a certain Signaling Point state. It comprises one primitive:
N-PCSTATE Indication.
z
N-PCSTATE Indication: Indicating to user of the status of signaling point.
4)
MTP service primitive
MTP_TRANSFER: Transfer primitive, used for the data transfer between MTP and
SCCP. It includes MTP_TRANSFER Request and MTP_TRANSFER Indication.
z
MTP_TRANSFER Request: Used to transfer signaling message from SCCP to

MTP.
MTP_TRANSFER Indication: Used to transfer signaling message from MTP to

SCCP.
V. MTP management primitive

MTP management primitive: Used to send SPC and MTP status indication from MTP to
SCCP. It includes MTP_PAUSE Indication, MTP_RESUME Indication, MTP_STATUS
Indication and MTP_RESTART Indication.
z
MTP_PAUSE Indication: indicating SP fault.
MTP_RESUME Indication: indicating SP recovery.
MTP_STATUS Indication: Indicating to SCCP of the MTP services to specified

destination provided by MTP when partial capability is available (e.g. due to
congestion), or notifying MTP user of "unreachable" or "unavailable" cause of the
subscriber.
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.
VI. SCCP Message Structure

SI is the Service Indicator of a Message Signaling Unit (MSU). If SI of a message is
0011, it indicates that this message is an SCCP message and its content is in the
Signaling Information Field (SIF) of the MSU. The format is shown in Figure 3-5.
Route label includes Destination signaling Point Code (DPC), Originating Point Code
(OPC) and Signaling Link Selection code (SLS).
3-11
Technical Manual
MSC Functions
Route flag
Message type
Essential para. A
M
Essential para. I
Essential items with

fixed length
Para. M indicator
M
Para. P indicator
Optional items start indi.
Para. M length indicator
Para. M
Essential items with

changeable length
M
Para. P length indicator
Para. P
Para. name X
Para. X length indicator
Para. X
M
Para. name Z
Optional items
Para. Z length indicator

Para. Z
Optional parameters end
Figure 3-5 SCCP message format
VII. SCCP Policing

Based on MTP, the SCCP function of SS7 protocol is a specific application allowing
message to access a node. The addressing is based on Global Title (GT), i.e. translate
the GT into Destination signaling Point Code (DPC) and SSN (Global Title Translation).
According to those addresses and their combinations, SCCP prevents the
unauthorized messages from passing STP. This function is so-called SCCP Policing.
The shielding modes of SCCP Policing include the shielding of the calling address and
that of the called address. And each mode includes four shielding combinations based
on DPCSSN, GT, GTT and GT+GTT. Since each shielding mode can be used
independently, SCCP Policing function can provide 24 shielding combinations.
MSC will automatically discard the SCCP message meeting shielding conditions,
therefore, the operator can make statistics of the shielded SCCP messages by
registering relevant traffic measurement task.
3-12
Technical Manual
MSC Functions
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.
II. TCAP Functions

TCAP functions provided by M900/M1800 MSC/SSP/IP are:
z
SCCP-supported addressing mode.
Structured and unstructured dialogs in the connectionless service.
Simultaneous support for multiple TC users.
Support for dialog controlling PDU and user information transmission.
The background maintenance terminal provides friendly man-machine interfaces

for direct message tracing on communications between TC user and TCAP.
Support of multi-SP features.
3-13
Technical Manual
MSC Functions
III. TCAP Structure

To control operations and dialogs, TCAP is divided into two sub-layers: the Component
Sub-Layer (CSL) and the Transaction Sub-Layer (TSL). CSL mainly enables operation
management while TSL mainly performs transaction (dialog) management. The
hierarchical structure is shown in Figure 3-6.
TC users are connected with CSL through the TC primitive, and CSL is connected with
TSL through the TR primitive.
Application Process
TC user
TCAP service
T
TC primitives
CSL
C
A
P
TSL
Network service
N primitives
SCCP
MTP
Figure 3-6 TCAP hierarchical structure

The TSL performs the management of communication process between local TSL
users and remote TSL users. As Component Sub-Layer (CSL) is the only TC user,
communication dialogs between equivalent CSL users are corresponding to
transactions.
The basic unit in the dialog message that TSL sends is the component. CSL performs
the processing of dialog components and the control processing of dialog.
Dialog information includes one or multiple components (few have no components and
are used only for dialog control). Each component corresponds to the execution
request or the execution result of an operation and is labelled by different component
invoke IDs. By using invoke IDs; the simultaneous execution of multiple operation
components of the same or different kind can be controlled. The definitions of
operations are labelled by specific operation codes and parameters and are defined by
TC users.
3-14
Technical Manual
MSC Functions
The CSL performs the component processing through TC component primitives. It

requests for the component related to a dialog identifier in dialog mode, then embeds
the component into the dialog & the dialog control part and sends it to the peer TCAP
through TR primitive. From above processing, it can be noted that a Component
Sub-Layer is divided into component processing and dialog processing.
TCAP message consists of a single-structured information unit, which comprises the
transaction processing part, CSL part and the optional dialog control part containing
context & user information. The coding principle of TCAP messages is based on ITU-T
X.208 and X.209 Recommendations. Information structure can be embedded with
basic information featuring high flexibility and openness. Contents of each unit can be a
value (basic mode) or one or multiple information units (structured mode).
The basic information unit comprises three parts: label, length and contents. The label
field is used to distinguish different information elements and it determines the
explanation to contents field. The length field indicates the 8-digit group number of the
content field. Contents can be a value (original mode) or one or multiple basic
information units (combined mode). The meaning of the code is as follows:
z
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.
IV. Signaling Process of TCAP

TCAP is adopted to provide unified support for the information interworking of
applications. The Signaling Process of TCAP is the procedure of processing and
control on operations & dialogs (transaction) by the Component Sub-Layer (CSL) &
Transaction Sub-Layer (TSL).
The TCAP signaling protocol is based on ITU-T X.219 and X.229 Recommendations
(ROSE, Remote Operation Service Element). In principle, TCAP can be supported by
any network layer services and in the SS7 network; it is supported by the
connectionless network services composed by SCCP and MTP.
TCAP procedure is divided into component sub-layer procedure and transaction
sub-layer procedure. The component sub-layer procedure provides a TC-user with the
capability of invoking remote operations and receiving replies. The component
sub-layer also receives dialogue control information and user information from a
TC-user and generates dialogue control APDUs as appropriate. It uses transaction
sub-layer capabilities for transaction control, which is the ability to carry a sequence of
components and, optionally, a dialogue portion, in transaction sub-layer messages
over an end-to-end connection between two TC-users. The transaction sub-layer
procedure provides end-to-end connection between two TC users. The transaction
processing ID identifies transaction processing. Local transaction processing ID is
assigned at each end and is exchanged at the transaction processing part.
3-15
Technical Manual
MSC Functions
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
Figure 3-7 TCAP signaling interworking in a mobile 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
MSC Functions
SCP
J
D
HLR
EIR
MSC
F
E
VLR
VLR
B
Gs
MSC
SGSN
EIR: Equipment Identifying Register


Figure 3-8 MAP-supported interfaces in the GSM network
II. MAP Functions

In M900/M1800 MSC/SSP/IP, the MAP message processing module is strictly
designed according to GSM 0902 specification. It provides all basic functions regulated
by the specification, including:
z
Version negotiation function.
Mobility management, including the mobility management of GSM subscribers

and GPRS subscribers.
Subscription data management, including management on basic service

subscription data and CAMEL subscription data.
Error restoration, including data restoration and HLR restart announcement.
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).
Handover control, including basic handover and subsequent handover.
Supplementary
services,
including
call-related
and
non-call
related
supplementary services.
z
Short message, including mobile originated and mobile terminated short

messages.
III. MAP message structure

In the Signaling System No.7, MAP messages are transmitted as the TCAP message
component part. The coding of the MAP message adopts the ASN1 format.
The MAP service message types correspond to the operation codes in TCAP
components. In the message transfer process, each message corresponds to an
3-17
Technical Manual
MSC Functions
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
Figure 3-9 Position of MAP in the SS7 protocol stack
MTP message
SCCP message
TCAP message
MAP message
Figure 3-10 Position of MAP in the link message
IV. MAP operations

MAP of M900/M1800 MSC/SSP/IP supports the operations specified in GSM 09.02
and listed in Table 3-1.
Table 3-1 Operations supported by MAP
Code
Operation
Purpose
0x02
UpdateLocation
Used by VLR to initiate the location update process to HLR in case of

inter-VLR location update or subscriber data unconfirmed by HLR.
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
MSC Functions
Code
Operation
Purpose
0x07
InsertSubscriber
Data
Used by HLR to insert the subscription data during location update and
subscriber data modifications.
0x08
DeleteSubscrib
erData
Used by HLR to independently delete the subscription data in VLR when

the operator deletes subscriber data.
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
Used for the registration of call forwarding supplementary services.
0x0B
EraseSS
Used for the deletion of call forwarding supplementary services.
0x0C
ActiveSS
Used for the activation of call forwarding, call barring and CW

0x0D
DeactiveSS
Used for the deactivation of call forwarding, call barring and CW

0x0E
InterrogateSS
Used for the interrogation of line identification, call forwarding, call barring
and CW supplementary services.
0x11
RegisterPasswo
rd
Used to modify the password for barring supplementary service

operations.
0x12
GetPassword
Used to activate/deactivate barring supplementary services and to get the

user password when modifying the barring password.
0x13
ProcessUnstruc
tureSS-Data
Used for Phase1 mobile originating unstructured supplementary service.
0x16
SendRoutingInf
ormation
Used by GMSC to get the subscriber location information from HLR,

including roaming number and forwarded-to number, when the subscriber
is called.
0x1C
PerformHandov
er
Used for the Phase1 handover request.
0x1D
SendEndSignal
Used for handover termination.
0x1E
PerformSubseq
uentHandover
Used for the Phase1 subsequent handover request.
0x21
ProcessAccess
Signaling
Used by MSCb to transparently transmit access information to MSCa.
0x22
ForwardAccess
Signaling
Used by MSCa to transparently transmit access information to MSCb.
0x25
Reset
Used to inform VLR about the location update originated to HLR when the
subscriber is active.
0x2B
checkIMEI
Used to check IMEI status from EIR.
0x2C
mt-forwardSM
PHASE2+ operation, used for mobile terminated short message.
0x2E
mo-forwardSM
PHASE2+ operation, used for mobile originated short

message.
3-19
Technical Manual
MSC Functions
Code
Operation
Purpose
0x30
NoteSubscriber
Present
Phase1 operation used for the announcement about short message

subscriber location updates or memory availability.
0x37
sendIdentificatio
n
Used to get the IMSI and authentication set from the original HLR.
0x38
SendAuthentica
tionInfo
Used by VLR to get the authentication set from HLR.
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
To get the subscriber IMSI via MSISDN.
0x3B
ProcessUnstruc
turedSS-Rreque
st
Used for the mobile originating unstructured supplementary service

processing.
0x3C
UnstructuredSS
-Rrequest
Used for the network originating unstructured supplementary service

processing.
0x3D
UnstructuredSS
-Notify
Used for the network originating unstructured supplementary service

announcement.
0x42
ReadyForSM
Used for the announcement of short message subscriber location update

or memory availability.
0x43
PurgeMS
Used by VLR to report to the HLR about its subscriber deletion operation.
0x44
PrepareHandov
er
Used for the non-Phase1 handover request.
0x45
PrepareSubseq
uentHandover
Used for the non-Phase1 subsequent handover request.
0x46
ProvideSubscrib
erInfo
Used by HLR to get the subscriber location information and status

information data from VLR.
According to specifications of relative protocols, MAP operations can be classified into

four types:
z
Type-1 operations: Confirmation will be returned whether the operation is

successful or not. The result is returned if the operation is successful. Otherwise,
an error is returned.
Type-2 operations: Confirmation will be returned only when the operation fails.
Type-3 operations: Confirmation will be returned only when the operation is

successful.
Type-4 operations: No confirmation needs to be returned for the operation.
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
MSC Functions
are regarded as failed. For Type-2 or Type-4 operations, the operations are regarded
as successful.
V. Typical process of MAP

The location update and send routing information processes are the most basic
functions supported by MAP for inter-network roaming of mobile subscribers. Other
functions include supplementary service processing, short message and handover
proceeding.
1)
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
When MSC/SSP/IP receives the location update request originated by the

subscriber, if VLR can not distinguish TMSI and the previous location information
attached in the location update request message is a location area near VLR, the
local VLR will originate the process to get subscriber identity and authentication
information from PVLR.
When MSC/SSP/IP receives the subscriber location update request, if no

available authentication information is found, it will send request to HLR for
authentication information.
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.
HLR sends the subscriber data to VLR.
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
MS
MSC Functions
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
Figure 3-11 Location update procedure

2)
Send Routing Information (SRI)
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
MSC Functions
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
Figure 3-12 SRI procedure
VI. Supplementary service operations

MAP operations related with supplementary service processing include activation,
deactivation, registration, cancellation and interrogation. Supplementary services
include line identification, Call Forwarding (CF), call barring and call hold.
VII. Password registration

Password refers to the default password assigned to the user for barring
supplementary services when the user opens the account. The user can change the
password through password registration process. When changing the password, old
password and new password should be input. Confirmation is required for the new
password.
VIII. Handover processing

Handover includes intra-MSC handover and inter-MSC handover. MAP support is
needed for inter-MSC handover. The MAP handover process comprises basic
handover, subsequent handover to original MSC, and the subsequent handover to the
third-party MSC. The MSC in call setup is the main control MSC, which will not be
released during handover process and will take care of charging information.
3-23
Technical Manual
MSC Functions
IX. HLR restart

After HLR is restarted due to any failure, information will be provided to the VLR
containing all home mobile subscribers. This is to facilitate the confirmation of
subscriber data from VLR to HLR when the concerned subscriber is in the active state.
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.
XI. MAP Policing

To avoid the unauthorized use of network resources and illegal modification of data,
MAP will prevent the unauthorized operations from being executed according to the
combination of the original address information and the content of the MAP operation.
This function is so-called MAP Policing.
The setup of the original address to be shielded by MAP Policing includes setting OPC
and setting GT of the original address. If the type of the address cannot be determined,
both the OPC and the GT of the same network can be set.
The setup of the operation content to be shielded by MAP Policing includes the setting
of MAP version, operation code, target subsystem and the combination of them.
MSC will automatically discard the MAP operations meeting the shielding conditions
and report event alarm.
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
MSC Functions
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.
II. DTAP messages

DTAP messages can be classified into Mobility Management (MM) and Call Control
(CC) messages.
MM messages include authentication, CM service request, identification request, IMSI
detach, location update, MM status and TMSI re-allocation related messages.
CC messages include alerting, call proceeding, connection, setup, modification,
release, disconnection, announcement, status query and starting DTMF related
messages.
III. BSSMAP messages

BSSMAP messages include connectionless and connection-oriented messages.
1)
Connectionless messages include block/unblock, handover, resources, reset, and

paging.
Block/unblock messages include block, block acknowledgement, unblock and

unblock acknowledgement messages. Group-block/unblock messages include
group-block, group-block acknowledgement, group-unblock and group-unblock
acknowledgement messages.
Handover messages include handover candidate query and handover candidate

query response messages.
Resources messages include resources request and resources indication

messages.
Resetting messages include reset and reset-confirmed messages.
2)
Connection-oriented messages include assignment, handover, purge and

ciphering messages.
Assignment messages include assignment request, assignment-completed and

assignment failure messages.
Handover messages include handover request, handover request confirmed,

handover command, handover-completed and handover failure messages.
Purge messages include purge request, purge command and purge-completed

messages.
Ciphering messages include cipher mode command and cipher mode command
completed.
3-25
Technical Manual
MSC Functions
IV. BSSAP Functions

BSSAP protocol enables its functions by SCCP connection-oriented mode or
connectionless mode.
There are two cases of connection setup, i.e. new call setup and handover.
For call setup, an MS sends "access request" message on RACH. BSS assigns a
dedicated radio channel (DCCH or TCH) to MS. After layer-2 connection is established
on the SDCCH (or FACCH) channel, BSS starts the connection setup to facilitate the
exchange of service-related information between MS and the network.
If MSC decides to execute an external handover (the target BSS might be the original
BSS), it must reserve the new DCCH or TCH from the target BSS. MSC will start the
connection setup.
Via the connection-oriented or connectionless messages, BSSAP protocol mainly
enables the following functional processes:
Assign
The purpose of assign is to ensure the correct assignment or re-assignment of
dedicated radio resources to MS. The initial MS random access and "immediate
assignment" to a DCCH is processed by BSS itself and is not controlled by MSC.
Block /unblock circuit
In the assignment process, MSC selects the suitable terrestrial circuit. If BSS finds
some terrestrial circuits unusable, it will inform MSC. The block/unblock process
enables the function.
Resource indication
The purpose of resource indication is to inform MSC that:
z
Number of available idle radio resources, which can be used in the traffic channel
in BSS.
Total available radio resources (idle or assigned).
This information is used by MSC when deciding an external handover.

Reset
The purpose of reset is to initialize the failed BSS or MSC. For example, if BSS is failed
and all reference information about processing is lost, BSS will send the "reset"
message to MSC to release all affected calls, delete affected reference information and
set all circuits related with BSS to idle.
In case of partial failure in MSC or BSS, the clear program can be used to clear the
affected part.
3-26
Technical Manual
MSC Functions
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
BSS detects a radio cause that demands a handover.
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
The "handover command" message from MSC is received.
The "reset" message is received.
All communications with MS are interrupted and the processing is abandoned.
The processing is finished, such as call release.
Handover resources allocation

Handover resources allocation enables MSC to request for resources from BSS
according to handover requirement. The target BSS will reserve the resources and
waits for the MS to access that assigned channel.
Handover process
MSC prompts MS to access the dedicated radio resources of another cell. In executing
the handover, the original dedicated radio resources and terrestrial resources will not
be released until MSC sends the "release command" message or resetting occurs.
Release of resources
After a processing is finished, MSC sends a "release command" to prompt BSS to
release radio resources. BSS receives the command and starts the release program on
the radio interface. Then, it sets the allocated terrestrial circuit in the idle state and
returns a release completion message to MSC. MSC will then release the terrestrial
resources of the local end.
If the resources are to be released because of BSS, BSS will send a "release request"
to inform MSC to start the release process, releasing the terrestrial and radio resources
in correspondence to MSC and BSS.
Paging
Paging to MS is transmitted by BSSMAP via the SCCP connectionless service. When
BSS receives the "paging response" message on the radio channel interface, it will
establish a SCCP connection to MSC. The paging response message is loaded in the
"complete L3 information" message in BSSMAP and will be transmitted to MSC via the
3-27
Technical Manual
MSC Functions
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.
II. Structure of TUP message

In SS7, all telephone signaling is transmitted through telephone signaling message
units. In its basic format, only the Signaling Information Field (SIF) is related to the
3-28
Technical Manual
MSC Functions
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
First sent bits
n2
Header code
Signal
information H1
8n
H0
Label
Figure 3-13 Structure of the telephone signaling message

1)
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
First sent bits
Figure 3-14 Label of TUP message

The label structure requires a unique code for each telephone switch, which functions
as a Signaling Point so as to distinguish the Switches/Signaling Points in a network.
M900/M1800 MSC/SSP/IP supports the 24 and 14 digit destination signaling point
code. It also supports the function of multiple DSPs, that is, the local office can be
multiple virtual OPCs. This function brings about diversified inter-office connection and
configuration which lays the basis for large capacity of the system.
3-29
Technical Manual
MSC Functions
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
Initial address message
0001
0010
IAI
Initial address message with additional information
0001
0011
SAM
Subsequent address message
0001
0100
SAO
Subsequent address message with one signal
0010
0001
GSM
General forward set-up information message
0010
0011
COT
Continuity signal
0010
0100
CCF
Continuity check failure message
0011
0001
GRQ
General request message
0010
0001
ACM
Address complete message
0100
0010
CHG
Charging message
0101
0001
SEC
Switching-equipment-congestion signal
0101
0010
CGC
Circuit group congestion signal
0101
0100
ADI
Address incomplete signal
0101
0101
CFL
Call-failure signal
0101
0110
SSB
0101
0111
UNN
Unallocated number signal
0101
1000
LOS
Line out-of-service signal
0101
1001
SST
Send-special-information tone signal
3-30
Technical Manual
MSC Functions
H0
H1
Message Type
Remarks
0101
1010
ACB
Access barred signal
0101
1011
DPN
Digital path not provided signal
0101
1100
MPR
Misdialled trunk prefix
0101
1111
EUM
Extended unsuccessful backward set-up

information message
0110
0000
ANU
Answer signal, unqualified
0110
0001
ANC
Answer signal, charge
0110
0010
ANN
Answer signal, no charge
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
Caller On-hook Message
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
Maintenance oriented group blocking message
1000
0010
MBA
Maintenance oriented group

blocking-acknowledgement message
1000
0011
MGU
Maintenance oriented group unblocking message
1000
0100
MUA
Maintenance oriented group

unblocking-acknowledgement message
1000
0101
HGB
Hardware failure oriented group blocking message
1000
0110
HBA
Hardware failure oriented group

blocking-acknowledgement message
1000
0111
HGU
Hardware failure oriented group unblocking

message
1000
1000
HUA
Hardware failure oriented group

unblocking-acknowledgement message
1000
1001
GRS
Circuit group reset message
3-31
Technical Manual
MSC Functions
H0
1000
H1
1010
Message Type
GRA
Remarks
Circuit group reset-acknowledgement message
III. Basic TUP Signaling Flow

1)
Setup of calls to idle mobile subscriber
The call proceeding process is shown in Figure 3-15.
LS
GMSC
VMSC
IAM
GRQ
GSM
IAI
ACM
ACM
Ring-back tone
ANC
ANC
Conversation
CBK
CBK
CLF
Called party clears
CLF
RLG
RLG
Calling party clears

CLF
CLF
RLG
RLG
LS: Fixed Local Switch

VMSC: Visited MSC
GMSC: Gateway MSC
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
MSC Functions
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)
Unsuccessful call attempt
The call proceeding process is shown in Figure 3-16.

LS
GMSC
VMSC
IAI
IAI
SSB, LOS, SST
SSB , LOS, SST
VMSC
Reject
call
CLF
CLF
RLG
RLG
UNN
CLF
RLG
GMSC
Reject
call
LS: Fixed Local Switch

VMSC: Visited MSC
GMSC: Gateway MSC
Figure 3-16 Unsuccessful call attempt

LS (Local Switch) is ready to set up calls, while the VMSC finds connection to the called
subscriber is unavailable due to the called subscriber busy, BSS failure (causing
paging to the subscriber impossible) or other reasons. The VMSC then sends SSB,
LOS or SST message to notify the unsuccessful connection. The LS clears the
inter-office trunk circuits and confirms via RLG. Some failure causes are known at
GMSC (such as unallocated number), so the GMSC directly sends backward failure
message to reject the call.
IV. TUP signaling multi-nation adaptation

Besides providing TUP signaling interface compliant with ITU-T recommendations,
M900/M1800 MSC/SSP/IP is also compatible with the national TUP specifications of
Thailand and Brazil, etc. It has the following features:
z
Controlling the duration of each timer in TUP signaling via data configuration.
3-33
Technical Manual
z
MSC Functions
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
Calling Line Identification Presentation/Restriction) (CLIP/CLIR)
Connected Line Identification Restriction/Presentation (COLR/COLP)
Call Forwarding Unconditional/on Busy/on No Reply/on subscriber Not Reachable

(CFU/CFB/CFNRy/CFNRc)
Call Hold (HOLD)
Call Waiting (CW)
User-to-User Signaling (UUS)
Three Party Service (3PTY)
ISUP also supports multi-SP function.

All ISUP messages are transferred through MTP. SCCP provides ISUP with the support
for peer-to-peer signaling service.
II. Structure and types of ISUP message

An ISUP message is transmitted in the signaling link in the form of Message Signaling
Unit (MSU). The ordinary form of the ISUP message is similar to that of the SCCP
message, whose length can be variable. Therefore, the ISUP message can carry
multiple parameters and is very flexible.
Types of ISUP messages are listed in Table 3-3.
3-34
Technical Manual
MSC Functions
Table 3-3 ISUP message types

Message Type
Code
Address complete message (ACM)
00000110
Answer signal, no charge (ANN)
00001001
Block (BLO)
00010011
Block-acknowledgement (BLA)
00010101
Call modification completed (CMC)
00011101
Call modification request (CMR)
00011100
Call modification rejected (CMRJ)
00011110
Call progress (CPG)
00101100
Charging (CRG)
00110001
Circuit group block (CGB)
00011000
Circuit group block acknowledgement (CGBA)
00011010
Circuit group reset (GRS)
00010111
Circuit group reset acknowledgement (GRA)
00101001
Circuit group unblock (CGU)
00011001
Circuit group unblock acknowledgement (CGUA)
00011011
Circuit group query(CQM)
00101010
Circuit group query response (CQR)
00101011
Confusion message (CFN)
00101111
Connect (CON)
00000111
Continuity signal (COT)
00000101
Continuity check request (CCR)
00010001
Delayed release (DRS)
00100111
Feature acceptance (FAA)
00100000
Feature (FAC)
00110011
Feature rejection (FRJ)
00100001
Feature request (FAR)
00011111
Forward transfer (FOT)
00001000
Identification request (IDR)
00110110
Identification response (IRS)
00110111
Information (INF)
00000100
Information request (INR)
00000011
3-35
Technical Manual
MSC Functions
Message Type
Code
Initial address message (IAM)
00000001
Loop-back acknowledgement (LPA)
00100100
Network resources management (NRM)
00110010
Overload message (OLM)
00110000
Pass (PAM)
0010100
Release (REL)
00001100
Release completed (RLC)
00010000
Reset circuit signal (RSC)
00010010
Restore (RES)
00001110
Segment message (SGM)
00111000
Subsequent address message (SAM)
00000010
Suspend (SUS)
00001101
Unblock (UBL)
00010100
Unblock acknowledgement (UBA)
00010110
Unallocated CIC (UCIC)
00101110
User part availability (UPA)
00110101
User part test (UPT)
00110100
User to user signaling (USR)
00101101
III. Basic ISUP Signaling Flow

Figure 3-17 illustrates the procedure of call setup between mobile subscribers and
fixed subscribers. A complete call setup procedure includes the ISUP signaling used
between exchanges in the figure and its DSS1 signaling between exchanges and
subscribers. DSS1 signaling will be described in detail in the following section.
3-36
Technical Manual
MSC Functions
MSC
GMSC
IAM
LS
IAM
ACM
ACM
ANM
ANM
Conversation
REL
REL
RLC
RLC
REL
REL
Called party clears
RLC
RLC
Figure 3-17 Basic call procedure using ISUP

z
Call setup process
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
Call release process
3-37
Technical Manual
MSC Functions
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.
IV. IUSP multi-nation adaptation

Besides providing ISUP signaling interface compliant with ITU-T recommendations,
M900/M1800 MSC/SSP/IP is also compatible with the national ISUP specifications of
the countries and regions, such as Russia, Thailand, Algeria, India, Indonesia and
Hong Kong, etc. It has the following features:
z
Transcoding various ISUP message codes and adjusting the parameters

contained in messages via data configuration.
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.2.1 Introduction to ISDN Network

ISDN network provides multiple functions including circuit switching, packet switching,
non-switching connection and common channel signaling.
3-38
Technical Manual
MSC Functions
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
TE: Terminal Equipment
Figure 3-18 An ISDN network

ISUP of the Signaling System No.7 regulates the control information switching in the
ISDN network (between ISDN switches). DSS1 regulates the control information of the
ISDN user-network interface.
M900/M1800 MSC/SSP/IP can serve as the ISDN network switching equipment to
support ISDN network and subscribers, as shown in Figure 3-19.
All ISDN signaling adopts the Common Channel Signaling. Therefore, independent
signaling channels exist in the user-network interface and inside the network and they
are completely isolated from user information channels.
3-39
Technical Manual
MSC Functions
SS7 (ISUP)
DSS1
User terminal
DSS1
MSC
MSC
SS7 (ISUP)
PABX
SS7 (ISUP)
ISDN switching equipment
Speech/trunk channel
Signaling channel
Figure 3-19 M900/M1800 MSC support of ISDN network
3.2.2 Structure of DSS1

ISDN network corresponds to the OSI (Open System Interworking) 7-layer model.
DSS1 system comprises three layers of protocols: Physical layer, Link layer and
Network layer. These three layers correspond to the lower 3 layers of OSI, as shown in
Figure 3-20.
Layer 4-7
Layer 3
Network layer
Layer 2
Link layer
Layer 1
Physical layer
OSI Mode
DSS1 signaling system
Figure 3-20 Correspondence between DSS1 and OSI
3.2.3 Physical Layer

M900/M1800 MSC/SSP/IP supports the PRI interface (Primary Rate Interface), i.e.
30B+D (30 B-channels and 1 D-channel).
B-channel: 64 kbit/s user information channel fully compliant with G.711 and G.722
Recommendations. It enables circuit switching, packet switching and Semi-Permanent
Connection.
3-40
Technical Manual
MSC Functions
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.
3.2.4 Data Link Layer

LAPD is the data link layer protocol of D-channel stipulated in Q.920/ Q.921
Recommendations. It defines the information switching via D-channel, on layer 2 of the
user-network interface. The switching can be implemented between TE (Terminal
Equipment) and NT2 (Network Termination 2), or between NT2 and the switch, or
between TE and the switch.
According to the features of S-interface and T-interface, layer-2 protocol of D-channel
satisfies the following two requirements:
Firstly, the protocol supports the working of multiple terminals on the interface, as
multiple terminals in ISDN access the network via the same interface. The terminals
can freely access or disconnect without prior registration in the network. Establishing
contact with the network is the only requirement before usage. To implement control on
multiple terminals, LAPD allows multiple independent links on the same D-channel. A
set of management measures for terminal identifiers is also provided.
Secondly, the protocol also supports the access of multiple layer-3 entities. In addition
to the control signaling, packet data or remote control/measurement signaling can be
transmitted on the D-channel. Different types of data are processed by different entities
in layer 3. To ensure that the entities get layer-2 services, LAPD sets up multiple SAPs
(Service Access Point) on layer-2 and layer-3 interfaces. Each SAP is assigned with a
unique identifier to enable the multi-channel multiplexing of several terminals and
various services.
I. Major Functions of LAPD

LAPD provides the following major functions:
3-41
Technical Manual
z
MSC Functions
Partition, synchronization and transparent transmission of frame: Information to

be transmitted on the D-channel is converted into frames according to a certain
format. Synchronization between receiving and transmitting is thereby enabled.
Specific measures are adopted to ensure the transparent transmission of
information.
Multiplexing of multiple data links on the same D-channel: It is allowed to establish

multiple data links on the same D-channel and to enable the independent working
of the links.
Consistency of frame receiving and sending sequences are maintained.
The transmission error, format error and operation error on the data link are
checked.
The transmission error is corrected by adopting the re-transmission mode.
Uncorrectable errors are intimated to the management entity.
Flow control is implemented.
Activation management is carried out on the physical layer.
The working speed between the receiver and the transmitter is coordinated.
II. Transfer Modes of LAPD Information

z
Unacknowledged information transfer
In this mode, frames carrying user data are not numbered and no acknowledgement is
needed after the transfer.
z
Acknowledged information transfer
This is a connection-oriented information transfer mode. Before transmitting data, the

logical connection between two layer-2 entities is established. After the data is
transferred, the logical connection should be released.
3.2.5 Network Layer

User-network interface layer-3 (network layer) provides the call control function. The
call control protocol is stipulated in Q.930/ Q.931, which regulates the process of
establishing connection on B-channel and the process of providing the user-to-user
signaling service on D-channel.
I. ISDN Call Control Function

The ISDN call control function provided by the network layer includes the following
aspects:
z
Processes layer-3 messages and communicates with call control & resource
management entities of the exchange to implement call handling.
Communicates with the adjacent layers via primitives.
Necessary resource management is carried out (channel, call reference value,

etc.).
3-42
Technical Manual
z
MSC Functions
Provides basic services and supplementary service performances, as required by

the user.
II. Message Structure

To enable the control on calls, layer-3 entities at the subscriber and the network sides
execute dialogues, which are achieved by exchanging messages on the D-channel.
Messages are data blocks of different lengths. They are generated & processed in
layer-3 and transmitted in the UI or I frame data fields of layer-2.
Q.931 Recommendation regulates the general format of the message. The message
comprises several octets. Each message includes a common part and some
information units. The common part comprises 3 sections, whose format is the same
for all messages, as shown in Figure 3-21.
Essential & optional

information units
Common part
Protocol discriminator
0
Call reference length
1 Byte
1 Byte
Call reference
Max. 2 bytes
Message type
1 Byte
Information unit
Information unit
.
.
.
Figure 3-21 Normal format of message

Protocol discriminator is used to separate the call control messages from other
messages, in the user-network interface. Its length is 1 octet.
Call reference is used to identify a call in B-channel.
Message type is used to distinguish the types of messages. The length is 1 octet.
Q.931 Recommendation defines a lot of message types, which have various functions
and contain different information units.
III. ISDN Circuit-Switched Call

Figure 3-22 shows a simple circuit-switched call process and the process of
transmitting call control information in the user-network interface.
3-43
Technical Manual
MSC Functions
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
Figure 3-22 Processing of circuit switched call

The subscriber call request is sent via the SETUP message, which is transmitted on an
established data link (all the following messages are sent over this link).
When the SETUP message reaches the network side, layer-3 entity of the network side
checks the completeness of the called address. If the address is complete, the CALL
PROCEEDING message is used to inform the subscriber to wait. If the address is
incomplete, the SETUP ACK message is sent to the subscriber, seeking further
information.
After the network side receives enough address information, it immediately informs the
exchange to implement routing and resource allocation. In the example shown in
Figure 3-22, the call is connected to the called subscriber via one more switch and the
originating exchange will send the call-related message to the terminating exchange
through SS7 Signaling.
When the terminating exchange receives this message, it sends the SETUP message
to the called subscriber. This message includes all the information sent by the
originating terminal (including bearer service capacity, terminal low-layer feature,
high-layer feature and end-to-end information) and the user information channel
selected by the terminating exchange.
On the basic interface of the called subscriber, the SETUP message is sent via the
broadcast data link (TEI=127), all terminals connected with the passive bus can receive
the SETUP message and implement compatibility check to see if they satisfy the call
3-44
Technical Manual
MSC Functions
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
MSC Functions
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
HDLC c om m unic atio n

Bus com m .
HDLC c om m unic atio n
Active GSPC
Figure 3-23 Access of CAS

M900/M1800 MSC/SSP/IP CAS system:
z
Supports E1
Supports bi-directional trunk
Provides three standard trunk hunting modes-maximum sequential, minimum

sequential, master/slave
Provides semi-permanent connection
Provides interface for external echo canceller
Provides control over satellite circuit selection
Provides international/national signaling processing
Provides two tandem modes: transfer and end-to-end
Supports Malicious Call Identification (MCI)
Supports Calling Line Identification Presentation (CLIP)
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.3.2 Line Signaling

The digital type of CAS line signaling uses the first two bits of the four bits provided by
the PCM TS16 for each speech channel. Under normal circumstances, signaling codes
on the PCM are as shown in Table 3-4.
3-46
Technical Manual
MSC Functions
Table 3-4 Signaling codes on PCM

Signaling codes
Circuit state
Forward
Backward
Free/release
Seizure
Seizure acknowledgment
Answer
Clear backward
Clear forward
Block
3.3.3 Register Signaling

Each register signal consists of 2 out of 6 in-band frequencies. There are forward and
backward signals. The forward signals are categorized into the group I and group II;
and the backward signals are categorized into group A and group B. Meanings of
signals are as shown in Table 3-5, Table 3-6, Table 3-7 and Table 3-8.
Table 3-5 Group I forward signals
Combina
tion
Signal
symbol
I-1
Language digit: French
Digit 1
I-2
Language digit: English
Digit 2
I-3
Language digit: German
Digit 3
I-4
Language digit: Russian
Digit 4
I-5
Language digit: Spanish
Digit 5
I-6
Reserved (language digit)
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
(c) Column: when

the international link
terminates at the
destination country,
signals
in
this
column would be
sent as the first
signal.
Technical Manual
MSC Functions
Combina
tion
Signal
symbol
11
Meaning of signal
c
12
Country code flag requiring

outgoing echo canceller
I-11
Country code flag, not

requiring the echo canceller
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)
Test call flag
2) Not contains
satellite circuit
14
Country code flag, the

outgoing echo suppressor
inserted
I-14
1) Requires the
incoming echo
canceller
(c) Column: when

the international link
terminates at a
international transit
exchange, signals in
this column would be
sent as the first
signal on the link.
(d) Column: signals
on the international
link other than those
sent as first digit.
2)
Contains
satellite circuits.
1) End of pulse
15
I-15
Unused signal
2)
End
identification
of
Table 3-6 Group II forward signals

Combination
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
These signals only apply to

national calls.
Technical Manual
MSC Functions
Combination
Signal symbol
Meaning of signal
Remark
II-7
Subscriber (or operator without

the CF feature)
II-8
Data transmission
II-9
Preferential subscriber
10
II-10
Operator with the CF feature
11
II-11
12
II-12
13
II-13
14
II-14
15
II-15
These signals apply

international calls.
Reserved for national use
Table 3-7 Group A backward signals

Combinatio
n
Signal symbol
A-1
Request next digit (n+1)
A-2
Request the digit before the last digit (n-1)
A-3
Address complete, turns to group B
A-4
National network congestion
A-5
Request calling subscriber category
A-6
Address complete, charge, enters into conversation state
A-7
Request the digit before the last 2 digit (n-2)
A-8
Request the digit before the last 3 digit (n-3)
A-9
10
A-10
11
A-11
Request country code flag
12
A-12
Request language or discrimination digit
13
A-13
Request circuit type
14
A-14
Request information on the provision of echo canceller
15
A-15
International exchange or its outgoing trunk congestion
Meaning of signal
3-49
to
Technical Manual
MSC Functions
Table 3-8 Group B backward signals

Combination
Signal symbol
Meaning of signal
B-1
B-2
Send special information tone
B-3
Subscriber busy
B-4
Congestion (congestion after the transit from group A

signals to group B signals)
B-5
Unallocated number
B-6
Subscriber free, charge
B-7
Subscriber free, no charge
B-8
Subscriber line fault
B-9
10
B-10
11
B-11
12
B-12
13
B-13
14
B-14
15
B-15
3.3.4 Signaling Procedure

Figure 3-24 illustrates the CAS procedure of a local call.
3-50
Technical Manual
MSC Functions
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
Figure 3-24 Signaling process of local call

In this figure, the called number is of 7 digits, PRQ is the office number. and ABCD is
user number.
From the figure, it can be seen that line signals are sent section by section. The forward
office in each section sends register signals only after it receives seizure
acknowledgement signals from the backward office.
Release signals are also transferred section by section.
Register signals are transmitted in peer-to-peer mode.
The connection by transit exchange only needs office number and the connection by
terminating exchange only needs user number. After PQR is received, the transit
3-51
Technical Manual
MSC Functions
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.
3.3.5 CAS Multi-nation Adaptation

Besides providing CAS signaling interface compliant with ITU-T recommendations,
M900/M1800 MSC/SSP/IP is also compatible with the national CAS specifications of
Russia, Thailand and India, etc. It has the following features:
z
Implementing adaptation of CAS line signaling message via data configuration.
Implementing adaptation of CAS register signaling message via data

configuration.
Controlling the duration of the timer in CAS signaling via data configuration.
Implementing the conversion between released cause value and backward

register signal via data configuration.
3-52
Technical Manual
MSC Functions
Chapter 4 Mobile Service Procedures

The call control module, signaling processing module, intelligent processing module
and relevant software of M900/M1800 MSC/SSP/IP coordinate to provide basic service,
Supplementary Service (SS), intelligent service and other Value Added Services (VAS).
The following introduces the incoming/outgoing call procedures of M900/M1800
MSC/SSP/IP serving as GMSC and the basic mobile service procedure of
M900/M1800 MSC/SSP/IP serving as VMSC. For the intelligent call procedure, refer to
WIN Application Protocols in module 5 SSP Functions of this manual.
4.1 MOC and MTC Processing Procedure

4.1.1 MOC Processing Procedure
The MOC processing procedure refers to the signaling processing procedure of
M900/M1800 MSC/SSP/IP (as VMSC) on the calling subscriber when a mobile
subscriber originates a call to another mobile subscriber or a PSTN subscriber, as
shown in Figure 4-1 below.
MS
MSC
BSS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Figure 4-1 MOC processing procedure

1)
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
2)
MSC Functions
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)
Channel assignment (assign cmd): MSC starts the assignment of A-interface

circuits and radio channels.
4)
Assignment complete (assign cmp): MSC receives the channel assignment

complete message. The speech channel for the calling subscriber is set up.
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)
Connection acknowledgement (connect_ack): The calling mobile subscriber

responds with the connect-acknowledgement message, and the calling subscriber
enters the conversation state.
After the call is finished, a Mobile Originated Call (MOC) bill will be generated.
4.1.2 MTC Processing Procedure

The MTC processing procedure refers to the signaling processing procedure of the
local MSC (as VMSC) on the called subscriber when another mobile subscriber or a
PSTN subscriber calls the mobile subscriber.
Suppose that a mobile subscriber calls a mobile subscriber of local MSC. The called
number type received by MSC will be MSISDN. MSC will first request for the roaming
number from HLR. After HLR returns the roaming number (MSRN), MSC analyzes the
MSRN to figure out the Visited MSC (VMSC) where the called subscriber is located. As
the called mobile subscriber is in the local MSC, the local MSC is VMSC destined. The
local MSC will then request some information about the called subscriber, including the
IMSI/TMSI and the current location area information of the called subscriber. After VLR
returns this information to MSC, MSC will use them to page the mobile subscriber. The
MTC process after the paging is shown in Figure 4-2.
4-2
Technical Manual
MSC Functions
MS
BSS
MSC
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Figure 4-2 MTC processing procedure

1)
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)
Paging response (paging_rsp): The called MS sends the paging response

message.
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)
Channel assignment (assign_cmd): MSC starts the assignment of A-interface

circuits and radio channels for the called mobile subscribers.
6)
Assignment complete (assign_cmp): MSC receives the channel assignment

complete response message.
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
connect-acknowledgement message to the called mobile subscriber, and the

called mobile subscriber enters the conversation state.
After the call is finished, a Mobile Terminated Call (MTC) bill will be generated.
4-3
Technical Manual
MSC Functions
4.2 Office Direction Call Processing Procedure

4.2.1 Mobile Terminated Inter-office Call Processing Procedure
When a mobile subscriber calls a mobile subscriber of other exchanges, besides MOC
and MTC processing procedures, there is also an inter-office call processing procedure,
which is between the MSC of the calling subscriber and the MSC/VLR of the called
subscriber, as shown in Figure 4-3.
(2)
(1)
(4)
HLR
MSC
(3)
(5)
MSC /VLR
(6)
Figure 4-3 Mobile terminated inter-office call processing procedure

1)
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)
MSC/VLR assigns an MSRN and returns it to HLR.
4)
On receiving the MSRN returned by MSC/VLR, HLR sends to MSC a response

message regarding the route information request.
5)
MSC sends initial address message to MSC/VLR according to the MSRN in the
route information message.
6)
On completing the called party access, MSC/VLR returns address-complete

response to MSC.
When a fixed network subscriber calls a mobile subscriber, the above inter-office call
processing procedure will also occur to MSC.
4.2.2 Tandem Call

Acting as the GMSC between mobile network and fixed network, M900/M1800
MSC/SSP/IP has tandem function (which is usually known as call handling function of
calls from mobile subscriber to fixed subscriber), implementing call connection by
connecting the call to the right destination.
4-4
Technical Manual
MSC Functions
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
Figure 4-4 Tandem process of GMSC

1)
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)
GMSC completes the connection, and the subscribers are in communication

status.
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.
4.3 Handover Procedure

Note:
The handover procedure described below is for M900/M1800 MSC/SSP/IP serving as VMSC.
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
MSC Functions
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.
4.3.1 Intra-MSC Handover Procedure

Intra-MSC handover, or inter-BSS handover, refers to the process of a mobile
subscriber being handed over from a radio channel of the current BSS to that of
another BSS in the same MSC.
The whole handover process is controlled by one MSC. MSC needs to initiate a
handover request to the new BSS to get ready for the MS access. After the new BSS
responds to the handover request, MSC informs MS to make handover through the old
BSS. When MS successfully accesses to the new BSS, MSC sets up the new
connection.
Before the handover is completed, MSC should keep the original connection. In this
way, communications can be kept uninterrupted on the original connection in case of
MS handover failure. Only after the handover is completed, MSC will release the old
connection.
4.3.2 Basic Handover Procedure

Basic handover refers to the process to keep communications when the mobile
subscriber moves from the BSS coverage area of one MSC (MSC-A) to the BSS
coverage area of another MSC (MSC-B) during the communication process.
The implementation of basic handover requires the coordination of MSC-A and MSC-B.
MSC-A serves as the handover controlling party until the call is released.
As the controlling party, MSC-A should have basic information required for the
handover, which defines the handover origination, handover destination and mobile
class.
z
Originating location information
The location information about the current MS can be obtained from the Cell Global
Identity (CGI).
z
Destination location information
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
MSC Functions
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)
Figure 4-5 Signaling process of basic handover

1)
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)
BSS-B responses to handover request. MSC-B sends the handover request

response to MSC-A, including the handover number.
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)
MSC-A receives the address-complete message and instructs MS to make

handover via BSS-A.
4-7
Technical Manual
8)
MSC Functions
MS accesses BSS-B, which informs MSC-A through MSC-B of the successful MS

access.
9)
Channel is successfully established between MS and BSS-B. MSC-B informs

MSC-A that the handover is completed.
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.3.3 Subsequent Handover Procedure

Subsequent handover refers to the inter-MSC handover in the subsequent
communication process after the basic handover.
According to the handover destinations, subsequent handover is divided into two types:
z
Subsequent handover to controlling MSC
In subsequent handover to the controlling MSC, the handover destination is the

coverage area of the original MSC (MSC-A). The handover control process of the
controlling MSC does not require the control of inter-MSC trunk circuits, and the
handover signaling procedure is similar to that of the basic handover. After the
handover is completed, MSC-A will completely release MSC-B.
z
Subsequent handover to third-party MSC
In subsequent handover to the third-party MSC, the handover destination is the

coverage are of a third-party MSC (MSC-C). Subsequent handover is controlled by the
controlling MSC (MSC-A). The handover process is similar to that of basic handover.
After the handover is completed, MSC-A completely releases resources on the MSC-B
side and keeps connection with MSC-C to continue to control the realization of mobile
services.
4.4 CF Processing Procedure

Note:
The processing procedure of Call Forwarding service described below is for M900/M1800 MSC/SSP/IP
serving as VMSC. When M900/M1800 MSC/SSP/IP serves as GMSC, it only completes corresponding
Call Forwarding service includes Call Forwarding Unconditional (CFU), Call

Forwarding on Busy (CFB), Call Forwarding on mobile subscriber Not Reachable
(CFNRc) and Call Forwarding on mobile subscriber No Reply (CFNRy).
4-8
Technical Manual
z
MSC Functions
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
MSC Functions
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
Figure 4-6 Procedure of forwarding registration and erasure
4.5 Call Hold Processing Procedure

Note:
The Call Hold processing procedure below applies to M900/M1800 MSC/SSP/IP serving as VMSC. When
it serves as GMSC (Gateway MSC), it only performs corresponding procedure processing.
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
MSC Functions
MSC/
VLR
MSa
MSb
Call going on
Hold request
Facility (notify)
Hold ack
Hold call
Retrieve request
Facility (notify)
Retrieve ack
Retrieve call
Figure 4-7 Call Hold service processing procedure
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.
4.6 Call Wait Processing Procedure

Note:
The Call Wait service processing procedure described below applies to M900/M1800 MSC/SSP/IP
serving as VMSC. When M900/M1800 MSC/SSP/IP serves as GMSC, it only completes corresponding
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
MSC Functions
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)
Figure 4-8 Call Wait service processing procedure
4.7 Multiparty Service Processing Procedure

The Multiparty (MPTY) service allows three to six subscribers to participate a call at the
same time. The party who convenes the multiparty call should have subscribed to
MPTY service and HOLD service.
The process to convene a multiparty call is shown in Figure 4-9.
1)
MSa holds the call with MSd.
2)
MSa establishes a call with MSb.
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)
MSa, MSb and MSd talk at the same time.
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
MSa
MSC Functions
MSC/
VLR
MSd
MSb
Call between MSa

and MSd is hold.
MSa and MSb are in conversation.
Facility(Build Mpty)
Facility
(Retrieve notify)
Facility
(Build Mpty notify)
Facility
(Build Mpty notify)
Facility
(Build Mpty ack)
Three-party call: MSa, MSb and MSd.
Figure 4-9 Multiparty service processing procedure
4.8 Explicit Call Transfer (ECT) Processing Procedure

ECT enables the called party to determine the forwarded-to party. The processing
procedure is shown in Figure 4-10.
1)
MSa holds the call with MSd.
2)
Msa calls MSb, MSb answers or is alerted.
3)
MSa originates ECT request.
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)
MSC/VLR notifies MSd and MSb of ECT message.
6)
MSC/VLR sends release message to MSa to disconnect the original MSa-MSd

call and MSa-MSb call.
7)
The communication between MSd and MSb is enabled.
4-13
Technical Manual
MSa
MSC Functions
MSC/
VLR
MSd
MSb
MSa-MSd call is held

Facility(ECT Request)
MSb answers or is
alerted
Facility
(Retrieve notify)
Facility
(ECT notify)
Facility
(ECT notify)
DISCONNECT/RELEASE/RELEASE COMPLETE
MSb-MSd call after CT

Figure 4-10 ECT processing procedure
4.9 SMS Processing Procedures

Note:
The Short Message Service (SMS) processing procedure described below applies to M900/M1800
MSC/SSP/IP serving as VMSC. When M900/M1800 MSC/SSP/IP serves as GMSC, it only completes
corresponding procedure processing.
4.9.1 Introduction to SMS

Short Message Service includes point-to-point short message service and cell
broadcast short message service.
Point-to-point short message services include mobile terminated short message
services (teleservice code 21) and mobile originated short message services
(teleservice code 22). The network entities involved include:
z
BSS side: BTS and BSC
NSS side: MSC/VLR and HLR
Short Message Center (SMC)
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
MSC Functions
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
BSS side: BTS and BSC.
Cell Broadcast Center (CBC).
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
MSC Functions
between SMC and other information source entities should be able to bear these two
different services.
4.9.2 Short Message Service (MT/PP)

The processing procedure of Mobile Terminated Point-to-Point Short Message Service
SC
SMC G/IW
MSC
Message transfer
HLR
MSC/
VLR
MS
Send Routing Info

For SM
Routing Info ack
MT forward short message
Message transfer
MT forward short message ack
Delivery report
SM Delivery
Report Status
Figure 4-11 Processing procedure of mobile terminated SMS

1)
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)
After VMSC receives the MT forward short message indication from

SMS-G/IWMSC, it will first retrieve the subscriber information from VLR to judge
whether the subscriber is reachable, whether roaming is permitted, whether the
MS supports the short message service, whether radio resources are busy, and
whether any radio connection already exists (i.e. to decide the possibility of
parallel services). Then it will determine whether to originate paging to the
4-16
Technical Manual
MSC Functions
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)
After receiving the ForwardShortMessage response from VMSC, SMS-G/IWMSC

will continue to send the information to the SMC if the forwarding succeeds. If
necessary, the short message delivery status report will be sent to HLR in order to
trigger the necessary process of arousing SMC and to clear away the relative flags
in MWI. If the forwarding failed due to mobile subscriber unreachable or short
message memory overflow, SMS-G/IWMSC will originate the short message
delivery status report to HLR to facilitate the instant updating of relative
information in MWI, and return the forwarding failure cause value and modified
MWI results to the SMC.
4.9.3 Short Message Service (MO/PP)

The processing procedure of Mobile Originated Point-to-Point Short Message Service
4-17
Technical Manual
MSC Functions
SMC G/IW
MSC
SC
HLR
MSC/
VLR
MS
Access request
Message transfer
MO forward short message

Message transfer
Delivery report
MO forward short message ack
Delivery report
Figure 4-12 Processing procedure of mobile-originated SMS

1)
When MS sends a short message, the process is similar to ordinary speech

service, that is, it must first submit a service request (CM_SERV_REQ) to the
network side. In addition, only after the necessary service access process can
MSC and MS establish a radio channel (RR) connection via BTS and BSC to carry
the short message service. The MS will send the short message to MSC through
the DTAP message using this connection (for the message format, please refer to
ETSI GSM 04.11) and wait for response from the system. MS will display the final
results of the short message submission after receiving response from the
network side.
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
MSC Functions
4.9.4 Instant Triggering after SMS-MT Failure

If the mobile-terminated short message fails due to mobile subscriber unreachable or
short message memory overflow, and the address of the SMC is already inserted in the
MWI of HLR, the SMC will place the short message in the queue waiting for
re-transmission triggering, and re-send it on receiving the AlertServiceCenter
message. In case of temporary transmission failure, the message will be placed in the
queue of periodic re-transmission.
In general, instant triggering of short messages may have the following three cases:
z
The sending of mobile-terminated short messages with high priority succeeded.
The mobile subscriber re-accesses the mobile network.
The subscriber makes memory available by deleting some short messages.
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
(ShortMessageMemoryAvailable) message, it will originate the ReadyForSM

message to HLR together with the memory-available cause value. After receiving this
message, HLR will delete the MCEF in MWI and trigger alert SMC.
On receiving the AlertServiceCenter message, SMS-G/IWMSC sends the message
to the SMC. The SMC will instantly process the corresponding short message to be
4-19
Technical Manual
MSC Functions
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.
4.10 Virtual Roaming Service (VRS) Processing Procedure

The subscriber -Mobile V- who has subscribed to the VRS owns one MSISDN
respectively in each network of both countries/regions. The VRS can be implemented
via special service procedure: When a subscriber in Country/Area A calls the Mobile V,
he only needs to dial Mobile V's MSISDN in the network of Country/Area A. Likewise,
when a subscriber in Country/Area B calls the Mobile V, he only needs to dial Mobile V's
MSISDN in the network of Country/Region B.
The processing procedure of VRS is shown in Figure 4-13.
(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
Figure 4-13 VRS processing procedure

1)
The MS1 roaming to MSC1 originates a call to MS2 (a VRS-subscribed user)

according to the called number MSISDN_A owned by MS2 in area A.
2)
Based on MSISDN_A, MSC1 sends routing request to HLR-A.
4-20
Technical Manual
3)
MSC Functions
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)
MSC/VLR2 sends the real roaming number MSRN_T of MS2 to HLR-B.
6)
HLR-B sends MSRN_T of MS2 to HLR-A.
7)
HLR-A
allocates
virtual
roaming
number
MSRN_V,
and
stores
the
correspondence between MSRN_V and MSRN_T. Then, it sends MSRN_V as the

roaming number to MSC1, responding to the routing request.
8)
MSC/VLR1 originates call to GMSC according to MSRN_V.
9)
GMSC analyzes MSRN-V and gets routing information from HLR-A.
10) HLR-A sends the real roaming number MSRN_T to GMSC.

11) GMSC originates call to MSC2 according to MSRN-T.
12) MS2 answers, and MS1 and MS2 can start the conversation.
4-21
HUAWEI
Technical Manual
SSP Functions
Technical Manual
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
SSP Functions
Table of Contents
4.3.2 Common CAP Operations..................................................................................... 4-10

4.3.3 Extended CAP Operations .................................................................................... 4-10
Chapter 5 WIN Service Procedures ............................................................................................. 5-1
5.1 PPS Subscriber Call Ordinary PLMN Subscriber .............................................................. 5-1
5.2 PPS Subscriber Call PSTN Subscriber ............................................................................. 5-2
5.3 PSTN Subscriber or Ordinary GSM Subscriber Call Overlay PPS Subscriber ................. 5-3
5.4 Call between PPS Subscriber in Overlay Mode ................................................................ 5-5
5.5 PPS Subscriber Recharging/Query Procedure ................................................................. 5-7
5.6 UCB (USSD Call Back) Service Procedure....................................................................... 5-8
5.6.1 RBT ....................................................................................................................... 5-11
ii
Technical Manual
SSP Functions
Chapter 1 Introduction to WIN

This chapter gives a general idea of the concept, features and services of Wireless
Intelligent Network (WIN) before introducing the SSP function of M900/M1800
MSC/SSP/IP.
1.1 Concept of Wireless Intelligent Network

Wireless intelligent network introduces the function entities of an intelligent network into
the mobile network to perform the intelligent control of mobile calls. It is the combination
of a wireless network and an intelligent network. The basic idea of IN (Intelligent
Network) is that the exchange implements the most basic connection function while all
value-added services are provided by another added network. Switching and services
are separated so that the service provider can economically and effectively provide
new services and make better control over the network.
The WIN is typically composed of Service Control Point (SCP), Service Switching Point
(SSP), Service Management System (SMS), Service Creation Environment (SCE) and
Intelligent Peripheral (IP).
SSP, as the connecting point of the existing mobile network and intelligent network,
provides the function of IN access. SSP detects the intelligent service requests,
communicates with SCP, and responds to SCP request. It allows the service logic in
SCP to act on call handling.
Functionally, an SSP contains Call Control Function (CCF) and Service Switching
Function (SSF). In the absence of IP, SSP should also include some Specialized
Resource Function (SRF). CCF accepts users call and implements basic connection
functions, such as call establishment and call holding. SSF receives and identifies
intelligent service call, reports it to SCP and receives the control command from SCP.
SCP, the core component of IN, stores subscriber data and service logic. SCP serves to
receive the query information from SSP, search the database and perform decoding.
Meanwhile, SCP can initiate different service logics according to the call events
reported by SSP, and send call control instructions to the corresponding SSP according
to the service logic for placing various intelligent calls. All the service control functions
available with WIN are centralized in SCP, and SCP communicates with SSP according
to the standard WIN interface protocol. SCP is generally composed of mini-computer,
high-performance microcomputer and large-scale real-time high-speed database. SCP
must be highly reliable, with an annual service interruption time less than 3 minutes. In
a WIN system, therefore, SCP must be configured in a duplicated mode at least.
1-1
Technical Manual
SSP Functions
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 Features of Wireless Intelligent Network

WIN is developed not only to provide numerous services to subscribers but also is
oriented to provide new services in the future in a convenient, quick and cost effective
manner. Separating switching and services, WIN establishes centralized service
controlling points and database, based on which centralized service management
system and service creation environment are established, so as to achieve the
above-mentioned objectives. SSP/IP has the following features:
z
Efficient use of information processing technology.
Efficient use of network resources
Modularization of network functions
It generates and implements new services by repeatedly using standard network

functions.
Flexible assignment of network functions in physical entities
Realization of standard communication between network functions through the

service-independent interfaces.
Controllability of service attributes prescribed by service subscribers
Standardized service logic
1-2
Technical Manual
SSP Functions
It supports SS7 signaling, and configuration of 14-bit and 24-bit signaling points.
It provides ISDN interface in compliance with ITU-T standard.
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.
Its specialized resource supports recorded announcements in up to 8 languages,

and the recorded announcement can be added online.
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 Services of Wireless Intelligent Network

WIN can generate and realize various new services in a quick, convenient, flexible,
economical and effective way. It can serve not only existing mobile communications
networks (TDMA and CDMA), Public Switched Telephone Network (PSTN), Packet
Switched Public Data Network (PSPDN) and Narrowband ISDN (N-ISDN), but also
broadband ISDN.
With the function of mobile service switching point, M900/M1800 MSC/SSP/IP can
function as SSP/IP equipment for WIN to provide various CAMEL services. The
following is the introduction to some wireless intelligent services supported by
M900/M1800 MSC/SSP/IP, including Pre-Paid Service (PPS), familiarity number
service, Cell and Time Discount (CTD) and Wireless Advertisement (WAD) service.
1.3.1 Pre-Paid Service

PPS (Pre-Paid Service) is a card number service. A PPS subscriber needs to establish
its account in the system by paying an amount of money in advance or buying a card
with a certain amount of money (such as rechargeable card).
The operator does not authenticate users. The relationship between the operator and
subscribers is only the appointment for pre-payment. Therefore, it is very easy and
convenient for both the operator and users to apply for and develop PPS.
When a call is established, the network will determine to accept or reject the call based
on the amount of money in the user account, perform charging during the call by
deducting the money paid from the user account. When the balance in the account is
used up, the call will be disconnected. Therefore, PPS can help the operator to prevent
the frauds.
1-3
Technical Manual
SSP Functions
1.3.2 Familiarity Number Service

Familiarity Number Service allows users to define several first-selected numbers (e.g.
5 numbers) by themselves. When the service users call these numbers, they can enjoy
discounts. In addition, the users can modify these first-selected numbers by dialing a
service number. To prevent users from modifying the first-selected numbers too
frequently, charging may be made on number modification. This is a new service to
attract users with new charging rates. Familiarity Number Service can also be used to
enhance the functions of other intelligent services such as PPS.
1.3.3 Cell and Time Discount

Cell and Time Discount (CTD) refers to the service that the network can determine the
current charging rate (based on the settings made by the operator) according to the cell
of the subscriber and the time when the subscriber originates or accepts a call.
The cell discount can be based on the cellular cells of GSM system. Due to the
difference in population and activity, some of the cells may bear heavier traffic than
others do. Cell Distribution provides the operator an approach to adjust the
geographical distribution of traffic amount with the charging rate. By reducing the
charging rate properly in a less traffic region, the traffic amount in the region may be
stimulated.
The time discount service can be implemented based on the unit of hour or minute. The
peak traffic may occur in different stages of a day depending on the activities of
subscribers. Time Distribution service allows the operator to determine different
discounts for different cells and different time segments of a day. It helps the operators
balance the traffic and increase their profits.
1.3.4 Wireless Advertisement Service

Wireless Advertisement Service (WAD) combines mobile service with advertisement to
allow normal users to obtain favorable or free service. Enterprises can use this service
to transfer product information to users. WAD service refers to that when a normal
mobile user makes a call, the user first dials a WAD number and listen to a piece of
advertisement first, then the user dials the called number for free or with discount. This
call charge is paid by the advertising company.
1.3.5 UCB Service

Instead of a standard intelligent network service, UCB (USSD Call Back) service is a
value-added service developed by Huawei based on GSM intelligent network
specifications according to customers demands. Via this service, the PPS international
1-4
Technical Manual
SSP Functions
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
SSP Functions
Chapter 2 WIN Functions

This chapter describes the functions of M900/M1800 MSC/SSP/IP in standard
CAMEL (Customized Applications for Mobile network Enhanced logic) Phase 2 WIN
(Wireless Intelligent Network) and in WIN of OVERLAY mode. This chapter also
introduces the provisioning of the intelligent resources and the triggering of intelligent
services by access code.
To introduce the intelligent network into GSM system, ETSI (European Telecom
Standard Institute) defined CAMEL (Phase 1) based on GSM Phase 2+ in 1997.
Phase 2 was released in March 1998. The standardization of CAMEL Phase 2 was
completed in August 1998.
The feature of CAMEL is to provide subscribers with a service consistency
independent of the service network. CAMEL feature is a network feature rather than a
supplementary service. It can be used as an approach that helps the network
operator provide subscribers with specialized services even if the subscribers are not
in the HPLMN (Home Public Land Mobile Network).
The following is the introduction to the functions of M900/M1800 MSC/SSP/IP on
standard CAMEL Phase 2 WIN, followed by the introduction to functions on WIN in
OVERLAY mode.
2.1 Standard CAMEL Phase 2 WIN

CAMEL standards include several phases. In August 1998, standardization of CAMEL
Phase 2 was launched.
2.1.1 Networking Structure of Standard CAMEL Phase2 WIN

The network structure of CAMEL Phase 2 is shown in Figure 2-1. Several functional
entities are added in the GSM network: gsmSSF (Service Switching Function),
gsmSRF (Special Resource Function) and gsmSCF (Service Control Function). CAP
Phase 2 protocol interface is applied among gsmSCF, gsmSSF and gsmSRF. Internal
protocol interface is used among GMSC, MSC and gsmSRF. Other entities adopt the
MAP Phase 2+ interface.
The equipment dedicated for the implementation of gsmSCF is called SCP. The
equipment dedicated for the implementation of gsmSSF is called SSP and the
equipment dedicated for the implementation of gsmSRF is called IP (Intelligent
Peripheral).
2-1
Technical Manual
SSP Functions
In addition to GMSC, MSC and VLR functions, M900/M1800 MSC/SSP/IP also

provides SSP and IP functions.
HLR
MAP
gsmSCF
MAP
CAP
MAP
MAP
CAP
GMSC
gsmSSF
VLR
CAP
gsmSSF
MSC
gsmSRF
GMSC: Gateway Mobile Switching Center
GsmSCF: GSM Service Control Function
GsmSRF: GSM Specialized resource Function

MAP: Mobile Application Part
GsmSSF: GSM Service Switching Function
Figure 2-1 Network structure of CAMEL phase 2
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
SSP 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.
IV. GSM Service Switching Function (gsmSSF)

gsmSSF is combined with GMSC/MSC to provide some required functions for the
communications between gsmCCF and gsmSCF. The physical entity dedicated to
provide the gsmSSF function is called SSP. M900/M1800 MSC/SSP/IP supports the
following gsmSSF functions:
z
Extending MSC/SSP/IP logic, including the identification of intelligent service

control triggering and inter-SCF communications.
Managing the signaling between MSC/SSP/IP and SCF.
Modifying the call connection processing function in MSC/SSP/IP as per the

requirement and processing intelligent calls under the control of gsmSCF.
V. GSM Service Control Function (gsmSCF)

gsmSCF stores relative intelligent service control logic to enable flexible control on
mobile intelligent services. The physical entity dedicated to provide gsmSCF function
is called SCP.
VI. GSM Special Resource Function (gsmSRF)

gsmSRF provides special resources needed in implementing intelligent services. It
comprises the special resource provision function and the resource management
function. The physical entity dedicated to provide gsmSRF function is called IP
(Intelligent Peripheral).
2.1.2 Service Triggering of Standard WIN

In the standard WIN, triggering of intelligent services is implemented according to CSI
data of the subscriber data. CAMEL subscription information includes O-CSI
(Originating CAMEL Subscription Information) and T-CSI (Terminating CAMEL
Subscription Information).
O/T-CSI includes the following contents:
z
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
z
SSP 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.
CAMEL Capability Handling: It indicates the phase of CAMEL, which is asked by

the SCP for the service.
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.2 WIN in OVERLAY Mode

To enable the standard CAMEL Phase 2 WIN for mobile intelligent services, GMSC,
MSC and HLR should support CAMEL features in addition to the adding of SCP
equipment. This condition, however, is difficult for the existing mobile networks. To
provide mobile intelligent services, the OVERLAY WIN mode can be adopted, which
can gradually transit to standard WIN.
2-4
Technical Manual
SSP Functions
2.2.1 Networking of WIN in Overlay Mode

The wireless intelligent network in OVERLAY mode uses independent SSP/IP
equipment to perform the call handling of mobile intelligent service. The existing MSC,
GMSC and HLR of the network do not necessarily support CAMEL feature. In such
network structure, M900/M1800 MSC/SSP/IP can serve as SSP/IP, GMSC or
MSC/VLR, as shown in Figure 2-2.
HLR
SCP
PSTN
SSP/IP
GMSC
MSC
MSC
GMSC: Gateway Mobile Switching Center

MSC
Figure 2-2 OVERLAY Networking mode of wireless intelligent network

Respective entities on the wireless intelligent network in OVERLAY mode are
introduced as follows:
I. HLR (Home Location Register)

In the implementation of the OVERLAY mode, data of the intelligent subscriber is the
same as that of the ordinary subscriber. HLR need not support the storage and
transfer of O-CSI/T-CSI data. Hence the implementation program of the OVERLAY
mode has no special requirement for the existing HLR in the network.
II. GMSC (Gateway MSC)

GMSC transits calls from/to PSTN and routes the MT intelligent call to SSP/IP for
handling.
III. MSC (Mobile Switching Center)

MSC routes the MO and MT mobile intelligent calls to SSP/IP for handling.
2-5
Technical Manual
SSP Functions
IV. SCP (Service Control Point)

SCP stores service control logic for corresponding intelligent services and implements
flexible control on mobile intelligent services.
V. SSP/IP (Service Switching Point/Intelligent Peripheral)

SSP/IP enables functions of GMSC, gsmSSF and gsmSRF described in Section 2.1.
It provides the CAP signaling interface to SCP. It also collects intelligent calls from
GMSC & MSC and implement intelligent call handling according to different services.
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.2.2 Service Triggering of Overlay WIN - Number Segment Triggering

To enable MSC & GMSC to distinguish ordinary subscribers and intelligent
subscribers, WIN in the overlay mode requires intelligent subscribers to be in a
special number segment. Upon receiving MO and MT calls from or to the special
number segment, GMSC and MSC routes the call to SSP/IP. The specific process is
as follows:
On receiving MO , MT and MF calls, if the calling subscriber or the called subscriber
is in the special number segment for intelligent subscribers, MSC/GMSC will route the
calls to the corresponding SSP/IP and add 1 or 2-digit area prefix before the called
numbers indicating the present area of MSC and GMSC.
When SSP/IP receives the MO call from MSC, it will judge whether the calling
subscriber is an intelligent subscriber according to the calling number. If the calling
subscriber is in the special number segment for intelligent subscribers, SSP/IP
obtains the calling service key and SCP address information of the calling 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 to trigger the calling intelligent service process. The trigger point is set as
DP2. The SSP/IP reports the service key, calling number, called number & calling
location information to SCP and complete MO intelligent call according to the SCP
call control command.
2-6
Technical Manual
SSP 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.
2.2.3 Smooth Evolution of WIN in OVERLAY Mode

A wireless intelligent network in OVERLAY mode is able to provide mobile intelligent
service quickly without upgrading the existing equipment. However, it causes the
2-7
Technical Manual
SSP 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.3 Services Triggering via Access Code Mode

Some intelligent services need unified access code to enable subscriber operations,
such as interrogation, loss report and complaint. CAMEL Phase 2 specification does
not support such applications.
M900/M1800 MSC/SSP/IP refers to the features of wired IN and provides the
capability to trigger mobile intelligent services via access codes. According to the
operator's requirement, a code can be defined as the trigger access code for relative
intelligent services. When the subscriber dials the code via any terminal equipment
(e.g. PSTN telephone, mobile terminal, etc.), M900/M1800 MSC/SSP/IP can
immediately trigger corresponding mobile intelligent service call handling.
2.4 Access of gsmSRF Resource

Integrated SSP/IP mode already provides gsmSRF functions, as shown in Figure 2-3.
In intelligent service procedures, the user interaction command issued by SCP is
transferred by the gsmSSF to the internal gsmSRF functional entity through internal
interface to enable the user interaction procedure needed by the intelligent call
handling.
2-8
Technical Manual
SSP Functions
SCP
gsmSCF
CAP
Internal
Interface
gsmSSF
gsmSRF
gsmCCF
SSP/IP
gsmSSF: GSM Service Switching Function
gsmCCF: GSM Call Control Function
gsmSCF: GSM Service Control Function

gsmSRF: GSM Specialized Resource Function
Figure 2-3 gsmSRF access mode
2.5 Supporting Virtual Roaming Number

In the Overlay networking mode, data configuration is always complicated. The Virtual
Roaming Number (VRN) function enables the support of MAP PHASE2+ in overall
HLR and GSMC/SSP, featuring the function of target network. In the condition that the
VMSC cannot provide CAMEL function, the VRN function can not only implements
the intelligent network service easily, but also avoid complicated data configuration.
During the intelligent call processing procedure, instead of sending the real MSRN to
VMSC, the HLR sends MSC number with SSP function. That is so-called virtual
roaming number. According to this virtual roaming number, the VMSC routes to
MSC/SSP to implement the overlay of the call. The intelligent service processing
procedure adopting VRN is shown in Figure 2-4.
2-9
Technical Manual
SSP Functions
MAP PHASE2+
HLR
2
MAP_PHASE2
MSC1
6
7
MSC2
10
12
1
A
MAP_PHASE2
11
GMSC/SSP
B
MAP PHASE2+
Figure 2-4 Processing procedure of intelligent service adopting VRN

1)
A subscriber in province A (subscriber A for short) calls local subscriber B, who

has subscribed to intelligent network service.
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)
HLR sends a virtual roaming number to MSC1.
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)
HLR returns TCSI and the real MSISDN of subscriber B to GMSC/SSP.
7)
GMSC/SSP triggers the intelligent network service of subscriber B according to

TCSI. Then, according to MAP process, it originates the operation to get the real
route of subscriber B according to the real MSISDN of it.
8)
The follow-up operations of HLR getting roaming number from MSC2 is same
with the standard procedure of MAP getting route information.
In short, in the above procedure, the GMSC/SSP is requested to be able to:

1)
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.
The special processing at HLR has the following features:

1)
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
SSP Functions
it returns the real MSISDN of the called subscriber to GMSC/SSP via the D
interface modified.
2.6 Supporting Overseas SSP Feature

To provide more service support to Overlay mobile intelligent network subscriber,
M900/M1800 MSC/SSP/IP has been enhanced with the following intelligent service
attributes:
z
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.
Supporting the special requirements in Thailand to play announcement by two

times for intelligent call. That is, to play prompt tone respectively when the
balance of the subscriber is three minutes left and one minute left. And the
operator can control whether to play once or twice the announcement.
Supporting the filling of CAC (Charging Area Code) in InitialDP message.
Generating bills in the format requested by the operator.
2-11
Technical Manual
SSP Functions
Chapter 3 Intelligent Call Handling

3.1 Overview
SSP is the connecting point between a mobile network and an intelligent network. It
provides an access to the functions of the intelligent network. The specific
call-proceeding procedure according to the logic of the intelligent service is
completely controlled by SCP.
To separate the switching function from the control function, it is necessary for SSP to
establish some detection points and control points during the call handling. The
detection points report the events during a call process to SCP and wait for the further
control command from SCP, while the control points accept the control command from
SCP and control the call procedure.
In an intelligent network, SSP integrates the functions of SSF, CCF, CCAF and SRF,
SCP integrates the functions of SCF and partial functions of SDF, SDP integrates
partial functions of SDF, SMS integrates the functions of SMF and SMAF, while SCE
provides SCEF function. These parts cooperate to perform the processing of
intelligent calls. Intelligent call handling models include SSF/CCF call state model,
SRF call state model, SCF call state model, SDF call state model and SMF call state
model. The following focuses on the discussion of IN basic call state model i.e.
SSF/CCF call state model. For the information about other models, please refer to
ETSI GSM Phase 2+ Specifications 02.78, 03.78 and 09.78.
3.2 IN Basic Call State Model

I. Major componets of SSF/CCF model
The SSF/CCF model mainly includes BCM (Basic Call Manager), IN-SM
(IN-Switching Manager), FIM (Feature Interactions Manager)/CM (Call Manager), the
relationship between BCM and IN-SM, the relationship between BCM and IN-SM, and
between BCM and FIM/DPP, and the function separation provided on SSF/CCF.
3-1
Technical Manual
SSP Functions
SC F
S LPI A
<Information flow>
SS F
SCF Access manager

IN Local Resource
Data Manager
IN Switching Manager
IN Switching State Model Inst.
< IN-SSM >
< IN-SSM events>
< Reso urce C ontrol>
IN Local Resource Data

Non-IN Feature Manager
Feature Interactions/Call Manager
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
Basic Call Manager

< D P P roc essing>
< B asic call triggers>
< B asic call ev ents >
C CF
<B CS M >
Basic Call Res. data Manager

SRF
CCAF
BC M
Basic Call Resource data
Bearer Control
C CA F
Figure 3-1 SSF/CCF Model of MOC/MTC single-end SLPI
II. Composition of SSF/CCF model

The SSF/CCF model of MOC/MTC single-end SLPI (Service Logic Processing
Instance) is shown in Figure 3-1. This model is composed of three parts:
z
Basic Call Manager (BCM)
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
Feature Interactions Manager/Call Manager (FIM/DPP)
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-Switching Manager (IN-SM)
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
SSP Functions
III. Relationships between the major components in SSF/CCF model

The main relationships between the components of SSF/CCF model are the
relationship between SCF and IN-SM (through SCF access function), the relationship
between IN-SM and FIM/DPP, and the relationship between FIM/DPP and BCM.
Among them, the relationship between SCF and IN-SM is the external relationship of
SSF/CCF and needs to be standardized. All these relationships are expressed by
information flows, as shown in Figure 3-2.
SCF
SSF Information Flow
SCF Information Flow
SSF/CCF
IN Switching Manager(IN-SM)
Non-IN Event Indicator
Non-IN Event Indicator
IN Control Request
Feature Interactions Manager/DP Processing

(FIM/DPP)
Non-IN Feature Manager
BCM Control Request
BCM Event Indicator
Non- IN Control Request

Basic Call Manager (BCM)
Figure 3-2 Information flows of SSF/CCF

BCM is responsible for processing all calls. Call events are reported to FIM/DPP with
BCM event information.
FIM/DPP is responsible for separating intelligent calls from non-intelligent calls and
reporting them to IN-SM through the IN event-indicator information flow.
IN-SM is responsible for converting the call information into the standard CAP
message and sending it to SCF. For the CAP message sent by SCF, IN-SM converts
it into the internal call information of the exchange and sends it to FIM/DPP through
the IN-control request information flow. FIM/DPP converts it into BCM control request
and sends it to BCM to act on the call handling.
IV. Basic call manager (BCM)

Basic call/connection control can be described in a call state transition diagram i.e.
Basic Call State Model (BCSM). BCSM uses a finite state mechanism to describe the
3-3
Technical Manual
SSP Functions
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
Figure 3-3 BCSM Component

PIC indicates the relatively stable state during a call, such as the state that a
subscriber is dialing. SCP can decide at which PIC a call is by sending a command.
PIC is also called a control point.
DP means the critical point when a call state is ended and before it enters the next
call state. It can be regarded as a break point in a continuous call process.
Transition indicates the normal flow direction from a PIC to another PIC during a basic
call/connection process.
Events cause the transition from one PIC to another PIC.
The DP and PIC that must be set during a call process are defined in CAMEL Phase
2 protocols. Also, the functions of the originating end (calling part) of an IN call are
separated from that of its terminating end (called part), as defined in the protocol.
Accordingly, BCSM consists of two parts: the originating BCSM and the terminating
BCSM, as shown in Figure 3-4 and Figure 3-5. They are managed by a BCM with
separate functions in SSF/CCF.
The originating BCSM describes the state transition of the basic call/connection on
the calling side, and the terminating BCSM describes the state transition of the basic
call/connection on the called side. In the diagram, the smaller box represents DP and
the bigger box represents PIC.
The originating BCSM and the terminating BCSM are established to provide better
service control in case the calling party and the called party involve two PICs. For
3-4
Technical Manual
SSP Functions
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
O_Null & Authorise_Origination_

Attempt_Collect_Info
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
Basic Call transition

Transition beyond Basic Call
Figure 3-4 Originating BCSM

z
O_Null & Authorize_Origination_Attempt_Collect Info
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
Analyse, Routing and Alerting
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
SSP Functions
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.
VI. Terminating BCSM

Note: The terminating BCSM is numbered together with the originating BCSM for PIC
and DP.
3-6
Technical Manual
SSP Functions
T_Exception
T_Null
DP18
T_Abandon
DP12
Terminating_Attempt_Authorised
Terminating Call Handling
T_Busy
T_No_Answer
T_Disconnect
T_Answer
DP17
DP13
DP14
DP15
T_Active
Basic Call transition

Transition beyond Basic Call
Figure 3-5 Terminating BCSM

z
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
Terminating Call Handling
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
SSP Functions
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.
3.3 Detection Point (DP)

I. Classification of DPs
DP (Detection Point) is used to trigger an intelligent call and detect the events related
to the intelligent call. A DP can be armed in order to notify the Intelligent Service
Logic Instance that the DP was encountered, and potentially to allow the Intelligent
Service Logic Instance to influence subsequent handling of the call. If the DP is not
armed, SSF/CCF continues the processing without gsmSCF involvement.
DP is classified into two types:
z
TDP (Trigger Detection Point)
EDP (Event Detection Point)
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
SSP Functions
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 armed EDP is met, then it is disarmed.
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
SSP Functions
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
Trigger Detection Point - Request (TDP-R)
Event Detection Point - Request (EDP-R)
Event Detection Point - Notification (EDP-N)
These DP types are defined by DP attributes, as shown in Table 3-1.

Table 3-1 BCSM DP types
Criteria
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.
III. DP types for mobile originating calls

The DP types used for mobile originating calls and forwarding calls are listed in Table
3-2.
Table 3-2 DP Types for mobile originating calls
CAMEL DP
DP Type
Description
DP2 Collected_Info
TDP - R
Indication that the O-CSI is analyzed.
DP4
Route_Select_Failure
EDP - N, EDP R
Indication that the call establishment failed
3-10
Technical Manual
CAMEL DP
SSP Functions
DP Type
Description
Indication that:
EDP - N, EDP R
- a busy indication is received from the terminating party,
DP6 O_No_Answer
EDP - N, EDP R
Indication that an application timer associated with the

O_No_Answer DP expires
DP7 O_Answer
EDP - N, EDP R
Indication that the call is accepted and answered by the

terminating party.
DP9 O_Disconnect
EDP - N, EDP R
A disconnect indication is received from the originating

party or from the terminating party.
DP10 O_Abandon
EDP - N
Indication that a disconnect indication is received from

the originating party during the call establishment
procedure
DP5 O_Busy
- a not reachable event is determined upon a cause IE in

the ISUP release message.
IV. DP Types for mobile terminating calls

The DP types used for mobile terminating calls are listed in Table 3-3.
Table 3-3 DP Types for mobile terminating calls
CAMEL DP
DP12
Terminating_Attempt_
Authorized
DP Type
TDP-R
Description
Indication that the T-CSI is analyzed.
Indication that:
DP13 T_Busy
EDP-N,
EDP-R
- a busy indication is received from the destination

exchange,
- Not reachable or call establishment failure event is
determined from the HLR response or upon a cause IE in
the ISUP release message.
DP14 T_No_Aanswer
EDP-N,
EDP-R
Indication that an application timer associated with the

T_No_Answer DP expires
DP15 T-Answer
EDP-N,
EDP-R
Call is accepted and answered by terminating party
DP17 T_Disconnect
EDP-N,
EDP-R
A disconnect indication is received from the terminating

party or from the originating party.
DP18 T_Abandon
EDP-N
A disconnect indication is received from the originating

party during the call establishment procedure
3-11
Technical Manual
SSP Functions
3.4 Triggering of Intelligent Service - TDP and Service Keys

The triggering of an intelligent service needs TDP and service keys.
A service key is an integer identifying an intelligent service.
Service keys differ from one another in different intelligent services. Service keys are
determined by the operator.
TDP and service keys need to be configured in the system data configuration.
3.5 Standard WIN Service Triggering - CSI Triggering

In the standard MIN, triggering of intelligent services is implemented according to CSI
data of the subscriber data. CAMEL subscription information includes O-CSI
(Originating CAMEL Subscription Information) and T-CSI (Terminating CAMEL
Subscription Information).
O/T-CSI includes the following contents:
z
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.
CAMEL Capability Handling: It indicates the phase of CAMEL, which is asked by

the SCP for the service.
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
SSP Functions
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.
3.6 Description of CAMEL Subscriber Data

The CAMEL subscriber data which correlate with SSP are: originating CAMEL
subscription information (O-CSI), terminating CAMEL subscription information
(T_CSI), Supplementary service CAMEL subscriber information (SS-CSI) and the
user information in SRI Interrogation.
1)
O/T-CSI includes:
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.
Service Key. The Service Key identifies to the gsmSCF the service logic that should
apply
Default Call Handling. The Default Call Handling indicates whether the call shall be
released or continued as requested in case of error in the gsmSSF to gsmSCF
dialogue.
TDP List. The TDP List indicates on which detection point triggering shall take place.
For O-CSI only DP2 is used. For T-CSI only DP12 is used.
DP criteria. The DP criteria indicate whether the gsmSSF shall request the gsmSCF
for instructions.
CAMEL Capability Handling: CAMEL Capability Handling indicates the phase of
CAMEL, which is asked by the gsmSCF for the service.
2)
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)
Location information/Subscriber state Interrogation. This data indicates whether

additional subscriber information shall be sent to the GMSC as part of the
terminating call handling.
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
SSP Functions
Chapter 4 WIN Application Protocols

4.1 Introduction to CAP
CAP (CAMEL Application Part) derives from INAP protocols from fixed intelligent
network. It implements the signaling interworking among WIN functional entities like
gsmSSF, gsmSRF and gsmSCF, so as to achieve CAMEL services.
CAP protocol is a part of SS7. It is the user part of TCAP (Transaction Capability
Application Part), using structured/unstructured dialog capability provided by TCAP to
realize the signaling interworking among different entities.
4.2 CAP Protocol

4.2.1 GSM Protocol Family of CAMEL Phase 2
To introduce an intelligent network into a mobile communication system, ETSI defined
the CAMEL (Customized Applications for Mobile network Enhanced Logic) protocols in
GSM Phase 2+ in 1997.
The GSM protocol family supporting CAMEL Phase II includes:
z
GSM02.78
CAMEL Service Definition
GSM03.78
Customized Application for Mobile Network Enhanced Logic
GSM09.78
CAMEL Application Part Specification
GSM09.02
Mobile Application Part Specification
GSM03.18
Basic Call Handling/Technical realization
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
SSP Functions
GSM03.18 protocol is an original protocol of GSM protocol family. In order to support

CAMEL, MAP Phase II+ 03.18 protocol has been expanded to support the CAMEL
related processing in the basic call handling.
4.2.2 Basic Principles of CAP Protocol

CAP is the protocol of the application layer based on OSI 7-layer model. It is used to
support the interactions among the four Aes (Application Entities) of SSF, SCF, SDF
and SRF in CAMEL Phase 1 and CAMEL Phase 2.
CAP specifies the programs and TCAP primitives for sending information among SSF,
SCF and SRF. In normal operation, CAP acts as a TC user and uses only the structured
dialogue provided by TCAP. When information is sent between two physical entities,
the following primitives can be used:
z
Establish a dialogue: TC user sends TC-BEGIN request primitive.
Maintain a dialogue: TC user sends TC-CONTINUE request primitive.
End a dialogue: TC user sends TC-END request primitive.
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.3 CAP Protocol and MAP Protocol

CAMEL Application Part (CAP) is based on INAP protocol of the intelligent network. In
Phase 1, CAP specifies the information flow between gsmSSF and gsmSCF. In Phase
2, CAP specifies the interface between gsmSRF and gsmSCF in addition to the
interface between gsmSSF and gsmSCF.
4-2
Technical Manual
SSP Functions
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.
ITU-T Signaling System No.7 Users

OSI
Layer
7
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
BSSAP: Base Station Subsystem Application Part

ISUP: ISDN User Part
TCAP: Transaction Capability Application Part
MTP: Message transfer Part

SCCP: Signaling Connection Control Part
TUP: Telephone User Part
OMAP: Operation and Maintenance Application Part
Figure 4-2 Positions of CAP and MAP in SS7
4.3 CAP Operation

The interactions between the different function entities of a wireless intelligent network
depend on the various operations defined by CAP protocol. The operation set defined
by CAP protocol varies in a different phase. M900/M1800 MSC/SSP/IP supports
CAMEL Phase 2. In this phase, CAP protocol defines 22 CAP operations
4.3.1 CAP Operation Types

CAP operations can be classified into four types:
z
Type 1 reports both success and failure.

4-3
Technical Manual
SSP Functions
Type 2 reports only failure.
Type 3 reports only success.
Type 4 reports neither success nor failure.
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
Return Result from Activate Test
Apply Charging
Same
Apply Charging Report
Same
Assist Request Instruction
Same
Call Information Report
Same
Call Information Request
Same
Cancel
Same
Connect
Same
Connect to Resource
Same
Continue
Same
Disconnect Forward Connection
Same
Establish Temporary Connection
Same
Event Report BCSM
Same
Furnish Charging Information
Same
Initiate DP
Same
Release Call
Same
Request Report BCSM Event
Same
Reset Timer
Same
Play Announcement
Same
Prompt and Collect User Information
Same
Specialized Resource Report
Same
Activity Test
Activity Test Response
4-4
Technical Manual
SSP Functions
Note:
"Same" in the operation column means the operation name is the same as the name of the information
flow.
The following part describes the functions of each CAP operation.

ActivityTest
This operation is originated by gsmSCF to test the normality of the control relation of
gsmSCF on gsmSSF/gsmSRF.
When the gsmSSF/gsmSRF receives indication to perform ActivityTest operation, if the
corresponding control relationship is normal, it will return ActivityTest respond. If no
reply is received, then the gsmSCF will assume that the gsmSSF has failed in some
way and will take the appropriate action.
ApplyCharging
This operation is sent from gsmSCF to gsmSSF and is used to control the call duration.
It is used for interacting from the gsmSCF with the gsmSSF function: CSE control of
call duration. The ApplyChargingReport operation provides the feedback from the
gsmSSF to the gsmSCF.
The "ApplyCharging" operation contains control parameters of the call, such as the
Max Call Period Duration and Tariff Switch Interval. The actual call duration is informed
to gsmSCF by sending the "ApplyChargingReport" when the call reaches the maximum
call duration or is released.
The charging scenarios supported by this operation are those given in GSM 02.78 for
CSE control of call duration.
ApplyChargingReport
gsmSSF performs this operation to report charging related information to the gsmSCF
as requested by the gsmSCF using the ApplyCharging operation. A report shall be
made either when a call disconnection event is detected by the gsmSSF or when the
gsmSSF
detects
that
the
call
period
duration
indicated
in
parameter
maxCallPeriodDuration (received in ApplyCharging operation) has been reached.

AssistRequestInstruction
This operation is sent to the gsmSCF as requested by the gsmSSF, which is acting as
the assisting gsmSSF in an assist procedure, or by a gsmSRF. The operation is sent
when an assisting gsmSSF or a gsmSRF receives an indication from an initiating
gsmSSF indicting an assist procedure.
4-5
Technical Manual
SSP Functions
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
Call Attempt Elapsed Time
Call Stop Time
Call Connected Elapsed Time
Release Cause
The information will be reported by gsmSSF to gsmSCF in the "CallInformationReport"

format in call release.
Cancel
The gmSCF uses this class2 operation to request the gsmSRF to cancel a correlated
previous operation.
The operation to be deleted can be either a PlayAnnouncement operation or a
PromptAndCollect UserInformation operation.
The cancellation of an operation is indicated via a respective error indication,
"Cancelled", to the invoking entity of the cancelled PlayAnnouncement or
PromptAndCollectUserInformation operation.
The Cancel operation can also be used to cancel all outstanding requests and enable
the state machines (gsmSSF/gsmSRF) to go to "Idle". In this case the Cancel operation
does not specify any specific operation to be cancelled.
Connect
This operation is used to request the gsmSSF to perform the call processing actions to
route a call to a specific destination. To do so, the gsmSSF may use destination
information from the calling party and existing call set-up information depending on the
information provided by the gsmSCF.
4-6
Technical Manual
SSP Functions
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
SSP Functions
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
SSP Functions
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
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
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 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
SSP Functions
4.3.2 Common CAP Operations

The common CAP operations are listed in Table 4-2.
Table 4-2 Common CAP operations
Common CAP operations
Initiate DP
Request Report BCSM Event
Connect to Resource
Prompt and Collect User Information
Apply Charging
Disconnect Forward Connection
Continue
Apply Charging Report
Event Report BCSM
Release Call
Play announcement
Active Test
4.3.3 Extended CAP Operations

To support UCB service, M900/M1800 MSC/SSP/IP extends the CAP operations
according to relevant contents in INAP. Table 4-3 show the extended CAP operations.
Table 4-3 Extended CAP Operations
Extended CAP operations
InitiateCallAttempt
PortConnected
ProvideAvailDN/AvailDNProvided
BridgePorts / PortBridged
ConnectOnePort
The functions of each CAP operation are described as below:
I. Initial Call Attempt

Issued by gsmSCF to gsmSSF, this operation requests gsmSSF to set up call to
subscriber according to the address information contained in the operation.
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
SSP Functions
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
SSP Functions
Chapter 5 WIN Service Procedures

WIN service procedure refers to the signaling processing procedure in which intelligent
subscriber involves.
There are two types of intelligent subscribers, number segment subscriber and
subscription subscriber. The later owns subscription data O-CSI/T-CSI, while the
former not. When talking about intelligent subscriber, we usually refer to the Prepaid
Service (PPS) subscriber, as PPS is the mayor application of intelligent service.
In terms of the signaling processing procedure supported by CAP signaling system,
intelligent service supports triggering by subscription information and by number
segment. The following focuses on the call procedures triggered by number segment.
5.1 PPS Subscriber Call Ordinary PLMN Subscriber

A calling PPS subscriber is connected to MSCa/SSP/IP in OVERLAY mode.
MSCa/SSP/IP analyzes the calling number and triggers the service according to the
calling number, as shown in Figure 5-1.
1)
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
SSP Functions
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
SRI: Send Routing Information

IDP: Initial DP
AC: Apply Charging
ANM: Answer Message
ERB: Event Report BCSM
Figure 5-1 Call procedure (PPS subscriber calling ordinary PLMN subscriber)
5.2 PPS Subscriber Call PSTN Subscriber

A calling PPS subscriber is connected to MSCa/SSP/IP in OVERLAY mode.
MSCa/SSP/IP analyzes the calling number and triggers the service according to the
calling number, as shown in Figure 5-2.
1)
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
2)
SSP Functions
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)
MSCa/SSP/IP performs call proceeding according to the called number.
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
RC: Release Call
IDP: Initial DP
AC: Apply Charging
ANM: Answer Message
Figure 5-2 Call procedure (Overlay PPS subscriber calling PSTN subscriber)
5.3 PSTN Subscriber or Ordinary GSM Subscriber Call

Overlay PPS Subscriber
If the calling party is an ordinary mobile subscriber or an ordinary GSM subscriber, and
the called party is a PPS subscriber connected to MSCa/SSP/IP in OVERLAY mode,
5-3
Technical Manual
SSP Functions
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,
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)
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
SSP Functions
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
RC: Release Call

IDP: Initial DP
AC: Apply Charging
ANM: Answer Message
Figure 5-3 Call procedure (PSTN subscriber or ordinary GSM subscriber Calling Overlay PPS subscriber)
5.4 Call between PPS Subscriber in Overlay Mode

If both the calling party and the called party are PPS subscriber connected to
MSCa/SSP/IP in OVERLAY mode, the service will be triggered by number segment.
The call procedure is shown in Figure 5-4.
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 calling number. If the calling party is a PPS subscriber,
5-5
Technical Manual
SSP Functions
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)
When receiving Continue message, MSCa/SSP/IP analyzes the called number. If

the called party is a PPS subscriber, it will place the toll area code representing the
actual location of the calling party in the parameter Location Number in IDP
message. Then it will query the number segment-SCP correspondence and send
IDP message to SCPb.
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)
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
SSP Functions
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
Triggering by the called

number segment
IDP
RRBE
AC
Continue
Charging the called party
IAM(MSRN)
ACM
ANM
...
ACR
ERB
RC
ACR
ERB
RC
CAP message
MAP message
ISUP message

RC: Release Call

IDP: Initial DP
AC: Apply Charging
ANM: Answer Message
Figure 5-4 Call procedure (Overlay PPS subscriber calling Overlay PPS subscriber)
5.5 PPS Subscriber Recharging/Query Procedure

The call procedure for a PPS subscriber to recharge/query balance by dialing the
recharging service number is shown in Figure 5-5.
5-7
Technical Manual
SSP Functions
SCP
MSC/SSP/IP
IDP
ACM
ANM
Connect To Resource
Prompt And Collect User Info
PC Result
Play Announcement
Announcement ......
Release Call
IDP: Initial DP
ANM: Answer Message
Figure 5-5 Call procedure (recharging/query made by PPS subscriber)

1)
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)
SSP sends ACM and ANM backward.
4)
SCP sends PromptAndCollectUserInfo message and receives the digital
ConnectToResource to SSP.
information input by the subscriber.

5)
After receiving the information, SCP sends PlayAnnouncement to the user to

confirm the information. SSP sends SpecializedResourecReport to SCP.
6)
SCP sends ReleaseCall to SSP. SSP disconnects the call.
5.6 UCB (USSD Call Back) Service Procedure

If the calling party (subscriber A) is an international roaming Overlay PPS subscriber,
and the called party (subscriber B) is a Overlay PPS subscriber, the connection of the
call will be implemented via UCB service. The call procedure is shown in Figure 5-6.
5-8
Technical Manual
SSP Functions
GMSC
SSP
SCPa
HLRa
USSD Req (USSD Code,Called Party Number)

USSD Req
USSD Res
USSD Res
Trigged by
Ussd Code
ICA(MSISDN A)
RRBE(DP7-R,LEG ID=1)
AC
IAM(MSISDN A)
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

REL: Release
RC: Release Call
ICA: Initial Call Attempt

AC: Apply Charging
ANM: Answer Message
Figure 5-6 UCB Service Procedure

5-9
Technical Manual
1)
SSP Functions
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)
According to the address information of subscriber A contained in ICA message,

SSP originates the call to subscriber A via GMSC.
6)
After subscriber A answers, SSP sends ERB message to SCPa, reporting DP7
(O_answer).
7)
After receiving ERB message, SCPa sends ProvideAvailDN message to SSP.
8)
Upon receiving ProvideAvailDN message, SCP allocates multiparty service

resources and relevant DN, and reports the AvailDNProvided message containing
the DN allocated to SCP.
9)
Based on the ConnectOnePort message issued via AvailDNProvided, SCP

requests the SSP to connect the call (to subscriber A) with the resource obtained
via Provide Avail DN operation.
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
SSP Functions
successful, it sends OnePortConnected message to SCPa, notifying the

successful operation.
18) After receiving OnePortConnected message, SCP issues BridgePorts message,
asking SSP to bridge the call to subscriber A and the call to subscriber B.
19) According to the two DNs contained in BridgePorts message, SSP puts subscriber
A and subscriber B through.
20) After the conversation between subscriber A and subscriber B is over, if any party
hooks on, SSP will reports the charging report of subscriber A and hook-on event
of subscriber B to SCPa.
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

REL: Release
AIP: Advanced Intelligent Peripheral

IDP: Initial DP
CPG: Call Progress
ANM: Answer Message
AC: Apply Charging
Figure 5-7 RBT Service Procedure
5-11
Technical Manual
SSP Functions
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
Technical Manual
Operation and Maintenance

Functions
Technical Manual

Table of Contents
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

Table of Contents
1.9.1 Scheduled Task Management .............................................................................. 1-32

1.9.2 Batch Command.................................................................................................... 1-32
1.9.3 Macro .................................................................................................................... 1-33
ii
Technical Manual

Chapter 1 Operation and Maintenance Functions

This chapter describes the functions of M900/M1800 MSC/SSP/IPs O&M system and
their realization. Operation and maintenance functions mainly include setting user
authorities, data configuration, alarm, performance measurement, charging, routine
maintenance, system testing, software patching and task management, etc.
1.1 Setting User Authorities

M900/M1800 MSC/SSP/IP O&M system is a multi-user system. To ensure safe and
convenient usage of the system, operators (users) and workstations are given with
different level of authorities.
In the system, whether a MML command can be executed depends on two conditions:
user authority and workstation authority. Only when the two conditions are both
satisfied, will the command be executed.
This authority management mode features that one user cannot perform all operations
on all workstations even he is a super-user. Usually, workstations are geographically
distributed, therefore, such mechanism can provide centralized control for important
commands based on decentralized management, ensuring system safety without the
loss of flexibility.
1.1.1 Command Group

Command group is a basic unit of authority setting. One command may belong to one
or more command group. When a user or workstation has the authority of the
command group, he has the authority to execute all commands contained in this group
on this workstation.
There are 66 command groups in the M900/M1800 MSC/SSP/IP, named as G_0~G_63,
G_GUEST and G_SYS respectively. G_GUEST group (containing 5 commands) is the
least command group executable by users and workstations. G_SYS group contains all
MML commands. Other groups contain certain commands, representing different
authorities.
The user authorized with G_SYS command group is called super-user. Similarly,
workstation authorized with G_SYS command group is called super-workstation.
There is one and only one super-user but multiple super-workstations for the system.
The default name of super-user is set during system installation, and it can not be
modified. The super-user can set his password only.
1-1
Technical Manual

Super-workstation can be set during system installation, or by super-user afterwards

through "Add Workstation" command and authorizing the workstation with G_SYS
command group. This allows super-user to control the whole system on any
super-workstation and facilitates system management.
All operations related to authority management, such as modifying user/workstation
authority, modifying commands in command group and modifying user logon time, can
be done only by super-user. This ensures the centralized management of users by the
super-user.
G_GUEST is the command group with least authority. Users or workstations only with
this group can only execute 5 commands in this group.
1.1.2 Management of User Account

M900/M1800 MSC/SSP/IP uses ID, rather than user name, to uniquely identify user.
New user account may has the same name and attributes with the deleted account,
whose authority will not be passed to new user with the same name. This eliminates the
possibility of using invalid or deleted account to log on system.
User password is stored in the database after encryption. Its security can be sured by
the security mechanism of the database and password encryption algorithm.
1.1.3 Logon Time

M900/M1800 MSC/SSP/IP can allow users to log on the system only at specified
period. To the user can execute the commands contained in authorized command
group only when he logs on the system at allowable time.
1.2 Data Configuration and Management

The data configuration and management function of M900/M1800 MSC/SSP/IP refers
to the setting of system operation parameters, and operation and management of
relative data.
1.2.1 Data Configuration

Data configuration includes configuration of hardware data, number analysis, trunk,
local office information, signaling, charging and service data.
I. Hardware data configuration

z
Module description data: data of modules forming M900/M1800 MSC/SSP/IP,

such as module number and module type.
1-2
Technical Manual
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.
Resource configuration data: configuration information of resources such as EC

resource, signal tone resource, DTMF and MFC resources.
II. Configuration of number analysis data

Configuration of data related to call handling flow according to calling and called
number, including:
z
Number conversion: adding, deleting or modifying one or several digits of calling

or called number upon requirements.
Called number analysis: Analyzing called number to perform call processing,

paging called MS, or searching outgoing route.
Number segment management: providing special services (such as Prepaid

Service PPS) for subscribers of certain number segment.
III. Configuration of trunk data

Configuration of trunk route data related to incoming and outgoing calls, including:
z
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.
Route: a logical concept, indicating the direction of another switching equipment

connected to local office directly or indirectly.
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 group: a subset of sub-route, it is composed of homogeneous trunk circuits.
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.
IV. Configuration of local office information

Configuration of data related to identification and features of local office, including:
z
Local office information: signaling point network ID of local office, MSC number,
provisioning of SP or STP functions.
Local office configuration: operational parameters and internal debugging

parameters of local office.
V. Configuration of signaling data

Configuration of data related to signaling, including:
1-3
Technical Manual

Signaling point: signaling network is formed by connecting many signaling points.
Signaling route: a logical concept, indicating the direction to corresponding

Destination Signaling Point (DPC).
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.
VI. Configuration of charging data

Configuration of data related to bill generation and providing of necessary charging
information for Billing Center.
VII. Configuration of service data

Service data refers to the data related to GSM services, including location area
information, roaming subscriber information, roaming restriction information and some
GSM configuration information.
z
Roaming subscriber information: describing the roaming types of subscribers.
Roaming restriction information: including Zone Code data, grouping information

of roaming-restricted subscribers, and roaming authority of subscribers.
Some GSM configuration information: including IMSI GT translation information,

information of national access code and GSM system services.
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.2.2 Data Operation and Management

After the data operation on WS, the MML service analyzes the commands, and
configuration management service procedures of BAM saves the modified data into
BAM database and implements format conversion. Later, the switching service
procedure of BAM sends the converted data to the data management system, which
will implement data updating in traffic handling modules to ensure the data security.
Data files sending to Host include DB_0.DAT, DB_C.DAT and DB_?.DAT. DB_O.DAT is
the data file to be loaded in AMP board. DB_C.DAT is the data file to be loaded in CDP.
1-4
Technical Manual

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.
I. Data format conversion

BAM converts the format of O&M-oriented data received from WS to the data that can
be processed by Service Processing Module. The user may convert some or all
modified data according to the requirement. Only after conversion can data be loaded
to Service Processing Module.
II. Data setting

Data setting is to send the data after format conversion from BAM to the corresponding
modules of MSC.
After the data in BAM is modified, data setting should be implemented. The time of data
setting is related to the connection status between BAM and Host. When the BAM is in
online status, data setting will be automatically implemented after the data in BAM is
modified. Otherwise, data setting will not be automatically implemented.
In addition, user can send some or all data to specific modules upon the requirements
(for example, when setting times out or CRC check proves data inconsistent.)
III. Data CRC check

To ensure the consistency of data in BAM (background) and the MSC modules
(foreground), M900/M1800 MSC/SSP/IP provides the CRC check to verify the
consistency of BAM data and MSC data.
User can perform CRC check for specific data in specific module or all data in all
modules. If the data is not consistent, the user can set or load data to make them
consistent.
IV. Data backup

To ensure the safety of data, the system provides the function to backup Alarm, BAM,
Status, Test database, registry and VMSCBam.ini configuration files to the specified
directory.
In case of system failure, the user can restore the system by using the backup
database files and configuration files.
1-5
Technical Manual

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.
1.3.1 System Structure

Alarm system comprises two parts: fault detection subsystem and alarm generation
subsystem.
I. Fault detection subsystem

This subsystem monitors the operation status of the equipment through hardware
detection, software detection, etc. and reports fault information in time.
Hardware detection is completed by boards, its contents include:
z
Operation status (normal/abnormal, active/standby) of the board
Multi-frame synchronization or loss of synchronization
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
Switching network test
Board self-loop test
MFC code transceiving test
CRC check
Frame format check
Memory check
Data consistency check
1-6
Technical Manual

II. Alarm generation subsystem

This subsystem collects and handles fault information, and generates detailed alarm
information in various forms to alert the maintenance engineers.
Alarm generation subsystem includes alarm module in MSC, BAM alarm service
module, alarm console and alarm box, as shown in Figure 1-1.
Alarm module in MSC collects alarm information from other modules and iGWB, and
sends them to BAM.
BAM alarm service module is responsible for analyzing, handling and saving all alarm
information (including alarms generated by BAM itself). It will also inform the alarm box
to generate audible and visible alarms, and display detailed alarm information and
troubleshooting suggestions on the alarm console.
Other software
module
MSC
Alarm service
module
Alarm module
Alarm
console
WS
Alarm
box
BAM
Figure 1-1 Alarm Generation Subsystem Structure

Broken lines in the figure represent the connection status of alarm box. Alarm box of
M900/M1800 MSC/SSP/IP can be directly connected with BAM and WS.
Besides alarm box and alarm console, maintenance engineers can also get alarm
information from following approaches:
z
Equipment state panel on workstation
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)
Buzzer sound generated due to fault on power supply board
1.3.2 Reporting of Hardware Alarm Information

All boards in the system can communicate with AMP, and report detection status of the
boards periodically or when abnormality occurs. On detecting status change, AMP will
generate hardware alarm and send it to BAM.
1-7
Technical Manual

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
Figure 1-2 Reporting of Hardware Alarm Information

Reported alarms can be classified into three types according to reporting path.
z
Alarm information of non-main control frame reported through CCMs

(Communication Control Module) HDLC link.
Alarm information of main control frame reported through bus.
Alarm information of clock and power supply reported through GALM serial port.
Alarm information reported through CCM takes advantage of hierarchical and

decentralized communication control of the system:
z
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

1.3.3 Reporting of Software Alarm Information

Software alarm information includes the information of incoordination of signaling
procedure between local office and peer office, circuit status change due to operation
on peer office, failure of service processing, CPU overload, etc.
Software alarm information is generated by Host software, BAM software and iGWB
software.
Alarms generated by Host software modules (signaling processing, call control, etc.)
are sent to alarm module, which will forward them to BAM alarm service module.
Alarms generated by iGWB software are also sent to MSC alarm module firstly and
then to BAM.
Alarms generated by BAM are handled directly by BAM alarm service module.
1.3.4 Alarm Box and Alarm Console

I. Alarm box
Alarm box is a part of the alarm system. It provides users with visible and audible alarm
information
The alarm box provides:
z
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.
Powerful serial communication functions. Collection, display, forwarding and

related handling of alarm information can be implemented via serial port. There
are 7 serial ports on the alarm box: 3 RS232 serial ports and 4 RS422 serial ports.
Up to 5 serial ports can be provided for external connection at one time, with two
rate options (4800bps and 19200bps) available. Alarm box supports connections
with multiple functional modules or entities.
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.
DY5 interface to connect with DY5 alarm box
Simple outlook, visual display, small size and easy installation
For detailed explanation and usage of the alarm box, please refer to Universal Alarm
Box User Manual.
1-9
Technical Manual

II. Alarm console

Alarm box only provides visible and audible alarm level information. Detailed alarm
information can be viewed on the alarm console of WS.
Alarm console is an important maintenance platform. To present the alarm information
timely and correctly to users, the alarm console provides browse, query and
management functions to users, including:
z
Real-time browse and conditional real-time browse of current alarms.
Combination query of certain alarm information and dynamic update of query

result.
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.
Automatic transfer of alarm information to pager so that the responsible person

can handle the alarm in time.
Alarm sound stop, reset and indicator operation of alarm box.
For detailed explanation and operation related to alarm console, please refer to online
help of alarm console.
1.3.5 Alarm Level and Type

I. Alarm type
Alarm report exported by alarm console will contain alarm types indicating alarm
property.
There are three types of alarms: fault alarms, recovery alarms (notification) and event
alarms.
z
Fault alarm: alarm generated due to hardware equipment failure or abnormality of

some important functions.
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.
Event alarm: prompt or failure indication of one-to-one correspondence of fault

and recovery.
II. Alarm level

The alarm level is used to identify the severity of alarms. According to the severity the
alarms are classified into the following four different levels.
z
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

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.4 Performance Measurement

Performance measurement is also called traffic statistics or traffic measurement.
Performance measurement provides the data such as traffic and load of the network.
This data can be used in network planning, design, operation and management for
network optimization, so as to improve network performance.
The M900/M1800 MSC/SSP/IP performance measurement system is used to measure
the objects related to traffic and system operation, such as trunk, switching equipment
and signaling system. It can measure the number of calls, traffic, average seizure time,
Quality of Service (QoS), network status monitoring, and equipment operations.
1.4.1 Structure of Performance Measurement System

Performance measurement system is composed of performance measurement module
in Host software service layer and performance server software module in BAM, as
shown in Figure 1-3. Performance measurement tasks registered by the users in the
WS service maintenance system are sent by BAM to the performance measurement
module on GSPC board via AMP.
Performance measurement module collects performance data including various call
processing information, equipment information and signaling information, and sends
the measurement result directly to BAM.
Performance service module in BAM saves and sorts the result. The user can view the
result stored in BAM through WS connected with BAM.
1-11
Equipment
information
.
.
.
Signaling
processing
Signaling
information
AMP
Performance
service module
Service module
Call processing
information
Maintenance
interface
Call control

Performance measurement module
Technical Manual
BAM
GSPC
Figure 1-3 Structure of Performance Measurement System

The core of performance measurement system is the performance measurement
module, whose structure is the combination of counters and event screening, as shown
in Figure 1-4.
One performance measurement module consists of up to 1500 types counters, which
are organized according to ITU-T recommendation and other relevant international
standards.
Other software
modules of MSC
Event
Counter
Measurement
task
management
Time
management
Event
Performance measurement module
Figure 1-4 Structure of Performance Measurement Module
1-12
BAM
performance
service module
Technical Manual

1.4.2 Types of Performance Measurements

Note:
Performance measurement includes three basic elements: measurement item, measurement object and
measurement time.
1) Measurement item: Values to be collected for certain measurement, such as the number of call
attempts, the number of trunk outgoing call attempts, etc. Measurement item sometimes is also called
measurement entity or measurement index.
2) Measurement object: physical or logic entity involved in the performance measurement, such as the
exchange system, a circuit group, a cell, an office direction, and a destination.
3) Measurement time: time elements involved in performance measurement, such as measurement start
time and end time.
For the convenience of traffic measurement operations, the performance measurement

items are classified according to measurement purposes. Measurement items for the
same measurement purpose form one measurement unit/type. Several measurement
types with similar measurement purpose form a measurement function type. Task
registration of the performance measurement system is organized according to
measurement function types.
The measurement function types of M900/M1800 MSC/SSP/IP performance
measurement system includes:
z
Digital Mobile Switch Traffic Measurement
Traffic Measurement Based on Connection Types
Failure Cause Measurement
Bearer Trunk Traffic Measurement
Trunk Traffic Measurement Based on Office Direction
Destination Traffic Measurement
Destination Distribution Measurement Based on Office Direction
Originating Traffic Distribution & Duration Measurement
Incoming Traffic Distribution & Duration Measurement
QoS Assessment Measurement
Combination Condition-Dependent Object Traffic Measurement
Call Connection Procedure Measurement
MSC Basic Service Traffic Measurement
MSC Special Service Measurement
MSC Basic Table Measurement
VLR Measurement
MSC Common Part Measurement
Signaling Procedure Measurement

1-13
Technical Manual

BSSMAP Measurement
Intelligent Service Measurement
CPH Function Measurement
GPRS Service Measurement
Location Area and Cell Traffic Model Measurement
For performance measurement operation and detailed explanations of measurement

points, please refer to the M900/M1800 MSC/SSP/IP Operation Manual Performance
Measurement.
1.4.3 Functions and Features of Performance Measurement System

I. Multiple measurement items and tasks
z
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.
Support of user-defined measurement items. On the basis of the measurement

items provided by the MSC, the user can define measurement items through
mathematical expressions. Operation numbers of the mathematical expressions
can be constant values, measurement period, or measurement items provided by
the MSC.
II. Multiple input modes of measurement objects available

When selecting measurement object, the user can select "All" or "Object 1, Object
2, " to facility task management.
III. Flexible measurement time, and real-time measurement feature.

z
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.
Supporting the recording period from 1 minute to 24 hours.
After measurement tasks are registered, their measurement period can be

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

IV. Other functions and features

z
Supporting the data dictionary function. Measurement types, measurement items

and measurement objects are described in data dictionary. Maintainability and
expandability are hence ensured.
Providing re-registration mechanism. With the re-registration mechanism, tasks

will not be lost during switchover or re-loading operations. All re-registration
processes are transparent to the user.
Providing self-healing mechanism. For example, if the exchange time changes

greatly, it can make relative recovery after self-check to avoid the suspension of
tasks.
Supporting activating and deactivating of tasks.
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.
1.4.4 Standard Compliance

Performance measurement of M900/M1800 MSC/SSP/IP supports the following
standards and specifications:
z
The measurement of traffic in 8 directions specified by E502.
The measurement of various optional bearer traffic objects (such as trunks,

destination point, office direction).
The measurement of GSM basic services at NSS side specified in GSM 12.04.
The metering measurement of SS7 signaling performance and service efficiency

recommended by ITU E505, Q 752.
Measurement of non-queuing public parts and control parts.
Traffic record measurement for evaluating MSC QoS specified in E502.
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

1.5.1 Structure of Charging System

M900/M1800 MSC/SSP/IP charging system is mainly comprised of the related
modules in MSC and the Charging Gateway (iGWB), as shown in Figure 1-5.
Call
control
module
Billing
Center
iGWB
Bill pool
MSC
WS
MSC/SSP/IP
Charging System
Figure 1-5 Structure of Charging System

Bill information of M900/M1800 MSC/SSP/IP is generated in the call control module,
and saved in the bill pool of GSPC board. Bills in the bill pool are sent to iGWB for
storage.
To ensure safe and quick transfer of the primary bills from MSC to the iGWB, TCP/IP
protocol is employed on the bottom layer between MSC and iGWB, and user-defined
sliding window communication protocol is employed on the application layer for the
communication.
The bills are sent to the iGWB in packets identified with unique packet number. To
ensure the safe transfer, the following functions are available: automatic connection
after network interruption, re-send of packets without acknowledged, and filtering out of
repeated packets.
The iGWB receives the bill packets and performs unpacking and checking. It then
saves the received original bills, sends acknowledgement messages to MSC and
makes relative log records.
Then, the iGWB will process the original bills. The processing procedures include bill
sorting (e.g. into ordinary bills and hot bills) and bill format conversion (binary format is
converted to text format). The processed bills are then stored in different directories
according to classifications.
Bill processing procedure is shown in Figure 1-6.
1-16
Technical Manual

Original bills
Host bill pool
Bill sorting
Bill format
conversion
Final bills
Billing Center
Figure 1-6 Bill Processing Procedure

The iGWB provides FTP/FTAM interface to the Billing Center. It supports the Server or
Client as FTP or the Responder as FTAM, and actively or passively sends the bill to the
Billing Center.
1.5.2 Bill Storage

Original bills and final bills are saved in the disk of the iGWB server.
Original bills: the bills sent by the MSC to the iGWB.
Final bills: the bills provided by iGWB to the Billing Center.
The iGWB first saves the original bills sent from MSC, then perform sorting and format
conversion to form final bills before storing them in certain directories. The following will
introduce the generation, naming rule and storage mode of original and final bill files.
I. Original bill files

Original bills are stored in original bill files according to order. A new file will be created
when the size of an original bill file reaches specified value. The size of an original bill
file can be set, but should not be less than 1MB.
The name format of original bill file is: b00000000.bil ~ b99999999.bil.
The system creates a new directory at time basis and saves the file under the original
or new directory.
For example: D:\BillFront\data\20000505\b0000000002.bil
1-17
Technical Manual

II. Final bill files

Final bills are saved in final bill files according to order and types.
Final bill file is generated according to defined max. interval of file generation and max.
size. Final bills are first saved in a temporary file. The iGWB will generate final bill file
when the time of temporary file exceeds the max. interval of file generation or the size
of temporary file exceeds max. size.
The value ranges of max. interval of file generation and max. size of bill file:
z
Max. size of bill file: 100kB---infinite. But it should not be more than 2M bytes
considering the security when transmitting on WAN.
Max generation interval of bill file: 10s---infinite.
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

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.
1.5.3 Bill Types

M900/M1800 MSC/SSP/IP can serve as GMSC, TMSC, VMSC or SSP. Different types
of bills will be generated for different calls.
Bill types mainly include:
z
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).
Mobile-Originated-Instead (MOI) bill: in the case a non-PPS subscriber calls a

PPS subscriber, and the networking is of Overlay mode, SSP will generate this bill
for the originating MSC (charging the non-PPS subscriber)
Call Forwarding (CFW) bill: bill generated for the called party when the called party
is mobile subscriber in local office and call forwarding occurs.
Call Attempt (ATTEMPT) bill: bill generated for unsuccessful calls.
Short Message Service (SMS) bill: bill generated for short message originating
and terminating services.
IN free call bill: Bill generated for free IN call.
1.5.4 Bill Format

The iGWB can offer bills of binary or text format to the billing center upon requirements.
1-19
Technical Manual

The bill contains the following contents:

z
Utilization of GSM/PLMN resource, such as MSC No., outgoing/incoming trunk

group No.
Use of basic services (based on originating point, destination, date, duration, and
bearer service).
User of supplementary services, such as Call Forwarding.
Subscriber related numbers, such as MSISDN, IMSI, MSRN.
1.6 Routine Maintenance

Through the service maintenance system in WS, routine maintenance and operation
can be implemented on M900/M1800 MSC/SSP/IP.
On receipt of the maintenance commands from service maintenance systems in WS,
BAM will first classify these commands and then send them to different parts of MSC for
processing. The structure of the maintenance system is shown in Figure 1-7.
WS service
maintenance
system
BAM
AMP
NCC
GSPC
CDP
Figure 1-7 Equipment maintenance system

Commands can be classified into three types according to the devices that commands
sent to and the return way of results.
z
Maintenance commands for most devices are processed by AMPs equipment

management module, and the result is returned to BAM.
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.
Maintenance commands for GSPC are sent directly to corresponding

maintenance function module for processing, or be further forwarded to
corresponding function module for processing by this module. It also receives the
commands forwarded by AMP (such as query of GSPC information).
1-20
Technical Manual

According to the purpose, maintenance items of the routine maintenance sub-system

can be classified into the following types:
z
Equipment maintenance and control: equipment status query, board management,

GE16/GETS/GECP management, resource management, SPC management,
etc.
Trunk/signaling management and control: trunk circuit control, signaling

maintenance, etc.
Real-time tracing and query: including tracing & monitoring, connection query, port
signaling tracing, subscriber status tracing, interface tracing, subscriber interface
tracing, etc.
Other maintenance functions: setting of operation parameters and system time,

GCKS management, etc.
1.6.1 Equipment Maintenance and Control

I. Equipment status query
Maintenance engineer can check the configuration, operation and CPU load through
the maintenance system. He can also check the versions of the running software for
the purpose of software updating and troubleshooting.
II. Board management

Board management includes switchover control, board reset, board status query, and
board loading.
1)
Switchover control
Switchover control includes setting switchover mode and active/standby board

immediate switchover control.
z
Setting switchover mode
To increase system reliability, critical parts in M900/M1800 MSC/SSP/IP, such as

GCKS, AMP, CDP, NCC, GSTU, GQSI, BCP, BCC, GSPC and GMHI, are all in dual hot
standby configuration. Two switchover modes are provided for such boards: automatic
switchover and controlled switchover. Their default state (active, standby or
load-sharing) can be set.
Only when the active board fails, will the standby board be automatically started and
enter active state, and the former active board is marked as standby or failed. If a part is
in controlled switchover mode, manual immediate switchover can be implemented via
the man-machine command.
It is not recommended to change the setting of the switchover mode. Modification may
be implemented only when the active/standby board fails, or for testing or other
1-21
Technical Manual

requirements. Generally, the switchover mode should be set as automatic switchover

mode.
z
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)
Board status query
Various board information can be queried, including board status and board type.
4)
Board loading
III. GE16/GETS /GECP management

GE16/GETS management
z
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.
Query E1/T1 status of GE16/GETS boards.
GECP management function

GECP management functions include a serial of operation and maintenance functions
for GECP board, such as query of GECP DIP switch, EC operational parameters,
operational state, self-test result, EC chip availability, and E1 loop-back status,
single-chip EC reset, setting echo cancellation of GECP, GECP EC self-loop test, etc.
IV. Resource management

Resource maintenance operation: such as query of GSPT and GSRC status
Loading GSPT voice files and syntax analyzing module
For special GSPT board, a series of maintenance functions related to loaded signal
tones are provided, such as voice loading, syntax analysis module loading, voice data
reading, voice code query, voice file deleting, channel state displaying, voice memory
query and formatting, etc.
1-22
Technical Manual

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.
Checking SPC status to enable the acknowledgement of SPC.
Suspending SPC without releasing the TS (Time Slot) occupied by the subscriber.
Restoring the suspended SPC.
Stopping SPC and releasing the TS occupied by the subscriber (not deleting from
database).
Restoring the stopped SPC.
1.6.2 Trunk/Signaling Management and Control

I. Circuit control
Circuit control includes operations such as Query, Block, Unblock and Reset
inter-exchange trunk circuits, etc. Circuits can be queried according to the circuit status.
Via the circuit control function, overall information about circuit and resource
occupation and faults can be obtained. Manual interference and handling can be
implemented on abnormal circuits so as to instantly remove the faults.
II. SS7 signaling maintenance

1)
This
SS7 signaling message tracing

function
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)
SS7 signaling link management
SS7 signaling link management includes such operations as disconnection, activation,

management inhibiting, and management enabling of SS7 signaling links.
3)
Query of SS7 signaling related status
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)
TUP and ISUP continuity check

1-23
Technical Manual

Continuity test of speech channels using SS7 signaling can be implemented to judge
the operation status of the speech channels.
5)
SS7 signaling circuit maintenance and control
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
SCCP management can execute a series of operation and maintenance functions,

such as initializing TCAP system resources, GT code testing, SCCP signaling point and
sub-system management.
III. CAS signaling maintenance

1)
CAS signaling message tracing
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)
CAS signaling circuit maintenance and control
The user can unblock, block or reset CAS circuits and query circuit status.
1.6.3 Real-time Tracing and Query

Tracing and query function is the direct graphical operation and maintenance function
provided to users, including equipment status monitoring and message tracing.
I. Equipment status monitoring

Through equipment control panel, configurations of physical racks, frames and boards
can be clearly and directly viewed, and the present status of boards can be obtained.
Detailed information of boards can be viewed via the right-click menu.
II. Message tracing

Message tracing includes subscriber status tracing, interface tracing, subscriber
interface tracing, dynamic connection tracing, TCAP message tracing, SCCP message
tracing, digital trunk tracing and interface message tracing. Real-time and dynamic
tracing can be implemented on the connection process of a subscriber, signaling
messages on standard interfaces, connection processes of trunk circuit, SS7 signaling
link, CAS link, PRA signaling link and port signaling link, status transition, resource
occupation, mutual-control process, code sending, and control information flows.
Tracing information can be saved. Observation reports can be printed according to the
requirement. The system provides two signaling trace & storage modes. One is
signaling message text mode, which is used for the verification, comparison and further
1-24
Technical Manual

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.
1.6.4 VLR Subscriber Management

I. Querying VLR subscriber information
Based on the MSISDN or IMSI of the subscriber, the basic information, basic services,
supplementary services, ECT supplementary services, intelligent network services and
the cell information of subscribers in local MSC can be queried. In additions, the
MSISDN of the subscriber in local area can be queried based on IMSI, and vice versa.
II. Querying VLR subscriber distribution

Based on HLR, or GVDP board, or the location area and prefix of MSISDN or IMSI, the
number of subscribers in local area can be queried.
III. Managing VLR subscribers

The following operations can be performed: Deleting certain VLR subscriber without
notifying HLR. Clearing the current call of certain subscriber forcibly. Setting the
number of available authentication sets of certain subscriber.
1.6.5 Other Maintenance Functions

I. Parameter setting
1)
Load control
Load control is adopted in case of CPU overload or resource congestion. By smoothly

adjusting traffic, system failure caused by overload can be avoided.
M900/M1800 MSC/SSP/IP allows the maintenance engineer to set the CPU overload
thresholds of various modules, query CPU occupancy, set resource equipment
overload thresholds, and query resource occupancy.
1-25
Technical Manual

Note:
Calculation of CPU occupancy:
CPU occupancy = 1
2)
CPU idle time

Period T
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 1: Bills and subscribers in communication will be kept. Subscribers under

connection will be affected. No data and program will be loaded.
Level 2: Bills will be kept. Subscribers in communication and under connection will
be affected. No data and program will be loaded.
be affected. Data will be loaded. No program will be loaded.
be affected. Data and program will be loaded.
3)
Setting backup mode
This is to set the backup mode of the system. Two modes can be adopted: no backup
and normal backup.
II. Setting system time

This function is to set system time during office deployment or correct system time
when it is incorrect.
In normal condition, the function should not be used, otherwise it may affect the
undergoing charging operations and the registered clock services.
M900/M1800 MSC/SSP/IP system operates with the clock of AMP or BAM as the
reference. Once the system time is set, the system will check the time of various SPMs
and WSs once every 5 minutes using the reference time in order to keep the
consistency of time.
III. GCKS management

z
Query of operation status: Query the status of GCKS reference source (including
frequency offset and status) and GCKS error interval.
1-26
Technical Manual
z

Parameter setting: The system administrators can set the GCKS stratum,
phase-locked loop mode, operational mode, reference source, and available
reference sources.
1.7 Software Patching

After the equipment is put into service, some modifications may be needed for the
software. In this case, software patching is useful, which realizes software upgrading
without affecting the normal service of the system.
1.7.1 Basic Concepts

Patch: a segment of executive codes used for replacing the corresponding codes in the
system which are erroneous or required to be updated.
Patch No.: Multiple errors may be found during system operation, therefore, multiple
patches are required. These patches are numbered according to the sequence of
creation time, this number is called patch number.
Patch area: a space in the system memory reserved specially for patches.
General patch: aims to solve the problems common to all users using the same basic
version.
Special patch: aims to solve the problems specific to certain users.
Patch file: all the patch files for the same basic version.
1.7.2 Features of Software Patch

Software patches features follows:
1)
It is based on certain software version
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)
Several patches constitute a patch file
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

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
Software patching operation can be executed through MML commands in system

running status.
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.
1.7.3 Structure of Software Patching System

Software patching system includes three parts: patch creation tools, BAM patch
management module and MSC patch management module.
1)
Patch creation tools
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
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.
Sending patch file to MSC.
Creating corresponding patch report file.
3)
MSC patch management module
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

Receiving patch file, isolating patch and sending it to patch area;
Writing patch file to Flash memory.
Patch restoration after system restart.
Patching synchronization of active/standby CPU.
1.7.4 Software Patching Operation

Users can add or remove software patch online with corresponding commands.
There are total 4 patch states, including Idle state, Deactivated state, Activated state
and Running state.
z
Idle state: initial state, indicating there is no patch.
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.
Transition of states is shown in Figure 1-8.

LOAD
Idle state
Deactivated
state
RMV
RMV
Running state
ACT
RMV
RUN
DEA
Activated state
Figure 1-8 Transition of Patch States

Activated state is a temporary state (trial running). After a period of trial running, if it
proves to be normal, activated state can be transited to running state with command
CFM PATCH. If error is found, this patch can be deactivated with command DEA
PATCH.
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

1.8 System Testing

To ensure the long-term, continuous and stable operation of the system, test and
diagnosis function for fault maintenance and preventive maintenance is dispensable to
the whole system.
M900/M1800 MSC/SSP/IP provides powerful test and diagnosis function. On the one
hand, each intelligent board equipped with self-test function. In the operation of the
equipment, each intelligent board performs real-time self-test, and automatically gives
alarms or performs switchover in case of error or fault. On the other hand, commands
can be sent to the Host from the test subsystem to test and measure the specified
device.
The test subsystem is a key part in the terminal maintenance and operation system,
which is responsible for testing and measuring the hardware and software of
M900/M1800 MSC/SSP/IP. According to measurement objects, the functions of the
test subsystem include:
z
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.
Test of LIM frame signaling HWs.
The structure of the test system is shown in Figure 1-9.

User sends the man-machine command to the test server in BAM through WS service
maintenance system.
The test server creates test tasks according to the commands received from WSs and
sends test instructions to the MSC. Then the latter sends corresponding test
commands to the corresponding devices to execute the tasks. After the task is
completed, the results are returned to the test server, which will store the results, make
analysis and statistics. Then it sends the processed result to the Client.
1-30
Technical Manual

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
BAM Test Server
Figure 1-9 Structure of test system

1)
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)
Parallel test control
1-31
Technical Manual

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.9 Task Management

To enable the user to implement various operation & maintenance via MML commands,
the service maintenance system provides the functions of scheduled task management,
batch task management and macro. Thus, the user can create a one-command task by
combining several commands, and implement the task immediately or at specified
time.
1.9.1 Scheduled Task Management

Scheduled task management enables the automatic execution of MML command. The
system will execute one or a batch of MML commands automatically at certain time,
thus greatly simplifying the maintenance of the system. A scheduled task consists of
multiple subtasks. Each subtask is specified by its time attribute and several MML
command strings. The time can be a fixed time, or a fixed time every day/week/month,
or several time points of certain days in a week/month.
1.9.2 Batch Command

Batch command refers to the function that the system executes all the MML commands
in a command script file according to the command sequence specified. The command
script file is a text file containing multiple MML commands. To enable the user to
execute batch command more efficiently, the system also provides debugging function
for it. The user can debug the command script by executing the batch file step by step,
or executing to specified line or executing to the place where MML command error
1-32
Technical Manual

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
Technical Manual
Appendix
Technical Manual
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
Appendix
Appendix A Standard Compliance

This section describes the international technical standards observed by M900/M1800
MSC/SSP/IP. The manufacturing standards observed are not included in this part.
A.1 ITU-T Recommendations

E.502 (06/92)
Traffic measurement requirements for digital telecommunication
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
Appendix
Q.713 (07/96) Signaling Connection Control part formats and codes

Q.714 (07/96) Signaling connection control part procedures
Q.715 (07/96) Signaling connection control part user guide
Q.716 (03/93)
Signaling System No.7-Signaling connection control part (SCCP)
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
Appendix
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)
Network element information model for SCCP accounting and
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)
Guidebook to Operations, Maintenance and Administration Part
(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)
Performance objectives in the integrated services digital network
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
Appendix
Q.781 (07/96) MTP level 2 test specification

Q.782 (07/96) MTP level 3 test specification
Q.783 (11/88) TUP test specification
Q.784 Annex A (03/93) TTCN version of Recommendation Q.784
Q.784.1 (07/96) ISUP basic call test specification: Validation and compatibility for
ISUP'92 and Q.767 protocols
Q.784.2 (06/97) ISUP basic call test specification: Abstract test suite for ISUP'92 basic
call control procedures
Q.785 (09/91) ISUP protocol test specification for supplementary services
Q.785.2 (03/99) Abstract test suite for ISUP'97 supplementary services
Q.786 (03/93) SCCP test specification
Q.787 (09/97) Transaction Capabilities (TC) test specification
Q.788 (06/97) User-network-interface to user-network-interface compatibility test
specifications for ISDN, non-ISDN and undetermined accesses interwoking over
international ISUP
Q.850 (05/98) Usage of cause and location in the Digital Subscriber Signaling System
No.7 ISDN User part
Q.920 (03/93) ISDN user-network interface data link layer - General aspects
Q.921 (09/97) ISDN user-network interface - Data link layer specification
Q.922 (02/92) ISDN data link layer specification for frame mode bearer services
Q.923 (02/95) Specification of a synchronization and coordination function for the
provision of the OSI connection-mode network service in an ISDN
Q.930 (03/93) ISDN user-network interface layer 3-General aspects
Q.931 (05/98) ISDN user-network interface layer 3 specification for basic call control
Q.932 (05/98) Digital Subscriber Signaling System No.1 - Generic procedures for the
control of ISDN supplementary services
Q.939 (03/93) Typical DSS1 service indicator codings for ISDN telecommunications
services
Q.940 (11/88)
ISDN user-network interface protocol for management - General
aspects
Q.941 (03/93) ISDN user-network interface protocol profile for management
A-4
Technical Manual
Appendix
Q.950 (06/97) Supplementary protocols, structure and general principles

Q.951.1 (02/92) Direct-dialing-in (DDI)
Q.951.2 (02/92) Multiple subscriber number (MSN)
Q.951.3 (03/93) Calling line identification presentation
Q.951.4 (03/93) Calling line identification restriction
Q.951.5 (03/93) Connected line identification presentation
Q.951.6 (03/93) Connected line identification restriction
Q.951.7 (06/97) Malicious Call Identification (MCID)
Q.951.8 (02/92) Sub-addressing (SUB)
Q.1000 (11/88) Structure of the Q.1000-Series Recommendations for public land
mobile networks
Q.1001 (11/88) Genera aspects of public land mobile networks
Q.1002 (11/88) Network functions
Q.1003 (11/88) Location registration procedures
Q.1004 (11/88) Location register restoration procedures
Q.1005 (11/88) Handover procedures
Q.1031 (11/88) General signaling requirements on interworking between the ISDN or
PSTN and the PLMN
Q.1032 (11/88) Signaling requirements relating to routing of calls to mobile subscribers
Q.1061 (11/88)
General aspects and principles relating to digital PLMN access
signaling reference points

Q.1062 (11/88) Digital PLMN access signaling reference configurations
Q.1036 (11/88) Digital PLMN channel structures and access capabilities at the radio
interface (Um reference point)
Q.1200 (09/97) General series Intelligent Network Recommendation structure
Q.1201/I.312 (10/92) Principles of intelligent network architecture
Q.1202/I.328 (09/97) Intelligent network - Service plane architecture
Q.1203/I.329 (09/97) Intelligent network - Global functional plane architecture
Q.1204 (03/93) Intelligent network distributed functional plane architecture
Q.1205 (03/93) Intelligent network physical plane architecture
A-5
Technical Manual
Appendix
Q.1208 (09/97) General aspects of the Intelligent Network Application protocol

Q.1210 (10/95) Q.1210-series Intelligent network Recommendation structure
Q.1211 (03/93) Introduction to intelligent network capability set1
Q.1213 (10/95) Global functional plane for intelligent network CS-1
Q.1214 (10/95) Distributed functional plane for intelligent network CS-1
Q.1218 (10/95) Interface Recommendation for intelligent network CS-1
Q.1219 (04/94) Intelligent network user's guide for capability set 1
Q.1220 (09/97) Q.1220-series Intelligent Network Capability Set 2 Recommendation
structure
Q.1221 (09/97) Introduction to Intelligent Network Capability Set 2
Q.1222 (09/97) Service plane for Intelligent Network Capability Set 2
Q.1223 (09/97) Global functional plane for Intelligent Network Capability Set 2
Q.1224 (09/97) Distributed functional plane for intelligent network Capability Set 2
Q.1225 (09/97) Physical plane for Intelligent Network Capability Set 2
Q.1228 (09/97) Interface Recommendation for intelligent network Capability set 2
Q.1229 (03/99) Intelligent Network user's guide for capability set 2
Q.1290 (05/98) Glossary of terms used in the definition of intelligent networks
X.208 (11/88) Specification of Abstract Syntax Notation One (ASN.1)
X.209 (11/88) Specification of basic encoding rules for Abstract Syntax Notation One
(ASN.1)
X.219 (11/88) Remote operations: Model, notation and service definition
X.229 (11/88) Remote operations: Protocol specification
A.2 ETSI Specifications

GSM 01 Series
GSM01.04: "Digital cellular telecommunications system (Phase2+); Abbreviations and
acronyms"
GSM 02 Series
A-6
Technical Manual
Appendix
GSM02.01: "Digital cellular telecommunications system (Phase 2); Principles of

telecommunication services supported by a GSM Public Land Mobile Network
(PLMN)".
GSM02.02: "Digital cellular telecommunications system (Phase 2); Bearer Services
(BS) supported by a GSM Public Land Mobile Network (PLMN)".
GSM02.03: "Digital cellular telecommunications system (Phase 2); Teleservices
supported by a GSM Public Land Mobile Network (PLMN)".
GSM02.04: "Digital cellular telecommunications system (Phase 2); General on
supplementary services".
GSM02.09: "Digital cellular telecommunications system (Phase 2); Security aspects".
GSM02.11: "Digital cellular telecommunications system (Phase 2);
Service
accessibility".
GSM02.24: "Digital cellular telecommunications system (Phase2);
Description of
Charge Advice Information (CAI)".

GSM02.40: "Digital cellular telecommunication system (Phase 2); Procedures for call
progress indications".
GSM02.41:
"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)
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)
GSM02.85: "Digital cellular telecommunication system (Phase 2); Closed User Group
(CUG) supplementary services - Stage 1".
A-7
Technical Manual
Appendix
GSM02.86: "Digital cellular telecommunication system (Phase 2); Advice of charge

(AoC) supplementary services - Stage 1".
GSM02.88: "Digital cellular telecommunication system (Phase 2); Call Barring (CB)
GSM02.90: "Digital cellular telecommunication system (Phase2+); "Stage 1 description
of Unstructured Supplementary Service Data (USSD)".
GSM 03 Series
GSM03.01: "Digital cellular telecommunication system (Phase 2); Network functions".
GSM03.02:
"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".
of operator determined barring".
GSM03.16: "Digital cellular telecommunication system (Phase 2); "Subscriber data
management - Stage 2".
A-8
Technical Manual
Appendix
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)".
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)".
realization of facsimile group 3 transparent".
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
A-9
Technical Manual
Appendix
GSM03.82: "Digital cellular telecommunication system (Phase 2); Call Forwarding (CF)
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)
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)
GSM03.88: "Digital cellular telecommunication system (Phase 2); Call Barring (CB)
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
Appendix
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".
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)"
interworking for supplementary services".
A-11
Technical Manual
Appendix
GSM09.14 "Integrated Services Digital Network (ISDN); Signaling System No.7;

telecommunication system (Phase2+); Application of ISDN User Part (ISUP) version 3
for the ISDN - Public Land Mobile Network (PLMN) Signaling interface; Part 1: Protocol
Specification".
GSM09.16: "Digital cellular telecommunication system (Phase 2+); General Packet
Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitor Location
Register (VLR); Gs Interface network service specification".
GSM09.18: "Digital cellular telecommunication system (Phase 2+); General Packet
Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitor Location
Register (VLR); Gs Interface layer 3 specification".
GSM09.78: "Digital cellular telecommunication system (Phase 2+); Customized
Application for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part
(CAP) specification".
GSM 12 Series
GSM 12.00: "Digital cellular telecommunications system (Phase 2); Objectives and
structure of Network Management (NM)".
GSM 12.01: "Digital cellular telecommunications system (Phase 2); Common aspects
of GSM Network Management (NM)".
GSM 12.07: "Digital cellular telecommunications system (Phase 2); Operations and
performance management".
GSM 12.02: "Digital cellular telecommunications system (Phase 2); Subscriber, Mobile
Equipment (ME) and services data administration".
GSM 12.03: "Digital cellular telecommunications system (Phase 2); Security
management".
GSM 12.04: "Digital cellular telecommunications system (Phase 2); Performance data
measurements".
GSM 12.05: "Digital cellular telecommunications system (Phase 2); Subscriber related
event and call data".
GSM 12.06: "Digital cellular telecommunications system (Phase 2); GSM Network
change control".
GSM 12.13: "Digital cellular telecommunications system (Phase 2); Maintenance of the
Mobile-services Switching Center (MSC)".
GSM 12.14: "Digital cellular telecommunications system (Phase 2); Maintenance of
location registers".
A-12
Technical Manual
Appendix
GSM 12.20: "Digital cellular telecommunications system (Phase 2); Network

Management (NM) procedures and messages".
A-13
Technical Manual
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.
Foreground/Background communication usually refers to the communication between

BAM and AMP of the AM cabinet.
B-1
Technical Manual
Appendix
Appendix C Abbreviations and Acronyms

A
A-interface
A3
Authentication algorithm A3
A5/1
Encryption algorithm A5/1
A5/2
Encryption algorithm A5/2
AC
Application Context
ACM
Accumulated Call Meter
ACM
Address Complete Message
ACMM
Accumulated Call Meter Max
ADI
Address Incomplete signal
ADM
Add / Drop Multiplexer
AE
Application Entity
AM /CM
Administration Module/ Communication Module
AMP
Administration Maintenance Processor
ANC
Answer signal, Charge
ANN
Answer signal, No charge
ANU
Answer signal, Unqualified
AoCC
Advice of Charge Charging
AoCI
Advice of Charge Information
ASE
Application Service Element
ASN.1
Abstract Syntax Notation One
AU
Access Unit
AuC
Authentication Centre
B
B-interface
BAIC
Barring of all Incoming Calls
BAOC
Barring of all Outgoing Calls
BAM
Back Administration Module
BCC
Bus Control CPC
C-1
Technical Manual
Appendix
BCD
Binary Coded Decimal
BCP
Bus Control Processor
BCIE
Bearer Capability Information Element
BCM
Basic Call Manager
BCSM
Basic Call State Model
BHCA
Busy Hour Calling Attempt
BI
all Barring of Incoming call supplementary service
BIC-Roam
Barring of Incoming Calls when Roaming outside the home PLMN country
BO
all Barring of Outgoing call supplementary service
BOIC
Barring of Outgoing International Calls supplementary service
BOIC-exHC
Barring of Outgoing International Calls except those directed to the Home

PLMN Country
BS
Basic Service (group)
BS
Bearer Service
BSG
Basic Service Group
BSC
Base Station Controller
BSM
Backward Setup Message
BSS
Base Station System
BSSAP
Base Station System Application Part
BSSMAP
Base Station System Management Application Part
BTS
Base Transceiver Station
C
C-interface
CA
Cell Allocation
CAI
Charge Advice Information
CAMEL
Customized Applications for Mobile Network Enhanced Logic
CAP
CAMEL Application Part
CBK
Clear BacK signal
CC
Country Code
CC
Call Control
CCBS
Completion of Calls to Busy Subscriber supplementary service
CCF
Conditional Call Forwarding
CCF
Call Control Function
C-2
Technical Manual
Appendix
CCM
Communication & Control Module
CDB
Center DataBase
CDP
Central Database Processor
CF
All Call Forwarding services
CFB
Call Forwarding on mobile subscriber Busy
CFNRc
Call Forwarding on mobile subscriber Not Reachable
CFNRy
Call Forwarding on No Reply
CFL
Call FaiLure signal
CFU
Call Forwarding Unconditional
CGC
Circuit Group Congestion signal
CI
Cell Identity
CI
CUG Index
CKM
ClocK Module
CKSN
Ciphering Key Sequence Number
CKV
Clock Driver
CLF
CLear Forward signal
CLI
Calling Line Identity
CLIP
Calling Line Identification Presentation supplementary service
CLIR
Calling Line Identification Restriction supplementary service
CM
Connection Management
Connection Module
CM
Call Manager
CNET
Central Network transfer and switch
COLI
COnnected Line Identification
COLP
COnnected Line identification Presentation supplementary service
COLR
COnnected Line identification Restriction supplementary service
CONNACK
CONNect Acknowledgement
COT
Continuity signal
CPM
Central Process Module
CSD
Circuit Switch Data-service
CSM
Call Supervision Message
CUG
Closed User Group
CW
Call Waiting
C-3
Technical Manual
Appendix
D
D-interface
DB
DataBase
DET
DETach
DISC
DISConnect
DP
Detection Point
DPC
Destination Point Code
DSS1
Digital Subscriber Signaling No.1
DTR
Dual Tone Transceiver
E
E-interface
EC
Echo Canceller
ECI
Echo Canceller Interface
EIR
Equipment Identity Register
ETS
European Telecommunication Standard
ETSI
European Telecommunications Standards Institute
F
F-interface
FAM
Front Administrative Module
FAM
Forward Address Message
FCS
Frame Check Sequence
FEAM
Function Entity Access Manager
FIM
Feature Interactions Manager
FN
Frame Number
FR
Full Rate
FSM
Forward Setup Message
FSM
Finite State Machine
FTC
Full Rate Transcoder
Ftn
forwarded-to number
C-4
Technical Manual
Appendix
GALM
GSM Alarm board
GAMD
GSM Alarm Machine Driver
GBAC
GSM Bus Administration & Configuration
GBDR
GSM Bus Driver
GCDI
GSM Circuit Data-service Interface
GCKD
GSM Clock Driver
GCKS
GSM Clock Synchronize board
GCTN
GSM Central T-Network board
GCNU
GSM Central Network Unit
GCPC
GSM Center Processor Cell
GE16
GSM Sixteen E1 interface board
GECP
GSM Echo Canceller Pool
GECS
GSM Echo Canceller with Sixteen E1 trunks
GFSN
GSM Frame Switch Net
GGSN
Gateway GPRS Support Node
GHN7
High-speed No.7 link process
G-interface
G/IW MSC
Gateway/Interworking MSC
GMHI
GSM Multi_Highway Interface
GRQ
General ReQuest message
GMSC
Gateway Mobile-services Switching Center
GPWS
GSM Power System
GQSI
GSM Quick Signal Interface board
GSNU
GSM Suburb Net Unit
GSPC
GSM Service Processor Cell
GSPT
GSM Speech and Tone
GSRC
GSM Shared Resources Card
GSTU
GSM Synchronous Transport Unit
GSM,
GSM900,
GSM1800
Global System for Mobile communications
gsmSCF
GSM Service Control Function
gsmSRF
GSM Specialized Resource Function
gsmSSF
GSM Service Switching Function
GT
Global Title
C-5
Technical Manual
Appendix
GUI
Graphic User Interface
GVDP
GSM Visitor Location Register Data Processor
H
HDB
HLR DataBase
HDLC
High Data Link Control
HLC
High layer Compatibility
HLR
Home Location Register
HO
HandOver
HOLD
Call Hold
HOFL
High Optic Fiber Link
HPLMN
Home PLMN
HR
Half Rate
HW
High Way
HWC
High Way Converter
I
IAM
Initial Address Message
IAI
Initial Address Message with Information
IC
Interlock Code (CUG SS)
ICB
Incoming Calls Barred (within the CUG)
ID
IDentification / IDentity
iGWB
iGateway Bill
IMEI
International Mobile station Equipment Identity
IMM
Integrated Management Module
IMSI
International Mobile Subscriber Identity
IN
Intelligent Network
IN-SM
IN-Switching Manager
ISDN
Integrated Services Digital Network
IP
Intelligent Peripheral
ITU-T
ITU Telecommunication Standardization Sector
ISUP
ISDN User Part (of signalling system No.7)
IWC
IWF Controller
C-6
Technical Manual
Appendix
IWF
Interworking Function
IWMSC
InterWorking MSC
IWU
InterWorking Unit
K
Kc
Ciphering key
Ki
Individual subscriber authentication key
L
L1
Layer 1
L2ML
Layer 2 Management Link
L2R
Layer 2 Relay
L3
Layer 3
LA
Location Area
LAC
Location Area Code
LAI
Location Area Identity
LAN
Local Area Network
LAN Switch
Local Area Network Switch
LAP
Link Access Protocol
LAPD
Link Access Procedure on the D-Channel
LIM
Line Interface Module
LLC
Low Layer Compatibility
LPLMN
Location PLMN
M
MAP
Mobile Application Part
MCC
Mobile Country Code
MM
Mobility Management
MML
Man Machine Language
MNC
Mobile Network Code
MO
Mobile Originated
MoU
Memorandum of Understanding
MPTY
Multi Party Service
C-7
Technical Manual
Appendix
MS
Mobile Station
MSC
Mobile services Switching Center, Mobile Switching Center
MSC-A
The controlling MSC on which the call was originally established
MSC-B
The MSC to which the ms is handed over in a basic Handover
MSC-B
The MSC to which the ms is handed over in a subsequent Handover
MSISDN
Mobile Station International ISDN Number
MSM
MSC Subrate channel Multiplexer
MSRN
Mobile Station Roaming Number
MT
Mobile Terminated
MTP
Message Transfer Part
MVPN
Mobile Virtual Private Network
N
NCC
Net Communication CPC
NDUB
Network Determined User Busy
NE
Network Equipment
NF
Network Function
NM
Network Management
NMC
Network Management Center
O
ODB
Operator Determined Barring
OET
Optical-Electrical Transformer
OFL
Optic Fiber Link
O&M, OM
Operations & Maintenance
OMAP
Operation and Maintenance Application Part
OMC
Operations & Maintenance Center
OMU
Operations & Maintenance Unit
OOP
Object Oriented Programming
OPC
Origination Point Code
OPT
Optic Interface board
OSI
Open System Interconnection
C-8
Technical Manual
Appendix
P
PABX
Private Automatic Branch Exchange
PCH
Paging Channel
PCM
Pulse Code Modulate
PCU
Packet Control Unit
PH
Packet Handler
PIC
Point in Call
PLMN
PPS
PrePaid Service
PRI
Primary Rate Interface
PSPDN
Packet Switched Public Data Network
PS
PassWord
PSTN
Public Switched Telephone Network
PWC
GSM Power Control board
Q
QoS
Quality of Service
R
RBT
(Customized) Ring Back Tone
RAND
RANDom number(used for authentication)
REJ
REJect (ion)
REL
RELease
REQ
REQuest
RLP
Radio Link Protocol
RLG
ReLease Guard signal
RR
Radio Resource
RSC
ReSet Circuit signal
RSZI
Regional Subscription Zone Identity
S
SAP
Service Access Point
SAM
Subsequent Address Message
C-9
Technical Manual
Appendix
SAO
Subsequent Address Message with One signal
SC
Service Center (used for SMS)
SC
Service Code
SCCP
Signaling Connection Control Part
SCE
Service Creation Environment
SCF
Service Control Function
SCP
Service Control Point
SDF
Service Data Function
SDH
Synchronous Digital Hierarchy
SDP
Service Data Point
SLB
Subscriber Local Busy signal
SLPI
Service Logic Processing Instance
SM
Switching Module
SMAF
Service Management Access Function
SMAP
Service Management Access Point
SMC
Short Message Center
SMF
Service Management Function
SMP
Service Management Point
SMS
Short Message Service
SMS
Service Management System
SMSCB
Short Message Service Cell Broadcast
SN
Subscriber Number
SPC
Signaling Point Code
SPLIM
Service Processing and Line Interface Module
SPM
Service Process Module
SOA
Suppress Outgoing Access (CUG SS)
SRF
Specialized Resource Function
SRM
Specialized Resource Module
SRME
Specialized Resource Management Entity
SRSM
Specialized Resource State Machine
SS
Supplementary Service
SSF
Service Switching Function
SSP
Service Switching Point
SS7
Signalling System No.7
C-10
Technical Manual
Appendix
SSME
Service Switching Management Entity
STB
Subscriber Toll Busy signal
STM
Synchronous Transfer Mode
STP
Signalling Transfer Point
T
TC
Transcoder
TCAP
Transaction Capability Application Part
TCSM
Transcoder and SubMultiplexer
TMSI
Temporary Mobile Subscriber Identity
TRAU
Transcoder & Rate Adapter Unit
TUP
Telephone User Part (SS7)
U
UI Client
Um
USSD
Unstructured Supplementary Service Data
V
VDB
VLR DataBase
VLR
Visitor Location Register
VM
Voice Mailbox
VMSC
Visited MSC
VPLMN
Visited PLMN
W
WAD
Wireless Advertisement
WAN
Wide Area Network
WAP
Wireless Application Protocol
WS
Work Station
WSS
Work Station Server
C-11

Technical - Manual MSC M1800 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical - Manual MSC M1800 PDF

Uploaded by

Copyright:

Available Formats

System Description

Table of Contents .........................................................................................

2.16.6 Signaling Interworking ............................................................

5.3.1 Principle of Load Control ..........................................................

1.2.3 Resource Sharing and Centralized Management.....................

5.2 AC Power Supply System .................................................................

2.6 Equipment Management ...................................................................

1.2.8 Unstructured Supplementary Service .......................................

3.3.3 Register Signaling ....................................................................

2.2 WIN in OVERLAY Mode ...................................................................

Operation and Maintenance Functions

1.1.2 Management of User Account ..................................................

Appendix A Standard Compliance ...............................................................

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

About This Manual

Module 1 System Description

Module 2 Hardware Architecture

Module 3 Software Architecture

Module 4 MSC Functions

Module 5 SSP Functions

focuses on the Wireless Intelligent Network (WIN) features, network functions,

Module 6 Operation and Maintenance Functions

Installation engineers & technicians

Operation & maintenance personnel

Normal paragraphs are in Arial.

Warnings, Cautions, Notes and Tips are in Arial Narrow.

Headings are in Boldface.

Terminal Display is in Courier New.

II. Command conventions

The keywords of a command line are in Boldface.

Command arguments are in italic.

Items (keywords or arguments) in square brackets [ ] are optional.

Alternative items are grouped in braces and separated by vertical bars.

Optional alternative items are grouped in square brackets and separated

Alternative items are grouped in braces and separated by vertical bars. A

Optional alternative items are grouped in square brackets and separated

III. GUI conventions

Multi-level menus are separated by forward slashes. For example,

IV. Keyboard operation

Press the left button twice continuously and quickly.

Caution, Warning, Danger: Means reader be extremely careful during the

5.3.2 Measures of Load Control....................................................................................... 5-8

1.1 Mobile Network Where M900/M1800 MSC/SSP/IP Resides

AUC: Authentication Centre

BSC: Base Station Controller

Figure 1-1 M900/M1800 MSC/SSP/IP in GSM network

Mobile Switching Center (MSC)

Service Switching Point/Intelligent Peripheral(SSP/IP)

Home Location Register (HLR)

Authentication Center (AuC)

Equipment Identity Register (EIR)

Serving GPRS Support Node (SGSN)

SGSN is responsible for MSs access control, mobility management, session

Gateway GPRS Support Node (GGSN)

Service Control Point (SCP)

Base Station Controller (BSC)

Base Transceiver Station (BTS)

BTS is controlled by BSC. It is responsible for radio connection. It performs functions