Traffic Statistic Manual

Chapter 1 Overview
1.1 Brief Introduction .................................................................................... 1-1

1.2 Contents and Principles of Traffic Statistics ........................................... 1-1
1.3 Concept of Traffic Statistics .................................................................... 1-3
1.3.1 Traffic Statistics Task ..................................................................... 1-3
1.3.2 Index Property ................................................................................ 1-4
1.3.3 Task Object Property ..................................................................... 1-5
1.3.4 Task Time Property........................................................................ 1-5
1.3.5 Measurement task status ............................................................... 1-6
1.4 Feature of Traffic Statistics..................................................................... 1-7
Chapter 2 Operation of Traffic Statistics
2.1 Overview ................................................................................................ 2-1
2.1.1 Brief Introduction ............................................................................ 2-1
2.1.2 Brief Introduction to Traffic statistics Operation ............................. 2-2
2.1.3 Logging in BSC Traffic Statistics System....................................... 2-3
2.1.4 Logging in Traffic Statistics Report System ................................... 2-5
2.2 Points for Attention ................................................................................. 2-6
2.3 Creating Traffic Statistics Task............................................................... 2-8
2.4 Modifying Traffic Statistics Task ............................................................. 2-20
2.4.1 Modifying Task Name .................................................................... 2-21
2.4.2 Modifying Permanent Task Period ................................................. 2-22
2.4.3 Modifying Task Configuration Information ..................................... 2-22
2.5 Halting/Activating Measurement Task .................................................... 2-24
2.5.1 Halting task .................................................................................... 2-24
2.5.2 Activating task ................................................................................ 2-24
2.6 Refreshing Task List ............................................................................... 2-25
2.7 Querying Traffic Statistics Task .............................................................. 2-25
2.7.1 Querying Task Status .................................................................... 2-25
2.7.2 Querying Detailed Information of Task .......................................... 2-26
2.7.3 Querying Backup of Detailed Task Information ............................. 2-27
2.8 Querying Measurement Result............................................................... 2-28
2.9 Deleting Traffic Statistics Task ............................................................... 2-38
2.9.1 Deleting Task ................................................................................. 2-38
2.9.2 Deleting Backup Task .................................................................... 2-39
2.10 Template Management ........................................................................ 2-39
2.10.1 Creating Item Template ............................................................... 2-39
2.10.2 Creating Time Template .............................................................. 2-41
2.10.3 Creating Object Template ............................................................ 2-41
2.11 Customizing Item .................................................................................. 2-41
2.12 Refreshing All Templates ..................................................................... 2-45
2.13 Other Operations .................................................................................. 2-45
2.13.1 Setting shortcut buttons in the Result Window ............................ 2-45
2.13.2 Customizing Setting ..................................................................... 2-46
Chapter 3 Traffic Statistic Items
3.1 BSC measurement function ................................................................... 3-1
3.1.1 General .......................................................................................... 3-1
3.1.2 Statistic Items................................................................................. 3-4
3.2 SCCP Measurement Function ................................................................ 3-82
3.2.1 General .......................................................................................... 3-82
3.2.2 Statistic items ................................................................................. 3-83
3.3 A-interface Operation and Management Statistic ................................... 3-89
3.3.1 General .......................................................................................... 3-89
3.3.2 Statistic Items................................................................................. 3-90
3.4 A-interface Equipment Maintenance Statistic ......................................... 3-94
3.4.1 General .......................................................................................... 3-94
3.4.2 Statistic Items................................................................................. 3-94
3.5 A-interface Trunk Board Message Statistic ............................................ 3-96
3.5.1 General .......................................................................................... 3-96
3.5.2 Statistic Items................................................................................. 3-97
3.6 CPU Measurement Function .................................................................. 3-98
3.6.1 General .......................................................................................... 3-98
3.6.2 Statistic Items................................................................................. 3-99
3.7 BSC Cell Broadcast Measurement......................................................... 3-100
3.7.1 General .......................................................................................... 3-100
3.7.2 Statistic Items................................................................................. 3-101
3.8 MTP Measurement Function .................................................................. 3-110
3.8.1 General .......................................................................................... 3-110
3.8.2 Statistic Items................................................................................. 3-110
3.9 Cell Measurement Function ................................................................... 3-115
3.9.1 SDCCH Measurement Function .................................................... 3-116
3.9.2 TCH Measurement Function .......................................................... 3-132
3.9.3 Random Access Measurement Function ....................................... 3-166
3.9.4 Inter-cell Handover Measurement Function ................................... 3-172
3.9.5 Intra-cell Handover Measurement Function ................................... 3-218
3.9.6 Other Measurement Function ........................................................ 3-226
3.10 Power Control Measurement ................................................................ 3-236
3.10.1 General ........................................................................................ 3-236
3.10.2 Statistic Items ............................................................................... 3-236
3.11 Call Drop Measurement ....................................................................... 3-240
3.11.1 General ........................................................................................ 3-240
3.11.2 Statistic Items ............................................................................... 3-241
3.12 SITE Initial Measurement Function ...................................................... 3-243
3.12.1 General ........................................................................................ 3-243
3.12.2 Statistic Items ............................................................................... 3-244
3.13 BTS Initial Measurement Function ....................................................... 3-246
3.13.1 General ........................................................................................ 3-246
3.13.2 Statistic Items ............................................................................... 3-247
3.14 Cell Broadcast Statistic ........................................................................ 3-249
3.14.1 General ........................................................................................ 3-249
3.14.2 Statistic Items ............................................................................... 3-250
3.15 Outgoing Inter Cell Handover Measurement Function ......................... 3-250
3.15.1 General ........................................................................................ 3-250
3.15.2 Statistic Items ............................................................................... 3-252
3.16 Incoming Inter Cell Handover Measurement Function ......................... 3-278
3.16.1 General ........................................................................................ 3-278
3.16.2 Statistic Items ............................................................................... 3-279
3.17 Undefined Adjacent Cell Measurement Function ................................. 3-282
3.17.1 General ........................................................................................ 3-282
3.17.2 Statistic Items ............................................................................... 3-283
3.18 Defined Adjacent Cell Measurement Function ..................................... 3-285
3.18.1 General ........................................................................................ 3-285
3.18.2 Statistic Items ............................................................................... 3-285
3.19 Receiving Quality Measurement .......................................................... 3-287
3.19.1 General ........................................................................................ 3-287
3.19.2 Statistic items ............................................................................... 3-288
3.20 Receiving Level Measurement Function .............................................. 3-291
3.20.1 General ........................................................................................ 3-291
3.20.2 Statistic Items ............................................................................... 3-294
3.21 Up-Down Link Balance Measurement Function ................................... 3-310
3.21.1 General ........................................................................................ 3-310
3.21.2 Statistic Items ............................................................................... 3-311
3.22 LAPD Link Measurement Function ....................................................... 3-313
3.22.1 General ........................................................................................ 3-313
3.22.2 Statistic Items ............................................................................... 3-314
3.23 Channel Allocation Measurement Function.......................................... 3-324
3.23.1 SDCCH Allocation Measurement Function .................................. 3-324
3.23.2 TCH Allocation Measurement Function ....................................... 3-331
3.24 Cell Flow Control Measurement Function ............................................ 3-338
3.24.1 General ........................................................................................ 3-338
3.24.2 Statistic Items ............................................................................... 3-338
3.25 GPRS Related Measurement Function ................................................ 3-341
3.25.1 General ........................................................................................ 3-341
3.25.2 Statistic Items ............................................................................... 3-342
3.26 Overlaid/Underlaid Subcell Measurement ............................................ 3-345
3.26.1 General ........................................................................................ 3-345
3.26.2 Statistic Items ............................................................................... 3-346
3.27 Cell Frequency Scan ............................................................................ 3-352
3.27.1 General ........................................................................................ 3-352
3.27.2 Principle ....................................................................................... 3-353
Chapter 4 Troubleshooting
4.1 Process of Trouble Shooting .................................................................. 4-1
4.2 Fault in Starting Traffic Statistics Console .............................................. 4-3
4.3 Operations of Traffic Statistics Task Failed ............................................ 4-4
4.3.1 No Resources Available ................................................................. 4-4
4.3.2 No enough disk space ................................................................... 4-5
4.3.3 Task Frame Length Exceeding the restriction of BAM and Host ... 4-5
4.3.4 Statistic Item Description Error or Number of Item Error ............... 4-6
4.3.5 Too Large HDD Space Needed for Saving Task Result ................ 4-6
4.3.6 This Statistic Function Type already Exists in Other Tasks ........... 4-7
4.3.7 Other User is Registering Scan Freq. Task ................................... 4-7
4.3.8 Statistic items cannot be resolved ................................................. 4-8
4.4 Querying Traffic Statistics Result Error .................................................. 4-8
4.4.1 Measurement Result Abnormal after Changing the Time of
BAM and Server ...................................................................................... 4-8
4.4.2 Task Results Incomplete due to Daylight Savings Time
Switching ................................................................................................. 4-9
4.4.3 Measurement Result of Percentage of CPU Occupation Being
0 .............................................................................................................. 4-10
4.4.4 Times of Successful Being 0/ Success rate Being ***** ..... 4-10
4.4.5 Average Inter Arrival Time of Random Access being "*****" .......... 4-11
4.4.6 Unknown statistic items Appearing in Item Value of Task
Result ...................................................................................................... 4-11
4.4.7 "?" Appearing in Task Value of Measurement Result .................... 4-11
4.4.8 Column Irregular ............................................................................ 4-12
4.5 Operations on Template and Item File Failed ........................................ 4-12
4.5.1 Item File or Template Being Modified ............................................ 4-12
4.5.2 FTP Connection Failed, Authentication Failed, Sending or
Receiving File Failed ............................................................................... 4-13
4.6 Response Speed of Traffic Statistics Console Slowing Down ............... 4-13
4.7 Others ..................................................................................................... 4-13
4.7.1 Status of Module in "Task Status" not Reflecting Actual
Situation .................................................................................................. 4-14
4.7.2 "Cant open help file! ................................................................... 4-14
4.7.3 Converting Result Timeout ............................................................ 4-14
4.7.4 Halting measurement task failed .................................................... 4-15
4.7.5 Activating measurement task failed ............................................... 4-15
4.7.6 Statistics About TRX ...................................................................... 4-16
HUAWEI
M900/M1800 Base Station Controller

Traffic Statistic Manual
V300R002
M900/M1800 Base Station Controller
Manual Version T2-031616-20030930-C-4.02
Product Version V300R002
BOM 31160816
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office, customer care center 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
2003 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this document 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, SoftX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX are trademarks of Huawei Technologies Co., Ltd.
Notice
The information in this document is subject to change without notice. Every effort
has been made in the preparation of this document to ensure accuracy of the
contents, but all statements, information, and recommendations in this document
don't constitute the warranty of any kind, express or implied.
About This Manual
Version
The product version corresponds to the manual is M900/M1800 BSC V300R002.
Organization of the Manual
The manual consists of 4 chapters which detail the traffic statistics system of BSC.
Chapter 1 is a brief introduction of the fundamental principle of the traffic statistic

system of BSC.
Chapter 2 introduces in detail the traffic statistic operations of BSC.
Chapter 3 introduces in detail each statistic item that Huawei BSC offers.
Chapter 4 introduces in detail the problems operator will encounter in traffic statistic
and the way to solve them.
Intended Readers
The manual is intended for the following readers:

z GSM maintenance engineer
z Operation & maintenance personnel
Conventions
This document 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.
Terminal Display is in Courier New; message input by the user via the terminal is in
Terminal Display
boldface.
II. GUI conventions
Convention Description
<> Message entered via the terminal is within angle brackets.
[] MMIs, menu items, data table and field names are inside square brackets [ ].
Multi-level menus are separated by forward slashes (/). For example,

/
[File/Create/Folder].
III. Keyboard operation
Format Description
Press the key with key name expressed with a pointed bracket, e.g. <Enter>,
<Key>
<Tab>, <Backspace>, or<A>.
Press the keys concurrently; e.g. <Ctrl+Alt+A> means the three keys should be
<Key1+Key2>
pressed concurrently.
<Key1, Key2> Press the keys in turn, e.g. <Alt, A>means the two keys should be pressed in turn.
The item with a square bracket indicates the menu option, e.g. [System] option on
[Menu Option] the main menu. The item with a pointed bracket indicates the functional button
option, e.g. <OK> button on some interface.
Multi-level menu options, e.g. [System/Option/Color setup] on the main menu

[Menu1/Menu2/Menu3] indicates [Color Setup] on the menu option of [Option], which is on the menu option
of [System].
IV. 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.
V. Symbols
Eye-catching symbols are also used in this document 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.

M900/M1800 Base Station Controller Table of Contents
Table of Contents
Chapter 1 Overview ....................................................................................................................... 1-1

1.1 Brief Introduction................................................................................................................ 1-1
1.2 Contents and Principles of Traffic Statistics ...................................................................... 1-1
1.3 Concept of Traffic Statistics ............................................................................................... 1-3
1.3.1 Traffic Statistics Task .............................................................................................. 1-3
1.3.2 Index Property ......................................................................................................... 1-4
1.3.3 Task Object Property .............................................................................................. 1-5
1.3.4 Task Time Property................................................................................................. 1-5
1.3.5 Measurement task status ........................................................................................ 1-6
1.4 Feature of Traffic Statistics ................................................................................................ 1-7
Chapter 2 Operation of Traffic Statistics .................................................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.1.1 Brief Introduction ..................................................................................................... 2-1
2.1.2 Brief Introduction to Traffic statistics Operation ...................................................... 2-2
2.1.3 Logging in BSC Traffic Statistics System................................................................ 2-3
2.1.4 Logging in Traffic Statistics Report System ............................................................ 2-5
2.2 Points for Attention ............................................................................................................ 2-6
2.3 Creating Traffic Statistics Task .......................................................................................... 2-8
2.4 Modifying Traffic Statistics Task ...................................................................................... 2-20
2.4.1 Modifying Task Name ........................................................................................... 2-21
2.4.2 Modifying Permanent Task Period ........................................................................ 2-22
2.4.3 Modifying Task Configuration Information ............................................................ 2-22
2.5 Halting/Activating Measurement Task ............................................................................. 2-24
2.5.1 Halting task............................................................................................................ 2-24
2.5.2 Activating task ....................................................................................................... 2-24
2.6 Refreshing Task List ........................................................................................................ 2-25
2.7 Querying Traffic Statistics Task ....................................................................................... 2-25
2.7.1 Querying Task Status............................................................................................ 2-25
2.7.2 Querying Detailed Information of Task ................................................................. 2-26
2.7.3 Querying Backup of Detailed Task Information .................................................... 2-27
2.8 Querying Measurement Result ........................................................................................ 2-28
2.9 Deleting Traffic Statistics Task ........................................................................................ 2-38
2.9.1 Deleting Task ........................................................................................................ 2-38
2.9.2 Deleting Backup Task ........................................................................................... 2-39
2.10 Template Management.................................................................................................. 2-39
2.10.1 Creating Item Template....................................................................................... 2-39
2.10.2 Creating Time Template...................................................................................... 2-41
i
2.10.3 Creating Object Template ................................................................................... 2-41

2.11 Customizing Item ........................................................................................................... 2-41
2.12 Refreshing All Templates............................................................................................... 2-45
2.13 Other Operations ........................................................................................................... 2-45
2.13.1 Setting shortcut buttons in the Result Window ................................................... 2-45
2.13.2 Customizing Setting ............................................................................................ 2-46
Chapter 3 Traffic Statistic Items .................................................................................................. 3-1

3.1 BSC measurement function............................................................................................... 3-1
3.1.1 General.................................................................................................................... 3-1
3.1.2 Statistic Items .......................................................................................................... 3-4
3.2 SCCP Measurement Function ......................................................................................... 3-82
3.2.1 General.................................................................................................................. 3-82
3.2.2 Statistic items ........................................................................................................ 3-83
3.3 A-interface Operation and Management Statistic............................................................ 3-89
3.3.1 General.................................................................................................................. 3-89
3.3.2 Statistic Items ........................................................................................................ 3-90
3.4 A-interface Equipment Maintenance Statistic.................................................................. 3-94
3.4.1 General.................................................................................................................. 3-94
3.4.2 Statistic Items ........................................................................................................ 3-94
3.5 A-interface Trunk Board Message Statistic ..................................................................... 3-96
3.5.1 General.................................................................................................................. 3-96
3.5.2 Statistic Items ........................................................................................................ 3-97
3.6 CPU Measurement Function ........................................................................................... 3-98
3.6.1 General.................................................................................................................. 3-98
3.6.2 Statistic Items ........................................................................................................ 3-99
3.7 BSC Cell Broadcast Measurement ................................................................................ 3-100
3.7.1 General................................................................................................................ 3-100
3.7.2 Statistic Items ...................................................................................................... 3-101
3.8 MTP Measurement Function ......................................................................................... 3-110
3.8.1 General................................................................................................................ 3-110
3.8.2 Statistic Items ...................................................................................................... 3-110
3.9 Cell Measurement Function........................................................................................... 3-115
3.9.1 SDCCH Measurement Function.......................................................................... 3-116
3.9.2 TCH Measurement Function ............................................................................... 3-132
3.9.3 Random Access Measurement Function ............................................................ 3-166
3.9.4 Inter-cell Handover Measurement Function........................................................ 3-172
3.9.5 Intra-cell Handover Measurement Function........................................................ 3-218
3.9.6 Other Measurement Function ............................................................................. 3-226
3.10 Power Control Measurement ....................................................................................... 3-236
3.10.1 General.............................................................................................................. 3-236
3.10.2 Statistic Items .................................................................................................... 3-236
3.11 Call Drop Measurement............................................................................................... 3-240
ii
3.11.1 General.............................................................................................................. 3-240

3.11.2 Statistic Items .................................................................................................... 3-241
3.12 SITE Initial Measurement Function.............................................................................. 3-243
3.12.1 General.............................................................................................................. 3-243
3.12.2 Statistic Items .................................................................................................... 3-244
3.13 BTS Initial Measurement Function............................................................................... 3-246
3.13.1 General.............................................................................................................. 3-246
3.13.2 Statistic Items .................................................................................................... 3-247
3.14 Cell Broadcast Statistic................................................................................................ 3-249
3.14.1 General.............................................................................................................. 3-249
3.14.2 Statistic Items .................................................................................................... 3-250
3.15 Outgoing Inter Cell Handover Measurement Function ................................................ 3-250
3.15.1 General.............................................................................................................. 3-250
3.15.2 Statistic Items .................................................................................................... 3-252
3.16 Incoming Inter Cell Handover Measurement Function ................................................ 3-278
3.16.1 General.............................................................................................................. 3-278
3.16.2 Statistic Items .................................................................................................... 3-279
3.17 Undefined Adjacent Cell Measurement Function ........................................................ 3-282
3.17.1 General.............................................................................................................. 3-282
3.17.2 Statistic Items .................................................................................................... 3-283
3.18 Defined Adjacent Cell Measurement Function ............................................................ 3-285
3.18.1 General.............................................................................................................. 3-285
3.18.2 Statistic Items .................................................................................................... 3-285
3.19 Receiving Quality Measurement.................................................................................. 3-287
3.19.1 General.............................................................................................................. 3-287
3.19.2 Statistic items .................................................................................................... 3-288
3.20 Receiving Level Measurement Function ..................................................................... 3-291
3.20.1 General.............................................................................................................. 3-291
3.20.2 Statistic Items .................................................................................................... 3-294
3.21 Up-Down Link Balance Measurement Function .......................................................... 3-310
3.21.1 General.............................................................................................................. 3-310
3.21.2 Statistic Items .................................................................................................... 3-311
3.22 LAPD Link Measurement Function .............................................................................. 3-313
3.22.1 General.............................................................................................................. 3-313
3.22.2 Statistic Items .................................................................................................... 3-314
3.23 Channel Allocation Measurement Function................................................................. 3-324
3.23.1 SDCCH Allocation Measurement Function....................................................... 3-324
3.23.2 TCH Allocation Measurement Function ............................................................ 3-331
3.24 Cell Flow Control Measurement Function ................................................................... 3-338
3.24.1 General.............................................................................................................. 3-338
3.24.2 Statistic Items .................................................................................................... 3-338
3.25 GPRS Related Measurement Function ....................................................................... 3-341
iii
3.25.1 General.............................................................................................................. 3-341

3.25.2 Statistic Items .................................................................................................... 3-342
3.26 Overlaid/Underlaid Subcell Measurement ................................................................... 3-345
3.26.1 General.............................................................................................................. 3-345
3.26.2 Statistic Items .................................................................................................... 3-346
3.27 Cell Frequency Scan ................................................................................................... 3-352
3.27.1 General.............................................................................................................. 3-352
3.27.2 Principle............................................................................................................. 3-353
Chapter 4 Troubleshooting .......................................................................................................... 4-1

4.1 Process of Trouble Shooting ............................................................................................. 4-1
4.2 Fault in Starting Traffic Statistics Console......................................................................... 4-3
4.3 Operations of Traffic Statistics Task Failed ....................................................................... 4-4
4.3.1 No Resources Available.......................................................................................... 4-4
4.3.2 No enough disk space............................................................................................. 4-5
4.3.3 Task Frame Length Exceeding the restriction of BAM and Host ............................ 4-5
4.3.4 Statistic Item Description Error or Number of Item Error ........................................ 4-6
4.3.5 Too Large HDD Space Needed for Saving Task Result......................................... 4-6
4.3.6 This Statistic Function Type already Exists in Other Tasks.................................... 4-7
4.3.7 Other User is Registering Scan Freq. Task ............................................................ 4-7
4.3.8 Statistic items cannot be resolved........................................................................... 4-8
4.4 Querying Traffic Statistics Result Error.............................................................................. 4-8
4.4.1 Measurement Result Abnormal after Changing the Time of BAM and Server ....... 4-8
4.4.2 Task Results Incomplete due to Daylight Savings Time Switching ........................ 4-9
4.4.3 Measurement Result of Percentage of CPU Occupation Being 0 ........................ 4-10
4.4.4 Times of Successful Being 0/ Success rate Being *****........................... 4-10
4.4.5 Average Inter Arrival Time of Random Access being "*****"................................. 4-11
4.4.6 Unknown statistic items Appearing in Item Value of Task Result ...................... 4-11
4.4.7 "?" Appearing in Task Value of Measurement Result ........................................... 4-11
4.4.8 Column Irregular.................................................................................................... 4-12
4.5 Operations on Template and Item File Failed ................................................................. 4-12
4.5.1 Item File or Template Being Modified ................................................................... 4-12
4.5.2 FTP Connection Failed, Authentication Failed, Sending or Receiving File Failed 4-13
4.6 Response Speed of Traffic Statistics Console Slowing Down ........................................ 4-13
4.7 Others .............................................................................................................................. 4-13
4.7.1 Status of Module in "Task Status" not Reflecting Actual Situation ....................... 4-14
4.7.2 "Can't open help file! ............................................................................................ 4-14
4.7.3 Converting Result Timeout.................................................................................... 4-14
4.7.4 Halting measurement task failed........................................................................... 4-15
4.7.5 Activating measurement task failed ...................................................................... 4-15
4.7.6 Statistics About TRX ............................................................................................. 4-16
iv
M900/M1800 Base Station Controller Chapter 1 Overview
Chapter 1 Overview
1.1 Brief Introduction
BSC Traffic Statistics (also known as performance measurement) is the data statistics
collection activities performed on BSC and its related network for the purpose of
measurement and observation of the operation, signaling, user and system resource
utilization so as to provide reliable data basis for communication network planning,
monitoring and maintenance.
BSC traffic statistics system supports the following functions: BSC Measurement
Function, SCCP Measurement Function, A-interface Operation and Management
Statistic, A-interface Equipment Maintenance Statistic, A-interface Trunk Board
Message Statistic, CPU Measurement Function, BSC Cell Broadcast Measurement
Function, MTP Measurement Function, Cell Measurement Function, Power-Control
Measurement Function, Call Drop Measurement Function, Site Initialization
Measurement Function, BTS Initialization Measurement Function, Cell Broadcast
Statistic, Outgoing Inter Cell Handover Measurement Function, Incoming Inter Cell
Handover Measurement Function, Undefined Adjacent Cell Measurement Function,
Defined Adjacent Cell Measurement Function, Receiving Quality Measurement
Function, Receiving Level Measurement Function, Up-Down Link Balance
Measurement Function, LAPD Link Measurement Function, Channel Allocation
Measurement Function, Cell Flow Control Measurement Function, GPRS Related
Measurement Function, Overlaid/Underlaid Subcell Cell Measurement Function and
Cell Frequency Scan, etc.
The major achievement includes:

z Important monitoring mode of the routine maintenance of equipment
z Important data source for network optimization
z Abnormality locating and fault handling
z Routine data for network management
1.2 Contents and Principles of Traffic Statistics
BSC traffic statistics system consists of the host equipment, BAM (Back Administration
Module) and WS (Work Station). Among them, the work station is the man-machine
interface, a friendly operation interface provided for traffic statistics. The work station of
BSC communicates with BAM as a far end user via OMC server or directly
communicates with BAM as a near end user. The functions provided under both modes
are completely the same.
1-1
BSC traffic statistics system network architecture is shown in Figure 1-1 and the logic
structure is shown in Figure 1-2. Both OMC Shell and LocalWS are software installed in
WS, and OMC Shell communicates with BAM via OMC Server, while LocalWS
communicates with BAM directly.
...
WS WS WS
OMC Server
BAM
Traffic Traffic Traffic

statistics statistics ... statistics
process 1 process 2 process n MPU
Figure 1-1 BSC traffic statistics system network architecture
IP IP
OMC Shell OMC Server Traffic statistics
BAM process
IP
Local WS MPU
Figure 1-2 BSC traffic statistics system logic structure
Below is the introduction to the functions of each part:

1) WS provides the direct operation interface for the user to register or delete the
traffic measurement tasks or to view the status and result of a task.
2) OMC Server provides the interface to network management centre, and manage
statistic tasks. It gets the data necessary for the traffic statistics from the Host via
the traffic statistics process in BAM.
3) BAM has two functions:
a) The bridge connecting WS and MPU board, via which the traffic statistics
commands from WS is transferred to MPU, and the response of MPU is returned
to WS;
b) The server in the Client/Server network mode, which realizes the management
of statistics tasks (mainly about the storage and transference of traffic statistics
data).
4) Traffic statistics process is actually a service process in charge of receiving and
interpreting the traffic statistics commands from BAM. The result of the interpreting
is the basis for processing and the processing result will be returned back to BAM.
1-2
The core function of it is to generate statistics from the result of various

measurement indices.
The following is the summary to the above information. User registers tasks at WS. The
commands registering the tasks are sent to the MPU board. When a measurement
cycle ends, the MPU automatically sends the measurement results to BAM which will
store the results in the format of Stxxx.res and Stxxx.tsk and in the directory of
\omc\bsc\BAM\appsvr\stats\Data, sends the permanent task result to OMC Server.
OMC Server will save the measurement result in Sybase database to generate the
report at report console. The user can query and print the traffic measurement report
stored in BAM at the WS.
Notes:
WS consists of several functional modules which provide the operations and maintenance interface for the
user to realize the functions of data configuration, equipment maintenance, fault monitoring, subscriber
management and traffic statistics via this subsystem. It communicates with BAM to realize various
operations and output the corresponding report.
Huawei's OMC adopts the integrated platform, which supports Huawei's GSM serial products access to
provide unified performance management, configuration management and fault management. The
operation and maintenance of multiple NEs can be implemented at the same terminal.
BAM fulfils the following functions:
z Background administration: data configuration of BSC, maintenance control of board, alarm
handling, traffic statistics, data backup etc;
z Save the converted data and send the operation instruction to MPU;
z Connection between equipment and user: receiving the commissioning, alarm of equipment and
notifying the user via LMT (WS).
For information related to traffic statistics of OMC Report, refer to the system operation part in
M900/M1800 Operations and Maintenance Center User Manual V4.0.
1.3 Concept of Traffic Statistics
1.3.1 Traffic Statistics Task
The core of traffic statistics is traffic statistics (measurement) task and traffic statistics
(measurement) result. User can "subscribe" to the necessary traffic statistics data. The
subscribed information makes up the traffic task. The system will implement the related
measurement according to the measurement task information and report the task
result.
1-3
A measurement task is made up of three elements: statistics time, statistics object,

statistics item (index). For details of these properties, refer to 1.3.2 Index Property,
1.3.3 Task Object Property and 1.3.4 Task Time Property.
Besides, in the whole statistics procedure of the task, there is a series of status from
"not started" to "ended", which will be detailed in 1.3.5 Measurement task status.
1.3.2 Index Property
I. Definition
Task index is the type of information to be "subscribed to" during the process of
measurement. The process of data collection, data record and data supervision during
the measurement is actually the process of management over the task indices.
The traffic statistics indices of BSC can be classified into initial index, pre-definition
index and customized index. The initial index is the basic unit of system index. The
pre-definition index is calculated from the initial index. The above two are the
self-contained indices of system. In addition, to satisfy the user's special requirements,
BSC also supports customized index function. Customized index is created by
combining initial index and pre-definition index in arithmetic principle according to the
actual requirement. The usage of these indices is same as initial index and
pre-definition index.
II. Organization mode
Since a traffic statistics system contains many statistics indices, for the convenience of
management and usage over these indices, the tree organization structure comprises
three stages. The first stage is Statistic Function Type, the second stage is Measure
Type and the third stage is Statistic Item.
Statistic Items are classified as a Measure Type. The Measurement types with similar
meanings are classified as a Statistic Function Type.
z Statistic Function Type
The set of several measurement types with some identical properties. Each
statistics function type describes a certain aspect of BSC equipment, such as
A-interface Operation and Management Statistic, CPU Measurement Function,
etc.
z Measure Type
Measurement type is the set of several related statistics indices of a measurement
object. It reflects the entire profile of the object. For example: Inter-cell Handover
Measurement Function describes the information of inter-cell handover.
z Statistic Item
1-4
It is the basic unit for measurement task to perform data statistics.
1.3.3 Task Object Property
The measurement object is various physical, logical entities or their combinations

measured. For example, to measure the TCH availability of a cell, this cell is a
measurement object. For the convenience of management and utilization, system
adopts the layered structure of Statistic Function Type Object Definition to decide a
measurement object.
1.3.4 Task Time Property
Time property includes parameters such as task type, time type, measurement cycle
and measurement time segment, etc. The management of measurement time can be
realized in the following three levels: time type, measurement time segment and
measurement cycle, as shown in Figure 1-3:
Date Date Date Date Date Date Date Date
Time type
Measurement
time segment
0:00 24:00
Measurement
cycle
Figure 1-3 Basic time type
1) Task type
Measurement tasks can be classified into permanent task, semi-permanent task and
limited period task.
z Permanent task
Permanent task is automatically registered from the moment system is started. It
is for measuring the important performance index, and generates reports
according to the requirement of the carrier. User cannot delete this type of tasks,
i.e. from the moment equipment is started, this task is carried out all the time
unless suspended;
z Semi-permanent task
Semi-permanent task is registered by the user and has no end time. It will keep
running unless deleted or suspended. For example, if a BSC measurement task is
1-5
created on 2002/1/1, started on 2002/1/1 without a termination, this task is a

semi-permanent task.
z Limited period task
Limited period task is registered by the user. It has an end time configured. When
the end time comes, the measurement is automatically terminated. For example,
the task temporarily measuring the TCH congestion rate can be set as the limited
period task.
2) Time type
There are three types: statistics by day, statistics by week and statistics by month.
They define the periodical operation mode of the task during its operation.
Statistics by day means that the task is carried out every day. Statistics by week
means that the task is carried out on the specified day of each week. For example,
a user can select Monday, Wednesday and Friday of each week to implement the
task. Statistics by month means that the task is carried out on the specified day of
each month. For example, a user can select the 1st, 5th and 13th of each month to
carry out the task. No matter in which mode, the task will be carried out during the
time decided together by measurement time segment and measurement cycle.
3) Measurement time segment
A day can be divided into at most three time segments in this system. The task is
only carried out in the time segment according to the configured measurement
cycle, and is terminated during the time between time segments. The range of
time segments cannot overlap. The daily operation time is decided together by the
measurement time segment and measurement cycle.
z From 00:00 of each day to 00:00 of the next day;
z For 1~3 discontinuous time segments, each one is started at a certain time
point (accuracy of minute) and carried out continuously for k measurement
cycles.
4) Measurement cycle
Measurement cycle is the sampling period of the measurement task. BSC traffic
management supports the measurement cycle of 15~1440 minutes.
z The duration with one minute as the unit. Upper limit is 24 hours.
z The default period is 30 minutes.
1.3.5 Measurement task status
A measurement task may be in various statuses in its life cycle: not started, activated,
suspended and complete.
z Not started
The current time of system is earlier than the start time of the task, i.e. the task is
not started yet.
1-6
z Activated
The current time of system is between the start time and end time of the task, i.e.
the task is being carried out.
z Suspended
When a task is temporarily not needed, it can be suspended. In this case, this task
will no longer provide measurement result. When it is necessary again, it can be
reactivated, and the measurement resumes. If a task is suspended, it cannot be
modified.
z Complete
The current time of system is or is later than the end time, i.e. the task is finished.
It is also called "terminated".
The process of measurement task change is shown in Figure 1-4.
Not started
Start time
Being halted
Activated suspended
Being activated
End time
Complete
Figure 1-4 Measurement task change
Note:
According to the definition of the task:
1) Permanent task can be in activated or suspended status;
2) Semi-permanent task can be in not started, activated or suspended status;
3) Limited period task can be in any status.
1.4 Feature of Traffic Statistics
The traffic statistics console of BSC, as a man-machine interface, supports the graphic
interface operation mode. It provides functions of task management, template
1-7
management and customized index management. Below are the details of these
functions.
I. Task management
The task management of traffic statistics includes creating/modifying/deleting

measurement task, activating/suspending measurement task, querying measurement
task information and querying task status, etc. For detailed operation of task
management, see "Chapter 2 Basic Operation". This chapter mainly introduces the
global features.
1) Creating task
Measurement indices are organized and managed according to measurement
type. But the user may also need to measure the indices reflecting the same
service function in the same task and have the combined output (especially when
generating the traffic statistics report). BSC supports selecting the measurement
indices from multiple measurement types.
2) Modifying task
There are three types of task modifications:
z Dynamic modification of task name
z Dynamic modification of task configuration information
z Dynamic modification of task object
Note:
It is not allowed to dynamically modify the suspended tasks, while possible to modify the task by
dynamically modifying the task configuration information.
3) Querying task
The information querying function can be used to query the various static
information in the MPU, including the status of task, measurement function set,
time property, measurement index and object type etc.
4) Suspending/activating task
If a task is temporarily not needed, this task can be suspended. When it is
necessary to have its output result again, it can be activated, and its output will
continue.
Only activated tasks can be suspended. On the other hand, only the suspended
task can be activated. Once the task is suspended, dynamic modification of this
task will be banned, while deleting and querying task is still valid.
1-8
5) Querying task result

It is possible to query the task result during or after the process of a task. The
query result can be listed in the sequence of object, time or index. The result can
also be displayed in the form of table, curve, bar chart, pie chart and point chart.
6) Printing result
User can perform "print preview", "print setting" and "print immediately" to the
measurement result.
7) Refreshing list
Normally, multiple users can perform the measurement to the same BAM. The list
refreshing of task/index/template enables the user to refresh the system
information on the interface.
II. Template management
Template is a set of parameters defined by the user, for the storage of common
information. When registering tasks, the template can be used to improve efficiency
and avoid repetition of information input. System supports three type templates:
statistic template, time template and object template.
z Statistic item template defines the combination of information about measurement
function type, statistics set and measurement item. System provides a default
statistic item template which can be customized by the user, and various
operations can be performed to the customized template;
z Time template defines the combination of time parameters;
z Object template defines the combination of information about measurement
function type and measurement object;
Template management facilitates an easy creation of templates and allows the user to
modify and delete the template.
Caution:
The creating/modifying of statistic item template, object template and time template should conform to the
principle of creating/modifying measurement tasks.
III. Customized index
For the convenience of customized traffic statistics data collection and reasonable
observation of the network operation, BSC provides the function of customized index
management function. The customized index refers to the index combination of the
1-9
initial indices and pre-definition indices after arithmetic procession based on the needs
of user.
Customized index management enables the creating, query, modification and deleting
of customized index. Besides, the user can also dynamically refresh the index list.
Similar to the initial index and pre-defined index, the customized index can be used to
create measurement task. All related initial indices and the customized indices should
belong to the same measurement function type.
System has a restriction to the number of customized indices. The current limit is 32768.
If the actual number of exceeds this limit, system will prompt the user to delete some
before adding the new ones.
Note:
Initial index and pre-definition index can be used to create customized index. While the customized index
cannot be used to create another customized index.
All indices can be used in creating measurement task.
The initial indices used to create customized index should belong to the same measurement function type.
1-10
M900/M1800 Base Station Controller Chapter 2 Operation of Traffic Statistics
Chapter 2 Operation of Traffic Statistics
2.1 Overview
The operation of BSC traffic statistics is implemented on WS (Work Station), and it

mainly includes the following functions:
z Maintenance of traffic statistics tasks, including creating, modifying, activating,
halting, deleting and querying.
z Graphic display of traffic statistics data. The report of results can be listed in the
format of tables according to the queried text report. The basic querying, result
sorting and result in table printing functions are also provided. Secondary data
analysis and processing can be implemented according to the result data. The
processed data can be displayed in bar chart or curve, etc.
The traffic statistics management system can be used to monitor the network
performance, and provide basis for the network maintenance and optimization. The
major functions of traffic statistics system is task registration, task deletion, task
modification, task status querying, task result analysis, task result printing, and
customized indices, etc.
2.1.1 Brief Introduction
Traffic statistics is mainly implemented with task operation. The rough process of traffic
statistics is shown in Figure 2-1, in which the dotted line symbolizes optional steps.
2-1
Start
Analyze requirements
Create task
Start measurement
Query task status
Modify task
Query task result
Suspend task
Activate task
Terminate task
Delete task
End
Figure 2-1 Process of traffic statistics
The task management system enables the user to create traffic statistics task, modify
traffic statistics task, query detailed information of traffic statistics task, query/save/print
the result of traffic statistics task and delete traffic statistics task. The most important
step among them is creating a traffic statistics task. The others are all implemented on
the basis of it.
In addition, BSC traffic statistics system also supports:

z Template management
z Customized index management
2.1.2 Brief Introduction to Traffic statistics Operation
The WS of BSC, as the man-machine interface of traffic statistics system, provides the
graphic operation interface shown in Figure 2-2.
2-2
Figure 2-2 Interface of traffic statistics system
2.1.3 Logging in BSC Traffic Statistics System
There are two methods of Logging in BSC traffic statistics system:
In the first method, the WS connects with BSC BAM via OMC Server. In this case,
select [Startup/Programs/Huawei GSM-OMC/OMC SHELL] as shown in Figure 2-3, to
log in OMC SHELL, and then right-click the BSC icon in OMC SHELL. Select [Traffic
Statistics] in the popped up pull-down menu to enter the traffic statistics system as
shown in Figure 2-4.
In the second method, the WS connects with BSC BAM directly. In this case, select
[Startup/Programs/Huawei GSM-OMC/OMC LocalWS] as shown in Figure 2-5 to log in
OMC Local WS, and then select [Start/Task/Traffic Statistics] in OMC Local WS as
shown in Figure 2-6 to enter the traffic statistics system.
2-3
Figure 2-3 Logging in OMC SHELL
Figure 2-4 Logging in traffic statistics system from OMC SHELL
2-4
Figure 2-5 Logging in OMC LocalWS
Figure 2-6 Logging in traffic statistics system from OMC LocalWS
2.1.4 Logging in Traffic Statistics Report System
BSC supports the report operation system under the unified management of Huawei
OMC. This system collects the traffic statistics data from the equipment's of the entire
network to generate the centralized reports conforming to network management
standard.
It is necessary to log in OMC SHELL before logging in report system. In OMC SHELL,
right-click the icon of OMC Server, and then select [Traffic Statistics Report] in the
shortcut menu to enter the main window of report system, as shown in Figure 2-7. The
operations of traffic statistics reports include create report, delete report, browse report,
print report, save report, and modify configuration information and the time definition of
data collecting. For the detailed introduction to the report system and the operations,
please refer to the section of "System Operation" in M900/M1800 Operation and
Maintenance Center User Manual.
2-5
Figure 2-7 Logging in report system
2.2 Points for Attention
Pay attention to the following when using BSC traffic statistics tools:
1) Each traffic statistics task occupies some of the system resources. If too many
tasks are implemented simultaneously or a task is implemented too frequently, too
much resource of BSC system will be used. Therefore, there are restrictions to the
number and period of traffic statistics task in BSC system:
z At most 200 tasks can be created in each BM (Basic Module).
z At most 3000 subtasks can be created in each BM.
A traffic statistics task is divided into subtasks according to the traffic statistics
objects in the task. The number of traffic statistics objects of a traffic statistics task
equals to the number of the subtasks contained in this task. The number of
subtasks of a BM is the total number of the subtasks of all tasks created in this BM.
For example, if a BM is fully configured to supports 128 cells, there will be 128
subtasks after creating a measurement task of cell performance for "all cells in the
module".
z A task can have at most 60 different initial indices.
For example, BSC Measurement Function has more than 120 primitive indices.
Cell Measurement Function has more than 220 primitive indices. At least three
tasks are to be created to measure all indices of BSC Measurement Function. At
least four tasks are to be created to measure all indices of Cell Measurement
Function.
2-6
Note:
The number of the initial indices contained in a pre-defined index or customized index equals to the
number of initial indices that compose these pre-defined or customized indices. If an initial index and its
pre-defined or customized index are both selected as the statistic items of a traffic statistics task, this initial
index will be measured once only.
There are another two special traffic statistics types: Cell Frequency Scan and Receiving Level
Measurement Function. These two types both contain over 60 primitive indices, but it is still possible to
select over 60 initial indices in a task here.
z Minimum traffic statistics cycle: 15 minutes

If the statistic cycle is too short and the task results are too many, the system burden will
increase. Therefore, the statistic cycle should not be shorter than 15 minutes. The
default setting is 30 minutes. The maximum statistic cycle is 1440 minutes.
2) User authorities
The user authorities of OMC traffic statistics system are divided into three levels:
service query authority, service configuration authority and service management
authority. See Table 2-1.
Table 2-1 User authorities
Operations allowed Service query Service configuration Service management

authority authority authority
Registering tasks No Yes Yes
Yes (for the task registered by
Deleting tasks/results No Yes
this user only)
Yes (for the task registered by
Modifying task name No Yes
this user only)
Change cycle of permanent Yes (for the task registered by
No Yes
task this user only)
Customized index No No Yes
Defining, saving, deleting
No Yes Yes
templates
Browsing tasks and results Yes Yes Yes
3) Statistic items that cannot be registered more than once

Do not register the statistic items concerning maximum/minimum values (e.g.
Maximum num. of busy TCHs) in multiple tasks. Otherwise, the data of these indices
may be incorrect.
The BSC traffic statistics indices concerning maximum/minimum values and their traffic
statistics function types are listed in Table 2-2.
2-7
Table 2-2 BSC indices concerning maximum/minimum values
Traffic statistics function type Index concerning maximum/minimum value

CPU Measurement Function Peak percentage of CPU occupation
Cell Measurement Function Maximum num. of busy SDCCHs
Cell Measurement Function Maximum TCH queue length
Cell Measurement Function Maximum num. of busy TCHs
Power-Control Measurement Function Maximum distance between MS and BTS
Power-Control Measurement Function Maximum downlink power duration percentage
Power-Control Measurement Function Maximum uplink power duration percentage
GPRS Related Measurement Function Max num. of available PDCH
GPRS Related Measurement Function Min num. of available PDCH
4) Do not modify the time of BAM and OMC Server.

Since the management and time of traffic statistics are closely related, if the time is
modified, the result of this cycle that outputted may be incorrect.
2.3 Creating Traffic Statistics Task
I. Analyze requirements
The demand of traffic statistics usually has the following considerations: routine
maintenance, fault handling and network optimization, etc. Before creating traffic
statistics task, it is necessary to analyze the requirements of the traffic statistics to
decide the parameters of the task.
The following takes the traffic statistics tasks needed during the system normal running
as an example. Assume that this BSC contains two BMs, each of which has 120 cells.
For the tasks needed under other situations, refer to the information of various statistic
items in Chapter 3.
1) Basic information
During the normal operation of BSC, the tasks of BSC Measurement Function and Cell
Measurement Functions for each cell should be registered, as which are shown in
Table 2-3.
Table 2-3 Basic tasks needed during the normal operation of BSC
Task Task name Description

1 BSC Measurement - Common The BSC Measurement is realized with two tasks. They
2 BSC Measurement - Maintenance are usually the routine type and maintenance type.
3 Cell Measurement 1 - SDCCH
4 Cell Measurement 2 - TCH1
The measurement of all cells is realized with five tasks.
5 Cell Measurement 3 - TCH2
They are SDCCH type, TCH type, handover type and
6 Cell Measurement 4 - Handover handover launch type.
Cell Measurement 5 - Launch
7
Handover
2-8
Note:
BSC measurement function and cell measurement function involve a large number of initial indices, but a
measurement task can has at most 60 initial indices. Therefore, there are usually two tasks created for
BSC measurement so as to cover those important initial indices; there are usually four tasks created for
cell performance measurement. In this example, to stress the pertinency of the measurement result, all
indices are classified into four types and totally 5 tasks created.
The principle for naming the tasks is simple and easy to distinguish.
2) Index information
The index information that should be registered is shown in Table 2-4.
Table 2-4 Basic statistic items needed during the BSC normal running
Task Measurement Measurement type Statistic item

function type concerned
Routine type statistic items in BSC Measurement
1
Function. See Note 1)
BSC
Measurement BSC Measurement Function
Maintenance type statistic items in BSC
2 Function
Measurement Function
SDCCH Measurement
Function SDCCH and other signaling channel type
3 Random Access measurement items in Cell Measurement
Measurement Function Function
Other Measurement Function
Partial statistic items of TCH type in Cell
4 TCH Measurement Function
Cell
TCH Measurement Function Residual statistic items of TCH type in Cell
5 Measurement
Other Measurement Function Measurement Function
Function
Inter-cell Handover
Handover type statistic items in Cell Measurement
6 Intra-cell Handover
Function
Other Measurement Function
Inter-cell Handover Statistic items of handover originating type in Cell
7
Measurement Function Measurement Function
2-9
Note:
1) Since there are a large number statistic items, it is impossible to list all indices in the above table. For the
correspondence between tasks and statistic items, refer to default statistic item template of BSC traffic
statistics system.
2) Since the implementation of traffic statistics task will occupy some system resources, and the number of
subtasks allowed to be created in the entire BM is limited, the following principles should be conformed to
when creating measurement tasks:
z Select statistic items concerned only;
z Arrange the pre-defined indices or customized indices processed from initial indices in the same task
with the initial indices.
3) Object information
Table 2-5 Object information of measurement task created during BSC normal running
Task Task Name Object

1 BSC Measurement-Common
No special parameters needed
2 BSC Measurement-Maintenance
3 Cell Measurement 1-SDCCH
4 Cell Measurement 2-TCH1
5 Cell Measurement 3-TCH2 All cells in the module 1 and 2
6 Cell Measurement 4-Handover
7 Cell Measurement 5-Launch Handover
z Time information
The time information settings of these five tasks are the same, as shown in Table 2-6.
Table 2-6 Time information of measurement task needed during BSC normal running
Parameter Content
Task type Semi-permanent task
Beginning Date 2002-11-12
End date None
Time Type Statistic by day
Statistic Cycle 60 minutes
The following takes the Task 1 in the measurement tasks needed during the BSC
normal running as an example to explain the process of creating a measurement task.
II. Enter the interface of creating tasks
There are three methods to enter the interface:

z Select [Task/New]
z Press <Ctrl+N>
2-10
z Click
System pops out a dialog box, as shown in Figure 2-8.
Figure 2-8 Registering new task
III. Set task name
This step decides the name of the task. The name should be concise and easy to be
distinguished. The name can contain letters, digits and characters. The length should
be shorter than 32 characters.
In Figure 2-9, the name of the task is "BSC Measurement-Common".
2-11
Figure 2-9 Setting task name
IV. Set statistic item
The interface for statistic item setting is shown in Figure 2-9. Each statistic item belongs
to the related Statistic Function Type and Measure Type. A task can only contain the
statistic items of the same Statistic Function Type, in other words, all indices of a
measurement task should belong to one or more Measurement types of the same
Statistic Function Type.
For the description of the dialog box illustrated in Figure 2-8, see Table 2-7.
Table 2-7 Description of the interface of creating tasks
Field name Meaning Value range Recommended value

Statistics function type Select the proper one
Statistic There are totally 27 BSC statistics
of the newly created according to the actual
Function Type function types
measurement task situation
The value range varies with different
[Statistic Function Type]. If [Statistic
Function Type] is "Cell Measurement
Function", the measurement type can be
"SDCCH Measurement Function", "TCH
Measurement type of Measurement Function", "Random Select the proper one
Measure Type the newly created Access Measurement Function", according to the actual
measurement task "Inter-cell Measurement Function", " situation
Intra-cell Measurement Function" or
"Other Measurement Function". If
[Statistic Function Type] is "Cell
Frequency Scan", the measurement
type can be "Band 900" or "Band 1800".
2-12

In other cases, the name of Measure
Type is the same as the name of Statistic
Function Type.
Display all indices
(including the
All Statistic customized indices and
All indices Select the proper one
Items index provided by
Huawei) of the
measurement type
Display the statistic
Selected Items items selected by the None None
user
Select a Select the statistic item The default templates and customized
None
Template template saved before templates
Display the status of
Status bar None None
system operation
For the description of the buttons in the interface, see Table 2-8.
Table 2-8 Description of the buttons in the interface of creating tasks
Button Function
<Statistic Item> Display the interface shown in Figure 2-9
<Sampling Time> Display the interface shown in Figure 2-11 or Figure 2-12
<Object Definition> Display the interface shown in Figure 2-14
Add the statistic items selected in [All Statistic Items] to [Selected Items]
Remove the selected statistic items from [Selected Items]
Add all statistic items in [All Statistic Items] to [Selected Items]
Remove all statistic items from [Selected Items]
Click this button to move the selected item in [Selected Items] up for a box
Click this button to move the selected item in [Selected Items] down for a box
<Save Template> Save the selected statistic items as a template file
<Delete Template> Delete the selected templates
<Register> Register the measurement task at MPU of BSC
<Close> Quit this interface
When registering a statistic task, the statistic items of the same statistics function type
but different measurement types can be selected as needed. The total number of initial
indices cannot exceed the limit of 60. Otherwise, the registration of measurement task
may fail, as shown in Figure 2-10.
2-13
Figure 2-10 Too many statistic items selected, registration failed
In Figure 2-9, the template function is used when selecting statistic items, i.e. "BSC
Measurement Function 1.1 (Common Statistic Template)" is selected in the dialog box
of template selection.
V. Set Sampling Time
The interface of Sampling Time is shown in Figure 2-11. To specify the days of
execution in each month select "Statistic by month" in the window of "Time Type", and
then set the measurement time. See Figure 2-12. The corresponding operation for the
weekly measurement task is similar.
2-14
Figure 2-11 Set time property 1
Figure 2-12 Set time property 2
For the description of the interface illustrated in Figure 2-11, see Table 2-9.
2-15
Table 2-9 Time definition of a new task

Any valid date, including before, current
The beginning and after. The format is yyyy-mm-dd. E.g.
Beginning Date Current date
date of the task "2002-10-20" means the measurement will
be started on Oct. 20th, 2002.
The interval of
generating a 30 minutes (default) or 60
Statistic Cycle 15~1440 (Unit: minute)
measurement minutes
result
The life cycle of Limited Period Task: 1~9999
Select according to the
Statistic Type the measurement Semi-Permanent Task: every day defined
actual situation
task in "Time type" after the date of registration
several time
Statistic segments each
Periods day can be 1~3
actual situation
Number selected for
measuring
Beginning and
The 1st part The time segment
end time of the 1st 00:00~24:00
fromTo concerned most
time segment
Beginning and
The 2nd part Do not overlap with the 1st
end time of the 00:00~24:00
fromTo time segment
2nd time segment
Beginning and
The 3rd part Do not overlap with the 1st
end time of the 00:00~24:00
fromTo and 2nd time segment
3rd time segment
Statistic by day: every day;
Execution date of Statistic by week: specified days of each
Time Type measurement week;
actual situation
task Statistic by month: specified days of each
month
Set the length of
Store the
period for saving
results of Depends on the corresponding
the measurement See Note.
latestdays in measurement task
results in the
BAM
BAM
Select the time
Select a
template created All time templates created before "Time template not used"
Template
before
Note:
1) System assigns certain amount of space for each task. When creating traffic statistic tasks, system
estimates the HDD space necessary for saving each statistic result within its storage time segment in the
BAM according to the number of indices, statistic cycle, number of statistic objects. If the space needed is
larger than the space available, system will prompt the error information and the possible days for storage
currently, as shown in Figure 2-13. In this case, set the save time again according to the prompt.
2) As far as the semi-permanent task are concerned, if the days the statistic task carried out have
exceeded the engaged one, BSC will delete the earliest statistic result.
2-16
Figure 2-13 Error when the measurement result storage time is too long
In Figure 2-11, the setting is that the task is implemented every day from Nov. 12th, and
system measures every 60 minutes and always saves measurement results of the last
60 days.
Note:
If the traffic statistics task has been created and the start time configured is reached, BSC system will start
measurement and output the results.
VI. Set object property
The interfaces of setting object property can be divided into several types. Figure 2-14
and Figure 2-15 are two of them.
2-17
Figure 2-14 Object definition 1
Figure 2-15 Object definition 2
In BSC traffic statistics system, the measurement entity is the object. There are several
types of objects: module object, site object, cell object, TRX object and signaling link
object. For the description of the parameters needed in [Objection Definition] in
statistics function types (special parameters), see Table 2-10.
2-18
Table 2-10 Description of special parameters
Special parameters Meaning Value range Recommended values

Module No. Module No. of BSC BM 1~8 None
Cell No. No. of the cell to be measured in this BM 0~127 None
TRX No. No. of the TRX to be measured in this site 0~35 None
SITE No. No. of the site to be measured in this module 0~63 None
Physical No. of the MTP link to be measured.
Start link No. of board related to SS7 (e.g. Configure according to
Depends on the
Links in the module LPN7) = max. number of links provided by this the actual situation.
actual situation
board % Board No. The max. number of links Normally start from 4
provided by LPN7 is 4.
CGI of the observed adjacent cell of the
Adjacent cell CGI LAI+CI None
measured cell
Percentage of the number of the
measurement reports related to this adjacent
Rate limit 0~100 None
cell accounts in the number of all
measurement reports
The lower limit of receiving level of MS to the
Level limit 0~63 None
adjacent cell for starting the measurement
Configure according to
Depends on the value decided in BSC
Signaling links No. No. of the LAPD link to be measured
actual situation Data Auto Configuration
System
In Figure 2-14, there is no need to define the object in the measurement of "BSC
Measurement".
After the setting of all indices, click <Register>, if the task is successfully created, the
interface illustrated in Figure 2-16 will appear. If the prompt of registration failure
appears, such as, the prompt of registration failure due to too many indices registered
(Figure 2-10), handle this problem according to the prompt information and the
information in Chapter 4 of this manual.
2-19
Figure 2-16 Registering tasks 5
2.4 Modifying Traffic Statistics Task
As shown in Figure 2-17, the BSC traffic statistics system supports modifying the task
name, configuration information and object of a task.
2-20
Figure 2-17 BSC task management menu
2.4.1 Modifying Task Name
I. Function
Modify the name of the created tasks.
II. Access
z Select [Task/Rename];
z Press <F2>.
III. Operation
The interface of modifying the name of a task is illustrated in Figure 2-18.
2-21
Figure 2-18 Interface of modifying the name of a task
The new name of the task can be composed of 32 characters.
In this example, the original name "Handover Stat of BSC" is modified as "Handover
Stat of BSC1".
2.4.2 Modifying Permanent Task Period
I. Function
Modify statistic cycle of permanent tasks.
II. Access
z Select [Task/Change Cycle];

z Press <Ctrl+P>.
2.4.3 Modifying Task Configuration Information
I. Function
Modify the configuration information of the created task, including statistic item, time
and object.
II. Accesss
z Select [Task/Modify Task];

z Press <CTRL+C>.
2-22
Caution:
If a task is modified in this manner for multiple times, BSC system will save the task information and
measurement result before the latest modification to [c:\omc\bsc\bam\appsvr\stats\databak] of the BAM
and take the place of the earlier data and information which will be all lost.
If only the object information needs to be modified, the access can also be:
z Select [Task/Modify Object];
z Press <CTRL+O>.
Note:
When modifying task object in this manner, it is possible to get the measurement results of the object
before and after modification for multiple times in the same table.
III. Operation
The interface of modifying task configuration is shown in Figure 2-19.
Figure 2-19 Modify task configuration
2-23
The operation of modification is similar to that of creating. Refer to Set statistic item, Set
Sampling Time and
Set object property.
2.5 Halting/Activating Measurement Task
2.5.1 Halting task
I. Function
Halt the operation of a task. As a result, the halted task will no longer output statistic
results until activated. In the task list, the icon before halted task changes to " ". If the
halt failed, the icon before the task changes to " ", and the related information will be
offered in the interface. Please take action according to the information.
II. Access
z Select [Task/Halt];
z Right-click a operating task, and then select [Halt] in the shortcut menu;
z Press <Ctrl+H>.
2.5.2 Activating task
I. Function
Activate the halted task in the task list to resume its operation. In the task list, the icon
before an operating task is " ". If the activation failed, the icon will change to " ".
Note:
When a task is halted, the related process in MPU will be canceled and all the resource occupied for this
task in MPU will be released. If new task is registered and the limits described in 2.2 Points for Attention is
reached. In this case, if the operator wants to activate the halted task, the system will give the information
of activation failed.
II. Access
Select the halted task to be activated, and then

z Select [Task/Activate];
2-24
z Right-click the halted task and then select [Activate] in the shortcut menu;
z Press <Ctrl+A>.
2.6 Refreshing Task List
I. Function
Display the latest information of the tasks.
II. Access
z Select [Task/Refresh]
z Right-click the task list and then select [Refresh] in the shortcut menu.
z Press <F5>.
2.7 Querying Traffic Statistics Task
2.7.1 Querying Task Status
I. Function
Query the current status of the selected traffic statistics task in the BSC Host. The
description of various statuses is detailed in Table 2-11.
Table 2-11 Task status description
Task status Meaning

The task hasn't been This task has not been successfully registered in BSC Host. If a halted task is
registered deleted at the Host, its status will then be "Task hasnt been registered".
This task has been successfully registered, but it has not been started because the
Task statistic not start
defined start time has not come.
The task is now running This traffic statistics task is running.
The task has been
This traffic statistics task has been halted; its operation is terminated temporarily.
suspended
The task has been The current time is later than the end time of the task, which is defined when
completed registering this task.
The module has no
The BSC Host module has not responded.
answer
II. Access
Select the task whose current status is to be queried, and then

z Select [Task/Status];
z Right-click the task whose current status is to be queried, and then select [Status]
in the shortcut menu.
2-25
2.7.2 Querying Detailed Information of Task
I. Function
Query various information of the task selected in the task list, such as current statistic
item, measurement object. If the task has been modified, implement the operation
introduced in 2.7.3 Querying Backup of Detailed Task Information.
II. Access
z Select [Task/Detail];
z Press <Ctrl+F7>.
III. Operation
The interface of task detailed information is illustrated in Figure 2-20. The detailed
information is displayed in "General Info", "Statistic Items" and "Object Info" in the
interface.
Figure 2-20 Interface of task detailed information
2-26
2.7.3 Querying Backup of Detailed Task Information
I. Function
Query the detailed information of a task measured between the last and the second last
modification if the task has ever been modified using [Modify Task].
Note:
When the task is modified using "Modifying Task Configuration Information", system will overwrite the old
configuration information saved before last modification. The overwritten information cannot be queried.
For example, if a task has been modified for five times, it is possible to query the information of the current
task using "Querying Detailed Information of Task", and information of the task before the 5th modification
and after 4th modification using "Querying Backup of Detailed Task Information". The other information
cannot be queried.
II. Access
z Select the modified measurement task, and then select [Task/Backup Detail];
z Right-click the modified traffic statistics task and the select [Backup Detail] in the
shortcut menu.
III. Operation
The interface of backup of detailed task information is illustrated in Figure 2-21.
2-27
Figure 2-21 Backup of detailed task information
2.8 Querying Measurement Result
I. Function
Query the measurement result of the selected task.
If a task has ever been modified using "Modifying Task Configuration Information", the
method of querying the measurement result before the modification is different from
that of querying the measurement result of the current task.
Note:
If a measurement task has been modified using "Modifying Task Configuration Information for several
times, it is impossible to query the task results before the last two modifications.
II. Access
1) To query the task result of the current task,

z Select [Task/ Results];
z Right-click the task, and then select [Statistic Results] in the shortcut menu;
2-28
z Press <Ctrl+F8>.
2) To query the task result before the latest modification of a task modified using
"Modifying Task Configuration Information", enter the interface for querying
backup of detailed task information (see 2.7.3 Querying Backup of Detailed Task
Information), and then click in this interface.
III. Operation
If the selected one is a permanent task, the interface will be the one shown in
Figure 2-22. For other tasks, the interface will be the one shown in Figure 2-23.
Figure 2-22 Querying the result of a permanent task
For the description of the interface shown in Figure 2-22, see Table 2-12.
Table 2-12 Options for querying a permanent traffic statistics task
Option Function
All results Query all task results of the permanent task
Get Latest Records Query a certain number (decided by the user) of the latest task results
Custom Result Time Range The start and end No. of the task result records selected by the user
2-29
Figure 2-23 Query task result of normal tasks
For the description of the interface in Figure 2-23, see Table 2-13.
Table 2-13 Settings of querying task results
Option Function
Query all results of statistics from the current day when the task is
Todays Result
started to now
All Results Query all results of a traffic statistics t task
Query all results of a task within the user-defined time segment.
Custom Range
Note that the start time should be earlier than the end time
Arrange Method to Show Result-by time List the results of the traffic statistics task in the sequence by time
List the results of the traffic statistics task in the sequence by the
Arrange Method to Show Result-by object
No. of traffic statistics objects
In Figure 2-22 and Figure 2-23, click <OK>, and the result of each measurement object
are output in list at each statistic cycle. In this case, all shortcut keys in the result
window will be activated, as shown in Figure 2-24.
Figure 2-24 Shortcut keys in the result window
Before viewing the task result, it is possible to click in Figure 2-24 to

further select the items to be displayed in the results. The setting interface is shown in
Figure 2-25.
2-30
Figure 2-25 Selecting the items to be displayed in the task result interface
Here the user can select those desired indices and hide those not needed. In this way,
only the results related to those selected items will be displayed in "Show Results". In
Figure 2-25, the task result of "Circuit paging (A-interface) success rate" is hidden.
The next step is to view the task result.
Figure 2-26 illustrates the tab of "Show Results". In this tab, it is possible to arrange the
sequence of the indices by different indices by clicking the column heading. This
enables the user to query the task results in the sequence by index on the basis of
result sequencing mode configured. After deciding the sequence (by time or by object),
it is possible to move back and forth among the groups of time or object by pressing
<F3> or <Shift+F3>.
Figure 2-27 illustrates the tab of "Detailed Information". This tab displays the results of a
task within a certain statistic cycle. It is possible to view the task results of other traffic
statistics objects or of other statistic cycle by clicking , , and .
2-31
Figure 2-26 Task statistic result
Figure 2-27 Task statistic result
For the convenience of comparison, BSC traffic statistics system supports the diagram
mode to display the task results more directly and clearly, as shown in Figure 2-28. To
query the task results of an object during a certain period of time, select "by object", and
2-32
then select an object in the dialog box. To query the task results during a certain period
of time, select "by time", and then specify the time in the dialog box.
In diagram displaying mode, if the diagram contains too many indices, the appearance
of it will be chaotic, thus affecting the analysis. Therefore, a diagram is allowed to
display at most 16 indices distinguished with 16 different colors. The lower area in this
interface is for selecting the indices to be displayed in the diagram. If too many indices
are selected, system will prompt error information.
As to the forms of the diagram, the available choices are Line , Bar and Point
. The property of the diagram can be configured with , as shown in Figure 2-29.
The configuration includes Vertical Range, 3D displaying mode and Grid as well as the
number of data points displayed in each page.
Figure 2-28 Diagram
2-33
Figure 2-29 Diagram configuration
System may simultaneously display many task results. The results user concerned
most may be "submerged" by the unconcerned results. Therefore, BSC supports a
powerful function of task result filtering. With this function, user can only view the task
results satisfying the filtering conditions of a specified object in the specified time
segment.
Note:
Make sure to obtain "Task Results" before configuring "Data Query". Otherwise, will
still be gray.
To configure querying conditions, click in the interface in Figure 2-24.

The interface for configuring conditions of querying the task result database is shown in
Figure 2-30.
2-34
Figure 2-30 Configuring conditions of querying the task result database
In this interface, the "Select Objects" (top-left) is for configuring the object to be queried.
After configuration, system will only provide the results of the selected objects. In
Figure 2-30, the task results of Cell 0~2 are queried. "Display items" (bottom-left) is
used to configure the statistic items to be queried. In Figure 2-30, the task results
related to all items of this task. "Time Range Setting" (top-middle) is for configuring the
traffic statistics time range of the task. After configuration, system will display the results
satisfying this condition only. "Grouping and Sort Type" (top-right) is for setting the
grouping and sequencing of the task results. In Figure 2-30, the task results are
grouped by time in ascending order. The results in each group are in ascending order.
In other words, the task results are first grouped according to their statistic cycle.
Results output in the same period make up a group. Different groups are sequenced by
time. If the items to be queried are not configured with traffic statistics type, i.e. only the
actual values of the items are queried, they will be sequenced by traffic statistics object
in ascending order in the group. To query the maximum value of an item, the
sequencing in the group is not needed, for there will be only one result displayed in
each group. If the results are not grouped, the task results queried according to the
conditions of object, item and time will be displayed in their original order. If the items to
be queried are configured with traffic statistics type, such as maximum value, there will
be only one result of the query. "Item Filtering Condition" (bottom-right) is for
configuring the conditions of task result output. If filtering conditions have been
configured, system will display the results satisfying these conditions according to the
object, item and time configured. If no setting made to this part, system will output all
2-35
results satisfying other conditions configured. In the example in Figure 2-30, the only
task results with "SDCCH blocking rate" > 10% and "Paging unsuccess rate (PCH
overloads)" > 5% will be displayed. The process of setting "Item Filtering Condition" is
as follows:
STEP 1: Decide the filtering conditions. In this example: SDCCH blocking rate > 10%
and Paging unsuccess rate (PCH overloads) > 5%
STEP 2: Configure the first condition. Select Item Name, Operator, and then input their
proper values. Click one of <AND>, <OR> and <NOT>. In this example: "T
SDCCH blocking rate", ">" and "10%" are selected, and then click <AND>.
STEP 3: Configure the second condition. Select item name, calculation relation, and
input the values, and then select the configured conditions which is at the
same level as this condition in the tab of "Item Filtering Condition Tree", and
finally, click one of <AND>, <OR> and <AND>. In this example: "Paging
unsuccess rate (PCH overloads)", ">" and "5%", and then select
"TermID_20201>10" in the tab of "Item Filtering Condition Tree", and finally,
click <AND>.
STEP 4: If there are still conditions to configure, follow this pattern to configure.
After configuration, click <View SQL> in the interface shown in Figure 2-30, and then
select "Item Filtering Condition" to query the finalized filtering conditions, as shown in
Figure 2-31.
Figure 2-31 Item filtering condition
The tab page of "SQL" displays all filtering conditions currently configured.
2-36
Figure 2-32 SQL conditional query statement
The interface of SQL conditional query statement is shown in Figure 2-32. Below is the
description of each field using this figure as an example. "RDateTime ASC, ModNo
ASC, CellNo ASC" means the grouping and sequencing mode;
"TermID_2197 ,TermID_2198 ,TermID_2186 ,TermID_2187 ,TermID_2188 ,TermID_2
189 ,TermID_2190 ,TermID_2191 ,TermID_2192 ,TermID_2193 ,TermID_2194 ,TermI
D_2195 ,TermID_2048 ,TermID_2062 ,TermID_2064 ,TermID_2065 ,TermID_2049 ,Te
rmID_2050 ,TermID_2051 ,TermID_2052 ,TermID_2053 ,TermID_2054 ,TermID_2055
,TermID_2056 ,TermID_2057 ,TermID_2070 ,TermID_2066 ,TermID_2067 ,TermID_2
068 ,TermID_2069 ,TermID_2072 ,TermID_2073 ,TermID_2076 ,TermID_2077 ,TermI
D_2078 ,TermID_2079 ,TermID_2080 ,TermID_2081 ,TermID_2082 ,TermID_2278 ,Te
rmID_2281 ,TermID_2282 ,TermID_2292 ,TermID_2074 ,TermID_2075 ,TermID_2083"
is the displayed items. "TermID_2197" refers to the statistic item numbered as 2197;
"Task17" is the name of the database table for saving the task results, "17" is the task
No. when a task is registered at WS, it will be allocated with a task No. "(RDateTime
>= :PDateTimeBeg) and (RDateTime < :PDateTimeEnd)" is the time range of the
displayed results; "(ModNo=1 And CellNo=0) OR (ModNo=1 And CellNo=1) OR
(ModNo=1 And CellNo=2)" is the conditions of object for displaying the task results;
"(TermID_20201 > 10) AND(TermID_20400 > 5)" is the configured filtering conditions.
If "Data Query" has been configured, the task will have another tab "Data Query", as
shown in Figure 2-33. In this tab, the results satisfying the conditions set in "Data
Query" will be displayed. After getting the results, they can be listed in the sequence by
different items by clicking the column headings. In this way, it is possible to query the
results in the sequence by items on the basis of the grouping mode and inter-group
sequencing mode configured before hand.
2-37
Figure 2-33 Data query result
2.9 Deleting Traffic Statistics Task
2.9.1 Deleting Task
I. Function
Delete the selected traffic statistics task. If the deleted task has a backup, the backup
will also be deleted.
Note:
BSC traffic statistics system supports the modification of task configuration information. If the configuration
information of a task is modified, the information before this modification will be saved as the backup.
II. Access
z Select the task to be deleted, and then select [Task/Delete];
z Select one or more tasks to be deleted, and then click ;
z Select a task to be deleted, and then press <Del>;

z Right-click a task to be deleted, and then select [Delete] in the shortcut menu.
2-38
2.9.2 Deleting Backup Task
I. Function
Delete the selected backup of a traffic statistics task. Deleting the backup of an
operating task will have no impact on this task.
Note:
BSC traffic statistics system supports the modification of task configuration information. If the configuration
information of a task is modified, the information before this modification will be saved as the backup.
II. Access
z Select a task whose backup is to be deleted, and then select [Task/Delete

Backup];
z Right-click the task to be deleted, and then select [Delete Backup] in the shortcut
menu.
2.10 Template Management
BSC traffic statistics system supports the function of template management. A template
can be used to create similar tasks. This can greatly improve the efficiency of creating
traffic statistics tasks. BSC traffic statistics templates can be divided into item template,
time template and object template.
2.10.1 Creating Item Template
I. Function
Create item templates. BSC system has some most frequently used item templates
preset, as shown in Table 2-14.
Table 2-14 BSC preset item template
Group No. Name Content

BSC Measurement Function 1.1 Common Statistic Template
1
BSC Measurement Function 1.1 Maintain Statistic Template
BSC Measurement Function 2.1 Access Statistic Template
2 BSC Measurement Function 2.2 Handover Statistic Template
BSC Measurement Function 2.3 Launch Handover Statistic Template
3 Cell Measurement Function 1.1 SDCCH Statistic Template
Cell Measurement Function 1.2 TCH-1 Statistic Template
Cell Measurement Function 1.3 TCH-2 Statistic Template
2-39
Group No. Name Content

Cell Measurement Function 1.4 Handover Statistic Template
Cell Measurement Function 1.5 Launch Handover Statistic Template
II. Access
z Select [Template/Statistic Item Template];
z Click .
III. Operation
The interface of item template management is shown in Figure 2-34.
Figure 2-34 Interface of item template management
When creating an item template, select the items needed from "All Statistic Items", and
add them to "Selected Statistic Item", and then click <Save Template>, and input the
template name in the pop-up dialog box, click <OK>.
Conform to the following rules when creating item templates:

z All statistic items of the same template should be of the same statistics function
type;
z The number of the initial statistic items should be smaller than 60.
2-40
2.10.2 Creating Time Template
I. Access
z Select [Template/Time Template];
z Click .
II. Operation
The operation of creating time template is similar to setting time property when creating
a traffic statistics task, see Set.
2.10.3 Creating Object Template
I. Access
z Select [Template/Object Template];
z Click .
II. Operation
The operation of creating object template is similar to setting object property when
creating a traffic statistics task, see
Set object property.
2.11 Customizing Item
I. Function
BSC traffic statistics system provides a large number of initial statistic items. With these
items, user can flexibly create customized items needed.
II. Access
z Select [Template/Custom Statistic Item];
z Click .
III. Operation
The interface of customizing items is shown in Figure 2-35.
2-41
Figure 2-35 Interface of customizing items 1
In the interface shown in Figure 2-35, the left part is for displaying Statistic Function
Type and Measure Type which is similar to directory tree, and the right part is for
displaying Item Name, Item ID and Express. After selecting a certain Measure Type,
system will display the information related to all initial items and pre-defined items of
this traffic statistics type.
Below is the description about creating customized items with "Intracell handover
success rate" as an example:
1) Make sure initial items for creating this customized item. In this example, Intra-cell
handover success rate = (Successful intracell handovers/Attempted intracell
handovers) % 100%;
2) Select the traffic statistics type of the statistic function type of the initial items. In
this example, [Cell Measurement Function/Intra-cell Handover Measurement
Function] is selected, and then click <Add Item>, as shown in Figure 2-36.
2-42
Figure 2-36 Creating customized item 1
3) The interface of adding customized items is shown in Figure 2-37. The

corresponding description is in Table 2-15.
Table 2-15 Interface of adding items
Field name Function

Statistic item Name Name of the customized item
Statistic Function Type Name of the statistic function type of the customized item
Measure Type Name of the measurement type of the customized item
Expression Formula of the customized item
All measurement items provided for this traffic statistics type and name, code and
Computational Object formula of the customized items. When inputting the formula, user can double-click
the box in the table to select the items needed
Constants frequently used when customizing items. Among them, the unit of
Constant "Statistic cycle" is minute. When inputting the formula, user can double-click the box
in the table to select the constants needed.
Operators used when displaying customized items. When inputting the formula, user
Operator
can double-click the box in the table to select the operators needed
Unit And Scope Unit and value range (%, 0, 100, 0) of the items whose values are percentage
<OK> Confirm the input customized item
<Cancel> Cancel the input customized item
Note:
The codes of the statistic items, numeric constants and operators can be input directly using the keyboard.
The item constant should be in [ ], and the numeric constants in { }. User can also double-click items,
constants and operators to input.
When creating a customized item, first input the name of the item in [Statistic Item
Name]. In this example, the name is "Intracell handover success rate". And then input
2-43
the formula following the method below: find and double-click the item "Successful
intracell handover" in [Computational Object], and then double-click "*" in [Operator:],
"100" in [Constant:] and "/" in [Operator:]. Finally, find and double-click "Attempted
intracell handovers" in [Computational Object:] as showed in Figure 2-37.
4) After confirming the above operation, the customized item is created. As shown in
Figure 2-38, this new item is at the bottom row of the item list.
2-44
IV. Deleting item
To delete an item, select the item to be deleted in the browsing interface of customized
items, and then click <Delete>.
2.12 Refreshing All Templates
I. Function
OMC traffic statistics system accepts the operations from multiple users simultaneously,
but the local traffic statistics system can display the modification made to the local
system. So this operation is for obtaining the currently newest templates.
Note:
By refreshing all templates, the up-to-date templates can be got from [AutoCfg/msmold/Version No.] of
OMC Server, i.e., the newest item template of bsctermmld.fml, the newest time template of bsctimemld.fml
and the newest object template of bscobjmld.fml can be taken to local WS.
II. Access
Select [Template/Refresh All].
2.13 Other Operations
2.13.1 Setting shortcut buttons in the Result Window
I. Function
Decide whether the shortcut buttons is displayed in the task result window. If this
function is activated, a tool bar shown in Figure 2-39 will appear in the task window.
This function is activated by default.
Figure 2-39 Shortcut buttons
2-45
II. Access
Select [Options/Shortcut for Result Window].
2.13.2 Customizing Setting
I. Function
Customize the color of window and print setting. The dialog box is shown in Figure 2-40
and Figure 2-41.
II. Access
Select [Options/Customizing];
III. Operation
The interface of customizing setting can be divided into two sub-interfaces.
The interface for color setting is shown in Figure 2-40. Select "Background color of text
in client widow", and then click <Color Setting> to open another interface for setting the
background color. The default setting of background color is white. To restore to the
default color, click <Reset to Default>.
Figure 2-40 Customizing setting color setting
The interface of print setting is shown in Figure 2-41. Click <Printer Setting> to enter
the interface of printer setting, paper size, paper source and printing direction. If these
properties have been configured in Windows, the setting here will be the same as those
in Windows. Click <Printer Font Setting> to set the printing font in the interface shown
2-46
in Figure 2-42. The default font of BSC traffic statistics system is "Arial", "Regular", "5",
"Black" and "Western". To restore to the default settings, click <System Default>.
Figure 2-41 Customizing setting printer setting
Figure 2-42 Setting the printing font
2-47
M900/M1800 Base Station Controller Chapter 3 Traffic Statistic Items
Chapter 3 Traffic Statistic Items
3.1 BSC measurement function
3.1.1 General
The statistic items in BSC Measurement Function are used to measure the traffic
statistic of all cells in the BSC. These items are listed in Table 3-1
The statistic items in BSC Measurement Function can be divided into following
classifications:
z Statistics of times that MSC rejects MSs service request, including the statistics
according to different rejection causes.
z The status of circuit service and packet service paging being transmitted and
implemented, including the measurement at A (Pb) interface and Abis interface.
z Measurement of circuit service and packet service CCCH overload.
z The status of circuit service and packet service immediate assignment request
and the implementation.
z Number of TCH seizure requests, the successful TCH seizures, TCH call drops,
TCH seizure requests for very early assignment, successful TCH seizures for very
early assignment, TCH call drops for very early assignment, SDCCH seizure
requests, successful SDCCH seizures, and SDCCH call drops.
z Dedicated measurement for assignment procedure, including the number of
unsuccessful assignments due to various causes.
z Measurement of TCH MR (measurement report), and independent measurement
of very early TCH assignment MR.
z Intra-BSC handover request and the implementation of the request, the
measurement of incoming BSC handover request and the implementation
(including the measurement of the unsuccessful incoming BSC handovers due to
various causes), outgoing BSC handover request and the implementation, and the
measurement of the handover due to various causes.
z The measurement of analytical items such as BSC handover success rate, call
drop rate, and traffic volume.
Table 3-1 Statistic items in BSC Measurement Function
No. Item name

1 Sum of CM service rejections
2 CM service rejections due to congestion
3 CM service rejections due to network failure
4 CM service rejections due to illegal MS
3-1
5 CM service rejections due to other causes

6 Average inter arrival time
7 Average inter of packet arrival time
8 Received circuit paging messages from MSC
9 Circuit paging commands to BTS
10 Successful circuit pagings of Abis interface
11 Circuit paging PCH overloads of Abis interface
12 Circuit paging RACH overloads of Abis interface
13 Packet paging commands to BTS
14 Packet paging PCH overloads of Abis interface
15 Immediate assignment requests
16 Packet immediate assignment request
17 Immediate assignment transmissions
18 Successful packet immediate assignment
19 Successful connections
20 TCH call drop connected
21 Attempted TCH seizures (all)
22 Successful TCH seizures
23 TCH call drop
24 Successful TCH seizures for very early assignment
25 TCH drop for very early assignment
26 Attempted SDCCH seizures (all)
27 Successful SDCCH seizures
28 Attempted SDCCH seizures meeting an SDCCH blocked state
29 SDCCH call drop
30 Assignment requests
31 Unsuccessful assignments
32 Unsuccessful assignments (equipment failure)
33 Unsuccessful assignments (requested terrestrial resource unavailable)
34 Unsuccessful assignments (terrestrial circuit already allocated)
35 Unsuccessful assignments (invalid message contents)
36 Unsuccessful assignments (radio interface failure, reversion to previous channel)
37 Unsuccessful assignments (no radio resource available)
38 Unsuccessful assignments (other causes)
39 Unsuccessful channel activation during assignment (NACK)
40 Channel activation timeout during assignment
41 Sum of TCH measurement reports (excluding very early assignment)
42 Sum of 1800 cell TCH measurement reports(excluding very early assignment)
43 Sum of configured TRX in the BSC
44 Sum of available TRX in the BSC
45 Attempted intracell handovers
46 Successful intracell handovers
47 Unsuccessful intracell handovers
48 Attempted intercell handovers
49 Intercell handovers
50 Attempted intercell handovers (9001800)
51 Attempted intercell handovers (1800900)
52 Successful intercell handovers
53 Successful intercell handovers (9001800)
54 Successful intercell handovers (1800900)
55 Intra BSC handovers
56 Attempted incoming BSC handovers
57 Attempted incoming BSC handovers (9001800)
58 Attempted incoming BSC handovers (1800900)
59 Attempted incoming BSC handovers (to 900)
60 Attempted incoming BSC handovers (to 1800)
61 Successful incoming BSC handovers
62 Successful incoming BSC handovers (9001800)
63 Successful incoming BSC handovers (1800900)
64 Successful incoming BSC handovers (to 900)
65 Successful incoming BSC handovers (to 1800)
3-2
66 Unsuccessful incoming BSC handovers

67 Unsuccessful incoming BSC handovers (equipment failure)
68 Unsuccessful incoming BSC handovers (requested terrestrial resource unavailable)
69 Unsuccessful incoming BSC handovers (Terrestrial Circuit Already Allocated)
70 Unsuccessful incoming BSC handovers (Invalid Message Contents)
71 Unsuccessful incoming BSC handovers (no radio resource available)
72 Unsuccessful incoming BSC handovers (other causes)
73 Unsuccessful channel activation in incoming BSC handovers (NACK)
74 Channel activation timeout in incoming BSC handovers
75 Incoming BSC handovers
76 Attempted outgoing BSC handovers
77 Attempted outgoing BSC handovers (from 900)
78 Attempted outgoing BSC handovers (from 1800)
79 Attempted outgoing BSC handovers (9001800)
80 Attempted outgoing BSC handovers (1800900)
81 Successful outgoing BSC handovers
82 Successful outgoing BSC handovers (from 900)
83 Successful outgoing BSC handovers (from 1800)
84 Successful outgoing BSC handovers (9001800)
85 Successful outgoing BSC handovers (1800900)
86 Outgoing BSC handovers
87 Unsuccessful outgoing BSC handovers with successful reversion
88 Unsuccessful outgoing BSC handovers with unsuccessful reversion
89 Attempted handovers for uplink quality
90 Attempted handovers for downlink quality
91 Attempted handovers for uplink strength
92 Attempted handovers for downlink strength
93 Attempted handovers for timing advance
94 Attempted handovers for better cell
95 Attempted handovers for traffic load
96 Attempted handovers for rapid rxlevel drop
97 Attempted handovers for response to MSC invocation
98 Attempted handovers for O&M intervention
99 Attempted handovers from underlaid subcell to overlaid subcell
100 Attempted handovers from overlaid subcell to underlaid subcell
101 Attempted handovers for directed retry
102 Attempted handovers for other causes
103 Extended cell attempted handovers for minimum timing advance
104 Successful handovers for uplink quality
105 Successful handovers for downlink quality
106 Successful handovers for uplink strength
107 Successful handovers for downlink strength
108 Successful handovers for timing advance
109 Successful handovers for better cell
110 Successful handovers for traffic load
111 Successful handovers for rapid rxlevel drop
112 Successful handovers for response to MSC invocation
113 Successful handovers for O&M intervention
114 Successful handovers from underlaid subcell to overlaid subcell
115 Successful handovers from overlaid subcell to underlaid subcell
116 Successful handovers for directed retry
117 Successful handovers for other causes
118 Extended cell successful handovers (minimum timing advance)
119 Successful BSC inter-layer handovers (upper to lower)
120 Successful BSC inter-layer handovers (lower to upper)
121 Unsuccessful BSC internal handovers with successful reversion
122 Unsuccessful BSC internal handovers with unsuccessful reversion
123 Circuit paging (A-interface) success rate
124 Ratio of paging channel overloads (%)
125 Rate of sending immediate assignment command
126 Intracell handover success rate
3-3
127 Intercell handover success rate

128 Incoming BSC handover success rate
129 Outgoing BSC handover success rate
130 Ratio of intraBSC interband handover to total intraBSC handover
131 Ratio of interBSC interband handover to total interBSC handover
132 Dual-band handover success rate
133 TCH call drop rate (%)
134 Traffic volume (excluding very early assignment) (Erl)
135 Traffic volume of 1800 cell (excluding very early assignment) (Erl)
136 Intra BSC radio handover success rate
137 Incoming BSC radio handover success rate
138 Outgoing BSC radio handover success rate
139 Percentage of TRX in good condition (%)
140 SDCCH call drop rate (%)
141 SDCCH blocking rate (%)
Many statistic items in BSC Measurement Function have the corresponding items of
cell level in Cell Measurement Function.
For the traffic status of the specified cell, you can register the related items in Cell
Measurement Function.
It is recommended that all statistic items in BSC Measurement Function should be

registered through 3 tasks after the BSC kickoff because these items are important
items for measuring network performance. It is recommended that the templates
should be used to register and the traffic statistic cycle should be 60 minutes.
Note:
1) A statistic task can contains at most 60 items. Therefore, 3 tasks are needed to register all items of BSC
Measurement Function.
2) Three default templates for BSC Measurement Function are provided.
The statistic object of BSC Measurement Function is the whole BSC. So there is no
object option on the object definition interface in OMC traffic statistics console.
3.1.2 Statistic Items
I. Sum of CM service rejections
z Description: in the MS originating immediate assignment procedure, first MS and

BSS establish RR connection, Then MS sends the detailed MM service request on
MM layer through CM SERVICE REQUEST to network side. This message can
carry the following MM service types: Mobile originating call establishment, packet
mode connection establishment, emergency call establishment, short message
3-4
service and supplementary service activation. BSS transparently transmits this

message to NSS. If NSS does not support or does not respond to this service
request for some reason, MSC sends CM SERVICE REJECT message to the MS.
BSC transparently transmits this message. See GSM 0408 protocol.
z Measurement point: as shown in Figure 3-1 A1, when BSC receives the DTAP
message of CM SERVICE REJECT from MSC, this item is measured regardless
the rejection cause carried in the message.
z Formula: none
MS BTS BSC MSC/VLR

1.L2-SABM
2.ESTABLISH INDICATION
3.CM SERVICE REQUEST
4.CM SERVICE REJECT
A1
B1
C1
D1
E1
A1: Sum of CM service rejections

B1: Sum of CM service rejections (congestion)
C1: Sum of CM service rejections (network failure)
D1: Sum of CM service rejections (illegal MS)
E1: Sum of CM service rejections (other reasons)
Figure 3-1 CM SERVICE REQUEST rejection process
II. CM service rejections due to congestion
z Description: if NSS cannot normally respond to a CM SERVICE REQUEST

message due to the congestion after receiving this message from MS MM layer,
NSS responds MS a CM SERVICE REJECT message in which the rejection
cause is congestion. See GSM 0408 protocol.
z Measurement point: as shown in the B1 in Figure 3-1, this item is measured when
BSC receives the DTAP message of CM SERVICE REJECT from MSC and the
rejection cause carried in this message is congestion.
z Formula: none
III. CM service rejections due to network failure
z Description: if NSS cannot normally respond to a CM SERVICE REQUEST due to

network failure after receiving this message from MS MM layer, NSS responds MS
a CM SERVICE REJECT message in which the rejection cause is network failure.
See GSM 0408 protocol.
3-5
z Measurement point: as shown in the C1 in Figure 3-1, BSC measures this item
when BSC receives the DTAP message of CM SERVICE REJECT from MSC, the
rejection cause carried in this message is network failure.
z Formula: none
IV. CM service rejections due to illegal MS

being unable to identify the MS after receiving this message from MS MM layer,
NSS responds MS a CM SERVICE REJECT message in which the rejection
cause is illegal MS. See GSM 0408 protocol.
z Measurement point: as shown in the D1 in Figure 3-1, This item is measured when
BSC receives the DTAP message of CM SERVICE REJECT from MSC with the
rejection cause carried in this message being illegal MS.
z Formula: none
V. CM service rejections due to other causes

the reasons other than above mentioned ones after receiving this message from
MS MM layer, NSS responds MS a CM SERVICE REJECT message. See GSM
0408 protocol.
z Measurement point: as shown in the E1 in Figure 3-1, This item is measured when
BSC receives the DTAP message of CM SERVICE REJECT from MSC with the
rejection cause carried in this message being other than the above mentioned
ones.
z Formula: none
VI. Average inter arrival time
z Description: This item describes the access frequency of MS. The RR entity of the
mobile station initiates the immediate assignment procedure by periodically
sending of CHANNEL REQUEST on the RACH to BTS, then BTS sends
CHANNEL REQUIRED to BSC. See GSM 0408.
z Measurement point: BSC measures the number of channel accesses every time
BSC receives CHANNEL REQUIRED message from BTS, and average inter
arrival time = statistic cycle/sum of channel access times in the statistic cycle.
z Formula: Statistic cycle*60/sum of channel access times in the statistic cycle
z Unit: Second
VII. Average inter of packet arrival time
z Description: This item describes the access frequency with the access cause
being packet call. The RR entity of the mobile station initiates the immediate
channel assignment procedure by periodically sending of CHANNEL REQUEST
3-6
on the RACH to BTS, then BTS sends CHANNEL REQUIRED to BSC. See GSM
0408 protocol.
z Measurement point: BSC measures number of channel access times every time
BSC receives CHANNEL REQUIRED message from BTS that the access cause is
packet call, and average inter of packet arrival time = statistic cycle/sum of
channel packet access times in the statistic cycle.
z Formula: Statistic cycle*60/sum of channel packet access times in the statistic
cycle
z Unit: Second
VIII. Received circuit paging messages from MSC
z Description: when an MS under the BSC is called for circuit service, MSC sends
the circuit service PAGING message to page the called MS from A interface (or
from Gb interface through SGSN). This item is used to measure the sum of the
received PAGING messages in the statistic cycle. The repeated PAGING
message is measured repeatedly. See GSM 0808 protocol.
z Measurement point: as shown in Figure 3-2 A1 and A2, this item is measured
every time BSC receives the circuit PAGING messages from A interface or Pb
interface (Huawei BSC-PCU interface).
z Formula: none
MS BTS BSC PCU SGSN M SC/VLR

1. PAGING
12'. PAGING
A1 13'. PAGING 11'. PAGING
REQUEST
REQUEST
A2
3. PAGING REQUEST 2. PAGING COM M AND
B1
4.CHANNEL REQUEST
5.CHANNEL REQUIRED
6.CHANNEL ACTIVATION
7. CHANNEL ACKTIVATION
ACKNOWLEDGE
8.IM M EDIATE ASSIGN
9. IM M EDIATE CM M AND
ASSIGNM ENT
10. PAGING 11. EST IND(PAGING
RESPONSE RESPONSE)
C1
A1: Received circuit paging messages from MSC

A2: Received circuit paging messages from MSC through GS interface
B1: Circuit paging commands to BTS
C1: Successful circuit paging of Abis interface
Figure 3-2 Circuit paging process
3-7
IX. Circuit paging commands to BTS
z Description: in the case an MS under the BSC is called for circuit service, BSC
sends PAGING COMMAND to the corresponding cell according to the cell
identification discriminator after receiving the circuit PAGING message from MSC
or PCU. This item is used to measure the paging delivery times at Abis. See GSM
0858 and 0408 protocol.
z Measurement point: as shown in the Figure 3-2 B1, this item is measured in every
cell every time BSC sends PAGING COMMAND message to the corresponding
cell.
z Formula: none
X. Successful circuit pagings of Abis interface
z Description: after a called MS receives PAGING REQUEST message from

network side, the paging response process is implemented. This MS reports
ESTABLISH INDICATION, with the cause value PAGING RESPONSE, to MSC if
it successfully seizes signaling channel. See GSM 0408 protocol.
z Measurement point: as shown in Figure 3-2 C1, this item is measured every time
BSC receives PAGING RESPONSE message from MS.
z Formula: none
XI. Circuit paging PCH overloads of Abis interface
z Description: BTS reports CCCH LOAD INDICATION message to BSC when

detecting the overload of PCH, then BSC measures this item and sends
OVERLOAD message to MSC simultaneously. See GSM 0858 protocol.
z Measurement point: as shown in Figure 3-3 A1, this item is measured when BSC
receives CCCH LOAD INDICATION message from BTS with the cause value
carried in the message being PCH overload.
z Formula: none
BT S BSC M S C /V LR
C C C H LO A D IN D IC A T IO N
A1
B1 O V E R LO A D
A1:Circuit paging PCH overloads of Abis interface

B1: Circuit paging RACH overloads of Abis interface
Figure 3-3 CCCH overload process
3-8
XII. Circuit paging RACH overloads of Abis interface
z Description: When detecting RACH overload, BTS reports CCCH LOAD

INDICATION to BSC, then BSC measures this item and implements the internal
flow control.
z Measurement point: as shown in Figure 3-3 B1, this item is measured when BSC
receives CCCH LOAD INDICATION message from BTS with the cause value
carried in the message being RACH overload.
z Formula: none
XIII. Packet paging commands to BTS
z Description: in the case an MS under the BSC is called for packet service, SGSN
sends PAGING REQUEST message to PCU to page this MS. PCU processes this
message and then sends PACKET PAGING message to BSC. According to the
cell identification discriminator carried in the PACKET PAGING message, BSC
sends PACKET PAGING REQUEST message to the corresponding cell. See
GSM 0408, 0460, 0360 protocols.
z Measurement point: as shown in Figure 3-4 A1, this item is measured in every cell
when BSC sends a PACKET PAGING REQUEST message to the corresponding
cell.
z Formula: none
MS BSC+BTS PCU SGSN

PAGING REQUEST
PACKET PAGING
PACKET PAGING REQUEST

A1
A1: Packet paging commands to BTS

Figure 3-4 Packet paging process
XIV. Packet paging PCH overloads of Abis interface
z Description: when detecting the overload of PCH seized by packet service (See
GPRS Related Measurement Function for packet combined channel relation),
BTS reports Packet CCCH Load Indication message to BSC. BSC forwards this
message to PCU and PCU initiates packet paging process.
z Measurement point: BSC measures this item upon reception of Packet CCCH
Load Indication message from BTS.
z Formula: none
3-9
XV. Immediate assignment requests
z Description: when an MS wants to obtain network service due to some reason, this
MS sends CHANNEL REQUEST message to BTS on RACH to request Dedicated
Control Channel, then BTS sends CHANNEL REQUIRED to BSC. This item
measures all the access cause value of CHANNEL REQUIRED.
z Measurement point: As shown in Figure 3-5 A1, this item is measured when BSC
receives CHANNEL REQUIRED message from BTS.
z Formula: none
MS BTS BSC
1.CHANNEL REQUEST
2.CHANNEL REQUIRED
3.CHANNEL ACTIVATION A1
ACKNOWLEDGE
5.IM M EDIATE ASSIGN CM M AND
B1
A1: Packet immediate assignment request

B1: Immediate assignment transmissions
Figure 3-5 immediate assignment transmission process
XVI. Packet immediate assignment request
z Description: to request channel for packet service, MS sends CHANNEL

REQUEST message to BTS on RACH and the access cause carried in the
message is Packet Call, then BTS sends CHANNEL REQUIRED to BSC. Upon
reception of this message, BSC forwards the request to PCU. See GSM 0408 and
0406 protocol.
z Measurement point: as shown in Figure 3-6 A1, BSC measures this item when
BSC receives CHANNEL REQUIRED message from BTS and if the access cause
carried in the message is Packet Call.
z Formula: none
MS BTS BSC HUAWEI PCU
CHANNEL REQUEST(PACKET CALL)
CHANNEL REQUIRED
A1 Packet Channel Request
Packet Im m ediate Assign Com m and

IM M EDIATE ASSIGN CM M AND
B1
A1: Packet immediate assignment request

B1: Successful packet immediate assignment
Figure 3-6 Packet immediate channel assignment procedure
3-10
XVII. Immediate assignment transmissions
z Description: in immediate assignment procedure, upon reception of the

CHANNEL REQUIRED message reported from BTS, BSC allocates and activates
a signaling channel for the MS. If BSC receives the CHANNEL ACTIVATION
ACKNOWLEDGE message from BTS indicating that the channel is ready, BSC
sends an IMMEDIATE ASSIGNMENT COMMAND message informing the MS to
access the dedicated signaling channel, which can be either SDCCH or TCH. This
item includes all access cause value of CHANNEL REQUIRED.
z Measurement point: As shown in Figure 3-5 B1, this item is measured when BSC
sends the IMMEDIATE ASSIGN COMMAND message to MS.
z Formula: none
XVIII. Successful packet immediate assignment
z Description: if the cause value carried in the CHANNEL REQUEST message sent
by MS on RACH is packet call, BSC forwards this message to PCU after receiving
the message. PCU initiates PDCH assignment procedure after receiving the
forwarded message and sends a Packet Immediate Assign Command message
(Huawei Pb interface) to BSC, then BSC converts this message into IMMEDIATE
ASSIGN COMMAND of Abis interface to BTS and BTS sends this message to MS.
This process is described in Figure 3-6. The measurement point of this item is
indicated in B1. See GSM 0408, 0460 protocol.
z Measurement point: upon reception of the Packet Immediate Assign Command
message from PCU, BSC measures this item and sends IMMEDIATE ASSIGN
COMMAND to BTS.
z Formula: none
XIX. Successful connections
z Description: the successful circuit service connection time in immediate

assignment procedure, if CC connection is to be established after MM connection
establishment of MOC, MOC sends a SETUP message to the network to request
the call setting up; then MSC responds a CALL PROCESSING message to MOC
and pages MTC simultaneously. After the MM connection establishment between
MSC and MTC, MSC sends a SETUP message to MTC to request the
establishment of CC connection. If permitting the call establishment, MTC
responds a CALL CONFIRM message to MSC and MSC forwards this message to
MOC. Having seized the traffic channel, MTC sends an ALERTING message to
MSC and MSC forwards this message to MOC. After that, MTC sends a
CONNECT message to MOC after its off-hook, MOC responds the CONNECT
ACKNOWLEDGE message. The call is set up and the MOC and MTC enter the
conversation state. See GSM 0408, 0858, 0808 protocols for detailed full process
of call connection establishment between the calling MS and the called MS.
3-11
Note:
This statistic item includes the "directed retry" in the channel assignment procedure. If the directed retry
takes place in the channel assignment procedure, this item is measured in the cell that actually allocates
channel, that is destination cell of directed retry.
z Measurement point: As shown in Figure 3-7 A, A, this item is measured when

BSC receives the DTAP type of CC message CONNECT or CONNECT
ACKNOWLEDGE. If MOC and MTC share the same BSC, both MOC and MTC
are measured.
z Formula: none
Ori-M S BSS1 M SC BSS2 Term i-M S

1.CM SERVICE
REQUEST
2.SETUP
3.CALL CONFIRM ED
4.ALARTING
4.CONNECT A1"
A1' 5.CONNECT ACKNOWLEDGE
Note:
A1' count in BSS1
A1" count in BSS2
A, A: Successful connections
Figure 3-7 CC connection establishment process
XX. TCH call drop connected
z Description: this item measures the number of call drop when MS is normally
during the conversation on radio channel. In the assignment procedure and
handover procedure, the establishment of a conversation is indicated by: in
assignment procedure BSC receives the CONNECT message and the CONNECT
ACKNOWLEDGE message from CC layer; in the incoming BSC handover
procedure the target cell sends HANOVER COMPLETE message to MSC;
successful intra BSC handover: the target cell sends HANDOVER PERFORMED
message to MSC when it detects the access of the MS. If the call drop occurs after
the above stages, it will be regarded as call drop connected.
z Measurement point:
1) Upon BSCs reception of ERROR INDICATION message from BTS due to an
abnormal connection in a radio link layer. See GSM 0508 protocol.
3-12
2) During MS conversation, BTS detects a fault in radio link layer or hardware; it

sends a CONNECTION FAILURE INDICATION message to BSC informing
the BSC this failure. See GSM 0508 protocol.
3) The timer expires when BSC waiting for the CLEAR COMMAND message
from MSC during outgoing BSC handover.
4) In Intra-BSC handover procedure, the target cell sends Inter Clear Request to
the source cell when the timer for the target cell to wait for HANDOVER
COMPLETE from MS expires, in this case, this item is measured in the
source cell.
5) In Intra-BSC handover procedure, the source cell, excluding the source cell
for directed retry, measures the item when the timer for the source cell to wait
for Inter Clear Request with cause value HANDOVER COMPLETE from the
target cell expires.
6) In Intra-BSC handover procedure, when the target cell AM/CM net-drive fails
(due to timeout or negative acknowledgement), the target cell sends Inter
Clear Request to source cell, in this case, this item is measured in the source
cell.
7) In the case that MS reverses to the original channel after intra BSC handover
fails, the source cell first releases the terrestrial connection but the AM/CM
re-net-drive fails (due to timeout or negative acknowledgement). In this case
this item is measured in the source cell.
8) The resource of the lower priority call will be preempted by the higher priority
call if MSC and BSC both supports preemption, which will cause call drop.
9) This item is measured when the RSL link of the TRX that the call is using
disconnects, which will cause call drop.
Note:
AM/CM net-drive: In assignment procedure or handover procedure, BSC establishes the terrestrial
connection in A-interface for a MS after it has successfully allocated radio channel.
z Formula: none
XXI. Attempted TCH seizures (all)
z Description: in the following procedures, if the requested channel type is SDCCH,

this item shall be measured after BSC receives a relevant request.
1) In immediate assignment procedure, MS sends CHANNEL REQUEST to
BTS to request radio channel.
2) In assignment procedure and incoming BSC handover procedure, MSC
requests radio resource by sending ASSIGNMENT REQUEST or
HANDOVER REQUEST to BSC.
3-13
3) In intra BSC handover, BSC itself requests a new channel for call.
Note:
SDCCH handover:
Handover happens on SDCCH.
Channel reallocation:
In the immediate assignment procedure, Huawei BSC supports channel reallocation. BSC initiates radio
channel allocation when it receives CHANNEL REQUIRED message from BTS. BSC allocates a TCH if
the access cause value of CHANNEL REQUIRED is "emergency call "or "call re-establishment" and BSC
supports very early assignment TCH. Otherwise, BSC allocates a SDCCH. BSC reallocates radio channel
automatically based on "GSM 0408" if BSC supports very early assignment of TCH and channel allocation
fails due to no radio resource available. In other words BSC allocates a TCH automatically if SDCCH
allocation fails and the access cause is not "location update", and similarly, BSC allocates a SDCCH
automatically if TCH allocation fails. So, to one CHANNEL REQUEST message, BSC measures both
SDCCH and TCH seizure times.
Very early assignment TCH:
If BSC allocates a TCH as a signaling channel in immediate assignment procedure, instead of the traffic
channel allocation procedure, the Mode Modify procedure can be implemented in the assignment
procedure.
Assignment SDCCH:
In the assignment procedure, MSC sends ASSIGNMENT REQUEST message to BSC to request for a
radio channel. BSC responses ASSIGNMENT COMPLETE message to MSC directly if the channel type in
the ASSIGNMENT REQUEST is SDCCH. In this case, BSC implements signaling or short message
transmission on the channel already allocated. BSC does not measure either "attempted SDCCH
seizures" or "successful SDCCH seizures" for it does not allocate a new channel. Instead, it measures the
times of "assignment requests" and "assignment success" after successfully sending ASSIGNMENT
COMPLETE message.
Discard CHANNLE REQUIRED in internal flow:
In the immediate assignment procedure, BSC receives CHANNEL REQUIRED messages from BTS. BSC
discards these messages if the system is too busy to respond. In this case, "attempted TCH" or "SDCCH
seizures" will be measured but "successful or unsuccessful channel seizures" will not be measured.
z Measurement point: the measurement point of this item is described in Figure 3-8,
Figure 3-9, Figure 3-10 and Figure 3-11 TCH-ATT-BSC1--TCH-ATT-BSC4.
1) In immediate assignment procedure, this item is measured when BSC
receives CHANNEL REQUIRED message from BTS and the requested
channel type is TCH.
2) In assignment procedure, this item is measured when BSC receives
ASSIGNMENT REQUEST message from MSC and the requested channel
type is TCH.
3-14
3) In intra BSC handover, the source cell sends Intercell Handover Request
message (Huawei defined message) to the target cell; if the handover is
taken place on TCH, this item is measured when the target cell receives this
message. The intra BSC handover includes the case that handover is taken
place in the same cell with the originating and the target cell being the same
one.
4) This item is measured when Huawei BSC receives the HANDOVER
REQUEST message from other BSC and the handover is taken place on
TCH.
z Formula: none
MS BTS BSC
CHANNEL REQUEST
CHANNEL REQUIRED
TCH-ATT-BSC1
CHANNEL ACTIVATION
CHANNEL ACKTIVATION ACKNOWLEDGE
TCH -ATT-BSC1: Attempted TCH seizures (all)

Figure 3-8 Immediate assignment procedure-channel seizure procedure
MS BTS BSC MSC
ASSIGNMENT REQUEST
TCH-ATT-BSC 2
QUEUEING INDICATION
(directly retry)HANDOVER REQIRED
(directly retry)HANDOVER REQUEST ACK
CHANNEL ACTICATION
CHANNEL ACTIVATION ACK
.ASSIGN CMMAND
SABM
ESTABLISH INDICATION
UA
ASSIGNMENT COMPLETE

Figure 3-9 Assignment procedure-channel seizure procedure
3-15
MS BTS' BSC Ori-Cell BSC Des-Cell BTS''

MR
Handover algorithm
Intercell Handover Request

TCH-ATT-BSC3
CH ACT
CH ACT ACK
Intercell Handover Response
HANDOVER COMMAND
HANDOVER ACCESS
SABM HANDOVER DETECT

UA
HANDOVER COMPLETE
Inter Clear Request (Handover Success)

Figure 3-10 Intra-BSC handover channel seizure procedure
MS Other BSC HUAWEI BSC HUAWEI BTS MSC

HANDOVER REQUIRED
HANDOVER REQUEST
TCH-ATT-BSC4
QUEUEING INDICATION
CH ACT
CH ACT ACK
HANDOVER REQUEST ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SABM
UA
HANDOVER COMPLETE

Figure 3-11 Incoming BSC handover channel seizure procedure
XXII. Successful TCH seizures
z Description: in very early assignment procedure, assignment procedure, and

handover procedure, BSC measures this item when MS successfully seizes the
allocated TCH. The successful directed retry is also measured as successful TCH
seizure: If there is no available channel after ASSIGNMENT REQUEST message
from MSC is sent to the cell of the BSC and the system supports directed retry,
3-16
then BSC initiates outgoing cell handover according to the information about
adjacent cell in MSs MR.
z Measurement point: this item is measured if TCH is successfully seized by the
following processes:
1) Upon BSCs reception of CHANNEL ACTIVATION ACKNOWLEDGE
message from BTS in very early assignment TCH process.
2) In the case the target cell of directed retry is located in other BSC and
directed retry succeeds, MSC sends CLEAR COMMAND message to the
originating BSC to release the original connection. This item is measured
when the originating BSC receives this message.
3) In the case the directed retry target cell is located in the same BSC and the
directed retry succeeds, target cell sends Inter Clear Request message to the
source cell to request to release the resource and the original connection.
This item is measured when the source cell receives this message.
4) This item is measured when BSC sends ASSIGNMENT COMPLETE
message to MSC after the assignment procedure is successfully
implemented.
5) In incoming BSC handover procedure. This item is measured when BSC
receives the HANDOVER DETECT message from BTS.
6) In the process of incoming internal inter cell handover and intracell handover
in BSC. BSC measures this item in the target cell when receiving
HANDOVER DETECTION message from BTS.
z Formula: none
XXIII. TCH call drop
z Description: in assignment procedure and traffic channel handover procedure,

BSC measures TCH call drop when the process implementation fails due to some
reason after MS has accessed the TCH assigned by BSC. Or this item is
measured when call drop takes place due to some reason when MS is in normal
seizure of TCH. After the above cases occur, BSC sends CLEAR REQUEST
message to MSC to request to clear the call.
z Measurement point: this item is measured if call drop occurs on TCH in the
following processes. Figure 3-12, Figure 3-13, Figure 3-14 A1 and A2 indicate the
main measurement points.
1) In the case TCH serves as traffic channel, this item is measured when BSC
receives ERROR INDICATION message from BTS due to an abnormal case
for a radio link layer connection. See GSM 0858 protocol.
2) In the case TCH is seized as traffic channel, this item is measured when BSC
receives the CONNECT FAILURE INDICATION message from BTS due to
3-17
an active connection has been broken for some reason such as TCH link
failure or hardware failure etc. See GSM 0508 for details.
3) In assignment procedure and handover procedure, this item is measured in
the case of the failure of decoding HANDOVER DETECT and HANDOVER
COMPLETE message.
4) In the case TCH serves as traffic channel, this item is measured when
incoming BSC handover is initiated and the timer for the target cell to wait for
HANDOVER COMPLETE message expires.
5) In the case TCH serves as traffic channel, this item is measured when
outgoing BSC handover is initiated and the timer for the source cell to wait for
CLEAR COMMAND message from MSC expires (T8 expires).
6) In Intra-BSC handover procedure, the target cell sends Inter Clear Request to
the source cell when the timer for the target cell to wait for HANDOVER
COMPLETE from MS expires, in this case, this item is measured in the
source cell.
7) In Intra-BSC handover procedure, the source cell, excluding the source cell
for directed retry, measures the item when the timer for the source cell to wait
for Inter Clear Request with cause value HANDOVER COMPLETE from the
target cell expires.
8) In Intra-BSC handover procedure, when the target cell AM/CM net-drive fails
(due to timeout or negative acknowledgement), the target cell sends Inter
Clear Request to source cell, in this case, this item is measured in the source
cell.
9) In the case that MS reverses to the original channel after intra BSC handover
fails, the source cell first releases the terrestrial connection but the AM/CM
re-net-drive fails (due to timeout or negative acknowledgement). In this case
this item is measured in the source cell.
10) The resource of the lower priority call will be preempted by the higher priority
call if MSC and BSC both supports preemption, which will cause call drop.
11) This item is measured when the RSL link of the TRX that the call is using
disconnects, which will cause call drop.
z Formula: none
3-18
MS BTS BSC MSC
ASSIGNMENT REQUEST
CHANNEL ACTICATION
ASSIGN CMMAND
SABM
UA
ERROR INDICATION
CONNECTION FAILURE INDICATION A1
A2
A1, A2: TCH call drop (BSC)

Figure 3-12 TCH drop for assignment
MS BSC' BSC Ori-Cell BSC Des-Cell BSC''
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SABM
UA
ERROR INDICATION
CONNECTION FAILURE A1
INDICATION
A2
A1, A2: TCH drop for very early assignment (BSC), TCH call drop (BSC)
Figure 3-13 Drop for Intra BSC handover
3-19
HANDOVER REQUIRED
HANDOVER REQUEST
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SABM
UA
ERROR INDICATION
A1
CONNECTION FAILURE INDICATION
A2
A1, A2: TCH drop for very early assignment (BSC), TCH call drop (BSC)
Figure 3-14 Incoming BSC TCH handover procedure
XXIV. Successful TCH seizures for very early assignment
z Description: BSC measures this item when MS successfully seizes the TCH
assigned by the network in very early assignment procedure (including the MS
access for various reasons).
z Measurement point: the measurement points of this item are indicated in
Figure 3-15 A1. This item is measured when BSC receivesCHANNEL
ACTIVATION ACKNOWLEDGE message from BTS in very early assignment
TCH process.
z Formula: none
MS BTS BSC
1.CHANNEL REQUEST
2.CHANNEL REQUIRED
3.CHANNEL ACTIVATION
ACKNOWLEDGE
5.IMMEDIATE ASSIGN CMMAND
ESTABLISH INDICATION(SAPI=0) A1
A1:Successful TCH seizures for very early assignment

Figure 3-15 Successful TCH seizures for very early assignment procedure
3-20
XXV. TCH drop for very early assignment
z Description: In intraBSC or interBSC handover procedure, if a handover occurs on

TCH and the speech data indication is signaling, this handover is regarded as a
signaling channel handover. BSC measures this item if MS has accessed the TCH
assigned by BSC but the implementation of the signaling channel handover fails
due to some reason. BSC also measures this item when call drop occurs due to
some reason after MS has established the normal connection on TCH and the
speech data indication is signaling. When the above cases occur, BSC sends a
CLEAR REQUEST message to MSC to clear the current connection.
z Measurement point: this item is measured if the channel type in the following
cases is TCH. The A1 and A2 in Figure 3-16, Figure 3-13, and Figure 3-14 indicate
the main measurement points of this item.
1) In the case TCH is seized as signaling channel, this item is measured when
BSC receives ERROR INDICATION message from BTS due to an abnormal
case for a radio link layer connection. See GSM 0858 protocol.
BSC receives CONNECTION FAILURE INDICATION message from BTS
due to an active connection has been broken for some reason such as TCH
link failure or hardware failure etc. See GSM 0858 protocol for details.
3) In the case TCH is seized as signaling channel, in incoming BSC handover
procedure, this item is measured in the target cell in the case of the failure of
decoding HANDOVER DETECT and HANDOVER COMPLETE message.
4) In the case TCH serves as signaling channel, this item is measured when
incoming BSC handover is initiated and the timer for the target cell to wait for
5) In the case TCH serves as signaling channel, this item is measured when
outgoing BSC handover is initiated and the timer for the source cell to wait for
CLEAR COMMAND message from MSC expires (T8 expires).
6) In the case TCH is seized as signaling channel, in Intra-BSC handover
procedure, this item is measured in the source cell when the timer for the
target cell or the source cell to wait for HANDOVER COMPLETE expires.
7) In the case TCH is seized as signaling channel, The resource of the lower
priority call will be preempted by the higher priority call if MSC and BSC both
supports preemption, which will cause call drop.
the RSL link of the TRX that the call is using disconnects, which will cause
call drop.
z Formula: none
3-21
MS BTS BSC
CHANNEL REQUEST
CHANNEL REQUIRED
CHANNEL ACTIVATION
SABM IMMEDIATE ASSIGN CMMAND

UA EST_IND
ERROR INDICATION
CONNECTION FAILURE INDICATION A1

A2
A1, A2: TCH drop for very early assignment (BSC)

Figure 3-16 TCH drop for very early assignment
XXVI. Attempted SDCCH seizures (all)
z Description: in immediate assignment procedure, MS sends CHANNEL

REQUEST to BTS to request radio channel. In incoming BSC handover procedure,
MSC requests radio resource by sending HANDOVER REQUEST to BSC. In intra
BSC handover, BSC itself requests a new channel for call. In those cases, this
item is measured when BSC receives SDCCH allocation request.
z Measurement point: the measurement point of this item is described in Figure 3-17,
Figure 3-19 and Figure 3-19 SD-ATT-BSC1--SD-ATT- BSC3.
1) In immediate assignment procedure, BSC measure this item when it receives
CHANNEL REQUIRED message from MS and if the requested channel type
is SDCCH.
2) For intra BSC handover on SDCCH, this item is measured when the target
cell receives Intercell Handover Request message (Huawei defined message)
from the source cell.
3) This item is measured if when Huawei BSC receives HANDVER REQUEST
message from other BSC and the handover is taken place on SDCCH.
z Formula: none
3-22
MS BTS BSC
CHANNEL REQUEST
SD-ATT-BSC1
CHANNEL REQUIRED
CHANNEL ACTIVATION
IM M EDIATE ASSIGN CM M AND

EST_IND
SD -ATT-BSC1: Attempted SDCCH seizures (all)


MR
Handover algorithm
SD-ATT-BSC2
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SABM
UA
HANDOVER COMPLETE
Inter Clear Request

(Handover Success)
SD-ATT-BSC2: Attempted SDCCH seizures (all)

3-23
HANDOVER REQUIRED
HANDOVER REQUEST
SD-ATT-BSC3
QUEUEING INDICATION
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SABM
UA
HANDOVER COMPLETE
SD -ATT-BSC3: Attempted TCH seizures (all)

XXVII. Successful SDCCH seizures
z Description: in immediate assignment procedure, assignment procedure, and

handover procedure, this item is measured when BSC receives the notification
from MS that MS has successfully seized the assigned SDCCH.
1) In immediate SDCCH assignment procedure, this item is measured when

BSC receives CHANNEL ACTIVATION ACKNOWLEDGE message from
BTS.
2) In the process of incoming BSC handover on SDCCH, BTS sends
HANDOVER DETECTION message to BSC. This item is measured when
BSC receives HANDOVER DETECTION.
3) In the process of incoming internal inter cell handover and intracell handover
in BSC, BTS sends HANDOVER DETECTION message to BSC. BSC
measures this item in the target cell when receiving this message.
z Formula: none
XXVIII. Attempted SDCCH seizures meeting an SDCCH blocked state
z Description: in immediate assignment procedure and handover procedure, this

item is measured if there is no available SDCCH for assignment when MS or MSC
requests BSS to assign SDCCH.
z Measurement point: this item is measured if there is no available SDCCH when
SDCCH is requested in the following cases:
1) BSC receives CHANNEL REQUIRED message from BTS.
3-24
2) BSC receives Intercell Handover Request message from other cell in the
same BSC.
3) BSC receives HANDOVER REQUEST message from other BSC.
z Formula: none
XXIX. SDCCH call drop
z Description: in immediate assignment procedure and handover procedure, BSC

measures SDCCH call drop when the process implementation fails due to some
reason after MS has accessed the SDCCH assigned by BSC. Or this item is
measured when call drop takes place due to some reason when MS is in normal
seizure of SDCCH. After the above cases occur, BSC sends CLEAR REQUEST
message to MSC.
1) This item is measured when BSC receives ERROR INDICATION message
from BTS due to an abnormal case for a radio link layer connection.
2) This item is measured when BSC receives CONNECTION FAILURE
INDICATION message from BTS because an active connection has been
broken for some reason such as SDCCH link failure or hardware failure (see
GSM 0508 for details).
3) In incoming BSC handover procedure on SDCCH, this item is measured in
the target cell in the case of the failure of decoding HANDOVER DETECT
and HANDOVER COMPLETE message.
4) In the process of incoming BSC handover on SDCCH, this item is measured
in the target cell when the timer for the target cell to wait for the HANDOVER
COMPLETE message expires.
5) In the process outgoing BSC handover on SDCCH, this item is measured
when the timer for the source cell to wait for CLEAR COMMAND message
from MSC expires (T8 expires).
6) In the process of intra BSC handover on SDCCH, this item is measured in the
source cell when the timer for the source cell or the target cell to wait for
7) This item is measured when the RSL link of the TRX that the call is running on
disconnect, which will cause call drop, this item measures call drop on
SDCCH for RSL disconnection.
z Formula: none
XXX. Assignment requests
z Description: the initial random access by the MS and "Immediate Assignment" to a

DCCH is handled autonomously by the BSS without reference to the MSC. After
the RR connection is established between MS and BSS, MS establishes the MM
and CC connection with MSC on this channel. MSC allocates or reallocates to the
3-25
MS a radio (and possibly terrestrial) resource in ASSIGNMENT REQUEST

message according to MSs CC connection request.
z Measurement point: as shown in Figure 3-20 A1, this item is measured when BSC
receives ASSIGNMENT REQUEST message from MSC.
z Formula: none
MS BTS BSC MSC

In Immediate Assignment or
IntraBSC Handover ASSIGNMENT REQUEST
A1
C1 D1
E1 G1
(directly retry)HANDOVER REQIRED G4 ASS FAILURE
H2
G5
(directly retry)HANDOVER FAILURE(REQUEST ACKNOWLEDGE)
G6
G5
MODE (MODIFY)
MODE (MODIFY) ACKNOLEDGE
H4
(NEGATIVE ACKNOWLEDGE,REJECT)
B 4B 5
G3 B3
CHANNEL ACKTIVATION G2
B 2 ASS FAILURE
CHANNEL ACKTIVATION ACKNOWLEDGE (NACK)
B6
F3
ASSIGN CMMAND
F3
SABM F1
ESTABLISH INDICATION H3
UA F1
F3
ASSIGNMENT COMPLETE H3 ASS FAILURE
F2 C2
ASSIGNMENT COMPLETE
A1: Assignment requests B2-B6: Unsuccessful assignments (equipment failure)

C1-C2: Unsuccessful assignments (requested
D1: Unsuccessful assignments (terrestrial circuit already allocated)
terrestrial resource unavailable)
E1:Unsuccessful assignments (invalid message F1-F3: Unsuccessful assignments (radio interface failure, reversion
contents)) to previous channel))
G1-G6: Unsuccessful assignments (no radio resource
H2-H4: Unsuccessful assignments (other causes))
available))
Figure 3-20 Assignment implementation process
XXXI. Unsuccessful assignments
z Description: BSS might fail to implement the assignment procedure due to some
reason after receiving ASSIGNMENT REQUEST message from MSC.
3-26
Note:
The relation between queue, directed retry and mode modify in assignment procedure.
In assignment procedure, upon reception of ASSIGNMENT REQUEST message, BSC first checks CIC
resource, then analyzes the CHANNEL TYPE in the message (See GSM 0808), at last compares the
analyzed CHANNEL TYPE with the currently seized one. The comparison result leads to three types of
options: mode modify, directed retry, or requesting a new channel.
CHANNEL TYPE contains channel rate and type and traffic type (speech/data indicator), speech encoding
algorithm and transparency indicator.
The channel re-allocation is initiated if the channel rate or type is different.
The mode modify is initiated if the traffic type (speech/data indicator), or speech encoding
algorithm/transparency indicator is different.
If all are consistent, the system uses the existing radio channel and allocates CIC for BSC net-drive.
So there are 5 subsequent processes after the reception of ASSIGNMENT REQUEST.
1). Mode modify.
2). Queue (if there is no available channel during re-allocation and the system supports queue).
3). Directed retry (if there is no available channel during re-allocation and the system supports directed
retry).
4). No available channel after the queue timeout; directed retry again if the system supports directed retry.
5). Normal assignment: new channel is assigned, activated, and then is normally seized by the MS.
z Measurement point: as shown in Figure 3-20, if BSS fails to respond to

ASSIGNMENT COMPLETE message to MSC due to some reason after receiving
ASSIGNMENT REQUEST message, this item is measured and BSS responds
ASSIGNMENT FAILURE message to MSC simultaneously. Figure 3-20
shows the reasons for unsuccessful assignment. This item is measured for the
unsuccessful assignment caused by any of these reasons.
z Formula: none
XXXII. Unsuccessful assignments (equipment failure)
z Description: the sum of unsuccessful assignments due to equipment failure. See

Unsuccessful assignments for the process.
z Measurement point: as shown in Figure 3-20 B2~B6, this item is measured in the
following case.
1) In assignment procedure, BSC assigns terrestrial circuit according to the CIC
specified by MSC but the assignment fails. In this case, this item is measured
and BSC requests MSC to clear the connection simultaneously.
2) In assignment procedure, this item is measured if BSCs AM/CM net-drive
fails (AM/CM returns net-drive failure or responds timeout) after the mode
modify is implemented and the radio channel has been successfully modified
according to the CHANNEL TYPE required by MSC.
3-27
3) If mode modify is initiated in assignment procedure, this item is measured

when BSC receives MODE MODIFY NEGATIVE ACKNOWLEDGE message
from BTS indicating the failure of mode modify after the MODE MODIFY
message is sent to BTS.
when the timer for BSC to wait for the response expires after the MODE
MODIFY message has been sent to BTS.
5) In assignment procedure, this item is measured when BSC receives Channel
Activation NACK or the timer for BSC to wait for Channel Activation ACK
expires.
z Formula: none
XXXIII. Unsuccessful assignments (requested terrestrial resource unavailable)
z Description: Unsuccessful assignments due to the requested terrestrial resource

unavailable. See Unsuccessful assignments for the process.
z Measurement point: as shown in Figure 3-20 C1~C2:
1) This item is measured when BSC detects the state of CIC requested in the
ASSIGNMENT REQUEST message received from MSC is unavailable.
2) This item is measured when AM/CM net-drive fails (AM/CM returns net-drive
rejection or timer for waiting for AM/CM expires) in assignment procedure,.
z Formula: none
XXXIV. Unsuccessful assignments (terrestrial circuit already allocated)
z Description: unsuccessful assignments due to terrestrial circuit already allocated.

See Unsuccessful assignments for the process.
z Measurement point: as shown in Figure 3-20 D1, in assignment procedure, this
item is measured when BSC detects the CIC requested in the ASSIGNMENT
REQUEST message received from MSC has already been allocated.
z Formula: none
XXXV. Unsuccessful assignments (invalid message contents)
z Description: unsuccessful assignments due to invalid message contents. See

z Measurement point: as shown in Figure 3-20 E1, this item is measured when BSC
detects the ASSIGNMENT REQUEST message contains invalid contents during
the message decoding, Which includes CHANNEL TYPE, CIC, Layer 3 header
information.
z Formula: none
3-28
XXXVI. Unsuccessful assignments (radio interface failure, reversion to

previous channel)
z Description: unsuccessful assignments due to radio interface failure with reversion

to previous channel
z Measurement point: as shown in Figure 3-20 F1-F3:
1) BSC measures this item when MS fails to access the new channel and
reverses to the old signaling channel due to Um interface failures after it
receives the ASSIGNMENT COMMAND message.
2) in assignment procedure, after sending the ASSIGNMENT COMMAND
message, if the timer for BSC to wait for ASSIGNMENT COMPLETE
message from MS expires, BSC measures this item and informs MSC to
clear the connection simultaneously.
z Formula: none
XXXVII. Unsuccessful assignments (no radio resource available)
z Description: unsuccessful assignments due to no radio resource available. See

z Measurement point: as shown in Figure 3-20 G1-G6,
1) This item is measured when BSC does not support the assigned channel.
2) This item is measured if there is no available channel when BSC assigns the
channel after receiving ASSIGNMENT REQUEST message and BSC does
not support queue and directed retry.
3) If mode modify is initiated in assignment procedure, the CHANNEL MODE
MODIFY message is sent to the MS, then the MS implement mode modify
and response CHANNEL MODE MODIFY ACKNOWLEDGE to BSC. This
item is measured when BSC receives this message from MS but meets error
when decode channel mode IE.
4) If there is no available channel when BSC receives ASSINGMENT
REQUEST message and the system supports queue, the assignment
procedure waits for channel resource; if idle channel is available before the
timer expires, the system allocates the channel successfully and the
assignment procedure goes normally; if there still no available channel
resource after the timer expires and the call doesnt support directed retry,
BSC measures the unsuccessful assignment due to channel unavailable.
5) If directed retry fails, this item is measured and ASSIGNMENT FAILURE
message is sent to MSC to request to clear the connection if the source cell of
directed retry is in one of the following cases.
a) There is no available target cell in the MR reported from MS, for directed
retry selects the target cell of handover according to the MR.
3-29
b) This item is measured in the source cell if the source cell receives Intercell
Handover Reject message from the target cell when directed retry is trying to
select other cell in the BSC.
c) This item is measured in the source cell if the MS reverses to the original
signaling channel when directed retry is trying to select other cell in the BSC.
d) This item is measured in the source cell when the timer for source cell to
wait for response from target cell expires when directed retry is trying to
select other cell in the BSC.
e) When directed retry is trying to select other cell in the BSC, the source cell
receives Inter Clear Request message (Huawei defined message) from the
target cell. However this message is not the one to inform the handover
completion but to inform the source cell of the directed retry failure and to
request to clear the connection. In this case, this item is measured in the
source cell.
f) When directed retry is trying to select other cell in the BSC, the source cell
sends HANDOVER COMMAND to MS to request the MS to access the new
channel. This item is measured if the source cell has not received Inter Clear
Request message (Huawei defined message) from the target cell after the
timer expires.
Note:
If directed retry is trying to select the target cell in other BSC and the directed retry process fails, the source
cell does not return assignment failure and the failure is not measured as an assignment failure item. The
failure is processed according to handover procedure.
z Formula: none
XXXVIII. Unsuccessful assignments (other causes)
z Description: unsuccessful assignments due to the following causes. See

z Measurement point: as shown in Figure 3-20 H2-H4,
1) When BSC detects IEs, such as, channel rate and type, speed encoding
algorithm, is incorrectly described in ASSIGNMENT REQUEST message.
2) In assignment procedure, BSC measures the item if the timer for BSC to wait
for ESTABLISH INDICATION expires when the ASSIGNMENT COMMAND
message has been sent to MS In this case BSC sends clear request to MSC
to clear the connection simultaneously.
3-30
3) If mode modify is initiated in assignment procedure, BSC does not receive

the acknowledge message from MS after sending mode modify message,
which leads to the timeout of BSC.
z Formula: none
XXXIX. Unsuccessful channel activation during assignment (NACK)
z Description: See Unsuccessful assignments.

z Measurement point: this item is measured when BSC receives CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE message from BTS after sending
CHANNEL ACTIVATION message to BTS to activate the newly- allocated
channel.
z Formula: none
XL. Channel activation timeout during assignment
z Description: See Unsuccessful assignments.

z Measurement point: this item is measured when the timer for BSC to wait for
CHANNEL ACTIVATION ACKNOWLEDGE from BTS expires after sending
CHANNEL ACTIVATION message to BTS to activate the newly- allocated
channel.
z Formula: none
XLI. Sum of TCH measurement reports (excluding very early assignment)
z Description: MS shall report a MR to the network every 480ms after the successful
seizure of TCH. See GSM 0408 protocol. This item is a parameter for traffic
calculation.
z Measurement point: this item is measured when BSC receives the MR of TCH
from BTS. This item excludes the MR of the TCH with speech/data indicator being
signaling. Both M900 and M1800 cells are included.
z Formula: none
XLII. Sum of 1800 cell TCH measurement reports(excluding very early

assignment)
z Description: MS shall report a MR to the network every 480ms after the successful
seizure of TCH. See GSM 0408 protocol. This item is a parameter for traffic
calculation.
z Measurement point: this item is measured when BSC receives the MR of TCH
from BTS. This item excludes the MR of the TCH with speech/data indicator being
signaling. Only M1800 cells are included.
z Formula: none
XLIII. Sum of configured TRX in the BSC
z Description: the sum of actually configured TRXs in the BSC.
3-31
z Measurement point: the configured TRXs that are shown in statistic database as
"install" are measured every time at the end of a statistic cycle.
z Formula: none
XLIV. Sum of available TRX in the BSC
z Description: sum of TRXs that managed by BSC and are in normal use state.
z Measurement point: this item is measured at the end of a statistic cycle.
z Formula: none
XLV. Attempted intracell handovers
z Description: Intracell handover is normally triggered by receiving strength,

receiving quality, O&M intervention, IUO, and its source cell and the target cell are
the same one. This item measures the times of handover attempts which are
initiated by a source cell in intracell handover. The measurement result can be
used to observe the frequency of the intracell handover initiated by BSC. Together
with Successful intracell handovers and Unsuccessful intracell handovers, this
item reflects the performance of intracell handover in the BSC. Related items:
Attempted intercell handovers, Attempted incoming BSC handovers, Attempted
outgoing BSC handovers.
Note:
In intraBSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in different
BMs of the same BSC, the adjacent cell will be treated as an idle cell, because system can't get the using
situation of channels in other BMs cell) has a higher priority to be selected as the target cell. If all adjacent
cells of the source cell are congested, system will still select the default adjacent cell which is the first one
of the adjacent cell candidates, even if it is congested. If the selected adjacent cell and the source cell are
the same one, this item will be measured. But the IUO handover (a special handover that still belongs to
intracell handover and occurs between the overlaid and underlaid subcell of an IUO cell) is an exception. If
the target subcell is congested, the handover cannot be initiated, and the measurement cannot be carried
out.
z Measurement point: After handover algorithm decision, the source cell sends an
Intercell Handover Request message to the target cell, and this item is measured if
the source cell is the same as the target cell.
z Formula: none.
XLVI. Successful intracell handovers

receiving quality, O&M intervention, IUO handover. If BSC receives a
HANDOVER COMPLETE message which shows an MS has been successfully
3-32
handed over to the target cell, then the BSC sends a HANDOVER PERFORMED
message to MSC to notify the success of this handover. This item measures the
times of successful internal intracell handovers. This item, together with Attempted
intracell handovers and Unsuccessful intracell handovers helps the user know the
performance of intracell handover in the BSC. Related items: Successful intercell
handovers, Successful incoming BSC handovers and Successful outgoing BSC
handovers.
z Measurement: Measured when BSC sends a HANDOVER PERFORMED
message to MSC after the MS has been successfully handed over to target cell
during the procedure of intracell handover, as shown in Figure 3-21 A1.
z Formula: none.
MS BTS BSC MSC/VLR

(Intracell handover)
.HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER PERFORMED
A1
A1: Successful intracell handover

Figure 3-21 Successful intracell handover
XLVII. Unsuccessful intracell handovers
z Description: After an intracell handover has been initiated, the source cell enters
the status of waiting for the Intercell Handover Response message. After BSC has
allocated channel, activated new channel, and sent a HANDOVER COMMAND
message to MS, the source cell enters the status of waiting for Inter Handover
Complete. After the MS has successfully accessed the new channel, the previous
channel will be released. During this period, any abnormality will cause failure of
the handover. This item measures the times of the unsuccessful intracell
handovers. This item, together with Attempted intracell handovers and Successful
intracell handovers helps the user know the performance of intracell handover in
the BSC. Related items: Unsuccessful incoming BSC handovers.
3-33
Note:
The following occasions might cause the failure of internal intracell handover:
1) Previous channel becomes invalid or the connection is terminated due to abnormality of radio resource
or terrestrial resource;
2) MS fails to access the destination channel due to poor radio environment or incorrect handover
parameter;
3) Handover is interrupted and original call is cleared because errors have been detected during BSS
internal processing;
4) BSS is informed to clear the call when MSC detects error.
1) Measured when the source cell receives the CONNECTION FAILURE
INDICATION message from BTS during the procedure of intracell handover,
as shown in Figure 3-22 A1 and A2.
2) During the procedure of intracell handover, after the source cell sends the
HANDOVER COMMAND message, if MS fails to access the destination
channel, the MS will return to the previous channel and send a HANDOVER
FAILURE message to the source cell. This item is measured when the source
cell receives this message, as shown in Figure 3-22 A3.
3) During the procedure of intracell handover, after the target cell receives
HANDOVER DETECT, it will send an Inter Clear Request message to source
cell for AM/CM net-drive fails or the timer waiting for HANDOVER
COMPLETE times out. This item is measured when the source cell receives
this message and then the source cell sends a CLEAR REQUEST message
to MSC simultaneously.
4) During the procedure of intracell handover, the source cell receives CLEAR
COMMAND from MSC. This item is measured in this case, as shown in
Figure 3-22 A4 and A5.
5) During the procedure of intracell handover, the target cell sends Intercell
Handover Reject to the source cell when it fails to prepare or activate the
channels (e.g. channel allocation failure, CHANNEL ACTIVATION
NEGATIVE ACKNOWLEDGE received, expiry of timer waiting for CHANNEL
ACTIVATION ACKNOWLEDGE). This item is measured when the target cell
receives this message.
6) During the procedure of intracell handover, the source cell receives ERROR
INDICATION from BTS. This item is measured in this case, as shown in
Figure 3-22 A6 and A7.
7) During the procedure of intracell handover, this item measured at the expiry
of the timer waiting for Intercell Handover Response in source cell.
3-34
8) During the procedure of intracell handover, this item measured at the expiry
of the timer waiting for Inter Clear Request in source cell.
z Formula: none.
MS BTS BSC MSC/VLR

(Intracell handover)
CONN FAIL IND
ERROR IND A1
A6 CLEAR COMMAND
.HANDOVER COMMAND A4
Old Channel
ERROR IND
A7
CONN FAIL IND
HANDOVER FAILURE A2
Old Channel
A3 CLEAR COMMAND
A5
HANDOVER COMPLETE
New Channel HANDOVER PERFORMED
A1~A7: Unsuccessful intracell handover

Figure 3-22 Unsuccessful intracell handover
XLVIII. Attempted intercell handovers
z Description: Internal intercell handover is normally triggered by receiving strength,

receiving quality, TA, traffic load, Response to MSC invocation, DIRECTED
RETRY, rapid rxlevel drop, better cell, O&M intervention. The source cell and
target cells are different ones in the same BSC. This item measures the times of
handover attempts which are initiated by a source cell in internal intercell
handover procedure. This item reflects the frequency of BSC initiating internal
intercell handovers. This item, together with Successful intercell handovers helps
the user know the performance of the Internal intercell handover. Related item:
Attempted intracell handovers, Attempted incoming BSC handovers and
Attempted outgoing BSC handovers.
Note:
In intra BSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in different
cells of the source cell are congested, system will still select the default adjacent cell which is the first one
of the adjacent cell candidates, even if it is congested so as to carry out the measurement of this item.
3-35
Intercell Handover Request message to the target cell, and this item is measured if
the source cell and the target cell are not the same cell.
z Formula: none.
XLIX. Intercell handovers
z Description: During the procedure of internal intercell handover, after successfully

activating the new channel, the target cell will inform the source cell that the
channel is ready. After receiving the information from the target cell, the source
cell will send HANDOVER COMMAND to the MS. This item measures the times of
this message being sent. This item, together with Attempted intercell handovers
helps the user observe the situation of handover failure due to abnormality during
the procedure of preparing new channel in the target cell, or together with
Successful intercell handovers know the situation of handover failure due to Um
interface abnormality. Related items: Intra BSC handovers, Incoming BSC
handovers and Outgoing BSC handovers.
z Measurement point: During the procedure of internal intercell handover, the
source cell sends the HANDOVER COMMAND message. This item is measured
in this case, as shown in Figure 3-23 A1.
z Formula: none.
MS BTS BSC MSC/VLR

(Intercell handover)
CHANNEL ACT
CHAN ACT ACK
HANDOVER COMMAND
A1
HANDOVER COMPLETE
HANDOVER PERFORMED
A1: internal intercell handover

Figure 3-23 internal intercell handover
L. Attempted intercell handovers (9001800)

target cells are different ones controlled by the same BSC. This item measures the
times of handover attempts from the source cell (GSM900) to the target cell
(GSM1800) in internal intercell handover. This item, together with Attempted
intercell handovers (1800900), helps the user know the frequency of interband
handovers, or together with Successful intercell handovers (9001800), know the
3-36
performance of interband handover in the BSC. Related items: Attempted intercell

handovers.
Note:
1) In intraBSC handover procedure, an idle adjacent cell (if the adjacent and the source cell are in different
cells of the source cell are congested, system will still select the default adjacent cell that is the first one of
the adjacent cell candidates, even if it is congested so as to carry out the measurement of this item.
2) Cell system type: GSM900 cell and GSM1800 cell.
GSM 900 cell: The frequency value of this cell is in GSM900 band, and the corresponding ARFCN is from
1 to 124.
GSM 1800 cell: The frequency value of this cell is in GSM1800 band, and the corresponding ARFCN is
from 512 to 885.
z Measurement point: Measured when the source cell (GSM900 cell) sends Intercell
Handover Request to the target cell (GSM1800 cell) after handover algorithm
decision.
z Formula: none.
LI. Attempted intercell handovers (1800900)

target cells are different ones controlled by the same BSC. This item measures the
times of handover attempts from the source cell (GSM1800) to the target cell
(GSM900) in internal intercell handover. This item, together with Attempted
intercell handovers (9001800), helps the user know the frequency of interband
handovers, or together with Successful intercell handovers (1800900) to know
the performance of interband handover in the BSC. Related items: Attempted
intercell handovers.
3-37
Note:
1) In intraBSC handover, an idle adjacent cell will be selected as the target cell. If all adjacent cells of the
source cell are congested, system will still select the default adjacent cell even if it is congested so as to
carry out the measurement of this item.
1 to 124.
from 512 to 885.
z Measurement point: Measured when the source cell (GSM1800 cell) sends
Intercell Handover Request to the target cell (GSM900 cell) after handover
algorithm decision.
z Formula: none.
LII. Successful intercell handovers
z Description: Internal intercell handovers can be classified into two types by the
handover cause: DIRECTED RETRY, non-DIRECTED RETRY (e.g. signal quality,
signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC
invocation, and O&M intervention). This item measures the times of successful
internal intercell handovers. This item, together with Attempted intercell handovers,
helps the user know the performance of internal intercell handover. Related items:
Successful intracell handovers, Successful incoming BSC handovers and
Successful outgoing BSC handovers.
1) Measured when BSC sends ASSIGNMENT COMPLETE to MSC after the MS
has successfully accessed in the target cell in internal intercell handover
procedure (handover cause: DIRECTED RETRY), as shown in Figure 3-24
A1.
2) Measured when BSC sends HANDOVER PERFORMED to MSC after the MS
has successfully accessed in the target cell in the internal intercell handover
procedure (handover cause: non-DIRECTED RETRY, e.g. signal quality,
signal strength, TA, traffic load, rapid rxlevel drop, better cell, Response to
MSC invocation, and O&M intervention), as shown in Figure 3-25 A1.
z Formula: none.
3-38
MS BTS BSC MSC/VLR
ASSIGNMENT REQUEST
HANDOVER COMMAND
HANDOVER COMPLETE
ASSIGNMENT COMPLETE
A1
B1
C1
A1: Successful internal intercell handover

B1: Successful internal intercell handover (900-1800)
C1: Successful internal intercell handover (1800-900)
Figure 3-24 Successful internal intercell handover (DIRECTED RETRY)
MS BTS BSC MSC/VLR

(Intercell Handover)
.HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER PERFORMED
A1
B1
C1
A1: Successful Internal intercell handover

B1: Successful Internal intercell handover (900-1800)
C1: Successful Internal intercell handover (1800-900)
Figure 3-25 Successful Internal intercell handover (not DIRECTED RETRY)
LIII. Successful intercell handovers (9001800)
internal intercell handovers from GSM900 cell to GSM1800 cell. This item,
together with Attempted intercell handovers (9001800) helps the user know the
performance of interband handover in the BSC. Related items: Successful
intercell handovers.
3-39
Note:
Cell system type: GSM900 cell and GSM1800 cell.
1 to 124.
from 512 to 885.
1) In internal intercell handover (handover cause: DIRECTED RETRY), the
source cell is a GSM900 cell and the target cell is a GSM1800 one. After MS
successfully accessed the target cell, BSC sends ASSIGNMENT
COMPLETE to MSC. This item is measured in this case, as shown in
Figure 3-24 B1.
2) In internal intercell handover (handover cause: non-DIRECTED RETRY, e.g.
signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better cell,
Response to MSC invocation, and O&M intervention), the source cell is a
GSM900 cell and the target cell is a GSM1800 one. After MS successfully
handed over to the target cell, BSC sends a HANDOVER PERFORMED
message to MSC. This item is measured in this case, as shown in
Figure 3-25 B1.
z Formula: none.
LIV. Successful intercell handovers (1800900)
internal intercell handovers from GSM1800 cell to GSM900 cell. This item,
together with Attempted intercell handovers (1800900) to know the performance
of inter-frequency handover in the BSC. Related items: Successful intercell
handovers.
Note:
1 to 124.
from 512 to 885.
3-40
1) In an internal intercell handover (handover cause: DIRECTED RETRY), the
source cell is a GSM1800 cell and the target cell is a GSM900 one. After MS
successfully handed over to the target cell, BSC sends an ASSIGNMENT
COMPLETE message to MSC. This item is measured in this case, as shown
in Figure 3-24 C1.
2) In a Internal intercell handover (handover cause: non-DIRECTED RETRY,
e.g. signal quality, signal strength, TA, traffic load, rapid rxlevel drop, better
cell, Response to MSC invocation, and O&M intervention), the source cell is a
GSM1800 cell and the target cell is a GSM900 one. After successfully
handed over to the target cell, BSC sends HANDOVER PERFORMED to
MSC. This item is measured in this case, as shown in Figure 3-25 C1.
z Formula: none.
LV. Intra BSC handovers
z Description: There are two types of intraBSC handovers: internal intracell

handover and internal intercell handover. After successfully activating the new
channel, the target cell informs the source cell that the channel is ready. After
receiving this information, the source cell sends a HANDOVER COMMAND
message to MS. This item measures the total times of sending this message in the
BSC, both in the cases of intercell handover and intracell handover. This item,
together with Intercell handovers, helps the user know the times of internal
intracell handovers. Related items: Intercell handovers, Incoming BSC handovers.
z Measurement point: During the procedure of intraBSC handover, the source cell
sends the HANDOVER COMMAND message. This item is measured in this case,
as shown in Figure 3-26 A1.
z Formula: none.
MS BTS BSC MSC/VLR

CHANNEL ACT
CHAN ACT ACK

.HANDOVER COMMAND
A1
HANDOVER COMPLETE
HANDOVER PERFORMED
A1: Intra BSC handover

Figure 3-26 Intra BSC handover
3-41
LVI. Attempted incoming BSC handovers
z Description: During the procedure of interBSC handover, source BSC initiates a

handover by sending a HANDOVER REQUIRED message to MSC. After
receiving this message, MSC sends a HANDOVER REQUEST message to target
BSC. The target BSC receives this message, and starts the preparation of new
channel. This item measures the times of target BSC receiving handover requests.
This item reflects the frequency of the handover from other BSCs to local BSC.
Together with Successful incoming BSC handovers, this item helps the user know
the performance of this type of handover in the local BSC. Related items:
Attempted intracell handovers, Attempted intercell handovers and Attempted
z Measurement point: During the procedure of interBSC handover, the target BSC
receives HANDOVER REQUEST from MSC. This item is measured in this case,
as shown in Figure 3-27 F1.
z Formula: none.
MS BTS BSC MSC/VLR

HANDOVER REQUEST
F1
CHANNEL ACT
CHAN ACT ACK

HANDOVER REQ ACK
HANDOVER DETECTION
HANDOVER COMPLETE
A1 ,B1 ,C1 , D1, E1
HANDOVER COMPLETE
A1: Successful incoming BSC handover

B1: Successful incoming BSC handover (900-1800)
C1: Successful incoming BSC handover (1800-900)
D1: Successful incoming BSC handover (to 900)
E1: Successful incoming BSC handover (to 1800)
F1: Successful incoming BSC handover
Figure 3-27 Successful incoming BSC handover
LVII. Attempted incoming BSC handovers (9001800)
z Description: During the procedure of interBSC handover, the target BSC receives
HANDOVER REQUEST from MSC, and then packs this message into IntoBSC
Handover Request, which will be sent to the BM which the target cell belongs to.
This item measures the times of the target BSC receiving IntoBSC Handover
Request when the source cell is a GSM900 one, and the target cell is a GSM1800
one. This item reflects the frequency of the handover from GSM900 cells of other
3-42
BSCs to GSM1800 cells of the local BSC. Together with Successful incoming BSC
handovers (9001800), this item helps the user know the performance of this type
of handover. Related items: Attempted incoming BSC handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of interBSC handover, the BM which

the target cell belongs to receives IntoBSC Handover Request, and the source cell
is a GSM900 one, the target cell is a GSM1800 one. This item is measured in this
case.
z Formula: none.
LVIII. Attempted incoming BSC handovers (1800900)
This item measures the times of the target BSC receiving IntoBSC Handover
Request when the source cell is a GSM1800 one, and the target cell is a GSM900
one. This item reflects the frequency of the handover from GSM1800 cells of other
BSCs to GSM900 cells of the local BSC. Together with Successful incoming BSC
handovers (1800900), this item helps the user know the performance of this type
of handover. Related items: Attempted incoming BSC handovers.
Note:
1 to 124.
from 512 to 885.

the target cell belongs to receives Inter IntoBSC Handover Request, and the
3-43
source cell is a GSM1800 one, while the target cell is a GSM900 one. This item is
measured in this case.
z Formula: none.
LIX. Attempted incoming BSC handovers (to 900)
This item measures the times of the target BSC receiving the Inter IntoBSC
Handover Request message when the target cell is a GSM900 one. This item
reflects of the handover to GSM900 cells of the local BSC. Together with
Successful incoming BSC handovers (to 900), this item helps the user know the
performance of this type of handover. Related items: Attempted incoming BSC
handovers.
the target cell belongs to receives Inter IntoBSC Handover Request, and the target
cell is a GSM900 one. This item is measured in this case.
z Formula: none.
LX. Attempted incoming BSC handovers (to 1800)
the HANDOVER REQUEST message from MSC, and then packs this message
into the Inter IntoBSC Handover Request message, which will be then sent to the
BM which the target cell belongs to. This item measures the times of the target
BSC receiving the Inter IntoBSC Handover Request message when the target cell
is a GSM1800 one. This item reflects of the handover to GSM1800 cells of the
local BSC. Together with Successful incoming BSC handovers (to 1800), this item
helps the user know the performance of this type of handover. Related items:
Attempted incoming BSC handovers.
Note:
1 to 124.
from 512 to 885.

the target cell belongs to receives Inter IntoBSC Handover Request, and the target
cell is a GSM1800 one. This item is measured in this case.
3-44
z Formula: none.
LXI. Successful incoming BSC handovers
the HANDOVER REQUEST message from MSC, and starts the preparation of
new channel. After the channel preparation has been done, and the MS has
accessed the target cell, the target BSC sends a HANDOVER COMPLETE
message to MSC to indicate that the handover has finished. This item, together
with Attempted incoming BSC handovers, helps the user know the performance of
this type of handover. Related items: Successful outgoing BSC handovers,
Successful intercell handovers, Successful intracell handovers.
receives HANDOVER COMPLETE, and forward it to MSC, as shown in
Figure 3-27 A1.
z Formula: none.
LXII. Successful incoming BSC handovers (9001800)
message to MSC to indicate that the handover has finished. This item measures
the successful handovers from other BSCs (GSM900 cells) to local BSC
(GSM1800 cell). This item, together with Attempted incoming BSC handovers
(9001800), helps the user know the performance of the handover of this type.
Related parameters: Successful incoming BSC handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of interBSC handover from GSM900

cell to GSM1800 cell, the target BSC receives the HANDOVER COMPLETE
message, and forwards it to MSC, as shown in Figure 3-27 B1.
z Formula: none.
3-45
LXIII. Successful incoming BSC handovers (1800900)
the successful handovers from other BSCs (GSM1800 cells) to local BSC
(GSM900 cell). This item, together with Attempted incoming BSC handovers
(1800900), helps the user know the performance of the handover of this type.
Related parameters: Successful incoming BSC handovers.
cell to GSM900 cell, the target BSC receives the HANDOVER COMPLETE
message, and forwards it to MSC, as shown in Figure 3-27 C1.
z Formula: none.
LXIV. Successful incoming BSC handovers (to 900)
the successful handovers from other BSCs to local BSC (GSM900 cell). This item,
together with Attempted incoming BSC handovers (to 900), helps the user know
the performance of the handover of this type. Related parameters: Successful
incoming BSC handovers.
z Measurement point: During the procedure of interBSC handover to GSM900 cell,
the target BSC receives the HANDOVER COMPLETE message, and forwards it
to MSC, as shown in Figure 3-27 D1.
z Formula: none.
LXV. Successful incoming BSC handovers (to 1800)
the successful handovers from other BSCs to local BSC (GSM1800 cell). This
item, together with Attempted incoming BSC handovers (to 1800), helps the user
know the performance of the handover of this type. Related parameters:
Successful incoming BSC handovers.
3-46
z Measurement point: During the procedure of interBSC handover to GSM900 cell,

the target BSC receives the HANDOVER COMPLETE message, and forwards it
to MSC, as shown in Figure 3-27 E1.
z Formula: none.
LXVI. Unsuccessful incoming BSC handovers
Handover Request, and sends the packed message to the BM which the target
cell belongs to request internal resource. And then the BSC checks the conditions
of incoming BSC handover. If the conditions can be satisfied, the BSC applies for
channel resource and generates HANDOVER COMMAND. And then the BSC
activates the new channel and waits for the access of an MS on the new channel.
On receiving HANDOVER COMPLETE from the MS, the target BSC sends a
HANDOVER COMPLETE message to MSC, and this handover is finished here. If
abnormality takes place during this period, BSC will send CLEAR REQUEST or
HANDOVER FAILURE to MSC to indicate that the BSC wishes to release the
associated dedicated resource(s). This means this incoming BSC handover fails.
This item, together with Attempted incoming BSC handovers helps the user know
the performance of this type of handover. The unsuccessful incoming BSC
handovers with all kinds of specified cause can help know the details that cause
the failure of BSC incoming handover. Related items: Unsuccessful outgoing BSC
handovers with successful reversion and Unsuccessful outgoing BSC handovers
with unsuccessful reversion.
Note:
The causes of unsuccessful incoming BSC handover can be:
1) Equipment failure;
2) Resource congestion or resource unavailable;
3) Message content invalid;
4) Timers time out;
5) Error detected during BSS internal processing, e.g. storing a message in buffer failed, No. of target cell
invalid, message decoding failed;
6) MSC informs BSC to clear resources.
1) During the procedure of interBSC handover, the target BSC processes the
HANDOVER REQUEST message. This item is measured if the following
abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE
3-47
message to MSC: message decoding failed, service type is speech or data

but no CIC contained or the contained CIC does not belong to the target BSC.
2) During the procedure of interBSC handover, the target BSC obtains the
specified CIC which is presented in the HANDOVER REQUEST message.
This item is measured when the following abnormalities occur, and in this
case, BSC will send a HANDOVER FAILURE message to MSC: the state of
the specified CIC is busy or abnormal, mismatching between circuit pool and
channel rate type or speech version.
3) During the procedure of interBSC handover, the target BSC sends a
HANDOVER FAILURE message to MSC for AM/CM net-drive fails. This item
is measured in this case send a HANDOVER FAILURE message to.
4) During the procedure of interBSC handover, the target BSC will check the
incoming BSC handover conditions. This item is measured when
abnormalities are detected, and BSC will at the same time send a
HANDOVER FAILURE message to MSC. The abnormalities include: Service
type is data but the channel rate type is unknown, fail to request channel,
ciphering algorithm is not supported.
5) During the procedure of interBSC handover, the target BSC fails to send a
CHANNEL ACTIVATION message. This item is measured in this case, and
at the same time, BSC sends a HANDOVER FAILURE message to MSC.
6) During the procedure of interBSC handover, the target BSC receives the
CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGEmessage. This item
is measured in this case, and at the same time, BSC will send a HANDOVER
FAILURE message to MSC, as shown in Figure 3-28 A1.
7) During the procedure of interBSC handover, the target BSC receives
CONNECTION FAILURE INDICATION from BTS after receiving
HANDOVER DETECTION. . This item is measured in this case, and at the
same time, BSC will send a HANDOVER FAILURE message to MSC, as
shown in Figure 3-28 A2.
HANDOVER DETECTION message or HANDOVER COMPLETE. This item
is measured when the decoding of these messages failed, and in this case,
BSC will send a CLEAR REQUEST message to MSC.
HANDOVER COMPLETE message to MSC. This item is measured when
BSC fails to send this message, and in this case, BSC will send a CLEAR
REQUEST message to MSC.
10) During the procedure of interBSC handover, the target BSC starts timer
waiting for the CHANNEL ACTIVATION ACKNOWLEDGEmessage. This
item is measured when this timer times out, and in this case, BSC will send a
HANDOVER FAILURE message to MSC.
3-48
11) During the procedure of interBSC handover, the target BSC starts timer Tqho
(maximum allowed queuing time for handover). This item is measured when
the timer times out, and in this case, BSC will send a HANDOVER FAILURE
message to MSC.
12) During the procedure of interBSC handover, the target BSC starts timer
waiting for HANDOVER DETECTION or timer waiting for HANDOVER
COMPLETE. This item is measured when these timers time out, and in this
case, BSC will send a CLEAR REQUEST message to MSC.
CLEAR COMMAND message from MSC. This item is measured in this case,
as shown in Figure 3-28 A3~A5.
z Formula: none.
MS BTS New BSC MSC/VLR Old BSC
HANDOVER REQUIRED
HANDOVER REQUEST
CHAN ACT
CLEAR COMMAND
CONN FAIL IND
A3
CHAN ACT NACK C1
A1
B1
CHAN ACT ACK D1
HANDOVER COMMAND CLEAR COMMAND
A4
HANDOVER DETECTION C2
New Channel CLEAR COMMAND
A5
CONN FAIL IND C3
A2
New Channel HANDOVER COMPLETE B2
HANDOVER COMPLETE
A1~A5 : Unsuccessful incoming BSC handover

B1~B2: Unsuccessful incoming BSC handover (equipment failure)
C1~C3: Unsuccessful incoming BSC handover (other causes)
D1 : Unsuccessful incoming BSC handover (NACK)
Figure 3-28 Unsuccessful incoming BSC handover
LXVII. Unsuccessful incoming BSC handovers (equipment failure)
z Description: This item measures the times of unsuccessful incoming BSC

handovers due to equipment failure during the procedure of interBSC handover.
Related items: Unsuccessful incoming BSC handovers.
HANDOVER REQUEST message. This item is measured when service type
is speech or data but the contained CIC does not belong to the target BSC,
and in this case, BSC will send a HANDOVER FAILURE message to MSC.
3-49

HANDOVER FAILURE message to MSC for AM/CM net-drive fails. This item
is measured in this case, and at the same time, BSC will send a HANDOVER
FAILURE message to MSC.
abnormalities of equipment failure are detected, and BSC will at the same
time send a HANDOVER FAILURE message to MSC.
4) During the procedure of interBSC handover, the target BSC fails to send a
CHANNEL ACTIVATION message. This item is measured in this case, and
at the same time, BSC sends a HANDOVER FAILURE message to MSC.
5) During the procedure of interBSC handover, when the target BSC receives
the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message, this
item is measured in this case, and at the same time, BSC will send a
HANDOVER FAILURE message to MSC, as shown in Figure 3-28 B1.
HANDOVER DETECTION message, and then receives the CONNECTION
FAILURE INDICATION message. This item is measured in this case, and at
the same time, THE BSC will send a HANDOVER FAILURE message to
MSC, as shown in Figure 3-28 B2.
7) During the procedure of interBSC handover, the target BSC starts the timer
waiting for the CHANNEL ACTIVATION ACKNOWLEDGE message. This
item is measured when this timer times out, and in this case, BSC will send a
HANDOVER FAILURE message to MSC.
z Formula: none.
LXVIII. Unsuccessful incoming BSC handovers (requested terrestrial resource

unavailable)

handovers due to requested terrestrial resource unavailable during the procedure
of interBSC handover. Related items: Unsuccessful incoming BSC handovers.
obtains the specified CIC in the handover request. This item is measured when the
specified CIC is abnormal, and in this case, BSC will send a HANDOVER
z Formula: none.
LXIX. Unsuccessful incoming BSC handovers (Terrestrial Circuit Already

Allocated)

handovers due to terrestrial circuit already allocated during the procedure of
interBSC handover. Related items: Unsuccessful incoming BSC handovers.
3-50
obtains the specified CIC in the handover request. This item is measured when the
specified CIC is busy, and in this case, BSC will send a HANDOVER FAILURE
message to MSC.
z Formula: none.
LXX. Unsuccessful incoming BSC handovers (Invalid Message Contents)

handovers due to invalid message contents during the procedure of interBSC
handover. Related items: Unsuccessful incoming BSC handovers.
will check the incoming BSC handover conditions. This item is measured when
service type is data but the channel rate type is unknown, and BSC will at the
same time send a HANDOVER FAILURE message to MSC.
z Formula: none.
LXXI. Unsuccessful incoming BSC handovers (no radio resource available)

handovers due to no radio resource available during the procedure of interBSC
handover. Related items: Unsuccessful incoming BSC handovers.
incoming BSC handover conditions. This item is measured when there is no
channel available, and BSC will at the same time send a HANDOVER
FAILURE message to MSC. For example, requesting for channel failed.
Tqho (maximum allowed queuing time for handover). This item is measured
when this timer times out, and in this case, BSC will send a HANDOVER
z Formula: none.
LXXII. Unsuccessful incoming BSC handovers (other causes)

handovers due to other causes rather than equipment failure, requested terrestrial
resource unavailable, terrestrial circuit already allocated, invalid message
contents and no radio resource available during the procedure of interBSC
handover. These causes include sending message failed, timeout of timer waiting
for HANDOVER DETECTION or timer waiting for the HANDOVER COMPLETE
message. Related items: Unsuccessful incoming BSC handovers.
HANDOVER REQUEST message. This item is measured if the following
3-51
abnormalities occur, and in this case, BSC will send a HANDOVER FAILURE
message to MSC: message decoding failed, service type is speech or data
but no CIC contained.
2) During the procedure of interBSC handover, the target BSC obtains the
specified CIC in the handover request. This item is measured when the
following abnormalities occur, and in this case, BSC will send a HANDOVER
FAILURE message to MSC: mismatching between circuit pool and channel
rate type or voice version.
abnormalities are detected, and BSC will at the same time send a
HANDOVER FAILURE message to MSC. The abnormalities include
ciphering algorithm not supported.
HANDOVER DETECTION message or the HANDOVER COMPLETE
message. This item is measured when the decoding of this message failed,
and in this case, BSC will send a CLEAR REQUEST message to MSC.
HANDOVER COMPLETE message to MSC. This item is measured when
BSC fails to send this message, and in this case, BSC will send a CLEAR
REQUEST message to MSC.
waiting for HANDOVER DETECTION or HANDOVER COMPLETE. This item
is measured when this timer times out, and in this case, BSC will send a
CLEAR REQUEST message to MSC.
7) During the procedure of interBSC handover, the target BSC receives CLEAR
COMMAND from MSC. This item is measured in this case, as shown in
Figure 3-28 C1-C3.
z Formula: none.
LXXIII. Unsuccessful channel activation in incoming BSC handovers (NACK)
z Description: This item measures the times of unsuccessful incoming handovers

due to unsuccessful channel activation in incoming BSC handovers (CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE received) which is a kind of
equipment failure. Related items: Unsuccessful incoming BSC handovers and
Unsuccessful incoming BSC handovers (equipment failure).
z Measurement point: This item is measured when the target BSC that is waiting for
the CHANNEL ACTIVATION ACKNOWLEDGE message receives the CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE message during the procedure of
interBSC handover. In this case, BSC will send a HANDOVER FAILURE message
to MSC, as shown in Figure 3-28 D1.
z Formula: none.
3-52
LXXIV. Channel activation timeout in incoming BSC handovers
z Description: This item measures the times of unsuccessful incoming handovers

due to timeout of timer for waiting for the CHANNEL ACTIVATION
ACKNOWLEDGE message which is a kind of equipment failure. Related items:
Unsuccessful incoming BSC handovers and Unsuccessful incoming BSC
handovers (equipment failure.
z Measurement point: This item is measured when timer waiting for the CHANNEL
ACTIVATION ACKNOWLEDGE message times out in the target BSC, and the
BSC will at the same time send a HANDOVER FAILURE message to MSC.
z Formula: none.
LXXV. Incoming BSC handovers
z Description: After the target BSC receives the HANDOVER REQUEST message
from MSC, it checks the conditions of incoming handover. If the check passes, the
target BSC will request channel resource, generate and store the HANDOVER
COMMAND message in buffer, and at the same time, it will send CHANNEL
ACTIVATION to BTS. After receiving CHANNEL ACTIVATION ACKNOWLEDGE,
the BSC packs the HANDOVER COMMAND message into HANDOVER
REQUEST ACKNOWLEDGE, which will then be sent to MSC. MSC transfers this
message to the source BSC, and the source BSC sends the HANDOVER
COMMAND message to MS. This item measures the times of target BSC sending
HANDOVER REQUEST ACKNOWLEDGE to MSC. This item, together with
Attempted incoming BSC handovers, helps the user know the unsuccessful
handovers due to abnormalities during the preparation of new channel in target
cell, together with Successful incoming BSC handovers, know unsuccessful
handovers due to radio interface abnormal. Related items: Intercell handovers and
Intra BSC handovers.
receives the CHANNEL ACTIVATION ACKNOWLEDGE message, and then
sends to MSC the HANDOVER REQUEST ACKNOWLEDGE message which
contains the HANDOVER COMMAND message, a message to be sent to MS.
This item is measured in this case, as shown in Figure 3-29 A1.
z Formula: none.
3-53
MS BTS BSC MSC/VLR

CHANNEL ACT
CHAN ACT ACK

HANDOVER REQ ACK
A1
HANDOVER DETECTION
HANDOVER COMPLETE
HANDOVER COMPLETE
A1: Incoming BSC handover

Figure 3-29 Incoming BSC handover
LXXVI. Attempted outgoing BSC handovers
z Description: InterBSC handover is normally triggered by receiving strength,

RETRY, rapid rxlevel drop, better cell or O&M intervention. The source cell and
target cell are from different BSCs. The source BSC sends HANDOVER
REQUIRED to MSC to initiate a handover. This message contains a list of
candidate cells for handover. At this stage, the source BSC does not know the
target cell which is selected by MSC or whether the selected cell is congested. It
only records the first cell in the candidate list as the default target cell. This item
measures the times of source BSC notifying MSC to initiate handover attempts.
This item reflects the frequecy of local BSC initiating interBSC handover. Together
with Successful outgoing BSC handovers, this item shows the performance of the
local BSC initiating interBSC handover. Related items: Attempted intracell
handovers, Attempted intercell handovers and Attempted incoming BSC
handovers.
z Measurement point: After handover algorithm decision, the source BSC sends
HANDOVER REQUIRED to MSC. This item is measured in this case, as shown in
Figure 3-30 A1.
z Formula: none.
3-54
MS BSC1 MSC/VLR BSC2
HANDOVER REQUIRED
A1, B1, C1 HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COMMAND
D1, E1, F1
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
CLEAR COMMAND
CLEAR COMPLETE
A1: Attempted outgoing BSC handovers

B1: Attempted outgoing BSC handovers (from 900)
C1: Attempted outgoing BSC handovers (from 1800))
D1: Outgoing BSC handovers
E1: Attempted outgoing BSC handovers (900-1800)
F1: Attempted outgoing BSC handovers (1800-900)
Figure 3-30 Attempted outgoing BSC handover
LXXVII. Attempted outgoing BSC handovers (from 900)

only knows the source cell (GSM900) that initiates this handover. This item
measures the times of source BSC (the source cell is GSM900 cell) notifying MSC
to initiate handover attempts. This item reflects the frequecy of GSM900 cells of
objective BSC initiating interBSC handover. Together with Successful outgoing
BSC handovers (from 900), this item shows the performance of this type handover.
Related items: Attempted outgoing BSC handovers.
3-55
Note:
1 to 124.
from 512 to 885.
z Measurement point: After handover algorithm decision, the source BSC (the
source cell is GSM900 cell) sends HANDOVER REQUIRED to MSC. This item is
measured in this case, as shown in Figure 3-30 B1.
z Formula: none.
LXXVIII. Attempted outgoing BSC handovers (from 1800)

only knows the source cell (GSM1800) that initiates this handover. This item
measures the times of source BSC (the source cell is GSM1800 cell) notifying
MSC to initiate handover attempts. This item reflects the frequency of GSM1800
cells of local BSC initiating interBSC handover. Together with Successful outgoing
BSC handovers (from 1800), this item shows the performance of this type
handover. Related items: Attempted outgoing BSC handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: After handover algorithm decision, the source BSC (the
source cell is GSM900 cell) sends HANDOVER REQUIRED to MSC. This item is
measured in this case, as shown in Figure 3-30 C1.
z Formula: none.
3-56
LXXIX. Attempted outgoing BSC handovers (9001800)

target cell are from different BSCs. This item reflects the frequency of local BSC
initiating interBSC handover from GSM900 cell to GSM1800 cell. Together with
Successful outgoing BSC handovers (9001800), this item shows the
performance of this type handover. Related items: Attempted outgoing BSC
Note:
1) The source BSC sends HANDOVER REQUIRED to MSC to initiate handover. This message contains a
list of candidate cells for handover. At this stage, the source BSC does not know the target cell which is
selected by MSC or whether the selected cell is congested. It only knows the source cell (GSM900) that
initiates this handover. If the item is measured at this moment, the result is not precise. The target cell and
its system type can only be known after receiving the first response message HANDOVER COMMAND
from MSC.
1 to 124.
from 512 to 885.

cell to GSM1800 cell, the source BSC receives the HANDOVER COMMAND
message from MSC. This item is measured in this case, as shown in Figure 3-30
E1.
z Formula: none.
LXXX. Attempted outgoing BSC handovers (1800900)

target cell are in different BSCs. This item reflects the frequency of local BSC
initiating interBSC handover from GSM1800 cell to GSM900 cell. Together with
Successful outgoing BSC handovers (1800900), this item shows the
performance of this type handover. Related items: Attempted outgoing BSC
3-57
Note:
1) The source BSC sends HANDOVER REQUIRED to MSC to initiate handover. This message contains a
list of candidate cells for handover. At this stage, the source BSC does not know the target cell which is
selected by MSC or whether the selected cell is congested. It only knows the source cell (GSM1800) that
initiates this handover. If the item is measured at this moment, the result is not precise. The target cell and
its system type can only be known after receiving the first response message HANDOVER COMMAND
from MSC.
1 to 124.
from 512 to 885.

cell to GSM900 cell, the source BSC receives the HANDOVER COMMAND
message from MSC. This item is measured in this case, as shown in Figure 3-30
F1.
z Formula: none.
LXXXI. Successful outgoing BSC handovers
z Description: During the procedure of interBSC handover, the source BSC sends a
HANDOVER COMMAND message to MS. After successfully accessed the target
cell, MSC sends CLEAR COMMAND (cause: handover success) to source BSC to
clear the previous resources. This handover successfully ends here. Together
with Attempted outgoing BSC handovers, this item shows the performance of this
type handover. Related items: Successful intracell handovers, Successful intercell
handovers and Successful incoming BSC handovers.
z Measurement point: During the procedure of interBSC handover, the source BSC
receives CLEAR COMMAND (cause: handover success) from MSC. This item is
measured in this case, as shown in Figure 3-31 A1.
z Formula: none.
3-58
HANDOVER REQUIRED
HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COMMAND
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
CLEAR COMMAND
A1, B1, C1 , D1, E1
CLEAR COMPLETE
A1: Successful outgoing BSC handover

B1: Successful outgoing BSC handover (from 900)
C1: Successful outgoing BSC handover (from 1800))
D1: Successful outgoing BSC handover (900-1800)
E1: Successful outgoing BSC handover (1800-900)
Figure 3-31 Successful outgoing BSC handover
LXXXII. Successful outgoing BSC handovers (from 900)
cell, MS sends CLEAR COMMAND (cause: handover success) to source BSC to
clear the previous resources. This handover successfully ends here. This item
measures the times of successful outgoing handover originated from GSM900 cell.
Together with Attempted outgoing BSC handovers (from 900), this item shows the
performance of this type handover. Related items: Successful outgoing BSC
handovers.
Note:
1 to 124.
from 512 to 885.
(source cell is GSM900 cell) receives CLEAR COMMAND (cause: handover
3-59
success) from MSC. This item is measured in this case, as shown in Figure 3-31
B1.
z Formula: none.
LXXXIII. Successful outgoing BSC handovers (from 1800)
measures the times of successful outgoing handover originated from GSM1800
cell. Together with Attempted outgoing BSC handovers (from 1800), this item
shows the performance of this type handover. Related items: Successful outgoing
BSC handovers.
(source cell is GSM1800 cell) receives CLEAR COMMAND (cause: handover
C1.
z Formula: none.
LXXXIV. Successful outgoing BSC handovers (9001800)
measures the times of successful outgoing handover from GSM900 cell to
GSM1800 cell. Together with Attempted outgoing BSC handovers (9001800),
this item shows the performance of this type handover. Related items: Successful
Note:
1 to 124.
from 512 to 885.

cell to GSM1800 cell, the source BSC receives CLEAR COMMAND (cause:
handover success) from MSC. This item is measured in this case, as shown in
Figure 3-31 D1.
3-60
z Formula: none.
LXXXV. Successful outgoing BSC handovers (1800900)
measures the times of successful outgoing handover from GSM1800 cell to
GSM900 cell. Together with Attempted outgoing BSC handovers (1800900), this
item shows the performance of this type handover. Related items: Successful
Note:
1 to 124.
from 512 to 885.

cell to GAM900 cell, the source BSC receives CLEAR COMMAND (cause:
handover success) from MSC. This item is measured in this case, as shown in
Figure 3-31 E1.
z Formula: none.
LXXXVI. Outgoing BSC handovers
z Description: During the procedure of interBSC handover, the target BSC finishes
allocating the new channel and generates the message HANDOVER COMMAND,
which is forwarded by MSC to the source BSC. After receiving this message, the
source BSC sends it to MS. This item measures the times of the source BSC
sending HANDOVER COMMAND. Together with Attempted outgoing BSC
handovers, this item shows the situation of unsuccessful handovers due to
abnormalities in the procedure of new channel preparation, and with Successful
outgoing BSC handovers, it shows the situation of unsuccessful handovers due to
radio interface abnormal. Related items: Incoming BSC handovers, Intra BSC
handovers and Intercell handovers.
z Measurement point: This item is measured when the source BSC receives
HANDOVER COMMAND from MSC, as shown in Figure 3-30 D1.
z Formula: none.
3-61
LXXXVII. Unsuccessful outgoing BSC handovers with successful reversion
HANDOVER COMMAND message to MS. If the MS cannot access the target cell
due to poor radio environment or handover parameter incorrect, it will send
HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel) to
the source BSC via the previous channel. BSC then forwards this message to
MSC. MSC requests the target BSC to clear the involved resources. The
connecting between the source BSC and MS remains the same. This item
measures the times of unsuccessful handover with successful reversion. Related
items: Unsuccessful incoming BSC handovers, Unsuccessful outgoing BSC
handovers with unsuccessful reversion and Unsuccessful BSC internal handovers
with successful reversion.
z Measurement point: This item is measured when the source BSC receives
HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel)
from MS during the procedure of interBSC handover, as shown in Figure 3-32 A1.
z Formula: none.
BTS BSC1 M S C /V L R
H A N D O V E R R E Q U IR E D
HANDOVER COM M AND HANDOVER COM M AND

H A N D O V E R F A IL U R E
A1 H A N D O V E R F A IL U R E
C O N N F A IL IN D
E R R O R IN D IC A T IO N B1
B2
C LEAR C O M M AN D
B3
C LEAR C O M M AN D
C LE AR C O M P LE TE
A1: Unsuccessful outgoing BSC handovers with successful reversion

B1~B3: Unsuccessful outgoing BSC handovers with unsuccessful reversion
Figure 3-32 Unsuccessful outgoing BSC handovers
LXXXVIII. Unsuccessful outgoing BSC handovers with unsuccessful reversion
z Description: During the procedure of interBSC handover, after the source BSC
sends the HANDOVER COMMAND message to MS, the connection between MS
and the source BSC is terminated before the connection established between MS
and the target BSC due to poor radio environment or equipment failure. When
BSC detects this situation, it will send a CLEAR REQUEST message to MSC to
request release the previous resources and the involved resources during
handover. This handover failed and the original service cannot be restored in the
3-62
source BSC. This item measures the times of unsuccessful handover with
unsuccessful reversion. Related items: Unsuccessful incoming BSC handovers,
Unsuccessful outgoing BSC handovers with successful reversion and
Unsuccessful BSC internal handovers with unsuccessful reversion.
1) This item is measured when the source BSC receives CONNECTION
FAILURE INDICATION from BTS during the procedure of interBSC handover,
as shown in Figure 3-32 B1.
2) This item is measured when the source BSC receives ERROR INDICATION
from BTS during the procedure of interBSC handover, as shown in
Figure 3-32 B2.
3) This item is measured when the source BSC receives CLEAR COMMAND
(cause: not handover success) from MSC during the procedure of interBSC
handover, as shown in Figure 3-32 B3.
4) This item is measured when the source BSC waiting for CLEAR COMMAND
(cause: handover success) from MSC times out during the procedure of
interBSC handover.
z Formula: none.
LXXXIX. Attempted handovers for uplink quality
z Description: At the beginning of a handover, BSC will receive Handover Indication

from LAPD module. This message contains the cause value of the handover,
according to which the BSC measures all kinds of handover attempts with specific
handover cause. This item measures the times of handovers (including internal
intracell handover, internal intercell handover and outgoing interBSC handover)
caused by uplink signal quality. This item shows the frequency of handover
caused by uplink signal quality in the BSC. Together with Successful handovers
for uplink quality, this item shows the performance of handovers of this type.
Related items: Attempted intracell handovers, Attempted intercell handovers and
z Measurement point: After handover algorithm decision, BSC sends Intercell
Handover Request (including internal intracell handover and internal intercell
handover) or HANDOVER REQUIRED (outgoing interBSC handover) due to
uplink signal quality. This item is measured in this case.
z Formula: none.
XC. Attempted handovers for downlink quality

handover cause. This item measures the times of handovers (including Internal
intracell handover, Internal intercell handover and outgoing interBSC handover)
3-63
caused by downlink signal quality. This item shows the frequency of handover
caused by downlink signal quality. Together with Successful handovers for
downlink quality, this item shows the performance of handovers of this type.
Handover Request (Internal intracell handover and internal intercell handover) or
HANDOVER REQUIRED (interBSC handover) due to downlink signal quality. This
item is measured in this case.
z Formula: none.
XCI. Attempted handovers for uplink strength

intracell handover, Internal intercell handover and outgoing interBSC handovers)
caused by uplink signal strength. This item shows the frequency of handover
caused by uplink signal strength. Together with Successful handovers for uplink
strength, this item shows the performance of handovers of this type. Related items:
Attempted intracell handovers, Attempted intercell handovers and Attempted
HANDOVER REQUIRED (interBSC handover) due to uplink signal strength. This
z Formula: none.
XCII. Attempted handovers for downlink strength

caused by downlink signal strength. This item shows the frequency of handover
caused by downlink signal strength. Together with Successful handovers for
downlink strength, this item shows the performance of handovers of this type.
3-64
HANDOVER REQUIRED (interBSC handover) due to downlink signal strength.

This item is measured in this case.
z Formula: none.
XCIII. Attempted handovers for timing advance

intercell handover and outgoing interBSC handover) caused by TA (because a
subscriber moves far away from the serving cell but close to the target cell while
talking, so the signal strength and the signal quality in serving cell drops and a
handover will be triggered.). This item shows the frequency of handover caused by
TA. Together with Successful handovers for timing advance, this item shows the
performance of handovers of this type. Related items: Attempted intracell
handovers, Attempted intercell handovers and Attempted outgoing BSC
handovers.
Handover Request (internal intercell handover) or HANDOVER REQUIRED
(interBSC handover) due to TA. This item is measured in this case.
z Formula: none.
XCIV. Attempted handovers for better cell

intercell handover and outgoing interBSC handover) caused by "better cell"
(adjacent cell with lower path loss (PBGT) or higher priority). This item shows the
frequency of handover caused by "better cell". Together with Successful
handovers for better cell, this item shows the performance of handovers of this
type. Related items: Attempted intracell handovers, Attempted intercell handovers
and Attempted outgoing BSC handovers.
(interBSC handover) due to "better cell". This item is measured in this case.
z Formula: none.
XCV. Attempted handovers for traffic load

3-65
intercell handover and outgoing interBSC handover) caused by traffic load. This
item shows the frequency of handover caused by traffic load. Together with
Successful handovers for traffic load, this item shows the performance of
handovers of this type. Related items: Attempted intracell handovers, Attempted
intercell handovers and Attempted outgoing BSC handovers.
(interBSC handover) due to traffic load. This item is measured in this case.
z Formula: none.
XCVI. Attempted handovers for rapid rxlevel drop

intercell handover and outgoing interBSC handover) caused by rapid rxlevel drop.
This item shows the frequency of handover caused by rapid rxlevel drop. Together
with Successful handovers for rapid rxlevel drop, this item shows the performance
of handovers of this type. Related items: Attempted intracell handovers,
Attempted intercell handovers, Attempted outgoing BSC handovers.
(interBSC handover) due to traffic load. This item is measured in this case.
z Formula: none.
XCVII. Attempted handovers for response to MSC invocation

intercell handover and outgoing interBSC handover) caused by Response to MSC
invocation (MSC sending HANDOVER CANDIDATE ENQUIRY to BSC which
causes handovers of multiple MSs in a cell). This item shows the frequency of
handover caused by Response to MSC invocation. Together with Successful
handovers for response to MSC invocation, this item shows the performance of
handovers of this type. Related items: Attempted intracell handovers, Attempted
intercell handovers and Attempted outgoing BSC handovers.
(interBSC handover) due to Response to MSC invocation. This item is measured
in this case.
3-66
z Formula: none.
XCVIII. Attempted handovers for O&M intervention

caused by O&M intervention (operation on O&M console which causes handovers,
such as forced handover, no call drop blocking (blocking channels, TRXs and
cells), BCCH mutual aid or TRX mutual aid). This item shows the frequency of
handover caused by O&M intervention. Together with Successful handovers for
O&M intervention, This item shows the performance of handovers of this type.
Handover Request (Internal intracell handover and internal intercell handovers) or
HANDOVER REQUIRED (interBSC handover) due to O&M intervention. This item
is measured in this case.
z Formula: none.
XCIX. Attempted handovers from underlaid subcell to overlaid subcell
z Description: Before originating handover, BSC will receive Handover Indication

from LAPD module. This message contains the cause value of handover. The
times of handover attempts of various can be measured according to this
message. This item measures the times of handovers from underlaid subcell to
overlaid subcell. This type of handover takes place only in IUO cells, and is
regarded as a specific intracell handover. This item shows the frequency of
handover from underlaid subcell to overlaid subcell. Together with Successful
handovers from underlaid subcell to overlaid subcell, this item shows the
handovers and Attempted handovers from overlaid subcell to underlaid subcell.
Handover Request (Internal intracell handover) due to handover from underlaid
subcell to overlaid subcell. This item is measured in this case.
z Formula: none.
C. Attempted handovers from overlaid subcell to underlaid subcell

handover cause. This item measures the times of handovers from overlaid subcell
3-67
to underlaid subcell. This type of handover takes place only in IUO cells, and is
regarded as intracell handover. This item shows the frequency of handover from
overlaid subcell to underlaid subcell. Together with Successful handovers from
overlaid subcell to underlaid subcell, this item shows the performance of
handovers of this type. Related items: Attempted intracell handovers and
Attempted handovers from underlaid subcell to overlaid subcell.
Handover Request (Internal intracell handover) due to handover from overlaid
subcell to underlaid subcell. This item is measured in this case.
z Formula: none.
CI. Attempted handovers for directed retry

intercell handover and outgoing interBSC handover) caused by directed retry (a
handover triggered because the current cell is congested during the procedure of
assignment). This item shows the frequency of handover caused by directed retry.
Together with Successful handovers for directed retry, this item shows the
performance of handovers of this type. Related items: Attempted intercell
handovers and Attempted outgoing BSC handovers.
Handover Request (internal intercell handovers) or HANDOVER REQUIRED
(interBSC handover) due to DIRECTED RETRY. This item is measured in this
case.
z Formula: none.
CII. Attempted handovers for other causes

caused by other causes (such as fast moving, handover cause being abnormal
value). This item shows the frequency of handover caused by other causes.
Together with Successful handovers for other causes, this item shows the
handovers, Attempted intercell handovers and Attempted outgoing BSC
handovers.
Handover Request (Internal intracell handover and internal intercell handovers) or
3-68
HANDOVER REQUIRED (interBSC handover) due to other causes. This item is

z Formula: none.
CIII. Extended cell attempted handovers for minimum timing advance
z Description: Before originating handover, BSC will receive Handover Indication

times of handover attempts of various can be measured according to this
message. This item measures the times of handovers (interBSC handovers)
caused by minimum timing advance (occurs only in single timeslot extended cells).
This item shows the frequency of handover caused by minimum timing advance.
Together with Extended cell successful handovers (minimum timing advance, this
item shows the performance of handovers of this type. Related items: Attempted
intracell handovers.
z Measurement point: In single timeslot extended cells, handovers can be triggered
by TA being smaller than minimum timing advance. After handover algorithm
decision, BSC sends Intercell Handover Request (internal intercell handovers).
z Formula: none.
CIV. Successful handovers for uplink quality
z Description: This item measures all successful handovers caused by uplink signal
quality, including internal intracell handover, internal intercell handover and
outgoing BSC handover. For intraBSC handovers, the message HANDOVER
PERFORMED to MSC contains the handover cause. For interBSC handovers, the
message HANDOVER REQUIRED corresponding to this handover contains the
handover cause. Together with Attempted handovers for uplink quality, this item
shows the performance of handovers of this type. Related items: Successful
intracell handovers, Successful intercell handovers and Successful outgoing BSC
handovers.
(cause: handover success) from MSC during the procedure of interBSC
handover caused by uplink signal quality.
2) During the procedure of Internal intracell handover/intercell handover caused
by uplink signal quality, after MS accessed the target cell, BSC will send
HANDOVER PERFORMED to MSC. This item is measured in this case.
z Formula: none.
CV. Successful handovers for downlink quality
z Description: This item measures all successful handovers caused by downlink

signal quality, including Internal intracell handover, Internal intercell handover and
3-69
outgoing handover. For intraBSC handovers, the message HANDOVER

handover cause. Together with Attempted handovers for downlink quality, this
item shows the performance of handovers of this type. Related items: Successful
handovers.
handover caused by downlink signal quality.
by downlink signal quality, after MS accessed the target cell, BSC will send
z Formula: none.
CVI. Successful handovers for uplink strength
z Description: This item measures all successful handovers caused by uplink signal
strength, including Internal intracell handover, Internal intercell handover and
outgoing handover. For intraBSC handovers, the message HANDOVER
handover cause. Together with Attempted handovers for uplink strength, this item
handovers.
handover caused by uplink signal strength.
by uplink signal strength, after MS accessed the target cell, BSC will send
z Formula: none.
CVII. Successful handovers for downlink strength
z Description: This item measures all successful handovers caused by downlink

signal strength, including Internal intracell handover, Internal intercell handover
and outgoing handover. For intraBSC handovers, the message HANDOVER
handover cause. Together with Attempted handovers for downlink strength, this
3-70
item shows the performance of handovers of this type. Related items: Successful
handovers.
handover caused by downlink signal strength.
by downlink signal strength, after MS accessed the target cell, BSC will send
z Formula: none.
CVIII. Successful handovers for timing advance
z Description: This item measures all successful handovers caused by TA (because

a subscriber moves far away from the serving cell but close to the target cell while
talking, so the signal strength and the signal quality in serving cell drops and a
handover will be triggered.), including Internal intercell handover and outgoing
handover. For intraBSC handovers, the message HANDOVER PERFORMED to
MSC contains the handover cause. For interBSC handovers, the message
HANDOVER REQUIRED corresponding to this handover contains the handover
cause. Together with Attempted handovers for timing advance, this item shows
the performance of handovers of this type. Related items: Successful intercell
handovers and Successful outgoing BSC handovers.
handover caused by TA.
2) During the procedure of BSC intercell handover caused by TA, after MS
accessed the target cell, BSC will send HANDOVER PERFORMED to MSC.
z Formula: none.
CIX. Successful handovers for better cell
z Description: This item measures all successful handovers caused by "better cell"
(adjacent cell with lower path loss (PBGT) or higher priority), including Internal
intercell handover and outgoing handover. For intraBSC handovers, the message
HANDOVER PERFORMED to MSC contains the handover cause. For interBSC
handovers, the message HANDOVER REQUIRED corresponding to this
handover contains the handover cause. Together with Attempted handovers for
better cell, this item shows the performance of handovers of this type. Related
items: Successful intercell handovers and Successful outgoing BSC handovers.
3-71
handover caused by "better cell".
2) During the procedure of BSC intercell handover caused by "better cell", after
MS accessed the target cell, BSC will send HANDOVER PERFORMED to
MSC. This item is measured in this case.
z Formula: none.
CX. Successful handovers for traffic load
z Description: This item measures all successful handovers caused by traffic load,
including Internal intercell handover and outgoing handover. For intraBSC
handovers, the message HANDOVER PERFORMED to MSC contains the
handover cause. For interBSC handovers, the message HANDOVER REQUIRED
corresponding to this handover contains the handover cause. Together with
Attempted handovers for traffic load, this item shows the performance of
handovers of this type. Related items: Successful intercell handovers and
handover caused by traffic load.
2) During the procedure of BSC intercell handover caused by traffic load, after
z Formula: none.
CXI. Successful handovers for rapid rxlevel drop
z Description: This item measures all successful handovers caused by rapid rxlevel
drop, including Internal intercell handover and outgoing handover. For intraBSC
Attempted handovers for rapid rxlevel drop, this item shows the performance of
handover caused by rapid rxlevel drop.
2) During the procedure of BSC intercell handover caused by rapid rxlevel drop,
after MS accessed the target cell, BSC will send HANDOVER PERFORMED
to MSC. This item is measured in this case.
3-72
z Formula: none.
CXII. Successful handovers for response to MSC invocation
z Description: This item measures all successful handovers caused by Response to

MSC invocation (MSC sending HANDOVER CANDIDATE ENQUIRY to BSC
which causes handovers of multiple MSs in a cell), including Internal intercell
handover and outgoing handover. For intraBSC handovers, the message
response to MSC invocation, this item shows the performance of handovers of this
type. Related items: Successful intercell handovers and Successful outgoing BSC
handovers.
handover caused by Response to MSC invocation.
2) During the procedure of BSC intercell handover caused by Response to MSC
invocation, after MS accessed the target cell, BSC will send HANDOVER
PERFORMED to MSC. This item is measured in this case.
z Formula: none.
CXIII. Successful handovers for O&M intervention
z Description: This item measures all successful handovers caused by O&M

intervention (operation on O&M console which causes handovers, such as forced
handover, no call drop blocking (blocking channels, TRXs and cells), BCCH
mutual aid or TRX mutual aid), including Internal intracell handover, Internal
intercell handover and outgoing handover. For intraBSC handovers, the message
O&M intervention, this item shows the performance of handovers of this type.
Related items: Successful intracell handovers, Successful intercell handovers and
handover caused by O&M intervention.
2) During the procedure of BSC intracell/intercell handover caused by O&M
intervention, after MS accessed the target cell, BSC will send HANDOVER
PERFORMED to MSC. This item is measured in this case.
z Formula: none.
3-73
CXIV. Successful handovers from underlaid subcell to overlaid subcell
z Description: This item measures all successful handovers from underlaid subcell
to overlaid subcell. This type of handover takes place only in IUO cells, which is a
specific type of internal intracell handover. For intraBSC handovers, the message
HANDOVER PERFORMED to MSC contains the handover cause. Together with
Attempted handovers from underlaid subcell to overlaid subcell, this item shows
the performance of handovers of this type. Related items: Successful intracell
handovers and Successful handovers from overlaid subcell to underlaid subcell.
z Measurement point: During the procedure of handover from underlaid subcell to
overlaid subcell, after MS accessed the overlaid subcell, BSC will send
z Formula: none.
CXV. Successful handovers from overlaid subcell to underlaid subcell
z Description: This item measures all successful handovers from overlaid subcell to
underlaid subcell. This type of handover takes place only in IUO cells, which is a
specific type of internal intracell handover. For intraBSC handovers, the message
HANDOVER PERFORMED to MSC contains the handover cause. Together with
Attempted handovers from overlaid subcell to underlaid subcell, this item shows
the performance of handovers of this type. Related items: Successful intracell
handovers and Successful handovers from underlaid subcell to overlaid subcell.
z Measurement point: During the procedure of handover from overlaid subcell to
underlaid subcell, after MS accessed the underlaid subcell, BSC will send
z Formula: none.
CXVI. Successful handovers for directed retry
z Description: This item measures all successful handovers caused by directed retry
(triggered the current cell is congested during the procedure of assignment),
including Internal intercell handover and outgoing handover. For intraBSC
Attempted handovers for directed retry, this item shows the performance of
handover caused by directed retry.
3-74
2) During the procedure of BSC intercell handover caused by directed retry,

after MS accessed the target cell, BSC will send HANDOVER PERFORMED
to MSC. This item is measured in this case.
z Formula: none.
CXVII. Successful handovers for other causes
z Description: This item measures all successful handovers caused by other causes
(fast moving, handover cause being abnormal value), including Internal intracell
handover, Internal intercell handover and outgoing handover. For intraBSC
Attempted handovers for other causes, this item shows the performance of
handovers of this type. Related items: Successful intracell handovers, Successful
intercell handovers and Successful outgoing BSC handovers.
handover caused by other causes (such as fast moving, handover cause
being filled with abnormal value).
2) During the procedure of BSC intercell handover caused by other causes
(such as fast moving, handover cause being filled with abnormal value), after
z Formula: none.
CXVIII. Extended cell successful handovers (minimum timing advance)
z Description: This item measures all successful handovers in a single timeslot

extended cell caused by minimum timing advance (occurs only in single timeslot
extended cells). It is a specific type of internal intracell handover. The message
HANDOVER PERFORMED sent to MSC contains the handover cause. Together
with Extended cell attempted handovers for minimum timing advance, this item
intracell handovers.
z Measurement point: After MS accessed the underlaid subcell, BSC will send
z Formula: none.
CXIX. Successful BSC inter-layer handovers (upper to lower)
z Description: This item measures the times of successful internal intercell

handovers in which the layer of the source cell is higher than the layer of the target
3-75
cell. Related items: Successful BSC inter-layer handovers (lower to upper) and
Successful intercell handovers.
Note:
The layers of cells are divided into four types, labelled with layer 1~4: 1. Pico, 2. Micro, 3. Macro, 4.
Umbrella. The higher layer has the lower priority. The upper layer normally refer to the one with the lower
priority between two layers, and the lower layer refers to the one with higher priority. This item aims at the
priority among the different type of layers, not at the different priority in the same type of layer.
z Measurement point: In internal intercell handover, after MS has been successfully

handed over to the target cell, the target cell sends Inter Clear Request to the
source cell to instruct the source cell to clear the involved resources. This item is
measured when the source cell receives this message, and the layer of the source
cell is higher than that of the target cell.
z Formula: none.
CXX. Successful BSC inter-layer handovers (lower to upper)
z Description: This item measures the times of successful BSC internal intercell
handovers in which the layer of the source cell is lower than the layer of the target
cell. Related items: Successful BSC inter-layer handovers (upper to lower and
Successful intercell handovers.
Note:
The layers of cells are divided into four types, labelled with layer 1~4: 1. Pico, 2. Micro, 3. Macro, 4.
Umbrella. The higher layer has the lower priority. The upper layer normally refers to the one with the lower
priority between two layers, and the lower layer refers to the one with higher priority. This item aims at the
priority among the different type of layers, not at the different priority in the same type of layer.
z Measurement point: In the internal intercell handover, after MS is successfully

source cell to instruct the source cell to clear the involved resources. This item is
measured when the source receives this message, and the layer of the source cell
is lower than that of the target cell.
z Formula: none.
3-76
CXXI. Unsuccessful BSC internal handovers with successful reversion
z Description: During the procedure of intraBSC handover, the source cell sends a
HANDOVER COMMAND message to MS. If the MS cannot be handed over to the
target cell due to poor radio environment or handover parameter incorrect, it will
send HANDOVER FAILURE (cause: Radio interface failure, reversion to old
channel) to the BSC via the previous channel. On receipt of this message the BSC
will release the involved resources associated with the target cell, and the
connecting between the BSC and MS remains the same. This item measures the
times of unsuccessful handover with successful reversion. Related items:
Unsuccessful intracell handovers, Unsuccessful outgoing BSC handovers with
successful reversion and Unsuccessful BSC internal handovers with unsuccessful
reversion.
z Measurement point: This item is measured when the source cell receives
HANDOVER FAILURE (cause: Radio interface failure, reversion to old channel)
from MS during the procedure of internal intracell handover or internal intercell
handover, as shown in Figure 3-33 A1.
z Formula: none.
MS BTS BSC MSC/VLR
.HANDOVER COMMAND
Old Channel
ERROR IND
B2
CONN FAIL IND
HANDOVER FAILURE B1
Old Channel
A1
HANDOVER COMPLETE
A1: Unsuccessful BSC internal handovers with successful reversion

B1~B2: Unsuccessful BSC internal handovers with unsuccessful reversion
Figure 3-33 Unsuccessful BSC internal handovers
CXXII. Unsuccessful BSC internal handovers with unsuccessful reversion
z Description: During the procedure of intraBSC handover, after the source BSC
sends the HANDOVER COMMAND message to MS, the connection between MS
and the source cell is terminated before the connection between MS and the target
cell set up due to poor radio environment or equipment failure. When BSC detects
this situation, it will send a CLEAR REQUEST message to MSC to clear the
previous resources and the involved resources during handover. This handover
3-77
failed and the original service cannot be restored. This item measures the times of
unsuccessful handover with unsuccessful reversion. Related items: Unsuccessful
intracell handovers, Unsuccessful BSC internal handovers with successful
reversion and Unsuccessful outgoing BSC handovers with unsuccessful
reversion.
1) This item is measured when the source cell receives CONNECTION
FAILURE INDICATION from BTS after sending the HANDOVER COMMAND
message to MS during the procedure of intraBSC handover, as shown in
Figure 3-33 B1.
2) During the procedure of intraBSC handover, after the target cell receives
HANDOVER DETECT, it will send an Inter Clear Request message to the
source cell if the timer waiting HANDOVER COMPLETE times out or AM/CM
net-drive fails. This item is measured when the source cell receives this
message, which will then send a CLEAR REQUEST message to MSC.
3) During the procedure of intraBSC handover, after sending HANDOVER
COMMAND to MS, the source cell receives ERROR INDICATION from BTS.
This item is measured in this case, as shown in Figure 3-33 B2.
4) During the procedure of intraBSC handover, the source cell starts the timer
waiting for Inter Clear Request after sending HANDOVER COMMAND to MS,
this item is measured when the timer times out.
z Formula: none.
CXXIII. Circuit paging (A-interface) success rate
z Description: See Successful circuit pagings of Abis interface and Received circuit
paging messages from MSC.
z Measurement point: none.
z Formula: Successful circuit pagings of Abis interface / Received circuit paging
messages from MSC
CXXIV. Ratio of paging channel overloads (%)
z Description: This item measures the percentage of PCH overloads in the paging
commands to BTS. See Circuit paging PCH overloads of Abis interface, Packet
paging PCH overloads of Abis interface, Circuit paging commands to BTS and
Packet paging commands to BTS.
z Formula: (Circuit paging PCH overloads of Abis interface + Packet paging PCH
overloads of Abis interface) / (Circuit paging commands to BTS + Packet paging
commands to BTS)
3-78
CXXV. Rate of sending immediate assignment command
z Description: See Immediate assignment transmissions and Immediate

assignment requests.
z Formula: Immediate assignment transmissions / Immediate assignment requests
CXXVI. Intracell handover success rate
z Description: See Successful intracell handovers, Attempted intracell handovers.

z Formula: Successful intracell handovers / Attempted intracell handovers
CXXVII. Intercell handover success rate
z Description: See Successful intercell handovers, Attempted intercell handovers.

z Formula: Successful intercell handovers / Attempted intercell handovers
CXXVIII. Incoming BSC handover success rate
z Description: See Successful incoming BSC handovers, Attempted incoming BSC

handovers.
z Formula: Successful incoming BSC handovers / Attempted incoming BSC
handovers
CXXIX. Outgoing BSC handover success rate
z Description: See Successful outgoing BSC handovers, Attempted outgoing BSC

handovers.
z Formula: Successful outgoing BSC handovers / Attempted outgoing BSC
handovers
CXXX. Ratio of intraBSC interband handover to total intraBSC handover
z Description: This item measures the percentage of the intraBSC interband

handovers in total internal intercell handovers. See Attempted intercell handovers,
Attempted intercell handovers (9001800), Attempted intercell handovers
(1800900).
z Formula: (Attempted intercell handovers (9001800) + Attempted intercell
handovers (1800900)) / Attempted intercell handovers
CXXXI. Ratio of interBSC interband handover to total interBSC handover
z Description: This item measures the percentage of the interBSC interband

handovers in total interBSC handovers. See Attempted incoming BSC handovers,
3-79
Attempted incoming BSC handovers (9001800), Attempted incoming BSC

handovers (1800900), Attempted outgoing BSC handovers, Attempted outgoing
BSC handovers (9001800), Attempted outgoing BSC handovers (1800900).
z Formula: (Attempted incoming BSC handovers (9001800 + Attempted incoming
BSC handovers (1800900) + Attempted outgoing BSC handovers (9001800) +
Attempted outgoing BSC handovers (1800900)) / (Attempted incoming BSC
handovers + Attempted outgoing BSC handovers)
CXXXII. Dual-band handover success rate
z Description: The dual-band handover success rate in a BSC, including intraBSC

dual-band handovers and interBSC dual-band handovers. See Successful
intercell handovers (9001800), Successful intercell handovers (1800900),
Attempted intercell handovers (9001800), Attempted intercell handovers
(1800900), Successful incoming BSC handovers (9001800), Successful
incoming BSC handovers (1800900), Attempted incoming BSC handovers
(9001800), Attempted incoming BSC handovers (1800900), Successful
outgoing BSC handovers (9001800), Successful outgoing BSC handovers
(1800900), Attempted outgoing BSC handovers (9001800), Attempted outgoing
BSC handovers (1800900).
z Formula: (Successful intercell handovers (9001800) + Successful intercell
handovers (1800900) + Successful incoming BSC handovers (9001800) +
Successful incoming BSC handovers (1800900) + Successful outgoing BSC
handovers (9001800)+ Successful outgoing BSC handovers (1800900)) /
(Attempted intercell handovers (9001800) + Attempted intercell handovers
(1800900) + Attempted incoming BSC handovers (9001800) + Attempted
incoming BSC handovers (1800900) + Attempted outgoing BSC handovers
(9001800) + Attempted outgoing BSC handovers (1800900))
CXXXIII. TCH call drop rate (%)
z Description: This item measures the percentage of TCH call drops in successful
TCH seizures. See TCH call drop and Successful TCH seizures.
z Formula: TCH call drop / Successful TCH seizures
CXXXIV. Traffic volume (excluding very early assignment) (Erl)
z Description: This item measures the total traffic volume of all cells in a BSC,
excluding the traffic volume during very early assignment. See Sum of TCH
measurement reports (excluding very early assignment).
3-80
z Formula: Sum of TCH measurement reports (excluding very early assignment) %

0.48 / Statistic Cycle (second)
CXXXV. Traffic volume of 1800 cell (excluding very early assignment) (Erl)
z Description: This item measures the total traffic volume of all GSM 1800 cells in a
BSC, excluding the traffic volume during very early assignment. See Sum of 1800
cell TCH measurement reports(excluding very early assignment).
z Formula: Sum of 1800 cell TCH measurement reports(excluding very early
assignment) % 0.48 / (Statistic Cycle (second))
CXXXVI. Intra BSC radio handover success rate
z Description: See Successful intracell handovers, Successful intercell handovers,

Intra BSC handovers.
z Formula: (Successful intracell handovers + Successful intercell handovers) / Intra
BSC handovers
CXXXVII. Incoming BSC radio handover success rate
z Description: See Successful incoming BSC handovers, Incoming BSC handovers.

z Formula: Successful incoming BSC handovers / Incoming BSC handovers
CXXXVIII. Outgoing BSC radio handover success rate
z Description: See Successful outgoing BSC handovers, Outgoing BSC handovers.

z Formula: Successful outgoing BSC handovers / Outgoing BSC handovers
CXXXIX. Percentage of TRX in good condition (%)
z Description: This item measures the percentage of good TRXs in total configured
TRXs. See Sum of available TRX in the BSC and Sum of configured TRX in the
BSC.
z Formula: Sum of available TRX in the BSC / Sum of configured TRX in the BSC
CXL. SDCCH call drop rate (%)
z Description: This item measures the percentage of SDCCH call drops in

successful SDCCH seizures. See SDCCH call drop and Successful SDCCH
seizures.
z Formula: SDCCH call drop / Successful SDCCH seizures
3-81
CXLI. SDCCH blocking rate (%)
z Description: This item measures the percentage of the attempted SDCCH

seizures meeting congestion in total attempted SDCCH seizures. See Attempted
SDCCH seizures meeting an SDCCH blocked state and Attempted SDCCH
seizures (all).
z Formula: Attempted SDCCH seizures meeting an SDCCH blocked state /
Attempted SDCCH seizures (all)
3.2 SCCP Measurement Function
3.2.1 General
In SS7 protocol system, SCCP (Signaling Connection Control Part) and MTP (Message
Transfer Part) provide a comprehensive network function for the data of application part.
SCCP provides two types of services: connectionless service and connection-oriented
service.
Connectionless service transmits signaling in the signaling network directly using the
routing function of SCCP and MTP without establishing signaling connection before
transmitting the signaling data. It is flexible and simple, and applicable for transmission
of small amount data.
Connection-oriented service needs to establish a signaling connection (virtual

connection) between calling SCCP and called SCCP in request-response mode before
transmitting signaling data. This connection is used to transmit signaling. When
transmission is completed, the relative message will be sent to request for releasing the
signaling connection. This type of service is applicable for transmission of large amount
data.
SCCP Measurement Function shows the flow of important messages under two types
of SCCP services at A interface. It can be used to analyze the operation of SCCP
system, and locate the faults at A interface signaling link layer.
All the statistic items are listed in Table 3-2.
Table 3-2 Statistic items in SCCP Measurement Function
No. Item name

1 UDT messages (O)
2 UDT messages (I)
3 XUDT messages (O)
4 XUDT messages (I)
5 CR messages (O)
6 CR messages (I)
7 CC messages (O)
8 CC messages (I)
3-82
9 CREF messages (O)

10 CREF messages (I)
11 DT1 messages (O)
12 DT1 messages (I)
13 RLSD messages (O)
14 RLSD messages (I)
15 RLC messages (O)
16 RLC messages (I)
3.2.2 Statistic items
I. UDT messages (O)
z Description: The connectionless service provided by SCCP uses the messages

UNITDATA (UDT) and EXTENDED UNITDATA (XUDT) to transmit user data.
UNITDATA does not have the capability of data segmenting/reassembling. The
maximum length of user data it can transmit is 128 octets. EXTENDED
UNITDATA is capable of segmenting/reassembling data. The maximum length of
user data it can transmit is 2048 octets.
z Measurement point: When SCCP service module of BSC sends UNITDATA, the
number of UDT messages (O) is increased by 1.
z Formula: none.
II. UDT messages (I)

z Measurement point: When SCCP service module of BSC receives UNITDATA
from the peer SCCP service module, the number of UDT messages (I) is
increased by 1.
z Formula: none.
III. XUDT messages (O)

z Measurement point: When SCCP service module of BSC sends EXTENDED
UNITDATA, the number of XUDT messages (O) is increased by 1.
3-83
z Formula: none.
IV. XUDT messages (I)

z Measurement point: When SCCP service module of BSC receives EXTENDED
UNITDATA from the peer SCCP service module, the number of XUDT messages
(I) is increased by 1.
z Formula: none.
V. CR messages (O)
z Description: Connection-oriented service needs to establish a signaling

connection (virtual connection) between calling SCCP and called SCCP in
request-response mode before transmitting signaling data. Figure 3-34 illustrates
the process of creating a successful signaling connection. The calling SCCP
sends CONNECTION REQUEST (CR) to the called SCCP to request the setup of
a signaling connection between the two entities. On reception of a CONNECTION
REQUEST, the called SCCP initiates the setup of the signaling connection, and
then sends CONNECTION CONFIRM (CC) to the calling SCCP. On reception of
CONNECTION CONFIRM, the calling SCCP completes the setup of the signaling
connection.
z Measurement point: When SCCP service module of BSC sends CONNECTION
REQUEST, the number of CR messages (O) is increased by 1.
z Formula: none.
SCCP-A SCCP-B
CONNECTION REQUEST
A B
CONNECTION CONFIRM
C D
A: CR messages (O)
B: CR messages (I)
C: CC messages (I)
D: CC messages (O)
Figure 3-34 Establishment of SCCP signaling connection (successful)
3-84
VI. CR messages (I)

request-response mode before transmitting signaling. Figure 3-34 illustrates the
process of creating a successful signaling connection. The calling SCCP sends
CONNECTION REQUEST (CR) to the called SCCP to request the setup of a
signaling connection between the two entities. On reception of a CONNECTION
REQUEST message, the called SCCP initiates the setup of the signaling
connection, and then sends CONNECTION CONFIRM (CC) to the calling SCCP.
On reception of CONNECTION CONFIRM, the calling SCCP completes the setup
of the signaling connection.
z Measurement point: When SCCP service module of BSC receives CONNECTION
REQUEST from the peer SCCP service module, the number of CR messages (I)
is increased by 1.
z Formula: none.
VII. CC messages (O)

connection.
CONFIRM, the number of CC messages (O) is increased by 1.
z Formula: none.
VIII. CC messages (I)

connection.
3-85

CONFIRM from the peer SCCP service module, the number of CC messages (I) is
increased by 1.
z Formula: none.
IX. CREF messages (O)

request-response mode before transmitting signaling. After calling SCCP initiates
CONNECTION REQUEST, the called SCCP or an intermediate node SCCP may
refuse the connection for some reason. In this case, they will initiates
CONNECTION REFUSED (CREF). See Figure 3-35.
REFUSED, the number of CREF messages (O) is increased by 1.
z Formula: none.
SCCP-A SCCP-B
CONNECTION REQUEST
CONNECTION REFUSED
A B
A: CREF messages (I)

B: CREF messages (O)
Figure 3-35 Establishment of SCCP signaling connection (failure)
X. CREF messages (I)

request-response mode before transmitting signaling. After calling SCCP initiates
CONNECTION REQUEST, the called SCCP or an intermediate node SCCP may
refuse the connection for some reason. In this case, they will initiates
CONNECTION REFUSED (CREF). See Figure 3-35.
REFUSED from the peer SCCP service module, the number of CREF messages (I)
is increased by 1.
z Formula: none.
3-86
XI. DT1 messages (O)

request-response mode before transmitting signaling data. DATA FORM 1 (DT1)
is used in transmitting signaling between SCCP signaling points. When a SCCP
needs to transmit signaling, it will send DT1 containing the signaling to the peer
SCCP. On reception of this DT1, the peer SCCP will also respond with a DT1
containing signaling. See Figure 3-36.
z Measurement point: When SCCP service module of BSC sends DATA FORM 1,
the number of DT1 messages (O) is increased by 1.
z Formula: none.
SCCP-A SCCP-B
CONNECTION REQUEST
CONNECTION CONFIRM
DATA FORM 1
DATA FORM 1
A B
A: DT1 messages (I)

B: DT1 messages (O)
Figure 3-36 Establishment of SCCP signaling connection and data transmission
XII. DT1 messages (I)

request-response mode before transmitting signaling data. DATA FORM 1 (DT1)
is used in transmitting signaling between SCCP signaling points. When a SCCP
needs to transmit signaling, it will send DT1 containing the signaling to the peer
SCCP. On reception of this DT1, the peer SCCP will also respond with a DT1
containing signaling. See Figure 3-36.
z Measurement point: When SCCP service module of BSC receives DATA FORM 1
from the peer SCCP service module, the number of DT1 messages (I) is increased
by 1.
z Formula: none.
XIII. RLSD messages (O)
z Destination: RELEASED (RLSD) is sent, in the forward or backward direction, to

indicate that the sending SCCP wants to release a signaling connection and the
3-87
associated resources. On reception of this message, the receiving SCCP should

release the connection and any other associated resources as well. A RELEASE
COMPLETE (RLC) message is sent in response to the RELEASED message
indicating that the RELEASED message has been received, and the appropriate
procedures have been completed. See Figure 3-37.
z Measurement point: When SCCP service module of BSC sends RELEASED, the
number of RLSD messages (O) is increased by 1.
z Formula: none.
SCCP-A SCCP-B
CONNECTION REQUEST
CONNECTION CONFIRM
DATA FORM 1
DATA FORM 1
RELEASED
A B
RELEASE COMPLETE
C D
A: RLSD messages (O)

B: RLSD messages (I)
C: RLC messages (I)
D: RLC messages (O)
Figure 3-37 Transmission of SCCP signaling
XIV. RLSD messages (I)

z Measurement point: When SCCP service module of BSC receives RELEASED
from the peer SCCP service module, the number of RLSD messages (I) is
increased by 1.
z Formula: none.
3-88
XV. RLC messages (O)

z Measurement point: When SCCP service module of BSC sends RELEASE
COMPLETE, the number of RLC messages (O) is increased by 1.
z Formula: none.
XVI. RLC messages (I)

z Measurement point: When SCCP service module of BSC receives RELEASE
COMPLETE from the peer SCCP service module, the number of RLC messages (I)
is increased by 1.
z Formula: none.
3.3 A-interface Operation and Management Statistic
3.3.1 General
"A-interface Operation and Management Statistic" reflect the O&M and running status
of BSC equipment, as well as concern the interworking between BSC and MSC,
including reset of MSC, reset of BSC, reset, fault and recovery of a single module in
BSC, the overall running status of A interface signaling, BSC's handling procedure after
MSC overload, etc. See Table 3-3 for the list of all the relevant statistic items.
Table 3-3 Statistic items in A-interface Operation and Management Statistic
No. Item name

1 BSC initiated reset
2 MSC initiated reset
3 Single module (BSC) initiated reset
4 Internal notifications of BSC reset
5 Internal notifications of MSC reset
6 Internal notifications of BM reset
3-89
7 BSC BM suspend
8 BSC BM resume
9 BSC overload
10 SS7 link connections
11 SS7 link breakdowns
I. BSC initiated reset
z Description: After the user initiates reset of BSC in BSC Maintenance System,
BSC Maintenance System sends an MT_RESET_RESOURCE message to BSC.
Upon receipt of the message, BSC shall execute the command. When BSC is
reset, all the calls within it shall be cleared (In the subsequent 128 seconds, the
establishment of new calls shall be prohibited). In the meantime, BSC shall send a
RESET message to MSC and await the response message (RESET_ACK). The
timer value for awaiting the RESET_ACK message is 150 second. BSC shall
resend the RESET message, if it cannot receive the RESET_ACK message
before the timer expires. Such repeat operations can be performed for max. 3
times. This statistic item is used calculate the number of RESET message sent
from BSC to MSC.
z Measurement point: Statistics will be made when BSC sends a RESET message
to MSC.
z Formula: none
II. MSC initiated reset
z Description: MSC sends a RESET message to BSC when it is reset. Upon receipt
of the RESET message, BSC returns a RESET_ACK message, and at the same
time, it clears all the CS calls (GPRS calls no impact) within BSC and prohibits the
establishment of new calls in the subsequent 128s. This item is used calculate the
number of times BSC receives RESET messages from MSC.
z Measurement point: Statistics will be made when BSC receives a RESET
message from MSC.
z Formula: none
III. Single module (BSC) initiated reset
z Description: When a single BM is reset, the calls in all the cells under this module
shall be cleared (The establishment of new calls shall be prohibited in the
subsequent 128s). At the same time, this BM shall notify other BMs to clear the
calls that occupy its A interface circuit resources. This item is used calculate the
number of times a single BM is reset. In the following cases, a single module shall
be reset.
1) The user resets a BM in BSC Maintenance System.
3-90
2) The communication between BM and AM/CM is resumed after interruption.

3) When the communication between BM and AM/CM is resumed after
interruption, the communication on A interface of BSC is in interruption state
(The SS7 links of the whole BSC are disconnected), but afterwards, BM
detects that the communication on A interface is resumed.
4) The first time BM detects that the communication on A interface is normal
after kickoff (At least 1 SS7 link is normal).
z Measurement point: Statistics will be made when a single BM is reset and calls are
cleared.
z Formula: none
IV. Internal notifications of BSC reset
z Description: This item is correlated with "BSC initiated reset". After user initiates
reset of BSC in BSC Maintenance System, the BM with the smallest module No.
among the BMs of BSC that work normally shall serve as the main control BM,
sends an INTER_BSC_RESET_IND message to the other BMs notifying them to
clear calls, and await the response messages. The timer value for awaiting the
response messages is 2 second. The BM shall resend the message if it has not
received the response messages before expiry of the timer. This statistic item is to
calculate the times of the main control BM notifying the other BMs to clear calls
during BSC reset.
z Measurement point: Statistics will be made when the other BMs receive an
INTER_BSC_RESET_IND message from the main control BM during BSC reset.
z Formula: none.
V. Internal notifications of MSC reset
z Description: This item is correlated with "MSC initiated reset". MSC sends a
RESET message to BSC when MSC is reset. After BSC receives the message,
the BM with the smallest module No. among the BMs of BSC that work normally
shall serve as the main control BM, return an RESET_ACK message to MSC,
clear all the CS calls (GPRS services are free from the impact) of itself, send an
INTER_MSC_RESET_IND message to the other BMs notifying them to clear CS
calls, and await the response messages. The timer value for awaiting the
response message is 2 second. The BM shall resend the message if it has not
received the response messages before expiry of the timer. This statistic item is to
calculate the times of the main control BM in BSC notifying other BMs to clear CS
calls after BSC receives a RESET message from MSC.
z Measurement point: After BSC receives a RESET message from MSC, the main
control BM sends an INTER_MSC_RESET_IND message to other BMs. When
the other BMs receive INTER_MSC_RESET_IND and clear CS calls, statistics will
be made.
z Formula: none.
3-91
VI. Internal notifications of BM reset
z Description: This item is correlated with "Single module (BSC) initiated reset".
When a single BM is reset, the BM shall send an INTER_BSC_BM_RESET_IND
message to other BMs notifying them to clear the calls that occupy its A interface
circuit resources, and await the response messages. The timer value for awaiting
the response message is 2 second. The BM shall resend the message if it has not
received the response message before expiry of the timer. This statistic item is to
calculate the times of a BM notifying other BMs to clear the calls that occupy its A
interface circuit resources when it is reset.
z Measurement point: Upon reset, a BM sends an INTER_BSC_BM_RESET_IND
message to other BMs. When the other BMs receive
INTER_BSC_BM_RESET_IND and clear the calls that occupy the A interface
circuit resources of that BM, statistics will be made.
z Formula: none.
VII. BSC BM suspend
z Description: "BM suspend" means that after the communication between AM/CM
and a BM in BSC is interrupted, the BM shall clear all the calls as well as prohibit
establishment of new calls in it, and disconnect its SS7 link. This statistic item is
used to calculate the number of times the communication between BM and
AM/CM is interrupted. The BM whose communication is interrupted is to make
statistics.
z Measurement point: Statistics will be made when BM detects that the
communication between AM/CM and itself is interrupted.
z Formula: none.
VIII. BSC BM resume
z Description: This statistic item is correlated with "BSC BM suspend". "BM resume"
means that the communication between BM and AM/CM is resumed after
interruption. This item is to calculate the times of that the communication between
BM and Am/CM is resumed after interruption. The BM whose communication is
interrupted is to make the statistics. BM will be automatically reset after its
communication with AM/CM is resumed. For relevant description, please refer to
"Single module (BSC) initiated reset".
z Measurement point: Statistics will be made when BM detects that its
communication with AM/CM is resumed after interruption.
z Formula: none.
IX. BSC overload
z Description: After overload occurs to MSC, MSC sends an OVERLOAD message

to BSC. Upon receipt of the OVERLOAD message, BSC starts the corresponding
flow control algorithm or raise the flow control level. According to the algorithm,
3-92
BSC shall discard a proportion of calls that are being established so as to lessen
the severity of MSC overload. According to the algorithm, if BSC no longer
receives any OVERLOAD messages from MSC within a period of time, the flow
control level will be automatically lowered, and the proportion of discarded calls
will be reduced until no flow control is required. This item is to calculate the times
of overload occur to MSC.
z Measurement point: Statistics will be made when BSC receives an OVERLOAD
message from MSC.
z Formula: none.
X. SS7 link connections
z Description: "SS7 link connection" refers to the normal connection of SCCP layer
between MSC and BSC on A interface. When the SCCP layer satisfies the
following conditions at the same time, the connection will be regarded as "normal".
Otherwise, it will be regarded as "breakdown".
1) Permitted by DPC
2) No congestion
3) SCCP available
This statistic item is to calculate the times of SCCP connection are resumed.
1) The first time BM detects that the SCCP connection on A interface is normal
after kickoff.
2) When BM detects that the state of SCCP connection on A interface has
changed from "breakdown" into "normal".
z Formula: none.
XI. SS7 link breakdowns
z Description: This statistic item is correlated with "SS7 link connections". When the
SCCP layer of BSC on A interface satisfies the following conditions at the same
time, the connection will be regarded as "normal". Otherwise, it will be regarded as
"breakdown".
1) Permitted by DPC
2) No congestion
3) SCCP available
This statistic item is to calculate the times of SCCP connection state changes from
"normal" into "breakdown".
z Measurement point: Statistics will be made when BM detects that the SCCP
connection on A interface is broken down.
z Formula: none.
3-93
3.4 A-interface Equipment Maintenance Statistic
3.4.1 General
"A-interface Equipment Maintenance Statistic" reflects the operations performed by

users to A interface trunk circuits and board equipment, including user-initiated block,
unblock, setting, reset, etc. See Table 3-4 for the list of all the relevant statistic items.
Table 3-4 Statistic items in A-interface Equipment Maintenance Statistic
No. Item name

1 Act of setting trunk circuit table dynamically
2 Act of unblocking circuits
3 Act of blocking circuits
4 Act of resetting circuits
5 Act of resetting FTC boards
6 Act of resetting SM boards
I. Act of setting trunk circuit table dynamically
z Description: The user implements dynamic data configuration to send the trunk
circuit table to one or more BMs. According to the data received, BM refreshes the
A interface circuit management table in memory. This statistic item is to calculate
the number of A interface trunk circuits in this BM after the A interface circuit
management table is updated(including the A interface trunk circuits that are not
installed)
z Measurement point: Statistics will be made when BM receives a trunk circuit table
from Data Management System.
z Formula: none.
II. Act of unblocking circuits
z Description: When the user performs an unblocking operation for A interface

circuits via BSC Maintenance System, BSC Maintenance System sends an
MT_OPEN_CIRCUIT message to the corresponding BM of BSC, which contains
the range of the to-be-unblocked circuits. Upon receipt of the message, BM
modifies the states of the circuits in the specified range, notifies MSC about the
state modifications through the GROUP_UNBLOCK_CIRCUIT and
UNBLOCK_CIRCUIT messages, and awaits the response message. BM will
resend the messages to MSC if it cannot receive a response message within 150
second. The max. number of resending is 2. This statistic item is to calculate the
times of the user performs unblocking operations in BSC Maintenance System.
3-94
z Measurement point: When BM modifies the states of circuits upon receipt of the
MT_OPEN_CIRCUIT message from BSC Maintenance System, statistics will be
made.
z Formula: none.
III. Act of blocking circuits
z Description: When the user performs a blocking operation for A interface circuits
via BSC Maintenance System, BSC Maintenance System sends an
MT_BLOCK_CIRCUIT message to the corresponding BM of BSC, which contains
the range of the to-be-blocked circuits. Upon receipt of the message, BM modifies
the states of the circuits in the specified range, notifies MSC about the state
modifications through the GROUP_BLOCK_CIRCUIT and BLOCK_CIRCUIT
messages, and awaits the response message. BM will resend the messages to
MSC if it cannot receive a response message within 150 second. The max.
number of resending is 2. If a circuit within the range is being occupied by a call,
the circuit state will be changed into "blocked" after the call is terminated. This
statistic item is to calculate the times of the user performs blocking operations in
BSC Maintenance System.
z Measurement point: When BM modifies the states of circuits upon receipt of the
MT_BLOCK_CIRCUIT message from BSC Maintenance System, statistics will be
made.
z Formula: none.
IV. Act of resetting circuits
z Description: When the user performs a reset operation for A interface circuits via
BSC Maintenance System, BSC Maintenance System sends an
MT_RESET_CIRCUIT message to the corresponding BM of BSC, which contains
the range of the to-be-reset circuits. Upon receipt of the message, BM changes
the states of the blocked circuits in the specified range into "idle", sends
RESET_CIRCUIT messages one by one to MSC, and awaits the response
messages. BM will resend the message to MSC if it cannot receive a response
message within 150 second. The max. number of resending is 2. Upon receipt of
the RESET_CIRCUIT message, MSC first judges whether the circuit is being
occupied by a call, clears the call if it occupies the circuit, and then returns
RESET_CIRCUIT_ACK message to BSC. This statistic item is to calculate the
number of times the user performs reset operations in BSC Maintenance System.
z Measurement point: When BM receives an MT_RESET_CIRCUIT message from
BSC Maintenance System, statistics will be made.
z Formula: none.
3-95
V. Act of resetting FTC boards
z Description: When the user resets FTC via BSC Maintenance System, BSC
Maintenance System sends a RESET_FTC message to the corresponding BM of
BSC. Upon receipt of the message, the BM implements reset operation for FTC.
This statistic item is to calculate the times of the user performs FTC reset
operations in BSC Maintenance System.
z Measurement point: When BM resets FTC after it receives a RESET_FTC
message from BSC Maintenance System, statistics will be made.
z Formula: none.
VI. Act of resetting SM boards
z Description: When the user resets an SM board via BSC Maintenance System,
BSC Maintenance System sends a RESET_SM message to the corresponding
BM in BSC. Upon receipt of the message, the BM implements reset operation for
the SM board. This statistic item is to calculate the times of the user performs SM
reset operations in BSC Maintenance System.
z Measurement point: When BM resets SM board after it receives a RESET_SM
message from BSC Maintenance System, statistics will be made.
z Formula: none.
3.5 A-interface Trunk Board Message Statistic
3.5.1 General
"A-interface Trunk Board Message Statistic" reflects the operational state of A interface
hardware equipment, including board reset, E1 trunk reset, fault and recovery. See
Table 3-5 for the list of all the relevant statistic items.
No. Item name

1 FTC board reset messages
2 FTC board errors
3 SM board reset messages
4 SM board errors
5 E3M board errors
6 E1 errors
7 E1 recovery
8 E1 warnings
3-96
I. FTC board reset messages
z Description: After FTC is successfully reset, a report is sent to BM, notifying it

about the success of FTC reset. Upon receipt of the message, BM sets the state of
the FTC as "normal", and sends configuration information (such as supporting of
TFO) to the FTC. This statistic item is to calculate the times of FTC reports
success of FTC reset to BM.
z Measurement point: When BM receives a message from FTC, indicating that the
FTC is successfully reset, statistics will be made.
z Formula: none.
II. FTC board errors
z Description: When an FTC fault is detected, BM will set the state of the FTC as
"faulty". This statistic item is to calculate the times of BM detects FTC faults.
z Measurement point: When BM detects that FTC becomes faulty, statistics will be
made.
z Formula: none.
III. SM board reset messages
z Description: After an SM board is successfully reset, a report is sent to BM,

notifying it about the success of SM reset. Upon receipt of the message, BM sets
the state of the SM board as "normal". This statistic item is to calculate the times of
the SM board reports success of SM reset to BM.
z Measurement point: When BM receives a message from a SM board, indicating
that the SM board is successfully reset, statistics will be made.
z Formula: none.
IV. SM board errors
z Description: When an SM board fault is detected, BM will set the state of the SM
board as "faulty". This statistic item is to calculate the times of BM detects SM
board faults.
z Measurement point: When BM detects that an SM board becomes faulty, statistics
will be made.
z Formula: none.
V. E3M board errors
z Description: When an E3M board fault is detected, BM will set the state of the E3M
board as "faulty". This statistic item is to calculate the number of times BM detects
E3M board faults.
z Measurement point: When BM detects that an E3M board becomes faulty,
statistics will be made.
3-97
z Formula: none.
VI. E1 errors
z Description: When an E1 trunk on A interface becomes faulty, FTC/SM reports the

E1 trunk fault to BM. BM will also consider that a fault has occurred to the relevant
A interface E1 trunk when it detects FTC/SM/E3M becomes faulty. BM will refresh
E1 state and relevant A interface circuit state. This statistic item is to calculate the
times of faults occur to the A interface trunk.
1) When BM receives a report from SM, notifying that a fault has occurred to an
E1 trunk.
2) When BM detects an FTC/SM/E3M fault.
z Formula: none.
VII. E1 recovery
z Description: FTC/SM reports E1 trunk recovery to BM when it detects that an E1

trunk on A interface has recovered from fault. BM will refresh the E1 state and
relevant A interface circuit state. This statistic item is to calculate the times of A
interface trunk recovers from fault.
z Measurement point: When BM receives an E1 trunk recovery report, statistics will
be made.
z Formula: none.
VIII. E1 warnings
z Description: When the state of an A interface E1 trunk changes (from "normal" to

"faulty", or from "faulty" to "normal"), BM will report an alarm to the alarm system
(Alarm No.: 317. Alarm name: A interface E1 state reporting). This statistic item is
to calculate the times of alarm 317 is reported.
z Measurement point: When BM reports alarm 317 to the alarm system, statistics
will be made.
z Formula: none.
3.6 CPU Measurement Function
3.6.1 General
CPU measurement function includes two statistic items: Percentage of CPU

occupation (%) and Peak percentage of CPU occupation (%), see Table 3-6.
The former one is the percentage of CPU in busy status during the measurement cycle.
This item indicates the load of BSC. The latter one is the maximum CPU occupation
within measurement cycle.
3-98
CPU occupation rate indicates the load of system. But 100% CPU occupation does not
mean that the processing capacity of CPU has been fully exerted, and no more tasks
can be accepted. Since BSC has some buffering capability, newly arrived tasks can be
stored in the buffer. Theoretically, as long as enough internal buffering space of BSC
still exists, BSC is able to accept new service requests, and the service will not be
interrupted. In other words, high CPU occupation does not always indicate BSC failure.
In practice, sometime, CPU occupation may go higher than 80%.
However, the internal buffering space of BSC is limited. If CPU occupation hooks on
high values for a long time, the BSC internal buffering space may be exhausted at a
certain instant because the arrival model of service requests has a high unexpectability.
In this case, the new service requests might be discarded.
Try to avoid the following operations in the case of high CPU occupation:
1) Setting large amount of data on-line;
2) Resetting BTS or board, or loading software to board;
3) Implementing interface signaling tracing.
It is recommended to register this task on any occasion.
In practice, if CPU occupation is higher than 80%, the network is likely in abnormal
status. The following can be the causes of high CPU occupation: long period of large
scope link disconnection between BTS and BSC (the duration of link disconnection is
longer than the period of MS periodical location update), large number of MSs
simultaneously implementing location update after recovery of transmission link, short
message broadcasting to entire network at NSS.
Measurement object: BM.
Recommended period: 30 minutes.
Table 3-6 Statistic items in CPU Measurement Function
No. Item name

1 Percentage of CPU occupation (%)
2 Peak percentage of CPU occupation (%)
I. Percentage of CPU occupation (%)
z Description: This item measures the percentage of CPU in busy status during the
measurement cycle. "CPU in busy status" can be that CPU is process system
message or timing task. It is opponent to "CPU in idle status", which means that
the ready message queue of operation system is empty, no clock interruption
occurs and CPU is waiting for clock interruption.
3-99
Note:
The internal sampling period of CPU occupation in BSC is 10 seconds. The occupation is obtained by
calculating idle rate. This means whenever CPU is idle, the duration of its idle time is summed up. After 10
seconds, the percentage of idle time is calculated, and then the CPU occupation is obtained by subtracting
this percentage from 1.
z Measurement point: Whenever CPU is idle, the duration of its idle time is summed
up every 10 seconds.
z Formula: none.
II. Peak percentage of CPU occupation (%)
z Description: Maximum CPU occupation within the measurement cycle.

z Measurement point: Whenever a higher CPU occupation is found within the period,
its value is recorded.
z Formula: none.
3.7 BSC Cell Broadcast Measurement
3.7.1 General
BSC Cell Broadcast Measurement provides statistic items for the measurement of
operations of Cell Broadcast short message service (CBS) in the entire BSC. Table 3-7
lists all statistic items of BSC Cell Broadcast Measurement. Note that all items are the
accumulated values during the operation of BSC cell broadcast module.
Table 3-7 Statistic items in BSC Cell Broadcast Measurement
No. Item name

1 Received "write-replace" messages
2 Received "kill request" messages
3 Received "status-CBCH-query" messages
4 Received "status-message-query" messages
5 Received "set-DRX" messages
6 Received "reset request" messages
7 Reports to "write-replace" message
8 Rejections to "write-replace" message
9 Reports to "kill request" message
10 Rejections to "kill request" message
11 Reports to "status-CBCH-query" message
12 Rejections to "status-CBCH-query" message
13 Reports to "status-message-query" message
14 Rejections to "status-message-query" message
15 Reports to "set-DRX" message
16 Rejections to "set-DRX" message
17 Successful reset
18 Unsuccessful reset
19 Received "failure-indication" messages
3-100
20 CBCH overload (overflow)

21 CBCH overload (underflow)
To know the operation of the cell broadcast of a specified cell, it is necessary to register
the relative items in Cell Broadcast Statistic.
The object of BSC cell broadcast measurement is the entire BSC. The Object Info
window of task registration should display "The task neednt special parameter", and all
the 21 statistic items have to be selected together when creating a task. The
recommended statistic cycle is 60 minutes.
Below are the details of each item, including the description, measurement point and
formula. "Description" briefly introduces the trigger process and trigger cause, and the
focus here is message interaction between Cell Broadcast Center (CBC) and BSC.
"Measurement point" lists the causes that trigger the measurement of this item. None of
the items here has measurement formula.
I. Received "write-replace" messages
z Description: CBC sends a WRITE-REPLACE message to the BSC when a new

message is created or a message already broadcast is modified. After receiving
this message and confirming its correctness, BSC will judge whether it is a new
message or a substitute. If it is a new message, it will store it in the message
library. If it is a substitute message, it will delete the corresponding old message,
and then store the new one in the message library. Next, BSC sends REPORT
Response to CBC. If the WRITE-REPLACE message BSC receives is incorrect
(not conforming to ETSI GSM 03.41), BSC will return REJECT Response. Related
items: Reports to "write-replace" message and Rejections to "write-replace"
message.
z Measurement point: As shown in Figure 3-38 A, this item is measured when BSC
receives WRITE-REPLACE from CBC regardless of the correctness of this
message.
z Formula: none.
3-101
CBC BSC
WRITE-REPLACE Request
A
REPORT Response
B
REJECT Response
C
A: Received "write-replace" messages

B: Reports to "write-replace" message
C: Rejections to "write-replace" message
Figure 3-38 Send broadcast short message
II. Received "kill request" messages
z Description: CBC sends a KILL Request message to the BSC when a Cell
Broadcast (CB) message sent to the specified (one or multiple) cells is deleted.
After receiving this message and confirming its correctness, BSC will delete it from
the message library. Next, BSC sends REPORT Response to CBC. If the KILL
Request BSC receives is incorrect, BSC will return REJECT Response. Related
items: Reports to "kill request" message and Rejections to "kill request" message.
receives KILL Request from CBC regardless of the correctness of this message.
z Formula: none.
CBC BSC
KILL Request
A
REPORT Response
B
REJECT Response
C
A: Received "kill request" messages

B: Reports to "kill request" message
C: Rejections to "kill request" message
Figure 3-39 Delete short message
III. Received "status-CBCH-query" messages
z Description: CBC sends STATUS CBCH QUERY Request to the BSC in order to
obtain the current loading of the CBCH of particular cells. After receiving this
message and confirming its correctness, BSC will query the relative data in cell
3-102
broadcast data library, and sends STATUS-CBCH-QUERY Response to CBC. If

the received STATUS-CBCH-QUERY Request is incorrect, BSC will return
REJECT Response. Related items: Rejections to "status-CBCH-query" message
and Reports to "status-CBCH-query" message.
receives STATUS-CBCH-QUERY request from CBC regardless of the
correctness of this message.
z Formula: none.
CBC BSC
STATUS-CBCH-QUERY Request
A
STATUS-CBCH-QUERY Response
B
REJECT Response
A: Received "status-CBCH-query" messages

B: Reports to "status-CBCH-query" message
C: Rejections to "status-CBCH-query" message
Figure 3-40 Query broadcast channel
IV. Received "status-message-query" messages
z Description: CBC sends a STATUS-MESSAGE-QUERY Request to the BSC in

order to obtain the current status of CB message for the cells referenced. After
receiving this message and confirming its correctness, BSC will query the relative
data in cell broadcast data library, and sends STATUS-MESSAGE-QUERY
Response to CBC. If the received STATUS-MESSAGE-QUERY Request is
incorrect, BSC will return REJECT Response. Related items: Reports to
"status-message-query" message and Rejections to "status-message-query"
message.
receives STATUS- MESSAGE-QUERY Request from CBC regardless of the
correctness of this message.
z Formula: none.
3-103
CBC BSC
STATUS-MESSAGE-QUERY Request
A
STATUS-MESSAGE-QUERY Response
B
REJECT Response
C
A: Received "status-message-query" messages

B: Reports to "status-message-query" message
C: Rejections to "status-message-query" message
Figure 3-41 Query the transmission of broadcast short message
V. Received "set-DRX" messages
z Description: DRX (Discontinuous Reception) mode can be configured in CBC so

that the MS can receive the CB message in DRX mode. In this mode, CBC sends
SET-DRX Request to BSC. After receiving this message and confirming its
correctness, BSC will set the next schedule message according to the parameter
in the message, and send SET-DRX Response to CBC. If the received SET-DRX
Request is incorrect, BSC will return REJECT Response. Related items: Reports
to "set-DRX" message and Rejections to "set-DRX" message.
receives SET-DRX Request from CBC regardless of the correctness of this
message.
z Formula: none.
CBC BSC
SET-DRX Request
A
SET-DRX Response
B
REJECT Response
C
A: Received "set-DRX" messages

B: Reports to "set-DRX" message
C: Rejections to "set-DRX" message
Figure 3-42 Set DRX mode
VI. Received "reset request" messages
z Description: When CBC resetting the specified cell, it will send RESET Request to
BSC. After receiving this message and confirming its correctness, BSC will stop
3-104
sending any message to the related cell, and clear the relative information in
message library and cell broadcast table. If the status of Cell Broadcast Channel
(CBCH) of the specified cell is normal before resetting, BSC will return
RESTART-INDICATION Request. If the status of CBCH is abnormal (e.g. cell
failure or not installed, CBCH blocked), BSC will return FAILURE-INDICATION
Request. If the received RESET Request is incorrect, BSC will return REJECT
Response. Related items: Successful reset, Unsuccessful reset and Received
"failure-indication" messages.
receives RESET Request from CBC regardless of the status of cell CBCH.
z Formula: none.
CBC BSC
RESET Request
A
RESTART-INDICATION Request
FAILURE-INDICATION Request B
C
REJECT Response
D
A: Received "reset request" messages

B: Successful reset
C: Received "failure-indication" messages
D: Unsuccessful reset
Figure 3-43 Reset cells
VII. Reports to "write-replace" message

this message and confirming its correctness, BSC will judge whether it is a new
message or a substitute. If it is a new message, it will store it in the message
library. If it is a substitute message, it will delete the corresponding old message,
and then store the new one in the message library. Next, BSC sends REPORT
Response to CBC. Related items: Received "write-replace" messages and
Rejections to "write-replace" message.
z Measurement point: As shown in Figure 3-38 B, when BSC receives
WRITE-REPLACE from CBC and the message is correct, it will send REPORT
Response to CBC. This item is measured in this case.
z Formula: none.
3-105
VIII. Rejections to "write-replace" message

this message and it is incorrect, BSC will return REJECT Response. Related items:
Received "write-replace" messages and Reports to "write-replace" message.
z Measurement point: As shown in Figure 3-38 C, when BSC receives
WRITE-REPLACE from CBC and the message is incorrect, it will send REJECT
Response to CBC. This item is measured in this case.
z Formula: none.
IX. Reports to "kill request" message
z Description: CBC sends a KILL Request message to the BSC when a CB

message sent to the specified (one or multiple) cells is deleted. After receiving this
message and confirming its correctness, BSC will delete it from the message
library. Next, BSC sends REPORT Response to CBC. Related items: Received
"kill request" messages and Rejections to "kill request" message.
z Measurement point: As shown in Figure 3-39 B, when BSC receives KILL Request
from CBC and the message is correct, it will send REPORT Response to CBC.
z Formula: none.
X. Rejections to "kill request" message
z Description: CBC sends a KILL Request message to the BSC when a CB

message sent to the specified (one or multiple) cells is deleted. After receiving this
message and it is incorrect, BSC will return REJECT Response. Related items:
Received "kill request" messages and Reports to "kill request" message.
z Measurement: As shown in Figure 3-39 C, when BSC receives KILL Request from
CBC and the message is incorrect, it will send REJECT Response to CBC. This
z Formula: none.
XI. Reports to "status-CBCH-query" message
z Description: CBC sends STATUS CBCH QUERY Request to the BSC in order to
obtain the current loading of the CBCH of particular cells. After receiving this
message and confirming its correctness, BSC will query the relative data in cell
broadcast data table, and sends STATUS-CBCH-QUERY Response to CBC.
Related items: Received "status-CBCH-query" messages and Reports to
"status-message-query" message.
z Measurement point: As shown in Figure 3-40 B, when BSC receives
STATUS-CBCH-QUERY Request from CBC and the message is correct, it will
send REPORT Response to CBC. This item is measured in this case.
z Formula: none.
3-106
XII. Rejections to "status-CBCH-query" message
z Description: CBC sends STATUS CBCH QUERY Request message to the BSC in
order to obtain the current loading of the CBCH of particular cells. If the received
STATUS-CBCH-QUERY Request is incorrect, BSC will return REJECT Response.
Related items: Received "status-CBCH-query" messages and Rejections to
"status-CBCH-query" message.
z Measurement point: As shown in Figure 3-40 C, when BSC receives
STATUS-CBCH-QUERY Request from CBC and the message is incorrect, it will
send REJECT Response to CBC. This item is measured in this case.
z Formula: none.
XIII. Reports to "status-message-query" message
z Description: CBC sends a STATUS-MESSAGE-QUERY Request to the BSC in

order to obtain the current status of CB message for the cells referenced. After
receiving this message and confirming its correctness, BSC will query the relative
data in cell broadcast data table, and sends STATUS-MESSAGE-QUERY
Response to CBC. Related items: Received "status-message-query" messages
and Rejections to "status-message-query" message.
z Measurement point: As shown in Figure 3-41 B, when BSC receives STATUS-
MESSAGE -QUERY Request from CBC and the message is correct, it will send
REPORT Response to CBC. This item is measured in this case.
z Formula: none.
XIV. Rejections to "status-message-query" message
z Description: CBC sends a STATUS-MESSAGE-QUERY Request message to the

BSC in order to obtain the current status of CB message for the cells referenced. If
the received STATUS-MESSAGE-QUERY Request is incorrect, BSC will return
REJECT Response. Related items: Reports to "status-message-query" message
and Reports to "status-message-query" message.
z Measurement point: As shown in Figure 3-41 C, when BSC receives STATUS-
MESSAGE -QUERY Request from CBC and the message is incorrect, it will send
REJECT Response to CBC. This item is measured in this case.
z Formula: none.
XV. Reports to "set-DRX" message

SET-DRX Request to BSC. After receiving this message and confirming its
correctness, BSC will set the scheduling message of next transmission according
to the parameter in the message, and send SET-DRX Response to CBC. If the
received SET-DRX Request is incorrect, BSC will return REJECT Response.
3-107
Related items: Received "set-DRX" messages and Rejections to "set-DRX"

message.
z Measurement point: As shown in Figure 3-42 B, when BSC receives SET-DRX
Request from CBC and the message is correct, it will send SET-DRX Response to
CBC. This item is measured in this case.
z Formula: none.
XVI. Rejections to "set-DRX" message

SET-DRX Request to BSC. If the received SET-DRX Request is incorrect, BSC
will return REJECT Response. Related items: Received "set-DRX" messages and
Rejections to "set-DRX" message.
z Measurement point: As shown in Figure 3-42 C, when BSC receives SET-DRX
Request from CBC and the message is incorrect, it will send REJECT Response
to CBC. This item is measured in this case.
z Formula: none.
XVII. Successful reset
(CBCH) of the specified cell is normal before resetting, BSC will return
RESTART-INDICATION Request. Related items: Received "reset request"
messages, Unsuccessful reset and Received "failure-indication" messages.
z Measurement point: Figure 3-43 B, when BSC receives RESET Request from
CBC and the status of the cell CBCH is normal it, will send
RESTART-INDICATION Request to CBC. This item is measured in this case.
z Formula: none.
XVIII. Unsuccessful reset
BSC. If the received RESET Request is incorrect, BSC will return REJECT
Response. Related items: Received "reset request" messages, Successful reset
and Received "failure-indication" messages.
z Measurement point: Figure 3-43 D, when BSC receives RESET Request from
CBC and the message is incorrect, it will send REJECT Response to CBC. This
z Formula: none.
3-108
XIX. Received "failure-indication" messages
z Description: When resetting the specified cell, CBC will send RESET Request to
(CBCH) of the specified cell is abnormal, BSC will return FAILURE-INDICATION
Request. Related items: Received "reset request" messages, Successful reset
and Unsuccessful reset.
1) As shown in Figure 3-43 C, when BSC receives RESET Request from CBC
and the message is correct while the status of CBCH is incorrect, it will send
FAILURE-INDICATION Request to CBC. This item is measured in this case.
2) This item is also measured when the links between BSC and Cell Broadcast
DataBase (CDB) are all disconnected.
z Formula: none.
XX. CBCH overload (overflow)
z Description: BTS reports the information about load of CBCH to BSC with the
message CBCH Loading Indication, and requests BSC to implement
corresponding flow control. According to the reported load type ("overflow" and
"underflow"), BSC measures the times of overflow/underflow.
receives CBCH Loading Indication from BTS, and load type is overflow.
z Formula: none.
BTS BSC
CBCH Loading Indication

A(B)
A: CBCH overload (overflow)

B: CBCH overload (underflow)
Figure 3-44 BTS reports CBCH overflow
XXI. CBCH overload (underflow)
z Description: BTS reports the information about load of CBCH to BSC with the
message CBCH Loading Indication, and requests BSC to implement
corresponding flow control. According to the reported load type ("overflow" and
"underflow"), BSC measures the times of overflow/underflow.
z Measurement point: As shown in Figure 3-44 B, this item is measured when BSC
receives CBCH Loading Indication from BTS, and load type is underflow.
3-109
z Formula: none.
3.8 MTP Measurement Function
3.8.1 General
In SS7 protocol system, SCCP (Signaling Connection Control Part) and MTP (Message
Transfer Part) provide comprehensive network function for the application layer.
The measurement object of MTP Measurement Function is the signaling link managed
by MTP service module of BSC. User can observe the operation of MTP processing
part of A interface and analyze the operation of SS7 system so as to implement
effective management over signaling network resources and evaluate the resource
performance and effectiveness of resource utilization.
Table 3-8 Statistic items in MTP Measurement Function
Serial No. Item name

1 Signaling link in service duration
2 Signaling link unavailable duration
3 Signaling link failure
4 Signaling link failure duration
5 Inhibitted local links
6 Local link inhibit duration
7 Inhibitted remote links
8 Remote link inhibit duration
9 Remote processor failure
10 Remote processor failure duration
11 Signaling link local auto rotate
12 Message signaling units (O)
13 Signaling octets (O)
14 Signaling link sending rate (%)
15 Message signaling units (I)
16 Signaling octets (I)
17 Signaling link receiving rate (%)
18 Signaling link in congestion
19 Signaling link congestion time
20 Lost message signaling units due to congestion
21 Transfer-prohibited signals (TFP) (I)
I. Signaling link in service duration
z Description: This item measures the duration of SS7 link in normal service.
z Measurement point: MTP service module of BSC checks the status of SS7 link
once per second. This item is measured when the status of the SS7 link is normal.
3-110
z Formula: none.
II. Signaling link unavailable duration
z Description: This item measures the duration of SS7 link unavailable for various
causes including but not limited to local management inhibited, remote
management inhibited and signaling link failure.
once per second. This item is measured when the link is unavailable.
z Formula: none.
III. Signaling link failure
z Description: This item measures the times of SS7 link out of service for various
causes. When a signaling link is out of service, its status is unavailable. But when
a signaling link is unavailable, it is not necessarily out of service. For example, a
signaling link can be unavailable due to remote management inhibited, but this link
is not faulty.
z Measurement point: This item is measured when SS7 is out of service.
z Formula: none.
IV. Signaling link failure duration
z Description: This item measures the duration of signaling link out of service due to
link failure. If the MTP service module of BSC receives the message indicating the
failure of a remote processor via an SS7 link, and then this link is out of service
due to failure, the measurement of the remote processor failure duration will be
terminated, and only the signaling link failure duration will be measured.
once per second. This item is measured when the link is out of service.
z Formula: none.
V. Inhibitted local links
z Description: This item measures the times of maintenance system successfully

inhibiting the SS7 link. In this occasion, the status of the SS7 link is unavailable.
z Measurement point: This item is measured when the SS7 link is successfully
inhibited by the maintenance system.
z Formula: none.
VI. Local link inhibit duration
z Description: This item measures the duration of signaling link in the status of local
management inhibited after the SS7 link is successfully inhibited by maintenance
system.
3-111
once per second. This item is measured when the link is in the status of local
management inhibited.
z Formula: none.
VII. Inhibitted remote links
z Description: This item measures the times of remote signaling point successfully
inhibiting SS7 link. In this case, the status of SS7 link is unavailable.
z Measurement point: This item is measured when the SS7 link is successfully
inhibited by a remote signaling point.
z Formula: none.
VIII. Remote link inhibit duration
z Description: This item measures the duration of signaling link in the status of
remote management inhibited after the SS7 link is successfully inhibited by
remote signaling point.
once per second. This item is measured when the link is in the status of remote
management inhibited.
z Formula: none.
IX. Remote processor failure
z Description: This item measures the times of MTP service module of BSC
receiving the message indicating remote processor failure via an SS7 link. In this
occasion, the status of SS7 is unavailable.
z Measurement point: This item is measured when MTP service module of BSC
receives the message indicating remote processor failure.
z Formula: none.
X. Remote processor failure duration
z Description: This item measures the duration of signaling link in the status of
unavailable due to remote processor failure after MTP service module of BSC
receives the message indicating remote processor failure.
once per second. This item is measured when the link unavailable due to remote
processor failure.
z Formula: none.
XI. Signaling link local auto rotate
switching the service from one SS7 link to another SS7 link when the status of the
SS7 link changes from available to unavailable.
3-112
initiates service switching on SS7 links.
z Formula: none.
XII. Message signaling units (O)
z Description: This item measures the number of message signal units transmitted
by MTP service module of BSC via an SS7 link.
sends message signal unit via an SS7 link.
z Formula: none.
XIII. Signaling octets (O)
z Description: This item measures the number of bytes occupied by Signaling

Information Field (SIF) and Service Information Octet (SIO) in the message signal
unit transmitted by MTP service module of BSC via an SS7 link.
transmits message signal unit via an SS7 link.
z Formula: none.
XIV. Signaling link sending rate (%)
z Description: This item measures the percentage of message signal units sent by
MTP service module of BSC via an SS7 link to the bearing capability (bandwidth)
of a signaling link. The bearing capability of a signaling link is 8k Byte/s, i.e. 8 %
1024 = 8192 (Byte/s). Each message signal unit contains message contents (SIF
+ SIO) of several bytes and other information of 6 bytes. Therefore the bytes of
message signal units transmitted via a signaling link can be calculated with the
formula: "Signaling octets (O) + Message signaling units (O) % 6".
z Formula: (Signaling octets (O) + Message signaling units (O) % 6) / (8192 %
measurement cycle(second))
XV. Message signaling units (I)
z Description: This item measures the number of message signal units received by
MTP service module of BSC via an SS7 link.
receives message signal unit via an SS7 link.
z Formula: none.
XVI. Signaling octets (I)
z Description: This item measures the number of bytes occupied by Signaling

Information Field (SIF) and Service Information Octet (SIO) in the message signal
unit received by MTP service module of BSC via an SS7 link.
3-113
receives message signal unit via an SS7 link.
z Formula: none.
XVII. Signaling link receiving rate (%)
z Description: This item measures the percentage of message signal units received
by MTP service module of BSC via an SS7 link to the bearing capability
(bandwidth) of signaling link. The bearing capability of signaling link is 8k Byte/s,
i.e. 8 % 1024 = 8192 (Byte/s). Each message signal unit contains message
contents (SIF + SIO) of several bytes and other information of 6 bytes. Therefore
the bytes of message signal units received via a signaling link can be calculated
with the formula: "Signaling octets (I) + Message signaling units (I) % 6".
z Formula: (Signaling octets (I) + Message signaling units (I) % 6) / (8192 %
measurement cycle(second))
XVIII. Signaling link in congestion
z Description: This item measures the times of the number of messages in the
sending buffer to be sent from L3 of MTP service module of BSC exceeding
congestion threshold.
z Measurement point: This item is measured when the number of messages in the
sending buffer to be sent from L3 of MTP service module of BSC exceeds
congestion threshold.
z Formula: none.
XIX. Signaling link congestion time
z Description: This item measures the duration of the number of messages in the
sending buffer sent from L3 of MTP service module of BSC exceeding congestion
threshold.
once per second. This item is measured when the number of messages in the
buffer to be sent from L3 of MTP service module of BSC exceeds congestion
threshold.
z Formula: none.
XX. Lost message signaling units due to congestion
z Description: This item measures the number of message signal units discarded
when the number of messages in the sending buffer to be sent from L3 of MTP
service module of BSC exceeding congestion threshold.
z Measurement point: This item is measured when the number of messages in the
sending buffer to be sent from L3 of MTP service module of BSC exceeds
congestion threshold and the message signal units is to be discarded.
3-114
z Formula: none.
XXI. Transfer-prohibited signals (TFP) (I)
receiving TransFer-Prohibited (TFP) message via an SS7 link.
receives TFP message via an SS7 link.
z Formula: none.
3.9 Cell Measurement Function
The traffic statistic items in "Cell Measurement Function" are used to measure the
traffic operation of a cell in BSC. The items can be classified into 5 types, SDCCH
seizure type, TCH seizure type, paging & random access type, handover type and radio
resource configuration type.
SDCCH seizure type: From the angles of channel seizure request, failure/success of
seizure, congestion, traffic volume, etc., items of this type reflect the operational state
of the SDCCH seizure procedure (including immediate assignment and handover), and
further reflect the usage status of SDCCH resources from the aspects of number of
channels in various states (blocked, idle and OOS), duration of seizure, etc.
TCH seizure type: From the angles of channel seizure request, failure/success of
seizure, congestion, traffic volume, etc., items of this type reflect the operational state
of the TCH seizure procedure (including very early assignment, assignment and
handover), and further reflect the usage status of TCH resources from the aspects of
number of channels in various states (blocked, idle and OOS), duration of seizure, etc.
Paging & random access type: From the aspects of page delivery, paging channel
overload and success of paging, items of this type reflect the operational state of the
paging procedure. From the aspects of immediate assignment request, immediate
assignment delivery and successful immediate assignment, the items reflect the
operational state of the immediate assignment procedure.
Handover type: From the angles of request, success, failure, handover failure, success
of re-establishment, etc., items of this type reflect the operational states of intra-cell
handover, intra-BSC intra-cell handover, and inter-BSC handover procedures. In
addition, This type also comprises the items related to dual-band handover.
Radio resource configuration type: From the angles of TRX configuration, the actual
configuration of various channels, initial configuration of various channels, etc., items of
this type reflect the radio resources configuration status in the current system.
3-115
3.9.1 SDCCH Measurement Function
Table 3-9 Statistic items in SDCCH Statistic Items
No. Item name

1 Attempted SDCCH seizures (all)
2 Successful SDCCH seizures (all)
3 Successful SDCCH seizures for handover
4 Successful SDCCH seizures for immediate assignment
5 Successful SDCCH seizures for location update
6 Successful SDCCH seizures for MOC
7 Successful SDCCH seizures for MTC
8 Successful SDCCH seizures for emergency call
9 Successful SDCCH seizures for call re-establishment
10 Successful SDCCH seizures for IMSI detach
11 Attempted SDCCH seizures meeting an SDCCH blocked state
12 Unsuccessful channel activation (NACK)
13 Channel activation timeout (timeout)
14 SDCCH lost radio connections (connection failure)
15 SDCCH lost radio connections (error indication)
16 Unsuccessful SDCCH seizures due to terrestrial link failures
17 Unsuccessful SDCCH seizures due to A-interface failure
18 SDCCH call drop
19 Uplink point to point short messages
20 Downlink point to point short messages
21 Configured SDCCHs
22 Available SDCCHs
23 Average SDCCH busy time (second)
24 All available SDCCH allocated time (second)
25 Average num. of busy SDCCHs
26 Maximum num. of busy SDCCHs
27 Average num. of congested SDCCHs
28 Average num. of idle SDCCHs
29 Average num. of OOS SDCCHs
30 Configured CBCHs
31 SDCCH usability (%)
32 SDCCH blocking rate (%)
33 SDCCH traffic volume (excluding very early assignment) (ERL)
34 SDCCH call drop rate (%)
35 Traffic density at average SDCCH call drop
36 SDCCH RF lost rate (%)
37 SDCCH channel activation NACK rate
38 SDCCH channel activation timeout rate
39 SDCCH seizure failures
40 SDCCH traffic volume (including very early assignment) (ERL)
I. Attempted SDCCH seizures (all)
z Description: In the immediate assignment procedure, MS directly requests BSS to

allocate channels. In the incoming BSC handover procedures, MSC requests BSS
to allocate channels to MS. In the intra-BSC handover procedure, BSC itself
requests BSS to reallocate radio channels. In the above procedures, if the
3-116
requested channel type is SDCCH, this item shall be measured after BSC
receives a relevant request.
Note:
SDCCH handover:
Handover happens on SDCCH.
Channel reallocation:
In the immediate assignment procedure, Huawei BSC supports channel reallocation. BSC initiates radio
channel allocation when it receives CHANNEL REQUIRED message from BTS. BSC allocates a TCH if
the access cause value of CHANNEL REQUIRED is "emergency call" or "call re-establishment" and BSC
supports very early assignment TCH. Otherwise, BSC allocates a SDCCH. BSC reallocates radio channel
automatically based on "GSM 0408" if BSC supports very early assignment of TCH and channel allocation
fails due to no radio resource available. In other words BSC allocates a TCH automatically if SDCCH
allocation fails and the access cause is not "location update", and similarly, BSC allocates a SDCCH
automatically if TCH allocation fails. So, to one CHANNEL REQUEST message, BSC measures both
SDCCH and TCH seizure times.
Very early assignment TCH:
If BSC allocates a TCH as a signaling channel in immediate assignment procedure, instead of the traffic
channel allocation procedure, the Mode Modify procedure can be implemented in the assignment
procedure.
Assignment SDCCH:
In the assignment procedure, MSC sends ASSIGNMENT REQUEST message to BSC to request for a
radio channel. BSC responses ASSIGNMENT COMPLETE message to MSC directly if the channel type in
the ASSIGNMENT REQUEST is SDCCH. In this case, BSC implements signaling or short message
transmission on the channel already allocated. BSC does not measure either "attempted SDCCH
seizures" or "successful SDCCH seizures" for it does not allocate a new channel. Instead, it measures the
times of "assignment requests" and "assignment success" after successfully sending ASSIGNMENT
COMPLETE message.
Discard CHANNLE REQUIRED in internal flow:
In the immediate assignment procedure, BSC receives CHANNEL REQUIRED messages from BTS. BSC
discards these messages if the system is too busy to respond. In this case, "attempted TCH" or "SDCCH
seizures" will be measured but "successful or unsuccessful channel seizures" will not be measured.
z Measurement point: "SD-ATT-C1" in Figure 3-45, "SD-ATT-C2" in Figure 3-47 and

"SD-ATT-C3" in Figure 3-48 indicate the measurement points of this statistic item
in the calling procedure.
1) In the immediate assignment procedure, this item is measured when BSC
receives a CHANNEL REQUIRED message from BTS and the requested
3-117
channel type is SDCCH (requested by MS, or by the system during the

second allocation procedure).
2) In the intra-BSC SDCCH handover procedure (the originating cell and target
cell belong to the same BSC), this item is measured when the target cell
receives an Intercell Handover Request message (internal message in
Huawei BSC) from the originating cell. This item is also measured on
intra-cell handover occasions. The mere difference is that the target cell and
originating cell are the same.
3) In the inter-BSC handover procedure, this item is measured when BSC
receives a HANDOVER REQUEST message from other BSC, and the
handover takes place on SDCCH.
z Formula: none.
MS BTS BSC
CHANNEL REQUEST
TCH-ATT-C 61 SD-ATT-C1
TCH-ATT-C 62 TCH-ATT-C1
TCH-ATT-C 7 TCH-ATT-BSC1
SD-ATT-BSC1
TCH-ATT-C 6
CHANNEL REQUIRED
CHANNEL ACTIVATION
CHANNEL ACTIVATION ACKNOWLEDGE
SD-SUCC-C 1
TCH-SUCC-C 6
TCH-SUCC-C 1
IMMEDIATE ASSIGN CMMAND
EST_IND
SD-SUCC-C4
SD-ATT-C1: Attempted SDCCH seizures (all)

TCH -ATT-C1: Attempted TCH seizures (all)
TCH -ATT-C6: Attempted TCH seizures for very early assignment
TCH -ATT-C7: Attempted TCH seizures for SDCCH busy
SD-SUCC-C1: Successful SDCCH seizures (all)
SD-SUCC-C4: Successful SDCCH seizures for immediate assignment
TCH -SUCC-C6: Successful TCH seizures for very early assignment
TCH -SUCC-C1: Successful TCH seizures (all)
TCH -SUCC-C61: Successful TCH allocation for very early assignment
TCH -SUCC-C62: Successful TCH seizures for SDCCH busy
3-118
MS BTS BSC MSC
ASSIGNMENT REQUEST
TCH-ATT-BSC 2 TCH-ATT-C 2
TCH-ATT-C 8
TCH-ATT-C 9
TCH-ATT-C 10
TCH-ATT-C 5
QUEUEING INDICATION
TCH-ATT-C16 TCH-ATT-C14
(directly retry)HANDOVER REQIRED
TCH-ATT-C13
(directly retry)HANDOVER REQUEST ACK
TCH-SUCC-C13 TCH-SUCC-C21,22
TCH-SUCC-C52,53,54,55,56
TCH-SUCC-C82,83
TCH-SUCC-C92,93
CHANNEL ACTIVATION TCH-SUCC-C102,103
.ASSIGN CMMAND
SABM
UA
ASSIGNMENT COMPLETE
TCH-SUCC-C23
TCH-SUCC-C51,54,55,56
TCH-SUCC-C81
TCH-SUCC-C91
TCH-SUCC-C101

TCH -ATT-C5: Attempted TCH seizures for call
TCH -ATT-C8: Attempted TCH seizures for MOC
TCH -ATT-C9: Attempted TCH seizures for MTC
TCH -ATT-C10: Attempted TCH seizures for call re-establishment
TCH -ATT-C13: Attempted TCH seizures for directed retry
TCH -ATT-C14: TCH queue requests
TCH -ATT-C16: TCH preemption requests
TCH -SUCC-C21--23: Successful TCH seizures (all)
TCH -SUCC-C51--53: Successful TCH seizures for call
TCH -SUCC-C81--83: Successful TCH seizures for MOC
TCH -SUCC-C91--93: Successful TCH seizures for MTC
TCH -SUCC-C101--103: Successful TCH seizures for call re-establishment
TCH -SUCC-C13: Successful TCH seizures for directed retry
TCH -SUCC-C54: Successful assignments of speech version 1 TCH
Figure 3-46 Assignment procedure-channel seizure procedure
3-119

MR
Handover algorithm

SD-ATT-BSC2 TCH-ATT-C11
TCH-ATT-C17 TCH-ATT-BSC3
TCH-ATT-C3 SD-ATT-C2
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
TCH-SUCC-C17 SD-SUCC-C2
TCH-SUCC-C3 TCH-SUCC-C11
SABM
UA
HANDOVER COMPLETE
Inter Clear Request
(Handover Success)

TCH -ATT-C11: Attempted TCH seizures for intraBSC incoming cell handover
TCH -ATT-C17: Attempted TCH seizures for intracell handover
TCH -SUCC-C17: Successful TCH seizures for intracell handover
TCH -SUCC-C11: Successful TCH seizures for intraBSC incoming cell handover
SD-SUCC-C2: Successful SDCCH seizures for handover, Successful SDCCH seizures (all)
3-120

HANDOVER REQUIRED
HANDOVER REQUEST
TCH-ATT-BSC4 TCH-ATT-C12
TCH-ATT-C4 SD-ATT-BSC3
TCH-ATT-C15 SD-ATT-C3 QUEUEING INDICATION
CH ACT
CH ACT ACK
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
SD-SUCC-C3
TCH-SUCC-C4
TCH-SUCC-C12
SABM
UA
HANDOVER COMPLETE

TCH -ATT-C4:Attempted TCH seizures (all)
TCH -ATT-C12: Attempted TCH seizures for interBSC incoming cell handover
TCH -SUCC-C12: Successful TCH seizures for interBSC incoming cell handover
SD -SUCC-C3: Successful SDCCH seizures for handover, Successful SDCCH seizures (all)
Figure 3-48 Incoming BSC handover channel seizure procedure
II. Successful SDCCH seizures (all)
z Description: In the immediate assignment and handover procedures, MS notifies

BSS after it successfully seizes the SDCCH allocated by the network. This item is
measured when BSC receives the notification. For related contents, please refer
to Attempted SDCCH seizures (all)".
z Measurement point: "SD-SUCC-C1" in Figure 3-45, "SD-SUCC-C2" in Figure 3-47
and "SD-SUCC-C3" in Figure 3-48 indicate the measurement points of this
statistic item in the calling procedure.
1) In the immediate procedure, this item is measured when BSC receives an

CHANNEL ACTIVATION ACKNOWLEDGE message for SDCCH from BTS.
2) In the incoming BSC handover on SDCCH procedure, BTS sends a
HANDOVER DETECTION message to the target BSC. Upon reception of
this message. BSC measures this item.
3) In the intra-BSC incoming cell handover procedure (including intracell
handover) on SDCCH, BTS sends a HANDOVER DETECTION message to
the target cell. This item is measured in the target cell when the target cell
receiving this message.
z Formula: none.
3-121
Note:
The message ESTABLISH INDICATION describes in this manual are all refer to that the value of SAPI is
zero, all other values are excluded.
III. Successful SDCCH seizures for handover
z Description: In the SDCCH handover procedure, BTS sends a HANDOVER

DETECTION message to the target cell. This item is measured when BSC
receives the HANDOVER DETECTION message. For related contents, please
refer to Attempted SDCCH seizures (all)".
z Measurement point: "SD-SUCC-C2" in Figure 3-47 and "SD-SUCC-C3" in
Figure 3-48 indicate the measurement points of this statistic item in the calling
procedure.
1) In the incoming BSC handover (incoming BSC handover on SDCCH)
procedure, BTS sends a HANDOVER DETECTION message to the target
cell. BSC measures the item when receives the HANDOVER DETECTION
message.
2) In the intra-BSC incoming cell handover procedure (intra-BSC incoming cell
handover on SDCCH), BTS sends a HANDOVER DETECTION message to
the target cell. This item is measured in the target cell when the target cell
receives the HANDOVER DETECTION message.
z Formula: none.
IV. Successful SDCCH seizures for immediate assignment
z Description: In the immediate assignment procedure for SDCCH, after

successfully seizing the SDCCH allocated by BSC, MS reports a SABM frame on
the SDCCH to BTS, indicating the establishment of a radio link layer connection in
the multi-frame mode. BTS returns a UA frame to MS, and sends an ESTABLISH
INDICATION message to BSC, notifying it to establish a normal Um interface
connection. This statistic item is measured on all the occasions allowed in the
service request message of ESTABLISH INDICATION. For related contents,
please refer to Attempted SDCCH seizures (all)".
z Measurement point: "SD-SUCC-C4" in Figure 3-45 indicates the measurement
point of this item in the calling procedure. In the immediate assignment procedure,
BTS reports an ESTABLISH INDICATION message to BSC, indicating the
establishment of SDCCH connection in the multi-frame mode. This item is
measured when BSC receives the ESTABLISH INDICATION message.
z Formula: none.
3-122
V. Successful SDCCH seizures for location update
z Description: This statistic item specially measures the number of times SDCCH is
successfully seized for MS location update.
establishment of SDCCH connection in the multi-frame mode. The type of the
service request message in ESTABLISH INDICATION is "LOCATION UPDATE
REQUEST".
z Formula: none.
VI. Successful SDCCH seizures for MOC
successfully seized for MOC (Mobile Originated Call).
service request message in ESTABLISH INDICATION is "CM SERVICE
REQUEST", and the CM service type is "MOC".
z Formula: none.
VII. Successful SDCCH seizures for MTC
successfully seized for MTC (Mobile Terminated Call).
service request message in ESTABLISH INDICATION is "PAGING RESPONSE".
z Formula: none.
VIII. Successful SDCCH seizures for emergency call
successfully seized for emergency calls.
service request message in ESTABLISH INDICATION is "CM SERVICE
REQUEST", and the CM service type is "Emergency call establishment".
z Formula: none.
3-123
IX. Successful SDCCH seizures for call re-establishment
successfully seized for MS call re-establishment.
service request message in ESTABLISH INDICATION is "CM
REESTABLISHMENT REQUEST".
z Formula: none.
X. Successful SDCCH seizures for IMSI detach
successfully seized for IMSI detach.
service request message in ESTABLISH INDICATION is "IMSI DETACH".
z Formula: none.
XI. Attempted SDCCH seizures meeting an SDCCH blocked state
z Description: in immediate assignment and handover procedure, this item is

measured in the case that the MS or MSC requests BSC to allocate SDCCH but
BSS has no available SDCCH.
z Measurement point: if the requested channel is SDCCH but the cell has no
available SDCCH, this item is measured in the following occasions:
1) BSC receives the CHANNEL REQUIRED message from the BTS.
2) The target cell receives the Intercell Handover Request message from other
cells of the BSC.
3) The BSC receives the HANDOVER REQUEST message from other BSC.
z Formula: none
XII. Unsuccessful channel activation (NACK)
z Description: in immediate assignment procedure, having allocated SDCCH for the

MS, BSC sends the CHANNEL ACTIVATION message to the BTS. If the BTS
returns a CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message to the
BSC, this indicates that the channel activation fails.
z Measurement point: this item is measured when BSC receives the CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE message from the BTS where the
cell is located.
z Formula: none
3-124
XIII. Channel activation timeout (timeout)
z Description: in immediate assignment procedure, having allocated SDCCH for the

MS, BSC sends a CHANNEL ACTIVATION message to the BTS and starts the
timer (internal timer, 5 seconds) to wait for the CHANNEL ACTIVATION
ACKNOWLEDGE message. This item is measured if the BTS has not responded
to this message when the timer expires.
z Measurement point: BSC sends the CHANNEL ACTIVATION message to the
BTS where the cell to be measured is located to activate the specified SDCCH.
Then, this item is measured if there is no response from the BTS when the timer
for the BSC to wait for the response from the BTS expires.
z Formula: none
XIV. SDCCH lost radio connections (connection failure)
z Description: If BTS detects that an active connection has been broken for some
reason, it sends a CONNECTION FAILURE INDICATION message to the BSC
informing the BSC that the call drop occurs at Um interface due to radio link
connection failure.
z Measurement point: BSC measures this item upon reception of the
CONNECTION FAILURE INDICATION message (cause: any cause except
0X20-equipment failure and 0X22-terrestrial channel failure) from the BTS and if
the failure occurs on SDCCH.
z Formula: none
XV. SDCCH lost radio connections (error indication)
z Description: If BTS detects an abnormal case for a radio link layer connection, it
sends a ERROR INDICATION message to BSC informing the BSC that the call
drop occurs at Um interface due to radio link error. See GSM 0858 protocol.
z Measurement point: BSC measures this item upon reception of the ERROR
INDICATION message from the BTS and if the failure occurs on SDCCH.
z Formula: none
XVI. Unsuccessful SDCCH seizures due to terrestrial link failures
z Description: If BTS detects that an active connection has been broken for some
reason, it sends a CONNECTION FAILURE INDICATION message to the BSC
informing the BSC that terrestrial link disconnect in ABIS interface.
1) BSC measures this item upon reception of CONNECTION FAILURE INDICATION
message (cause: 0X20-equipment failure and 0X22-terrestrial channel failure)
from the BTS and if the failure occurs on SDCCH.
2) This item is measured when the RSL link of the TRX that the call is running on
disconnect, which will cause call drop, this item measures call drop on SDCCH for
RSL disconnection.
3-125
z Formula: none
XVII. Unsuccessful SDCCH seizures due to A-interface failure
z Description: after the call established on SDCCH reports the ESTABLISH

INDICATION message, the established SDCCH and the related link will be
released if A interface connection failure occurs due to A interface connection
failures.
Note:
This item is also measured if the duration of A interface trunk circuit failure exceeds 15 seconds, the
resource check of internal RR-AIR software detects exception, the inconsistency between the SCCP code
and BSSMAP code is found, SCCP connection disconnect, BSC receives RESET CIRCUIT message from
MSC.
z Measurement point: This item is measured if the duration of A interface trunk

circuit failure exceeds 15 seconds, SCCP connection disconnect, BSC receives
RESET CIRCUIT message from MSC.
z Formula: none
XVIII. SDCCH call drop
z Description: the description of this item is the same as that of SDCCH call drop of
"BSC Measurement Function" except the measurement object is the specified
cell.
z Measurement point: See SDCCH call drop in "BSC Measurement Function"
z Formula: none
XIX. Uplink point to point short messages
z Description: SDCCH can be used to send the uplink/downlink short messages.

This item is used to measure the number of the uplink short messages sent on
SDCCH.
z Measurement point: this item is measured when BSC receives the uplink short
message sent on SDCCH.
z Formula: none
XX. Downlink point to point short messages
z Description: SDCCH can be used to send the uplink/downlink short messages.

This item is used to measure the number of the downlink short messages sent on
SDCCH.
z Measurement point: this item is measured when BSC receives the downlink short
message sent on SDCCH.
3-126
z Formula: none
XXI. Configured SDCCHs
z Description: This item indicates the number of SDCCHs currently configured for a
certain cell on real-time basis. It includes the SDCCH dynamically adjusted from
TCH. It is an average number of SDCCHs at various sampling points within the
measurement cycle.
z Measurement point: System checks the number of configured SDCCHs every five
seconds. The accumulated value from the data got at the sampling points is
divided with the times of sampling to get the average number of configure
SDCCHs within the measurement cycle.
z Formula: none.
XXII. Available SDCCHs
z Description: This item indicates the number of available (idle or busy) SDCCHs in
a certain cell on real-time basis. It includes the SDCCH dynamically adjusted from
TCH. It is an average number of available SDCCHs at various sampling points
within the measurement cycle.
z Measurement point: System checks the number of available SDCCHs every five
divided with the times of sampling to get the average number of available
SDCCHs within the measurement cycle.
z Formula: none.
XXIII. Average SDCCH busy time (second)
z Description: This item indicates the average duration of the SDCCHs configured
for a cell being busy. It shows the situation of random access frequency in the
objective cell from the angle of channel seizure duration. See Configured
SDCCHs
z Measurement point: Average duration of SDCCHs busy in a cell.
z Formula: Sum of the durations of SDCCHs busy in a cell / Number of configured
SDCCHs
XXIV. All available SDCCH allocated time (second)
z Description: This item indicates the duration of no SDCCH can be allocated. It

shows the situation of all SDCCHs have been allocated or blocked so that no
SDCCH can be allocated any more.
z Measurement point: Total duration of no SDCCH in a cell can be allocated.
z Formula: none.
3-127
XXV. Average num. of busy SDCCHs
z Description: This item indicates the average number of the busy SDCCHs
configured for a cell. It is an average number of busy SDCCHs at various sampling
points within the measurement cycle. It shows the situation of random access
frequency in the objective cell from the angle of number of channel seized.
z Measurement point: System checks the number of busy SDCCHs every five
divided with the times of sampling to get the average number of busy SDCCHs
z Formula: none.
XXVI. Maximum num. of busy SDCCHs
z Description: This item indicates the maximum number of the SDCCHs configured
for a cell being busy. It is a peak value of the number of busy SDCCHs at various
sampling points within the measurement cycle. It shows the highest random
access frequency in the objective cell from the angle of number of channel seized.
z Measurement point: System checks the number of busy SDCCHs every five
seconds. The highest value by the end of the period is recorded.
z Formula: none.
XXVII. Average num. of congested SDCCHs
z Description: This item indicates the average number of the blocked SDCCHs
configured for a cell. It is an average number of blocked SDCCHs at various
sampling points within the measurement cycle. The block of SDCCH can be
caused by O&M, or by RSL link disconnection. It shows the situation of SDCCH
blocked.
z Measurement point: System checks the number of blocked SDCCHs every five
divided with the times of sampling to get the average number of blocked SDCCHs
z Formula: none.
XXVIII. Average num. of idle SDCCHs
z Description: This item indicates the average number of the idle SDCCHs
configured for a cell. It is an average number of idle SDCCHs at various sampling
points within the measurement cycle. The status of an idle SDCCH is normal and
not seized. It shows the situation of SDCCH seizure in a cell within the period.
z Measurement point: System checks the number of idle SDCCHs every five
divided with the times of sampling to get the average number of idle SDCCHs
z Formula: none.
3-128
XXIX. Average num. of OOS SDCCHs
z Description: This item indicates the average number of the OOS SDCCHs
configured for a cell. It is an average number of OOS SDCCHs at various sampling
points within the measurement cycle. The status of OOS means a channel is
unavailable, it may be caused by the following reasons, channel blocked due to
O&M, cells status changed from installed to not installed and BTS or TRX failure.
It shows the situation of unavailable SDCCHs in a cell within the period.
z Measurement point: System checks the number of OSS SDCCHs every five
divided with the times of sampling to get the average number of OSS SDCCHs
z Formula: none.
XXX. Configured CBCHs
z Description: CELL BROADCAST CHANNEL (CBCH) is used to transfer the cell

broadcast information from CBC to MS. For the areas where cell broadcast is
available, it is possible to configure CBCH with the combination of BCCH + CBCH
or SDCCH + CBCH in Radio Channel Configuration Table. This item indicates the
number of configured CBCHs for a cell. It is an average number of configured
CBCHs at various sampling points within the measurement cycle.
z Measurement point: System checks the number of configured CBCHs every five
divided with the times of sampling to get the average number of configured
CBCHs within the measurement cycle.
z Formula: none.
XXXI. SDCCH usability (%)
z Description: This item indicates the percentage of usable SDCCHs accounting the
configured SDCCHs. See Available SDCCHs and Configured SDCCHs.
z Formula: number of usable SDCCHs / number of configured SDCCHs
XXXII. SDCCH blocking rate (%)
z Description: This item indicates the percentage of times of attempted seizures

meeting an SDCCH blocked state accounting the total number of SDCCH
requests. See Attempted SDCCH seizures meeting an SDCCH blocked state and
Attempted SDCCH seizures (all).
z Formula: times of attempted seizures meeting an SDCCH blocked state /
attempted SDCCH seizures (all)
3-129
XXXIII. SDCCH traffic volume (excluding very early assignment) (ERL)
z Description: This item indicates the traffic volume on SDCCH, i.e. the ratio of
duration of MS seizing SDCCH to measurement cycle. The duration of MS seizing
SDCCH is calculated by multiplying the number of MR reported by MS via SDCCH
with the report period (0.47 seconds). See Sum of SDCCH measurement reports
in the cell.
z Formula: Total number of SDCCH measurement reports % 0.47 / measurement
cycle (second)
XXXIV. SDCCH call drop rate (%)
z Description: This item indicates the percentage of SDCCH call drops accounting
all successful SDCCH seizures. See SDCCH call drop and Successful SDCCH
seizures (all).
z Formula: SDCCH call drops / all successful SDCCH seizures
XXXV. Traffic density at average SDCCH call drop
z Description: This item indicates average duration of MS seizing SDCCH after

which a SDCCH call drop occurs. The duration of MS seizing SDCCH is calculated
by multiplying the number of MR reported by MS via SDCCH with the report period
(0.47 seconds). See Sum of SDCCH measurement reports in the cell and SDCCH
call drop.
z Formula: Total number of SDCCH measurement reports % 0.47 / SDCCH call
drops
XXXVI. SDCCH RF lost rate (%)
z Description: This item indicates the percentage of SDCCH call drops due to radio
link disconnection when seized by MS caused by air interface causes accounting
all successful SDCCH seizures. See SDCCH lost radio connections (connection
failure), SDCCH lost radio connections (error indication) and Successful SDCCH
seizures (all).
z Formula: (times of radio link disconnection when SDCCH seized (connection
failure) + times of radio link disconnection when SDCCH seized (error indication))
/ successful SDCCH seizures (all)
XXXVII. SDCCH channel activation NACK rate
z Description: This item indicates the percentage of times of BTS returning

CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE after receiving CHANNEL
ACTIVATION aiming at SDCCH from BSC accounting times of CHANNEL
3-130
ACTIVATION sent. See Unsuccessful channel activation (NACK), Attempted

SDCCH seizures (all) and Attempted SDCCH seizures meeting an SDCCH
blocked state.
z Formula: Unsuccessful channel activation (NACK) / (Attempted SDCCH seizures
(all) Attempted SDCCH seizures meeting an SDCCH blocked state)
XXXVIII. SDCCH channel activation timeout rate
z Description: This item indicates the percentage of times of no response from BTS
within the time limit set in the timer of waiting for channel activation response after
BTS receiving CHANNEL ACTIVATION aiming at SDCCH from BSC accounting
times of CHANNEL ACTIVATION sent. The times of BSC sending CHANNEL
ACTIVATION aiming at SDCCH can be calculated by subtracting Attempted
SDCCH seizures (all) with Attempted SDCCH seizures meeting an SDCCH
blocked state. See Channel activation timeout (timeout), Attempted SDCCH
seizures (all) and Attempted SDCCH seizures meeting an SDCCH blocked state.
z Formula: Channel activation timeout (timeout) / (Attempted SDCCH seizures (all) -
Attempted SDCCH seizures meeting an SDCCH blocked state)
XXXIX. SDCCH seizure failures
z Description: After MS initiates the request to seize SDCCH of a cell, there may be
no available SDCCH in the cell, or after BSC initiates CHANNEL ACTIVATION,
BTS may return CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE or BTS
does not respond within the duration set in the timer. In these cases, MS is unable
to seize SDCCH. This item measures times of MS failing to seize SDCCH in the
objective cell. See Attempted SDCCH seizures meeting an SDCCH blocked state,
Unsuccessful channel activation (NACK) and Channel activation timeout
(timeout).
z Formula: Attempted SDCCH seizures meeting an SDCCH blocked state +
Unsuccessful channel activation (NACK) + Channel activation timeout (timeout)
XL. SDCCH traffic volume (including very early assignment) (ERL)
z Description: This item indicates the traffic volume on signaling channels, i.e. the
ratio of duration of MS seizing signaling channels to measurement cycle. The
signaling channels here include SDCCH and TCH acting as signaling channel.
The duration of MS seizing SDCCH channels is calculated by multiplying the
number of MR reported by MS via SDCCH channels with the report period 0.47
second, the duration of MS seizing TCH channels is calculated by multiplying the
number of MR reported by MS via TCH channels with the report period 0.48
3-131
second. See Sum of TCH measurement reports during very early assignment
procedure in the cell and Sum of SDCCH measurement reports in the cell.
z Formula: (Very early TCH measurement reports % 0.48 + Total number of SDCCH
measurement reports % 0.47 )/ measurement cycle (second)
3.9.2 TCH Measurement Function
Table 3-10 Statistic items in TCH statistic items
No. Item name

1 Attempted TCH seizures (all)
2 Attempted TCH seizures for call
3 Attempted TCH seizures for very early assignment
4 Attempted TCH seizures for SDCCH busy
5 Attempted TCH seizures for MOC
6 Attempted TCH seizures for MTC
7 Attempted TCH seizures for call re-establishment
8 Attempted TCH seizures for intraBSC incoming cell handover
9 Attempted TCH seizures for interBSC incoming cell handover
10 Attempted TCH seizures for directed retry
11 TCH queue requests
12 TCH preemption requests
13 Attempted TCH seizures for intracell handover
14 Successful TCH seizures for intracell handover
15 Successful TCH seizures for very early assignment
16 Successful TCH seizures (all)
17 Successful TCH seizures for call
18 Successful TCH allocation for very early assignment
19 Successful TCH seizures for SDCCH busy
20 Successful TCH seizures for MOC
21 Successful TCH seizures for MTC
22 Successful TCH seizures for call re-establish
23 Successful TCH seizures for intraBSC incoming cell handover
24 Successful TCH seizures for interBSC incoming cell handover
25 Successful TCH seizures for directed retry
26 Successful TCH queue operation
27 Successful TCH preemption
28 Successful assignments of speech version 1 TCH
31 TCH seizure failures for call(no radio resource)
32 TCH seizure failures for interBSC incoming cell handover
33 TCH seizure failures for intraBSC incoming cell handover
34 TCH Seizure failures (all)
35 Attempted TCH seizures meeting a TCH blocked state
36 TCH seizure failures for call
37 TCH seizure failures for very early assignment
38 TCH seizure failures for MOC
39 TCH seizure failures for MTC
40 TCH seizure failures for call re-establishment
41 TCH seizure failures for intraBSC incoming cell handover(no radio resource)
42 TCH seizure failures for interBSC incoming cell handover(no radio resource)
43 TCH seizure failures for directed retry
44 TCH Queue failures for queue full
3-132
45 TCH queue failures for timeout

46 Directed retry after queue failure
47 TCH seizure failures (equipment failure)
48 TCH seizure failures (requested terrestrial resource unavailable)
49 TCH seizure failures (terrestrial circuit already allocated)
50 TCH seizure failures (invalid message contents)
51 TCH call drop
52 TCH drop for very early assignment
53 TCH lost radio connections (connection failure)
54 TCH lost radio connections (error indication)
55 TCH channel activation NACKs (call)
56 TCH channel activation timeout (call)
57 TCH channel activation NACKs (handover)
58 TCH channel activation timeout (handover)
59 TCH mode modification (NACK)
60 TCH mode modification timeout
61 TCH seizure failures due to terrestrial link failures
62 TCH seizure failures due to A-interface failures
63 Average TCH queue length
64 Maximum TCH queue length
65 Average TCH queue time
66 Uplink point to point short messages
67 Downlink point to point short messages
68 TCH seizure failures for intracell handover
69 TCH seizure failures for intracell handover (no radio resource)
70 Configured TCHs of 1800 cell
71 Configured TCHs of 900 cell
72 Available TCHs
73 Average num. of busy TCHs
74 Maximum num. of busy TCHs
75 All available TCH allocated time (second)
76 Average TCH busy time (second)
77 Average num. of idle TCHs in Interf. band 1
82 Average num. of congested TCHs
83 Average num. of idle TCHs
84 Average num. of OOS TCHs
85 TCH usability (%)
86 Attempted TCH seizures (excluding handover)
87 Attempted TCH seizures (including handover)
88 TCH seizure failures (excluding handover)
89 TCH seizure failures (including handover)
90 TCH blocking rate (excluding handover)(%)
91 TCH blocking rate (including handover)(%)
92 TCH traffic volume (excluding very early assignment) (ERL)
93 Traffic density at average TCH call drop
94 TCH RF lost rate (%)
95 TCH call drop rate (%)
96 TCH traffic volume of 1800 cell (excluding very early assignment) (ERL))
97 TCH blocking rate (meeting a TCH blocked state on attempted TCH seizures)(%)
I. Attempted TCH seizures (all)
z Description: In the immediate assignment procedure, assignment procedure and

inter-BSC handover procedure, MS or MSC requests BSS to allocate radio
3-133
channels. In the intra-BSC handover procedure, BSC itself reallocates radio

channels. In the above procedures, if the requested channel type is TCH, this item
shall be measured after BSC receives a relevant request.
z Measurement point: "TCH-ATT-C1"~"TCH-ATT-C4" in Figure 3-45, Figure 3-46,
Figure 3-47 and Figure 3-48 indicate the measurement points of this statistic item
in the calling procedure. In the procedures below, if the requested channel type is
TCH, this item shall be measured.
1) In the very early assignment procedure for TCH (The TCH allocated in the
immediate assignment procedure serves as a signaling channel), this item is
measured when BSC receives a CHANNEL REQUIRED message from BTS.
2) In the assignment procedure, this item is measured when BSC receives an
ASSIGNMENT REQUEST message from MSC and the requested channel
type is TCH.
3) In the intra-BSC handover procedure (the originating cell and target cell
belong to the same BSC), this item is measured when the target cell receives
an Intercell Handover Request message (internal message in Huawei BSC)
from the originating cell. This item is also measured on Intra-cell handover
occasions. The mere difference is that the target cell and originating cell is
the same.
4) This item is measured when BSC receives a HANDOVER REQUEST
message from other BSC.
z Formula: none.
II. Attempted TCH seizures for call
z Description: This statistic item measures the number of times BSC receives
ASSIGNMENT REQUEST messages from MSC requesting to seize TCH. For
related information, please refer to Attempted TCH seizures (all)".
z Measurement point: "TCH-ATT-C5" in Figure 3-46 indicates the measurement
point of this statistic item in the calling procedure. In the assignment procedure,
this item is measured when BSC receives an ASSIGNMENT REQUEST message
from MSC, requesting allocation of TCH.
z Formula: none.
III. Attempted TCH seizures for very early assignment
z Description: This statistic item measures the number of times BSC receives
CHANNEL REQUEST messages from MS requesting to seize TCH, either TCH
first allocation or reallocation is included. For related information, please refer to
Attempted SDCCH seizures (all).
point of this statistic item in the calling procedure. In the very early assignment
procedure, this item is measured when BSC receives CHANNEL REQUIRED
message from BTS and the requested channel type is TCH.
3-134
z Formula: none.
IV. Attempted TCH seizures for SDCCH busy
z Description: In the immediate assignment procedure, BSC receives a Channel

Quest message from MS requesting to seize SDCCH, but SDCCH allocation fails
due to no SDCCH available. BSS shall automatically attempt to allocate TCH once
if it supports that. This statistic item specially measures the number of times the
system attempts to allocate TCH after SDCCH allocation fails. BSC doesn't do
channel secondary allocation if the access cause is location update in the
CHANNEL REQUEST because CHANNEL REQUEST with location update
access cause dont support TCH as signaling channel, For related information,
please refer to Attempted TCH seizures (all)".
BSC receives a CHANNEL REQUEST message from MS requesting to seize
SDCCH, but SDCCH allocation fails. This item is measured when the system
automatically attempts to allocate TCH.
z Formula: none.
V. Attempted TCH seizures for MOC
z Description: This statistic item specially measures the number of TCH allocation
requests received by BSC from MSC in the assignment procedure, requesting
BSS to allocate TCH for MOC in BSC. For related contents, please refer to
Attempted TCH seizures (all)".
point of this item. In the assignment procedure, this item is measured when BSC
receives an ASSIGNMENT REQUEST message from MSC, requesting BSS to
allocate TCH for MOC.
z Formula: none.
VI. Attempted TCH seizures for MTC
BSS to allocate TCH for MTC in BSC. For related contents, please refer to
Attempted TCH seizures (all)".
point of this item in the calling procedure. In the assignment procedure, this item is
measured when BSC receives an ASSIGNMENT REQUEST message from MSC,
requesting BSS to allocate TCH for MTC.
z Formula: none.
3-135
VII. Attempted TCH seizures for call re-establishment
BSS to allocate TCH for MS call re-establishment. For related contents, please
refer to Attempted TCH seizures (all)".
point of this item. In the assignment procedure, this item is measured when BSC
receives an ASSIGNMENT REQUEST message from MSC, requesting BSS to
allocate TCH for MS call re-establishment.
z Formula: none.
VIII. Attempted TCH seizures for intraBSC incoming cell handover
z Description: In the intra-BSC handover procedure, this statistic item measures the
number of times the target cell receives Intercell Handover Request messages
from the originating cell, requesting allocation of TCH.
point of this item in the calling procedure. In the intra-BSC handover procedure,
the originating cell sends an Intercell Handover Request message to the target cell,
requesting allocation of TCH. This item is measured when the target cell receives
this message. It is not measured on intra-cell handover occasions. For relevant
contents of intra-cell handover, please refer to Attempted TCH seizures for
intracell handover.
z Formula: none.
IX. Attempted TCH seizures for interBSC incoming cell handover
z Description: In the inter-BSC handover procedure, this statistic item measures the
number of times the cell in Huawei BSC receives HANDOVER REQUEST
messages from other BSC (transferred via MSC), requesting allocation of TCH.
point of this item in the calling procedure. This item is measured when BSC
receives an incoming BSC handover request (HANDOVER REQUEST),
requesting allocation of TCH.
z Formula: none.
X. Attempted TCH seizures for directed retry
z Description: BSC performs message content check and status check after it
receives an ASSIGNMENT REQUEST message from MSC.If it finds no available
channel for allocation, and it supports directed retry, BSC can automatically initiate
directed retry to another cell in the current BSC or to a cell in other BSC. For the
originating cell, the directed retry procedure is an outgoing cell handover
procedure with the cause value "Directed retry", whereas, for the target cell, it is an
incoming cell handover procedure with the cause value "Directed retry".
3-136

point of this item in the calling procedure. After the above-mentioned conditions
are satisfied, the originating cell initiates directed retry, by sending a HANDOVER
REQUIRED message to MSC or sending a Intercell Handover Request message
to another cell in the current BSC, this item is measured.
z Formula: none.
XI. TCH queue requests
z Description: BSC performs message content check and status check after it
receives an ASSIGNMENT REQUEST message from MSC. If it finds no available
channel for allocation, and either of the following two conditions is satisfied, BSC
can automatically initiate the queue procedure.
1) If BSC and the priority IE contained in the ASSIGNMENT REQUEST
message both support preemption, BSC shall implement preemption. If
preemption is successfully implemented, and queue is supported by BSC
and the queue IE in the ASSIGNMENT REQUEST message, BSC shall
initiate the queue procedure.
2) Even if priority IE in ASSIGNMENT REQUEST or BSS does not support
preemption, BSC can also initiate the queue procedure, so long as queue IE
in ASSIGNMENT REQUEST and BSS support queue.
In assignment procedure, after the queue conditions are satisfied, BSC returns a
QUEUEING INDICATION message to MSC and starts timer T11. Before expiry of timer
T11, if there are released channels in BSS and the queuing calls successfully seize the
idle channels; the assignment procedure shall go on.
Likewise, for incoming BSC handover, if there is no channel available in BSC and
queue is supported, the system can also perform queue for TCH seizures. This
procedure is similar to the assignment procedure. The only difference is that the timer
started in the incoming BSC handover procedure is timer Tqho. Preemption and queue
are not supported in the immediate assignment and intra-BSC handover procedures.
point of this item in the calling procedure. In the assignment or incoming BSC
handover procedure, when BSC initiates the queue procedure by returning a
QUEUEING INDICATION message to MSC, this item is measured.
z Formula: none.
XII. TCH preemption requests
z Description: In the assignment or incoming BSC handover procedure, BSC

performs message content check and status check after it receives an
ASSIGNMENT REQUEST or HANDOVER REQUEST message from MSC. If it
finds no available channel for allocation, and it supports preemption, which is also
supported by ASSIGNMENT REQUEST or HANDOVER REQUEST, BSC shall
3-137
implement preemption. If preemption is successfully implemented, and queue is

supported by the system, BSC shall initiate the queue procedure.
point of this item in the calling procedure. In the assignment or incoming BSC
handover procedure, preemption shall be implemented when there is no available
channel in BSC and the system supports resource preemption. At the same time,
this item shall be measured.
z Formula: none.
XIII. Attempted TCH seizures for intracell handover
z Description: This item measures the number of times the serving cell receives
Intracell Handover Request messages in the intra-cell handover (handover
between different channels in the serving cell) procedure.
Note:
BSC performs handover decision according to the MR reported by MS; the target cell can be either other
cell or the serving cell itself. Handover between different channels in the same cell is called intra-cell
handover.

point of this item in the calling procedure. This item is measured when the serving
cell receives an Intercell Handover Request message from itself.
z Formula: none.
XIV. Successful TCH seizures for intracell handover
z Description: In the intra-cell handover procedure, upon reception of a HANDOVER

COMMAND message from the serving cell, MS accesses the new channel, and
sends a HANDOVER ACCESS on this channel
z Measurement point: "TCH-SUCC-C17" in Figure 3-47 indicates the measurement
point of this item in the calling procedure. In the intra-cell handover procedure, MS
reports a HANDOVER ACCESS message on the new channel after it accesses a
new channel in the serving cell. BTS sends HANDOVER DETECTION message
to BSC.This item is measured in the serving cell when BSC receives the
HANDOVER DETECTION message.
z Formula: none.
XV. Successful TCH seizures for very early assignment
z Description: In the very early assignment procedure, after a TCH is allocated, BSC
activates the TCH. BTS shall return a CHANNEL ACTIVATION ACKNOWLEDGE
message to BSC if it considers that the channel is successfully activated. Then
3-138
BSC sends IMMEDIATE ASSIGN COMMAND to MS, upon reception of this

message, MS sends a SABM frame to BTS to establish the radio interface
connection, BTS sends ESTABLISH INDICATION to BSC and response a UA
frame to MS to acknowledge the connection. Whether Abis interface adopts a
terrestrial link or satellite for transmission, the measurement point is the same (If
satellite transmission is adopted, the CHANNEL ACTIVATION and IMMEDIATE
ASSIGN COMMAND messages are delivered together to MS).
point of this item in the calling procedure. In the very early assignment procedure,
this item is measured when BSC receives an CHANNEL ACTIVATION
ACKNOWLEDGE message from BTS.
z Formula: none.
XVI. Successful TCH seizures (all)
z Description: In the very early assignment procedure, assignment procedure and

handover procedure, BSC measures this item when MS successfully seizes the
TCH allocated by the network.
Note:
In the assignment procedure, successful directed retry is regarded as successful TCH seizure. More
specifically, after the ASSIGNMENT REQUEST message from MSC is delivered to a cell in BSC, if there is
no available channel in that cell and the system supports directed retry, BSC shall initiate outgoing cell
handover according to the adjacent cell information in the MR (Measurement Report) of MS. If directed
retry is performed in BSC, the target cell shall send an ASSIGNMENT CONFIRMED message to MSC
after it has successfully implemented directed retry. In the meantime, this item shall be measured in the
originating cell. Directed retry only takes place in the TCH assignment procedure.
z Measurement point: "TCH-SUCC-C1" in Figure 3-45, "TCH-SUCC-C21~23" in

Figure 3-46, "TCH-SUCC-C3" in Figure 3-47 and "TCH-SUCC-C4" in Figure 3-48
indicate the measurement points of this statistic item in the calling procedure.
1) In the very early assignment procedure for TCH, this item is measured when
BSC receives an CHANNEL ACTIVATION ACKNOWLEDGE message from
BTS.
2) In the assignment procedure, if directed retry is successfully implemented
and the target cell for direct retry belongs to other BSC, MSC shall send a
CLEAR COMMAND to the originating cell to clear the previous connections.
This item shall be measured when the originating cell receives the CLEAR
COMMAND message.
and the target cell for direct retry belongs to the current BSC, the target cell
3-139
shall send an Inter Clear Request message to the originating cell, notifying it
to clear resources and connections. This item shall be measured when the
originating cell receives the Inter Clear Request message.
4) This item is measured when the assignment procedure is successfully
completed, and BSC sends an ASSIGNMENT COMPLETE message to MSC.
The case that the target cell of directed retry sends ASSIGNMENT
COMPLETE message to MSC after successfully completes directed retry is
excluded.
5) In the incoming BSC handover procedure, this item is measured in the target
BSC when the target BSC receives a HANDOVER DETECTION message
from MS.
6) In the intra-BSC incoming cell handover procedure and intracell handover
procedure, this item is measured in the target cell when BSC receives
HANDOVER DETECTION from BTS.
z Formula: none.
XVII. Successful TCH seizures for call
z Description: In the assignment procedure, upon reception of an ASSIGNMENT

REQUEST message from MSC, BSC allocates TCH (for voice data transmission)
to MS. After channel allocation is successfully completed, BSC requests BTS to
activate this channel. BTS shall return a CHANNEL ACTIVATION
ACKNOWLEDGE message to BSC if it allows channel activation operations.
Upon reception of the CHANNEL ACTIVATION ACKNOWLEDGE message, BSC
sends ASSIGNMENT COMMAND to MS, which sends ASSIGNMENT
COMPLETE to BSC after it successfully accesses the new channel.
z Measurement point: "TCH-SUCC-C51~53" in Figure 3-46 indicates the
measurement point of this item in the calling procedure.
1) In the assignment procedure, this item is measured when BSC sends an
ASSIGNMENT COMPLETE message to MSC. The case that the target cell
of directed retry sends ASSIGNMENT COMPLETE message to MSC after
successfully completes directed retry is excluded.
This item is measured when the originating cell receives the CLEAR
COMMAND message.
to clear resources and connections. This item is measured when the
z Formula: none.
3-140
XVIII. Successful TCH allocation for very early assignment
z Description: In the very early assignment procedure, whether TCH is allocated in

the first allocation or second allocation procedure, so long as BSC has
successfully allocated TCH, this item shall be measured. For second allocation
strategies, please refer to Attempted SDCCH seizures (all).
this item is measured when BSC successfully allocates TCH for calls.
z Formula: none.
XIX. Successful TCH seizures for SDCCH busy
z Description: In the very early assignment procedure, if BSC successfully allocates

TCH in the channel second allocation procedure (For the requested SDCCH,
because there is no SDCCH available, BSC allocates TCH in the second
allocation procedure), this item shall be measured. For second allocation
strategies, please refer to Attempted SDCCH seizures (all).
this item is measured when BSC successfully allocates TCH in the channel
second allocation procedure.
z Formula: none.
XX. Successful TCH seizures for MOC
z Description: This item is related to "Successful TCH seizures for call". It measures
the number of times BSC successfully allocates TCH for MOC. For the directed
retry in assignment procedure, please refer to Attempted TCH seizures for
directed retry.
z Measurement point: "TCH-SUCC-C81~C83" in Figure 3-46 indicates the
COMMAND message.
3-141

z Formula: none.
XXI. Successful TCH seizures for MTC
the number of times BSC successfully allocates TCH for MTC. For the directed
retry in assignment procedure, please refer to Attempted TCH seizures for
directed retry.
COMMAND message.
z Formula: none.
XXII. Successful TCH seizures for call re-establish
the number of times BSC successfully allocates TCH for call re-establishment. For
the directed retry in assignment procedure, please refer to Attempted TCH
seizures for directed retry.
3-142
COMMAND message.
z Formula: none.
XXIII. Successful TCH seizures for intraBSC incoming cell handover
z Description: In the intra-BSC incoming cell handover procedure, BTS shall report
a HANDOVER DETECTION message to the target cell after MS accesses the
TCH of the target cell. This item measures the number of times the target cell
receives the HANDOVER DETECTION messages.
point of this item in the calling procedure. In the intra-BSC incoming cell handover
procedure, this item is measured when the target cell receives a HANDOVER
DETECTION message. This item is not measured on intra-cell handover
occasions. For the statistic item related to intra-cell handover, please refer to
Successful TCH seizures for intracell handover.
z Formula: none.
XXIV. Successful TCH seizures for interBSC incoming cell handover
z Description: In the inter-BSC incoming cell handover procedure, BTS reports a

HANDOVER DETECTION message to the target cell in Huawei BSC after MS
seizes the TCH of the cell. This item measures the number of times the target BSC
receives the HANDOVER DETECTION messages.
point of this item in the calling procedure. This item is measured when BSC
receives a HANDOVER DETECTION message from BTS which indicates MS
came from other BSC and the handover takes place on TCH.
z Formula: none.
XXV. Successful TCH seizures for directed retry
z Description: In the directed retry procedure, when directed retry is successfully

implemented, i.e. MS successfully accesses the target cell in the current BSC or
other BSC, this item shall be measured in the originating cell. For description of
the directed retry procedure; please refer to Attempted TCH seizures for directed
retry.
1) If the target cell for directed retry is another cell in the current BSC, from the
angle of the target cell, the directed retry procedure is an incoming cell
handover procedure, whereas, from the angle of originating cell, the
3-143
directed retry procedure is outgoing cell handover in assignment procedure.

Therefore, for the originating cell, successful inter-cell directed retry in BSC
means successful outgoing cell handover.
2) If the target cell for directed retry belongs to other BSC, from the angle of the
target cell, the directed retry procedure is an incoming BSC handover
procedure, whereas, from the angle of originating cell, the directed retry
procedure is outgoing BSC handover procedure. Therefore, for the
originating cell, successful inter-BSC directed retry means successful
outgoing BSC handover.
point of this item in the calling procedure. When there is no available channel, BSC
initiates directed retry. Directed retry shall be implemented in the target cell of the
current BSC or other BSC.
1) If the target cell belongs to the current BSC, the target cell shall send an
Inter Clear Request message (internal message in Huawei BSC) with the
cause value "Handover Success" to the originating cell after it successfully
implements incoming cell handover. This item is measured when the
2) If the target cell belongs to other BSC, the target cell shall send a
HANDOVER COMPLETE message to MSC after it successfully implements
incoming BSC handover. Upon reception of the message, MSC sends a
CLEAR COMMAND message to the originating cell. This item is measured
when the originating cell receives the CLEAR COMMAND message.
z Formula: none.
XXVI. Successful TCH queue operation
z Description: For description of queue in the assignment and incoming BSC

handover procedures, please refer to TCH queue requests. In the queue of
assignment procedure, BSC returns a QUEUEING INDICATION message to MSC
and starts timer T11. Before expiry of timer T11, if there are released TCHs in BSS
and the queuing calls successfully seize the idle channels, the assignment
procedure shall go on, and this item shall be measured once. Likewise, for
incoming BSC handover, if there is no available TCH in BSC and queue is
supported, the system can perform queue for TCH seizures. This procedure is
similar to the assignment procedure. The only difference is that the timer started in
the incoming BSC handover procedure is timer Tqho.
z Measurement point: In the assignment procedure or in the incoming BSC
handover procedure, BSC returns a QUEUEING INDICATION message to MSC.
Before expiry of specified timer, if the system has successfully allocated TCH to a
queuing call, this item shall be measured.
z Formula: none.
3-144
XXVII. Successful TCH preemption
z Description: For description of the TCH seizure preemption in the assignment and
incoming BSC handover procedures, please refer to TCH preemption requests.
Based on the priorities of the channel type requested in the ASSIGNMENT
REQUEST messages from MSC, BSC preempts a channel which is seized by a
lower-priority call. This item is measured when the channel is successfully
preempted.
z Measurement point: In the assignment or in incoming BSC handover procedure, if
the current call successfully preempts the channel seized by a lower-prior call, this
item shall be measured in the cell where the assignment or handover takes place.
z Formula: none.
XXVIII. Successful assignments of speech version 1 TCH
Description: The measurement point of this item is similar to that of Successful TCH
seizures for call. This item is specially used to measure the number of times the speech
version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm version 1".
point of this item in the calling procedure.
When assignment is successfully implemented, BSC sends an ASSIGNMENT
COMPLETE message to MSC, in which, the indicated speech version is "GSM
speech algorithm version 1".
z Formula: none.
XXIX. Successful assignments of speech version 2 TCH
Description: The measurement point of this item is similar to that of "Successful TCH
seizures for call". This item is specially used to measure the number of times the
speech version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm
version 2".
point of this item in the calling procedure. When assignment is successfully
implemented, BSC sends an ASSIGNMENT COMPLETE message to MSC, in
which, the indicated speech version is "GSM speech algorithm version 2".
z Formula: none.
XXX. Successful assignments of speech version 3 TCH
Description: The measurement point of this item is similar to that of "Successful TCH
seizures for call". This item is specially used to measure the number of times the
speech version indicated in ASSIGNMENT COMPLETE is "GSM speech algorithm
version 3".
3-145

point of this item in the calling procedure. When the assignment is successfully
implemented, BSC sends an ASSIGNMENT COMPLETE message to MSC, in
which, the indicated speech version is "GSM speech algorithm version 3".
z Formula: none.
XXXI. TCH seizure failures for call(no radio resource)
z Description: See Unsuccessful assignments of BSC Measurement Function. This

item is used to measure the unsuccessful assignments due to no available TCH in
assignment procedure.
z Measurement point: See Unsuccessful assignments (no radio resource available)
of BSC Measurement Function. the measurement object of this item is the cell.
z Formula: none
XXXII. TCH seizure failures for interBSC incoming cell handover
z Description: in the case inter BSC handover occurs when the MS is seizing TCH,
this item is measured if the target BSC receives the CLEAR COMMAND message
from MSC or receives the clear message of RR-AIR inside the BSC. In this case
the HANDOVER FAILURE message is not sent. Otherwise, If the incoming BSC
handover fails due to some other reason, the target BSC should send a
HANDOVER FAILURE message to MSC and it measures this item at the same
time.
1) In the case inter BSC handover occurs when MS is seizing TCH. This item is
measured if the target BSC meets A interface connection failure in the target
BSC. In this case the target will not send HANDOVER FAILURE to MSC
2) The target BSC under the following states receives the CLEAR COMMAND
message from MSC. The target BSC has no available channel and is
queuing for the channel. Or the target BSC is waiting for the HANDOVER
DETECT or HANDOVER COMPLETE message from the MS. In this case
this item is measured and the target BSC does not send the HANDOVER
3) In the case inter BSC handover occurs when MS is seizing TCH. This item is
measured when the target BSC sends the HANDOVER FAILURE message
to MSC because the BSC fails to implement the handover procedure due to
some reason (excluding the above mentioned causes).
z Formula: none
XXXIII. TCH seizure failures for intraBSC incoming cell handover
z Description: in the case intra BSC incoming cell handover occurs when MS is
seizing TCH; the handover implementation fails due to some reason during the
period after the target cell receives the Intercell Handover Request message from
3-146
the source cell and before the target cell sends the Intercell Handover Response
message to the source cell, then the target cell sends the Intercell Handover
Failure message to the source cell. This item is not used to measure the intra cell
handover.
z Measurement point: if intra BSC incoming cell handover occurs when the MS is
seizing TCH, this item is measured when the following occasions occur.
1) The target cell receives the CHANNEL ACTICATION NEGATIVE
ACKNOWLEDGE message from the BTS when activating the newly
allocated TCH.
2) The implementation of the incoming cell handover procedure fails because
the target cell does not support the encryption algorithm in the Intercell
Handover Request message.
3) No response after the timer (internal timer, 5 seconds) expires when the
target cell activates the newly allocated TCH.
4) The target cell has no available TCH.
z Formula: none
XXXIV. TCH Seizure failures (all)
z Description: TCH seizure failures that occur in all calling procedure due to all
reasons. The measurement point includes those failures for radio failure during
handovers and the measurement of the following statistic items: TCH seizure
failures for call, TCH seizure failures for interBSC incoming cell handover, TCH
seizure failures for very early assignment, TCH seizure failures for intraBSC
incoming cell handover, and TCH seizure failures for intracell handover. However,
this item is an initial statistic item.
z Formula: See the TCH seizure failures in various occasions mentioned in the
above description and radio failure condition.
XXXV. Attempted TCH seizures meeting a TCH blocked state
z Description: this item is measured if there is no available TCH in immediate TCH

assignment, TCH assignment, incoming BSC handover on TCH, or intra BSC
incoming cell handover procedure. Though no TCH available, the call might
initiate forced seizure, queue, and directed retry procedure etc., according to the
actual situation. So this item does not means that the implementation of calling
procedure fails.
z Measurement point: this item is measured if there is no available TCH when
requesting TCH in the calling procedure.
z Formula: none
3-147
XXXVI. TCH seizure failures for call
z Description: See Unsuccessful assignments of "BSC Measurement Function". In

Huawei BSC traffic statistic system, unsuccessful assignments occur in the cell
are measured as TCH seizure failures.
z Measurement point: the same as that of Unsuccessful assignments of "BSC
Measurement Function". But the statistic object of this item is cell.
z Formula: none
XXXVII. TCH seizure failures for very early assignment
z Description: this item is measured when TCH allocation failure, TCH activation
failure, or TCH activation NACK occurs in BSC in very early TCH assignment
procedure.
1) This item is measured if there is no available TCH when the MS requests
channel from BSC in very early TCH assignment procedure.
2) In very early TCH assignment procedure, after BSC allocates a TCH, it
sends a CHANNEL ACTIVATION message to the BTS to activate this
channel. If BTS returns the CHANNEL ACTIVATION NEGATIVE
ACKNOWLEDGE message. Then this item is measured when BSC
3) In very early TCH assignment procedure, after BSC allocates a TCH, sends
a CHANNEL ACTIVATION message to the BTS to activate this channel. At
the same time, BSC starts the timer. Then this item is measured if the
response from the BTS has not been received when the timer expires.
z Formula: none
XXXVIII. TCH seizure failures for MOC
z Description: the same as that of TCH seizure failures for call except this item is
used to measure only the occasion that the MS serves as MOC.
z Measurement point: this item is measured when assignment procedure in which
the MS serves as MOC fails due to some reason. The measurement point is
similar to that of TCH seizure failures for call.
z Formula: none
XXXIX. TCH seizure failures for MTC
used to measure only the occasion that the MS serves as MTC.
z Measurement point: this item is measured when assignment procedure in which
the MS serves as MTC fails due to some reason. The measurement point is similar
to that of TCH seizure failures for call.
z Formula: none
3-148
XL. TCH seizure failures for call re-establishment
used to measure only the occasion of call re-establishment.
z Measurement point: this item is measured when the implementation of the call
re-establishment procedure fails due to some reason. The measurement point is
similar to that of TCH seizure failures for call.
z Formula: none
XLI. TCH seizure failures for intraBSC incoming cell handover(no radio
resource)
z Description: in intra BSC incoming cell handover procedure, this item is measured
if the target cell has no available TCH when allocating TCH upon reception of the
Intercell Handover Request message requesting TCH from other cell in the same
BSC.
z Measurement point: in intra BSC incoming cell handover, this item is measured if it
is TCH that is requested and the handover fails due to no available TCH.
z Formula: none
XLII. TCH seizure failures for interBSC incoming cell handover(no radio
resource)
z Description: this item measures the handover failure in inter-BSC handover due to
no available radio channel or timer for queue expires in target cell in the target
BSC.
z Measurement point: In incoming BSC handover procedure occurs when the MS is
seizing TCH, if there is no available TCH after the target cell receives the
HANDOVER REQUEST message and queue isnt supported, this item is
measured. If there is no available TCH but both BSC and this handover support
the queue, then the system starts the timer to wait for TCH release. This item is
measured if there is still no TCH available when the timer expires.
z Formula: none
XLIII. TCH seizure failures for directed retry
z Description: in assignment procedure, if it is TCH that MSC requests for and the
cell supports directed retry, then BSC judges to select an adjacent cell for outgoing
cell handover according to the MR from the MS. As this handover is caused by
directed retry, this procedure is called directed retry. This item is used to measure
the TCH seizure failures for directed retry if the source cell implements the
directed retry.
1) In the case directed retry occurs in TCH assignment procedure, this item is
measured in the source cell in the following case: if the target cell is in the
same BSC and the source cell receives the Inter Clear Request message
3-149
from the target cell in the directed retry procedure; however this message is
not the one to inform the handover completion but to inform the source cell
of the directed retry failure and to request to clear the connection.
measured if the target cell is in the same BSC and the source cell receives
the Intercell Handover Reject message from the target cell in the directed
retry procedure.
3) In the case directed retry occurs in TCH assignment procedure and the
target cell is in the same BSC, this item is measured in the source cell if the
timer for the source cell to wait for Inter Clear Request message upon the
completion of the handover from the target cell expires after the source cell
sends the MS the HANDOVER COMMAND message to request the MS to
access the new channel.
measured if the target cell is in the same BSC and the target cell fails to
respond to the Intercell Handover Request message sent by the source cell
after the timer expires.
z Formula: none
XLIV. TCH Queue failures for queue full
z Description: in assignment procedure and incoming BSC handover procedure, if it

is TCH that MSC requests for, there is no available TCH in the cell when BSC
allocates the channel, and the system supports queue, then the call queue is
initiated. Each Huawei BSC BM supports only 100 queuing calls. This item is
measured if the call queue fails because the queue is full.
z Measurement point: in assignment procedure and incoming BSC handover
procedure, this item is measured if the call queue fails because the queue is full.
z Formula: none
XLV. TCH queue failures for timeout
z Description: in assignment procedure and incoming BSC handover procedure, if it

is TCH that MSC requests for, there is no available TCH in the cell when BSC
allocates the channel, and the system supports queue, then the call queue is
initiated and the related timer is started to wait for the resource release.
z Measurement point: in assignment procedure and incoming BSC handover
procedure, if BSC starts the queue timer due to no available TCH, then this item is
measured if there is no TCH released when the timer expires and the system
doesn't support the queue in assignment procedure.
z Formula: none
3-150
XLVI. Directed retry after queue failure
z Description: in assignment procedure, if it is TCH that MSC requests for, there is

no available TCH in the cell when BSC allocates the channel, and if the system
supports queue, then the call queue is initiated and the related timer (T11) is
started. If the system supports the directed retry, the directed retry is initiated and
this item is measured in the case there is still no TCH available when the timer
(T11) expires.
z Measurement point: If the queue is initiated in TCH assignment procedure and
there is still no TCH available after the queue timer expires, the system initiates
the directed retry if possible and this item is measured at the same time.
z Formula: none
XLVII. TCH seizure failures (equipment failure)
z Description: in assignment procedure, if it is TCH that MSC requests for, this item
is measured when the implementation of the assignment procedure fails due to
equipment failure. See the following measurement points for the definition of
equipment failure.
1) In channel assignment procedure, BSC allocates the terrestrial circuit
according to the CIC specified by MSC but the allocation fails. Then this
item is measured and BSC requests MSC to clear the connection
simultaneously.
2) If mode modify is initiated in assignment procedure, after the radio channel
is successfully modified according to the CHANNEL TYPE requested by
MSC, this item is measured if the AM/CM net-drive of BSC fails. (AM/CM
returns net-drive rejection or response timeout).
when BSC receives the MODE MODIFY NEGATIVE ACKNOWLEDGE
message from BTS indicating the failure of mode modify after the MODE
MODIFY message is sent to BTS.
when the timer for BSC to wait for the response expires after the MODE
MODIFY message has been sent to the BTS.
5) In assignment procedure, this item is measured when BSC receives
Channel Activation NACK or the timer for BSC to wait for Channel Activation
ACK expires.
z Formula: none
XLVIII. TCH seizure failures (requested terrestrial resource unavailable)
is measured if the implementation of assignment procedure fails because the
requested terrestrial resource on BSS side is unavailable. See the following
3-151
measurement points for the definition of "requested terrestrial resource

unavailable".
1) This item is measured when BSC detects the state of CIC requested in
ASSIGNMENT REQUEST message received from MSC is unavailable.
2) In assignment procedure, this item is measured when AM/CM net-drive fails
(AM/CM returns net-drive rejection or AM/CM response timeout).
z Formula: none
XLIX. TCH seizure failures (terrestrial circuit already allocated)
is measured if the BSC detects the requested CIC has already been seized. At the
same time BSC informs MSC of the assignment failure.
z Measurement point: in assignment procedure, this item is measured when BSC
detects the CIC requested in ASSIGNMENT REQUEST message received from
MSC has already been seized.
z Formula: none
L. TCH seizure failures (invalid message contents)
is measured when BSC detects the ASSIGNMENT REQUEST message contains
invalid contents during the message decoding. At the same time BSC informs
MSC of the assignment failure.
z Measurement point: this item is measured when BSC detects the ASSIGNMENT
REQUEST message contains invalid contents during the message decoding,
Which includes CHANNEL TYPE, CIC, Layer 3 header information.
z Formula: none
LI. TCH call drop
z Description: the same as that of TCH call dropof "BSC Measurement Function".
But the statistic object of this item is cell.
z Description: the same as that of TCH call drop of "BSC Measurement Function".
But the statistic object of this item is cell.
z Formula: none
LII. TCH drop for very early assignment
z Description: the same as that of TCH drop for very early assignmentof "BSC
Measurement Function". But the statistic object of this item is cell.
z Measurement point: the same as that of TCH drop for very early assignment of
"BSC Measurement Function". But the statistic object of this item is cell.
z Formula: none
3-152
LIII. TCH lost radio connections (connection failure)
z Description: in the case that the TCH is seized as the traffic channel, if BTS
detects that an active connection has been broken for some reason, it sends
CONNECTION FAILURE INDICATION message to BSC informing the BSC that
the call drop occurs at Um interface due to radio link connection failure.
z Measurement point: BSC measures this item upon reception of CONNECTION
FAILURE INDICATION message (cause: any cause except 0X20-equipment
failure and 0X22-terrestrial channel failure) from the BTS and if the failure occurs
on TCH.
z Formula: none
LIV. TCH lost radio connections (error indication)
detects an abnormal case for a radio link layer connection, it sends ERROR
INDICATION message to BSC informing the BSC that the call drop occurs at Um
interface due to radio link error. See GSM 0858 protocol
z Measurement point: BSC measures this item upon reception of ERROR
INDICATION message from the BTS and if the failure occurs on TCH.
z Formula: none
LV. TCH channel activation NACKs (call)
z Description: after receiving ASSIGNMENT REQUEST message from MSC, BSC

initiates assignment procedure, then allocates channel. After the successful
channel allocation, BSC sends CHANNEL ACTIVATION message to the BTS to
activate the allocated channel. BTS checks the state of this channel and
responses to the BSC.
z Measurement point: in assignment procedure, BSC measures this item upon
reception of CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message
from the BTS after having sent CHANNEL ACTIVATION message to the BTS.
z Formula: none
LVI. TCH channel activation timeout (call)
z Description: after receiving ASSIGNMENT REQUEST message from MSC, BSC

initiates assignment procedure, then allocates channel. After the successful
channel allocation, BSC sends the CHANNEL ACTIVATION message to the BTS
to activate the allocated channel. BTS checks the state of this channel and
responses to the BSC.
z Measurement point: in assignment procedure, BSC sends the CHANNEL
ACTIVATION message to the BTS and the timer is started to wait for the response.
This item is measured if no response is received when the timer expires.
z Formula: none
3-153
LVII. TCH channel activation NACKs (handover)
z Description: the measurement result of this item includes intra BSC handover
(including intra cell handover and inter cell handover) and inter BSC handover.
After the BSC receives the HANDOVER REQUEST message from MSC, the
incoming BSC handover procedure is initiated. The cell of the BSC (target cell)
receives the Intercell Handover Request message from the other channel of this
cell or from the other cell in this BSC (source cell), the intra BSC handover
procedure is initiated. In these two procedures BSC first allocates channel for the
request. After the successful allocation, BSC sends a CHANNEL ACTIVATION
message to the BTS to activate the allocated channel. BTS checks the state of this
channel and responses to the BSC.
z Measurement point: in intra BSC handover or inter BSC handover procedure, BSC
measures this item upon reception of the CHANNEL ACTIVATION NEGATIVE
ACKNOWLEDGE message from the BTS where the target cell is located after
having sent the CHANNEL ACTIVATION message to this BTS.
z Formula: none
LVIII. TCH channel activation timeout (handover)
z Description: the measurement result of this item includes intra BSC handover
(including intra cell handover and inter cell handover) and inter BSC handover.
After the BSC receives the HANDOVER REQUEST message from MSC, the
incoming BSC handover procedure is initiated. The cell of the BSC (target cell)
receives the HANDOVER REQUEST message from the other channel of this cell
or from the other cell in this BSC (source cell), the intra BSC handover procedure
is initiated. In these two procedures BSC first allocates channel for the request.
After the successful allocation, BSC sends a CHANNEL ACTIVATION message to
the BTS to activate the allocated channel. BTS checks the state of this channel
and responses to the BSC.
z Measurement point: in intra BSC handover or inter BSC handover procedure, BSC
sends a CHANNEL ACTIVATION message to the TCH of the BTS where the
target cell is located and the timer is started to wait for the response. This item is
measured if there is no response from the BTS when the timer expires.
z Formula: none
LIX. TCH mode modification (NACK)
z Description: after receiving the ASSIGNMENT REQUEST message from MSC,

BSC judges the CHANNEL TYPE contained in the message. The mode modify
procedure is initiated if BSC finds that the relation between the requested TCH
and the radio channel allocated in the immediate assignment phase is as follows:
"channel rate and type" are consistent, "speech encoding algorithm/transparency
indicator" are not consistent or speech encoding algorithm/transparency indicator
are not consistent.
3-154
z Measurement point: in the case mode modify procedure is initiated in TCH

assignment procedure, after the MODE MODIFY message is sent to the BTS,
BSC measures this item upon reception of the MODE MODIFY NEGATIVE
ACKNOWLEDGE message responded from the BTS indicating the
implementation of mode modify procedure fails.
z Formula: none
LX. TCH mode modification timeout
z Description: after receiving the ASSIGNMENT REQUEST message from MSC,

BSC judges the CHANNEL TYPE contained in the message. The mode modify
procedure is initiated if BSC finds that the relation between the requested TCH
and the radio channel allocated in the immediate assignment phase is as follows:
"channel rate and type" consistent, and "speech encoding algorithm/transparency
indicator" are not consistent or speech encoding algorithm/transparency indicator
are not consistent.
1) In TCH assignment procedure, if the mode modify procedure is initiated,
after the MODE MODFIY message has been sent to the BTS, a timer is
started. This item is measured if there is no response when the timer expires,
indicating the implementation of the mode modify procedure fails.
2) In the assignment procedure, if the mode modify procedure is initiated, after
the CHANNEL MODE MODFIY message has been sent to the MS, a timer
is started. This item is measured if there is no response from MS when the
timer expires, indicating the implementation of the mode modify procedure
fails.
z Formula: none
LXI. TCH seizure failures due to terrestrial link failures
detects that an active connection has been broken for some reason, it sends a
CONNECTION FAILURE INDICATION message to BSC informing the BSC that
the terrestrial link in ABIS interface fails.
1) BSC measures this item upon reception of the CONNECTION FAILURE
INDICATION message (cause: 0X20-equipment failure and 0X22-terrestrial
channel failure) from the BTS and if the failure occurs on TCH.
2) This item is measured when the RSL link of the TRX that the call is running
on disconnect, which will cause call drop.
z Formula: none
3-155
LXII. TCH seizure failures due to A-interface failures
z Description: after the call established on TCH reports the ESTABLISH

INDICATION message, the established TCH and the related link will be released if
A interface connection failure occurs due to A interface connection failures.
z Measurement point: This item is measured if the duration of A interface trunk
circuit failure exceeds 15 seconds, SCCP connection disconnect, BSC receives
RESET CIRCUIT message from MSC.
z Formula: none
LXIII. Average TCH queue length
z Description: indicates the average number of the calls that participate in the
queuing in the specified cell.
z Measurement point: at the end of a statistic cycle, the average number of the calls
that participate in the queuing in this cycle is sent to the BAM.
z Formula: none
LXIV. Maximum TCH queue length
z Description: indicates the maximum number of the calls that participate in the
queuing in the specified cell.
z Measurement point: at the end of a statistic cycle, the maximum number of the
calls that participate in the queuing in this cycle is sent to the BAM.
z Formula: none
LXV. Average TCH queue time
z Description: in assignment and incoming BSC handover procedure, BSC

implement queue procedure due to no available radio channel and the system
support that. This item indicates the average waiting duration of the calls that
participate in the queuing in the statistic cycle in the specified cell.
z Measurement point: at the end of a statistic cycle, the sum of waiting duration of
the calls that participate in the queuing in this cycle is sent to the BAM. Together
with TCH queue requests and TCH Queue failures for queue full, the average TCH
queue time will be calculated.
z Formula: the sum of TCH queue time / (TCH queue requests - TCH Queue failures
for queue full )
LXVI. Uplink point to point short messages
z Description: TCH can be used to send uplink/downlink short message. This item is
used to measure the number of the uplink short messages sent on the TCH of the
cell.
z Measurement point: this item is measured upon BSCs reception of the uplink
short message sent on TCH.
z Formula: none
3-156
LXVII. Downlink point to point short messages
z Description: TCH can be used to send uplink/downlink short messages. This item
is used to measure the number of the downlink short messages sent on the TCH
of the cell.
z Measurement point: this item is measured upon BSCs reception of the downlink
short message sent on TCH.
z Formula: none
LXVIII. TCH seizure failures for intracell handover
z Description: In the view of calling procedure, intra cell handover in the BSC is the
same as intra BSC handover procedure except the source cell and the serving cell
are the same If the source cell and target cell are the same cell, then this cell is
called the serving cell. In intra cell handover procedure, before the serving cell
sends the Intercell Handover Response message to indicate the new channel is
ready, if the new channel preparation fails due to some reason, the serving cell
sends a Intercell Handover Failure message internally indicating the intra cell
handover failure.
1) In the new TCH activation procedure, this item is measured when the serving
cell receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE
message from the BTS.
2) This item is measured if the implementation of intra cell handover procedure
fails because the encryption algorithm in Intercell Handover Request
message does not support.
3) No response after the timer (internal timer, 5 seconds) expires when the
serving cell activates the new TCH.
4) in intra cell handover procedure, if it is TCH that is requested in the handover
but there is no available TCH in the serving cell, and this leads to the
handover failure. In this case, this item is measured.
z Formula: none
LXIX. TCH seizure failures for intracell handover (no radio resource)
z Description: in intra cell handover procedure, the serving cell sends the Intercell
Handover Request message internally to request a new TCH. Then this item is
measured if the serving cell detects that there is no available TCH during the TCH
allocation.
z Measurement point: in intra cell handover procedure, if it is TCH that is requested
in the handover but there is no available TCH in the serving cell, and this leads to
the handover failure. In this case, this item is measured.
z Formula: none
3-157
LXX. Configured TCHs of 1800 cell
z Description: This item indicates the number of TCH currently configured for a
certain 1800 cell on real-time basis. It excludes the TCH dynamically adjusted to
SDCCH, and includes the TCH adjusted from dynamic PDCH. It is an average
number of configured TCHs got at all sampling points within the statistic cycle.
z Measurement point: System gets the number of configured TCHs every five
seconds. The accumulated value of the data got at all sampling points is divided
with the times of sampling times to get the average number of configured TCHs of
1800 cell within the statistic cycle.
z Formula: none
LXXI. Configured TCHs of 900 cell
z Description: This item indicates the number of TCH currently configured for a
certain 900 cell on real-time basis. It excludes the TCH dynamically adjusted to
number of configured TCHs got at all sampling points within the statistic cycle.
z Measurement point: System gets the number of configured TCHs every five
with the times of sampling to get the average number of configured TCHs of 900
cell within the statistic cycle.
z Formula: none
LXXII. Available TCHs
z Description: This item indicates the number of available (idle or busy) TCHs in a
certain cell on real-time basis. It excludes the TCH dynamically adjusted to
number of available TCHs got at all sampling points within the statistic cycle.
z Measurement point: System gets the number of available TCHs every five
with the times of sampling to get the average number of available TCHs within a
statistic cycle.
z Formula: none
LXXIII. Average num. of busy TCHs
z Description: This item indicates the average number of the busy TCHs in a cell
within the statistic cycle. It is an average number of busy TCHs got at all sampling
points within the statistic cycle. In the view of the number of channel seizures, it
shows the average level of the MSs of this cell seizing the traffic channel
resources.
z Measurement point: System gets the number of busy TCHs every five seconds.
The accumulated value of the data got at all sampling points is divided with the
times of sampling to get the average number of busy TCHs within a statistic cycle.
3-158
z Formula: none
LXXIV. Maximum num. of busy TCHs
z Description: This item indicates the maximum number of the busy TCHs in a cell. It
is a peak value of busy TCHs got at all sampling points within a statistic cycle. In
the view of channel seizures, it shows the maximum traffic channel resource that
is seized by the MSs of the cell.
z Measurement point: System gets the number of busy TCHs every five seconds.
The maximum value can be known by the end of the statistic cycle.
z Formula: none
LXXV. All available TCH allocated time (second)
z Description: This item indicates the duration of no TCH can be allocated. It shows
the situation that all the traffic channel resources of the cell have been allocated or
blocked so that no TCH can be allocated any more.
z Measurement point: Total duration that no TCH in a cell can be allocated.
z Formula: none
LXXVI. Average TCH busy time (second)
z Description: This item indicates the average duration that the TCHs in a cell are
busy, i.e., the average duration for each TCH being busy. In the view of channel
seizure duration, it shows the average level that the MSs of this cell seizes the
traffic channel resource. See Configured TCHs of 1800 cell and Configured TCHs
of 900 cell.
z Measurement point: Total duration of each TCH in a cell being busy.
z Formula: Sum of the duration of each TCH in a cell being busy / (number of
configured TCHs in 1800 cell + number of configured TCHs in 900 cell)
LXXVII. Average num. of idle TCHs in Interf. band 1
z Description: The interference band is the uplink interference level rank of TCH and
this level is reported to BSC by BTS at idle TCH via the RF RESOURCE
INDICATION message. There are six ranks of interference band. The level range
for each band can be set through the data configuration console. Generally they
are set as follows:
Interfere band 0 -110~-105dBm
3-159
The higher the level, the severer the interference. Generally, it is regarded that the
interference exists if the idle channel falls into the interference band 4 or interference
band 5. This item indicates the average number of idle TCHs in the interference band 1.
z Measurement point: System gets the number of idle TCHs in the interference band
1 every five seconds. The accumulated value of the data got at all sampling points
is divided with the times of sampling to get the average number of idle TCHs in
interference band 1 within the statistic cycle.
z Formula: none
LXXVIII. Average num. of idle TCHs in Interf. band 2
are set as follows:
Interference band 0 -110~-105dBm
interference exists if the idle channel falls into the interference band 4 or
interference band 5. This item indicates the average number of idle TCHs in the
interference band 2.
z Formula: none
LXXIX. Average num. of idle TCHs in Interf. band 3
are set as follows:
3-160
z Formula: none
LXXX. Average num. of idle TCHs in Interf. band 4
are set as follows:
z Formula: none
LXXXI. Average num. of idle TCHs in Interf. band 5
are set as follows:
3-161
z Formula: none
LXXXII. Average num. of congested TCHs
z Description: This item indicates the average number of the TCHs being blocked. It
is the average of blocked TCHs got at all sampling points within the statistic cycle.
The TCH blocking can be caused by the channel blocking during the O&M or
caused by RSL link disconnection. It shows the situation of TCHs in a cell being
unavailable within the statistic cycle.
z Measurement point: System checks the number of blocked TCHs every five
divided with the times of sampling to get the average number of blocked TCHs
z Formula: none
LXXXIII. Average num. of idle TCHs
z Description: This item indicates the average number of the TCHs in a cell being
idle. It is the average of idle TCHs got at all sampling points within the statistic
cycle. An idle TCH refers to a TCH that is in normal state and has not been seized.
It shows the situation of TCH seizure in a cell within the period.
z Measurement point: System checks the number of idle TCHs every five seconds.
The accumulated value from the data got at the sampling points is divided with the
times of sampling to get the average number of idle TCHs within the measurement
cycle.
z Formula: none
LXXXIV. Average num. of OOS TCHs
z Description: This item indicates the average number of the TCHs in a cell being in
OOS state. It is the average of OOS TCHs got at all sampling points within the
statistic cycle. The status of OOS means the channel is unavailable, including
channel blocked due to O&M, site status changed from installed to not installed
and BTS or TRX failure. It shows the situation of unavailable TCHs in a cell within
the statistic cycle.
z Measurement point: System checks the number of OOS TCHs every five seconds.
The accumulated value from the data got at the sampling points is divided with the
3-162
times of sampling to get the average number of OOS TCHs within the
measurement cycle.
z Formula: none
LXXXV. TCH usability (%)
z Description: This item indicates the percentage of available TCHs in totally

configured TCHs. See Available TCHs, Configured TCHs of 900 cell and
Configured TCHs of 1800 cell.
z Measurement point: none
z Formula: number of available TCHs / (number of configured TCHs in 1800 cell +
number of configured TCHs in 900 cell)
LXXXVI. Attempted TCH seizures (excluding handover)
z Description: This item indicates the attempted TCH seizures, excluding the ones
for handover and including the ones for calls and for very early TCH assignment.
See Attempted TCH seizures for call and Attempted TCH seizures for very early
assignment.
z Formula: Attempted TCH seizures for call + Attempted TCH seizures for very early
assignment
LXXXVII. Attempted TCH seizures (including handover)
z Description: This item indicates all attempted TCH seizures, excluding the ones
for intracell handover. See Attempted TCH seizures for call, Attempted TCH
seizures for very early assignment, Attempted TCH seizures for intraBSC
incoming cell handover and Attempted TCH seizures for interBSC incoming cell
handover
z Formula: Attempted TCH seizures for call + Attempted TCH seizures for very early
assignment + Attempted TCH seizures for intraBSC incoming cell handover +
Attempted TCH seizures for interBSC incoming cell handover
LXXXVIII. TCH seizure failures (excluding handover)
z Description: This item indicates the TCH seizure failures for calls and for very early
TCH assignment, excluding the ones for handover. See TCH seizure failures for
call and TCH seizure failures for very early assignment.
z Formula: TCH seizures failures for call + TCH seizures failures for very early
assignment
3-163
LXXXIX. TCH seizure failures (including handover)
z Description: This item indicates all TCH seizure failures, excluding the ones for
intracell handover. See TCH seizure failures for call, TCH seizure failures for very
early assignment, TCH seizure failures for intraBSC incoming cell handover(no
radio resource) and TCH seizure failures for interBSC incoming cell handover(no
radio resource).
z Formula: TCH seizure failures for call + TCH seizure failures for very early
assignment + TCH seizure failures for intra BSC incoming cell handover (no radio
resource) + TCH seizure failures for inter BSC incoming cell handover (no radio
resource)
XC. TCH blocking rate (excluding handover)(%)
z Description: This item indicates the percentage of attempted TCH seizure failures
(excluding the ones for handover) in total TCH requests. See TCH seizure failures
for call, TCH seizure failures for very early assignment, Attempted TCH seizures
for call and Attempted TCH seizures for very early assignment.
z Formula: (TCH seizure failures for call + TCH seizure failures for very early
assignment) / (attempted TCH seizures + attempted TCH seizures for very early
assignment)
XCI. TCH blocking rate (including handover)(%)
z Description: This item indicates the percentage of attempted TCH seizure failures
(including the ones for handover, excluding the ones for intracell handover) in total
TCH requests. See TCH seizure failures for call, TCH seizure failures for very
early assignment, TCH seizure failures for intraBSC incoming cell handover(no
radio resource), TCH seizure failures for interBSC incoming cell handover(no
radio resource), Attempted TCH seizures for call, Attempted TCH seizures for very
early assignment, Attempted TCH seizures for intraBSC incoming cell handover
and Attempted TCH seizures for interBSC incoming cell handover.
z Formula: (TCH seizure failures for call + TCH seizure failures for very early
assignment + TCH seizure failures for intra BSC incoming cell handover (no radio
resource) + TCH seizure failures for inter BSC incoming cell handover (no radio
resource) ) / (attempted TCH seizures (all) + attempted TCH seizures for very
early assignment + attempted TCH seizures for intraBSC incoming cell handover
+ attempted TCH seizures for interBSC incoming cell handover)
XCII. TCH traffic volume (excluding very early assignment) (ERL)
z Description: This item indicates the ratio of duration of MS seizing TCH to statistic
cycle. The duration of MS seizing TCH is calculated by multiplying the number of
3-164
MR reported by MS via TCH with the report period (0.48 seconds). See Sum of
TCH measurement reports in the cell (excluding very early assignment).
z Formula: Sum of TCH measurement reports in the cell (excluding very early
assignment) % 0.48 / statistic cycle (second)
XCIII. Traffic density at average TCH call drop
z Description: This item indicates average duration of MS seizing TCH after which a
TCH call drop occurs. The duration of MS seizing TCH is calculated by multiplying
the number of MR reported by MS via TCH with the report period (0.48 seconds).
See Sum of TCH measurement reports in the cell (excluding very early
assignment) and TCH call drop.
z Formula: Total number of TCH measurement reports (excluding very early
assignment) % 0.48 / TCH call drops
XCIV. TCH RF lost rate (%)
z Description: This item indicates the percentage of call drops due to radio link
disconnection when seized by MS caused by air interface causes accounting all
successful TCH seizures. See TCH lost radio connections (connection failure),
TCH lost radio connections (error indication) and Successful TCH seizures (all).
z Formula: (times of radio link disconnection when TCH seized (connection failure)
+ times of radio link disconnection when TCH seized (error indication)) /
successful TCH seizures (all)
XCV. TCH call drop rate (%)
z Description: This item indicates the percentage of TCH call drops accounting all
successful TCH seizures. See TCH call drop, Successful TCH seizures (all).
z Formula: TCH call drops / successful TCH seizures (all)
XCVI. TCH traffic volume of 1800 cell (excluding very early assignment) (ERL))
z Description: This item indicates the ratio of duration of MS (in 1800 cell) seizing
TCH to statistic cycle. The duration of MS seizing TCH is calculated by multiplying
the number of MR reported by MS via TCH with the report period (0.48 seconds).
See Sum of TCH measurement reports in 1800 cell (excluding very early
assignment).
z Formula: Total number of TCH measurement reports in 1800 cell (excluding very
early assignment) % 0.48 / statistic cycle (second)
3-165
XCVII. TCH blocking rate (meeting a TCH blocked state on attempted TCH
seizures)(%)
z Description: This item indicates the percentage of meeting a TCH blocked state on
attempted TCH seizures in attempted TCH seizures (all). See Attempted TCH
seizures meeting a TCH blocked state and Attempted TCH seizures (all).
z Formula: Attempted TCH seizures meeting a TCH blocked state / Attempted TCH
seizures (all)
3.9.3 Random Access Measurement Function
Table 3-11 Random access measurement items
No. Item name

1 Packet paging commands to BTS
2 Packet paging PCH overloads of ABIS interface
3 Circuit paging commands to BTS
4 Successful circuit pagings of ABIS interface
5 Circuit paging PCH overloads of ABIS interface
6 Immediate assignment requests
7 Successful immediate assignments
8 Successful immediate assignments for location update
9 Successful immediate assignments for location update (dual-band MS)
10 Successful immediate assignments for MOC
11 Successful immediate assignments for MOC (dual-band MS)
12 Successful immediate assignments for MTC
13 Successful immediate assignments for MTC (dual-band MS)
14 Successful immediate assignments for emergency calls
15 Successful immediate assignments for call re-establishment
16 Successful immediate assignments for other procedures
17 Circuit paging RACH overloads of ABIS interface
18 Immediate assignment rejections
19 Immediate assignment transmissions
20 Ratio of paging channel overloads(%)
21 Immediate assignment success rate (%)
I. Packet paging commands to BTS
z Description: in the case an MS under the BSC is called for packet service, SGSN
sends a PAGING REQUEST message to PCU to page this MS. PCU processes
this message and then sends the PACKET PAGING message to the BSC.
According to the cell identification discriminator carried in the PACKET PAGING
message, BSC sends a PACKET PAGING REQUEST message to the
corresponding cell. See GSM 0408, 0460, and 0360 protocols.
z Measurement point: this item is measured when BSC sends the PACKET
PAGING REQUEST message to the corresponding cell.
z Formula: none
3-166
II. Packet paging PCH overloads of ABIS interface
z Description: when detecting the overload of PCH seized by packet service (See
GPRS Related Measurement Function for packet logical channel combination
relation), BTS reports the Packet CCCH Load Indication message to the BSC. The
BSC forwards this message to PCU and PCU initiates packet paging flow control
procedure.
z Measurement point: BSC measures this item upon reception of the Packet CCCH
Load Indication message from BTS.
z Formula: none
III. Circuit paging commands to BTS
z Description: in the case an MS under the BSC is called for circuit service, the BSC
sends the PAGING COMMAND message to the corresponding cell according to
the cell identification discriminator after receiving the circuit PAGING message
from MSC or PCU. This item is used to measure the paging times at Abis. See
GSM 0858 and 0408 protocol.
z Measurement point: this item is measured when the BSC sends the PAGING
REQUEST message to the corresponding cell.
z Formula: none
IV. Successful circuit pagings of ABIS interface
z Description: after a called MS receives PAGING REQUEST message from

network side, the paging response procedure is initiated. This MS reports an
ESTABLISH INDICATION (the type of the service request message is PAGING
RESPONSE) to MSC if it successfully seizes the signaling channel. See GSM
0408 protocol.
z Measurement point: this item is measured when BSC receives the ESTABLISH
INDICATION message from MS and the type of the service request message in
ESTABLISH INDICATION is "PAGING RESPONSE".
z Formula: none
V. Circuit paging PCH overloads of ABIS interface
z Description: BTS reports a CCCH LOAD INDICATION message to the BSC when
detecting the overload of CCCH type of PCH, then BSC measures this item and
sends a OVERLOAD message to MSC simultaneously. See GSM 0858 protocol.
z Measurement point: this item is measured when BSC receives the CCCH LOAD
INDICATION message from the BTS with the cause value carried in the message
being PCH overload.
z Formula: none
3-167
VI. Immediate assignment requests
z Description: When network service is required, MS reports a CHANNEL

REQUEST message on RACH, requesting a dedicated control channel. Upon
reception of this message, BSC starts channel allocation and measures this item.
Note:
For a channel request, if second allocation takes places, this item shall only be measured once.
z Measurement point: "SD-ATT-C1" in Figure 3-45 indicates the measurement point.

This item is measured when BSC receives a CHANNEL REQUEST message from
MS.
z Formula: none.
VII. Successful immediate assignments
z Description: In the immediate assignment procedure, after successfully seizing a

channel (SDCCH or TCH) allocated by BSC for transferring signaling, MS reports
a SABM frame on this channel to BTS, indicating the establishment of a radio link
layer connection in the multi-frame mode. BTS returns a UA frame to MS, and
sends an ESTABLISH INDICATION message to BSC, notifying it to establish a
normal Um interface connection.
Note:
This statistic item is measured on all the occasions allowed in the service request message of ESTABLISH
INDICATION. The following items are measured as per the requested service type in the service request
message. All the measurement points are the same.

point in the calling procedure. This item is measured when BSC receives an
ESTABLISH INDICATION message from BTS in the immediate assignment
procedure.
z Formula: none.
VIII. Successful immediate assignments for location update
z Description: This item measures the number of successful immediate

assignments for location update.
3-168
z Measurement point: In the immediate assignment procedure, this item is

measured when BSC receives an ESTABLISH INDICATION from MS, in which,
the type of the service request message is "LOCATION UPDATE REQUEST".
z Formula: none.
IX. Successful immediate assignments for location update (dual-band MS)
z Description: In the immediate assignment procedure, after MS sends a SABM

frame, A UA frame is returned, indicating the establishment of a radio link layer
connection in the multi-frame mode. If SYSTEM INFORMATION TYPE 3 is set as
"ECSC (Early ClassMark Sending Control) allowed", MS (such as dual-band MS
and vehicle mounted large power MS) can automatically initiate the classmark
change procedure, by sending a CLASSMARK CHANGE message on the
dedicated channel. The message contains the new MS classmark 2 information
element. It may also contain a classmark 3 information element. In addition, after
the MM connection between MS and MSC is established, MSC can also initiate
the classmark change procedure, by sending a CLASSMARK CHANGE message
to MS. Likewise, MS shall acknowledge the message and implement the class
change procedure. For further description, please refer to GSM 0408.
z Measurement point: A1 and A2 in Figure 3-49, indicate the measurement point.
This item is measured when BSC receives a CLASSMARK CHANGE message
from MS and finds that the initial access cause is "LOCATION UPDATE".
z Formula: none.
MS BSS M SC
SYSTEM INFORM ATION TYPE 3

ECSC
SABM COM PLETE LAYER 3 INFORM ATION
CLASSM ARK CHANGE CLASSM ARK UPDATE

A1
B1
C1
CLASSM ARK ENQUIRY CLASSM ARK REQUEST
CLASSM ARK CHANGE

CLASSM ARK UPDATE
A2
B2
C2
A1,A2: Successful immediate assignments for location update (dual-band MS)

B1,B2: Successful immediate assignments for MOC (dual-band MS)
C1,C2: Successful immediate assignments for MTC (dual-band MS
Figure 3-49 Classmark change procedure
3-169
X. Successful immediate assignments for MOC

assignments for MOC.
the type of service request message is "CM SERVICE REQUEST" and CM
service type is "MOC".
z Formula: none.
XI. Successful immediate assignments for MOC (dual-band MS)
Description: This item measures the number of successful immediate assignments for
MOC (dual-band MS). For description of the classmark change procedure, please refer
to Successful immediate assignments for location update (dual-band MS)".
z Measurement point: B1 and B2 in Figure 3-49 indicate the measurement point.
from MS and finds that the initial access cause is "MOC".
z Formula: none.
XII. Successful immediate assignments for MTC

assignments for MTC.
the type of service request message is "PAGING RESPONSE".
z Formula: none.
XIII. Successful immediate assignments for MTC (dual-band MS)
z Description: For description of the classmark change procedure, please refer to

Successful immediate assignments for location update (dual-band MS)".
z Measurement point: A1 and A2 in Figure 3-49 indicate the measurement point.
from MS and finds that the initial access cause is "MTC".
z Formula: none.
XIV. Successful immediate assignments for emergency calls

assignments for emergency calls
the type of service request message is "CM SERVICE REQUEST" and CM
service type is "Emergency call establishment".
3-170
z Formula: none.
XV. Successful immediate assignments for call re-establishment
z Description: This item measures successful immediate assignments for call

re-establishment.
measured when BTS reports an ESTABLISH INDICATION message to BSC,
indicating the establishment of SDCCH connection in the multi-frame mode, and
the type of service request message contained in ESTABLISH INDICATION is "
CM REESTABLISHMENT REQUEST".
z Formula: none.
XVI. Successful immediate assignments for other procedures

assignments, and the type of the service request message in ESTABLISH
INDICATION is a value other than the above-mentioned values. For related
information, please refer to Successful immediate assignments.
measured when BTS reports an ESTABLISH INDICATION message to BSC,
which indicates the establishment of SDCCH connection in the multi-frame mode
and contains the following information. Type of the service request message is
"IMSI DETACH" or "CM SERVICE REQUEST". CM service type is "Packet mode
connection establishment", "Short message service", or "Supplementary service
activation".
z Formula: none.
XVII. Circuit paging RACH overloads of ABIS interface
z Description: when detecting CCCH type of RACH overload, BTS reports to BSC,
then BSC measures this item and implements the internal flow control if BSC
support that.
z Measurement point: this item is measured when BSC receives the CCCH LOAD
INDICATION message from the BTS with the cause value carried in the message
being RACH overload.
z Formula: none
XVIII. Immediate assignment rejections
z Description: upon reception of the CHANNEL REQUEST message from the MS, if
there is no available channel, the BSC sends the IMMEDIATE ASSIGNMENT
REJECT message to the MS indicating the immediate assignment procedure fails.
z Measurement point: upon reception of the CHANNEL REQUEST message from
the MS, if there is no available channel, the BSC sends the IMMEDIATE
ASSIGNMENT REJECT message to the MS. In this case, this item is measured.
3-171
z Formula: none
XIX. Immediate assignment transmissions
z Description: upon reception of the CHANNEL REPORT message reported from

MS, BSC allocates and then activates a signaling channel for the MS. Upon
reception of CHANNEL ACTIVATION ACKNOWLEDGE message from BTS
indicating that the channel is ready, BSC sends a IMMEDIATE ASSIGN
COMMAND to inform the MS to access the dedicated signaling channel, which
can be SDCCH or TCH.
z Measurement point: this item is measured when the BSC sends the IMMEDIATE
ASSIGN COMMAND message.
z Formula: none
XX. Ratio of paging channel overloads(%)
z This is an analytic item that describes the relation between PCH overloads and
paging at Abis interface. Both circuit service and packet service are included in
this item.
z Measurement point: Analytic item. See Circuit paging PCH overloads of ABIS
interface, Packet paging PCH overloads of ABIS interface, Circuit paging
commands to BTS, and Packet paging commands to BTS.
z Formula: (Circuit paging PCH overloads of ABIS interface + Packet paging PCH
overloads of ABIS interface ) / (Circuit paging commands to BTS + Packet paging
commands to BTS)
XXI. Immediate assignment success rate (%)
z Description: This is an analytic item. In immediate assignment procedure, for one

request, MS might send several the CHANNEL REQUEST messages but the
ESTABLISH INDICATION message can be sent only one time. So this item
cannot directly reflect the situation of unsuccessful immediate assignments.
z Measurement point: Analytic item. See Successful immediate assignments and
Immediate assignment requests
z Formula: Successful immediate assignments/ Immediate assignment requests
3.9.4 Inter-cell Handover Measurement Function
Table 3-12 Statistic items in Inter-cell Handover Measurement Function
No. Item name

1 Attempted incoming internal inter cell handovers
2 Incoming internal inter cell handovers
3 Attempted incoming interBSC inter cell handovers
4 Attempted incoming internal inter cell handovers (from 900 cell)
5 Attempted incoming internal inter cell handovers (from 1800 cell)
3-172
6 Attempted outgoing internal inter cell handovers

7 Outgoing internal inter cell handovers
8 Attempted outgoing interBSC inter cell handovers
9 Attempted outgoing internal inter cell handovers (to 900 cell)
10 Attempted outgoing internal inter cell handovers (to 1800 cell)
11 Outgoing interBSC inter cell handovers (to 900 cell)
12 Outgoing interBSC inter cell handovers (to 1800 cell)
13 Attempted handovers for uplink quality
14 Attempted handovers for downlink quality
15 Attempted handovers for uplink strength
16 Attempted handovers for downlink strength
17 Attempted handovers for timing advance
18 Attempted handovers for better cell
19 Attempted handovers for traffic load
20 Attempted handovers for rapid level drop
21 Attempted handovers for response to MSC invocation
22 Attempted handovers for O&M intervention
23 Attempted handovers for directed retry
24 Attempted handovers for other causes
25 Attempted handovers with receiving level rank 0
31 Attempted handovers with receiving quality rank 0
39 Average receiving level at handover request
40 Average receiving quality at handover request
41 Successful incoming internal inter cell handovers
42 Successful incoming interBSC inter cell handovers
43 Successful incoming internal inter cell handovers (from 900 cell)
44 Successful incoming internal inter cell handovers (from 1800 cell)
45 Successful outgoing internal inter cell handovers
46 Successful outgoing interBSC inter cell handovers
47 Successful outgoing internal inter cell handovers (to 900 cell)
48 Successful outgoing internal inter cell handovers (to 1800 cell)
49 Successful outgoing interBSC inter cell handovers (to 900 cell)
50 Successful outgoing interBSC inter cell handovers (to 1800 cell)
51 Unsuccessful incoming internal inter cell handovers
52 Unsuccessful incoming internal inter cell handovers (no radio resource available)
53 Unsuccessful incoming internal inter cell handovers (other causes)
54 Unsuccessful outgoing internal inter cell handovers
55 Unsuccessful incoming interBSC inter cell handovers
56 Unsuccessful outgoing interBSC inter cell handovers
57 Unsuccessful internal inter cell handovers (channel mode unacceptable)
58 Unsuccessful internal inter cell handovers (timing advance out of range)
59 Unsuccessful internal inter cell handovers (frequency not implemented)
60 Unsuccessful internal inter cell handovers (timer expired)
61 Unsuccessful internal inter cell handovers (other causes)
62 Unsuccessful internal inter cell handovers with successful reversions
63 Unsuccessful internal inter cell handovers with unsuccessful reversions
64 Attempted inter cell handovers
65 Successful inter cell handovers
66 Internal inter cell handover success rate (%)
3-173
67 Inter cell radio handover success rate(%)

68 Dual-band internal inter cell handover success rate (%)
I. Attempted incoming internal inter cell handovers
z Description: During the procedure of internal intercell handover, the source cell
sends an Intercell Handover Request message to the target cell after handover
algorithm decision. This item measures the times of the current cell, as the target
cell of internal intercell handover, receiving the Intercell Handover Request
message. It indicates the frequency of the intraBSC handover from other cells to
the current cell. Together with Successful incoming internal inter cell handovers
and Unsuccessful incoming internal inter cell handovers, this item shows the
performance of this type of handover. Related items: Attempted incoming
interBSC inter cell handovers and Attempted outgoing internal inter cell
handovers.
z Measurement point: During the procedure of internal intercell handover, the target
cell (current cell) receives an Intercell Handover Request message from the
source cell. This item is measured in this case.
z Formula: none.
II. Incoming internal inter cell handovers
z Description: During the procedure of internal intercell handover, the target cell
sends Intercell Handover Response to the source cell after channel activation to
indicate that the channel preparation is complete. This message contains the
HANDOVER COMMAND message to be sent to MS. This item measures the
times of the current cell, as the target cell of internal intercell handover, sending
Intercell Handover Response. Together with Attempted incoming internal inter cell
handovers, this item shows the situation of handover failure due to abnormality
during the procedure of channel preparation in the target cell. Together with
Successful incoming internal inter cell handovers, this item shows the situation of
handover failure due to radio interface abnormal. Related items: Outgoing internal
inter cell handovers and Inter BSC incoming cell handovers.
cell (current cell) sends Intercell Handover Response to the source cell. This item
is measured in this case.
z Formula: none.
III. Attempted incoming interBSC inter cell handovers
z Description: During the procedure of interBSC handover, on reception of

HANDOVER REQUEST from MSC, the target BSC will pack this message into
IntoBSC Handover Request to be transferred to the BM of the target cell. This item
measures the times of the current cell receiving IntoBSC Handover Request. It
3-174
indicates the frequency of the handovers from cells in other BSC to the current cell.
Together with Successful incoming interBSC inter cell handovers and
Unsuccessful incoming interBSC inter cell handovers, this items shows the
performance of this type of handover. Related items: Attempted incoming internal
inter cell handovers and Attempted outgoing interBSC inter cell handovers.
z Measurement point: During the procedure of interBSC handover, the target cell
(current cell) receives IntoBSC Handover Request. This item is measured in this
case.
z Formula: none.
IV. Attempted incoming internal inter cell handovers (from 900 cell)
algorithm decision. This item measures the times of current cell, as the target cell
of internal intercell handover, receiving Intercell Handover Request from the
source cell (GSM900). It indicates the frequency of the intraBSC handover from
other cells (GSM900) to the current cell. Together with Successful incoming
internal inter cell handovers (from 900 cell), this item shows the performance of
this type of handover. Related items: Attempted incoming internal inter cell
handovers.
Note:
Cell system type: GSM 900 cell and GSM 1800 cell.
1 to 124.
from 512 to 885.
cell (current cell) receives the Intercell Handover Request message from the
source cell (GSM900). This item is measured in this case.
z Formula: none.
V. Attempted incoming internal inter cell handovers (from 1800 cell)
algorithm decision. This item measures the times of current cell, as the target cell
of internal intercell handover, receiving Intercell Handover Request from the
source cell (GSM1800). It indicates the frequency of the intraBSC handover from
other cells (GSM1800) to the current cell. Together with Successful incoming
3-175
internal inter cell handovers (from 1800 cell), this item shows the performance of
this type of handover. Related items: Attempted incoming internal inter cell
handovers.
Note:
1 to 124.
from 512 to 885.
cell (current cell) receives the Intercell Handover Request message from the
source cell (GSM1800). This item is measured in this case.
z Formula: none.
VI. Attempted outgoing internal inter cell handovers

receiving quality, TA, traffic load, Response to MSC invocation, directed retry,
rapid rxlevel drop, better cell, O&M intervention. The source cell and the target cell
are different ones in the same BSC. This item measures the times of internal
intercell handover attempts initiated by the current cell. This item reflects the
frequency of the current cell initiating internal intercell handovers. This item,
together with Successful outgoing internal inter cell handovers and Unsuccessful
outgoing internal inter cell handovers, shows the performance of this type of
handover. Related items: Attempted outgoing interBSC inter cell handovers and
Attempted incoming internal inter cell handovers.
Note:
In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of the
same BSC, the adjacent cell will be treated as an idle cell because system cant get the using situation of
channels in other BMs cell) has higher priority to be selected as the target cell. If all adjacent cells of the
source cell are congested, system will still select the default adjacent cell which is the first one in the
handover candidate list, even if it is congested so as to carry out the measurement of this item.
3-176
Intercell Handover Request message to the target cell. This item is measured if
the source cell and the target cell are different in this case.
z Formula: none.
VII. Outgoing internal inter cell handovers
z Description: During the procedure of internal intercell handover, after successfully

activating the new channel, the target cell will inform the source cell that the
channel is ready. After receiving the information, the source cell will send a
HANDOVER COMMAND message to the MS. This item measures the times of the
HANDOVER COMMAND message being sent from the current cell. This item,
together with Attempted outgoing internal inter cell handovers, this item shows the
situation of handover failure due to abnormality during the procedure of channel
preparation in the target cell. Together with Successful outgoing internal inter cell
handovers, this item shows the situation of handover failure due to radio interface
abnormal. Related items: Incoming internal inter cell handovers and Inter BSC
outgoing cell handovers.
source cell sends a HANDOVER COMMAND message to a MS. This item is
z Formula: none.
MS BTS BSC MSC/VLR

(Intercell handover)
CHANNEL ACT
CHAN ACT ACK
HANDOVER COMMAND
A1
HANDOVER COMPLETE
HANDOVER PERFORMED
A1: Outgoing internal inter cell handovers

Figure 3-50 Outgoing internal inter cell handovers
VIII. Attempted outgoing interBSC inter cell handovers

rapid rxlevel drop, better cell, O&M intervention. The source cell and target cell are
in different BSCs. The source cell sends a HANDOVER REQUIRED message to
MSC to initiate a handover. This message contains a list of candidate cells for
handover. At this stage, the source cell does not know the target cell which is
selected by MSC or whether the selected cell is congested. It only records the first
3-177
cell in the candidate list as the default target cell. This item measures the times of
source cell notifying MSC to initiate handover attempts. This item reflects the
frequency of current cell initiating interBSC handover. Together with Successful
outgoing interBSC inter cell handovers and Unsuccessful outgoing interBSC inter
cell handovers, this item shows the performance of this type of handover. Related
items: Attempted outgoing internal inter cell handovers and Attempted incoming
interBSC inter cell handovers.
z Measurement point: After handover algorithm decision, the source cell (current
cell) sends a HANDOVER REQUIRED message to MSC. This item is measured in
this case, as shown in Figure 3-51 A1.
z Formula: none.
MS BSC1 MSC/VLR BSC2 MS
HANDOVER REQUIRED
A1 HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COMMAND
B1 , C1, D1, E1, F1
HANDOVER COMMAND
HANDOVER ACCESS
HANDOVER DETECT
HANDOVER COMPLETE
HANDOVER COMPLETE
CLEAR COMMAND
CLEAR COMPLETE
A1: Attempted outgoing interBSC inter cell handovers

B1: Inter BSC outgoing cell handovers
C1: Outgoing interbsc inter cell handovers (to 900)
D1: Outgoing interbsc inter cell handovers (to 1800)
E1: Attempted dual-band intercell handovers
F1: Attempted outgoing inter cell handovers (including various handover causes)
Figure 3-51 Attempted outgoing interBSC inter cell handovers
IX. Attempted outgoing internal inter cell handovers (to 900 cell)

different ones in the same BSC. This item measures the times of handover
attempts from the current cell to the target cell (GSM900). It shows the frequency
of the handovers from the current cell to other GSM900 cells in the same BSC.
This item, together with Successful outgoing internal inter cell handovers (to 900
3-178
cell), shows the performance of this type of handover. Related items: Attempted
outgoing internal inter cell handovers.
Note:
1) In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of the
2) Cell system type: GSM 900 cell and GSM 1800 cell.
1 to 124.
from 512 to 885.
cell) sends Intercell Handover Request to the target cell (GSM900 cell). This item
is measured if the source cell and the target cell are different ones in this case.
z Formula: none.
X. Attempted outgoing internal inter cell handovers (to 1800 cell)

different ones in the same BSC. This item measures the times of handover
attempts from the current cell to the target cell (GSM1800). It shows the frequency
of the handovers from the current cell to other GSM1800 cells in the same BSC.
This item, together with Successful outgoing internal inter cell handovers (to 1800
cell), shows the performance of this type of handover. Related items: Attempted
outgoing internal inter cell handovers.
3-179
Note:
1). In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of
the same BSC, the adjacent cell will be treated as an idle cell because system cant get the using situation
of channels in other BMs cell) has higher priority to be selected as the target cell. If all adjacent cells of the
2). Cell system type: GSM 900 cell and GSM 1800 cell.
1 to 124.
from 512 to 885.
cell) sends an Intercell Handover Request message to the target cell (GSM1800
cell). This item is measured if the source cell and the target cell are different.
z Formula: none.
XI. Outgoing interBSC inter cell handovers (to 900 cell)
which is sent by MSC to the source BSC. After receiving this message, the source
BSC sends it to MS. This item measures the times of the current cell sending the
HANDOVER COMMAND message in the handovers from the current cell to the
GSM900 cells. Together with Successful outgoing interBSC inter cell handovers
(to 900 cell), this item shows the situation of handover failure due to radio interface
abnormal. Related items: Inter BSC outgoing cell handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of InterBSC handover, this item is

measured when the source cell (current cell) receives the HANDOVER
COMMAND message from MSC and the target cell is a GSM900 one, as shown in
Figure 3-51 C1.
3-180
z Formula: none.
XII. Outgoing interBSC inter cell handovers (to 1800 cell)
BSC sends it to MS. This item measures the times of the current cell sending the
HANDOVER COMMAND message in the handovers from the current cell to the
GSM1800 cells. Together with Successful outgoing interBSC inter cell handovers
(to 1800 cell), this item shows the situation of handover failure due to radio
interface abnormal. Related items: Attempted outgoing interBSC inter cell
handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of InterBSC handover, this item is

measured when the source cell (current cell) receives the HANDOVER
COMMAND message from MSC and the target cell is a GSM1800 one, as shown
in Figure 3-51 D1.
z Formula: none.
XIII. Attempted handovers for uplink quality
z Description: When BSC initiates a handover, it will receive a Handover Indication

message from LAPD module. This message contains the cause value of handover.
The times of handover attempts for all kinds of causes can be measured according
to the causes in this message. This item measures the times of handover attempts
(including internal intracell handover, internal intercell handover and interBSC
handovers) caused by uplink signal quality in the current cell. This item shows the
frequency of handover caused by uplink signal quality in the current cell. Related
items: Attempted intracell handovers, Attempted outgoing internal inter cell
handovers, Attempted outgoing interBSC inter cell handovers and Attempted
intracell handovers for uplink quality.
cell) sends the Intercell Handover Request message (internal intracell handover
and internal intercell handover) or the HANDOVER REQUIRED message
3-181
(interBSC handover) due to uplink signal quality. This item is measured in this
case.
z Formula: none.
XIV. Attempted handovers for downlink quality

(including BSC internal intracell handover, internal intercell handover BSC internal
intercell and inter BSC handovers) caused by downlink signal quality in the current
cell. This item shows the frequency of handover caused by downlink signal quality
in the current cell. Related items: Attempted intracell handovers, Attempted
outgoing internal inter cell handovers, Attempted outgoing interBSC inter cell
handovers and Attempted intracell handovers for .
(interBSC handover) due to downlink signal quality. This item is measured in this
case.
z Formula: none.
XV. Attempted handovers for uplink strength

intercell and inter BSC handovers) caused by uplink signal strength in the current
cell. This item shows the frequency of handover caused by uplink signal strength
in the current cell. Related items: Attempted intracell handovers, Attempted
handovers and Attempted intracell handovers for other causes.
(interBSC handover) due to uplink signal strength. This item is measured in this
case.
z Formula: none.
3-182
XVI. Attempted handovers for downlink strength

intercell and inter BSC handovers) caused by downlink signal strength in the
current cell. This item shows the frequency of handover caused by downlink signal
strength in the current cell. Related items: Attempted intracell handovers,
Attempted outgoing internal inter cell handovers, Attempted outgoing interBSC
inter cell handovers and Attempted intracell handovers for other causes.
(interBSC handover) due to downlink signal strength. This item is measured in this
case.
z Formula: none.
XVII. Attempted handovers for timing advance

to the causes in this message. This item measures the times of handovers
(including internal intercell handover and interBSC handover) caused by TA in the
current cell (a subscriber moves far away from the serving cell but it is close to the
target cell while talking, which causes the signal strength and the signal quality in
serving cell drop thus a handover is triggered). This item shows the frequency of
handover caused by TA in the current cell. Related items: Attempted outgoing
internal inter cell handovers and Attempted outgoing interBSC inter cell
handovers.
z Measurement point: After handover algorithm decision, the source cell sends the
Intercell Handover Request message (internal intercell handover) or the
HANDOVER REQUIRED message (interBSC handover) due to TA. This item is
z Formula: none.
XVIII. Attempted handovers for better cell

(including internal intercell handover and interBSC handover) caused by "better
3-183
cell" (adjacent cell with lower path loss (PBGT) or higher priority) in the current cell.
This item shows the frequency of handover caused by "better cell" in the current
cell. Related items: Attempted outgoing internal inter cell handovers and
Attempted outgoing interBSC inter cell handovers.
HANDOVER REQUIRED message (interBSC handover) due to "better cell". This
z Formula: none.
XIX. Attempted handovers for traffic load

(including internal intercell handover and interBSC handover) caused by traffic
load in the current cell. This item shows the frequency of handover caused by
traffic load in the current cell. Related items: Attempted outgoing internal inter cell
handovers and Attempted outgoing interBSC inter cell handovers.
HANDOVER REQUIRED message (interBSC handover) due to traffic load. This
z Formula: none.
XX. Attempted handovers for rapid level drop

(including internal intercell handover and interBSC handover) caused by rapid
rxlevel drop in the current cell. This item shows the frequency of handover caused
by rapid rxlevel drop in the current cell. Related items: Attempted outgoing internal
inter cell handovers and Attempted outgoing interBSC inter cell handovers.
HANDOVER REQUIRED message (interBSC handover) due to rapid rxlevel drop.
z Formula: none.
3-184
XXI. Attempted handovers for response to MSC invocation

(including internal intercell handover and interBSC handover) caused by
Response to MSC invocation (MSC sending HANDOVER CANDIDATE
ENQUIRY to BSC which causes handovers of multiple MSs in a cell) in the current
cell. This item shows the frequency of handover caused by Response to MSC
invocation in the current cell. Related items: Attempted outgoing internal inter cell
HANDOVER REQUIRED message (interBSC handover) due to Response to
MSC invocation. This item is measured in this case.
z Formula: none.
XXII. Attempted handovers for O&M intervention

intercell and inter BSC handovers) caused by O&M intervention (operation on
O&M console which causes handovers, such as forced handover, blocking without
call dropped (blocking channels, TRXs and cells), BCCH mutual aid or TRX
mutual aid) in the current cell. This item shows the frequency of handover caused
by O&M intervention. Related items: Attempted intracell handovers, Attempted
handovers and Attempted intracell handovers for other causes.
Handover Request (BSC internal intracell and BSC internal intercell handovers) or
the HANDOVER REQUIRED message (interBSC handover) due to O&M
intervention. This item is measured in this case.
z Formula: none.
XXIII. Attempted handovers for directed retry

(including internal intercell handover and interBSC handover) caused by directed
3-185
retry (a handover triggered for the current cell is congested during the procedure
of assignment) in the current cell. This item shows the frequency of handover
caused by directed retry. Related items: Attempted outgoing internal inter cell
HANDOVER REQUIRED message (interBSC handover) due to directed retry.
z Formula: none.
XXIV. Attempted handovers for other causes

The times of handover attempts for all kinds of handover causes can be measured
according to the cause in this message. This item measures the times of handover
attempts (including BSC internal intracell handover, internal intercell handover
BSC internal intercell and inter BSC handovers) caused by other causes (such as
fast moving, handover cause being abnormal value) in the current cell. This item
shows the frequency of handover caused by other causes. Related items:
Attempted intracell handovers, Attempted outgoing internal inter cell handovers,
Attempted outgoing interBSC inter cell handovers and Attempted intracell
handovers for other causes.
Handover Request (BSC internal intracell and BSC internal intercell handovers) or
the HANDOVER REQUIRED message (interBSC handover) due to other causes.
z Formula: none.
XXV. Attempted handovers with receiving level rank 0
z Description: When BSC initiates handover, it will receive Handover Indication from
LAPD module. The times of various ranks can be measured according to the
receiving strength rank and receiving quality rank (obtained from the last MR that
triggered the handover) contained in this message. This item measures the times
of uplink receiving strength rank being 0 (rxlevel -100 dBm) when the current cell
initiates a handover (including internal intracell handover, internal intercell
handover and interBSC handover). Together with times of other receiving strength
ranks and receiving quality ranks, this item shows the handover environment of
the current cell.
cell) sends an Intercell Handover Request message (internal intracell handover,
internal intercell handover) or the HANDOVER REQUIRED message (interBSC
handover) and the uplink receiving strength rank is 0 (rxlevel -100 dBm).
3-186
z Formula: none.
XXVI. Attempted handovers with receiving level rank 1
of uplink receiving strength rank being 1 (-99 ~ -95 dBm) when the current cell
the current cell.
handover) and the uplink receiving strength rank is 1 (-99 ~ -95 dBm).
z Formula: none.
XXVII. Attempted handovers with receiving level rank 2
the current cell.
z Formula: none.
XXVIII. Attempted handovers with receiving level rank 3
3-187
the current cell.
z Formula: none.
XXIX. Attempted handovers with receiving level rank 4
the current cell.
z Formula: none.
XXX. Attempted handovers with receiving level rank 5
of uplink receiving strength rank being 5 ( -69 dBm) when the current cell initiates
a handover (including internal intracell handover, internal intercell handover and
interBSC handover). Together with times of other receiving strength ranks and
receiving quality ranks, this item shows the handover environment of the current
cell.
handover) and the uplink receiving strength rank is 5 ( -69 dBm).
z Formula: none.
3-188
XXXI. Attempted handovers with receiving quality rank 0
of uplink receiving quality rank being 0 (BER < 0.2%) when the current cell initiates
handover (including BSC internal intra cell, BSC internal inter cell and interBSC
handovers). Together with times of other receiving strength ranks and receiving
quality ranks, this item shows the handover environment of the current cell.
Intercell Handover Request message (BSC internal intra cell, BSC internal inter
cell handovers) or the HANDOVER REQUIRED message (interBSC handovers)
and the uplink receiving quality rank is 0 (BER < 0.2%).
z Formula: none.
XXXII. Attempted handovers with receiving quality rank 1
of uplink receiving quality rank being 1 (BER: 0.2 ~ 0.4%) when the current cell
initiates handover (including BSC internal intra cell, BSC internal inter cell and
interBSC handovers). Together with times of other receiving strength ranks and
cell.
and the uplink receiving quality rank is 1 (BER: 0.2 ~ 0.4%).
z Formula: none.
XXXIII. Attempted handovers with receiving quality rank 2
cell.
3-189
z Formula: none.
XXXIV. Attempted handovers with receiving quality rank 3
cell.
z Formula: none.
XXXV. Attempted handovers with receiving quality rank 4
cell.
z Formula: none.
XXXVI. Attempted handovers with receiving quality rank 5
3-190
cell.
z Formula: none.
XXXVII. Attempted handovers with receiving quality rank 6
cell.
z Formula: none.
XXXVIII. Attempted handovers with receiving quality rank 7
of uplink receiving quality rank being 7 (BER > 12.8%) when the current cell
cell.
and the uplink receiving quality rank is 7 (BER > 12.8%).
3-191
z Formula: none.
XXXIX. Average receiving level at handover request
LAPD module. This message contains uplink receiving strength (obtained from the
last MR that triggered the handover). Whenever the current cell initiates a
handover (including internal intracell handover, internal intercell handover and
interBSC handover), the uplink receiving strength will be added to the value of this
item which is the sum of the receiving strength at handover in BSC. The sum of the
receiving strengths at handover and the times of initiating three types of attempted
handovers can be used to calculate the average receiving strength when the
current cell initiates handovers. This item shows the handover environment of the
current cell.
Intercell Handover Request message (internal intracell handover, internal intercell
handover) or the HANDOVER REQUIRED message (interBSC handover). The
uplink receiving strength reported by LAPD module is measured at this moment
for this item.
z Formula: Sum of receiving strengths at handovers / (Attempted outgoing internal
inter cell handovers + Attempted outgoing interBSC inter cell handovers +
Attempted intracell handovers)
Note:
The sum of receiving strengths at handovers is the BSC internal statistic meaning of average receiving
strength item at initiating handover. The average value is obtained after the calculation following the
formula.
XL. Average receiving quality at handover request
LAPD module. This message contains uplink receiving quality (obtained from the
last MR that triggered the handover). Whenever the current cell initiates a
handover (including internal intracell handover, internal intercell handover and
interBSC handover), the uplink receiving quality will be added to the value of this
item which is the sum of the receiving strength at handover in BSC. The sum of the
receiving strengths at handover and the times of initiating three types of attempted
handovers can be used to calculate the average receiving quality when the current
cell initiates handovers. This item shows the handover environment of the current
cell.
3-192
Intercell Handover Request message (internal intracell handover, internal intercell
handover) or the HANDOVER REQUIRED message (interBSC handover). The
uplink receiving quality reported by LAPD module is measured at this moment for
this item.
z Formula: Sum of receiving quality at handovers / (Attempted outgoing internal
inter cell handovers + Attempted outgoing interBSC inter cell handovers +
Attempted intracell handovers)
Note:
The sum of receiving quality at handovers is the BSC internal statistic meaning of average receiving
quality item at initiating handover. The average value is obtained after the calculation following the
formula.
XLI. Successful incoming internal inter cell handovers
handover cause: directed retry, non-directed retry (e.g. signal quality, signal
strength, TA, traffic load, rapid rxlevel drop, better cell, Response to MSC
handovers. This item, together with Attempted incoming internal inter cell
handovers, helps the user know the performance of internal intercell handovers.
Related items: Successful incoming interBSC inter cell handovers, Successful
outgoing internal inter cell handovers, Successful outgoing interBSC inter cell
handovers. Successful intracell handovers.
1) Measured when the target cell (current cell) sends ASSIGNMENT
COMPLETE to MSC after the MS has been successfully handed over to the
target cell in the internal intercell handover (handover cause: directed retry),
as shown in Figure 3-52 A1.
2) Measured when the target cell (current cell) sends a HANDOVER
PERFORMED message to MSC after the MS has been successfully handed
over to the target cell in the internal intercell handover (handover cause:
non-directed retry, e.g. signal quality, signal strength, TA, traffic load, rapid
rxlevel drop, better cell, Response to MSC invocation, and O&M intervention),
z Formula: none.
3-193
MS BTS BSC MSC/VLR
ASSIGNMENT REQUEST
HANDOVER COMMAND
HANDOVER COMPLETE
ASSIGNMENT COMPLETE
A1, B1, C1, D1, E1
A1: Successful incoming internal inter cell handovers

B1: Successful incoming internal inter cell handovers (from 900)
C1: Successful incoming internal inter cell handovers (from 1800)
D1: Successful dual-band intercell handovers
E1: Successful incoming inter cell handovers
Figure 3-52 Successful incoming internal inter cell handovers (directed retry)
MS BTS BSC MSC/VLR
.HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER PERFORMED
A1, B1 , C1, D1, E1, F1
A1: Successful intracell handovers

B1: Successful incoming internal inter cell handovers
D1: Successful incoming internal inter cell handovers (from 1800)
E1: Successful dual-band intercell handovers
F1: Successful incoming inter cell handovers
Figure 3-53 Successful intraBSC handovers (not directed retry)
XLII. Successful incoming interBSC inter cell handovers
accessed the target cell, the target BSC fv MSC, and this handover is finished
successfully. This item, together with Attempted incoming interBSC inter cell
handovers, helps the user know the performance of interBSC handovers. Related
items: Successful incoming internal inter cell handovers, Successful outgoing
internal inter cell handovers, Successful outgoing interBSC inter cell handovers.
z Measurement point: During the procedure of interBSC handover, the target
(current) cell receives HANDOVER COMPLETE, and sends it to MSC. This item is
z Formula: none.
3-194
MS BTS BSC MSC/VLR

HANDOVER REQUESTT
CHANNEL ACT
CHAN ACT ACK HANDOVER REQ ACK
.HANDOVER DETECTION
HANDOVER COMPLETE
A1, B1, C1
HANDOVER COMPLETE
A1: Successful incoming inter BSC inter cell handovers

B1: Successful dual-band intercell handovers
C1: Successful incoming inter cell handovers
Figure 3-54 Successful incoming inter BSC internal inter cell handovers
XLIII. Successful incoming internal inter cell handovers (from 900 cell)
invocation, and O&M intervention). This item measures the times of MS being
handed over successfully from other GSM 900 cell to the current cell in the same
BSC. This item, together with Attempted incoming internal inter cell handovers
(from 900 cell), helps the user know the performance of internal intercell handover.
Related items: Successful incoming internal inter cell handovers.
Note:
1 to 124.
from 512 to 885.
COMPLETE to MSC after the MS has been successfully handed over from
the GSM900 cell to the target cell in the internal intercell handover (handover
cause: directed retry), as shown in Figure 3-52 B1.
3-195
over from the GSM900 cell to the target cell in the internal intercell handover
(handover cause: non-directed retry, e.g. signal quality, signal strength, TA,
traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and
O&M intervention), as shown in Figure 3-53 C1.
z Formula: none.
XLIV. Successful incoming internal inter cell handovers (from 1800 cell)
invocation, and O&M intervention). This item measures the times of MS being
handed over successfully from other GSM 1800 cell to the current cell in the same
BSC. This item, together with Attempted incoming internal inter cell handovers
(from 1800 cell), helps the user know the performance of internal intercell
handover. Related items: Successful incoming internal inter cell handovers.
Note:
1 to 124.
from 512 to 885.
COMPLETE to MSC after the MS has been successfully handed over from
the GSM1800 cell to the target cell in the internal intercell handover
(handover cause: directed retry), as shown in Figure 3-52 C1.
over from the GSM1800 cell to the target cell in the internal intercell handover
(handover cause: non-directed retry, e.g. signal quality, signal strength, TA,
traffic load, rapid rxlevel drop, better cell, Response to MSC invocation, and
O&M intervention), as shown in Figure 3-53 D1.
z Formula: none.
XLV. Successful outgoing internal inter cell handovers
sends a HANDOVER COMMAND message to MS. After MS is handed over to the
target cell, the target cell sends Inter Clear Request to the source cell to indicate
3-196
that the handover succeeded. On reception of this message, the source cell clears
the original resources. This item measures the times of the current cell, as the
source cell, receiving Inter Clear Request from the target cell. Together with
Attempted outgoing internal inter cell handovers, this item shows the performance
of internal intercell handover. Related items: Successful incoming internal inter
cell handovers, Successful outgoing interBSC inter cell handovers.
source cell (current cell) receives Inter Clear Request (cause: internal intercell
handover succeeded) from the target cell. This item is measured in this case.
z Formula: none.
XLVI. Successful outgoing interBSC inter cell handovers
z Description: During the procedure of interBSC handover, the source cell sends a
HANDOVER COMMAND message to MS. After MS successfully accessed the
target cell, the source cell receives the CLEAR COMMAND message (cause:
handover success) from MSC and begins to clear the previous resources. This
handover successfully ends here. Together with Attempted outgoing interBSC
inter cell handovers, Unsuccessful outgoing interBSC inter cell handovers, this
item shows the performance of interBSC handover. Related items: Successful
intracell handovers, Successful incoming interBSC inter cell handovers,
Successful outgoing internal inter cell handovers.
z Measurement point: During the procedure of interBSC handover, the source cell
(current cell) receives the CLEAR COMMAND message (cause: handover
A1.
z Formula: none.
3-197
HANDOVER REQUIRED
HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COMMAND
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
CLEAR COMMAND
A1, B1, C1, D1, E1
CLEAR COMPLETE
A14: Successful outgoing interbsc inter cell handovers

B1: Successful outgoing interbsc inter cell handovers (to 900)
C1: Successful outgoing interbsc inter cell handovers (to 1800)
E1: Successful outgoing inter cell handovers (including various causes)
Figure 3-55 Successful outgoing interBSC inter cell handovers
XLVII. Successful outgoing internal inter cell handovers (to 900 cell)
(current cell) sends a HANDOVER COMMAND message to MS. After MS is
source cell to clear the previous resources. This item measures the times of the
current cell, as the source cell, receiving Inter Clear Request from the target
GSM900 cell. Together with Attempted outgoing internal inter cell handovers (to
900 cell), this item shows the performance of internal intercell handover. Related
items: Successful outgoing internal inter cell handovers.
Note:
1 to 124.
from 512 to 885.
3-198

handover succeeded) from the target GSM900 cell.
z Formula: none.
XLVIII. Successful outgoing internal inter cell handovers (to 1800 cell)
(current cell) sends a HANDOVER COMMAND message to MS. After MS is
source cell to clear the previous resources. This item measures the times of the
current cell, as the source cell, receiving Inter Clear Request from the target
GSM1800 cell. Together with Attempted outgoing internal inter cell handovers (to
1800 cell), this item shows the performance of internal intercell handover. Related
items: Successful outgoing internal inter cell handovers.
Note:
1 to 124.
from 512 to 885.

handover succeeded) from the target GSM1800 cell.
z Formula: none.
XLIX. Successful outgoing interBSC inter cell handovers (to 900 cell)
cell, MSC sends CLEAR COMMAND (cause: handover success) to source cell to
measures the times of successful interBSC handovers from the current cell to
other GSM900 cells in other BSC. Related items: Successful outgoing interBSC
inter cell handovers.
3-199
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of interBSC handover from the source
cell (current cell) to a GSM900 cell, the source cell receives the CLEAR
COMMAND message (cause: handover success) from MSC. This item is
measured in this case, as shown in Figure 3-55 B1.
z Formula: none.
L. Successful outgoing interBSC inter cell handovers (to 1800 cell)
z Description: During the procedure of interBSC handover, the source cell (current
cell) sends a HANDOVER COMMAND message to MS. After successfully
accessed the target cell, MSC sends CLEAR COMMAND (cause: handover
success) to source cell to clear the previous resources. This handover
successfully ends here. This item measures the times of successful interBSC
handovers from the current cell to other GSM1800 cells in other BSC. Related
items: Successful outgoing interBSC inter cell handovers.
Note:
1 to 124.
from 512 to 885.
z Measurement point: During the procedure of interBSC handover from the source
cell (current cell) to a GSM1800 cell, the source cell receives the CLEAR
COMMAND message (cause: handover success) from MSC. This item is
measured in this case, as shown in Figure 3-55 C1.
z Formula: none.
LI. Unsuccessful incoming internal inter cell handovers
z Description: After internal intercell handover is initiated, the target cell receives the
Intercell Handover Request message from the source cell. And then, it allocates
3-200
and activates channels and waits for the access of MS to the target channel. If the
access of MS is successful, the target cell will send a HANDOVER PERFORMED
message to MSC to indicate that this handover is successful. If abnormality occurs
during this process, then this handover is a failure. This item measures the times
of unsuccessful incoming internal inter cell handovers to the current cell. Together
withAttempted incoming internal inter cell handovers, Successful incoming
internal inter cell handovers, this item shows the performance of incoming internal
inter cell handover. Related items: Unsuccessful intracell handovers,
Unsuccessful outgoing internal inter cell handovers, Unsuccessful incoming
Note:
The following are the causes of unsuccessful incoming internal inter cell handover:
1) The original channel becomes invalid or connection disconnects due to abnormality of radio resource
and terrestrial resource;
parameters;
3) Handover is interrupted and the original call is cleared when error has been detected during BSS
1) During the procedure of internal intercell handover, the target cell (current cell)
receives Inter Clear Request from the source cell. This item is measured in
this case. The source cell sends Inter Clear Request to the target cell on
reception of the CONNECTION FAILURE INDICATION message, the
ERROR INDICATION message, the CLEAR COMMAND message or at the
expiry of the timer waiting for Inter Clear Request.
receives CONNECTION FAILURE INDICATION from BTS. This item is
measured in this case, as shown in Figure 3-56 A1, A2 and A3.
receives the ERROR INDICATION message (cause: timer T200 expired
(N200 + 1) times (0x01) or unsolicited DM response, multiple frame
established state (0x05) or sequence error (0x07)). This item is measured in
this case, as shown in Figure 3-56 A5, A6 and A7.
4) During the procedure of internal intercell handover, abnormality (no available
channel) occurs when the target cell (current cell) is allocating new channels.
This item is measured in this case, and at the same time, Intercell Handover
Reject is sent to the source cell.
3-201
fails to send the CHANNEL ACTIVATION message. This item is measured in
this case, and at the same time, Intercell Handover Reject is sent to the
source cell.
6) During the procedure of internal intercell handover, the target (current) cell
receives the CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE
message. This item is measured in this case, and at the same time, Intercell
Handover Reject is sent to the source cell, as shown in Figure 3-56 A4.
receives Clear For Handover Failure from the source cell after successful
channel activation. This happens when MS fails to access the target cell and
returns to the source cell, and then the source cell notifies the target cell to
clear the related resources after receiving the HANDOVER FAILURE
message from MS.
waiting for CHANNEL ACTIVATION ACKNOWLEDGE times out. This item is
measured in this case, and at the same time, Intercell Handover Reject is
sent to the source cell.
waiting for HANDOVER DETECTION times out again after resending
Intercell Handover Response on timeout. This item is measured in this case,
and then the related resources are released.
waiting for HANDOVER COMPLETE times out. This item is measured in this
case, and at the same time, Inter Clear Request is sent to the source cell.
z Formula: none.
3-202
MS BTS BSC MSC/VLR

CHANNEL ACT
CHAN ACT NACK
CONN FAIL IND A4
ERROR IND A2, B2
CHAN ACT ACK A5, B4
.HANDOVER COMMAND
Old Channel
ERROR IND
A6 , B5
CONN FAIL IND
A1 , B1
HANDOVER DETECTIOIN
New Channel
ERROR IND
CONN FAIL IND A7 , B6
A3 , B3
HANDOVER COMPLETE
New Channel
HANDOVER PERFORMED
A1~A7: Unsuccessful incoming internal inter cell handovers

B1~B6: Unsuccessful incoming internal inter cell handovers (other causes)
Figure 3-56 Unsuccessful incoming internal inter cell handovers
LII. Unsuccessful incoming internal inter cell handovers (no radio resource
available)
Intercell Handover Request message from the source cell. And then, it starts to
allocate channels. If the channel allocation fails here, this handover will fail due to
no channel available in the target cell. This item measures the times of
unsuccessful internal intercell handovers to the current cell due to no radio
resource available. Together with Unsuccessful incoming internal inter cell
handovers, this item shows the situation of unsuccessful handover due to channel
allocation.
z Measurement point: During the procedure of internal intercell handover,
abnormality (no available channel) occurs when the target cell (current cell) is
allocating new channels. This item is measured in this case, and at the same time,
Intercell Handover Reject is sent to the source cell.
z Formula: none.
LIII. Unsuccessful incoming internal inter cell handovers (other causes)
Intercell Handover Request message from the source cell. And then, it allocates
and activates channels and waits for the access of MS to the target channel. If the
3-203
access of MS is successful, the target cell will send a HANDOVER PERFORMED

message to MSC to indicate that this handover is successful. If abnormality occurs
during this process, then this handover is a failure. This item measures the times
of unsuccessful incoming internal inter cell handovers to the current cell due to
other causes (e.g. timer timeout, radio interface abnormal). Together with
Unsuccessful incoming internal inter cell handovers, this item shows the situation
of unsuccessful handover due to other causes.
receives Inter Clear Request from the source cell. This item is measured in
this case. The source cell sends Inter Clear Request to the target cell on
reception of the CONNECTION FAILURE INDICATION message, the
ERROR INDICATION message, the CLEAR COMMAND message or at the
expiry of the timer waiting for the Inter Clear Request message.
2) Measured when the source cell (current cell) receives CONNECTION
FAILURE INDICATION from BTS during the procedure of internal intercell
handover, as shown in Figure 3-56 B1, B2 and B3.
established state (0x05) or sequence error (0x07)). This item is measured in
this case, as shown in Figure 3-56 B4, B5 and B6.
fails to send the CHANNEL ACTIVATION message. This item is measured in
this case, and at the same time, Intercell Handover Reject is sent to the
source cell.
receives Clear for Handover Failure from the source cell after successful
channel activation. This happens when MS fails to access the target cell and
returns to the source cell, and then the source cell notifies the target cell to
clear the related resources after receiving the HANDOVER FAILURE
message from MS.
message. This item is measured in this case, and at the same time, Intercell
Handover Reject is sent to the source cell.
waiting for CHANNEL ACTIVATION ACKNOWLEDGE times out. This item is
measured in this case, and at the same time, Intercell Handover Reject is
sent to the source cell.
waiting for HANDOVER DETECTION times out again after resending
3-204
Intercell Handover Response on timeout. This item is measured in this case,

and then the related resources are released.
waiting for HANDOVER COMPLETE times out. This item is measured in this
case, and at the same time, the Inter Clear Request message is sent to the
source cell.
z Formula: none.
LIV. Unsuccessful outgoing internal inter cell handovers
z Description: After internal intercell handover is initiated, the source cell enters the
state of waiting for Intercell Handover Response. The target cell allocates and
activates channels, and then sends Intercell Handover Response to notify the
source cell. The source cell sends a HANDOVER COMMAND message to MS,
and then enters the states of waiting for the Inter Clear Request message. After
MS has successfully access the new channel, the target cell sends Inter Clear
Request to notify the source cell to clear the original resource. This handover is a
successful one. The abnormalities occur during this period will result in the failure
of outgoing internal inter cell handovers. This item measures the times of
unsuccessful outgoing internal inter cell handovers to the current cell. Together
with Attempted outgoing internal inter cell handovers, Successful outgoing internal
inter cell handovers, this item shows the performance of internal intercell handover.
Related items: Unsuccessful intracell handovers, Unsuccessful incoming internal
inter cell handovers, Unsuccessful outgoing interBSC inter cell handovers.
Note:
The following are the causes of unsuccessful outgoing internal inter cell handover:
1) The original channel becomes invalid or connection disconnects due to abnormality of radio resource
and terrestrial resource;
parameters;
3) Handover is interrupted and the original call is cleared when error has been detected during BSS
1) During the procedure of internal intercell handover, the source cell (current
cell) receives CONNECTION FAILURE INDICATION from BTS. This item is
measured in this case, as shown in Figure 3-57 A1 and A2.
2) During the procedure of internal intercell handover, MS fails to access the
target cell and returns to the source cell (current cell), and the source cell
3-205
receives the HANDOVER FAILURE message from MS. This item is

measured in this case, and at the same time, Clear for Handover Failure is
sent to the target cell, as shown in Figure 3-57 A3.
cell) receives the ERROR INDICATIONmessage (cause: timer T200 expired
(N200 + 1) times (0x01) or unsolicated DM response, multiple frame
established state (0x05) or sequence error" (0x07)) from BTS. This item is
cell) receives the CLEAR COMMAND message from MSC. This item is
5) During the procedure of internal intercell handover, when AM/CM net-drive
fails or the timer waiting for HANDOVER COMPLETE times out, the target
cell sends Inter Clear Request to the source cell. This item is measured when
the source cell (current cell) receives this message.
6) During the procedure of internal intercell handover, the target cell sends
Intercell Handover Reject to the source cell when it fails to prepare or activate
the channels (e.g. channel allocation failure, CHANNEL ACTIVATION
NEGATIVE ACKNOWLEDGE received, expiry of the timer waiting for
CHANNEL ACTIVATION ACKNOWLEDGE). This item is measured when
the source cell (current cell) receives this message.
7) During the procedure of internal intercell handover, when the source cell
(current cell) waiting for Inter Clear Request times out, it sends Inter Clear
Request to the target cell. This item is measured in this case.
8) During the procedure of internal intercell handover, the source cell waiting for
Intercell Handover Response times out again after resending Intercell
Handover Request. This item is measured in this case, and then the related
resources will be released.
z Formula: none.
3-206
MS BTS BSC MSC/VLR

CHANNEL ACT
CONN FAIL IND

ERROR IND A1 , F2
A4, F4
CLEAR COMMAND
A6, F6
Old Channel .HANDOVER COMMAND
ERROR IND
A5, F5, H2, J2
CONN FAIL IND
A2, F3, H1,J1 CLEAR COMMAND
.HANDOVER FAILURE A7, F7
Old Channel
A3, B1, C1, D1, E1, F1, G1, I1
HANDOVER COMPLETE
A1~A7: Unsuccessful outgoing internal inter cell handovers

B1: Unsuccessful outgoing internal inter cell handovers (channel invalid)
C1: Unsuccessful outgoing internal inter cell handovers (TA invalid)
D1: Unsuccessful outgoing internal inter cell handovers (frequency invalid)
E1: Unsuccessful outgoing internal inter cell handovers (timer expired)
F1~F7: Unsuccessful outgoing internal inter cell handovers (other causes)
G1: Unsuccessful internal inter cell handovers with successful reversions
H1~H2: Unsuccessful internal inter cell handovers with unsuccessful reversions
I1: Unsuccessful outgoing intercell handovers with successful reversions
J1~J2: Unsuccessful outgoing intercell handovers with unsuccessful reversions
Figure 3-57 Unsuccessful outgoing internal inter cell handovers
LV. Unsuccessful incoming interBSC inter cell handovers
the HANDOVER REQUEST message from MSC, and then packs this message
into IntoBSC Handover Request, which is then sent to the BM of the target cell to
request for internal resource. And then BSC checks the conditions of incoming
BSC handovers. If the conditions can be satisfied, BSC requests for channel
resource and generates a HANDOVER COMMAND message. And then BSC
activates the channel and waits for the access of MS to the new channel. On
receiving the HANDOVER COMPLETE message from MS, the target BSC sends
a HANDOVER COMPLETE message to MSC, and this handover is finished here.
If abnormality takes place during this period, BSC will send a CLEAR REQUEST
message or a HANDOVER FAILURE message to MSC to release the resource.
This means this incoming BSC handover fails. This item measures the times of
interBSC handovers when the current cell is the target cell. Together with
Attempted incoming interBSC inter cell handovers, this item shows the
performance of interBSC handover. Related items: Unsuccessful incoming
internal inter cell handovers, Unsuccessful outgoing interBSC inter cell handovers.
3-207
Note:
The causes of incoming BSC handover can be:
1) Equipment failure;
2) Resource congestion or resource unavailable;
3) Message content invalid;
4) Timers time out;
5) Error have been detected during BSS internal processing, e.g. storing a message in buffer failed,
decoding failed;
6) MSC notifies BSC to clear resources.
1) During the procedure of interBSC handover, the target cell (current cell)
processes HANDOVER REQUEST. This item is measured if the following
abnormalities occur, and in this case, the target cell will send a HANDOVER
FAILURE message to MSC: service type is speech or data but no CIC
contained or the contained CIC does not belong to the target BSC.
obtains the specified CIC contained in the HANDOVER REQUEST message.
This item is measured when the following abnormalities occur, and in this
case, the target cell will send a HANDOVER FAILURE message to MSC: the
state of the specified CIC is busy or abnormal, dismatching between circuit
pool and channel rate type or speech version.
sends a HANDOVER FAILURE message to MSC for AM/CM net-drive fails.
4) During the procedure of interBSC handover, the target cell (current cell) will
check the incoming BSC handover conditions. This item is measured when
abnormalities are detected, and the target cell will at the same time send
HANDOVER FAILURE to MSC. The abnormalities include: Service type is
data but the channel rate type is unknown, requesting for channel failed,
ciphering algorithm is not supported.
5) During the procedure of interBSC handover, the target cell (current cell) fails
to send the CHANNEL ACTIVATION message. This item is measured in this
case, and at the same time, the target cell sends a HANDOVER FAILURE
message to MSC.
message. This item is measured in this case, and at the same time, the target
cell will send a HANDOVER FAILURE message to MSC, as shown in
Figure 3-58 A1.
3-208
receives CONNECTION FAILURE INDICATION from BTS after receiving
HANDOVER DETECTION. This item is measured in this case, and at the
same time, the target cell will send a HANDOVER FAILURE message to
MSC, as shown in Figure 3-58 A2.
receives HANDOVER DETECTION or HANDOVER COMPLETE. This item
is measured when the decoding of these messages failed, and in this case,
the target cell will send a CLEAR REQUEST message to MSC.
sends a HANDOVER COMPLETE message to MSC. This item is measured
when the target cell fails to send this message, and in this case, it will send a
starts timer waiting for CHANNEL ACTIVATION ACKNOWLEDGE. This item
is measured when this timer times out, and in this case, the target cell will
send a HANDOVER FAILURE message to MSC.
starts timer Tqho (maximum allowed queuing time for handover). This item is
measured when the timer times out, and in this case, the target cell will send
a HANDOVER FAILURE message to MSC.
starts timer waiting for the HANDOVER DETECTION message or timer
waiting for the HANDOVER COMPLETE message. This item is measured
when these timers time out, and in this case, the target cell will send a
receives the CLEAR COMMAND message from MSC. This item is measured
in this case, as shown in Figure 3-58 A3~A5.
z Formula: none.
3-209
MS BTS New BSC MSC/VLR Old BSC
HANDOVER REQUIRED
HANDOVER REQUEST
CHAN ACT
CLEAR COMMAND
A3
CHAN ACT NACK
A1
CHAN ACT ACK
HANDOVER REQ ACK
HANDOVER COMMAND
HANDOVER COMMAND
Old Channel
CLEAR COMMAND
HANDOVER DETECTION A4
New Channel CLEAR COMMAND
A5
CONN FAIL IND
A2
New Channel HANDOVER COMPLETE
HANDOVER COMPLETE
A1~A5 : Unsuccessful incoming interbsc inter cell handovers

Figure 3-58 Unsuccessful incoming interBSC inter cell handovers
LVI. Unsuccessful outgoing interBSC inter cell handovers
HANDOVER REQUIRED message to MSC to initiate a handover. After MS has
been successfully handed over to the target cell, the source cell which receives
the CLEAR COMMAND message from MSC, which means the handover has
been successfully completed. If abnormality occurs during this period, the
interBSC handover will be an unsuccessful one. This item measures the times of
interBSC handover failures when the current cell is the source cell, i.e. interBSC
outgoing handover failures. Together with, Attempted outgoing interBSC inter cell
handovers, Successful outgoing interBSC inter cell handovers, this item shows
the performance of interBSC handover. Related items: Unsuccessful outgoing
internal inter cell handovers, Unsuccessful incoming interBSC inter cell handovers,
Unsuccessful outgoing BSC handovers with successful reversion, Unsuccessful
outgoing BSC handovers with unsuccessful reversion.
1) During the procedure of interBSC handover, MS fails to access the target cell
and returns to the source cell (current cell). The source cell receives the
HANDOVER FAILURE message (cause: Radio interface failure, reversion to
old channel) from MS. This item is measured in this case, as shown in
Figure 3-59 A1.
2) During the procedure of interBSC handover, the source cell (current cell)
receives CONNECTION FAILURE INDICATION from BTS. This item is
3-210
(N200+1) times" (0x01) or unsolicited DM response, multiple frame
established state (0x05) or sequence error" (0x07)) from BTS. This item is
receives the CLEAR COMMAND message (cause: not handover success)
from MSC. This item is measured in this case, as shown in Figure 3-59 A6
and A7.
receives HANDOVER REQUIRED REJECT from MSC. This item is
6) During the procedure of interBSC handover, the timer T7 (waiting for
HANDOVER COMMAND) expired after the source cell (current cell) had
resent HANDOVER REQUIRED for twice due to this timer expiry. This item is
7) During the procedure of interBSC handover, the timer T8 (waiting for the
CLEAR COMMAND message (cause: handover success) from MSC) expired.
BTS BSC1 MSC/VLR

HANDOVER REQUIRED
CONN FAIL IND
A2 CLEAR COMMAND
A6
ERROR INDICATION
A4
HANDOVER REQ REJ
A8
HANDOVER COMMAND
HANDOVER COMMAND
HANDOVER FAILURE
A1 CLEAR COMMAND
A7
CONN FAIL IND
A3
ERROR INDICATION
A5
CLEAR COMMAND
CLEAR COMPLETE
A1~A8: Unsuccessful incoming interBSC inter cell handovers

Figure 3-59 Unsuccessful incoming interBSC inter cell handovers
3-211
LVII. Unsuccessful internal inter cell handovers (channel mode unacceptable)
z Description: After internal intercell handover is initiated, the source cell sends a
HANDOVER COMMAND message to MS, and then enters the states of waiting for
the Inter Clear Request message. After the access of MS to the new channel, the
target cell sends Inter Clear Request to notify the source cell to clear the previous
resources. This marks a successful internal intercell handover. If MS fails to
access the target cell due to channel invalid (the mode or the type of the allocated
channel not in line with what MS requests for), then this outgoing internal inter cell
handover is a failure in the current cell. This item measures the times of
unsuccessful outgoing internal inter cell handovers due to channel invalid when
the current cell is the source cell. Together with Unsuccessful outgoing internal
inter cell handovers, this item shows the situation of unsuccessful outgoing
internal inter cell handovers due to channel invalid when the current cell is the
source cell.
z Measurement point: During the procedure of internal intercell handover, MS fails
to access the target cell and returns to the source cell (current cell), and the source
cell receives the HANDOVER FAILURE message (cause: Abnormal release,
channel unacceptable (0x02) or Channel mode unacceptable (0x09)) from MS.
z Formula: none.
LVIII. Unsuccessful internal inter cell handovers (timing advance out of range)
HANDOVER COMMAND message to MS, and then enters the state of waiting for
access the target cell due to TA invalid (the value of TA out of normal range), then
this outgoing internal inter cell handover is a failure. This item measures the times
of unsuccessful outgoing internal inter cell handovers due to timing advance out of
range when the current cell is the source cell. Together with Unsuccessful
outgoing internal inter cell handovers, this item shows the situation of
unsuccessful outgoing internal inter cell handovers due to timing advance out of
range when the current cell is the source cell.
cell receives the HANDOVER FAILURE message (cause: Handover impossible,
timing advance out of range (0x08)) from MS. This item is measured in this case,
as shown in Figure 3-57 C1.
z Formula: none.
3-212
LIX. Unsuccessful internal inter cell handovers (frequency not implemented)
access the target cell due to frequency not implemented (the allocated ARFCN of
frequency not supported by MS), then this outgoing internal inter cell handover is a
failure. This item measures the times of unsuccessful outgoing internal inter cell
handovers due to frequency not implemented when the current cell is the source
cell. Together with Unsuccessful outgoing internal inter cell handovers, this item
shows the situation of unsuccessful outgoing internal inter cell handovers due to
frequency not implemented when the current cell is the source cell.
cell receives the HANDOVER FAILURE message (cause: Frequency not
implemented (0x0a)) from MS. This item is measured in this case, as shown in
Figure 3-57 D1.
z Formula: none.
LX. Unsuccessful internal inter cell handovers (timer expired)
resources. This marks a successful internal intercell handover. If various timers
expired during the process, then this outgoing internal inter cell handover is a
failure. This item measures the times of unsuccessful outgoing internal inter cell
handovers due to timer expired when the current cell is the source cell. Together
with Unsuccessful outgoing internal inter cell handovers, this item shows the
situation of unsuccessful outgoing internal inter cell handovers due to timer
expired when the current cell is the source cell.
receives the HANDOVER FAILURE message (cause: Abnormal release,
timer expired (0x03)) from MS. This item is measured in this case, as shown
in Figure 3-57 E1.
2) During the procedure of internal intercell handover, when the timer waiting for
HANDOVER COMPLETE times out, the target cell sends Inter Clear Request
to the source cell. This item is measured when the source cell (current cell)
3-213
cell) waiting for Inter Clear Request times out. This item is measured in this
case.
4) During the procedure of internal intercell handover, the source cell waiting for
Intercell Handover Response times out again after resending Intercell
Handover Request due to timeout. This item is measured in this case.
z Formula: none.
LXI. Unsuccessful internal inter cell handovers (other causes)
resources. This marks a successful internal intercell handover. There are many
abnormalities during the process, such as abnormal channel preparation in the
target cell, abnormal at radio link and internal processing abnormal, which caused
this handover failure. As far as, the causes except for channel invalid, TA out of
range, frequency not implemented and timer expired are all considered as other
causes. This item measures the times of unsuccessful outgoing internal inter cell
handovers due to other causes when the current cell is the source cell. Together
with Unsuccessful outgoing internal inter cell handovers, this item shows the
situation of unsuccessful outgoing internal inter cell handovers due to other
causes when the current cell is the source cell.
receives the HANDOVER FAILURE message (cause: other causes,
including Abnormal release, unspecified (0x01), Preemptive release (0x05),
Call already cleared (0x41), Semantically incorrect message (0x5f), Invalid
mandatory information (0x60), Message type non - existent or not
implemented (0x61), Message type not compatible with protocol state (0x62),
Conditional IE error (0x64), No cell allocation available (0x65), Protocol error
unspecified (0x6f), etc.) from MS. This item is measured in this case, as
shown in Figure 3-57 F1.
cell) receives CONNECTION FAILURE INDICATION from BTS. This item is
measured in this case, as shown in Figure 3-57 F2 and F3.
cell) receives the ERROR INDICATION message (cause: timer T200 expired
established state (0x05) or sequence error (0x07)) from BTS. This item is
3-214
cell) receives the CLEAR COMMAND message from MSC. This item is
5) During the procedure of internal intercell handover, the target cell sends
Intercell Handover Reject to the source cell when it fails to prepare or activate
the channels (e.g. channel allocation failure, CHANNEL ACTIVATION
ACTIVATION ACKNOWLEDGE). This item is measured when the source
cell (current cell) receives this message.
fails, the target cell sends Inter Clear Request to the source cell. This item is
measured when the source cell (current cell) receives this message.
z Formula: none.
LXII. Unsuccessful internal inter cell handovers with successful reversions
sends a HANDOVER COMMAND message to MS. If the MS cannot access the
send a HANDOVER FAILURE message (cause: Radio interface failure, reversion
to old channel) to the source cell via the previous channel. The source cell then
informs the target cell to clear the resources related to this handover. The
connecting between the source cell and MS remains the same. This item
measures the times of unsuccessful handover with successful reversion when the
current cell is the source cell in a handover. Related items: Unsuccessful outgoing
internal inter cell handovers, Unsuccessful internal inter cell handovers with
unsuccessful reversions, Unsuccessful intracell handovers with successful
reversions, Unsuccessful outgoing BSC handovers with successful reversion.
z Measurement point: This item is measured when the source cell (current cell),
receives the HANDOVER FAILURE message (cause: Radio interface failure,
reversion to old channel) from MS during the procedure of internal intercell
handover, as shown in Figure 3-57 G1.
z Formula: none.
LXIII. Unsuccessful internal inter cell handovers with unsuccessful reversions
z Description: During the procedure of internal intercell handover, after the source
cell sends a HANDOVER COMMAND message to MS, the connection between
MS and the source cell is terminated before the connection between MS and the
target cell set up due to poor radio environment or equipment failure. When BSC
detects this situation, it will send a CLEAR REQUEST message to MSC to clear
the previous resources and the involved resources during handover. This
handover failed and the original service cannot be restored. This item measures
the times of unsuccessful handover with unsuccessful reversion when the current
3-215
cell is the source cell in a handover. Related items: Unsuccessful outgoing internal
inter cell handovers, Unsuccessful internal inter cell handovers with successful
reversions, Unsuccessful intracell handovers with unsuccessful reversions,
Unsuccessful outgoing BSC handovers with unsuccessful reversion.
z Measurement:
1) This item is measured when the source cell (current cell) receives
CONNECTION FAILURE INDICATION during the procedure of internal
intercell handover, as shown in Figure 3-57 H1.
cell) receives the ERROR INDICATION message (cause: timer T200 expired
measured in this case, as shown in Figure 3-57 H2.
fails, the target cell sends Inter Clear Request to the source cell. This item is
4) This item is measured when the source cell (current cell) waiting for Inter
Clear Request times out after sending the HANDOVER COMMAND
message to MS during the procedure of internal intercell handover.
z Formula: none.
LXIV. Attempted inter cell handovers
z Description: This item measures the times of attempted inter cell handovers in the
current cell, including incoming internal inter cell handover, incoming interBSC
inter cell handover, outgoing internal inter cell handover and outgoing interBSC
inter cell handover. Related items:Attempted incoming internal inter cell
handovers, Attempted incoming interBSC inter cell handovers, Attempted
handovers.
z Formula: Attempted incoming internal inter cell handovers+ Attempted incoming
interBSC inter cell handovers + Attempted outgoing internal inter cell handovers +
Attempted outgoing interBSC inter cell handovers
LXV. Successful inter cell handovers
z Description: This item measures the times of successful inter cell handovers in the
inter cell handover, outgoing internal inter cell handover, outgoing interBSC inter
cell handover. Related items: Successful incoming internal inter cell handovers,
Successful incoming interBSC inter cell handovers, Successful outgoing internal
inter cell handovers, Successful outgoing interBSC inter cell handovers.
3-216
z Formula: Successful incoming internal inter cell handovers + Successful incoming

interBSC inter cell handovers + Successful outgoing internal inter cell handovers +
Successful outgoing interBSC inter cell handovers
LXVI. Internal inter cell handover success rate (%)
z Description: This item measures the success rate of the inter cell handovers in the
inter cell handover, outgoing interBSC inter cell handover and outgoing interBSC
inter cell handover. Related items: Successful incoming internal inter cell
handovers, Successful incoming interBSC inter cell handovers, Successful
handovers, Attempted incoming internal inter cell handovers, Attempted incoming
interBSC inter cell handovers, Attempted outgoing internal inter cell handovers,
z Formula: (Successful incoming internal inter cell handovers + Successful
incoming interBSC inter cell handovers + Successful outgoing internal inter cell
handovers + Successful outgoing interBSC inter cell handovers) / (Attempted
incoming internal inter cell handovers+ Attempted incoming interBSC inter cell
handovers + Attempted outgoing internal inter cell handovers + Attempted
outgoing interBSC inter cell handovers)
LXVII. Inter cell radio handover success rate(%)
z Description: This item measures the success rate of inter cell radio handover in
the current cell, including incoming internal inter cell handover, incoming interBSC
inter cell handover, outgoing interBSC inter cell handover and outgoing interBSC
inter cell handover. Related items: Successful incoming internal inter cell
handovers, Incoming internal inter cell handovers, Inter BSC incoming cell
handovers, Outgoing internal inter cell handovers, Inter BSC outgoing cell
handovers.
z Formula: (Successful incoming internal inter cell handovers + Successful
incoming interBSC inter cell handovers + Successful outgoing internal inter cell
handovers + Successful outgoing interBSC inter cell handovers) / (Incoming
internal inter cell handovers + Inter BSC incoming cell handovers + Outgoing
internal inter cell handovers + Inter BSC outgoing cell handovers).
LXVIII. Dual-band internal inter cell handover success rate (%)
z Description: This item measures the success rate of dual-band inter cell handover
in the current cell, including incoming internal inter cell handover, incoming
3-217
interBSC inter cell handover, outgoing interBSC inter cell handover and outgoing
interBSC inter cell handover. Related items: Successful dual-band intercell
handovers, Attempted dual-band intercell handovers.
z Formula: Successful dual-band intercell handovers / Attempted dual-band intercell
handovers
3.9.5 Intra-cell Handover Measurement Function
The items of intra-cell handover measurement function are shown in Table 3-13.
Table 3-13 Statistic items in intra-cell handover measurement function
No. Item name

1 Attempted intracell handovers
2 Successful intracell handovers
3 Attempted intracell handovers for uplink quality
4 Attempted intracell handovers for downlink quality
5 Attempted intracell handovers for other causes
6 Unsuccessful intracell handovers
7 Unsuccessful intracell handovers (channel mode unacceptable)
8 Unsuccessful intracell handovers (frequency not implemented)
9 Unsuccessful intracell handovers (timer expired)
10 Unsuccessful intracell handovers (other causes)
11 Unsuccessful intracell handovers with successful reversions
12 Unsuccessful intracell handovers with unsuccessful reversions
13 Intracell handover success rate (%)
I. Attempted intracell handovers

receiving quality, O&M intervention, and IUO handover. Its source cell and target
cell are the same one. This item measures the number of intracell handover
attempts initiated by the current cell. The measurement result of this item can be
used to observe the frequency of the intracell handover initiated by the current cell.
Together with Successful intracell handovers, Unsuccessful intracell handovers,
this item reflects the performance of intracell handover of the current cell. Related
items: Attempted outgoing internal inter cell handovers, Attempted outgoing
3-218
Note:
In intraBSC handover, an idle adjacent cell (if the adjacent and the source cell are in different BMs of the
handover candidate list, even if it is congested. If the selected adjacent cell and the source cell are the
same one, this item will be measured. But IUO handover (a special type of intracell handover from
underlaid to overlaid subscell or from overlaid to underlaid subcell of an IUO cell) is an exception. When
the target subcell is congested, handover cannot be initiated, and the measurement will not be carried out.
cell) sends an Intercell Handover Request message to the target cell. This item is
measured if the source cell is the same as the target cell in this case.
z Formula: none.
II. Successful intracell handovers

receiving quality, O&M intervention, and IUO handover. If BSC receives Handover
Complete, which indicates the MS has been successfully handed over to the
target cell. BSC then sends Handover Performed to MSC to notify the success of
this handover. This item measures the times of successful intracell handovers in
the current cell. This item, together with Attempted intracell handovers and
Unsuccessful intracell handovers helps the user know the performance of intracell
handover in the current cell. Related items: Successful incoming internal inter cell
handovers.
z Measurement: Measured when the target cell (current cell) sends Handover
Performed to MSC after the MS has been successfully handed over to target cell
in the intracell handover, as shown in Figure 3-53 A1.
z Formula: none.
III. Attempted intracell handovers for uplink quality
z Description: When BSC initiates a handover, it will receive Handover Indication

from LAPD module. This message contains the cause value of the handover. The
times of handover attempts for all kinds of handover causes can be measured
according to the cause in this message. This item measures the times of
attempted intracell handovers caused by uplink signal quality in the current cell.
This item shows the frequency of intracell handover caused by uplink signal
3-219
quality in the current cell. Related items: Attempted intracell handovers, Attempted
handovers for uplink quality.
cell) sends an Intercell Handover Request message (internal intracell handover)
due to uplink signal quality. This item is measured if the source and target cells are
the same one in this case.
z Formula: none.
IV. Attempted intracell handovers for downlink quality

attempted intracell handovers caused by downlink signal quality in the current cell.
This item shows the frequency of intracell handover caused by downlink signal
quality in the current cell. Related items: Attempted intracell handovers, Attempted
handovers for downlink quality.
due to downlink signal quality. This item is measured if the source and target cells
are the same one in this case.
z Formula: none.
V. Attempted intracell handovers for other causes

attempted intracell handovers caused by other causes (e.g. signal strength, O&M
intervention) in the current cell. This item shows the frequency of intracell
handover caused by other causes in the current cell. Related items: Attempted
intracell handovers, Attempted handovers for other causes.
due to other causes (e.g. signal strength, O&M intervention). This item is
measured if the source and target cells are the same one in this case.
z Formula: none.
VI. Unsuccessful intracell handovers
z Description: After an intracell handover has been initiated, the source cell enters
the state of waiting for Intercell Handover Response. After the target cell has
allocated channel, activated new channel, and sent Intercell Handover Response
3-220
to inform the source cell about it. After the source cell sends Handover Command
to MS, it enters the state of waiting for the Inter Clear Request message. After the
MS has been successfully accessed the new channel, the target cell will send Inter
Clear Request to inform the source cell to release the previous channel and this
intracell handover is finished successfully. During this period, any abnormality will
cause failure of handover. This item measures the times of the unsuccessful
intracell handovers in the current cell. This item, together with Attempted intracell
handovers, Successful intracell handovers helps the user know the performance
of intracell handover in the current cell. Related items: Unsuccessful outgoing
internal inter cell handovers, Unsuccessful incoming internal inter cell handovers,
Unsuccessful outgoing interBSC inter cell handovers.
Note:
Below are the causes of unsuccessful intracell handover:
1) Previous channel becomes invalid or connection is terminated due to abnormality of radio resource or
terrestrial resource;
2) MS fails to access the target channel due to poor radio environment or incorrect handover parameter;
3) Handover is interrupted and original call is cleared because errors have been detected during BSS
FAILURE INDICATION during the procedure of intracell handover, as shown
in Figure 3-60 A1 and A2.
2) During the procedure of intracell handover, MS fails to access the target cell,
then returns to the source cell (current cell) and sends HANDOVER
FAILURE to source cell. This item is measured when the source cell receives
this message, and at the same time, a Clear For Handover Failure message
is sent to the target cell, as shown in Figure 3-60 A3.
3) During the procedure of intracell handover, the source cell (current cell)
in this case, as shown in Figure 3-60 A6 and A7.
HANDOVER DETECT, it will send Inter Clear Request to the source cell for
3-221
AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times
out. This item is measured when the source cell receives (current cell) this
message.
7) During the procedure of intracell handover, when the source cell (current cell)
waiting for Inter Clear Request times out, it sends Inter Clear Request to the
target cell. This item is measured in this case.
waiting for Intercell Handover Response times out again after resending
Intercell Handover Request due to timeout. This item is measured in this case,
and the related resources will be released at the same time.
z Formula: none.
MS BTS BSC MSC/VLR

CHANNEL ACT
CONN FAIL IND

ERROR IND A1
A4
CLEAR COMMAND
A6, E6
Old Channel HANDOVER COMMAND
ERROR IND
A5, G2
CONN FAIL IND
A2, G1 CLEAR COMMAND
HANDOVER FAILURE A7
Old Channel
A3, B1, C1, D1, E1, F1
HANDOVER COMPLETE
A1~A7: Unsuccessful intracell handovers

B1: Unsuccessful intracell handovers (channel invalid)
C1: Unsuccessful intracell handovers (TA invalid)
D1: Unsuccessful intracell handovers (timer expired)
E1: Unsuccessful intracell handovers (other causes)
F1: Unsuccessful intracell handovers with successful reversions
G1~G2: Unsuccessful intracell handovers with unsuccessful reversions
Figure 3-60 Unsuccessful intracell handovers
3-222
VII. Unsuccessful intracell handovers (channel mode unacceptable)
z Description: After intracell handover is initiated, the source cell sends a

resources. This marks a successful internal intracell handover. If MS fails to
access the target cell due to channel invalid (the mode or the type of the allocated
channel not in line with what MS requests for), then this intracell handover is a
failure. This item measures the times of unsuccessful intracell handovers due to
channel invalid in the current cell. Together with Unsuccessful intracell handovers,
this item shows the situation of unsuccessful intracell handover caused by channel
invalid in the current cell.
z Measurement point: During the procedure of internal intracell handover, MS fails
cell receives the HANDOVER FAILURE message (cause: Abnormal release,
channel unacceptable (0x02) or Channel mode unacceptable (0x09)) from MS.
z Formula: none.
VIII. Unsuccessful intracell handovers (frequency not implemented)

resources. This marks a successful internal intracell handover. If MS fails to
access the target cell due to frequency not implemented, then this intracell
handover is a failure. This item measures the times of unsuccessful intracell
handovers due to frequency not implemented in the current cell. Together with
Unsuccessful intracell handovers, this item shows the situation of unsuccessful
intracell handover caused by frequency not implemented in the current cell.
z Measurement point: During the procedure of internal intracell handover, MS fails
cell receives the HANDOVER FAILURE message (cause: Frequency not
implemented (0x0a)) from MS. This item is measured in this case, as shown in
Figure 3-60 C1.
z Formula: none.
IX. Unsuccessful intracell handovers (timer expired)

3-223
resources. This marks a successful internal intracell handover. If various timers

expired during the process, then this intracell handover is a failure. This item
measures the times of unsuccessful intracell handovers due to timer expired in the
current cell. Together with Unsuccessful intracell handovers, this item shows the
situation of unsuccessful intracell handover caused by timer expired.
1) During the procedure of intracell handover, MS fails to access the target cell
and returns to the source cell (current cell), and the source cell receives the
HANDOVER FAILURE message (cause: Abnormal release, timer expired
(0x03)) from MS. This item is measured in this case, as shown in Figure 3-60
D1.
the timer waiting for HANDOVER COMPLETE times out. This item is
waiting for Inter Clear Request times out. This item is measured in this case.
4) During the procedure of intracell handover, the source cell waiting for Intercell
Handover Response times out again after resending Intercell Handover
Request due to timeout. This item is measured in this case.
z Formula: none.
X. Unsuccessful intracell handovers (other causes)

resources. This marks a successful internal intracell handover. There are many
abnormalities during the process, such as abnormal channel preparation in the
target cell, abnormal at radio link, which caused this handover failure, are
considered as other causes. This item measures the times of unsuccessful
intracell handovers due to other causes in the current cell. Together with
Unsuccessful intracell handovers, this item shows the situation of unsuccessful
intracell handover caused by other causes.
1) During the procedure of intracell handover, MS fails to access the target cell
and returns to the source cell (current cell), and the source cell receives the
HANDOVER FAILURE message (cause: other causes, including Abnormal
release, unspecified (0x01), Preemptive release (0x05), Call already cleared
(0x41), Semantically incorrect message (0x5f), Invalid mandatory information
(0x60), Message type non-existent or not implemented (0x61), Message type
not compatible with protocol state (0x62), Conditional IE error (0x64), No cell
3-224
allocation available (0x65), Protocol error unspecified (0x6f), etc.) from MS.
This item is measured in this case, as shown in Figure 3-60 E1.
FAILURE INDICATION during the procedure of intracell handover.
in this case.
6) During the procedure of intracell handover, when AM/CM net-drive fails after
the target cell receives HANDOVER DETECT, the target cell sends Inter
Clear Request to the source cell. This item is measured when the source cell
(current cell) receives this message
z Formula: none.
XI. Unsuccessful intracell handovers with successful reversions
z Description: During the procedure of intracell handover, the source cell sends a
HANDOVER COMMAND message to MS. If the MS cannot access the target cell
due to poor radio environment or handover parameter incorrect, it will send a
HANDOVER FAILURE message (cause: Radio interface failure, reversion to old
channel) to the source cell via the previous channel. On reception of this message,
the source cell notifies the target cell to clear the resources related to this
handover. The connecting between the source cell and MS remains the same.
This item measures the times of unsuccessful intracell handover with successful
reversion in the current cell. Related items: Unsuccessful intracell handovers,
Unsuccessful intracell handovers with unsuccessful reversions, Unsuccessful
internal inter cell handovers with successful reversions, Unsuccessful outgoing
BSC handovers with successful reversion.
z Measurement point: This item is measured when the source cell (current cell)
reversion to old channel) from MS during the procedure of intracell handover, as
shown in Figure 3-60 F1.
z Formula: none.
3-225
XII. Unsuccessful intracell handovers with unsuccessful reversions
z Description: During the procedure of intracell handover, after the source BSC
sends a HANDOVER COMMAND message to MS, the connection between MS
and the source cell is terminated before the connection between MS and the target
cell due to poor radio environment or equipment failure. When BSC detects this
situation, it will send a CLEAR REQUEST message to MSC to request for clearing
the previous resources and the resources during handover. This handover is failed
and the original service cannot be restored. This item measures the times of
unsuccessful handover with unsuccessful reversion in the current cell. Related
items: Unsuccessful intracell handovers, Unsuccessful intracell handovers with
successful reversions, Unsuccessful internal inter cell handovers with
unsuccessful reversions, Unsuccessful outgoing BSC handovers with
unsuccessful reversion.
CONNECTION FAILURE INDICATION from BTS after sending the
HANDOVER COMMAND message to MS during the procedure of intracell
handover, as shown in Figure 3-60 G1.
measured in this case, as shown in Figure 3-60 G 2.
AM/CM net-drive fails or the timer waiting for HANDOVER COMPLETE times
out. This item is measured when the source cell (current cell) receives this
message.
4) This item is measured when the source cell (current cell) waiting for the Inter
Clear Request message (cause: handover success) times out after sending
the HANDOVER COMMAND message to MS during the procedure of
intracell handover.
z Formula: none.
XIII. Intracell handover success rate (%)
z Description: See Successful intracell handovers, Attempted intracell handovers.

z Formula: Successful intracell handovers / Attempted intracell handovers
3.9.6 Other Measurement Function
3-226
Table 3-14 Statistic items in other measurement function
No. Item name

1 Sum of TCH measurement reports in 1800 cell (excluding very early assignment)
2 Sum of TCH measurement reports in the cell (excluding very early assignment)
3 Sum of SDCCH measurement reports in the cell
4 Sum of configured TRX in the cell
5 Sum of available TRX in the cell
6 Sum of TCH measurement reports during very early assignment procedure in the cell
7 Sum of TCH measurement reports during very early assignment procedure in the 1800 cell
8 Unusable time of the cell (second)
9 Attempted handovers in the extended cell (minimum timing advance)
10 Attempted dual-band intercell handovers
11 Successful dual-band intercell handovers
12 Inter BSC incoming cell handovers
13 Inter BSC outgoing cell handovers
14 SDCCHs initially configured
15 Initially configured TCHs of 900 cell
16 Initially configured TCHs of 1800 cell
17 Initially configured dynamic PDCHs of 900 cell
18 Initially configured dynamic PDCHs of 1800 cell
19 Unsuccessful outgoing BSC handovers with successful reversion
20 Unsuccessful outgoing BSC handovers with unsuccessful reversion
21 Percentage of TRX in good condition (%)
22 Ratio of cell usability (%)
I. Sum of TCH measurement reports in 1800 cell (excluding very early

assignment)
z Description: MS shall report a MR to the network every 480ms after it seizes TCH.
This item reflects the number of original MRs received from MS on all the TCHs
(speech/data) of a 1800 cell in BSC, and is irrelated to the state of the MR
pre-processing switch. This item is used to calculate the traffic volume on TCH
which serves as a speech/data channel.
z Measurement point: This item shall be measured when BSC receives a MR which
is reported by BTS on TCH, and the TCH serves as a speech/data channel instead
of signaling channel.
z Formula: none.
II. Sum of TCH measurement reports in the cell (excluding very early
assignment)
(speech/data) of a cell (900 cell or 1800 cell) in BSC, and is irrelated to the state of
the MR pre-processing switch. This item is used to calculate the traffic volume on
TCH which serves as a speech/data channel.
is reported by BTS on TCH, and the TCH serves as a speech/data channel instead
of signaling channel.
3-227
z Formula: none.
III. Sum of SDCCH measurement reports in the cell
z Description: MS shall report a MR to the network every 470ms after it seizes

SDCCH. This item reflects the number of original MRs received from MS on all the
SDCCHs of a cell in BSC, and is irrelated to the state of the MR pre-processing
switch. This item is used to calculate the traffic volume on SDCCH.
z Measurement point: This item is measured when BSC receives a MR which is
reported by BTS on SDCCH.
z Formula: none.
IV. Sum of configured TRX in the cell
z Description: This item reflects the number of TRXs installed in a cell in BSC. If the
state of a cell is "Not installed", the measurement result of this item is "0".
z Measurement point: This item is measured at the end of a statistic cycle.
z Formula: none.
V. Sum of available TRX in the cell
z Description: This item reflects the number of available TRXs in a cell in BSC. Here,
"available" means that the state of TRX is "Enabled" and RSL state is "Normal".
z Measurement point: This item is measured at the end of a statistic cycle.
z Formula: none.
VI. Sum of TCH measurement reports during very early assignment procedure
in the cell
(signaling) of a cell (900 cell or 1800 cell) in BSC, and is irrelated to the state of the
MR pre-processing switch. This item is used to calculate the traffic volume on TCH
which serves as a signaling channel.
is reported by BTS on TCH, and the TCH serves as a signaling channel, instead of
speech/data channel.
z Formula: none.
VII. Sum of TCH measurement reports during very early assignment

procedure in the 1800 cell
(signaling) of a 1800 cell in BSC, and is irrelated to the state of the MR
pre-processing switch. This item is used to calculate the traffic volume on TCH
which serves as a signaling channel.
3-228
is reported by BTS on TCH, and the TCH serves as a signaling channel instead of
speech/data channel.
z Formula: none.
VIII. Unusable time of the cell (second)
z Description: Here, "unusable" means that the operational state of the current
primary BCCH of a cell is "Disabled", or the RSL of the TRX where the current
primary BCCH of a cell is located is broken down. So long as either of the two
conditions is satisfied, the cell shall be regarded as "unusable". This item reflects
the out-of-service duration of a cell resulted from various causes.
z Measurement point: The system checks cell state every 5s. This item is measured
when the system detects that a cell has exited "Service" state. There may exist a
+5s/-5s deviation.
z Formula: none.
IX. Attempted handovers in the extended cell (minimum timing advance)

handovers (intracell handovers) caused by minimum timing advance (occurs only
in single timeslot extended cells) in the current cell. This item shows the frequency
of handover caused by minimum timing advance in the current cell. Relate items:
Attempted intracell handovers.
z Measurement point: In single timeslot extended cells (current cell), handovers can
be triggered by TA being smaller than minimum timing advance. After handover
algorithm decision, the current cell sends Intercell Handover Request (internal
intracell handover). This item is measured in this case.
z Formula: none.
X. Attempted dual-band intercell handovers
z Description: Dual-band handover refers to the handover from GSM900 cell to

GSM1800 cell or from GSM 1800 cell to GSM 900 cell. The cell system type of the
source cell and the target cell should be the different. This type of handovers
includes intraBSC handover and interBSC handover. This item measures the
times of the current cell taking place dual-band intercell handovers. If the current
cell is a GSM 900 cell, the item measures the handovers which are from other
GSM 1800 cells to the current cell or from the current cell to other GSM1800 cells.
If the current cell is a GSM 1800 cell, the item measures the handovers which are
from other GSM900 cells to the current cell or from the current cell to other
GSM900 cells. This item shows the frequency of the dual-band intercell handovers
3-229
taking place in the current cell. Together with Successful dual-band intercell
handovers, this item shows the performance of this type of handover. Related
items:Attempted incoming internal inter cell handovers, Attempted incoming
interBSC inter cell handovers, Attempted outgoing internal inter cell handovers,
Note:
1) For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER
REQUIRED message to MSC, the source cell does not know the target cell until the reception of a
HANDOVER COMMAND message from MSC.
1 to 124.
from 512 to 885.
cell) sends an Intercell Handover Request message, and the cell system type
of the target cell and the source cell are different. This item is measured in
this case.
receives Intercell Handover Request, and the cell system type of the target
cell and the source cell are different. This item is measured in this case.
receives the HANDOVER COMMAND message from MSC, and the cell
system type of the target cell and the source cell are different. This item is
measured in this case, as shown in Figure 3-51 E1.
receives IntoBSC Handover Request, and the cell system type of the target
cell and the source cell are different. This item is measured in this case.
z Formula: none.
XI. Successful dual-band intercell handovers
z Description: Dual-band handover refers to the handover from GSM900 cell to

GSM1800 cell or from GSM 1800 cell to GSM 900 cell. The cell system type of the
source cell and the target cell should be different. This type of handovers includes
intraBSC handover and interBSC handover. This item shows the times of
successful dual-band intercell handovers taking place in the current cell. Together
with Attempted dual-band intercell handovers, this item shows the performance of
3-230
this type of handover. Related items: Successful incoming internal inter cell
handovers.
Note:
1) For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER
HANDOVER COMMAND message from MSC.
1 to 124.
from 512 to 885.
cell) receives Inter Clear Request (cause: internal intercell handover
succeeded) from the target cell. This item is measured in this case.
2) During the procedure of internal intercell handover (cause: directed retry),
after MS is successfully handed over to the target cell (current cell), the target
cell will send ASSIGNMENT COMPLETE to MSC. This item is measured
when the current cell sends this message, as shown in Figure 3-52 D1.
3) During the procedure of internal intercell handover (cause: not directed retry,
such as receiving strength, receiving quality, TA, traffic load, Response to
MSC invocation, directed retry, rapid rxlevel drop, better cell or O&M
intervention), after MS is successfully handed over to the target cell (current
cell), the target cell sends a HANDOVER PERFORMED message to MSC.
This item is measured in this case Figure 3-53 E1.
receives the CLEAR COMMAND message (cause: handover success) from
MSC. This item is measured in this case, as shown in Figure 3-55 D1.
receives HANDOVER COMPLETE from MS and sends it to MSC at the same
time. This item is measured in this case, as shown in Figure 3-54 B1.
z Formula: none.
XII. Inter BSC incoming cell handovers
z Description: After the target BSC receives the HANDOVER REQUEST message
from MSC, it checks the conditions of incoming handover. If the check passed, the
3-231
target BSC will request for channel resource, generate and store the HANDOVER
COMMAND message in buffer, and at the same time, it will send a CHANNEL
ACTIVATION to BTS message. After receiving the CHANNEL ACTIVATION
ACKNOWLEDGE message, BSC packs the HANDOVER COMMAND message
into the HANDOVER REQUEST ACKNOWLEDGE message, which will then be
sent to MSC. MSC transfers this message to the source BSC, and the source BSC
sends a HANDOVER COMMAND message to MS. This item measures the times
of the current cell as the target cell sending HANDOVER REQUEST
ACKNOWLEDGE to MSC. This item, together with Attempted incoming interBSC
inter cell handovers, helps the user know the situation of the unsuccessful
handovers due to abnormalities during the preparation of new channel in the
current cell, or with Successful incoming interBSC inter cell handovers to know the
situation of unsuccessful handovers due to radio interface abnormal in the current
cell. Related items: Inter BSC outgoing cell handovers, Incoming internal inter cell
handovers.
z Measurement point: During the procedure of interBSC handover, after the target
cell (current cell) receives the CHANNEL ACTIVATION ACKNOWLEDGE
message, it sends HANDOVER REQUEST ACKNOWLEDGE to MSC which
contains the HANDOVER COMMAND message to be sent to MS. This item is
z Formula: none.
MS BTS BSC MSC/VLR

CHANNEL ACT

A1
HANDOVER DETECTION
HANDOVER COMPLETE
HANDOVER COMPLETE
A1: Inter BSC incoming cell handovers

Figure 3-61 Inter BSC incoming cell handovers
XIII. Inter BSC outgoing cell handovers
allocating the new channel and generates the HANDOVER COMMAND message,
BSC sends it to MS. This item measures the times of the current cell as the source
cell sending the HANDOVER COMMAND message to MS. Together with
Attempted outgoing interBSC inter cell handovers, this item helps the user know
3-232
the situation of unsuccessful handovers due to abnormalities during the

preparation of new channel in the target cell, or with Successful outgoing interBSC
inter cell handovers to know the situation of unsuccessful handovers due to radio
interface abnormal in the target cell. Related items: Outgoing internal inter cell
handovers, Inter BSC incoming cell handovers.
receives the HANDOVER COMMAND message from MSC, as shown in
Figure 3-51 B1.
z Formula: none.
XIV. SDCCHs initially configured
z Description: This item reflects the number of SDCCHs of a cell in BSC at the start
time of a statistic cycle which are configured in the data configuration table. The
SDCCHs obtained by dynamic adjustment of TCHs are excluded.
z Measurement point: This item is measured at the start time of a statistic cycle.
z Formula: none.
XV. Initially configured TCHs of 900 cell
z Description: This items reflects the number of TCHs of a 900 cell in BSC at the
start time of a statistic cycle which are configured in the data configuration table,
including the TCHs which are dynamically converted into SDCCHs.
z Formula: none.
XVI. Initially configured TCHs of 1800 cell
z Description: This items reflects the number of TCHs of a 1800 cell in BSC at the
start time of a statistic cycle which are configured in the data configuration table,
including the TCHs which are dynamically converted into SDCCHs.
z Formula: none.
XVII. Initially configured dynamic PDCHs of 900 cell
z Description: This items reflects the number of dynamic PDCHs of a 900 cell in
BSC at the start time of a statistic cycle which are configured in the data
configuration table
z Formula: none.
XVIII. Initially configured dynamic PDCHs of 1800 cell
z Description: This items reflects the number of dynamic PDCHs of a 1800 cell in
BSC at the start time of a statistic cycle which are configured in the data
configuration table
3-233
z Formula: none.
XIX. Unsuccessful outgoing BSC handovers with successful reversion
z Description: During the procedure of interBSC handover, after the source cell
sends a HANDOVER COMMAND message to MS, if the MS cannot accessed the
send a HANDOVER FAILURE message (cause: Radio interface failure, reversion
to old channel) to the source BSC via the previous channel. The source BSC then
sends this message to MSC. MSC notifies the target BSC to clear the resources
related to this handover. The connecting between the source cell and MS remains
the same. This item measures the times of unsuccessful handover with successful
reversion when the current cell is the source cell. Related items: Unsuccessful
outgoing BSC handovers with unsuccessful reversion, Unsuccessful internal inter
cell handovers with successful reversions, Unsuccessful intracell handovers with
successful reversions.
reversion to old channel) from MS during the procedure of interBSC handover, as
shown in Figure 3-62 A1.
z Formula: none.
HANDOVER COMMAND HANDOVER COMMAND
A 1, C 1 H A N D O V E R F A IL U R E
C O N N F A IL IN D
E R R O R IN D IC A T IO N B1 , D1
B2 , D2
CLEAR C O M M AND
B3 , D3
CLEAR C O M M AND
C LEAR C O M PLETE

C1: Unsuccessful outgoing inter cell handovers with successful reversion
D1~D3: Unsuccessful outgoing inter cell handovers with unsuccessful reversion
3-234
XX. Unsuccessful outgoing BSC handovers with unsuccessful reversion
z Description: During the procedure of interBSC handover, after the source cell
sends a HANDOVER COMMAND message to MS, the connection between MS
and the source BSC is terminated before the connection between MS and the
target BSC set up due to poor radio environment or equipment failure. When BSC
detects this situation, it will send a CLEAR REQUEST message to MSC to request
for clearing the previous resources and the resources during handover. This
handover is failed and the original service cannot be restored. This item measures
the times of unsuccessful handover with unsuccessful reversion when the current
cell is the source cell. Related items: Unsuccessful outgoing BSC handovers with
successful reversion, Unsuccessful outgoing interBSC inter cell handovers,
Unsuccessful internal inter cell handovers with unsuccessful reversions,
Unsuccessful intracell handovers with unsuccessful reversions.
CONNECTION FAILURE INDICATION from BTS during the procedure of
interBSC handover, as shown in Figure 3-62 B1.
2) This item is measured when the source cell (current cell) receives the
ERROR INDICATION message (cause: timer T200 expired (N200 + 1) times
(0x01) or unsolicited DM response, multiple frame established state (0x05) or
sequence error (0x07)) from BTS during the procedure of interBSC handover,
3) This item is measured when the source cell (current cell) receives the CLEAR
COMMAND message (cause: not handover success) from MSC during the
procedure of interBSC handover, as shown in Figure 3-62 B3.
4) This item is measured when the source cell (current cell) waiting for the
CLEAR COMMAND message (cause: handover success) from MSC times
out during the procedure of interBSC handover.
z Formula: none.
XXI. Percentage of TRX in good condition (%)
z Description: This item reflects the percentage of available TRXs to configured

TRXs. See Sum of available TRX in the cell and Sum of configured TRX in the cell.
z Measurement point: Omitted.
z Formula: Sum of available TRX in the BSC / Sum of configured TRX in the BSC
XXII. Ratio of cell usability (%)
z Description: This item reflects the percentage of unusable time of the cell to the
statistic cycle. See Unusable time of the cell (second)
z Measurement point: Omitted.
z Formula: 1-unusable time of the cell (s) / Statistic cycle (s).
3-235
3.10 Power Control Measurement
3.10.1 General
Power control is the process of changing the transmission power of BTS and MS during
a conversation. The purpose of power control is to improve conversation quality, and at
the same time keep the signal level to remain at a certain range. The elements that
trigger power control are the receiving level and receiving strength in MR.
Power control measurement is for the statistics of parameters related to the

transmitting power and receiving level, including times of BSC sending power control
commands to BTS and MS, the average transmitting power level of BTS and MS.
When power control is registered, it is possible to analyze "Average downlink strength"

to know the coverage quality and power control effect, or to analyze "Power control
messages to MS for power increasing" to get the information of the frequency of power
control implementation in a cell.
The object of power control measurement is the cell. The module No. and cell No. (or
all cells in a module) can be configured in the interface of Object Definition. This
measurement indices in this part is listed in Table 3-15.
Table 3-15 Power control measurement items
No. Item name

1 Power control messages to MS for power increasing
2 Power control messages to MS for power decreasing
3 Power control messages to BTS for power increasing
4 Power control messages to BTS for power decreasing
5 Average MS power level
6 Average BTS power level
7 Average downlink strength
8 Average uplink strength
9 Average downlink quality
10 Average uplink quality
11 Maximum downlink power duration percentage
12 Maximum uplink power duration percentage
13 Average distance between MS and BTS
14 Maximum distance between MS and BTS
15 Sum of measurement reports in a cell
I. Power control messages to MS for power increasing
z Description: After receiving MR, BSC compares the uplink receiving level and
uplink receiving strength in MR with the configured uplink receiving level threshold
and uplink receiving strength threshold according to the power control algorithm. If
3-236
the result suggests that the MS needs to increase transmitting power, the
corresponding message will be sent to MS. Whenever this happens, this index will
increase by 1.
z Measurement point: Measured when BSC sends the power increasing message
to MS.
z Formula: none.
II. Power control messages to MS for power decreasing
the result suggests that the MS needs to lower transmitting power, the
corresponding message will be sent to MS. Whenever this happens, this index will
increase by 1.
z Measurement point: Measured when BSC sends the power decreasing message
to MS.
z Formula: none.
III. Power control messages to BTS for power increasing
z Description: After receiving MR, BSC compares the downlink receiving level and
downlink receiving strength in MR with the configured downlink receiving level
threshold and downlink receiving strength threshold according to the power
control algorithm. If the result suggests that the BTS needs to increase
transmitting power, the corresponding message will be sent to BTS. Whenever
this happens, this index will increase by 1.
z Measurement point: Measured when BSC sends the power increasing message
to BTS.
z Formula: none.
IV. Power control messages to BTS for power decreasing
the result suggests that the BTS needs to lower transmitting power, the
corresponding message will be sent to BTS. Whenever this happens, this index
will increase by 1.
z Measurement point: Measured when BSC sends the power decreasing message
to BTS.
z Formula: none.
3-237
V. Average MS power level
z Description: This index reflects the average transmitting power of the MSs in the
cell. After receiving MR, BSC will add the transmitting power level value of MS in
MR to the sum. The value of this index is generated by dividing the sum with the
total times of receiving MR. The lower MS average power level suggests the
higher MS transmitting power.
z Measurement point: Measured when BSC receives MR.
z Formula: none.
VI. Average BTS power level
z Description: This index reflects the average transmitting power of the BTSs in the
cell. After receiving MR, BSC will add the transmitting power level value of BTS in
MR to the sum. The value of this index is generated by dividing the sum within the
measurement cycle with the total times of receiving MR. The lower BTS average
power level suggests the higher BTS transmitting power.
z Formula: none.
VII. Average downlink strength
z Description: This index reflects the average downlink receiving level in this cell.
After receiving MR, BSC will add the downlink receiving level values to the sum.
The value of this index is generated by dividing the sum within the measurement
cycle with the total times of receiving MR.
z Formula: none.
VIII. Average uplink strength
z Description: This index reflects the average uplink receiving level in this cell. After
receiving MR, BSC will add the downlink receiving level values to the sum. The
value of this index is generated by dividing the sum within the measurement cycle
with the total times of receiving MR.
z Formula: none.
IX. Average downlink quality
z Description: This index reflects the average downlink receiving quality in the cell.
After receiving MR, BSC will add the downlink receiving quality level values to the
sum. The value of this index is generated by dividing the sum within the
measurement cycle with the total times of receiving MR. There are 8 quality levels:
0~7. The lower average downlink signal quality suggests the better quality.
z Formula: none.
3-238
X. Average uplink quality
z Description: This index reflects the average uplink receiving quality in the cell.
After receiving MR, BSC will add the uplink receiving quality level values to the
sum. The value of this index is generated by dividing the sum within the
measurement cycle with the total times of receiving MR. There are 8 quality levels:
0~7. The lower average uplink signal quality suggests the better quality.
z Formula: none.
XI. Maximum downlink power duration percentage
z Description: This index reflects the percentage of time BTS spent in maximum
power transmission in the cell. After BSC receiving MR, the times of downlink
power being the maximum value will increase by 1 if the downlink transmitting
power level value is 0 in MR. The value of this index is generated by dividing the
times of the downlink power being the maximum value with the total times of
receiving MR, and then multiplying quotient with 100. If the time for downlink
power being the maximum value is too long, then there may be areas with poor
coverage or unreasonably configured power control parameter.
z Measurement point: Measured when BSC receives the MR in which the downlink
transmitting power level value is 0.
z Formula: none.
XII. Maximum uplink power duration percentage
z Description: This index reflects the percentage of time MS spent in maximum

power transmission in the cell. After BSC receiving MR, the times of uplink power
being the maximum value will increase by 1 if the uplink transmitting power level
value is smaller than "MS Max Radio Power Control Level" in system information
in MR. Normally the lower power level value suggests the higher MS transmitting
power. The value of this index is generated by dividing the times of the uplink
power being the maximum value with the total times of receiving MR, and then
multiplying quotient with 100. If the time for uplink power being the maximum value
is too long, then there may be too low receiving level or unreasonably configured
power control parameter.
z Measurement point: Measured when BSC receives the MR in which the uplink
transmitting power level value is smaller or equal to "MS Max Radio Power Control
Level" in system message.
z Formula: none.
XIII. Average distance between MS and BTS
z Description: This index reflects the average distance between MSs and BTS in the
cell. The average distance between MSs and BTS is indicated with TA (a unit of
TA value equal to about 550 meters). After receiving MR, BSC will add the TA
3-239
value in MR to the sum. The value of this index is generated by dividing the sum
within the measurement cycle with the total times of receiving MR. Normally, the
larger distance between MS and BTS will cause larger TA value.
z Formula: none.
XIV. Maximum distance between MS and BTS
z Description: This index reflects the maximum distance between MSs and BTS in
the cell. The maximum distance between MSs and BTS is indicated with TA (a unit
of TA value equal to about 550 meters). After receiving MR, BSC will compare the
current TA value in MR with the previous one. The larger one is recorded. The
value of this index is largest TA within the measurement cycle with the total times
of receiving MR. Normally, the larger distance between MS and BTS will cause
larger TA value.
z Measurement point: Measured when BSC receives MR in which the TA is larger
than the previous one.
z Formula: none.
XV. Sum of measurement reports in a cell
z Description: This index reflects the total times of sending cell measurement
reports. When BSC receives MR, this index increases by 1.
z Formula: none.
3.11 Call Drop Measurement
3.11.1 General
Call drop measurement measures the average level, strength and TA when call drop
occurs.
The result of call drop measurement can be analyzed to get the reason of call drop. For
example, if the measurement item "Average timing advance at TCH call drop" is
registered, the TA value when call drop after seizing TCH will be measured. If the
measured value is high, then the cause of call drop is that the TA value is too high. The
further cause may be that the subscriber is too far away from BTS or the configurations
of the adjacent cells are improper. Here is another example. The measured value of
"Average uplink level at TCH call drop" is high, so is that of "Average uplink strength at
TCH call drop". This means that the uplink receiving level is high enough while the
strength of TCH is poor. The cause of call drop may be the interference on uplink.
3-240
The object of call drop measurement task is cell. In the interface of Object Definition, it
is possible to configure the module No. and cell No. of the task or all cells in the module
setting range.
This part includes all items, as shown in Table 3-16.
Table 3-16 Call drop measurement indices
No. Item name

1 Average uplink level at SDCCH call drop
2 Average downlink level at SDCCH call drop
3 Average uplink strength at SDCCH call drop
4 Average downlink strength at SDCCH call drop
5 Average timing advance at SDCCH call drop
6 Average uplink level at TCH call drop
7 Average downlink level at TCH call drop
8 Average uplink strength at TCH call drop
9 Average downlink strength at TCH call drop
10 Average timing advance at TCH call drop
I. Average uplink level at SDCCH call drop
z Description: When seizing SDCCH, MS reports an MR every 470 ms to the

network. This index shows the uplink level in MR when call drop occurs on
SDCCH. When a call drop occurs on SDCCH, the uplink level on the last effective
MR is added. This value is generated by dividing the sum of the entire period with
the total times of call drops on all SDCCH in a cell.
z Measurement point: Measured when call drop occurs on SDCCH.
z Formula: none.
II. Average downlink level at SDCCH call drop

network. This index shows the downlink level in MR when call drop occurs on
SDCCH. When a call drop occurs on SDCCH, the downlink level on the last
effective MR is added. This value is generated by dividing the sum of the entire
period with the total times of call drops on all SDCCH in a cell.
z Formula: none.
III. Average uplink strength at SDCCH call drop

network. This index shows the uplink strength in MR when call drop occurs on
SDCCH. When a call drop occurs on SDCCH, the uplink strength value on the last
effective MR is added. This value is generated by dividing the sum of the entire
3-241
period with the total times of call drops on all SDCCH in a cell. This value is
generated by dividing the sum of the entire period with the total times of call drops
on all SDCCH in a cell.
z Formula: none.
IV. Average downlink strength at SDCCH call drop

network. This index shows the downlink strength in MR when call drop occurs on
SDCCH. When a call drop occurs on SDCCH, the downlink strength value on the
last effective MR is added. This value is generated by dividing the sum of the
entire period with the total times of call drops on all SDCCH in a cell.
z Formula: none.
V. Average timing advance at SDCCH call drop

network. This index shows the TA value in MR when call drop occurs on SDCCH.
When a call drop occurs on SDCCH, the TA value on the last effective MR is
added. This value is generated by dividing the sum of the entire period with the
total times of call drops on all SDCCH in a cell.
z Formula: none.
VI. Average uplink level at TCH call drop
z Description: When seizing TCH, MS reports an MR every 480 ms to the network.

This index shows the uplink level in MR when call drop occurs on TCH. When a
call drop occurs on TCH, the uplink level on the last effective MR is added. This
value is generated by dividing the sum of the entire period with the total times of
call drops on all TCH in a cell.
z Measurement point: Measured when call drop occurs on TCH.
z Formula: none.
VII. Average downlink level at TCH call drop

This index shows the downlink level in MR when call drop occurs on TCH. When a
call drop occurs on TCH, the downlink level on the last effective MR is added. This
value is generated by dividing the sum of the entire period with the total times of
call drops on all TCH in a cell.
z Formula: none.
3-242
VIII. Average uplink strength at TCH call drop

This index shows the uplink strength in MR when call drop occurs on TCH. When a
call drop occurs on TCH, the uplink strength value on the last effective MR is
added. This value is generated by dividing the sum of the entire period with the
total times of call drops on all SDCCH in a cell. This value is generated by dividing
the sum of the entire period with the total times of call drops on all TCH in a cell.
z Formula: none.
IX. Average downlink strength at TCH call drop

This index shows the downlink strength in MR when call drop occurs on TCH.
When a call drop occurs on TCH, the downlink strength value on the last effective
MR is added. This value is generated by dividing the sum of the entire period with
the total times of call drops on all TCH in a cell.
z Formula: none.
X. Average timing advance at TCH call drop

This index shows the TA value in MR when call drop occurs on TCH. When a call
drop occurs on TCH, the TA value on the last effective MR is added. This value is
generated by dividing the sum of the entire period with the total times of call drops
on all TCH in a cell.
z Formula: none.
3.12 SITE Initial Measurement Function
3.12.1 General
The traffic statistic items in "SITE Initial Measurement Function" are used to measure
the initialization status of a BTS. See Table 3-17 for the list of all the relevant statistic
items.
No. Item name

1 Sum of site initializations
2 Successful site initializations(kickoff)
3 Successful site initializations(reset)
4 Unsuccessful site initializations(kickoff)
5 Unsuccessful site initializations(reset)
3-243
The measurement object of each traffic statistic item in "SITE Initial Measurement
Function" is BTS, and the statistic result is number of BTS initializations, number of
successful initializations, number of unsuccessful initializations, etc. respectively.
Because the statistics are made without distinguishing the causes for BTS initialization,
initialization success or failure, the statistic results can only reflect the site initialization
status in a statistic period on the whole, and are of no significance for analyzing the
success or failure of a specific initialization. When analyzing the specific causes, the
user can make use of the alarm progress interface and BTS reset progress interface.
For example, by viewing the [Site Initialization] interface in Figure 3-63, the user can
learn that the site initialization failure is caused by erroneous data configuration.
Figure 3-63 Site initialization
I. Sum of site initializations
z Description: This item is used to calculate the number of initializations of a BTS

within a statistic period. It does not differentiate initialization causes. So long as a
BTS is initialized, the number of site initializations will be incremented by 1. The
causes that can lead to BTS initialization include level-3 or level-4 reset initiated by
BTS Maintenance System, BTS reset initiated by BSC after BTS reports an
erroneous state change report, scheduled initialization performed after BTS
initialization fails, initialization caused by dynamic data configuration (including
dynamic addition of BTS, modification of channel type in a BTS of chain
connection, TRX addition, cell addition, modification of the relevant property of a
2-TS extended cell, etc.), initialization requested by BTS.
z Measurement point: The number of successful site initializations will be
incremented by 1 when a site is successfully initialized.
3-244
z Formula: none.
II. Successful site initializations(kickoff)
z Description: Site kickoff initialization refers to BTS initialization that is led to by

causes other than level-3 or level-4 reset initiated by BTS Maintenance System,
and BTS reset initiated by BSC after BTS reports an erroneous state change
report. For example, scheduled initialization performed after BTS initialization fails,
initialization caused by dynamic data configuration (including dynamic addition of
BTS, modification of channel type in a BTS of chain connection, TRX addition, cell
addition, modification of the relevant property of a 2-TS extended cell, etc.),
initialization requested by BTS. This statistic item is used to calculate the number
of successful BTS kickoff initializations within a statistic period.
z Measurement point: The number of successful site kickoff initializations will be
incremented by 1 when a BTS kickoff initialization is successfully completed and
BSC receives a state change report from BTS.
z Formula: none.
III. Successful site initializations(reset)
z Description: This item is used to calculate the number of all successful site
initializations except successful site kickoff initializations. The causes for site
non-kickoff initialization include level-3 and level-4 reset initiated by BTS
Maintenance System, and BTS reset initiated by BSC after BTS reports an
erroneous state report.
z Measurement point: The number of successful site initializations will be
incremented by 1 when a site non-kickoff initialization is successfully completed
and BSC receives a state change report from BTS.
z Formula: none.
IV. Unsuccessful site initializations(kickoff)
z Description: This item is used to calculate the number of unsuccessful site kickoff
initializations. The following causes can lead to site kickoff initialization failure.
1) BSC cannot receive a response within the specified time after it sends an
initialization message to BTS.
2) During the course of initialization, BSC detects an error such as data
configuration error.
3) After BSC sends initialization messages to BTS for three successive times,
BTS still returns an erroneous response.
1) When site kickoff initialization fails.
2) When site kickoff initialization is initiated again after the previous site kickoff
initialization fails.
3) When flow control is performed during the course of site kickoff initialization.
3-245
z Formula: none.
V. Unsuccessful site initializations(reset)
z Description: This item is used to calculate the number of unsuccessful site

initializations except unsuccessful site kickoff initializations. The following causes
can lead to site initialization failure.
1) BSC cannot receive a response within the specified time after it sends an
3) After BSC sends initialization messages to BTS for three successive times,
BTS still returns an erroneous response.
1) When site initialization fails.
2) When site initialization is initiated again after the previous site initialization
fails.
3) When flow control is performed during the course of site initialization.
z Formula: none.
3.13 BTS Initial Measurement Function
3.13.1 General
The traffic statistic items in "BTS Initial Measurement Function" are used to measure
the initialization status of a cell. See Table 3-18 for the list of all the relevant statistic
items.
Table 3-18 Statistic items in BTS Initial Measurement Function
No. Item name

1 Sum of cell initializations
2 Successful cell initializations(kickoff)
3 Successful cell initializations(reset)
4 Unsuccessful cell initializations(kickoff)
5 Unsuccessful cell initializations(reset)
The measurement object of each traffic statistic item in "BTS Initial Measurement
Function" is cell, and the statistic result is number of cell initializations, number of
successful initializations, number of unsuccessful initializations, etc. respectively.
Because the statistics are made without distinguishing the causes for cell initialization,
initialization success or failure, the statistic results can only reflect the cell initialization
status in a statistic period on the whole, and are of no significance for analyzing the
success or failure of a specific initialization. When analyzing the specific causes, the
3-246
user can make use of the alarm progress interface and initialization progress interface.
For example, by viewing the [Site Initialization] interface in Figure 3-64, the user can
learn that the cell initialization failure is caused by erroneous cell extended property
configuration.
Figure 3-64 Cell initialization failure
I. Sum of cell initializations
z Description: This item is used to calculate the number of initializations of a cell

within a statistic period. It does not differentiate initialization causes. So long as a
cell configuration message is delivered to BTS, the number of cell initializations
will be incremented by 1. The causes that can lead to cell initialization include BTS
initialization, cell initialization caused by dynamic data configuration (including
dynamic addition of a cell, dynamic addition/deletion of TRX in a baseband FH cell,
dynamic modification of the frequencies of the TRX where BCCH is located,
modification of the frequencies of the TRX that participates in baseband FH,
modification of cell FH data, etc.), TRX mutual aid or TRX switchback occurred in
a baseband FH cell, and scheduled cell initialization initiated again after the
previous cell initialization fails.
z Measurement point: The number of cell initializations will be incremented by 1
when a cell configuration message is delivered to BTS.
z Formula: none.
3-247
II. Successful cell initializations(kickoff)
z Description: Cell kickoff initialization refers to the cell initialization that is led to by
causes other than level-3 or level-4 reset of BTS initiated by BTS Maintenance
System, and BTS reset initiated by BSC after BTS reports an erroneous state
change report, For example, cell initialization caused by dynamic data
configuration (including dynamic addition of a cell, dynamic addition/deletion of
TRX in a baseband FH cell, dynamic modification of the frequencies of the TRX
where BCCH is located, modification of the frequencies of the TRX that
participates in baseband FH, modification of cell FH data, etc.), TRX mutual aid or
TRX switchback occurred in a baseband FH cell, scheduled cell initialization
initiated again after the previous cell initialization fails, etc. This item is used to
calculate the number of successful cell kickoff initializations within a statistic
period.
z Measurement point: The number of successful cell kickoff initializations will be
incremented by 1 when a cell kickoff initialization is completed, and a report is
received indicating that the management state of the cell has changed.
z Formula: none.
III. Successful cell initializations(reset)
z Description: This item is used to calculate the number of successful cell

initializations (reset), The causes that can lead to this kind of cell initialization
include level-3 or level-4 reset of BTS initiated by BTS Maintenance System, and
BTS reset initiated by BSC after BTS reports an erroneous state change report.
z Measurement point: The number of successful cell initializations (reset) will be
incremented by 1 when a cell initialization is completed, and a report is received
indicating that the management state of the cell has changed.
z Formula: none.
IV. Unsuccessful cell initializations(kickoff)
z Description: This item is used to calculate the number of unsuccessful cell kickoff
initializations. The following causes can lead to cell initialization failure.
1) BSC cannot receive a response within the specified time after it sends a cell
3) After BSC sends cell initialization messages to BTS for three successive
times, BTS still returns an erroneous response.
1) When cell kickoff initialization fails.
2) When cell kickoff initialization is initiated again after the previous cell kickoff
initialization fails.
3) When flow control is performed during the course of cell initialization.
3-248
z Formula: none.
V. Unsuccessful cell initializations(reset)
z Description: This item is used to calculate the number of unsuccessful cell

initializations except unsuccessful cell kickoff initializations. The following causes
can lead to cell initialization failure.
1) BSC cannot receive a response within the specified time after it sends a cell
3) After BSC sends cell initialization messages to BTS for three successive
times, BTS still returns an erroneous response.
1) When cell initialization fails.
2) When cell initialization is initiated again after the previous cell initialization
fails.
3) When flow control is performed during the course of cell initialization.
z Formula: none.
3.14 Cell Broadcast Statistic
3.14.1 General
The items of Cell Broadcast Statistic are used to measure the times of CB messages
and the load of CBCH in one or multiple cells under a specified module. Table 3-19 lists
all items in Cell Broadcast Statistic.
Table 3-19 Statistic items in Cell broadcast statistic
No. Item name

1 CBS messages (O)
2 Percentage of CBCH load (%)
To know the operation of the cell broadcast of the entire BSC, it is necessary to register
the relative items in BSC Cell Broadcast Measurement Function.
The object of Cell Broadcast Statistic is cell which can be one or multiple cells under the
specified BM. The recommended measurement cycle is 60 minutes.
3-249
I. CBS messages (O)
z Description: BSC transfers CBS information to each appropriate BTS via the SMS
BROADCAST COMMAND message, indicating the channel which shall be used.
In DRX mode, the broadcast short messages also include the schedule messages
and null messages.
sends SMS BROADCAST COMMAND
z Formula: none.
BSC BTS
SMS BROADCAST COMMAND
A
A: CBS messages (O)

Figure 3-65 Times of sending SMS broadcast
II. Percentage of CBCH load (%)
z Description: The percentage of the current length of queue for CB message

transmission accounting the total capacity of the buffer for cell transmission.
z Measurement point: Length of the CB message transmission queue of BSC
sampling cell every five minutes.
z Formula: Length of the CB message transmission queue / total capacity of the
buffer for cell transmission
3.15 Outgoing Inter Cell Handover Measurement Function
3.15.1 General
The statistic items in Outgoing Inter Cell Handover Measurement Function are used to
know the performance of the handover between the specified cell and its adjacent cells.
They are mainly divided into attempted handover, successful handovers, and
unsuccessful handovers, where attempted handover and successful handovers are
measured according to different handover causes respectively, reflecting the handover
performance from the specified cell to its adjacent cells in detail. All statistic items of
Outgoing Inter Cell Handover Measurement Function are listed in Table 3-20.
3-250
To know the incoming inter cell handover performance of the specified cell, the related
statistic items of Incoming Inter Cell Handover Measurement Function should be
registered.
For the statistic items of Outgoing Inter Cell Handover Measurement Function, it is
recommended that they should be registered at the early stage of BSC running, or be
registered when the handover performance of the specified cell is to be known so that
the network optimization can be performed. At the stable running stage of BSC, the
task of these statistic items can be deleted. These items together with the statistic items
of Incoming Inter Cell Handover Measurement Function can be used to know the
handover situation between two specified cells. The statistic cycle is recommended to
be 60 minutes.
The statistic object of the statistic items of Outgoing Inter Cell Handover Measurement
Function is two cells: the source cell and its adjacent cell. While registering, the way of
setting the adjacent cell can either be set to all adjacent cells of the source cell, or can
be specified by CGI. All statistic items of Outgoing Inter Cell Handover Measurement
Function will be selected together for registration.
The description, measurement point, and measurement formula for each statistic item
are described as follows:
The description is to brief the procedure to trigger the statistic item, the cause to trigger
the statistic item, the feature of the traffic indicated by the statistic item, and the
handling of the abnormal situations.
Measurement point gives all causes to trigger the statistic item.
Table 3-20 Statistic items in Outgoing Inter Cell Handover Measurement Function
No. Item name

1 Attempted outgoing inter cell handovers
2 Attempted outgoing inter cell handovers for uplink quality
3 Attempted outgoing inter cell handovers for downlink quality
4 Attempted outgoing inter cell handovers for uplink strength
5 Attempted outgoing inter cell handovers for downlink strength
6 Attempted outgoing inter cell handovers for timing advance
7 Attempted outgoing inter cell handovers for traffic load
8 Attempted outgoing inter cell handovers for response to MSC
9 Attempted outgoing inter cell handovers for O&M intervention
10 Attempted outgoing inter cell handovers for better cell
11 Attempted outgoing inter cell handovers for rapid level drop
12 Attempted outgoing inter cell handovers for directed retry
13 Attempted outgoing inter cell handovers for other causes
14 Attempted extended inter cell outgoing cell handovers for minimum timing advance
15 Successful outgoing inter cell handovers
16 Successful outgoing inter cell handovers for uplink quality
17 Successful outgoing inter cell handovers for downlink quality
18 Successful outgoing inter cell handovers for uplink strength
19 Successful outgoing inter cell handovers for downlink strength
20 Successful outgoing inter cell handovers for timing advance
21 Successful outgoing inter cell handovers for traffic load
3-251
22 Successful outgoing inter cell handovers for response to MSC

23 Successful outgoing inter cell handovers for O&M intervention
24 Successful outgoing inter cell handovers for better cell
25 Successful outgoing inter cell handovers for rapid level drop
26 Successful outgoing inter cell handovers for directed retry
27 Successful outgoing inter cell handovers for other causes
28 Successful outgoing inter cell handovers in the extended cell (minimum timing advance)
29 Unsuccessful outgoing cell handover with successful reversion
30 Unsuccessful outgoing cell handover with unsuccessful reversion
31 Outgoing inter cell handover success rate (%)
I. Attempted outgoing inter cell handovers
z Description: the attempted handovers that the current cell (source cell) initiates to
the specified target cell. If the target cell and the current cell are in different BSCs,
the handover is interBSC handover; otherwise the handover is internal intercell
handover. This item is used to indicate the frequency of the handover from the
current cell to the specified target cell. This item together with Successful outgoing
inter cell handovers can be used to know the performance of such handover from
the current cell to the specified target cell. See Attempted outgoing internal inter
cell handovers and Attempted outgoing interBSC inter cell handovers.
Note:
For outgoing interBSC inter cell handover, after initiating a handover by sending a HANDOVER
HANDOVER COMMAND message from MSC. Therefore, the source cell measures the number of
attempted handovers by measuring the number of outgoing interBSC inter cell handover, i.e., accumulates
the number of attempted handovers on reception of a HANDOVER COMMAND message.
1) In internal intercell handover procedure, the target cell is the registered
adjacent cell. This item is measured when the source cell (the current cell)
sends an Intercell Handover Request message to the specified target cell
after the handover algorithm decision.
2) In interBSC handover procedure, the target cell is the registered adjacent cell.
This item is measured when the source cell (the current cell) receives the
HANDOVER COMMAND message from MSC, as shown in Figure 3-66 F1.
z Formula: none
3-252
MS BSC1 M S C /V L R BSC2 MS
A1 HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COM M AND

B 1 , C 1, D 1, E 1, F 1
HANDOVER COM M AND
HANDOVER ACCESS
HANDOVER DETECT
H A N D O V E R C O M P LE T E
H A N D O V E R C O M P LE T E
C LE A R C O M M A N D
C LE A R C O M P LE T E
A1: Attempted outgoing interBSC inter cell handovers

B1: Inter BSC outgoing cell handovers
C1: Outgoing interbsc inter cell handovers (to 900)
D1: Outgoing interbsc inter cell handovers (to 1800)
E1: Attempted dual-band intercell handovers
F1: Attempted outgoing inter cell handovers (including various handover causes)
Figure 3-66 Attempted outgoing interBSC inter cell handovers
II. Attempted outgoing inter cell handovers for uplink quality
z Description: when BSC initiates a handover, it will receive Handover Indication

message containing "handover cause" from LAPD module. The attempted
handovers are measured according to the different handover causes in this
message. This item measures the attempted handovers (internal intercell
handover or interBSC handover, determined by the source cell and the target cell)
that the current cell initiates to the specified target cell due to uplink quality. This
item is used to indicate the frequency that the current cell initiates the handovers
to the specified target cell due to uplink quality. This item together with Successful
outgoing inter cell handovers for uplink quality can be used to know the
performance of such handover from the current cell to the specified target cell.
See Attempted outgoing inter cell handovers.
Note:
attempted handovers by measuring the number of outgoing interBSC inter cell handover, i.e, accumulates
3-253
due to the uplink quality after the handover algorithm decision.
2) In inter BSC handover procedure, the target cell is the registered adjacent
cell. In the case the source cell initiates handover due to the uplink quality,
this item is measured when the source cell (the current cell) receives the
z Formula: none
III. Attempted outgoing inter cell handovers for downlink quality

message. This item is used to measure the attempted handovers (internal intercell
handover or inter BSC handover, determined by the source cell and target cell)
that the current cell initiates to the specified target cell due to down quality. This
to the specified target cell due to downlink quality. This item together with
Successful outgoing inter cell handovers for downlink quality can be used to know
the performance of such handover from the current cell to the specified target cell
can be known. See Attempted outgoing inter cell handovers.
Note:
due to downlink quality after the handover algorithm decision.
cell. In the case the source cell initiates handover due to downlink quality,
3-254
z Formula: none
IV. Attempted outgoing inter cell handovers for uplink strength

that the current cell initiates to the specified target cell due to uplink strength. This
to the specified target cell due to uplink strength. This item together with
Successful outgoing inter cell handovers for uplink strength can be used to know
can be known. SeeAttempted outgoing inter cell handovers.
Note:
due to the uplink strength after the handover algorithm decision.
cell. In the case the source cell initiates handover due to the uplink strength,
z Formula: none
V. Attempted outgoing inter cell handovers for downlink strength

that the current cell initiates to the specified target cell due to downlink strength.
3-255
This item is used to indicate the frequency that the current cell initiates the
handovers to the specified target cell due to downlink strength. This item together
with Successful outgoing inter cell handovers for downlink strength can be used to
know the performance of such handover from the current cell to the specified
target cell can be known. See Attempted outgoing inter cell handovers.
Note:
due to the downlink strength after the handover algorithm decision.
cell. In the case the source cell initiates handover due to the downlink
strength, This item is measured when the source cell (the current cell)
Figure 3-66 F1.
z Formula: none
VI. Attempted outgoing inter cell handovers for timing advance

that the current cell initiates to the specified target cell due to TA (during the
conversation, the subscriber is far from the serving cell but near to the target cell.
This leads to the drop of signal strength and signal quality in serving cell, and a
handover will be triggered.). This item is used to indicate the frequency that the
current cell initiates the handovers to the specified target cell due to TA. This item
together with Successful outgoing inter cell handovers for timing advance can be
used to know the performance of such handover from the current cell to the
specified target cell can be known. See Attempted outgoing inter cell handovers.
3-256
Note:
due to TA after the handover algorithm decision.
cell. In the case the source cell initiates handover due to TA, This item is
measured when the source cell (the current cell) receives the HANDOVER
COMMAND message from MSC, as shown in Figure 3-66 F1.
z Formula: none
VII. Attempted outgoing inter cell handovers for traffic load

that the current cell initiates to the specified target cell due to traffic load. This item
is used to indicate the frequency that the current cell initiates the handovers to the
specified target cell due to traffic load. This item together with Successful outgoing
inter cell handovers for traffic load can be used to know the performance of such
handover from the current cell to the specified target cell can be known. See
Attempted outgoing inter cell handovers.
Note:
3-257
due to traffic load after the handover algorithm decision.
cell. In the case the source cell initiates handover due to traffic load, This item
is measured when the source cell (the current cell) receives the HANDOVER
COMMAND message from MSC, as shown in Figure 3-66 F1.
z Formula: none
VIII. Attempted outgoing inter cell handovers for response to MSC

that the source cell initiates to the target cell for Response to MSC invocation
(MSC sends a HANDOVER CANDIDATE EQUIRY message to BSC which
causes handovers of multiple MSs in a cell.). This item is used to indicate the
frequency that the current cell initiates the handovers to the specified target cell for
response to MSC. This item together with Successful outgoing inter cell
handovers for response to MSC can be used to know the performance of such
Note:
sends an Intercell Handover Request message to the target cell for response
to MSC after the handover algorithm decision.
cell. In the case the source cell initiates handover for response to MSC, This
3-258
item is measured when the source cell (the current cell) receives the
z Formula: none
IX. Attempted outgoing inter cell handovers for O&M intervention

that the current cell initiates to the specified target cell due to O&M intervention
(the handover is due to the operation on O&M console, such as forced handover,
blocking without call drop (blocking channels, TRXs, and cells, etc.; or BCCH/TRX
mutual assistance). This item is used to indicate the frequency that the current cell
initiates the handovers to the specified target cell due to O&M intervention. This
item together with Successful outgoing inter cell handovers for O&M intervention
can be used to know the performance of such handover from the current cell to the
Note:
due to O&M intervention after the handover algorithm decision.
cell. In the case the source cell initiates handover due to O&M intervention,
z Formula: none
X. Attempted outgoing inter cell handovers for better cell

3-259

that the current cell initiates to the specified target cell due to "better cell" (the
adjacent cell with lower path loss (PBGT) or higher priority). This item is used to
indicate the frequency that the current cell initiates the handovers to the specified
target cell due to "better cell". This item together with Successful outgoing inter cell
handovers for better cell can be used to know the performance of such handover
from the current cell to the specified target cell can be known. See Attempted
outgoing inter cell handovers.
Note:
due to "better cell" after the handover algorithm decision.
cell. In the case the source cell initiates handover due to "better cell", This
z Formula: none
XI. Attempted outgoing inter cell handovers for rapid level drop

that the current cell initiates to the specified target cell due to rapid level drop. This
to the specified target cell due to rapid level drop. This item together with
Successful outgoing inter cell handovers for rapid level drop can be used to know
3-260
can be known. See Attempted outgoing inter cell handovers.
Note:
due to rapid level drop after the handover algorithm decision.
cell. In the case the source cell initiates handover due to rapid level drop, This
z Formula: none
XII. Attempted outgoing inter cell handovers for directed retry

that the current cell initiates to the specified target cell due to directed retry (a
handover is triggered for the current cell is congested during the process of
assignment). This item is used to indicate the frequency that the current cell
initiates the handovers to the specified target cell due to directed retry. This item
together with Successful outgoing inter cell handovers for directed retry can be
used to know the performance of such handover from the current cell to the
3-261
Note:
due to directed retry after the handover algorithm decision.
cell. In the handover initiated by the source cell (the current cell) due to
directed retry, This item is measured when the source cell (the current cell)
Figure 3-66 F1.
z Formula: none
XIII. Attempted outgoing inter cell handovers for other causes

that the current cell initiates to the specified target cell due to other causes (such
as fast moving and handover cause being abnormal value). This item is used to
indicate the frequency that the current cell initiates the handovers to the specified
target cell due to other causes. This item together with Successful outgoing inter
cell handovers for other causes can be used to know the performance of such
3-262
Note:
due to other causes (such as fast moving and handover cause unknown)
after the handover algorithm decision.
cell. In the case the source cell initiates handover due to other causes (such
as fast moving and handover cause unknown), This item is measured when
the source cell (the current cell) receives the HANDOVER COMMAND
message from MSC, as shown in Figure 3-66 F1.
z Formula: none
XIV. Attempted extended inter cell outgoing cell handovers for minimum
timing advance

that the current cell (single timeslot extended cell) initiates to the specified target
cell due to the minimum timing advance. This item is used to indicate the
frequency that the current cell (single timeslot extended cell) initiates the handover
due to the minimum timing advance. This item together with Successful outgoing
inter cell handovers in the extended cell (minimum timing advance) can be used to
know the performance of such handover from the current cell to the specified
target cell. See Attempted outgoing inter cell handovers.
z Measurement point: In single timeslot extended cell (the current cell), this item is
measured when the current cell sends an Intercell Handover Request message
(for internal intercell handover) due to the minimum timing advance after the
handover algorithm decision.
z Formula: none
3-263
XV. Successful outgoing inter cell handovers
z Description: the successful handovers for the MS initiates from the current cell to
the specified target cell. If the target cell and the current cell are in different BSCs,
the handover is interBSC handover; otherwise the handover is internal intercell
handover. This item together with Attempted outgoing inter cell handovers can be
used to know the performance of such handover from the current cell to the target
cell. See Successful outgoing internal inter cell handovers, Successful outgoing
Note:
receives the Inter Clear Request message (cause: internal intercell handover
success) from the target cell.
2) In interBSC handover procedure, the target cell is the registered adjacent cell.
CLEAR COMMAND message (cause: handover success) from MSC, as
shown in Figure 3-67 E1.
z Formula: none
3-264
HANDOVER REQUIRED
HANDOVER REQUEST
HANDOVER REQ ACK
HANDOVER COMMAND
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
CLEAR COMMAND
A1, B1, C1, D1, E1
CLEAR COMPLETE
A1: Successful outgoing interbsc inter cell handovers

B1: Successful outgoing interbsc inter cell handovers (to 900)
C1: Successful outgoing interbsc inter cell handovers (to 1800)
E1: Successful outgoing inter cell handovers (including various causes)
Figure 3-67 Successful outgoing interBSC inter cell handovers
XVI. Successful outgoing inter cell handovers for uplink quality
z Description: the successful handovers that the MS initiates from the current cell to
the specified target cell due to uplink quality. If the target cell and the current cell
are in different BSCs, the handover is interBSC handover; otherwise the handover
is internal intercell handover. For internal intercell handover, the handover cause
is carried in the HANDOVER PERFORMED message sent to MSC, for interBSC
handover, it is carried in the corresponding HANDOVER REQUIRED message.
This item together with Attempted outgoing inter cell handovers for uplink quality
can be used to know the performance of such handover. See Successful outgoing
inter cell handovers.
Note:
3-265
1) In internal intercell handover procedure due to uplink quality, the target cell is
the registered adjacent cell. This item is measured when the source cell (the
current cell) receives the Intercell Handover Request message (cause:
internal intercell handover success) from the target cell.
2) In inter BSC handover due to uplink quality, the target cell is the registered
MSC, as shown in Figure 3-67 E1.
z Formula: none
XVII. Successful outgoing inter cell handovers for downlink quality
the specified target cell due to downlink quality. If the target cell and the current
cell are in different BSCs, the handover is inter BSC handover, otherwise the
handover is internal intercell handover. For internal intercell handover, the
handover cause is carried in HANDOVER PERFORMED message sent to MSC,
while the cause for inter BSC handover is carried in the corresponding
HANDOVER REQUIRED message. This item together with Attempted outgoing
inter cell handovers for downlink quality can be used to know the performance of
such handover. See Successful outgoing inter cell handovers.
Note:
1) In internal intercell handover procedure due to downlink quality, the target cell
is the registered adjacent cell. This item is measured when the source cell
(the current cell) receives the Intercell Handover Request message (cause:
2) In inter BSC handover due to downlink quality, the target cell is the registered
z Formula: none
3-266
XVIII. Successful outgoing inter cell handovers for uplink strength
the specified target cell due to uplink strength. If the target cell and the current cell
are in different BSCs, the handover is inter BSC handover, otherwise the
inter cell handovers for uplink strength can be used to know the performance of
Note:
1) In internal intercell handover procedure due to uplink strength, the target cell
2) In inter BSC handover due to uplink strength, the target cell is the registered
z Formula: none
XIX. Successful outgoing inter cell handovers for downlink strength
the specified target cell due to downlink strength. If the target cell and the current
cell are in different BSCs, the handover is inter BSC handover, otherwise the
inter cell handovers for downlink strength can be used to know the performance of
3-267
Note:
1) In internal intercell handover procedure due to downlink strength, the target
cell is the registered adjacent cell. This item is measured when the source
cell (the current cell) receives the Intercell Handover Request message
(cause: internal intercell handover success) from the target cell.
2) In inter BSC handover due to downlink strength, the target cell is the
registered adjacent cell. This item is measured when the source cell (the
current cell) receives the CLEAR COMMAND message (cause: handover
success) from MSC, as shown in Figure 3-67 E1.
z Formula: none
XX. Successful outgoing inter cell handovers for timing advance
the specified target cell due to timing advance. If the target cell and the current cell
inter cell handovers for timing advance can be used to know the performance of
Note:
3-268
1) In internal intercell handover procedure due to timing advance, the target cell
2) In inter BSC handover due to timing advance, the target cell is the registered
z Formula: none
XXI. Successful outgoing inter cell handovers for traffic load
the specified target cell due to traffic load. If the target cell and the current cell are
in different BSCs, the handover is inter BSC handover, otherwise the handover is
internal intercell handover. For internal intercell handover, the handover cause is
carried in HANDOVER PERFORMED message sent to MSC, while the cause for
inter BSC handover is carried in the corresponding HANDOVER REQUIRED
message. This item together with Attempted outgoing inter cell handovers for
traffic load can be used to know the performance of such handover. See
Successful outgoing inter cell handovers.
Note:
1) In internal intercell handover procedure due to traffic load, the target cell is
2) In inter BSC handover due to traffic load, the target cell is the registered
z Formula: none
3-269
XXII. Successful outgoing inter cell handovers for response to MSC
the specified target cell for response to MSC. If the target cell and the current cell
inter cell handovers for response to MSC can be used to know the performance of
Note:
1) In internal intercell handover for response to MSC, the target cell is the
2) In inter BSC handover for response to MSC, the target cell is the registered
z Formula: none
XXIII. Successful outgoing inter cell handovers for O&M intervention
the specified target cell due to the operation on O&M console, such as forced
switchover, blocking without call drop (blocking channel, TRX, and cell, etc.; or
main BCCH/TRX mutual assistance. If the target cell and the current cell are in
different BSCs, the handover is inter BSC handover, otherwise the handover is
3-270
O&M intervention can be used to know the performance of such handover. See
Note:
1) In internal intercell handover for O&M intervention, the target cell is the
2) In inter BSC handover for O&M intervention, the target cell is the registered
z Formula: none
XXIV. Successful outgoing inter cell handovers for better cell
the specified target cell due to "better cell". If the target cell and the current cell are
in different BSCs, the handover is inter BSC handover, otherwise the handover is
better cell can be used to know the performance of such handover. See
Note:
3-271
1) In internal intercell handover procedure due to "better cell", the target cell is
2) In inter BSC handover due to "better cell", the target cell is the registered
z Formula: none
XXV. Successful outgoing inter cell handovers for rapid level drop
the specified target cell due to rapid level drop. If the target cell and the current cell
inter cell handovers for rapid level drop can be used to know the performance of
Note:
1) In internal intercell handover procedure due to rapid level drop, the target cell
2) In inter BSC handover due to rapid level drop, the target cell is the registered
z Formula: none
3-272
XXVI. Successful outgoing inter cell handovers for directed retry
the specified target cell due to directed retry. If the target cell and the current cell
inter cell handovers for directed retry can be used to know the performance of
Note:
1) In internal intercell handover procedure due to directed retry, the target cell is
2) In inter BSC handover due to directed retry, the target cell is the registered
z Formula: none
XXVII. Successful outgoing inter cell handovers for other causes
the specified target cell due to other causes (such as fast moving and handover
cause unknown). If the target cell and the current cell are in different BSCs, the
handover is inter BSC handover, otherwise the handover is internal intercell
handover. For internal intercell handover, the handover cause is carried in
HANDOVER PERFORMED message sent to MSC, while the cause for inter BSC
handover is carried in the corresponding HANDOVER REQUIRED message. This
item together with Attempted outgoing inter cell handovers for other causes can be
3-273
used to know the performance of such handover. See Successful outgoing inter
cell handovers.
Note:
1) In internal intercell handover procedure due to other causes (such as fast
moving and handover cause unknown), the target cell is the registered
receives the Intercell Handover Request message (cause: internal intercell
handover success) from the target cell.
2) In inter BSC handover due to other causes (such as fast moving and
handover cause unknown), the target cell is the registered adjacent cell. This
item is measured when the source cell (the current cell) receives the CLEAR
COMMAND message (cause: handover success) from MSC, as shown in
Figure 3-67 E1.
z Formula: none
XXVIII. Successful outgoing inter cell handovers in the extended cell

(minimum timing advance)
z Description: The successful handovers due to minimum timing advance in single

timeslot extended cell. The handover is internal intracell handover. The handover
cause is carried in HANDOVER PERFROMED message sent to MSC. This item
together with Attempted extended inter cell outgoing cell handovers for minimum
timing advance can be used to know the performance of such handover. See
z Measurement point: In single timeslot extended cell (the current cell), after the MS
successfully accesses the target channel during the internal intracell handover
due to the minimum timing advance, the current cell sends a HANDOVER
PERFORMED message to MSC. This item is measured when the current cell
sends this message.
z Formula: none
3-274
XXIX. Unsuccessful outgoing cell handover with successful reversion
z Description: after the source cell sends a HANDOVER COMMAND message to

the MS, if the MS cannot access the specified target cell due to the causes, such
as poor radio environment or handover parameter error, the MS sends a
HANDOVER FAILURE message (cause: Radio interface failure, reversion to old
channel) to the source cell on the original channel. Upon reception of this
message, the source cell informs the target cell to clear the related handover
resource and MS restores the connection in the source cell. In the handover with
the current cell serving as the source cell (the target cell is the specified cell), this
item is used to measure the number of the above mentioned occasions, i.e.,
successful reversions after the handover failure. If the target cell and the current
cell are in different BSCs, the handover is interBSC handover; otherwise the
handover is internal intercell handover. See Unsuccessful outgoing cell handover
with unsuccessful reversion, Unsuccessful internal inter cell handovers with
successful reversions, and Unsuccessful outgoing BSC handovers with
successful reversion.
1) In internal intercell handover, the target cell is the registered adjacent cell.
HANDOVER FAILURE message (cause: Radio interface failure, reversion to
old channel) from the MS, as shown in Figure 3-68 I1.
2) In interBSC handover, the target cell is the registered adjacent cell. This item
is measured when the source cell (the current cell) receives the HANDOVER
FAILURE message (cause: Radio interface failure, reversion to old channel)
from the MS, as shown in Figure 3-69 C1.
3-275
z Formula: none
MS BTS BSC MSC/VLR
CHANNEL ACT
CONN FAIL IND
ERROR IND A1 , F2
A4, F4
CLEAR COMMAND
A6, F6
Old Channel HANDOVER COMMAND
ERROR IND
A5, F5, H2, J2
CONN FAIL IND
A2, F3, H1,J1 CLEAR COMMAND
.HANDOVER FAILURE A7, F7
Old Channel
A3, B1, C1, D1, E1, F1, G1, I1
HANDOVER COMPLETE
A1~A7: Unsuccessful outgoing internal inter cell handovers

B1: Unsuccessful outgoing internal inter cell handovers (channel invalid)
C1: Unsuccessful outgoing internal inter cell handovers (TA invalid)
D1: Unsuccessful outgoing internal inter cell handovers (frequency invalid)
E1: Unsuccessful outgoing internal inter cell handovers (timer expired)
F1~F7: Unsuccessful outgoing internal inter cell handovers (other causes)
G1: Unsuccessful internal inter cell handovers with successful reversions
H1~H2: Unsuccessful internal inter cell handovers with unsuccessful reversions
I1: Unsuccessful outgoing intercell handovers with successful reversions
J1~J2: Unsuccessful outgoing intercell handovers with unsuccessful reversions
Figure 3-68 Unsuccessful outgoing internal inter cell handovers
HANDOVER COMMAND HANDOVER COMMAND
A 1, C 1 H A N D O V E R F A IL U R E
C O N N F A IL IN D
E R R O R IN D IC A T IO N B1 , D1
B2 , D2
C LEAR C O M M AN D
B3 , D3
C LEAR C O M M AN D
C LEAR C O M PLETE

C1: Unsuccessful outgoing inter cell handovers with successful reversion
D1~D3: Unsuccessful outgoing inter cell handovers with unsuccessful reversion
3-276
XXX. Unsuccessful outgoing cell handover with unsuccessful reversion
z Description: after the source cell sends a HANDOVER COMMAND message to

the MS, if the connection between the MS and the target cell has not been
established yet but the connection between the MS and the source cell has been
disconnected due to the causes, such as poor radio environment or equipment
failure, then BSC sends a CLEAR REQUEST message to MSC to request clearing
the old resource and the resource involved in the handover. So this handover is
unsuccessful and the original service cannot be restored. In the handover with the
current cell serving as the source cell (the target cell is the specified cell), this item
is used to measure the number of the above mentioned occasions, i.e.,
unsuccessful handover with unsuccessful reversion. If the target cell and the
current cell are in different BSCs, the handover is inter BSC handover, otherwise
the handover is internal intercell handover. See Unsuccessful outgoing cell
handover with successful reversion, Unsuccessful internal inter cell handovers
with successful reversions, and Unsuccessful outgoing BSC handovers with
successful reversion.
CONNECTION FAILURE INDICATION message from the BTS after sending
a HANDOVER COMMAND message to MS, as shown in Figure 3-68 J1.
ERROR INDICATION message (cause: "timer T200 expired (N200+1) times"
(0x01), or "unsolicited DM response, multiple frame established state"(0x05),
or "sequence error"(0x07)) from the BTS, as shown in Figure 3-68 J2.
3) In internal intercell handover, after the target cell receives the HANDOVER
DETECTION message, when AM/CM net-drive fails or the timer waiting for
HANDOVER COMPLETE times out, it sends an Inter Clear Request
message to the source cell . This item is measured when the source cell (the
current cell) receives this message.
This item is measured when the timer for the source cell (the current cell) to
wait for Inter Clear Request message after sending HANDOVER COMMAND
message expires.
5) In inter BSC handover, the target cell is the registered adjacent cell. This item
is measured when the source cell (the current cell) receives the
CONNECTION FAILURE INDICATION message from BTS, as shown in
Figure 3-69 D1.
is measured when the source cell (the current cell) receives the ERROR
INDICATION message (cause: "timer T200 expired (N200+1) times" (0x01),
3-277
or "unsolicited DM response, multiple frame established state" (0x05), or

"sequence error"(0x07)), as shown in Figure 3-69 D2.
is measured when the source cell (the current cell) receives the CLEAR
COMMAND message (cause: not handover success), as shown in
Figure 3-69 D3.
is measured when the timer for the source cell to wait for the CLEAR
COMMAND message (cause: handover success) from MSC expires.
z Formula: none
XXXI. Outgoing inter cell handover success rate (%)
z Description: The success rate of the outgoing inter cell handovers from the current
cell to the specified target cell, including outgoing internal intercell handover and
outgoing interBSC inter cell handover. See Attempted outgoing inter cell
handovers and Successful outgoing inter cell handovers.
z Formula: Successful outgoing inter cell handovers / Attempted outgoing inter cell
handovers
3.16 Incoming Inter Cell Handover Measurement Function
3.16.1 General
The statistic items of Incoming Inter Cell Handover Measurement Function are used to
know the incoming inter cell handover performance of the specified cell, such as
attempted incoming inter cell handovers and successful incoming inter cell handovers.
All statistic items of Incoming Inter Cell Handover Measurement Function are listed in
Table 3-21.
To know the outgoing inter cell handover performance of the specified cell, the related
statistic items of Outgoing Inter Cell Handover Measurement Function should be
registered.
For the statistic items of Incoming Inter Cell Handover Measurement Function, it is
recommended that they should be registered at the early stage of BSC running, or be
registered when the handover performance of the specified cell is to be known so that
the network optimization can be performed. At the stable running stage of BSC, the
task of these statistic items can be deleted. These items together with the statistic items
of Outgoing Inter Cell Handover Measurement Function can be used to know the
handover situation between two specified cells. The statistic cycle is recommended to
be 60 minutes.
3-278
The statistic object of the statistic items of Incoming Inter Cell Handover Measurement
Function is the target adjacent cell that MSs hand over to, the specified cell must be
nominated as the target cell in a handover, and the statistic results about this cell will list
the situations all other adjacent cell (maxnum 32 cells) handed over to the cell. All
statistic items of Incoming Inter Cell Handover Measurement Function will be selected
together for registration.
Table 3-21 Statistic items in Incoming Inter Cell Handover Measurement Function
No. Item name

1 Attempted incoming inter cell handovers
2 Successful incoming inter cell handovers
3 Unsuccessful incoming cell handovers (congestion)
4 Incoming inter cell handover success rate (%)
I. Attempted incoming inter cell handovers
z Description: the incoming inter cell handover requests (including inter BSC
handover and internal intercell handover) that the current cell (the target cell)
receives from other cells (source cell). If source cells are different, the results and
the measured objects are different and they are determined by some source cell
and some target cell. This item can be used to know the frequency of the
handovers that some source cell initiates to the current cell. This item together
with Successful incoming inter cell handovers can be used to know the
performance of the handover from this cell to the current cell. See Attempted
incoming interBSC inter cell handovers, and Attempted incoming internal inter cell
handovers.
1) In internal intercell, a source cell will send a Intercell Handover Request
message to a target cell after the handover algorithm decision. The target cell
is the registered adjacent cell. This item is measured when the target cell (the
current cell) receives this message.
2) In interBSC handover, the target BSC packs the HANDOVER REQUEST
message received from MSC into the IntoBSC Handover Request message,
and then forwards the message to the BM where the target cell configured.
This item is measured when the target cell (the current cell) receives this
message.
z Formula: none
3-279
II. Successful incoming inter cell handovers
z Description: the successful incoming inter cell handovers (including inter BSC
handover and internal intercell handover) that MS is hander over from some other
cells (source cell) to the current cell (the target cell). If source cells are different,
the results and the measured objects are different and they are determined by
some source cell and some target cell This item together with Attempted incoming
inter cell handovers can be used to know the performance of the handover from
some cell to the current cell. See Attempted incoming interBSC inter cell
handovers and Attempted incoming internal inter cell handovers.
1) In internal intercell handover (cause: directed retry), after the MS successfully
accesses the target cell (the current cell), the target cell will finally send an
ASSIGNMENT COMPLETE message to MSC,this item is measured in this case,
as shown in Figure 3-69 E1.
2) In internal intercell handover (cause: non-directed retry, such as signal quality,
signal strength, TA, traffic load, rapid level drop, better cell, MSC invocation, and
O&M intervention, after the MS successfully accesses the target cell (the current
cell), this item is measured when the target cell will finally send a HANDOVER
PERFORMED message to MSC, as shown in Figure 3-70 F1.
3) In interBSC handover, this item is measured when the target cell (the current cell)
forwards HANDOVER COMPLETE message to MSC after the target cell has
received this message, as shown in Figure 3-71 C1.
z Formula: none
MS BTS BSC MSC/VLR
ASSIGNMENT REQUEST
HANDOVER COMMAND
HANDOVER COMPLETE
ASSIGNMENT COMPLETE
A1, B1, C1, D1, E1
A1: Successful incoming internal inter cell handovers

B1: Successful incoming internal inter cell handovers (from 900)
E1: Successful incoming inter cell handovers
Figure 3-70 Successful incoming internal inter cell handovers(directed retry)
3-280
MS BTS BSC MSC/VLR
.HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER PERFORMED
A1, B1 , C1, D1, E1, F1
A1: Successful intracell handover

B1: Successful incoming internal inter cell handovers
D1: Successful incoming internal inter cell handovers (from 1800)
E1: Successful dual-band intercell handovers
F1: Successful incoming inter cell handovers
Figure 3-71 Successful intraBSC handover (not DIRECTED RETRY)
MS BTS BSC MSC/VLR

HANDOVER REQUESTT
CHANNEL ACT
.HANDOVER DETECTION
HANDOVER COMPLETE
A1, B1, C1
HANDOVER COMPLETE
A1: Successful incoming inter BSC inter cell handovers

B1: Successful dual-band intercell handovers
C1: Successful incoming inter cell handovers
Figure 3-72 Successful incoming inter BSC internal inter cell handovers
III. Unsuccessful incoming cell handovers (congestion)
z Description: after the current cell (target cell) has received handover request
(including interBSC handover or internal intercell handover) from other cells
(source cell), the current cell initiates the channel preparation procedure. If
exception occurs during the channel preparation procedure, the handover will be
measured as an unsuccessful handover due to channel congestion. If source cells
are different, the results and the measured objects are different and they are
determined by some source cell and some target cell. See Unsuccessful incoming
internal inter cell handovers (no radio resource available) and Unsuccessful
incoming BSC handovers (no radio resource available.
3-281
1) In internal intercell handover, this item is measured when the exception, such
as no available channel, occurs during the target cell (the current cell) is
allocating a new channel. And the target cell sends an Intercell Handover
Reject message to the source cell simultaneously.
2) In interBSC handover, during the target cell (the current cell) checking the
conditions for incoming BSC handover, if the check result is that there is no
available channel, for example, channel request fails, This item is measured
and the target cell sends a HANDOVER FAILURE message to MSC in this
case.
3) In interBSC handover, the target cell (the current cell) measures this item
when the timer Tqho (maximum allowed queuing time for handover) in the
target cell expires. And the target cell sends a HANDOVER FAILURE
message to MSC simultaneously.
z Formula: none
IV. Incoming inter cell handover success rate (%)
z Description: the success rate of the incoming inter cell handovers (including
internal intercell handover and interBSC handover) that some cell initiates to the
current cell. See Attempted incoming inter cell handovers and Successful
incoming inter cell handovers.
z Formula: Successful incoming inter cell handovers / Attempted incoming inter cell
handovers
3.17 Undefined Adjacent Cell Measurement Function
3.17.1 General
An undefined adjacent cell is a cell which is not configured as adjacent cell in Cell
Adjacent Relationship table but whose BCCH frequency is configured in BA table in
BSC data configuration. Undefined Adjacent Cell Measurement Function is used to
measure the information of undefined adjacent cells reported by MS. This is an
effective measure to check the adjacent cells missed in configuration. It is
recommended to register this measurement task at equipment deployment, and delete
it after the operation of system is stable.
If the measurement results of this task indicate during the initial stage of the newly
deployed equipment that the signals from some cells are strong while these cells are
not configured as adjacent cells, then these cells can be configured as adjacent cells
during network optimization.
The object of undefined adjacent cell measurement task is cell. User can set the
module and cell of the task in the interface of Object Definition, as well as Rate limit and
3-282
Level limit. In the information of undefined adjacent cell reported by MS, a unique cell is
defined by BSIC and BCCH. The measurement results of an undefined adjacent cell
will be displayed at the background if the ratio of number of MRs containing this
undefined adjacent cell to total number of MRs containing all undefined adjacent cells
equals to Rate limit, and the Average signal intensity of undefined adjacent cells is
larger than or equal to Level limit. For example, in the measurement task of Cell A, Cell
A has three undefined adjacent cells: N1, N2 and N3. Among the MRs reported by MS,
there is one MR containing N1, one MR containing N2, eight containing N3. The
Average signal intensity of N1, N2 and N3 is 25. If the Rate limit is 15, and Level limit is
20, then the MRs of N1 and N2 are 1 / (1 + 1 + 8) = 10%, and MR of N3 is 8 / (1 + 1 + 8)
= 80%. Therefore, only the measurement results of N3 will be displayed at background.
The items of this measurement are listed in Table 3-22.
Table 3-22 Statistic items in Undefined Adjacent Cell Measurement Function
No. Item name

1 BSIC of undefined adjacent cell
2 BCCH of undefined adjacent cell
3 Average signal intensity of undefined adjacent cell
4 Undefined adjacent cell measurement reports
I. BSIC of undefined adjacent cell
z Description: MS reports to the network one MR per 480ms. If the signal of a

frequency received by MS is configured in BA table of BSC, it will be reported as
an adjacent cell in MR. If this cell is not configured as adjacent cell in Cell Adjacent
Relationship table, its BSIC will be recorded as an undefined adjacent one. The
frequencies of BSIC and BCCH can be used to identify an adjacent cell.
z Measurement point: On reception of MR, BSC judges whether the record of the
undefined adjacent cell in this MR already exists according to the frequencies of
BSIC and BCCH. If the record already exists, the receiving level of this cell is
accumulated, and Undefined adjacent cell measurement reports increases by 1.
Otherwise, a new record will be created to measure BSIC; BCCH, receiving level
and number of measurement reports of this undefined adjacent cell.
z Formula: none.
II. BCCH of undefined adjacent cell

3-283
Relationship table, its BCCH will be recorded as an undefined adjacent one. The
frequencies of BSIC and BCCH can be used together to identify an adjacent cell.
Otherwise, a new record will be created to measure BSIC, BCCH, receiving level
and number of measurement reports of this undefined adjacent cell.
z Formula: none.
III. Average signal intensity of undefined adjacent cell

Relationship table, its signal intensity will be recorded as an undefined adjacent
one. If the average signal intensity is large, it may be necessary to adjust the
coverage or adjacent cells.
The value of this item is got by dividing the sum of the accumulated receiving level
with Undefined adjacent cell measurement reports. Otherwise, a new record will
be created to measure BSIC, BCCH, receiving level and number of measurement
reports of this undefined adjacent cell.
z Formula: none.
IV. Undefined adjacent cell measurement reports

Relationship table, the number of MRs containing this cell will be measured.
accumulated, and the value of this item increases by 1. Otherwise, a new record
will be created to measure BSIC, BCCH, receiving level and number of
measurement reports of this undefined adjacent cell.
z Formula: none.
3-284
3.18 Defined Adjacent Cell Measurement Function
3.18.1 General
A defined adjacent cell is a cell which is configured as adjacent cell in Cell Adjacent
Relationship table and whose BCCH frequency is configured in BA table in BSC data
configuration. Defined Adjacent Cell Measurement Function is used to measure the
information of defined adjacent cells reported by MS. This is an effective measure to
check the redundant adjacent cells. It is recommended to register this measurement
task at equipment deployment, and delete it after the operation of system is stable.
The measurement results of this measurement function can be the basis of the network
optimization.
The object of defined adjacent cell measurement task is cell. User can set the module
and cell of the task in the interface of Object Definition, as well as Rate limit and Level
limit. In the information of defined adjacent cell reported by MS, a unique cell is defined
by BSIC and BCCH. The measurement results of an defined adjacent cell will be
displayed at the background if the ratio of number of MRs containing this defined
adjacent cell to total number of MRs containing all defined adjacent cells equals to Rate
limit, and the Average signal intensity of defined adjacent cells is larger than or equal to
Level limit. For example, in the measurement task of Cell A, Cell A has three defined
adjacent cells: N1, N2 and N3. Among the MRs reported by MS, there is one MR
containing N1, one MR containing N2, eight containing N3. The Average signal
intensity of N1, N2 and N3 is 25. If the Rate limit is 15, and Level limit is 20, then the
MRs of N1 and N2 are 1 / (1 + 1 + 8) = 10%, and MR of N3 is 8 / (1 + 1 + 8) = 80%.
Therefore, only the measurement results of N3 will be displayed at background. The
items of this measurement are listed in Table 3-23.
Table 3-23 Statistic items in Defined Adjacent Cell Measurement Function
No. Item name

1 BSIC of defined adjacent cell
2 BCCH of defined adjacent cell
3 Average signal intensity of defined adjacent cell
4 Defined adjacent cell measurement reports
I. BSIC of defined adjacent cell

an adjacent cell in MR. If this cell is configured as adjacent cell in Cell Adjacent
3-285
Relationship table, its BSIC will be recorded as an undefined adjacent one. The
frequencies of BSIC and BCCH can be used to identify an adjacent cell.
defined adjacent cell in this MR already exists according to the frequencies of
accumulated, and Defined adjacent cell measurement reports increases by 1.
and number of measurement reports of this defined adjacent cell.
z Formula: none.
II. BCCH of defined adjacent cell

Relationship table, its BCCH will be recorded as a defined adjacent one. The
frequencies of BSIC and BCCH can be used together to identify an adjacent cell.
accumulated, and defined adjacent cell measurement reports increases by 1.
and number of measurement reports of this defined adjacent cell.
z Formula: none.
III. Average signal intensity of defined adjacent cell

Relationship table, its signal intensity will be recorded as a defined adjacent one. If
the average signal intensity is large, it may be necessary to adjust the coverage or
adjacent cells.
accumulated, and Defined adjacent cell measurement reports increases by 1. The
value of this item is got by dividing the sum of the accumulated receiving level with
Defined adjacent cell measurement reports. Otherwise, a new record will be
created to measure BSIC, BCCH, receiving level and number of measurement
reports of this defined adjacent cell.
z Formula: none.
3-286
IV. Defined adjacent cell measurement reports

Relationship table, the number of MRs containing this cell will be measured.
accumulated, and the value of this item increases by 1. Otherwise, a new record
will be created to measure BSIC, BCCH, receiving level and number of
measurement reports of this defined adjacent cell.
z Formula: none.
3.19 Receiving Quality Measurement
3.19.1 General
The MR received by BSC contains uplink receiving quality and downlink receiving
quality. There are 8 levels of receiving quality: 0~7. Each level corresponds to a BER
range. As shown in Table 3-24, Level 0 indicates the lowest BER, i.e. best receiving
quality; Level 7 indicates the largest BER, i.e. the worst receiving quality.
Table 3-24 Receiving quality level and BER correspondence
Receiving quality level BER

0 < 0.2%
1 0.2 ~ 0.4%
2 0.4 ~ 0.8%
3 0.8 ~ 1.6%
4 1.6 ~ 3.2%
5 3.2 ~ 6.4%
6 6.4 ~ 12.8%
7 > 12.8%
Receiving Quality Measurement reflects the uplink and downlink quality level
distribution in a cell by measuring the times of receiving signals being at all receiving
quality levels within the measurement cycle according to the records of MR received in
a measurement cycle. The result of receiving quality measurement, with the result of
Receiving Level Measurement as the reference, can be analyzed to get the information
of radio signal coverage and interference of a cell.
The object of Receiving quality measurement is TRX. The module No., cell No. and
TRX No. (or all TRXs in the configured range of cells in the configured range) of the
3-287
task can be configured in Object Definition. All measurement items are listed in
Table 3-25.
Table 3-25 Receiving quality measurement items
No. Item name

1 Average uplink receiving quality 0
9 Average downlink receiving quality 0
3.19.2 Statistic items
I. Average uplink receiving quality 0
z Description: After BSC receiving MR, this index will increase by 1 if the uplink
receiving quality level is 0.
z Formula: none.
II. Average uplink receiving quality 1
z Formula: none.
III. Average uplink receiving quality 2
z Formula: none.
3-288
IV. Average uplink receiving quality 3
z Formula: none.
V. Average uplink receiving quality 4
z Formula: none.
VI. Average uplink receiving quality 5
z Formula: none.
VII. Average uplink receiving quality 6
z Formula: none.
VIII. Average uplink receiving quality 7
z Formula: none.
IX. Average downlink receiving quality 0
z Description: After BSC receiving MR, this index will increase by 1 if the downlink
z Formula: none.
3-289
X. Average downlink receiving quality 1
z Formula: none.
XI. Average downlink receiving quality 2
z Formula: none.
XII. Average downlink receiving quality 3
z Formula: none.
XIII. Average downlink receiving quality 4
z Formula: none.
XIV. Average downlink receiving quality 5
z Formula: none.
XV. Average downlink receiving quality 6
z Formula: none.
3-290
XVI. Average downlink receiving quality 7
z Formula: none.
3.20 Receiving Level Measurement Function
3.20.1 General
The MR BSC receives contains the level values of uplink receiving level and downlink
receiving level.
The signal receiving levels are classified into 6 ranks: Level: 0~5. Each rank stands for
a range of receiving levels. As shown in Table 3-26, the higher rank suggests the higher
receiving level. Rank 0 is the lowest receiving level. Rank 5 is the highest one.
Table 3-26 Correspondence between receiving levels and their ranks
Receiving level ranks Receiving level (dBm)

0 -100
1 -99 ~ -95
2 -94 ~ -90
3 -89 ~ -80
4 -79 ~ -70
5 -69
The receiving quality is classified into 8 ranks: 0~7. Each rank corresponds to a range
of BER. As shown in Table 3-27, the higher rank suggests the worse receiving quality.
Rank 0 stands for the lowest BER, i.e. the best receiving quality, and Rank 7 stands for
the highest BER, i.e. the worst receiving quality.
Table 3-27 Correspondence between receiving quality ranks and BER
Receiving quality rank BER

0 < 0.2%
1 0.2 ~ 0.4%
2 0.4 ~ 0.8%
3 0.8 ~ 1.6%
4 1.6 ~ 3.2%
5 3.2 ~ 6.4%
6 6.4 ~ 12.8%
7 > 12.8%
3-291
Receiving Level Measurement Function reflects the rank distribution of the receiving
level and receiving quality of uplink/downlink signal in the cell by measuring the times of
the signals being in various receiving level ranks and receiving quality ranks according
to the records of MRs received in a measurement cycle.
It is possible to analyze the result of receiving level measurement with the result of
receiving quality measurement as the reference to obtain the information of radio signal
coverage and interference of a cell. For example, if the times of high level and low
quality are many, there may be some problems with the coverage. This kind of
information can be used to locate the faults in the transceiving channels such as TRX
and antenna feeder.
The object of receiving quality measurement is TRX. The module No., cell No. and TRX
No. (or all TRXs in the configured range of cells in the configured range) of the task can
be configured in Object Definition. All measurement items are listed in Table 3-28.
Table 3-28 Items of receiving level measurement
No. Item name

1 Uplink receiving level rank 0 and receiving quality rank 0
3-292

49 Downlink receiving level rank 0 and receiving quality rank 0
3-293
I. Uplink receiving level rank 0 and receiving quality rank 0
z Description: After BSC receives MR, this index will increase by 1 if the uplink
receiving level rank is 0 and the uplink receiving quality rank is 0.
z Measurement point: Measured when the uplink receiving level rank is 0 and the
uplink receiving quality level is 0.
z Formula: none.
II. Uplink receiving level rank 0 and receiving quality rank 1
uplink receiving quality rank is 1.
z Formula: none.
III. Uplink receiving level rank 0 and receiving quality rank 2
z Formula: none.
IV. Uplink receiving level rank 0 and receiving quality rank 3
z Formula: none.
V. Uplink receiving level rank 0 and receiving quality rank 4
z Formula: none.
VI. Uplink receiving level rank 0 and receiving quality rank 5
3-294
z Formula: none.
VII. Uplink receiving level rank 0 and receiving quality rank 6
z Formula: none.
VIII. Uplink receiving level rank 0 and receiving quality rank 7
z Formula: none.
IX. Uplink receiving level rank 1 and receiving quality rank 0
z Formula: none.
X. Uplink receiving level rank 1 and receiving quality rank 1
z Formula: none.
XI. Uplink receiving level rank 1 and receiving quality rank 2
z Formula: none.
XII. Uplink receiving level rank 1 and receiving quality rank 3
3-295
z Formula: none.
XIII. Uplink receiving level rank 1 and receiving quality rank 4
z Formula: none.
XIV. Uplink receiving level rank 1 and receiving quality rank 5
z Formula: none.
XV. Uplink receiving level rank 1 and receiving quality rank 6
z Formula: none.
XVI. Uplink receiving level rank 1 and receiving quality rank 7
z Formula: none.
XVII. Uplink receiving level rank 2 and receiving quality rank 0
z Formula: none.
XVIII. Uplink receiving level rank 2 and receiving quality rank 1
3-296
z Formula: none.
XIX. Uplink receiving level rank 2 and receiving quality rank 2
z Formula: none.
XX. Uplink receiving level rank 2 and receiving quality rank 3
z Formula: none.
XXI. Uplink receiving level rank 2 and receiving quality rank 4
z Formula: none.
XXII. Uplink receiving level rank 2 and receiving quality rank 5
z Formula: none.
XXIII. Uplink receiving level rank 2 and receiving quality rank 6
z Formula: none.
XXIV. Uplink receiving level rank 2 and receiving quality rank 7
3-297
z Formula: none.
XXV. Uplink receiving level rank 3 and receiving quality rank 0
z Formula: none.
XXVI. Uplink receiving level rank 3 and receiving quality rank 1
z Formula: none.
XXVII. Uplink receiving level rank 3 and receiving quality rank 2
z Formula: none.
XXVIII. Uplink receiving level rank 3 and receiving quality rank 3
z Formula: none.
XXIX. Uplink receiving level rank 3 and receiving quality rank 4
z Formula: none.
XXX. Uplink receiving level rank 3 and receiving quality rank 5
3-298
z Formula: none.
XXXI. Uplink receiving level rank 3 and receiving quality rank 6
z Formula: none.
XXXII. Uplink receiving level rank 3 and receiving quality rank 7
z Formula: none.
XXXIII. Uplink receiving level rank 4 and receiving quality rank 0
z Formula: none.
XXXIV. Uplink receiving level rank 4 and receiving quality rank 1
z Formula: none.
XXXV. Uplink receiving level rank 4 and receiving quality rank 2
z Formula: none.
XXXVI. Uplink receiving level rank 4 and receiving quality rank 3
3-299
z Formula: none.
XXXVII. Uplink receiving level rank 4 and receiving quality rank 4
z Formula: none.
XXXVIII. Uplink receiving level rank 4 and receiving quality rank 5
z Formula: none.
XXXIX. Uplink receiving level rank 4 and receiving quality rank 6
z Formula: none.
XL. Uplink receiving level rank 4 and receiving quality rank 7
z Formula: none.
XLI. Uplink receiving level rank 5 and receiving quality rank 0
z Formula: none.
XLII. Uplink receiving level rank 5 and receiving quality rank 1
3-300
z Formula: none.
XLIII. Uplink receiving level rank 5 and receiving quality rank 2
z Formula: none.
XLIV. Uplink receiving level rank 5 and receiving quality rank 3
z Formula: none.
XLV. Uplink receiving level rank 5 and receiving quality rank 4
z Formula: none.
XLVI. Uplink receiving level rank 5 and receiving quality rank 5
z Formula: none.
XLVII. Uplink receiving level rank 5 and receiving quality rank 6
z Formula: none.
XLVIII. Uplink receiving level rank 5 and receiving quality rank 7
3-301
z Formula: none.
XLIX. Downlink receiving level rank 0 and receiving quality rank 0
z Description: After BSC receives MR, this index will increase by 1 if the downlink
receiving level rank is 0 and the downlink receiving quality rank is 0.
z Measurement point: Measured when the downlink receiving level rank is 0 and the
downlink receiving quality level is 0.
z Formula: none.
L. Downlink receiving level rank 0 and receiving quality rank 1
downlink receiving quality rank is 1.
z Formula: none.
LI. Downlink receiving level rank 0 and receiving quality rank 2
z Formula: none.
LII. Downlink receiving level rank 0 and receiving quality rank 3
z Formula: none.
LIII. Downlink receiving level rank 0 and receiving quality rank 4
z Formula: none.
LIV. Downlink receiving level rank 0 and receiving quality rank 5
3-302
z Formula: none.
LV. Downlink receiving level rank 0 and receiving quality rank 6
z Formula: none.
LVI. Downlink receiving level rank 0 and receiving quality rank 7
z Formula: none.
LVII. Downlink receiving level rank 1 and receiving quality rank 0
z Formula: none.
LVIII. Downlink receiving level rank 1 and receiving quality rank 1
z Formula: none.
LIX. Downlink receiving level rank 1 and receiving quality rank 2
z Formula: none.
LX. Downlink receiving level rank 1 and receiving quality rank 3
3-303
z Formula: none.
LXI. Downlink receiving level rank 1 and receiving quality rank 4
z Formula: none.
LXII. Downlink receiving level rank 1 and receiving quality rank 5
z Formula: none.
LXIII. Downlink receiving level rank 1 and receiving quality rank 6
z Formula: none.
LXIV. Downlink receiving level rank 1 and receiving quality rank 7
z Formula: none.
LXV. Downlink receiving level rank 2 and receiving quality rank 0
z Formula: none.
LXVI. Downlink receiving level rank 2 and receiving quality rank 1
3-304
z Formula: none.
LXVII. Downlink receiving level rank 2 and receiving quality rank 2
z Formula: none.
LXVIII. Downlink receiving level rank 2 and receiving quality rank 3
z Formula: none.
LXIX. Downlink receiving level rank 2 and receiving quality rank 4
z Formula: none.
LXX. Downlink receiving level rank 2 and receiving quality rank 5
z Formula: none.
LXXI. Downlink receiving level rank 2 and receiving quality rank 6
z Formula: none.
LXXII. Downlink receiving level rank 2 and receiving quality rank 7
3-305
z Formula: none.
LXXIII. Downlink receiving level rank 3 and receiving quality rank 0
z Formula: none.
LXXIV. Downlink receiving level rank 3 and receiving quality rank 1
z Formula: none.
LXXV. Downlink receiving level rank 3 and receiving quality rank 2
z Formula: none.
LXXVI. Downlink receiving level rank 3 and receiving quality rank 3
z Formula: none.
LXXVII. Downlink receiving level rank 3 and receiving quality rank 4
z Formula: none.
LXXVIII. Downlink receiving level rank 3 and receiving quality rank 5
3-306
z Formula: none.
LXXIX. Downlink receiving level rank 3 and receiving quality rank 6
z Formula: none.
LXXX. Downlink receiving level rank 3 and receiving quality rank 7
z Formula: none.
LXXXI. Downlink receiving level rank 4 and receiving quality rank 0
z Formula: none.
LXXXII. Downlink receiving level rank 4 and receiving quality rank 1
z Formula: none.
LXXXIII. Downlink receiving level rank 4 and receiving quality rank 2
z Formula: none.
LXXXIV. Downlink receiving level rank 4 and receiving quality rank 3
3-307
z Formula: none.
LXXXV. Downlink receiving level rank 4 and receiving quality rank 4
z Formula: none.
LXXXVI. Downlink receiving level rank 4 and receiving quality rank 5
z Formula: none.
LXXXVII. Downlink receiving level rank 4 and receiving quality rank 6
z Formula: none.
LXXXVIII. Downlink receiving level rank 4 and receiving quality rank 7
z Formula: none.
LXXXIX. Downlink receiving level rank 5 and receiving quality rank 0
z Formula: none.
XC. Downlink receiving level rank 5 and receiving quality rank 1
3-308
z Formula: none.
XCI. Downlink receiving level rank 5 and receiving quality rank 2
z Formula: none.
XCII. Downlink receiving level rank 5 and receiving quality rank 3
z Formula: none.
XCIII. Downlink receiving level rank 5 and receiving quality rank 4
z Formula: none.
XCIV. Downlink receiving level rank 5 and receiving quality rank 5
z Formula: none.
XCV. Downlink receiving level rank 5 and receiving quality rank 6
z Formula: none.
XCVI. Downlink receiving level rank 5 and receiving quality rank 7
3-309
z Formula: none.
3.21 Up-Down Link Balance Measurement Function
3.21.1 General
To achieve an excellent system, it is necessary to have a power estimation during

planning so as to maintain the balance between the uplink and downlink signals within
the covered area. If the uplink signal coverage is larger than that of downlink signal, the
signal at the edge of the cell will be weak and easily "submerged" by the stronger
signals from other cells. If the downlink signal coverage is larger than that of uplink
signal, MS will be forced to station at this signal, but since the unlink signal is too weak,
the voice quality will be affected. The balance here does not mean absolute equal. With
the MR on Abis interface, it is easy to judge whether the uplink and downlink signal is in
balance.
The MR BSC receives contains uplink receiving level and downlink receiving level.
Here is a calculation method for Up-Down Link Balance Measurement: (downlink
receiving level uplink receiving level) (MS sensitivity BTS sensitivity). The current
value for BSC is 6. This difference calculated from the above formula can be classified
into 11 ranks according the to dB value of the result: Rank 1~11. The number of MR in
each rank is measured in this measurement. The correspondence is listed in
Table 3-29.
Table 3-29 Relation between uplink/downlink balance rank and receiving level
Uplink and downlink balance level Downlink receiving level uplink receiving level 6 (dB)
1 -15
2 -14 ~ -10
3 -9 ~ -6
4 -5 ~ -3
5 -2 ~ 0
6 0
7 1~2
8 3~5
9 6~9
10 10 ~ 14
11 15
If the measurement result shows that the uplink/downlink are frequently in the balance
level 1, then the downlink loss is too large or the downlink transmitting power is to weak.
If the measurement result shows that the uplink/downlink are frequently in the balance
level 11, then the uplink loss is too large or the uplink transmitting power is to weak.
These data can be used as a reference to locate the faults in transceiving channels
such as TRX and antenna feeder.
3-310
The object of Up-down link balance measurement is TRX. The module No., cell No.
and TRX No. (or all TRXs in the configured range of cells in the configured range) of the
task can be configured in Object Definition. All measurement items are listed in
Table 3-30.
Table 3-30 Up-down link balance measurement items
No. Item name

1 Rank 1
2 Rank 2
3 Rank 3
4 Rank 4
5 Rank 5
6 Rank 6
7 Rank 7
8 Rank 8
9 Rank 9
10 Rank 10
11 Rank 11
I. Rank 1
z Description: After BSC receives MR, this index increases by 1 if the result from the
calculation method in 3.21.1 General is in up-down link balance rank 1.
z Measurement point: Measured when BSC receives MR, and the result from the
calculation method in 3.21.1 General is in the up-down link balance rank 1.
z Formula: none.
II. Rank 2
z Formula: none.
III. Rank 3
z Formula: none.
3-311
IV. Rank 4
z Formula: none.
V. Rank 5
z Formula: none.
VI. Rank 6
z Formula: none.
VII. Rank 7
z Formula: none.
VIII. Rank 8
z Formula: none.
IX. Rank 9
z Formula: none.
3-312
X. Rank 10
z Formula: none.
XI. Rank 11
z Formula: none.
3.22 LAPD Link Measurement Function
3.22.1 General
The Layer 3 (L3) information interaction between BSC and BTS is conducted on the
basis of normal functioning of Layer 2 (L2) link. The management and maintenance of
L2 link conforms to the specification of ISDN data link layer. In BSC, the management
of L2 is carried out by LAPD board.
"LAPD Link Measurement Function" measures the times of sending and receiving link
setup or refuse messages between LAPD and L2 entity in BTS. These items can be
used to judge whether L2 link is in normal condition.
The object of "LAPD Link Measurement Function" is the link. In the interface of Object
Definition, it is possible to register the module No., link No. or the links within the
configured range in the module. All items are listed in Table 3-31.
Table 3-31 LAPD link measurement items
No. Item name

1 BSC num. of sending link setups
2 BSC num. of receiving link setups
3 BSC num. of sending rejections
4 BSC num. of receiving rejections
5 BSC num. of sending RNRs
6 BSC num. of receiving RNRs
7 BSC num. of retransmissions
8 BSC num. of received serial number errors
9 BSC num. of receiving layer 3 data requests
10 BSC num. of sending messages
11 BSC num. of receiving messages
12 BSC num. of sending message queue overflows
13 BSC num. of receiving long frame errors
3-313
14 BSC num. of receiving octets errors

15 BSC num. of receiving give-up serials
16 BSC num. of receiving CRC errors
17 BSC num. of L1L2 queue overflows
18 BSC num. of received frames by physical layer
19 BTS num. of receiving long frame errors
21 BTS num. of sending long frame errors
23 BTS num. of sending RNRs
24 BTS num. of receiving RNRs
25 BTS num. of retransmissions
26 BTS num. of received serial number errors
27 BTS num. of receiving layer 3 data requests
28 BTS num. of sending messages
29 BTS num. of receiving messages
30 BTS num. of sending message queue overflows
32 BTS num. of receiving octets errors
33 BTS num. of receiving give-up serials
34 BTS num. of receiving CRC errors
35 BTS num. of L1L2 queue overflows
36 BTS num. of received frames by physical layer
I. BSC num. of sending link setups
z Description: This item measures the times of LAPD, the L2 entity in BSC, sending
SABME frames. Normally, SABME frame is sent to request for link setup. After the
startup of BSC, the link status is converted to multi-frame (Multi_I) setup through
the frame interaction between the L2 entities of BSC and BTS. During this
procedure, LAPD sends SABME from to BTS L2 entity. In the normal operation of
BSC, if link status becomes abnormal or physical link between BSC and BTS is
broken, BSC will also send SABME frame to request for link reestablishment.
z Measurement point: This item is measured when LAPD sends SABME frame.
z Formula: none.
II. BSC num. of receiving link setups
z Description: This item measures the times of LAPD, the L2 entity in BSC, receiving
SABME frames. According to the specification of L2, SABME frame is sent to
request for link setup. During the startup and normal operation of BSC, link setup
is not initiated by BTS, so BTS will not send SABME frame to BSC, and that
means this item should be 0. If the link status is abnormal (other than Multi_I), BTS
may send SABME frame to BSC. Note that if the uplink physical link is broken,
then even BTS have sent SABME frame, BSC will have no chance to receive it, so
this item will not increase.
z Measurement point: This item is measured when LAPD receives SABME frame.
3-314
z Formula: none.
III. BSC num. of sending rejections
z Description: This item measures the times of BSC L2 entity, i.e. LAPD, sending
REJ frame. In L2 specification, REJ frame is a monitoring frame which means the
received Frame I (information frame) is refused, and at the same time the Serial
No. of Frame I is expected from the peer end. Frame I is an information frame
numbered in sequence. LAPD has records for the received and sent Frame Is.
Normally this item should be 0. If the LAPD receives a Frame I whose No. is not
expected, it sends a REJ frame to BTS, and this item increases by 1. For example,
the serial No. of Frame I expected by BSC is A, while the No. of the received one is
B, BSC sends a REJ frame to request for Frame I whose serial No. is A.
z Measurement point: This item is measured when LAPD sends REJ frame.
z Formula: none.
IV. BSC num. of receiving rejections
z Description: This item measures the times of BSC L2 entity, i.e. LAPD, receiving
REJ frame. In L2 specification, REJ frame is a monitoring frame which means the
received Frame I (information frame) is refused, and at the same time the Serial
No. of Frame I is expected from the peer end. Frame I is an information frame
numbered in sequence. LAPD has records for the received and sent Frame Is.
Normally this item should be 0. If the BTS receives a Frame I whose No. is not
expected, it sends a REJ frame to BSC, and this item increases by 1. For example,
the serial No. of Frame I expected by BTS is A, while the No. of the received one is
B, BTS sends a REJ frame to request for Frame I whose serial No. is A.
z Measurement point: This item is measured when LAPD receives a REJ frame.
z Formula: none.
V. BSC num. of sending RNRs
RNR frame. In L2 specification, REJ frame is a monitoring frame which means the
home end is busy and is not ready to receive the next Frame I and at the same
time the Serial No. of Frame I is expected from the peer end. When the peer end
receives, it stops sending Frame I. if the receiver of BSC is busy, it sends RNR
frame to BTS. BTS stops sending Frame I on reception of RNR.
z Measurement point: This item is measured when LAPD sends RNR frame.
z Formula: none.
VI. BSC num. of receiving RNRs
RNR frame. In L2 specification, REJ frame is a monitoring frame which means the
home end is busy and is not ready to receive the next Frame I and at the same
3-315
time the Serial No. of Frame I is expected from the peer end. When the peer end
receives, it stops sending Frame I. if the receiver of BTS is busy, it sends RNR
frame to BSC. BSC stops sending Frame I on reception of RNR.
z Measurement point: This item is measured when LAPD receives RNR frame.
z Formula: none.
VII. BSC num. of retransmissions
z Description: This item measures the times of BSC L2 entity, i.e. LAPD, resending
Frame I (information frame). BSC receiving REJ frame from BTS means that error
occurs when BTS receives Frame I. BSC resends the Frame I of the No. in REJ
frame and all Frame Is after this No. BSC receiving REJ frame from BTS means
that BTS L2 receiver is busy and cannot receive Frame I. BSC resends the Frame
I of the No. in REJ frame and all Frame Is after this No. after the peer end is not
busy. This item increases by 1 when BSC resends a Frame 1.
z Measurement point: This item is measured when LAPD resends Frame I.
z Formula: none.
VIII. BSC num. of received serial number errors
z Description: This item measures the times of inconsistency between expected

serial No. of information frame and the one to be sent after BSC L2 entity, i.e.
LAPD, receives the frame containing expected serial No. of information frame.
The frames of RR, RNR, REJ and I sent from BTS all contain the expected serial
No. of Frame I to be sent from BSC. And BSC records the range of serial No of the
Frame Is. If the received Frame I is not in that range, then this serial No. is
considered to be an incorrect one, and this item increases by 1.
z Measurement point: This item is measured when LAPD receives frames
containing the serial No of expected information frames and the No. is incorrect.
z Formula: none.
IX. BSC num. of receiving layer 3 data requests
the to-be-confirmed information L3 transfer requests. L3 transfer requests can be
divided into two types: one needs to be confirmed and the other needs no
confirming. The former type is transferred with L2 Frame I and the latter one is
transferred with L2 Frame UI. All L3 messages sent by BSC are to be confirmed.
This item increases by 1 if LAPD receives a to-be-confirmed information L3
transfer requests.
z Measurement point: This item is measured when LAPD receives to-be-confirmed
information L3 transfer requests.
z Formula: none.
3-316
X. BSC num. of sending messages
Frame I. Frame I is a numbered information frame. L3 transfer requests can be
transferred with L2 Frame UI. All L3 messages sent by BSC are to be confirmed.
This item increases by 1 if LAPD sends a to-be-confirmed information L3 transfer
requests.
z Measurement point: This item is measured when LAPD sends a Frame I.
z Formula: none.
XI. BSC num. of receiving messages
Frame I. Frame I is a numbered information frame. L3 transfer requests can be
transferred with L2 Frame UI. All L3 messages received by BSC are to be
confirmed. This item increases by 1 if LAPD receives a to-be-confirmed
information L3 transfer requests.
z Measurement point: This item is measured when LAPD receives a Frame I.
z Formula: none.
XII. BSC num. of sending message queue overflows
z Description: L3 transfer requests can be divided into two types: one needs to be
confirmed and the other needs no confirming. The former type is transferred with
L2 Frame I and the latter one is transferred with L2 Frame UI. When sending the
information to be confirmed, BSC L2 entity, i.e. LAPD, put the Frame I in a
message queue to be sent in sequence. If large amount of information is to be sent
within a short period of time by L3, the message queue will overflows, and
message will be lost. This item increases by 1 whenever the message queue
overflows. This situation seldom appears because the processing capacity of
LAPD is powerful and the message queue is long.
z Measurement point: This item is measured when the message queue of Frame Is
sent by LAPD overflows.
z Formula: none.
XIII. BSC num. of receiving long frame errors
z Description: L3 message is sent via L2 to L1. L1 is the physical for sending the
information in the form of physical frame. If error takes place when L1 receives
long frame, then this frame will be discarded, and this item increases by 1.
z Measurement point: This item is measured when L1 of BSC receives incorrect
long frame.
3-317
z Formula: none.
XIV. BSC num. of receiving octets errors
information in the form of physical frame. If L1 receives frames containing byte
errors, then this frame will be discarded; this item increases by 1.
z Measurement point: This item is measured when L1 of BSC receives frame
containing byte errors.
z Formula: none.
XV. BSC num. of receiving give-up serials
information in the form of physical frame. If L1 receives frames containing give-up
serials, then this frame will be discarded; this item increases by 1.
containing give-up serials.
z Formula: none.
XVI. BSC num. of receiving CRC errors
information in the form of physical frame. If L1 receives frames containing CRC
errors, then this frame will be discarded; this item increases by 1.
containing CRC errors.
z Formula: none.
XVII. BSC num. of L1L2 queue overflows
z Description: When receiving message, BSC first receives physical frame via L1,
and then put it in the queue leading from L1 to L2. If large amount of information is
received within a short period of time by L1, the message queue will overflows,
and message will be lost. This item increases by 1 whenever the message queue
overflows.
z Measurement point: This item is measured when the message queue leading from
L1 to L2 overflows.
z Formula: none.
XVIII. BSC num. of received frames by physical layer
z Description: When receiving message, BSC first receives physical frame via L1,
and then put it in the queue leading from L1 to L2. This item increases by 1
whenever L1 receives a physical frame.
z Measurement point: This item is measured when L1 receives a physical frame.
z Formula: none.
3-318
XIX. BTS num. of receiving long frame errors
z Description: This item measures the times of L2 entity in BTS sending SABME
frames. According to the specification of L2, SABME frame is sent to request for
link setup. During the startup and normal operation of BSC, link setup is not
initiated by BTS; so BTS will not send SABME frame to BSC, and that means this
item should be 0. If the link status is abnormal (other than Multi_I), BTS may send
SABME frame to BSC. Note that if the uplink physical link is broken, then even
BTS have sent SABME frame, BSC will have no chance to receive it, so this item
will not increase.
z Measurement point: This item is measured when BTS L2 entity sends a SABME
frame.
z Formula: none.
XX. BTS num. of receiving long frame errors
z Description: This item measures the times of L2 entity in BTS receiving SABME
frames. Normally, SABME frame is sent to request for link setup. After the startup
of BSC, the link status is converted to multi-frame (Multi_I) setup through the
frame interaction between the L2 entities of BSC and BTS. During this procedure,
LAPD sends SABME from to BTS L2 entity. In the normal operation of BSC, if link
status becomes abnormal or physical link between BSC and BTS is broken, BSC
will also send SABME frame to request for link reestablishment.
z Measurement point: This item is measured when BTS L2 entity receives a SABME
frame.
z Formula: none.
XXI. BTS num. of sending long frame errors
z Description: This item measures the times of BTS L2 entity sending REJ frame. In
L2 specification, REJ frame is a monitoring frame which means the received
Frame I (information frame) is refused, and at the same time the Serial No. of
Frame I is expected from the peer end. Frame I is an information frame numbered
in sequence. LAPD has records for the received and sent Frame Is. Normally this
item should be 0. If the BTS receives a Frame I whose No. is not expected, it
sends a REJ frame to BSC, and this item increases by 1. For example, the serial
No. of Frame I expected by BTS is A, while the No. of the received one is B, BTS
sends a REJ frame to request for Frame I whose serial No. is A. If the uplink
physical link is broken, the measurement result cannot be sent to BSC, and this
item will not increase.
z Measurement point: This item is measured when BTS L2 entity sends a REJ
frame.
z Formula: none.
3-319
XXII. BTS num. of receiving long frame errors
z Description: This item measures the times of BTS L2 entity receiving REJ frame.
In L2 specification, REJ frame is a monitoring frame which means the received
Frame I (information frame) is refused, and at the same time the Serial No. of
Frame I is expected from the peer end. Frame I is an information frame numbered
in sequence. LAPD has records for the received and sent Frame Is. Normally this
item should be 0. If the LAPD receives a Frame I whose No. is not expected, it
sends a REJ frame to BTS, and this item increases by 1. For example, the serial
No. of Frame I expected by BSC is A, while the No. of the received one is B, BSC
sends a REJ frame to request for Frame I whose serial No. is A. If the uplink
z Measurement point: This item is measured when BTS L2 entity receives a REJ
frame.
z Formula: none.
XXIII. BTS num. of sending RNRs
z Description: This item measures the times of BTS L2 entity receiving RNR frame.
In L2 specification, REJ frame is a monitoring frame which means the home end is
busy and is not ready to receive the next Frame I and at the same time the Serial
No. of Frame I is expected from the peer end. When the peer end receives, it stops
sending Frame I. if the receiver of BTS is busy, it sends RNR frame to BSC. BSC
stops sending Frame I on reception of RNR. If the uplink physical link is broken,
the measurement result cannot be sent to BSC, and this item will not increase.
z Measurement point: This item is measured when BTS L2 entity sends a RNR
frame.
z Formula: none.
XXIV. BTS num. of receiving RNRs
z Description: This item measures the times of BTS L2 entity receiving RNR frame.
In L2 specification, REJ frame is a monitoring frame which means the home end is
busy and is not ready to receive the next Frame I and at the same time the Serial
No. of Frame I is expected from the peer end. When the peer end receives, it stops
sending Frame I. if the receiver of BSC is busy, it sends RNR frame to BTS. BTS
stops sending Frame I on reception of RNR. If the uplink physical link is broken,
the measurement result cannot be sent to BSC, and this item will not increase.
z Measurement point: This item is measured when BTS L2 entity receives a RNR
frame.
z Formula: none.
3-320
XXV. BTS num. of retransmissions
z Description: This item measures the times of BTS L2 entity resending Frame I
(information frame). BTS receiving REJ frame from BSC means that error occurs
when BSC receives Frame I. BTS resends the Frame I of the No. in REJ frame
and all Frame Is after this No. BTS receiving REJ frame from BSC means that
BSC L2 receiver is busy and cannot receive Frame I. BTS resends the Frame I of
the No. in REJ frame and all Frame Is after this No. after the peer end is not busy.
This item increases by 1 when BTS resends a Frame 1. If the uplink physical link is
broken, the measurement result cannot be sent to BSC, and this item will not
increase.
z Measurement point: This item is measured when BTS L2 entity resends Frame I.
z Formula: none.
XXVI. BTS num. of received serial number errors
z Description: This item measures the times of inconsistency between expected

serial No. of information frame and the one to be sent after BTS L2 entity receives
the frame containing expected serial No. of information frame. The frames of RR,
RNR, REJ and I sent from BSC all contain the expected serial No. of Frame I to be
sent from BTS. And BTS records the range of serial No of the Frame Is. If the
received Frame I is not in that range, then this serial No. is considered to be an
incorrect one, and this item increases by 1. If the uplink physical link is broken, the
measurement result cannot be sent to BSC, and this item will not increase.
z Measurement point: This item is measured when BTS L2 entity receives frames
containing the serial Nos of expected information frames and the No. is incorrect.
z Formula: none.
XXVII. BTS num. of receiving layer 3 data requests
z Description: This item measures the times of BTS L2 entity receiving the
to-be-confirmed information L3 transfer requests. L3 transfer requests can be
transferred with L2 Frame UI. Only MR message in the L3 messages sent from
BTS needs no confirming. This item increases by 1 if BTS L2 entity receives a
to-be-confirmed information L3 transfer requests. If the uplink physical link is
increase.
z Measurement point: This item is measured when BTS L2 entity receives
to-be-confirmed information L3 transfer requests.
z Formula: none.
3-321
XXVIII. BTS num. of sending messages
z Description: This item measures the times of BTS L2 entity sending Frame I.
Frame I is a numbered information frame. L3 transfer requests can be divided into
two types: one needs to be confirmed and the other needs no confirming. The
former type is transferred with L2 Frame I and the latter one is transferred with L2
Frame UI. Only MR message in the L3 messages sent from BTS needs no
confirming. This item increases by 1 if BTS L2 entity sends a to-be-confirmed
information L3 transfer requests. This item increases by 1 if BTS L2 entity receives
a to-be-confirmed information L3 transfer requests. If the uplink physical link is
increase.
z Measurement point: This item is measured when BTS L2 entity sends a Frame I.
z Formula: none.
XXIX. BTS num. of receiving messages
z Description: This item measures the times of BTS L2 entity receiving Frame I.
Frame I is a numbered information frame. L3 transfer requests can be divided into
two types: one needs to be confirmed and the other needs no confirming. The
former type is transferred with L2 Frame I and the latter one is transferred with L2
Frame UI. Only MR message in the L3 messages sent from BTS needs no
confirming. This item increases by 1 if BTS L2 entity receives a to-be-confirmed
information L3 transfer requests. If the uplink physical link is broken, the
z Measurement point: This item is measured when BTS L2 entity receives a Frame
I.
z Formula: none.
XXX. BTS num. of sending message queue overflows
z Description: L3 transfer requests can be divided into two types: one needs to be
confirmed and the other needs no confirming. The former type is transferred with
L2 Frame I and the latter one is transferred with L2 Frame UI. When sending the
information to be confirmed, BTS L2 entity put the Frame I in a message queue to
be sent in sequence. If large amount of information is to be sent within a short
period of time by L3, the message queue will overflows, and message will be lost.
This item increases by 1 whenever the message queue overflows. If the uplink
z Measurement point: This item is measured when the message queue of Frame Is
sent by BTS L2 entity overflows.
z Formula: none.
3-322
XXXI. BTS num. of receiving long frame errors
information in the form of physical frame. If error takes place when L1 receives
long frame, then this frame will be discarded, and this item increases by 1. If the
uplink physical link is broken, the measurement result cannot be sent to BSC, and
this item will not increase.
z Measurement point: This item is measured when L1 of BTS receives incorrect
long frame.
z Formula: none.
XXXII. BTS num. of receiving octets errors
information in the form of physical frame. If L1 receives frames containing byte
errors, then this frame will be discarded; this item increases by 1. If the uplink
z Measurement point: This item is measured when L1 of BTS receives frame
containing byte errors.
z Formula: none.
XXXIII. BTS num. of receiving give-up serials
information in the form of physical frame. If L1 receives frames containing give-up
serials, then this frame will be discarded; this item increases by 1. If the uplink
containing give-up serials.
z Formula: none.
XXXIV. BTS num. of receiving CRC errors
information in the form of physical frame. If L1 receives frames containing CRC
errors, then this frame will be discarded; this item increases by 1. If the uplink
containing CRC errors.
z Formula: none.
3-323
XXXV. BTS num. of L1L2 queue overflows
z Description: When receiving message, BTS first receives physical frame via L1,
and then put it in the queue leading from L1 to L2. If large amount of information is
received within a short period of time by L1, the message queue will overflows,
and message will be lost. This item increases by 1 whenever the message queue
overflows. If the uplink physical link is broken, the measurement result cannot be
sent to BSC, and this item will not increase.
z Measurement point: This item is measured when the message queue leading from
L1 to L2 overflows.
z Formula: none.
XXXVI. BTS num. of received frames by physical layer
z Description: When receiving message, BTS first receives physical frame via L1,
and then put it in the queue leading from L1 to L2. This item increases by 1
whenever L1 receives a physical frame. If the uplink physical link is broken, the
z Measurement point: This item is measured when L1 of BTS receives a physical
frame.
z Formula: none.
3.23 Channel Allocation Measurement Function
Channel Allocation Measurement Function is the basis of evaluating the channel

allocation algorithm, observing channel allocation during system operation, and
locating problems related to channel allocation. To be specific, it provides the
information of the channel distribution at various interference bands, the degree of the
channel interference exceeding the threshold set by Channel II algorithm, times of
various situations happened from channel allocation to seizure and then to call drop
and times of call drops caused by connection failure and error indication. In addition, it
also provides the items such as Successful SDCCH seizure rate after allocation,
Unsuccessful SDCCH seizure rate after allocation and SDCCH call drop rate as the
reference for network operation analysis.
The measurement object of Channel Allocation Measurement Function is the TRX.

User can select the TRX in a cell as the object of statistic task.
Since the items in Channel Allocation Measurement Function are used to observe the
performance of channel allocation algorithm, it should be registered in that case. The
recommended statistic cycle is 60 minutes.
3.23.1 SDCCH Allocation Measurement Function
All the statistic items in this part are listed in Table 3-32.
3-324
Table 3-32 Statistic items in Channel Allocation Measurement Function
No. Item name

1 Average num. of idle SDCCHs in Interf. band 1
6 Num. of the uplink Interf. indication message in seized SDCCH
7 Num. of the downlink Interf. indication message in seized SDCCH
8 SDCCH allocations
9 Successful SDCCH seizures
10 SDCCH seizure failures (caused by channel
11 SDCCH call drops (caused by channel)
12 SDCCH lost radio connections (connection failure)
13 SDCCH lost radio connections (error indication)
14 Successful SDCCH seizure rate after allocation
15 SDCCH seizure failure rate (caused by channel)
16 SDCCH call drop rate (caused by channel
I. Average num. of idle SDCCHs in Interf. band 1
z Description: Interference band is the level rank contained in RF RESOURCE

INDICATION to be reported to BSC by BTS when the channel is idle. There are six
ranks. The level range can be decided with data configuration. Below is the normal
setting:
Interf. 0 -110~-105 dBm
Interf. 1 -105~-98 dBm
The higher rank suggests higher interference level. Normally, an idle channel at Interf. 4
or 5 suggests the existence of interference. This item measures the average times of
the uplink interference level rank of an idle SDCCH of a TRX at Interf. 1 within the
measurement cycle.
z Measurement point: System gets the number of idle SDCCHs at Interf. 1 every five
seconds. At the end of the measurement cycle, the total number from all sampling
points is divided with the times of sampling to get the average number of idle
SDCCHs at Interf. 1.
z Formula: none.
II. Average num. of idle SDCCHs in Interf. band 2

setting:
3-325
Interf. 0 -110~-105 dBm

measurement cycle.
z Formula: none.
III. Average num. of idle SDCCHs in Interf. band 3

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
z Formula: none.
IV. Average num. of idle SDCCHs in Interf. band 4

setting:
3-326
Interf. 0 -110~-105 dBm

measurement cycle.
z Measurement point: System get the number of idle SDCCHs at Interf. 4 every five
z Formula: none.
V. Average num. of idle SDCCHs in Interf. band 5

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
z Formula: none.
VI. Num. of the uplink Interf. indication message in seized SDCCH
z Description: In the application of Huawei II channel allocation algorithm, BSC

calculates the priority rank of channel interference indication according to the
channel interference indication message reported by LAPD module. The priority
rank is the basis for the subsequent channel allocation. LAPD compares the level
3-327
and quality in the measurement report reported by MS via this channel with the
threshold configured to decide whether to send interference indication message to
BSC. If both level and quality exceeds the threshold, LAPD sends interference
indication message to BSC. This item measures the number of uplink interference
indication messages of a SDCCH within the measurement cycle received by BSC.
z Measurement point: This item is measured when BSC receives an uplink
interference indication message of a SDCCH reported by LAPD module.
z Formula: none.
VII. Num. of the downlink Interf. indication message in seized SDCCH

message to BSC. This item measures the number of downlink interference
indication messages of a SDCCH within the measurement cycle received by BSC.
z Measurement point: This item is measured when BSC receives a downlink
interference indication message of a SDCCH reported by LAPD module.
z Formula: none.
VIII. SDCCH allocations
z Description: This item measures the times of BSC radio resource management
module successfully finding idle SDCCH after receiving SDCCH requests,
including the times of successfully preempting SDCCH. BSC sends a CHANNEL
ACTIVATION message to BTS afterwards to activate this SDCCH.
z Measurement point: This item is measured when BSC radio resource
management module finds or preempts an idle SDCCH from the channel resource
table.
z Formula: none.
IX. Successful SDCCH seizures
z Description: This item measures the times of BSC receiving the notification
indicating successful SDCCH seizures after MS successfully seizes the SDCCH
during the procedure of immediate assignment and handover.
1) This item is measured when BTS sends CHANNEL ACTIVATION
ACKNOWLEDGE message to BSC in the immediate assignment procedure.
2) During the procedure of Incoming BSC handover, when the destination cell
receives HANDOVER DETECTION from BTS, this item is measured.
3-328
3) During the procedure of Intra-BSC incoming cell handover, when the

destination cell receives HANDOVER DETECTION from BTS, this item is
measured.
z Formula: none.
X. SDCCH seizure failures (caused by channel)
z Description: This item measures the times of SDCCH seizure failures caused by
unsuccessful channel activation.
z Measurement point: In the immediate assignment procedure, after BSC sends
CHANNEL ACTIVATION to BTS, BTS dose not respond or returns CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this case.
z Formula: none.
XI. SDCCH call drops (caused by channel)
z Description: This item measures the times of SDCCH call drops caused by
unsuccessful message decoding at air interface or radio interface link broken.
1) BTS detects SDCCH radio link failure or hardware link failure, and sends
CONNECTION FAILURE INDICATION to BSC to indicate that call drop
happens at the air interface due to radio link connection failure. This item is
measured when BSC receives this message.
2) BTS sends ERROR INDICATION to BSC due to SDCCH radio link layer
connection abnormal so as to notify BSC the call drop at air interface due to
radio link failure. This item is measured when BSC receives ERROR
INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited
DM response, multiple frame established state (0x05), sequence error
(0x07)).
3) In the process of BSC internal outgoing inter cell handover (SDCCH
handover), this item is measured when waiting for the Internal Handover
Complete message times out.
4) In the process of outgoing inter BSC handover (SDCCH handover), this item
is measured when waiting for the CLEAR COMMAND message with cause of
handover success times out.
z Formula: none.
XII. SDCCH lost radio connections (connection failure)
z Description: BTS detects SDCCH radio link failure, and sends CONNECTION
FAILURE INDICATION to BSC to indicate that call drop happens at the air
interface due to radio link connection failure. This item measures the times of
receiving CONNECTION FAILURE INDICATION (cause: all causes described in
"GSM 0858" except for equipment failure (0X20) and terrestrial channel failure
(0X22)).
3-329
z Measurement point: This item is measured when BSC receives CONNECTION

FAILURE INDICATION (cause: all causes described in GSM 0858 except for
equipment failure (0X20) and terrestrial channel failure (0X22)) from the SDCCH
of objective cell.
z Formula: none.
XIII. SDCCH lost radio connections (error indication)
z Description: BTS sends ERROR INDICATION to BSC due to SDCCH radio link
layer connection abnormal so as to notify BSC the call drop at air interface due to
radio link failure. This item is measured when BSC receives ERROR INDICATION
(cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response,
multiple frame established state (0x05), sequence error (0x07)). See "GSM 0858".
z Measurement point: This item is measured when BSC receives ERROR
INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM
response, multiple frame established state (0x05), sequence error (0x07)) from
the SDCCH of the objective cell.
z Formula: none.
XIV. Successful SDCCH seizure rate after allocation
z Description: This item measures the percentage of times of MS successfully

seizing channels accounting times of BSC successfully allocating channels. See
Successful SDCCH seizures and SDCCH allocations.
z Formula: successful SDCCH seizures / SDCCH allocations
XV. SDCCH seizure failure rate (caused by channel)
z Description: This item measures the percentage of times of unsuccessful MS

seizing channels due to channel related causes accounting times of BSC
successfully allocating channels. See SDCCH seizure failures (caused by channel)
and SDCCH allocations.
z Formula: SDCCH seizure failures (caused by channel) / times of SDCCH
allocations
XVI. SDCCH call drop rate (caused by channel)
z Description: This item measures the percentage of SDCCH call drops (caused by
channel) accounting for successful SDCCH seizures. See SDCCH call drops
(caused by channel) and Successful SDCCH seizures.
z Formula: SDCCH call drops (caused by channel) / successful SDCCH seizures
3-330
3.23.2 TCH Allocation Measurement Function
All the statistic items in this part are listed in Table 3-33.
Table 3-33 Statistic items in TCH Allocation Measurement Function

6 Num. of the uplink Interf. indication message in seized TCH
7 Num. of the downlink Interf. indication message in seized TCH
8 TCH allocations
9 Successful TCH seizures
10 TCH seizure failures (caused by channel)
11 TCH call drops (caused by channel)
12 TCH lost radio connections (connection failure)
13 TCH lost radio connections (error indication)
14 Successful TCH seizure rate after allocation
15 TCH seizure failure rate (caused by channel)
16 TCH call drop rate (caused by channel)
I. Average num. of idle TCHs in Interf. band 1

setting:
Interf. 0 -110~-105 dBm
the uplink interference level rank of an idle TCH of a TRX at Interf. 1 within the
measurement cycle.
z Measurement point: System gets the number of idle TCHs at Interf. 1 every five
points is divided with the times of sampling to get the average number of idle TCHs
at Interf. 1.
z Formula: none.
3-331
II. Average num. of idle TCHs in Interf. band 2

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
at Interf. 2.
z Formula: none.
III. Average num. of idle TCHs in Interf. band 3

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
at Interf. 3.
z Formula: none.
3-332
IV. Average num. of idle TCHs in Interf. band 4

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
at Interf. 4.
z Formula: none.
V. Average num. of idle TCHs in Interf. band 5

setting:
Interf. 0 -110~-105 dBm
measurement cycle.
at Interf. 5.
z Formula: none.
3-333
VI. Num. of the uplink Interf. indication message in seized TCH

indication message to BSC. This item measures the number of uplink interference
indication messages of a TCH within the measurement cycle received by BSC.
z Measurement point: This item is measured when BSC receives an uplink
interference indication message of a TCH reported by LAPD module.
z Formula: none.
VII. Num. of the downlink Interf. indication message in seized TCH

indication message to BSC. This item measures the number of downlink
interference indication messages of a TCH within the measurement cycle received
by BSC.
z Measurement point: This item is measured when BSC receives a downlink
interference indication message of a TCH reported by LAPD module.
z Formula: none.
VIII. TCH allocations
z Description: This item measures the times of BSC radio resource management
module successfully finding idle TCH after receiving TCH requests, including the
times of successfully preempting TCH. BSC sends CHANNEL ACTIVATION to
BTS afterwards to activate this TCH.
z Measurement point: This item is measured when BSC radio resource
management module successfully finding or successfully preempting an idle TCH
after receiving TCH requests.
z Formula: none.
IX. Successful TCH seizures
z Description: This item measures the times of MS successfully seizing the TCHs
allocated by the network during the procedure of very early assignment,
3-334
assignment and handover. Successful directed retries during assignment are also
regarded as successful TCH seizures. After the ASSIGNMENT REQUEST from
MSC is sent to a certain cell of BSC, if this cell has no channel available and
system supports directed retry, BSC will initiate outgoing inter cell handover
according to the adjacent cell information in MS measurement report (MR). In the
case of BSC internal directed retry, the destination cell sends ASSIGNMENT
COMPLETE to MSC, but it is the originating cell that measures this item. Directed
retry takes place only in the procedure of TCH assignment.
z Measurement:
1) In the procedure of very early assignment, this item is measured when BTS
sends CHANNEL ACTIVATION ACKNOWLEDGE message to BSC.
2) If the destination cell of directed retry is from other BSC, after directed retry is
successfully implemented, MSC sends CLEAR COMMAND to originating cell
to clear the original connection. This item is measured when the originating
cell of the local BSC receives CLEAR COMMAND.
3) If the destination cell of directed retry is from local BSC, after directed retry is
successfully implemented, the destination cell notifies the originating cell to
clear the original resource and connection. This item is measured when the
originating cell of the local BSC receives this Internal Clear Request.
4) After successful implementation of TCH assignment, BSC sends
ASSIGNMENT COMPLETE to MSC. This item is measured in this case.
5) During the procedure of Incoming BSC handover (TCH handover), when the
destination cell receives HANDOVER DETECTION from BTS, this item is
measured.
6) During the procedure of Incoming inter cell handover (TCH handover), when
the destination cell receives HANDOVER DETECTION from BTS, this item is
measured.
z Formula: none.
X. TCH seizure failures (caused by channel)
z Description: This item measures the times of TCH seizure failures due to BTS
channel activation failures or unsuccessful MS access the assigned channels
during the procedure of very early assignment, assignment and handover.
1) In the procedure of very early assignment, after BSC sends CHANNEL
ACTIVATION to BTS, BTS does not respond or returns CHANNEL
ACTIVATION NEGATIVE ACKNOWLEDGE. This item is measured in this
case.
2) In the procedure of assignment, after BSC sends CHANNEL ACTIVATION to
BTS, BTS does not respond or returns CHANNEL ACTIVATION NEGATIVE
ACKNOWLEDGE. This item is measured in this case. This item can also be
measured when MS fails to access the assigned channel and returns to the
3-335
original channel and reports this assignment failure via original channel. In
this case, the cause value reported by BSC to MSC is reverting to old channel
(0x0a). If MS can neither access the assigned channel nor return to the
original channel, the cause value reported is radio interface message failure
(0x00). This item is also measured in this case.
3) In the procedure of BSC internal incoming cell handover (TCH handover),
after BSC sends CHANNEL ACTIVATION to BTS, BTS does not respond or
returns CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is
measured in this case. When the destination cell waiting for HANDOVER
DETECTION from BTS times out, is also measured. And when the originating
cell receives HANDOVER FAILURE from MS or CONNECTION FAILURE
INDICATION or ERROR INDICATION from BTS, this item is also measured.
4) In the procedure of incoming inter BSC handover (TCH handover), BSC
sends CHANNEL ACTIVATION to BTS, BTS does not respond or returns
CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE. This item is
5) Formula: none.
XI. TCH call drops (caused by channel)
z Description: This item measures the times of call drops after TCH seizures due to
message decoding failure at air interface or radio link broken
1) BTS detects TCH radio link failure or hardware link failure, and sends
CONNECTION FAILURE INDICATION to BSC to indicate that call drop
happens at the air interface due to radio link connection failure. This item is
measured when BSC receives this message.
2) BTS sends ERROR INDICATION to BSC due to TCH radio link layer
connection abnormal so as to notify BSC the call drop at air interface due to
radio link failure. This item is measured when BSC receives ERROR
INDICATION (cause: timer T200 expired (N200 + 1) times (0x01),
unsolicited DM response, multiple frame established state (0x05), sequence
error (0x07)).
3) In the procedure of BSC internal outgoing inter cell handover, this item is
measured when waiting for the Internal Handover Complete message times
out.
4) In the procedure of outgoing inter BSC handover, this item is measured when
waiting for CLEAR COMMAND with cause of handover success times out.
z Formula: none.
XII. TCH lost radio connections (connection failure)
z Description: BTS detects TCH radio link failure, and sends CONNECTION
FAILURE INDICATION to BSC to indicate that call drop happens at the air
3-336
interface due to radio link connection failure. This item measures the times of
receiving CONNECTION FAILURE INDICATION (cause: all causes described in
"GSM 0858" except for equipment failure (0X20) and terrestrial channel failure
(0X22)).
z Measurement point: This item is measured when BSC receives CONNECTION
FAILURE INDICATION (cause: all causes described in GSM 0858 except for
equipment failure (0X20) and terrestrial channel failure (0X22)) from the TCH of
objective cell.
z Formula: none.
XIII. TCH lost radio connections (error indication)
z Description: BTS sends ERROR INDICATION to BSC due to TCH radio link layer
connection abnormal so as to notify BSC the call drop at air interface due to radio
link failure. This item is measured when BSC receives ERROR INDICATION
(cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM response,
multiple frame established state (0x05), sequence error (0x07)). See "GSM 0858".
z Measurement point: This item is measured when BSC receives ERROR
INDICATION (cause: timer T200 expired (N200 + 1) times (0x01), unsolicited DM
response, multiple frame established state (0x05), sequence error (0x07)) from
the TCH of the objective cell.
z Formula: none.
XIV. Successful TCH seizure rate after allocation
z Description: This item measures the percentage of times of MS successfully

seizing TCHs accounting times of BSC successfully allocating TCHs. See
Successful TCH seizures and TCH allocations.
z Formula: successful TCH seizures / TCH allocations
XV. TCH seizure failure rate (caused by channel)
z Description: This item measures the percentage of times of unsuccessful MS

seizing TCHs due to channel related causes accounting times of BSC successfully
allocating channels. See TCH seizure failures (caused by channel) and TCH
allocations
z Formula: TCH seizure failures (caused by channel) / times of TCH allocations
XVI. TCH call drop rate (caused by channel)
z Description: This item measures the percentage of TCH call drops (caused by
channel) accounting for successful TCH seizures. See TCH call drops (caused by
channel) and Successful TCH seizures.
3-337
z Formula: TCH call drops (caused by channel) / successful TCH seizures
3.24 Cell Flow Control Measurement Function
3.24.1 General
"Cell Flow Control Measurement Function" shows the resources utilization of the cell
and BTS that the cell belongs to. All the statistic items in this part are listed in
Table 3-34.
The statistic items of this measurement type can be registered selectively according to
necessity.
Recommended period: 60 minutes
Measurement object cell
Table 3-34 Statistic items in Cell Flow Control Measurement Function
No. Item name

1 Delete indications
2 CCCH load indications (Circuit RACH overload)
3 CCCH load indications (Circuit PCH overload)
4 TRX overloads (CCCH overload)
5 TRX overloads (TRX processor overload)
6 TCH overloads
7 Load indications to MSC
8 Times of TCH convert to SDCCH
9 Times of SDCCH convert to TCH
I. Delete indications
z Description: When an IMMEDIATE ASSIGN COMMAND message is deleted due

to downlink CCCH overload, BTS reports the DELETE INDICATION message.
This item measures the number of times BSC receives the DELETE INDICATION
message from the current cell within the measurement cycle.
z Measurement point: This item is measured when BSC receives the DELETE
INDICATION message reported by BTS.
z Formula: none.
II. CCCH load indications (Circuit RACH overload)
z Description: When the uplink CCCH (RACH) is overload, BTS sends CCCH LOAD
INDICATION (RACH overload) BSC. Currently Huawei BSS does not support the
RACH overload of packet service; therefore packet call caused RACH overload is
3-338
also regarded as circuit service RACH overload. Besides, when the downlink
CCCH is overload, BTS not only reports overload to BSC, but also distinguishes
between overload caused by packet service and overload caused by circuit
service. In the former case, CCCH LOAD INDICATION is sent to BSC, and in the
latter case, PACKET CCCH LOAD INDICATIN is sent to PCU.
z Measurement point: This item is measured when BSC receives the CCCH LOAD
INDICATION (cause: uplink CCCH (RACH) overload) message from BTS.
z Formula: none.
III. CCCH load indications (Circuit PCH overload)
z Description: BTS stores the downlink CCCH (PCH) messages from BSC and PCU
in different receiving buffer queues. Downlink CCCH overload takes place when
the length of a receiving buffer queue exceeds the threshold. Whether CCCH
LOAD INDICATION is reported to PCU or BSC depends on the overloaded queue.
z Measurement point: This item is measured when BSC receives the CCCH LOAD
INDICATION (cause: circuit service downlink CCCH (PCH) overload) message.
z Formula: none.
IV. TRX overloads (CCCH overload)
z Description: This item measures the number of times BSC receives the
OVERLOAD (cause: CCCH overload) message from the objective cell within the
measurement cycle. That means, when BTS detects CCCH overload, it reports
OVERLOAD (cause: CCCH overload) to BSC, and at the same time, it also
reports CCCH LOAD INDICATION to BSC.
Note:
TRX overload reports (CCCH overload) = CCCH load reports (RACH overload) + CCCH load reports
(PCH overload) (including circuit service and packet service). However, in practice, BER may cause
difference of this equation.
z Measurement point: This item is measured when BSC receives the OVERLOAD
(cause: CCCH overload) message from BTS.
z Formula: none.
V. TRX overloads (TRX processor overload)
z Description: This item measures the number of times BSC receives the
OVERLOAD (cause: TRX processor overload) message from the objective cell
within the measurement cycle. TRX processor overload means the CPU
occupation of the TRX processor under the measured cell exceeds the threshold.
This item has no direct relation with CCCH overload.
3-339
z Measurement point: This item is measured when BSC receives the OVERLOAD
(cause: TRX processor overload) message from BTS.
z Formula: none.
VI. TCH overloads
z Description: On the occasion of TCH flow control, this item is measured when the
number of idle service channels is smaller than the number threshold of service
channels. Whenever this happens, BSC will adjust cell flow ranks, which affects
the minimum access level in the system message issued by BSC. The higher cell
flow rank suggests higher minimum access level, and it is more difficult for MS to
access or camp on the current cell. But in practice, the function of TCH flow control
is prohibited, so the result of this index is 0.
z Measurement point: On the occasion of TCH flow control, this item is measured
when the number of idle service channels is smaller than the number threshold of
service channels.
z Formula: none.
VII. Load indications to MSC
z Description: BSC finds that a cell has no service channel available, but this cell
has been configured with external adjacent cell, to prevent the handovers from
adjacent cell to the current cell, BSC sends LOAD INDICATION to MSC, which
forwards this message to the BSS where the adjacent cell is located. The external
adjacent cell will leave the congested cells out of candidate list. BSC checks the
number of idle service channels every five seconds.
z Measurement point: BSC finds that a cell has no service channel available, but
this cell has been configured with external adjacent cell. to prevent the handovers
from adjacent cell to the current cell, BSC sends LOAD INDICATION to MSC. This
item is measured when BSC sends this message to MSC.
z Formula: none.
VIII. Times of TCH convert to SDCCH
z Description: On the occasion that SDCCH dynamic convert is allowed, if BSC

finds that the number of idle SDCCHs in the current cell is smaller than the number
threshold when allocating SDCCH, it starts to convert a TCH to SDCCH. If the
coverted TCH is idle, TCH is dynamically converted to SDCCH immediately.
Otherwise, the call seizing the current TCH will be handed over to other channel,
and then dynamic convert is initiated. This item is measured when dynamic
convert is implemented.
z Measurement point: This item is measured when BSC initiates TCH dynamic
convert (TCH to SDCCH).
z Formula: none.
3-340
IX. Times of SDCCH convert to TCH
z Description: On the occasion that SDCCH dynamic convert is allowed, BSC first
initiates dynamic convert algorithm (leaky bucket algorithm). When necessary, the
TCH dynamically converted to SDCCH will be converted back to TCH. This item
measures the times of SDCCH converted to TCH.
z Measurement point: This item is measured when a SDCCH is converted back to
TCH.
z Formula: none.
3.25 GPRS Related Measurement Function
3.25.1 General
Huawei BSS consists of BSC, BTS and PCU. The packet data is transferred to the core
network of GPRS via BTS, BSC and PCU. The signaling transmission path is MS
BTS BSC (BSC performs partial management) PCU SGSN.
Huawei BSS system supports the following combined channels:

1) PBCCH + PCCCH + PDTCH + PACCH + PTCCH
2) PCCCH + PDTCH + PACCH + PTCCH
3) PDTCH + PACCH + PTCCH
Note that: PCCCH = PPCH + PRACH + PAGCH + PNCH.
Currently, most MSs does not support the first two types of combined channels, so
CCCH is usually used to realize the function of PCCCH, BCCH realizes the function of
PBCCH. This means that normally only the combination of PDTCH + PACCH + PTCCH
(called PDCH) is applied.
The packet call procedure at BTS-BSC side only consists of immediate assignment
procedure. The immediate assignment process is as follows: MS is accessed the
network via RACH, and It sends CHANNEL REQUEST (contained cause value: Packet
Call (0 x 03)) to request for PDCH. When BSC decides that this request is a packet call
request, it will forward this message to PCU, which will implement channel assignment.
After assigning PDCH, PCU will initiate PACKET IMMEDIATE ASSIGNMENT
COMMAND, which will be transparently transferred by BSC to MS. MS is then notified
to access the assigned PDCH. After access PDCH, MS implements the corresponding
signaling transmission and data transmission. PCU implements packet channel
assignment according to the actual needs of the connection. The signaling concerning
assignment is transmitted on PACCH. The packet service supports cell reselection, not
handover process. When providing packet service, if it is necessary to set up circuit
connection, BSC will notify PCU (then PCU notifies MS) to suspend the packet service,
3-341
and give the priority to circuit service. After the circuit service is complete and the
related link is released, BSC will resume the packet service.
All statistic items related to packet call and PDCH resources in BSS traffic statistic
system are contained in this measurement function, and see Table 3-35 for details. For
cells supporting GPRS, it is recommended to use a task to register these items, both
during the initial operation and normal operation of the network so as to obtain the
information about the implementation of packet call process and utilization of PDCH
resources.
If there are many MSs supporting GPRS in a cell or some MS attach failed, there will be
many Packet immediate assignment requests. It is possible to obtain the information of
packet immediate assignment by comparing "Successful packet immediate
assignments" and "Packet immediate assignment requests". The interface information
tracing function provided by BSC and PCU can be used to trace the information at Pb
interface.
Recommended cycle: 60 minutes
The measurement object of GPRS Related Measurement Function is cell.
Table 3-35 GPRS performance measurement
No. Item name

1 Packet immediate assignment requests
2 Successful packet immediate assignments
3 TCH requires to PCU by BSC
4 Successful TCH requires to PCU by BSC
5 Configured static PDCHs
6 Configured dynamic PDCHs
7 Average availabled PDCHs
8 Max num. of availabled PDCH
9 Min num. of availabled PDCH
I. Packet immediate assignment requests
z Description: The packet call procedure at BSC-PCU side only consists of

immediate assignment procedure, i.e. MS accesses the network via RACH. It
sends CHANNEL REQUEST (contained cause value: Packet Call (0 x 03)) to
request for PDCH. When BSC decides that this request is a packet call request, it
will forward this message to PCU, which will implement channel assignment.
z Measurement point: This item is measured when BSS receives CHANNEL
REQUEST from MS.
z Formula: none.
3-342
II. Successful packet immediate assignments
z Description: On reception of CHANNEL REQUEST forwarded by BSS, PCU

assigns channels, and then initiates PACKET IMMEDIATE ASSIGNMENT
COMMAND.
z Measurement: This item is measured when BSC receives PACKET IMMEDIATE
ASSIGNMENT COMMAND from PCU.
z Formula: none.
III. TCH requires to PCU by BSC
z Description: Huawei BSS supports both static PDCH and dynamic PDCH. On the
occasion of the former one, after GPRS cells start to function, PCU obtains the
right to assign these channels, while BSC only has the right of basic maintenance,
and will not implement the management and allocation of these channels. On the
occasion of dynamic channel, the circuit service and packet service request for
channels to each other when necessary, but the circuit service has the right to
forcedly seize the channel.
z Measurement point: When the circuit service needs to seize or plans to seize the
dynamic PDCH currently seized by packet service, it will send
BSC_PCU_TCH_REQ (Huawei Pb interface message) to PCU. This item is
z Formula: none.
IV. Successful TCH requires to PCU by BSC
z Description: After BSC requires to get back dynamic PDCH from PCU, if PCU
responds and agrees to this requirement, this item is measured.
z Measurement point: This item is measured when BSC receives
PCU_BSC_TCH_ACK (Huawei Pb interface message) from PCU.
z Formula: none.
V. Configured static PDCHs
z Description: This item measures the average number of static PDCHs configured
in a cell in each measurement cycle. This item is measured in sampling
mechanism. BSC check the number of static PDCHs recorded in the database
every five minutes. This number is accumulated within measurement cycle. At the
end of measurement cycle, this accumulated number is divided with the times of
accumulating (times of sampling) to get the value of this item. Therefore, this item
may not be an integer.
z Measurement point: At the end of each measurement cycle, the average number
of static PDCH configured will be calculated and sent to BAM.
z Formula: none.
3-343
VI. Configured dynamic PDCHs
z Description: This item measures the average number of dynamic PDCHs

configured in a cell in each measurement cycle. This item is measured in sampling
mechanism. BSC check the number of dynamic PDCHs recorded in the database
every five minutes. Note that what concerned here is the configuration in the
database. Even if the dynamic PDCH is currently used as TCH by BSC, this item
will still be measured. This number is then accumulated within measurement cycle.
At the end of measurement cycle, this accumulated number is divided with the
times of accumulating (times of sampling) to get the value of this item. Therefore,
this item may not be an integer.
z Measurement point: At the end of each measurement cycle, the average number
of dynamic PDCH configured will be calculated and sent to BAM.
z Formula: none.
VII. Average availabled PDCHs
z Description: This item measures the average number of available PDCHs in a cell
within the measurement cycle, including the cells whose configuration status are
"static PDCH" or "dynamic PDCH" and operation status are "PDCH" (i.e. the
related channels are currently seized by packet service). The channel status can
be either idle or using, but it should be an available channel. This item is measured
in sampling mechanism. BSC check the number of dynamic PDCHs recorded in
the database every five minutes. This number is accumulated within measurement
cycle. At the end of measurement cycle, this accumulated number is divided with
the times of accumulating (times of sampling) to get the value of this item.
Therefore, this item may not be an integer.
z Measurement point: At the end of each measurement cycle, the average available
PDCHs will be calculated and sent to BAM.
z Formula: none.
VIII. Max num. of availabled PDCH
z Description: This item measures the maximum number of available PDCHs in a

cell within the measurement cycle, including the PDCHs whose configuration
status are "static PDCH" or "dynamic PDCH" whose operation status are "PDCH".
The channel status can be either idle or using.
z Measurement point: At the end of each measurement cycle, the maximum number
of available PDCH will be calculated and sent to BAM.
z Formula: none.
IX. Min num. of availabled PDCH
z Description: This item measures the minimum number of available PDCHs in a

cell within the measurement cycle, including the PDCHs whose configuration
3-344
status are "static PDCH" or "dynamic PDCH" whose operation status are "PDCH".
The channel status can be either idle or using.
z Measurement point: At the end of each measurement cycle, the minimum number
of available PDCH will be calculated and sent to BAM.
z Formula: none.
3.26 Overlaid/Underlaid Subcell Measurement
3.26.1 General
When using the function of IUO cell, it is important to reasonably configure the TRXs of
the overlaid subcell and underlaid subcell so that in the wide covered area the
underlaid subcell can be used to provide remote coverage and the overlaid subcell to
bear the traffic; in the dense multiplexing area the less multiplexed TRX frequency (e.g.
BCCH) can be used. With scientific configuration of the parameters related to overlaid
and underlaid power, the system interference can be lowered to the greatest extent.
Overlaid/Underlaid Subcell Measurement Function is used to measure the IUO cell

related indices such as times of overflow and handover success rate. These data can
be used to decide whether the IUO channel allocation and IUO HO parameter
configuration is reasonable.
The task of overlaid/underlaid subcell measurement is the cell. The module No., cell No.
and TRX No. (or all cells in the module) of the task can be configured in Object
Definition. All measurement items are listed in Table 3-36.
Table 3-36 Statistic items in Overlaid/underlaid subcell measurement items
No. Item name

1 Attempted TCH seizures in UnderLaid subcell meeting a TCH blocked state
2 Attempted TCH seizures in OverLaid subcell meeting a TCH blocked state
3 Number of TCH measurement reports in UnderLaid subcell
4 Number of TCH measurement reports in OverLaid subcell
5 Attempted handovers from UnderLaid subcell to OverLaid subcell
6 Attempted handovers from OverLaid subcell to UnderLaid subcell
7 Successful handovers from UnderLaid subcell to OverLaid subcell
8 Successful handovers from OverLaid subcell to UnderLaid subcell
9 Failed handovers from UnderLaid subcell to OverLaid subcell due to congestion
10 Failed handovers from OverLaid subcell to UnderLaid subcell due to congestion
11 Average uplink level of handovers from OverLaid subcell to UnderLaid subcell
12 Average downlink level of handovers from OverLaid subcell to UnderLaid subcell
13 Average timing advance(TA) of handovers from OverLaid subcell to UnderLaid subcell
14 Average uplink level of handovers from UnderLaid subcell to OverLaid subcell
15 Average downlink level of handovers from UnderLaid subcell to OverLaid subcell
16 Average timing advance(TA) of handovers from UnderLaid subcell to OverLaid subcell)
17 Attempted SDCCH seizures in UnderLaid subcell meeting a TCH blocked state
18 Attempted SDCCH seizures in OverLaid subcell meeting a TCH blocked state
19 Number of SDCCH measurement reports in UnderLaid subcell
20 Number of SDCCH measurement reports in OverLaid subcell
21 TCH traffic volume in UnderLaid subcell (ERL)
3-345
22 TCH traffic volume in OverLaid subcell (ERL)

23 Successful handover rate from underlaid subcell to overlaid subcell (%)
24 Successful handover rate from overlaid subcell to underlaid subcell(%)
I. Attempted TCH seizures in UnderLaid subcell meeting a TCH blocked state
z Description: When BSC needs to allocate TCH to MS for some reasons (e.g.
assignment, immediate assignment, intra-BSC handover, inter-BSC handover), it
will first fill the IUO property in the channel request according to the configured
data, and then initiate the channel allocation process. If the requested IUO is
underlaid subcell, but there is no idle TCH in underlaid subcell, this index will
increase by 1. The information of times of IUO TCH overflow can be used to
optimize the IUO channel allocation parameters and IUO handover parameter.
z Measurement point: Measured when the TCH allocated by BSC for MS is in
underlaid subcell, while the underlaid subcell has no idle TCH.
z Formula: none.
II. Attempted TCH seizures in OverLaid subcell meeting a TCH blocked state
z Description: When BSC needs to allocate TCH to MS for some reasons (e.g.
assignment, immediate assignment, intra-BSC handover, inter-BSC handover), it
will first fill the IUO property in the channel request according to the configured
data, and then initiate the channel allocation process. If the requested IUO is
overlaid subcell, but there is no idle TCH in overlaid subcell, this index will
increase by 1. The information of times of IUO TCH overflow can be used to
optimize the IUO channel allocation parameters and IUO handover parameter.
z Measurement point: Measured when the TCH allocated by BSC for MS is in
overlaid subcell, while the overlaid subcell has no idle TCH.
z Formula: none.
III. Number of TCH measurement reports in UnderLaid subcell
z Description: The total number of MRs received from the TCH of underlaid subcell.
When BSS receives the MR from MS, if the serving cell is the underlaid subcell
and currently seizes TCH, this index increases by 1.
z Measurement point: Measured when BSS receives the MR from MS and the
serving cell is underlaid subcell, and currently seizes TCH.
z Formula: none.
3-346
IV. Number of TCH measurement reports in OverLaid subcell
z Description: The total number of MRs received from the TCH of overlaid subcell.
When BSS receives the MR from MS, if the serving cell is the overlaid subcell and
currently seizes TCH, this index increases by 1.
serving cell is overlaid subcell, and currently seizes TCH.
z Formula: none.
V. Attempted handovers from UnderLaid subcell to OverLaid subcell
z Description: Attempts of handover from underlaid to overlaid subcell. The index

will increase by 1 when the serving cell is the underlaid subcell, and after the BSC
handover decision algorithm process, system initiates the handover from
underlaid to overlaid subcell. If the value of this index is too large, the configuration
of IUO HO Data may be not reasonable.
z Measurement point: Measured BSC initiates the handover from underlaid to
overlaid subcell within a cell.
z Formula: none.
VI. Attempted handovers from OverLaid subcell to UnderLaid subcell
z Description: Attempts of handover from overlaid to underlaid subcell. The index

will increase by 1 when the serving cell is the overlaid subcell, and after the BSC
handover decision algorithm process, system initiates the handover from overlaid
to underlaid subcell. If the value of this index is too large, the configuration of IUO
HO Data may be not reasonable.
z Measurement point: Measured BSC initiates the handover from overlaid to
underlaid subcell within a cell.
z Formula: none.
VII. Successful handovers from UnderLaid subcell to OverLaid subcell
z Description: Times of successful handover from underlaid to overlaid subcell. The

index will increase by 1 when the serving cell is the underlaid subcell, and after the
BSC handover decision algorithm process, system initiates a successful handover
from underlaid to overlaid subcell.
z Measurement point: Measured BSC initiates a successful handover from
underlaid to overlaid subcell within a cell.
z Formula: none.
VIII. Successful handovers from OverLaid subcell to UnderLaid subcell
z Description: Times of successful handover from overlaid to underlaid subcell. The

index will increase by 1 when the serving cell is the overlaid subcell, and after the
BSC handover decision algorithm process, system initiates a successful handover
from overlaid to underlaid subcell.
3-347
z Measurement point: Measured BSC initiates a successful handover from overlaid

to underlaid subcell within a cell.
z Formula: none.
IX. Failed handovers from UnderLaid subcell to OverLaid subcell due to

congestion
z Description: When the serving cell is the underlaid subcell, after the BSC
handover decision algorithm process, system initiates a handover from underlaid
to overlaid subcell. This index will increase by 1 if the handover failed due to
overlaid subcell congestion. It is possible to judge whether the TCH configuration
of overlaid subcell is reasonable with this index and "Rank 2" as the reference.
z Measurement point: Measured when the handover within a cell from underlaid to
overlaid subcell failed due to overlaid subcell congestion.
z Formula: none.
X. Failed handovers from OverLaid subcell to UnderLaid subcell due to

congestion
z Description: When the serving cell is the overlaid subcell, after the BSC handover
decision algorithm process, system initiates a handover from overlaid to underlaid
subcell. This index will increase by 1 if the handover failed due to underlaid subcell
congestion. It is possible to judge whether the TCH configuration of underlaid
subcell is reasonable with this index and "Average uplink receiving quality 0".
z Measurement point: Measured when the handover within a cell from ovderlaid to
underlaid subcell failed due to underlaid subcell congestion.
z Formula: none.
XI. Average uplink level of handovers from OverLaid subcell to UnderLaid

subcell
z Description: Average uplink level during the IUO handover from overlaid to
underlaid subcell. When the serving cell is the overlaid subcell, after the BSC
handover decision algorithm process, system initiates a handover from overlaid to
underlaid subcell. The uplink level value in MR will be added to the sum in this
case. The value of this index is generated by dividing the sum with the total times
adding the level values within the measurement cycle. Note that, the
measurement point is at the moment when the handover is initiated. No matter the
handover afterwards is successful or not, the uplink level in MR that triggers the
handover will be measured. This index can be used to judge whether the
configuration of IUO HO Data is reasonable.
z Measurement point: Measured when BSC initiates a handover from overlaid to
z Formula: none.
3-348
XII. Average downlink level of handovers from OverLaid subcell to UnderLaid

subcell
z Description: Average downlink level during the IUO handover from overlaid to
underlaid subcell. When the serving cell is the overlaid subcell, after the BSC
handover decision algorithm process, system initiates a handover from overlaid to
underlaid subcell. The downlink level value in MR will be added to the sum in this
handover afterwards is successful or not, the downlink level in MR that triggers the
z Formula: none.
XIII. Average timing advance(TA) of handovers from OverLaid subcell to

UnderLaid subcell
z Description: Average TA during the IUO handover from overlaid to underlaid

subcell. When the serving cell is the overlaid subcell, after the BSC handover
decision algorithm process, system initiates a handover from overlaid to underlaid
subcell. The TA value in MR will be added to the sum in this case. The value of this
index is generated by dividing the sum with the total times adding the TA values
within the measurement cycle. Note that, the measurement point is at the moment
when the handover is initiated. No matter the handover afterwards is successful or
not, the TA in MR that triggers the handover will be measured. This index can be
used to judge whether the configuration of IUO HO Data is reasonable.
z Formula: none.
XIV. Average uplink level of handovers from UnderLaid subcell to OverLaid

subcell
z Description: Average uplink level during the IUO handover from underlaid to
overlaid subcell. When the serving cell is the underlaid subcell, after the BSC
to ovderlaid subcell. The uplink level value in MR will be added to the sum in this
handover afterwards is successful or not, the uplink level in MR that triggers the
3-349
z Measurement point: Measured when BSC initiates a handover from underlaid to
z Formula: none.
XV. Average downlink level of handovers from UnderLaid subcell to OverLaid

subcell
z Description: Average downlink level during the IUO handover from underlaid to
overlaid subcell. When the serving cell is the underlaid subcell, after the BSC
to ovderlaid subcell. The downlink level value in MR will be added to the sum in
this case. The value of this index is generated by dividing the sum with the total
times adding the level values within the measurement cycle. Note that, the
handover afterwards is successful or not, the downlink level in MR that triggers the
z Formula: none.
XVI. Average timing advance(TA) of handovers from UnderLaid subcell to

OverLaid subcell)
z Description: Average TA during the IUO handover from underlaid to overlaid

subcell. When the serving cell is the underlaid subcell, after the BSC handover
decision algorithm process, system initiates a handover from underlaid to
ovderlaid subcell. The TA value in MR will be added to the sum in this case. The
value of this index is generated by dividing the sum with the total times adding the
TA values within the measurement cycle. Note that, the measurement point is at
the moment when the handover is initiated. No matter the handover afterwards is
successful or not, the TA level in MR that triggers the handover will be measured.
This index can be used to judge whether the configuration of IUO HO Data is
reasonable.
z Formula: none.
XVII. Attempted SDCCH seizures in UnderLaid subcell meeting a TCH blocked

state
z Description: After receiving an SDCCH request, BSC first fill the IUO property in
the channel request according to the data configuration, and then initiates the
3-350
channel allocation process. The value of this index will increase by 1 if the property
of IUO that requests for channel is underlaid subcell while there is no idle SDCCH
in this underlaid subcell. If the times of underlaid signaling channel overflow is
large, the SDCCH configured for underlaid subcell is not enough, which often
results in congestion.
z Measurement point: Measured when the property of IUO that requests for channel
is underlaid subcell while there is no idle SDCCH in this underlaid subcell.
z Formula: none.
XVIII. Attempted SDCCH seizures in OverLaid subcell meeting a TCH blocked

state
z Description: After receiving an SDCCH request, BSC first fill the IUO property in
the channel request according to the data configuration, and then initiates the
channel allocation process. The value of this index will increase by 1 if the property
of IUO that requests for channel is overlaid subcell while there is no idle SDCCH in
this overlaid subcell. If the times of overlaid signaling channel overflow is large, the
SDCCH configured for overlaid subcell is not enough, which often results in
congestion.
z Measurement point: Measured when the property of IUO that requests for channel
is overlaid subcell while there is no idle SDCCH in this overlaid subcell.
z Formula: none.
XIX. Number of SDCCH measurement reports in UnderLaid subcell
z Description: Total number of MRs on the SDCCH of IUO underlaid subcell. The
value of this index will increase by 1 if the serving cell is the underlaid subcell and
SDCCH is currently seized when BSS receives the MR from MS.
serving cell is the underlaid subcell and SDCCH is currently seized.
z Formula: none.
XX. Number of SDCCH measurement reports in OverLaid subcell
z Description: Total number of MRs on the SDCCH of IUO overlaid subcell. The
value of this index will increase by 1 if the serving cell is the overlaid subcell and
SDCCH is currently seized when BSS receives the MR from MS.
serving cell is the overlaid subcell and SDCCH is currently seized.
z Formula: none.
XXI. TCH traffic volume in UnderLaid subcell (ERL)
z Description: Underlaid TCH traffic. This is an analysis index. Unit: ERL. It is

calculated from Number of TCH measurement reports in UnderLaid subcell.
3-351
z Formula: Number of TCH measurement reports in UnderLaid subcell% 0.48 /

Measurement cycle (second)
XXII. TCH traffic volume in OverLaid subcell (ERL)
z Description: Overlaid TCH traffic. This is an analysis index. Unit: ERL. It is

calculated from Number of TCH measurement reports in OverLaid subcell.
z Formula: Number of TCH measurement reports in OverLaid subcell % 0.48 /
Measurement cycle (second)
XXIII. Successful handover rate from underlaid subcell to overlaid subcell (%)
z Description: Success rate of IUO handover from underlaid to overlaid subcell. This
is an analysis index. Unit: %. It is calculated from Successful handovers from
UnderLaid subcell to OverLaid subcell and Attempted handovers from UnderLaid
subcell to OverLaid subcell.
z Formula: Successful handovers from UnderLaid subcell to OverLaid subcell /
Attempted handovers from UnderLaid subcell to OverLaid subcell
XXIV. Successful handover rate from overlaid subcell to underlaid subcell(%)
z Description: Success rate of IUO handover from overlaid to underlaid subcell. This
is an analysis index. Unit: %. It is calculated from Successful handovers from
OverLaid subcell to UnderLaid subcell and Attempted handovers from OverLaid
subcell to UnderLaid subcell.
z Formula: Successful handovers from OverLaid subcell to UnderLaid subcell /
Attempted handovers from OverLaid subcell to UnderLaid subcell
3.27 Cell Frequency Scan
3.27.1 General
Uplink frequency scan function is a Huawei-featured function. It can scan the uplink Rx
level of all the frequencies in GSM900/1800 frequency band, i.e. it can scan the
strength of interference signals in the frequency bands of "890~915M Hz" and
"1805~1880M Hz". The uplink frequency scan function is to test interference. Because
the uplink frequency scan is a test of uplink Rx level, the measurement result reflects
the strength of the signals of the measurement frequency that can be received in the
cell, and can serve as the reference for engineers to select appropriate working
frequencies.
3-352
3.27.2 Principle
On the precondition that normal conversion is not affected, the uplink frequency scan
function utilizes an idle frame on a TCH of the measurement cell to conduct a cyclic test
(When BSC allocates this channel, the TCH on the TRX which BCCH belongs to is
preferred), and scans the uplink Rx level of the designated frequency. TCH is of
26-multiframe structure, and there is one idle frame in each multiframe. So the period of
the idle frame on TCH is "26 multiframe structure*0.577 (burst length)*8 (TDMA frame)
=120ms". In actual application, it takes about 1 minute to scan 50 frequencies. In a
frequency scan task, max. 124 measurement frequencies can be registered. An
ergodic scan approximately takes 3 minutes. Uplink frequency scan is triggered after a
frequency scan traffic statistic task is registered. The measurement shall be stopped
when the traffic statistic task is deleted or suspended.
The measurement result output in Traffic Statistic System is the average value of the
uplink Rx level scanned from the start time of a frequency scan task till the
measurement result is output, but clipping to measurement result is performed
technically. Because an idle frame is adopted for uplink frequency scan, in actual
application, the uplink Rx level of synchronous cells (including the frequencies of the
other TRXs of this cell) cannot be scanned.
The uplink frequency scan function is used to measure the interference level that
affects GSM900/1800 uplink Rx quality in the radio environment. It can measure the
uplink interference of all GSM900/1800 frequency bands. To perform more accurate
measurement for the interference band of idle TCH, please refer to the items in "Cell
Measurement Function" and "Channel Allocation Measurement Function".
Measurement of this interference band only aims at designated frequencies.
Because the main set and sub set levels are reported and processed separately, there
are two statistic values for the uplink frequency scan result of a frequency. The values
adopt "main setlevel/sub set level" form.
The registered task period can be set as per the actual requirement. The min. period is
15 minutes. The object type of a frequency scan traffic statistic task is "cell"
Note:
BTS20 does not support the frequency scan function. The principle of BTS3001C frequency scan function
is similar to that of BTS3X. BTS3001C uses all the timeslots of the 8 TCHs on the whole TRX, so the
precision is comparatively higher. However, normal conversion is interrupted. BTS3001C frequency scan
function is started and controlled by BTS Maintenance System.
3-353
M900/M1800 Base Station Controller Chapter 4 Troubleshooting
Chapter 4 Troubleshooting
4.1 Process of Trouble Shooting
While using BSC traffic statistics system, if there is any phenomenon or fault beyond
your knowledge and no related information can be found in this manual, please
handle this problem following the steps below:
I. Save the location information in time
1) Data necessary for locating a problem:

Assume that OMC-BSC system is installed in the path of "c:\omc" in BAM, then all
task files (including task information and data) and traffic statistics log files can be
found in "c:\omc\bsc\bam\appsvr\stats" in BAM. There are three folders in this path:
"data", "databak" and "log".
There are four types of files in "data" folder:

z PubInfo.tsk: for saving the public information of all tasks registered in this BAM;
z result.buf: buffer file, for saving the result frame sent to the server;
z stxxx.tsk: for saving the private information of each task;
z stxxx.res: for saving the result of each task.
Note:
In the file names above, "xxx" stands for the task No. BSC system allocates a task No. for each
measurement task which has already been registered in BSC successfully. The task No. of one task can
be found in the interface of "Data Query" where there is a window of "SQL Condition Query Statement"
display the task No. as Taskxxx.
"databak" is used to backup the task information and result file when modifying the
task configuration.
There are five files in log folder:

z stats.ver: for saving the information of the version modification made to the BAM;
z system.log: for recording system log;
z osystem.log: system log before saving the file of system.log;
z error.log: for recording the log of errors;
z sysconv.log: operation log of traffic statistics result conversion program;
4-1
Any of above files in the folder "data" will be recreated if it is damaged so that the
system can work normally. However, the original content of this file will be cleared and
all information related to this file will be lost. "stats.ver" in the folder "log" will be
recreated whenever BAM is restarted, and "system.log", "error.log" and "sysconv.log"
will be recreated when they are damaged.
The maximum number of sub-records of No.xxx task results saved in each "stxxx" file
is limited. For permanent task, the number is 65535. For normal task, the number
depends on the days specified. However, due to the space limit (max. 25M each) for
the result files, the number of records in task result file cannot be larger than 32767.
The size of "system.log" also has limit. The default limit is 5M each, but this limit can
be modified by modifying "bam.ini". When the size exceeds the limit, this file will be
backed up to "osystem.log", and at the same time, the original information in
"system.log" is cleared.
The configurations related to traffic statistics in bam.ini is as follows:
[STATISTICS]
INSTALLED=1
Note:
"1" stands for traffic statistics has been installed.
"0" stands for traffic statistics has not been installed.
SYSLOG=1
Note:
"1" stands for system log will be saved.
"0" stands for system log wont be saved.
SYSLOGSIZE=5120
Note:
Size of "system.log". When SYSLOG=0, this file is invalid.
4-2
The BAM log file related to traffic statistics console is in

"c:\omc\bamlog\logdata\operations". "htxxx.log" (xxx is the No. of log file) is for
recording the operations performed on traffic statistics console and the frame
information sent from BAM to BSC and WS.
2) Files necessary for locating problems:
z The folder of stats in [c:\omc\bsc\bam\appsvr] of the BAM or "pubinfo.tsk" in the
folders of "data" and "databak", "stxxx.tsk" and "stxxx.res" of the related task as
well as all files in the folder of "log";
z All BAM log files related to traffic statistics console;
All files in "c:\omc\bamlog\logdata\operations" in the BAM.
z Item file: "bscterm.fml"
This file is normally located in "OMC/SHELL/xxxx/PRMMNG" in WS.
II. Save the BAM printing message in abnormality in time;
While running BSC-BAM from [Start/Programs/Huawei GSM-OMC/ BSC-BAM],

select [Function/SavetoFile] in the interface of BAM Server. And the printing
information should be saved as "txt" file.
III. Troubleshooting;
Make sure to record all operations implemented before the abnormality occurs, such
as operations performed at auto configuration console and data management console,
or dynamic data configuration.
Please also remember to record the measures taken during the process of clearing
the fault according to this chapter.
IV. Contact Huawei's technical support engineers in time.
Please contact the custom support center by the following methods, and provide the
data, file and the operation steps referred above.
z Hotline for technical support: 86-0755-26540036;
z FAX: 86-0755-26540035;
z Email: Support@huawei.com.
4.2 Fault in Starting Traffic Statistics Console
I. Fault description
When registering a traffic statistics task, system prompts The application will exit due
to the error when opening project file. or The application version is incompatible with
project file version, the application will exit.
4-3
II. Cause
1) Item files of the current version which is in the folder of [AutoCfg/msmold/ current
version] in OMC Server are damaged;
2) The version of item file is not consistent with that of the Host selected when
starting the traffic statistics console, and as a result, the traffic statistics console
cannot match the two.
III. Handling
Reinstall BSC operations and maintenance module of Huawei GSM-OMC system or

copy the corresponding version of item files from the server to the version directory.
Caution:
1) Do not modify the item files manually.

2) Do not copy item files from one version directory to a different version directory.
4.3 Operations of Traffic Statistics Task Failed
4.3.1 No Resources Available
When registering a traffic statistics task, if there are over 200 tasks (including
permanent tasks, system will prompt Task num. is more than the front limits or Lack
of resource in the front.
II. Cause
At most 200 tasks or 3000 subtasks can be created at each BM. Currently a BM
supports at most 128 cells. Therefore, under the condition of full configuration,
registering a task of "Cell Measurement Function" whose object is defined as All cells
in the module will register 128 subtasks. When the number of subtasks contained in
the tasks registered in this BM exceeds 3000 or the number of registered task
exceeds 200, system will provide the corresponding prompt of error.
4-4
III. Handling
Register tasks according to the actual situation. Try to avoid registering tasks with the
object of All cells in the module or similar ones. And try not to register the same
statistic items with the same objects in multiple tasks so as to avoid wasting available
resources.
4.3.2 No enough disk space
When registering a traffic statistics task, system prompts No enough disk space in
BAM.
II. Cause
When creating a task, BAM will allocate disk space (25 M at the most) necessary for
saving the corresponding task result file for this task according to task information. If
the current disk space available is smaller than the required, system will give this
prompt.
III. Handling
Sort out the disk space of BAM, and clear the Recycle Bin to prepare enough space
for saving task results.
4.3.3 Task Frame Length Exceeding the restriction of BAM and Host
When registering a measurement task, system prompts Length of Appframe for

register task is beyond the communication limit of BAM and front.
II. Cause
There are restrictions to the length of the communication frame between BAM and
Host. If there are too many objects to register or too many items, the length of the
frame related to task registration may exceed the corresponding restriction, and as a
result, the task cannot be registered successfully.
III. Handling
Reduce the number of objects and items in a task so that the information of the items
selected and object will not both be too large during registration. If the object of a
4-5
certain task is all cells under each module, it is possible to reduce the number of
objects by combining the objects. For example, it is possible to register all cells under
each module instead of each specified cell under this module.
4.3.4 Statistic Item Description Error or Number of Item Error
When registering a measurement task, system will prompt Descriptions of statistic

items is wrong, or statistic items are overmuch.
II. Cause
Each task can have at least 60 original items except for two statistic function types:
Cell Frequency Scan and Receiving Level Measurement Function. Each original
item has its own ID which is the same as the one in the counter of Host. If the
protocols between foreground and background are inconsistent or the number of
registered original items is more than 60, system will prompt measurement items
description error or number of items error.
Note:
The number of original items contained in a measurement task is shown in the table heading of Selected
Items.
III. Handling
Reduce the number of original items contained in a task. If these items are to be
registered, please distribute them to multiple tasks.
4.3.5 Too Large HDD Space Needed for Saving Task Result
When registering a task, system prompts Register task failed: Task need too large
disk space
4-6
II. Cause
The space allocated by BAM for result of each task is 25 M at the most. System will
give this prompt if system finds according to the objects, items and measurement time
of the task that the HDD space needed is larger than 25 M.
III. Handling
1) Do not use the traffic statistics console with version different from the Host to
register tasks;
2) Reduce the number of items or objects involved, shorten the measurement time,
increase measurement period and reduce the time length for saving the
measurement results.
4.3.6 This Statistic Function Type already Exists in Other Tasks
When registering a traffic statistics task, system prompt Failed: Task belongs to this
statistic function type has existed. Can't repeatedly register.
II. Cause
In BSC, some statistic function type can be registered for only once. For example:
CPU Measurement Function, Outgoing Inter Cell Handover Measurement Function,
Incoming Inter Cell Handover Measurement Function, Defined Adjacent Cell
Measurement Function, Undefined Adjacent Cell Measurement Function and Cell
Frequency Scan. If these statistic function types are registered in more than one task,
system will prompt this information.
III. Handling
Avoid registering these statistic types in more than one task.
4.3.7 Other User is Registering Scan Freq. Task
When registering a measurement task, system prompts Failed: Other user is

registering scan freq. task
II. Cause
The task of Cell Frequency Scan cannot be registered in multiple tasks. If tasks of this
statistic function type are registered at multiple WSs, system will give this prompt.
4-7
III. Handling
Avoid registering tasks of Cell Frequency Scan at multiple WSs.
4.3.8 Statistic items cannot be resolved
When registering a task, system prompts Can't resolve computable statistic items.
Maybe items are mistaken, or lack of memory.
II. Cause
The memory of WS is insufficient to resolve the items selected into original items, or
the selected items include customized items, but the formula of the customized items
is not in line with system criterion.
III. Handling
Quit those programs temporary not needed and register the task again. If the
registration fails again, check whether the formula of the customized item is in line
with the criterion. If not, delete the customized item and create another customized
item to register the task.
4.4 Querying Traffic Statistics Result Error
4.4.1 Measurement Result Abnormal after Changing the Time of BAM and
Server
When the time of BAM and Server has been changed, user cannot query the results
of some tasks, or the measurement results are obviously incorrect.
II. Cause
The management of traffic statistics depends greatly on time. A measurement result is

allocated with an index No. according to its time of generation. Its offset in the buffer,
which is the basis for recording measurement result, is also calculated from its time of
generation. If the actual time of outputting result is earlier than the time of the saved
results in the file, this measurement result cannot be saved, and the task results
during this period cannot be queried at the Client.
4-8
For example, the measurement time of a task is 8:00~10:00, and its period is 30
minutes. System has output the results twice at 8:30 and 9:00. While the time of
Server is adjusted to 8:00 at 9:00, as shown in Figure 4-1, at the last result queries,
the results 8:30 and 9:00 are the ones before adjusting the time. After the time is
adjusted, the results during 8:00~9:00 cannot be outputted. The result outputted at
9:30 is actually the result the sums of three periods during 8:00~9:30. This result is
not reliable, and can be ignored. The result at 10:00 will recover to normal.
Before adjusting 8:00 8:30 9:00
After adjusting 8:00 8:30 9:00 9:30 10:00
Time to output 9:30

8:30 9:00 10:00
results
Figure 4-1 Adjusting time
III. Handling
Do not change the time of BAM or Server.
If the time of BAM or Server has been changed, please discard the first outputted
measurement result after adjusting the time.
4.4.2 Task Results Incomplete due to Daylight Savings Time Switching
On the day of time system switching daylight savings time, there is a blank in the
measurement result covering a certain period of time.
II. Cause
On the day of switching time system, the time is switched back for one hour. The
results generated during this period cannot be queried. When switching back to
normal system, there will also be a period of time with no results save due to the
one-hour-long time overlapping.
III. Handling
Configure the time zone in OMC Server and BAM according to actual situation so that
this abnormality will not occur to the countries or areas where daylight savings time
system is not practiced.
4-9
In the areas practicing daylight savings time system, do discard the first outputted
measurement result after the time has been changed.
Do not configure different time zones on the BAMs connected to the same OMC
Server.
4.4.3 Measurement Result of Percentage of CPU Occupation Being 0
Measurement of Percentage of CPU occupation is 0.
II. Cause
If the occupancy of CPU is 0, then the MPU may have been restarted or switched over
during the measurement period, which results in results of this period lost or
unavailable. In this case, the traffic statistics console will use "0" to indicate the
measurement result. The traffic statistics console will indicate the result availability of
each object at Detailed Information. The available ones are marked with "", and the
unavailable ones are marked with "X".
III. Handling
None.
4.4.4 Times of Successful Being 0/ Success rate Being *****
Times of successful is 0, or success rate of is ***** (counter statistics).
II. Cause
Normally only under the situation of task result lost/unavailable, will the successful
times of be 0. In this case, Detailed Information is "".
And normally only in the case of adopting pre-defined items or customized items, will
the success rate of be *****. The pre-defined items and customized items are
calculated from original items. If the measurement result corresponding to
denominator part in the formula of a pre-defined item or customized item is 0, the
measurement result will be "*****".
III. Handling
None.
4-10
4.4.5 Average Inter Arrival Time of Random Access being "*****"
The Average inter arrival time in BSC Measurement Function is "*****".
II. Cause
Average inter arrival time in BSC Measurement Function is obtained in BSC by

dividing the times of channel requests whose cause value is "Call Initiating"
("emergency call" not included) with measurement period. Therefore, if there is no
channel request whose cause value is "Call initiating", the result of this measurement
is "*****". This definition is accord with GSM ETSI 12.04 protocol.
III. Handling
None.
4.4.6 Unknown statistic items Appearing in Item Value of Task Result
When measurement results, Unknown statistic items appears in the item value of
the task result.
II. Cause
This item may have been deleted or the item cannot be found in item file of the current
version due to version mismatching.
III. Handling
1) If a customized item has been deleted, it is necessary to select other items for
this task;
2) Avoid using Clients of different versions to query measurement results;
3) After adding a customized item and using this new customized item to register a
task, make sure to refresh item files at other Clients in time.
4.4.7 "?" Appearing in Task Value of Measurement Result
When querying task results, "?" appearing in the item value of measurement result
and system prompts Illegal statistic item. May have been deleted!
4-11
II. Cause
The calculation formula of this item is invalid, or the original items contained in this
item cannot be found in the item file of the current version due to version mismatching.
III. Handling
1) Check whether the calculation formula of this item is valid;

2) Avoid using Clients of different versions to query measurement results;
4.4.8 Column Irregular
When printing the measurement results, system prompts The font you used may lead
to irregular of the column, a monospaced font for example Courier New is suggested.
Continue? If continue, the columns in the printed result will be in disorder.
II. Cause
Before printing the measurement result, system will calculate the width offset for each
column. If non-monospaced font is selected, the position of the columns may be in
disorder.
III. Handling
Select monospaced font to print measurement result.
4.5 Operations on Template and Item File Failed
4.5.1 Item File or Template Being Modified
When modifying a customized item or template, system prompts Can't save/delete

the template because other users are operating on it. Please try it later. Or Other
user is operating. Please try it later!
II. Cause
The customized items, item templates, time templates and object templates of the
same version cannot be simultaneously modified at different machines.
4-12
III. Handling
Avoid simultaneously modifying the customized items, item templates, time templates
and object templates of the same version, which are connected to the same OMC
Server at different machines.
4.5.2 FTP Connection Failed, Authentication Failed, Sending or Receiving

File Failed
When modifying customized items or various templates, system prompts: Failed to

connect with server by FTP!, Failed to get authentication by FTP!, Failed to send
file by FTP!, Failed to get file by FTP!
II. Cause
The network connecting to OMC Server is abnormal, or the initial information of the
FTP default user configured in OMC Server is modified (e.g. user deleted, password
modified, write right deleted).
III. Handling
1) Check whether the network is correctly connected;

2) Check and restore the default FTP user information configured in OMC Server.
4.6 Response Speed of Traffic Statistics Console Slowing

Down
BAM and application consoles need system resources to operate. Since it is possible
to open multiple application consoles at a BAM from multiple WSs, or open multiple
application consoles at multiple BAMs from WSs, the system resources may be
insufficient for too many applications to operate. In this case, the operation may be
abnormal, and BAM and application consoles (including traffic statistics console) may
not be able to respond for a long time.
If this abnormality occurs, please close the OMC WSs not needed. Try not to open
many application consoles at a BAM from multiple WSs, nor simultaneously carry out
operations of large data size.
4.7 Others
Normally, if abnormality occurs to a measurement task, please deletes the abnormal

task, and then register it again, and the abnormality will be cleared.
4-13
4.7.1 Status of Module in "Task Status" not Reflecting Actual Situation
When querying task status, the status of module in "Task Status" does not reflect the
actual situation.
II. Cause
It is not allowed to continuously click <Task Status> when querying tasks status. A
query should be initiated after the previous one has been done.
III. Handling
Do not click <Task Status> continuously.
4.7.2 "Can't open help file!
When viewing the help file of traffic statistics console, system prompts: Can't open
help file!
II. Cause
System cannot find "Stat_Content.htm" in the current OMC installation path.
III. Handling
1) Make sure that the help file has been installed, and can be found under
"\Help\Stat" in the current OMC installation path. If not, please reinstall the
system;
2) Do not delete this file nor modify its file name.
4.7.3 Converting Result Timeout
When modifying a tasks object, system prompts Modify task failed: Time out to
convert results.
II. Cause
Dynamic configuration may cause task re-registration at the BAM and a lot of task
results may need to be converted. The operation of modify tasks objects also needs
4-14
to convert tasks result. If these two are operated at the same time, there will be many
task results to be converted; as a result, converting result timeout may occur.
III. Handling
Try not to implement object modification when dynamic configuration is underway.
4.7.4 Halting measurement task failed
After halting the measurement task, the icon of the task is changed to be .
II. Cause
There is no response from the processing module of MPU or the communication

connection between MPU and BAM is interrupted.
III. Handling
Check and make sure that the MPU and the connection between MPU and BAM are
normal.
4.7.5 Activating measurement task failed
After activating the measurement task, the icon of the task is changed to be .
II. Cause
A lot of cause will lead to this failure, such as BAM allocating memory failure, no
response from MPU, failure returned from MPU.
III. Handling
1) Check and make sure that the MPU is normal.

2) Check and make sure the communication between BAM and MPU is normal.
3) Check and make sure the task meets the requirement referred in 2.2 Points for
Attention.
4) Activate the task again.
5) Re-register the task with the function of modifying task configuration Information.
4-15
4.7.6 Statistics About TRX
After the dynamic data configuration involving TRX addition/deletion, such as TRX
addition/deletion, CELL TRX addition/deletion, SITE TRX addition/deletion, the result
of the task whose object is TRX will be incorrect for the system reconfiguration.
However, which only affect the task result of the cycle in which the dynamic
configuration is made.
4-16

Traffic Statistic Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Traffic Statistic Manual

Загружено:

Авторское право:

Доступные форматы

Chapter 1 Overview

1.1 Brief Introduction .................................................................................... 1-1

M900/M1800 Base Station Controller

Manual Version T2-031616-20030930-C-4.02

Product Version V300R002

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this document may be reproduced or transmitted in any form or by any

The product version corresponds to the manual is M900/M1800 BSC V300R002.

Organization of the Manual

Chapter 1 is a brief introduction of the fundamental principle of the traffic statistic

Chapter 2 introduces in detail the traffic statistic operations of BSC.

The manual is intended for the following readers:

This document uses the following conventions:

Arial Normal paragraphs are in Arial.

<> Message entered via the terminal is within angle brackets.

Multi-level menus are separated by forward slashes (/). For example,

III. Keyboard operation

Multi-level menu options, e.g. [System/Option/Color setup] on the main menu

IV. Mouse operation

Caution, Warning, Danger: Means reader be extremely careful during the

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Chapter 1 Overview ....................................................................................................................... 1-1

Chapter 2 Operation of Traffic Statistics .................................................................................... 2-1

2.10.3 Creating Object Template ................................................................................... 2-41

Chapter 3 Traffic Statistic Items .................................................................................................. 3-1

3.11.1 General.............................................................................................................. 3-240

3.25.1 General.............................................................................................................. 3-341

Chapter 4 Troubleshooting .......................................................................................................... 4-1

1.1 Brief Introduction

The major achievement includes:

1.2 Contents and Principles of Traffic Statistics

Traffic Traffic Traffic

Figure 1-1 BSC traffic statistics system network architecture

Figure 1-2 BSC traffic statistics system logic structure

Below is the introduction to the functions of each part:

The core function of it is to generate statistics from the result of various

1.3 Concept of Traffic Statistics

1.3.1 Traffic Statistics Task

A measurement task is made up of three elements: statistics time, statistics object,

1.3.2 Index Property

II. Organization mode

It is the basic unit for measurement task to perform data statistics.

1.3.3 Task Object Property

The measurement object is various physical, logical entities or their combinations

1.3.4 Task Time Property

Date Date Date Date Date Date Date Date

Figure 1-3 Basic time type

created on 2002/1/1, started on 2002/1/1 without a termination, this task is a

1.3.5 Measurement task status

The process of measurement task change is shown in Figure 1-4.

Figure 1-4 Measurement task change

1.4 Feature of Traffic Statistics

The task management of traffic statistics includes creating/modifying/deleting

5) Querying task result

II. Template management

III. Customized index

Chapter 2 Operation of Traffic Statistics

The operation of BSC traffic statistics is implemented on WS (Work Station), and it

2.1.1 Brief Introduction

Query task status