Net03 NTWK Perf Gsr7 Inc Amr

NET03 - Network Performance inc AMR
NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories
or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs,
including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer
programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express
written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation
of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or
disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized
copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any
inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes
to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make
changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume
any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR

Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ETSI standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Feature references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Special key sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Definition of Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Example and format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Failure to comply with warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Definition of Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Example and format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
General warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Specific warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Potentially hazardous voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Parts substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Lithium batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 1: BSS Statistics Introduction

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5
Introduction to Statistical Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Health statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Call Model statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
BSS Performance Management (PM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 8
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR i

Contents NET03 - Network Performance inc AMR
Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Message Transfer Link (MTL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Transcoder Base Site Link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
BSS Software Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
BSS — Radio Subsystem (RSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
RSS — Configuration and FM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
RSS - Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
RSS - Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
RSS - A-bis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Handover Detection and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Ladder Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Chapter 2: Statistical Data Types

Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3
Description of statistical data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 4
Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 6
Counter statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 8
CALLS_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 8
Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Counter array example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Gauge statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Duration Example — SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Normal distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Normal Distribution example — INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . 2-20
Weighted Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Weighted Distribution example — BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Counter array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Normal distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Weighted distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Chapter 3: Statistical MMI Commands

Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 3
Displaying Enabled Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 4
Enabling and Disabling Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 6
Changing Statistical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8
ii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

NET03 - Network Performance inc AMR Contents
Changing statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8

Displaying statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8
Setting Bin Ranges for Distribution Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Setting the Statistical Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Displaying the interval timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Note: Clearing statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Displaying Statistical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Chapter 4: Call Statistics

Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 4
Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
INV_EST_CAUSE_ON_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
CHAN_REQ_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
ALLOC_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
BUSY_SDCCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
OK_ACC_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
ALLOC _SDCCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
CHAN_REQ_MS_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
SCCP Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
CONN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
MS_ACCESS_BY_TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
PAGING PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
PAGE_REQUEST_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Paging Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Paging Procedure Continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
ACCESS_PER_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
PAGING_REQUESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Dynamic Allocation RXCDR and BSC Circuits (DARBC) . . . . . . . . . . . . . . . . . . . . . 4-22
AMR Phase 2 GSR7 - See Chapter 10 for AMR Phase 1 Feature . . . . . . . . . . . . . . . 4-22
ATER_CHANNEL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Bin 1 - ATER_CHAN_REQUEST_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Bin 2 - CALL_SETUP_FAIL_COMM_ERR . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Bin 4 - ATER_SWITCH_FAIL_COMM_ERR . . . . . . . . . . . . . . . . . . . . . . . 4-26
Bin 5 - CALL_SETUP_FAIL_NO_ATER. . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Bin 6 - INT_HO_CIC_FAIL_NO_ATER . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Bin 8 - BSC_INIT_BLOCK_CIC_LOW_ATER . . . . . . . . . . . . . . . . . . . . . . . 4-28
Busy CICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR iii

Adaptive Multi-Rate - See Chapter 10 for detail . . . . . . . . . . . . . . . . . . . . . . . . 4-32

AMR Full-Rate Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
AMR Half-Rate Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
MA_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
MA_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
CALL_SP_VERS_DOWNGRADE_MONITOR . . . . . . . . . . . . . . . . . . . . . . . . 4-34
ALLOC_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
ALLOC_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
TCH_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
BUSY_TCH_CARRIER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
BUSY_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
BUSY_TCH_CARR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
TCH_CONGESTION_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Concentric Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
TCH_CONG_INNER_ZONE_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
TCH_USAGE_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Extended Range Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
BSC - BTS Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
DYNET_ASSIGN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
DYNET_CALL_REJECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Assignment Request Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Assignment request queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
CALLS_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
CLR_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Standard Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
CONGEST_ STAND_HO_ ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Non-imperative handover rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Congestion relief handover retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Congestion Relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Congestion relief mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
CONGEST_EXIST_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
CONGEST_ASSIGN_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
TCH Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
ALLOC_TCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
ALLOC_TCH_FAIL_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Blocked and Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
SECOND_ASSIGN_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Assignment delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
TCH_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
TOTAL_CALLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Downlink Bit Error Ratio (BER) Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
iv NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

U_BER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Frame Erasure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
FER_GSM_FR_EFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
FER_AMR_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
FER_AMR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Residual Bit Error Rate (RBER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Interpreting the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
UPLINK_PATH_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Transmit Power Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
CHAN_UL_TX_PWR_LVL and CHAN_DL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . 4-70
Call Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Ciphering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
CIPHER_MODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
RF_LOSSES_TCH_HR_AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Classmark Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
CLASSMK_UPDATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Idle Interference Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
IDLE_TCH_INTF_BAND (n = 0 to 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Available time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
AVAILABLE_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
AVAILABLE_TCH_HR_AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
AVAILABLE_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
SMS Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
SMS_INIT_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Cell Broadcast (CB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
SMS_NO_BCAST_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Emergency Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
NUM_EMERG_REJECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
NUM_EMERG_TERM_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Ater Emergency Pre-empt Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
Bin 1 - EMERG_PREEMPT_ATMPT_CALL_SETUP . . . . . . . . . . . . . . . . . . . 4-86
Bin 2 - EMERG_PREEMPT_ATMPT_ATER_SWITCH . . . . . . . . . . . . . . . . . . 4-86
Bin 3 - EMERG_PREEMPT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
MSC_OVLD_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Call Establishment Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Chapter 5: Handover Statistics

Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Intra-cell handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Intra-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Inter-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Internal/External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 6
Intra-Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR v

Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
INTRA_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
INTRA_BSS_HO_CAUSE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
ER_INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
ER_INTRA_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Intra-Cell Handover Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
INTRA_CELL_EQUIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Mobile Lost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Reason 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Reason 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
INTRA_CELL_HO_LOSTMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
OUT_INTRA_BSS_HO_LOSTMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Call Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
INTRA_CELL_HO_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Intra-Cell Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Neighbour Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
OUT_HO_NC_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Intra-BSS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
IN_INTRA_BSS_NC_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
OUT_INTRA_BSS_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Successful Intra-BSS Handover Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
OUT_INTRA_BSS_HO_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
IN_INTRA_BSS_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
OUT_HO_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
INTRA_BSS_HO_CAUSE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
CONGEST_ASSIGN_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
ASSIGNMENT_REDIRECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Intra-BSS Handover Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
OUT_INTRA_BSS_HO_RETURN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
OUT_INTRA_BSS_EQUIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
IN_INTRA_BSS_HO_RETURN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
IN_INTRA_BSS_EQUIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Mobile Lost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Reason 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Reason 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Reason 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
OUT_INTRA_BSS_HO_LOSTMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Call Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
OUT_INTRA_BSS_HO_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
IN_INTRA_BSS_HO_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Outgoing Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Incoming Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Bad Handover Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Inter-BSS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
vi NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
HO_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
HO_REQ_ACK_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
OUT_INTER_BSS_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
IN_INTER_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
OUT_INTER_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
OUT_HO_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Inter-BSS Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
OUT_INTER_BSS_HO_RETURN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
OUT_INTER_BSS_EQUIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
OUT_INTER_BSS_HO_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
IN_INTER_BSS_EQUIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
OUT_INTER_BSS_HO_LOSTMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
IN_INTER_BSS_MS_NO_SEIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
IN_INTER_BSS_HO_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Outgoing External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Incoming External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Chapter 6: Interface Statistics

Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3
X.25 and Link Access Procedure "D" (LAPD) objectives . . . . . . . . . . . . . . . . . 6- 3
MTP objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3
SCCP objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3
Miscellaneous objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 3
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
OML, RSL and XBL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
MTL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
SCCP performance and utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
MTP C7 performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
MTP C7 availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
MTP C7 utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 4
The X.25 and LAPD protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
HDLC frame structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
Frame check sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 6
The X.25 and LAPD protocols continued . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
HDLC operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
Acknowledged mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
Non-acknowledged mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
HDLC frame types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
Information frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
Supervisory frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
Unnumbered frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6- 8
X.25 and LAPD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
X.25 and LAPD performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
FRMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
INVALID_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
N2_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
X.25 and LAPD utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
I_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
I_FRAMES_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
SABM_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR vii

MTL Interface Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

The C7 protocol - MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
MTP1 - Signalling data link functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
MTP2 - Signalling link functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
MTP3 - Signalling network functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Signalling Units (SUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
The C7 Protocol - MTP continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Flag (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Backward Sequence Number (BSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Backward Indicator Bit (BIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Forward Sequence Number (FSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Forward Indicator Bit (FIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Length Indicator (LI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Signalling Information Field (SIF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Service Information Octet (SIO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Check Bits (CK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
MTP C7 performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
MTP_SL_FAIL and LMTP_SL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
MTP_SL_FIBR and LMTP_SL_FIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
MTP_SL_ERROR_RATE and LMTP_SL_ERROR_RATE . . . . . . . . . . . . . . . . . 6-16
MTP_SL_ACK and LMTP_SL_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
MTP_SL_CONGESTION and LMTP_REMOTE_SL_CONGESTION . . . . . . . . . . . 6-16
LMTP_LOCAL_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
MTP C7 performance continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
MTP C7 performance continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
MTP C7 availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
MTP C7 availability continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
LMTP_SIB_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
MTP C7 availability continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
MTP C7 utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
MTP C7 utilization continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
MTP C7 utilization continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
The C7 protocol - SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
Connectionless. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
Connection-Oriented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
SCCP performance and utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
SCCP performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
BSS Location Services (LCS) - System Overview . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
TA Positioning Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
E-OTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
A-GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
BSS Location Services (LCS) - Network Architecture . . . . . . . . . . . . . . . . . . . . . . . 6-40
GMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
SMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
BSS Location Services (LCS) - Network Architecture . . . . . . . . . . . . . . . . . . . . . . . 6-42
LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Type A LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Type B LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
LMU Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
BSS-Based SMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
BSSMAP_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
BSSMAPLE_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
BSS-Based SMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
LCS Teardown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
BSSMAPLE_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
BSSMAP_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
viii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Perform Location Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48

BSSMAP_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
BSSMAPLE_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . 6-48
Time of Arrival Positioning Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
BSSLAP_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Timing Advance Positioning Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
BSSLAP_TA_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
BSSLAP Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
BSSLAP_RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
E-OTD and A-GPS Positioning Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
Successful Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
BSSLAP_MS_POS_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
BSSLAP_MS_POS_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
Timing Advance Positioning Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
BSSLAP Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
BSSLAP_ABORT_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
BSSLAP_ABORT_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
SMLC-SMLC Messaging (BSS Based SMLC only) . . . . . . . . . . . . . . . . . . . . . . . . 6-60
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
BSSMAP_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
BSSMAP_CONLESS_INFO_SENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
BSSMAPLE_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
BSSMAPLE_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
Processor Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62
CPU_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62
Chapter 7: Key Statistics

Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 3
Introduction — Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 4
Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
TCH channel usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
Call summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
RF loss summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
Link Utilisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 6
SDCCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8
SDCCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8
SDCCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7- 8
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
TCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
TCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
TCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
TCH _MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
MEAN_TCH_BUSY_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
TCH_BLOCKING_RATE_OUTER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
TCH_BLOCKING_RATE_OUTER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Call Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
HANDOVER_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR ix

TOTAL_CALLS_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
SUCCESS_INTERNAL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
UNSUCCESS_INTERNAL_HO_REEST . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
UNSUCCESS_INTERNAL_HO_NOREEST. . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
RF Loss Summary Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
CELL_TCH_ASSIGNMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
ATTEMPTED_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
SUCCESS_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
SDCCH_ACCESS_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
SDCCH_ACCESS_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
MEAN_ARRIVAL _TIME_BETWEEN_CALLS. . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Link Utilisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Chapter 8: Network Health Statistics

Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 3
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 6
DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8- 8
CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
SDCCH_ACCESSES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
SDCCH USAGE STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
SDCCH USAGE STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
TCH_CONGESTION_TIME_OUTER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
TCH_CONGESTION_TIME_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
MEAN_TIME_BETWEEN_HOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
INCOMING_HO_VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
OUTGOING_HO_VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
HANDOVER PERCENTAGE BY CAUSE VALUE . . . . . . . . . . . . . . . . . . . . . . . 8-34
OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
PERCENTAGE_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
x NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

PERCENTAGE_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
PERCENTAGE_INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
PERCENTAGE HANDOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
PAGING_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . 8-44
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS . . . . . . . . . . . . . 8-46
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . 8-48
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . 8-50
OUT_INTER_CELL_HO_FAIL_RECOVER . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-54
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-54
MEAN_TIME_BETWEEN_DROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-56
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF . . . . . . . . . . . . . . 8-58
SPILL_OVER_FACTOR_DIRECTED_RETRY . . . . . . . . . . . . . . . . . . . . . . . . 8-58
SPILL_OVER_FACTOR_MULTIBAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58
Chapter 9: Call Model Statistics

Call Model Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 3
Introduction to call model statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 4
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 4
CALL_DURATION (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 6
CALL_SETUP_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 6
HANDOVERS_PER_CALL (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 8
INTRA_BSS_HO_TO_ALL_HO (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 8
STATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9- 9
STATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
LOCATION_UPDATES_TO_CALLS (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
IMSI_DETACHES_TO_CALL (Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
STATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
LOCATION_UPDATE_FACTOR (L). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
PAGES_PER_CALL (Ppc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
PAGES_PER_SECOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
PAGING_RATE (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Pps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
SMS_TO_CALL_RATIO (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Chapter 10: Adaptive Multi-Rate

Adaptive Multi-Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 3
Adaptive Multi-Rate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 4
AMR Full - Rate Channel Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 4
Full Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 4
AMR Half - Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 4
Half Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 4
AMR Full - Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 6
AMR_FR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 8
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR xi

Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10- 8
AMR_FR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
AMR_FR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
AMR_FR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
AMR Half - Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
AMR_HR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
AMR_HR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
AMR_HR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
AMR_HR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
MS Monitor Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
AMR_INCREASE_THRESH_ADJUST (DECREASE) . . . . . . . . . . . . . . . . . . . . . . . 10-28
Description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
Chapter 11: Appendix A

Control Channels and Multiframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11- 3
Chapter 12: Answers

Call Establishment Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12- 3
Chapter 13: Glossary of Terms

Glossary of technical terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13- 3
A Interface - AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13- 3
B Interface - Byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13- 7
C - CW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
D Interface - DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
E - EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
F Interface - Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
G Interface - GWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
H Interface - Hyperframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
I - IWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
k - KW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
L1 - LV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
M - MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
NACK - nW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45
O - Overlap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
PA - PXPDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-49
QA- Quiesent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
R - RXU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
S7- SYSGEN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61
T -TxBPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
U - UUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
V - VTX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
W - WWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
X - X Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78
ZC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78
xii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

About This Manual Version 1 Rev 4

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 1

Version 1 Rev 4 General information
General information
Important notice
• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or any one acting on the customers behalf, to abide by the instructions, system parameters
or recommendations made in Motorola Customer Product Documentation.
• If this manual was obtained when attending a Motorola training course, it will not be updated or
amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under
normal operational circumstances, to support a major software release, then corrections will be
supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola Technical Training manuals are intended to support the delivery of Technical Training only
and are not intended to replace the use of Motorola Customer Product Documentation.
WARNING Failure to comply with Motorola’s operation, installation and
maintenance instructions may, in exceptional circumstances,
lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola,
although they can be used to supplement and enhance the knowledge gained through such training.
ETSI standards
The standards in the table below able are protected by copyright and are the property of
the European Telecommunications Standards Institue (ETSI).
ETSI specification number

GSM 02.60 GSM 04.10 GSM 08.08
GSM 03.60 GSM 04.11 GSM 08.16
GSM 03.64 GSM 04.12 GSM 08.18
GSM 04.01 GSM 04.13 GSM 08.51
GSM 04.02 GSM 04.60 GSM 08.52
GSM 04.03 GSM 04.64 GSM 08.54
GSM 04.04 GSM 04.65 GSM 08.56
GSM 04.05 GSM 08.01 GSM 08.58
GSM 04.06 GSM 08.02 GSM 09.18
GSM 04.07 GSM 08.04 GSM 09.60
GSM 04.08 GSM 08.06
Figures from the above cited technical specifications standards are used, in this training manual,
with the permission of ETSI. Further use, modification, or redistribution is strictly prohibited. ETSI
standards are available from http://pda.etsi.org/pda/ and http://etsi.org/eds/
2 NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

General information Version 1 Rev 4
General information
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features
released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In
these manuals, new and amended features are tagged to help users to assess the impact on installed
networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research
and Development Prioritization (RDP) numbers. The tags include index references which are listed
in the manual Index. The Index includes the entry feature which is followed by a list of the RDB or
RDP numbers for the released features, with page references and hot links in electronic copy.
The tags have the format: {nnnn} or {nnnnn}
Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
Table 1
New and amended feature information Tag position in text

New sentence/s or new or amended text. Immediately before the affected text.
Complete new blocks of text as follows: Immediately after the headings as follows:
• Full sections under a main heading • Main heading
• Full paragraphs under subheadings • Subheading

New or amended complete Figures and After the Figure or Table number and
Tables before the title text.
Warning, Caution and Note boxes. Immediately before the affected text in the
box.
General command syntax, operator input On a separate line immediately above the
or displays (in special fonts). affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this
software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or
to the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers
and section names. The references to external publications are shown in italics, chapter
and section name cross references are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top
of each page???, and are listed in the table of contents.

Version 1 Rev 4 General information
General information
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM
and GPRS network is encrypted. In order to comply with the export and import requirements of
particular countries, this encryption occurs at different levels as individually standardised, or may not
be present at all in some parts of the network in which it is normally implemented. The manual set,
of which this manual is a part, covers encryption as if fully implemented. Because the rules differ in
individual countries, limitations on the encryption included in the particular software being delivered,
are covered in the Release Notes that accompany the individual software release.
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent
keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
¦ Press the pipe symbol key.
CR or RETURN Press the Return key.

Reporting safety issues Version 1 Rev 4
Reporting safety issues

Whenever a safety issue arises, carry out the following procedure in all instances. Ensure
that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre,
Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and
follow up with a written report by fax, Swindon +44 (0)1793 430987 or China
+86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer
Network Resolution Centre.

Version 1 Rev 4 Warnings and cautions
Warnings and cautions

The following describes how warnings and cautions are used in this manual and
in all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use
of adhesives and solvents, as well as those inherent in the equipment.
Example and format
WARNING Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specific
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customer’s failure to comply with these requirements.
Cautions
A definition and example follow below:
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
CAUTION Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.

General warnings Version 1 Rev 4
General warnings
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
• Potentially hazardous voltage.

• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola
assumes no liability for the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel
working with or operating Motorola equipment must comply with any warning labels fitted to the
equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will
be incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must any
other warnings given in text, in the illustrations and on the equipment. Potentially hazardous voltage
Potentially hazardous voltage
WARNING This equipment operates from a potentially hazardous voltage

of 230 V ac single phase or 415 V ac three phase supply. To
achieve isolation of the equipment from the ac supply, the ac
input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations
1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
NOTE Motorola GSM equipment does not utilise high voltages.
Electric shock
WARNING Do not touch the victim with your bare hands until the
electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating
material and pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even
death, may result. Direct electrical contact can stun a casualty causing breathing, and even the
heart, to stop. It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS
send for trained first aid or medical assistance IMMEDIATELY.

Version 1 Rev 4 General warnings
General warnings
If the casualty is also suffering from burns, flood the affected area with cold water to
cool, until trained first aid or medical assistance arrives.
RF radiation
WARNING High RF potentials and electromagnetic fields are present in this

equipment when in operation. Ensure that all transmitters are switched
off when any antenna connections have to be changed. Do not key
transmitters connected to unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields
High Frequency (10 kHz to 300 GHz).
Laser radiation
WARNING Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or
unterminated fibre optic cables connected to data in/out connectors.
Lifting equipment
WARNING When dismantling heavy assemblies, or removing or replacing

equipment, a competent responsible person must ensure that
adequate lifting facilities are available. Where provided, lifting
frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames
must be used for these operations. When equipments have to be manhandled, reference must
be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual
handling of loads legislation for the country in which the equipment is used.
Parts substitution
WARNING Do not install substitute parts or perform any unauthorized modification

of equipment, because of the danger of introducing additional hazards.
Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
WARNING Do not wear earth straps when working with standby battery supplies.
Lithium batteries
WARNING Lithium batteries, if subjected to mistreatment, may burst and

ignite. Defective lithium batteries must not be removed or
replaced. Any boards containing defective lithium batteries must
be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.

General cautions Version 1 Rev 4
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specific cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes
no liability for the customer’s failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted
to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual.
These must be observed by all personnel at all times when working with the equipment, as must
any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
CAUTION Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
CAUTION Motorola equipment contains CMOS devices. These metal oxide

semiconductor (MOS) devices are susceptible to damage from
electrostatic charge. See the section Devices sensitive to static in
the preface of this manual for further information.

Version 1 Rev 4 Devices sensitive to static
Devices sensitive to static

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied
to the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted together,
for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic
foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
• Always wear an earth strap which must be connected to the electrostatic

point (ESP) on the equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices.
These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible
to electrostatic damage. However PCBs should be handled with care, preferably by their edges
and not by their tracks and pins, they should be transferred directly from their packing to the
equipment (or the other way around) and never left exposed on the workbench.

BSS Statistics Introduction Version 1 Rev 4
Chapter 1
BSS Statistics Introduction
©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 1-1

Version 1 Rev 4 BSS Statistics Introduction
This page intentionally left blank.
1-2 NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Introduction Version 1 Rev 4
Introduction
Objectives
On completion of this chapter the student will be able to:
• Identify the five signalling links within the BSS subsystem infrastructure, indicate their
purpose, bandwidth and Time Slot (TS) allocations.
• Understand the interaction of the Central Statistics Process (CSP) with the
Distributed Statistics Function (DSF).
• Revise their understanding of the main software entities within the BSS and
also the location of these processes.

Version 1 Rev 4 Network Performance
Network Performance
The performance of a network may be monitored and measured. By monitoring the network
performance an indication of the service provided to the subscriber may be measured.
Statistical information is gathered from the network components, this information being
used to monitor and measure the network performance.
Monitoring statistical information provides a “health check " for the network. Problems
can therefore be anticipated and prevented. This information can also be of assistance
during optimization or when a network is to be expanded .
Measuring the performance of the network can supply important information regarding the
quality of service provided to the subscriber (e.g. call setup time).
The statistical information may be gathered over periods of time to gain an insight into
trends on the network (e.g. the busiest call periods).
Motorola Global System for Mobile communication (GSM) Base Station System (BSS) equipment
generates statistical information which may be used to measure the performance of the network.
The statistics are monitored at the Operations and Maintenance Centre (OMC).
During this course the origin of all the statistics output by the BSS will be investigated
and methods for measuring quality of service will be established. Methods of setting up
and displaying statistical information will also be covered.

Network Performance Version 1 Rev 4
Network Performance
Stats information provides a "health check" for the network

Version 1 Rev 4 Introduction to Statistical Types
Introduction to Statistical Types

There are a number of categories of statistics which may be used to monitor network performance.
These are known as Raw, Key, Network Health and Call Model statistics.
The key and health statistics provide a more general picture of how the network is operating. There
are only a limited number of key and health statistics and therefore they are much easier to reliably
monitor. If operators notice a problem with the network when looking at the key statistics they can
then start to study the raw statistics to get a more detailed view of the problem.
The raw statistics and key statistics are described below:
Raw statistics
There are over 100 raw statistics produced by the Motorola BSS equipment which are
sub-categorized into three groups: call statistics, interface statistics and processor utilization
statistics. A description of these statistics is provided below.
• Call statistics
Call statistics are calculated during Call Processing (CP). Call assignments and failures
are monitored along with handover assignments and failures. Also there are many
features within the BSS which are monitored by statistics.
• Interface statistics
Interface statistics relate to activities on the terrestrial interfaces. These interfaces connect
the network components (e.g. Mobile services Switching Centre (MSC) to BSS). Messages
travelling over the interfaces are counted and signalling link outages are recorded.
• Processor utilization statistics
Processor utilization statistics calculate the percentage to which the Generic
Processor board (GPROC) is being utilized.
Key statistics
The Operations and Maintenance Centre (OMC) uses a selection of raw call statistics described above
to calculate key statistics. Key statistics provide the operator with a summary of network performance.
Health statistics
Network health statistics quantify BSS performance from a subscriber perspective. A combination of
raw and other network health statistics are used by the OMC-R to calculate these statistics.
Call Model statistics

These statistics are used to derive the call model values used the plan a network.
Raw statistics are used to calculate their values.

Introduction to Statistical Types Version 1 Rev 4
Introduction to Statistical Types

Raw Statistic Raw Statistic Raw Statistic
Calculation
Key Statistic
Health Statistics
Call Model Statistics

Version 1 Rev 4 BSS Performance Management (PM)
BSS Performance Management (PM)

Before examining the origin of each statistic it is worth noting which software
processes within the BSS collect and upload them.
The Performance Management (PM) applications gather and transport to the OMC the BSS statistics
defined in the software requirements section of the equipment performance specification.
All processes responsible for collecting statistics in the system software will automatically
create a Distributed Statistics Function (DSF) as a sub-process. This DSF is responsible
for collecting and storing all statistics relevant to that process.
The DSF can store up to 12 statistical files, each file containing the statistics (stats) monitored over a set
period. Each statistic gathering period can be set by the operator, this period is one hour or one half-hour.
At a remote Base Transceiver Station (BTS) a Site Statistics Process (SSP) is started, the
SSP is responsible for interfacing to the Central Statistics Process (CSP) located at the BSC
and is used as a message distributor between the CSP and the SSP. The reason for this is
that the CSP does not have to keep track of all the DSFs. Instead for each site it can send
messages to the SSP which will distribute the messages for the CSP.
The Code Object Upload Process (COUP) is utilized to transfer the statistics
gathered by the CSP to the OMC.
The agent process reports statistics threshold alarms and the end of a data collection
interval (file ready event) to the OMC.
Upon request from the OMC or upon the end of a data collection interval (file ready
event), the CSP gathers the statistics from the DSFs and sorts the data and then, using
the COUP the CSP, uploads the statistics to the OMC.

BSS Performance Management (PM) Version 1 Rev 4
BSS Performance Management (PM)
OMCR
OMCR
BSC
Agent COUP
Central Statistics
Central Statistics
Process
Process
(CSP)
(CSP)
BTS
Remote BTS Remote BTS Remote BTS
SSP SSP SSP
DSF DSF DSF DSF DSF DSF

Version 1 Rev 4 Subsystem Interfaces
Subsystem Interfaces
The diagram opposite shows all the interfaces utilized within the Motorola subsystem
infrastructure. Each of these interfaces are statistically monitored.
Message Transfer Link (MTL)

The MTL is the Motorola device name given to the signalling link between the MSC and the BSC.
Each MTL has a bandwidth of 64 kbs and employs the ITU-T SS N o 7 protocol. In the diagram
opposite the MTL is shown cross-connected through the Remote Transcoder (RXCDR) which is
a quite normal practice. Multiple MTLs can be implemented to one BSC up to a maximum of 16.
A MTL could be terminated on any time slot (except 0) at the BSC, although circuit numbering
conventions and hardware reasons always lead the MTL to be placed on time slot 16.
Transcoder Base Site Link (XBL)

The XBL is the Motorola device name given to the Fault Management (FM) link interconnecting
the RXCDR and BSC. The XBL is an essential control link and provides a robust message
link between the RXCDR and the BSC. It allows run-time checks to be performed to confirm
E1/T1 connectivity between the BSC and RXCDR, and also consistency between CIC devices
equipped at the BSC and those at the RXCDR database to support the dynamic allocation of
Ater channels carrying call traffic between the BSC and RXCDR.
The XBL also performs as a fault management link. Using the XBL, if a XCDR/GDP card becomes faulty
the FM in the RXCDR can inform the BSC which incoming traffic circuits are down. The BSC will then be
able to notify the MSC, and this information is passed on the MTL as a "blocking message". The MSC will
block these circuits until it receives an "unblocking message" signifying the traffic circuits are repaired.
The number of XBLs required depends upon the number of CICs and/or the number of Ater
interface channels. A BSC can be connected to a maximum of 9 RXCDRs, and vice versa.
A maximum of 10 XBLs (which may be equipped at 64 kbit/s or 16 kbit/s) can be configured for
each BSC/RXCDR. The XBL can occupy any time slot on the 2Mb trunk and is positioned by a
database command. The minimum number of XBLs required is 1 XBL at 64 kbit/s capacity per 1200
MSC-BSC trunks, or equivalent capacity at 16 kbit/s. The XBL uses the LAPD protocol.

Subsystem Interfaces Version 1 Rev 4
MSC
MTLs OMC
OMLs
OMS OMS
RXCDRs CBC
CBLs
ABSS ABSS
XBL XBL XBL
MTP CBA MTP CBA

BSCs OMS OMS
AXCDR AXCDR
RSLs
BTS BTS BTS BTS

Version 1 Rev 4 Operations and Maintenance Link (OML)
Operations and Maintenance Link (OML)

The Operations and Maintenance Link (OML) is the Motorola device name given to the signalling
connection between OMC and one of two entities, the BSC or RXCDR. A common configuration is
shown opposite. The RXCDR has a single 2 Mbit/s link from the packet switch. Time slot 1 will contain
the OML for the RXCDR, which will be terminated in the operations and maintenance software. The
OML and indeed CBL bound for the BSC are simply cross-connected through the RXCDR. The OML is
a 64 kbs link using the X25 protocol, multiple OMLs (up to 4) can be configured to a single entity. The
link will support a huge range of maintenance traffic. Time slot allocation and 2 Mbit/s termination of
this link is very important and must be consistent with BSS ROM default requirements.
Cell Broadcast Link (CBL)

The Cell Broadcast Link (CBL) is the signalling connection from the BSC to the Cell Broadcast
Centre (CBC). The GSM CBC is responsible for building and maintaining air interface Cell
Broadcast (CB) messages. These messages will be passed to the CB agent in the BSC
on the CBL. The BSC is responsible for their distribution to individual CB schedulers within
each BTS. Once again the CBL utilizes the X.25 protocol and as the diagram opposite
shows it can be cross-connected through the RXCDR. Using current software only one CBL
can be configured, and essentially any time slot can be utilized.
Radio Signalling Link (RSL)

The Radio Signalling Link (RSL) supports traffic signalling and maintenance operations between the
BSC and BTS. The Layer 2 protocol used is LAPD and the bandwidth necessary for each link
is 64 kbs. Multiple radio signalling links can be configured up to a maximum of eight.
InCell — 8
MCell & Horizon Macro — 6, max 2 per E1 span
Horizon 2 Macro — 6, max 4 per E1 span.

Operations and Maintenance Link (OML) Version 1 Rev 4
Operations and Maintenance Link (OML)

MSC
Single 2Mb
OMS
RXCDR OML
OML X.25 OMC
FM CBL
MTL XBL CBL Single 2Mb

OML
CBC
MTP FM CBA
OMS
BSC
RSL
BTS

Version 1 Rev 4 BSS Software Review
BSS Software Review

Before studying call handling and handover statistics it is very important to revise the BSS
software entities involved. Successful CP procedures depend on the interaction and messaging
between individual processes. Whether successful or not each software entity will monitor
every event and increment their own statistics accordingly.
BSS — Radio Subsystem (RSS)

The Radio Subsystem (RSS) is a collection of application processes whose purpose is to manage
the BSS RF hardware to the MSs. The RSS functions include the Layer 2 interface (LAPDm) and
radio link control including the handover detection and power control process.
The RSS part of the BSS implements the interconnection between the
application layer (Layer 3) and the physical channel hardware (Layer 1).
Using In-Cell equipment the RSS software is designed to run on a single GPROC and at
maximum can handle six carriers. Although possible, the handling of this many carriers
could lead to a shortfall in processing power. Multiple instances of RSS software can
co-exist in the same digital cage. Each instance will run on a separate GPROC, usually a
Digital Host Processor (DHP), but also the Base Transceiver Process (BTP) can be used.
For InCell the instance of RSS software must always be located in the same digital
cage as the Digital Radio Interface extended Memory (DRIM) cards it is supporting.
In M-Cell the RSS software will run on the Transceiver Station Manager (TSM) card
within the Transceiver Control Unit (TCU), each instance therefore will handle a single
carrier only. The case of Horizon is similar to M-Cell.
The RSS comprises of five components:

1. RSS configuration and Fault Management (CFM)
2. Layer 1 interface
3. Layer 2 protocol
4. RSS A-bis interface
5. Handover detection and power control (HDPC)

BSS Software Review Version 1 Rev 4
BSS Software Review
Radio SubSystem
Software interface procedures between
BSS RF hardware and mobile station (MS).
One subsystem can support up to 6
carriers (InCell).
MCell - one RSS per carrier
Horizon - one RSS per carrier

Horizon 2 - one RSS per carriers

Version 1 Rev 4 RSS — Configuration and FM Interface
RSS — Configuration and FM Interface

This process controls the configuration of its related radios, and is the interface to the BTS FM
system. It is in charge of hardware configuration, and instructing the radio as to the usage of
each TS (e.g. BCCH, SDCCH or TCH channel. Additionally it is responsible for downloading the
operational software during the initialization of the base site, as well as the loading and configuring
the radio before CP is achieved. Once the site is in CP this process is essentially idle.
RSS - Layer 1
The functions of Layer 1:
• Downloads firmware.
• Message link between RSS - hardware.
• Collects fault information and reports to Fault Collection Process (FCP).
• Scheduling both Access Grant Channel (AGCH) and Paging Channel (PCH)
messages on the air interface.
• Translates downlink layer 2 (LAPDm frames) into DRI/DPR messages.
• Translates Digital Radio Interface (DRI) into Layer 2 messages.
• Supports multiple pages in one message.
• Supports immediate assignments and immediate assignment rejects in one message.
• Layer is responsible for obtaining timer values for non-synchronized handovers
and passing them to the DRI.
RSS - Layer 2
Layer 2 is the link between Layer 1 and the RSS A-bis (Layer 3). The purpose of Layer 2 is to
perform the data link operation as per OSI Layer 2 as specified in TS GSM 04.05 and TS GSM 04.06.
This layer interprets incoming messages from both the Layer 3 interface and Layer 1 interface
and acts on them, for example Layer 2 provides the LAPDm protocol necessary for converting
Layer 3 messages to LAPDm frames which are sent to Layer 1, and vice versa.
Layer 2 is also responsible for establish an Short Message Service (SMS) link to
the MS for the delivery of short messages.
Layer 2 can handle SMS messages up to 255 bytes long. Layer 2 also verifies the SMS messages
and performs any segmentation/reassembling of the SMS messages.
RSS - A-bis
The RSS A-bis provides the interface and message protocol between the RSS and CP.
The RSS A-bis supports a pseudo A-bis interface known as Mobis, designed by Motorola
to conform closely with the GSM requirements but to provide a means for more software
control of hardware and software located at the BTS site.
All messages between CP and RSS go through the RSS A-bis and the Mobis interface to the
Radio Resource State Machine (RRSM) and the Radio Channel Identifier (RCI).
The main responsibilities of the RSS A-bis are as follows:
• Initializing the RSS A-bis
• Checking downlink message validity
• Reporting and logging erroneous states via Software Fault Management (SWFM)
• Translates downlink messages into internal RSS messages
• Translates uplink messages into RSS - CP interface

RSS — Configuration and FM Interface Version 1 Rev 4
RSS — Configuration and FM Interface

FM
CFM
FCP
FTP
DRI
HDPC L1 Um
L2
RSS
A-bis
External to RSS
Within RSS Call Processing

(CP)
RRSM/RCI

Version 1 Rev 4 Handover Detection and Power Control
Handover Detection and Power Control

This process has by far the most functions to fulfil inside the RSS. It controls the transmission power
of the MS (uplink) and also the transmission power of its related radio (downlink) on a per time
slot basis. The object is to keep both the MS and the radio on the lowest possible transmission
power to help reduce interference between system users. This process is also responsible for
calculating the MS’s timing advance to keep the MS inside its allocated time slot.
The handover detection and power control process takes responsibility for initiating
the handover process for a MS. It detects the need for handover based on a number
of criteria set up and optimized in the data base.
Whilst time slots on its related radio are not busy, this process monitors these time slots
to produce a noise interference level for the frequency on which the carrier is operating.
These figures are then passed up to the Layer 3 CP software.
Once a call to a MS has been established, if a MS leaves the system without deregistering,
the system will waste its resources if the MS channel remains in operation. To reduce this, the
handover detection and power control process monitors the Slow Associated Control Channel
(SACCH) messages from all MSs on its radios. If a SACCH message from a MS fails to
appear, the process waits a predetermined time, if still no SACCH message appears, it instructs
the CP software to close down the resources allocated to that MS.

Handover Detection and Power Control Version 1 Rev 4
Handover Detection and Power Control
Functions
Controls transmission power of MS
Controls the timing advance of MS
Controls the transmission power of the BSS
Determine the need for handover (intra-BSS and
inter-BSS)
Monitors the interference level on idle channels
Detects loss of SACCH messages (conserving
resources)

Version 1 Rev 4 Call Processing (CP)
Call Processing (CP)

The purpose of CP) is controlling communication between the MSC, BSC, BTS and MS.
CP and RSS interact to control call setup and clearing, handover, encryption and movement
of Direct Transfer Application (DTAP) messages between the MSC and MS.
CP has been split into 2 levels connected by the Mobis link:
CPBSC Connectionless Manager (CLM)

Message Transfer Part L3 (MTPL3)
Signalling Connection Control Part
(SCCP) pre-processor
SCCP State Machine (SSM).
CPBTS Radio Resource State Machine (RRSM)

Cell Resource Manager (CRM)
Cell Broadcast Scheduler (CBS).

Call Processing (CP) Version 1 Rev 4

Collection of Layer 3 protocols
Functions Call setup/clearing
Message transfer (DTAP/ BSSMAP)
Control handovers
CP RSS interface
Encryption
Allocation of resources
Configuration of logical channels
CPBSC CLM
MTPL3
SSM
SCCP preprocessor
SM
CPBTS RRSM/RCI
CRM
CBS

Message Transfer Part Layer 3 (MTPL3)/SCCP Preprocessor

The MTPL3 is comprised of the MTPL3 and Signalling Connection Control Part (SCCP) preprocessor.
The MTPL3 is responsible for maintaining the signalling link between the MSC - BSS. The process
within MTPL3 is responsible for the data link layer operations of MTP.
The SCCP preprocessor is responsible for determining the type of message (DTAP/BSSMAP)
and then routing the internal message.
SCCP State Machine (SSM)

The SSM maintains the state of the call at the MSC interface. The SSM is responsible for call
initialization, maintenance, release and the primary control of the call during a handover. For all these
activities the SSM can be considered the central hub and decision making process of CP.
The SSM is located at the BSC where it can appear in multiple instances, one
per Link Control Function (LCF).
Connectionless Manager (CLM)

The CLM handles the connectionless procedures of BSSMAP these procedures include,
blocking, reset circuit, global reset and signalling point inaccessible.
The connectionless procedures within GSM are needed to maintain an active interface
with the MSC. The CLM is located at the BSC where a single instance can only be
found on the Base Site control Processor (BSP).
Switch Manager (SM)

The SM supervises the dynamic and static connections implemented by the Kiloport Switch board
(KSW) or Time slot Switch (TSW) card. The SM will be present at every site type and will appear as a
single instance on the master Generic Processor Board (GPROC) device. It can be considered as
part of CP when located at the BSC where it will be controlled by the SSM and prompted to make
Circuit Identity Code (CIC) to Traffic Channel (TCH) connections dynamically. The SM is also involved
in internal handovers, where the CIC trunk is maintained but the TCH must be switched.
Radio Resource State Machine (RRSM)

The RRSM can be considered the centre of CP at the BTS. A single instance only is
necessary and can be found on the BTP. The RRSM will maintain a higher level of control
of the air interface TCH resources. Upon receipt of instructions from the SSM the RRSM
will supervise the activation and deactivation of TCHs. This includes the control of the RSS
software and the compilation of radio resource messages to the MS.


MTPL3 CA
CA
SCCP
SM
Preprocessor
CLM SM
CA
Man Machine
SSM Interface (MMI)
External CP interfaces
RRSM
Internal CP interfacees
RCI
CRM
RSS
RSS A-bis CBS
RSS CM
CA
FM FM
Cell Broadcast
Agent (CBA)
MMI

Radio Channel Interface (RCI)

The RCI performs the routing of messages from the RSS to the CP functions. The
RCI and RRSM validate the uplink messages.
The RCI attaches an SCCP reference number to each uplink message and maintains
an accurate map of these numbers with regard to the RSS. The RCI process provides
a routing and validation function between RSS and CP
The RCI is also responsible for processing requests from the SCCP preprocessor
and distributing paging messages.
Cell Resource Manager (CRM)

The CRM supervises the allocation of available radio resources. It utilises a dynamic data base and
marks the state of each channel (SDCCH & TCH) within each cell it controls. GSM specifications
demand that resources be allocated on a best to worst basis and indeed the CRM maintains an
idle interference reading for each free channel. Not only does the CRM allocate resources but also
provides each connection with a unique identity called the SCCP reference number. The CRM is also
responsible for building system information messages using elements provided by the CM. The CRM
also provides all the necessary information for the configuration of each logical channel. A number of
BSS features are also supervised by the CRM, SDCCH dynamic reconfiguration and TCH flow control.

MTPL3 MSC
CA
SCCP
SM
Preprocessor
CLM SM
CA
MMI
SSM
External CP interfaces
Internal CP interfacees
RRSM
RCI
CRM
CBS
RSS
CBS CM
RSS A-bis MMI
CA FM

Version 1 Rev 4 Ladder Diagrams
Ladder Diagrams
Many statistics within CP are based on the arrival or nonarrival (timer expiry) of BSS defined messages.
These interprocess messages are shown as a straight line between two software processes, above the
line will be the title of the message. The diagram opposite shows the framework of a ladder diagram
less the messages. From this diagram the location and GPROC device type should be carefully
noted, as these details are omitted from the working diagrams. The transmission mechanism of these
messages is complex and an explanation is unnecessary for the subject matter covered by this course.

Ladder Diagrams Version 1 Rev 4
Ladder Diagrams
BTS BSC
MS RSS CRM RRSM SSM SM MTP MSC
Initiate assignment
DHP/TCU/CTU BTP LCF BSP

(multiple) (single) (multiple) (single)

Version 1 Rev 4 Ladder Diagrams

Statistical Data Types Version 1 Rev 4
Chapter 2
Statistical Data Types

Version 1 Rev 4 Statistical Data Types

Objectives
• Name the six statistical data types.
• Describe how each of the statistical data types collect information.
• State the results each statistical data type will output.


Description of statistical data types
There are six statistical data types. Every statistic considered during this course will comprise
of one of these types. Most statistics are either counters or durations, these are the simplest
data types. The six statistical data types available are listed below:
• Counter
• Counter array
• Gauge
• Duration
• Normal distribution
• Weighted distribution
During this section a detailed description of each of these types will be given
along with examples where appropriate.

Counter Cumulative value (+) Counter Array

Cumulative value
Bin array
A B C D E F G H I J
Duration Gauge
Cumulative value (+time) MAX
Mean
Minimum 12 TICK
Maximum TICK 9 3
6
TICK Mean value (+/-)
Maximum
Bin value (+) Normal Distribution

Mean
Minimum
Maximum
Weighted Distribution
Bin value (+time)
Mean TICK TICK TICK TICK
0 1 2 3 4 5 6 7 8 9 Minimum 12 12
9 3 TICK 9 3 TICK
Maximum 6 6
0 1 2 3 4 5 6 7 8 9

Counter
The counter cumulative value is pegged by n (the reported value) each time a report is
made by the application process. Therefore, the counter cumulative value represents
the number of occurrences of an event within an interval.
A threshold value may be specified in the case of alarm generating counters.
An event is reported to the OMC when the threshold value is reached. The event will
only be reported once during an interval if a threshold is reached, for it does not report
multiple events if the threshold has been exceeded.


Counter
Report Produced
Increment cumulative value by n.
Value (n)
Application Process
Statistical interval expired
FINAL REPORT
Cumulative value
12
Final Report
9 3

Counter statistic example

CALLS_QUEUED
After the MS has successfully completed call set-up on the SDCCH the next stage is for the network
to transfer the MS to a TCH, this process is called the assignment procedure. .
The assignment procedure is initiated by the MSC by sending the assignment request
message to the SSM, this message includes the characteristics of the channel required
and the CIC trunk to be used on the A-interface.
Before making any trunk connections the SSM will send the initiate assignment message to
the RRSM requesting that suitable resources be activated in respect of this MS connection.
The RRSM will send an assignment resource request to the CRM, which holds a dynamic
data base denoting individual TCH availability. If no resource of the correct type is available
the request may be queued, depending upon data base parameters and message contents.
If the request can be queued then the force queue message is sent to the RRSM. For every
channel request which is queued this counter statistic is incremented


Counter Example:
CALLS QUEUED
MSC
SSM
SS
RRSM
Assignment request
Initiate assignment
CRM
Assignment resource
request
No TCHs available
Force
orce queue
Assignment queued
pegs: CALLS_QUEUED Queueing indication

Counter Array Statistic

A counter array statistic is an enhancement of the simple counter, in that the total figure reported
is supplemented with a categorical breakdown using up to 16 bin counters. Each bin value will
represent a particular category depending on the statistic being monitored.
Depending upon the number of bins required in the array, the array can be small (4 bins),
medium (8 bins), large (12 bins) or extra large (16 bins). This number is not configurable,
but is preset in software for each relevant statistic.
Counter array example

When the SSM receives a handover recognized message it will analyse the cause value
before executing the appropriate handover type. At this point in time the message is also
used to increment handover cause statistics. The cumulative value is incremented for each
handover attempted, whilst the appropriate bin is also incremented depending on the cause
value. Ten bins are utilized with the following fixed designations:
0 - UPQUAL
1 - UPLEVEL
2 - DOWNQUAL
3 - DOWNLEVEL
4 - DISTANCE
5 - UPINTERF
6 - DOWNINTERF
7 - POWERBDGT
8 - CONGESTION
9 - ADJ_CHAN_INTF
10- NON IMPERATIVE MULTIBAND
At the end of the statistical interval the cumulative total is reported along with the bin
array, showing the cause values that make up this total.


Counter Array
Report Produced
Increment cumulative counter by 1
Increment relative bin by 1
Application Process Cause
A B C D E F G H I J K L
FINAL REPORT
12 Cumulative total
Final Report Bin array
9 3
TICK
12
6 9 3 TICK
6
TICK

Gauge
The gauge current value is incremented or decremented by n (the reported value)
each time a report is made by the application process. A gauge adjusts readings that
monitor occurrences of an event within an interval.
A threshold value may be specified in the case of alarm generating gauges. An event is reported to the
OMC when the threshold value is reached. The event will only be reported once during an interval if a
threshold is reached, for it does not report multiple events if the threshold has been exceeded.
At the end of the interval, gauge statistics give the average value and maximum
value achieved during that interval.
Gauge statistic example

PCH_AGCH_Q_LENGTH
This gauge statistic tracks the average number of paging or access granting messages queuing to
be transmitted. It is pegged by the RSS Layer 1 software every paging multirame.


Gauge
Report Produced
Increment/decrement current value by n.
Store Maximum value
MAX
Application Process Value (n)

FINAL REPORT
Mean Value
12 Maximum Value MAX
Final Report
9 3

Duration
The duration cumulative value is kept by the application process by starting and stopping the timer
when events begin and cease respectively. The time in between these reports is recorded as a
cumulative time value. All durations report cumulative values in milliseconds (msec).
The duration maximum and minimum values are saved and reported at the end of the interval.
The duration mean value is calculated each time a report is made.


Duration
Report Produced Increment cumulative value by duration

Increment number of samples
Store minimum value
Application Process Store maximum value
TICK Value (n)
TICK 12
9 3
TICK 12 TICK
Start 6
Stop TICK 9 3
6
TICK

FINAL REPORT
Cumulative value
12 Minimum value
Final Report Maximum value
9 3 Mean value 12 TICK
TICK 9 3
6 6
TICK

Duration Example — SDCCH_CONGESTION

When a channel request is received the network will try to assign an SDCCH subslot. The channel
request is passed up to the RRSM which in turn solicits the CRM for an available SDCCH. If
available, the CRM will assign one by returning the channel assigned message to the RRSM.
If the last available SDCCH was assigned then an internal timer is started at the CRM. This
timer is stopped only when an SDCCH subslot next becomes available.


Duration Example
SDCCH_CONGESTION
MS RSS RRSM CRM
Channel request
Channel request
Channel request
received
Channel assigned If last SDCCH assigned
start timer
RF channel released
Stop timer when the
ack. received
first SDCCH becomes
available
Elapsed time update:

SDCCH_CONGESTION

Normal distribution
Normal distribution statistics record the number of times a statistical element is at a specific value.
This statistic type allocates the data collected into ‘bins. There are 10 bins available. Bin
ranges for the 10 bins may be set up for each individual distribution statistic (default values
may also be used). When the application process reports an event the bin representing
the reported value of the event is then incremented by one.
Two additional measurements are also required: the number of samples and the cumulative value.
When an event is reported the number of samples is incremented by one and the cumulative value is
updated by the reported value. These two measurements are used to calculate the mean value.
The distribution maximum and minimum values are saved throughout the interval and reported
at the end of the interval. The duration mean value is calculated each time a report is made.
An array of values representing the total counts per bin is also reported.


Normal Distribution
Report Produced Increment cumulative value by reported value n

Increment relative bin by one
Value (n) Increment number of samples by one
Store minimum value
Application Process
Store maximum value
0 1 2 3 4 5 6 7 8 9

FINAL REPORT
Bin array
12 Minimum value
Final Report
9 3 Maximum value
Mean value
6
0 1 2 3 4 5 6 7 8 9

Normal Distribution example — INTF_ON_IDLE
Every Time Division Multiple Access (TDMA) frame each idle time slot is monitored for interference,
these values are reported using the scale 0-63 (-110 to -47dBm). The HDPC will average these
interference levels using an unweighted algorithm and produce a value representing the interference
level on a SACCH multiframe basis. This value increments the cumulative total for this statistic and will
also cause the appropriate bin and the number of samples count to be incremented by one.


Normal Distribution Example
INTF_ON_IDLE
HDPC
Carrier
Interface level 0-63
Averaging
process
Value produced
every 480ms
Cumulative value
Appropriate bin
Increment number of
samples by one

Weighted distribution statistics record the duration for which a statistical element is at a specific value.
This statistic type allocates the data collected in to bins. The data placed into the
bins is weighted by time. Bin ranges for the 10 bins may be set up for each individual
distribution statistic (default values may also be used).
The application process reports the start of the distribution at a particular value and updates it
when a change in the value occurs. This procedure starts and stops internal timers which compute
the duration of an activity. Weighted distributions increment the bin count by the amount of time
(in ms) that the statistic had the given value. When an event is reported the number of samples
is incremented by the time difference and the cumulative value is updated by the time difference
multiplied by the bin value. At interval expiry the mean value is calculated.
The statistic result consists of an array of values representing the total time in which the value
was active per bin and a mean across all bins. The distribution maximum and minimum values
are also saved throughout the interval and reported at the end of the interval.


Report Produced Increment relevant bin by duration

Increment cumulative value by (duration xn)
Value (n) Increment number of samples by the duration
Duration
Application Process Store minimum value TICK TICK
TICK TICK TICK
TICK 12
Store maximum value 12 12
9 3
TICK 9 3 TICK 9 3 TICK
Start 6
Stop 6 6
0 1 2 3 4 5 6 7 8 9

FINAL REPORT
Bin array
12 Minimum value
Final Report TICK TICK TICK TICK
Maximum value 12 12
9 3 Mean value
9 3 TICK 9 3 TICK
6 6
6
0 1 2 3 4 5 6 7 8 9

Weighted Distribution example — BUSY_TCH
After the MS has successfully completed call set-up on the SDCCH the next stage is for the network
to transfer the MS to a TCH, this process is called the assignment procedure. The assignment
procedure is initiated by the MSC by sending the assignment request message to the SSM, this
message includes the characteristics of the channel required and the CIC trunk to be used on the
A-interface. Before making any trunk connections the SSM will send the initiate assignment message
to the RRSM requesting that suitable resources be activated in respect of this MS connection. The
RRSM will send an assignment resource request to the CRM, if the CRM is able to allocate the
required resources it will return an assignment channel assigned message detailing the resources
to be used. Upon allocating these resources the CRM will update this statistic.


Weighted Distribution Example
BUSY_TCH
CRM RRSM SSM MSC

Assignment request
Initiate assignment
Assignment resource
request
BUSY_TCH
Assignment channel
assigned

Summary
Counter
Counts the number of occurrences of an event.
Counter array
Counts the number of occurrences of an event with a breakdown of applicable causes.
Gauge
Reports the mean and maximum value of the statistic in question. Incremented
or decremented when an event is received.
Duration
Measures the duration of an event.
Normal distribution
Records the number of times a statistical element is at a specific value.
Weighted distribution
Records the duration for which a statistical element is at a specific value.


Summary
Counter Cumulative value (+) Counter Array

Cumulative value
Bin array
A B C D E F G H I J
Duration
Gauge
Cumulative value (+time)
Mean MAX
Minimum 12 TICK
Maximum TICK 9 3
6
TICK
Mean value (+/-)
Maximum
Bin value (+) Normal Distribution

Mean
Minimum Weighted Distribution
Maximum
Bin value (+time)
Mean TICK TICK TICK TICK
0 1 2 3 4 5 6 7 8 9 Minimum 12 12
9 3 TICK 9 3 TICK
Maximum 6 6
0 1 2 3 4 5 6 7 8 9


Statistical MMI Commands Version 1 Rev 4
Chapter 3
Statistical MMI Commands

Version 1 Rev 4 Statistical MMI Commands

Statistical MMI Commands Version 1 Rev 4
Statistical MMI Commands
Objectives
• Enable and disable raw statistics.
• Display statistical information including:
a. Parameter values which are set for specific statistics.
b. List statistics which are currently active.
c. Statistical data for a chosen statistical interval.

• Set thresholds for alarm statistics.
• Initialize bin ranges for distribution statistics.

Version 1 Rev 4 Displaying Enabled Statistics
Displaying Enabled Statistics

The disp_enable_stat command will cause the BSS to generate a list of the currently enabled statistics
for the specified argument. The argument is optional and may be omitted. If so the complete list of
enabled statistics will be displayed including cell related (per cell cell id) and non-cell related.
The argument used will abbreviate the list down to a specified cell or location. It is possible to
specify a statistical name, if so the display will return a list of all cell/sites in the BSS where that
statistic has been enabled. Examples of this display command are in the W56 manual.

Displaying Enabled Statistics Version 1 Rev 4
Displaying Enabled Statistics
disp_enable_stat [ * ]
* <cell_number>
<cell_name>
<bss>
<meas_type>
<location>

Version 1 Rev 4 Enabling and Disabling Statistics
Enabling and Disabling Statistics
Statistics will not be collected unless enabled prior to the start of a statistical period. The
stat_mode command is used to enable or disable specific statistics within the CM database.
There are some statistics that are enabled in the CM database by default, a list of these and
further examples of this command can be found on page 2–2 in the W56 manual.

Enabling and Disabling Statistics Version 1 Rev 4
Enabling and Disabling Statistics
stat_mode <meas_type> mode [<location>][<cell_desc>]
meas_type - Name of statistic
mode - On or Off
location - 0 or bsc
1 - 100
all
cell desc - cell id

cell name
all

Version 1 Rev 4 Changing Statistical Properties
Changing Statistical Properties
Changing statistical properties

The chg_stat_prop command is used to change the properties (but not the interval) of a statistic
. The properties that can be altered are dependent on the statistical type specified:
• The alarm threshold can be changed for counter, counter array and gauge statistics if applicable.
• Bin ranges may be changed for normal and weighted distribution statistics.
• Properties may not be changed for durational statistics.
After the command line the system will prompt for further information depending upon
the above, examples can be found in the W56 manual.
Displaying statistical properties

Statistical properties can be displayed by use of the disp_stat_prop command. This
command will cause the system to display the current properties of the specified statistic,
the information and presentation format are dependent upon the statistic type. Examples
of system outputs can be located in the W56 manual.

Changing Statistical Properties Version 1 Rev 4
Changing Statistical Properties

chg_stat_prop<meas_type> [<location>][<cell_desc>]
meas_type - Name of statistic

location - 0 or bsc
1 - 100
all
cell desc - cell id
cell name
all
prompts follow
Displaying Statistical Properties

disp_stat_prop<meas_type>[<location>][<cell_desc>]

Version 1 Rev 4 Setting Bin Ranges for Distribution Statistics
Setting Bin Ranges for Distribution Statistics
A bin is a range which records the number of times or the length of time for which an
event occurs. Therefore, a bin represents a `pool of data"
Normal distribution statistics record how often a particular event or state-change occurs.
Normal distribution bins contain a count.
0 1 2 3 4 5 6 7 8 9
Weighted distribution statistics record the time (in milliseconds) that an element is at a
specific value. Weighted distribution bins contain a duration.
12 TICK 12 TICK
9 3 9 3
6
TICK 6
TICK
TICK TICK
0 1 2 3 4 5 6 7 8 9
The bin ranges are set in exactly the same way for both normal and weighted distribution
statistics. Each bin has a maximum and a minimum value, these values determine the
range of values which may be placed in that bin.
30 45 71
0 1 2 3 4 5 6 7 8 9
min=0 min=11 min=21 min=31 min=41 min=51 min=61 min=71 min=81 min=91
max=10 max=20 max=30 max=40 max=50 max=60 max=70 max=80 max=90 max=100
The bin range for each bin may be made as large or as small as the operator requires,
each bin may have a different size range. The total number of bins never changes.
The diagrams opposite illustrate various scenarios which require the bin ranges to be
sized in different ways.

Setting Bin Ranges for Distribution Statistics Version 1 Rev 4
Setting Bin Ranges for Distribution Statistics

Constant Activity Across the Range
0 1 2 3 4 5 6 7 8 9
More Activity at the Centre of the Range
0 1 2 3 4 5 6 7 8 9
More Activity at the End of the Range
0 1 2 3 4 5 6 7 8 9

Version 1 Rev 4 Setting the Statistical Interval
Setting the Statistical Interval

The statistical interval can be set using the chg_element command. This period is used to control
the time interval between successive uploads of statiscal information. At the end of the period
specified the central statistics function at the BSC will collect statistical data from its associated
distributed statistics functions and call the OMC to inform it that a statistics file is ready to be uploaded.
Although it is possible to set this period anywhere between 5 and 60 minutes, the practical value
will always be 30 or 60, as these are the only two values presently supported by the OMC. This
period, set at the BSC, must be the same value as that being used at the OMC.
The disp_element command can be used to display the current interval in use.
Displaying the interval timer

At any moment in time the BSC will retain 12 statistical files each pertaining to a particular
chronological period, in length each period will be equal to the statistical interval. This command
will prompt a display of the chronological range of each of the 12 start times.
Note: Clearing statistics

The command clear_stats is no longer supported and has been removed.

Setting the Statistical Interval Version 1 Rev 4
Setting the Statistical Interval
chg_element stat_interval <*><location>

* 30 or 60
Displaying the Interval Timer

disp_interval

Version 1 Rev 4 Displaying Statistical Reports
Displaying Statistical Reports
Once a statistical interval (stat interval) has expired the statistical results can be displayed
using the disp_stats command. Several examples of typical displays can be seen in
the W56. The format of the command is as follows:
disp_stats<interval><meas_type>[cell_number] [board_id]

Displaying Statistical Reports Version 1 Rev 4
Displaying Statistical Reports
disp_stats <interval><meas_type> [
* ]
* cell_desc
board_desc

Version 1 Rev 4 Displaying Statistical Reports

Call Statistics Version 1 Rev 4
Chapter 4
Call Statistics

Version 1 Rev 4 Call Statistics

Call Statistics
Objectives
• Name the five call statistics groups.
• Indicate where each call statistic is incremented given related ladder diagrams and the W56 manual.

Version 1 Rev 4 Call Statistics
Call Statistics
Introduction
Call statistics are generated during CP. Call assignments and failures are monitored along with
handover assignments and failures. The handover statistics will be investigated in the next section.
Call statistics fall into five categories which are detailed in the W56 manual.
1. Connection Establishment Statistics.
Identifies statistics updated when attempting to establish a signalling channel.
2. TCH Assignment Statistics.
These statistics are updated when attempting to establish a traffic channel.
3. Usage/Congestion Statistics.
Identifies the statistics which are used to monitor usage and congestion.
4. Call Clearing Statistics.
These statistics are associated with call clearing.
5. Handover Statistics.
A handover is the process of transferring a MS from one RF channel to another RF channel,
between cells or within a cell. These statistics will be studied separately in the next section.

Call Statistics
CONNECTION
ESTABLISHMENT
TCH ASSIGNMENT hello
USAGE / CONGESTION ?
! !
* *
CALL CLEARING
bye
HANDOVER
Cell
Cell Site

Version 1 Rev 4 Connection Establishment
Connection Establishment
In an attempt to establish dedicated mode the MS will transmit a "channel request" message,
packaged in the familiar access burst. The channel request contains 8 bits of intelligent
information, an establishment cause value (3-6 bits) and a random reference (2-5 bits). Before
transmitting this information the MS will perform an X-OR function on the data using the
serving cells Base transceiver Station Identity codes (BSIC). This simple encoding function
will enable the receiving server to discriminate between "channel requests" bound for other
cells utilizing similar Broadcast Control Channel (BCCH) frequencies.
The channel coder decodes the message on the Random Access Channel (RACH) from the Radio
Channel Unit (RCU). If the channel coder is unable to equalize and hence decode the message it will
peg an internal counter for the unrecognized message. If the channel request is correctly decoded
it will then be sent to RSS L1, this message also includes the status of the unrecognized message
counter and an indication as to the required relative timing advance relevant to this request.
Statistics
OK_ACC_PROC_SUC_RACH
RSS Layer 1 increments this statistic for each channel request received from the channel coder.
The channel request message is used by the MS to request allocation if a dedicated channel (to be
used as an SDCCH) by the network, in response to a paging message (incoming call) from the network
or as a result of an outgoing call/supplementary short message service dialled from the MS.
ACCESS_PER_RACH
RSS L1 will also increment this statistic once for the channel request, plus the number
indicated by the unrecognized message counter.
INV_EST_CAUSE_ON_RACH
Upon receipt of the channel request RSS A-bis will validate the establishment cause value which
must be consistent with specified causes in TS GSM 04.08. If it is not consistent , this statistic
is incremented and the channel request is ignored. Providing the cause value is successfully
validated and a channel required message will be formatted and sent to CP.
So-called "phantom" RACHs could possibly contribute to incrementing the above statistics.
Phantom RACHs can essentially be attributed to sporadic noise and interference. Channel
requests from distant MSs can obviously be affected by such noise especially when MS output
power is low. Conversely when MS output is high any transmitted signals can cause interference
to other co-channel and adjacent channel cells. In Motorola’s implementation it is unlikely that
cells using similar frequencies will be finely synchronized. This could only happen by chance as
each BTS does not have frame synchronization. It is possible though for part synchronization
to occur and this could contribute to the phantom RACH problem.
Once the RRSM has received the channel required message it will attempt to establish the MS on
a dedicated channel, usually a Stand-alone Dedicated Control Channel (SDCCH).

Connection Establishment Version 1 Rev 4
MS
Channel
coder
(DRIM)
RSS L1
Channel request
peg:
Channel request OK_ACC_PROC_SUC_RACH
ACCESS_PER_RACH
RSS ABIS
After verification
Channel request if invalid peg:
INV_EST_CAUSE_ON_RACH
CP
Channel required

CHAN_REQ_CAUSE_ATMPT
This counter array pegs whenever a channel required message is received by the RRSM. It tracks
the cause values of channel requests occurring in a cell. The bins of the array are as below:
0 - Originating call
1 - Emergency call
2 - CM re-establishment
3 - Location update
4 - Page response
5 - LMU establishment
The RRSM is responsible for incrementing the appropriate bin depending on the cause.
ALLOC_SDCCH
This counter statistic is incremented in the CRM each time an SDCCH sub-slot is successfully allocated.
SDCCH sub-slots are allocated through immediate assignment, assignment and handover procedures.
BUSY_SDCCH
Each time the CRM allocates an SDCCH the BUSY_SDCCH statistic is incremented.
This statistic is a weighted distribution and will produce a mean value indicating the
average number of SDCCHs in use per interval.
ACCESS_PER_AGCH
Pegged in the RSS and counts the number of immediate assignment, immediate assignment
extended and immediate assignment reject messages sent on AGCH. This statistic counts
messages, not assignments or rejects. Remember that one message could contain up to 2
immediate assignments or indeed up to 4 immediate assignment rejects.
OK_ACC_PROC
Once the link layer has been established between the RSS and MS, the RSS will send an
establish indication message containing the L3 initial message originating from the MS. The
L3 initial message will be dependent on the MS’s requirements.
0 — CM Service Request - Call
1 — CM Service Request - SMS
2 — CM Service Request - Supplementary services
3 — CM Service Request - CM Emergency Call
4 — CM Re-establishment
5 — Location Update
6 — IMSI Detach
7 — Page Response
8 — Location update follow on request SMS
9 — Location update follow on request normal
10 — Location Services

RSS A-BIS RRSM
Channel required Peg:

CHAN_REQ_CAUSE_ATMPT
CRM
Channel required
Peg: received
ALLOC_SDCCH
BUSY_SDCCH
Channel assigned
RSS Channel activation
Channel activation acknowledge
Immediate assignment cmd
MS
Immediate
Peg:
assignment
cmd
ACCESS_PER_AGCH
SABM
Establish indication Peg:
(L3 Initial
message) (L3 Initial message) OK_ACC_PROC
UA
(L3 Initial
message)

SDCCH_CONGESTION
When the last SDCCH available is allocated then the CRM will start the sdcch_congestion timer.
This timer will only be stopped when at least one SDCCH becomes idle. SDCCH_CONGESTION is a
durational statistic indicating the total time within a period that no SDCCH was available.
ALLOC _SDCCH_FAIL
This statistic is pegged each time the CRM tries to allocate a free SDCCH but is prevented
because they are all busy. This statistic is also incremented in the target cell when
rejecting an SDCCH handover through lack of resources.
ALARM 1.CELL: Attempt at allocating an SDCCH failed - PM (major)
CHAN_REQ_MS_BLK
This statistic is pegged by the RSS and is incremented each time an immediate
assignment reject message is received from the CRM.

RSS A BIS RRSM
Channel required
CRM
If last SDCCH assigned Channel required
start sdcch_congestion received
timer for:
SDCCH_CONGESTION
Channel assigned
RSS RRSM
Channel required
CRM
Channel required
received
Immediate
assignment reject If no sdcch available
increment
On receipt of immediate ALLOC_SDCCH_FAIL
assignment reject peg:
CHAN_REQ_MS_BLK

CHAN_REQ_MS_FAIL
Upon sending the immediate assignment message to RSS the RRSM will start timer
rr_t3101. If rr_t3101 is allowed to expire and an establish indication for that connection
has not been received then this counter statistic is incremented.
ALARM 1.CELL: Attempt at allocating an SDCCH failed - PM (minor)

RSS RRSM
Immediate assignment rr_t3101
MS
Immediate assignment
rr_t3101
If rr_t3101 expires and

no establish indication is
received peg:
CHAN_REQ_MS_FAIL

Version 1 Rev 4 SCCP Connection Establishment
SCCP Connection Establishment

After receiving the establish indication from the RSS to indicate the MS has successfully
arrived on its dedicated channel, the RRSM will then forward the L3 information onto the
SSM. At this stage the SSM is responsible for establishing an SCCP virtual circuit connection
for this MS (in connection orientated mode) with the MSC.
Statistics
CONN_REQ_TO_MSC
To establish a Switch Virtual Circuit (SVC) within the SCCP layer of C7 the BSS must send
a connection request to the MSC. The connection request will contain the L3 information
originally sent by the MS plus other connection oriented information.
CONN_REFUSED
The MSC should respond with a connection confirm indicating that an SVC has been established
at the SCCP layer. If, for some reason, this is not possible the MSC will return with a connection
refused. On receipt of these messages the SSM will increment this statistic. The connection
refused messages could, depending on switch implementation, be returned as a result of
successful or unsuccessful location updating, failed call re-establishment and as a result of
International Mobile Subscriber Identity (IMSI) detach. Depending upon switch software the
connection refused could be returned when congestion relief is employed.
MS_ACCESS_BY_TYPE
This medium counter array measures the number of accesses of the system by MSs of different
frequency band capabilities. The RRSM decodes this information from the classmark 3 message,
usually sent just after the L3 initial message. The bins are defined below:
0 = PGSM
1 = DCS1800
2 = PCS1900
3 = PGSM + EGSM
4 = PGSM + DCS1800
5 = PGSM + EGSM + DCS1800
6 = PGSM + PCS1900
7 = PGSM + EGSM + PCS1900

SCCP Connection Establishment Version 1 Rev 4
SCCP Connection Establishment

RSS RRSM MTP/MSC
pegs: MS_ACCESS_BY_TYPE
Establish indication
One of: SSM

CM service request Initial L3 Information
CM re establish <CR>
Location update request After the CR is sent <CONNECTION REQUEST>
IMSI detach the S SM pegs: Complete L3 information
Respond to page CONN_REQ_TO_MSC
<CC>
<CONNECTION CONFIRM>
OR
<CREF>
<CONNECTION REFUSED>
On receipt of a CREF
the S SM pegs:
CONN_REFUSED

Stats
PAGING PROCEDURE
The MSC is responsible for initiating the paging procedure and does so by sending the BSS a
paging message. This message is received by the SCCP preprocessor, it contains the information
necessary to page the MS (i.e. IMSI,Temporary Mobile Subscriber Identity (TMSI) and the cell
id list). This message is sent in the connectionless mode of the SCCP Layer.
PAGE_REQ_FROM_MSC
This statistic is pegged by the preprocessor and is simply a count of the number
of paging messages received from the MSC.
PAGE_REQUEST_FROM_MSC_FAIL
The preprocessor will peg this statistic when a paging message has been
received suffering a protocol error.
Providing the paging message can be interpreted by the preprocessor, the called MSs paging group
will be determined and included in the page mobile request which will then be despatched to the
appropriate instances of RRSM. From there, paging commands will then be sent to the correct
instances of RSS where the pages will be grouped and formatted into paging request messages
ready for transmission on the air-interface at the appropriate moment in time.

Paging Procedure
MSC
MTP L3
(pre-proc)
RCI/RRSM
Paging
RSS
Page
mobile request
Incremented for every
Paging decoded paging msg:
PAGE_REQ_FROM_MSC
command
Peg:
MS Incremented for every
PAGING_REQUESTS undecoded paging msg:
PCH_AGCH_Q_LENGTH
Pegged per msg:
Paging request ACCESS_PER_PCH
Possibly increment
PCH_Q_PAGE_DISCARD

Version 1 Rev 4
Paging Procedure Continued

Providing the paging message can be interpreted by the preprocessor, the called MSs paging group
will be determined and included in the page mobile request which will then be despatched to the
appropriate instances of RRSM. From there, paging commands will then be sent to the correct
instances of RSS where the pages will be grouped and formatted into paging request messages
ready for transmission on the air-interface at the appropriate moment in time.
ACCESS_PER_PCH
ACCESS_PER_PCH
Each time a paging request message is sent on the air-interface this statistic is incremented. As with
the other access statistics this is incremented per message, remember a paging request message
could contain up to 4 pages if paging by TMSI and up to 2 pages if paging by IMSI. This statistic is
modified to count both Circuit Switched (CS) and Packet Switch (PS) paging on Page Channel (PCH). .
Bin 0 – ACCESS_PER_PCH_PS_CS Both CS and PS pages within the PAGING REQUEST message.
Bin 1 – ACCESS_PER_PCH_CS Only CS pages within the PAGING REQUEST message.
Bin 2 – ACCESS_PER_PCH_PS Only PS pages within the PAGING REQUEST message
PAGING_REQUESTS
PAGING_REQUESTS
This statistic accounts for any message making use of a PCH block. This statistic is similar to
PCH_Q_PAGE_DISCARD except the messages are sent, not discarded. This statistic is obtained by
measuring the number of paging requests received from the network for transmission on the PCH. .
Bin 0 – PAGING_REQS_TOT Number of Paging requests received to be transmitted on the PCH.
Bin 1 – PAGING_REQS_CS Number of Paging requests received to be transmitted on the CS.
Bin 2 – PAGING_REQS_PS Number of Paging requests received to be transmitted on the PS
PCH_Q_PAGE_DISCARD
This counter statistic will increment each time a page from the MSC (IMSI or TMSI number) is overwritten
whilst waiting in the queue. The oldest TMSI/IMSI number is overwritten first. The maximum queue
length is 8 TMSI or IMSI numbers. They will be queued awaiting their paging group to appear in time.
ALARM 24.CELL: PCH Queue page discard - PM (minor)
PCH_AGCH_Q_LENGTH
This gauge statistic tracks the average number of paging or access granting messages queueing
to be transmitted. It is pegged by the RSS Layer 1 software every paging multiframe.

Version 1 Rev 4
Paging Procedure Continued
MSC
MTP L3
(pre-proc)
RCI/RRSM
Paging
RSS
Page
mobile request
Incremented for every
Paging decoded paging msg:
PAGE_REQ_FROM_MSC
command
Peg:
MS Incremented for every
PAGING_REQUESTS undecoded paging msg:
PCH_AGCH_Q_LENGTH
Pegged per msg:
Paging request ACCESS_PER_PCH
Possibly increment
PCH_Q_PAGE_DISCARD

Version 1 Rev 4 Half Rate
Half Rate
The GSM Half Rate feature offers enhanced capacity over the air interface, corresponding to the
proportion of mobiles within a coverage area that supports Half Rate. An air timeslot is split into two
sub–channels, each containing a half rate channel. Speech quality is considered inferior to other speech
codecs but has a high penetration level (of GSM HR capable mobiles) due to its early introduction into the
standards. Due to these large penetration levels it is considered a viable option for high density areas.
A GSM HR call can fit within an 8kbps timeslot (an Ater channel) on the terrestrial resource from the
BSC to the RXCDR, rather than the 16kbps timeslot required for FR calls. If a percentage of the
active calls can be assumed to be HR, then efficiencies can be gained by reducing the number of
terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can dynamically
allocate a timeslot to a CIC on an 8kbps/16kbps basis. This dynamic allocation is performed across
a trunked interface between the BSC and a remote transcoder (RXCDR). This interface is called
the Ater interface. The dynamic allocation is an enhancement to the existing Auto Connect mode
feature, referred to as ”Enhanced Auto Connect mode”. Enhanced Auto Connect is part of the AMR
feature and is mentioned here only to point out that GSM HR will enjoy the same benefit.
The backhaul requirements between the BTS and BSC may also be reduced to 8kbps as long
as subrate (8K) switching is present at the BSC. Both GDP and GDP2 boards will be enhanced to
support GSM HR. GDP will be introduced first, followed by GDP2 in a future release.

Half Rate Version 1 Rev 4
Half Rate
MS A – Sub Channel 0
IDLE SACCH Half Rate TCH – MS A

Half Rate TCH – MS A
25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
SACCH Half Rate TCH – MS B IDLE Half Rate TCH – MS B
MS B – Sub Channel 1
SYS02_CH1_09A

Version 1 Rev 4 Dynamic Allocation RXCDR and BSC Circuits (DARBC)
Dynamic Allocation RXCDR and BSC Circuits (DARBC)

The evolved DARBC feature of GSR 5 has introduced automatic connection of Ater channels
(between the RXCDR and BSC) to connect MSC-allocated CICs to the BSC. The mode of
operation is known as the ‘Auto-Connect mode’ and is the standard mode following upgrade
to GSR 5. The previous GSR 4 mode, now known as ‘Backwards Compatibility Mode’, is
part of GSR 5 but is superseded after upgrade is complete
Prior to this feature, connectivity between MSC and BSC via the transcoder was mapped statically, but
with this feature the BSC treats its Ater or connecting channels as a pool resource A CIC is mapped to
a through connection via the RXCDR on initiation, and when the CIC is nominated by the MSC, the Ater
channel is utilised in its mapped mode. However if a fault should occur on the Ater carrying the call
between the RXCDR and BSC, a new Ater channel will be allocated so that the call is not lost.
BSC tracks CIC and Ater utilization, and allocates/deallocates Ater channels as required. It also
instructs the RXCDR via the enhanced XBL to make connections between its MSC and Ater
interfaces. The BSC also carries out audit of the CIC and Ater information via the XBL.
The RXCDR makes switch connections between the Ater channels and the MSC interface, and informs
the BSC when faults or operator actions affect the usability of CICs or Ater channels. It also ensures
that the correct idle tone is connected and provides the BSC with CIC/Ater audit information.
AMR Phase 2 GSR7 - See Chapter 10 for AMR Phase 1 Feature

An AMR HR call can occupy an 8kbps (except when the 7.95kbps codec mode is included in the
HR ACS, in which case 16kbps is required) timeslot (an Ater channel) on the terrestrial resource
from the BSC to the RXCDR, rather than the 16kbps timeslot required for FR calls for FR calls. If
a percentage of the active calls can be assumed to be HR, then efficiencies can be gained by
reducing the number of terrestrial resources between the BSC and RXCDR. This is possible only if
the BSC can dynamically allocate a 8 kbps timeslot to a CIC. This allocation is performed across
the Ater interface and may be considered to be an enhancement to the existing ‘Auto-Connect
mode’ hence it will be referred to as ‘Enhanced Auto-Connect mode’ or EAC.
The AMR half-rate channel mode will only be available on the CTU, TCU-A and TCU-B radio
platforms. It will require all BSC/RXCDRs KSWs to be replaced with DSWs. The feature
allows either BSC-BTS backhaul independent of BSC-RXCDR backhaul savings. If this is
the case the 16kbps Ater channels will carry 8kbps TRAU frames. Or alternatively both
BSC-BTS and BSC-RXCDR can be enabled for backhaul savings.
Enhanced GDP refers to a new firmware configuration of the GDP board. In this configuration, each
of the 15 DSPs on the GDP board is only capable of supporting the transcoding function for a single
channel of GSM speech (AMR, FR, and EFR) and Phase 2 data services. This is due to the additional
requirements of AMR. To fully offer 30 channels of enhanced transcoding using the same E1 span line
to the MSC, enhanced GDPs are equipped as pairs, each providing half of the transcoding resources.
The GDP2 board refers to the new transcoding platform for increased AMR support. This platform shall
co-exist with current XCDR and GDP boards and is capable of supporting full 2 E1 links meaning 60
AMR transcoding circuits on one board. Full use of the GDP2 boards (60 channels) will require use
of 2048 timeslot mode and a ngRXU cage and is local transcoding cabinets to be ngBSSC.

Dynamic Allocation RXCDR and BSC Circuits (DARBC) Version 1 Rev 4
Dynamic Allocation RXCDR and BSC Circuits (DARBC)
MSC
MSC allocates CIC to call
CIC CIC
RXCDR RXCDR RXCDR
The method to connect Ater chans

timeslots can be backwards
compatable, auto-connect
or enhanced auto-connect BSC
A bis
BTS

Version 1 Rev 4 ATER_CHANNEL_STATUS
ATER_CHANNEL_STATUS
A single new statistic ATER_CHANNEL_STATUS is introduced at GSR7 and is used to track call related
ATER allocation scenarios and any associated failed assignments due to lack of Aters or communication
failure with the RXCDR. This statistic is only applicable in Enhanced Auto Connect mode.
Stats
Bin 0 - ATER_CHAN_REQUEST
This statistic is used to track the number of Ater channels requested on a per AXCDR basis.
This stat is pegged whether or not an Ater channel is successfully allocated.
Bin 1 - ATER_CHAN_REQUEST_FAIL
This statistic is used to track the number of Ater channels requested but cannot
be allocated on a per AXCDR basis.
Bin 2 - CALL_SETUP_FAIL_COMM_ERR
This statistic is used to track on a per AXCDR basis, the number of call setups that fail due to
BSC-RXCDR communication failures. This statistic is pegged only after all attempts to communicate
with the RXCDR have failed and the call has to be dropped. If the first attempt results in a
communication failure but a subsequent attempt succeeds the statistic will not be pegged. It could
be pegged either due to a call assignment or due to an inter-BSS handover.

ATER_CHANNEL_STATUS Version 1 Rev 4
ATER_CHANNEL_STATUS
Allocation Ater ATER_CHAN_REQUEST

request assign
MSC RXCDR BSC
0 3 Groups - Ater chans

0 1 31
0 31
TS 3-29
Timeslots
ATER_CHAN_REQUEST_FAIL
Allocation Assign Fail
request (all reasons)
MSC RXCDR BSC
Allocation CALL_SETUP_FAIL_COMM_ERR
request
COMM failure
MSC RXCDR BSC

ATER_CHANNEL_STATUS
Stats
Bin 3 - INT_HO_CIC_FAIL_COMM_ERR
This statistic is used to track on a per AXCDR basis, the number of internal call handovers that
fail due to BSC-RXCDR communication failures. This statistic is pegged only after all attempts to
communicate with the RXCDR have failed and the call has to be dropped. If the first attempt results in
a communication failure but a subsequent attempt succeeds the statistic will not be pegged.
Bin 4 - ATER_SWITCH_FAIL_COMM_ERR
This statistic is used to track on a per AXCDR basis, the number of Ater switchovers that fail
due to BSC-RXCDR communication failures. This statistic is pegged only after all attempts to
communicate with the RXCDR have failed and the call has to be dropped. If the first attempt results in
a communication failure but a subsequent attempt succeeds the statistic will not be pegged.
Bin 5 - CALL_SETUP_FAIL_NO_ATER
This statistic is used to track on a per AXCDR basis, the number of call setups that fail due to no available
Ater channels. It could be pegged either due to a call assignment or due to an Inter-BSS handover.
Bin 6 - INT_HO_CIC_FAIL_NO_ATER
This statistic is used to track on a per AXCDR basis, the number of internal call handovers
and CIC remaps that fail due to no available Ater channels.

ATER_CHANNEL_STATUS
INT_HO_CIC_FAIL_COMM_ERR
HO
MSC RXCDR BSC
ATER_SWITCH_FAIL_COMM_ERR
Allocation
request Full/blocked
MSC RXCDR BSC
CALL_SETUP_FAIL_NO_ATER
Full/blocked
MSC RXCDR BSC
0 3 INT_HO_CIC_FAIL_NO_ATER
0 Full/blocked 31
HO
MSC RXCDR BSC

ATER_CHANNEL_STATUS
Stats
Bin 7 - ATER_SWITCH_FAIL_NO_ATER
This statistic is used to track on a per AXCDR basis, the number of Ater switchovers
that fail due to no available Ater channels.
Bin 8 - BSC_INIT_BLOCK_CIC_LOW_ATER
This statistics is used to track on a per AXCDR basis, the number of times the BSC initiates CIC
blocking due to low Ater resources. This statistic is pegged whenever the cic_block_thresh is passed.

ATER_CHANNEL_STATUS
ATER_SWITCH_FAIL_NO_ATER
Full/blocked
MSC RXCDR BSC
0 3
BSC_INIT_BLOCK_CIC_LOW_ATER
0 Low Ater 31
HO
MSC RXCDR BSC

Version 1 Rev 4 Busy CICs
Busy CICs
The number of CICs in use during each statistics interval is recorded by the
weighted distribution statistic BUSY_CICS.
CICs are initially equipped at both the RXCDR and at the BSC. From the RXCDR they are
mapped to the MSC, but not mapped to the BSC since they will be allocated dynamically if
auto-connect mode of operation is chosen. They carry 64 kbit/s PCM speech from MSC to
RXCDR (the A Interface), and transcoded 16kbit/s channels between RXCDR and BSC (the
Ater interface), and are described in the equip 0 cic command at both RXCDR and BSC as
CIC numbers (which actually relate to the MSC outgoing multiplexer).
The CIC is allocated by the MSC in the assignment request message. As the BSC detects the
allocation or de-allocation of a CIC, the statistic BUSY_CICS is pegged.
This weighted distribution statistic is a 10-bin device. Its bin ranges are set in initial configuration
to cover the range of CICs physically available to the BSC.
The statistic will record the number of CICs (as a bin range) in use and also the length of time in
ms that the bin range is valid. For each bin range, a cumulative total busy time is accumulated.
At the end of the statistic gathering interval, the individual bin contents, as call-milliseconds, are
summated; and when divided by the total period will yield a mean ERLANG value for the BSC
during the interval concerned. Also the statistic will show the minimum and maximum number of
CICs in use during the interval, and the overall bin array for further analysis
The statistic BUSY_CICS therefore represents the number of calls in progress from the
particular MSC for the base station system concerned.

Busy CICs Version 1 Rev 4
Busy CICs
Tick
12
12
Tick 9 3 9 3
6
Tick 6
MSC RXCDR BSC
CICs allocated by CICs mapped at BSC

MSC as Call is set up through RXCDR to MSC
Use recorded as
BUSY_CICS

Version 1 Rev 4 TCH Assignment Statistics
TCH Assignment Statistics

Adaptive Multi-Rate - See Chapter 10 for detail
Adaptive Multi Rate (AMR) is new ETSI standard for voice codecs in both full rate (FR) and Half
Rate (HR). The codec is selected to optimise voice quality depending on radio link quality. A codec
adaptation algorithm selects the optimised channel (half or full rate) and speech rate as a function
of the channel quality. The most robust codec mode is selected in bad propagation conditions.
The codec mode providing the best quality is selected in good propagation conditions. The codec
adaptation relies on channel quality measurements performed in the MS and the network and on
in band information sent over the Air Interface together with the speech data.
Current GSM speech codecs (FR, EFR, and HR) operates at a fixed rate and constant
error protection level whatever the radio link quality.
AMR Full-Rate Channel

The AMR full-rate channel is a full-rate channel that employs an AMR speech codec to
provide higher speech quality in areas of poor RF conditions.
AMR Half-Rate Channel

The AMR half-rate channel mode allows two AMR calls to be placed on a single air interface
timeslot. Use of the AMR half-rate channel mode will thus allow increases in cell capacity without
the need for deployment of extra radio hardware. The cost of the increase in cell capacity with
this release of the AMR half-rate channel mode is the need for the provisioning of extra backhaul
between the BSC and BTS and the lower QoS provided by AMR half-rate calls.
MA_REQ_FROM_MSC
This statistic counts the number of Assignment Requests for each MSC preferred speech
version. The bins for this statistic are defined as follows:
Bin 0 - PM_FR
Bin 1 - PM_EFR
Bin 2 - PM_AMR FR
Bin 3 - PM_AMR HR
Bin 4 - PM_GSM_HR
Bin 5 - PM_SDCCH_CHAN
Bin 6 - PM_Other
MA_REQ_FROM_MSC_FAIL
This counter statistic is incremented by the SSM each time an assignment request message
from the MSC fails validation. In this event the MSC is notified with the assignment failure
message with cause "protocol error between BSC and MSC".

TCH Assignment Statistics Version 1 Rev 4
MSC
CRM/AM RRSM SSM

Assignment request
Initiate assignment
Assignment resource On receipt of msg peg:
request
MA_REQ_FROM_MSC
Assignment channel
BUSY_CICS
assigned
CRM pegs
CALL_SP_VERS_DOWNGRADE_MONITOR
ALLOC_TCH ALLOC_TCH_HR
TCH_USAGE (durational)
MS_TCH_USAGE_BY_TYPE
TCH_Q_REMOVED (Also ALLOC_TCH_FAIL - see later)
BUSY_TCH (weighted mean)

BUSY_TCH_HR
BUSY_TCH_CARRIER
BUSY_TCH_CARR_HR
TCH_CONGESTION
TCH_CONGESTION_HR


This statistic tracks the number of call rejects and call downgrades due to not supporting requested
speech versions. From GSR6 multi-platform use (both XCDR and GDP) is supported, this means
that the software must be able to pool resources and allocate them as necessary if available. The
same argument applies to handover requests and in-call modification (by channel mode modify
procedure). An other consideration is the gradual increase in the use of mobiles supporting AMR.
It is envisaged that these will available before the software supports the use of AMR and that the
call will be downgraded to EFR or FR. These features are all part of the Call Downgrade on CIC
Capability Mismatch Feature. The statistic is a small counter array containing four bins:
Bin 0 - EFR_REQUEST_DOWNGRADE.
Pegged when the call is downgraded due to CIC capabilities i.e.
Assignment Request for/including EFR Handover Request or EFR In-Call modification request.
Bin 1 - AMR_FR_CALL_DOWNGADE. Pegged when the full-rate AMR call is downgraded.
BIN 2 - AMR_HR_CALL_DOWNGRADE. Pegged when the half-rate AMR call is downgraded.
Bin 3 - GSM_HR_CALL_DOWNGRADE. Pegged when the HR GSM call is downgraded.
ALLOC_TCH
This counter statistic is incremented in the CRM each time a TCH is successfully
allocated. The reasons for the allocation can be origination including successful allocations
due to directed retry or intra/inter cell handovers.
ALLOC_TCH_HR
This statistic keeps a counter of the number of successful HR AMR TCH allocations within
a cell for both call originations and hand ins. Hand in allocations include intra-cell, incoming
intra-BSS, incoming inter-BSS, and incoming directed retry scenarios.
TCH_USAGE
When the CRM allocates a channel to the RRSM it sends an assignment channel assigned or
handover channel assigned message. Upon doing this it simultaneously starts an internal timer.
This timer records the duration for which the TCH is in use. When the channel is deallocated the
timer is stopped. The elapsed duration increments the TCH_USAGE total for that cell, including
normal range channels in extended cells and the outer zone of concentric cells.
This is a counter array that tracks the length of time each frequency type is in use in a
cell. It is pegged by the CRM on a per cell basis. Although similar to TCH_USAGE,
this statistic is completely independent of it.

MSC
CRM/AM RRSM SSM

Assignment request
Initiate assignment
request
MA_REQ_FROM_MSC
Assignment channel
BUSY_CICS
assigned
CRM pegs

BUSY_TCH_HR
BUSY_TCH_CARRIER
BUSY_TCH_CARR_HR
TCH_CONGESTION
TCH_CONGESTION_HR


TCH_Q_REMOVED
This statistic tracks when a queued call is assigned to a traffic channel. This statistic is a two bin array
which counts the number of times a queued call is assigned during call set-up (bin 0) and when
a ho_request is received from the MSC typically during an inter-bss handover (bin 1).
BUSY_TCH
Each time the CRM allocates a TCH the BUSY_TCH statistic is incremented, this statistic
is a weighted distribution and will produce a mean value indicating the average number
of TCHs in use per interval. The CRM will allocate a TCH upon assignment, immediate
assignment (in the case of an emergency call) and handover.
BUSY_TCH_CARRIER
This is a gauge statistic that tracks the number of TCHs allocated during an interval. It produces a
mean value indicating the average number of TCHs in use during that interval, therefore giving an
average capacity for additional traffic in the cell. This statistic includes TCHs used as dedicated control
channel in immediate assignment mode (in the case of emergency call, or it has been allowed in the
cell by the database parameter). At the end of the period a mean and maximum value is given.
BUSY_TCH_HR
This statistic provides a mean value indicating the average number of HR AMR TCHs in use. This
statistic is updated each time an allocation or deallocation of a HR AMR TCH occurs.
BUSY_TCH_CARR_HR
This statistic reports a maximum and average value for the amount of Half Rate AMR busy TCHs on a per
carrier basis. This statistic is updated each time an allocation or deallocation of a HR AMR TCH occurs.
TCH_CONGESTION
When the last TCH available is allocated then the CRM will start the TCH_CONJESTION timer,
this timer will only be stopped when at least one TCH becomes idle. TCH_CONGESTION is a
durational statistic indicating the total time within a period that no TCH was available.
TCH_CONGESTION_HR
This statistic indicates the duration of time when no HR AMR TCHs are available. When
the last HR AMR TCH available is allocated a timer is started and the timer is stopped
when at least one HR AMR TCH becomes idle. For concentric cell or Dual Band Cells, this
measurement indicates HR AMR TCH congestion for the outer zone.
The assignment procedure is initiated by the MSC after authentication, cyphering and call set-up
is completed on the SDCCH. The assignment procedure is started when the MSC transmits
an assignment request for the SCCP connection specified. This message indicates the type of
channel required, the CIC to be used and also any priority levels which may exist.

MSC
CRM/AM RRSM SSM

Assignment request
Initiate assignment
request
MA_REQ_FROM_MSC
Assignment channel
BUSY_CICS
assigned
CRM pegs

BUSY_TCH_HR
BUSY_TCH_CARRIER
BUSY_TCH_CARR_HR
TCH_CONGESTION
TCH_CONGESTION_HR

Version 1 Rev 4 Concentric Cells
Concentric Cells
Concentric Cells is an optional feature which provides cell resource partitioning using
the concept of the concentric cell structure (outer and inner zones) to allow for tighter
re-use patterns and increased frequency economy.
This feature describes the use of a single BCCH using interference estimation or
measurement to move traffic between the conventional macrocell underlay (Outer
zone) and the super reuse layer (Inner zone).
Concentric Cell is an elegant and simple technique in which the size of cells on the super re-use layer
(inner zone) is self-governed by interference or by the power that the carriers on the inner zone transmit.
With this feature the operator may configure non-BCCH carriers within a cell to have a smaller
coverage area. The carriers equipped within a cell may be grouped into two zones:
• Zone 0: Also referred to as the "outer zone", is reserved for carriers that may broadcast
at the maximum transmit level defined for the cell.
• Zone 1: Also referred to as the "inner zone", may be defined with non-BCCH carriers
transmitting lower power than the BCCH carrier, or having a tighter reuse pattern
that reduces the useful coverage area of the carrier.
The Mobile Station connected to Zone 0 must meet specific criteria before it can be assigned a traffic
channel configured on a carrier in Zone 1 and vice versa. There are two different "use algorithms",
specified by the operator on a per cell basis, to trigger the transitions between the two zones of the cell.
• Power Based Concentric Cells: Inner zone carriers transmit less power than outer ones
and the transitions between zones are based on absolute level thresholds.
• Interference Based Concentric Cells: Inner and outer zone carriers transmit all the same power
within and the transitions between zones are based on some interference conditions. These
interference conditions are protection margins against potential interfering neighbours.
The use of a single BCCH implies that the carriers placed in the outer zone are available in the
whole cell coverage area whereas the inner zone carriers are only available in a restricted area
close to the site location. The signalling previous to the call set-up is established in the outer zone
and whenever it is possible to move to the inner, the call is transferred to the inner carriers.
The Concentric Cell feature is basically a capacity enhancement feature. The possibility of
implementing tighter reuse patterns in the area close to the antenna site permits to increase the
capacity at the same time that quality is guaranteed by the use of interference estimation algorithm
Multiband
From software release GSR 5.0 multiband operation of concentric cells is allowed. For example if
DCS1800 is being added to an existing GSM900 network, the existing GSM900 BCCH plan can be
used, since there is no need to plan DCS1800 BCCHs when 1800MHz carriers are added.
For this feature to be efficient the network should have sufficient number of multiband-capable
mobiles and equipment should be collocated and synchronized. (InCell cabinets cannot be mixed
with M-Cell/Horizon cabinets in the same logical area). In the example described above, all mobiles
must be at least GSM900 capable to access the system. Since the BCCH carriers are defined in
the GSM900 band, single band DCS1800 mobiles will be unable to access the system.

Concentric Cells Version 1 Rev 4
Concentric Cells
Zone 1 - Inner Zone
Non - BCCH
Transmitting at BCCH
lower power than Broadcast at max tx
BCCH or level defined for that
Zone 0 - Outer Zone
cell
Having a tighter
Other non_BCCH carriers
reuse pattern that
reduces the useful
coverage area of Multiband Operation of Concentric Cells
the carrier Supported from GSR 5.0

Version 1 Rev 4 Concentric Cells
Concentric Cells
Stats
TCH_CONG_INNER_ZONE.
This statistic pegs as for TCH_CONGESTION but only when congestion exists
in the inner zone of a concentric cell
TCH_CONG_INNER_ZONE_HR
This statistic indicates the duration of time when no HR AMR TCHs are available in the inner zone of a
concentric cell or Dual Band Cell. When the last inner zone HR AMR TCH available is allocated a timer
is started and the timer is stopped when at least one inner zone HR AMR TCH becomes idle.
TCH_USAGE_INNER_ZONE
This statistic pegs as for TCH_USAGE but only when a channel in the inner
zone of a concentric cell is allocated.

Concentric Cells Version 1 Rev 4
Concentric Cells
MSC
SSM
Assignment request
RRSM
CRM/AM Initiate assignment
Assignment resource
request
Assignment channel
assigned
CRM pegs
TCH_USAGE_INNER_ZONE
TCH_CONG_INNER_ZONE
TCH_CONG_INNER_ZONE_HR

Version 1 Rev 4 Extended Range Cells
Extended Range Cells

Motorola supports a software feature called ‘Extended Range Cell’ or ERC that allows mobiles
to use a cell beyond the GSM specified 35 kilometre limit.
At distances greater than 35 Km the propagation delay exceeds the standard GSM timing
advance of 63 bit periods or 233us. This timing advance is sufficient for the two-way
propagation delay between the BTS and the MS to be overcome.
From distances over 35km, the MS’s transmitted signal will begin to arrive in the following
timeslot, corrupting the data being processed in both timeslots. With the ERC feature
enabled, the BTS expands its receive window to cover both the MS allocated timeslot and
the following timeslot. This gives an effective 156 extra bit periods for the propagation
delay which increases the maximum cell radius to 121km.
In simple terms, it is necessary to use two normal timeslots to form a single extended range timeslot.
Using two timeslots allows the BTS to handle additional propagation delay from the mobile.
The actual value of timing advance given to the MS can still only go up to 63 bit periods, but as the
MS’s transmit burst can be late by a whole timeslot at the BTS and still be decoded correctly.
The extended range cell feature is supported by the SCU, TCU and CTU families of radio.
TCH_USAGE_EXT_RANGE
This counter statistic works exactly as TCH_USAGE, but tracks the usage of extended range
channels only, on a per cell basis. It is pegged at the CRM.

Extended Range Cells Version 1 Rev 4
Extended Range Cells

Tx
BTS 1 2 3 4 5 6 7 0 1 2
Propagation Delay
Rx 1 2 3 4 5 6 7 0 1 2
MS
3 timeslot offset
Tx 6 7 0 1 2 3 4 5 6 7
MS
Propagation Delay
Rx 6 7 0 1 2 3 4 5 6 7
BTS
To prevent the burst from moving from its timeslot into a neighbouring timeslot a timing advance
is introduced to send the burst earlier therefore overcoming the propogation delay
The maximum timing advance for a normal range timeslot is 63 bit or a propogation distance of
35 km radius anymore than this and it runs into the next timeslot.
Extended range allows the complete use of the next timeslot, hence a further 156 bits, which
together with the 63 bits from the primary timeslot gives a radius of 121 km
MSC
SSM
Assignment request
RRSM
Assignment resource
request
Assignment channel
assigned
CRM pegs
TCH_USAGE_EXT_RANGE

Version 1 Rev 4 BSC - BTS Dynamic Allocation
BSC - BTS Dynamic Allocation

The BSC - BTS dynamic allocation feature provides an alternative mechanism for allocating terrestrial
backhaul for radio resources ("terrestrial backing resources") between the BSC and BTS. Previous to
the introduction of this feature, these resources were allocated when RTFs were equipped.
The terrestrial backing resource is a 16 kbs portion of a time slot on a span and is allocated on
demand from a pool of available resources by the BSC. The pool is shared by the BTSs that are
chosen to use dynamic allocation and appear within the same network configuration. It should
be noted that dynamic allocation is limited to spoke, daisy-chain and closed loop daisy-chain
network configurations (maximum of 20 BTS configurations may be specified).
Dynamic allocation allows greater air capacity to be equipped than terrestrial backing resources
exist, whether at a BTS site or within a BTS network. The feature allows RTF equipage for
coverage purposes, not capacity purposes. Additionally, capacity can move dynamically
between BTSs in the same network based upon traffic considerations.
Even with dynamic allocation, greater bandwidth than that provided by a single span may
be wanted by an operator. Networks may have up to 3 spans between each BTS in
the configuration. The same number of spans must be specified between each BTS to
maintain the simplicity needed to provide dynamic allocation.
Note:
The allocation of 16 kbs terrestrial backing resources requires 16 kbs switching at the BTS
site. M-Cell/Horizon BTSs do not support 16 kbs switching. InCell BTSs support 16 kbs when
equipped with a KSW. In-building picocellular systems also support 16 kbs.
DYNET_ASSIGN_FAIL
Pegged at the AM, this counter statistic counts the number of assignment procedure failures
due to a lack of terrestrial backing resources. It is pegged per BSS.
DYNET_CALL_REJECTS
This counter array is pegged at the AM in similar circumstances to
DYNET_ASSIGN_FAIL, but gives causes:
Bin Procedures Description

0 NON_EMRG_CALL_BLK = Non emergency call blocked - lack of resources
1 EMRG_CALL_BLK = Emergency calls blocked - lack of resources
2 NON_EMRG_RESERVED = Non emergency calls blocked - resources
reserved
3 NON_EMRG_PREEMP = Call pre-empted due to emergency calls
4 LOSS_OF_RESOURCES = Calls pre-empted due to loss of resources.

BSC - BTS Dynamic Allocation Version 1 Rev 4
BSC - BTS Dynamic Allocation

MSC
SSM
Assignment request
RRSM
Assignment resource
request
Assignment channel
CRM pegs assigned
AM pegs
DYNET_ASSIGN_FAIL
DYNET_CALL_REJECT

Version 1 Rev 4 Assignment Request Queueing
Assignment Request Queueing

Assignment request queueing
If no TCH resources are available at the CRM the assignment request may be queued. This is
dependent upon a flag in the assignment request message received from the MSC and also a
database element, queue_management_information, set in add_cell.
CALLS_QUEUED
If queueing has been allowed and no resources exist then the CRM queues the request
and informs the RRSM with a force queue message. This counter statistic merely counts
the number of assignment requests that have been queued in a statistical interval. This
statistic does not include queued handover requests.
ALARM 20.CELL: Number of calls queued - PM (warning)
TCH_Q_LENGTH
This weighted distribution statistic will provide a maximum and mean number of queued assignments
during the period specified. These assignments will include originations and external handovers.
Queueing will obviously result from the call queueing feature but also Extended GSM (EGSM)
forced handovers, emergency call pre-emption, and directed retry.
TCH_Q_REMOVED
This counter array statistic tracks when a queued call is assigned to a traffic channel.
This can be queued assignment requests or handover requests. Prior to GSR 5 this
statistic did not exist which resulted in inaccuracies when calculating SDCCH blocking, as
a queued request pegs the statistic ALLOC_TCH_FAIL, so if a queued request is granted
a tch resource it should be taken into account as a success.
Bin 0 ASSIGNMENT_RESOURCE_REQ
1 HO_REQ
2 ASSIGNMENT_RESOURCE_REQ_INNER_Z
3 HO_REQ_INNER_Z
CLR_REQ_TO_MSC
An assignment request cannot be queued indefinitely and in fact will be queued for a maximum of GSM
timer T11 (BSSMAP_T11). If no assignment channel assigned message is received by the RRSM and
T11 is allowed to expire the RRSM will send a release request to the SSM, which will be forwarded
as a clear request to the MSC. There are a number of reasons why a clear request may be sent to
the MSC, these include problems with cyphering, RF loss, intra-cell handover failure and inter-cell
handover failure. Each time the message is sent to the MSC this counter statistic is incremented.
Bin 0 CLEAR_REQ_TO_MSC_SD Counts the number of clear requests sent to the MSC
for an SDCCH.
1 CLEAR_REQ_TO_MSC_FR Counts the number of clear requests sent to the MSC
for a Full Rate TCH.
2 CLEAR_REQ_TO_MSC_HR Counts the number of clear requests sent to the MSC for
a Half Rate TCH.
If the cell is barred no other associated stats will be pegged, but this one will.

Assignment Request Queueing Version 1 Rev 4
Assignment Request Queueing
SSM MSC
RRSM Assignment request
CRM Initiate assignment
Assignment resource
request
If assignment is queued
pegs:
CALLS_QUEUED
TCH_Q_LENGTH
TCH_Q_REMOVED
Force queue
Assignment queued
Queueing indication
RRSM T11
CRM
Force queue
No assignment channel
assigned received
SSM MSC
Clear request
Release request
pegs:
CLR_REQ_TO_MSC

Version 1 Rev 4 Directed Retry
Directed Retry
The GSM directed retry feature, if purchased and enabled, can allow an otherwise queued
assignment to be allocated a traffic channel in an alternate cell. As a compliment to this feature
a further congestion relief mechanism can be specified which can result in TCHs being freed
up by handing over existing calls that suit the congestion relief criteria.
The standard GSM directed retry feature and the congestion relief feature are purchased
and enabled individually. The GSM directed retry feature can work in conjunction with
one of the two congestion relief procedures available.
The criteria to allow a directed retry handover, initiated by either of the above features, is the same.
Criteria one and two as specified in GSM TS 05.08 must be met by neighbour candidates, albeit using
a congestion handover margin instead of the familiar ho_margin specified in add_neighbor. If
reported neighbours do not meet these criteria then no handover will be attempted for that MS.
The initiation of the directed retry procedure is similar for standard directed retry and both congestion
relief procedures. When the CRM receives an assignment resource request message from the RRSM
and is unable to allocate a free TCH due to congestion, the request will be placed in a queue. The
very existence of the queue and its maximum size is normally determined by a combination of a
database parameter and the queueing flag sent in the original assignment request message from
the MSC. When directed retry is enabled a queue is formed regardless of these factors. The CRM
will inform the RRSM that the request is in a queue using the force queue message. A further
message is then generated and sent to the RRSM indicating congestion and the method by which
it should be resolved. This could be a combination of the standard directed retry and/or one of the
congestion relief mechanisms. This will depend on purchase and database parameters.

Directed Retry Version 1 Rev 4
Directed Retry
CRM RRSM SSM MSC
Assignment request
Initiate assignment
Assignment resource
request
Force queue
Assignment queued
Congestion indication
Further events depend on congestion procedure employed

Version 1 Rev 4 Directed Retry
Directed Retry
The messaging that follows will depend on the DR mechanism specified in the
congestion indication message.
Standard Directed Retry

When instructed to implement the standard directed retry mechanism the RRSM will send a force
handover request message to the instance of RSS concerned. At this point the RSS will check
if it is possible to hand the queued MS to another cell based on the last received measurement
report. If the congestion criteria are met by at least one neighbour reported by the specified
MS, then the familiar handover recognized message will be sent to CP.
CONGEST_ STAND_HO_ ATMPT

Upon receipt of the handover recognized received message containing the cause value "standard
directed retry" the SSM will increment this counter statistic. This statistic is incremented for both
intra-BSS and inter-BSS handovers. The handover itself will be executed in the normal way.
Non-imperative handover rejection

The BSS rejects an incoming non-imperative handover (of which one reason may be
congestion relief) if it will cause congestion relief procedures to be triggered in the
target cell. Should such a handover be allowed, then the net result would simply be the
movement of a congestion problem from one cell to another.
Congestion relief handover retry

The source cell will not attempt a congestion relief handover to a target cell which has rejected
a previous non-imperative handover attempt for a period of time set by two timer parameters.
It does not, however, affect any imperative handover retries. These handovers are allowed to
take place regardless, as they are needed in order to keep the call active.

Directed Retry Version 1 Rev 4
Directed Retry
Standard
RSS RRSM SSM
Force handover request
Force handover response
IF ANY NEIGHBOURS MEET CRITERIA
Handover recognized
Handover recogized received

Pegs:
CONGEST_STAND_HO_ATMPT

Version 1 Rev 4 Congestion Relief
Congestion Relief
Congestion relief mechanisms
When instructed to execute the first of the congestion relief mechanism "handover needed TCHs"
the RRSM will canvas each instance of RSS in the cell with a candidate list query in a search for
suitable calls. To resolve congestion this mechanism will cause the RRSM to aim at handing over as
many calls as assignment requests queued in the CRM, the congestion indication message will
contain this number. A suitable candidate would be an existing call where the MS has reported
a neighbour meeting the congestion relief handover criteria. Each instance of RSS will in turn
respond with suitable candidates, specifying pbgt result. The RRSM will wait to receive all or most
of the candidate list response messages (timeout) and then construct the appropriate number of
handover recognised received messages based upon the best Pbgt results.
When instructed to execute the second of the congestion relief mechanism the RRSM will send
each instance of RSS in the cell concerned a force handover request message. This will cause
each RSS concerned to engage the congestion relief handover criteria and send handover
recognized messages for any candidates satisfying this new criteria.
CONGEST_EXIST_HO_ATMPT
In the case of either congestion relief mechanism being employed, upon receipt of the handover
recognized received message containing either the "handover needed TCHs" or "handover all TCHs"
cause values the SSM will increment this counter statistic. This statistic is incremented for both
intra-BSS and inter-BSS handovers. The handover itself will be executed in the normal way.
CONGEST_ASSIGN_HO_SUC
This counter statistic is incremented in the source cell for successful internal and external handovers
that were executed as a result of standard directed retry. In the case of external handovers the statistic
is incremented on receipt of the clear command from the MSC with cause value successful handover.
For the internal case the statistic will be incremented as the SSM transmits the handover performed to
the MSC. These procedures will covered in greater detail in the handover section of this course.
This statistic used as a pre GSR5 BSS.
ASSIGNMENT_REDIRECTION [DIRECTED_RETRY]
This statistic tracks the number if times a call assignment is successfully redirected
to another cell for standard directed retry reasons. This statistic is covered in more
detail in the handover section of this course.

Congestion Relief Version 1 Rev 4
Congestion Relief
"Handover Needed TCHs"
RSS RRSM SSM
RSS s Candidate list query
Candidate list query
CHECK IF CALLS
MEET CRTERIA
Candidate list response
Candidate list response Handover recognized received
Handover recognized received Pegs:
"Handover all TCHS"

RSS RRSM SSM
RSS Force handover request
Force handover request
Handover recognized Handover recognized received
Handover recognized
Handover recognized received
Handover recognized
Handover recognized received Pegs:

Version 1 Rev 4 TCH Assignment
TCH Assignment
ALLOC_TCH_FAIL
This counter statistic increments each time the CRM is unable to allocate a TCH channel within a cell due
to lack of resources for both call origination or hand in. Immediate Assignment Rejects are also pegged.
ALARM 25.CELL: Attempt at allocating an TCH failed - PM (major)
ALLOC_TCH_FAIL_HR
This statistic counts the number of unsuccessful HR (AMR) and/or HR (GSM) TCH
allocations within a cell for both call origination and hand in. I.A.R.s and unsuccessful
allocations due to directed retries are also pegged.
Note: For every failure of a TCH half rate channel, the combined statistic
ALLOC_TCH_FAIL and the statistic ALLOC_TCH_FAIL_HR will be pegged. A
further statistic called ALLOC_TCH_FAIL_FR is derived from these statistics.
For the correct calculation to be made ALLOC_TCH_FAIL statistic will be pegged twice for
a call with FR and HR capability. Where the non–preferred channel type is
successfully assigned a failure will be pegged for the preferred type.
When HR is disabled only ALLOC_TCH and ALLOC_TCH_FAIL will be pegged as all calls will be FR.

TCH Assignment Version 1 Rev 4
TCH Assignment
Blocked and Failure
MSC
SSM
Assignment request
RRSM Initiate assignment
CRM Assignment resource
request
All TCHs Busy
Resource not available

ALLOC_TCH_FAIL
ALLOC_TCH_FAIL_HR
Unsuccessful assignment
pegs:
Assignment failure
MA_CMD_TO_MS_BLKD

TCH Assignment
MA_CMD_TO_MS_BLKD
When no queueing is allowed or indeed is allowed but has reached a maximum
(queue_management_information), the CRM will send a resource not available message to the
RRSM informing it that the assignment request has been blocked through lack of resources. This
statistic is pegged by the RRSM on receipt of this message. This message will also be received for
the same reasons when an intra-cell handover is blocked, this too will increment this statistic.
ALARM 2.CELL: Mobile assign command to MS blocked (no channel available) - PM (minor)
MA_CMD_TO_MS
After the RRSM receives the assigned channel information from the CRM it will instruct the
RSS to activate the specified time slot before sending an assignment command to the MS
indicating the characteristics of its new TCH. This counter statistic is incremented at the
RRSM each time an assignment command is sent to an MS.
MA_FAIL_FROM_MS
Assuming the CRM can allocate a TCH, the RRSM will proceed to activate the new channel and
subsequently send the assignment command to the MS. The MS will, having received the assignment
command, attempt to gain a L2 connection with the new TCH. The MS will not try to make this
connection for an indefinite period and in fact an internal timer limits the duration allowed for this
procedure. If the MS has not established a L2 connection on the new TCH and the timer expires
then it will return to the original SDCCH and send an assignment failure to the BSS. On receipt
of this message the RRSM will increment this counter statistic. This statistic is also incremented
in the case of a failed intra-cell handover, this is detailed in the next section.
ALARM 23.CELL: Mobile assignment failure from MS - PM (warning)
SECOND_ASSIGN_ATMPT
If the BSS feature SECOND_ASSIGNMENT is set, should the first attempt at assignment fail, (i.e.
the MS returns to the SDCCH and report assignment failure) the RRSM will send a second channel
activation command. The RRSM will peg the counter SECOND_ASSIGN_ATMPT at this point.
SECOND_ASSIGN_SUC
If the second assignment attempt succeeds, the counter statistic SECOND_ASSIGN_SUC will peg.

TCH Assignment
Blocked and Failure
RRSM SSM
CRM
Assignment resource Initiate assignment
request
RSS Assignment channel
assigned
Physical context request
MS Physical context confirm

Channel activation
Assignment command
Assignment command pegs:
MA_CMD_TO_MS
Assignment failure Assignment failure
pegs:
(Second) assignment command MA_FAIL_FROM_MS
Assignment command
SECOND_ASSIGN_ATMPT
Assignment complete Assignment successful
SECOND_ASSIGN_SUC

TCH Assignment
Assignment delay
As previously mentioned it is possible for assignment requests to be queued, waiting for a TCH
to become available. It is also possible for a handover request to be queued under the same
scheme. For queueing to take place it must be indicated in the message originating from the
MSC, also certain database parameters in add_cell must be enabled.
TCH_DELAY
When an assignment or handover request is queued for a specific connection the CRM
starts an internal timer which is only stopped when a channel is allocated. The elapsed
time is recorded by this normal distribution statistic. This statistic is not incremented upon
BSSMAP_T11 expiry or if the call is cleared before assignment.

TCH Assignment
Assignment Delay
MSC
SSM
Assignment request
RRSM
Initiate assignment
CRM
Assignment resource
Start request
T11
Force queue
Assignment queued
Stop Queueing indication
Assignment channel
assignment
Increments:
TCH_DELAY

TCH Assignment
The complete TCH assignment procedure is detailed in the diagram opposite. When the RRSM receives
an assignment request from the SSM it will start GSM timer assign_successful for the specified SCCP
connection. This timer is stopped when the RRSM receives an assignment complete from the MS, in
turn the RRSM will then send an assignment successful to the SSM. If assign_successful is ever
allowed to expire a release request will be sent to the SSM, followed by a clear request to the MSC.
MA_COMPLETE_FROM_MS
This counter statistic tracks the number of assignment complete messages received from mobiles.
MA_COMPLETE_TO_MSC
This counter statistic is incremented in the SSM each time an assignment complete message is
forwarded to the MSC. It should be remembered that one call could have multiple assignments (e.g. if
the subscriber switches from voice to data). Directed retry will also affect this statistic as the assignment
complete message will sent from the new server and hence this statistic would not be incremented
in the old source but in fact in the new cell. The bins for this statistic are defined as follows:
Bin 0 - PM_FR
Bin 1 - PM_EFR
Bin 2 - PM_AMR FR
Bin 3 - PM_AMR HR
Bin 4 - PM_GSM_HR
Bin 6 - PM_Other
TOTAL_CALLS
This counter statistic is very similar to the one above. Each time a call is initially set up
and the assignment complete message is sent from SSM to the MSC this statistic will
be incremented. Subsequent channel changes (assignment procedures) within the same
connection will not cause this statistic to be incremented. Directed retry will also have a
similar affect on this statistic as it does on the one above.

TCH Assignment
Successful Assignment
SSM MSC
CRM RRSM Assignment request
Initiate assignment
Assignment
resource request
Assignment
RSS channel assigned
Physical context request

Physical context confirmed
Channel activation
MS assign_successful
Assignment command
Assignment complete assign_successful
MA_COMPLETE_FROM_MS
Assignment successful
SM
Connection
request
Switch response
Assignment complete
success
pegs:
TOTAL_CALLS
MA_COMPLETE_TO_MSC

Version 1 Rev 4 Downlink Bit Error Ratio (BER) Monitoring
Downlink Bit Error Ratio (BER) Monitoring

Whilst engaged on a TCH the MS will receive 100 downlink bursts from the BSS per SACCH multiframe.
Each burst is checked for quality and an individual BER determined. Using a unweighted algorithm
these 100 BER results are processed into an overall BER average for that SACCH multiframe. This
average is then encoded into a GSM defined quality band and sent to the BSS in an uplink measurement
report. The quality band that is reported to the BSS, for the previous SACCH multiframe, is then
converted to the equivalent assumed value before further averaging and processing by the HDPC.
Depending upon database parameters the assumed value may not be used and instead the reported
band figures are processed. The HDPC will then decide if the MS requires power control or a handover.
Stats
BER
The BER is a normal distribution statistic determined on a time slot basis and updated every SACCH
multiframe (480ms) by the downlink quality measurement reported by the MS.
U_BER
From GSR6 BER is calculated for the uplink. It has the same properties in any other respect as BER.

Downlink Bit Error Ratio (BER) Monitoring Version 1 Rev 4
Downlink Bit Error Ratio (BER) Monitoring
Uplink measurement report
Downlink transmission
GSM quality bands:

BER REPORTED ASSUMED
0 to 0.2 0 0.14
0.2 to 0.4 1 0.28
0.4 to 0.8 2 0.57
0.8 to 1.6 3 1.13
1.6 to 3.2 4 2.26
3.2 to 6.4 5 4.53
6.4 to 12.8 6 9.05
Greater than 12.8 7 18.1

Version 1 Rev 4 Frame Erasure Rate
Frame Erasure Rate

FER_GSM_FR_EFR
The uplink FER_GSM_FR_EFR statistic is derived from measuring the ratio of successfully
decoded GOOD speech frames to unsuccessfully decoded BAD speech frames each
480ms period by the RSS HDPC process.
The ratio calculated from the 24 x 20 ms vocoded speech frames received and decoded during a
480ms SACCH multiframe is used with a lookup table. It is converted to a FER quality number between
0 and 9, and the relevant bin is incremented, as is the Cumulative value of measurements.
The range of the bins in the array is not alterable and is as follows:
FER QUALITY ERASURE RATE

FER Quality Number FER Ratio (min to max)
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
Example:
On the air interface, the HDPC successfully decodes 22 frames of the 24 measured. The resulting
ratio of 2 to 24 (0.0833) results in a lookup table for FER_GSM_FR_EFR quality number of 2.
FER_AMR_FR
This statistic pegs the uplink frame erasure rate for AMR Full Rate calls for each carrier
in a cell and is measured on a TS basis for active channels.
FER_AMR_HR
This statistic pegs the uplink frame erasure rate for AMR Half Rate calls for
each carrier in a cell on a TS basis.
FER_GSM_HR
This statostic pegs the uplink frame erasure rate for GSM Half Rate calls for
each carrier in a cell on a TS basis.

Frame Erasure Rate Version 1 Rev 4
Frame Erasure Rate
bad frames vs all frames
CHAN CODERS HDPC LOOK UP TABLE
Normal Distribution
PEG
0 1 2 3 4 5 6 7 8 9
FER_GSM_FR_EFR FER_GSM_HR
FER_AMR_FR FER_AMR_HR

Version 1 Rev 4 Residual Bit Error Rate (RBER)
Residual Bit Error Rate (RBER)

Residual Bit Error Rate Quality (RBER_QUAL) is a normal distribution statistic having 8 bins which
records a quality number between 0 and 7 on a traffic channel timeslot. The quality number is obtained
via a look-up table from the measurement of a ratio of number of bits in error to the number of bits
received within error-detected speech frames defined as ‘GOOD’ on the air interface uplink .
The statistic is pegged within the HDPC process of the Radio Sub System every 480 ms. The
ratio calculated is taken from the 24 x 20 ms vocoded speech frames received and decoded
during a 480ms SACCH multiframe after the frames have been received, de-modulated,
de-interleaved and decoded by the Channel Coder devices.
The RBER Quality number is derived from the following relational look-up table:
RBER Quality Number Conversion

RBER Quality Number RBER Ratio (min to max)
0 0 to 0.2
1 0.2 to 0.4
2 0.4 to 0.8
3 0.8 to 1.6
4 1.6 to 3.2
5 3.2 to 6.4
6 6.4 to 12.8
7 12.8 and greater
The statistic is used for trend analysis for target optimization effects on cell/radios with regards to quality.

Residual Bit Error Rate (RBER) Version 1 Rev 4
Residual Bit Error Rate (RBER)
Error bits vs total bits
CHAN CODERS HDPC LOOK UP TABLE
Cumulative score
2800
RBER
2400
2000
1600
1200
PEG
800
400
0
0 1 2 3 4 5 6 7

Version 1 Rev 4 PATH_BALANCE
PATH_BALANCE
This normal distribution statistic provides link balance verification on a carrier basis, updated
every 480 ms. Path loss can be defined as the difference between the commanded power
level and that power level perceived by the receiving station. As such the following formula
is used to calculate this statistic on a SACCH multiframe basis.
Path Loss = Uplink path loss - Downlink path loss
where:
Uplink path loss = actual MS txpwr - rxlev_ul
Downlink path loss = actual BS txpwr - rxlev_dl
The rxlev_ul/dl values are the latest reported, they are not the averaged values.
PATH_BALANCE = Path Loss + 110
The result of the above equation is based around 110, the actual statistical result will equal path loss
plus 110. Typically the path loss should be similar in both the uplink and downlink directions. With
diversity gain enabled the path balance will be just below 110, indicating a lower uplink path loss.
Interpreting the results

Negative results (values below 110) indicate problems with the BTS transmit
equipment, antenna, RF cabling, filters etc.
Positive results (values above 110) indicate problems with the BTS receive equipment,
antenna, RF cabling, receive splitter, etc.
UPLINK_PATH_LOSS
The uplink path loss can be displayed as a statistic in its own right. This statistic is a
normal distribution and is updated every SACCH multiframe for every active call. However,
the value is a per-carrier average, and so is intended to give a profile of the radio link
propagation path rather than accurate measurements per call.

PATH_BALANCE Version 1 Rev 4
PATH_BALANCE
Path loss = Uplink path loss - Downlink path loss
where
Uplink path loss = actual MS txpwr - rxlev_ul

Downlink path loss = actual BS txpwr - rxlev_dl
PATH_BALANCE = Path loss +110

Version 1 Rev 4 Transmit Power Levels
Transmit Power Levels
CHAN_UL_TX_PWR_LVL and CHAN_DL_TX_PWR_LVL
The uplink and downlink transmit power levels can be tracked by the normal distribution
statistics CHAN_UL_TX_PWR_LVL and CHAN_DL_TX_PWR_LVL respectively. Both are
pegged in HDPC and updated every SACCH multiframe. They represent the average level
of each carrier, across all its time slots, in dBm. With power control, each time slot could be
using a different power level and so this average is intended as a guide to the average levels
in use in a cell rather than providing accurate per-channel data.

Transmit Power Levels Version 1 Rev 4
Transmit Power Levels
TX
TX
HPDC
CHAN_DL_TX_PWR_LVL
CHAN_UL_TX_PWR_LVL

Version 1 Rev 4 Call Clearing Statistics
Call Clearing Statistics
Ciphering
The ciphering procedure is detailed on the page opposite. It is initialized by the MSC sending a cipher
mode command to the SSM, this message specifies the permitted A5 algorithms that may be used,
cipher key (Kc) and also how the MS should respond. The SSM will decide the A5 version to be used
based upon relevant database parameters. The SSM will pass the ciphering request message to the
RRSM specifying the A5 algorithm to be used for this connection, it will also contain Kc and the MS
response mode, at this time the SSM will start GSM timer ciphering_successful. The RRSM will then
pass cipher mode command down to the MS via the RSS, at this time the RRSM will start an internal
timer, cipher_comp_ms. Kc of course is not sent to the MS. The correct reponses can be seen on the
page opposite, and of course, in normal operation, the timers will not expire. However if the timer in the
RRSM should expire, a radio channel released message will be sent to the SSM, which will in turn
cause the SSM to send a clear request to the MSC. If ciphering_successful should expire in the SSM
and no ciphering successful is received from the RRSM then a clear request will be sent to the MSC.
CIPHER_MODE_FAIL
In either situation if a clear request is sent to the MSC due to ciphering problems
then this statistic is incremented.
ALARM 6.CELL: Cipher mode command from MSC failed - PM (minor)

Call Clearing Statistics Version 1 Rev 4

Ciphering
SSM MSC
Cipher mode
RRSM
MS Ciphering request request
Ciphering mode
command
cipher_comp_ms ciphering_successful
cipher_mode_ms ciphering_successful
Ciphering mode
complete
Ciphering
Cipher mode
successful
complete
ciphering_successful
OR
Expires
No ciphering Clear request

successful peg:
received CIPHER_MODE_FAIL
CLR_REQ_TO_MSC

Version 1 Rev 4 Call Clearing Statistics

Whilst in dedicated mode the MS will transmit measurement reports to the BSS every SACCH
multiframe (480ms). The HDPC maintains a counter which will be decremented by one, should a
measurement report not arrive. The counter is called link_fail and its maximum value can be set within
the add_cell command of the database. If a series of measurement reports do not arrive at the BSS
then this obviously indicates that the uplink connection with the MS has been lost. In this situation
link_fail will successively be decrement and eventually reach zero, at this point the RSS will declare
link failure and inform the RRSM by sending an error indication message. The RRSM will instruct the
RSS to deactivate the TCH and also inform the SSM of the failure and subsequent release by sending
a radio channel released message. The SSM will then send a clear request to the MSC.
RF_LOSSES_TCH
This counter statistic is pegged on a time slot basis when the RRSM receives an error indication
message with channel type TCH. It should be noted that an error indication message contains
a cause value that can indicate a number of Layer 2 problems and therefore this statistic is
incremented for a number of reasons of which link failure is just one.
RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a per
timeslot level. The OMC-R rolls up the information up to cell level and refers to
this information as RF_LOSSES_TCH_ROLL.
ALARM 0.TIMESLOT: Radio frequency losses while using an TCH - PM (major)
RF_LOSSES_TCH_HR_AMR
This per timeslot statistic keeps a counter of the number of calls lost while using a Half Rate AMR TCH.
RF_LOSSES_SD
This counter statistic is pegged on a time slot basis when the RRSM receives an
error indication message with channel type SDCCH.
ALARM 0.CELL: Radio frequency losses while using an SDCCH - PM (major)

Call Clearing Statistics Version 1 Rev 4

RF Loss
MS RSS
Uplink measurement
report
Missing report
Missing report
Missing report Link_fail
Link failure
declared
RRSM Pegs:
RF_LOSSES_TCH_HR_AMR
SSM
RF_LOSSES_SD
or
Error indication RF_LOSSES_TCH
Radio channel MSC
released
Clear request
Pegs:
CLR_REQ_TO_MSC

Version 1 Rev 4 Classmark Updating
Classmark Updating
MS classmark information is sent by the MS to the BSS/MSC as part of the L3 initial

message which is sent when the MS tries to establish a signalling connection at L2 on the
SDCCH. The MS classmark information, depending on its type, specifies the MS’s capability
concerning frequency, power, SMS, cyphering and revision level.
It is possible that the MS or MSC may originate a classmark update procedure whilst the MS is already
engaged on a dedicated resource. An MS may originate this procedure if it were to change power class
during a call, the MSC may originate the procedure after a some kind of Visitor Location Register (VLR)
MS registration problem. The origination of a classmark update procedure by either party is a rare event.
CLASSMK_UPDATE_FAIL
The classmark updating procedure is shown opposite, in this example the MSC has
originated the process. This counter statistic is incremented by the RRSM when an update
classmark message has been received in protocol error.
ALARM 4.CELL: Class-mark update from MS protocol error - PM (minor)

Classmark Updating Version 1 Rev 4
Classmark Updating
MSC
SSM
RRSM
Classmark request
Request classmark
RSS
Classmark enquiry
Classmark change
Update classmark
Classmark update
pegs:
CLASSMK_UPDATE_FAIL

Version 1 Rev 4 Idle Interference Monitoring
Idle Interference Monitoring

When a TCH time slot is idle it is constantly monitored for any uplink ambient noise. During a
SACCH multiframe an idle time slot is monitored 104 times. These samples are then processed to
produce a noise level average per 480ms. This average is then reported to the HDPC, where it
is further averaged and processed. Periodically the HDPC will report the interference level of each
idle slot to the CRM, which will use this information in its channel allocation procedure.
Stats
INTF_ON_IDLE
This normal distribution statistic is time slot based, it is pegged in the HDPC and is updated
every 480ms by the latest calculated ambient noise level.
IDLE_TCH_INTF_BAND (n = 0 to 4)
Five gauge statistics are available to measure the average number of idle TCHs
in each of the five interferer bands. CRM pegs these statistics each time its idle
channel ranking information is updated by HDPC.
Available time slots

AVAILABLE_TCH
This gauge statistic is incremented and decremented as TCH time slots become enabled and
disabled. This number includes the time slots already busy. A TCH is considered available by
the CRM when its operational state is enabled and its administrative state is unlocked or shutting
down. A TCH is considered unavailable when its operational state is disabled or its administrative
state is locked. A TCH channel may be dynamically converted to an SDCCH slot under control
of the reconfiguration feature, which will also be reflected by this statistic.
AVAILABLE_TCH_HR_AMR
This statistic provides the mean and maximum number of available HR AMR TCH’s
that are in use or available to be used within the cell.
AVAILABLE_SDCCH
This gauge statistic is incremented and decremented as SDCCH time slots become enabled and
disabled. This number includes the sub-slots already busy. An SDCCH is considered available and
unavailable under much the same conditions as a TCH. As mentioned above a SDCCH channel
may be dynamically converted to an TCH slot which will also be reflected by this statistic.

Idle Interference Monitoring Version 1 Rev 4
Idle Interference Monitoring
IDLE TS
104 TDMA
FRAMES
CC HDPC
pegs: INTF_ON_IDLE
n= 0 1 2 3 4
IDLE_TCH_INTF_BAND (0-4)

Version 1 Rev 4 Timing Advance
Timing Advance
To simplify the design of the mobile, the GSM Recommendations specify an offset of three
time-slots between the BSS and MS timing thus avoiding the necessity for the mobile to transmit
and receive simultaneously. The facing diagram illustrates this.
However, the synchronisation of a TDMA system is critical because bursts have to be
transmitted and received within the “real-time” time slots allotted to them. The further the MS
is from the BSS then, obviously, the longer it will take for the bursts to travel the distance
between them. The GSM BSS caters for this problem by instructing the MS to advance its
timing (i.e. transmit earlier) to compensate for the increased propagation delay.This advance
is then superimposed upon the 3 time-slot nominal offset, as shown
Motorola supports a software feature called ‘Extended Range Cell’ or ERC that allows mobiles to use a
cell beyond the GSM specified 35 kilometre limit. At distances greater than 35 Km the propagation
delay exceeds the standard GSM timing advance of 63 bit periods or 233us. This timing advance is
sufficient for the two–way propagation delay between the BTS and the MS to be overcome.
From distances over 35km, the MS’s transmitted signal will begin to arrive in the following
timeslot, corrupting the data being processed in both timeslots. With the ERC feature
enabled, the BTS expands its receive window to cover both the MS allocated timeslot and
the following timeslot. This gives an effective 156 extra bit periods for the propagation
delay which increases the maximum cell radius to 121km.
. In simple terms, it is necessary to use two normal timeslots to form a single extended range timeslot.
Using two timeslots allows the BTS to handle additional propagation delay from the mobile. The
actual value of timing advance given to the MS can still only go up to 63 bit periods, but as the MS’s
transmit burst can be late by a whole timeslot at the BTS and still be decoded correctly.
ROC
This statistic tracks the maximum, minimum and mean Range Of Carrier between BSS and
MS on a per carrier basis. The range of carrier value corresponds to the timing advance (TA)
measurement reports. ROC statistic measurements are only reported for active channels.
The bin ranges for the ROC statistic correspond to a number of user definable TA ranges
up to a maximum of 10 bins. It is reported every 480ms.
BIN 0 — 0 to 6
BIN 1 — 7 to 13
BIN 2 —14 to 20
BIN 3 —21 to 27
BIN 4 —28 to 34
BIN 5 —35 to 41
BIN 6 —42 to 48
BIN 7 —49 to 54
BIN 8 —55 to 63
BIN 9 —64 to 219
These bins (defaults) are not displayed at the OMC but can be displayed at the MMI. To set and
display the bin ranges refer to the chg_stat_prop and disp_stat_prop commands.

Timing Advance Version 1 Rev 4
Timing Advance
Tx
BTS 1 2 3 4 5 6 7 0 1 2
Propagation Delay
Rx 1 2 3 4 5 6 7 0 1 2
MS
3 timeslot offset
Tx 6 7 0 1 2 3 4 5 6 7
MS
Propagation Delay
Rx 6 7 0 1 2 3 4 5 6 7
BTS
To prevent the burst from moving from its timeslot into a neighbouring timeslot a timing advance
is introduced to send the burst earlier therefore overcoming the propogation delay
The maximum timing advance for a normal range timeslot is 63 bit or a propogation distance of
35 km radius anymore than this and it runs into the next timeslot.
Extended range allows the complete use of the next timeslot, hence a further 156 bits, which
together with the 63 bits from the primary timeslot gives a radius of 121 km

Version 1 Rev 4 SMS Performance
SMS Performance
Point-to-point
SMS point-to-point provides a means to transfer messages between the MS and short message
entity via a service centre. SMS can be MS originated or MS terminated. Messages can be
transferred on an SDCCH, should the MS be idle at the time of origination, or SACCH, should
the MS already be in dedicated mode. Before an SMS can be transferred to an MS a Layer 2
connection using SAPI 3 must be established, however before the establishment of SAPI 3 a
connection at SAPI 0 must first exist. The flow diagrams opposite follow the establishment of a
Layer 2 connection using SAPI 3 for both MS terminating and originating cases.
SMS_INIT_ON_SDCCH
This counter statistic is incremented in the RRSM each time an establish indication or
establish confirm is received from RSS on an SDCCH channel.
SMS_INIT_ON_TCH
This counter statistic is incremented in the RRSM each time an establish indication or
establish confirm is received from RSS on an TCH channel.
Cell Broadcast (CB)

The CB feature enables the MS to receive unacknowledged information messages of a general nature
such as traffic conditions, advertisements etc. The MS can only receive these messages whilst idle
and indeed has to be configured to do so using the MS’s MMI. These messages generally originate
from a Cell Broadcast Centre (CBC) which has an X.25 SVC link to the BSC. In addition to messages
from a CBC a number of background messages can be initiated using the base stations customer
MMI. The two software entities controlling this feature are called the Cell Broadcast Agent (CBA) and
the Cell Broadcast Scheduler (CBS) which are located at the BSC and the BTS respectively.
SMS_NO_BCAST_MSG
Each time a CB message is transmitted on the air-interface this counter is incremented,
the statistic is pegged in the CBS.

SMS Performance Version 1 Rev 4
SMS Performance
MS ORIGINATING
SAPI 0 connection
already established RSS
MS RRSM
SABM SAPI 3 pegs:
SSM
SMS_INIT_ON_SDCCH
MSC
UA or
Establish indication SMS_INIT_ON_TCH
(SAPI 3)
SMS DATA
Data indication
<DTAP>
(Link id SAPI 3) <DTAP>
MS TERMINATING RSS
SSM RRSM MS
MSC
<DTAP> SAPI 0 connection
<DTAP> already established
Short message
Establish request
SABM SAPI 3
(SAPI 3)
pegs: Unnumbered
Establish confirm
Acknowledgement
SMS_INIT_ON_SDCCH
or (UA)
SMS_INIT_ON_TCH Data request
SMS data

Version 1 Rev 4 Emergency Access
Emergency Access
When a MS makes an emergency call, by dialling 112, the series of events that follow to set up the call
will differ significantly from the usual call set-up process. The channel request message contains a
special emergency cause value (101). Receiving this cause value the CRM will immediately try to
allocate a TCH, the SDCCH stage is bypassed, this is called the immediate assign mode. Limited call
set-up procedures will take place on the TCH and the call will continue on the same time slot. If no
TCH is available the MS will be allocated an SDCCH and queue for a TCH in the usual way.
A feature exists in the BSS called emergency pre-emption and can be enabled using customer
MMI. This feature enables the BSS to dislodge a call currently in progress in order to allocated the
emergency request the newly available resource. When the feature is enabled and an emergency
channel request is received, if no TCHs are available then the MS will be allocated an SDCCH whilst a
current call in progress is dislodged. In the unlikely event that no SDCCHs are available either then
the MS is sent an immediate assignment reject message, in the meantime the BSS will dislodge a
call in progress in anticipation of the channel request being repeated after the wait period (expiration
of T3122). A number of statistic are based on the treatment of an emergency request.
Stats
NUM_EMERG_ACCESS
This counter statistic is incremented in the CRM each time a channel request received
message is received having an emergency call value. This statistic is incremented regardless
of the emergency pre-emption feature being enabled.
NUM_EMERG_REJECTED
This counter statistic is incremented in the CRM each time an immediate assignment reject
is sent to the MS indicating that no resource, TCH or SDCCH , is available. This statistic is
incremented regardless of the emergency pre-emption feature being enabled.
NUM_EMERG_TCH_KILL
This counter statistic is incremented in the CRM and indicates the number of TCHs torn
down to allow an emergency request to use the freed resource. This statistic is only
incremented if the emergency pre-emption feature is enabled.
NUM_EMERG_TERM_SDCCH
This counter statistic is incremented in the CRM and indicates the number of emergency calls
which although allocated a SDCCH could not be subsequently assigned a TCH. This statistic is
incremented regardless of the emergency pre-emption feature being enabled.

Emergency Access Version 1 Rev 4
Emergency Access
MS RSS RSS A BIS RRSM

Channel request
(emergency) Channel request
Channel required
CRM
pegs: Channel request
NUM_EMERG_ACCESS received
(value 101)
Channel
RSS assigned
(TCH)
Immediate
assignment
SABM
(L3 inital message) Establish indicator
pegs:
UA (CM SERVICE REQUEST EMERGENCY) OK_ACC_PROC
[CM_SERV_EME]
RRSM
CRM
Channel request
MS NO SDCCH
received
NO TCH
Reject pegs:
(Wait indication) NUM_EMERG_REJECTED

Version 1 Rev 4 Ater Emergency Pre-empt Status
Ater Emergency Pre-empt Status

A new statistic has been introduced at GSR7 ATER_EMERG_PREEMPT_STATUS for the BSC
that tracks the preemption of Aters for emergency calls related to Ater allocation scenarios
and any failed assignments due to communication failure with the RXCDR. This statistic will
be applicable in both Auto Connect and Enhanced Auto Connect modes.
Stats
Bin 0 - EMERG_PREEMPT_ATMPT
This BSC statistic tracks on a per AXCDR basis the number of preemption
attempts made for emergency calls.
Bin 1 - EMERG_PREEMPT_ATMPT_CALL_SETUP
This BSC statistic tracks on a per AXCDR basis the number of preemption attempts
due to no available Aters for emergency call setups.
Bin 2 - EMERG_PREEMPT_ATMPT_ATER_SWITCH
This BSC statistic tracks on a per AXCDR basis the number of preemption attempts due
to the switchover of Ater channels for emergency calls.
Bin 3 - EMERG_PREEMPT_FAIL
This BSC statistic tracks on a per AXCDR basis the number of preemption attempts that fail
due to BSC-RXCDR communication failure for emergency calls.

Ater Emergency Pre-empt Status Version 1 Rev 4
Ater Emergency Pre-empt Status
Preempt attempt EMERG_PREEMPT_ATMPT
MSC RXCDR BSC
EMERG_PREEMPT_ATMPT_CALL_SETUP
Pre-empt
No Aters available - preempt attempt
MSC RXCDR BSC
Emerg call
EMERG_PREEMPT_ATMPT_ATER_SWITCH
Pre-
empt
MSC RXCDR BSC

Switchover
After chans
EMERG_PREEMPT_FAIL
Pre-empt Fail
Comms error
MSC RXCDR BSC
Ater chans

Version 1 Rev 4 Flow Control
Flow Control
Invocation of the flow control process at the CRM can be initiated from the CRM itself, the
RSS, SSM, or from the MSC. The overload procedure, which protects against overload both
within the BSS and also at the MSC, operates by temporarily barring randomly-chosen mobile
station access classes, one by one, until the overload is relieved.
The messages indicating the onset of process overload can be seen on the opposite page. The Flow
Control procedure is quite simple in that on receipt of any of the specified messages, the CRM will
dynamically alter the BCCH system information messages to reflect the barring of an access class. As
more messages are received thus more access classes are barred which should lighten the load the
BSS is temporarily suffering. There are internal CRM timers (T1 and T2, set by FLOW_CONTROL_t1
and FLOW_CONTROL_t2 respectively) which control the barring and unbarring of these access classes.
Stats
FLOW_CONTROL_BARRED
This durational statistic is processed in the CRM. When the first overload message is received,
a pair of internal timers (T1 and T2) are started, and during the period that follows a number of
access classes will be barred and unbarred. When the timer sequence stops, the last access class
is unbarred. The elapsed time is added to the total duration for that period.
MSC_OVLD_MSGS_RX
This counter statistic records the number of Overload messages received from
the MSC. It is pegged at the SSM.

Flow Control Version 1 Rev 4
Flow Control
CRM
Overload onset
RCI
OR
RSS overload
SSM
OR
MSC_OVLD_MSGS_RX
MSC
Overload onset
OR
MSC overload
FLOW_CONTROL_BARRED

Version 1 Rev 4 Call Establishment Exercise
Call Establishment Exercise
The interprocess message shown opposite has resulted in an MS being able to establish on a TCH.
Insert the incremented statistics at the appropriate software process at each stage of the establishment.

Call Establishment Exercise Version 1 Rev 4
Call Establishment Exercise

RSS
MS L1 ABIS RRSM CRM SM SSM MSC
Channel
request Channel
request Channel
required Channel 4 SDCCHs are available
required received
RSS Channel
Channel activation
assigned
Channel activation
acknowledge
Immediate Immediate assignment
assignment
L2 SABM Establish indication Initial L3 information
<CR>
CM service request CM Service request Complete L3
information
<CC>
L3 CALL SET UP MESSAGES
Initiate assignment Assignment
request
Assignment resource
request 3 TCH's available
ACTIVATION Assignment channel
Assignment command assigned
Assignment complete Assignment successful
Connection request
Switch response Assignment
success complete

Version 1 Rev 4 Call Establishment Exercise

Handover Statistics Version 1 Rev 4
Chapter 5
Handover Statistics

Version 1 Rev 4 Handover Statistics

Handover Statistics Version 1 Rev 4
Handover Statistics
Objectives
• Name the three handover statistics groups.
• Indicate where each handover statistic is incremented given related ladder
diagrams and the W56 manual.

Version 1 Rev 4 Introduction
Introduction
The statistics generated during handovers will now be considered. There are three
distinct handover types, these are detailed below:
Intra-cell handover statistics.

An intra-cell handover occurs when an MS is transferred from one channel to another within
a cell. This type of handover is normally controlled by the BSC.
Intra-BSS handover statistics.

This type of handover involves an MS being transferred from one cell to another, when both cells
are being controlled by the same BSC. This type of handover is generally controlled by the BSC
although for reasons of subscription or potential congestion can be controlled by the MSC.
Inter-BSS handover statistics.

This type of handover involves an MS being transferred from one cell to another,
when the target cell is controlled by a different BSC to that of the source cell. This
type of handover is alway controlled by the MSC.
Internal/External
Further to the above definitions there are also two categories of handover to consider. Internal
handovers are those controlled by the BSC, in general these will be intra-cell or intra-BSS.
External handovers are those controlled by the MSC, these will normally be inter-BSS. It is
worth noting that both intra-cell and intra-BSS could be controlled by the MSC, depending upon
database parameters resident in the SSM. In these cases the handover will be considered
external and will increment only the inter-BSS handover statistics.
An operator may wish the MSC to control certain handovers, the advantages of this include
consideration of congestion, handover queueing at the BSS and handovers related to subscription.

Introduction Version 1 Rev 4
Introduction
Handover Statistics
MSC
BSC BSC
BTS BTS BTS BTS
INTRA-BSS INTER-BSS INTRA-CELL

HANDOVER HANDOVER HANDOVER

Version 1 Rev 4 Handover Initiation
Handover Initiation
The RSS will initiate the handover sequence when the HDPC sends a handover recognized message
to the RRSM. This message will contain a cause value plus a number of "qualified" neighbours for a
specified connection. The RRSM will transfer this message as a handover recognized received
message to the SSM. Upon receipt of this message the BSC must decide the type of handover that
should take place for this connection, one of intra-cell, intra-BSS or inter-BSS and also the entity that
shall control the handover either, the BSC or the MSC. The type of handover can be influenced by
the cause value and also the neighbour types, internal or external, being expressed in the message.
If the list of targets contain no neighbours then this can also affect the handover type.
The decision as to the controlling entity will be influenced upon two database parameters found
in add_cell, intra_cell_handover_allowed and inter_cell_handover_allowed. Inter-BSS
handovers, if permitted, will always be controlled by the MSC.

Handover Initiation Version 1 Rev 4
Handover Initiation
RSS
RRSM SSM
HDPC
Handover recognised
<CAUSE>
plus neighbours Handover recognized received
<N1><N2><N3>...

Version 1 Rev 4 Intra-Cell Statistics
Intra-Cell Statistics
An example of a successful intra-cell handover sequence is shown opposite.
Intra–cell handovers can occur for congestion related full–rate to half–rate intra–cell handovers,
half–rate to full–rate intracell handovers. The detection of interference handovers has to
be enabled in add_cell along with the SSM element intra_cell_handover_allowed. When
the cause value is interference the SSM will always attempt an intra-cell handover first and
only if this is blocked will any specified targets be considered.
Stats
INTRA_CELL_HO_REQ
This counter statistic is incremented in the SSM each time an intra-cell handover is considered the best
option by the handover evaluator process. The statistic is pegged just before sending the initiate intra-
cell handover message to the CRM. The value is held in a bin of the counter array INTRA_CELL_HO.
INTRA_CELL_HO_ATMPT
This counter statistic is incremented in the RRSM after the channel activation message is received
from the RSS and just before the assignment command is sent to the MS. Its value is held at the
SSM in a bin of the counter array INTRA_CELL_HO. From GSR 7 it has been split into four bins to
support AMR. It has been enhanced to count the number of congestion related full-rate to half-rate
intra-cell handovers, half-rate to full-rate intracell handovers. The four bins are:
INTRA_CELL_HO_ATMPT_FR_FR
INTRA_CELL_HO_ATMPT_HR_HR
INTRA_CELL_HO_ATMPT_HR_FR
INTRA_CELL_HO_ATMPT_FR_HR
MA_CMD_TO_MS
This statistic was covered in the previous section, but it is worth noting that it is incremented each time
an assignment command is sent to the MS, which of course also includes intra-cell handovers.
INTRA_CELL_HO_SUC
This counter statistic is incremented in the SSM each time a handover performed message is sent to
the MSC due to an intra-cell handover. Its value is held in a bin of the counter array INTRA_CELL_HO.
INTRA_BSS_HO_CAUSE_SUC
This tracks the number of handovers in a BSS on a per cause basis. It is a counter array with
the same bins defined as OUT_HO_NC_CAUSE_ATMPT, but pegs when the handover performed
message is sent to the MSC to indicate that a successful handover has occurred.
ER_INTRA_CELL_HO_ATMPT
This is a small counter array that tracks intra-cell handover attempts between extended and normal
range channels in either direction. It is pegged at the SSM whenever the handover evaluator decides
that an extended range intra-cell handover is the best option for the call. It is also important to note
that this is the only statistic pegged for an extended range intra-cell handover, in addition to CV of
interference UL or DL; no other intra-cell handover statistic is pegged under these circumstances.

Intra-Cell Statistics Version 1 Rev 4
Successful Intra-cell Handover Sequence
RSS RRSM SSM

ho_recognised
ho_rec received
SSM decides intra cell
CRM pegs:
INTRA_CELL_HO_REQ
Initiate intra cell handover may peg:
Internal ho ZONE_CHANGE_ATMPT
assignment Internal ho initated
SM
Transfer request
Internal ho initiated
Internal ho ack
assignment ack Switch response
Physical context
request
Physical context
confirm
Channel activation
Channel activation ack INTRA_CELL_HO_ATMPT may peg:
MS Assignment cmd ER_INTRA_CELL_HO_SUC
MSC
Assignment MA_CMD_TO_MS
ZONE_CHANGE_SUC
cmd (FACCH)
SABM Establish indication
UA
Assignment complete
Assignment
(FACCH) successful ho perf
INTRA_CELL_HO_SUC

Version 1 Rev 4 Intra-Cell Statistics
ER_INTRA_CELL_HO_SUC
This small counter array tracks successful intra-cell handovers between extended and normal range
channels. It is pegged at the SSM when the assignment_successful message is received.
ZONE_CHANGE_ATMPT
This counter statistic is pegged at the SSM whenever a zone change is
attempted in aconcentric cell. If the zone change is successful then
ZONE_CHANGE_SUC is also pegged when the assignment_successful
message arrives. Both peg under the following circumstances:
• Inner to outer zone handover.

• Outer to inner zone handover.
• Handovers between different carriers in the inner zone.
• TCH assignment to the inner zone.
• Incoming inter-cell handovers directly into the inner zone.
Bin 0 — INNER_TO_OUTER_ZONE Number of handover attempts from inner zone to outer zone.
Bin 1 — OUTER_TO_INNER_ZONE Number of handover attempts from outer zone to inner zone.
Bin 2 — INTRA_ZONE Number of intra-zone handover attempts.
Bin 3 — TCH_ASSIGN_TO_INNER_ZONE Number of TCH assignment attempts to inner zone cells.
Bin 4 — IN_INTER_CELL_HO_TO_IN_ZONE Number of internal inter-cell
handover attempts to inner zone.
ZONE_CHANGE_SUC
The ZONE_CHANGE_SUC statistic tracks each type of successful Concentric Cell specific handover.
The Concentric Cell option must be enabled for this statistic to be enabled, disabled, or displayed.
Bin 0 — INNER_TO_OUTER_ZONE Number of successful handovers from inner zone to outer zone.
Bin1 — OUTER_TO_INNER_ZONE Number of successful handovers from outer zone to inner zone.
Bin 2 — INTRA_ZONE Number of successful intra-zone handovers.
Bin 3 — TCH_ASSIGN_TO_INNER_ZONE Number of successful TCH assignments to inner zone cells.
Bin 4 — IN_INTER_CELL_HO_TO_IN_ZONE Number of successful internal
inter-cell handovers to inner zone.

Intra-Cell Statistics Version 1 Rev 4
Successful Intra-cell Handover Sequence
RSS RRSM SSM

ho_recognised
ho_rec received
SSM decides intra cell
CRM pegs:
INTRA_CELL_HO_REQ
Initiate intra cell ho may peg:
Internal ho ZONE_CHANGE_ATMPT
assignment Internal ho initated
SM
Transfer request
Internal ho initiated
Internal ho ack
assignment ack Switch response
Physical context
request
Physical context
confirm
Channel activation
Channel activation ack INTRA_CELL_HO_ATMPT may peg:
MS Assignment cmd ER_INTRA_CELL_HO_SUC
MSC
Assignment MA_CMD_TO_MS
ZONE_CHANGE_SUC
cmd (FACCH)
SABM Establish indication
UA
Assignment complete
Assignment
(FACCH) successful ho perf
INTRA_CELL_HO_SUC

Version 1 Rev 4 Intra-Cell Handover Scenarios
Intra-Cell Handover Scenarios

Stats
INTRA_CELL_HO_RETURN
Upon receipt of the assignment command the MS will essentially attempt to gain L2 establishment
with the new TCH, if this attempt is not possible due to an incorrectly formatted or erroneous
assignment command then the MS will send the assignment failure message in the old TCH. When
the MS does attempt to gain a connection with the new TCH but fails due establishment problems
or if establishment is not gained within a certain time, the MS will return to the old TCH and transmit
the assignment failure message. This information is passed to the SSM as an unsuccessful
assignment, which internally generates a revert to old channel message. At this moment this statistic
is incremented. Its value is held in a bin of the counter array INTRA_CELL_HO.
MA_CMD_TO_MS_BLKD
Although this statistic is already covered in the previous section it is worth noting that it is also
incremented in the case of resources not available for an intra-cell handover.
MA_FAIL_FROM_MS
This statistic is also covered in the previous section and again it is worth noting that an intra-cell
handover resulting in an assignment failure message will increment this statistic.
INTRA_CELL_EQUIP_FAIL
If the assignment failure contains the cause "equipment failure" or if the Switch Manager (SM)
reports a KSW/highway fault in the switch response message, then the handover can be said
to have failed due to equipment failure. This increments the INTRA_CELL_EQUIP_FAIL
bin of the INTRA_CELL_HO counter array statistic.
HO_FAIL_NO_RESOURCES
This is pegged every time the target CRM of a handover cannot allocate resources. It
is a counter array and tracks all handover types.

Intra-Cell Handover Scenarios Version 1 Rev 4
Failed Intra-Cell Handover

MS RRSM
SSM
Assignment failure Pegs:
MA_FAIL_FROM_MS
Unsuccessful assignment
INTRA_CELL_EQUIP_FAIL
Blocked Intra-Cell Handover

CRM SSM
Initiate intra cell handover
Handover resource not available
ALLOC_TCH_FAIL
ALLOC_SDCCH_FAIL

Version 1 Rev 4 Intra-Cell Handover Scenarios

There are a number of reasons why a mobile is pegged as "lost" by the BSS for intra-cell
handovers. For an example two reasons are listed below, however this is not an
exhaustive list and there can be many more reasons.
Mobile Lost
Reason 1
Intra cell handover - MS transmits L2 establishment SABM N200+1 times to target cell,
BTS sends a L2 UA acknowledgement for each SABM, MS fails to receive UA. Subsequently
MS transmits L2 establishment SABM N200+1 times to source cell, BTS sends a L2 UA
acknowledgement for each SABM, MS fails to receive UA.
Reason 2
Intra cell handover - BTS transmits ASSIGNMENT COMMAND N200+1 times, MS
fails to receive ASSIGNMENT COMMAND
INTRA_CELL_HO_LOSTMS
Upon sending the assignment command the RRSM will start an internal timer, t10 (BSSMAP_t10).
If this timer is allowed to expire and no assignment complete or assignment failure is received
the RRSM will release both the old and new channels and simultaneously send the SSM a radio
channel released message. Upon receipt of this message the SSM will clear the connection and
increment this statistic. Its value is held in a bin of the counter array INTRA_CELL_HO.
OUT_INTRA_BSS_HO_LOSTMS
This bin of OUT_INTRA_BSS_HO pegs if the the MS fails to return to original channel during
a handover attempt if the new soucre cell channel could not be seized.
Call Cleared
Number of outgoing/incoming intra-cell handovers aborted due to call clearing. This
scenario corresponds to the receipt of a Clear Command, SCCP Released, or Release
Done (internal message) during the handover procedure.
INTRA_CELL_HO_CLEARED
This bin of INTRA_CELL_HO is pegged every time a call is cleared down during an intra_cell handover.

Intra-Cell Handover Scenarios Version 1 Rev 4

Mobile Lost
MS RRSM
t10
Assignment command
Expiry
assignment not complete

or
assignment failure
SSM
t10
Pegs
Expired INTRA_CELL_HO_LOST_MS
CLR_REQ_TO_MSC
Radio channel released INTRA_CELL_HO_CLEARED

Version 1 Rev 4 Intra-Cell Handover Tracking
Intra-Cell Handover Tracking

Several statistics that apply to intra-cell handovers are "rolled up" into a single counter array
statistic, INTRA_CELL_HO. Each statistic is held in a bin of the array as shown below,
and can only be displayed as part of the array, not individually:
BIN
0 = INTRA_CELL_HO_REQ
1 = INTRA_CELL_HO_ATMPT_FR_FR
2 = INTRA_CELL_HO_ATMPT_HR_HR
3 = INTRA_CELL_HO_ATMPT_HR_FR
4 = INTRA_CELL_HO_ATMPT_FR_HR
5 = INTRA_CELL_HO_SUC
6 = INTRA_CELL_HO_LOSTMS
7 = INTRA_CELL_HO_RETURN
8 = INTRA_CELL_EQUIP_FAIL
9 = INTRA_CELL_HO_CLEARED

Intra-Cell Handover Tracking Version 1 Rev 4
Intra-Cell Handover Tracking
BIN
0 = INTRA_CELL_HO_REQ
1 = INTRA_CELL_HO_ATMPT_FR_FR
2 = INTRA_CELL_HO_ATMPT_HR_HR
3 = INTRA_CELL_HO_ATMPT_HR_FR
4 = INTRA_CELL_HO_ATMPT_FR_HR
5 = INTRA_CELL_HO_SUC
6 = INTRA_CELL_HO_LOSTMS
7 = INTRA_CELL_HO_RETURN
8 = INTRA_CELL_EQUIP_FAIL
9 = INTRA_CELL_HO_CLEARED

Version 1 Rev 4 Neighbour Cell Statistics
Neighbour Cell Statistics

Outline
When the BSS is configured to control inter-cell handovers, four neighbour cell handover
statistics may be used to track handovers. These neighbour statistics provide detailed tracking
information about the destination cell of an outgoing handover or the origination cell of an incoming
handover. The following statistics can be enabled in the BSS software:
IN_INTRA_BSS_NC_ATMPT
IN_INTRA_BSS_NC_SUC
OUT_HO_NC_CAUSE_ATMPT
OUT_HO_NC_SUC
Neighbour Cell statistics provide an opportunity to carry out detailed analysis of cell
handover performance for a limited number of selected cells within a network. These
statistics can only be enabled for 16 cells within a BSS. The cells at which each of the
four statistics are enabled do not have to be the same.
IN_INTRA_BSS_NC statistics. The two statistics which are incremented in the target cell (IN.....) can
only be pegged for 32 different source cells. Priority is given to reciprocal neighbours first, then
source cells are chosen on a increasing sequential basis using the local cell identity.
A reciprocal neighbour occurs when both the source cell and the target cell
have each other as a neighbour.
OUT_HO_NC statistics. The two statistics which are incremented in the source cell
(OUT.....) will be pegged for up to 32 neighbours, but as this is the maximum number of
SACCH neighbours permissible, no real limitation exists.
As an example, this statistic which is a 12-bin array records outgoing handover causes from a selected
source cell to each of up to 32 neighbour cells. It may be pegged for up to 16 source cells.

Neighbour Cell Statistics Version 1 Rev 4
Neighbour Cell Statistics
Cells 1–16
OUT_HO_NC_CAUSE_ATMPT - Cell 0
Cause UpQual UpLev DnQual DnLev Upinterf..
Neighbour
NC1 X X X X X
NC2 X X X X X
NC3 X X X X X
NC4 Etc
NC5
.
.
.
.
.
NC32

Version 1 Rev 4 Intra-BSS Statistics
Intra-BSS Statistics
An example of a successful intra-BSS handover sequence is shown opposite.
Stats
OUT_INTRA_BSS_HO_REQ
This counter statistic is pegged each time the SSM decides to commit an intra-BSS handover. The SSM
will only allow an intra-BSS handover if the SSM element inter_cell_handover_allowed is enabled in
the correct way. Primarily the SSM will decide on an intra-BSS handover if the first neighbour specified
in the handover recognized message is internal. Its value is held in a bin of OUT_INTRA_BSS_HO.
IN_INTRA_BSS_NC_ATMPT
This statistic is incremented after handover allocation is received from the target RRSM. It is pegged on
a neighbour basis in that it is incremented in the target cell against a specific source.
The procedure that follows involves the SSM requesting resources from the target CRM, the
CRM allocates the resource and informs the target RRSM which in turn activates the new
TCH via the RSS. Upon completion of this activation the RRSM will acknowledge the original
internal handover request with a handover allocation message, this provides the SSM with
the characteristics of the new TCH which now awaits the MS’s arrival.

Intra-BSS Statistics Version 1 Rev 4
Successful Intra-BSS Handover Sequence
RSS (S) RRSM (S) SSM

ho_rec
ho_rec received
OUT_INTRA_BS S_HO_REQ
CRM (T)
Internal handover request
IN - (pegged for target )

RRSM (T) OUT - (pegged for source)
ho_channel NC - per neighbour
assigned
RSS(T)
Channel act
Channel act ack
MS power control
Handover allocation
IN_INTRA_BS S_NC_ATMPT

OUT_INTRA_BSS_HO_ATMPT
The SSM will initiate the transfer of the MS to the target resource specified in the handover
allocation message received from the target RRSM, by sending the initiate handover
message. Upon sending this message this counter statistic is incremented for the source
cell. Its value is held in a bin of OUT_INTRA_BSS_HO.
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in
the source relative to a neighbour and a specified cause value. In the internal case this statistic is
incremented at the same time as the one above, when the initiate handover message is sent to
the source RRSM. For the case of AMR the statistic has been altered in the following way. In the
case of FR to HR congestion based intra-cell handovers, the congestion bin will be pegged. HR
quality based intra-cell handovers will cause the DOWNINTERF or UPINTERF bin to be pegged.
This statistic utilises a counter array containing the following bin definitions:
Bin Cause Description

0 UPQUAL Handovers due to uplink quality.
1 UPLEVEL Handovers due to uplink level.
2 DOWNQUAL Handovers due to downlink quality.
3 DOWNLEVEL Handovers due to downlink level.
4 DISTANCE Handovers due to distance.
5 UPINTERF Handovers due to uplink interference.
6 DOWNINTERF Handovers due to downlink interference.
7 POWERBDGT Handovers due to power budget.
8 CONGESTION Handovers due to congestion.
9 ADJ_CHAN_INTF Handovers due to adjacent channel
interference.
10 BAND_RE_ASSIGN Handovers due to band reassignment.
11 BAND_HANDOVER Handovers between bands.
The cause value for congestion includes standard directed retry and both congestion relief mechanisms.

MS RSS (S) RRSM (S) SSM

Initiate handover
ho_cmd OUT_INTRA_BSS_HO_ATMPT
ho_cmd OUT_HO_NC_CAUSE_A TMPT
<FACCH> OUT_HO_CAUSE_ATMPT
RSS(T) INTERBAND_ACTIVITY
ho_access <FACCH> RRSM(T)
ho_access
ho_access
ho_access
ho_detection SM
ho_detect received
Phys info Trans req
SABM
Establish indication Switch resp
UA
ho_cmplt
ho_cmplt MTP
ho_succ
ho_performed
IN_INTRA_BS S_HO_SUC
OUT_INTRA_BS S_HO_SUC
IN_INTRA_BS S_NC_SUC
OUT_HO_NC_SUC
ASSIGNMENT_REDIRECTION

OUT_HO_CAUSE_ATMPT
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is very
similar to the statistic above and indeed is incremented at the same time. The difference
is that this statistic is not incremented on a neighbour basis and merely shows the total
number of attempted handovers out of the source cell with a breakdown per cause value.
The counter array values are the same as those shown above.
INTERBAND_ACTIVITY
This counter array statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It counts
the number of handovers initiated to each frequency band (PGSM, EGSM, DCS1800 and DCS1900),
but is also pegged when a multiband handover fails due to incorrect frequency information.
Its counter bins are as follows:

0 PGSM_HO_ATMPT Handover attempts to PGSM.
1 EGSM_HO_ATMPT Handover attempts to EGSM.
2 DCS1800_HO_ATMPT Handover attempts to DCS1800.
3 PCS1900_HO_ATMPT Handover attempts to PCS1900.
4 PGSM_HO_FAIL Handover failures to PGSM.
5 EGSM_HO_FAIL Handover failures to EGSM.
6 DCS1800_HO_FAIL Handover failures to DCS1800.
7 PCS1900_HO_FAIL Handover failures to PCS1900.
8 INVALID_FREQ_ASGN Freq not implemented - asgn.
9 INVALID_FREQ_HO Freq not implemented - ho.


Initiate handover
ho_access
ho_access
ho_access
ho_detection SM
ho_detect received
Phys info Trans req
SABM
UA
ho_cmplt
ho_cmplt MTP
ho_succ
ho_performed
OUT_HO_NC_SUC

Version 1 Rev 4 Successful Intra-BSS Handover Sequence

Upon receipt of the initiate handover message the RRSM will format the air-interface handover
command, this is sent via the RSS to the MS. The command is delivered on the Fast Associated
Control Channel (FACCH) , and provides the MS with details of the target TCH, these details
will include characteristics such as the time slot, frequency, Training Sequence Code (TSC),
handover reference number and an indication of synchronization.
The MS will alter its air-interface characteristics and will attempt gain firstly a L1 then a L2
connection with the target RSS. The procedure shown opposite assumes the handover is
asynchronous, and thus the MS transmits a continuous flow of L1 access bursts until it receives
the physical information message (containing timing advance information) when it will then
attempt L2 establishment. In the synchronized case where the MS has been able to calculate the
relevant timing advance necessary, a physical information message is not necessary, the MS
will send 4 consecutive L1 access bursts before attempting L2 establishment.
When the target RSS detects the MS at Layer 1 it will report this event to the RRSM which in turn
reports to the SSM. The detection procedure allows the SSM time to control the relevant switch transfer.
When the MS has gained L2 establishment with the RSS it will send a L3 handover complete
message which is passed to the SSM as a handover succesful message. Upon receipt of this
the SSM will format and send a handover performed message to the MSC. After the SSM
has transmitted this message a number of statistics are incremented.
Stats
IN_INTRA_BSS_HO_SUC
This statistic is pegged for the target cell and is not source cell related.
OUT_INTRA_BSS_HO_SUC
This statistic is incremented in the source cell only and is not target cell related.
IN_INTRA_BSS_NC_SUC
This statistic is incremented in the target cell in respect of a specified source.
OUT_HO_NC_SUC
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in the
source cell relative to a specified neighbour. In the internal case this statistic is incremented at the
same time as those above. It is pegged each time a successful handover message is received from
the target RRSM resulting in a handover performed message being sent to the MSC.
This tracks the number of handovers in a BSS on a per cause basis. It is a counter array with
the same bins defined as OUT_HO_NC_CAUSE_ATMPT, but pegs when the handover performed
message is sent to the MSC to indicate that a successful handover has occurred.
Note From GSR7 a FR to HR congestion based intracell handover will cause the
CONGESTION bin to be pegged. HR quality based intracell handovers will cause the
DOWNINTERF or UPINTERF bin to be pegged.

Successful Intra-BSS Handover Sequence Version 1 Rev 4

RSS (S) RRSM (S) SSM Source cell (when
ho_rec ho_rec received OUT_INTRA_BSS_HO_REQ SSM decides
intra BSS is best)
CRM (T)
RRSM (T) IN - (pegged for target )
ho_channel OUT - (pegged for source)
RSS(T) assigned NC - per neighbour
Channel act
Channel act ack
MS power control Handover allocation
IN_INTRA_BS S_NC_ATMPT
RSS (S) RRSM (S) SSM
MS ho_cmd
Initiate handover
<FACCH> OUT_HO_CAUSE_ATMPT PT
ho_access <FACCH>
ho_access RRSM(T)
ho_access
ho_access ho_detection SM
ho_detect received
Phys info Trans req
SABM
UA
ho_cmplt MTP
ho_cmplt ho_succ ho_performed
IN_INTRA_BSS_HO_SUC
OUT_INTRA_BSS_HO_SUC
IN_INTRA_BSS_NC_SUC
OUT_HO_NC_SUC

Version 1 Rev 4 Successful Intra-BSS Handover Sequence

This container statistic is incremented in the source SSM for successful Internal (and external)
handovers that were executed as a result of Standard Directed Retry. This is used for a pre-GSR5 BSS.
This statistic tracks the number of times a call assignment is Successfully redirected
to another cell during Sdcch to Tch assignments.

0 DIRECTED_RETRY Handovers that were executed as the result of
standard directed retry
1 DURING_ASSIGNMENTS Tracks the handovers that occured during
the Sdcch Tch assignment for normal Radio
reasons.
2 MULTIBAND_BAND Tracks the handovers that were executed
as a result of Sdcch to Tch assignment as
part of the multiband reassign procedure.
This is dependant on the data base setting
band_preference_mode.

Successful Intra-BSS Handover Sequence Version 1 Rev 4

Initiate handover
ho_access
ho_access
ho_access
ho_detection SM
ho_detect received
Phys info Trans req
SABM
UA
ho_cmplt
ho_cmplt MTP
ho_succ
ho_performed
OUT_HO_NC_SUC

Version 1 Rev 4 Intra-BSS Handover Scenarios
Intra-BSS Handover Scenarios

Stats
OUT_INTRA_BSS_HO_PRI_BLK.
Upon receipt of the handover recognized received message from the source RRSM the SSM will
determine the handover type, if an intra-BSS handover is necessary then resources are requested
from the CRM of the primary target. The primary target is the neighbour cell in the first position of
the handover recognized message, the RSS orders the neighbours best to worst generally based
on RF suitability. Should these resources be unavailable the CRM will return with the handover
resources not available message. Queueing is not allowed in the case of an intra-BSS handover.
Upon receiving this message the SSM will increment this statistic. The SSM will only increment
this statistic in the case of the primary (first) target being blocked. Subsequent targets (if available
in the handover recognized message) may be tried and also blocked, these further attempts will
not peg this statistic. Its value is held in a bin of OUT_INTRA_BSS_HO
The target CRM increments bins 0, 1 or 2 of the counter HO_FAIL_NO_RESOURCES whenever
it cannot allocate resources because all channels are in use. Bins 3 to 5 are incremented
whenever a handover fails due to a lack of terrestrial backing (i.e. Dynet) resources. It tracks
internal, external and intra-cell handovers in the bins shown below:
Bin Scenario Description

0 INTRA_BSS Intra BSS HOs that fail due to lack of resources
1 INTER_BSS Same for Inter BSS HOs
2 INTRA_CELL Same for Intra Cell HOs
3 INTRA_BSS_DYNET BTS Dynamic Allocation Intra BSS HOs that
fail due to lack of resources
4 INTER_BSS_DYNET Same for BTS Dynamic Allocation Inter BSS
HOs
5 INTRA_CELL_DYNET Same for BTS Dynamic Allocation Intra Cell
HOs

Intra-BSS Handover Scenarios Version 1 Rev 4

Handover Blocked
Source RRSM SSM

Handover recognized received
Target CRM
Handover resources not available

Increments:
OUT_INTRA_BSS_HO_PRI_BLK


At the moment the SSM transmits the initiate handover message to the source RRSM it
starts an internal timer running, the timer is called T3103 in GSM and Motorola’s designation
is rr_t3103. In the successful case the SSM will receive a handover successful message
from the target RRSM before the expiry of the timer.
Upon receipt of the handover command the MS will alter its characteristics and attempt to
gain L1 establishment with the target RSS. In the asynchronous case the MS will start an
internal timer, T3124, and send a continuous flow of handover access bursts until a physical
information message is returned. If T3124 should expire and no physical information has been
received or if a lower layer failure happens before the handover complete message is sent
then the MS will deactivate the new channel and return to the old TCH.
OUT_INTRA_BSS_HO_RETURN
Upon returning to the old TCH the MS will send a handover failure message, this message
has a number of cause values as specified in GSM TS 04.08. The source RRSM will
translate this message to an unsuccessful handover message and send it to the SSM. Upon
receipt of this message the SSM will stop timer rr_t3103 and increment this statistic for the
source cell. Its value is held in a bin of OUT_INTRA_BSS_HO.
OUT_INTRA_BSS_EQUIP_FAIL
If the handover failure message contains the cause "equipment failure" or the SM reports a
KSW/highway problem in the switch response message, then the handover can be said to have failed
due to equipment failure. This statistic is incremented in a bin of OUT_INTRA_BSS_HO.
IN_INTRA_BSS_HO_RETURN
This statistic is pegged as for OUT_INTRA_BSS_HO_RETURN but is updated with
respect to the target cell. It is a bin of IN_INTRA_BSS_HO.
IN_INTRA_BSS_EQUIP_FAIL
This statistic is pegged as for OUT_INTRA_BSS_EQUIP_FAIL but is updated with respect
to the target cell. It is a bin of IN_INTRA_BSS_HO.


Handover Failure
Source
MS RRSM SSM
Initiate handover rr_t3103
Handover command
Expiry
rr_t3103
Handover failure Expiry
Unsuccessful handover
INTERBAND_ACTIVITY
OUT_INTRA_BSS_HO_RETURN
OUT_INTRA_BSS_EQUIP_FAIL
IN_INTRA_BSS_HO_RETURN
IN_INTRA_BSS_EQUIP_FAIL


There are a number of reasons why a mobile is pegged as "lost" by the BSS for intra BSS
handovers, the examples below give three reasons why this would happen, but this is not
exhaustive and there can be many more reasons why the mobile could be lost.
Mobile Lost
Reason 1
Intra bss handover - MS transmits L2 establishment SABM N200+1 times to target cell, BTS
sends a L2 UA acknowledgement for each SABM, MS fails to receive UA. Subsequently
MS transmits L2 establishment SABM N200+1 times to source cell, BTS sends a L2 UA
acknowledgement for each SABM, MS fails to receive UA.
Reason 2
Intra cell handover - BTS transmits ASSIGNMENT COMMAND N200+1 times, MS
fails to receive ASSIGNMENT COMMAND
Reason 3
Intra BSS handover - BTS transmits HANDOVER COMMAND N200+1 times,
MS fails to receive HANDOVER COMMAND
For all these reasons the BSS pegs:
OUT_INTRA_BSS_HO_LOSTMS
This bin of OUT_INTRA_BSS_HO pegs if the the MS fails to return to original channel during a handover
attempt if the new source cell channel could not be seized. This is controlled by the timer bssmap_t8.
IN_INTRA_BSS_HO_LOSTMS
This bin of IN_INTRA_BSS_HO pegs if the MS fails to handover to the new channel during a handover
attempt if the MS could not return to the original channel. This is controlled by the timer ho_complete.
The clear request to the MSC is under control of the timer rr_t3103 that is started when the initiate
assignment message is sent to the source RRSM. If the SSM has not received a handover successful
message from the target RRSM to inform that the MS has arrived on the new channel or an
unsuccessful handover message from the source RRSM, rr_t3103 expires and the SSM sends a
CLEAR REQUEST message to the MSC that contains the cause value RF message failure.
Call Cleared
Number of outgoing/incoming inter-BSS handovers aborted due to call clearing. This
scenario corresponds to the receipt of a Clear Command, SCCP Released, or Release
Done (internal message) during the handover procedure.
OUT_INTRA_BSS_HO_CLEARED
This bin of OUT_INTRA_BSS_HO pegs if a call is cleared down during an intra BSS handover.
IN_INTRA_BSS_HO_CLEARED
This bin of IN_INTRA_BSS_HO pegs if a call is cleared down during an intra BSS handover.


Mobile Lost
Target Target ho_complete

RSS RRSM SSM
Channel act
acknowledge Expiry
Handover allocation
Source rr_t3103
MS RRSM Initiate handover
Handover command bssmap_t8
Expiry
Expiry
Target
ho_complete
RRSM
Expired
Radio channel released IN_INTRA_BSS_HO_LOSTMS
bssmap_t8 Source
RRSM Radio channel released rr_t3103
Expired
Expired
Clear request
OUT_INTRA_BS S_HO_LOSTMS
CLR_REQ_TO_MSC

Version 1 Rev 4 Outgoing Intra-BSS Handover Tracking
Outgoing Intra-BSS Handover Tracking

Several statistics that apply to outgoing intra BSS handovers are "rolled up" into a single counter
array statistic, OUT_INTRA_BSS_HO. Each is held in a bin of the array as shown below and can
only be displayed as part of the array, not individually. All are pegged at the SSM.
BIN
0 = OUT_INTRA_BSS_HO_REQ
1 = OUT_INTRA_BSS_HO_PRI_BLK
2 = OUT_INTRA_BSS_HO_ATMPT
3 = OUT_INTRA_BSS_HO_SUC
4 = OUT_INTRA_BSS_HO_LOSTMS
5 = OUT_INTRA_BSS_HO_RETURN
6 = OUT_INTRA_BSS_EQUIP_FAIL
7 = OUT_INTRA_BSS_HO_CLEARED

Outgoing Intra-BSS Handover Tracking Version 1 Rev 4
Outgoing Intra-BSS Handover Tracking

OUT_INTRA_BSS_HO
BIN
0 = OUT_INTRA_BSS_HO_REQ
1 = OUT_INTRA_BSS_HO_PRI_BLK
2 = OUT_INTRA_BSS_HO_ATMPT
3 = OUT_INTRA_BSS_HO_SUC
4 = OUT_INTRA_BSS_HO_LOSTMS
5 = OUT_INTRA_BSS_HO_RETURN
6 = OUT_INTRA_BSS_EQUIP_FAIL
7 = OUT_INTRA_BSS_HO_CLEARED

Version 1 Rev 4 Incoming Intra-BSS Handover Tracking
Incoming Intra-BSS Handover Tracking

Several statistics associated with incoming internal handovers are "rolled up" into a single counter
array, IN_INTRA_BSS_HO. Each is held in a bin of the array as shown below, and can only
be displayed as part of the array, not individually. All are pegged at the SSM.
BIN
0 = IN_INTRA_BSS_HO_SUC
1 = IN_INTRA_BSS_HO_LOSTMS
2 = IN_INTRA_BSS_EQUIP_FAIL
3 = IN_INTRA_BSS_HO_RETURN
4 = IN_INTRA_BSS_HO_CLEARED

Incoming Intra-BSS Handover Tracking Version 1 Rev 4
Incoming Intra-BSS Handover Tracking

IN_INTRA_BSS_HO
BIN
0 = IN_INTRA_BSS_HO_SUC
1 = IN_INTRA_BSS_HO_LOSTMS
2 = IN_INTRA_BSS_EQUIP_FAIL
3 = IN_INTRA_BSS_HO_RETURN
4 = IN INTRA_BSS_HO_CLEARED

Version 1 Rev 4 Bad Handover Reference Number
Bad Handover Reference Number

In both the intra-BSS and inter-BSS handover a reference number is used by MS and BSS for the
correct operation of handover detection. Taking the intra-BSS case as an example of this, when the
SSM requests resources from the target cell, the CRM will randomly generate an 8-bit handover
reference number. The number will be passed in Layer 3 information to the SSM and in turn passed
to the MS in the handover command. The MS will transmit this number to the target cell within the
handover access burst. The target channel coder, which knows the correct handover reference number
to be used will check handover bursts arriving in the specified time slot to ensure the numbers match.
Only when the handover access burst is correctly decoded will the handover reference number be
checked by the Channel Coder (CC). When a handover access burst is decoded and the reference
number is correct the whole message is passed to the RSS with a count of the "Bad" handover
reference numbers received by the CC. This statistic is incremented by that number.

Bad Handover Reference Number Version 1 Rev 4
Bad Handover Reference Number
Target
CRM SSM
Target
RRSM
ho channel
assigned
CHANNEL ACT
Source Handover allocation

Source RRSM
MS RSS Initiate handover
ho_cmd
ho_cmd
CC
Handover
TARGET Target
access burst RSS RRSM
L1
Handover
access BAD_HO_REFNUM_MS
Physical ho_detection
information ho_detect received

Version 1 Rev 4 Inter-BSS Statistics
Inter-BSS Statistics
An example of a successful inter-BSS handover sequence is shown opposite.
Stats
OUT_INTER_BSS_REQ_TO_MSC
This counter statistic is pegged each time the SSM sends a handover required message to the MSC,
in a bin of OUT_INTER_BSS_HO. This would generally indicate that the SSM had decided that
an external handover was necessary, however the SSM may refer the control of all handovers
including internal to the MSC, this decision will be dependent upon the value of the SSM database
element, inter_cell_handover_allowed. The SSM will generally decide on an external handover
if the first neighbour specified in the handover recognize message is external.
Depending upon the complexity of the switch handover algorithm the MSC will initiate the handover
request procedure to the first neighbour specified in the handover required message. This
procedure involves the establishment of an SCCP connection and piggy-backed on this CR will
be the handover request message. This message specifies such details as the type of resource
required, encryption information, classmark information, downlink Discontinuous Transmission
(DTX) instructions and also an indication of the MSC-BSC trunk to be utilized.
The sequence of events that follow include the air-interface activation of the new TCH along
with the necessary cross-connect being established by the SM.
HO_REQ_FROM_MSC
This statistic has been introduced in GSR7 specifically to support AMR. It counts the number of Handover
Requests for each channel type and speech version.The bins for this statistic are defined as follows:
Bin 0 - PM_FR
Bin 1 - PM_EFR
Bin 2 - PM_AMR_FR
Bin 3 - PM_AMR _HR
Bin 4 - PM_GSM_HR
Bin 6 - PM_Other
HO_REQ_ACK_TO_MSC
The SCCP CC is then returned to the MSC containing the handover request acknowledge message. This
message will contain specific channel characteristics which will, for the most part, be passed to the MS
concerned. When this message is sent to the MSC the target SSM will increment this counter statistic.
Bin 0 - PM_FR
Bin 1 - PM_EFR
Bin 2 - PM_AMR _FR
Bin 3 - PM_AMR_ HR
Bin 4 - PM_GSM_HR
Bin 5 - PM_SIGNALLING
Bin 6 - PM_DATA
Bin 7 - PM_Other

Inter-BSS Statistics Version 1 Rev 4
Successful Inter-BSS Handover Sequence
SOURCE TARGET
MS RSS RRSM SSM MSC SSM CRM RRSM RSS
ho_rec ho_rec received
ho required <CR> Handover
Handover
request ho channel
request Channel act
assigned
OUT_INTER_BSS_REQ_TO_MSC
Channel act
Handover allocation acknowledge
SM
Conn req
Switch
resp
<CC>
Handover req HO_REQ_MSC_OK
acknowledge
Handover cmd
Initiate ho
Handover cmd OUT_INTER_BSS_HO_ATMPT
OUT_HO_CAUSE_ATMPT RSS MS
RRSM
ho access
FACCH
ho_detect
ho_detect received Phys info
ho_detect SABM
Establish ind
ho_successful ho_cmplt
ho_cmplt
Clear command IN_INTER_BSS_HO_SUC
OUT_INTER_BSS_HO_SUC

OUT_INTER_BSS_HO_ATMPT
Upon receipt of the handover request acknowledge message the MSC will initiate the
handover by formatting and sending the handover command to the source SSM. When the
source SSM receives this message and subsequently forwards it to the MS this statistic is
incremented and stored in a bin of OUT_INTER_BSS_HO_ATMPT.
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged
in the source relative to a neighbour and a specified cause value. In the external case this
statistic is incremented at the same time as the one above, when the SSM receives the
handover command from the MSC and subsequently forwards it to the MS. This statistic
utilizes a counter array containing the following bin definitions:

0 UPQUAL Handovers due to uplink quality.
1 UPLEVEL Handovers due to uplink level.
2 DOWNQUAL Handovers due to downlink quality.
3 DOWNLEVEL Handovers due to downlink level.
4 DISTANCE Handovers due to distance.
5 UPINTERF Handovers eu to uplink interference
6 DOWNINTERF Handovers due to downlink interference.
7 POWERBDGT Handovers due to power budget.
8 CONGESTION Handovers due to congestion.
9 ADJ_CHAN_INTF Handovers due to adjacent channel interference.
10 BAND_RE_ASSIGN Handovers due to band reassignment.
11 BAND_HANDOVER Handovers between bands.
The cause value for congestion includes standard directed retry and both congestion relief mechanisms.
OUT_HO_CAUSE_ATMPT
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is very
similar to the statistic above and indeed is incremented at the same time. The difference
is that this statistic is not incremented on a neighbour basis and merely shows the total
number of attempted handovers out of the source cell with a breakdown per cause value.
The counter array values are the same as those shown above.

SOURCE TARGET
MS RRSM SSM MSC SSM RRSM RSS
Handover cmd
OUT_INTER_BSS_HO_ATMPT
Initiate ho
OUT_HO_CAUSE_ATMPT
Handover cmd
RSS MS
ho_access
FACCH
ho_detect
ho_detect received Phys info
SABM
ho_detect Establish ind
ho_cmplt
ho_successful
ho_cmplt
IN_INTER_BSS_HO_SUC
Clear command

Once the MS receives the handover command it will change its characteristics and try to gain,
initially L1, and then L2 establishment on the new TCH wth the target RSS. The BSS will inform
the MSC when the MS has been detected at L1, this will give the MSC advance warning of the
handover complete and will allow time for the MSC to switch terrestrial connections. After L2
establishment on the air interface the MS will send the L3 handover complete message, the
RRSM will forward this to the SSM as the handover successful message.
IN_INTER_BSS_HO_SUC
The SSM will inform the MSC of a successful handover by sending the handover complete, each
time this message is sent this statistic is incremented. For this statistic to be incremented the
source cell must be external. The value is held in a bin of IN_INTER_BSS_HO.
To complete the handover procedure the source TCH must be deactivated, this is initiated by the
MSC by sending a clear command to the source SSM. Each time this message is received by the
SSM with a cause value indicating a successful handover to an external neighbour this counter
statistic is incremented. The value is held in a bin of OUT_INTER_BSS_HO.
OUT_HO_NC_SUC
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is
pegged in the source cell relative to a specified neighbour. In the external case this
statistic is incremented at the same time as the one above, when the clear command is
received from the MSC with the cause successful handover.

RRSM RSS MS
T
ho_access
SSM FACCH
MSC
ho_detect
ho_detect received
Phys info
SABM
S ho_detect
Establish ind
SSM
ho_cmplt
ho_successful
ho_cmplt
IN_INTER_BSS_HO_SUC
Clear command
OUT_HO_NC_SUC

Version 1 Rev 4 Inter-BSS Failure Scenarios
Inter-BSS Failure Scenarios

Stats
HO_REQ_MSC_FAIL
This counter statistic can be incremented in the source or the target SSM, depending upon
where the failure occurs. It is incremented when the SSM sends the MSC the handover
failure message. This message has many different cause values and hence a number of
associated handover failure scenarios, the only cause value that does not increment this
statistic specifies no radio resources available in the target.
In the source cell this statistic is primarily incremented when the SSM receives an indication as to
handover failure originating from the MS, this indicates that the MS has reverted to the old channel.
A handover failure message originating from the target SSM will do so at the handover resource
allocation stage and could indicate one of a number of problems examples include terrestrial circuit
unavailable, terrestrial circuit in use and cyphering algorithm not supported.
ALARM 18.CELL: HO Failure to the MSC due to all possible errors except no channels - PM (warning)
HO_REQ_MSC_PROTO
This statistic is pegged every time a Handover Request message from the MSC fails message
validation at the BSS. Validation failure may occur due to protocol errors where the message is
badly formatted or incompatible database elements exist at the BSC and MSC.
Alarm- - - - 17. BSS: HO request from the MSC protocol error — PM alarm is generated – (warning).

Inter-BSS Failure Scenarios Version 1 Rev 4

Handover Failure
MSC TARGET SSM
<CR> Handover request

HO_REQ_MSC_PROTO
<CREF> Handover failure
HO_REQ_MSC_FAIL

Version 1 Rev 4 Inter-BSS Failure Scenarios
OUT_INTER_BSS_HO_RETURN
This counter statistic is incremented in the source SSM each time an unsuccessful handover
message is received from the RRSM when the target cell is external.
OUT_INTER_BSS_EQUIP_FAIL
This is incremented in a bin of OUT_INTER_BSS_HO if the MS returns a cause of
"equipment failure" in the handover failure message.
OUT_INTER_BSS_HO_CLEARED
This is pegged in a bin of OUT_INTER_BSS_HO when a call is cleared down
during an inter-BSS handover.
IN_INTER_BSS_EQUIP_FAIL
This is pegged at the target SSM when a handover failure message is received from
the MSC. It is a bin of IN_INTER_BSS_HO.
OUT_INTER_BSS_HO_LOSTMS
This is pegged in a bin of OUT_INTER_BSS_HO if a clear command is not received from the MSC
(indicating that the handover was successful) and no handover failure message is received either.
IN_INTER_BSS_MS_NO_SEIZE
This statistic is pegged at the target SSM whenever a MS fails to seize the new channel
for any reason. It is a bin of IN_INTER_BSS_HO.
IN_INTER_BSS_HO_CLEARED
This bin of IN_INTER_BSS_HO is pegged when a call is cleared down whilst
an inter-BSS handover is in progress.

Inter-BSS Failure Scenarios Version 1 Rev 4

Handover Failure
MS RRSM Source SSM
Handover command
Initiate handover
Handover command
Handover failure
Unsuccessful handover
Handover failure
OUT_INTER_BSS_HO_RETURN
HO_REQ_MSC_FAIL
OUT_INTER_BSS_EQUIP_FAIL

Version 1 Rev 4 Outgoing External Handover Tracking
Outgoing External Handover Tracking

Several statistics associated with outgoing external handovers are "rolled up" into a single counter
array statistic, OUT_INTER_BSS_HO. Each is held in a bin of the array as shown below, and can
only be displayed as part of the array, not individually. All are pegged at the source SSM.
BIN
0 = OUT_INTER_BSS_REQ_TO_MSC
1 = OUT_INTER_BSS_HO_ATMPT
2 = OUT_INTER_BSS_HO_SUC
3 = OUT_INTER_BSS_HO_LOSTMS
4 = OUT_INTER_BSS_HO_RETURN
5 = OUT_INTER_BSS_EQUIP_FAIL
6 = OUT_INTER_BSS_HO_CLEARED

Outgoing External Handover Tracking Version 1 Rev 4
Outgoing External Handover Tracking

OUT_INTER_BSS_HO
BIN
0 = OUT_INTER_BSS_REQ_TO_MSC
1 = OUT_INTER_BSS_HO_ATMPT
2 = OUT_INTER_BSS_HO_SUC
3 = OUT_INTER_BSS_HO_LOSTMS
4 = OUT_INTER_BSS_HO_RETURN
5 = OUT_INTER_BSS_EQUIP_FAIL
6 = OUT INTER_BSS_HO_CLEARED

Version 1 Rev 4 Incoming External Handover Tracking
Incoming External Handover Tracking

Several statistics associated with incoming external handovers are "rolled up" into a single counter
array, IN_INTER_BSS_HO. Each is held in a bin of the array as shown below, and can only be
displayed as part of the array, not individually. All are pegged at the target SSM.
BIN
0 = IN_INTER_BSS_HO_SUC
1 = IN_INTER_BSS_MS_NO_SEIZE
2 = IN_INTER_BSS_EQUIP_FAIL
3 = IN_INTER_BSS_HO_CLEARED

Incoming External Handover Tracking Version 1 Rev 4
Incoming External Handover Tracking

IN_INTER_BSS_HO
BIN
0 = IN_INTER_BSS_HO_SUC
1 = IN_INTER_BSS_MS_NO_SEIZE
2 = IN_INTER_BSS_EQUIP_FAIL
3 = IN_INTER_BSS_HO_CLEARED

Version 1 Rev 4 Incoming External Handover Tracking

Interface Statistics Version 1 Rev 4
Chapter 6
Interface Statistics

Version 1 Rev 4 Interface Statistics

Interface Statistics Version 1 Rev 4
Interface Statistics
Objectives
X.25 and Link Access Procedure "D" (LAPD) objectives
• Name the variants of High level Data Link Controller (HDLC) which are used by GSM.
• Draw the framing structure for HDLC and identify in which fields the following parameters are sent:
Service Access Point Indicator (SAPI)
Frame type
• Name the three frame types used by HDLC. Which type of frame is used to
transmit the following messages:
Frame Reject (FRMR)?
Set Asynchronous Balanced Mode (SABM)
• Name the modes used by HDLC. Which mode is the default mode? Draw signalling
diagrams to illustrate how the other mode is initiated and terminated.
• Identify illustrated X.25 and LAPD statistics using the statistical table provided.
MTP objectives
• State the functions of the three MTP levels.

• Draw a diagram of an MTP Signalling Unit (SU).
• Name the three SU types.
• Name the two parameters which make up the data field of a SU.
• Name the three MTP statistical groups and describe the network conditions they relate to.
• Identify illustrated MTP statistics using the statistical tables provided.
SCCP objectives
• Identify which field of the MTP SU is used to transmit SCCP messages.

• Name the two operating modes for SCCP and state their associated protocol class number.
• Identify illustrated SCCP statistics using the statistical tables provided.
Miscellaneous objectives
• Name the processor utilization statistic.

Version 1 Rev 4 Statistics
Statistics
These statistics relate to activities on the network interfaces for example, messages
travelling over the interfaces are counted and signalling link outages are recorded.
There are two groups of interface statistics: :
a. Operations and Maintenance Link (OML), Radio Signalling Link (RSL), and
Transcoder to BSS Link (XBL) interface statistics
b. MTL interface statistics. These are detailed below
OML, RSL and XBL interface statistics

X.25 messages are recorded travelling between the BSS and the OMC (OML). LAPD messages
are recorded travelling between the BSS and RXCDR (XBL) and between the BSC and BTS
(RSL). These statistics are referred to as X.25 and LAPD statistics.
MTL interface statistics

The MTL is the interface between the BSS and the network switching system. Since
there are a large number of statistics pertaining to the MTL these statistics will be broken
down into several categories as specified in CCITT Q.791.
SCCP performance and utilization.

SCCP makes up the transport layer of CCITT #7 and manages the establishment
and release of call related connections.
MTP C7 performance.
MTP makes up the link and network layers of CCITT #7. These statistics count the different
types of failure and recovery situations on the BSC to MSC interface.
MTP C7 availability.
These statistics count the durations for which the signalling links between the BSC and the MSC are OOS.
MTP C7 utilization.
These statistics count the messages received, transmitted and retransmitted
on the BSC to MSC interface.

Statistics Version 1 Rev 4
Statistics
Interface
OSI Layers SS#7

SS#7 X.25 Others
Levels
Application 7
BSSAP
Presentation 6 X.25
4 (DTAP+BSSMAP)
Session 5 Applications A-bis
Transport 4
SCCP
Network 3
3 MTP Level3 X.25
Link 2 2 MTP Level2 LAPB LAPD
Physical 1 MTP Level1
1 2Mb/s Trunk
ACRONYMS
BSSAP Base Station System Application Part
BSSMAP Base Station System Management Application Part
DTAP Direct Transfer Application Part
MTP Messages Transfer Application Part
LAPB-D Link Access Procedure B-D
SCCP Signalling Connection Control Part
Transmission of X.25 & C7 on 2 Mb/s Trunk
Alignment
information X.25 Packet C7 Signalling Unit
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
2 Mb/s Trunk frame structure

Statistics
The X.25 and LAPD protocols
Before we start to look at the interface statistics it is essential that the student is familiar with the
protocols used on the respective interfaces. The first protocol we will look at is the HDLC protocol.
HDLC is a Layer 2 protocol and variations of it are used by both X.25 and A-bis. X.25 uses LAPB for
Layer 2 messaging, while A-bis uses LAPD. Both LAPB and LAPD protocols are variants of HDLC.
HDLC frame structure

The framing structure for HDLC is illustrated on the page opposite. The component
parts of the frame are described below:
Flags
The flags are used to denote the start and end of each frame. The end flag can also act as
the start of the next frame. The flag pattern used is 01111110. If this pattern occurs within
the frame ‘‘bit stuffing" is used to prevent the data being confused with a flag. Bit stuffing
involves a ‘‘0" being inserted after any five consecutive ‘‘1"s.
Address
Identifies the intended receiver when a command frame is sent and indicates the
transmitter when a response frame is sent.
The SAPI is part of the address field and indicates which Layer 3 entity has
generated or is to receive the frame.
SAPI 0 - RSL
SAPI 62 - OML
SAPI 63 - L2ML
The address field also contains the Terminal endpoint identifier (Tei) which identifies
a logical user on the HDLC link.
Control
Indicates which type of frame it is, there are three frame types. These will be
described in more detail on the following page.
Information frames
Supervisory frame
Unnumbered frames
Information
Layer 3 data is transmitted in this field.
Frame check sequence

Provides error checking for the frame, all bits between the flags are checked. If
errors are found the frame will be retransmitted.

Statistics
HDLC Frame Structure
first bit last bit

Frame
Flag Address Control Info check Flag
sequence
LAPD Addressing
Logical Channels
BTS
BSC
DRCU
RSL (SAPI 0)
OML (SAPI 62) Tei
BSP L2ML (SAPI 63)
003
Tei= 0
DRCU
RSL (SAPI 0)
OML (SAPI 62)
L2ML (SAPI 63)
Tei
002
BTP
OML (SAPI 62)
L2ML (SAPI 63) Tei
001
LAPB Addressing
Command - 01 hex
Primary Response - 01 hex Secondary
Command - 03 hex
Secondary Response - 03 hex Primary

Statistics
The X.25 and LAPD protocols continued
HDLC operating modes
The HDLC protocol can operate in two distinct modes: acknowledged mode and non-acknowledged
mode. By default the protocol will operate in non-acknowledged mode, to initiate or terminate
acknowledged mode the messages illustrated on the page opposite must be sent.
Acknowledged mode
When operating in this mode every message sent must receive an acknowledgement
(e.g. assignment and assignment complete).
Non-acknowledged mode
When operating in this mode messages may be sent and no acknowledgement is required
(e.g. measurement reports sent from the MS to the BSS).
HDLC frame types

There are three frame types used by HDLC these are detailed below:
Information frames
Used to convey Layer 3 information, each unit of data must be acknowledged.
May be referred to as I-frames.
Supervisory frames
Used for flow control purposes, manages the flow of I-frames. They are used to acknowledge
or request retransmission of I-frames. There are three types of S-frames:
Receive Ready (RR)
Receive Not Ready (RNR)
Reject (REJ)
Unnumbered frames
Used for link establishment and release, these frames are used to initiate or terminate acknowledged
mode There are several types of U-frames. Some common ones are listed below:
Set Asynchronous Balanced Mode (SABM)
Disconnect (DISC)
Unnumbered Information (UI)
Unnumbered Acknowledgement (UA)
Frame Reject (FRMR)

Statistics
Layer 2 Alignment
SUCCESSFUL
BTS 2 Mbit/s link BSC

SABME
UA
I-FRAME
I-FRAME
DISCONNECT
BTS BSC
DISC
UA

Statistics
X.25 and LAPD statistics
X.25 and LAPD performance
FRMR
FRMR frames - Counts the number of FRMR frames received and transmitted.
INVALID_FRAMES_RX
Invalid received frames - Counts the number of invalid frames received.
N2_EXPIRY
Expiration of N2 - Counts the number of times the retry count threshold has been exceeded.
X.25 and LAPD utilization
I_FRAMES_RX
Received I-frames - Counts the number of information frames received.
I_FRAMES_TX
Transmitted I-frames - Counts the number of information frames transmitted.
SABM_TX
SABM frames - Counts the number of SABM frames transmitted.
OML
OMC BSC
XBL
RXCDR BSC
RSL
BTS BSC
Note:
The RSL is used to illustrate these statistics but they are also calculated for OML and XBL.

Statistics
X.25 and LAPD
FRMR INVALID_FRAMES_RX
FRMR
BSC BTS
Invalid Frame
I-FRAME
N2_EXPIRY RETRY I-FRAME 1ST TIME
RETRY I-FRAME N2TH TIME

BSC BTS
I_FRAME_RX I_FRAMES_TX
I-FRAME
BSC BTS
I-FRAME
SABM_TX
SABM
BSC BTS

Version 1 Rev 4 MTL Interface Statistics
MTL Interface Statistics

The C7 protocol - MTP
This group of statistics report MTP information. MTP is part of the C7 protocol which is used
throughout the network. MTP provides Layers 2 and 3 of the seven Layer model.
MTP is the transport system for reliable transfer of messages between users.
It is broken down into 3 levels:
MTP1 - Signalling data link functions

Physical, electrical and mechanical specifications for the interface.
MTP2 - Signalling link functions

Defines the the functions and procedures for controlling the transfer of signalling
messages over a signalling link.
MTP3 - Signalling network functions

Defines the methods for message handling and routeing on a signalling link.
Signalling Units (SUs)

MTP uses SUs to transmit information, there are three SU types:
Message Signalling Unit (MSU)
Link Status Signalling Unit (LSSU)
Fill-In Signalling Unit (FISU)
The basic structure of a SU is illustrated on the opposite page. There are three parts to a SU:
1. Header
Carries the information to ensure that the messages are sent in sequence and a length
indicator. The detail of the header is illustrated over the page.
2. Data
There are two parts to the data field; the Signalling Information Field (SIF)
and the Service Information Octet (SIO).
3. Tail
Contains error checking for the SU.

MTL Interface Statistics Version 1 Rev 4

Signalling Protocol Reference Model
A-interface
Other applications Operation and
To other (e.g. call control)
processes Maintenance
within the BSS information to
PLMN O &M
To air
interface
transmission
equipment BSS BSS
DTAP MAP DTAP MAP
BSS BSS
OSI OMAP OMAP
MODEL
Distribution Function Distribution Function
Layer 4-7
To other
Layer 3 SCCP SCCP users of the
SCCP and
Layer 1-3 MTP MTP MTP
Physical Layer
DTAP: Direct Transfer Application Part

BSSMAP: BSS Management Application Part MTP: Message Transfer Part
BSS OMAP: BSS Operation and Maintenance Application Part BSS: Base Station System
SCCP: Signalling Connection Control Part MSC: Mobile services Switching Centre
The C7 Protocols - MTP
SIGNALLING UNIT (SU)
first bit last bit
HEADER DATA TAIL
MSU
LSSU
FISU


The C7 Protocol - MTP continued
The MTP SU is described below. There are three parts to a SU. These are described in detail below.
Header
The header sequence is the same for all types of SUs and consists of the following:
Flag (F)
All SUs begin and end with an 8 bit flag. The flag bit pattern is 01111110. To ensure a flag pattern is
not contained in the data, a "0" is inserted after any five consecutive "1s" at the transmitter. At the
receiver, the "0" is removed. These processes are called "bit stuffing and "bit stripping".
Backward Sequence Number (BSN)

The BSN is the sequence number of an MSU being acknowledged.
Backward Indicator Bit (BIB)

Used with the the BSN to perform SU sequencing control and acknowledgement.
Forward Sequence Number (FSN)

The FSN is the sequence number of the SU in which it is being carried. The FSN and BSN are binary
coded using modulo 128. The FSN and BSN in a particular SU bear no relationship to each other.
Forward Indicator Bit (FIB)

Used with the FSN to perform SU sequencing and acknowledgement.
Length Indicator (LI)

Indicates the length of the message in octets.
Data
Signalling Information Field (SIF)
Provides routeing information and carries user traffic. Contains the Origination Point
Code (OPC) and Destination Point Code (DPC).
Service Information Octet (SIO)

Identifies source and destination users and indicates whether traffic is national or international.
Tail
Check Bits (CK)
Error checking bits. Retransmission is requested if the frame is in error.


The C7 Protocols
first bit last bit
Header Data Tail
B F
FLAG BSN I FSN I LI
B B
8 7 1 7 1 6 2
SIO SIF
2 8
CK FLAG
16 8


MTP C7 performance
MTP_SL_FAIL and LMTP_SL_FAIL
Signalling Link (SL) failure-All reasons - Counts the number of CEPT (see Glossary) SL
failures for any reason including those detailed below.
ALARM 0. MTL: SL Failure all reasons - PM (major)

0. LMTL: SL Failure all reasons - PM (major)
MTP_SL_FIBR and LMTP_SL_FIBR

SL failure-Abnormal Forward Indicator Bit Received (FIBR) or Backward Sequence Number Received
(BSNR) - Counts the number of times the signalling fails due to the detection of an abnormal
FIB caused by the mis-synchronization of the sequence numbers BSN and FSN.
ALARM 1. MTL: SL Failure abnormal FIBR/BSNR - PM (major)

1. LMTL: SL Failure abnormal FIBR/BSNR - PM (major)
MTP_SL_ERROR_RATE and LMTP_SL_ERROR_RATE

SL failure-Excessive error rate - Counts the number of times the signalling fails due to
the Signal Unit Error Rate Monitor (SUERM) timer expiration.
ALARM 3. MTL: SL Failure excessive error rate - PM (major)

3. LMTL: SL Failure excessive error rate - PM (major)
MTP_SL_ACK and LMTP_SL_ACK

SL failure-Excessive delay of ACK - Counts the number of times the link fails due to a timer
that expired because an acknowledgement of a MSU was not sent.
ALARM 2. MTL: SL Failure excessive delay of ACK - PM (major)

2. LMTL: SL Failure excessive delay of ACK - PM (major)
MTP_SL_CONGESTION and LMTP_REMOTE_SL_CONGESTION

SL failure-Excessive duration of congestion - Counts the number of times the SL fails
due to the remote congestion timer expiring.
ALARM 4. MTL: SL Failure excessive duration of congestion - PM (major)

4. LMTL: SL Failure excessive duration of congestion - PM (major)
LMTP_LOCAL_SL_CONGESTION
There are two types of congestion that may occur across an Lb interface SL: local congestion (that
is the MTP L2 of the BSS detects that the TX queue is full) and remote congestion (that is the
BSS-based SMLC is congested). Both types of congestion may exist across an Lb-interface SL at
one time; however, regardless of congestion type, the statistic is pegged only upon the entrance


into the congested state of the Lb-interface SL. Thus, if the Lb-interface SL is locally congested
and remote congestion is detected, the statistic is not pegged. Likewise, if the Lb-interface SL
is remotely congested and local congestion is detected, the statistic is not pegged.
ALARM 12. LMTL: SL Congestion indications - PM (major)
MTP C7 Performance
(LMTP)MTP_SL_FIBR
FIB
MSU ERROR
MSC BSC
N good MAX
frames (LMTP)MTP_SL_ERROR RATE
Bad
frame
(LMTP)
MTP_SL_FAIL
MSC BSC
(LMTP)MTP_SL_ACK
ACK
MSC BSC
MSU
(LMTP)MTP_SL_CONGESTION
LMTP_LOCAL_SL_CONGESTION
MSC BSC


MTP C7 performance continued
MTP_SU_ERROR
LMTP_SU_ERROR
Number of SUs in error - Counts the number of times erroneous SUs are received on
the SL that are acceptable in normal system operation.
ALARM 6.
MTL: Number of signal units in error - PM
(warning)
6.
LMTL: Number of signal units in error - PM
(warning)
MTP_NEG_ACKS
LMTP_NEG_ACKS
SL number of negative ACKs received - Counts the number of times the BSS
detects out of order messages from the MSC.
ALARM 7.
MTL: SL Number of negative ACKs received -
PM (warning)
7.
LMTL: SL Number of negative ACKs received -
PM (warning)
MTP_SL_ALIGNMENT
LMTP_SL_ALIGNMENT
SL alignment failure - Counts the number of times the SL tries to align with the A-interface while it is OOS.
ALARM 5.
MTL: SL Alignment failure - PM (minor)
5.
LMTL: SL Alignment failure - PM (minor)
MTP_RESTORATION
LMTP_RESTORATION
SL restoration - Counts the number of times the SL starts carrying user traffic. This happens when
the SL comes into service, is uninhibited, or recovers from a remote processor outage.


MTP C7 Performance
(LMTP)MTP_SU_ERROR
FIB
SU ERROR!
SU
MSC BSC
SU (LMTP)MTP_NEG_ACKS
SU
MSC Neg-Ack BSC

(request transmit)
(LMTP)MTP_SL_ALIGNMENT
MSC BSC
GO! (LMTP)MTP_RESTORATION
MSC BSC


MTP C7 performance continued
MTP_CHANGEOVER
LMTP_CHANGEOVER
Local automatic changeovers - Counts the number of times MTP traffic is routed to an alternate SL.
MTP_CHANGEBACK
LMTP_CHANGEBACK
Local automatic changebacks - Counts the number of times MTP traffic is diverted back
to the original SL after having been routed to an alternate SL.
MTP_LINK_INS
LMTP_LINK_INS
Duration of link in the INS state - Measures the duration that the SL is INS.


MTP C7 Performance
(LMTP)MTP_CHANGEOVER
GO!
GO!
MSC BSC
(LMTP)MTP_CHANGEBACK
GO!
GO!
MSC BSC
(LMTP)MTP_LINK_INS
12 TICK
TICK 9 3
6
GO! TICK
MSC BSC


MTP C7 availability
MTP_UNAVAILABLE
LMTP_UNAVAILABLE
Duration of SL unavailability (for any reason) - Measures the duration for which CEPT SL is unavailable.
MTP_LINKFAIL
LMTP_LINKFAIL
Duration of SL unavailablility due to link failure - Measures the duration that the SL is OOS.
MTP_LOCAL_BUSY
LMTP_LOCAL_BUSY
Duration of local busy - Measures the duration that the SL is congested locally.


MTP C7 Availability
(LMTP)MTP_UNAVAILABLE
12 TICK
TICK 9 3
6
TICK
All cases
MSC BSC
(LMTP)MTP_LINK_FAIL
12 TICK
TICK 9 3
6
TICK
Link failure
MSC BSC
(LMTP)MTP_LOCAL_BUSY
12 TICK
TICK 9 3
6
TICK
MSC BSC


MTP C7 availability continued
MTP_REMOTE_PROC
LMTP_REMOTE_PROC
Duration of SL unavailability due to remote processor outage - Measures the

duration that a remote processor is OOS.
MTP_START_RPO
LMTP_START_RPO
Start of remote processor outage - Counts the number of times a remote processor
outage condition is identified.
MTP_STOP_RPO
LMTP_STOP_RPO
Stop of remote processor outage - Counts the number of times a remote processor outage is cleared.
LMTP_SIB_TX
This statistic is pegged each time the BSS transmits a Status Indication Busy (SIB)
LSSU message across the Lb-interface signalling link.
LMTP_SIB_RX
This statistic is pegged each time the BSS receives a Status Indication Busy (SIB)
LSSU message across the Lb-interface signalling link.


MTP C7 Availability
BANG! (LMTP)MTP_START_RPO
LMTP_SIB_TX
CRASH
CLUNK!
(RPO - Remote Proc Outage)

MSC BSC
LSSU-RPO
(LMTP)MTP_REMOTE_PROC
LSSU-BUSY
12 TICK
TICK 9 3
6
TICK
.....WHIRR..... (LMTP)MTP_STOP_RPO
LMTP_SIB_RX
MSC LSSU
BSC
LSSU-BUSY


MTP C7 availability continued
MTP_LOCAL_MGT
LMTP_LOCAL_MGT
Duration of SL inhibition due to local management actions - Measures the duration that
the SL is inhibited due to local management actions.
MTP_MGT_INHIBIT
LMTP_MGT_INHIBIT
Local management inhibit - Counts the number of times the SL is inhibited by the user
carrying out a lock command to the associated link.
MTP_MGT_UNINHIBIT
LMTP_MGT_UNINHIBIT
Local ,anagement uninhibit - Counts the number of times the SL is uninhibited by the
user carrying out an unlock command to the link.
MTP_REMOTE_MGT
LMTP_REMOTE_MGT
Duration of SL inhibition due to remote management actions - Measures the duration

that the SL is inhibited due to remote management action.


MTP C7 Availability
(LMTP)MTP_MGT_INHIBIT
MSC BSC
(LMTP)MTP_LOCAL_MGT
12 TICK
TICK 9 3
(LMTP)MTP_MGT_UNINHIBIT 6
TICK
MSC BSC
STOP (LMTP)MTP_REMOTE_MGT
12 TICK
TICK 9 3
6
TICK
MSC BSC


MTP C7 utilization
MTP_CONGESTION
LMTP_CONGESTION
Cumulative duration of SL congestion - Measures the duration that the SL is congested.
SL_CONGESTION
SL congestion indications - Tracks the number of times the remote congestion timer
expires due to excessive congestion on the SL.
ALARM 4.
MTL: SL Failure Excessive duration of congestion
- PM (warning)
SL_STOP_CONGESTION
L_SL_STOP_CONGESTION
Stop of SL congestion - Counts the number of times a SL congestion indication stops.
CONGESTION_LOST_MSU
LMTP_CONGESTION_LOST_MSU
Number of SL congestion events resulting in loss of MSUs - Counts the number of times
a congestion event occurs which results in MSUs being lost.
ALARM 11.
MTL: SL Congestion events resulting in lost
MSUs - PM (warning
11.
LMTL: SL Congestion events resulting in lost
MSUs - PM (warning)
MSU_DISCARDED
LMTP_MSU_DISCARDED
Number of MSUs discarded due to SL congestion - Counts the number of MSUs which
are discarded whilst there is congestion on the SL.


MTP C7 Utilization
SL_CONGESTION
MSC BSC (LMTP)MTP_CONGESTION

LSSU-B 12 TICK
TICK
Congestion indication 9 3
(L_)SL_STOP_CONGESTION 6
TICK
MSC BSC
LSSU
(LMTP)CONGESTION_LOST_MSU
MSC BSC
(LMTP)MSU_DISCARDED


MTP C7 utilization continued
MTP_MSU_RX
LMTP_MSU_RX
Number of MSUs received - Counts the number of MSUs received over the SL.
MTP_MSU_TX
LMTP_MSU_TX
Number of MSUs transmitted - Counts the number of MSUs transmitted over the SL.
MTP_RE_TX
LMTP_RE_TX
Number of octets retransmitted - Counts the number of octets that the BSS has retransmitted
to the MSC(SMLC) because the MSC(SMLC) has requested retransmission. This indicates
how much the BSS and an MSC(SMLC) are off in message sequencing.
ALARM 9.
MTL: Number of octets retransmitted - PM
(warning)
9.
LMTL: Number of octets retransmitted - PM
(warning)


MTP C7 Utilization
(LMTP)MTP_MSU_RX
MSU
MSC BSC
(LMTP)MTP_MSU_TX
MSC MSU BSC
(LMTP)MTP_RE_TX
Retransmission request
MSC BSC
Retransmission


MTP C7 utilization continued
MTP_SIF_SIO_RX
LMTP_SIF_SIO_RX
Number of SIF and SIO octets received - Counts the number of SIFs and SIOs received over the SL.
MTP_SIF_SIO_TX
LMTP_SIF_SIO_TX
Number of SIF and SIO octets transmitted - Counts the number of SIFs and SIOs transmitted over the SL.
SIF_SIO_RX_OPC
L_SIF_SIO_RX_OPC
Number of SIF and SIO octets received - Counts the number of SIFs or SIOs
received across all SLs to a BSS.
SIF_SIO_TX_DPC
L_SIF_SIO_TX_DPC
Number of SIF and SIO octets transmitted - Counts the number of SIFs or SIOs
transmitted across all SLs to a BSS.
SIF_SIO_TYPE
L_SIF_SIO_TYPE
Number of SIF and SIO octets handled with given SIO - Counts the number of SIFs or
SIOs transmitted or received on each SL. The signal types available are MTP, Test and
SCCP. This statistic pegs the sum of all SLs to the BSS.


MTP C7 Utilization
(LMTP)MTP_SIF_SIO_RX
SU data
MSC BSC
(LMTP)MTP_SIF_SIO_TX
SU data
MSC BSC
(L_)SIF_SIO_RX_OPC
SU data
MSC BSC (L_)SIF_SIO_TYPE
(L_)SIF_SIO_TX_DPC
SU data
MSC BSC


The C7 protocol - SCCP
The SCCP statistics will now be considered. SCCP builds on MTP to provide full network
service. The framing structure for SCCP is illustrated on the opposite page.
As can be seen SCCP is part of the SIF found in an MTP SU.
SCCP can operate in four modes, two of these modes are used for GSM these are; connectionless
and connection-oriented. Protocol class numbers carried in the mandatory fixed field of the SCCP
message indicate which mode is being used. The two modes used for GSM are described below:
Connectionless
Protocol Class 0 - Single messages are sent to other SCCP users. There is only one
type of message sent in connectionless mode.
UDT - Unit Data
Connection-Oriented
Protocol Class 2 - A signalling connection is established before messages are sent. Several
SCCP message types must be passed to establish this connection.
CR - Connection Request
CC - Connection Confirm
CREF - Connection Refused
DT1 - Data form 1
IT - Inactivity Test
Once the communication is complete the link must be released. The following SCCP
message types are used to release the connection:
RLSD - Released
RLC - Release Complete


C7 Protocol - SCCP
HEADER DATA TAIL

MTP
SIO SIF
ROUTING SCCP
LABEL MESSAGE
SCCP
DPC OPC SLS
Mandatory Mandatory Optional

Message
fixed variable (Data)
type
part part part


SCCP performance and utilization
SCCP performance
ROUTING_SYNTAX
L_ROUTING_SYNTAX
Routing failure syntax error detected - Counts when a syntax error is detected in an SCCP routeing label.
ALARM 1.
BSS: Routing failure syntax error detected - PM
(warning)
18.
BSS Routing failure syntax error detected
(SMLC) - PM (warning)
ROUTING_UNKNOWN
L_ROUTING_UNKNOWN
Routing failure reason unknown - Counts the number of invalid signalling point
codes received from the MSC.
ALARM 2.
BSS: Routing failure - reason unknown - PM
(warning)
19.
BSS: Routing failure - reason unknown - PM
(warning)
SCCP Utilization
SCCP_MSGS_TX
L_SCCP_MSGS_TX
Total messages sent (by classes 0 and 2) - Counts the number of SCCP messages transmitted on the SL.
SCCP_MSGS_RX
L_SCCP_MSGS_RX
Total messages received (by classes 0 and 2) - Counts the number of SCCP
messages received on the SL.
SCCP_MSGS
L_SCCP_MSGS
Total messages handled from local or remote subsystem - Counts the number of SCCP
messages which are transmitted or received on the SL per BSS.


SCCP Performance and Utilization
(L_)ROUTING_SYNTAX
Syntax
SCCP routeing label error
MSC BSC
(L_)ROUTING_UNKNOWN
OPC MSC (SPC) DPC BSS (SPC)
SCCP routing label
MSC BSC
(L_)SCCP_MSGS_RX
SCCP
MSC BSC (L_)SCCP_MSGS
(L_)SCCP_MSGS_TX
SCCP
MSC BSC

Version 1 Rev 4 BSS Location Services (LCS) - System Overview
BSS Location Services (LCS) - System Overview

From GSR6 the BSS is providing support for Location Services. Location Services uses one or
more positioning mechanisms in order to determine the location of the MS. The positioning process
involves two main steps: signal measurements and location estimate computation based on the
measured signals. LCS has been seen by operators, service providers and Motorola as a key
application enabler. This will allow calculation of the position of the MS directly, location specific
advertising and to determine the routing of voice traffic. This can be achieved in three ways:
TA Positioning Mechanism
The Timing Advance positioning mechanism is based on the existing Timing Advance (TA)
parameter. The TA value is known for the serving BTS. The TA value, the cell ID and the
measurement reports are return to the requesting LCS client.
E-OTD
Enhanced Observed Time Difference (E-OTD) Positioning Mechanism uses the MS and a number
of BTS’s to calculate a position for the MS based on time delays (Real Time Differences - RTDs)
to the MS from the BTS and geometry. This depends on whether it is a synchronised network
or unsynchronised network. If synchronised the MS measures the relative time of arrival of the
signal from several BTSs. For unsynchronised the signals are received by a fixed measuring
point known as a Location Measurement Unit (LMU). The calculations can be made in the MS
if all information present (MS-based) or if not MS-assisted. To obtain accurate triangulation
RTDs are required from at least three geographically distinct BTSs.
A-GPS
Global Positioning System (GPS) provides a means to determine position, velocity and time around the
globe. It uses satellites emitting radio signals to the recievers to determine position of the receiver. The
GPS constellation consists of 24 satellites orbiting at an altitude of 20,183.62km above Earths surface.
Based on Time of Arrival (TOA) principle, when four or more satellites are in Line of Sight (LOS) from
the reciever, the latitude, longitude and altitude of the reciever are determined. Standard Positioning
Service (SPS) is a grade of GPS service avaialble for commercial applications including mobile phone
location determination. SPS is delibrately degraded by selective availability (SA), but provides
horizontal position accuracy within a circle of 100m radius 95% of the time. Differential-GPS (D-GPS)
can reduce the error to under 5m, while SA and other factors are in effect. It uses a reference receiver
at a surveyed position to send correcting information to the mobile over the communication link.
For Assisted-GPS (A-GPS), a GPS reference network (or a Wide area D-GPS network) is established.
The GPS reference network manages receivers with clear views of the sky and can operate
continuously. This reference network is connected with the GSM network. At the request of the
GSM network, assistance data from the reference network is transmitted to the MS to increase
performance of the GPS sensor. The Assisted-GPS method should be able to:
• Reduce the sensor start-up time;
• Increase the sensor sensitivity; and
• Consume less handset power than conventional GPS does.
Additional assisted data, such as differential GPS corrections, approximate handset
location or cell base station location, and others can be transmitted to improve the
location accuracy and decrease acquisition time.

BSS Location Services (LCS) - System Overview Version 1 Rev 4
BSS Location Services (LCS) - System Overview
Timing Advance Positioning Mechanism

Enhanced Observed Time Difference Positioning Mechanism
Assisted - Global Position System Positioning Mechanism

Version 1 Rev 4 BSS Location Services (LCS) - Network Architecture
BSS Location Services (LCS) - Network Architecture

Several new network elements are added to the general GSM architecture to support
Location Services. A brief illustration of the new network topology is shown in the diagram
opposite. Note that a number of new interfaces were created for the new network entities.
The central interface impacting the BSS is the Lb interface.
GMLC
The Gateway Mobile Location Center (GMLC) is a new network element being added to the GSM
PLMN in support of Location Services. The GMLC is the first node an external LCS Client accesses in
a GSM PLMN. The GMLC may request routing information from the HLR via the Lh interface. After
performing registration authorization, it sends positioning requests to and receives final location
estimates from the VMSC via the Lg interface. The GMLC is responsible for the following functions:
• Managing external interface to LCS
• Authorizing LCS Clients requesting LCS information
• Collecting charging and billing data related to LCS for both clients and subscribers
• Transforming location estimates into local geographic system understood by the client.
SMLC
The Serving Mobile Location Center (SMLC) is a new network element being added to the
GSM PLMN in support of Location Services. The SMLC manages the overall coordination and
scheduling of resources required for MS positioning. It also calculates the final location estimate
and accuracy. As seen in the diagram opposite, two new signal interfaces, Ls and Lb, have been
defined to transport messages to and from the SMLC. The Ls interface associates the SMLC with the
VMSC. Hence, the VMSC will be needed to route signals to the SMLC via the Ls interface in this
configuration. Similarly, the Lb interface associates the SMLC with the BSC. The BSC will need to
support message routing to the SMLC via the Lb interface in this configuration.
The SMLC is responsible for the following functions:
• Registering and maintaining operational status of LMUs
• Providing broadcast capability for E-OTD and A-GPS
• Managing the positioning of a MS through the coordination and scheduling of re-sources
• Calculating the positioning of the MS
The phrase "BSS based SMLC" refers to an SMLC communicating with the BSS via the Lb
interface. The phrase "NSS based SMLC" refers to an SMLC communicating with the MSC via
the Ls interface. For this feature BSS will be communicating with the MSC only.

BSS Location Services (LCS) - Network Architecture Version 1 Rev 4
Other
Gateway PLMN
MLC
Lg
Lp Ls Lg Le
Gateway External
SMLC SMLC MSC/VLR LCS
MLC Client
Lb A Lh
CBC-SMLC
CBC CBC-BSC BSC HLR
ABIS ABIS
BTS LMU
LMU
Type B Type B
LMU
Type A
mail
Master
Smail
Return
call

Version 1 Rev 4 BSS Location Services (LCS) - Network Architecture

LMU
A Location Measurement Unit (LMU) makes radio measurements to support one or
more positioning methods. These measurements fall into one of two categories:
• Location measurements specific to one MS used to compute the location of this MS
• Assistance measurements specific to all MSs in a certain geographic area
All location and assistance measurements obtained by an LMU are supplied to a particular SMLC
associated with the LMU. Instructions concerning the timing, the nature and any periodicity of these
measurements are either provided by the SMLC or are pre-administered in the LMU.
Type A LMU
A type A LMU is accessed exclusively over the GSM air interface (Um interface): there is no wired
connection to any other network element. A type A LMU has a serving BTS and BSC that provide
signaling access to a controlling SMLC. With an NSS based SMLC, a type A LMU also has a serving
MSC and VLR and a subscription profile in an HLR. A type A LMU always has a unique IMSI and
supportsall radio resource and mobility management functions of the GSM air interface that are
necessary to support signaling using an SDCCH to the SMLC. A type A LMU supports those connection
management functions necessary to support LCS signaling transactions with the SMLC and may support
certain call control functions to support signaling to an SMLC using a circuit switched data connection.
Type B LMU
A Type B LMU is accessed over the Abis interface from a BSC. The LMU may be either a standalone
network element addressed using some pseudo cell ID or connected to or integrated in a BTS.
Signaling to a Type B LMU is by means of messages routed through the controlling BSC for a BSS
based SMLC or messages routed through a controlling BSC and MSC for an NSS based SMLC.
The term "LMU" indicates a Type A LMU. The BSS does not support Type B LMUs.
Also the term "SMLC", when not prefaced by either "NSS based" or "BSS based" shall
be inferred to be indicating a BSS based SMLC.
LMU Procedures
For the most part, LMUs will be handled like regular mobiles, except that all signalling goes to
the SMLC and not the MSC when the SMLC is BSS based. The LMUs are allowed to get an
SDCCH and even perform handovers. However, the LMUs cannot get a TCH.

BSS Location Services (LCS) - Network Architecture Version 1 Rev 4
Other
Gateway PLMN
MLC
Lg
Lp Ls Lg Le
Gateway External
SMLC SMLC MSC/VLR LCS
MLC Client
Lb A Lh
CBC-SMLC
CBC CBC-BSC BSC HLR
ABIS ABIS
BTS LMU
LMU
Type B Type B
LMU
Type A
mail
Master
Smail
Return
call

Version 1 Rev 4 BSS-Based SMLC
BSS-Based SMLC
There are a number of statistics based upon the receipt and transmission of messages regarding
the MSC and the BSS-based SMLC. The BSS now must contend with two terrestrial point codes
(SMLC and MSC), whereas previously the BSS could assume the MSC was the end destination (after
all, it was the only other SPC in the network besides the BSS). The creation of a new interface,
and its supporting protocols, introduces a sizeable amount of added functionality.
Initial Setup
BSSMAP_PERF_LOC_REQ_MSGS
A portion of the functionality necessary for a BSS based SMLC is identical regardless of positioning
method. The initial setup of all resources and notification to the SMLC of a positioning attempt
is done prior to the SMLC deciding what type of positioning method to use. Remember that the
MSC will always know of an LCS attempt before the SMLC or BSS, and will set up a call (at least
to an SDCCH) prior to notifying the SMLC of the location attempt. Thus, from the BSSs point of
view, a call is already established before LCS even begins. Note that a call could already be in
progress (user just happened to be involved in a normal voice/data call at the time), so the MS
could already be on an SDCCH or a TCH. In that case, the MSC can skip the call setup messaging
since it has already been done. So after call establishment, the BSS has an SCCP connection
to the MSC for the MS call, and no connection to the SMLC (yet). Any BSS based SMLC LCS
scenario will start with the MSC sending a BSSMAP Perform Location Request message over
the SCCP connection for the MS to be located. This message is actually for the SMLC, not the
BSS, but the MSC has no direct connection to the SMLC. Thus it must send the message over
the only interface it has to reach the SMLC via the BSS A-Interface. This message is routed by
MTPL3 to SSM, just as any connection oriented message on an SCCP DT1 is.
Therefore everytime a BSSMAP Perform Location Request message is received
by the BSS this statistic is pegged.
BSSMAPLE_PERF_LOC_REQ_MSGS
The SSM will recognize the BSSMAP Perform Location Request message as an LCS message
and will need to set up another SCCP connection, this time to the SMLC. Since the Lb interface uses
standard SS7 up to the application layers, the SSM initiates the SCCP connection just as it does for the
A-Interface. The SSM sends an SCCP CR with an embedded BSSMAP-LE Perform Location Request
inside. Before the SSM incorporates the BSSMAP-LE Perform Location Request message inside the
SCCP CR, it will retrieve the timing advance and the measurement report from the RSS. The SSM will
insert the BSSLAP TA Layer 3 element in the BSSLAP APDU of the BSSMAP-LE Perform Location
Request message to be sent to the SMLC. When the BSS sends the BSSMAP-LE Perform Location
Request message, the BSS shall start the LCS Perform Location Timer. The SMLC will answer
with an SCCP CC, which may or may not have an embedded BSSMAP-LE Connection Oriented
Information (with an embedded BSSLAP command) inside. If the BSSMAP-LE Connection Oriented
Information is not present in the SCCP CC, the message will come afterwards inside an SCCP DT1.
Therefore everytime a BSSMAP-LE Perform Location Request message is
sent to the SMLC this statistic is pegged.

BSS-Based SMLC Version 1 Rev 4
BSS-Based SMLC
SMLC RSS RRSM SSM MSC/VLR
BSSMAP Perform
Location Request
TA request
Abis TA request
Abis TA response
TA response
BSSMAPLE Perform
BSSMAP-LE_PERF_LOC_REQ_MSGS
Location Request

BSS-Based SMLC
LCS Teardown
For successful LCS cases, the LCS positioning procedure can end with the SMLC sending a
BSSMAP-LE Perform Location Response message encapsulated in an SCCP RLSD message or the
SMLC sending a BSSMAP-LE Perform Location Response message only. In the former case, the SSM
process forwards the BSSMAP Perform Location Response message to the MSC and responds to the
SMLC with an SCCP RLC message. For the latter case, once the BSSMAP Perform Location Response
message is forwarded to the MSC, the SSM initiates teardown of the SMLC SCCP connection by
sending an SCCP RLSD to the SMLC. The SMLC will respond with an SCCP RLC message to the
SSM. For either case, the MSC will initiate normal MS teardown once the LCS procedure is finished.
BSSMAPLE_PERF_LOC_RESP_MSGS
This statistic is pegged everytime a BSSMAP-LE message is received by the BSS from the SMLC.
BSSMAP_PERF_LOC_RESP_MSGS
This statistic is pegged everytime a BSSMAP message is forwarded onto the MSC from the BSS.

BSS-Based SMLC
MS SMLC SSM MSC/VLR
BSSMAPLE Perform BSSMAPLE_PERF_LOC_RESP_MSGS
Location Response
BSSMAP Perform
Location Response
BSSMAP_PERF_LOC_RESP_MSGS
SCCP Release MSG
Normal MSC Initiated MS

Teardown

BSS-Based SMLC
Perform Location Abort
If the BSS receives a BSSMAP Perform Location Abort message from the MSC, it will forward this
message in a BSSMAP-LE Perform Location Abort message to the SMLC on the existing Lb
SCCP connection. The SMLC shall respond to the BSS with a BSSMAP-LE Perform Location
Response message when it receives a BSSMAP-LE Perform Location Abort message. The
BSS will then send a BSSMAP Perform Location Response message to the MSC. If no Lb
SCCP connection exists for this A-interface SCCP connection, or no BSS-based SMLC exists,
the BSS will discard the BSSMAP Perform Location Abort message.
BSSMAP_PERF_LOC_ABORT_MSGS
When the BSS receives a BSSMAP Perform Location Abort message from
the MSC, this statistic is pegged.
BSSMAPLE_PERF_LOC_ABORT_MSGS
When the BSS forwards the BSSMAP Perform Location Response message in the from of a
BSSMAP-LE Perform Location Abort message this statistic is pegged.

BSS-Based SMLC
Perform Location Abort
SMLC BSS MSC
BSSMAP Perform
Location Abort
BSSMAP_PERF_LOC_ABORT_MSGS
BSSMAP-LE Location Abort
BSSMAP-LE Location Abort
BSSMAPLE_PERF_LOC_ABORT_MSGS
BSSMAP Perform
Location Abort

Version 1 Rev 4 Time of Arrival Positioning Method
Time of Arrival Positioning Method

Motorola’s end to end solution will not include the TOA (Time of Arrival) positioning method, and
therefore the BSS will not support this procedure. For inter-operability, in case another vendor’s SMLC
is being used, the BSS will notify the MSC that this positioning procedure is not supported through
the use of the BSSLAP Reject message, with a cause value set to "Positioning procedure not
supported." This will be sent in response to the BSSLAP TOA Request message from the MSC.
Stats
BSSLAP_TOA_REQ
Every time the BSS receives a BSSLAP TOA Request message from the MSC this statistic is pegged.
BSSLAP_REJ
Everytime the BSS sends a BSSLAP Reject message to the MSC in response to a
BSSLAP TOA message this statistic is pegged.

Time of Arrival Positioning Method Version 1 Rev 4
Time of Arrival Positioning Method

SSM MSC
BSSLAP TOA Request

BSSLAP_TOA_REQ
BSSLAP REJ
BSSLAP_REJ

Version 1 Rev 4 Timing Advance Positioning Method
Timing Advance Positioning Method

The BSS supports the Timing Advance positioning procedure. In the requirements that follow, the
phrase "Timing Advance positioning attempt" shall mean the time in which the BSS is processing a
BSSLAP TA Request message from the SMLC/MSC. The procedure is finished when the BSS
returns a BSSLAP TA Response message to the SMLC/MSC or the procedure is abandoned due
to an error scenario (sending of BSSLAP Reject/Abort or LCS Supervision Timer expiry).
A BSSLAP TA Request can either be sent by a BSS-Based SMLC or a MSC. In the case of
a BSS-Based SMLC. The TA scenario begins when the BSS receives a BSSLAP TA Request
message (encapsulated inside a BSSMAP-LE Connection Oriented Information message) from
the SMLC. This will be received over the SCCP connection that was set up with the SMLC for
this positioning attempt. Three pieces of data are necessary to respond to the SMLC: the serving
cell ID, the timing advance, and a measurement report. The SSM knows the serving cell ID, the
RSS knows the timing advance, and RSS HO maintains a sliding window of measurement reports
(for this case, the latest measurement report is sufficient). Assuming no handover is in progress,
the SSM sends a ta request to its associated RRSM for this call. The SSM starts timer LCS
Supervision Timer to guard the receipt of a TA response from the RRSM. Once the information
is located, the SSM will stop the timer LCS Supervision Timer and then build a BSSLAP TA
Response message, with the measurement report and timing advance, and the serving cell ID.
This message is en-capsulated in a BSSMAP-LE Connection Oriented Information message
(and further encapsulated into an SCCP DT1) and sent to the SMLC.
Stats
BSSLAP_TA_REQ
This statistic is pegged everytime a BSSLAP TA Request is received by the BSS.
BSSLAP_TA_RESP
This statistic is pegged everytime BSSLAP TA Response message is sent to the SMLC/MSC.
MT_LCS_ON_SDCCH
This stat is pegged each time there is an MT LTU on an SDCCH. It is also pegged for an MT
call when any LCS transaction takes place while the MS is on an SDCCH. Any of the following
messages received over the A - Interface are considered LCS Transaction initiations:
BSSLAP TA Request, BSSLAP MS Position Command, BSSMAP Perform Location
Request (latter only applies in the case of a BSS based SMLC.)

Timing Advance Positioning Method Version 1 Rev 4

RSS RRSM SSM SMLC/MSC
BSSLAP TA
Request
TA Request
BSSLAP_TA_REQ
Abis TA Request
Abis TA Response
TA Response
BSSLAP_TA_RESP
BSSLAP T
TA
Response


BSSLAP Reset
Location determination is considered a lower priority feature compared to RR management procedures,
such as handover, ciphering, assignment, and mode modify. So if any intra-BSS Handover (or other
RR management procedure) is necessary, it will preempt an ongoing LCS procedure.
When SSM is informed that an intra-BSS Handover (or other RR management procedure)
is necessary, it will abort any processing of an ongoing LCS attempt. During the intra-BSS
handover or RR management procedure, the LCS Supervision Timer is still running. Once the
intra-BSS handover or RR management procedure is completed, the SSM process performs the
TA procedure to retrieve the timing advance and measurement report data. The SSM process
performs the TA procedure within the time allotted by the LCS Supervision Timer.
After the TA procedure is completed, the SSM process includes the timing advance and measurement
report data in the BSSLAP Reset message which is sent to the SMLC via the MSC (encapsulated
within a BSSMAP Connection Oriented Message). The cause value in the BSSLAP Reset message
is set to "Intra-BSS Handover" if the RR management procedure was intra-BSS handover. If the RR
management procedure was something else, the cause value is set to "Failure for other radio related
events". The RR management procedures that will require this behavior are as follows: intra-BSS
handover, assignment, ciphering, classmark update procedures, and mode modify. Note that if the ta
response comes back from RRSM after the BSSLAP Reset has been sent, it will be ignored.
BSSLAP_RESET
This statistic is pegged everytime a BSSLAP Reset message is sent.


BSSLAP Reset
RSS (Abis) RRSM SSM

BSSMAP CO1
Abis TA request (BSSLAP TA Request)
Abis TA request
Can happen at
RR Management Procedure Needed
anytime
Abis TA response
Abis TA response
These msgs ignored
RR Management Procedure Performed
RR Management Procedure Completed

If Supervisory timer st
Abis TA request running
Abis TA request
Abis TA response BSSLAP_RESET

Abis TA response
BSSMAP CO1
(BSSLAP Reset)

Version 1 Rev 4 E-OTD and A-GPS Positioning Method
E-OTD and A-GPS Positioning Method

For E-OTD and A-GPS, the MS unit will be required to either assist in the positioning calculation or
perform the positioning calculation. The BSS’s role in this procedure is to act as a conduit between
the MS and the SMLC, as well as act as a conduit between the LMU and the SMLC. The LMUs
will be providing BTS timing information for use by the SMLC. Whether the scenario is E-OTD or
A-GPS is irrelevant to the BSS. The two messages that govern the E-OTD/A-GPS procedures are
the BSSLAP MS Position Command and the BSSLAP MS Position Response. These messages
contain embedded RRLP messages, which are transparent to the BSS. The BSS will not be
concerned about which flavour BSSLAP message is appropriate for a given RRLP message, the
BSS will decide on the Command/Response BSSLAP by the direction of the message:
• SMLC -> BSS : BSSLAP MS Position Command
• BSS -> SMLC : BSSLAP MS Position Response
The BSSLAP messages are transported inside the BSSMAP-LE Connection Oriented Information
message. Again, remember that before the BSSLAP MS Position Command message arrives
to begin the E-OTD/A-GPS scenario, the MSC will have set up a call (if not set up already),
and the BSS will have set up an SCCP connection to the SMLC.
Successful Scenario
E-OTD, MS Assisted E-OTD, and A-GPS. The SMLC determines possible assistance data and
sends an RRLP Measure Position Request message encapsulated in a BSSLAP MS Position
Command message to the MSC. The MSC forwards the BSSLAP MS Position Command message
to the BSS via a BSSMAP Connection Oriented Information message. The SSM process
decapsulates the RRLP Measure Position Request message from the BSSLAP MS Position
Command and re-wraps the RRLP in a RR Application Information message and forwards it to the
RRSM process. The SSM process then starts the LCS Supervision Timer to guard for a response
from the RRSM. The RRSM process sends the RR message through the RSS to the MS. The
MS performs the requested E-OTD or A-GPS measurements. If the MS is able to calculate its
own location, the MS computes the E-OTD or A-GPS location estimate.
Any data necessary to perform these operations are provided in the RRLP Measure Position Request
message or available from broadcast sources. The resultant E-OTD or A-GPS measurements
or location estimate is returned to the BSS in a RRLP Measure Position Response message.
This message is encapsulated in a RR Application Information message. The MS sends the RR
Application Information message to the RSS which forwards to the RRSM, who forwards the
message to the SSM process. It then extracts the RRLP Measure Position Response message
from the RR Application Information message and re-wraps it in a BSSLAP MS Position Response
message. In addition, the SSM process includes the timing advance and the measurement report
in the BSSLAP MS Position Response message. The SSM will also stop the LCS Supervision
Timer if the C/R bit of the RR Application Information message indicates a Final Response. The
BSSLAP MS Position Response is then encapsulated in the BSSMAP Connection Oriented
Information message which is forwarded to the SMLC via the MSC.
BSSLAP_MS_POS_CMD
This statistic is pegged everytime a BSSLAP MS Position Command message is sent to the BSS.
BSSLAP_MS_POS_RESP
This statistic is pegged everytime a BSSLAP Position Response message is
sent from the BSS to SMLC.

E-OTD and A-GPS Positioning Method Version 1 Rev 4
E-OTD and A-GPS Positioning Method

MS RSS RRSM SSM SMLC
BSSLAP MS
Position Command
RR Application
Information
RR Application
RR Application Information
Information
RR Application
Information
RR Application
Information
RR Application
BSSMAPLE_PERF_LOC_REQ_MSGS
Information
BSSLAP MS Position
Response


BSSLAP Abort
If the LCS Supervision Timer expires, the SSM process sends a BSSLAP Abort message to
the SMLC with a cause of "Supervision Timer Expired" and abandons this positioning attempt.
The BSSLAP Abort message is encapsulated in a BSSMAP Connection Oriented Information
message and is sent to the SMLC via the MSC. The BSSLAP Abort message instructs the SMLC
to abort the Location Services procedure. Another reason for the BSSLAP Abort message being
sent is an inter-BSS handover as the TA request is useless as it about to change to a new cell
in a different BSC, in this case the cause value will be "Inter-BSS Handover".
During an LCS procedure, the SMLC may abort the attempt at any time by sending a
BSSLAP Abort message to the BSC. When SSM receives this message, it will stop the LCS
Supervision Timer and abort further processing. Any responses from RRSM for this location
attempt after receiving the BSSLAP Abort message will be ignored.
If, during an LCS procedure, SSM determines that the call is going to be released (this could
occur for any number of reasons such as MSC teardown, loss of signalling connection to the
MS such as T10 or T3103 timer expiries, etc), SSM will send a BSSLAP Abort message to the
SMLC with cause value "Loss of signalling connection to MS" and abandon any further LCS
processing for this call. Further, if the SCCP connection to the MSC is torn down, then the SCCP
connection to the SMLC will be torn down as well. If any BSSLAP command is received from
the SMLC while the call is being torn down, SSM will respond to the BSSLAP command with
a BSSLAP Abort with cause value "Loss of signalling connection to MS".
BSSLAP_ABORT_SENT
This statistic is pegged everytime a BSSLAP Abort message is sent.
BSSLAP_ABORT_RCV
This statistic is pegged everytime a BSSLAP Abort message is received.


RSS RRSM SSM SMLC
Positioning Attempt in Progress
BSSLAP_ABORT_SENT
BSSLAP Abort
1. Supervisory Timer Expired

2. Inter - BSS Handover -
3. Loss of Signalling Link
BSSLAP Abort
BSSLAP_ABORT_RCV
Supervisory timer
stopped
Responses ignored
regarding positioning
attempt

Version 1 Rev 4 SMLC-SMLC Messaging (BSS Based SMLC only)
SMLC-SMLC Messaging (BSS Based SMLC only)

Technically, SMLC-SMLC messaging occurs in the NSS-based SMLC case, but the BSS will not be
involved in it at all. The BSS is involved in the BSS-based SMLC case only because the SMLC’s only
connection to the PLMN (the other components in the network) is through the BSS. This causes
the BSS to act similarly to an STP in SS7. However, unlike a true STP, the information to route the
message appropriately is not found in the routeing label for SMLCPP messages (like any other
message), the DPC in any received message will be the BSS’s SPC. The BSSMAP(LE) Connectionless
Information handling which is done by the CLM will perform the routing of the message.
Routing
When a BSSMAP-LE Connectionless Information message is received by MTPL3 from the
SMLC, it comes in on an SCCP UDT. Like any other SCCP UDT, it is sent to CLM for processing.
When CLM examines the message type, it will discover that the message is a BSSMAP-LE
Connectionless Information message. CLM realises that this message is from the SMLC, and
at present the BSSMAP-LE Connectionless Information message can only carry encapsulated
SMLCPP messages, so the message must be destined for another SMLC. The BSS’s only link to
the rest of the network is through the MSC. CLM sends a BSSMAP Connectionless Information
message carrying the SMLCPP message to an MTPL3 serving the A-interface, who forwards it
to the MSC. The MSC will be able to route the message from that point on using the Network
Element Identity fields in the message. These are provided by the SMLC in the original message,
and identify (in one of various formats) which SMLC the message is to/for. Similarly, if a BSSMAP
Connectionless Information message is received by an MTPL3 serving the MSC, it will send the
entire SCCP UDT to CLM, who will forward its content on to an MTPL3 serving the Lb linkset.
BSSMAP_CONLESS_INFO_RCV
This statistic is pegged everytime a BSSMAP Connectionless Information message
is received from the MSC to the BSS.
BSSMAP_CONLESS_INFO_SENT
This statistic is pegged everytime a BSSMAP Connectionless Information
message is sent to the MSC by the BSS.
BSSMAPLE_CONLESS_INFO_RCV
This statistic is pegged everyime a BSSMAP-LE Connectionless Information
message is received from the SMLC to the BSS.
BSSMAPLE_CONLESS_INFO_SENT
This statistic is pegged everyime a BSSMAP-LE Connectionless Information
message is sent to the SMLC by the BSS.

SMLC-SMLC Messaging (BSS Based SMLC only) Version 1 Rev 4
SMLC-SMLC Messaging (BSS Based SMLC only)

MSC MTPL3 (A) CLM MTPL3 (Lb) SMLC
BSSMAP
BSSMAP_CONLESS_INFO_RCV
Connectionless
Info
BSSMAP
Connectionless
Info
BSSMAP- LE
BSSMAPLE_CONLESS_INFO_SENT
Connectionless
Info
BSSMAP- LE
Connectionless
Info
BSSMAP- LE
BSSMAPLE_CONLESS_INFO_RCV
Connectionless
Info
BSSMAP- LE
Connectionless
BSSMAP Info
BSSMAP_CONLESS_INFO_SENT
Connectionless
Info
BSSMAP
Connectionless
Info

Version 1 Rev 4 Processor Utilization Statistics
Processor Utilization Statistics

This statistic applies to the process utilization of GPROCs and TCUs within each
site of the BSS (i.e. BTS, BSC and RXCDR).
CPU_USAGE
Records the maximum, minimum and mean values of the short-term processor utilization measurement.
Every second an internal timer will expire causing the process utilization percentage to be sent to the
stats process. This statistic is recorded for each GPROC and TCU under the control of a BSS.

Processor Utilization Statistics Version 1 Rev 4
Processor Utilization Statistics
PROCESSOR UTILIZATION (MAX, MIN, MEAN)

100%
90%
80% MAX
70% MIN
60%
50% MEAN
40%
30%
20%
10%
0%
0 1 2 3 4 5 6 7 8 9 10 11
STATISTICAL INTERVAL NUMBER

Version 1 Rev 4 Processor Utilization Statistics

Key Statistics Version 1 Rev 4
Chapter 7
Key Statistics

Version 1 Rev 4 Key Statistics

Key Statistics
Objectives
• State why we use key statistics.
• Name the five key statistic groups.
• Recognise a key statistic from a raw statistic calculation.

Version 1 Rev 4 Introduction — Key Statistics
Introduction — Key Statistics

Key statistics provide the operator with a summary of system performance during a specific
interval. They are designed to give an overall indication of the condition of the system to
help detect congestion trends and possible performance degradation.
Key statistics are provided to facilitate the monitoring of the most important network parameters.
Key statistics are produced by combining various raw statistic’s values using a pre-defined formula.
For example, various handover failure statistics may be combined and averaged over the total
number of handover attempts to produce a handover failure rate key statistic.
At the beginning of each day a key statistics report for the previous 24 hours could be
obtained from which network performance could be assessed and potential problems identified.
Further information could then be obtained from the raw statistics.
The key statistics are divided into five groups.
• SDCCH channel usage
• TCH channel usage
• Call summary
• RF loss summary
• Connection establishment
• Link utilisation

Introduction — Key Statistics Version 1 Rev 4
Introduction — Key Statistics
What’s Up
Doc?

Version 1 Rev 4 Key Statistics
Key Statistics
All key statistics are calculated on a per-cell basis except where specified.
Stats
SDCCH channel usage
• SDCCH mean holding time

• SDCCH mean arrival rate
• SDCCH traffic
• SDCCH congestion
TCH channel usage
• TCH mean holding time

• TCH mean arrival rate
• TCH traffic
• TCH congestion
• Mean TCH busy time
Call summary
• Handover success rate

• Handover failure rate
• TCH assignment success rate
• Total calls key
• Unsuccessful internal handovers without re-establishment
• Unsuccessful internal handovers with successful re-establishment
• Successful internal handovers
RF loss summary
• RF loss rate
• SDCCH RF loss rate
• TCH RF loss rate
• Cell TCH assignments
• Cell TCH allocations
Connection establishment
• Mean inter arrival time

• Successful immediate assignment procedures
• Attempted immediate assignment procedures
• Mean arrival time between calls
Link Utilisation
• MTL utilisation rx and tx

Key Statistics
SDCCH channel usage
TCH channel usage
Call summary
RF loss summary
Connection establishment

Version 1 Rev 4 SDCCH Channel Usage
SDCCH Channel Usage

SDCCH_MEAN_HOLDING_TIME
Units: Seconds.
Usage: Network planning.
This statistic measures the average duration of calls on SDCCH channels in seconds.
BUSY_SDCCH_MEAN is the mean number of SDCCHs occupied in the cell during the reporting
interval and this, when multiplied by the duration of the interval gives the total number of call-seconds
for that interval. Dividing by the number of sdcch allocations gives the average time held per access.
Raw statistics Description

BUSY_SDCCH_MEAN Mean value of BUSY_SDCCH statistic.
Average number of SDCCHs carrying traffic in a
cell during a collection interval.
ALLOC_SDCCH Total number of successful sdcch allocations.
SDCCH_MEAN_ARRIVAL_RATE
Units: Calls per hour.

This statistic indicates the call arrival (set-up) rate for the SDCCHs in the cell.
It is measured in calls per hour.

OK_ACC_PROC Successful accesses by procedure. The value
used is the sum of bins 0 — 7 in the array.

SDCCH Channel Usage Version 1 Rev 4
SDCCH Channel Usage

SDCCH_MEAN_HOLDING_TIME
SDCCH
_MEAN = (BUSY_SDCCH x INTERVAL_SUM)
_HOLDING
ALLOC_SDCCH
_TIME
SDCCH_MEAN_ARRIVAL_RATE
SDCCH
SUM (OK_ACC_PROC)
_MEAN =
_ARRIVAL
SUM (INTERVAL)
_RATE

Version 1 Rev 4 SDCCH Channel Usage
SDCCH Channel Usage

SDCCH_TRAFFIC_CARRIED
Units: Erlangs.
This statistic gives the total traffic on the SDCCHs of the cell. It is measured in erlangs.

BUSY_SDCCH_MEAN Mean of BUSY_SDCCH statistic.
SDCCH_BLOCKING_RATE
Units: Percentage.
Usage: Quality of service monitoring.
Network planning.
This statistic indicates the percentage of call set-ups refused due to congestion on the SDCCHs.

ALLOC_SDCCH_FAIL Total number of times an attempt to allocate an
SDCCH fails due to congestion.
ALLOC_SDCCH Total number of successful SDCCH allocations.

SDCCH Channel Usage Version 1 Rev 4
SDCCH Channel Usage

(BUSY_SDCCH_MEAN
SDCCH_TRAFFIC =
SUM (INTERVAL)
_CARRIED
SDCCH_BLOCKING_RATE
SUM (ALLOC_SDCCH_FAIL)
SDCCH_BLOCKING = x 100%
_RATE SUM (ALLOC_SDCCH + ALLOC_SDCCH_FAIL)

Version 1 Rev 4 TCH Channel Usage
TCH Channel Usage

TCH_MEAN_HOLDING_TIME
Units: Seconds.
This statistic tracks the average duration of calls on traffic channels (TCH) in seconds.
Raw Statistics Description

BUSY_TCH_MEAN Average number of busy FR TCHs.
BUSY_TCH_HR_MEAN Number of successful TCH allocations.
TOTAL_CALLS Total number of calls
ASSIGNMENT_REDIRECTION Tracks the number of times a call assignment
is redirected to another cell.
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC] Incoming Intra BSS Handovers
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] Incoming Inter BSS Handovers
The numerator and denominator may peg on different intervals (where a call extends across
multiple collection boundaries). This will affect the accuracy of the stat for the period. Therefore,
this stat should be used as a trend rather than focusing on specific values.

TCH Channel Usage Version 1 Rev 4
TCH Channel Usage

TCH_MEAN_HOLDING_TIME
TCH_MEAN_HOLDING_TIME =
Cell Level
(BUSY_TCH_MEAN + BUSY_TCH_HR_MEAN) * INTERVAL_LENGTH
TOTAL_CALLS + IN_INTRA_BSS_HO [IN_INTRA_BSS_HO_SUC]

+
IN_INTER_BSS_HO [IN_INTER_BSS_HO_SUC]
BSS Level
TOTAL_CALLS + ASSIGNMENT_REDIRECTION [DIRECTED_RETRY]

+
ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENT]
+
ASSIGNMENT_REDIRECTION [MULTIBAND_BAND]
+
IN_INTER_BSS_HO [IN_INTER_BSS_HO_SUC]
NTWK Level
TOTAL_CALLS + ASSIGNMENT_REDIRECTION [DIRECTED_RETRY]

+
ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENT]
+
ASSIGNMENT_REDIRECTION [MULTIBAND_BAND]

TCH Channel Usage

TCH _MEAN_ARRIVAL_RATE
Units: Calls per hour.

This statistic indicates the call arrival rate in calls per hour for the cell in question.

ALLOC_TCH Number of successful TCH allocations.
ALLOC_TCH_FAIL Number of unsuccessful TCH allocations.
TCH_Q_REMOVED Number of successful TCH allocations that were
originally in queue for both assignments and
external hand in.

TCH Channel Usage

TCH_MEAN_ARRIVAL_RATE
SUM(ALLOC_TCH + ALLOC_TCH_FAIL - TCH_Q_REMOVED)

TCH_MEAN =
_ARRIVAL_RATE SUM (INTERVAL)

TCH Channel Usage

TCH_TRAFFIC_CARRIED
Units: Erlangs.
This statistic gives the total traffic on the TCHs of the cell. This key statisitc should be between
0 and 7 for single carrier cells, 0 and 15 for 2 carrier cells etc.

BUSY_TCH_MEAN Mean of BUSY_TCH statistic.
BUSY_TCH_HR_MEAN Mean of BUSY_TCH_HR
TCH_BLOCKING_RATE
Units: Percentage.
Network planning.
Fault finding.
The statistic indicates a percentage of call setup and intra-cell handovers refused
due to congestion on the TCHs.

ALLOC_TCH_FAIL Number of unsuccessful TCH allocations.
ASSIGNMENT_RESOURCE_REQ Number of successful TCH allocations from
queue (for both assignments and external hand
in.)
Note on TCH_Q_REMOVED —. From GSR7 bins regarding concentric cell inner zones have been
added to this Stat, though they are not included in this calculation of TCH_BLOCKING_RATE.
MEAN_TCH_BUSY_TIME
Units: Seconds.
Usage: Capacity planning.
This key statistic is calculated on a cell basis and will provide a mean usage time per TCH.

BUSY_TCH Mean number of busy TCHs in per interval.
AVAILABLE_TCH Mean number of in-service TCHs.

TCH Channel Usage

TCH_TRAFFIC_CARRIED
SUM (BUSY_TCH_MEAN * INTERVAL

TCH_TRAFFIC = + BUSY_TCH_HR_MEAN * INTERVAL)
_CARRIED
SUM (INTERVAL)
TCH_BLOCKING_RATE
TCH_BLOCKING_RATE =
SUM (ALLOC_TCH_FAIL -
TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ] -
TCH_Q_REMOVED {HO_REQ] )
x 100%
SUM (ALLOC_TCH + ALLOC_TCH_FAIL -
TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ -
TCH_Q_REMOVED {HO_REQ] )
MEAN_TCH_BUSY_TIME
MEAN_TCH_BUSY_TIME =
BUSY_TCH * INTERVAL * 3600
AVAILABLE_TCH

TCH Channel Usage

Stats
CELL_TCH_ALLOCATIONS
Units: Counter.
This statistic tracks the number of successful allocations of a TCH within a cell
for both call originations and hand ins.
Raw Statistic Description

ALLOC_TCH Number of successful TCH allocations
TCH_BLOCKING_RATE_INNER_Z
Units: Percentage
Usage: Quality of service monitoring
Network Planning
Fault finding
This statistic provides the percentage of all requests for Inner Zone TCH resources (originations
and hand ins) which fail due to no available inner TCH resources.

ALLOC_TCH_INNER_Z Number of successful TCH allocations within
Inner Zone
ALLOC_TCH_FAIL_INNER_Z Number of unsuccessful TCH allocations within
Inner Zone
external hand in.
Note on TCH_Q_REMOVED — From GSR7 bins for concentric cells have been added to this Stat,
and these are included in the calculation of TCH_BLOCKING_RATE_INNER_Z (bins 2 and 3).

TCH Channel Usage

CELL_TCH_ALLOCATIONS
TCH_MEAN (BUSY_TCH_MEAN x INTERVAL_SUM x 3600)

=
_HOLDING_TIME
(ALLOC_TCH)
TCH_BLOCKING_RATE_INNER_Z
ALLOC_TCH_FAIL_INNER_Z -
TCH_Q_REMOVED [ASSIGNMENT_REQ_INNER_Z] -
TCH_Q_REMOVED [HO_REQ_INNER_Z]
TCH_BLOCKING =
* 100%
_RATE_INNER_Z
ALLOC_TCH_INNER_Z -
ALLOC_TCH_FAIL_INNER_Z -
TCH_Q_REMOVED [ASSIGNMENT_REQ_INNER_Z] -

Version 1 Rev 4 TCH_BLOCKING_RATE_OUTER_Z
TCH_BLOCKING_RATE_OUTER_Z
Units: Percentage
Network Planning
Fault finding
This statistic provides the percentage of all requests for Outer Zone TCH resources (originations
and hand ins) which fail due to no available Outer TCH resources.

ALLOC_TCH_FAIL Number of unsuccessful TCH allocations
ALLOC_TCH Number of successful TCH allocations in Outer Z
ALLOC_TCH_INNER_Z Number of successful TCH allocations within
Inner Zone
ALLOC_TCH_FAIL_INNER_Z Number of unsuccessful TCH allocations within
Inner Zone
external hand in.
Note on TCH_Q_REMOVED — From GSR7 bins for concentric cells have been added to this
Stat, and these are included in the calculation of TCH_BLOCKING_RATE_INNER_Z .

TCH_BLOCKING_RATE_OUTER_Z Version 1 Rev 4
TCH_BLOCKING_RATE_OUTER_Z
[
[ ALLOC_TCH_FAIL - ALLOC_TCH_FAIL_INNER_Z –
[ TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ] –
TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ_INNER_Z]
[ –
TCH_Q_REMOVED [HO_REQ] –
TCH_BLOCKING_ = * 100%
RATE_OUTER_Z
[ ALLOC_TCH – ALLOC_TCH_INNER_Z [ +
[
[ALLOC_TCH_FAIL – ALLOC_TCH_FAIL_INNER_Z –
[ TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ] –
TCH_Q_REMOVED [ASSIGNMENT_RESOURCE_REQ_INNER_Z]
[ –
[TCH_Q_REMOVED [HO_REQ] – TCH_Q_REMOVED [HO_REQ_INNER_Z] [

Version 1 Rev 4 Call Summary
Call Summary
HANDOVER_SUCCESS_RATE
Units: Percentage.
Optimization.
Fault finding.
This statistic represents handovers which were attempted from the source cell that
succeeded to establish at the destination cell. The handover attempt is counted
when the handover command is sent to the MS.
Raw statistics: Description

OUT_INTER_BSS_HO_SUC Outgoing interBSS handover.
INTRA_CELL_HO_SUC Intra-cell handover completed.
OUT_INTRA_BSS_HO_SUC Intra-BSS handover completed.
OUT_INTER_BSS_HO_ATMPT Inter-BSS handover attempts.
INTRA_CELL_HO_ATMPT Intra-cell handover attempts.
OUT_INTRA_BSS_HO_ATMPT Intra-BSS handover attempts.
This statistic is pegged after the system checks for congestion.

Handover Success Rate + Handover Failure Rate≠ 100% because the calls that fail and
recover to the initial cell are not included in either of these values.

Call Summary Version 1 Rev 4
Call Summary
HANDOVER_SUCCESS_RATE
HANDOVER_SUCCESS_RATE =
SUM(OUT_INTER_BSS_HO_SUC + INTRA_CELL_HO_SUC +
OUT_INTRA_BSS_HO_SUC)
x 100%
SUM(OUT_INTER_BSS_HO_ATMPT + INTRA_CELL_HO_ATMPT ++
OUT_INTRA_BSS_HO_ATMPT)

Call Summary
HANDOVER_FAILURE_RATE
Units: Percentage.
Optimization.
Fault finding.
This statistic represents handovers that were attempted from the source cell that failed to establish
at the destination cell. The call was also dropped as it failed to re-establish at the source cell. The
handover attempt is counted when the ‘‘handover command" message is sent the MS.

INTRA_CELL_HO_LOSTMS Intra-cell handover failed and MS lost.
OUT_INTRA_BSS_HO_LOSTMS Intra-BSS handover failed and MS lost.
INTER_BSS_HO_LOSTMS Determined from the calculation opposite.
OUT_INTER_HO Clear command from MSC.
INTER_BSS_MS_FAIL Inter-BSS handover, MS handover failed
message received.
OUT_INTER_BSS_HO_ATMPT Inter-BSS handover attempts.
NTRA_CELL_HO_ATMPT Intra-cell handover attempts.
OUT_INTRA_BSS_HO_ATMPT Intra-BSS handover attempts.
This statistic is pegged after the system checks for congestion.

Call Summary
HANDOVER_FAILURE_RATE
HANDOVER_FAILURE_RATE =
SUM (INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS +

INTER_BSS_HO_LOSTMS)
x 100%
SUM (OUT_INTER_BSS_HO_ATMPT + INTRA_CELL_HO_ATMPT ++
OUT_INTRA_BSS_HO_ATMPT)
Where:
INTER_BSS_HO_LOSTMS
= OUT_INTER_BSS_HO_ATMPT - OUT_INTER_BSS_HO_RETURN - OUT_INTER_BSS_HO_SUC

Call Summary
CALL_SETUP_SUCCESS_RATE
Units: Percentage.
Network planning.
Fault finding.
Tracks the percentage of call attempts that result in a successful TCH access. Network
accesses which do not require a TCH are excluded i.e. location updates, SMS on
SDCCH and supplementary service attempts.

TOTAL_CALLS Total number of calls.
ASSIGNMENT_REDIRECTION How many incoming SD-TCH handovers, all bins
OK_ACC_PROC Sum of bins:
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV-RQ_EMERG
CM_RE-ESTABLISH
PAGE_RESPONSE
LOC_FLW_ON_REQ_NORMAL
LOC_FLW_ON_REQ_SMS
SMS_INIT_ON_SDCCH How many SMS transactions on SDCCH
SMS_INIT_ON_SDCCH_HO_IN How many incoming SDCCH handovers during
SMS
MT_LCS_ON_SDCCH Counts the number of MS terminated SDCCH
sessions for Location Services

Call Summary
CALL_SETUP_ SUM(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

SUCCESS_RATE = x 100%
OK_ACC_PROC (CM_SERV_REQ_CALL)
+
OK_ACC_PROC (CM_SERV_REQ_SMS)
+
OK_ACC_PROC (CM_SERV_REQ_EMERG)
+
OK_ACC_PROC (CM_RE-ESTABLISH)
+
OK_ACC_PROC (PAGE_RESPONSE)
+
OK_ACC_PROC (LOC_FLW_ON_REQ_NORMAL)
+
OK_ACC_PROC (LOC_FLW_ON_REQ_SMS)
+
(SMS_INIT_ON_SDCCH_HO_IN _
_
SMS_INIT_ON_SDCCH MT_LCS_ON_SDCCH)

Call Summary
TOTAL_CALLS_KEY
Units: Number of successful TCH connections.

Usage: Planning.
Indicates the number of successful TCH connections originating in the cell.

SUCCESS_INTERNAL_HO
Units: Number of successful handovers.

Usage: Planning.
Optimization.
This key statistic will provide the number of successful handovers per BSC
including both intra-cell and intra-BSS.

INTRA_CELL_HO_SUC Number of successful intra-cell handovers.
OUT_INTRA_BSS_HO_SUC Number of successful intra-BSS handovers.
OUT_HO_CAUSE_ATMPT[bin#] Number of handover attempts per cell per cause

Call Summary
TOTAL_CALLS_KEY
TOTAL_CALLS_KEY = SUM (TOTAL_CALLS)
SUCCESS_INTERNAL_HO (Per intra_cell, per BSC)
SUCCESS_INTERNAL_HO = SUM(INTRA_CELL_HO[INTRA_CELL_HO_SUC])
SUCCESS_INTERNAL_HO (Per BSC)
SUCCESS_INTERNAL_HO = SUM(INTRA_CELL_HO_SUC + OUT_INTRA_BSS_HO_SUC)
SUCCESS_INTERNAL_HO (Per cause)
SUCCESS_INTERNAL_HO = SUM(OUT_HO_CAUSE_ATMPT[BIN#])

Call Summary
UNSUCCESS_INTERNAL_HO_REEST
Units: Number of unsuccessful handovers.

Usage: Optimisation planning
When this statistic is reported for intra-cell handover failures on a per BSC basis, it provides the number
of times a call fails to move from an occupied channel of a cell to another free channel on the same cell.

INTRA_CELL_HO_RETURN Number of intra-cell handovers where the MS
failed to gain a connection with the target TCH
and managed to return the source TCH.
OUT_INTRA_BSS_HO_RETURN Number of intra-BSS handovers where the MS
failed to gain a connection with the target cells
TCH and managed to return the source TCH.

Call Summary
UNSUCCESS_INTERNAL_HO_REEST (Per Intra-cell, Per BSC)
UNSUCCESS_INTERNAL_HO_REEST =
SUM(INTRA_CELL_HO[INTRA_CELL_HO_RETURN])
UNSUCCESS_INTERNAL_HO_REEST (Per BSS)
SUM(INTRA_CELL_HO[INTRA_CELL_HO_RETURN] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN])
UNSUCCESS_INTERNAL_HO_REEST (Per Cell)
(INTRA_CELL_HO[INTRA_CELL_HO_RETURN] +

Call Summary
UNSUCCESS_INTERNAL_HO_NOREEST
Units: Number of unsuccessful handovers.

Usage: Optimization.
Planning.
This key statistic will provide the number of unsuccessful handovers on a per BSC or per cell basis
where the MS did not manage to reestablish its connection to the source TCH.

INTRA_CELL_HO_LOSTMS Number of intra-cell handovers where the MS
and did not manage to return the source TCH.
OUT_INTRA_BSS_HO_LOSTMS Number of intra-BSS handovers where the MS
and did not manage to return the source TCH.

Call Summary
UNSUCCESS_INTERNAL_HO_NOREEST (BSS Level)
UNSUCCESS_INTERNAL_HO_NOREEST =
SUM (INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS)
UNSUCCESS_INTERNAL_HO_NOREEST (Cell Level)
UNSUCCESS_INTERNAL_HO_NOREEST =
(INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS)

Version 1 Rev 4 RF Loss Summary Statistics
RF Loss Summary Statistics

RF_LOSS_RATE
Units: Percentage.
Fault finding and optimization.
This statistic compares the total number of RF losses with the number of calls set up in the cell, plus
the number of calls handed into the cell. It indicates the cell/system ability to preserve calls.

RF_LOSSES_TCH RF losses on TCH.
RF_LOSSES_ SD RF losses on SDCCH.
OK_ACC_PROC Successful accesses by process. The value used
is the sum total of all the bins in the array.
IN_INTER_HO Incoming inter-BSS handovers.
IN_INTRA_BSS_HO_SUC Incoming intra-BSS handovers.
CELL_TCH_ASSIGNMENTS
Units: Number of TCHs.

The total number of calls that establish on a TCH. Should include both calls set up
on TCHs within a cell and handovers into the cell.

IN_INTER_BSS_HO_SUC Incoming inter-BSS handovers
IN_INTRA_BSS_HO_SUC Incoming intra-BSS handovers

RF Loss Summary Statistics Version 1 Rev 4

RF_LOSS_RATE
RF_LOSSES_SD
SUM +
RF_LOSS ( RF_LOSSES_TCH [1] + .... + RF_LOSSES_TCH [nTCH] )
x 100%
_RATE =
IN_INTER_BSS_HO_SUC
SUM (OK_ACC_PROC) + SUM +
IN_INTRA_BSS_HO_SUC
nTCH = number of TCHs in cell.
CELL_TCH_ASSIGNMENTS
CELL_TCH_ASSIGNMENTS = TOTAL_CALLS +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]

Version 1 Rev 4 RF Loss Summary Statistics

SDCCH_RF_LOSS_RATE
Units: Percentage.
Fault finding.
This statistic compares the total number of RF losses (while using an SDCCH), as a percentage
of the total number of call attempts for SDCCH channels. This statistic is intended to give
an indication of how good the cell/system is at preserving calls.

RF_LOSSES_SD RF losses on SDCCH.
ALLOC_SDCCH Total number of successful SDCCH allocations
CHAN_REQ_MS_FAIL Tracks number of times BSS times out waiting for
MS to establish on assigned SDCCH
TCH_RF_LOSS_RATE
Units: Percentage.
Usage: Quality of service.
Fault finding.
The TCH_RF_LOSS_RATE statistics tracks the percentage of TCH resources that are
abnormally released due to a failure on the radio interface.

TOTAL_CALLS Total number of calls
RF_LOSSES_TCH RF Losses on FR TCH.
RF_LOSSES_TCH_HR RF Losses on HR TCH
IN_INTER_BSS_HO_SUC Number of successful incoming inter-BSS
handovers.
IN_INTRA_BSS_HO_SUC Number of successful incoming intra-BSS
handovers.
ASSIGNMENT_REDIRECTION Tracks the number of times a call assignment is
redirected to another cell.

RF Loss Summary Statistics Version 1 Rev 4

SDCCH_RF_LOSS_RATE
SDCCH_RF RF_LOSSES_SD
= x 100%
_LOSS_RATE
ALLOC_SDCCH -- CHAN_REQ_MS_FAIL
TCH_RF_LOSS_RATE
Cell level
RF_LOSSES_TCH + RF_LOSSES_TCH_HR
TCH_RF_LOSS_RATE = x 100%
(TOTAL_CALLS + IN_INTER_BSS_HO_SUC
+
IN_INTRA_BSS_HO_SUC)
BSS Level
(TOTAL_CALLS + IN_INTER_BSS_HO_SUC
+
ASSIGNMENT_REDIRECTION)
Network Level
(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

MEAN_INTER_ARRIVAL_TIME
Units: Seconds.
Usage: Planning.
This key statistic is calculated on a BSS basis, and indicates the mean of the sum
of time intervals between consecutive normal, SMS, supplementary, and emergency
requests for service. (SDCCH accesses.)

OK_ACC_PROC sum of bins:
CM_SERV _REQ_CALL
CM_SERV _REQ_SUPP
CM_SERV _REQ_SMS
CM_SERV _REQ_EMERG
ATTEMPTED_IMMED_ASSIGN_PROC
Units: Number of attempts.

Usage: Planning.
This key statistic is calculated on a BSS basis, and provides the number of attempted
assignment procedures that have been verified.

INV_EST_CAUSE_ON_RACH A-bis verified channel requests.
OK_ACC_PROC_SUC_RACH RSS L1 decoded channel requests.

MEAN_INTER_ARRIVAL_TIME (BSS Level)
SUM (INTERVAL) x 3600
MEAN_INTER_ARRIVAL_TIME = SUM (OK_ACC_PROC [CM_SERV_REQ_CALL]

+
OK_ACC_PROC [CM_SERV_REQ_SUPP]
+
OK_ACC_PROC [CM_SERV_REQ_SMS]
+
OK_ACC_PROC [CM_SERV_REQ_EMERG])
ATTEMPT_IMMED_ASSIGN_PROC (BSS Level)
ATTEMPT_IMMED_ASSIGN_PROC =
SUM (OK_ACC_PROC_SUC_RACH - INV_EST_CAUSE_ON_RACH)
ATTEMPT_IMMED_ASSIGN_PROC (Cell Level)
ATTEMPT_IMMED_ASSIGN_PROC =
(OK_ACC_PROC_SUC_RACH - INV_EST_CAUSE_ON_RACH)

SUCCESS_IMMED_ASSIGN_PROC
Units: Number of successful procedures.

Usage: Planning.
Network expansion.
This key statistic is calculated on a BSS or Cell basis, and provides the number
of successful assignment procedures.

CHAN_REQ_MS_BLK Immediate assignment rejects.

SUCCESS_IMMED_ASSIGN_PROC (BSS Level)
SUCCESS_IMMED_ASSIGN_PROC =
SUM (OK_ACC_PROC_SUC_RACH - INV_EST_CAUSE_ON_RACH - CHAN_REQ_MS_BLK)
SUCCESS_IMMED_ASSIGN_PROC (Cell Level)
SUCCESS_IMMED_ASSIGN_PROC =
(OK_ACC_PROC_SUC_RACH - INV_EST_CAUSE_ON_RACH - CHAN_REQ_MS_BLK)

SDCCH_ACCESS_SUCCESS_RATE
Units: This statistic calculates the proportion of SDCCH

activation which is followed by successful MS
accesses.
Usage: Planning
This key statistic is calculated on a BSS Cell basis, and provides the number of successful MS accesses.

CHAN_REQ_MS_BLK Immediate assignment rejects.
OK_ACC_PROC Sum of bins: CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV_REQ_SUPP
CM_SERV–RQ_EMERG
CM_RE–ESTABLISH
PAGE_RESPONSE
LOCATION_UPDATE
IMSI_DETACH
LOCATION_SERVICES

SDCCH_ACCESS_SUCCESS_RATE
OK_ACC_PROC[CM_SERV_REQ_CALL] +
OK_ACC_PROC[CM_SERV_REQ_SMS] +
OK_ACC_PROC[CM_SERV_REQ_SUPP] +
OK_ACC_PROC[CM_SERV_REQ_EMERG] +
OK_ACC_PROC[CM_REESTABLISH] +
OK_ACC_PROC[LOCATION_UPDATE] +
OK_ACC_PROC[IMSI_DETACH] +
OK_ACC_PROC[PAGE_RESPONSE] +
SDCCH_ACCESS_SUCCESS_RATE = OK_ACC_PROC[LOCATION_SERVICES]
OK_ACC_PROC_SUC_RACH –
INV_EST_CAUSE_ON_RACH –
CHAN_REQ_MS_BLK

MEAN_ARRIVAL _TIME_BETWEEN_CALLS
Units: Seconds.
Usage: Planning.
This key statistic is calculated on a per cell basis, and gives the average length of
time between channel requests in the cell.

CHAN_REQ_CAUSE_ATMPT [CM_SERV_REQ_CALL]
CHAN_REQ_CAUSE_ATMPT [CM_SERV_REQ_EMERG]

MEAN_ARRIVAL_TIME_BETWEEN_CALLS
MEAN_ARRIVAL_TIME_BETWEEN_CALLS =
SUM (INTERVAL) X 3600
SUM [CHAN_REQ_CAUSE_ATMPT(CM_SERV_CALL)]
+
[CHAN_REQ_CAUSE_ATMPT(CM_SERV_EMERG)]

Version 1 Rev 4 Link Utilisation
Link Utilisation
MTL_UTILISATION_RX
Units: Percentage.
Network planning.
The MTL_UTILISATION_RX statistics provides a measure of MTL utilisation

for the MSC to BSS direction.
Formula
_ _ _ _ _ _
_
_ _
NOTE: As an explanation as to how the formula was derived, refer to the

following which shows more details:
_ _ _ _ _ _
_ _
_ _

MTP_MSU_RX Number of MSUs received
MTP_SIF_SIO_RX Number of SIF and SIO octets received over the
signalling link
SIB_RX Counts the number of Status Indication Busy
LSSU messages received
MTP_LINK_INS Duration of link in the INS state

Link Utilisation Version 1 Rev 4
Link Utilisation
MTL_UTILISATION_RX
MTL_UTILISATION_RX = ((MTP_MSU_RX*6) + MTP_SIF_SIO_RX) + (SIB_RX * 7) * 100
(MTP_LINK_INS * 8)

Link Utilisation
MTL_UTILISATION_TX
Units: Percentage.
Network planning.
The MTL_UTILISATION_TX statistics provides a measure of MTL utilisation

for the BSS to MSC direction.
Formula
_ _ _ _ _ _
_ _
_ _
NOTE: As an explanation as to how the formula was derived, refer to the

following which shows more details:
_ _ _ _ _ _
_ _
_ _

MTP_MSU_TX Number of MSUs transmitted
MTP_SIF_SIO_TX Number of SIF and SIO octets transmitted over
the signalling link
SIB_TX Counts the number of Status Indication Busy
LSSU messages transmitted
MTP_LINK_INS Duration of link in the INS state

Link Utilisation Version 1 Rev 4
Link Utilisation
MTL_UTILISATION_TX
MTL_UTILISATION_TX = ((MTP_MSU_TX*6) + MTP_SIF_SIO_TX) + (SIB_TX * 7) * 100
(MTP_LINK_INS * 8)


Network Health Statistics Version 1 Rev 4
Chapter 8
Network Health Statistics

Version 1 Rev 4 Network Health Statistics


Objectives
• Understand the network health statistics.


Network health reports are calculated statistics that quantify BSS performance from the subscriber’s
perspective. They were originally designed by Motorola Optimisation engineers who believed they were
more useful than the standard key statistics, and are now available on the OMC. The OMC calculates
these statistics using a combination of the raw and key statistics explained in earlier sections.
The network health statistics are organized in the following groupings:
HEALTH CHECK:
CALL_SETUP_SUCCESS_RATE DROP_CALL_RATE
CALL_SUCCESS_RATE RANKING_FORMULA
CALL_VOLUME SDCCH_BLOCKING_RATE
TCH_TRAFFIC_CARRIED
SDCCH CONGESTION:
SDCCH_ACCESSES SDCCH_TRAFFIC_CARRIED
SDCCH_USAGE SDCCH_CONGESTION_TIME
SDCCH_BLOCKING_RATE
TCH CONGESTION:
TCH_ACCESSES TCH_CONGESTION_TIME
MAX_TCH_BUSY HO_PER_CALL
SPILL_OVER_FACTOR TCH_TRAFFIC_CARRIED
HANDOVER PERFORMANCE:
MEAN_TIME_BETWEEN_HO INCOMING_HO_VOLUME
OUTGOING_HO_VOLUME INTERNAL_SUCCESS
INTRA_CELL_HO_FAIL_LOST_MS INTRA_CELL_HO_FAIL_RECOVERED
INTRA_CELL_HO_SUCCESS_RATE INTERNAL_LOST
INTERNAL_RECOVERED HANDOVER_PERCENTAGE_BY_CAUSE
OUT_INTER_BSS_HO_SUCCESS_RATE _VALUE
OUT_INTER_BSS_HO_FAIL_RECOVERED OUT_INTER_BSS_HO_FAIL_LOST_MS
OUT_INTER_CELL_HO_FAIL_RECOVER OUT_INTER_CELL_HO_FAIL_LOST_MS
OUT_INTER_CELL_HO_SUCCESS_RATE
PAGING PERFORMANCE:
AIR_INTERFACE_PAGING MSC_PAGING
PAGING_OVERFLOW_RATE PAGING_RESPONSE
PAGING_SUCCESS_RATE PAGING_COMPRESSION_RATE
RADIO PERFORMANCE:
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE CALL_SETUP_RF_ASSIGNMENT_FAIL
_LOST_MS _RATE_RECOVERED_MS
CALL_SETUP_RF_ASSIGNMENT_SUCCESS OUT_INTER_CELL_HO_FAIL_LOST_MS
_RATE OUT_INTER_CELL_HO_SUCCESS_RATE
OUT_INTER_CELL_HO_FAIL_RECOVER TCH_RF_LOSS_RATE
ASSIGN_SUCCESS_RATE
MEAN_TIME_BETWEEN_DROPS


HEALTH CHECK
SDCCH CONGESTION
TCH CONGESTION
HANDOVER PERFORMANCE
PAGING PERFORMANCE
RADIO PERFORMANCE


Units: Percentage.
Network planning.
Fault finding.
Tracks the percentage of call attempts that result in a successful TCH access. Network
accesses which do not require a TCH are excluded: for example, location updates,
SMS on SDCCH and supplementary service attempts.

ASSIGNMENT_REDIRECTION How many incoming SD-TCH handovers, all bins
OK_ACC_PROC Sum of bins:
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV-RQ_EMERG
CM_RE-ESTABLISH
PAGE_RESPONSE
LOC_FLW_ON_REQ_NORMAL
LOC_FLW_ON_REQ_SMS
SMS_INIT_ON_SDCCH How many SMS transactions on SDCCH
MT_LCS_ON_SDCCH Counts the number of mobile-terminated SDCCH
sessions for Location Services


CALLP_SETUP_ SUM(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

SUCCESS_RATE = x 100%
OK_ACC_PROC (CM_SERV_REQ_CALL)
+
OK_ACC_PROC (CM_SERV_REQ_SMS)
+
OK_ACC_PROC (CM_SERV_REQ_EMERG)
+
OK_ACC_PROC (CM_RE-ESTABLISH)
+
OK_ACC_PROC (PAGE_RESPONSE)
+
OK_ACC_PROC (LOC_FLW_ON_REQ_NORMAL)
+
OK_ACC_PROC (LOC_FLW_ON_REQ_SMS) +
SMS_INIT_ON_SDCCH_HO_IN -
SMS_INIT_ON_SDCCH _ MT_LCS_ON_SDCCH


DROP_CALL_RATE
This statistic shows the proportion of MSs which, having successfully accessed the TCH, subsequently
experience an abnormal release, caused by either radio or equipment problems. This includes RF
losses and losses during handovers. This statistic can be calculated at the cell, BSS, or network level.
Usage: Fault finding.

Service retainability.
Basis Cell, BSS, or network.
Type Percentage.
Raw statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].
RF_LOSSES_TCH.
TOTAL_CALLS.


DROP_CALL_RATE
RF_LOSSES_TCH +
Cell Level INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED])
DROP_CALL_RATE = * 100%
(TOTAL_CALLS +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]
+IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])
RF_LOSSES_TCH +
BSS Level INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
OUT_INTER_BSS_HO[INTER_BSS_HO_CLEARED])
(TOTAL_CALLS + ASSIGNMENT_REDIRECTION) +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC])
RF_LOSSES_TCH +
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
Network Level
OUT_INTER_BSS_HO[INTER_BSS_HO_CLEARED])
(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)


CALL_SUCCESS_RATE
This statistic shows the percentage of calls that end with normal completions at the radio subsystem.
It provides an indication of overall network performance from the subscriber’s point of view.
The CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATE network health
statistics are used to calculate this statistic.

Service accessibility.
Fault finding.
Basis Cell.
Type Percentage.
Raw statistics ASSIGNMENT_REDIRECTION.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS]
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED]
TOTAL_CALLS
RF_LOSSES_TCH
SMS_INIT_ON_SDCCH.
OK_ACC_PROC [CM_REESTABLISH]
[PAGE_RESPONSE]
[CM_SERV_REQ_CALL]
[CM_SERV_REQ_EMERG]
[CM_SERV_REQ_SMS].
[LOC_FLW_ON_REQ_NORMAL]
[LOC_FLW_ON_REQ_SMS]


CALL_SUCCESS_RATE
CALL_SUCCESS_RA TE (%) =
DROP_CALL_RATE
CALL_SETUP_SUCCESS_RATE *
100


RANKING_FORMULA
This statistic provides a measure by which cells can be ranked by performance. From this the cells
requiring the most urgent optimization can be identified. The value of this statistic increases for cells
with high call volumes and low call success rates, indicating that these cells should be optimized first.
The CALL_SUCCESS_RATE and CALL_SETUP_SUCCESS_RATE network
health statistics are used in this calculation.
Usage: Optimization..
Basis Cell.
Type Counter
Raw statistics ASSIGNMENT_REDIRECTION.
.INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS]
.MT_LCS_ON_SDCCH
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]
OK_ACC_PROC[CM_REESTABLISH].
OK_ACC_PROC[PAGE_RESPONSE].
OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_EMERG].
OK_ACC_PROC[CM_SERV_REQ_SMS]
OK_ACK_PROC[LOC_FLW_ON_REQ_SMS]
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL]
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED]
RF_LOSSES_TCH
SMS_INIT_ON_SDCCH.
TOTAL_CALLS


RANKING_FORMULA
2
RANKING_FORMULA = [(1 - CALL_SUCCESS_RATE)
* TOTAL_CALLS] * 100%
Higher the figure output when comparing cells will indicate which is to be optimized first


CALL_VOLUME
This statistic shows the total number of calls that successfully access a TCH.

Installation and commissioning.
Basis Cell.
Type Counter
Raw Statistics TOTAL_CALLS.

ASSIGNMENT_REDIRECTION.


CALL_VOLUME
CALL_VOLUME = TOTAL_CALLS + ASSIGNMENT_REDIRECTION


SDCCH_BLOCKING_RATE
This statistic is the percentage of SDCCH access attempts that were blocked,
including handover attempts.

Installation and commissioning.
Service accessibility.
Basis Cell.
Type Percentage.
Raw Statistics ALLOC_SDCCH.

ALLOC_SDCCH_FAIL.
TCH_TRAFFIC_CARRIED
This statistic is the mean number of busy TCHs during an interval, equivalent to the TCH traffic in erlangs.
Usage: Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Counter.
Raw Statistics BUSY_TCH_MEAN


SDCCH_BLOCKING_RATE
SDCCH_BLOCKING_RATE =
ALLOC_SDCCH_FAIL
* 100
(ALLOC_SDCCH + ALLOC_SDCCH_FAIL)
TCH_TRAFFIC_CARRIED
TCH_TRAFFIC_CARRIED = BUSY_TCH_MEAN


SDCCH_ACCESSES
This statistic is the number of times an SDCCH is successfully seized and a layer
2 SABM command is received from the MS.
Usage: RF Loss.
Congestion.
Quality of service.
Network planning.
Basis Cell.
Type Counter.
Raw Statistics ALLOC_SDCCH

CHAN_REQ_MS_FAIL.
This statistic is the mean number of busy SDCCHs during the interval. It is
equivalent to the SDCCH traffic in Erlangs.
Usage: RF Loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistics BUSY_SDCCH_MEAN


SDCCH_ACCESSES
SDCCH_ACCESS = (ALLOC_SDCCH - CHAN_REQ_MS_FAIL)
SDCCH_TRAFFIC_CARRIED = BUSY_SDCCH_MEAN


SDCCH USAGE STATISTICS
A group of health statistics have been introduced at GSR 7 that calculate the percentage of SDDCH
accesses for each cause value. This also includes the percentage of SDCCH failures against the total
number of SDCCH accesses. On this page all the statistics are listed, but as they are very similar
only two examples are shown on the opposite page and a full description can be found in W56.
SDCCH_USAGE_ ACCESS_FAILURE
CALL_REESTABLISHMENT
EMERGENCY_CALL
IMSI_DETACH
LOCATION_UPDATE
MS_ORIGINATED_CALL
MS_ORIGINATED_SMS
SMS_ORIGINATED_SS
PAGING_RESPONSE
SDCCH_USAGE_SMS
Usage Quality of Service

Fault Finding
Service Accessibility
Basis Cell
Type Percentage
Raw Statistics SMS_INIT_ON_SDCCH.
CHAN_REQ_MS_FAIL
OK_ACC_PROC[CM_SERV_REQ_CALL]
OK_ACC_PROC[CM_SERV_REQ_SMS]
OK_ACC_PROC[CM_SERV_REQ_SUPP]
OK_ACC_PROC[CM_SERV_REQ_EMERG]
OK_ACC_PROC[PAGE_RESPONSE]
OK_ACC_PROC[CM_REESTABLISHMENT]
OK_ACC_PROC[LOCATION_UPDATE]
OK_ACC_PROC[IMSI_DETACH]


SDCCH USAGE STATISTICS
CHAN_REQ_MS_FAIL
SDCCH_USAGE_ACCESS_FAILURE =
* 100
CHAN_REQ_MS_FAIL
SMS_INIT_ON_SDCCH
SDCCH_USAGE_SMS = 100
*
CHAN_REQ_MS_FAIL


SDCCH_CONGESTION_TIME
This statistic is the number of seconds for which all SDCCHs were busy in a cell.
Usage: RF Loss.
Congestion.
Quality of service
Network planning.
Optimization.
Basis Cell
Type Duration (total time in seconds).
Raw Statistics SDCCH_CONGESTION.
TCH_ACCESSES
This statistic is the total number of originating calls and incoming handovers
to a cell, on a cell, BSS, or network level.
Usage: Handover
Quality of service
Network planning.
Basis Cell, BSS, or network.
Type Counter.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].

TOTAL_CALLS
ASSIGNMENT REDIRECTION.


SDCCH_CONGESTION_TIME
SDCCH_CONGESTION
SDCCH_CONGESTION_TIME =
1000
TCH_ACCESSES
Cell level
TCH_ACCESSES = (TOTAL_CALLS +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
BSS level
TCH_ACCESSES = (TOTAL_CALLS +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] )
+ ASSIGNMENT_REDIRECTION
Network level
TCH_ACCESSES = (TOTAL_CALLS)+ ASSIGNMENT_REDIRECTION


TCH_CONGESTION_TIME_OUTER_ZONE
This statistic is the time in seconds for which all Outer Zone TCH channels in a cell are busy.
Usage: Congestion.
Quality of service
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
Note: If the Half Rate feature is unrestricted the raw statistic TCH_CONGESTION
is replaced with TCH_CONGESTION_HR.
TCH_CONGESTION_TIME_INNER_ZONE
This statistic is the time in seconds for which all Inner Zone TCH channels in a cell are busy.
Usage: Congestion.
Quality of service
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION_INNER_ZONE.
MAX_TCH_BUSY
This statistic is the maximum number of TCHs simultaneously busy during an interval.
Usage: Congestion.
Quality of service
Network planning.
Optimization.
Basis Cell.
Type Counter
Raw Statistics BUSY_TCH[MAX].

TCH_CONGESTION_TIME_OUTER_ZONE
TCH_CONGESTION_TIME _OUTER_ZONE = TCH_CONGESTION

1000
TCH_CONGESTION_TIME_INNER_ZONE
TCH_CONGESTION_TIME _INNER_ZONE = TCH_CONGESTION_INNER_Z

1000
MAX_TCH_BUSY
MAX_TCH_BUSY = BUSY_TCH[MAX]


HO_PER_CALL
This statistic is the number of handovers per call in an interval.
Usage: Quality of service

Fault finding.
Basis Cell.
Type Counter
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].
INTRA_CELL_HO[INTRA_CELL_HO_SUC].
TOTAL_CALLS
ASSIGNMENT_REDIRECTION.


HO_PER_CALL
Cell Level
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] +
INTRA_CELL_HO[INTRA_CELL_HO_SUC])
HO_PER_CALL =
TOTAL_CALLS
BSS Level
SUM (OUT_INTER_BSS_HO[OUT_INTRA_BSS_HO_SUC] +
HO_PER_CALL =
SUM (TOTAL CALLS + ASSIGNMENT_REDIRECTION)
Network Level
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] +
HO_PER_CALL =
SUM (TOTAL_CALLS)


MEAN_TIME_BETWEEN_HOs
This statistic provides the mean time interval between successive handovers during a call.

Fault finding.
Basis Cell.
Type Time interval (in seconds).
Raw Statistics BUSY_TCH_MEAN

BUSY_TCH_HR_MEAN
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].
INCOMING_HO_VOL
This statistic is the number of successful incoming internal and external
handovers, at the cell or BSS level.

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].

OUTGOING_HO_VOL
This statistic tracks the number of successful outgoing handovers.

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics OUT_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].

OUT_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].


MEAN_TIME_BETWEEN_HOs
MEAN_TIME_BETWEEN_HOs =
(BUSY_TCH_MEAN+BUSY_TCH_HR_MEAN * INTERVAL_SUM)
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]+
INTRA_CELL_HO[INTRA_CELL_HO_SUC]) * 1000
INCOMING_HO_VOLUME
Cell Level
INCOMING_VOLUME = (IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC] )
BSS Level
INCOMING_VOLUME = (IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC])
OUTGOING_HO_VOLUME
Cell Level
OUTGOING_HO_VOLUME = (OUT_INTER_BSS_HO_[OUT_INTER_BSS_HO_SUC]+
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])
BSS Level
OUTGOING_HO_VOLUME = OUT_INTER_BSS_HO_SUC


INTERNAL_SUCCESS
This statistic is the percentage of successful internal handovers.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].
INTRA_CELL_HO_FAIL_LOST_MS
This statistic tracks the percentage of intra-cell assignment commands that are sent over
the air interface which result in the MS failing to access the target channel and failing to
recover to the original channel; that is, the call drops.

Fault finding.
Basis Cell, BSS or Network.
Type Percentage.
Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

INTRA_CELL_HO[INTRA_CELL_HO_LOST_MS]


INTERNAL_SUCCESS
INTERNAL_SUCCESS =
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] +
* 100%
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] )
INTRA_CELL_HO_FAIL_LOST_MS
INTRA_CELL_HO_FAIL_LOST_MS = x 100%
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]


INTRA_CELL_HO_FAIL_RECOVERED
This statistic tracks the percentage of intra-cell assignment commands that are sent
over the air interface which result in the MS failing to access the target channel and
subsequently successfully recovering to the original channel.

Fault finding.
Type Percentage.

INTRA_CELL_HO[INTRA_CELL_HO_RETURN]
INTRA_CELL_HO_SUCCESS_RATE
This statistic tracks the percentage of intra-cell assignment commands that are sent over the
air interface which result in the MS successfully accessing the target channel.

Fault finding.
Type Percentage.

INTRA_CELL_HO[INTRA_CELL_HO_SUC]


INTRA_CELL_HO_FAIL_RECOVERED
INTRA_CELL_HO_FAIL_RECOVERED = x 100%
INTRA_CELL_HO_SUCCESS_RATE
INTRA_CELL_HO[INTRA_CELL_HO_SUC]
INTRA_CELL_HO__SUCCESS_RATE x 100%


INTERNAL_LOST
This statistic is the percentage of attempted internal handovers that result in a lost MS.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS]
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]
INTERNAL_RECOVERED
This statistic is the percentage of attempted internal handovers that fail with the MS
subsequently recovering to the source cell.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN]

HANDOVER PERCENTAGE BY CAUSE VALUE

For each handover cause value, a ratio is calculated between this handover to the total number
of handovers in a cell. This ration is expressed as a percentage. The handover cause values
are listed below and one example is shown in the diagram opposite.
HO_CAUSE_ULQUAL HO_CAUSE_DLQUAL
HO_CAUSE_ULLEVEL HO_CAUSE_DLLEVEL
HO_CAUSE_ULINTERF HO_CAUSE_DLINTERF
HO_CAUSE_DISTANCE HO_CAUSE_PWRBGT
HO_CAUSE_CONGESTION HO_CAUSE_ADJ_CHAN_INTERF
HO_CAUSE_BAND_HO HO_CAUSE_BAND_REASSIGN
Usage Quality of service. Fault finding

Basis Cell
Type Percentage
Raw Statistics OUT_HO_CAUSE_ATMPT


INTERNAL_LOST
INTERNAL_LOST (%) =
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] )
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] ) *100%
INTERNAL_RECOVERED
INTERNAL_RECOVERED =
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] +
INTRA_CELL_HO[INTRA_CELL_HO_RETURN] )
*100%
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] )
HANDOVER PERCENTAGE BY CAUSE VALUE
OUT_HO_CAUSE_ATMPT [UPQUAL]
HO_CAUSE_UPQUAL = *100%
OUT_HO_CAUSE_ATMPT


OUT_INTER_BSS_HO_SUCCESS_RATE
This statistic is the percentage of successful external handovers.

Fault finding.
Basis BSS
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].
OUT_INTER_BSS_HO_FAIL_LOST_MS
This statistic is the percentage of attempted external handovers that result in a lost MS.

Fault finding.
Basis BSS
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN].


OUT_INTER_BSS_HO_SUCCESS_RATE
OUT_INTER_BSS_HO_SUCCESS_RATE =
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC])
*100%
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] )
OUT_INTER_BSS_HO_FAIL_LOST_MS
OUT_INTER_BSS_HO_FAIL_LOST_MS =
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] -
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] -
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] )
*100%
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT])
OUT_INTER_BSS_HO_FAIL_RECOVERED
This statistic is the percentage of attempted external handovers that fail with the
MS subsequently recovering to the source cell.

Fault finding.
Basis BSS
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN].

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT.


MSC_PAGING
This statistic is the total number of Paging messages received from the MSC for each cell in a BSS.
Usage: Network_Planning
Radio Resource Allocation
Basis Cell
Type Counter
Raw Statistics PAGING_REQ_FROM_MSC.
AIR_INTERFACE_PAGING
This statistic is the total number of Paging Request messages sent on the air
interface for each cell in a BSS.
Usage: Network planning

Radio resource allocation.
Basis Cell.
Type Counter.
Raw Statistics ACCESS_PER_PCH[ACCESS_PER_PCH_PS_CS.

ACCESS_PER_PCH[ACCESS_PER_PCH_CS
ACCESS_PER_PCH[ACCESS_PER_PCH_PS


OUT_INTER_BSS_HO_FAIL_RECOVERED
OUT_INTER_BSS_HO_FAIL_RECOVERED =
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])
x 100%
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT])
MSC_PAGING
MSC_PAGING = PAGE_REQ_FROM_MSC
AIR_INTERFACE_PAGING
AIR_INTERFACE_PAGING = ACCESS_PER_PCH [ACCESS_PER_PS_CS] +

ACCESS_PER_PCH [ACCESS_PER_CS] +
ACCESS_PER_PCH [ACCESS_PER_PS]


PERCENTAGE_INTER_BSS_HO
This statistic calculates the percentage of all inter–BSS handover attempts in
comparison to all handover attempts.
Usage Quality of service. Fault finding.

Basis BSS.
Type Percentage.
Raw Stats OUT_INTER_BSS_HO_ATMPT INTRA_CELL_HO (The value
used in this formula is the sum of bins 1 to 4 of this counter array
statistic). OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]
PERCENTAGE_INTRA_BSS_HO
This statistic calculates the percentage of all intra–BSS handover attempts in

Basis BSS.
Type Percentage.
Raw Stats OUT_INTRA_BSS_HO_ATMPT INTRA_CELL_HO (The value
used in this formula is the sum of bins 1 to 4 of this counter array
statistic). OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]
PERCENTAGE_INTRA_CELL_HO
This statistic calculates the percentage of all intra–cell handover attempts in

Basis BSS.
Type Percentage.
Raw Stats INTRA_CELL_HO (The value used in this formula is
the sum of bins 1 to 4 of this counter array statistic).


PERCENTAGE HANDOVER
PERCENTAGE_INTER_BSS_HO
PERCENTAGE_INTER_BSS_HO = OUT_INTER_BSS_HO_ATMPT
*100%
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR] +
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +
PERCENTAGE_INTRA_BSS_HO
PERCENTAGE_INTRA_BSS_HO = OUT_INTRA_BSS_HO_ATMPT
*100%
PERCENTAGE_INTRA_CELL_HO
PERCENTAGE_INTRA_CELL_HO = OUT_INTRA_CELL_HO_ATMPT
*100%


PAGING_OVERFLOW_RATE
This statistic tracks the percentage of pages which are dropped from the BSS
paging queue due to paging queue overflow.

Fault finding.
Type Percentage.
Raw Statistics PAGING_REQUESTS [PAGING_REQS_CS]

PAGING_REQUESTS [PAGING_REQS_PS]
PCH_PAGE_Q_DISCARD [PS]
PCH_PAGE_Q_DISCARD [CS]
PAGING_RESPONSE
This statistic tracks the volume of MSs which respond to a page through a successful SDCCH access.

Fault finding.
Type Counter.
Raw Statistics OK_ACC_PROC[PAGE_RESPONSE].
PAGING_SUCCESS_RATE
This statistic tracks the percentage of pages which receive a successful response from
an MS. This statistic is measured on a location area basis.

Fault finding.
Basis Location area.
Type Percentage.
Raw Statistics OK_ACC_PROC[PAGE_RESPONSE]

PAGING_REQUEST [CS]


PAGING_OVERFLOW_RATE
Circuit switched PCH_PAGE_Q_DISCARD [CS] x 100%

PAGING_OVERFLOW_RATE =
PAGING_REQUESTS[PAGING_REQS_CS]
Packet switched PCH_PAGE_Q_DISCARD [PS] x 100%

PAGING_OVERFLOW_RATE =
PAGING_REQUESTS[PAGING_REQS_CS]
PAGING_RESPONSE
PAGING_RESPONSE =
OK_ACC_PROC[PAGE_RESPONSE]
PAGING_SUCCESS_RATE
SUM(OK_ACC_PROC[PAGE_RESPONSE]
PAGING_SUCCESS_RATE = x 100%
PAGE_REQUESTS[CS]
NOTE: OK_ACC_PROC[PAGE_RESPONSE] is summed across all cells in the location area and the
statistic also assumes paging is configured on a location area basis, PAGE_REQ_FROM_MSC
is the maximum value occuring on any cell within the LAC.


PAGING_COMPRESSION_RATE
This statistic provides a measure of page packing on the air interface.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ACCESS_PER_PCH. The value used here is the sum of bins 0 to 2
of this CA Stat
PAGGING_REQUESTS. The value used here is the sum of bins 0 to 2
of this CA Stat
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS
This statistic provides the percentage of air interface call set–up assignment commands that
are sent to over the air interface which result in the MS failing to access the target channel
and failing to recover to the original channel. This statistic includes the impact of successful
second assignments and intra–cell handover assignment attempts.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS

MA_COMPLETE_TO_MSC.
MA_FAIL_FROM_MS
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_HR]
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_HR]
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_FR]
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_FR]
INTRA_CELL_HO_SUC INTRA_CELL_HO_RETURN
SECOND_ASSIGN_ATMPT


PAGING_COMPRESSION_RATE
ACCESS_PER_PCH [ACCESS_PER_PCH_PS_CS] +
ACCESS_PER_PCH [ACCESS_PER_PCH_CS] +
ACCESS_PER_PCH [ACCESS_PER_PCH_PS] +
* 100%
PAGING_COMPRESSION_RATE =
PAGING_REQESTS [PAGING_REQS_CS] +
PAGING_REQESTS [PAGING_REQS_PS]
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS
MA_CMD_TO_MS _ [
[ MA_COMPLETE_TO_MS _
MA_FAIL_FROM_MS
_
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_HR]+ [
[ INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_HR]+
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_FR]+
INTRA_CELL_HO_SUC - INTRA_CELL_HO_RETURN * 100
_
CALL_SETUP_RF
_ASSIGNMENT_FAIL = _
_RATE_LOST_MS MA_CMD_TO_MS
[
[
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_HR]+
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_HR]+ _
SECOND_ASSIGN_ATMPT


CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS
This statistic provides the percentage of air interface call set–up assignment commands that
are sent over the air interface which result in the MS failing to access the target channel and
subsequently successfully recovering to the original channel. This statistic includes the impact
of successful second assignments and intra–cell handover assignment attempts.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS.

MA_FAIL_FROM_MS
SECOND_ASSIGN_ATMPT


CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS
_ [
CALL_SETUP_RF
_ASSIGN_FAIL = [ MA_FAIL_FROM MS
INTRA_CELL_HO_RETURN _
SECOND_ASSIGN_ATMPT
* 100
_RATE_RECOVERED_MS
MA_CMD_TO_MS _
[
[
SECOND_ASSIGN_ATMPT


CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
This statistic provides the percentage of air interface call set–up assignment commands that are
successfully sent over the air interface which result in the MS accessing the target channel. This statistic
includes the impact of successful second assignments and intra–cell handover assignment attempts.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS.

MA_FAIL_FROM_MS
SECOND_ASSIGN_ATMPT


CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
_ [
CALL_SETUP_RF
=
[ MA_COMPLETE_TO_MS
INTRA_CELL_HO_SUC
_ASSIGN_SUCCESS
* 100
_RATE
MA_CMD_TO_MS _
[
[
SECOND_ASSIGN_ATMPT


OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS
This statistic is the percentage of attempted handovers that result in lost connections,
but does not include intra-cell handovers.

Fault finding.
Basis Cell.
Type Percentage.

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOST_MS].


)
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOST_MS]+
( OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] -
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] -
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN]
( OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]+
( OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]


OUT_INTER_CELL_HO_FAIL_RECOVER
This statistic is the percentage of attempted handovers that fail with the MS recovering to the source cell.

Fault finding.
Basis Cell.
Type Percentage.

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_FAIL].
This statistic tracks the percentage of inter-cell handover commands that result in the MS successfully
accessing the target channel. This statistic includes intra-BSS and inter-BSS inter-cell handovers.

Fault finding.
Basis Cell.
Type Percentage.

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC]..
ASSIGNMENT_SUCCESS_RATE
This statistic tracks the success rate of the A-interface assignment procedure, which will
automatically also include the impact of the air interface assignment procedure.

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics MA_REQ_FROM_MSC

MA_COMPLETE_TO_MSC


OUT_INTER_CELL_HO_FAIL_RECOVER
OUT_INTER_CELL_HO_FAIL_RECOVER =
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] +
*100
SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] )
OUT_INTER_CELL_HO_SUCCESS_RATE =
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]+
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])
*100
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]+
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT])
ASSIGNMENT_SUCCESS_RATE
ASSIGNMENT_SUCCESS_RATE =
MA_COMPLETE_TO_MSC
*100
MA_REQ_FROM_MSC


TCH_RF_LOSS_RATE
This statistic is the percentage of allocated calls on TCHs that are lost due to
radio connection failure on the TCH.

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION

TOTAL_CALLS.
RF_LOSSES_TCH.
IN_INTER_BSS[IN_INTER_HO_SUC]
IN_INTER_BSS[IN_INTRA_BSS_SUC.


TCH_RF_LOSS_RATE
Cell Level
RF_LOSSES_TCH
TCH_RF_LOSS_RATE = *100
TOTAL_CALLS + IN_INTRA_BSS_HO_SUC
+IN_INTER_BSS_HO_SUC
BSS Level
RF_LOSSES_TCH
TOTAL_CALLS + IN_INTER_BSS_HO_SUC
+ASSIGNMENT_REDIRECTION
Network Level
RF_LOSSES_TCH
TOTAL_CALLS+


The MEAN_TIME_BETWEEN_DROPS statistic tracks the mean time interval between
dropped calls due to the loss of the radio link.

Fault finding.
Basis Cell.
Type Time Interval.
Raw Statistics BUSY_TCH_MEAN.

BUSY_TCH_HR_MEAN.
RF_LOSSES_TCH_MEAN.
RF_LOSSES_TCH_HR_MEAN.
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].


(BUSY_TCH_MEAN + BUSY_TCH_HR_MEAN)
* INTERVAL_SUM
MEAN_TIME_BETWEEN_DROPS=
(RF_LOSSES_TCH + RF_LOSSES_TCH_HR +
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED])


SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF
This stat tracks the percentage of successful call setups initiated in a cell which cause an
existing call to be subject to a congestion relief handover attempt.
Usage: Service retainability.

Fault finding.
Basis Cell.
Type Percentage
Raw Statistics CONGEST_EXIST_HO_ATMPT

TOTAL_CALLS
SPILL_OVER_FACTOR_DIRECTED_RETRY
This stat tracks the percentage of successful call setups initiated in a cell which completed TCH
assignment in a neighbouring cell via directed retry or a handover during assignment.

Fault finding.
Basis Cell.
Type Percentage

TOTAL_CALLS
SPILL_OVER_FACTOR_MULTIBAND
This stat tracks the percentage of successful call setups initiated in a cell which completed
TCH assignment in a neighbouring cell via a multiband handover.

Fault finding.
Basis Cell.
Type Percentage

TOTAL_CALLS


SPILL OVER FACTOR
CALL_SET_UP_BLOCKING_RATE CONGEST_EXIST_HO_ATMPT
SPILL_OVER_FACTOR_ATTEMPTS = * 100
_AT CONGESTION_RELIEF = TOTAL_CALLS
MA_REQ_FROM_MSC
+ ASSIGNMENT_
REDIRECTION
ASSIGNMENT_REDIRECTION [DIRECTED_RETRY] +
SPILL_OVER_FACTOR_ ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENTS]
CALL_SET_UP_BLOCKING_RATE
DIRECTED_RETRY = = * 100
MA_REQ_FROM_MSC
TOTAL_CALLS + ASSIGNMENT_
REDIRECTION
SPILL_OVER_FACTOR_ATTEMPTS
CALL_SET_UP_BLOCKING_RATE ASSIGNMENT_REDIRECTION
= [MULTIBAND]
_AT CONGESTION_RELIEF = * 100
MA_REQ_FROM_MSC
TOTAL_CALLS + ASSIGNMENT_
REDIRECTION


Call Model Statistics Version 1 Rev 4
Chapter 9

Version 1 Rev 4 Call Model Statistics

Call Model Statistics Version 1 Rev 4

Objectives
• Understand the call model statistics

Version 1 Rev 4 Introduction to call model statistics
Introduction to call model statistics

Description
This chapter describes the derivation of call model parameter values from the GSM
network statistics collected at the OMC-R.
All the statistics used for determining the call model parameters must be collected during busy
hours and averaged over a reasonable period of time (3 months or more).
The call model parameters should be averaged over the entire network or at the BSC level for equipment
dimensioning purposes. This gives more scope of averaging out the load from the network entities.
The following are call model statistics:
• CALL_DURATION (T).
• CALL_SETUP_BLOCKING_RATE.
• HANDOVERS_PER_CALL (H).
• IMSI_DETACHES_TO_CALLS (Id).
• INTRA_BSS_HO_TO_ALL_HO (i).
• LOCATION_UPDATE_FACTOR (L).
• LOCATION_UPDATES_TO_CALLS (l).
• PAGES_PER_CALL (Ppc).
• PAGES_PER_SECOND.
• PAGING_RATE (P).
• SMS_TO_CALL_RATIO (S).

Introduction to call model statistics Version 1 Rev 4

Introduction to Call Model Statistics
Raw statistics used to derive call model statistics
Raw statistics must be collected during busy hour

and collected over reasonable period
Call model statistics should be averaged over entire

network or for equipment dimensioning purposes
Refer to Planning Guide W21 or SYS04 for

detailed explanation


CALL_DURATION (T)
This statistic provides the average call duration.
Units: Seconds (s)

Optimisation
Basis Cell.
Raw statistics BUSY_TCH_MEAN
TOTAL_CALLS
CALL_SETUP_BLOCKING_RATE
This statistic provides the percentage of attempts to allocate a TCH call setup that were blocked.
Units: Percentage (%)

Optimisation
Basis Cell.
Raw statistics MA_CMD_TO_MS_BLKD
MA_REQ_FROM_MSC


CALL_DURATION
T= SUM(BUSY_TCH_MEAN)
SUM(BUSY_TCH_MEAN) ** INTERVAL_SUM
I NTERVAL_SUM* 3600
* 3600
SUM(TOTAL_CALLS ++ASSIGNMENT_REDIRECTION)
SUM(TOTAL_CALLS ASSIGNMENT_REDIRECTION)
Assuming statistical interval = 1 hour
CALL_SETUP_BLOCKING_RATE
CALL_SET_UP_BLOCKING_RATE = MA_CMD_TO_MS_BLKD * 100

MA_REQ_FROM_MSC


HANDOVERS_PER_CALL (H)
This statistic provides the number of Handovers per call where the handovers
may be inter-BSS, intra-BSS or intra-cell.

Optimisation
Basis Cell.
Raw statistics OUT_INTER_BSS_REQ_TO_MSC
INTRA_CELL_HO_ATMPT
TOTAL_CALLS
INTRA_BSS_HO_TO_ALL_HO (i)
This statistic provides the ratio of intra-BSS handovers to all handovers.

Optimisation
Basis Cell.
Raw statistics OUT_INTER_BSS_REQ_TO_MSC
INTRA_CELL_HO_ATMPT


STATS
HANDOVERS_PER_CALL (H)
H= SUM(OUT_INTER_BSS_REQ_TO_MSC + OUT_INTRA_BSS_HO_ATMPT
+ INTRA_CELL_HO_ATMPT)
SUM(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)
INTRA_BSS_HO_TO_ALL_HO(i)
i= SUM(OUT_INTRA_BSS_HO_ATMPT + INTRA_CELL_HO_ATMPT
SUM(OUT_INTER_BSS_REQ_TO_MSC + OUT_INTRA_BSS_HO_ATMPT
+ INTRA_CELL_HO_ATMPT)


STATS
LOCATION_UPDATES_TO_CALLS (I)
Description
This statistic provides the ratio of location updates to calls.

Optimisation
Basis Cell.
Raw statistics OK_ACC_PROC [LOCATION UPDATE]
TOTAL_CALLS
IMSI_DETACHES_TO_CALL (Id)
This statistic provides the ratio of IMSI detaches per call.

Optimisation
Basis Cell.
Raw statistics OK_ACC_PROC [IMSI_DETACH]
TOTAL_CALLS


STATS
LOCATION_UPDATES_TO_CALLS(l)
I= SUM(OK_ACC_PROC [LOCATION UPDATE]

IMSI_DETACHED_TO_CALLS(Id)
Id = SUM(OK_ACC_PROC [IMSI_DETACH]

Version 1 Rev 4 LOCATION_UPDATE_FACTOR (L)
LOCATION_UPDATE_FACTOR (L)
Description
This statistic is calculated using the ratio of location updates per call (l) and the ratio of
IMSI detaches per call (Id). For networks with IMSI detach disabled, the location update
factor equals the ratio of location updates per call (l).
IMSI detach types determine the way the MSC clears the connection with the BSS after receiving the
IMSI detach. When using IMSI detach type 1, the MSC clears the SCCP connection, a clearing
procedure that involves only one uplink (average size of 42 bytes) and one downlink message (average
size of 30 bytes). When using IMSI detach type 2, the MSC sends the CLEAR COMMAND and the
BSS sends CLEAR COMPLETE, etc., which involves three uplink (average size of 26 bytes) and three
downlink messages (average size of 30 bytes). A location update procedure itself takes five downlink
messages (average size of 30 bytes) and six uplink messages (average size of 26 bytes).
Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number
of messages as a location update and a IMSI detach (type 2) takes 6/11 (approximately
0.5) of the messages of a location update.
Formula
If IMSI detach is enabled, then depending on whether short message sequence (type 1)
or long message sequence (type 2) is used, L is calculated as:
L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled i.e. Id=0 )
L = LOCATION_UPDATES_TO_CALLS + 0.2* IMSI_DETACHES_TO_CALLS (type 1)
L = LOCATION_UPDATES_TO_CALLS + 0.5* IMSI_DETACHES_TO_CALLS (type 2)

Optimisation
Basis Cell.
Raw statistics LOCATION_UPDATES_TO_CALLS
IMSI_DETACHES_TO_CALLS

LOCATION_UPDATE_FACTOR (L) Version 1 Rev 4
L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled i.e. Id = 0)
L = LOCATION_UPDATES_TO_CALLS + 0.2 * IMSI_DETACHES_TO_CALLS (type 1)
L = LOCATION_UPDATES_TO_CALLS + 0.5 * IMSI_DETACHES_TO_CALLS (type 2)

Version 1 Rev 4 Pages
Pages
PAGES_PER_CALL (Ppc)
Description
This statistic provides the number of pages per call.

Optimisation
Basis Cell.
Raw statistics PAGE_REQ_FROM_MSC
TOTAL_CALLS
PAGES_PER_SECOND
Description
This statistic provides the number of pages per second.

Optimisation
Basis Cell.
PAGING_RATE (P)
The paging rate is the summation of the paging messages sent to each location
area averaged over the interval period.

Optimisation
Basis Cell.

Pages Version 1 Rev 4
Pages
Pps
PAGES_PER_SECOND
PAGES_PER_SECOND = PAGE_REQ_FROM_MSC
INTERVAL_SUM * 3600
PAGES_PER_CALL (Ppc)
PPC = SUM(PAGE_REQ_FROM_MSC)
PAGING_RATE
SUM(PAGE_REQ_FROM_MSC)
P=
stat_interval_in_seconds
Note: SUM in this case refers to the location areas. The maximum
PAGE_REQ_FROM_MSC value should be used for each location area

Pages
SMS_TO_CALL_RATIO (S)
Description
This statistic provides the ratio of SMSs to calls.

Optimisation
Basis Cell.
Raw statistics SMS_INIT_ON_SDCCH
SMS_INIT_ON_TCH
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV_REQ_EMERG
PAGE_RESPONSE

Pages Version 1 Rev 4
Pages
SMS_TO_CALL_RATIO (S)
S= (SMS_INIT_ON_SDCCH + SMS_INIT_ON_TCH)
S=
(CM_SERV_REQ_CALL + CM_SERV_REQ_SMS +
CM_SERV_REQ_EMERG + PAGE_RESPONSE) – (SMS_INIT_ON_SDCCH)


Adaptive Multi-Rate Version 1 Rev 4
Chapter 10
Adaptive Multi-Rate

Version 1 Rev 4 Adaptive Multi-Rate

Adaptive Multi-Rate Version 1 Rev 4
Adaptive Multi-Rate
Objectives
• Describe the Adaptive Multi-Rate Feature.
• Describe the AMR statistics.

Version 1 Rev 4 Adaptive Multi-Rate (AMR)
Adaptive Multi-Rate (AMR)

Adaptive Multi-Rate (AMR) is introduced in GSR7 and provides two modes of working AMR
full-rate channel mode (AMR FR) and AMR half-rate channel mode (AMR HR).
AMR Full - Rate Channel Mode

This mode of working provides higher speech quality in areas of poor RF conditions.
Full Rate Link Adaptation

AMR FR link adaptation works in conjunction with the rest of the AMR feature set, namely AMR,
Call downgrade on CIC capability mismatch and Enhanced GDP provisioning. It provides improved
speech quality in poor RF environments by adapting the speech rates and level of error correction
on a call. Speech quality is improved by reducing the speech rate and increasing the level of
error correction in poor RF environment. The speech rate used is determined by the codec
mode used. The Active Codec Set (ACS) refers to the set of up to 4 AMR codec modes that
can be utilised for any given voice call in the uplink and downlink direction.
AMR Half - Rate Channel Mode

This mode of working allows two AMR calls to be placed on a single air interface timeslot. This gives an
increase in cell capacity with no additional hardware. However extra backhaul is required between
BSC and BTS due to there being no 8kbps switching in release GSR7. This means that AMR
half-rate speech data has to be carried in 16kbps TRAU format between BSC and BTS. Given that
potentially 16 AMR half-rate calls can be supported on an AMR half-rate carrier, an AMR half-rate
RTF must have four associated E1 timeslots provisioned between BSC and BTS.
Due to reduced bandwidth, an AMR half-rate call will in general have a lower QoS than a full-rate
call. For this reason the user will be able to specify a congestion level that has to be exceeded in
an AMR half-rate cell before new calls will be assigned to a half-rate channel. In addition, when
the received bit error rate (Rxqual) indicates that a half rate channel is suffering interference and
that the speech quality of the call is therefore impaired, an intra-cell handover back to full-rate
(or to another half-rate channel) is supported to maintain quality of service.
There is also a lower QoS provided by AMR half-rate calls.
Half Rate Link Adaptation

AMR HR link adaptation operates in a similar way to AMR FR link adaptation. The differences
are the bit rates of the HR codec modes supported, different initial HR codec mode and different
associated uplink and downlink codec mode adaptation thresholds and hystersis values.
In total there are 8 Active Codec Set values.
0 - 12.20 kbps
1 - 10.20 kbps
2 - 7.95 kbps
3 - 7.40 kbps
4 - 6.70 kbps
5 - 5.90 kbps
6 - 5.15 kbps
7 - 4.75 kbps
The BSS supports:-
12.2, 10.2, 7.4, 6.7 and 5.15 kbps for a full rate channel.
7.95, 7.4, 6.7, 5.9 and 5.15 kbps for a half rate channel.

Adaptive Multi-Rate (AMR) Version 1 Rev 4
Adaptive Multi-Rate (AMR)
Dependant on:
- Enhanced GDP Provisioning
- Call downgrade on CIC
capability mismatch
Up to 16 AMR half rate calls
Up to 8 AMR full rate calls

MSC RXCDR BSC BTS Or a combination of the two.
Up to four codec
modes can be
included in FR and
HR Active Codec
Set
Which Codec Mode

0 used depends on
RF conditions
For half rate rtf - two E1 timeslots required

Version 1 Rev 4 AMR Full - Rate Link Adaptation
AMR Full - Rate Link Adaptation

Full Rate AMR Link Adaptation provides the mechanism by which the BSS adapts between speech
codec modes in an AMR codec on the uplink and downlink of an AMR FR call, to provide the most
suitable level of error correction for the RF environment. Uplink and downlink codec modes are
considered separately and can be adapted separately. The AMR feature provides a set of Full Rate
codec modes. With Full Rate Link Adaptation, up to four of these codec modes could be placed in the
per cell Full Rate Active Codec Set. It is over this Active Codec Set that the call is adapted according to
the quality of the link between the mobile and the BSS. The Full Rate codec modes supported are:
AFS 12.2 kbps
AFS 10.2 kbps
AFS 7.4 kbps
AFS 6.7 kbps
AFS 5.15 kbps
The higher the bit rate of the codec mode indicated the higher the speech rate and the lower the
error correction rate. Up to 4 of these codec modes can be included in the FR ACS.
For each pair of codec of modes there is an associated threshold and hysteresis value. The associated
threshold is used as the lower decision threshold for switching the codec mode to a lower mode with a
lower speech rate. The sum of the associated threshold and associated hysteresis is used as the upper
decision threshold for switching the codec mode to a less robust mode with a higher speech rate. The
threshold and hysteresis are expressed in terms of normalized Carrier to Interference (C/I) values.
CODEC_MODE_1 Represents the lowest codec mode (lowest

speech bit rate, highest error correction bit rate)
of the FR ACS
CODEC_MODE_2 Represents the second lowest codec mode, if the
ACS contains more than one codec mode.
CODEC_MODE_3 Represents the third lowest codec mode, if the
ACS contains more than two codec modes.
CODEC_MODE_4 Represents the highest codec mode (highest
speech bit rate, lowest error correction bit rate) of
the ACS if the ACS contains four codec modes.
The FR ACS, Full Rate Initial Codec mode and the associated codec mode adaptation
threshold and hysteresis values to be used are communicated to the mobile and the
channel coder on call initialization and handover.
FR AMR codecs provide different levels of error correction and allow different channel bit error rates
for acceptable quality of service. As an example, at the lowest codec mode (low speech rate, high
error correction) a larger BER may be acceptable as more of the errors will be corrected, where as
in a higher codec mode a larger BER would be unacceptable as less errors will be corrected. The
differences in AMR channel characteristics prompt the introduction for a new set of HDPC RXQUAL
algorithm thresholds. The new HDPC parameters are specific to AMR FR calls and utilize the existing
GSM Handover and Power Control algorithms. These new HDPC parameters allow an AMR FR
capable cell to be tailored for AMR FR capable mobiles, to increase the range of cells and improve
service in poor coverage areas, minimize interference levels to improve speech quality, increase
capacity (through tighter-reuse of frequencies) and increase service quality by lowering the number
of handovers for AMR FR. This release of Full Rate Link Adaptation is tailored towards maximizing
speech quality and hence all defaulted values supplied in the software are geared to that goal.

AMR Full - Rate Link Adaptation Version 1 Rev 4
AMR Full - Rate Link Adaptation
C/I
CODEC_MODE_4
Up to 4 can be
chosen
THR3 + HYST3
THR3
Available Full Rate
Codec Modes CODEC_MODE_3
AFS 12.2 kbps
AFS 10.2 kbps THR2 + HYST2
AFS 7.4 kbps THR2
AFS 6.7 kbps

CODEC_MODE_2
AFS 5.15 kbps
THR1 + HYST1
THR1
CODEC_MODE_1

Version 1 Rev 4 AMR_FR_DL_CODEC_MODE_USAGE
AMR_FR_DL_CODEC_MODE_USAGE
Description:
The AMR_FR_DL_CODEC_MODE_USAGE statistics keeps a count of each AMR full-rate
codec mode used on the downlink of AMR full-rate calls on a per-cell basis.
The bins are:
Bin 0 AMR full-rate DL codec mode usage of AFS 12.2kbps
This counter statistic is pegged each time that a specific codec mode is used
on the downlink of full-rate AMR calls.

AMR_FR_DL_CODEC_MODE_USAGE Version 1 Rev 4
AMR_FR_DL_CODEC_MODE_USAGE
Bin 0 AMR FR DL Codec Mode Usage of AFS 12.2kbps


Version 1 Rev 4 AMR_FR_UL_CODEC_MODE_USAGE
AMR_FR_UL_CODEC_MODE_USAGE
Description:
The AMR_FR_UL_CODEC_MODE_USAGE statistics keeps a count of each AMR full-rate
codec mode used on the uplink of AMR full-rate calls on a per-cell basis.
The bins are:
Bin 0 AMR full-rate UL codec mode usage of AFS 12.2kbps
This counter statistic is pegged each time that a specific codec mode is used
on the uplink of full-rate AMR calls.

AMR_FR_UL_CODEC_MODE_USAGE Version 1 Rev 4
Bin 0 AMR FR UL Codec Mode Usage of AFS 12.2kbps


Version 1 Rev 4 AMR_FR_DL_ADAPTATION
AMR_FR_DL_ADAPTATION
Description:
The AMR_FR_DL_ADAPTATION counter array statistic statistic keeps count of the number of times
the codec mode is adapted on the downlink of full-rate AMR calls on a per-cell basis.
There are up to four codec modes in the ACS and the format of this statistic allows for this.
The codecs are referenced sequentially from the lowest speech coding rate to the highest.
The lowest speech coding rate is called the 1st codec. If there are less than four codecs in
the ACS, the higher bit rates are not valid and contains value zero.
The bins are:
Bin 0 AMR full-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
Bin 1 AMR full-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
Bin 2 AMR full-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
Bin 3 AMR full-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
Bin 4 AMR full-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
Bin 5 AMR full-rate DL codec mode usage adaptation from 4th to 3rd codec mode.

AMR_FR_DL_ADAPTATION Version 1 Rev 4
AMR_FR_DL_ADAPTATION

Version 1 Rev 4 AMR_FR_UL_ADAPTATION
AMR_FR_UL_ADAPTATION
Description:
The AMR_FR_UL_ADAPTATION counter array statistic statistic keeps count of the number of times
the codec mode is adapted on the uplink of full-rate AMR calls on a per-cell basis.
The bins are:
Bin 0 AMR full-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
Bin 1 AMR full-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
Bin 2 AMR full-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
Bin 3 AMR full-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
Bin 4 AMR full-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
Bin 5 AMR full-rate UL codec mode usage adaptation from 4th to 3rd codec mode.

AMR_FR_UL_ADAPTATION Version 1 Rev 4
AMR_FR_UL_ADAPTATION

Version 1 Rev 4 AMR Half - Rate Link Adaptation
AMR Half - Rate Link Adaptation

Half Rate AMR Link Adaptation provides similar functionality to Full Rate AMR Link Adaptation but
for the Half Rate AMR channel. In Half Rate AMR Link Adaptation there is a different Half Rate
Active Codec Set. This AHS can contain up to four of the Half Rate AMR codec modes that are
supported. The Half Rate codec modes supported are AHS 7.95 kbps, 7.4 kbps, 6.7 kbps, 5.9 kbps
and 5.15 kbps. There is also a different Half Rate Initial Codec Mode and different associated
uplink and downlink codec mode adaptation thresholds and hysteresis values for Half Rate AMR
calls. The existing GSM Handover and Power Control algorithms are still used for the Half Rate
AMR channel, but similar to Full Rate Link Adaptation a new set of Handover and Power Control
thresholds are introduced. The new Half Rate AMR HDPC RXQUAL thresholds are different to the
Full Rate AMR HDPC thresholds because the Half Rate channel will display different characteristics
to a Full Rate AMR channel. For these reasons the customer may wish to configure the Handover
and Power Control algorithms in a different manner to cater for the Half Rate AMR channel. The MS
Monitor introduced in Full Rate AMR Link Adaptation also applies to Half Rate AMR calls.
CODEC_MODE_1 Represents the lowest codec mode (lowest

speech bit rate, highest error correction bit rate)
of the HR ACS
CODEC_MODE_2 Represents the second lowest codec mode, if the
HR ACS contains more than one codec mode.
CODEC_MODE_3 Represents the third lowest codec mode, if the
HR ACS contains more than two codec modes.
CODEC_MODE_4 Represents the highest codec mode (highest
speech bit rate, lowest error correction bit rate)
of the HR ACS if the ACS contains four codec
modes.

AMR Half - Rate Link Adaptation Version 1 Rev 4
AMR Half - Rate Link Adaptation
C/I
Up to 4 can be
chosen CODEC_MODE_4
THR3 + HYST3
THR3
Available Half Rate
Codec Modes CODEC_MODE_3
AFS 7.95 kbps
AFS 7.4 kbps THR2 + HYST2
AFS 6.7 kbps THR2
AFS 5.9 kbps

CODEC_MODE_2
AFS 5.15 kbps
THR1 + HYST1
THR1
CODEC_MODE_1

Version 1 Rev 4 AMR_HR_DL_CODEC_MODE_USAGE
AMR_HR_DL_CODEC_MODE_USAGE
Description:
The AMR_HR_DL_CODEC_MODE_USAGE statistics keeps a count of each AMR half-rate codec
mode used on the downlink of AMR half-rate calls on a per-cell basis.
The bins are:
Bin 0 AMR half-rate DL codec mode usage of AFS 7.95kbps
This counter statistics is pegged each time that a specific codec mode is used
on the downlink of half-rate AMR calls.

AMR_HR_DL_CODEC_MODE_USAGE Version 1 Rev 4
AMR_HR_DL_CODEC_MODE_USAGE
Bin 0 AMR FR DL Codec Mode Usage of AFS 7.95 kbps


Version 1 Rev 4 AMR_HR_UL_CODEC_MODE_USAGE
AMR_HR_UL_CODEC_MODE_USAGE
Description:
The AMR_HR_UL_CODEC_MODE_USAGE statistics keeps a count of each AMR half-rate
codec mode used on the uplink of AMR full-rate calls on a per-cell basis.
The bins are:
Bin 0 AMR half-rate UL codec mode usage of AFS 7.95kbps
This counter statistics is pegged each time that a specific codec mode is used
on the uplink of half-rate AMR calls.

AMR_HR_UL_CODEC_MODE_USAGE Version 1 Rev 4
AMR_HR_UL_CODEC_MODE_USAGE
Bin 0 AMR FR UL Codec Mode Usage of AFS 7.95 kbps


Version 1 Rev 4 AMR_HR_DL_ADAPTATION
AMR_HR_DL_ADAPTATION
Description:
The AMR_HR_DL_ADAPTATION counter array statistic statistic keeps count of the number of times
the codec mode is adapted on the downlink of half-rate AMR calls on a per-cell basis.
The bins are:
Bin 0 AMR half-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
Bin 1 AMR half-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
Bin 2 AMR half-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
Bin 3 AMR half-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
Bin 4 AMR half-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
Bin 5 AMR half-rate DL codec mode usage adaptation from 4th to 3rd codec mode.

AMR_HR_DL_ADAPTATION Version 1 Rev 4
AMR_HR_DL_ADAPTATION
Bin 0 AMR HR DL Codec Mode Usage Adaptation from 1st to 2nd codec mode
Bin 1 AMR HR DL Codec Mode Usage Adaptation from 2nd to 3rd codec mode
Bin 2 AMR HR DL Codec Mode Usage Adaptation from 3rd to 4th codec mode
Bin 3 AMR HR DL Codec Mode Usage Adaptation from 2nd to 1st codec mode
Bin 4 AMR HR DL Codec Mode Usage Adaptation from 3rd to 2nd codec mode
Bin 5 AMR HR DL Codec Mode Usage Adaptation from 4th to 3rd codec mode

Version 1 Rev 4 AMR_HR_UL_ADAPTATION
AMR_HR_UL_ADAPTATION
Description:
The AMR_HR_UL_ADAPTATION counter array statistic statistic keeps count of the number of times
the codec mode is adapted on the uplink of half-rate AMR calls on a per-cell basis.
The bins are:
Bin 0 AMR half-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
Bin 1 AMR half-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
Bin 2 AMR half-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
Bin 3 AMR half-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
Bin 4 AMR half-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
Bin 5 AMR half-rate UL codec mode usage adaptation from 4th to 3rd codec mode.

AMR_HR_UL_ADAPTATION Version 1 Rev 4
AMR_HR_UL_ADAPTATION
Bin 0 AMR HR UL Codec Mode Usage Adaptation from 1st to 2nd codec mode
Bin 1 AMR HR UL Codec Mode Usage Adaptation from 2nd to 3rd codec mode
Bin 2 AMR HR UL Codec Mode Usage Adaptation from 3rd to 4th codec mode
Bin 3 AMR HR UL Codec Mode Usage Adaptation from 2nd to 1st codec mode
Bin 4 AMR HR UL Codec Mode Usage Adaptation from 3rd to 2nd codec mode
Bin 5 AMR HR UL Codec Mode Usage Adaptation from 4th to 3rd codec mode

Version 1 Rev 4 MS Monitor Functionality
MS Monitor Functionality
Full Rate AMR Link Adaptation introduces MS Monitor functionality that monitors and compensates for
the inability of some mobiles to accurately estimate the current conditions of the channel that it is using.
The threshold and hysteresis values supplied for AMR calls by the network at call initialization
may be ineffective for some mobiles in certain RF conditions. The MS Monitor is introduced
as a mechanism to adjust the downlink codec mode adaptation thresholds during a call so
that the MS is able to correctly adapt across the ACS as needed.
The MS Monitor works by monitoring a mobile during a call and detecting conditions that indicate
that the downlink codec mode adaptation thresholds need adjusting. The MS Monitor will decrease
the thresholds at the MS if they are deemed to be too high and increase the thresholds if they
appear to be too low. If a mobile’s thresholds are too low, i.e. the range of C/I values that the MS is
measuring is below the lowest threshold in the ACS, then the mobile will request the lowest codec
mode whilst simultaneously indicating to the network that that call is in very good RF quality conditions.
The mobile could operate very well in these conditions in the highest codec mode.
The Monitor checks these conditions over a certain period of time and if the quality of the call is high
enough then the downlink adaptation thresholds will be modified in the mobile. Similarly, the MS
Monitor will increase the thresholds at the mobile if the network sees that the MS is requesting the
highest codec mode, whilst indicating that the call is in poor RF quality conditions, as this would indicate
that the range of C/I values measured by the mobile were above the highest threshold in the ACS.

MS Monitor Functionality Version 1 Rev 4
MS Monitor Functionality
Rxqual Thresholds
0
Lower threshold for When an AMR MS has requested
the lowest codec mode at least 95%
monitoring AMR MSs
(def) of the monitoring period
requesting the lowest
(40 SACCH def)
2 Default codec mode
Apply increase or decrease

to DL adaptation thresholds
4 Default
When an AMR MS has requested
Higher threshold for
the highest codec mode at least
monitoring AMR MSs
99% (def) of the monitoring period
requesting the highest
(40 SACCH def)
codec mode
7

Version 1 Rev 4 AMR_INCREASE_THRESH_ADJUST (DECREASE)
AMR_INCREASE_THRESH_ADJUST (DECREASE)
Description:
The AMR_INCREASE_THRESH_ADJUST counter statistic pegs each time that the BSS monitor
increases the downlink codec mode adaptation thresholds due to inaccurate C/I estimation by the MS.
The AMR_DECREASE_THRESH_ADJUST counter statistic pegs each time that the BSS monitor
decreases the downlink codec mode adaptation thresholds due to inaccurate C/I estimation by the MS.

AMR_INCREASE_THRESH_ADJUST (DECREASE) Version 1 Rev 4
AMR_INCREASE_THRESH_ADJUST (DECREASE)
AMR_INCREASE_THRESH_ADJUST
AMR_DECREASE_THRESH_ADJUST

Version 1 Rev 4 AMR_INCREASE_THRESH_ADJUST (DECREASE)

Appendix A Version 1 Rev 4
Chapter 11
Appendix A

Version 1 Rev 4 Appendix A

Control Channels and Multiframes Version 1 Rev 4
Control Channels and Multiframes

Version 1 Rev 4 Control Channels and Multiframes

GSM BURST TYPES
FRAME 1 FRAME 2
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
3 NORMAL BURST (NB) 3
Encrypted Bits Training Sequence Encrypted Bits

TB TB GP
57 26 57
1 1 8.25
3 FREQ CORRECTION BURST (FB) 3
Fixed Bits
TB TB GP
142
8.25
3 SYNCHRONISATION BURST (SB) 3
Encrypted Bits Synchronisation Sequence Encrypted Bits

TB TB GP
39 64 39
8.25
DUMMY BURST
3 3
Fixed Bits Training Sequence Fixed Bits

TB TB GP
57 26 57
1 1 8.25
ACCESS BURST
3
Synchronisation Sequence Encrypted Bits GP

TB TB
41 36 73.25
156.25 Bit Durations


26-FRAME MULTIFRAME
0.546ms
Time-slot
0.577ms
TDMA frame
7 6 5 4 3 2 1 0
4.615ms
2 1 0
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Idle SACCH
Multiframe
25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
120ms
Time


51-FRAME MULTIFRAME - Control Channel
Version 1 Rev 1
0.577ms
Time-slot
TDMA frame
7 6 5 4 3 2 1 0
4.615ms
2 1 0
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Multiframe
51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
235.635ms
Time


CONTROL CHANNELS
CCH
Control Channel
NB NB/DB
NB/AB
DCCH
BCCH -
downlink only
SDCCH ACCH
Synch
BCCH
Chans
FACCH SACCH SB FB
SCH FCH
CCCH
AB NB
RACH- PCH/AGCH
CBCH
uplink - downlink
NB= NORMAL BURST

FB = FREQUENCY BURST
SB = SYCHRONISATION BURST
AB = ACCESS BURST
DB = DUMMY BURST


BCCH/CCCH MULTIFRAME
50 I KEY 50 R
R
C
R= RACH (Random) R
B= BCCH (Broadcast) R
F= FCCH (Frequency)
S= SCH (Sync.)
R
C= CCCH (Common) R
C I= Idle R
R
R
S R
40 F 40 R
R
C R
R
R
R
C R
R
R
S R
30 F 30 R
R
C R
R
R
R
C R
R
R
S R
20 F 20 R
R
C R
R
R
R
C R
R
R
S R
10 F 10 R
R
C R
R
R
R
B R
R
R
S R
0 F 0 R
Downlink Uplink


DCCH MULTIFRAME
50 I I 50
I I KEY
I I A0 A4
D= SDCCH/8 (Dedicated)
A= SACCH/C8 (Associated)
A3 A7 I= Idle
D7 D7
A2 A6
40 40 D6 D6
A1 A5
D5 D5
A0 A4
D4 D4
30 30
D7 D7
D3 D3
D6 D6
D2 D2
D5 D5
20 20 D1 D1
D4 D4
D0 D0
D3 D3 I I
I I
I I
10 10
D2 D2 A7 A3
D1 D1 A6 A2
D0 D0 A5 A1
0 0
Downlink Uplink


COMBINED MULTIFRAME
KEY
50 I I R= RACH (Random)
50
B= BCCH (Broadcast) D2 D2
A1 A3 F= FCCH (Frequency)
S= SCH (Sync.)
C= CCCH (Common) R R
D= SDCCH/4 (Dedicated) R R
A= SACCH/C4 (Associated)
A0 A2 I= Idle
D1 D1
S S
40 F F 40
D0 D0
D3 D3
R R
R R
D2 D2 R R
R R
R R
S S R R
30 F F 30 R R
R R
D1 D1 R R
R R
R R
R R
D0 D0 R R
R R
R R
S S R R
20 F F 20 R R
R R
C C R R
R R
R R
R R
C C R R
S S A3 A1
10 F F 10
C C A2 A0
R R
B B R R
S S D3 D3
0 F F 0
Downlink Uplink

Answers Version 1 Rev 4
Chapter 12
Answers

Version 1 Rev 4 Answers

The interprocess messages shown below have resulted in an MS being able to establish
©MOTOROLA LTD.2002
on a TCH. Insert the incremented statistics at the appropriate software process at each stage
of the establishment.
L1 ABIS RRSM CRM SM SSM MSC
channel
request OK_ACC_PROC_SUC_RACH
Call Establishment Exercise Answers
ACCESS_PER_RACH
channel
channel CHAN_REQ_CAUSE_ATMPT
request
required channel
4 SDCCHs are available
required received
channel
assigned
ALLOC_SDCCH
RSS BUSY_SDCCH
channel activation
channel activation
acknowledge

immediate assignment
immediate
assignment ACCESS_PER_AGCH
MS_ACCESS_BY_TYPE
L2 SABM establish indication

CM service request OK_ACC_PROC [CM_SERV_CALL]
inital L3 information
CM Service request
Version 1 Rev 4
12-3
12-4
Version 1 Rev 4
<CR>
Complete L3
information
CONN_REQ_TO_MSC
CC
CALL SET UP MESSAGES
assignment request
initiate assignment
MA_REQ_FROM_MSC
assignment resource request
3 TCHs available
TCH_USAGE
channel assigned BUSY_TCH

ALLOC_TCH
ACTIVATION
assignment channel command

MA_CMD_TO MS
assignment complete

assignment successful
connectIon required
connection response
©MOTOROLA LTD.2002
Glossary of Terms Version 1 Rev 4
Chapter 13
Glossary of Terms

Version 1 Rev 4 Glossary of Terms

Glossary of technical terms Version 1 Rev 4
Glossary of technical terms

This Glossary of technical terms contains standard Motorola acronyms, abbreviations
and numbers used throughout the documentation set.
A Interface - AUTO
A Interface Interface between MSC and BSS. The interface is based on the
use of one or more E1/T1 digital links. The channels on these
links can be used for traffic or signalling.
A3 Authentication algorithm that produces SRES, using RAND and
Ki.
A38 A single algorithm performing the function of A3 and A8.
A5 Stream cipher algorithm, residing on an MS, that produces
ciphertext out of plaintext, using Kc.
A8 Ciphering key generating algorithm that produces Kc using
RAND and Ki.
AB See Access Burst.
Abis interface Interface between a remote BSC and BTS. Motorola offers
a GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message traffic and
thus the number of 2 Mbit/s lines required between BSC and BTS.
ABR Answer Bid Ratio. The ABR is the ratio of successful calls to total
number of calls. As a measure of effective calls, it reflects the
performance of the total network
ac-dc PSM AC-DC Power Supply module.
ac Alternating Current. In electricity, AC occurs when charge
carriers in a conductor or semiconductor periodically reverse their
direction of movement. Household utility current in most countries
is AC with a frequency of either 50 or 60 hertz (complete cycles
per second). The RF current in antennas and transmission lines
is another example of AC. An AC waveform can be sinusoidal,
square, or sawtooth-shaped. Some AC waveforms are irregular
or complicated. Square or sawtooth waves are produced by
certain types of electronic oscillators, and by a low-end UPS
when it is operating from its battery.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control. A method by which congested
switches automatically communicate their congestion level to
other switches.
Access Burst The Access Burst is used by the MS to access the BTS. It carries
RACH uplink from the MS to the BTS to start a call.
ACCH Associated Control CHannel. Control information associated with
TCH or DCCH.
ACK, Ack ACKnowledgement.

Version 1 Rev 4 Glossary of technical terms

ACM Accumulated Call meter. The ACM is a function contained within
the SIM. It accumulates the total units (in the home currency) for
both the current call and all preceding calls. For security reasons,
the SIM only allows the value of the ACM to be incremented,
not decremented. Resetting of the ACM is only possible after
entering PIN2.
ACM Address Complete Message.
ACPIM AC Power Interface Module. Used in M-Cell6 indoor ac BTS
equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE Association Control Service Element. The ACSE is one of the
three Application Service Elements (ASE) which reside in the
application layer of the OSI protocol and act as an interface to the
lower layer protocols. It is used by applications to create a title
for identification. See also ASI and ROSE.
ACU Antenna Combining Unit.
A/D Analogue to Digital (converter). See ADC.
ADC ADministration Centre.
ADC Analogue to Digital Converter. A device that converts a signal
that is a function of a continuous variable into a representative
number sequence carrying equivalent information.
ADCCP Advanced Data Communications Control Protocol. A bit-oriented
data-link-layer (DL) protocol used to provide point-to-point and
point-to-multipoint transmission of data frames that contain
error-control information. Note: ADCCP closely resembles
high-level data link control (HDLC).
ADM ADMinistration processor.
ADMIN ADMINistration.
ADN Abbreviated Dialling Number. Abbreviated dialling is a telephone
service feature that (a) permits the user to dial fewer digits to
access a network than are required under the nominal numbering
plan, and (b) is limited to a subscriber-selected set of frequently
dialled numbers.
ADPCM Adaptive Differential Pulse Code Modulation. Differential
pulse-code modulation (DPCM) in which the prediction algorithm
is adjusted in accordance with specific characteristics of the input
signal.
AE Application Entity. The system-independent application activities
that are made available as application services to the application
agent.
AEC Acoustic Echo Control. In a system, the reduction of the power
level of an echo or the elimination of an echo.
AEF Additional Elementary Functions.
AET Active Events Table. Alarms and events are sent to the Events
Log in the GUI. Different operators will have different subscription
lists. All alarms and events are sent to the AET before they are
re-routed to different subscription lists.


AFC Automatic Frequency Control. A device or circuit that maintains
the frequency of an oscillator within the specified limits with
respect to a reference frequency.
AFN Absolute Frame Number.
AGC Automatic Gain Control. A process or means by which gain is
automatically adjusted in a specified manner as a function of a
specified parameter, such as received signal level.
AGCH Access Grant CHannel. A GSM common control channel used to
assign MS to a SDCCH or a TCH.
Ai Action indicator.
AI Artificial Intelligence. A branch of computer science whose goal
is to develop electronic devices that can operate with some of the
characteristics of human intelligence. Among these properties
are logical deduction and inference, creativity, the ability to make
decisions based on past experience or insufficient or conflicting
information, and the ability to understand natural language.
AIB Alarm Interface Board.
AIO A class of processor.
Air interface The radio link between the BTS and the MS.
AL See Application Layer.
AM Amplitude Modulation. Modulation in which the amplitude of a
carrier wave is varied in accordance with some characteristic
of the modulating signal.
AMA Automatic Message Accounting (processor). A service feature
that automatically records data regarding user-dialled calls.
AMR Adaptive Multi-Rate. The capability of operating at gross bit-rates
of 11.4 kbit/s (half-rate) and 22.8 kbit/s (full-rate) over the air
interface.
AM/MP Cell broadcast mobile terminated message. A message
broadcast to all MSs in a cell.
ANSI American National Standards Institute. ANSI is the primary
organisation for fostering the development of technology
standards in the United States. ANSI works with industry groups
and is the U.S. member of ISO and the IEC. Long established
computer standards from ANSI include ASCII and SCSI.
Antenna A transmitter/receiver which converts electrical currents into RF
and vice versa. In GSM systems, transmits and receives RF
signals between the BTS and MS.
AoC Advice of Charge.
AoCC Advice of Charge Charging supplementary service.
AoCI Advice of Charge Information supplementary service.
AOC Automatic Output Control.
AP Application Process.


Application Layer See OSI RM. The Application Layer is the highest of seven
hierarchical layers. It interfaces directly to, and performs common
application services for, the application processes. It also issues
requests to the Presentation Layer. The common application
services provide semantic conversion between associated
application processes.
ARFCN Absolute Radio Frequency Channel Number. The GSM available
frequency is divided in two bands. Each band is divided into
200kHz slots called ARFCN. Each ARFCN is shared between
8 mobiles, each using it in turn. Each mobile uses the ARFCN
for one TS (Timeslot) and then waits for its turn to come around
again. A mobile has use of the ARFCN once per the TDMA
frame. The combination of a TS number and ARFCN is called a
physical channel.
ARQ Automatic Repeat-reQuest. Error control for data transmission in
which the receiver detects transmission errors in a message and
automatically requests a retransmission from the transmitter.
ARP Address Resolution Protocol. A Transmission Control Protocol
/ Internet Protocol (TCP/IP) protocol that dynamically binds a
Network Layer (NL) IP address to a Data Link Layer (DL) physical
hardware address, e.g., Ethernet address.
ASCE Association Control Service Element. An ASE which provides
an AP with the means to establish and control an association
with an AP in a remote NE. Maps directly onto the Presentation
layer (OMC).
ASCII American Standard Code for Information Interchange. ASCII is
a standard developed by ANSI to define how computers write
and read characters. It is the most common format for text files
in computers and on the Internet. In an ASCII file, alphabetic,
numeric, and special characters are represented with a 7-binary
digit binary number. 128 possible characters are defined. UNIX
and DOS-based operating systems (except for Windows NT) use
ASCII for text files. Windows NT uses a newer code, Unicode.
IBM’s System 390 servers use a proprietary 8-bit code called
extended binary-coded decimal interchange code. Conversion
programs allow different operating systems to change a file from
one code to another.
ASE Application Service Element (OMC). A coherent set of integrated
functions to help accomplish application communication, e.g.,
within an application entity (AE).
ASE Application Specific Entity (TCAP).
ASN.1 Abstract Syntax Notation One. A formal notation used
for describing data transmitted by telecommunications
protocols, regardless of language implementation and physical
representation of these data, whatever the application, whether
complex or very simple.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio. The percentage of calls that are
completed successfully.
ATB All Trunks Busy. An equipment condition in which all trunks
(paths) in a given trunk group are busy.


Ater The interface between XCDR and BSC.
ATI Antenna Transceiver Interface.
ATM Asynchronous Transfer Mode. A high-speed multiplexing and
switching method utilising fixed-length cells of 53 octets to
support multiple types of traffic.
ATT (flag) ATTach.
ATTS Automatic Trunk Testing Subsystem. Ensures the quality of
telephone lines by means of a series of tests. ATTS can be
initiated by either an operator command or by a command file,
which can be activated at a predetermined time.
AU Access Unit.
AUC Authentication Centre. A GSM network entity which provides the
functionality for verifying the identity of an MS when requested by
the system. Often a part of the HLR.
AUT(H) AUThentication.
AUTO AUTOmatic mode.
B Interface - Byte
B Interface Interface between MSC and VLR.

BA BCCH Allocation. The radio frequency channels allocated in a
cell for BCCH transmission.
BAIC Barring of All Incoming Calls supplementary service.
BAOC Barring of All Outgoing Calls supplementary service.
Baud The unit in which the information carrying capacity or signalling
rate of a communication channel is measured. One baud is one
symbol (state transition or level-transition) per second. This
coincides with bits per second only for two-level modulation with
no framing or stop bits
BBBX Battery Backup Board.
BBH Base Band Hopping. Method of frequency hopping in which each
transceiver at the base station is tuned to a different frequency,
and the signal is switched to a different transceiver for each burst.
BCC Base station Colour Code. The BCC and the NCC are part of the
BSIC. The BCC comprises three bits in the range 000 to 111.
See also NCC and BSIC.
BCCH Broadcast Control CHannel. A GSM control channel used to
broadcast general information about a BTS site on a per cell or
sector basis.
BCD Binary Coded Decimal. The representation of a decimal digit by a
unique arrangement of no fewer than four binary digits.
BCF Base station Control Function. The GSM term for the digital
control circuitry which controls the BTS. In Motorola cell sites this
is a normally a BCU which includes DRI modules and is located
in the BTS cabinet.


B channel Bearer channel. Used in ISDN services to carry 64kbit/s of data,
when used at full capacity.
BCIE Bearer Capability Information Element. Specific GSM parameters
in the Setup message are mapped into a BCIE for signalling to
the network and within the PLMN. The BCIE is used to request a
bearer service (BS) from the network.
BCU Base station Control Unit. A functional entity of the BSS which
provides the base control function at a BTS site. The term no
longer applies to a type of shelf (see BSC and BSU).
BCUP Base Controller Unit Power.
BEP Bit Error Probability.
BER Bit Error Rate. The number of erroneous bits divided by the total
number of bits transmitted, received, or processed over some
stipulated period. The BER is usually expressed as a coefficient
and a power of 10; for example, 25 erroneous bits out of 100,000
bits transmitted would be 25 out of 105 or 25 x 10-5.
BES Business Exchange Services.
BFI Bad Frame Indication. An indication of unsuccessfully decoded
speech frames. See FER.
BH Busy Hour. In a communications system, the sliding 60-minute
period during which occurs the maximum total traffic load in a
given 24-hour period.
BHCA Busy Hour Call Attempt. A statistic based on call attempts that a
switch processes during a BH. See also BH.
BI Barring of all Incoming call supplementary service.
BIB Balanced-line Interconnect Board. Provides interface to 12
balanced (6-pair) 120 ohm (37-pin D-type connector) lines for 2
Mbit/s circuits. See also T43.
BIC-Roam Barring of all Incoming Calls when Roaming outside the Home
PLMN Country supplementary service.
Bi-directional neighbour See Reciprocal neighbour..
BIM Balanced-line Interconnect Module.
Bin From BINary. An area in a data array used to store information.
Also, a name for a directory that contain files stored in binary
format.
BL BootLoad. Also known as download. For example, databases
and software can be downloaded to the NEs from the BSS.
BLER Block Error Rate
BLLNG BiLLiNG.
bit Binary digit. A character used to represent one of the two states
or digits (0 or 1) in the numeration system with a radix of two.
Also, a unit of storage capacity.


bit/s Bits per second (bps). A measure of data transmission speed.
The number of binary characters (1s or 0s) transmitted in one
second. For example, an eight-bit parallel transmission link which
transfers one character (eight bits) per second is operating at
8 bps.
block A group of bits (binary digits) transmitted as a unit, over which a
parity check procedure is applied for error control purposes.
Bm Full rate traffic channel. See also Full Rate.
BN Bit Number. Number which identifies the position of a particular
bit period within a timeslot.
BPF Bandpass Filter. A filter that ideally passes all frequencies
between two non-zero finite limits and bars all frequencies not
within the limits.
BPSM µBCU Power Supply Module.
BRI Basic Rate Interface. An ISDN multipurpose user interface
allowing simultaneous voice and data services provided over
two clear 64 kb/s channels (B channels) and one clear 16 kb/s
channel (D channel). The interface is also referred to as 2B+D.
BS Base Station. See BSS.
BS Basic Service (group).
BS Bearer Service. A type of telecommunication service that
provides the capability for the transmission of signals between
user-network interfaces. The PLMN connection type used to
support a bearer service may be identical to that used to support
other types of telecommunication service.
BSC Base Station Controller. A network component in the GSM PLMN
which has the digital control function of controlling all BTSs. The
BSC can be located within a single BTS cabinet (forming a BSS)
but is more often located remotely and controls several BTSs
(see BCF, BCU, and BSU).
BSG Basic Service Group.
BSIC Base Transceiver Station Identity Code. Each cell has a BSIC. It
is a local colour code that allows a mobile station to distinguish
between different neighbouring base stations. The BSIC is an
octet, consisting of three bits for the Network Colour Code (NCC)
and three bits for the Base station Colour Code (BCC). The
remaining two bits are unused. See also NCC and BCC.
BSIC-NCELL BSIC of an adjacent cell.
BSP Base Site control Processor (at BSC).
BSN Backward Sequence Number. A field in a signal unit (SU) that
contains the forward sequence number (FSN) of a correctly
received signal unit being acknowledged in the signal unit that is
being returned to the sender. See also FSN and SU.


BSS Base Station System. The system of base station equipment
(Transceivers, controllers and so on) which is viewed by the
MSC through a single interface as defined by the GSM 08
series of recommendations, as being the entity responsible for
communicating with MSs in a certain area. The radio equipment
of a BSS may cover one or more cells. A BSS may consist of one
or more base stations. If an internal interface is implemented
according to the GSM 08.5x series of recommendations, then the
BSS consists of one BSC and several BTSs.
BSSAP BSS Application Part (part of SS7) . Protocol for LAPD or
LAPB signalling links on the A-interface. Comprises DTAP
and BSSMAP messages. Supports message communication
between the MSC and BSS.
BSSC Base Station System Control cabinet. The cabinet which houses
one or two BSU shelves at a BSC or one or two RXU shelves at a
remote transcoder (RXCDR).
BSSMAP Base Station System Management Application Part (part of SS7).
Call processing protocol for A-interface messages exchanged
between the MSC and BSS. The BSS interprets these messages.
BSSOMAP BSS Operation and Maintenance Application Part (part of SS7).
BSU Base Station Unit shelf. The shelf which houses the digital
control modules for the BTS (part of BTS cabinet) or BSC (part
of BSSC cabinet).
BT British Telecom.
BT Bus Terminator. In order to avoid signal reflections on the bus,
each bus segment has to be terminated at its physical beginning
and at its end with the characteristic impedance.
BTC Bus Terminator Card.
BTF Base Transceiver Function.
BTP Base Transceiver Processor (at BTS). One of the six basic task
groups within the GPROC.
BTS Base Transceiver Station. A network component in the GSM
PLMN which serves one cell, and is controlled by a BSC. The
BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The physical
content of a timeslot.
Byte A sequence of adjacent binary digits operated upon as a unit.
Generally consists of eight bits, usually presented in parallel. A
byte is usually the smallest addressable unit of information in a
data store or memory.
C - CW
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 See SS7.


CA Cell Allocation. The radio frequency channels allocated to a
particular cell.
CA Central Authority. Software process that controls the BSS.
CAB Cabinet.
CADM Country ADMinistration. The Motorola procedure used within
DataGen to create new country and network files in the DataGen
database.
CAI Charge Advice Information.
CAT Cell Analysis Tool. The CAT is part of the Motorola Cell
Optimization product. It is intended for engineering staff and
OMC administrators. CAT provides information about GSM
network cell performance.
CB Cell Balancer. The CB process balances the cells configured for
GPRS across PRPs. In the event of a PRP outage, this process
sends message(s) indicating that GPRS service is unavailable to
the appropriate CRM(s) for the cells that could not be moved to
an INS (IN Service) PRP.
CB Cell Broadcast. See CBSMS.
CB Circuit Breaker.
CBA Cell Broadcast Agent.
CBC Cell Broadcast Centre. The call processing centre for CBSMS
messages.
CBCH Cell Broadcast CHannel. The channel which is used to broadcast
messages to all MSs in a specific cell.
CBF Combining Bandpass Filter.
CBL Cell Broadcast Link. A bi-directional data link which allows
communications between the BSS and the CBC.
CBM Circuit Breaker Module.
CDMA Code-Division Multiple Access. CDMA is a digital cellular
technology that uses spread-spectrum techniques. Unlike
competing systems, such as GSM, that use TDM, CDMA does
not assign a specific frequency to each user. Instead, every
channel uses the full available spectrum. Individual conversations
are encoded with a pseudo-random digital sequence.
CBMI Cell Broadcast Message Identifier.
CBS Cell Broadcast Service. See CBSMS.
CBSMS Cell Broadcast Short Message Service. CBSMS allows a number
of unacknowledged general messages to be broadcast to all MSs
within a particular region. The content may include information
such as local traffic conditions, the weather, the phone number of
the local taxi company, etc. The messages are sent from a CBC
via a BSC to a BTS and from there on a special cell broadcast
channel to the MSs. The CBC is considered as a node outside
the PLMN and can be connected to several BSCs. However, a
BSC is only connected to one CBC.
CBUS Clock Bus.


CC Connection Confirm. Part of SCCP network connectivity.
CC Country Code. A one to three digit number which specifically
identifies a country of the world that an international call is being
routed to (e.g., 1 = North America, 44 = United Kingdom).
CC Call Control. CC functions, such as number translations and
routeing, matrix path control, and allocation of outgoing trunks
are performed by the MSC.
CCB Cavity Combining Block, a three way RF combiner. There are
two types of CCB, CCB (Output) and CCB (Extension). These,
with up to two CCB Control cards, may comprise the TATI. The
second card may be used for redundancy.
CCBS Completion of Calls to Busy Subscriber supplementary service.
CCCH Common Control CHannels. A class of GSM control channels
used to control paging and grant access. Includes AGCH, PCH,
and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding. See CFC.
CCH Control CHannel. Control channels are channels which carry
system management messages.
CCH Council for Communications Harmonization (referred to in GSM
Recommendations).
CCITT Comité Consultatif International Télégraphique et Téléphonique.
This term has been superseded. See ITU-TSS.
CCM Current Call Meter.
CCP Capability/Configuration Parameter.
CCPE Control Channel Protocol Entity.
CCS Hundred call-seconds. A single call lasting one hundred seconds
is one CCS. Also, a measure of traffic load obtained by multiplying
the number of calls per hour by the average holding time per call
expressed in seconds, and dividing by 100. Often used in practice
to mean hundred call seconds per hour with “per hour" implied;
as such, it is a measure of traffic intensity. See also erlang.
CCU Channel Codec Unit. The CCU performs the following functions:
Channel coding functions, including FEC and interleaving, Radio
channel measurement functions, including received quality level,
received signal level, and information related to timing advance
measurements.
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab - cron job file).


CDR Call Detail Record. A record of voice or data SVCs, which
includes calling and called numbers, local and remote node
names, data and timestamp, elapsed time, and call failure class
fields. This is the information needed to bill the customer for calls
and facility usage data for calls.
CD-ROM Compact Disk-Read Only Memory.
CDUR Chargeable DURation.
CEB Control Equalizer Board (BTS).
CED Called station identifier.
CEIR Central Equipment Identity Register.
Cell By GSM definition, a cell is an RF coverage area. At an
omni-site, cell is synonymous with site; at a sectored site, cell is
synonymous with sector. This differs from analogue systems
where cell is taken to mean the same thing as site. (See below)
CEND End of charge point. The time at which the calling, or called, party
stops charging by the termination of the call or by an equivalent
procedure invoked by the network or by failure of the radio path.
CEPT Conférence des administrations Européennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor. Identifies when discontinuity is
detected in a circuit. An alarm is generated and sent to the
OMC-R when the error count exceeds an operator specified
threshold. The alarm identifies the RCI or CIC and the path
where the error is detected.
CF Conversion Facility.
CF Call Forwarding. A feature available to the mobile telephone
user whereby, after initiation of the feature by an authorised
subscriber, calls dialled to the mobile telephone of an authorised
subscriber will automatically be routed to the desired number.
See also CFC and CFU.
CF Control Function. CF performs the SGSN mobility management
functions and OA&M functions for the GSN module.
CFB Call Forwarding on mobile subscriber Busy supplementary
service. Service automatically redirects incoming calls for phone
busy situations.
CFC Call Forwarding Conditional supplementary service. Service
automatically redirects incoming calls for busy, no reply, or not
reachable situations. See also CFB, CFNRc, and CFNRy.
CFM Configuration Fault Management RSS process.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service. Service automatically redirects incoming
calls for not reachable situations.


CFNRy Call Forwarding on No Reply supplementary service. Service
automatically redirects incoming calls for no reply situations.
CFU Call Forwarding Unconditional supplementary service. Service
automatically redirects all incoming calls.
CG Charging Gateway.
CGF Charging Gateway Function.
Channel A means of one-way transmission. A defined sequence of
periods (for example, timeslots) in a TDMA system; a defined
frequency band in an FDMA system; a defined sequence of
periods and frequency bands in a frequency hopped system.
CIM Coaxial Interconnect Module.
Channel Mode See Full Rate and Half Rate. These are the channel modes
that are currently used.
CHP CHarging Point.
CHV Card Holder Verification information.
CKSN Ciphering Key Sequence Number. The CKSN is a number which
is associated with the ciphering key, Kc. It is used to ensure
authentication consistency between the MS and the VLR.
CI Cell Identity. A block of code which identifies a cell within a
location area.
CI CUG Index.
C/I Carrier to Interference ratio.
CIC Circuit Identity Code. The unique identifier of the terrestrial
portion of a circuit path. A CIC is either a 64 kbit/s or 16 kbit/s
connection depending on whether a site has local or remote
transcoding. A CIC with local transcoding occupies a complete
E1/T1 timeslot. A 16 kbit/s CIC, at a site with remote transcoding,
occupies a sub-channel of an E1/T1 timeslot.
CIR, C/I Carrier to Interference Ratio. Indicates the received signal power
level relative to the interference power level.
Ciphertext Unintelligible data produced through the use of encipherment.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity. The identity of the caller. See also CLIP
and CLIR.
CLIP Calling Line Identification Presentation supplementary service.
Allows the called party to identify the caller. See also CLIR.
CLIR Calling Line Identification Restriction supplementary service.
Allows the caller to withhold their identity from the called party.
See also CLIP.
CLK Clock.
CLKX Clock Extender half size board. The fibre optic link that distributes
GCLK to boards in system (part of the BSS, etc).


CLM ConnectionLess Manager. Coordinates global control over
the BSS by handling of all connectionless messages (that is,
messages that are not directly concerned with a connected call).
This includes such messages as global resets, load limiting and
circuit blocking.
CLR CLeaR.
CM Configuration Management. Configuration management allows
the operator to perform network configuration tasks, and to
maintain all details of the network configuration at the OMC.
CM Connection Management. See CLM.
CM Connectionless Manager. See CLM.
CMD CoMmanD.
CMM Channel Mode Modify. Message sent to an MS to request a
channel mode change. When it has received the CMM message,
the MS changes the mode to the indicated channel and replies
with a Channel Mode Modify Acknowledge message indicating
the new channel mode.
CMIP Common Management Information Protocol. Protocol used for
communication over the OML.
CMISE Common Management Information Service Element. An ASE
which provides a means to transfer management information via
CMIP messages with another NE over an association established
by ASCE using ROSE (OMC).
CMR Cellular Manual Revision. Documentation updates.
CNG CalliNg tone.
Codec Coder/Decoder. A speech coding unit that converts speech into a
digital format for radio broadcast, and vice versa.
CODEX Manufacturer’s name for a type of multiplexer and packet switch
commonly installed at the Motorola OMC-R.
Coincident Cell A cell whose cell boundary follows the boundary of a co-located
neighbour cell. The coincident cell has a different frequency type,
but the same BSIC, as that of the neighbour cell.
COLI COnnected Line Identity. Identity of the connected line. See also
COLP and COLR.
Collocated Placed together; two or more items together in the same place.
Colour Code An 8-bit code assigned to a BTS to distinguish interfering signals
from another cell.
COLP COnnected Line Identification Presentation supplementary
service. Allows the calling party to identify the line identity of the
connected party. See also COLR.
COLR COnnected Line Identification Restriction supplementary service.
Allows the connected party to withhold its line identity from the
calling party. See also COLP.
COM Code Object Manager (software).
COM COMplete.


COMB Combiner. The purpose of a combiner in the BSS is to combine
transmitter outputs from the RCUs onto an antenna.
COMM, Comms COMMunications.
CommHub Communications Hub. Provides Ethernet switching and IP
routeing for the GSN complex local networking and GSN complex
E1 interfaces to the public data network.
CommsLink Communications Link. See also 2 Mbit/s link.
Compact PCI See cPCI.
CONF CONFerence circuit. Circuit used for multi-party conference calls.
CONFIG CONFIGuration Control Program.
Congestion Situation occurring when an element cannot receive all the
service it is requesting.
CONNACK CONNect ACKnowledgement. Part of the synchronization
process. After a connection has been established, the CONNACK
message indicates that traffic channels are available.
CP Call Processing. The CP process in the BTS controls the MS to
BSS to MS signalling link, MS originated and terminated calls
and inter-BSS and inter-BTS handovers.
cPCI Compact Peripheral Component Interconnect. A set of standards
that define a common card cage, power supplies, and processor
boards.
CPGM CCCH Paging Manager. The CPGM processes the paging
messages sent from the SGSN to the BSC/BTS.
CPS Code and Puncturing Scheme.
CPU Central Processing Unit. The portion of a computer that controls
the interpretation and execution of instructions. Also, the portion
of a digital communications switch that executes programmed
instructions, performs arithmetic and logical operations on
signals, and controls input/output functions.
C/R Command/Response field bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity). An
SCCP Connection Request message is sent from the BSS to the
MSC to establish a connection. See also CREF.
CRC Cyclic Redundancy Check (3 bit). An error-detection scheme that
(a) uses parity bits generated by polynomial encoding of digital
signals, (b) appends those parity bits to the digital signal, and
(c) uses decoding algorithms that detect errors in the received
digital signal.
CRE Call RE-establishment procedure. Procedure for re-establishing
a call in the event of a radio link failure.
CREF Connection REFused (Part of SCCP network connectivity). In
a number of operating circumstances, a CREF message may
be sent from the MSC to the BSS in response to a Connection
Request (CR).


CRM Cell Resource Manager. The CRM allocates and activates
timeslots and subchannels on the available carriers.
CRM Cell Resource Machine.
CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed
modem used to interwork 300 to 2400 bit/s data services under
V.22bis, V.23, or V.21 standards. High speed modem used to
interwork 1200 to 9600 bit/s data services under V.22bis, V.32,
or V.29/V.27ter/V.21 standards.
CRO Motorola Controlled Roll Out Group. A CRO consists of a
customer site implementation of a new product, software release,
or combination of products/releases.
CRT Cathode Ray Tube (video display terminal).
CS Circuit Switched.
CS-1 GPRS Coding Scheme-1 (9.05 kbit/s per TCH).
CSFP Code Storage Facility Processor (at BSC and BTS). A GPROC
device which facilitates the propagating of new software instances
with reduced system down time. See also IP.
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network. A publicly available
communications network using circuit switched digital data
circuits.
CT Call Transfer supplementary service.
CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool). The CTP is designed to help operators
of GSM900 and DCS1800 communication networks tune and
optimize their systems. CTP allows Call Trace data to be
analysed and decoded.
CTP Control Terminal Port.
CTR Common Technical Regulation.
CTS Clear to Send. A handshake signal used with communication
links, especially RS232 or CCITT Rec. V.24, to indicate (to a
transmitter from a receiver) that transmission may proceed.
Generated in response to a request to send signal. See also RTS.
CTU Compact Transceiver Unit (M-Cellhorizon radio).
CUG Closed User Group supplementary service. A CUG is used
to control who can receive and/or place calls, by creating a
unique group. When a CUG is configured for an interface, only
those subscribers that are members of the same CUG can
receive/place calls.


Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service. A subscriber feature which
allows an individual mobile telephone user currently engaged in a
call to be alerted that another caller is trying to reach him. The
user has a predetermined period of time in which to terminate the
existing conversation and respond to the second call.
D Interface - DYNET
D Interface Interface between VLR and HLR.

D/A Digital to Analogue (converter). See DAC.
DAB Distribution Alarm Board (in BTS6 cabinet).
DAC Digital to Analogue Converter. A device that converts an input
number sequence into a function of a continuous variable.
DACS Digital Access Cross-connect System. A data concentrator and
organizer for Tl / El based systems.
DAK Downlink Acknowledgement
DAN Digital ANnouncer (for recorded announcements on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape. Audio-recording and playback medium/format
that maintains a signal quality equal to that of the CD-ROM
medium/format.
DataGen Sysgen Builder System. A Motorola offline BSS binary object
configuration tool.
Data Link Layer See OSI RM. This layer responds to service requests from the
Network Layer and issues service requests to the Physical Layer.
It provides the functional and procedural means to transfer data
between network entities and to detect and possibly correct
errors that may occur in the Physical Layer.
dB Decibel. A unit stating the logarithmic ratio between two numeric
quantities. See also dBm.
DB DataBase.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration/Database Administrator.
dBm A dB referenced to 1 milliwatt; 0 dBm equals one milliwatt.
DBMS DataBase Management System.
dc Direct Current. DC is the unidirectional flow or movement of
electric charge carriers, usually electrons. The intensity of the
current can vary with time, but the general direction of movement
stays the same at all times. As an adjective, the term DC is used
in reference to voltage whose polarity never reverses.
DCB Diversity Control Board (part of DRCU).


DCCH Dedicated Control CHannel. A class of GSM control channels
used to set up calls and report measurements. Includes SDCCH,
FACCH, and SACCH.
DCD Data Carrier Detect signal. Hardware signal defined by the
RS-232-C specification that indicates that a device such as a
modem is on-line and ready for transmission.
DCE Data Circuit terminating Equipment. The DCE performs functions
such as signal conversion and coding, at the network end of the
line between the DTE and the line.
Also, The RS232 configuration designated for computers. DCE
equipment can be connected to DTE equipment with a straight
cable, but to other DCE equipment only with a null modem cable.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in Horizonmacro).
D channel Data channel. Used in ISDN to perform call signalling and
connection setup functions. In some circumstances, the channel
can also be used to carry user data.
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation devices
to the Operations Systems.
DC PSM DC Power Supply Module.
DCS1800 Digital Cellular System at 1800 MHz. A cellular phone network
using digital techniques similar to those used in GSM 900, but
operating on frequencies of 1710 - 1785 MHz (receive) and
1805 - 1880 MHz (transmit).
DDF Dual-stage Duplexed combining Filter. (Used in Horizonmacro).
The DDF is an integrated combiner, filter and duplexer.
DDS DataGen Data Store. Store area for DataGen input and output
files.
DDS Data Drive Storage.
DDS Direct Digital Synthesis. A technology for generating highly
accurate and frequency-agile (rapidly changeable frequency over
a wide range), low-distortion output waveforms.
DEQB Diversity Equalizer Board.
DET DETach.
DFE Decision Feedback Equalizer. A receiver component/function.
The DFE results in a very sharp Bit Error Rate (BER) threshold
by using error feedback.
DGT Data Gathering Tool. The DGT collects all the relevant data
relating to a specified problem and copies it to tape or file,
together with a problem description. The file or tape is then sent
to Motorola for analysis.
DHP Digital Host Processor. A hard GPROC based device located
at Horizonmicro2 BTS sites. It represents the MCU of a slave
Horizonmicro2 FRU. The MCU that the DHP represents is
responsible for providing DRI and carrier support.
DIA Drum Intercept Announcer.


DINO E1/HDSL Line termination module (part of Horizonmicro).
DINO T1 Line termination module (part of Horizonmicro).
DISC DISConnect.
Discon Discontinuous.
DIQ Diversity In phase and Quadrature phase.
DIR Device Interface Routine. Software routine used in the BSS.
DL Data Link (layer). See Data Link Layer.
DL See Downlink.
DLCI Data Link Connection Identifier. In frame-relay transmission
systems, 13-bit field that defines the destination address of a
packet. The address is local on a link-by-link basis.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLS DownLink Segmentator. The DLS segments LLC frames into
RLC data blocks to be transmitted over the air interface.
DLSP Data Link Service Process. Handles messages for an OMP and
a shelf GPROC.
DLSP Digital Link Signalling Processor.
Dm Control channel (ISDN terminology applied to mobile service).
DMA Deferred Maintenance Alarm. An alarm report level; an
immediate or deferred response is required (see also PMA).
DMA Direct Memory Access. Transfer of data from a peripheral device,
such as a hard disk drive, into memory without that data passing
through the microprocessor. DMA transfers data into memory at
high speeds with no processor overhead.
DMR Digital Mobile Radio.
DMX Distributed Electronic Mobile Exchange (Motorola’s networked
EMX family).
DN Directory Number.
DNIC Data Network Identifier Code. In the CCITT International X.121
format, the first four digits indicate the international data number,
the next three digits are the data country code, and the final digit
is the network code.
DNS Domain Name Service. A service that translates from logical
domain or equipment names to IP addresses.
Downlink Physical link from the BTS towards the MS (BTS transmits, MS
receives).
DP Dial/Dialled Pulse. A dc pulse produced by an end instrument that
interrupts a steady current at a sequence and rate determined
by the selected digit and the operating characteristics of the
instrument.
DPC Destination Point Code. A part of the label in a signalling
message that uniquely identifies, in a signalling network, the
(signalling) destination point of the message.


DPC Digital Processing and Control board.
DPCM Pulse-code modulation (PCM) in which an analog signal is
sampled and the difference between the actual value of each
sample and its predicted value, derived from the previous sample
or samples, is quantified and converted, by encoding, to a
digital signal. Note: There are several variations of differential
pulse-code modulation.
DPNSS Digital Private Network Signalling System (BT standard for PABX
interface).
DPP Dual Path Preselector. BTS module.
DPR, DPRAM Dual Port Random Access Memory.
DPROC Data PROCessor.
DPSM Digital Power Supply Module.
DRAM Dynamic Random Access Memory. A type of semiconductor
memory in which the information is stored in capacitors on a
integrated circuit.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for 8 circuits.
Part of IWF.
DRCU Diversity Radio Channel Unit. Contains transceiver, digital control
circuits, and power supply. Part of the BSS.
DRI Digital Radio Interface. Provides encoding/decoding and
encryption/decryption for radio channels. Part of BSS.
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
DRIX DRI Extender half size board. Fibre optic link from DRI to BCU.
Part of the BSS.
DRX, DRx Discontinuous reception (mechanism). A means of saving battery
power (for example in hand-portable units) by periodically and
automatically switching the MS receiver on and off.
DS-1 Digital transmission System 1 (or Digital Signal level 1). Term
used to refer to the 1.44 Mbit/s (U.S.) or 2.108 Mbit/s (Europe)
digital signal carried on a T1 facility.
DS-2 German term for 2 Mbit/s line (PCM interface).
DSE Data Switching Exchange.
DSI Digital Speech Interpolation. A compression technique that relies
on the pauses between speech bursts to provide additional
compression. DSI enables users to gain an additional 2:1
compression on the average on their line.
DSO 64 kbit/s timeslot on an E1/T1.
DSP Digital Signal Processor. A specialized, programmable computer
processing unit that is able to perform high-speed mathematical
processing.
DSS1 Digital Subscriber Signalling No 1. N-ISDN user network interface
signalling.


DSSI Diversity Signal Strength Indication.
DTAP Direct Transfer Application Part (Part of SS7). Call processing
protocol for A-Interface messages exchanged directly between
the MSC and the mobile unit without interpretation by the BSS.
DTE Data Terminal Equipment. An end instrument that converts
user information into signals for transmission or reconverts the
received signals into user information.
Also, the RS232 configuration designated for terminals. DTE
equipment can be connected to DCE with a straight cable, but to
other DTE equipment only with a null modem.
DTF Digital Trunk Frame. A frame or electronic rack of digital trunk
interface equipment.
DT1 DaTa form 1 (Part of SCCP network connectivity).
DTI Digital Trunk Interface.
DTM Dual Transer Mode.
DTMF Dual Tone Multi-Frequency. Multifrequency signalling in which
specified combinations of two voice band frequencies, one from a
group of four low frequencies and the other from a group of four
higher frequencies, are used. The sounds a push button tone
telephone makes when it dials a number.
DTR Data Terminal Ready signal. Method of flow control (RS232
Interface). A modem interface control signal sent from the DTE
to the modem, usually to indicate to the modem that the DTE is
ready to transmit data.
DTRX Dual Transceiver Module. (Radio used in Horizonmicro
(M-Cellarena) and Horizonmacro (M-Cellarenamacro)).
DTX, DTx Discontinuous Transmission (mechanism). A means of saving
battery power (for example in hand-portable units) and reducing
interference by automatically switching the transmitter off when
no speech or data are to be sent.
Dummy burst A period of carrier less than one timeslot whose modulation is a
defined sequence that carries no useful information. A dummy
burst fills a timeslot with an RF signal when no information is
to be delivered to a channel.
DYNET DYnamic NETwork. Used to specify BTSs sharing dynamic
resources.
E - EXEC
E See Erlang.
E1 Also known as CEPT1. The 2.048 Mbit/s rate used by European
CEPT carrier to transmit 30 64 kbit/s digital channels for voice
or data calls, plus a 64 kbit/s signalling channel and a 64 kbit/s
channel for framing and maintenance.
E Interface Interface between MSC and MSC.
EA External Alarm. See EAS. Typical external alarms are: Door
open, High humidity, Low humidity, Fire, Intruder.


EAS External Alarm System. The EAS is responsible for the monitoring
of all customer-defined environmental alarms at a site. The
customer defines the alarm string and the severity of the alarms
based on the individual requirements of the site. Indications are
provided when the alarms are set or cleared.
Eb/No Energy per Bit/Noise floor, where Eb is the signal energy per bit
and No is the noise energy per hertz of noise bandwidth.
EBCG Elementary Basic Service Group.
EC Echo Canceller. Performs echo suppression for all voice circuits.
If cancellation does not take place, the PLMN subscriber hears
the voice signal as an echo, due to the total round-trip delay
introduced by the GSM system (typically 180 ms).
ECB Provides echo cancelling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode. A facsimile mode, in which the sending
machine will attempt to send a partial page up to four times.
Ec/No Ratio of energy per modulating bit to the noise spectral density.
ECT Event Counting Tool. The ECT provides information about the
number and type of events and alarms generated throughout the
network. It extracts data from the event log files for specified
dates, allowing the user to generate reports on individual network
elements, groups of elements, or the whole network.
ECT Explicit Call Transfer supplementary service. ECT enables a
user to connect two other parties with which he is engaged in a
telephone call and leave the connection himself.
EDGE Enhanced Data-rates for Global Evolution.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable Read Only Memory. An
EEPROM is a special type of PROM that can be erased by
exposing it to an electrical charge. Like other types of PROM,
EEPROM retains its contents even when the power is turned off.
EGPRS Enhanced GPRS.
EGSM900 Extended GSM900. EGSM900 provides the BSS with a further
range of frequencies for MS and BSS transmit. EGSM MSs can
use the extended frequency band as well as the primary band,
while non-EGSM MSs cannot use the extended frequency band.
A GSM900 cell can contain both GSM900 and EGSM900 carrier
hardware. EGSM operates on the frequency range, 880 - 915
MHz (receive) and 925 - 960 MHz (transmit).
EI Events Interface. Part of the OMC-R GUI.
EIA Electronic Industries Alliance.


EIR Equipment Identity Register. The EIR contains a centralized
database for validating the IMEI. The register consists of lists of
IMEIs organised as follows: White List - IMEIs which are known
to have been assigned to valid MS equipment. Black List - IMEIs
which have been reported stolen or which are to be denied service
for some other reason. Grey List - IMEIs which have problems
(for example, faulty software). These are not, however, sufficiently
significant to warrant a black listing.
EIRP Effective Isotropically Radiated Power. The arithmetic product of
the power supplied to an antenna and its gain.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC-R application. It provides a
centralised facility for reporting network-wide generated events
and alarms, and for monitoring the status of the Network.
EMC ElectroMagnetic Compatibility. The ability of systems, equipment,
and devices that utilize the electromagnetic spectrum to operate
in their intended operational environments without suffering
unacceptable degradation or causing unintentional degradation
because of electromagnetic radiation or response.
EMF Electro Motive Force. The rate at which energy is drawn from a
source that produces a flow of electricity in a circuit; expressed
in volts.
EMI Electro Magnetic Interference. Any electromagnetic disturbance
that interrupts, obstructs, or otherwise degrades or limits the
effective performance of electronics/electrical equipment.
eMLPP enhanced Multi-Level Precedence and Pre-emption service. This
service has two parts: precedence and pre-emption. Precedence
involves assigning a priority level to a call in combination with
fast call set-up. Pre-emption involves the seizing of resources,
which are in use by a call of a lower precedence, by a higher level
precedence call in the absence of idle resources. Pre-emption
can also involve the disconnection of an on-going call of lower
precedence to accept an incoming call of higher precedence.
EMMI Electrical Man Machine Interface.
EMX Electronic Mobile Exchange (Motorola’s MSC family).
en bloc Fr. - all at once (a CCITT #7 Digital Transmission scheme);
En bloc sending means that digits are sent from one system to
another ~ (that is, all the digits for a given call are sent at the same
time as a group). ~ sending is the opposite of overlap sending.
A system using ~ sending will wait until it has collected all the
digits for a given call before it attempts to send digits to the next
system. All the digits are then sent as a group.
EOP Enhanced One-Phase
EOT End of Tape.
EPCR EGPRS Packet Channel Request.


EPROM Erasable Programmable Read Only Memory. EPROM is a type of
memory that retains its contents until it is exposed to ultraviolet
light. The ultraviolet light clears its contents, making it possible to
re-program the memory.
EPSM Enhanced Power Supply Module. Used in +27 V positive earth
cabinets.
EQ50 Static model against which the performance of the equalizer is
tested to extremes. See also TU3, TU50, HT100 and RA250.
EQB Equalizer Board. Control circuit for equalization for 8 time slots
each with equalizing circuitry and a DSP.
EQCP Equalizer Control Processor.
EQDSP Equalizer Digitizer Signal Processor.
Equalization The process by which attenuation and/or phase shift is rendered
essentially constant over a band of frequencies, even though the
transmission medium or the equipment has losses that vary with
frequency.
Equalizer An electrical network in which attenuation (or gain) and/or
phase shift varies as a function of frequency. Used to provide
equalization.
Erlang International (dimensionless) unit of traffic intensity defined as
the ratio of time a facility is occupied to the time it is available
for occupancy. One erlang is equal to 36 CCS. In the US this is
also known as a traffic unit (TU).
ERP Ear Reference Point. Facility for assessing handset and headset
acoustic responses.
ERP Effective Radiated Power. The power supplied to an antenna
multiplied by the antenna gain in a given direction.
ERR ERRor.
ESP Electro-static Point. Connection point on the equipment for an
anti-static wrist strap.
ESQL Embedded SQL (Structured Query Language). An RDBMS
programming interface language.
E-TACS Extended TACS (analogue cellular system, extended).
Ethernet A standard protocol (IEEE 802.3) for a 10 Mbit/s baseband local
area network (LAN) bus using carrier-sense multiple access
with collision detection (CSMA/CD) as the access method,
implemented at the Physical Layer in the OSI RM, establishing
the physical characteristics of a CSMA/CD network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETSI European Telecommunications Standards Institute.
ETX End of Transmission.
EXEC Executive Process.


F Interface - Full Rate
F Interface Interface between MSC and EIR.

FA Fax Adaptor. Device which complements Group 3 facsimile
apparatus in order to be able to communicate over a GSM
PLMN.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACCH Fast Associated Control Channel. A GSM dedicated control
channel which temporarily uses the TCH to perform high speed
transmissions, and carries control information after a call is set
up. See also SDCCH.
FACCH/F Fast Associated Control Channel/Full rate. See also Full Rate.
FACCH/H Fast Associated Control Channel/Half rate. See also Half Rate.
FB See Frequency correction burst.
FBM Flow control Buffer Management. FBM is a functional unit
residing on the PRP. It controls buffer capacity for each cell
and each mobile so that the incoming data from the SGSN
matches the air throughput.
FC-AL Fibre Channel Arbitrated Loop. A serial data transfer
architecture. FC-AL is designed for mass storage devices and
other peripheral devices that require very high bandwidth.
Using optical fibre to connect devices, FC-AL supports
full-duplex data transfer rates of 100MBps.
FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction of
the MS.
FCP Fault Collection Process. Part of the fault management process
in the BTS.
FCS Frame Check Sequence. The extra characters added to a
frame for error detection and correction.
FDM Frequency Division Multiplex. A multiplexing technique that
uses different frequencies to combine multiple streams of data
for transmission over a communications medium. FDM assigns
a discrete carrier frequency to each data stream and then
combines many modulated carrier frequencies for transmission.
FDMA Frequency Division Multiple Access. The use of frequency
division to provide multiple and simultaneous transmissions
to a single transponder.
FDN Fixed Dialling Number. The fixed dialling feature limits dialling
from the MS to a pre-determined list maintained on the SIM
card. It can be used to limit calling to certain areas, exchanges
or full phone numbers.
FDP Fault Diagnostic Procedure.


FEC Forward Error Correction. Correction of transmission errors by
transmitting additional information with the original bit stream.
If an error is detected, the additional information is used to
recreate the original information.
FEP Front End Processor. An OMC-R device. The FEP is a driver
that stores data in its own database about all of the sites in the
system. All bursts from the sites are directed to the FEP. It can
also interrogate the sites and collect its data either manually or
automatically at pre-defined times.
FER Frame Erasure Ratio. The ratio of successfully decoded good
speech frames against unsuccessfully decoded bad frames.
FFS, FS For Further Study.
FH See Frequency Hopping.
FHI Frequency Hopping Indicator.
FIB Forward Indicator Bit. Used in SS7 - Message Transfer Part.
The forward indicator bit and backward indicator bit together
with the forward sequence number and backward sequence
number are used in the basic error control method to perform
the signal unit sequence control and acknowledgement
functions.
FIFO Memory logic device in which the information placed in the
memory in a given order is retrieved in that order.
FIR Finite Impulse Response (filter type).
FK Foreign Key. A database column attribute; the foreign key
indicates an index into another table.
FM Fault Management (at OMC).
FM Frequency Modulation. Modulation in which the instantaneous
frequency of a sine wave carrier is caused to depart from
the centre frequency by an amount proportional to the
instantaneous value of the modulating signal.
FMIC Fault Management Initiated Clear. An alarm type. If an FMIC
alarm is received, the fault management software for the
network item clears the alarm when the problem is solved. See
also Intermittent and OIC.
FMUX Fibre optic MUltipleXer module.
FN Frame Number. Identifies the position of a particular TDMA
frame within a hyperframe.
FOA First Office Application. A full functional verification of new
product(s) on a commercial system using accepted technology
and approved test plans.
FOX Fibre Optic eXtender board.
FR See Full Rate.
FR Frame Relay. An interface protocol for statistically
multiplexed packet-switched data communications in which
(a) variable-sized packets (frames) are used that completely
enclose the user packets they transport, and (b) transmission
rates are usually between 56 kb/s and 1.544 Mb/s (the T-1 rate).


Frame A set of consecutive Pulse Code Modulation (PCM) time slots
containing samples from all channels of a group, where the
position of each sample is identified by reference to a frame
alignment signal. Also, an information or signal structure which
allows a receiver to identify uniquely an information channel.
Frame Alignment The state in which the frame of the receiving equipment is
synchronized with respect to that of the received signal to
accomplish accurate data extraction.
FRU Field Replaceable Unit. A board, module, etc. which can be
easily replaced in the field with a few simple tools.
Frequency Correction Period of RF carrier less than one timeslot whose modulation
bit stream allows frequency correction to be performed easily
within an MS burst.
Frequency Hopping The repeated switching of frequencies during radio transmission
according to a specified algorithm. Frequency hopping
improves capacity and quality in a highly loaded GSM network.
Multipath fading immunity can be increased by using different
frequencies and interference coming from neighbour cells
transmitting the same or adjacent frequencies can be reduced.
FS Frequency Synchronization. All BSS frequencies and timing
signals are synchronized to a high stability reference oscillator
in the BSS. This oscillator can free run or be synchronized to
the recovered clock signal from a selected E1/T1 serial link.
MSs lock to a reference contained in a synchronization burst
transmitted from the BTS site.
FSL Free Space Loss. The decrease in the strength of a radio
signal as it travels between a transmitter and receiver. The
FSL is a function of the frequency of the radio signal and the
distance the radio signal has travelled from the point source.
FSN Forward Sequence Number. See FIB.
FTAM File Transfer, Access, and Management. An ASE which
provides a means to transfer information from file to file. (OMC).
ftn forwarded-to number.
FTP Fault Translation Process (in BTS).
FTP File Transfer Protocol. A client-server protocol which allows
a user on one computer to transfer files to and from another
computer over a TCP/IP network. Also the client program the
user executes to transfer files.
Full Rate Refers to the current capacity of a data channel on the GSM
air interface, that is, 8 simultaneous calls per carrier. See also
HR - Half Rate.
G Interface - GWY
G Interface Interface between VLR and VLR.

Gateway MSC An MSC that provides an entry point into the GSM PLMN
from another network or service. A gateway MSC is also an
interrogating node for incoming PLMN calls.


GB, Gbyte Gigabyte. 230 bytes = 1,073,741,824 bytes = 1024 megabytes.
GBIC Gigabit Interface Converter Converter for connection to the
Gigabit Ethernet.
GBL Gb Link.
GBM Gb Manager.
GCLK Generic Clock board. System clock source, one per site (part
of BSS, BTS, BSC, IWF, RXCDR).
GCR Group Call Register. The register which holds information
about VGCS or VBS calls.
GDP Generic DSP Processor board. Interchangeable with the
XCDR board.
GDP E1 GDP board configured for E1 link usage.
GDP T1 GDP board configured for T1 link usage.
GDS GPRS Data Stream.
GGSN Gateway GPRS Support Node. The GGSN provides internet
working with external packet-switched networks.
GHz Giga-Hertz (109).
GID Group ID. A unique number used by the system to identify a
user’s primary group.
GIP GPRS Initialization Process
GMB GSM Multiplexer Board (part of the BSC).
GMM GPRS Mobility Management.
GMR General Manual Revision.
GMSC Gateway Mobile-services Switching Centre. See Gateway
MSC.
GMSK Gaussian Minimum Shift Keying. The modulation technique
used in GSM.
GND GrouND.
GOS Grade of Service. A traffic statistic defined as the percentage
of calls which have a Probability of Busy or Queueing Delay.
An alternative criterion is a maximum time for a percentage
of calls to wait in the busy queue before they are assigned a
voice channel.
GPA GSM PLMN Area.
GPC General Protocol Converter.
GPROC Generic Processor board. GSM generic processor board: a
68030 with 4 to 16 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPROC2 Generic Processor board. GSM generic processor board: a
68040 with 32 Mb RAM (part of BSS, BTS, BSC, IWF, RXCDR).
{4354} GPROC3 Generic Processor board. GSM generic processor board:
a 68060 with 128 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).


GPRS General Packet Radio Service. A GSM data transmission
technique that does not set up a continuous channel from a
portable terminal for the transmission and reception of data, but
transmits and receives data in packets. It makes very efficient
use of available radio spectrum, and users pay only for the
volume of data sent and received.
GPS Global Positioning by Satellite. A system for determining
position on the Earth’s surface by comparing radio signals from
several satellites.
GR Gb Router.
GSA GSM Service Area. The area in which an MS can be reached
by a fixed subscriber, without the subscriber’s knowledge of the
location of the MS. A GSA may include the areas served by
several GSM PLMNs.
GSA GSM System Area. The group of GSM PLMN areas accessible
by GSM MSs.
GSD GSM Systems Division.
GSL GPRS Signalling Link.
GSM Groupe Spécial Mobile (the committee).
GSM Global System for Mobile communications (the system).
GSM900 See PGSM.
GSM MS GSM Mobile Station.
GSM PLMN GSM Public Land Mobile Network.
GSM RF GSM Radio Frequency.
GSN GPRS Support Node. The combined functions provided by
the SGSN and GGSN.
GSN Complex A GSN Complex consists of an ISS Cluster, GGSN and SGSNs
connected to a single CommHub.
GSR GSM Software Release.
GT Global Title. A logical or virtual address used for routing SS7
messages using SCCP capabilities. To complete message
routing, a GT must be translated to a SS7 point code and
subsystem number.
GTM Gb Transmit Manager.
GTE Generic Table Editor. The Motorola procedure which allows
users to display and edit MCDF input files.
GTS GBRS TBF Scheduler
Guard period Period at the beginning and end of timeslot during which MS
transmission is attenuated.
GUI Graphical User Interface. A computer environment or program
that displays, or facilitates the display of, on-screen options.
These options are usually in the form of icons (pictorial
symbols) or menus (lists of alphanumeric characters) by means
of which users may enter commands.


GUI client A computer used to display a GUI from an OMC-R GUI
application which is being run on a GUI server.
GUI server A computer used to serve the OMC-R GUI application process
running locally (on its processor) to other computers (GUI
clients or other MMI processors).
GWM GateWay Manager.
GWY GateWaY (MSC/LR) interface to PSTN.
H Interface - Hyperframe
H Interface Interface between HLR and AUC.

H-M Human-Machine Terminals.
HAD, HAP HLR Authentication Distributor.
Half Rate Refers to a type of data channel that will double the current
GSM air interface capacity to 16 simultaneous calls per carrier
(see also FR - Full Rate).
HANDO, Handover HANDOver. The action of switching a call in progress from
one radio channel to another radio channel. Handover allows
established calls to continue by switching them to another
radio resource, as when an MS moves from one BTS area to
another. Handovers may take place between the following
GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.
HCU Hybrid Combining Unit. (Used in Horizonmacro). Part of
the DDF, the HDU allows the outputs of three radios to be
combined into a single antenna.
HDLC High level Data Link Control. A link-level protocol used to
facilitate reliable point-to-point transmission of a data packet.
Note: A subset of HDLC, LAP-B, is the layer-two protocol for
CCITT Recommendation X.25.
HDSL High bit-rate Digital Subscriber Line. HDSL is a data
transmission mechanism which supports duplex high speed
digital communication (at E1 rates) on one or more unshielded
twisted pair lines.
HLC High Layer Compatibility. The HLC can carry information
defining the higher layer characteristics of a teleservice active
on the terminal.
HLR Home Location Register. The LR where the current location
and all subscriber parameters of an MS are permanently stored.
HMS Heat Management System. The system that provides
environmental control of the components inside the ExCell,
TopCell and M-Cell cabinets.
HO HandOver. See HANDO.
HPU Hand Portable Unit. A handset.


HOLD Call hold supplementary service. Call hold allows the
subscriber to place a call on hold in order to make another call.
When the second call is completed, the subscriber can return
to the first call.
HPLMN Home PLMN.
HR See Half Rate.
HS HandSet.
HSI/S High Speed Interface card.
HSM HLR Subscriber Management.
HSN Hopping Sequence Number. HSN is a index indicating the
specific hopping sequence (pattern) used in a given cell. It
ranges from 0 to 63.
HT100 Hilly Terrain with the MS travelling at 100 kph. Dynamic model
against which the performance of a GSM receiver can be
measured. See also TU3, TU50, RA250 and EQ50.
HU Home Units. The basic telecommunication unit as set by the
HPLMN. This value is expressed in the currency of the home
country.
HW Hardware.
Hybrid Combiner A combiner device which requires no software control and is
sufficiently broadband to be able to cover the GSM transmitter
frequency band. See also COMB.
Hybrid Transformer A circuit used in telephony to convert 2-wire operation to
4-wire operation and vice versa. For example, every land-line
telephone contains a hybrid to separate earpiece and
mouthpiece audio and couple both into a 2-wire circuit that
connects the phone to the exchange.
Hyperframe 2048 superframes. The longest recurrent time period of the
frame structure.
I - IWU
I Information frames. Part of RLP.

IA Incoming Access supplementary service. An arrangement
which allows a member of a CUG to receive calls from outside
the CUG.
IA5 International Alphanumeric 5 character set.
IADU Integrated Antenna Distribution Unit. The IADU is the
equivalent of the Receive Matrix used on BTSs that pre-date
the M-Cell range.
IAM Initial Address Message. A message sent in the forward
direction that contains (a) address information, (b) the signaling
information required to route and connect a call to the called
line, (c) service-class information, (d) information relating to
user and network facilities, and (e) call-originator identity or
call-receiver identity.


IAS Internal Alarm System. The IAS is responsible for monitoring
all cabinet alarms at a BSS.
IC Integrated Circuit. An electronic circuit that consists of
many individual circuit elements, such as transistors,
diodes, resistors, capacitors, inductors, and other active and
passive semiconductor devices, formed on a single chip of
semiconducting material and mounted on a single piece of
substrate material.
IC Interlock Code. A code which uniquely identifies a CUG within
a network.
IC(pref) Interlock Code of the preferential CUG.
ICB Incoming Calls Barred. An access restriction that prevents a
CUG member from receiving calls from other members of that
group.
ICC Integrated Circuit(s) Card.
ICM In-Call Modification. Function which allows the service mode
(speech, facsimile, data) to be changed during a call.
ICMP Internet Control Message Protocol. An extension to the Internet
Protocol (IP) that allows for the generation of error messages,
test packets, and informational messages related to IP. The
PING command, for example, uses ICMP to test an Internet
connection.
ID, Id IDentification/IDentity/IDentifier.
IDN Integrated Digital Network. A network that uses both digital
transmission and digital switching.
IDS Interface Design Specification.
IDS Informix Dynamic Server. The OMC-R relational database
management system.
IE Information Element. The part of a message that contains
configuration or signalling information.
IEC International Electrotechnical Commission. An international
standards and conformity assessment body for electrical,
electronic and related technologies.
IEEE Institute of Electrical and Electronic Engineers. A non-profit,
technical professional association.
IEI Information Element Identifier. The identifier field of the IE.
I-ETS Interim European Telecommunication Standard.
IF Intermediate Frequency. A frequency to which a carrier
frequency is shifted as an intermediate step in transmission
or reception.
IFAM Initial and Final Address Message.
IM InterModulation. The production, in a nonlinear element of a
system, of frequencies corresponding to the sum and difference
frequencies of the fundamentals and harmonics thereof that
are transmitted through the element.
IMACS Intelligent Monitor And Control System.


IMEI International Mobile station Equipment Identity. Electronic
serial number that uniquely identifies the MS as a piece or
assembly of equipment. The IMEI is sent by the MS along with
request for service. See also IMEISV.
IMEISV International Mobile station Equipment Identity and Software
Version number. The IMEISV is a 16 digit decimal number
composed of four elements:- a 6 digit Type Approval Code; - a
2 digit Final Assembly Code; - a 6 digit Serial Number; and - a
2 digit Software Version Number (SVN).
The first three elements comprise the IMEI. When the network
requests the IMEI from the MS, the SVN (if present) is also sent
towards the network. See also IMEI and SVN.
IMM IMMediate assignment message. IMMs are sent from the
network to the MS to indicate that the MS must immediately
start monitoring a specified channel.
IMSI International Mobile Subscriber Identity. Published mobile
number (prior to ISDN) that uniquely identifies the subscription.
It can serve as a key to derive subscriber information such as
directory number(s) from the HLR. See also MSISDN.
IN Intelligent Network. A network that allows functionality to
be distributed flexibly at a variety of nodes on and off the
network and allows the architecture to be modified to control
the services.
IN Interrogating Node. A switching node that interrogates an HLR,
to route a call for an MS to the visited MSC.
INS IN Service.
INS Intelligent Network Service. A service provided using the
capabilities of an intelligent network. See also IN.
InterAlg Interference Algorithm.
Intermittent Intermittent alarms are transient and not usually associated
with a serious fault condition. After the intermittent alarms are
displayed in the Alarm window, the operator must handle and
clear the alarm. The system will report every occurrence of an
intermittent alarm unless it is throttled. See also FMIC and OIC.
Interworking The general term used to describe the inter-operation of
networks, services, supplementary services and so on. See
also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Service. Tool for improving the network
quality. The IOS generates reports based on performance data
from the BTS and OMC-R.
IP Initialisation Process. The IP is primarily responsible for
bringing up the site from a reset, including code loading
the site from a suitable code source. IP also provides the
CSFP functionality, allowing two BSS code load version to be
swapped very quickly, allowing the site to return to service as
soon as possible.


IP Internet Protocol. A standard protocol designed for use
in interconnected systems of packet-switched computer
communication networks. IP provides for transmitting blocks
of data called datagrams from sources to destinations,
where sources and destinations are hosts identified by
fixed-length addresses. The internet protocol also provides for
fragmentation and reassembly of long datagrams, if necessary,
for transmission through small-packet networks. See also TCP
and TCP/IP.
IPC Inter-Process Communication. Exchange of data between one
process and another, either within the same computer or over
a network.
IP, INP INtermodulation Products. Distortion. A type of spurious
emission.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (-48 V).
IPX Internetwork Packet EXchange A networking protocol used by
the Novell NetWare operating systems. Like UDP/IP, IPX is a
datagram protocol used for connectionless communications.
Higher-level protocols are used for additional error recovery
services.
IR Incremental Redundancy (Hybrid Type II ARQ)
Iridium A communications system comprising a constellation of 66
low-earth-orbiting (LEO) satellites forming a mobile wireless
system allowing subscribers to place and receive calls from any
location in the world. The satellite constellation is connected
to existing terrestrial telephone systems through a number of
gateway ground-stations.
ISAM Indexed Sequential Access Method. A method for managing
the way a computer accesses records and files stored on a
hard disk. While storing data sequentially, ISAM provides direct
access to specific records through an index. This combination
results in quick data access regardless of whether records are
being accessed sequentially or randomly.
ISC International Switching Centre. The ISC routes calls to/from
other countries.
ISDN Integrated Services Digital Network. A digital network using
common switches and digital transmission paths to establish
connections for various services such as telephony, data telex,
and facsimile. See also B channel and D channel.
ISG Motorola Information Systems group (formerly CODEX).
ISO International Organisation for Standardization. ISO is a
world-wide federation of national standards bodies from some
130 countries, one from each country.
ISQL An Interactive Structured Query Language client application for
the database server. See also IDS.
ISS Integrated Support Server. The ISS resides on a Sun Netra
t 1125 and performs the CGF, DNS, NTP, and NFS functions
for the GSN.


IST Integrated System Test.
ISUP ISDN User Part. An upper-layer application supported by
signalling system No. 7 for connection set up and tear down.
IT Inactivity Test (Part of SCCP network connectivity).
ITC Information Transfer Capability. A GSM Bearer Capability
Element which is provided on the Dm channel to support
Terminal adaptation function to Interworking control procedures.
ITU International Telecommunication Union. An intergovernmental
organization through which public and private organizations
develop telecommunications. It is responsible for adopting
international treaties, regulations and standards governing
telecommunications.
ITU-T International Telecommunication Union - Telecommunications
Standardization Sector. The standardization functions were
formerly performed by CCITT, a group within the ITU.
IWF InterWorking Function. A network functional entity which
provides network interworking, service interworking,
supplementary service interworking or signalling interworking.
It may be a part of one or more logical or physical entities in a
GSM PLMN.
IWMSC InterWorking MSC. MSC that is used to deliver data to/from
SGSN.
IWU InterWorking Unit. Unit where the digital to analogue (and visa
versa) conversion takes place within the digital GSM network.


k - KW
k kilo (103).
k Windows size.
K Constraint length of the convolutional code.
KAIO Kernel Asynchronous Input/Output. Part of the OMC-R
relational database management system.
kb, kbit kilo-bit.
kbit/s, kbps kilo-bits per second.
kbyte kilobyte. 210 bytes = 1024 bytes
Kc Ciphering key. A sequence of symbols that controls the
operation of encipherment and decipherment.
kHz kilo-Hertz.
Ki Individual subscriber authentication Key. Part of the
authentication process of the AUC.
KIO A class of processor.
KPI Key Performance Indicator.
KSW Kiloport SWitch board. TDM timeslot interchanger to connect
calls. Part of the BSS.
KSWX KSW Expander half size board. Fibre optic distribution of TDM
bus. Part of the BSS.
kW kilo-Watt.
L1 - LV
L1 Layer 1 (of a communications protocol).

L2ML Layer 2 Management Link. L2ML is used for transferring layer
2 management messages to TRX or BCF. One link per TRX
and BCF.
L2R Layer 2 Relay function. A function of an MS and IWF that
adapts a user’s known layer 2 protocol LAPB onto RLP for
transmission between the MT and IWF.
L2R BOP L2R Bit Orientated Protocol.
L2R COP L2R Character Orientated Protocol.
LA Link Adaptation.
LA Location Area. An area in which an MS may move freely
without updating the location register. An LA may comprise one
or several base station areas.


LAC Location Area Code. The LAC is part of the LAI. It is an
operator defined code identifying the location area.
LAI Location Area Identity. The information indicating the location
area in which a cell is located. The LAI data on the SIM is
continuously updated to reflect the current location of the
subscriber.
LAN Local Area Network. A data communications system that (a)
lies within a limited spatial area, (b) has a specific user group,
(c) has a specific topology, and (d) is not a public switched
telecommunications network, but may be connected to one.
LANX LAN Extender half size board. Fibre optic distribution of LAN
to/from other cabinets. Part of BSS, etc.
LAPB Link Access Protocol Balanced. The balanced-mode, enhanced
version of HDLC. Used in X.25 packet-switching networks.
LAPD Link Access Protocol D-channel (Data). A protocol that
operates at the data link layer (layer 2) of the OSI architecture.
LAPD is used to convey information between layer 3 entities
across the frame relay network. The D-channel carries
signalling information for circuit switching.
LAPDm Link Access Protocol on the Dm channel. A link access
procedure (layer 2) on the CCH for the digital mobile
communications system.
Layer 1 See OSI-RM and Physical Layer.
Layer 2 See OSI-RM and Data Link Layer.
Layer 3 See OSI-RM and Network Layer.
Layer 4 See OSI-RM and Transport Layer.
Layer 5 See OSI-RM and Session Layer.
Layer 6 See OSI-RM and Presentation Layer.
Layer 7 See OSI-RM and Application Layer.
LC Inductor Capacitor. A type of filter.
LCF Link Control Function. LCF GPROC controls various links in
and out of the BSC. Such links include MTL, XBL, OMF and
RSL. See also LCP.
LCN Local Communications Network. A communication network
within a TMN that supports data communication functions
(DCFs) normally at specified reference points q1 and q2. LCNs
range from the simple to the complex. LCN examples include
point-to-point connections and networks based on star and
bus topologies.
LCP Link Control Processor. An LCP is a GPROC or PCMCIA
board device which supplies the LCF. Once the LCF has been
equipped, and assuming GPROCs have been equipped,
processors are allocated by the software.
LCS Location Services
LE Local Exchange.


LED Light Emitting Diode. A type of diode that emits light when
current passes through it. Depending on the material used the
colour can be visible or infrared.
LF Line Feed. A code that moves the cursor on a display screen
down one line. In the ASCII character set, a line feed has a
decimal value of 10. On printers, a line feed advances the
paper one line.
LI Length Indicator. Delimits LLC PDUs within the RLC data
block, when an LLC PDU boundary occurs in the block.
LI Line Identity. The LI is made up of a number of information
units: the subscriber’s national ISDN/MSISDN number; the
country code; optionally, subaddress information. In a full
ISDN environment, the line identity includes all of the address
information necessary to unambiguously identify a subscriber.
The calling line identity is the line identity of the calling party.
The connected line identity is the line identity of the connected
party.
LLC Logical Link Control.
LLC Lower Layer Compatibility. The LLC can carry information
defining the lower layer characteristics of the terminal.
Lm Traffic channel with capacity lower than a Bm.
LMP LAN Monitor Process. Each GPROC which is connected to a
LAN has an LMP, which detects faults on the LAN. LAN alarms
are generated by the GPROC.
LMS Least Mean Squares. Parameters determined by minimizing
the sum of squares of the deviations.
LMSI Local Mobile Station Identity. A unique identity temporarily
allocated to visiting mobile subscribers in order to speed up
the search for subscriber data in the VLR, when the MSRN
allocation is done on a per cell basis.
LMT Local Maintenance Terminal. Diagnostic tool, typically an IBM
compatible PC.
LNA Low Noise Amplifier. An amplifier with low noise characteristics.
LND Last Number Dialled.
Location area An area in which a mobile station may move freely without
updating the location register. A location area may comprise
one or several base station areas.
LPC Linear Predictive Coding. A method of digitally encoding analog
signals. It uses a single-level or multi-level sampling system in
which the value of the signal at each sample time is predicted
to be a linear function of the past values of the quantified signal.
LPLMN Local PLMN.
LQC Link Quality Control.
LR Location Register. The GSM functional unit where MS location
information is stored. The HLR and VLR are location registers.
LSSU Link Stations Signalling Unit (Part of MTP transport system).


LSTR Listener Side Tone Rating. A rating, expressed in dB, based
on how a listener will perceive the background noise picked
up by the microphone.
LTA Long Term Average. The value required in a BTS’s GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
LU Local Units.
LU Location Update. A location update is initiated by the MS when
it detects that it has entered a new location area.
LV Length and Value.
M - MUX
M Mandatory.
M Mega (106).
M-Cell Motorola Cell.
M&TS Maintenance and TroubleShooting. Functional area of Network
Management software which (1) collects and displays alarms,
(2) collects and displays Software/Hardware errors, and (3)
activates test diagnostics at the NEs (OMC).
MA Mobile Allocation. The radio frequency channels allocated to
an MS for use in its frequency hopping sequence.
MAC Medium Access Control. MAC includes the functions related
to the management of the common transmission resources.
These include the packet data physical channels and their
radio link connections. Two Medium Access Control modes are
supported in GSR5, dynamic allocation and fixed allocation.
MACN Mobile Allocation Channel Number. See also MA.
Macrocell A cell in which the base station antenna is generally mounted
away from buildings or above rooftop level.
MAF Mobile Additional Function.
MAH Mobile Access Hunting supplementary service. An automatic
service which searches for the first available mobile user out of
a defined group.
MAI Mobile Allocation Index.
MAIDT Mean Accumulated Intrinsic Down Time.
MAINT MAINTenance.
MAIO Mobile Allocation Index Offset. The offset of the mobile hopping
sequence from the reference hopping sequence of the cell.
MAP Mobile Application Part (part of SS7 standard). The
inter-networking signalling between MSCs and LRs and EIRs.


MAPP Mobile Application Part Processor.
MB, Mbyte Megabyte. 220 bytes = 1,048,576 bytes = 1024 kilobytes.
Mbit/s Megabits per second.
MCAP Motorola Cellular Advanced Processor. The MCAP Bus is the
inter-GPROC communications channel in a BSC. Each card
cage in a BSC needs at least one GPROC designated as an
MCAP Server.
MCC Mobile Country Code. The first three digits of the IMSI, used
to identify the country.
MCDF Motorola Customer Data Format used by DataGen for simple
data entry and retrieval.
MCI Malicious Call Identification supplementary service. This
feature is supported by a malicious call trace function by
printing the report at the terminating MSC when the mobile
subscriber initiates a malicious call trace request.
MCS Modulation and Coding Scheme.
MCSC Motorola Customer Support Centre.
MCU Main Control Unit for M-Cell2/6. Also referred to as the Micro
Control Unit in software.
MCUF Main Control Unit, with dual FMUX. (Used in M-Cellhorizon).
MCU-m Main Control Unit for M-Cellmicro sites (M-Cellm). Also referred
to as the Micro Control Unit in software.
MCUm The software subtype representation of the Field Replaceable
Unit (FRU) for the MCU-m.
MD Mediation Device. The MD (which handles the Q3 interface)
allows the OSI Processor to communicate between the
Network Management Centre (NMC) and OMC-R for network
configuration, events and alarms.
MDL mobile Management entity - Data Link layer.
ME Maintenance Entity (GSM Rec. 12.00).
ME Mobile Equipment. Equipment intended to access a set of GSM
PLMN and/or DCS telecommunication services, but which does
not contain subscriber related information. Services may be
accessed while the equipment, capable of surface movement
within the GSM system area, is in motion or during halts at
unspecified points.
MEF Maintenance Entity Function (GSM Rec. 12.00). A function
which possesses the capability to detect elementary anomalies
and convey them to the supervision process.
MF MultiFrame. In PCM systems, a set of consecutive frames in
which the position of each frame can be identified by reference
to a multiframe alignment signal.
MF Multi-Frequency (tone signalling type). See DTMF.
MF MultiFunction block.
MGMT, mgmt Management.


MGR Manager.
MHS Message Handling System. The family of services and
protocols that provides the functions for global electronic-mail
transfer among local mail systems.
MHS Mobile Handling Service.
MHz Mega-Hertz (106).
MI Maintenance Information.
MIB Management Information Base. A Motorola OMC-R database.
There is a CM MIB and an EM MIB.
MIC Mobile Interface Controller.
Microcell A cell in which the base station antenna is generally mounted
below rooftop level. Radio wave propagation is by diffraction
and scattering around buildings, the main propagation is within
street canyons.
min minute(s).
µs micro-second (10-6).
µBCU Micro Base Control Unit. The µBCU is the Macro/Microcell
implementation of a BTS site controller.
MIT Management Information Tree. A file on the Motorola OMC-R.
The MIT file effectively monitors data on every device and
every parameter of each device that is in the current versions
of software on the OMC-R. The data is stored as a text file
on the OMC-R. The MIT file also contains the hierarchical
relationships between the network devices.
MM Man Machine. See MMI.
MM Mobility Management. MM functions include authorization,
location updating, IMSI attach/detach, periodic registration, ID
confidentiality, paging, handover, etc.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method by which the user
interfaces with the software to request a function or change
parameters. The MMI may run on a terminal at the OMC, or
an LMT. The MMI is used to display alarm reports, retrieve
device status, take modules out of service and put modules
into service.
MMI client A machine configured to use the OMC-R software from an MMI
server.
MMI processor MMI client/MMI server.
MMI server A computer which has its own local copy of the OMC-R
software. It can run the OMC-R software for MMI clients to
mount.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (see also 2Mbit/s link)


MNC Mobile Network Code. The fourth, fifth and optionally sixth
digits of the IMSI, used to identify the network.
MNT MaiNTenance.
Mobis Motorola Signalling Link between the BSC and BTS.
MO Mobile Originated.
MO/PP Mobile Originated Point-to-Point messages. Transmission of
a SMS from a mobile to a message handling system. The
maximum length of the message is 160 characters. The
message can be sent whether or not the MS is engaged in
a call.
MOMAP Motorola OMAP.
MoU Memorandum of Understanding. Commercial term. An MoU
usually sets out the broad parameters of an understanding as
well as the general responsibilities and obligations of each
party in a proposed venture. It has little legal significance
except to indicate the parties’ commitments and acts as an aid
to interpreting the parties’ intentions. There are various types
of MOUs: compliance MOUs help ensure that all Motorola
units comply with applicable laws and regulations; intellectual
property MOUs deal with copyright, trademark, and patent
rights; and business arrangement MOUs relate to the terms
and conditions of a product or service transfer.
MPC Multi Personal Computer (was part of the OMC).
MPH (mobile) Management (entity) - PHysical (layer) [primitive].
MPROC Master Processor
MPTY MultiParTY (Multi ParTY) supplementary service. MPTY
provides a mobile subscriber with the ability to have a
multi-connection call, i.e. a simultaneous communication with
more than one party.
MPX MultiPleXed.
MRC Micro Radio Control Unit.
MRN Mobile Roaming Number.
MRP Mouth Reference Point. Facility for assessing handset and
headset acoustic responses.
MS Mobile Station. The GSM subscriber unit. A subscriber
handset, either mobile or portable, or other subscriber
equipment, such as facsimile machines, etc.
MSC Mobile-services Switching Centre, Mobile Switching Centre.
The MSC handles the call set up procedures and controls the
location registration and handover procedures for all except
inter-BTS, inter-cell and intra-cell handovers. MSC controlled
inter-BTS handovers can be set as an option at the switch.
MSCM Mobile Station Class Mark.
MSCU Mobile Station Control Unit.
msec millisecond (.001 second).


MSI Multiple Serial Interface board. Intelligent interface to two 2
Mbit/s digital links. See 2 Mbit/s link and DS-2. Part of BSS.
MSIN Mobile Station Identification Number. The part of the IMSI
identifying the mobile station within its home network.
MSISDN Mobile Station International ISDN Number. Published mobile
number (see also IMSI). Uniquely defines the mobile station as
an ISDN terminal. It consists of three parts: the Country Code
(CC), the National Destination Code (NDC) and the Subscriber
Number (SN).
MSRN Mobile Station Roaming Number. A number assigned by the
MSC to service and track a visiting subscriber.
MSU Message Signal Unit (Part of MTP transport system). A signal
unit containing a service information octet and a signalling
information field which is retransmitted by the signalling link
control, if it is received in error.
MT Mobile Terminated. Describes a call or short message destined
for an MS.
MT (0, 1, 2) Mobile Termination. The part of the MS which terminates the
radio transmission to and from the network and adapts terminal
equipment (TE) capabilities to those of the radio transmission.
MT0 is mobile termination with no support for terminal, MT1
is mobile termination with support for an S-type interface and
MT2 is mobile termination with support for an R-type interface.
MTBE Mean Time Between Exceptions.
MTBF Mean Time Between Failures. An indicator of expected system
reliability calculated on a statistical basis from the known failure
rates of various components of the system. MTBF is usually
expressed in hours.
MTL Message Transfer Link. The MTL is the 64 kbit/s PCM timeslot
that is used to convey the SS7 signalling information on the A
interface between the MSC and the BSC.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part. The part of a common-channel
signaling system that transfers signal messages and performs
associated functions, such as error control and signaling link
security.
MT/PP Mobile Terminated Point-to-Point messages. Transmission of a
short message from a message handling system to a mobile.
The maximum length of the message is 160 characters. The
message can be received whether or not the MS is engaged in
a call.
MTTR Mean Time To Repair. The total corrective maintenance time
divided by the total number of corrective maintenance actions
during a given period of time.
Multiframe Two types of multiframe are defined in the system: a 26-frame
multiframe with a period of 120 ms and a 51-frame multiframe
with a period of 3060/13 ms.
MU Mark Up.


MUMS Multi User Mobile Station.
MUX Multiplexer. A device that combines multiple inputs into an
aggregate signal to be transported via a single transmission
channel.
NACK - nW
NACK, Nack No Acknowledgement

N/W Network.
NB Normal Burst (see Normal burst).
NBIN A parameter in the frequency hopping sequence generation
algorithm.
NCC Network Colour Code. The NCC and the BCC are part of the
BSIC. The NCC comprises three bits in the range 000 to 111.
It is the same as the PLMN Colour Code. See also NCC and
BSIC.
NCELL Neighbouring (of current serving) Cell.
NCH Notification CHannel. Part of the downlink element of the
CCCH reserved for voice group and/or voice broad-cast calls
and notification messages.
NCRM Network Cell Reselection Manager.
ND No Duplicates. A database column attribute meaning the
column contains unique values (used only with indexed
columns).
NDC National Destination Code. Part of the MSISDN. An NDC is
allocated to each GSM PLMN.
NDUB Network Determined User Busy. An NDUB condition occurs
when a call is about to be offered and the maximum number of
total calls for the channel has been reached. In practice, the
total number of calls could be three: one for the basic call, one
for a held call and one for call waiting.
NE Network Element (Network Entity). A piece of
telecommunications equipment that provides support or
services to the user.
NEF Network Element Function block. A functional block that
communicates with a TMN for the purpose of being monitored,
or controlled, or both.
NET Norme Européennes de Telecommunications.
NetPlan An RF planning tool, NetPlan can import data from the OMC
and use it to carry out a network frequency replan.


Network Layer See OSI RM. The Network Layer responds to service requests
from the Transport Layer and issues service requests to the
Data Link Layer. It provides the functional and procedural
means of transferring variable length data sequences from
a source to a destination via one or more networks while
maintaining the quality of service requested by the Transport
Layer. The Network Layer performs network routing, flow
control, segmentation/desegmentation, and error control
functions.
NF Network Function.
NFS Network File System. A file system that is distributed over a
computer network. Also, a file system, on a single computer,
that contains the low-level networking files for an entire network.
NHA Network Health Analyst. The NHA is an optional feature. It
detects problems by monitoring network statistics and events
via the OMC-R. The NHA analyses the event history, statistics
and network configuration data to try to determine the cause of
the detected problems.
NIB Network Interface Board.
NIC Network Interface Card. A network interface device in the form
of a circuit card that provides network access.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralised control of
network information for example hostnames, IP addresses and
passwords.
N-ISDN Narrowband Integrated Services Digital Network: Services
include basic rate interface (2B+D or BRI) and primary rate
interface (30B+D - Europe and 23B+D - North America or PRI).
Supports narrowband speeds at/or below 1.5 Mbps.
NIU Network Interface Unit. A device that performs interface
functions, such as code conversion, protocol conversion, and
buffering, required for communications to and from a network.
NIU-m Network Interface Unit, micro. M-Cellmicro MSI.
NL See Network Layer.
NLK Network LinK processor(s).
Nm Newton metres.
NM Network Management (manager). NM is all activities which
control, monitor and record the use and the performance of
resources of a telecommunications network in order to provide
telecommunication services to customers/users at a certain
level of quality.
NMASE Network Management Application Service Element.
NMC Network Management Centre. The NMC node of the GSM
TMN provides global and centralised GSM PLMN monitoring
and control, by being at the top of the TMN hierarchy and linked
to subordinate OMC nodes.


NMSI National Mobile Station Identification number, or, National
Mobile Subscriber Identity. The NMSI consists of the MNC and
the MSIN.
NMT Nordic Mobile Telephone system. NMT produced the world’s
first automatic international mobile telephone system.
NN No Nulls. A database column attribute meaning the column
must contain a value in all rows.
Normal burst A period of modulated carrier less than a timeslot.
NPI Number Plan Identifier.
NRZ Non Return to Zero. A code in which ones are represented by
one significant condition and zeros are represented by another,
with no neutral or rest condition.
NSAP Network Service Access Point. An NSAP is a registration made
by an application which specifies its desired listening criteria.
The registration is limited to a particular CPU and port number.
Criteria can include: DNICs, national numbers, subaddress
ranges, protocol-ids, and extended addresses.
NSP Network Service Provider. A national or regional company
that owns or maintains a portion of the network and resells
connectivity.
NSS Network Status Summary. A feature of the OMC-R MMI,
which provides different network maps giving visual indication
of the network configuration and performance, and how the
different network management functions are implemented by
the OMC-R.
NST Network Service Test(er). A PCU process that periodically tests
all alive NS-VCs on a PICP board.
NS-VC Network Service - Virtual Circuit.
NT Network Termination. Network equipment that provides
functions necessary for network operation of ISDN access
protocols.
NT Non Transparent.
NTAAB NTRAC Type Approvals Advisory Board. Committee engaged
in harmonisation type approval of telecom terminals in Europe.
NTP Network Time Protocol. A protocol built on top of TCP/IP that
assures accurate local timekeeping with reference to radio,
atomic or other clocks located on the Internet. This protocol is
capable of synchronizing distributed clocks within milliseconds
over long time periods.
Numbers # - The symbol used for number.2 Mbit/s link - As used in
this manual set, the term applies to the European 4-wire
2.048 Mbit/s digital line or link which can carry 30 A-law PCM
channels or 120 16 kbit/s GSM channels.4GL - 4th Generation
Language. Closer to human languages than typical high-level
programming languages. most 4GLs are used to access
databases.
NUA Network User Access.
NUI Network User Identification.


NUP National User Part. (part of SS7).
NV NonVolatile.
NVRAM Non-Volatile Random Access Memory. Static random access
memory which is made into non-volatile storage either by
having a battery permanently connected, or, by saving its
contents to EEPROM before turning the power off and
reloading it when power is restored.
nW Nano-Watt (10-9).
O - Overlap
O Optional.
OA Outgoing Access supplementary service. An arrangement
which allows a member of a CUG to place calls outside the
CUG.
OA&M Operation, Administration, & Management.
OAMP Operation, Administration, Maintenance, and Provisioning.
O&M Operations and Maintenance.
OASCU Off-Air-Call-Set-Up. The procedure in which a
telecommunication connection is being established whilst the
RF link between the MS and the BTS is not occupied.
OCB Outgoing Calls Barred within the CUG supplementary service.
An access restriction that prevents a CUG member from
placing calls to other members of that group.
OCXO Oven Controlled Crystal Oscillator. High stability clock source
used for frequency synchronization.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
offline IDS shutdown state.
online IDS normal operating state.
OIC Operator Initiated Clear. An alarm type. OIC alarms must be
cleared by the OMC-R operator after the fault condition that
caused the alarm is resolved. See also FMIC and Intermittent.
OLM Off_Line MIB. A Motorola DataGen database, used to modify
and carry out Radio Frequency planning on multiple BSS
binary files.
OLR Overall Loudness Rating.
OMAP Operations and Maintenance Application Part (part of SS7
standard) (was OAMP).
OMC Operations and Maintenance Centre. The OMC node of the
GSM TMN provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area controlled
by the specific OMC.
OMC-G Operations and Maintenance Centre - Gateway Part. (Iridium)


OMC-G Operations and Maintenance Centre - GPRS Part.
OMC-R Operations and Maintenance Centre - Radio Part.
OMC-S Operations and Maintenance Centre - Switch Part.
OMF Operations and Maintenance Function (at BSC).
OML Operations and Maintenance Link. The OML provides
communication between an OMC-R and a BSC or RXCDR for
transferring network management (O&M) data.
OMP Operation and Maintenance Processor. Part of the BSC.
OMS Operation and Maintenance System (BSC-OMC).
OMSS Operation and Maintenance SubSystem.
OOS Out Of Service. Identifies a physical state. The OOS state
indicates the physical device is out of service. This state is
reserved for physical communication links. Also, identifies a
telephony state. The OOS state is used by the BTS device
software to indicate that the BTS is completely out of service.
OPC Originating Point Code. A part of the label in a signalling
message that uniquely identifies, in a signalling network, the
(signalling) origination point of the message.
ORAC Olympus Radio Architecture Chipset.
OS Operating System. The fundamental program running on a
computer which controls all operations.
OSI Open Systems Interconnection. The logical structure for
communications networks standardized by the ISO. The
standard enables any OSI-compliant system to communicate
and exchange information with any other OSI-compliant
system.
OSI RM OSI Reference Model. An abstract description of the digital
communications between application processes running in
distinct systems. The model employs a hierarchical structure of
seven layers. Each layer performs value-added service at the
request of the adjacent higher layer and, in turn, requests more
basic services from the adjacent lower layer:Layer 1 - Physical
Layer, Layer 2 - Data Link Layer, Layer 3 - Network Layer,
Layer 4 - Transport Layer, Layer 5 - Session Layer, Layer 6 -
Presentation Layer, Layer 7 - Application Layer.
OSF Operation Systems Function block.
OSF/MOTIF Open Software Foundation Motif. The basis of the GUI used
for the Motorola OMC-R MMI.
OSS Operator Services System.
Overlap Overlap sending means that digits are sent from one system to
another as soon as they are received by the sending system. A
system using ~ will not wait until it has received all digits of a
call before it starts to send the digits to the next system. This
is the opposite of en bloc sending where all digits for a given
call are sent at one time. See en bloc.


PA - PXPDN
P1, P2, P3 Puncturing Schemes 1, 2, and 3.

PA Power Amplifier.
PAB Power Alarm Board. Part of the BSS.
PABX Private Automatic Branch eXchange. A private automatic
telephone exchange that allows calls within the exchange and
also calls to and from the public telephone network.
PACCH Packet Associated Control Channel.
Packet A sequence of binary digits, including data and control signals,
that is transmitted and switched as a composite whole.
Packet Switching The process of routing and transferring data by means of
addressed packets so that a channel is occupied during the
transmission of the packet only, and upon completion of the
transmission the channel is made available for the transfer of
other traffic.
PAD Packet Assembler/Disassembler facility. A hardware device
that allows a data terminal that is not set up for packet switching
to use a packet switching network. It assembles data into
packets for transmission, and disassembles the packets on
arrival.
Paging The procedure by which a GSM PLMN fixed infrastructure
attempts to reach an MS within its location area, before any
other network-initiated procedure can take place.
PATH CEPT 2 Mbit/s route through the BSS network.
PBCCH Packet Braodcast Control channel.
PBUS Processor Bus.
PBX Private Branch eXchange. In the general use of the term, PBX
is a synonym for PABX. However, a PBX operates with only a
manual switchboard; a private automatic exchange (PAX) does
not have a switchboard, a private automatic branch exchange
(PABX) may or may not have a switchboard.
PC Personal Computer. A general-purpose single-user
microcomputer designed to be operated by one person at a
time.
pCA PCU Central Authority. One pCA software process is located at
every PCU. The CA is in control of the PCU. It is resident on
the master DPROC (MPROC) only, and maintains a list of the
status of every device and every software process at the site.
PCCCH Packet Common Control Channel.
PCH Paging CHannel. A common access RF channel providing
point-to-multipoint unidirectional signaling downlink. Provides
simultaneous transmission to all MSs over a wide paging area.
PCHN Paging Channel Network.


PCHN Physical Channel. The physical channel is the medium over
which the information is carried. In the case of GSM radio
communications this would be the Air Interface. Each RF
carrier consists of eight physical channels (or timeslots) used
for MS communications. In the case of a terrestrial interface
the physical channel would be cable. See also Physical Layer.
PCI Packet Control Interface.
PCI Peripheral Component Interconnect. A standard for connecting
peripherals to a personal computer, PCI is a 64-bit bus, though
it is usually implemented as a 32-bit bus.
PCM Pulse Code Modulation. Modulation in which a signal is
sampled, and the magnitude (with respect to a fixed reference)
of each sample is quantized and converted by coding to a
digital signal. Provides undistorted transmission, even in the
presence of noise. See also 2 Mbit/s link, which is the physical
bearer of PCM.
pCM PCU Configuration Management. pCM is a GWM process. It
distributes all database changes performed at the BSC to the
PCU boards.
PCN Personal Communications Network. Any network supporting
PCS, but in particular DCS1800.
PCR Preventative Cyclic Retransmission. A form of error correction
suitable for use on links with long transmission delays, such
as satellite links.
PCS The U.S. Federal Communications Commission (FCC) term
used to describe a set of digital cellular technologies being
deployed in the U.S. PCS works over GSM, CDMA (also called
IS-95), and North American TDMA (also called IS-136) air
interfaces.
PCS System Personal Communications Services System. In PCS, a
collection of facilities that provides some combination of
personal mobility, terminal mobility, and service profile
management. Note: As used here, "facilities" includes
hardware, software, and network components such as
transmission facilities, switching facilities, signalling facilities,
and databases.
PCS1900 A cellular phone network using the higher frequency
range allocated in countries such as the USA. It operates
on the frequency range, 1850 - 1910 MHz (receive) and
1930 - 1990 MHz (transmit).
PCU Packet Control Unit. A BSS component that provides GPRS
with packet scheduling over the air interface with the MS, and
packet segmentization and packetization across the Frame
Relay link with the SGSN.
PCU Picocell Control unit. Part of M-Cellaccess.
pd Potential difference. Voltage.
PD Protocol Discriminator field. The first octet of the packet header
that identifies the protocol used to transport the frame.
PD Public Data. See PDN.


PDB Power Distribution Board.
PDCH Packet Data Channel. PDCH carries a combination of PBCCH
and PDTCH logical channels.
PDF Power Distribution Frame (MSC/LR).
PDN Public Data Network. A network established and operated by
a telecommunications administration, or a recognized private
operating agency, for the specific purpose of providing data
transmission services for the public.
PDP Packet Data Protocol.
PDTCH Packet Data Traffic Channels
PDU Power Distribution Unit. The PDU consists consisting of the
Alarm Interface Board (AIB) and the Power Distribution Board
(PDB).
PDU Protected Data Unit.
PDU Protocol Data Unit. A term used in TCP/IP to refer to a unit of
data, headers, and trailers at any layer in a network.
PEDC Pan-European Digital Cellular network. The GSM network in
Europe.
Peg A single incremental action modifying the value of a statistic.
Also, A number indicating the use of a device or resource.
Each time the device or resource is used the peg count is
incremented.
Pegging Modifying a statistical value.
pFCP PCU Fault Collection Process. See pFTP.
pFTP PCU Fault Transaction Process. The pFTP resides on the PSP
as part of the GWM Functional Unit process. All alarms at the
PCU are reported to pFTP. All DPROCs and the MPROC have
a local pFCP to handle Software Fault Management indications
(SWFMs). The pFTP forwards alarms to the Agent at the BSC
and generates messages to pCA for device transitions as
needed, based on faults reported.
PGSM Primary GSM. PGSM operates on the standard GSM frequency
range, 890 - 915 MHz (receive) and 935 - 960 MHz (transmit).
PH Packet Handler. A packet handler assembles and disassembles
packets.
PH PHysical (layer). See Physical Layer.
PHI Packet Handler Interface.
Physical Layer See OSI-RM. The Physical Layer is the lowest of seven
hierarchical layers. It performs services requested by the Data
Link Layer. The major functions and services of the layer
are: (a) establishment and termination of a connection to a
communications medium; (b) participation in the process of
sharing communication resources among multiple users; and,
(c) conversion between the representation of digital data in
user equipment and the corresponding signals transmitted over
a communications channel.


PI Presentation Indicator. The PI forms part of the calling name
information. Depending on database settings, the PI may
prevent the called party from seeing the identity of the calling
party.
PIA Packet Immediate Assignment.
Picocell A cell site where the base station antenna is mounted within
a building.
PICP Packet Interface Control Processor. A PCU hardware
component, the PICP is a DPROC board used for network
interfacing functions such as SGSN and BSC.
PICS Protocol Implementation Conformance Statement. A statement
made by the supplier of an implementation or system claimed
to conform to a given specification, stating which capabilities
have been implemented.
PID Process IDentifier/Process ID.
PIM PCM Interface Module (MSC).
PIN Personal Identification Number. A password, typically four
digits entered through a telephone keypad.
PIN Problem Identification Number.
PIX Parallel Interface Extender half size board. Customer alarm
interface, part of the BSS. The PIX board provides a means of
wiring alarms external to the BSS, BSC, or BTS into the base
equipment.
PIXT or PIXIT Protocol Implementation eXtra information for Testing.
A statement made by a supplier or implementor of an
implementation under test (IUT) which contains information
about the IUT and its testing environment which will enable a
test laboratory to run an appropriate test suite against the IUT.
PK Primary Key. A database column attribute, the primary key is a
not-null, non-duplicate index.
PL See Presentation Layer.
Plaintext Unciphered data.
PlaNET Frequency planning tool.
PLL Phase Lock Loop (refers to phase locking the GCLK in the
BTS). PLL is a mechanism whereby timing information is
transferred within a data stream and the receiver derives the
signal element timing by locking its local clock source to the
received timing information.
PLMN Public Land Mobile Network. The mobile communications
network.
PM Performance Management. An OMC application. PM enables
the user to produce reports specific to the performance of the
network.
PMA Prompt Maintenance Alarm. An alarm report level; immediate
action is necessary. See also DMA.
PMC PCI Mezzanine Card.


PMR Packet Management Report.
PMS Pseudo MMS.
PM-UI Performance Management User Interface.
PMUX PCM MUltipleXer.
PN Permanent Nucleus group of the GSM committee.
PNE Présentation des Normes Européennes. Presentation rules
of European Standards.
POI Point of Interconnection. A point at which the cellular network
is connected to the PSTN. A cellular system may have multiple
POIs.
POTS Plain Old Telephone Service. Basic telephone service without
special features such as call waiting, call forwarding, etc.
pp, p-p Peak-to-peak.
PP Point-to-Point.
ppb Parts per billion.
PPB PCI (Peripheral Component Interconnect) to PCI Bridge board.
The PPB allows an MPROC to be linked to a separate bus.
The PPB and MPROC are paired boards.
PPE Primitive Procedure Entity.
ppm Parts per million (x 10-6).
Pref CUG Preferential CUG. A Pref CUG, which can be specified for each
basic service group, is the nominated default CUG to be used
when no explicit CUG index is received by the network.
Presentation Layer See OSI RM. The Presentation Layer responds to service
requests from the Application Layer and issues service
requests to the Session Layer. It relieves the Application
Layer of concern regarding syntactical differences in data
representation within the end-user systems.
Primary Cell A cell which is already optimized in the network and has a
co-located neighbour whose cell boundary follows the boundary
of the said cell. The primary cell has a preferred band equal to
the frequency type of the coincident cell.
PRM Packet Resource Manager. The PRM is a PRP process. It
performs all RLC/MAC functions and realises UL/DL power
control and timing advance.
PROM Programmable Read Only Memory. A storage device that, after
being written to once, becomes a read-only memory.
PRP Packet Resource Process(or). A PCU hardware component,
the PRP is a DPROC board which manages the packet
resources at the PCU and is the processor where all of the
radio related processing occurs. GPRS channels are routed to
PRPs which perform the RLC/MAC processing, air interface
scheduling, and frame synchronization of the channels.


Ps Location probability. Location probability is a quality criterion
for cell coverage. Due to shadowing and fading a cell edge is
defined by adding margins so that the minimum service quality
is fulfilled with a certain probability.
PS Puncturing Scheme.
PSA Periodic Supervision of Accessibility. PSA is a fault
management function. It periodically sends messages to
BSSs requesting information on their current state. This
verifies whether the BSSs are operational or not. If a BSS fails
to respond to a PSA request for its status, the OMC-R will
generate an alarm for that BSS.
PSI Packet System Information.
PSAP Presentation Services Access Point.
pSAP PCU System Audit Process. pSAP is a GWM process. It
periodically monitors the soft devices to maintain the reliability
of the system.
PSM Power Supply Module.
pSM PCU Switch Manager. The pSM resides on the PSP as part of
the GWM Functional Unit process. The pSM maintains data
paths within the PCU and communicates with the BSC.
PSP PCU System Processor board. Part of GPRS.
PSPDN Packet Switched Public Data Network. See Packet Switching
and PDN.
PSTN Public Switched Telephone Network. The domestic land
line telecommunications network. It is usually accessed by
telephones, key telephone systems, private branch exchange
trunks, and data arrangements.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTACH Packet Timing Advance Control Channel
PTO Public Telecommunications Operator.
PTR Packet Timeslot Reconfiguration.
PUA Packet Uplink Assignment.
PUCT Price per Unit Currency Table. The PUCT is the value of the
Home unit in a currency chosen by the subscriber. The PUCT
is stored in the SIM. The value of the PUCT can be set by
the subscriber and may exceed the value published by the
HPLMN. The PUCT value does not have any impact on the
charges raised by the HPLMN.
PVC Permanent Virtual Circuit. Also, in ATM terminology,
Permanent Virtual Connection. A virtual circuit that is
permanently established, saving the time associated with circuit
establishment and tear-down. See also SVC.
PW Pass Word.


PWR Power.
PXPDN Private eXchange Public Data Network. See also PDN.
QA- Quiesent mode
QA Q (Interface) - Adapter. TMN interface adapter used to

communicate with non-TMN compatible devices and objects.
Used to connect MEs and SEs to TMN (GSM Rec. 12.00).
Q3 Interface between NMC and GSM network.
Q-adapter See QA.
QAF Q-Adapter Function.
QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to
TDM switch highway. See MSI.
QIC Quarter Inch Cartridge (Data storage format).
QoS Quality Of Service. An alarm category which indicates that a
failure is degrading service.
Queue Data structure in which data or messages are temporarily
stored until they are retrieved by a software process. Also a
series of calls waiting for service. See also FIFO.
Quiescent mode IDS intermediate state before shutdown.
R - RXU
R Value of reduction of the MS transmitted RF power relative

to the maximum allowed output power of the highest power
class of MS (A).
RA RAndom mode request information field.
RA Radio Access.
RA Routing Area.
RA250 Rural Area with the MS travelling at 250 kph. Dynamic model
measured. See also TU3, TU50, HT100 and EQ50.
RAB Random Access Burst. Data sent on the RACH.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel. The RACH is used by the mobile
station to request access to the network. See also RAB.
Radio Frequency A term applied to the transmission of electromagnetically
radiated information from one point to another, usually using air
or vacuum as the transmission medium. An electromagnetic
wave frequency intermediate between audio frequencies and
infrared frequencies used in radio and television transmission.


RAM Random Access Memory. A read/write, nonsequential-access
memory in which information can be stored, retrieved and
modified. This type of memory is generally volatile (i.e., its
contents are lost if power is removed).
RAND RANDom number (used for authentication). The RAND is sent
by the SGSN to the MS as part of the authentication process.
RAT Radio Access Technology
RATI Receive Antenna Transceiver Interface.
RAx Rate Adaptation.
RBDS Remote BSS Diagnostic System (a discontinued Motorola
diagnostic facility).
RBER Residual Bit Error Ratio. RBER is a ratio of the number of
bits in error to the total number of bits received, within error
detected speech frames defined as good. The measurement
period over which the calculation is made is 480 ms. During this
period, 24 speech frames are decoded and a ratio calculated.
By referring to a lookup table, the ratio is then converted to an
RBER Quality number between 0 and 7.
RBTS Remote Base Transceiver Station. A BTS that is not co-located
with the BSC that controls it.
RCB Radio Control Board. Part of the DRCU.
RCI Radio Channel Identifier. The unique identifier of the radio
channel portion of the circuit path.
RCI Radio Channel Interface. The RCI changes the MS address
used in the RSS (channel number) to the address used in
Layer 3 in the BSC CP.
RCP Radio Control Processor.
RCU Radio Channel Unit. Part of the BSS. Contains transceiver,
digital control circuits, and power supply. Note: The RCU is
now obsolete, see DRCU.
RCVR Receiver.
RDB Requirements Database.
RDBMS Relational DataBase Management System (INFORMIX). The
database management system for the OMC-R database.
RDI Restricted Digital Information.
RDIS Radio Digital Interface System.
RDM Reference Distribution Module. The RDM provides a stable
3MHz reference signal to all transceivers. It is used for carrier
and injection frequency synthesis.
RDN Relative Distinguished Name. A series of RDNs form a unique
identifier, the distinguished name, for a particular network
element.
REC, Rec RECommendation.


Reciprocal neighbour Used to describe adjacent cells; each being designated as
a neighbour of the other. Also known as bi-directional and
two-way neighbour.
Registration The process of a MS registering its location with the MSC in
order to make or receive calls. This occurs whenever the MS
first activates or moves into a new service area.
REJ REJect(ion).
REL RELease.
RELP Residual Excited Linear Predictive. A form of speech coding.
RELP coders are usually used to give good quality speech at
bit rates in the region of 9.6 kbit/s.
RELP-LTP RELP Long Term Prediction. A name for GSM full rate. See
Full Rate.
Remotely Tuned Combiner A combiner device which houses two processors (for
paired-redundancy) and several tuneable cavities. See also
COMB
resync Resynchronize/resynchronization.
REQ REQuest.
Reuse Pattern The minimum number of cells required in a pattern before
channel frequencies are reused, to prevent interference.
Varies between cell configuration type and channel type. The
pattern shows assignments of adjacent channels to minimize
interference between cells and sectors within the pattern area.
Revgen A Motorola DataGen utility for producing an MMI script from a
binary object database.
RF See Radio Frequency.
RFC, RFCH Radio Frequency Channel. A partition of the system RF
spectrum allocation with a defined bandwidth and centre
frequency.
RFE Radio Front End (module).
RFE Receiver Front End (shelf).
RFEB Receiver Front End Board. Part of DRCU II.
RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RFN Reduced TDMA Frame Number.
RFU Reserved for Future Use.
RJ45 Registered Jack 45. An eight-wire connector used commonly
to connect computers onto a local-area networks (LAN),
especially Ethernets.
RISC Reduced Instruction Set Computer. A type of microprocessor
that recognizes a relatively limited number of instruction types,
allowing it to operate at relatively higher speeds.


RL Remote login. RL is a means by which the operator performs
configuration management, fault management, and some
performance management procedures at the NEs. The RL
software manages the X.25 connection for remote login. The
circuit is made by the OMC-R calling the NE.
RLC Release Complete. An SCCP message type used with RLSD
to release a connection.
RLC Radio Link Control. Air interface transmission layer. The RLC
function processes the transfer of PDUs from the LLC layer.
RLM RF Link Manager.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between an MT and IWF. See GSM 04.22.
RLR Receive Loudness Rating. See SLR.
RLSD ReLeaSeD. An SCCP message type used with RLC to release
a connection.
RMS Root Mean Square (value). The most common mathematical
method of defining the effective voltage or current of an AC
wave. For a sine wave, the rms value is 0.707 times the peak
value.
RMSU Remote Mobile Switching Unit. An RMSU is a line concentrator.
It may be inserted between the MSC and some of the BSS
sites served by the MSC to reduce the number of terrestrial
signalling and traffic circuits required.
RNTABLE Table of 128 integers in the hopping sequence.
ROAM Reliability, Operability, Availability, Maintainability.
Roaming Situation where mobile station operates in a cellular system
other than the one from which service is subscribed.
ROM Read Only Memory. Computer memory that allows fast
access to permanently stored data but prevents addition to or
modification of the data. ROM is inherently non-volatile storage
- it retains its contents even when the power is switched off.
ROSE Remote Operations Service Element. An ASE which carries a
message between devices over an association established by
ASCE (a CCITT specification for O & M) (OMC).
Roundtrip Time period between transmit and receive instant of a timeslot
in the BTS, propagation determined by the response behaviour
of the MS and the MS to BTS delay distance.
RPE Regular Pulse Excited (codec). See RPE-LTP.
RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSM
digital speech coding scheme. GSM uses a simplified RPE
codec, with long-term prediction, operating at 13 kbits/s to
provide toll quality speech.
RPOA Recognised Private Operating Agency. Private
telecommunications operator recognised by the appropriate
telecommunications authority.


RPR Read Privilege Required. Part of the table structure of the
OMC database schema. Access to the column is allowed only
for privileged accounts.
RR Radio Resource management. Part of the GSM management
layer. The functions provided by RR include paging, cipher
mode set, frequency redefinition, assignments, handover and
measurement reports.
RR Receive Ready.
RRSM Radio Resource State Machine. Translates messages through
Call Processing (CP). Activates and deactivates radio channels
as controlled by the CRM.
RRSM Radio Resource Switch Manager.
RS232 Recommended Standard 232. The interface between a
terminal (DTE) and a modem (DCE) for the transfer of serial
data. Standard serial interface.
RSE Radio System Entity.
RSL Radio Signalling Link. RSL is used for signalling between the
BSC and BTSs. The interface uses a 64 kbit/s timeslot with
a LAPD protocol.
RSLF Radio System Link Function.
RSLP Radio System Link Processor.
RSS Radio SubSystem (replaced by BSS).
RSSI Received Signal Strength Indicator. A parameter returned from
a transceiver that gives a measure of the RF signal strength
between the MS and BTS, either uplink or downlink.
RSZI Regional Subscription Zone Identity. The RSZI defines the
regions in which roaming is allowed. The elements of the RSZI
are:The Country Code (CC) which identifies the country in
which the GSM PLMN is located,The National Destination Code
(NDC) which identifies the GSM PLMN in that country,The
Zone Code (ZC) which identifies a regional subscription zone
as a pattern of allowed and not allowed location areas uniquely
within that PLMN.
RTC Remotely Tuneable Channel Combiner. RTCs are used to
fine-tune the cavities to the right frequency. A poorly tuned
cavity can cause power destined for the antenna to be reversed.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function. RTF is the function that supports
the air interface channel and the DRI/Transceiver pair. When
equipping a DRI at a remote BTS, one or more RTFs must
be equipped.
RTF Receive Transmit Functions.
RTS Request to Send. A handshaking signal used with
communication links, especially RS232 or CCITT Rec. V.24 to
indicate (from a transmitter to a receiver) that data is ready for
transmission. See also CTS.
RU Rack Unit.


Run level System processor operating mode.
Rx Receive(r).
RX Receive window buffer.
RXCDR Remote Transcoder. An RXCDR is used when the transcoding
is performed at a site away from the BSC. This site would be
at or near the MSC. This enables 4:1 multiplexing in which the
transcoded data for four logical channels is combined onto one
64 kbit/s link, thus reducing the number of links required for
interconnection to the BSCs. See also XCDR.
RXF Receive Function (of the RTF).
RXLEV Received signal level. An indication of received signal level
based on the RSSI. RXLEV is one of the two criteria for
evaluating the reception quality (the basis for handover and
power control). See also RXQUAL. The MS reports RXLEV
values related to the apparent received RF signal strength. It is
necessary for these levels to attain sufficient accuracy for the
correct functioning of the system.
RXLEV-D Received signal level downlink.
RXLEV-U Received signal level uplink.
RXQUAL Received signal quality. An indication of the received signal
quality based on the BER. RXQUAL is one of the two criteria
for evaluating the reception quality (the basis for handover
and power control). See also RXLEV. The MS measures the
received signal quality, which is specified in terms of BER
before channel decoding averaged over the reporting period of
length of one SACCH multiframe.
RXQUAL-D Received signal quality downlink.
RXQUAL-U Received signal quality uplink.
RXU Remote Transcoder Unit. The shelf which houses the remote
transcoder modules in a BSSC cabinet at a remote transcoder
site.
S7- SYSGEN
S7 See SS7.
S/W SoftWare.
SABM Set Asynchronous Balanced Mode. A message which
establishes the signalling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for conveying power control and timing
advance information in the downlink direction, and RSSI and
link quality reports in the uplink direction.
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.
SACCH/C8 Slow Associated Control CHannel/SDCCH/8.


SACCH/T Slow Associated Control CHannel/Traffic channel.
SACCH/TF Slow Associated Control CHannel/Traffic channel Full rate.
SACCH/TH Slow Associated Control CHannel/Traffic channel Half rate.
SAGE A brand of trunk test equipment.
SAP Service Access Point. In the reference model for OSI, SAPs of
a layer are defined as gates through which services are offered
to an adjacent higher layer.
SAP System Audits Process. SAP is on each GPROC in the BSS. It
monitors the status of the BSS on a periodic (scheduled) and
on-demand basis during normal mode. SAP detects faulty or
degrading hardware and software (through the use of audit
tests) and notifies the Alarms handling software of the condition.
SAPI Service Access Point Indicator (identifier). The OSI term for the
component of a network address which identifies the individual
application on a host which is sending or receiving a packet.
SAW Surface Acoustic Wave. SAW devices basically consist of an
input transducer to convert electrical signals to tiny acoustic
waves, which then travel through the solid propagation medium
to the output transducer where they are reconverted to
electrical signals. SAW band pass filters are used for sorting
signals by frequency.
SB Synchronization Burst (see Synchronization burst).
SBUS Serial Bus. An SBUS is a logical device made up of the
communication path between the GPROCs and LANX cards
in a cage.
SC Service Centre (used for Short Message Service).
SC Service Code.
SCCA System Change Control Administration. Software module
which allows full or partial software download to the NE (OMC).
SCCP Signalling Connection Control Part (part of SS7).
SCEG Speech Coding Experts Group (of GSM).
SCH Synchronization CHannel. A GSM broadcast control channel
used to carry information for frame synchronization of MSs and
identification of base stations.
SCI Status Control Interface. A slave to the Status Control Manager.
SCIP Serial Communication Interface Processor.
SCM Status Control Manager. Accepts messages from other
processors within the switch requesting status displays in the
form of one or more lights on a hardware panel. The SCM maps
the status display requests into specific commands to the status
control interface processor to turn on and/or turn off lights.
SCN Sub-Channel Number. One of the parameters defining a
particular physical channel in a BS.
SCP Service Control Point (an intelligent network entity).


SCSI Small Computer Systems Interface. A processor-independent
standard for system-level interfacing between a computer and
intelligent devices including hard disks, floppy disks, CD-ROM,
printers, scanners, and many more. SCSI-1 can connect up to
seven devices to a single SCSI adaptor (or host adaptor) on
the computer’s bus.
SCU Slim Channel Unit.
SCU900 Slim Channel Unit for GSM900.
SDCCH Stand-alone Dedicated Control CHannel. A GSM control
channel where the majority of call setup occurs. Used for MS to
BTS communications before MS assigned to TCH. A SDCCH
is used by a single MS for call setup, authentication, location
updating and SMS point to point.
SDL Specification Description Language. A method for visually
depicting the functionality of call processing, operations and
maintenance software.
SDM Sub-rate Data Multiplexor
SDT SDL Development Tool. A software tool to model and validate
real-time, state-based product software designs.
SDU Service Data Unit. In layered systems, a set of data that is sent
by a user of the services of a given layer, and is transmitted to
a peer service user semantically unchanged.
SDR Special Drawing Rights. The SDR is the International Monetary
Fund unit of account. It also serves as a basis for the unit of
account for a number of other international organizations and
as a basis for private financial instruments. The SDR is based
on the values of the euro, U.S. dollar, Japanese yen and pound
sterling.
SE Support Entity. See SEF.
Secondary Cell A cell which is not optimized in the network and has a
co-located neighbour whose cell boundary follows the boundary
of the said cell. The secondary cell has a preferred band the
same as that of its own frequency type.
SEF Support Entity Function. SEFs are functions not directly
involved in the telecommunication process. They include fault
localisation, protection switching, etc. (GSM Rec.12.00).
Session Layer See OSI RM. The Session Layer responds to service requests
from the Presentation Layer and issues service requests to
the Transport Layer. It provides the mechanism for managing
the dialogue between end-user application processes. It
provides for either duplex or half-duplex operation and
establishes checkpointing, adjournment, termination, and
restart procedures.


SFH Synthesizer Frequency Hopping. The principle of SFH is that
every mobile transmits its time slots according to a sequence of
frequencies that it derives from an algorithm. The frequency
hopping occurs between time slots and, therefore, a mobile
station transmits (or receives) on a fixed frequency during one
time slot. It must then hop before the time slot on the next
TDMA frame. Due to the time needed for monitoring other
base stations the time allowed for hopping is approximately 1
ms, according to the receiver implementation. The receive and
transmit frequencies are always duplex frequencies.
SGSN Serving GPRS Support Node. The SGSN provides the control,
transmission, OAMP, and charging functions. It keeps track of
the individual MS locations, and performs security functions
and access control. The SGSN is connected to the BSS via a
Frame Relay network.
SI Screening Indicator. The supplementary service (SS) screening
indicator is sent by the MS at the beginning of the radio
connection to allow the network to assess the capabilities of the
MS and hence determine either whether a particular network
initiated SS operation may be invoked or which version of a
network initiated SS operation should be invoked. The SS
screening indicator is only relevant to network initiated SS
operation and is valid for the duration of a radio connection.
SI Service Interworking. Part of the IWF.
SI Supplementary Information.
SI System Information.
SIA Supplementary Information A.
SID Silence Descriptor. The transmission of comfort noise
information to the RX side is achieved by means of a SID
frame. A SID frame is transmitted at the end of speech bursts
and serves as an end of speech marker for the RX side. In
order to update the comfort noise characteristics at the RX
side, SID frames are transmitted at regular intervals also during
speech pauses. This also serves the purpose of improving the
measurement of the radio link quality by the radio subsystem
(RSS).
SIF Signal Information Field. The bits of a message signal unit that
carry information for a certain user transaction; the SIF always
contains a label.
Signalling System No.7 See SS7.
SIM Subscriber Identity Module. Removable module which is
inserted into a mobile equipment; it is considered as part of
the MS. It contains security related information (IMSI, Ki, PIN),
other subscriber related information and the algorithms A3 and
A8.
SIMM Single Inline Memory module.
SIMM System Integrated Memory Module. A small plug-in circuit
board providing additional RAM for a computer.


SIO Service Information Octet. Eight bits contained in a message
signal unit, comprising the service indicator and sub-service
field. A value in the SIF of an SS7 signalling message
specifying the User Part type.
SITE BSC, BTS or collocated BSC-BTS site.
SIX Serial Interface eXtender. Converts interface levels to TTL
levels. Used to extend 2 serial ports from GPROC to external
devices (RS232, RS422, and fibre optics).
SK Secondary Key. A database column attribute, the secondary
key indicates an additional index and/or usage as a composite
key.
SL See Session Layer.
SL Signalling Link. The signalling links between the various
network elements are: Remote BTS to BSC - Radio Signalling
Link (RSL), BSC to MSC - Message Transfer Link (MTL),
OMC(R) to BSS - Operations and Maintenance Link (OML),
Remote XCDR to BSC - XCDR signalling Link (XBL), CBC to
BSC - Cell Broadcast Link (CBL).
SLNK Serial Link. One of four communications paths between SCIP
and peripheral equipment. The information on the link is sent
serially in a bit-synchronous format.
SLR Send Loudness Rating. The SLR, in the mobile to land
direction, and the Receive Loudness Rating (RLR) in the land
to mobile direction, determine the audio signal levels for the
customers speech. The loudness ratings are calculated from
the send and receive sensitivity masks or frequency responses.
SLTA Signalling Link Test Acknowledge. Message sent from the
MSC to the BSC in response to an SLTM.
SLTM Signalling Link Test Message. During the process of bringing
an MTL link into service, the BSC sends an SLTM message to
the MSC. The MSC responds with an SLTA message.
SM Switch Manager. The function of the SM is to connect a MS
terrestrial trunk from the MSC (designated by the MSC), to the
radio channel given to a MS by the cell resource manager in
the BSS software.
SM Summing Manager.
SMAE System Management Application Entity (CCITT Q795, ISO
9596). OSI terminology for a software Management Information
Server that manages a network.
SMASE System Management Application Service Element.
SMCB Short Message Cell Broadcast.
SME Short Message Entity. An entity that may send or receive Short
Messages. The SME may be located in a fixed network, an
MS, or a SC. See also SMS.
SMG Special Mobile Group. To avoid confusion between the GSM
system and the GSM committee with its wider responsibilities,
the committee was renamed SMG in 1992.


SMP Motorola Software Maintenance Program. A Motorola program
designed to ensure the highest quality of software with the
highest level of support.
SMS Short Message Service. SMS is a globally accepted wireless
service that enables the transmission of alphanumeric
messages between mobile subscribers and external systems
such as electronic mail, paging, and voice-mail systems. It
transfers the short messages, up to 160 characters, between
Smts and MSs via an SMS-SC. See also SMS-SC, SMS/PP
and Smt.
SMSCB Short Message Service Cell Broadcast. SMSCB is a service in
which short messages may be broadcast from a PLMN to MSs.
SMSCB messages come from different sources (e.g. traffic
reports, weather reports). Messages are not acknowledged by
the MS. Reception of SMSCB messages by the MS is only
possible in idle mode. The geographical area over which each
message is transmitted is selected by the PLMN operator, by
agreement with the provider of the information.
SMS-SC Short Message Service - Service Centre. SMS-SC is an
interworking unit between stationary networks and the GSM
Network. It acts as a store and forward centre for short
messages. See also SMS, SMS/PP and Smt.
SMS/PP Short Message Service/Point-to-Point. Two different
point-to-point services have been defined: Mobile Originated
(MO) and Mobile Terminated (MT). A short message always
originates or terminates in the GSM network. This means that
short messages can never be sent between two users both
located in stationary networks. See also SMS, SMS-SC and
Smt.
Smt Short message terminal. See also SMS, SMS-SC and
SMS/PP. There are different types of Smt interfaces, one being
the Computer Access Interface which provides services for
external computers communicating with SMS-SCs through the
Computer Access Protocol.
SN Subscriber Number.
SND SeND.
SNDR SeNDeR.
SNR Serial NumbeR.
SOA Suppress Outgoing Access (CUG SS). An arrangement which
prevents a member of a CUG placing calls outside the CUG.
Software Instance A complete set of software and firmware objects including the
database object.
SP Service Provider. The organisation through which the
subscriber obtains GSM telecommunications services. This
may be a network operator or possibly a separate body.
SP Signalling Point. A signalling point is a node within a SS7
network.
SP Special Product.
SP SPare.


SPARC Scalable Processor ArChitecture. a 32- and 64-bit
microprocessor architecture from Sun Microsystems that is
based on the Reduced Instruction Set Computer (RISC).
SPARC has become a widely-used architecture for hardware
used with UNIX-based operating systems.
SPC Signalling Point Code.
SPC Suppress Preferential CUG. Prohibits the use of the preferential
CUG, on a per call basis.
SPI Signalling Point Inaccessible.
SPP Single Path Preselector.
SQE Signal Quality Error.
SQL Structured Query Language. The standard language for
relational database management systems as adopted by the
American National Standards Institute (ANSI X3.135-1989) and
the International Standards Organization (ISO 9075-1989).
SRD Service Request Distributor.
SRES Signed RESponse (authentication). The SRES is calculated by
the MS, using the RAND, and sent to the SGSN to authenticate
the MS.
SS Supplementary Service. A modification of, or a supplement to,
a basic telecommunication service.
SS System Simulator.
SS7 ITU-TSS Common Channel Signalling System No. 7. Also
known as C7, S7 or SS#7. The standard defines the procedures
and protocol by which network elements in the PSTN exchange
information over a digital signalling network to effect wireless
(cellular) and wireline call setup, routing and control.
SSA SubSystem-Allowed. SSA is used for SCCP subsystem
management. An SSA message is sent to concerned
destinations to inform those destinations that a subsystem
which was formerly prohibited is now allowed. (see ITU-T
Recommendation Q.712 para 1.15).
SSAP Site System Audits Processor.
SSC Supplementary Service Control string. When a subscriber
selects a supplementary service control from the menu in a
GSM network, the mobile station invokes the SSC by sending
the network the appropriate functional signalling message.
SSF Subservice Field. The level 3 field containing the network
indicator and two spare bits.
SSM SCCP Switch Manager.
SSM Signalling State Machine.
SSN SubSystem Number. In SS7, each signalling point (SP) may
contain a number of subsystems. Each subsystem has a
unique ID, the SSN (e.g. 149 for SGSN and 6 for HLR).


SSP Service Switching Point. Intelligent Network Term for the Class
4/5 Switch. The SSP has an open interface to the IN for
switching signalling, control and handoff.
SSP Subsystem-prohibited. SSP is used for SCCP subsystem
management. An SSP message is sent to concerned
destinations to inform SCCP Management at those destinations
of the failure of a subsystem.
SSS Switching SubSystem. The SSC comprises the MSC and the
LRs.
STAN Statistical ANalysis (processor).
STAT STATistics.
stats Statistics.
STC System Timing Controller. The STC provides the timing
functions for the GPROC.
STMR Side Tone Masking rating. A rating, expressed in dB, based on
how a speaker will perceive his own voice when speaking.
SUERM Signal Unit Error Rate Monitor. A link error rate monitor.
STP Signalling Transfer Point. A node in the SS7 telephone network
that routes messages between exchanges and between
exchanges and databases that hold subscriber and routing
information.
SU Signal Unit. A group of bits forming a separately transferable
entity used to convey information on a signalling link.
SunOS Sun Microsystems UNIX Operating System. SunOS was
renamed Solaris.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
Super user User account that can access all files, regardless of protection
settings, and control all user accounts.
SURF Sectorized Universal Receiver Front-end (Used in
Horizonmacro).
SVC Switch Virtual Circuit. A temporary virtual circuit that is set up
and used only as long as data is being transmitted. Once the
communication between the two hosts is complete, the SVC
disappears. See also PVC.
SVM SerVice Manager. The SVM provides overall management
authority for all in-service service circuits.
SVN Software Version Number. The SVN allows the ME
manufacturer to identify different software versions of a given
type approved mobile. See also IMEI and IMEISV.
SW Software.
SWFM SoftWare Fault Management. Software faults are handled
through a SWFM facility which routes those events to the OMC
independently through the FCP.
SYM SYstem information Manager. The SYM builds and sends
GPRS system information messages over the BCCH.


sync synchronize/synchronization.
Synchronization burst Period of RF carrier less than one timeslot whose modulation
bit stream carries information for the MS to synchronize its
frame to that of the received signal.
Synthesizer hopping Synthesizer hopping is a method of frequency hopping in
which the RCUs are re-tuned in real-time, from frequency to
frequency.
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for loading a
configuration database into a BTS.
T -TxBPF
T Timer.
T Transparent.
T Type only.
T1 Digital WAN carrier facility that transmits DS-1-formatted
data at 1544 kbp/s through the telephone-switching network.
companies. T1 lines are widely used for private networks as
well as interconnections between an organization’s PBX or
LAN and the telco.
T43 Type 43 Interconnect Board. Provides interface to 12
unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for 2
Mbit/s circuits (See BIB).
TA Terminal Adaptor. A physical entity in the MS providing terminal
adaptation functions (see GSM 04.02).
TA See Timing Advance.
TAC Type Approval Code. Part of the IMEISV.
TACS Total Access Communication System. European analogue
cellular system.
TAF Terminal Adaptation Function.
TATI Transmit Antenna Transceiver Interface. The TATI consists of
RF combining equipments, either Hybrid or Cavity Combining.
See CCB.
TAXI Transparent Asynchronous Transmitter/Receiver Interface
(physical layer). A 100 Mbps ATM transmission standard
defined by the ATM Forum.
TBD To Be Determined.
TBF Temporary Block Flow. MAC modes support the provision of
TBFs allowing the point-to-point transfer of signalling and user
data between the network and an MS.
TBR Technical Basis for Regulation. An ETSI document containing
technical requirements and procedures.


TBUS TDM Bus. A TBUS is a logical device made up of the TDM
backplane of a cage, the KSW devices managing the TDM
highway of the cage, and local and remote KSWX devices (if
they exist).
TC Transaction Capabilities. TC refers to a protocol structure
above the network layer interface (i.e., the SCCP service
interface) up to the application layer including common
application service elements but not the specific application
service elements using them. TC is structured as a Component
sub-layer above a Transaction sub-layer.
TCAP Transaction Capabilities Application Part. The layer of the SS7
protocol that is used to obtain Routing data for certain services.
TCB TATI Control Board.
TCH Traffic CHannel. GSM logical channels which carry either
encoded speech or user data.
TCH/F A full rate TCH. See also Full Rate.
TCH/F2.4 A full rate TCH at ? 2.4 kbit/s.
TCH/F4.8 A full rate TCH at 4.8 kbit/s.
TCH/F9.6 A full rate TCH at 9.6 kbit/s.
TCH/FS A full rate Speech TCH.
TCH/H A half rate TCH. See also Half Rate.
TCH/H2.4 A half rate TCH at ? 2.4 kbit/s.
TCH/H4.8 A half rate TCH at 4.8 kbit/s.
TCH/HS A half rate Speech TCH.
TCI Transceiver Control Interface.
TCP Transmission Control Protocol. TCP is one of the main
protocols in TCP/IP networks. Whereas the IP protocol deals
only with packets, TCP enables two hosts to establish a
connection and exchange streams of data. TCP guarantees
delivery of data and also guarantees that packets will be
delivered in the same order in which they were sent. See also
IP and TCP/IP.
TCP/IP Transmission Control Protocol/Internet Protocol. Two
interrelated protocols that are part of the Internet protocol suite.
TCP operates on the OSI Transport Layer and IP operates on
the OSI Network Layer. See also IP and TCP.
TC-TR Technical Commitee Technical Report.
TCU Transceiver Control Unit.
TDF Twin Duplexed Filter. Used in M-Cellhorizon.
TDM Time Division Multiplexing. A type of multiplexing that combines
data streams by assigning each stream a different time slot in a
set. TDM repeatedly transmits a fixed sequence of time slots
over a single transmission channel. Within T-Carrier systems,
such as T-1 and T-3, TDM combines PCM streams created for
each conversation or data stream.


TDMA Time Division Multiple Access. A technology for delivering
digital wireless service using TDM. TDMA works by dividing
a radio frequency into time slots and then allocating slots to
multiple calls. In this way, a single frequency can support
multiple, simultaneous data channels.
TDU TopCell Digital Unit. Part of the TopCell BTS hardware. A TDU
is capable of supporting 6 TRUs for supporting up to 6 sectors.
TE Terminal Equipment. Equipment that provides the functions
necessary for the operation of the access protocols by the user.
Tei Terminal endpoint identifier. A number that identifies a specific
connection endpoint within a service access point.
TEI Terminal Equipment Identity.
TEMP TEMPorary.
TEST TEST control processor.
TF Transmission Function. The TF provides layered protocol
software for handling payload information transfer and for
providing signalling communications between the control
function and external systems.
TFA TransFer Allowed. An SPC route management message used
to notify adjacent signalling points of an accessible route.
TFP TransFer Prohibited. An SPC route management message
used to notify adjacent signalling points of an inaccessible
route.
TFTP Trivial File Transfer Protocol. TFTP is a simple form of FTP. It
uses UDP and provides no security features. It is often used by
servers to boot diskless workstations, X-terminals, and routers.
TI Transaction Identifier.
Timeslot The multiplex subdivision in which voice and signalling bits are
sent over the air. Each RF carrier is divided into 8 timeslots.
See also ARFCN.
Timing advance A signal sent by the BTS to the MS. It enables the MS to
advance the timing of its transmission to the BTS so as to
compensate for propagation delay.
TL See Transport Layer.
TLLI Temporary Logical Link Identifier.
TLV Type, Length and Value. An encoding element composed of
three fields: a type identifier, a length indicator, and content
octets.
TM Traffic Manager.
TMI TDM Modem Interface board. Provides analogue interface
from IWF to modems for 16 circuits. Part of IWF.
TMM Traffic Metering and Measuring. TMM provides system tools
to be used by traffic engineering and switch maintenance
personnel to determine if the system is operating correctly.
TMM reports are provided for trunk circuits, trunk groups,
service circuits, call routing and miscellaneous system data.


TMN Telecommunications Management Network. The physical
entities required to implement the Network Management
functionality for the PLMN.
Also, TMN was originated formally in 1988 under the ITU-TS
as a strategic goal to create or identify standard interfaces
that would allow a network to be managed consistently across
all network element suppliers. The concept has led to a
series of interrelated efforts at developing standard ways to
define and address network elements. TMN uses the OSI
Management Standards as its framework. TMN applies to
wireless communications and cable TV as well as to private
and public wired networks.
TMSI Temporary Mobile Subscriber Identity. A unique identity
temporarily allocated by the MSC to a visiting mobile subscriber
to process a call. May be changed between calls and even
during a call, to preserve subscriber confidentiality.
TN Timeslot Number.
TOM Tunneling of Messages.
TON Type Of Number.
Traffic channels Channels which carry user’s speech or data. See also TCH.
Traffic unit Equivalent to an erlang.
Training sequence Sequence of modulating bits employed to facilitate timing
recovery and channel equalization in the receiver.
Transport Layer See OSI RM. The Transport Layer responds to service requests
from the Session Layer and issues service requests to the
Network Layer. Its purpose is to provide transparent transfer
of data between end users, thus relieving the upper layers
from any concern with providing reliable and cost-effective
data transfer.
TRS Timeslot Resource Shifter. The TRS determines which
timeslots are active in a PRP board to perform a control of the
GPRS traffic.
TRAU Transcoder Rate Adaption Unit. TRAU converts the encoded
voice and rate adapted data into 64 kbps data for the PSTN.
TRM Terrestrial Resource Management.
TRU TopCell Radio unit.
TRX Transceiver(s). A network component which can serve full
duplex communication on 8 full-rate traffic channels according
to specification GSM 05.02. If Slow Frequency Hopping (SFH)
is not used, then the TRX serves the communication on one
RF carrier.
TS Technical Specification.
TS TeleService. Any service provided by a telecommunication
provider.
TS TimeSlot (see Timeslot).
TS1 Training Sequence 1.
TS2 Training Sequence 2.


TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech & Data Interface.
TSC Training Sequence Code. A training sequence is sent at the
centre of a burst to help the receiver identify and synchronize
to the burst. The training sequence is a set sequence of bits
which is known by both the transmitter and receiver. There are
eight different TSCs numbered 0 to 7. Nearby cells operating
with the same RF carrier frequency use different TSCs to allow
the receiver to identify the correct signal.
TSI TimeSlot Interchange. The interchange of timeslots within a
TDM stream.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSN TRAU SyNc.
TSW Timeslot SWitch.
TTCN Tree and Tabular Combined Notation. TTCN is a programming
language endorsed by ISO that is used to write test suites for
telecommunications systems.
TTL Transistor to Transistor Logic. A common semiconductor
technology for building discrete digital logic integrated circuits.
TTY TeleTYpe (refers to any terminal).
TU Traffic Unit.
TU3 Typical Urban with the MS travelling at 3 kph. Dynamic model
measured. See also TU50, HT100, RA250 and EQ50.
TU50 Typical Urban with the MS travelling at 50 kph. Dynamic model
measured. See also TU3, HT100, RA250 and EQ50.
TUP Telephone User Part. TUP was an earlier implementation of
SS7 and generally does not allow for data type applications.
TV Type and Value.
Two-way neighbour See Reciprocal neighbour.
Tx Transmit(ter).
TX Transmit window buffer.
TXF Transmit Function. See RTF.
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter. See BPF.


U - UUS
UA Unnumbered Acknowledgment. A message sent from the MS

to the BSS to acknowledge release of radio resources when
a call is being cleared.
UCS2 Universal Coded Character Set 2. A codeset containing all of
the characters commonly used in computer applications.
UDI Unrestricted Digital Information.
UDP User Datagram Protocol. UDP is a connectionless protocol that,
like TCP, runs on top of IP networks. Unlike TCP/IP, UDP/IP
provides very few error recovery services, offering instead a
direct way to send and receive datagrams over an IP network.
It is used primarily for broadcasting messages over a network.
UDUB User Determined User Busy.
UFE Uplink Frame Error.
UHF Ultra High Frequency. The UHF range of the radio spectrum is
the band extending from 300 MHz to 3 GHz.
UI Unnumbered Information (Frame).
UIC Union International des Chemins de Fer. The UIC is the
worldwide organisation for cooperation among railway
companies. Its activities encompass all fields related to the
development of rail transport.
UID User ID. Unique number used by the system to identify the user.
UL Upload (of software or database from an NE to a BSS).
UL UpLink.
ULC UpLink Concatenator. The ULC concatenates RLC data blocks
into LLC frames.
Um Air interface.
UMTS Universal Mobile Telecommunication System. The European
implementation of the 3G wireless phone system. UMTS, which
is part of IMT-2000, provides service in the 2GHz band and
offers global roaming and personalized features. Designed as
an evolutionary system for GSM network operators, multimedia
data rates up to 2 Mbps are expected.
UNIX A multiuser, multitasking operating system that is widely used
as the master control program in workstations and especially
servers. UNIX was developed by AT&T and freely distributed to
government and academic institutions, causing it to be ported
to a wider variety of machine families than any other operating
system. As a result, UNIX became synonymous with open
systems.
UPCMI Uniform PCM Interface (13 bit). The UPCMI is introduced for
design purposes in order to separate the speech transcoder
impairments from the basic audio impairments of the MS.
UPD Up to Date.
Uplink Physical link from the MS towards the BTS (MS transmits, BTS
receives).


UPS Uninterruptable Power Supply. A device that is inserted
between a primary power source, such as a commercial utility,
and the primary power input of equipment to be protected,
e.g., a computer system, for the purpose of eliminating the
effects of transient anomalies or temporary outages. Backup
power is used when the electrical power fails or drops to an
unacceptable voltage level.
UPU User Part Unavailable.
Useful part of burst That part of the burst used by the demodulator; differs from
the full burst because of the bit shift of the I and Q parts of the
GMSK signal.
USF Uplink State Flag.
USSD Unstructured Supplementary Service Data. The USSD
mechanism allows the MS user and a PLMN operator defined
application to communicate in a way which is transparent to
the MS and to intermediate network entities. The mechanism
allows development of PLMN specific supplementary services.
UTRAN UMTS Radio Access Network
UUS User-to-User Signalling supplementary service. The UUS
supplementary service allows a mobile subscriber to
send/receive a limited amount of information to/from another
PLMN or ISDN subscriber over the signalling channel in
association with a call to the other subscriber.
V - VTX host
V Value only.
VA Viterbi Algorithm (used in channel equalizers). An algorithm to
compute the optimal (most likely) state sequence in a model
given a sequence of observed outputs.
VAD Voice Activity Detection. A process used to identify presence or
absence of speech data bits. VAD is used with DTX.
VAP Videotex Access Point.
VBS Voice Broadcast Service. VBS allows the distribution of speech
(or other signals which can be transmitted via the speech
codec), generated by a service subscriber, into a predefined
geographical area to all or a group of service subscribers
located in this area.
VC See Virtual Circuit.
VCO Voltage Controlled Oscillator. An oscillator whose clock
frequency is determined by the magnitude of the voltage
presented at its input. The frequency changes when the
voltage changes.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit. A device used for the real-time temporary
display of computer output data. Monitor.
VGCS Voice Group Call Service.


Videotex The Videotex service is an interactive service, that by means of
proper access points and standardized procedures, provides
the access to data base information stored in host computers
external to the PLMN, via public telecommunication networks.
Virtual Circuit A connection between two devices, that functions as though
it is a direct connection, even though it may physically be
circuitous. The term is used most frequently to describe
connections between two hosts in a packet-switching network.
VLR Visitor Location Register. A GSM network element which
provides a temporary register for subscriber information for a
visiting subscriber. Often a part of the MSC.
VLSI Very Large Scale Integration (in ICs). The process of placing
between 100,000 and one million electronic components on
a single chip.
VMSC Visited MSC. (Recommendation not to be used).
vocoder Abbreviation for voice-coder. A device that usually consists of
a speech analyzer, which converts analog speech waveforms
into narrowband digital signals, and a speech synthesizer,
which converts the digital signals into artificial speech sounds.
VOX Voice Operated Transmission. An acoustoelectric transducer
and a keying relay connected so that the keying relay is
actuated when sound, or voice energy above a certain
threshold is sensed by the transducer. A vox is used to
eliminate the need for push-to-talk operation of a transmitter by
using voice energy to turn on the transmitter
VPLMN Visited PLMN.
VSC Videotex Service Centre.
V(SD) Send state variable.
VSP Vehicular Speaker Phone.
VSWR Voltage Standing Wave Ratio. In a transmission line, the ratio
of maximum to minimum voltage in a standing wave pattern.
Note: The VSWR is a measure of impedance mismatch
between the transmission line and its load. The higher the
VSWR, the greater the mismatch. The minimum VSWR, i.e.,
that which corresponds to a perfect impedance match, is unity.
VTX host The components dedicated to Videotex service.


W - WWW
WAN Wide Area Network. A physical or logical network that provides

data communications to a larger number of independent users
than are usually served by a LAN and is usually spread over a
larger geographic area than that of a LAN. WANs may include
physical networks, such as ISDN networks, X.25 networks,
and T1 networks.
WPA Wrong Password Attempts (counter). Some supplementary
services have the option of the subscriber using a password.
If a password check is done with an incorrect password, the
WPA is incremented by one. If a password check is passed,
the WPA is set to zero. If the WPA exceeds the value three,
the subscriber will have to register a new password with the
service provider.
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network management
purposes.
WSF Work Station Function block.
WWW World Wide Web. An international, virtual-network-based
information service composed of Internet host computers that
provide on-line information in a specific hypertext format. WWW
servers provide hypertext metalanguage (HTML) formatted
documents using the hypertext transfer protocol, HTTP.
Information on the WWW is accessed with a hypertext browser.


X - X Window
X.25 X.25, adopted as a standard by the CCITT, is a commonly used

protocol for public packet-switched networks (PSPDNS). The
X.25 protocol allows computers on different public networks to
communicate through an intermediary computer at the network
layer level. The protocol corresponds closely to the data-link
and physical-layer protocols defined in the OSI communication
model.
X.25 link A communications link which conforms to X.25 specifications
and uses X.25 protocol (NE to OMC links).
XBL Transcoder to BSS Link. The carrier communications link
between the Transcoder (XCDR) and the BSS.
XCB Transceiver Control Board. Part of the Transceiver.
XCDR Full-rate Transcoder. The XCDR is the digital signal processing
equipment required to perform GSM-defined speech encoding
and decoding. In terms of data transmission, the speech
transcoder interfaces the 64 kbit/s PCM in the land network to
the 13 kbit/s vocoder format used on the Air Interface. See
also RXCDR.
XCDR board The circuit board required to perform speech transcoding at
the BSS or (R)XCDR). Also known as the MSI (XCDR) board.
Interchangeable with the GDP board.
XFER Transfer.
XID eXchange IDentifier.
xterm X terminal window. A terminal emulator program for the X
Window System. A user can have many different invocations
of xterm running at once on the same display, each of which
provides independent input and output for the process running
in it (normally a shell).
X Window A specification for device-independent windowing operations
on bitmap display devices.
ZC
ZC Zone Code. Part of the RSZI. The ZC identifies a regional

subscription zone as a pattern of allowed and not allowed
location areas uniquely within a PLMN.



Net03 NTWK Perf Gsr7 Inc Amr

Загружено:

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

Оригинальное название

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

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

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

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

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

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

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

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

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

Net03 NTWK Perf Gsr7 Inc Amr

Загружено:

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

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

NET03 - Network Performance inc AMR

NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR

NET03 - Network Performance inc AMR

Chapter 1: BSS Statistics Introduction

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR i

Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Chapter 2: Statistical Data Types

Chapter 3: Statistical MMI Commands

ii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Changing statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8

Chapter 4: Call Statistics

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR iii

Adaptive Multi-Rate - See Chapter 10 for detail . . . . . . . . . . . . . . . . . . . . . . . . 4-32

iv NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Chapter 5: Handover Statistics

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR v

vi NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Chapter 6: Interface Statistics

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR vii

MTL Interface Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

viii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Perform Location Abort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48

Chapter 7: Key Statistics

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR ix

Chapter 8: Network Health Statistics

x NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Chapter 9: Call Model Statistics

Chapter 10: Adaptive Multi-Rate

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR xi

Chapter 11: Appendix A

Chapter 12: Answers

Chapter 13: Glossary of Terms

xii NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

NET03 - Network Performance inc AMR

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 1

ETSI specification number

2 NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

The tags are positioned in text as follows:

New and amended feature information Tag position in text

• Full sections under a main heading • Main heading

• Full paragraphs under subheadings • Subheading

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 3

Special key sequences

CTRL-c Press the Control and c keys at the same time.

4 NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

Reporting safety issues

Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 5

Warnings and cautions

Example and format

Failure to comply with warnings

Example and format

6 NET03 - Network Performance inc AMR ©MOTOROLA LTD.2002

• Potentially hazardous voltage.

Potentially hazardous voltage

WARNING This equipment operates from a potentially hazardous voltage

©MOTOROLA LTD.2002 NET03 - Network Performance inc AMR 7

WARNING High RF potentials and electromagnetic fields are present in this

WARNING When dismantling heavy assemblies, or removing or replacing

WARNING Do not install substitute parts or perform any unauthorized modification

WARNING Lithium batteries, if subjected to mistreatment, may burst and