motorola BSS counters

CH

AP

TE

R 2

STA

TIS

TIC

AL

OP

ER

AT

ION

SC

HA

PT

ER

3B

SS

STA

TIS

TIC

SC

HA

PT

ER

4C

EL

L S

TAT

IST

ICS

CH

AP

TE

R 5

NE

IGH

BO

UR

STA

TIS

TIC

SC

HA

PT

ER

1 IN

TR

OD

UC

TIO

N TO

STA

TIS

TIC

S

CH

AP

TE

R 7

GP

RO

C A

ND

DP

RO

CS

TAT

IST

ICS

CH

AP

TE

R 8

LM

TL

STA

TIS

TIC

SC

HA

PT

ER

9B

SS

STA

TS

FO

R L

OC

AT

ION

SE

RV

ICE

S S

UP

PO

RT

CH

AP

TE

R 10

MT

L S

TAT

IST

ICS

CH

AP

TE

R 6

CA

RR

IER

AN

D T

IME

SL

OT

STA

TIS

TIC

S

CH

AP

TE

R 12

PC

U S

TAT

IST

ICS

CH

AP

TE

R 13

BS

S–S

ML

C S

TAT

IST

ICS

CH

AP

TE

R 14

WE

B M

MI S

TAT

IST

ICS

CH

AP

TE

R 15

HR

AN

D A

MR

STA

TIS

TIC

SC

HA

PT

ER

11C

BL

, GS

L, O

ML

, RS

L A

ND

XB

L S

TAT

IST

ICS

CH

AP

TE

R 17

KE

Y S

TAT

IST

ICS

CH

AP

TE

R 18

NE

TW

OR

K H

EA

LTH

RE

PO

RT

S

CH

AP

TE

R 19

LA

DD

ER

DIA

GR

AM

SC

HA

PT

ER

20IM

PAC

TS

ON

STA

TIS

TIC

SC

HA

PT

ER

16C

AL

L M

OD

EL

STA

TIS

TIC

S

IND

EX

MAINTENANCE INFORMATIONGSM STATISTICS APPLICATION

GSM SOFTWARE RELEASE 7 HALF RATE

GSR7 Half Rate

CONTROLLED INTRODUCTION

68P02901W56-Q

MA

INT

EN

AN

CE

INF

OR

MA

TIO

NG

SM

STA

TIS

TIC

S A

PP

LIC

AT

ION

GS

M S

OF

TW

AR

E R

EL

EA

SE

7 HA

LF

RA

TE

GSR7 Half Rate

CONTROLLEDINTRODUCTION

68P02901W56-Q

Maintenance Information: GSMStatistics Application

© 1994 - 2004 Motorola, Inc.

68P02901W56-Q

All Rights Reserved CONTROLLED INTRODUCTION 24 May 2004

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 tocopy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola productsdescribed in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchaseof Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patentapplications 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 inaccordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part ofthe 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 omissionsin this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improvereliability, 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 tonotify 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.

CONTROLLED INTRODUCTION 24 May 2004

Tableof

Contents

Contents

Maintenance Information: GSM Statistics ApplicationIssue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 1: Introduction to statisticsIntroduction to GSM Statistics Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Types of raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Statistic usages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Chapter 2: Statistical operationsEnabling/disabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Displaying statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Setting the statistic interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Displaying the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Displaying the statistic interval start times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Setting statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Displaying statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Chapter 3: BSS statisticsBSS statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2BSS_OVLD_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4HO_REQ_MSC_PROTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5INTRA_BSS_HO_CAUSE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6MA_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8MSC_OVLD_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9MSGS_DISCARD_ON_GPROC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10MSGS_DISCARD_ON_RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11PAGE_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12ROUTING_SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

68P02901W56-Q i

24 May 2004 CONTROLLED INTRODUCTION

Contents

ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14RSL_LCF_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17SCCP_MSGS_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Chapter 4: Cell statisticsCell statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8ACCESS_PER_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9ACCESS_PER_PPCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13ALLOC_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14ALLOC_SDCCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16ALLOC_TCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17ALLOC_TCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18ASSIGNMENT_REDIRECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19AVAILABLE_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20AVAILABLE_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21BAD_HO_REFNUM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25BUSY_TCH_CARR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27CALL_SP_VERS_DOWNGRADE_MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28CALLS_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30CHAN_REQ_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31CHAN_REQ_MS_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33CIPHER_MODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34CLASSMK_UPDATE_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35CLR_CMD_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36CLR_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37CONGEST_EXIST_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39CONGEST_STAND_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40CONN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41CONN_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43DYNET_ASSIGN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44DYNET_CALL_REJECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45ER_INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46ER_INTRA_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47FLOW_CONTROL_BARRED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49HO_REQ_MSC_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51HO_REQ_ACK_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52IDLE_TCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54IDLE_TCH_INTF_BAND1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55IDLE_TCH_INTF_BAND2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56IDLE_TCH_INTF_BAND3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57IDLE_TCH_INTF_BAND4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58IN_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59IN_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

ii 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

Maintenance Information: GSM Statistics Application Contents

INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62INV_EST_CAUSE_ON_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69MA_REQ_FROM_MSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72MS_ACCESS_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74MS_TCH_USAGE_BY_TYPE_PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75MT_LCS_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77NUM_EMERG_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78NUM_EMERG_REJECTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80NUM_EMERG_TERM_SDCCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81OK_ACC_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85OUT_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87OUT_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91PAGING_REQUESTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94PPCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100SECOND_ASSIGN_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101SMS_INIT_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102SMS_INIT_ON_SDCCH_HO_IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104SMS_NO_BCAST_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106TCH_CONG_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107TCH_DELAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110TCH_USAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111TCH_USAGE_EXT_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113TCH_USAGE_INNER_ZONE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114TOTAL_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117

Chapter 5: Neighbour statisticsIntroduction to neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2IN_INTRA_BSS_NC_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8IN_INTRA_BSS_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9OUT_HO_NC_CAUSE_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10OUT_HO_NC_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

68P02901W56-Q iii


Contents

Chapter 6: Carrier and timeslot statisticsCarrier and timeslot statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2ALLOC_SDCCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4ALLOC_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6CHAN_DL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9CHAN_UL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11FER_GSM_FR_EFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16RBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22U_BER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23UPLINK_PATH_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Chapter 7: GPROC and DPROC statisticsCPU_USAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Chapter 8: LMTL statisticsLMTL statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2LMTP_CONGESTION_LOST_MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4LMTP_MSU_DISCARDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5LMTP_CHANGEBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6LMTP_CHANGEOVER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7LMTP_LOCAL_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8LMTP_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9LMTP_LINKFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10LMTP_LOCAL_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11LMTP_LOCAL_MGT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12LMTP_MGT_INHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13LMTP_MGT_UNINHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14LMTP_MSU_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15LMTP_MSU_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16LMTP_NEG_ACKS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17LMTP_RE_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18LMTP_REMOTE_MGT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19LMTP_REMOTE_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20LMTP_RESTORATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21LMTP_SIF_SIO_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22LMTP_SIF_SIO_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23LMTP_SL_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24LMTP_SL_ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25LMTP_REMOTE_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26LMTP_SL_ERROR_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27LMTP_SL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28LMTP_SL_FIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29LMTP_START_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30LMTP_STOP_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31LMTP_SU_ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32LMTP_UNAVAILABLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33LMTP_SIB_RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

iv 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004


LMTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35LMTP_SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36

Chapter 9: BSS statistics for Location Services supportBSS statistics for Location Services support subgroups. . . . . . . . . . . . . . . . . . . . . . . . . . 9-2BSSLAP_ABORT_RCV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4BSSLAP_ABORT_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5BSSLAP_MS_POS_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6BSSLAP_MS_POS_RESP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7BSSLAP_REJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8BSSLAP_RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9BSSLAP_TA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10BSSLAP_TA_RESP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11BSSLAP_TOA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12BSSMAP_CONLESS_INFO_RCV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13BSSMAP_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14BSSMAP_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15BSSMAP_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16BSSMAP_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17BSSMAPLE_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18BSSMAPLE_CONLESS_INFO_SENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19BSSMAPLE_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20BSSMAPLE_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21BSSMAPLE_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

Chapter 10: MTL statisticsMTL statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2BUSY_CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4CONGESTION_LOST_MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6MSU_DISCARDED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7MTP_CHANGEBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8MTP_CHANGEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9MTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10MTP_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11MTP_LINKFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12MTP_LOCAL_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13MTP_LOCAL_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14MTP_MGT_INHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15MTP_MGT_UNINHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16MTP_MSU_RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17MTP_MSU_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18MTP_NEG_ACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19MTP_RE_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20MTP_REMOTE_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21MTP_REMOTE_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22MTP_RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23MTP_SIF_SIO_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24MTP_SIF_SIO_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25MTP_SL_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26MTP_SL_ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27MTP_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28MTP_SL_ERROR_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29MTP_SL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30MTP_SL_FIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31

68P02901W56-Q v


Contents

MTP_START_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32MTP_STOP_RPO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33MTP_SU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34MTP_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35SIB_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38SL_STOP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39

Chapter 11: CBL, GSL, OML, RSL and XBL statisticsX.25/LAPD Level: X.25 and LAPD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2ATER_CHANNEL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3ATER_EMERG_PREEMPT_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5FRMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6I_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7I_FRAMES_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8INVALID_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9LAPD_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10N2_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11SABM_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12

Chapter 12: PCU statisticsPCU statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2AIR_DL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7AIR_DL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8AIR_DL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10AIR_UL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11AIR_UL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12AIR_UL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14CELL_FLUSH_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15CH_REQ_UNSVCD_PCU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18CHANNEL_REQS_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20CODING_SCHEME_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22CONG_REL_DL_SCTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24CS12_ON_32K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26DL_BUSY_PDTCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27DL_PDTCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29DL_PDTCH_Q_LENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31DL_RADIO_BLKS_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32DL_RADIO_BLKS_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34DL_RADIO_BLKS_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36DL_RADIO_BLKS_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-38DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-40DL_RLC_DDTR_BLKS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-45DL_RLC_STALLED_BLKS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49DL_TBF_TIME_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51DL_TBF_TIME_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-52DL_TBF_TIME_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53

vi 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004


DL_TBF_TIME_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-54EGPRS_64K_CHANNELS_SWITCHED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55EGPRS_64K_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-56EGPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57EGPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-58G_RACH_UNSVCD_BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-60GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-63GBL_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-64GBL_PAGING_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-65GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-67GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69GPRS_32K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-70GPRS_32K_DL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71GPRS_32K_UL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74GPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-75GPRS_CELL_RESELECT_ATTMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-77GPRS_CELL_RESELECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-78GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-79GPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-80GPRS_DYNET_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-81GPRS_DYNET_RES_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-83GPRS_DYNET_SWI_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-84GPRS_MS_NEIGHBOR_STRONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-85GPRS_PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-86GPRS_PPCH_PAGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-88GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90IDLE_PDTCH_INTF_BAND0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-92IDLE_PDTCH_INTF_BAND1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-93IDLE_PDTCH_INTF_BAND2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-94IDLE_PDTCH_INTF_BAND3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-95IDLE_PDTCH_INTF_BAND4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96IMM_ASSGN_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97MS_CLASS_1_10_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99MS_CLASS_11_20_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101MS_CLASS_21_29_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-103NO_PDTCH_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-105NO_PDTCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-106PRP_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-107UL_BUSY_PDTCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-109UL_PDTCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-111UL_PDTCH_Q_LENGTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112UL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-113UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-114UL_RADIO_BLKS_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-116UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-118UL_RADIO_BLKS_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-120UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-122UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-124UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-126

68P02901W56-Q vii


Contents

UL_TBF_TIME_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-128UL_TBF_TIME_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-129UL_TBF_TIME_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-130UL_TBF_TIME_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-131

Chapter 13: BSS-SMLC statisticsBSS-based SMLC statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2L_ROUTING_SYNTAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3L_ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4L_SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5L_SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6L_SCCP_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7L_SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8L_SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9L_SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10PAGE_REQ_FROM_SMLC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11

Chapter 14: Web MMI statisticsMMI statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Chapter 15: HR and AMR statisticsHR statistics group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2AMR statistics group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3ALLOC_TCH_FAIL_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4ALLOC_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6AMR_DECREASE_THRESH_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7AMR_FR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8AMR_FR_DL_ADAPTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9AMR_FR_UL_ADAPTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10AMR_FR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11AMR_HR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12AMR_HR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13AMR_HR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14AMR_HR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15AMR_INCREASE_THRESH_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16AVAILABLE_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17BUSY_TCH_CARR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18BUSY_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19FER_AMR_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20FER_AMR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22FER_GSM_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-24HO_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-26RF_LOSSES_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-27TCH_CONG_INNER_ZONE_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-28TCH_CONGESTION_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-29

Chapter 16: Call model statisticsCALL_DURATION (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2CALL_SETUP_TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3HANDOVERS_PER_CALL (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4IMSI_DETACHES_TO_CALL (Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5INTRA_BSS_HO_TO_ALL_HO (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6

viii 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004


LOCATION_UPDATE_FACTOR (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7LOCATION_UPDATES_TO_CALLS (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8PAGES_PER_CALL (PPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9PAGES_PER_SECOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10PAGING_RATE (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11SMS_TO_CALL_RATIO (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12

Chapter 17: Key statisticsKey statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2ATTEMPT_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6CELL_TCH_ALLOCATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7CELL_TCH_ASSIGNMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9HANDOVER_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10MEAN_ARRIVAL_TIME_BETWEEN_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13MEAN_TCH_BUSY_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17SDCCH_ACCESS_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19SDCCH_SETUP_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20SDCCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21SDCCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24SUCCESS_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26SUCCESS_INTERNAL_HO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-27TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28TCH_BLOCKING_RATE_INNER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29TCH_BLOCKING_RATE_OUTER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30TCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31TCH_MEAN_HOLDING_TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-36TOTAL_CALLS_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38UNSUCCESS_INTERNAL_HO_NOREEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39UNSUCCESS_INTERNAL_HO_REEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-40

Chapter 18: Network health reportsNetwork health statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8AIR_INTERFACE_BW_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9AIR_INTERFACE_BW_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10AIR_INTERFACE_BW_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12ASSIGNMENT_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . 18-14CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . . 18-16CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 18-17CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19

68P02901W56-Q ix


Contents

CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20CELL_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21CS1_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22CS1_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23CS2_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24CS2_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25CS3_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26CS3_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-27CS4_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28CS4_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29DL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-30DL_AIR_INTERFACE_BW_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31DL_AIR_INTERFACE_BW_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32DL_AIR_INTERFACE_BW_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33DOWNLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36GBL_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38GPRS_BW_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39GPRS_BW_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40GPRS_DL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41GPRS_UL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42HO_CAUSE_ADJ_CH_INTERF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-43HO_CAUSE_BAND_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-44HO_CAUSE_BAND_REASSGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-45HO_CAUSE_CONGEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-46HO_CAUSE_DISTANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-47HO_CAUSE_DLINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48HO_CAUSE_DLLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-49HO_CAUSE_DLQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-50HO_CAUSE_PWRBGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51HO_CAUSE_UPINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52HO_CAUSE_UPLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53HO_CAUSE_UPQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-54HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55IN_INTER_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-56IN_INTER_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57IN_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-58INCOMING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-59INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-62INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-65MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-67MEAN_TIME_BETWEEN_DROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-68MEAN_TIME_BETWEEN_HOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-72OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS. . . . . . . . . . . . . . . . . . . . . . . . . . . 18-73OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS. . . . . . . . . . . . . . . . . . . . . . . 18-74OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . 18-76

x 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004


OUT_INTRA_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78OUT_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79OUTGOING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84PERCENTAGE_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-85PERCENTAGE_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-86PERCENTAGE_INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-87PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK. . . . . . . . . . . . . . . . . . . . . . . . . 18-88RANKING_FORMULA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-89RF_ASSIGN_FAIL_RATE_LOST_MS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-90RF_ASSIGN_FAIL_RATE_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-91RF_ASSIGNMENT_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-92SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-93SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-94SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-95SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-96SDCCH_USAGE_ACCESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-98SDCCH_USAGE_CALL_REESTABLISH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-99SDCCH_USAGE_EMERGENCY_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-100SDCCH_USAGE_IMSI_DETACH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-101SDCCH_USAGE_LOCATION_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-102SDCCH_USAGE_MS_ORIGINATED_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-103SDCCH_USAGE_MS_ORIGINATED_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-104SDCCH_USAGE_SMS_ORIGINATED_SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-105SDCCH_USAGE_PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-106SDCCH_USAGE_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-107SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF . . . . . . . . . . . . . . . . . . 18-108SPILL_OVER_FACTOR_DIRECTED_RETRY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-109SPILL_OVER_FACTOR_MULTIBAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-110TCH_ACCESSES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-111TCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-113TCH_CONGESTION_TIME_INNER_ZONE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-114TCH_CONGESTION_TIME_OUTER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-115TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-116TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-118UL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-120UL_AIR_INTERFACE_BW_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-121UL_AIR_INTERFACE_BW_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-122UL_AIR_INTERFACE_BW_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-123UPLINK_PDTCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-124UPLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-125

Chapter 19: Ladder diagramsLadder diagram constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2Phone call model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3Call procedure milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5Call setup and handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9Assignment to TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14Intra-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17

68P02901W56-Q xi


Contents

Inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26Call clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-35Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-41Intra-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-42Inter-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-46Interband assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-50Band Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-53MTL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-55GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-60Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-64Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-69

Chapter 20: Impacts on statisticsExtended GSM (EGSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2Approximate equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6Questions and answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9

xii 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

Listof

Figures

List of Figures

Figure 1-1: Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Figure 1-2: Histogram of a weighted distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . 1-11Figure 1-3: Diagram of immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Figure 19-1: Diagram of immediate assignment failure. . . . . . . . . . . . . . . . . . . . . . . . . . 19-2Figure 19-2: Handover procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4Figure 19-3: Connection establishment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10Figure 19-4: Connection establishment failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11Figure 19-5: Immediate assignment blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12Figure 19-6: Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12Figure 19-7: Connection establishment (mobile terminated call) successful . . . . . . . . . . . . . . . . 19-13Figure 19-8: TCH assignment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14Figure 19-9: Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15Figure 19-10: TCH assignment blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15Figure 19-11: TCH assignment fail-recovered to SDCCH . . . . . . . . . . . . . . . . . . . . . . . . 19-16Figure 19-12: Handover (intra-cell) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17Figure 19-13: Handover (intra-cell) blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18Figure 19-14: Handover (intra-cell) fail-recovered to source channel . . . . . . . . . . . . . . . . . . . 19-18Figure 19-15: Handover (intra-cell) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19Figure 19-16: Handover (inter-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20Figure 19-17: Handover (inter-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21Figure 19-18: Handover (inter-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-22Figure 19-19: Handover (inter-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23Figure 19-20: Inter-BSS handover failure with lost mobile . . . . . . . . . . . . . . . . . . . . . . . . 19-24Figure 19-21: Inter-BSS handover directed retry external . . . . . . . . . . . . . . . . . . . . . . . . 19-25Figure 19-22: Handover (intra-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26Figure 19-23: Handover (intra-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27Figure 19-24: Handover (intra-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28Figure 19-25: Handover (intra-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29Figure 19-26: Intra-BSS handover standard directed retry . . . . . . . . . . . . . . . . . . . . . . . . 19-30Figure 19-27: BSS initiated call clearing-cipher mode fail . . . . . . . . . . . . . . . . . . . . . . . . 19-31Figure 19-28: BSS initiated call clearing (RF loss on an SDCCH) . . . . . . . . . . . . . . . . . . . . 19-32Figure 19-29: BSS initiated call clearing (RF loss on a TCH) . . . . . . . . . . . . . . . . . . . . . . . 19-33Figure 19-30: BSS initiated call clearing (queueing timeout) . . . . . . . . . . . . . . . . . . . . . . . 19-34Figure 19-31: MS originated short message service (point-to-point) . . . . . . . . . . . . . . . . . . . . 19-35Figure 19-32: MS terminated short message service (point-to-point) . . . . . . . . . . . . . . . . . . . 19-36Figure 19-33: Intra-BSS congestion relief handover procedure . . . . . . . . . . . . . . . . . . . . . . 19-38Figure 19-34: Intra-BSS directed retry procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40Figure 19-35: Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-41Figure 19-36: Successful intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-43Figure 19-37: Unsuccessful interband handover with fail-recovered source cell . . . . . . . . . . . . . . 19-44Figure 19-38: Unsuccessful interband handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-45Figure 19-39: Successful inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-47

68P02901W56-Q xiii


List of Figures

Figure 19-40: Inter-BSS handover unsuccessful with fail-recovered source cell . . . . . . . . . . . . . . 19-48Figure 19-41: Inter-BSS handover unsuccessful due to invalid frequency supported . . . . . . . . . . . . 19-49Figure 19-42: Invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-50Figure 19-43: Intra-BSS handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51Figure 19-44: Unsuccessful band reassign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-52Figure 19-45: RSL link scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-54Figure 19-46: MTL link scenario (Part I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-56Figure 19-47: MTL link transition scenarios (Part II) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57Figure 19-48: MTL link transition scenarios (Part III) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-58Figure 19-49: MTL link transition scenarios (Part IV) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-59Figure 19-50: GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-60Figure 19-51: GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-61Figure 19-52: CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-61Figure 19-53: GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-62Figure 19-54: GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-63Figure 19-55: Accessibility CHANNEL_REQ_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-64Figure 19-56: GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . 19-65Figure 19-57: Accessibility and GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66Figure 19-58: MS CLASS statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67Figure 19-59: GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-68Figure 19-60: Uplink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70Figure 19-61: Downlink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71Figure 20-1: Approximate equality procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5Figure 20-2: Phantom RACHs illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

xiv 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

Listof

Tables

List of Tables

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Table 2-1: Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Table 4-1: Default bin ranges for BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Table 4-2: Default bin ranges for BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Table 5-1: Neighbour cell statistics pegged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Table 6-1: FER_GSM_FR_EFR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . 6-12Table 6-2: Default bin ranges for INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Table 6-3: Signal level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Table 6-4: RBER Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Table 6-5: Bin ranges for ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22Table 10-1: BUSY CICS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Table 12-1: AIR_DL_DATA_BLKS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8Table 12-2: AIR_UL_DATA_BLKS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12Table 12-3: CODING_SCHEME_CHANGE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22Table 12-4: DL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27Table 12-5: Bin ranges for DL_RADIO_BLKS_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32Table 12-6: Bin ranges for DL_RADIO_BLKS_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34Table 12-7: Bin ranges for DL_RADIO_BLKS_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36Table 12-8: Bin ranges for DL_RADIO_BLKS_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-38Table 12-9: Bin ranges for DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 12-40Table 12-10: Bin ranges for DL_RLC_DDTR_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42Table 12-11: Bin ranges for DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43Table 12-12: Bin ranges for DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-45Table 12-13: Bin ranges for DL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 12-47Table 12-14: Bin ranges for DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . 12-49Table 12-15: GBL_DL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61Table 12-16: GBL_UL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . 12-67Table 12-17: GPRS_DYNET_FAILURES bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-81Table 12-18: GPRS_DYNET_RES_REQS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-83Table 12-19: GPRS_DYNET_SWI_REQS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-84Table 12-20: Default bin ranges for GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . 12-88Table 12-21: Default bin ranges for GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . . . . 12-90Table 12-22: IMM_ASSGN_CAUSE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97Table 12-23: MS_CLASS_1_10_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99Table 12-24: MS_CLASS_11_20_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101Table 12-25: MS_CLASS_21_29_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-103Table 12-26: Mapping between timeslots pending service and PRP load. . . . . . . . . . . . . . . . . . 12-107Table 12-27: PRP load range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-107Table 12-28: UL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-109Table 12-29: Bin ranges for UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . 12-114Table 12-30: Bin ranges for UL_RADIO_BLKS_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . 12-116

68P02901W56-Q xv


List of Tables

Table 12-31: Bin ranges for UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . 12-118Table 12-32: Bin ranges for UL_RADIO_BLKS_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . 12-120Table 12-33: Bin ranges for UL_RLC_ACK_NEW_BLKS. . . . . . . . . . . . . . . . . . . . . . . . 12-122Table 12-34: Bin ranges for UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-124Table 12-35: Bin ranges for UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . 12-126Table 14-1: Location of MMI PCU real-time stats descriptions . . . . . . . . . . . . . . . . . . . . . . 14-2Table 14-2: Location of MMI BSC/BTS real-time stats descriptions . . . . . . . . . . . . . . . . . . . 14-2Table 15-1: FER_AMR_FR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . 15-20Table 15-2: FER_AMR_HR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . 15-22Table 15-3: FER_GSM_HR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . 15-24Table 17-1: Key statistic descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4Table 19-1: Call setup and handover statistics matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6Table 20-1: MS access to a traffic channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3Table 20-2: Impact due to increased handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3Table 20-3: Impact due to congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4

xvi 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

AboutThis

Manual

Maintenance Information: GSM StatisticsApplication

What is Covered In This Manual?The manual provides context information and detailed descriptions of the GSR7 raw, key and networkhealth statistics sets supported by Motorola GSM cellular equipment.

Detailed information on previous GSR statistical information, for example, GSR 5.1 and GSR6,can be obtained from the appropriate GSM Statistics Application manual.

The target audience for this manual is GSM network operators and administrators.

68P02901W56-Q 1


Issue status of this manual


The following shows the issue status of this manual since it was first released.

Version information

The following table lists the versions of this manual in order of issue:

Table 1 Manual version history

Manualissue Date of issue Remarks

O 03 Oct 1994 Original issue - Software release 1.2.2.x

A 30 Dec 1994 Issue A - Software release 1.2.3.x

B 01 Sep 1995 Issue B - Software release 1.3.0.x

C 31 May 1996 Issue C - Software release 1.4.0.x

D 28 Mar 1997 Issue D - Software release 1.4.1.x

E 29 Aug 1997 Issue E - GSM Software Release 2

F 27 Apr 1998 Issue F - GSM Software Release 3

G 12 Mar 1999 Issue G - GSM Software Release 4

H 14 Jul 2000 Issue H - GSM Software Release 1.6.1.3

J 31 Jul 2001 Issue J - GSM Software Release 5

K 31 May 2002 Issue K - GSM Software Release 5.1

L 30 Nov 2002 Issue L - GSM Software Release 6

M 02 May 2003 Issue M - GSM Software Release 6 (Horizon II)

P 13 Nov 2003 Issue P - GSM Software Release 7

Q 24 May 2004 Issue Q- GSM Software Release 7 Half Rate(Controlled Introduction)

2 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004


Resolution of Service Requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

ServiceRequest

GMRNumber Remarks

N/A N/A

68P02901W56-Q 3


General information

General information

• 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 failureof the customer, or any one acting on the customers behalf, to abide by the instructions,system parameters or recommendations made in this manual

• If this manual was obtained when attending a Motorola training course, it will not be updatedor amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was suppliedunder normal operational circumstances, to support a major software release, then correctionswill be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).

Purpose

Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It isrecommended that all personnel engaged in such activities be properly trained by Motorola.

Failure to comply with Motorola’s operation, installation and maintenanceinstructions 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, althoughthey can be used to supplement and enhance the knowledge gained through such training.

Feature references

Most of the manuals in the set, of which this manual is part, are revised to accommodate featuresreleased at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. Inthese manuals, new and amended features are tagged to help users to assess the impact on installednetworks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research andDevelopment Prioritization (RDP) numbers. The tags include index references which are listed in themanual Index. The Index includes the entry feature which is followed by a list of the RDB or RDPnumbers for the released features, with page references and hot links in electronic copy.


General information

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:

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:

• Full sections under a main heading

• Full paragraphs under subheadings

Immediately after the headings as follows:

• Main heading

• Subheading

New or amended complete Figures and Tables After the Figure or Table number and beforethe title text.

Warning, Caution and Note boxes. Immediately before the affected text in the box.

General command syntax, operator input ordisplays (in special fonts).

On a separate line immediately above theaffected item.

For a list of Roadmap numbers and the RDB or RDP numbers of the features included in thissoftware release, refer to the manualSystem Information: GSM Overview (68P02901W01), or tothe manual System Information: GPRS Overview (68P02903W01).

Cross references

Throughout this manual, references are made to external publications, chapter numbers andsection names. The references to external publications are shown in italics, chapter andsection name cross references are emphasised blue in text.

This manual is divided into uniquely identified and numbered chapters that, in turn, aredivided into sections. Sections are not numbered, but are individually named at the top ofeach page, and are listed in the table of contents.

Data encryption

In order to avoid electronic eavesdropping, data passing between certain elements in the GSM andGPRS network is encrypted. In order to comply with the export and import requirements of particularcountries, this encryption occurs at different levels as individually standardised, or may not be presentat all in some parts of the network in which it is normally implemented. The manual set, of whichthis manual is a part, covers encryption as if fully implemented. Because the rules differ in individualcountries, limitations on the encryption included in the particular software being delivered, are coveredin the Release Notes that accompany the individual software release.

68P02901W56-Q 5


General information

Text conventions

The following conventions are used in the Motorola cellular infrastructure manuals to representkeyboard input text, screen output text and special key sequences.

InputCharacters typed in at the keyboard are shown like this.

OutputMessages, prompts, file listings, directories, utilities, and environmentalvariables that appear on the screen are shown like this.

Special key sequencesSpecial 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

Reporting safety issues

Whenever a safety issue arises, carry out the following procedure in all instances. Ensurethat all site personnel are familiar with this procedure.

Procedure

Whenever a safety issue arises:

Procedure 1 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 writtenreport 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 NetworkResolution Centre.

68P02901W56-Q 7


Warnings and cautions


The following describes how warnings and cautions are used in this manual and inall manuals of this Motorola manual set.

Warnings

A definition and example follow below:

Definition of WarningA warning is used to alert the reader to possible hazards that could cause loss of life, physicalinjury, or ill health. This includes hazards introduced during maintenance, for example, the use ofadhesives and solvents, as well as those inherent in the equipment.

Example and format

Do not look directly into fibre optic cables or data in/out connectors. Laserradiation can come from either the data in/out connectors or unterminatedfibre 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 equipmentdescribed in the Motorola manuals. Failure to comply with these warnings, or with specificwarnings elsewhere in the Motorola manuals, or on the equipment itself, violates safetystandards of design, manufacture and intended use of the equipment. Motorola assumes noliability for the customer’s failure to comply with these requirements.

Cautions

A definition and example follow below:



Definition of CautionA caution means that there is a possibility of damage to systems, software or individual items ofequipment within a system. However, this presents no danger to personnel.

Example and format

Do not use test equipment that is beyond its due calibration date;arrange for calibration to be carried out.

68P02901W56-Q 9


General warnings

General warnings

Observe the following specific warnings during all phases of operation, installation andmaintenance 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 assumesno 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 workingwith 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 beincorporated into procedures as applicable.

These must be observed by all personnel at all times when working with the equipment, as mustany other warnings given in text, in the illustrations and on the equipment.


General warnings

Potentially hazardous voltage

This equipment operates from a potentially hazardous voltage of 230 V a.c. singlephase or 415 V a.c. three phase supply. To achieve isolation of the equipmentfrom the a.c. supply, the a.c. 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.

Motorola GSM equipment does not utilise high voltages.

Electric shock

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 materialand 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 evendeath, 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. ALWAYSsend for trained first aid or medical assistance IMMEDIATELY.

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

High RF potentials and electromagnetic fields are present in this equipmentwhen in operation. Ensure that all transmitters are switched off whenany antenna connections have to be changed. Do not key transmittersconnected to unterminated cavities or feeders.

68P02901W56-Q 11


General warnings

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 Exposureto Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic FieldsHigh Frequency (10 kHz to 300 GHz).

Laser radiation

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 unterminatedfibre optic cables connected to data in/out connectors.

Lifting equipment

When dismantling heavy assemblies, or removing or replacing equipment, acompetent responsible person must ensure that adequate lifting facilities areavailable. Where provided, lifting frames must be used for these operations.

When dismantling heavy assemblies, or removing or replacing equipment, the competent responsibleperson must ensure that adequate lifting facilities are available. Where provided, lifting framesmust be used for these operations. When equipment has to be manhandled, reference must bemade to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handlingof loads legislation for the country in which the equipment is used.

Parts substitution

Do not install substitute parts or perform any unauthorized modification ofequipment, because of the danger of introducing additional hazards. ContactMotorola if in doubt to ensure that safety features are maintained.


General warnings

Battery supplies

Do not wear earth straps when working with stand-by batterysupplies. Use only insulated tools.

Lithium batteries

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defectivelithium batteries must not be removed or replaced. Any boards containingdefective lithium batteries must be returned to Motorola for repair.

Contact your local Motorola office for how to return defective lithium batteries.

68P02901W56-Q 13


General cautions

General cautions

Observe the following cautions during operation, installation and maintenance of the equipmentdescribed in the Motorola manuals. Failure to comply with these cautions or with specific cautionselsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes noliability 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 tothe 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 mustany other cautions given in text, on the illustrations and on the equipment.

Fibre optics

Fibre optic cables must not be bent in a radius of less than 30 mm.

Static discharge

Motorola equipment contains CMOS devices. These metal oxide semiconductor(MOS) devices are susceptible to damage from electrostatic charge. See the sectionDevices sensitive to static in the preface of this manual for further information.


Devices sensitive to static

Devices sensitive to static

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer ofinsulation that is susceptible to damage from electrostatic charge. Such a charge applied tothe leads of the device could cause irreparable damage.

These charges can be built up on nylon overalls, by friction, by pushing the hands into highinsulation packing material or by use of unearthed soldering irons.

MOS devices are normally despatched from the manufacturers with the leads short circuited together,for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plasticfoam. Provided the leads are short circuited it is safe to handle the device.

Special handling techniques

In the event of one of these devices having to be replaced, observe the followingprecautions when handling the replacement:

• Always wear an earth strap which must be connected to the electrostaticpoint (ESP) on the equipment.

• Leave the short circuit on the leads until the last moment. It may be necessary to replacethe 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 plasticwork 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 toelectrostatic damage. However PCBs should be handled with care, preferably by their edges andnot 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.

68P02901W56-Q 15


Motorola manual set

Motorola manual set

The Motorola manual sets provide the information needed to operate, install and maintain the Motorolaequipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:

• Printed hard copy.

• Electronic, as fully navigable PDF files on:

The Motorola customer support web site at:(https://mynetworksupport.motorola.com/index.asp).

CD-ROM produced in support of a major system software release.

Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS softwarerelease, together with current versions of appropriate hardware manuals, and has additionalnavigation facilities. A snapshot copy of on-line documentation is also included, though itwill not be updated in line with subsequent point releases.

The CD-ROM does not include Release Notes or documentation supporting specialistproducts such as MARS or COP.

Ordering manuals and CD-ROMs

Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.

All orders must be placed with your Motorola Local Office or Representative.


GMR amendment

GMR amendment

Changes to a manual that occur after the printing date are incorporated into the manual usingGeneral Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and whenrequired. A GMR has the same identity as the target manual. Each GMR is identified by anumber in a sequence that starts at 01 for each manual at each issue.

GMR availability

GMRs are published as follows:

• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.

Remove and replace pages in this manual, as detailed on the GMR instruction sheet.

• Motorola service web - Updated at the same time as hard copies.

• CD-ROM - Updated periodically as required.

GMR instructions

When a GMR is inserted in this manual, the amendment record below is completed torecord the GMR. Retain the instruction sheet that accompanies each GMR and insert it ina suitable place in this manual for future reference.

68P02901W56-Q 17


GMR amendment

GMR amendment record

Record the insertion of GMRs in this manual in the following table:

GMR number Incorporated by (signature) Date

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20


Chapter

1Introduction to statistics

Statistics are pieces of numerical data which have been collected and systematically categorized. InGSM terms, the data collected is generated from network and system events, categorized as a rawstatistic type and used to determine system quality of service. This allows network operators andadministrators to gauge service accessibility, integrity and retainability.

The following topics are described:

• "Introduction to GSM Statistics Manual" on page 1-2

• "Types of raw statistics" on page 1-6

• "Statistic usages" on page 1-13

68P02901W56-Q 1-124 May 2004 CONTROLLED INTRODUCTION

Introduction to GSM Statistics Manual Chapter 1: Introduction to statistics

Introduction to GSM Statistics Manual

Statistics

This manual describes the statistical measurements generated by the BSS in response to monitorednetwork and system events. The statistics include statistical measurements defined in the GSMTechnical Specification 12.04, plus additional Motorola-defined statistics.

To facilitate easy access, the statistics are presented in alphabetical order.

Network management and planning

Network operators may use raw and processed statistics for the following networkmanagement and planning functions:

• Quality of service monitoring.

Service accessibility.

Service integrity.

Service retainability.

• Fault finding.

• Optimization.

• Network planning.

• Installation and commissioning.

Raw statistics

The BSS generates raw statistics for reporting individual network performance. The OMC-Rprocesses raw statistics to create key, network health and custom statistics. These statistics includecall processing, interface, and processor utilization measurements.

1-2 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual

Call statisticsCall processing functions and features generate statistics that show how the system is performing.

Interface statisticsTerrestrial interface activities generate interface statistics that show the activity on and condition of the interfacelinks. The interface links are the physical connections between the MS, BSS, and MSC network elements.

Processor utilization statisticsProcessor utilization statistics show the percentage of GPROC utilization.

Key statistics

Key statistics are generated at the OMC-R by processing raw statistics generated by the BSS,using predefined algorithms. These statistics are designed to give an overall indication of thecondition of the system and allow comparisons of similar time periods over a span of time, tohelp detect congestion trends and possible performance degradation.

Key statistics are also provided to facilitate the monitoring of the most important network parameters.For example, various handover failure statistics may be combined and averaged over the totalnumber of calls, to produce a handover failure rate key statistic.

The following are the key statistics groupings:

• Call Summary.

• Channel Usage.

• Connection Establishment.

• RF Loss Summary.

• MTL Utilization.

Network health statistics

Network health statistics are calculated at the OMC-R using a combination of raw and key statistics.These statistics are used to create BSS network performance reports. These reports provide anindication of the networks health from the subscribers perspective.

The following are the network health report groupings:

• Health check.

• GPRS performance.

• Handover performance.

• TCH congestion.


Introduction to GSM Statistics Manual Chapter 1: Introduction to statistics

• SDCCH congestion.

• Paging performance.

• Radio performance.

Custom statistics

The OMC-R permits the creation of custom statistics using the algebraic combination of existingraw and key statistics. Refer to the Installation and Configuration: GSM System Configuration(68P02901W17) manual for procedures on creating custom statistics.

Statistic terms

This manual contains the following statistical terms throughout this manual:

Application process - The process responsible for creating and pegging a statistic.

Bin - A collection area used for the storage of cumulative values for distribution and counter array statistics.

Distribution statistics:

The use of a bin is for measuring the frequency of an event. The measurement can be doneby time (weighted distributions) or by occurrences (normal distributions). There are 10 bins(numbered 0 - 9). Each bin has a low to high range.

Counter array statistics:

The use of a bin is for counting the number of occurrences on a per scenario or cause basis. Thenumber of bins varies based on the number of causes being tracked.

Cumulative value - The total value for the entire interval.

Default time interval - The key statistics default time interval is 0.5 hours when computing all key statistics.

The interval used for two key statistics, TCH_MEAN_HOLDING_TIME and SD-CCH_MEAN_HOLDING_TIME, is specified in seconds. To convert the default value of0.5 hours to seconds, multiply the 0.5 hours by 3600.

Interval - A recording period of time in which a statistic is pegged. The default time is 30minute intervals and there are 12 intervals of data stored at the BSS.

Interval expiry - The end of an interval.

Maximum value - The highest reported value for the interval.

Mean value - The average value for the interval.

Minimum value - The lowest reported value for the interval.

Number of periods - The value used in calculating the mean for durations. This value isincremented by one every time the duration timer is stopped.


Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual

Number of samples - The value used in calculating the mean for distributions. For a normal distribution,this value is incremented by one each time a value is reported. For a weighted distribution, thisvalue is incremented by the time difference since the last reported value.

Peg - A peg is a single incremental action modifying the value of a statistic.

Pegging - Pegging refers to recording a statistical value.

Reported value - The value reported by the application process pegging the statistic.

SUM - In the key and network health statistic formulae, SUM is the arithmetic total of a mathematicalformula for one or more cells selected in the OMC-R GUI Performance Management window. Themathematical formula may include a single raw statistic or a set of arithmetic functions.

Temporary value - This value is used in weighted distributions. The application processsupplies both the reported value (which is used to update a bin) and the temporary value(which is stored for updating a bin at interval expiry).

Threshold value - The threshold value can be set in the configuration management database using theMMI. When the reported value for a statistic equals the threshold value, an alarm is sent from the BSS tothe OMC-R. Thresholds may also be specified for individual bins in counter array statistics.


Types of raw statistics Chapter 1: Introduction to statistics

Types of raw statistics

Introduction

The BSS reports the following six types of statistics:

• Counter.

• Counter array.

• Gauge.

• Duration.

• Normal distribution.

• Weighted distribution.

Counter statistics

A counter statistic is the cumulative value of an event reported by an application process. Theapplication process increments or pegs the counter statistic by the reported value during an interval.The ALLOC_SDCCH statistic is an example of a counter statistic.

Threshold event reportingA counter statistic may have a user specified threshold that can generate an alarm when reached. TheBSS only reports one alarm to the OMC for a specific statistic during an interval.

Maximum valueThe maximum value of a counter statistic is 4294967294 (hex= 0xfffffffe). If a counter statistic reachesthe maximum value, it will remain at that value until the interval expiry.

Interval expiryInterval expiry is the end of a statistic interval. At the interval expiry, the BSS savesthe counter statistic value then resets it to zero.


Maintenance Information: GSM Statistics Application Types of raw statistics

Counter array statistics

Counter array statistics are the total number of times an event occurs and a breakdown of the causesor reasons why the event occurred during an interval. When an event occurs, the BSS incrementsthe individual cause or reason by the value reported by the application at the interval expiry. TheOK_ACC_PROC statistic is an example of a counter array statistic.

Display conventionThe convention used in this manual for presenting a specific bin of a counter array statistic is COUNTERARRAY STATISTIC NAME[bin name]. For example, OK_ACC_PROC[CM_REESTABLISH]is the CM_REESTABLISH bin of the OK_ACC_PROC counter array statistic.

Counter array binsA bin is a storage area in a counter array for cumulative cause or reason values. The number of bins in acounter array statistic depends on the number of causes or reasons associated with a specific event.

Maximum valueThe maximum value for the total and individual cumulative values is 65534 (hex=0xfffe). If a bin countreaches this value during a period, the bin contents will remain at the maximum value until the interval expiry.

Interval expiryInterval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the counter arraytotal values and the values of the individual bins then resets them to zero.

Gauge statistics

Gauge statistics report the maximum and mean values of a statistic for an interval. TheIDLE_TCH_INTF_BAND0 statistic is an example of a gauge statistic.

While a gauge statistic may result in the report of a reported negative value, the cumulative valuemay not be a negative value. The BSS checks the cumulative before calculating the mean value,and if the result is a negative number, it will set the mean zero.

Threshold event reportingA gauge statistic may have a user specified threshold that can generate an alarm when reached. TheBSS only reports one alarm to the OMC for a specific statistic during an interval.

Interval expiryInterval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the meanand maximum gauge statistic values then resets them to zero.



Duration statistics

A duration statistic is a group of values associated with timing of events controlled by an applicationprocess. The duration statistics include the total duration, mean, maximum, and minimum values. TheFLOW_CONTROL_BARRED statistic is an example of a duration statistic.

Total durationThe OMC only reports the total duration.

The total duration is the length of time an event occurs during an interval. It is a cumulativevalue reported in milliseconds. When the event starts, the BSS saves the start time of day (inmilliseconds). When the event ends, the BSS saves the stop time of day (in milliseconds). TheBSS calculates the total duration using the following formula:

stop time - start time

Wraparound to next dayThe BSS automatically checks the time of day to determine if the interval started beforemidnight and ended after midnight. If the start time is greater than the stop time, the BSScalculates the total duration using the following formula:

(86400000 - start time) + stop time

Mean valueThe BSS calculates the mean duration by dividing the total duration by the period counter. The BSSincrements the period counter each time a measured event occurs during an interval.

mean = total time / period counter

Maximum valueThe maximum value of a duration statistic is 86400000 (the number of milliseconds in 24 hours).

Interval expiryInterval expiry is the end of a statistic interval. The following processes occur at the interval expiry:

• If no events occur during the interval, the BSS sets the duration minimum value is tozero. The BSS saves this minimum value then resets it to 0xffffffff.

• The BSS saves the duration mean and maximum values then resets them to zero.

• The BSS resets the period counter and cumulative values to zero.

• The BSS stops and resets any active timers.



Normal distribution statistics

Normal distribution statistics are the number of times the reported value of an event falls within aspecified range. A distribution statistic is a single row array of 10 bins, numbered 0-9. The BSS alsosaves the minimum reported value, the maximum reported value, and a calculated mean of the reportedvalues. The OMC only reports the distribution mean, maximum, and minimum values.

BinsEach bin represents a range of values reported by an application. Each time an application reportsa value, the BSS increments the bin corresponding to the reported value by one. The BSS alsoincrements the sample count by one and calculates the total of all reported values during theinterval. The disp_stats command displays the individual bin values.

The operator may specify the range of values represented by each bin or use the system defaults. Therange of values to be represented by each bin is dependent on the focus of the statistical analysis.Narrow bin ranges permit closer examination of periods of greatest activity.

Mean valueThe BSS calculates the mean value by dividing the cumulative total of the reported values by the sample count.

If there are gaps in the bin ranges, some occurrences of reported events are not includedin the bin counts. For example, if the assigned range of values of two adjacent binsare 10-15 and 17-20, a reported event with a value of 16 is not recorded. The meanvalue does not account for the unrecorded event.

HistogramA normal distribution statistic may be illustrated as a histogram. Figure 1-1 shows the range ofvalues assigned to bin 0 is 0-10, bin 1 is 11-20, and bin 7 is 71-80. The histogram shows bins0 and 1 each contain two occurrences and bin 7 one occurrence.

Figure 1-1 Histogram of a normal distribution statistic

20 1 3 4 5 6 7 8 9

1

2

3

4

5

0

BINS

COUNT



Interval expiryInterval expiry is the end of a statistic interval. The following events occur at the interval expiry:

1. The mean value is calculated. If the number of reported events is not equal to0, the mean value is calculated by dividing the cumulative value of all of thereported events by the number of reported events.

2. The distribution minimum value is saved and reset to 0xffffffff. If no value wasreceived during the interval, the duration minimum value is to 0.

3. The distribution mean value and maximum value are saved and reset to 0.

4. The number of reported events and the cumulative value are reset to 0.

5. The values in each of the 10 bins are saved and reset to 0.

Weighted distribution statistics

Weighted distribution statistics are the length of time that the reported value of an event fallswithin a specified range. These statistics are placed in a single row array of 10 bins, numbered0-9, and a mean duration of the reported events. The minimum and maximum durations of thereported values are also saved and reported at the end of the interval.

BinsEach bin is defined to represent a range of values. Each time an application process reports avalue, the bin corresponding to the reported value is incremented by the length of time the reportedvalue stays within the bin’s specified range. This allows the number of times a reported valuefalls within a specific range to be used to calculate the mean.

The range of values that may be assigned to each of the 10 bins in the array is variable. The range ofvalues may be sized based on the focus of the analysis to be performed. For example, when measuring astatistic, the range of values assigned to the bins may be assigned to reflect the periods of greatest activity.By narrowing the bin ranges, the periods of greatest activity may be more closely examined.

If there are gaps in the bin ranges, some occurrences of reported events are not includedin the bin counts. For example, if the assigned range of values of two adjacent binsare 10-15 and 17-20, a reported event with a value of 16 is not recorded. The meanvalue does not account for the unrecorded event.

Wraparound to next dayA check is automatically made to determine if the interval started before midnight and ended after midnight.If the start time is greater than the stop time, the total duration is calculated using the following formula:

(86400000 - start time) + stop time



Mean valueThe mean value is the statistical average of all of the reported values divided by the number of reported events.

The mean for a weighted distribution statistic is not a duration value and isnot calculated using the bin values.

HistogramA weighted distribution statistic may be illustrated as a histogram. Figure 1-2 shows the rangeof values assigned to bin 0 is 0-10 and bin 7 is 71-80. The following histogram shows thatthe duration of the event reporting values from 0-10 was 40 milliseconds and the duration ofthe events reporting values from 71-80 was 20 milliseconds.

Figure 1-2 Histogram of a weighted distribution statistic

20 1 3 4 5 6 7 8 9

10

20

30

40

50

0

BINS

COUNT



Interval expiryInterval expiry is the end of a statistic interval. The following events occur at the interval expiry:

1. Stop any running timers.

2. The mean value is calculated. If the number of reported events is not equal to0, the mean value is calculated by dividing the cumulative value of all of thereported events by the number of reported events.

3. The distribution minimum value is saved and reset to 0xffffffff. If no value was receivedduring the expired interval, the duration minimum value is to 0.

4. The distribution mean value and maximum value are saved and reset to 0.

5. The number of reported events and the cumulative value are reset to 0.

6. The values in each of the 10 bins are saved and reset to 0.


Maintenance Information: GSM Statistics Application Statistic usages

Statistic usages

Quality of service monitoring

Quality of service is determined by statistics related to service accessibility, integrity, and retainability.

Service accessibilityStatistics associated with the following processes are used to determine service accessibility:

• Mobile registration.

• Mobile paging.

• Network accessibility.

• Call set up time.

• Call release time.

• Call release delay.

Service integrityStatistics associated with the following processes are used to determine service integrity:

• Call clarity.

• Interference.

Service retainabilityStatistics associated with premature releases are used to determine service retainability.

Service accessibility

Service accessibility is associated with the following call setup and clearing processes:

• Mobile registration and paging.

• Network accessibility.

• Call set up time.

• Call release time.

• Call release delay.


Statistic usages Chapter 1: Introduction to statistics

Mobile registration and pagingCells are grouped in location areas, and a mobile station (MS) is typically paged only in the cells of onelocation area when an incoming call arrives. Therefore, the MS must inform the MSC of the locationarea in which the subscriber should be paged. It does so by a location updating procedure.

The best outcome of the procedure is when the network indicates normal service is available.

Several outcomes are possible when the registration is not successful, either due to the procedure runningcorrectly and the network providing a meaningful answer, possibly denying service or the procedurerunning incorrectly and the network providing an answer that is meaningless.

If the MS satisfactorily updates its location, it can then be paged by the MSC when an incomingcall arrives. The MSC provides the concerned BSC with the ID of the MS to be paged and the listof cells in which the paging should be issued. The BSC is in charge of managing the groupingand scheduling of paging messages and initial assignment of messages.

Network accessibilityA registered MS should be able to access the network. Access denial is divided into three main categories:

• Call blocking.

No signalling channel (SDCCH) is available.

No Traffic Channel (TCH) is available.

• Failure to maintain a signalling channel or traffic channel.

Mobile is moving out of range, for example, into a garage.

Mobile is being switched off.

A hardware failure (MS or BSS).

• Refusal by the MSC for network access.

Failure to gain access to the network is pegged in BSS statistics, but for a more detailedpicture MSC statistics would have to be investigated, as it is an MSC process.

Call set-up timeCall set-up time is affected by post-selection delay and answer signal delay.

• Post-selection delay.

Post-selection delay is the time from dialling the last digit on the fixed network, or pressing the“send" button on a MS, to receiving the appropriate tone. One possible reason for this delay isthat all resources have been allocated to other calls, which may result in a queueing delay.

• Answer signal delay.

Answer signal delay is the time taken in connecting the called terminal through to thecalling terminal, once the called terminal has gone off hook.

The raw statistics TCH_DELAY and CALLS_QUEUED are associated with callset-up time and answer signal delay.



Call release timeCall release time is the time taken to release the call from the moment the end button is pressed(or after the handset is replaced on the fixed network).

Call release delayCall release delay is the time between releasing one call and being able to originate another. The onlyaspect of concern to the BSS is queueing. All other areas are transparent to the BSS.

Service integrity

Service integrity is determined by the processes affecting the following:

• Call clarity.

• Lack of interference.

• Correct tones and announcements.

Call clarityCall clarity is measured by the uplink-downlink path loss difference on the air interface. The rawstatistic PATH_BALANCE is the only measurement associated with call clarity.

Lack of interferenceThe lack of interference is measured by the bit error rate and the interference level on monitored idle channels.The raw statistics BER and INTF_ON_IDLE are the only measurements associated with lack of interference.

Correct tones and announcementsSubscriber perceptions of service integrity are influenced by the delivery of correct tones and announcementswhen using the system. No statistics are available to measure correct tones and announcements.

Service retainability

Service retainability is determined by the lack of premature releases. A premature releasemay be affected by one of the following factors:

• The base ceases to detect the RF signalling from the mobile.

• The MS fails to reach the target channel on handover.

• The call releases due to equipment failure (MSC, base site, or MS).

• The call is lost due to emergency call preemption.

A subscriber perceives a premature release as a dropped call. Refer to the Ladderdiagrams in Chapter 19, "Ladder diagrams".


Statistic usages Chapter 1: Introduction to statistics

Fault finding

GSM statistics can be used to find certain classes of faults in the cellular system. A set of statisticswhich may be used to perform this function is identified in this section.

Monitoring FaultsHard failures are normally identified via alarm surveillance. However, it is possible for a systemcomponent to deteriorate over time, while still continuing to function. The deterioration may manifestitself in a number of ways such as an increase in dropped call rate, or a lower call completion rate.Monitoring of these system parameters over time can provide the operator with an early indicationof performance degradation due to deterioration in hardware components.

Types of faultsExample of the types of faults that may be identified using statistics include:

• Damaged antennas.

• Frequency drift.

• Electromechanical problems.

Problems with remote combiners.

Noisy channels.

Optimization

Optimization of system parameters is necessary to ensure that the installed cellular infrastructureis utilized as efficiently as possible. Statistics can be used to monitor and verify the effects ofoptimization activities. For example, if handover thresholds are adjusted, statistics may be used toverify that the new threshold results in an improved handover success rate.

Optimization of a GSM network is a process whereby several BSS database parameters are fine-tuned fromtheir default values and antenna installations are adjusted to improve call success rate and quality.

By optimizing a network, the performance of the cellular equipment is verified and a benchmarkobtained for the system that may be used for subsequent expansion. The results may also be usedto modify the original data used in the frequency planning tool.

Network planning

It is possible to determine whether or not the network is correctly dimensioned for the offered trafficload. Statistics that monitor resource utilization and congestion can be used to determine when thenetwork needs to be expanded, (or contracted, if resources are being under utilized).



Installation and commissioning

Installation and commissioning of cellular equipment is a complex procedure that must be verified aftercompletion. Part of the verification procedure uses statistics to ensure that the system is operational.

Drive testing is currently one of the means used to verify installation of the network.Statistics can be used to verify the data collected during drive testing, in order to ensurethat all components of the system are operational.

This activity is currently supported via the Call Trace feature


Ladder diagrams Chapter 1: Introduction to statistics

Ladder diagrams

About ladder diagrams

The relationship between statistics and call processing elements and functions are graphicallyrepresented as ladder diagrams in Chapter 19, "Ladder diagrams".

Ladder diagrams show the relationships between theMS, BSS, andMSC elements, represented as vertical lines.

The message flows between the network elements are presented as horizontal lines representinga sequential flow of events. Arrows are used to indicate the direction of the message flow.Message names are placed above the directional line.

Intermediate network element functions are placed on the vertical lines as a sequential reference. Parallelfunctions may also be included as separate vertical lines for additional reference.

Statistics associated with individual messages are located immediately below the directional line. All of thestatistics that may be generated as the result of the process flow will be listed on the diagram.

Example

Figure 1-3 Diagram of immediate assignment failure

MS BSS

CHANNEL REQUEST (RACH)

IMMEDIATE ASSIGNMENT (AGCH)

MSC

TIMEOUT

CHAN_REQ_MS_FAIL

OK_ACC_PROC_RACH (SEE NOTE)

NOTE: RSS Abis does additional filtering of RACH.


Chapter

2Statistical operations

Statistical data can be employed in various ways to describe the operation of the system. The view anoperator gets of how the system is performing can be shown through the way statistics are displayed. Thetopics described here show how statistical property displays can be enabled and configured.

The following topics are described:

• "Enabling/disabling a statistic" on page 2-2

• "Displaying enabled statistics" on page 2-5

• "Displaying statistic values" on page 2-7

• "Setting the statistic interval" on page 2-9

• "Displaying the statistic interval" on page 2-10

• "Displaying the statistic interval start times" on page 2-11

• "Setting statistic properties" on page 2-13

• "Displaying statistic properties" on page 2-17


Enabling/disabling a statistic Chapter 2: Statistical operations

Enabling/disabling a statistic

Description

Statistics must be enabled to obtain statistical data. The stat_mode command enables anddisables a statistic. Refer to the Technical Description: BSS Command Reference (68P02901W23)for a detailed description of the stat_mode command.

Default enabled statistics

Per cell statisticsThe default mode at start up for the following per cell statistics is enabled. Thesestatistics are also enabled when a cell is added:

• ACCESS_PER_PCH.

• ALLOC_SDCCH.

• ALLOC_SDCCH_FAIL.

• ALLOC_TCH.

• ALLOC_TCH_FAIL.

• BUSY_SDCCH.

• BUSY_TCH.

• IN_INTER_BSS_HO.

• IN_INTRA_BSS_HO.

• INTRA_CELL_HO.

• MA_CMD_TO_MS_BLKD.

• MA_REQ_FROM_MSC.

• OK_ACC_PROC.

• OUT_INTER_BSS_HO.

• OUT_INTRA_BSS_HO.

• RF_LOSSES_SD.

• TOTAL_CALLS.


Maintenance Information: GSM Statistics Application Enabling/disabling a statistic

Per timeslot statisticsThe default mode at start up for the following per timeslot statistics is enabled:

• RF_LOSSES_TCH.

Enabling a statistic

A statistic is enabled by entering the stat_mode command using the following syntax:stat_mode <meas_type> on [<location>] [<cell_desc>]

Where: is:

meas_type the statistic being enabled

on enable mode

location the location of the statistic beingenabled, if required

cell_desc the cell name or number, ifrequired

Examplestat_mode rf_losses_tch on cell_name=mid34a

Where: is:

rf_losses_tch meas_type

on enable mode

cell_name=mid34a cell_desc

System response:COMMAND ACCEPTED

Disabling a statistic

A statistic is disabled by entering the stat_mode command using the following syntax:stat_mode <meas_type> off [<location>] [<cell_desc>]

Where: is:

meas_type the statistic being disabled

off disable mode

location the location of the statistic beingdisabled, if required



Enabling/disabling a statistic Chapter 2: Statistical operations

Examplestat_mode mtp_link_ins off

Where: is:

mtp_link_ins meas_type

off disable mode



Maintenance Information: GSM Statistics Application Displaying enabled statistics

Displaying enabled statistics

Description

A listing of the currently enabled statistics may be displayed using the disp_enable_statcommand. Refer to the Technical Description: BSS Command Reference (68P02901W23) fora detailed description of the disp_enable_stat command.

Specific listings may be generated based on the arguments entered with the disp_en-able_stat command, including:

• No argument - A listing of all currently enabled statistics will be presented.

• BSS - A listing of all of the currently enabled BSS-wide statistics will be presented.

• cell_desc - A listing of all of the currently enabled statistics for thespecified cell will be presented.

• location - A listing of all of the currently enabled statistics for the specified site will be presented.

• meas_type - A listing of all of the currently enabled statistics for the specifiedmeasurement type will be presented.

Displaying all enabled statistics

A listing of all of the enabled statistics may be displayed by entering the disp_enable_statcommand using the following syntax:disp_enable_stat

System response:Enabled Non-Cell Statisticsma_req_from_msc_failpage_req_from_msc_failho_req_msc_protomtp_sl_failmtp_sl_fibrmtp_sl_ackmtp_sl_error_ratemtp_sl_congestionmtp_sl_alignmentmtp_su_errormtp_neg_acksmtp_changeovermtp_changebackmtp_restorationmtp_start_rpomtp_stop_rpo


Displaying enabled statistics Chapter 2: Statistical operations

mtp_mgt_inhibitmtp_mgt_uninhibitmtp_re_txmtp_sif_sio_rxmtp_msu_txmtp_msu_rxsl_congestionsl_stop_congestionmsu_discardedcongestion_lost_msusif_sio_rx_opcsif_sio_tx_dpcsif_sio_typerouting_syntaxrouting_unknownsccp_msgssccp_msgs_txsccp_msgs_rxinvalid_frames_rxi_frames_rxi_frames_txsabm_tx frmrn2_expirymtp_link_insmtp_unavailablemtp_local_mgtmtp_remote_mgtmtp_linkfailmtp_remote_procmtp_local_busymtp_congestioncpu_usage...Enabled Statistics for Cell 001 01 03e7h 0028h{23658} egprs_avail_pdtchrf_losses_tchrf_losses_sdintra_cell_hoin_inter_hoout_inter_hointra_bss_hoaccess_per_rach...tch_delayintf_on_idlebusy_tchbusy_sdcchber..

The remaining cell statistics follow until all of the enabled statistics have been displayed.


Maintenance Information: GSM Statistics Application Displaying statistic values

Displaying statistic values

Description

The current value of individual statistics for a specific interval can be displayed using the disp_statscommand. Displayed information may represent incremental (peg count) or duration values,depending on the specified statistic. Refer to the Technical Description: BSS Command Reference(68P02901W23) for a detailed description of the disp_stats command.

The value of a statistic for the current interval cannot be displayed. The disp_intervalcommand may be used to display completed intervals.

When counter array statistics are displayed, the values for the individual bins are displayed.A total value of all of the bins may also be displayed for some counter array statistics. Referto the descriptions of individual counter array statistics.

The disp_stats command is entered using the one of the following syntax:

disp_stats <interval> <meas_type> <cell_desc>disp_stats <interval> <meas_type> <board_desc>

Where: is:

interval a completed statistical interval

meas_type the name of the statistic to bedisplayed


board_desc the board_id, if required

When using the disp_stats command to display a per link statistic, the generated outputwill report all links for a specified board.


Displaying statistic values Chapter 2: Statistical operations

ExampleThis example shows the interaction required to display the value of a counter arraystatistic which includes a total value.disp_stats 5 out_ho_cause_atmpt cell_number=5 4 3 2 1 61986 34944

Where: is:

5 interval

out_ho_cause_atmpt statistic

5 4 3 2 1 61986 34944 cell_number

System response:SITE: 0 CELL #: LAC = f222h CI = 8880hMEAS_TYPE : OUT_HO_CAUSE_ATMPT

Total: 110Uplink Quality : 10Uplink Level : 20Downlink Quality : 10Downlink Level : 10Distance : 10Uplink Interference : 10Downlink Interference : 10Power Budget : 10Congestion : 10Adjacent Channel Interference : 10


Maintenance Information: GSM Statistics Application Setting the statistic interval

Setting the statistic interval

Description

The stat_interval is a nonstatistical parameter that is used to specify the interval. Referto the Technical Description: BSS Command Reference (68P02901W23) for a detaileddescription of the stat_interval parameter.

In normal operations, key statistics and health indicators are calculated by the OMC-Rbased on the default interval of 30 minutes. If the interval is changed to 60 minutes, itmust be reset to 30 minutes for normal operations.

The OMC-R can calculate key statistics at 60 minute intervals if it is configuredto handle 60 minute statistic files.

The stat_interval is specified by entering the chg_element command using the following syntax:chg_element stat_interval <30 or 60> <location>

Where: is:

stat_interval parameter name

30 or 60 valid values for the parameter, inminutes

location This is a BSS-wide parameter and0 is the only valid value for thisargument.

ExampleThis example shows the interaction required to change the statistical interval to 60 minutes.chg_element stat_interval 60 0

Where: is:


60 60 minutes

0 location



Displaying the statistic interval Chapter 2: Statistical operations

Displaying the statistic interval

Description

The stat_interval is a non-statistical parameter that is used to specify the interval. The current intervalmay be displayed using the disp_element command using the following syntax:disp_element stat_interval <location>

Where: is:


location This is a BSS-wide parameter and0 is the only valid value for thisargument.

ExampleThis example shows the interaction required to display the statistical interval.chg_element stat_interval 0

Where: is:


0 location

System response:stat_interval = 30


Maintenance Information: GSM Statistics Application Displaying the statistic interval start times

Displaying the statistic interval start times

Description

The starting times of the statistic intervals may be displayed by entering the disp_interval command.Refer to the Technical Description: BSS Command Reference (68P02901W23) for a detailed descriptionof the disp_interval command. No arguments are required with the command.

On startup, the first start time (interval 0) corresponds to current time of the system clock. Thesecond start time (interval 1) automatically becomes synchronized to the next hour (:00) orhalf hour (:30), depending upon the current statistic interval.

ExampleThis example shows the interaction required to display the starting times of the statistical intervals wherethe statistic interval is 30 and the disp_interval command was entered at 1230.disp_interval

System response:Interval Start Time (HH:MM:SS)

-------- --------------------

0 09:08:48

1 09:30:00

2 10:00:00

3 10:30:00

4 11:00:00

5 11:30:00

6 12:00:00

7 12:30:00

8 None

9 None

10 None

11 None

The displayed starting times depend on the time of day that the disp_interval command is entered. Whenthe command is entered, the current set of 12 start times is presented. If the command is entered afterinterval 11 would be completed, the listing displays the next set of 12 interval start times.

ExampleIf the disp_interval command is entered at 1501, the following output displays:disp_interval


Displaying the statistic interval start times Chapter 2: Statistical operations

System response:Interval Start Time (HH:MM:SS)

-------- --------------------

0 15:00:00

1 09:30:00

2 10:00:00

3 10:30:00

4 11:00:00

5 11:30:00

6 12:00:00

7 12:30:00

8 13:00:00

9 13:30:00

10 14:00:00

11 14:30:00


Maintenance Information: GSM Statistics Application Setting statistic properties

Setting statistic properties

Description

The properties for statistics (except for the statistic interval) may be changed using the chg_stat_propcommand. Refer to the Technical Description: BSS Command Reference (68P02901W23) fora detailed description of the chg_stat_prop command.

The specific properties that may be changed are dependent on the statistic type.

• The alarm threshold may be changed for counter, counter array and gauge statisticsif an alarm is associated with the statistic.

• Bin ranges may be changed for normal and weighted statistics.

• Properties may not be changed for total time (duration) statistics.

Setting a threshold

Some counter and gauge statistics may be associated with alarms. Threshold values maybe specified for these statistics. An alarm is sent to the Operations and Maintenance Centre- Radio (OMC-R) when the threshold is reached.

A threshold is specified by entering the chg_stat_prop command using the following syntax:chg_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a counter or gauge statistic

location the location of the statistic whosethreshold is being set, if required


ExampleThis example shows the interaction required to change the alarm threshold for therf_losses_tch statistic for cell_name=mn14b at site 1.chg_stat_prop rf_losses_tch cell_name=mn14b

Where: is:

rf_losses_tch meas_type

cell_name=mn14b cell_desc


Setting statistic properties Chapter 2: Statistical operations

System response:Enter the alarm threshold: 500COMMAND ACCEPTED

Counter statistics

Counter statistics that may be assigned a threshold are presented in Table 2-1.

Table 2-1 Counter statistics

Statistical name Alarm severity Valid values Basis

ALLOC_SDCCH_FAIL Major min: 1 max: 2147483647 cell

ALLOC_TCH_FAIL Major min: 1 max: 2147483647 cell

BAD_HO_REFNUM_MS Warning min: 1 max: 2147483647 cell

CALLS_QUEUED Warning min: 1 max: 2147483647 cell

CHAN_REQ_MS_BLK Minor min: 1 max: 2147483647 cell

CHAN_REQ_MS_FAIL Minor min: 1 max: 2147483647 timeslot

CIPHER_MODE_FAIL Minor min: 1 max: 2147483647 cell

CLASSMK_UPDATE_FAIL Minor min: 1 max: 2147483647 cell

CONGESTION_LOST_MSU Warning min: 1 max: 2147483647 SS7 link

FRMR Warning min: 1 max: 2147483647 X.25 link orLAPD link

HO_REQ_MSC_FAIL Warning min: 1 max: 2147483647 cell

HO_REQ_MSC_PROTO Warning min: 1 max: 2147483647 BSS

INVALID_FRAMES_RX Warning min: 1 max: 2147483647 X.25 link orLAPD link

MA_CMD_TO_MS_BLKD Minor min: 1 max: 2147483647 cell

MA_FAIL_FROM_MS Warning min: 1 max: 2147483647 cell

MA_REQ_FROM_MSC_FAIL Warning min: 1 max: 2147483647 BSS

MSU_DISCARDED Warning min: 1 max: 2147483647 SS7 link

MTP_NEG_ACKS Warning min: 1 max: 2147483647 SS7 link

MTP_RE_TX Warning min: 1 max: 2147483647 SS7 link

MTP_SL_ACK Major min: 1 max: 2147483647 SS7 link

MTP_SL_ALIGNMENT Minor min: 1 max: 2147483647 SS7 link

MTP_SL_CONGESTION Major min: 1 max: 2147483647 SS7 link

MTP_SL_ERROR_RATE Major min: 1 max: 2147483647 SS7 link

MTP_SL_FAIL Major min: 1 max: 2147483647 SS7 link

MTP_SL_FIBR Major min: 1 max: 2147483647 SS7 link


Maintenance Information: GSM Statistics Application Setting statistic properties

Table 2-1 Counter statistics (Continued)

Statistical name Alarm severity Valid values Basis

MTP_START_RPO Warning min: 1 max: 2147483647 SS7 link

MTP_SU_ERROR Warning min: 1 max: 2147483647 SS7 link

N2_EXPIRY Warning min: 1 max: 2147483647 X.25 link orLAPD link

PAGE_REQ_FROM_MSC_FAIL Minor min: 1 max: 2147483647 BSS

PCH_Q_PAGE_DISCARD Minor min: 1 max: 2147483647 cell

RF_LOSSES_SD Major min: 1 max: 2147483647 cell

RF_LOSSES_TCH Major min: 1 max: 2147483647 timeslot

ROUTING_SYNTAX Warning min: 1 max: 2147483647 BSS

ROUTING_UNKNOWN Warning min: 1 max: 2147483647 BSS

{24661}RSL_LCF_CONGES-TION

Warning min: 1 max: 2147483647 BSS

SL_CONGESTION Warning min: 1 max: 2147483647 SS7 link

The maximum value that may be assigned to a threshold (2147483647) is set as the defaultvalue upon initialization of the CM database.

The default for the maximum value in the Valid Values column is 2147483647.

Setting bin ranges

Distribution statistics include 10 bins, numbered 0 to 9. Each bin represents a range of values. When eventsare reported, the bin corresponding to the reported value is incremented. The range of values for the individualbins in a distribution statistic may be specified with the chg_stat_prop command using the following syntax:chg_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a normal or weighted distributionstatistic

location the location of the statistic whosebin range is being set, if required


The bin ranges for the BER statistic may not be modified.


Setting statistic properties Chapter 2: Statistical operations

Bin rangesDistribution statistics include 10 bins, numbered 0 to 9. The range of values to be measured by thestatistic must be considered when assigning values for the individual bins in the distribution. Forexample, if the possible range of values to be measured is from 0 to 100, then the minimum valuefor bin 0 should be 0, and the maximum value for bin 9 should be 100.

Gaps in the range of values covered should be avoided when assigning the minimum and maximum values forthe individual bins. For example, if bin 0 covers values from 0 to 10 and bin 1 covers values from 12 to 15, agap would exist for the value 11. This would cause any report of a value equal to 11 to be ignored.

Bin minimums and maximums may be set to the same value for the same bin. This allows a specificvalue to be reported within the overall distribution. For example, if the minimum and maximum valuesfor a bin are both specified to be 10, the bin is pegged each time a value of 10 is reported.

Default rangesDistribution statistics have default ranges for bins.

ExampleThis example shows the interaction required to change the minimum and maximum values fortwo bins of the BUSY_TCH statistic for all cells at site 1.chg_stat_prop busy_tch 1 all

Where: is:

busy_tch meas_type

1 location

all all cells at the specified site

System response:Enter the bin number(s): 0,1Enter the min value for bin 0: 0Enter the max value for bin 0: 5Enter the min value for bin 1: <return>7 Enter the max value for bin 1: 7COMMAND ACCEPTED


Maintenance Information: GSM Statistics Application Displaying statistic properties

Displaying statistic properties

Description

The properties of individual statistics may be displayed using the disp_stat_prop command. Theinformation and presentation format are dependent upon the statistic type, including:

• Alarm severity and threshold values are displayed for counter and gauge statistics.

• Bin ranges are displayed for normal and weighted statistics.

• The cause is displayed for the counter array statistics.

• The mode and type only are displayed for the duration statistics.


Displaying statistic properties Chapter 2: Statistical operations

Displaying a counter statistic

Counter statistic properties are displayed by entering the disp_stat_prop command using the following syntax:disp_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a counter statistic

location the location of the statistic whoseproperties are being displayed, ifrequired


ExampleThis example shows the interaction required to display the properties for the TO-TAL_CALLS statistic for all cells at site 1.disp_stat_prop total_calls 1 all

Where: is:

total_calls meas_type

1 location

all all cells at the specified location

System response:STATISTIC: TOTAL_CALLS SITE: 1

TYPE: PER CELL OBJECT:COUNTER

CELL # MODE ALARMSEVERITY

ALARMTHRESHOLD

--------- --------- --------- ---------

543 21 61698 (f102h)34776 (87d8h) ENABLED NO ALARM N/A


543 21 61698 (f102h)34778 (87dah) ENABLED NO ALARM N/A

543 21 61698 (f102h)34779 (87dbh) ENABLED NO ALARM N/A

543 21 61698 (f102h)34780 (87dch) ENABLED NO ALARM N/A



Displaying a gauge statistic

Gauge statistic properties are displayed by entering the disp_stat_prop command using the following syntax:disp_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a gauge statistic



ExampleThis example shows the interaction required to display the properties for the AVAILABLE_TCHstatistic for cell_number=5 4 3 2 1 61698 34776 at site 1.disp_stat_prop available_tch 1 cell_number=5 4 3 2 1 61698 34776

Where: is:

available_tch meas_type

1 location

cell_number=5 4 3 2 1 61698 34776 cell_desc

System response:STATISTIC: AVAILABLE_TCH SITE: 1

TYPE: PER CELL OBJECT: GAUGE

CELL # MODE ALARMSEVERITY

ALARMTHRESHOLD

--------- --------- --------- ---------




Displaying a distribution statistic

Distribution statistic properties are displayed by entering the disp_stat_prop com-mand using the following syntax:disp_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a distribution statistic



ExampleThis example shows the interaction required to display the properties for the BUSY_TCHstatistic for cell_number=5 4 3 2 1 61698 34776 at site 1.disp_stat_prop busy_tch 1 cell_number=5 4 3 2 1 61698 34776

Where: is:

busy_tch meas_type

1 location

5 4 3 2 1 61698 34776 cell_desc

System response:STATISTIC: BUSY_TCH SITE: 1

TYPE: PER CELL OBJECT:DISTRIB

CELL # MODE BIN MIN MAX

--------- --------- --------- --------- ---------

543 21 61698 (f102h)34776(87d8h)

ENABLED 0 0 1

1 2 3

2 4 5

3 6 7

4 8 9

5 10 11

6 12 13

7 14 15



8 16 2147174832

9 214174833 2141749879



Displaying a counter array statistic

Counter array statistic properties are displayed by entering the disp_stat_prop com-mand using the following syntax:disp_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a counter array statistic



ExampleThis example shows the interaction required to display the properties for theOUT_HO_CAUSE_ATMPT statistic.disp_stat_prop out_ho_cause_atmpt cell_number=5 4 3 2 1 62259 8736

Where: is:

out_ho_cause_atmpt meas_type

5 4 3 2 1 62259 8736 cell_desc

System response:STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 2

TYPE: PER CELL OBJECT: COUNTERARRAY

BIN # CAUSE

--------- ---------

0 ENABLED NO ALARM

1 ENABLED NO ALARM

2 ENABLED NO ALARM

3 ENABLED NO ALARM

4 ENABLED NO ALARM

5

6

7

8

9

CELL # MODE



------------------------- -------

543 21 62259 (f333h) 8736 (2220h) DISABLED



Displaying a duration statistic

Duration statistic properties are displayed by entering the disp_stat_prop command using the following syntax:disp_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: is:

meas_type a duration statistic



ExampleThis example shows the interaction required to display the properties for theFLOW_CONTROL_BARRED statistic.disp_stat_prop flow_control_barred 2 5 4 3 2 1 62259 8736

Where: is:

flow_control_barred meas_type

2 location

5 4 3 2 1 62259 8736 cell_desc

System response:STATISTIC: FLOW_CONTROL_BARRED SITE: 2

TYPE: PER CELL OBJECT: TOTAL TIME

CELL # MODE

------------------ ---------

543 21 62259 (f333h) 8736 (2220h) DISABLED


Chapter

3BSS statistics

BSS statistics are captured from events occurring at the BSS. They are categorized into subgroups,each of which are described in "BSS statistics subgroups" on page 3-2.


BSS statistics subgroups Chapter 3: BSS statistics

BSS statistics subgroups

BSS statistics are organized into the following major subgroups:

• "BSS C7 utilization" on page 3-2.

• "Intra-BSS handover" on page 3-2.

• "SCCP performance and utilization" on page 3-2.

• "RSL congestion control" on page 3-3

BSS C7 utilization

BSS C7 utilization statistics track the number of messages received and transmitted onthe signalling links. This information indicates the activity level on the Signalling Links(SLs). The following are BSS C7 utilization statistics:

• "SIF_SIO_RX_OPC" on page 3-19.

• "SIF_SIO_TX_DPC" on page 3-20.

• "SIF_SIO_TYPE" on page 3-21.

Intra-BSS handover

A single counter array statistic tracks the number of successful intra-BSS handovers:"INTRA_BSS_HO_CAUSE_SUC" on page 3-6.

SCCP performance and utilization

SCCP performance and utilization statistics track the performance of the Signalling ConnectionControl Part (SCCP) protocol layer of the ITU-TSS C7.

The SCCP manages the establishment and release of call related connections. A connection isestablished for each transaction. For example, location update and service request, both BSS andMSC maintain contexts related to the transaction; these contexts may be identified using the SCCPreference number. This information indicates the performance level and quality of the SCCP.The following are the SCCP performance and utilization statistics:

• "HO_REQ_MSC_PROTO" on page 3-5.

• "MA_REQ_FROM_MSC_FAIL" on page 3-8.

• "MSC_OVLD_MSGS_RX" on page 3-9.


Maintenance Information: GSM Statistics Application BSS statistics subgroups

• "PAGE_REQ_FROM_MSC_FAIL" on page 3-12.

• "ROUTING_SYNTAX" on page 3-13.

• "ROUTING_UNKNOWN" on page 3-14.

• "SCCP_MSGS" on page 3-16.

• "SCCP_MSGS_RX" on page 3-17.

• "SCCP_MSGS_TX" on page 3-18.

RSL congestion control

{24661}

RSL Congestion Control statistics are PM statistics that track the amount of time a processor was ina congested state and the count of BSS Overload messages during RSL congestion.

The following are the RSL Congestion Control statistics:

• "BSS_OVLD_MSGS_TX" on page 3-4

• "MSGS_DISCARD_ON_GPROC" on page 3-10

• "MSGS_DISCARD_ON_RSL" on page 3-11

• "RSL_LCF_CONGESTION" on page 3-15


BSS_OVLD_MSGS_TX Chapter 3: BSS statistics

BSS_OVLD_MSGS_TX

{24661}

Description

This statistic tracks the number of BSS Overload messages that have been sent from the BSSto the MSC. The BSS sends Overload messages to the MSC when the first RSL-LCF board iscongested. The BSS sends this statistic to the OMC-R periodically.

PeggingThis statistic is pegged each time an Overload message is sent from the from the BSS to the MSC..

AnalysisThis statistic is used for trend analysis of RSL congestion status on a BSS basis.

Reference GSM TS 12.04, GSM TS 8.08

Usage RSL Congestion Control.Trend analysis.

Basis BSS.

Type Counter.

Alarm None


Maintenance Information: GSM Statistics Application HO_REQ_MSC_PROTO

HO_REQ_MSC_PROTO

Description

This statistic tracks the number of Handover Request messages received from the MSC that fail messagevalidation. Validation failure may occur due to protocol errors which may occur if the message isbadly formatted or incompatible database elements exist in the BSS and MSC.

PeggingThis statistic is pegged each time a Handover Request message from the MSC fails messagevalidation at the BSS. Currently, this statistic is not pegged.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of messagevalidation failures that are acceptable in normal system operations.

If the specified threshold is exceeded, the 17. BSS: HO Request from the MSC protocolerror - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.1.5.2.2.

Usage Handover.Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.


INTRA_BSS_HO_CAUSE_SUC Chapter 3: BSS statistics

INTRA_BSS_HO_CAUSE_SUC

Description

This statistic tracks the number of successful intra BSS handovers on a per cause basis. Atotal count of all successful results is also maintained.

Bin Cause Description

0 UPLINK_QUALITY Handovers due to uplink quality.

1 UPLINK_LEVEL Handovers due to uplink level.

2 DOWNLINK_QUALITY Handovers due to downlink quality.

3 DOWNLINK_LEVEL Handovers due to downlink level.

4 DISTANCE Handovers due to distance.

5 UPLINK_INTERFERENCE Handovers due to uplink interference.

6 DOWNLINK_INTERFERENCE Handovers due to downlink interference.

7 POWER_BUDGET Handovers due to power budget.

8 CONGESTION Handovers due to congestion.

PeggingThe bin corresponding to the cause of the successful handover is pegged each time a HandoverPerformed message is sent from the BSS to the MSC.

{4322} Full-rate to half-rate congestion based Intra-cell handovers cause the CONGESTION bin to be pegged.

{4322} Half-rate quality based Intra-cell handovers cause the DOWNLINK_INTERFERENCEor UPLINK_INTERFERENCE bins to be pegged.


Maintenance Information: GSM Statistics Application INTRA_BSS_HO_CAUSE_SUC

AnalysisThis statistic can be used for trend analysis permitting early identification of problems before they affect service.

Reference GSM 12.04, 4.21, B.1.1.11.GSM 12.04, 8.08, 3.2.1.9, and 3.2.1.25.

Usage Radio resource allocation.Quality of service monitoring.Network planning.Optimization.

Basis BSS.

Type Counter array.


MA_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics

MA_REQ_FROM_MSC_FAIL

Description

This statistic tracks the number of Assignment Request messages received from the MSC that failmessage validation. Validation failure may occur due to protocol errors which may occur if the messageis badly formatted or incompatible database elements exist in the BSS and MSC.

PeggingThis statistic pegs each time an Assignment Request message from theMSC fails message validation at the BSS.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number offailures that are acceptable in normal system operations.

If the specified threshold is exceeded, the 7. BSS: Mobile assignment request from MSCprotocol error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.2.2.5 and 3.2.1.3.

Usage Radio resource allocation.Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application MSC_OVLD_MSGS_RX

MSC_OVLD_MSGS_RX

Description

This statistic tracks the number of MSC Overload messages that have been received by the BSS from theMSC. This statistic pegs independently of the MSC Overload Control feature being enabled or disabled.

PeggingThis statistic pegs each time an Overload message is received by the BSS from the MSC.

AnalysisIn systems without the MSC Overload Control feature, this statistic can be used to determineif the MSC feature should be acquired, if not currently installed.

Reference GSM-BSS-MOC-EFP-001, v1.1, 2238-7

Usage Quality of service.Network planning.

Basis BSS.

Type Counter.


MSGS_DISCARD_ON_GPROC Chapter 3: BSS statistics

MSGS_DISCARD_ON_GPROC

{24661}

Description

This statistic counts the number of downlink messages discarded on each GPROCby the RSL Congestion Control operation.

PeggingThis statistic is pegged each time a downlink message (including MTL-LCF to RSL-LCF, MCU toDRI) is discarded on a GPROC by the RSL Congestion Control operation.

AnalysisThis statistic is used for trend analysis of RSL congestion status.

Reference GSM TS 12.04, GSM TS8.08

Usage RSL Congestion Control.Quality of service.Trend analysis.

Basis BSS

Type Counter.

Alarm None


Maintenance Information: GSM Statistics Application MSGS_DISCARD_ON_RSL

MSGS_DISCARD_ON_RSL

{24661}

Description

This statistic counts the number of downlink messages discarded on each RSL by theRSL Congestion Control operation.

PeggingThis statistic is pegged each time downlink messages are discarded by the RSLCongestion Control operation on each RSL.

AnalysisThis statistic is used for trend analysis of RSL congestion status.

Reference GSM TS 12.04, GSM TS8.08

Usage RSL Congestion Control.Quality of service.Trend analysis.

Basis BSS.

Type Counter.

Alarm None


PAGE_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics

PAGE_REQ_FROM_MSC_FAIL

Description

This statistic tracks the number of Page Request messages received from the MSC that fail messagevalidation. Validation failure may occur due to protocol errors which may occur if the message isbadly formatted. A protocol error does not indicate paging success or failure.

PeggingThis statistic pegs each time a Page Request message from the MSC fails message validation at the BSS.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum numberof failures that are acceptable in normal system operations. The Cell Identifier List is notverified until the page is about to be sent to the cells.

If the specified threshold is exceeded, the 0. BSS: Paging request from MSC protocolerror - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Usage Quality of service monitoring: Paging analysis.Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application ROUTING_SYNTAX

ROUTING_SYNTAX

Description

This statistic tracks the number of SCCP messages with syntax errors.

PeggingThis statistic pegs when a syntax error is detected in an SCCP message.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.Excessive syntax errors can result in degraded SCCP performance. A threshold value should beassigned to this statistic which reflects the maximum number of SCCP messages with syntaxerrors that are acceptable in normal system operations.

If the specified threshold is exceeded, the 1. BSS: Routing failure - syntax error detected- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.ITU-TSS Q.791 - (3.2 - 3.10).

Usage SCCP performance and utilization.Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.


ROUTING_UNKNOWN Chapter 3: BSS statistics

ROUTING_UNKNOWN

Description

This statistic tracks the number of invalid signalling point codes (SPCs) that a BSC has received from the MSC.

PeggingThis statistic pegs whenever an invalid SPC is received from the MSC.

AnalysisAn SPC is the destination address for a message routed by the networking functions of the MTP3protocol. If the BSC receives an incorrect SPC, it will not be able to correctly route the message.A threshold value should be assigned to this statistic which reflects the maximum number ofinvalid SPCs that are acceptable in normal system operations.

If the specified threshold is exceeded, the 2. BSS: Routing failure - reason unknown- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis BSS.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application RSL_LCF_CONGESTION

RSL_LCF_CONGESTION

{24661}

Description

This statistic indicates the amount of time that a RSL-LCF board is in a congested state. TheBSS sends this duration statistic to the OMC-R periodically.

PeggingThe timer for this statistic is started when more than a certain percentage of RSLs on a LCF board iscongested, and the timer is stopped when less than a certain percentage of RSLs on a LCF board is congested.

AnalysisThis statistic is used for trend analysis of RSL congestion status on a LCF basis.

A threshold value should be assigned to this statistic reflecting the maximum percentage ofcongested RSLs on a LCF board at which the timer is started, and the minimum percentage ofcongested RSLs on a LCF board at which the timer is stopped.

Whenever this statistic timer is started, the 19:GPROC: RSL links congestion alarm is generateduntil the timer stops indicating that normal state has resumed. Refer to the Maintenance Information:Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM TS 12.04, GSM TS 8.08

Usage RSL Congestion Control trend analysis.Quality of service.Fault finding.

Basis BSS.

Type Duration.

Alarm Warning


SCCP_MSGS Chapter 3: BSS statistics

SCCP_MSGS

Description

This statistic tracks the total number of SCCP messages either transmitted or received over an SL.

PeggingThis statistic pegs when SCCP messages are transmitted or received on the signalling link.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC. Thisstatistic can be used for trend analysis of SCCP performance and utilization.


Usage SCCP performance and utilization.

Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application SCCP_MSGS_RX

SCCP_MSGS_RX

Description

This statistic tracks the total number of SCCP messages received on an SL for class 0 or class 2.

PeggingThis statistic pegs when SCCP messages are received on the signalling link.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.This statistic can be used for trend analysis of the activity on an SL.



Basis BSS.

Type Counter.


SCCP_MSGS_TX Chapter 3: BSS statistics

SCCP_MSGS_TX

Description

This statistic tracks the total number of SCCP messages transmitted on an SL for class 0 or class 2.

PeggingThis statistic pegs when SCCP messages are transmitted on the signalling link.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.This statistic can be used for trend analysis of the activity on an SL.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application SIF_SIO_RX_OPC

SIF_SIO_RX_OPC

Description

This statistic tracks the total number of SIF and SIO octets received on all SLs for a particular BSS.

PeggingThis statistic pegs each time Signal Information Fields (SIF) or Service Information Octets(SIO) are received across all signalling links to a BSS.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC. Thisstatistic can be used for trend analysis of the activity on all SLs for a particular BSS.


Usage MTP C7 utilization.

Basis BSS.

Type Counter.


SIF_SIO_TX_DPC Chapter 3: BSS statistics

SIF_SIO_TX_DPC

Description

This statistic tracks the total number of Signal Information Fields (SIF) and Service Information Octets(SIO) octets transmitted on all SLs of a particular BSS by the Destination Point Code (DPC).

PeggingThis statistic pegs each time SIF or SIO are transmitted across all signalling links to a BSS.

AnalysisA DPC is part of the label in a signalling message that uniquely identifies, in a signallingnetwork, the destination point of the message. This statistic can be used for trend analysisof the activity of the signalling links on a BSS.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application SIF_SIO_TYPE

SIF_SIO_TYPE

Description

This statistic tracks the number of SIF MTP, TEST, and SCCP SIO octets transmittedor received on an SL on an SIO basis.

PeggingThis statistic pegs each time SIF or SIO octets are transmitted or received on each signalling link.

AnalysisThis statistic can be used for trend analysis of the activity of the signalling links on a BSS.



Basis BSS.

Type Counter.


SIF_SIO_TYPE Chapter 3: BSS statistics

This page intentionally left blank.


Chapter

4Cell statistics

Cell statistics are captured from events occurring in a cell. They are categorized into subgroups,each of which are described in "Cell statistics subgroups" on page 4-2.


Cell statistics subgroups Chapter 4: Cell statistics

Cell statistics subgroups

Cell statistics are organized into the following major subgroups:

• "Assignment redirection" on page 4-2.

• "Call clearing" on page 4-2.

• "Concentric cell" on page 4-3.

• "Connection establishment" on page 4-3.

• "Directed retry" on page 4-4.

• "Emergency call access" on page 4-4.

• "Extended range cell" on page 4-4.

• "General handover" on page 4-4.

• "Inter-BSS handover" on page 4-5.

• "Intra-BSS handover" on page 4-5.

• "Intra-cell handover" on page 4-5.

• "Multiband" on page 4-5.

• "TCH assignment" on page 4-6.

• "Usage congestion" on page 4-6.

• "DYNET failures" on page 4-7.

• "Interference bands" on page 4-7.

Assignment redirection

Assignment redirection statistics track the number of times a call assignment is redirected to another cell. Thestatistic "ASSIGNMENT_REDIRECTION" on page 4-19 is the only assignment redirection statistic.

Call clearing

Call clearing statistics track the number calls lost due to RF failures, cipher mode failures, orprocedure timeouts. The following are call clearing statistics:

• "CIPHER_MODE_FAIL" on page 4-34.

• "CLR_REQ_TO_MSC" on page 4-37.


Maintenance Information: GSM Statistics Application Cell statistics subgroups

• "CLR_REQ_TO_MSC" on page 4-37.

• "RF_LOSSES_SD" on page 4-96.

• "RF_LOSSES_TCH" on page 4-97.

Concentric cell

Concentric cell statistics track concentric cell feature processes. The following are concentric cell statistics:

• "TCH_CONG_INNER_ZONE" on page 4-107.

• "TCH_USAGE_INNER_ZONE" on page 4-114.

• "ZONE_CHANGE_ATMPT" on page 4-116.

• "ZONE_CHANGE_SUC" on page 4-117.

Connection establishment

Connection establishment statistics track access, allocation, channel request, and MSC page requestfunctions. The following are connection establishment statistics:

• "ACCESS_PER_AGCH" on page 4-8.

• "ACCESS_PER_PCH" on page 4-9.

• {3723}"ACCESS_PER_PPCH" on page 4-11

• "ACCESS_PER_RACH" on page 4-13.

• "ALLOC_SDCCH" on page 4-14.

• "ALLOC_SDCCH_FAIL" on page 4-16.

• "ALLOC_TCH" on page 4-17.

• "CALL_SP_VERS_DOWNGRADE_MONITOR" on page 4-28.

• "CHAN_REQ_CAUSE_ATMPT" on page 4-31.

• "CHAN_REQ_MS_BLK" on page 4-32.

• "CHAN_REQ_MS_FAIL" on page 4-33.

• "CONN_REFUSED" on page 4-41.

• "CONN_REQ_TO_MSC" on page 4-43.

• "INV_EST_CAUSE_ON_RACH" on page 4-64.

• "OK_ACC_PROC" on page 4-82.



• "OK_ACC_PROC_SUC_RACH" on page 4-84.

• "PAGE_REQ_FROM_MSC" on page 4-91.

Directed retry

Directed retry statistics track congestion processes associated with the directed retryfeature. The following are directed retry statistics:

• "CONGEST_EXIST_HO_ATMPT" on page 4-39.

• "CONGEST_STAND_HO_ATMPT" on page 4-40.

Emergency call access

Emergency call access statistics track emergency call processes. The following areemergency call access statistics:

• "NUM_EMERG_ACCESS" on page 4-78.

• "NUM_EMERG_REJECTED" on page 4-79.

• "NUM_EMERG_TCH_KILL" on page 4-80.

• "NUM_EMERG_TERM_SDCCH" on page 4-81.

Extended range cell

Extended range statistics track extended range feature processes. The followingare extended range cell statistics:

• "ER_INTRA_CELL_HO_ATMPT" on page 4-46.

• "ER_INTRA_CELL_HO_SUC" on page 4-47.

• "TCH_USAGE_EXT_RANGE" on page 4-113.

General handover

General handover statistics track processes common to all types of handovers. Thefollowing are handover statistics:

• "BAD_HO_REFNUM_MS" on page 4-22.



• "HO_FAIL_NO_RESOURCES" on page 4-49.

Inter-BSS handover

Inter-BSS handover statistics track inter-BSS handover processes. The followingare inter-BSS handover statistics:

• "HO_REQ_MSC_FAIL" on page 4-51.

• {4322}"HO_REQ_ACK_TO_MSC" on page 4-52.

• "IN_INTER_BSS_HO" on page 4-59.

• "OUT_INTER_BSS_HO" on page 4-87.

Intra-BSS handover

Intra-BSS handover statistics track intra-BSS handover processes. The followingare intra-BSS handover statistics:

• "IN_INTRA_BSS_HO" on page 4-60.

• "OUT_HO_CAUSE_ATMPT" on page 4-85

• "OUT_INTRA_BSS_HO" on page 4-89.

Intra-cell handover

Intra-cell handover statistics track intra-cell handover processes. The following isthe only intra-cell handover statistic:

• "INTRA_CELL_HO" on page 4-62.

Multiband

Multiband statistics track multiband feature processes. The following are multiband statistics:

• "ASSIGNMENT_REDIRECTION" on page 4-19.

• "INTERBAND_ACTIVITY" on page 4-61.

• "MS_ACCESS_BY_TYPE" on page 4-73.

• "MS_TCH_USAGE_BY_TYPE" on page 4-74.

• "MS_TCH_USAGE_BY_TYPE" on page 4-74.



• "OUT_HO_CAUSE_ATMPT" on page 4-85.

TCH assignment

TCH assignment statistics track successful, unsuccessful, and total traffic channel assignmentprocesses. The following are TCH assignment statistics:

• "MA_CMD_TO_MS" on page 4-65.

• "MA_CMD_TO_MS_BLKD" on page 4-72.

• "MA_FAIL_FROM_MS" on page 4-69.

• "MA_REQ_FROM_MSC" on page 4-70.

• "TCH_Q_REMOVED" on page 4-110.

• "TOTAL_CALLS" on page 4-115.

Usage congestion

Usage congestion statistics track congestion processes not related to the directed retryfeature. The following are usage congestion statistics:

• "AVAILABLE_SDCCH" on page 4-20.

• "AVAILABLE_TCH" on page 4-21.

• "BUSY_SDCCH" on page 4-23.

• "BUSY_TCH" on page 4-25.

• "BUSY_TCH_CARR" on page 4-27.

• "CALLS_QUEUED" on page 4-30.

• "CLASSMK_UPDATE_FAIL" on page 4-35.

• "FLOW_CONTROL_BARRED" on page 4-48.

• "MA_COMPLETE_TO_MSC" on page 4-67.

• "MA_FAIL_FROM_MS" on page 4-69.

• "MA_REQ_FROM_MSC" on page 4-70.

• "PAGING_REQUESTS" on page 4-92

• "PCH_AGCH_Q_LENGTH" on page 4-93.

• "PCH_Q_PAGE_DISCARD" on page 4-94.



• {3723}"PPCH_Q_PAGE_DISCARD" on page 4-95

• "SDCCH_CONGESTION" on page 4-99.

• "SECOND_ASSIGN_ATMPT" on page 4-100.

• "SECOND_ASSIGN_SUC" on page 4-101.

• "SMS_INIT_ON_SDCCH" on page 4-102.

• "SMS_INIT_ON_SDCCH_HO_IN" on page 4-103

• "SMS_INIT_ON_TCH" on page 4-104.

• "SMS_NO_BCAST_MSG" on page 4-105.

• "TCH_CONGESTION" on page 4-106.

• "TCH_DELAY" on page 4-108.

• "TCH_Q_LENGTH" on page 4-109.

• "TCH_USAGE" on page 4-111.

DYNET failures

Usage DYNET failures statistics track failures of the DYNET. The following are DYNET failures statistics:

• "DYNET_ASSIGN_FAIL" on page 4-44.

• "DYNET_CALL_REJECTS" on page 4-45.

Interference bands

Interference band statistics track the number of idle TCHs per interference band:

• "IDLE_TCH_INTF_BAND0" on page 4-54.






ACCESS_PER_AGCH Chapter 4: Cell statistics

ACCESS_PER_AGCH

Description

The ACCESS_PER_AGCH statistic tracks Immediate Assignment messages sent onthe Access Grant Channel (AGCH) of a cell.

Access Grants for more than one MS may be contained in one Access Grant message. An Access Grantfor more than one MS is only pegged once. This count includes Immediate Assignment, ImmediateExtended, and Immediate Assignment Reject messages sent on the AGCH of a cell.

PeggingThis statistic pegs when an Access Grant message is sent on the AGCH to signal theavailability of an allocated channel.

AnalysisThis statistic can be used for trend analysis of Intermediate Assignment messages sent on the AGCH of a cell.

Reference GSM 4.03, 3.0.3, 4.3.2.1.GSM 4.08, 3.8.0, 3.3.1.2.1, 7.1.2, 9.1.17-19.GSM 12.04, 3.1.0, B.1.1.10.

Usage Radio resource allocation statistics.Network planning.

Basis Cell.

Type Counter.

This statistic is affected by phantom Random Access CHannel (RACH).The level ofcongestion on the AGCH cannot be determined using current statistics


Maintenance Information: GSM Statistics Application ACCESS_PER_PCH

ACCESS_PER_PCH

Description

The ACCESS_PER_PCH statistic tracks the number of Paging Request messages sent on the air interface.

A paging message could contain up to four pages for paging by TMSI and up to two pages for paging by IMSI.

This statistic is modified to count both Circuit Switched (CS) and Packet Switch(PS) paging on Page Channel (PCH).

This statistic is obtained by measuring the number of PAGING REQUEST messages senton the PCH. This statistic counts the number of attempts.

The bins are:


0 ACCESS_PER_PCH_PS_CS Both CS and PS pages within the PAGINGREQUEST message.

1 ACCESS_PER_PCH_CS Only CS pages within the PAGING REQUESTmessage

2 ACCESS_PER_PCH_PS Only PS pages within the PAGING REQUESTmessage.

PeggingThis statistic pegs received requests that:

• Succeeded (resulting in channel assignment).

• Failed (did not result in channel assignment).

{23658} This statistic is pegged for both GPRS and EGPRS events.


ACCESS_PER_PCH Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of Paging Request messages sent on the PCH of a cell.

Reference GSM 4.03, 3.0.3, 4.3.2.1.GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.GSM 12.04, 3.1.0, B.1.1.10.

Usage Radio resource allocation.Network planning.

Basis Cell.

Type Counter array.

The ACCESS_PER_PCH statistic pegs a second time if the MS does not answer thefirst page. This is because there is no way for the BSS to distinguish between a retryof a page to one MS and an attempt to page a different mobile.


Maintenance Information: GSM Statistics Application ACCESS_PER_PPCH

ACCESS_PER_PPCH

{3723}

Description

The ACCESS_PER_PPCH statistic tracks the number of attempted transmissions of Packet PagingRequest messages sent on the Packet Paging Channel (PPCH).

The bins are:

Bin Description

0 Both CS and PS pages within the PACKET PAGING REQUEST message.

1 Only CS pages within the PACKET PAGING REQUEST message.

2 Only PS pages within the PACKET PAGING REQUEST message.

PeggingThis statistic is obtained by measuring the number of Packet Paging Requests sent onthe PPCH. The number of attempts are counted.


AnalysisThis statistic can be used for trend analysis of Packet Paging Request messages sent on the PPCH of a cell.

Reference GSM 4.03, 3.0.3, 4.3.2.1.GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.GSM 12.04, 3.1.0, B.1.1.10.


Basis Cell.

Type Counter array statistic.


ACCESS_PER_PPCH Chapter 4: Cell statistics

The ACCESS_PER_PPCH statistic pegs a second time if the MS does not answer thefirst page. This is because there is no way for the BSS to distinguish between a retryof a page to one MS and an attempt to page a different mobile.


Maintenance Information: GSM Statistics Application ACCESS_PER_RACH

ACCESS_PER_RACH

Description

The ACCESS_PER_RACH statistic tracks Channel Request messages received by the BSS on the RandomAccess CHannel (RACH) of a cell for Circuit Switched (CS) and Packet Switched (PS) related messages.

A Channel Request message is used by the MS to request allocation of a dedicated channel (to beused as an SDCCH) by the network, in response to a paging message (incoming call) from thenetwork or as a result of an outgoing call/supplementary short message service dialled from theMS. It is also used as part of the call re-establishment procedure.

PeggingThis statistic pegs received requests that:

• Succeeded (resulting in channel assignment).

• Failed (did not result in channel assignment).

AnalysisThis statistic can be used for trend analysis of Channel Request messages sent on the RACH of a cell.

Reference GSM 4.08, 3.8.0, 3.3.1.1, 3.3.2.2, 4.5.1.6, 5.5.4, 7.1.2, 9.1.8 and9.2.4.GSM 4.03, 3.03 and 4.3.2.1.GSM 12.04, 3.2.0, B.1.1.10.

Usage RF loss.Congestion.Quality of service monitoring.Network planning.

Basis Cell.

Type Counter.

This statistic is affected by phantom RACHs. The counter is incremented atleast once for each phantom RACH.


ALLOC_SDCCH Chapter 4: Cell statistics

ALLOC_SDCCH

Description

The ALLOC_SDCCH statistic is the sum of the number of times a SDCCH is successfully seized. Ifa TCH is reconfigured as an SDCCH, only the SDCCH statistics will be configured.

A Channel Request message is used by the MS to request allocation of a dedicated channel (to beused as an SDCCH) by the network, in response to a paging message (incoming call) from thenetwork or as a result of an outgoing call/supplementary short message service dialled from theMS. It is also used as part of the call re-establishment procedure.

SDCCH seizure is caused by immediate assignment, handover, and channel assignment procedures.Congestion is signalled by the Immediate Assignment Reject or the Assignment/Handover Failure message.

PeggingThis statistic pegs each time an Immediate Assignment message is sent by the BSS. AnImmediate Assignment message will be sent upon:

• Successful handover on an SDCCH channel.

• Successful immediate assignment on an SDCCH channel.

This statistic peg for reasons other than calls requiring a traffic channel, such as location updates.

AnalysisThis statistic can be used for trend analysis of SDCCH seizures.

Reference GSM 12.04, 3.1.0, B.1.3.3.GSM 4.08, 3.8.0, 3.3.12, 3.4.3.1, 3.4.4.1, 9.1.2 to 9.1.4, 9.1.14 to9.1.19.

Usage RF loss.Congestion.Quality of service monitoring: Call set-up.Network planning.Ladder: Immediate assignment successful,Intra-cell handover, Inter-BSS handover, Connection establishment,Intra-BSS handover.Key statistic: SDCCH_CONGESTION.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application ALLOC_SDCCH

This statistic is affected by phantom RACHs.


ALLOC_SDCCH_FAIL Chapter 4: Cell statistics

ALLOC_SDCCH_FAIL

Description

The ALLOC_SDCCH_FAIL statistic tracks the number of times that an attempt at SDCCHseizure was rejected because of SDCCH congestion.

If a TCH is reconfigured as an SDCCH, only the SDCCH statistics is incremented. Congestion is signalledby the Immediate Assignment Reject or the Assignment/Handover Failure message.

PeggingThis statistic pegs when an Immediate Assignment Reject message is sent to the MS in response toa channel request because no SDCCH channels were available to be allocated. It is also pegged inthe target cell when rejecting a handover due to a lack of resources.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of SDCCHfailures due to congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCHfailed - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling atthe OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.04, 3.1.0, B.1.3.4.GSM 4.08, 3.8.0, 3.3.1.2.2, 3.4.3.3, 3.4.4.4, 9.1.4, 9.1.16 and 9.1.19.

Usage RF loss.Congestion.Quality of service monitoring: Call set-up.Network planning.Fault finding.Optimization.Ladder: Immediate assignment blocked, Connection establishment.Key statistic : SDCCH_CONGESTION.

Basis Cell.

Type Counter.

Alarm Major.



Maintenance Information: GSM Statistics Application ALLOC_TCH

ALLOC_TCH

Description

The ALLOC_TCH statistic tracks the number of successful full rate and half rate TCHallocations within a cell for both call originations and hand ins.

Pegging

This statistic pegs for successful TCH allocations within a cell as a result of a callestablishment or hand in attempt:

• Successful allocation due to call establishment including successfulallocations due to directed retries.

• Successful allocation due to intra-cell hand in.

• Successful allocation due to inter-cell/intra-cell hand in.

• Successful allocation due to inter-BSS hand in.

This statistic pegs before the transmission of the assignment/handover command to the MS and, therefore,does not take into account the success or failure of the assignment/hand in from an RF perspective.

Analysis

This statistic can be used for trend analysis of TCH allocations.

Usage Quality of service monitoring: Call setup.Network planning.Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cellhandover, Assignment to TCH.Key statistics: TCH_MEAN_AR-RIVAL_RATE, TCH_MEAN_HOLDING_TIME,CELL_TCH_ASSIGNMENTS, TCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.


ALLOC_TCH_FAIL Chapter 4: Cell statistics

ALLOC_TCH_FAIL

Description

The ALLOC_TCH_FAIL statistic tracks the number of unsuccessful full rate and half rateallocations of a TCH within a cell for both call origination and hand in. Cases involvingImmediate Assignment Reject are also included in the peg count.

Pegging

This statistic pegs when an attempt to allocate a TCH in a cell fails due to a lack of resources:

• Unsuccessful allocation due to call establishment including unsuccessfulallocations due to directed retries.

• Unsuccessful allocation due to intra-cell hand in.

• Unsuccessful allocation due to inter-cell/intra cell hand in.

• Unsuccessful allocation due to inter-BSS hand in.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum number of TCHfailures due to congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 25. CELL: Attempt at allocating an TCH failed- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Usage Quality of service: Call set-up.Fault finding.Optimization.Network planning Ladder: Inter-BSS handover, Intra-BSShandover, Assignment to TCH.Key statistics: TCH_MEAN_ARRIVAL_RATE.

Basis Cell.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application ASSIGNMENT_REDIRECTION

ASSIGNMENT_REDIRECTION

Description

The ASSIGNMENT_REDIRECTION statistic tracks the number of times a callassignment is redirected to another cell.


0 DIRECTED_RETRY Tracks the handovers that were executed as theresult of standard directed retry.

1 DURING_ASSIGNMENTS Tracks the handovers that occurred during theassignment for normal radio reasons.

2 MULTIBAND_BAND Tracks the handovers that were executed as theresult of multiband reassign procedure.

PeggingThis statistic pegs whenever a call assignment is redirected to another cell (SD -> TCH).

AnalysisThis statistic can be used for trend analysis of the number of successful internal and externalhandovers performed as the result of standard directed retry mechanisms.

Reference GSM 8.08, 4.90.GSM 3.09, 4.50.GSM 4.08, 4.11.0.

Usage Quality of service.Network planning.

Basis Cell.

Type Counter array.


AVAILABLE_SDCCH Chapter 4: Cell statistics

AVAILABLE_SDCCH

Description

The AVAILABLE_SDCCH statistic tracks the average number of available SDCCHsthat are in use or available for use.

The SDCCH is available when its administrative state is unlocked or shutting down and its operational state isenabled. The SDCCH is unavailable when its administrative state is locked and its operational state is disabled.

PeggingThe statistic pegs whenever there is a change in the channel configuration for any channel in the cell (ifthe number of TCHs has not changed, it will be pegged with the same value as before).

This statistic pegs when a change in SDCCH availability is detected.

AnalysisThis statistic can be used for trend analysis of SDCCH availability.

By comparing the number of available SDCCHs to the total number of SDCCHs in a system, apercentage of utilization can be calculated. An analysis of the utilization information can be used todetermine the requirement for additional resources before problems occur.

Reference GSM 12.04, 4.2.1, B.2.1.21

Usage Congestion.Network planning.

Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application AVAILABLE_TCH

AVAILABLE_TCH

Description

The AVAILABLE_TCH statistic tracks the mean and max number of available TCHsthat are in use or available for use.

The TCH is available when its administrative state is unlocked or shutting down and its operational state isenabled. The TCH is unavailable when its administrative state is locked and its operational state is disabled.

This statistic is modified to exclude all PDTCHs, both switchable and reserved unlessthe switchable PDTCH is configured as TCH.

This statistic is obtained by maintaining the current and total number of available TCH and the amount oftime each TCH is available over the statistical period. The corresponding mean and maximum number ofTCH available are then computed. The TCH is available when its administrative state is unlocked orshutting down and the operational state is enabled and is unavailable when the its administrative statechanges to locked or the operational state changes to disabled. The available number of TCH is thenincremented or decremented when there is a change in TCH states as described above.

This statistic only counts those traffic channels, which are configured as TCH at the time of measurement.Switchable PDTCHs will be included only if they are configured as TCHs.

PeggingThe statistic pegs whenever there is a change in the channel configuration for any channel in the cell (ifthe number of TCHs has not changed, it will be pegged with the same value as before).

This statistic pegs when a change in TCH availability is detected.

AnalysisThis statistic can be used for trend analysis of TCH availability.

By comparing the number of available TCHs to the total number of TCHs in a system, a percentageof utilization can be calculated. An analysis of the utilization information can be used to determinethe requirement for additional resources before problems occur.

Reference GSM 12.04, 4.2.1, B.2.1.10


Basis Cell.

Type Gauge.


BAD_HO_REFNUM_MS Chapter 4: Cell statistics

BAD_HO_REFNUM_MS

Description

The BAD_HO_REFNUM_MS statistic tracks the number of times a MS has accessed a channelwith a Handover Reference Number that the BSS was not expecting.

PeggingThis statistic is pegged once for each time a MS has accessed a channel with a Handover ReferenceNumber that the BSS was not expecting. This field is an unformatted random number. The BSSonly compares what it received with what it expected, for example, potentially up to four timesfor each logical handover detect for the SDCCH processed at the BSS.

The MS will continue to attempt access until a good Handover Reference Number is received,therefore, the handover can be successful and the statistic will still peg. This statistics pegs ifthe handover fails and recovers, or fails and loses the mobile.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number ofMS accesses of channels with Handover Reference Numbers that the BSS was not expectingthat are acceptable in normal system operations.

High values reported for this statistic may not be because a handover access meant for one cell can bedetected by another, but the channel at the target cell is susceptible during the time between channelactivation and when the MS actually arrives. This is similar to “Phantom RACHs."

If the specified threshold is exceeded, the 19. CELL: Bad HO reference numbers from theMS - PM alarm will be generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 4.08, 3.8.0, 3.4.4.2.1, 3.4.4.2.2 and 9.1.13.

Usage Handover.Fault finding.

Basis Cell.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application BUSY_SDCCH

BUSY_SDCCH

Description

The BUSY_SDCCH statistic tracks the number of SDCCHs allocated during an interval.

This is a weighted distribution statistic and will produce a mean value indicating the averagenumber of SDCCHs in use during the interval.

The bin ranges may be changed using the chg_stat_prop command. The default bin rangesfor the BUSY_SDCCH statistic are shown in Table 4-1.


Table 4-1 Default bin ranges for BUSY_SDCCH

Bin Range

0 0 - 0

1 1 - 2

2 3 - 4

3 5 - 6

4 7 - 8

5 9 - 10

6 11 - 12

7 13 - 14

8 15 - 16

9 17 - 400

PeggingThe individual bin values are incremented by the length of time that the number of allocated SDCCHs fallwithin the bin range of values. Bin values are pegged each time a SDCCH is allocated or de-allocated.

If a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be pegged.


BUSY_SDCCH Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of the amount of RF signalling traffic in thecell SDCCHs. An analysis of the allocation information can be used to determine therequirement for additional resources before problems occur.

Reference GSM 12.04, 3.1.0, B.1.3.2.

Usage RF loss.Congestion.Quality of service monitoring.Network planning.Optimization.Key statistic: SDCCH_MEAN_HOLDING_TIME, SDCCH_TRAFFIC_CARRIED.

Basis Cell.

Type Weighted distribution.


Maintenance Information: GSM Statistics Application BUSY_TCH

BUSY_TCH

Description

The BUSY_TCH statistic tracks the number of full rate and half rate TCHs allocated during an interval.

This is a weighted distribution statistic and produces a mean value indicating the average number ofTCHs in use during the interval. It is an indication of the average capacity for additional traffic inthe cell. This statistic includes TCHs used as a Dedicated Control CHannel (DCCH) in immediateassignment mode. The BUSY_TCH time includes the guard time (the time allowed between endinga call and being allowed to start another). Since the channel is not available to be used againuntil the guard timer expires, it is not considered to be free until then.

The bin ranges may be changed using the chg_stat_prop command. The default bin rangesfor the BUSY_TCH statistic are shown in Table 4-2.

Table 4-2 Default bin ranges for BUSY_TCH

Bin Range

0 0 - 0

1 1 - 2

2 3 - 4

3 5 - 6

4 7 - 8

5 9 - 10

6 11 - 12

7 13 - 14

8 15 - 16

9 17 - 400

Pegging

The individual bin values are incremented by the length of time that the number of allocated full rate and halfrate TCHs fall within the bin range of values. Bin values peg each time a TCH is allocated or de-allocated.

If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are pegged.


BUSY_TCH Chapter 4: Cell statistics

Analysis

The value of this statistic is not dependent on the number of transceivers. Rather it is dependent on thenumber (however large) of simultaneously busy channels. The only dependence on the number of transceiversis that the value reported may be larger if more traffic channels are used simultaneously.

This statistic can be used for trend analysis of the amount of RF signalling traffic in the cellTCHs. An analysis of the allocation information can be used to determine the requirementfor additional resources before problems occur.

Reference GSM 12.04, 3.1.0, B1.1.1. GSM 4.08, 3.8.0, 3.3.1.2.1.

Usage RF loss.Congestion.Quality of service monitoring.Network planning.Optimization.Key statistic: TCH_MEAN_HOLDING_TIME,TCH_TRAFFIC_CARRIED.

Basis Cell.



Maintenance Information: GSM Statistics Application BUSY_TCH_CARR

BUSY_TCH_CARR

Description

TheBUSY_TCH_CARR statistic tracks the number of full rate and half rate TCHs allocated during an interval.

This is a gauge statistic and produces a mean value indicating the average number of TCHs in use during theinterval. It is an indication of the average capacity for additional traffic in the cell. This statistic includes TCHsused as a Dedicated Control CHannel (DCCH) in immediate assignment mode. The BUSY_TCH_CARR timeincludes the guard time (the time allowed between ending a call and being allowed to start another). Since thechannel is not available to be used again until the guard timer expires, it is not considered to be free until then.

Pegging

This statistic pegs when a change in the number of full rate and half rate TCHs in use are detected.

Analysis

This statistic can be used for trend analysis of the amount of RF signalling traffic in the cellTCHs. An analysis of the allocation information can be used to determine the requirementfor additional resources before problems occur.

Reference GSM 12.04, 3.1.0, B1.1.1. GSM 4.08, 3.8.0, 3.3.1.2.1.

Usage Congestion.Network planning.Optimization.

Basis Carrier.

Type Gauge.


CALL_SP_VERS_DOWNGRADE_MONITOR Chapter 4: Cell statistics

CALL_SP_VERS_DOWNGRADE_MONITOR

Description

This statistic tracks the number of call rejects and call downgrades due to not sup-porting requested speech versions.

{4322} The statistic keeps a count of the number of times that the codec mode was downgradedfor EFR, HR AMR FR AMR and GSM HR calls on a per BSS basis.


0 EFR_REQUEST_DOWNGRADE Pegged when the call is downgraded dueto CIC capabilities:Assignment request foror including EFRHandover request for orincluding EFRIn-call modification requestfor or including EFR.

1 {4322}AMR_FR_CALL_DOWNGRADE Pegged when the full-rate AMR call isdowngraded.

2 {4322}AMR_HR_CALL_DOWNGRADE Pegged when the half-rate AMR call isdowngraded.

{22064} With the Half Rate feature unrestricted, the statistic also keeps a count of the number of times thatthe codec mode was downgraded for GSM HR calls on a per BSS basis. The additional bin is as follows:


3 GSM_HR_CALL_DOWNGRADE Pegged when the half-rate GSM call isdowngraded.

Pegging

The bin corresponding to the cause of the call downgrade or reject is as indicated in description above.


Maintenance Information: GSM Statistics Application CALL_SP_VERS_DOWNGRADE_MONITOR

Analysis

This statistic can be used for analysis of non-support of requested speech versions.No alarms are raised by this statistic.

Reference GSM 08.08

Usage Radio resource allocation.Quality of service monitoring.Network planning.Optimization.

Basis BSS.

Type Counter array.


CALLS_QUEUED Chapter 4: Cell statistics

CALLS_QUEUED

Description

The CALLS_QUEUED statistic tracks the Assignment Requests that are queued during aninterval. If queuing has been allowed and no resources exist, the CRM queues an assignmentrequest and informs the RRSM with a force queue message.

This statistic does not track handovers.

PeggingThis statistic pegs when queueing is enabled in an assignment request and available queueblocks are used to queue the call successfully.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of callsqueued for each cell on the BSS that are acceptable in normal system operations.

If the specified threshold is exceeded, the 20. CELL: Number of calls queued - PM alarmwill be generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.

Reference GSM 3.01, 3.1.1, 4.1.GSM 4.08, 3.8.0, 5.2.1.1.10 and 5.2.2.8.GSM 8.08, 3.9.2, 3.1.17.

Usage Quality of service monitoring: queuing delay.Network planning.Optimization.Fault finding.Ladder: BSS initiated call clearing.

Basis Cell.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application CHAN_REQ_CAUSE_ATMPT

CHAN_REQ_CAUSE_ATMPT

Description

The CHAN_REQ_CAUSE_ATMPT statistic tracks the number of Channel Request messages received bythe network from a MS (or LMU) by cause. A total count of all successful results is also tracked.


0 ORIGINATING_CALL Number of MS requests for originating service.

1 EMERGENCY_CALL Number of MS requests for emergency call service.

2 CM_REESTABLISH Number of failed MS requests for service in whichthe call recovered to the original cell.

3 LOCATION_UPDATE Number of MS location update requests.

4 PAGE_RESPONSE Number of MS page request responses.

5 LMU_ESTABLISHMENT Number of channel requests from LocationMeasurement Unit devices. (An LMU is a specialdevice used for certain kinds of Location Services).

PeggingThis statistic pegs the cause of each Channel Request message received by the network from a MS.

AnalysisThis statistic can be used for trend analysis of the type of Channel Request messages thatare received from MSs. This information can be used to used to determine the requirementfor additional resources before problems occur.

Reference GSM 12.04, 4.21, B.2.1.6.GSM 4.08, v4.15.0, 9.1.8.

Usage Radio resource allocation.Quality of service monitoring.Network planning.

Basis Cell.

Type Counter array.


CHAN_REQ_MS_BLK Chapter 4: Cell statistics

CHAN_REQ_MS_BLK

Description

The CHAN_REQ_MS_BLK statistic tracks the number of times a MS has been refused access to a channel.

An Immediate Assignment Reject message was sent to the MS on CCCH. This event indicatesthat the MS has requested allocation of a dedicated channel, and the network has responded byrefusing immediate access to a channel. Pegging of this counter indicates that there are no channelsavailable for assignment in the cell. The counter pegs once for each Channel Request Reference inthe message announcing the blocking. The cell is therefore fully used, and it will not be possibleto hand over existing calls into the cell or set up new calls in the cell.

If adjacent cells that are candidates for handover are unable to provide the MS with a radioresource, it will be impossible for the MS to initiate a call. Handover of calls may beprevented. This will result in call blocking and loss.

PeggingThis statistic pegs when an Immediate Assignment Reject message is sent to the MS on CCCH thusindicating that there are no channels available for assignment in the cell.

AnalysisThis statistic can be used for trend analysis of the number of times channel access has been denied. Thisinformation can be used to used to determine the requirement for additional resources.

Reference GSM 4.08, 3.8.0, 4.5.1.1,8 and 9.1.27a

Usage Radio resource and allocation.Fault finding.Network planning.Quality of service monitoring : Call setup.Ladder : Immediate assignment blocked

Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application CHAN_REQ_MS_FAIL

CHAN_REQ_MS_FAIL

Description

This statistic is the number of times that the BSS times out waiting for the MS to establish on the SDCCH thatwas assigned to it during the immediate assignment procedure (see "CHAN_REQ_MS_FAIL" on page 6-9).


CIPHER_MODE_FAIL Chapter 4: Cell statistics

CIPHER_MODE_FAIL

Description

The CIPHER_MODE_FAIL statistic pegs when an internal Motorola-defined timer in the BSS expiresto indicate that the MS did not respond to the Cipher Mode Command message with the Cipher ModeComplete message within the allowable time period or responded improperly. It indicates that the MSprobably did not switch correctly into encrypted communication mode when commanded to do so.

PeggingThis statistic pegs when the MS fails to respond to a Cipher Mode Command from the BSS.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of times that MSfailures to respond to BSS Cipher Mode Command messages are acceptable in normal system operations.

If the specified threshold is exceeded, the 6. CELL: Cipher mode command from MSCfailed - PM alarm will be generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 4.08, 3.8.0,8 and 9.1.9.GSM 8.08, 3.9.2, 3.1.14 and 3.2.1.30.

Usage Classmark update and cipher mode.Quality of service monitoring.Fault finding.Ladder: BSS initiated call clearing.

Basis Cell.

Type Counter.

Alarm Minor.


Maintenance Information: GSM Statistics Application CLASSMK_UPDATE_FAIL

CLASSMK_UPDATE_FAIL

Description

The CLASSMK_UPDATE_FAIL statistic tracks the number of classmark updates containing errors. Theclassmark update procedure allows the MS to inform the network of a change to its classmark.

PeggingThis statistic pegs when the validation of the Classmark Update message from the MS fails.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of classmarkupdates containing errors that are acceptable in normal system operations.

If the specified threshold is exceeded, the 4. CELL: Class-mark update from MS protocolerror - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 4.08, 3.8.0,8 and 10.5.1.5-6.GSM 8.08, 3.9.2, 3.1.13 and 3.2.1.29.

Usage Classmark update and cipher mode.Quality of service monitoring.Fault finding.

Basis Cell.

Type Counter.

Alarm Minor.


CLR_CMD_FROM_MSC Chapter 4: Cell statistics

CLR_CMD_FROM_MSC

Description

The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commands received fromthe MSC for SDCCH and TCH resources thereby allowing the analysis of dropped calls.

PeggingThis statistic pegs when a Clear command is received from the MSC.


0 CLR_CMD_FROM_MSC_SD Counts the number of clear commands receivedfrom the MSC for an SDCCH.

1 CLR_CMD_FROM_MSC_FR Counts the number of clear commands receivedfrom the MSC for a Full Rate TCH.

2 CLR_CMD_FROM_MSC_HR Counts the number of clear commands receivedfrom the MSC for a Half Rate TCH.

AnalysisThis statistic can be used for trend analysis of the number of Clear commands received from the MSC.This information can be used to identify and correct problems before they become serious.

Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.

Usage Radio resource allocation.Quality of service monitoring.Fault finding.Network planning.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application CLR_REQ_TO_MSC

CLR_REQ_TO_MSC

Description

The CLR_REQ_TO_MSC statistic separately tracks the number of Clear Request messagessent to the MSC for SDCCH and TCH resources.

GeneratingThe Clear Request message may be generated due to one of the following:

• No radio resources available to allocate from the BSS, call queuing is enabled,and the maximum call delay has been exceeded.

• Radio interface message failure.

• Protocol error.

• Ciphering algorithm not supported.

SendingAll Clear Requests are sent per GSM 8.08 specifications. The Clear Request messages are sent to theMSC because of radio channel failure or a timeout during a procedure. In this case a timeout meansa required message was not received during a procedure. The procedures are:

• Immediate Assignment.

• Assignment.

• Channel Mode Modify.

• Ciphering.

• Handover - Intra-cell, Inter-cell and External.

PeggingThis statistic pegs when the BSS sends a Clear Request message to the MSC. CLR_REQ_TO_MSCis pegged for numerous reasons related to timer expiry. It is a mix of both GSM and internal Motorolatimers. Normal release of a call either from a MS or Land site never cause it to be pegged. A callmust have at least been assigned to an SDCCH or TCH in order for this to be pegged. It is notpegged when on an AGCH overload. RF loss is the major cause of pegging.


CLR_REQ_TO_MSC Chapter 4: Cell statistics


0 CLR_REQ_TO_MSC_SD Counts the number of clear requests sent to theMSC for an SDCCH.

1 CLR_REQ_TO_MSC_FR Counts the number of clear requests sent to theMSC for a Full Rate TCH.

2 CLR_REQ_TO_MSC_HR Counts the number of clear requests sent to theMSC for a Half Rate TCH.

CLR_REQ_TO_MSC is not pegged when the CONN_REFUSED statistic is pegged. However,there are a number of cases where CLR_REQ_TO_MSC is pegged and no associated statisticis pegged. For example, if during an assignment the BSS determines that the cell is barred,CLR_REQ_TO_MSC is pegged but no associated statistic is pegged.

AnalysisThis statistic can be used for trend analysis of the number of Clear Request messages sent to the MSC.This information can be used to identify and correct problems before they become serious.

Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.

Usage Radio resource allocation.Quality of service monitoring.Fault finding.Network planning.Ladder : BSS initiated call clearing, handover (Intra-cell) fail/lost,handover (Intra-BSS) fail/lost.

Adding up the statistics in the ladder diagrams will nottotal CLR_REQ_TO_MSC.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application CONGEST_EXIST_HO_ATMPT

CONGEST_EXIST_HO_ATMPT

Description

The CONGEST_EXIST_HO_ATMPT statistic tracks the number of attempted inter-cell handovers (internalor external to the BSS) of calls on a TCH due to TCH congestion from the source cell.

PeggingThis statistic pegs each time a congestion relief handover is attempted. This statistic ispegged for both internal inter-cell and external handovers.

AnalysisThis statistic can be used for trend analysis of the number of internal and external handoversattempts due to TCH congestion from source cells.


Usage Optimization.Network planning.

Basis Cell.

Type Counter.


CONGEST_STAND_HO_ATMPT Chapter 4: Cell statistics

CONGEST_STAND_HO_ATMPT

Description

The CONGEST_STAND_HO_ATMPT statistic tracks the number of attempted handovers of a MS dueto standard Directed Retry procedure caused by TCH congestion from the source cell. These inter-cellhandovers (internal or external to the BSS) involve changing the channel mode during the handover.

PeggingThis statistic pegs each time a Directed Retry handover procedure is attempted forboth inter-cell and external handovers.

AnalysisThis statistic can be used for trend analysis of the number of attempted internal or external handoversdue to standard Directed Retry mechanisms caused by TCH congestion.



Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application CONN_REFUSED

CONN_REFUSED

Description

The CONN_REFUSED statistic tracks the number of SCCP connection refused(CREF) messages received from the MSC.

PeggingThis statistic pegs when the MSC sends the BSS an SCCP Connection Refused (CREF) message.The MSC may send an SCCP Connection Refused message in response to a BSS generatedSCCP Connection Request (CR) message, as a result of

• MS access for a location update.

• MS originated call establishment.

• MS terminated call establishment.

• SMS activity.

• Supplementary service activity.

• IMSI detach.

• Call re-establishment.

For example, if an association already exists for the identity of the MS requesting a connection,the connection request is refused, and this statistic pegs.

Analyse MSC statistics to determine why the CONN_REFUSED statistic is pegged.

Some MSCs may generate a Connection Refused Message during a successful IMSI Detachrather than a Connection Confirm, so a high value for the CONN_REFUSED statistic maynot indicate a system problem. The MSC performance during IMSI Detach proceduresshould be investigated before interpreting the CONN_REFUSED statistic.


CONN_REFUSED Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of the reasons for connections refusedfrom the MSC. This is an MSC procedure.

Reference GSM 8.06, 3.5.0, 6.1.GSM 8.08, 3.9.2, 3.1.16.

Usage Originated call and service/connection request.Quality of service monitoring.Optimization.Network planning.Ladder: Connection establishment failure.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application CONN_REQ_TO_MSC

CONN_REQ_TO_MSC

Description

TheCONN_REQ_TO_MSC statistic tracks the number of connection requests that the BSS sends to theMSC.

PeggingThe statistic pegs only for connection establishments initiated by the BSS. This message is sent bythe MS when it is requesting set-up of the connections for several types of transactions, includinglocation updates, connection establishments (including re-establishment on failure, short messagetransfer, and supplementary service requests), and paging responses.

AnalysisThis statistic can be used for trend analysis of the number of connection requests sent from the BSS to the MSC.

Reference GSM 8.06, 3.5.0, 6.1.GSM 8.08, 3.9.2, 3.1.16.

Usage Originated call and service/connection request.Network planning.Ladder: Connection establishment successful, connectionestablishment failure.

Basis Cell.

Type Counter.


DYNET_ASSIGN_FAIL Chapter 4: Cell statistics

DYNET_ASSIGN_FAIL

Description

The DYNET_ASSIGN_FAIL statistic tracks the number of times assignments have failed due toinsufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.

PeggingThis statistic pegs each time an assignment procedure fails due to the lack of terrestrial backing resources.

Usage Quality of service monitoring.Radio resource allocation.Network planning.

Basis BSS.

Type Counter.

Alarm None.


Maintenance Information: GSM Statistics Application DYNET_CALL_REJECTS

DYNET_CALL_REJECTS

Description

The DYNET_CALL_REJECTS statistic tracks the number of times calls have been blocked or preempteddue to insufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.

Bin Procedures Description

0 NON_EMRG_CALL_BLK A non-emergency call is not allocated a TCH dueto the lack of terrestrial backing resources in a BTSnetwork.

1 EMRG_CALL_BLK An emergency call is not allocated a TCH due tothe lack of terrestrial backing resources in a BTSnetwork.

2 NON_EMRG_RESERVED A non-emergency call is not allocated a TCH due tothe cell exceeding its reserve amount of terrestrialbacking resources and no further backing resourcesare available.

3 NON_EMRG_PREEMP A non-emergency call is preempted to provideterrestrial backing resources for an emergency call.

4 LOSS_OF_RESOURCES An emergency or non-emergency call is preempteddue to the loss of of terrestrial backing resources.

PeggingThe appropriate bin is incremented when specific calls are rejected or preempted.

Usage Quality of service monitoring.Networking planning.Radio resource allocation.

Basis DYNET.

Type Counter array.

Alarm None.


ER_INTRA_CELL_HO_ATMPT Chapter 4: Cell statistics

ER_INTRA_CELL_HO_ATMPT

Description

The ER_INTRA_CELL_HO_ATMPT statistics tracks the number of attempted intra-cellhandovers between normal range and extended range channels in an extended range cell. Atotal count of attempted handover is also maintained.

This statistic may be enabled only if the Extended Range Cell feature is unrestricted and enabled for the cell.


0 NORM_TO_EXT_HO Number of intra-cell handover attempts fromnormal range channels to extended range channels.

1 EXT_TO_NORM_HO Number of intra-cell handover attempts fromextended range channels to normal range channels.

PeggingThis statistic pegs each time a handover is attempted between a normal channel and anextended channel in an extended range cell.

AnalysisThis statistic can be used for trend analysis of the attempted intra-cell handovers between normal and extendedrange channels in an extended range cell. The number of attempted extended range intra-cell handovers canbe used to determine the number of extended range timeslots to configure in an extended range cell.

Reference None.

Usage Quality of service.Network planning.Radio resource allocation.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application ER_INTRA_CELL_HO_SUC

ER_INTRA_CELL_HO_SUC

Description

The ER_INTRA_CELL_HO_SUC tracks the number of successful intra-cell handovers betweennormal range and extended range channels in an extended range cell. The values reportedfor this statistic can be used to configure normal and extended range traffic channels in a cell.A total count of attempted handover is also maintained.

This statistic may be enabled only if the Extended Range Cell feature is unrestricted and enabled for the cell.


0 NORM_TO_EXT_HO Number of successful intra-cell handovers fromnormal range channels to extended range channels.

1 EXT_TO_NORM_HO Number of successful intra-cell handovers fromextended range channels to normal range channels.

PeggingThis statistic pegs each time a handover is successful between a normal channel and an extendedchannel in an extended range cell. No other intra_cell handover statistic is pegged when one ofthe bins of the ER_INTRA_CELL_HO_SUC statistic is pegged.

AnalysisThis statistic can be used for trend analysis of the successful intra-cell handovers between normal and extendedrange channels in an extended range cell. The number of successful extended range intra-cell handovers canbe used to determine the number of extended range timeslots to configure in an extended range cell.

Reference None.


Basis Cell.

Type Counter array.


FLOW_CONTROL_BARRED Chapter 4: Cell statistics

FLOW_CONTROL_BARRED

Description

The FLOW_CONTROL_BARRED statistic tracks the duration for which access classes are barred as a resultof flow control. This statistic gives an indication when flow control actions have been taken to prevent overload.

PeggingThe statistic duration is started when any of the access classes are barred due to flow control and stoppedwhen the last access class which was barred due to flow control is unbarred.

AnalysisThis statistic can be used for trend analysis of the access classes barred as a result of flow control.

Usage Quality of Service.Network Planning.Optimization.

Basis Cell.

Type Duration (total time in milliseconds).


Maintenance Information: GSM Statistics Application HO_FAIL_NO_RESOURCES

HO_FAIL_NO_RESOURCES

Description

TheHO_FAIL_NO_RESOURCES tracks the number of handover failures due to a lack of available resources.

Bin Scenario Description

0 INTRA_BSS Number of intra-BSS handover failures due to alack of available resources.

1 INTER_BSS Number of inter-BSS handover failures due to alack of available resources.

2 INTRA_CELL Number of intra-cell handover failures due to a lackof available resources.

3 INTRA_BSS_DYNET Number of BTS Dynamic Allocation intra-BSShandover failures due to a lack of availableresources.

4 INTER_BSS_DYNET Number of BTS Dynamic Allocation inter-cellhandover failures due to a lack of availableresources.

5 INTRA_CELL_DYNET Number of BTS Dynamic Allocation intra-cellhandover failures due to a lack of availableresources.

PeggingThese individual bins are incremented on a per scenario basis.


HO_FAIL_NO_RESOURCES Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of the handover failures due to a lack of resources, such as:

• The target cell is barred for some reason, such as hardware failure.

• The channel is unavailable, that is there is congestion at the target celland the queue timer is expired.

• Incoming handovers are turned off at the target.

• The speech algorithm at the target BSS is not supported by the MS.

• An SCCP connection is not allocated, that is CRM runs out of SCCP numbers.

Reference Metrica.

Usage Radio resource allocation.Quality of service monitoring.Network planning.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application HO_REQ_MSC_FAIL

HO_REQ_MSC_FAIL

Description

The HO_REQ_MSC_FAIL statistic tracks the number of handover request failure messages sent to theMSC, except for no channel resources available. This message is sent to notify the MSC that the BSScould not reserve the radio resource that the MSC requested in the Handover Request message.

PeggingThis statistic pegs in the source or target cell depending on where the failure occurs.

This statistic pegs in the source cell if the handover failure originates from the MS. Thisindicates that the MS has reverted back to its original channel.

This statistic pegs in the target cell if the handover failure message originates from the target cell.This could indicate one of the following problems: terrestrial circuit unavailable, terrestrial circuitin use, ciphering algorithm not supported, or radio resources unavailable.

This statistic is not pegged if resources are not available in the target cell.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of handover failuresfor any reason other than lack of channel resources that are acceptable in normal system operations.

If the specified threshold is exceeded, the 18. CELL: HO failure to the MSC due to all possibleerrors except no channels - PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.1.5.3.2, 3.2.1.8 and 3.2.1.16.

Usage Handover.Fault finding.Ladder: Handover (Inter-BSS) blocked.

Basis Cell.

Type Counter.

Alarm Warning.

HO_REQ_MSC_FAIL can be equal to INTER_BSS_MS_FAIL if the cell hasnever been the target for a failed handover.


HO_REQ_ACK_TO_MSC Chapter 4: Cell statistics

HO_REQ_ACK_TO_MSC

{4322 unless stated otherwise}

This statistic was previously named HO_REQ_MSC_OK.

Description

The HO_REQ_ACK_TO_MSC statistic tracks the number of handover request acknowledge messages sentto theMSC for each channel type and speech version by the destination cell in an inter-BSS (external) handover.


0 PM_FR Counts the number of full rate handoverrequest acknowledgements sent to the MSC.

1 PM_EFR Counts the number of enhanced full ratehandover request acknowledgements sent tothe MSC.

2 PM_AMR_FR Counts the number of Adaptive Multi-ratefull rate handover request acknowledgmentssent to the MSC.

3 PM_AMR_HR Counts the number of Adaptive Multi-ratehalf rate handover request acknowledgmentssent to the MSC.

4 PM_SIGNALLING Counts the number of SDCCH channelhandover request acknowledgments sent tothe MSC.

5 PM_DATA Counts the number of data handover requestacknowledgments sent to the MSC.

{22064} When the Half Rate feature is unrestricted, the HO_REQ_ACK_TO_MSC bintable introduces bin procedure PM_GSM_HR as shown:

Bin Procedure Description

6 PM_GSM_HR Counts the number of GSM half ratehandover request acknowledgments sent tothe MSC.


Maintenance Information: GSM Statistics Application HO_REQ_ACK_TO_MSC

Pegging

This statistic pegs for each channel type and speech version when the BSS sends a Handover RequestAcknowledge message to the MSC. This message is sent to notify the MSC that the BSS has reservedthe radio resource that the MSC asked for in the Handover Request message.

Analysis

This statistic can be used for trend analysis of successful radio resource reservations per channel typeand speech version by the BSS in response to MSC Handover Request messages.

Reference GSM 08.08, 3.9.2, 3.1.5.3.1, 3.2.1.8 and 3.2.1.10.

Usage Handover.Network planning.Ladder: Handover (Inter-BSS) successful, handover (Inter-BSS)fail/recovered.

Basis Cell.



IDLE_TCH_INTF_BAND0 Chapter 4: Cell statistics

IDLE_TCH_INTF_BAND0

Description

The IDLE_TCH_INTF_BAND0 statistic tracks the maximum and mean number of idle trafficchannels (TCHs) for interference band 0. An idle TCH falls into band 0 if its average interferenceband is less than the value of the element interfer_bands, 0.

Idle TCHs are allocated to five interference bands. Each band has an associatedstatistic for tracking idle TCHs.

PeggingThis statistic is reported periodically using the rf_res_ind_period element.

AnalysisThis statistic can be used for trend analysis of idle traffic channels.

Reference GSM 12.04, 4.2.1, B.2.1.13.

Usage Service integrity.Fault finding.

Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IDLE_TCH_INTF_BAND1

IDLE_TCH_INTF_BAND1

Description





Reference GSM 12.04, 4.2.1, B.2.1.13.


Basis Cell.

Type Gauge.



IDLE_TCH_INTF_BAND2

Description





Reference GSM 12.04, 4.2.1, B.2.1.13.


Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IDLE_TCH_INTF_BAND3

IDLE_TCH_INTF_BAND3

Description





Reference GSM 12.04, 4.2.1, B.2.1.13.


Basis Cell.

Type Gauge.



IDLE_TCH_INTF_BAND4

Description





Reference GSM 12.04, 4.2.1, B.2.1.13.


Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IN_INTER_BSS_HO

IN_INTER_BSS_HO

Description

The IN_INTER_BSS_HO statistic tracks incoming inter-BSS handover procedures on a per scenariobasis. A total value for this statistic is not meaningful and is not displayed.


0 IN_INTER_BSS_HO_SUC Number of successful incoming inter-BSShandovers.

1 IN_INTER_BSS_MS_NO_SEIZE Number of times an MS does not seize an allocatedchannel.This statistic is not currently pegged.

2 IN_INTER_BSS_EQUIP_FAIL Number of incoming inter-BSS handovers that faildue to equipment failure.

3 IN_INTER_BSS_HO_CLEARED Number of incoming inter-BSS handovers aborteddue to call clearing. This scenario corresponds tothe receipt of a Clear Command, SCCP Released,or Release Done (internal message) during thehandover procedure.

PeggingThese individual bins are incremented on a per cause basis.

AnalysisThis statistic can be used for trend analysis of incoming inter-BSS handover procedures on a per scenario basis.

Reference Metrica, GSM 12.04, 3.1.0, B.1.1.7.

Usage Radio resource allocation.Quality of service monitoring.Network planning.Fault finding.Handover.

Basis Cell.

Type Counter array.


IN_INTRA_BSS_HO Chapter 4: Cell statistics

IN_INTRA_BSS_HO

Description

The IN_INTRA_BSS_HO statistic tracks incoming intra-BSS handover procedures on a per scenariobasis. A total value for this statistic is not meaningful and is not displayed.


0 IN_INTRA_BSS_HO_SUC Number of successful incoming intra-cellhandovers.

1 IN_INTRA_BSS_HO_LOSTMS Number of failed incoming intra-BSS handoversthat also failed to recover to the original cell.

2 IN_INTRA_BSS_EQUIP_FAIL Number of failed incoming intra-BSS handoversthat fail due to equipment failure.

3 IN_INTRA_BSS_HO_RETURN Number of failed incoming intra-BSS handoversthat recover to the original cell/channel.

4 IN_INTRA_BSS_HO_CLEARED Number of incoming intra-BSS handovers aborteddue to call clearing. This scenario corresponds tothe receipt of a Clear Command, SCCP Released,or Release Done (internal message) during thehandover procedure.

PeggingThese individual bins are incremented on a per scenario basis.

AnalysisThis statistic can be used for trend analysis of incoming intra-BSS handover procedures on a per scenario basis.

Reference Metrica.GSM 8.08, 3.9.2, 3.1.7, 3.1.5.2.1, 3.2.1.12.

Usage Radio resource allocation.Quality of service monitoring.Network planning.Service retainability.Fault finding.Handover.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application INTERBAND_ACTIVITY

INTERBAND_ACTIVITY

Description

The INTERBAND_ACTIVITY statistic tracks inter-band handover attempts in the BSS. Assignmentand handover failures due to incorrect or unsupported frequency information are also tracked. TheMultiband option must be enabled for this statistic to be enabled, disabled, or displayed.


0 PGSM_HO_ATMPT Attempts to handover to base GSM band.

1 EGSM_HO_ATMPT Attempts to handover to extended GSM band.

2 DCS1800_HO_ATMPT Attempts to handover to DSC1800 band.

3 PCS1900_HO_ATMPT Attempts to handover to PCS1900 band.

4 PGSM_HO_FAIL Handover failures to base GSM band.

5 EGSM_HO_FAIL Handover failures to extended GSM band.

6 DCS1800_HO_FAIL Handover failures to DCS1800 band.

7 PCS1900_HO_FAIL Handover failures to PCS1900 band.

8 INVALID_FREQ_ASGN Frequency not implemented for assignment request.

9 INVALID_FREQ_HO Frequency not implemented for handover.

PeggingThis individual bins are incremented on a per cause basis. For inter-band handovers, thebin of the destination frequency is pegged.

AnalysisThis statistic can be used for trend analysis of inter-band handover attempts in the BSS on a per cause basis.

Reference None.

Usage Handover.Quality of service monitoring.Network planning.Service retainability.

Basis Cell.

Type Counter array.


INTRA_CELL_HO Chapter 4: Cell statistics

INTRA_CELL_HO

Description

The INTRA_CELL_HO statistic tracks intra-cell handovers on a per scenario basis.

{4322} This statistic is enhanced to count the number of congestion/quality related handovers:

• full-rate to full-rate intra-cell handovers.

• full-rate to half-rate intra-cell handovers.

• half-rate to half-rate intra-cell handovers.

• half-rate to full-rate intra-cell handovers.

A total value for this statistic is not meaningful and is not displayed.


0 INTRA_CELL_HO_REQ Number of times an intra-cell handover isconsidered the best option by the handoverevaluator process.

1 {4322}IN-TRA_CELL_HO_ATMPT_FR_FR

Number of assignment commands sent to MSduring a full-rate to full-rate intra-cell handover.

2 {4322}IN-TRA_CELL_HO_ATMPT_HR_HR

Number of assignment commands sent to MSduring a half-rate to half-rate intra-cell handover.

3 {4322}IN-TRA_CELL_HO_ATMPT_HR_FR

Number of assignment commands sent to MSduring a half-rate to full-rate intra-cell handover.

4 {4322}IN-TRA_CELL_HO_ATMPT_FR_HR

Number of assignment commands sent to MSduring a full-rate to half-rate intra-cell handover.

5 INTRA_CELL_HO_SUC Number of successful intra-cell handovers.

6 INTRA_CELL_HO_LOSTMS Number of failed intra-cell handovers that alsofailed to recover to the original cell.

7 INTRA_CELL_HO_RETURN Number of failed intra-cell handovers that recoveredto the original cell/channel.

8 INTRA_CELL_EQUIP_FAIL Number of attempted intra-cell handover failuresdue to equipment failure.

9 INTRA_CELL_HO_CLEARED Number of incoming intra-cell handovers aborteddue to call clearing. This scenario corresponds tothe receipt of a Clear Command, SCCP Released,or Release Done (internal message) during thehandover procedure.


Maintenance Information: GSM Statistics Application INTRA_CELL_HO

PeggingINTRA_CELL_HO_REQ is pegged just before sending the intra-cell handover message.INTRA_CELL_HO_ATMPT_XX_XX replaces INTRA_CELL_HO_ATMPT below.

{4322} INTRA_CELL_HO_ATMPT_XX_XX is pegged after the channel activation message isreceived and just before the assignment command is sent to the MS.

INTRA_CELL_HO_SUC is pegged each time a handover performed message is sent to the MS.

INTRA_CELL_HO_LOSTMS is pegged when a radio channel released message is received.

INTRA_CELL_HO_RETURN is pegged when a revert to old channel message is received.

INTRA_CELL_EQUIP_FAIL is pegged when an assignment failure message contains anequipment failure cause or KSW/highway fault.

INTRA_CELL_HO_CLEARED is pegged every time a call is cleared down during an intra-cell handover.

AnalysisThis statistic can be used for trend analysis of intra-cell handovers on a per scenario basis.

Reference Metrica.GSM 12.04, 3.1.0, B.1.1.6.GSM 8.08, 3.9.2, 3.1.6, 3.2.1.25.GSM 4.08, 3.8.0, 9.1.3.

Usage Radio resource allocation.Quality of service monitoring.Network planning.Fault finding.Service retainability.

Basis Cell.

Type Counter array.


INV_EST_CAUSE_ON_RACH Chapter 4: Cell statistics

INV_EST_CAUSE_ON_RACH

Description

The INV_EST_CAUSE statistic tracks the number of RACHs with invalid establishment cause.This helps to account more fully for occurrences of Phantom RACHs.

PeggingThis statistic pegs when the establishment cause is not validated.

It is possible for invalid Channel Requests not to be pegged by this statistic because the Channel Requestsare precisely formatted to prevent being caught by all the validation routines (channel coder, RSS Layer 1,RSS Abis). These invalid Channel Requests that are not pegged are due to phantom RACHs.

AnalysisThis statistic can be used for trend analysis of RACHs with invalid establishment causes.

Reference GSM 4.08, 3.8.0, 3.3.1.1, 3.3.2.2, 4.5.1.6, 5.5.4, 7.1.2, 9.1.8, and9.2.4.GSM 4.03, 3.03, and 4.3.2.1.

Usage Handover.Quality of service monitoring.Fault finding.Ladder: Immediate Assignment Failure.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application MA_CMD_TO_MS

MA_CMD_TO_MS

Description

TheMA_CMD_TO_MS statistic tracks the number of Assignment Commands sent to the MS.

PeggingThis statistic pegs when the BSS initiates the channel assignment procedure by sending an AssignmentCommand to the MS on the main SDCCH. Assignment Command is sent to the MS at call setup(traffic channel assignment) and at intra-cell handovers. This causes the MS to:

• Release its link layer connections.

• Disconnect from its current physical channels.

• Switch to the assigned channels.

• Initiate re-establishment of the lower layer connections.

AnalysisThis statistic can be used for trend analysis of BSS initiated channel assignment procedures to the MS.

Reference GSM 4.08, 3.8.0, 3.4.3.1 and 9.1.2.

Usage Radio resource allocation.Call setup.Ladder: TCH assignment successful, TCH assignmentfail-recovered to SDCCH, handover (Intra-cell) successful,handover (Intra-cell) fail-recovered, handover (Intra-cell) fail-lost.

Basis Cell.

Type Counter.


MA_COMPLETE_FROM_MS Chapter 4: Cell statistics

MA_COMPLETE_FROM_MS

Description

The MA_COMPLETE_FROM_MS statistic tracks the number of AssignmentComplete messages received from MSs.

PeggingThis statistic pegs when the BSS receives an Assignment Complete message from the MS.

AnalysisThis statistic can be used for trend analysis.

Reference GSM 12.04, 4.2.1, B.2.1.15

Usage Originated call and service/connection request.Quality of service: Call set-up.Network planning.Ladder: TCH assignment successful.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application MA_COMPLETE_TO_MSC

MA_COMPLETE_TO_MSC

Description

{4322} The MA_COMPLETE_TO_MSC statistic tracks the number of successful assignmentcompletions for each channel and speech version.


0 PM_FR Counts the number of full rate assignmentrequests forwarded from the MS to the MSC.

1 PM_EFR Counts the number of enhanced full rateassignment requests forwarded from the MSto the MSC.

2 PM_AMR_FR Counts the number of Adaptive Multi-ratefull rate assignment requests forwarded fromthe MS to the MSC.

3 PM_AMR_HR Counts the number of Adaptive Multi-ratehalf rate assignment requests forwardedfrom the MS to the MSC.

4 PM_SIGNALLING Counts the number of SDCCH channelassignment requests forwarded from the MSto the MSC.

5 PM_DATA Counts the number of data assignmentrequests forwarded from the MS to the MSC.

{22064} When the Half Rate feature is unrestricted, the MA_COMPLETE_TO_MSC bintable introduces bin procedure PM_GSM_HR as shown:


6 PM_GSM_HR Counts the number of GSM half rateassignment requests forwarded from the MSto the MSC.

Pegging

This statistic pegs when the Assignment Complete message from the MS is forwarded on to the MSC.


MA_COMPLETE_TO_MSC Chapter 4: Cell statistics

Analysis

{4322} This statistic can be used for trend analysis of successful assignment completionsper channel type and speech version.

Reference GSM 08.08,12.04, 4.2.1, B.2.1.15

Usage Originated call and service/connection request.Quality of service: Call set-up.Network planning.Ladder: TCH assignment successful.

Basis Cell.

Type {4322} Counter array statistic.


Maintenance Information: GSM Statistics Application MA_FAIL_FROM_MS

MA_FAIL_FROM_MS

Description

The MA_FAIL_FROM_MS statistic tracks the number of Assignment Failure messagesreceived from MSs. An Assignment Failure message can be received at call setup (trafficchannel assignment) and at intra cell handovers.

PeggingThis statistic pegs when the BSS receives an Assignment Failure message from the MS. If the MS detects alower layer failure on the new channels before the Assignment Complete message has been sent:

• It deactivates the new channels.

• Reactivates the old channels.

• Reconnects any TCHs.

• Triggers establishment of the main signalling link.

• It then sends the Assignment Failure message on the main DCCH. This statisticpegs for channel assignment failures at intra-cell handovers for new calls andchannel assignment failures at handover.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number ofassignment failures for MSs that are acceptable in normal system operations.

If the specified threshold is exceeded, the 23. CELL: Mobile assignment failure from MS- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.2.1.3 and 3.2.2.5.GSM 12.07, 3.0.2, 2.8.6.c.GSM 4.08, 3.8.0, 3.4.3.3 and 9.1.4.

Usage Radio resource allocation.Quality of service monitoring: Call setup.Fault finding.Ladder: TCH assignment fail-recovered to SDCCH, handover(Intra-cell) fail-recovered.

Basis Cell.

Type Counter.

Alarm Warning.


MA_REQ_FROM_MSC Chapter 4: Cell statistics

MA_REQ_FROM_MSC

Description

The MA_REQ_FROM_MSC statistic tracks the number of times the MSC asked the BSS toallocate radio resources. The MSC sends the BSS an Assignment request message containingdetails of the type of resource required. The type of resource is based on the MSC analysisof the call control information received from the MS.

{4322} The bins are:


0 PM_FR Counts the number of full rate assignment requestsfrom the MSC.

1 PM_EFR Counts the number of enhanced full rate assignmentrequests from the MSC.

2 PM_AMR_FR Counts the number of Adaptive Multi-rate full rateassignment requests from the MSC.

3 PM_AMR_HR Counts the number of Adaptive Multi-rate half rateassignment requests from the MSC.

4 PM_SIGNALLING Counts the number of SDCCH channel assignmentrequests from the MSC.

5 PM_DATA Counts the number of data assignment requestsfrom the MSC.

When the Half Rate feature is unrestricted, the MA_REQ_FROM_MSC bin tableintroduces bin procedure PM_GSM_HR as shown:


6 PM_GSM_HR Counts the number of GSM half rate assignmentrequests from the MSC.

PeggingThis statistic pegs the radio resource request for each preferred speech version made to a BSS by the MSC.


Maintenance Information: GSM Statistics Application MA_REQ_FROM_MSC

AnalysisThis statistic can be used for trend analysis of MSC request to the BSS to allocate radio resources.


Usage Radio resource allocation.Quality of service monitoring: Call setup.Network planning.Ladder: TCH assignment successful, TCH assignmentfail-recovered to SDCCH, TCH assignment blocked.

Basis Cell.



MA_CMD_TO_MS_BLKD Chapter 4: Cell statistics

MA_CMD_TO_MS_BLKD

Description

TheMA_CMD_TO_MS_BLKD statistic tracks the number of times an assignment request from theMSC could not be processed (assignment command could not be generated and sent to the mobilestation) as there were no traffic channels available at the cell due to congestion.

PeggingThis statistic is pegged by the BSS when the MSC requests the BSS to allocate radio resourceto an MS, and the BSS finds it has no channels available to allocate. The pegging of thisstatistic indicates no channels were available in the currently allocated cell. It is indicated by anAssignment Failure message with cause: No radio resource available.

If queueing is enabled the statistic is pegged when the BSS queueing related timer bss_t11 expires. If the BSSassignment_successful timer is set shorter than the BSS bssmap_t11 timer then this statistic will not be pegged.It is recommended that the assignment_successful timer be always set greater than the bssmap_t11 timer.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of times trafficchannels that may be congested due to a lack of radio resources that are acceptable in normal system operations.

If the specified threshold is exceeded, the 2. CELL: Mobile assign command to MS blocked(no channel available) - PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.


Usage Radio resource allocation.Quality of service monitoring: Call setup and handover.Fault finding.Network planning.Optimization.Ladder: TCH assignment blocked.

Basis Cell.

Type Counter.

Alarm Minor.


Maintenance Information: GSM Statistics Application MS_ACCESS_BY_TYPE

MS_ACCESS_BY_TYPE

Description

The MS_ACCESS_BY_TYPE statistic tracks the number of system accesses by the various typesof MSs. The type of MS is included in the MS Classmark 3 information.

This statistic may be enabled only if the Multiband feature is unrestricted and enabled for the cell.

Bin MS Type Description

0 MS_PGSM_ONLY Base GSM band only.

1 MS_DCS1800_ONLY DCS1800 band only.

2 MS_PCS1900_ONLY PCS1900 band only.

3 MS_PGSM_EGSM Base and extended GSM bands.

4 MS_PGSM_DCS1800 Base GSM and DCS1800 bands.

5 MS_PGSM_EGSM_DCS1800 Base GSM, extended GSM, and DCS1800 bands.

6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.

7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, and PCS1900 bands.

PeggingThe MS_ACCESS_BY_TYPE statistic is pegged by RRSM after the sending of the initial layer3 information by the MS, on receipt of the classmark of the MS. It can also be pegged if the MSsends a CLASSMARK CHANGE message whilst in dedicated mode.

AnalysisThis statistic can be used for trend analysis of system accesses by MS type.

Usage Quality of Service monitoring.Network planning.

Basis Cell.

Type Counter array.


MS_TCH_USAGE_BY_TYPE Chapter 4: Cell statistics

MS_TCH_USAGE_BY_TYPE

Description

The MS_TCH_USAGE_BY_TYPE statistic tracks the length of time spent on TCHs by thevarious types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.For example, if MS_TCH_USAGE_BY_TYPE = 31, the call duration was 3.1 minutes or 186seconds). The type of MS is included in the MS Classmark 3 information.

This statistic may only be enabled if the Multiband feature is unrestricted and enabled for the cell.

Bin MS Type Description

0 MS_PGSM_ONLY Base GSM band only.

1 MS_DCS1800_ONLY DCS1800 band only.

2 MS_PCS1900_ONLY PCS1900 band only.

3 MS_PGSM_EGSM Base and extended GSM bands.

4 MS_PGSM_DCS1800 Base GSM and DCS1800 bands.

5 MS_PGSM_EGSM_DCS1800 Base GSM, extended GSM, and DCS1800 bands.

6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.

7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, and PCS1900 bands.

PeggingEach bin is updated by the cell resource manager when the duration for an active channel is recorded. A totalduration is calculated which is the sum for all channels usage time by MSs in a given cell.

AnalysisThis statistic can be used for trend analysis of active channel usage. This information can beused to identify problems before they can affect service.

Usage Service accessibility.Network planning.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application MS_TCH_USAGE_BY_TYPE_PCS

MS_TCH_USAGE_BY_TYPE_PCS

Description

The MS_TCH_USAGE_BY_TYPE_PCS statistic tracks the length of time spent on TCHs by thevarious types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.For example, if MS_TCH_USAGE_BY_TYPE_PCS = 31, the call duration was 3.1 minutes or 186seconds). The type of MS is included in the MS Classmark 3 information.

This statistic may only be enabled if either the PCS1900 or GSM850 frequency band is allowedon the BSS and the Multiband feature is unrestricted and enabled for the cell.

Bin Description

0 GSM850 only capable mobiles.

1 DCS1800-PCS1900 capable mobiles.

2 PGSM-DCS1800-PCS1900 capable mobiles.

3 PGSM-EGSM-DCS1800-PCS1900 capable mobiles.

4 PGSM-GSM850 capable mobiles.

5 PGSM-EGSM-GSM850 capable mobiles.

6 GSM850-DCS1800 capable mobiles.

7 PGSM-GSM850-DCS1800 capable mobiles.

8 PGSM-EGSM-GSM850-DCS1800 capable mobiles.

9 GSM850-PCS1900 capable mobiles.

10 PGSM-GSM850-PCS1900 capable mobiles.

11 PGSM-EGSM-GSM850-PCS1900 capable mobiles.

12 GSM850-PCS1900-DCS1800 capable mobiles.

13 PGSM-GSM850-PCS1900-DCS1800 capable mobiles.

14 PGSM-EGSM-GSM850-PCS1900-DCS1800 capable mobiles.

PeggingEach bin is updated by the cell resource manager when the duration for an active channel is recorded. A totalduration is calculated which is the sum for all channels usage time by MSs in a given cell.


MS_TCH_USAGE_BY_TYPE_PCS Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of active channel usage. This information can beused to identify problems before they can affect service.

Usage Service accessibility.Network planning.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application MT_LCS_ON_SDCCH

MT_LCS_ON_SDCCH

Description

This statistic counts the number of mobile-terminated SDCCH sessions for Location Services.

The statistic has been introduced to allow the Call Setup Success Rate key statistic (see Chapter17) to work following the introduction of the Location Services feature.

PeggingThis statistic is pegged each time there is an MT LMU on an SDCCH.

It is also pegged for a MT call when any LCS transaction occurs while the MS is on an SDCCH.Any of the following messages received over the A-interface are considered LCS transactioninitiations: BSSLAP TA Request, BSSLAP MS Position Command, BSSMAP Perform LocationRequest (only applies in the case of a BSS based SMLC).

Reference GSM 03.71 v7.4.0.

Usage Fault finding.

Basis Cell.

Type Counter.


NUM_EMERG_ACCESS Chapter 4: Cell statistics

NUM_EMERG_ACCESS

Description

The NUM_EMERG_ACCESS statistic tracks the number of emergency calls that access the system.

PeggingThis statistic pegs after the receipt of an emergency RACH.

AnalysisThis statistic can be used for trend analysis of emergency call accesses.

Usage Quality of Service monitoring.Network planning.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application NUM_EMERG_REJECTED

NUM_EMERG_REJECTED

Description

The NUM_EMERG_REJECTED statistic tracks the number of times an emergency callaccesses the system and has to be immediately rejected because there are no resources andanother call cannot be pre-empted to allow it access.

PeggingThis statistic pegs the number of emergency calls that are rejected because all channels wereoccupied by other emergency or high priority calls.

AnalysisThis statistic can be used for trend analysis of emergency call accesses that failed because allchannels were occupied by other emergency or high priority calls.

Usage Quality of Service.Network planning.

Basis Cell.

Type Counter.


NUM_EMERG_TCH_KILL Chapter 4: Cell statistics

NUM_EMERG_TCH_KILL

Description

The NUM_EMERG_TCH_KILL statistic tracks the number of times a call is lost due to emergencycall pre-emption and not to other factors, such as RF losses.

The active channel with the lowest priority is the one that releases a TCH. Additionally,emergency calls are not pre-empted by other emergency calls.

PeggingThis statistic pegs the number of active calls that are terminated in order to make a TCH available foran emergency call. This situation arises if all TCHs are occupied and an emergency access requires achannel. This statistic pegs only if the emergency pre-emption feature is enabled.

AnalysisThis statistic can be used for trend analysis of the number of times that calls are lostdue to emergency call pre-emption only.


Basis Cell

Type Counter.


Maintenance Information: GSM Statistics Application NUM_EMERG_TERM_SDCCH

NUM_EMERG_TERM_SDCCH

Description

The NUM_EMERG_TERM_SDCCH statistic tracks the number of emergency accessesterminated after SDCCH congestion. Used to indicate that an emergency call was allocatedan SDCCH but could not be allocated a TCH.

PeggingThis statistic pegs each time an emergency call is assigned to an SDCCH but must be terminatedbecause no TCHs are available to complete the call. This statistic is pegged regardless ofthe status of the emergency preemption feature.

AnalysisThis statistic can be used for trend analysis of the number of times that emergencyaccesses are terminated after SDCCH congestion.


Basis Cell.

Type Counter.


OK_ACC_PROC Chapter 4: Cell statistics

OK_ACC_PROC

Description

The OK_ACC_PROC tracks successful accesses by procedure. A total count ofall successful accesses is also maintained.


0 CM_SERV_REQ_CALL Number of MS requests for originating service.

1 CM_SERV_REQ_SMS Number of MS requests for SMS service.

2 CM_SERV_REQ_SUPP Number of MS requests for supplementary services.

3 CM_SERV_REQ_EMERG Number of MS requests for emergency call service.

4 CM_REESTABLISH Number of failed MS requests for service in whichthe call recovered to the original cell.

5 LOCATION_UPDATE Number of MS location update requests.

6 IMSI_DETACH Number of received IMSI detach messages.

7 PAGE_RESPONSE Number of MS page request responses.

8 LOC_FLW_ON_REQ_SMS Location Update follow-on request- SMS.

9 LOC_FLW_ON_REQ_NORM Location Update follow-on request- Normal.

10 LOCATION _SERVICES Number of Location Measurement Unit (LMU)service requests for location services.

LOCATION_SERVICES is stored in column cm_lcs_request of the OMC database.

PeggingThis statistic pegs the total number of successful results per procedure including location services.


Maintenance Information: GSM Statistics Application OK_ACC_PROC

AnalysisThis statistic can be used for trend analysis of the number of successful accesses by procedure.

Reference GSM 12.04, 4.21, B.3.1.2.GSM 4.08, 4.12, 3.15, 3.3.2.2, 4.4.1, 4.4.4.1, 4.5.1.1, 4.5.1.1,4.5.1.6, 5.5.4, 7.3.1, 9.2.9, 9.2.12, 9.2.15, and 9.45.

Usage Radio resource allocation.Quality of service monitoring: Call setup.Network planning.Ladder: Immediate assignment successful.Key Statistics: RF_LOSS_RATE, SDCCH_MEAN_HOLD-ING_TIME, SDCCH_MEAN_ARRIVAL_RATE,SDCCH_RF_LOSS_RATE.

Basis Cell.

Type Counter array.


OK_ACC_PROC_SUC_RACH Chapter 4: Cell statistics

OK_ACC_PROC_SUC_RACH

Description

The OK_ACC_PROC_SUC_RACH statistic tracks successful Channel Requestmessages on the RACH of a cell.

This message is used by the MS to request allocation of a dedicated channel (to be used as a SDCCH)by the network, in response to a paging message (incoming call) from the network or as a result ofan outgoing call/supplementary short message service dialled from the MS.

PeggingThis statistic pegs what it determines to be a valid Channel Request (RACH). This does notnecessarily result in a seizure attempt of an SDCCH.

AnalysisThis statistic can be used for trend analysis of the number of successful channel requests on the RACH of a cell.

Reference GSM 4.08, 3.8.0, 3.3.1. 3.3.2.2, 4.5.1.6, 5.5.4, 9.1.8 and 9.2.4.GSM 12.04, 3.1.0, B.1.2.1.

Usage Radio resource allocation. Ladder: Immediate assignmentsuccessful, Immediate assignment blocked, Immediate assignmentfailure.

Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application OUT_HO_CAUSE_ATMPT

OUT_HO_CAUSE_ATMPT

Description

The OUT_HO_CAUSE_ATMPT statistic tracks the number of handover attempts per cell per cause.The handover attempts include cases involving outgoing inter-cell handovers.


0 UPQUAL Number of times an outgoing inter-cell handover isattempted due to the Uplink signal quality in sourcecell.

1 UPLEVEL Number of times an outgoing inter-cell handover isattempted due to the Uplink signal level in sourcecell.

2 DOWNQUAL Number of times an outgoing inter-cell handoveris attempted due to the Downlink signal quality insource cell.

3 DOWNLEVEL Number of times an outgoing inter-cell handoveris attempted due to the Downlink signal level insource cell.

4 DISTANCE Number of times an outgoing inter-cell handoveris attempted due to a weakening signal strengthto/from MS because of the distance from signalsource.

5 UPINTERF Number of times an outgoing inter-cell handoveris attempted due to the Uplink signal interferencein source cell.

6 DOWNINTERF Number of times an outgoing inter-cell handover isattempted due to the Downlink signal interferencein source cell.

7 POWERBDGT Number of times an outgoing inter-cell handover isattempted due to the power budget assessment ofsignal strength in the source cell.

8 CONGESTION Number of times an outgoing inter-cell handover isattempted due to traffic channel (TCH) congestionin the source cell.

9 ADJ_CHAN_INTF Number of times an outgoing inter-cell handover isattempted due to adjacent channel interference.

10 BAND_RE_ASSIGN Number of times an outgoing inter-cell handover isattempted due to band reassignment in source cell.

11 BAND_HANDOVER Number of times an outgoing inter-cell handover isattempted due to band handover.


OUT_HO_CAUSE_ATMPT Chapter 4: Cell statistics

When a specific bin is included in descriptions or formulae in this manual, the convention used forthe presentation of the statistic and the bin identification will beOUT_HO_CAUSE_ATMPT[binname]. An example of this convention is OUT_HO_CAUSE_ATMPT[UPQUAL].

PeggingThis statistic pegs the total number of handover attempts out of a specific cell and the causefor each attempt. This statistic is pegged at the source cell.

AnalysisThis statistic can be used for trend analysis of the number of handover attempts per cell per cause.

Reference GSM 12.04, 4.2.1, B.1.1.11

Usage Handover.Quality of service.Network planning.Ladder: Intra-BSS handover.Optimization.Fault finding.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO

OUT_INTER_BSS_HO

Description

The OUT_INTER_BSS_HO statistic tracks a range of handover actions associated with outgoinginter-BSS handovers. A total value for this statistic is not meaningful and is not displayed.


0 OUT_INTER_BSS_REQ_TO_MSC Number of outgoing inter-BSS handover requeststo the MSC.

1 OUT_INTER_BSS_HO_ATMPT Number of assignment commands sent to MSduring an inter-BSS handover.

2 OUT_INTER_BSS_HO_SUC Number of successful inter-BSS handovers.

3 OUT_INTER_BSS_HO_LOSTMS Number of failed intra-BSS handovers in which theMS also failed to recover to the original BSS.This statistic is not currently pegged.

4 OUT_INTER_BSS_HO_RETURN Number of failed inter-BSS handovers in which theMS recovered to the original BSS/channel.

5 OUT_INTER_BSS_EQUIP_FAIL Number of attempted inter-BSS handover failuresdue to equipment failure.

6 OUT_INTER_BSS_HO_CLEARED Number of outgoing inter-BSS handovers aborteddue to call clearing. This scenario corresponds tothe receipt of a Clear Command, SCCP Released,or Release Done (internal message) during thehandover procedure.

PeggingOUT_INTER_BSS_REQ_TO_MSC is pegged each time a handover required message is sent to the MSC.

OUT_INTER_BSS_HO_ATMPT is pegged when the handover command is forwarded to the MS.

OUT_INTER_BSS_HO_SUC is pegged when a clear command message is received.

OUT_INTER_BSS_HO_LOSTMS is pegged if a clear command is not received from theMSC and no handover failure message is received either.

OUT_INTER_BSS_HO_RETURN is pegged each time an unsuccessful handover message is received.

OUT_INTER_BSS_EQUIP_FAIL is pegged if the MS returns a cause of equipmentfailure in the handover failure message.

OUT_INTER_BSS_HO_CLEARED is pegged when a call is cleared down during an inter-BSS handover.


OUT_INTER_BSS_HO Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of inter-BSS handovers on a per handover scenario basis.

Reference GSM 8.08, 3.9.2, 3.1.5.3.1 and 3.2.1.11. GSM 4.08, 3.8.0, 9.1.16and 3.4.4.4.GSM 3.1.5.1.1 and 3.2.1.9.GSM 12.04, 3.2.0, B.1.1.8.GSM 3.1.9.3 and 3.2.1.21.Metrica.


Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO

OUT_INTRA_BSS_HO

Description

The OUT_INTRA_BSS_HO statistic tracks a range of handover actions associated with outgoingintra-BSS handovers. A total value for this statistic is not meaningful and is not displayed.


0 OUT_INTRA_BSS_HO_REQ Number of times an intra-BSS HandoverRecognized message is received. This messageis sent when the system recognizes a handover isneeded.

1 OUT_INTRA_BSS_HO_PRI_BLK Number of times an intra-BSS handover to theprimary target cell was blocked.

2 OUT_INTRA_BSS_HO_ATMPT Number of assignment commands sent to MSduring an intra-BSS handover.

3 OUT_INTRA_BSS_HO_SUC Number of successful intra-BSS handovers.

4 OUT_INTRA_BSS_HO_LOSTMS Number of failed intra-BSS handovers in which theMS also failed to recover to the original BSS.

5 OUT_INTRA_BSS_HO_RETURN Number of failed intra-BSS handovers in which theMS recovered to the original BSS/channel.

6 OUT_INTRA_BSS_EQUIP_FAIL Number of attempted intra-BSS handover failuresdue to equipment failure.

7 OUT_INTRA_BSS_HO_CLEARED Number of outgoing intra-BSS handovers aborteddue to call clearing. This scenario corresponds tothe receipt of a Clear Command, SCCP Released,or Release Done (internal message) during thehandover procedure.

PeggingOUT_INTRA_BSS_HO_REQ is pegged each time an intra-BSS handover message is received.

OUT_INTRA_BSS_HO_PRI_BLK is pegged when resources not available message is received.

OUT_INTRA_BSS_HO_ATMPT is pegged when the initiate handover message is sent.

OUT_INTRA_BSS_HO_SUC is pegged when a handover performed message is sent.

OUT_INTRA_BSS_HO_LOSTMS is pegged if the MS fails to return to the originalchannel during a handover attempt.

OUT_INTRA_BSS_HO_RETURN is pegged when an unsuccessful handover message is received.

OUT_INTRA_BSS_EQUIP_FAIL is pegged when an assignment failure message containsan equipment failure cause or KSW/highway fault.


OUT_INTRA_BSS_HO Chapter 4: Cell statistics

OUT_INTRA_BSS_HO_CLEARED is pegged when a call is cleared down during an intra-BSS handover.

AnalysisThis statistic can be used for trend analysis of intra-BSS handovers on a per (handover) scenario basis.

Reference GSM 4.08, 3.8.0, 3.4.4.4.GSM 8.08, 3.9.2, 3.2.1.16 and 3.2.1.20.GSM 4.08, 3.8.0, 3.4.4.4 & 7.3.6 and 9.1.16.GSM 8.08, 3.9.2, 3.1.5.3.2 and 3.2.1.16.GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.1.1.GSM 4.08, 3.8.0, 3.4.4.GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.3.1.GSM12.04, 3.2.0, B.1.1.9.GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.2.1 and 3.2.1.12 & 3.2.1.25.Metrica.


Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_MSC

PAGE_REQ_FROM_MSC

Description

The PAGE_REQ_FROM_MSC statistic tracks the number of paging requests received from the MSC.

This message is sent by the network when attempting to locate the MS. Each Page messagerefers to only one MS. The BSS in turn transmits a paging message which may includeidentities for more than one MS (see ACCESS_PER_PCH).

PeggingThis statistic pegs the number of Paging messages received from the MSC by the BSS. This statistic ispegged when a Paging message is received pertaining to the cell in which the MS is paged.

AnalysisThis statistic can be used for trend analysis of the number of paging requests received from the MSC.

Reference GSM 4.08, 3.8.0, 3.3.2.1.GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Usage Quality of service monitoring: Paging analysis.

Basis Cell.

Type Counter.


PAGING_REQUESTS Chapter 4: Cell statistics

PAGING_REQUESTS

Description

This statistic accounts for any message making use of a PCH block. This statistic is similar toPCH_Q_PAGE_DISCARD except the messages are sent, not discarded. This statistic is obtained bymeasuring the number of paging requests received from the network for transmission on the PCH.

The bins are:


0 PAGING_REQS_TOT Number of Paging requests received to betransmitted on the PCH.

1 PAGING_REQS_CS Number of Paging requests received to betransmitted on the CS .

2 PAGING_REQS_PS Number of Paging requests received to betransmitted on the PS.

PeggingThis statistic pegs every multiframe for each message going over a paging block (PCH).

AnalysisThis statistic can be used for trend analysis of the number of paging requests received.

Reference Reference Digital cellular telecommunications systems (phase 2+)Version 7.0.0 Jan 2000 ETSI.

Usage Quality of service monitoring: Paging analysis.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application PCH_AGCH_Q_LENGTH

PCH_AGCH_Q_LENGTH

Description

The PCH_AGCH_Q_LENGTH statistic tracks the mean number of messagesreported in the PCH-AGCH queue.

The statistic is modified to support Circuit Switched (CS) pages only.

PeggingThis statistic pegs once per paging multiframe, by summing the total number of messages in the pagingqueue. At the end of the interval, the mean number of messages are calculated and reported.

AnalysisThe 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.

Reference GSM 12.04, 4.2.1, B.2.1.1

Usage Quality of service: Paging analysis.Optimization.Network planning.

Basis Cell.

Type Gauge.

Alarm Minor.


PCH_Q_PAGE_DISCARD Chapter 4: Cell statistics

PCH_Q_PAGE_DISCARD

Description

The PCH_Q_PAGE_DISCARD statistic tracks the number of paging messages discardedfrom the PCH queue before they could be transmitted.

A page may be discarded from the queue for the following reasons: queue overflow, priorityinsertion causing an overflow, and an in_queue timer expiry. The only cause for discardingpages in the Motorola BSS is queue overflow.

The statistic is modified to count both Circuit Switched (CS) and Packet Switch (PS) pages.

The bins are:

• CS pages discarded.

• PS pages discarded.

This statistic is obtained by measuring the number of Paging requests, which are discardedfrom the PCH queue before they could be transmitted. Pages can be discarded from the queues(assuming queuing is in operation) for a number of reasons, including queue overflow, priorityinsertion in the queue causing an overflow and in-queue timer expiry.

PeggingThis statistic pegs each time a page from the MSC is overwritten while in the queue.

The statistic also pegs for CS and PS pages as well as the assignments which theBSS was going to send over the PCH.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of paging messagesthat may be discarded from the PCH queue that are acceptable in normal system operations.

Reference GSM 12.04, 4.2.1, B.2.1.8


Basis Cell.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application PPCH_Q_PAGE_DISCARD

PPCH_Q_PAGE_DISCARD

{3723}

Description

The PPCH_Q_PAGE_DISCARD statistic tracks the number of Packet Paging Request messagesdiscarded from the PPCH queue before they could be transmitted.

A page may be discarded from the queue for the following reasons: queue overflow, priorityinsertion causing an overflow, and an in_queue timer expiry. The only cause for discardingpages in the Motorola BSS is queue overflow.

The bins are:

Bin Description

0 CS pages discarded.

1 PS pages discarded.

PeggingThis statistic pegs each time a Packet Paging Request is discarded from the PPCH queue.

Reference GSM 12.04, 4.2.1, B.2.1.8


Basis Cell.

Type Counter array.


RF_LOSSES_SD Chapter 4: Cell statistics

RF_LOSSES_SD

Description

The RF_LOSSES_SD statistic tracks the number of calls lost while using a SDCCH. If a TCHis reconfigured as a SDCCH, only the SDCCH statistics are configured.

PeggingThis statistic pegs the number of calls that were terminated because of RF problems. Thisstatistic will only peg for lost calls after the call has been established. This statistic will not bepegged when the CHAN_REQ_MS_FAIL statistic is pegged.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of lostcalls while using a SDCCH that are acceptable in normal system operations.

If the specified threshold is exceeded, the 0. CELL: Radio frequency losses while using anSDCCH - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling atthe OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.04, 3.1.0, B.1.1.5.GSM 4.08, 3.8.0, 3.5.2 and 9.1.27a and 10.5.2.19.

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.Installation and commissioning.Key statistic: RF_LOSS_RATE, SDCCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application RF_LOSSES_TCH

RF_LOSSES_TCH

Description

The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate TCH.

RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a pertimeslot level. The OMC-R rolls the information up to the cell level and refers tothis information as RF_LOSSES_TCH_ROLL.NOTE

Pegging

This statistic pegs the number of full rate and half rate calls that were terminated because ofRF problems. It is composed of calls lost while using a TCH. If a TCH is reconfigured asan SDCCH, only the SDCCH statistics are configured.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum number of lostcalls while using a TCH that are acceptable in normal system operations.

Reference GSM 12.04, 3.1.0, B.1.1.5.GSM 4.08, 3.8.0, 3.5.2, 9.1.27a and 10.5.2.19.

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.Installation and commissioning.Key Statistic: RF_LOSS_RATE, TCH_RF_LOSS_RATE.

Basis Timeslot.

Type Counter.

Alarm Major.


RF_LOSSES_TCH Chapter 4: Cell statistics

RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hoppingenvironment, this statistic may not be useful at channel level; therefore, roll to cell level.


Maintenance Information: GSM Statistics Application SDCCH_CONGESTION

SDCCH_CONGESTION

Description

The SDCCH_CONGESTION statistic tracks the amount of time that no SDCCHchannel was available in a cell.

PeggingThis statistic records the sum of the duration of periods when all the SDCCH channels in a cell werebusy. The statistic also collects the mean, maximum, and minimum time of SDCCH congestion. Ifa TCH is reconfigured as an SDCCH, only the SDCCH statistics are recorded.

Although the mean, maximum and minimum values are collected for this statistic, they canonly be viewed through the MMI using the disp_stats command.

AnalysisThis statistic can be used for trend analysis of the length of time during whichSDCCH channels were not available.

Reference GSM 12.04, 3.1.0, B.1.3.5.

Usage RF loss.Congestion.Quality of service monitoring.Network planning.Optimization.

Basis Cell.




SECOND_ASSIGN_ATMPT Chapter 4: Cell statistics

SECOND_ASSIGN_ATMPT

Description

The SECOND_ASSIGN_ATMPT statistic tracks the number of times the network initiated a secondassignment procedure on receipt of an Assignment Failure message from the MS.

PeggingThe BSS only attempts (initiates) a second assignment procedure on receipt of an AssignmentFailure message if the per BSS element second_asgnmnt is set.

Reference None.

Usage Congestion.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application SECOND_ASSIGN_SUC

SECOND_ASSIGN_SUC

Description

The SECOND_ASSIGN_SUC statistic tracks the number of times that a second assignment procedure initiatedby the network is successfully completed, upon receipt of an Assignment Complete message from the MS.

PeggingThe BSS only attempts (initiates) a second assignment procedure on receipt of an AssignmentFailure message if the per BSS element second_asgnmnt is set.

Reference None.

Usage Congestion.

Basis Cell.

Type Counter.


SMS_INIT_ON_SDCCH Chapter 4: Cell statistics

SMS_INIT_ON_SDCCH

Description

The SMS_INIT_ON_SDCCH statistic tracks how many Short Message Service(SMS) transactions occurred on a cell.

This statistic can be used to keep track of the number of times a Service Access Point (SAPI3) connection iscreated, a SMS requires a logical SAPI3 connection. Additionally, the statistic can be used to determinehow SDCCHs are being used (for example, for SMS as opposed to location update).

PeggingThis statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.

AnalysisThis statistic can be used for trend analysis of how many SMS transactions occurred on a cell.

Usage Originated call and service/connection request.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application SMS_INIT_ON_SDCCH_HO_IN

SMS_INIT_ON_SDCCH_HO_IN

Description

The SMS_INIT_ON_SDCCH_HO_IN statistic tracks how many Service Access Point (SAP13) connectionsare established over an SDCCH for Short Message Service (SMS) transactions during incoming handovers .

PeggingThis statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.

AnalysisThis statistic can be used for trend analysis of how many SAP13 connections occurred on a cell.


Basis Cell.

Type Counter.


SMS_INIT_ON_TCH Chapter 4: Cell statistics

SMS_INIT_ON_TCH

Description

The SMS_INIT_ON_TCH statistic tracks how many Short Message Service (SMS)transactions occurred on a cell related to a TCH.

This statistic can be used to keep track of the number of times a Service Access Point (SAPI3) connection iscreated, a SMS requires a logical SAPI3 connection. Additionally, the statistic can be used to determinehow TCHs are being utilized (for example, for SMS as opposed to normal voice traffic).

PeggingThis statistic is incremented upon successful SAPI3 connection related to a TCH.

AnalysisThis statistic can be used for trend analysis of how many SMS transactions occurred on a cell related to a TCH.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application SMS_NO_BCAST_MSG

SMS_NO_BCAST_MSG

Description

The SMS_NO_BCAST_MSG statistic tracks the number of times that a message hasbeen broadcast on a per cell basis.

PeggingThis statistic pegs each time a message is broadcast on the CBCH.

AnalysisThis statistic can be used for trend analysis of how many times a message has been broadcast on a per cell basis.

Usage Fault finding.

Basis Cell.

Type Counter.


TCH_CONGESTION Chapter 4: Cell statistics

TCH_CONGESTION

Description

The TCH_CONGESTION statistic indicates the amount of time that no {22064} fullrate TCH channels were available in that cell.

The TCH_CONGESTION statistic will only be used for outer zone resources when {22064}full rate TCH congestion is being measured for Concentric Cells.

A congestion (or blocking) state occurs when all {22064} full rate channels available to trafficwithin a cell (the number may vary over time due to failure or maintenance actions) are busy,where busy means unavailable for allocation to a new call attempt.

Pegging

This statistic pegs the sum of the duration of periods when all {22064} full rate TCHs were busy.

The statistic also reports the mean, maximum and minimum time of {22064} full rate TCH congestion. If a{22064} full rate TCH is configured as an SDCCH only the SDCCH statistics will be configured.

Reference GSM 12.04, 3.1.0, B.1.1.12


Basis Cell.



Maintenance Information: GSM Statistics Application TCH_CONG_INNER_ZONE

TCH_CONG_INNER_ZONE

Description

The TCH_CONG_INNER_ZONE statistic tracks the total length of time in which all of the{22064} full rate TCHs in the inner zone of a concentric cell are busy. The Concentric Cell optionmust be enabled for this statistic to be enabled, disabled, or displayed.

PeggingThe timer for this statistic is started when all TCHs belonging to {22064} full rate TCHs in the innerzone are busy. The timer is stopped when an inner zone {22064} full rate TCH is freed.

AnalysisThis statistic can be used for trend analysis of the length of time in which all of the {22064}full rate TCHs in the inner zone of a concentric cell are busy.

Reference None.

Usage Network planning.

Basis Cell.

Type Duration.


TCH_DELAY Chapter 4: Cell statistics

TCH_DELAY

Description

The TCH_DELAY statistic tracks the mean delay and the statistical distribution of the delay between anassignment request or handover request and a TCH being allocated for each cell on the BSS.

As more calls (in proportion to the total number of calls) are queued, the mean delay will be longer. Queueingis only done if the assignment or Handover Request indicates that queueing is allowed for that request. Thisstatistic will measure the queueing delay effectively. It is possible to have assignments and handovers for whichthere is no delay in resource allocation. These no-delay assignments are included in the mean delay statistic.

PeggingA timer is started when the request is queued and stopped when the request is allocated.

AnalysisThis statistic can be used for trend analysis of the queueing delay for a traffic channel being allocated to a cell.

Reference GSM 12.04, 3.1.0, B.1.1.3.GSM 3.01, 3.1.1, 4.1.GSM 8.08, 3.9.2, 3.1.17.GSM 4.08, 3.8.0, 5.2.1.1.10 and 5.2.2.8.

Usage Quality of service monitoring: Queueing delay.Network planning.Optimization.

Basis Cell.

Type Normal distribution.


Maintenance Information: GSM Statistics Application TCH_Q_LENGTH

TCH_Q_LENGTH

Description

The TCH_Q_LENGTH statistic tracks the arithmetic mean of the number of queued TCHassignment procedures. Queueing is done due to the Call Queueing feature, EmergencyCall Pre-emption, EGSM, and Directed Retry.

PeggingThis measurement is obtained by sampling the TCH queue length and reporting the current length. The meanTCH queue length includes the number of queued assignment and external handover requests.

AnalysisThis statistic can be used for trend analysis of the number of queued TCH assignment procedures.

Reference GSM 12.04, 4.2.1, B.2.1.15

Usage Quality of service: Network accessibility.Network planning.Optimization.

Basis Cell.



TCH_Q_REMOVED Chapter 4: Cell statistics

TCH_Q_REMOVED

Description

The TCH_Q_REMOVED statistic tracks when a queued call is assigned to a Traffic Channel (TCH).


0 ASSIGNMENT_RESOURCE_REQ Number of times an assignment resource isrequested.

1 HO_REQ Number of times a handover is requested.

2 ASSIGNMENT_RESOURCE_REQ_IN-NER_Z

Number of times an assignment resource isrequested in the inner zone.

3 HO_REQ_INNER_Z Number of times a handover is requested in theinner zone.

PeggingThese bins are pegged upon removal of either an assignment request or handover request from the TCH queue.

AnalysisThis statistic can be used for trend analysis of the number of queued TCH assignment procedures.

Reference None.

Usage Quality of service: Network accessibility.Network planning.Optimization.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application TCH_USAGE

TCH_USAGE

Description

The TCH_USAGE statistic gives an indication of the total amount of traffic carried by the cell. Active meansconnected (capable of transmitting circuit mode user data) and activated, for example, used as a DCCH.

The TCH_USAGE statistic is used only for outer zone resources when TCH usageis being measured for Concentric Cells.

The TCH_USAGE statistic measures only the usage of normal range channels in Extended Range Cells.

Both TCH_USAGE and BUSY_TCH include the guard timer value. This is a counter value.The sum equals the amount of time in milliseconds the TCH was busy, kept by internal timers.Therefore, when the interval expires, TCH usage may not be reported until the next interval. Exercisecaution if using this value over short interval periods. For example:

• Interval 0 starts.

• TCH 0 starts call - internal timer starts.

• TCH 1 starts call - internal timer starts.

• TCH 0 ends call - internal timer stops.

• TCH_USAGE counter incremented by time.

• Difference for TCH 0.

• Interval 0 expires.

The value reported for the interval will only include the call for TCH0.

• Interval 1 starts.

• TCH 1 ends a call - internal timer stopped.

• TCH_USAGE counter incremented by time.

• Difference for TCH 1.

PeggingThis statistic is the sum of the time that each TCH was active with a call for all TCHs on the cell. Ifa TCH is reconfigured as an SDCCH, only the SDCCH statistics will be configured.


TCH_USAGE Chapter 4: Cell statistics

AnalysisThis statistic can be used for trend analysis of the total amount of traffic carried by the cell.

Reference GSM 4.08, 3.8.0, 3.1.4.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application TCH_USAGE_EXT_RANGE

TCH_USAGE_EXT_RANGE

Description

The TCH_USAGE_EXT_RANGE statistic tracks the number of extended range traffic channels in use.

This statistic may only be enabled if the Extended Range Cell feature is unrestricted and enabled for the cell.

PeggingThis statistic pegs each time an extended range traffic channel is used.

AnalysisThis statistic can be used for trend analysis of the number of extended range traffic channels in use.

Reference None.


Basis Cell.

Type Counter.


TCH_USAGE_INNER_ZONE Chapter 4: Cell statistics

TCH_USAGE_INNER_ZONE

Description

The TCH_USAGE_INNER_ZONE statistic tracks the usage of TCHs belonging to carriersin the inner zone of a concentric cell. The Concentric Cell option must be enabled forthis statistic to be enabled, disabled, or displayed.

The TCH_USAGE statistic is used only for outer zone resources when the Concen-tric Cells feature is unrestricted.

PeggingThis statistic pegs when a TCH belonging to a carrier in the inner zone is used.

AnalysisThis statistic can be used for trend analysis of the usage of TCHs belonging to carriersin the inner zone of a concentric cell.

Reference None.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application TOTAL_CALLS

TOTAL_CALLS

Description

The TOTAL_CALLS statistic tracks the total number of calls originated for each cell on the BSS.

PeggingThis statistic indicates the number of circuit oriented calls that are originated in the cell. It ispegged only once per connection at the time of the first successful TCH assignment procedure.Subsequent channel changes, for example voice to data, are not counted.

This statistic does not necessarily peg all successful calls. It only pegs calls that have beenassigned to the TCH. For example, if the call fails to send a Direct Transfer Application Part(DTAP) Connect Acknowledge, it still looks successful to the base.

This statistic is not pegged on the short message service

AnalysisThis statistic can be used for trend analysis of the total number of calls originated for each cell on the BSS.

Reference GSM 4.08, 3.8.0, 5.2.

Usage Originated call and service/connection request.Quality of service monitoring : Call setup.Network planning.Ladder: TCH assignment successful.Key Statistics: RF_LOSS_RATE, TCH_MEAN_HOLD-ING_TIME, TCH_MEAN_ARRIVAL_RATE,TCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.


ZONE_CHANGE_ATMPT Chapter 4: Cell statistics

ZONE_CHANGE_ATMPT

Description

The ZONE_CHANGE_ATMPT statistic tracks attempts of each type of concentric cell specific handover.The Concentric Cell option must be enabled for this statistic to be enabled, disabled, or displayed.


0 INNER_TO_OUTER_ZONE Number of handover attempts from inner zone toouter zone.

1 OUTER_TO_INNER_ZONE Number of handover attempts from outer zone toinner zone.

2 INTRA_ZONE Number of intra-zone handover attempts.

3 TCH_ASSIGN_TO_INNER_ZONE Number of TCH assignment attempts to inner zonecells.

4 IN_INTER_CELL_HO_TO_IN_ZONE Number of internal inter-cell handover attempts toinner zone.

PeggingEach bin is pegged when a corresponding concentric cell handover is attempted.

AnalysisThis statistic can be used for trend analysis of the attempts of each type of concentric cell specific handover.

Reference None.


Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application ZONE_CHANGE_SUC

ZONE_CHANGE_SUC

Description

The ZONE_CHANGE_SUC statistic tracks each type of successful Concentric Cell specific handover. TheConcentric Cell option must be enabled for this statistic to be enabled, disabled, or displayed.


0 INNER_TO_OUTER_ZONE Number of successful handovers from inner zoneto outer zone.

1 OUTER_TO_INNER_ZONE Number of successful handovers from outer zoneto inner zone.

2 INTRA_ZONE Number of successful intra-zone handovers.

3 TCH_ASSIGN_TO_INNER_ZONE Number of successful TCH assignments to innerzone cells.

4 IN_INTER_CELL_HO_TO_IN_ZONE Number of successful internal inter-cell handoversto inner zone.

PeggingEach bin is pegged when a corresponding concentric cell handover is successful.

AnalysisThis statistic can be used for trend analysis of each type of successful concentric cell specific handover.

Reference None.


Basis Cell.

Type Counter array.


ZONE_CHANGE_SUC Chapter 4: Cell statistics



Chapter

5Neighbour statistics

When the BSS is configured to control inter-cell handovers, four of the handover statistics maybe used to track handovers. These neighbour statistics provide the destination cell of an outgoinghandover or the origination cell of an incoming handover.

Each of the neighbour statistics keep track of handover information for a pair of source and neighbour cells.

Neighbour statistics are described in "Introduction to neighbour statistics" on page 5-2.


Introduction to neighbour statistics Chapter 5: Neighbour statistics

Introduction to neighbour statistics

The following terms are used in the description of neighbour cells:

• Source cell - the cell in which a handover is initiated. Each source cell mayhave up to 32 target (neighbour) cells.

• Target cell - the neighbour cell into which the MS may be handed over. There is no limiton the number of source cells that may handover calls to a target cell.

The following limitations apply to neighbour statistics:

• Each neighbour statistic can be enabled for a maximum of 16 cells in a BSS. The cellsfor which each of the statistics are enabled do not have to be the same.

When the copy_cell command is used to copy a cell for which one or more of theneighbour statistics is enabled, all of the statistics for the cell created by the copy_cellcommand will be disabled. The individual statistics for the new cell will have to beenabled individually including the neighbour statistics.

• IN_INTRA_BSS_NC_ATMPT and IN_INTRA_BSS_NC_SUC statistics are incrementedin the target cell and can only be pegged for up to 32 source cells.

• OUT_HO_NC_CAUSE_ATMPT and OUT_HO_NC_SUC statistics are incrementedin the source cell and can only be pegged for up to 32 target cells.

• If the BSS is configured to have the MSC control intra-BSS handovers, the incomingper cell statistics are affected, and may not be used to track handovers.

Outgoing neighbour cell statistics

Outgoing neighbour statistics track the number of attempted and successful handovers from asource cell into a neighbour cell. The outgoing neighbour statistics are:

• "OUT_HO_NC_CAUSE_ATMPT" on page 5-10.

• "OUT_HO_NC_SUC" on page 5-12.


Maintenance Information: GSM Statistics Application Introduction to neighbour statistics

Example of tracked statisticsIn this example, cell_0 has 32 neighbours (cell_1 through cell_32), and theOUT_HO_NC_CAUSE_ATMPT statistic is enabled at cell_0.

The BSS tracks the following types of intra-BSS handover attempts:

• Originating in cell_0 that hand into cell_1.


• .

• .


Example showing effects of the del_neighbor commandIf the del_neighbor command is used to delete one of the neighbour cells of a source cell,only the statistics for the remaining neighbour cells are pegged.

In this example, cell_0 has 32 neighbours (cell_1 through cell_32), and theOUT_HO_NC_CAUSE_ATMPTstatistic is enabled at cell_0. The del_neighbor command is used to delete cell_32 as a neighbour cell of cell_0.

The BSS will track intra-BSS handover attempts:

• originating in cell_0 that hand into cell_1


• .

• .


Example showing effects of the add_neighbor commandIf the del_neighbor command is used to delete one of the neighbour cells of a source cell, onlythe statistics for the remaining neighbour cells will be pegged.

In this example, cell_0 has 31 neighbours (cell_1 through cell_31), and theOUT_HO_NC_CAUSE_ATMPTstatistic is enabled at cell_0. The add_neighbor command is used to add cell_32 as a neighbour cell of cell_0.



• originating in cell_0 that hand into cell_2.

• .

• .




Incoming neighbour statistics

Incoming neighbour statistics track the number of attempted and successful handovers into a neighbourcell from a source cell. Handovers are tracked for only 32 cells for each neighbour cell, even if aneighbour cell has more than 32 source cells. The incoming neighbour statistics are:

• "IN_INTRA_BSS_NC_ATMPT" on page 5-8.

• "IN_INTRA_BSS_NC_SUC" on page 5-9.

Choosing source cellsAn algorithm chooses which source cells to track for the incoming neighbour statistics. Thesource cells are chosen with the following priority:

1. Reciprocal neighbours are chosen. A reciprocal neighbour occurs when both thesource cell and the target cell have each other as a neighbour.

2. Each cell is sequentially checked, starting at 0 (local cell ID), until a sourcewhich has not already been selected is found.

Effect of the del_neighbor or add_neighbor commandsWhen neighbour cells are added or deleted from a cell in which the incoming neighbourstatistics are enabled, the following checks are performed:

1. If the cell is already tracking 32 source cells, no changes are made.

2. If the cell is not tracking 32 source cells, a check is done to see if new ones can be tracked.

3. If new source cells can be added, reciprocal neighbours are added first, followed bynon-reciprocal neighbours, which are chosen by sequentially looking through the database.

Example of tracked statisticsIn this example, the BSS has 90 cells (cell_0 through cell_89), cell_1 through cell_10 have cell_0 asa neighbour, and the IN_INTRA_BSS_NC_ATMPT statistic is enabled at cell_0.


• that hand into cell_0 originating from cell_1


• .

• .




Example of when there are more than 32 neighbour cellsIn this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 as neighbours. Cell_1 throughcell_50 each have cell_0 as a neighbour. The incoming neighbour statistics are enabled at cell_0. Whilecell_1 through cell_50 can hand into cell_0, the BSS can only track 32 of these cells.

The reciprocal neighbours (cell_1 through cell_16) are chosen for tracking first. Becauseanother 16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50are not tracked because the 32 cell limit has been reached.

Example of when a reciprocal neighbour is addedIn this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 as neighbours. Cell_1 throughcell_50 each have cell_0 as a neighbour. The incoming neighbour statistics are enabled at cell_0. Whilecell_1 through cell_50 can hand into cell_0, the BSS can only track 32 of these cells.

The reciprocal neighbours (cell_1 through cell_16) are chosen for tracking first. Becauseanother 16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50are tracked because the 32 cell limit has been reached.

A new neighbour (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbourpair. The cells being tracked will not be changed just because a new reciprocal neighbour pair hasbeen added because it is already at the maximum number of cells it can track.

Example of when a neighbour cell is deletedIn this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 as neighbours. Cell_1 throughcell_50 each have cell_0 as a neighbour. The incoming neighbour statistics are enabled at cell_0. Whilecell_1 through cell_50 can hand into cell_0, the BSS can only track 32 of these cells.

The reciprocal neighbours (cell_1 through cell_16) are chosen for tracking first. Becauseanother 16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50are tracked because the 32 cell limit has been reached.

A new neighbour (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbourpair. The cells being tracked will not be changed just because a new reciprocal neighbour pair hasbeen added because it is already at the maximum number of cells it can track.

Neighbour cell_0 is deleted from cell_18. When this cell is deleted, cell_0 only tracks 31 source cells.Because 32 cells may be tracked, a search is done to see if there are any reciprocal neighbours.

Since cell_45 was added creating a reciprocal pair, cell_45 would now be tracked. If a reciprocal pair had notbeen available, cell_33 would have been chosen as the next non-reciprocal source not already tracked.

Examples of notation and initial situation

The following are examples of typical handover situations to show how neighbour cell statistics are pegged.

NotationAn example of the notation used in the examples is:



stat name peg count source cell_B and target cell_A

IN_INTRA_BSS_NC_ATMPT: 0 (B-A)

Initial situationTable 5-1 shows an example of three cells: cell_A, cell_B, and cell_C. All four neighbour cell statisticsare enabled at cell_A. For this example, all cells are internal to the same BSS.

cell_C

cell_Bcell_A

Table 5-1 Neighbour cell statistics pegged

Neighbour status Initial peg count Peg sourcetarget

cell_B is a neighbour of cell_A andcell_A is a neighbour of cell_Bcell_C is a neighbour of cell_A andcell_A is a neighbour of cell_C

IN_INTRA_BSS_NC_ATMPTIN_INTRA_BSS_NC_SUCIN_INTRA_BSS_NC_ATMPTIN_INTRA_BSS_NC_SUCOUT_HO_NC_CAUSE_ATMPTOUT_HO_NC_SUCOUT_HO_NC_CAUSE_ATMPTOUT_HO_NC_SUC

0 (B-A)0 (B-A)0 (C-A)0 (C-A)0 (A-B)0 (A-B)0 (A-C)0 (A-C)

Successful handover (B-A)AMS that originated in cell_B performs a successful handover into cell_A. The following statistics are updated:





Successful handover (A-C)The MS, which is now in cell_A, performs another successful handover into cell_C.The following statistics are updated.



Unsuccessful handover (C-A)The MS in cell_C attempts a handover into cell_A, but is unsuccessful. The following statistics are updated.




IN_INTRA_BSS_NC_ATMPT Chapter 5: Neighbour statistics

IN_INTRA_BSS_NC_ATMPT

Description

The IN_INTRA_BSS_NC_ATMPT statistic tracks the number of intra-BSS handover attemptsinto a cell and the location of the cell originating the handover attempt. Allows study of thehandover performance of a specific cell for each of its source cells. Provides information todetermine quality of service and to support optimization.

This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic isenabled, a maximum of 32 source cells can be tracked.

PeggingThis statistic is pegged in the target cell against a specific source cell. This is done each timethe SSM decides to perform an intra-BSS handover where the target is an internal neighbourwhich is placed first in the Handover Recognized message.

AnalysisThis statistic can be used for trend analysis of the number of handover attempts into a celland the location of the cells originating the handover attempts.

Reference GSM 12.04, 4.0.0, B.2.2.1GSM 4.08, 8.08, 8.58

Usage Handover.Quality of Service.Network Planning.Optimization.Fault Finding.

Basis NCell (Neighbour cell).

Type Counter.


Maintenance Information: GSM Statistics Application IN_INTRA_BSS_NC_SUC

IN_INTRA_BSS_NC_SUC

Description

The IN_INTRA_BSS_NC_SUC statistic tracks the successful incoming internalinter-cell handovers per originating cell.

This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic isenabled, a maximum of 32 source cells can be tracked.

PeggingThis statistic is pegged in the target cell upon notification of a successful intra-BSS handover from a specific cell.

AnalysisThis statistic can be used for trend analysis of incoming internal inter-cell handovers per originating cell.




Type Counter.


OUT_HO_NC_CAUSE_ATMPT Chapter 5: Neighbour statistics

OUT_HO_NC_CAUSE_ATMPT

Description

The OUT_HO_NC_CAUSE_ATMPT statistic tracks the number of handovers per neighbourper cause. This statistic can be enabled for a maximum of 16 cells. For each cell where thestatistic is enabled, a maximum of 32 target cells can be tracked.

This statistic provides information to determine quality of service and to support optimization. Allowsstudy of the handover performance of a specific cell for each of its neighbouring target cells.

Inter-band handovers are also tracked when the Multiband Handover feature is enabled.(Refer to the description for Bin 10, below.)


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.

PeggingThis statistic pegs the total number of handover attempts out of a specific cell, the location of the targetcell, and the cause for each attempt. This statistic is pegged at the source cell.


Maintenance Information: GSM Statistics Application OUT_HO_NC_CAUSE_ATMPT

AnalysisThis statistic can be used for trend analysis of handover attempts per neighbour on a per cause basis.

Reference GSM 12.04, 4.0.0, B.2.2.3GSM 4.08, 8.08, 8.58GSM 12.04, 4.2.1

Usage Handover.Quality of Service.Network Planning.Optimization.Fault Finding.Ladder: Intra-BSS handover.


Type Counter array.


OUT_HO_NC_SUC Chapter 5: Neighbour statistics

OUT_HO_NC_SUC

Description

The OUT_HO_NC_SUC statistic tracks the number of successful outgoing inter-cell handoversper target cell. This statistic can be enabled for a maximum of 16 cells. For each cell where thestatistic is enabled, a maximum of 32 target cells can be tracked.

PeggingThis statistic pegs the total number of successful handovers out of a specific cell and thelocation of the target cell for each successful handover.

AnalysisThis statistic can be used for trend analysis of handover performance of specific cellsfor each of its neighbouring target cells.




Type Counter.


Chapter

6Carrier and timeslot statistics

Carrier and timeslot statistics are captured from events occurring in a carrier. They are categorized intosubgroups, each of which are described in "Carrier and timeslot statistics subgroups" on page 6-2.


Carrier and timeslot statistics subgroups Chapter 6: Carrier and timeslot statistics

Carrier and timeslot statistics subgroups

Carrier and timeslot statistics are organized into the following major subgroups:

• "Downlink RXQUAL (BER)" on page 6-2.

• "Uplink RXQUAL (U_BER)" on page 6-2.

• "Link balance verification" on page 6-2.

• "BTS dynamic allocation" on page 6-3.

• "Timing advance" on page 6-3.

• "Miscellaneous" on page 6-3.

Downlink RXQUAL (BER)

Downlink receive quality statistics are used to track the Bit Error Rate (BER) of active channels.The statistic "BER" on page 6-6 is the only downlink RXQUAL statistic.

Uplink RXQUAL (U_BER)

Uplink receive quality statistics are used to track the Bit Error Rate (BER) of active channels. Thestatistic "U_BER" on page 6-23 is the only uplink RXQUAL statistic.

Link balance verification

Link balance verification statistics are used to track the link balance between air interface of theuplink and downlink path loss. The following are the link balance statistics:

• "CHAN_DL_TX_PWR_LVL" on page 6-8.

• "CHAN_UL_TX_PWR_LVL" on page 6-11.

• "PATH_BALANCE" on page 6-16.

• "UPLINK_PATH_LOSS" on page 6-25.


Maintenance Information: GSM Statistics Application Carrier and timeslot statistics subgroups

BTS dynamic allocation

BTS dynamic allocation statistics are used to track utilization of dynet channels. Thefollowing are the BTS dynamic allocation statistics:

• "ALLOC_SDCCH_CARR" on page 6-4.

• "ALLOC_TCH_CARR" on page 6-5.

Timing advance

The timing advance statistic "ROC" on page 6-22 is used to monitor the timing advance measurements.

Miscellaneous

Miscellaneous statistics are used to track several unrelated carrier and timeslot statistics.The following are the miscellaneous carrier statistics:

• "CHAN_REQ_MS_FAIL" on page 6-9.

• {4322}"FER_GSM_FR_EFR" on page 6-12.

• "INTF_ON_IDLE" on page 6-14.

• "RBER" on page 6-18.

• "RF_LOSSES_TCH" on page 6-20.


ALLOC_SDCCH_CARR Chapter 6: Carrier and timeslot statistics

ALLOC_SDCCH_CARR

Description

TheALLOC_SDCCH_CARR statistic is the sum of the number of SDCCHallocations per carrier within a cell.

PeggingThis statistic pegs each time an Immediate Assignment message is sent by the BSS. AnImmediate Assignment message will be sent upon:

• Successful handover on an SDCCH channel.

• Successful immediate assignment on an SDCCH channel.

This statistic pegs for reasons other than calls requiring a traffic channel, such as location updates.

AnalysisThis statistic can be used for trend analysis of SDCCH allocations and allows the calculationof the mean hold time of a SDCCH per carrier.

Reference GSM 12.04, 3.1.0, B.1.3.3.GSM 4.08, 3.8.0, 3.3.12, 3.4.3.1, 3.4.4.1, 9.1.2 to 9.1.4, 9.1.14 to9.1.19.

Usage RF loss.Congestion.Quality of service monitoring: Call set-up.Network planning.Ladder: Immediate assignment successful, Intra-cell handover,Inter-BSS handover, Connection establishment, Intra-BSShandover.

Basis Carrier.

Type Counter.



Maintenance Information: GSM Statistics Application ALLOC_TCH_CARR

ALLOC_TCH_CARR

Description

The ALLOC_TCH_CARR statistic provides the number of successful TCH allocations percarrier within a cell for both call originations and hand ins.

PeggingThis statistic pegs for successful TCH allocations per carrier within a cell as a resultof a call establishment or hand in attempt:

• Successful allocation due to call establishment including successfulallocations due to directed retries.


• Successful allocation due to inter-cell/intra-cell hand in.

• Successful allocation due to inter-BSS hand in.

This statistic is pegged before the transmission of the assignment/handover command to the MS and,therefore, does not take into account the success or failure of the assignment/hand in from an RF perspective.

AnalysisThis statistic can be used for trend analysis of TCH allocations and allows the calculationof the mean hold time of a TCH per carrier.

Usage Quality of service monitoring: Call setup.Network planning.Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cellhandover, Assignment to TCH.Key statistics: TCH_MEAN_ARRIVAL_RATE,TCH_MEAN_HOLDING_TIME, CELL_TCH_ALLOCA-TIONS, TCH_RF_LOSS_RATE.

Basis Carrier.

Type Counter.


BER Chapter 6: Carrier and timeslot statistics

BER

Description

The BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for activechannels. The bit error rate value corresponds to the RXQUAL downlink measurement reports.BER statistic measurements are reported only when the channel is active.

BER on SDCCH channels are affected by phantom RACHs. BER on TCHs are not affected. For acell with a non-combined BCCH configuration, there are no values presented on timeslot 0.

PeggingThe statistic pegs every 480 ms (corresponding to each SACCH multiframe).

UnitsThis statistic is reported using values 0 to 7 that are derived from the RXQUAL values:

RXQUAL BER (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 greater than 12.8

The bin ranges for this statistic may not be changed.


Maintenance Information: GSM Statistics Application BER

AnalysisThis statistic can be used for trend analysis of the BER for active channels.

Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.

Basis Timeslot.



CHAN_DL_TX_PWR_LVL Chapter 6: Carrier and timeslot statistics

CHAN_DL_TX_PWR_LVL

Description

The CHAN_DL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum BSS(downlink) transmit power level. The reported value is in dBm units.

PeggingThis statistic pegs every SACCH multiframe.

AnalysisThis statistic can be used for trend analysis of mean BSS transmit power levels.

Reference GSM 12.04, 4.2.1, B.2.1.28.

Usage Fault finding.Quality of service.

Basis Carrier.



Maintenance Information: GSM Statistics Application CHAN_REQ_MS_FAIL

CHAN_REQ_MS_FAIL

Description

The CHAN_REQ_MS_FAIL statistic tracks the number of times that the BSS times out while waiting for theMS to establish on the SDCCH that was assigned to it during the immediate assignment procedure.

An Immediate Assign message is sent to the MS on the Access Grant CHannel (AGCH)and a SDCCH allocated. When the MS does not reply with a SABM on that SDCCH, theallocated channel is relinquished, and the request forgotten.

This may be a normal occurrence on few occasions such as when the MS is moving out of range, theMS is failing, or the MS is switched off. However, frequent occurrences of this event within a shortperiod of time and/or geographically clustered may indicate a hardware failure.

CHAN_REQ_MS_FAIL is the BSS MMI name of the statistic kept by the BSS ona per timeslot level. The OMC-R rolls the information up to the cell level and refersto this information as CHAN_REQ_MS_FAIL_ROLL.

PeggingThis statistic pegs when theMS does not reply with Set Asynchronous BalancedMode (SABM) on the SDCCH.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of BSStimeouts while waiting for an MS to establish on the SDCCH assigned during the immediateassignment procedure that are acceptable in normal system operations.

If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCHfailed - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling atthe OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 4.08, 3.8.0, 3.3.1.4 and 9.1.17.

Usage Radio resource and allocation.Fault finding.Quality of service monitoring: Call setup.Ladder: Immediate assignment blocked.

Basis Timeslot.

Type Counter.

Alarm Minor.


CHAN_REQ_MS_FAIL Chapter 6: Carrier and timeslot statistics



Maintenance Information: GSM Statistics Application CHAN_UL_TX_PWR_LVL

CHAN_UL_TX_PWR_LVL

Description

The CHAN_UL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum MS (uplink)transmit power levels. The value is reported in dBm units.

PeggingThis statistic pegs every SACCH multiframe.

AnalysisThis statistic can be used for trend analysis of mean MS transmit power levels.

Reference GSM 12.04, 4.2.1, B.2.1.29.

Usage Fault finding.Quality of service.

Basis Carrier.



FER_GSM_FR_EFR Chapter 6: Carrier and timeslot statistics

FER_GSM_FR_EFR

{22064}

{4322} This statistic was previously named FER.

Description

The uplink FER_GSM_FR_EFR Quality statistic is derived from a ratio of successfullydecoded good speech frames against unsuccessfully decoded bad frames for non-AMR calls. Themeasurement 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 a FER_GSM_FR_EFR Quality number between 0 and 9.

For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,Table 6-1, this relates to an FER_GSM_FR_EFR Quality number of 2.

PeggingThis statistic pegs the uplink frame erasure rate for non_AMR calls for each carrier in a cell.

UnitsThe FER_GSM_FR_EFR is reported using values 0 to 9 as follows.

Table 6-1 FER_GSM_FR_EFR Quality number conversion

FER_GSM_FR_EFR Qualitynumber FER ratio (min:1 to max:1)

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


Maintenance Information: GSM Statistics Application FER_GSM_FR_EFR

Table 6-1 FER_GSM_FR_EFR Quality number conversion (Continued)

FER_GSM_FR_EFR Qualitynumber FER ratio (min:1 to max:1)

8 0.3333 to 0.3749

9 0.3750 to 1.0000

FER_GSM_FR_EFR Quality is measured on a timeslot basis for active channels afterdecoding de-interleaving and error correction. Data for this statistic is reported by firmwareto the RSS/HO software process where it is pegged.

The values of the bins are fixed and are not adjustable by the operator.

AnalysisThis statistic can be used for trend analysis for target optimization effects on cell/radios with regards to quality.

Reference None.

Usage Quality of service,Fault finding,RF loss,Congestion.

Basis Carrier.



INTF_ON_IDLE Chapter 6: Carrier and timeslot statistics

INTF_ON_IDLE

Description

The INTF_ON_IDLE statistic indicates the maximum, minimum, and mean interference levelsexperienced on idle channels as determined by the BSS.

The bin ranges may be changed using the chg_stat_prop command. The default bin rangesfor the INTF_ON_IDLE statistic are shown in Table 6-2.

Table 6-2 Default bin ranges for INTF_ON_IDLE

Bin Range

0 0 - 5

1 6 - 10

2 11 - 15

3 16 - 20

4 21 - 25

5 26 - 30

6 31 - 35

7 36 - 40

8 41 - 45

9 46 - 65

Table 6-3 provides an indication of the interference on a channel by recording measurements of receivedsignal strength taken when the channel is idle. This measurement parallels the activity of the channel selectionalgorithm of the Cell Resource Manager which uses the same data to rank idle channels, giving preferenceto the channels with a lower interference level. The measured signal level is mapped to an RXLEV valuebetween 0 and 63. Each RXLEV value corresponds to a dBm value, as shown in Table 6-3.

Table 6-3 Signal level

RXLEV value dBm level

0 less than -110 dBm

1 -110 dBm to -109 dBm

2 -109 dBm to -108 dBm

62 -49 dBm to -48 dBm

63 greater than -48 dBm


Maintenance Information: GSM Statistics Application INTF_ON_IDLE

PeggingThis statistic pegs every 480 ms.

AnalysisThis statistic can be used for trend analysis of interference levels experienced on idle channels.

Reference GSM 12.04, 3.2.0, B.1.1.13.GSM 5.08, 3.6.0, 8.1-8.5 and Appendix A.3.ii.

Usage RF loss and congestion.Quality of service monitoring.Network planning.Fault finding.

Basis Timeslot.



PATH_BALANCE Chapter 6: Carrier and timeslot statistics

PATH_BALANCE

Description

The PATH_BALANCE statistic tracks the maximum, minimum, and mean link balance onthe air interface between the uplink and downlink path loss.

The actual value for path_balance depends on the type of RF combining used.

PeggingThis statistic is pegged by the value calculated by the following equation:

path_balance = path loss + 110

where:

path loss = uplink path loss - downlink path loss

where:

uplink path loss = actual MS txpower - rxlev_ul

downlink path loss = actual BTS txpower - rxlev_dl

The rxlev_ul and rxlev_dl values reflect the latest reported value and are not averaged values.PATH_BALANCE is not pegged when either rxlev_ul or rxlev_dl is equal to 63 (-47 dBm).

The range of values for this statistic is 0 to 220 with a long term average of 110 with normal use. Adeviation of ±10 is acceptable, but this is to be understood as a practical guide and not as producttolerance. If the deviation is greater than ±10, the RF path should be checked.

If a low noise amplifier (LNA) is fitted, a deviation of -20 is possible.


Maintenance Information: GSM Statistics Application PATH_BALANCE

Typically, the path loss should be similar in both the uplink and downlink directions. When diversity gainis enabled, the path balance will be just below 110, indicating a lower uplink path loss.

Mismatch of Horizon and Horizon macro database and hardware.The path_balance statistic will be incorrect if the the Horizon and Horizonmacro cabinet and database aremismatched. The following table describes the two mismatch scenarios between the cabinet and database.

If... Then...

the Horizon cabinet is equipped with Horizonmacrodatabase, the path_balance statistic will beincorrect.

the SITE alarm 28 “data configuration and Horizonhardware mismatch" will be generatedoperatorsshould change either the hardware or the databaseaccordingly.Consult the manual, Maintenance Information:Alarm Handling At The OMC-R (68P02901W26).

the Horizonmacro cabinet is equipped with Horizondatabase, the path_balance statistic will beincorrect.

the SITE alarm 28 “data configuration and Horizonhardware mismatch" will be generated.operatorsshould change either the hardware or the databaseaccordingly.Consult the manual, Maintenance Information:Alarm Handling At The OMC-R (68P02901W26).

If the Horizonmacro booster unit is faulty or not present, the path_balance statistic isincorrect. Operators should disregard this statistic until the booster is replaced. Networkplanners should check with the OMC operator to determine if any Horizonmacroalarms (SITE alarms 25, 26 or 27) have been generated.

AnalysisThis statistic can be used for trend analysis of the link balance on the air interfacebetween the uplink and downlink path loss.

Reference None.

Usage Quality of service: Service integrity.Optimization.Fault finding.

Basis Carrier.


Unit dB.


RBER Chapter 6: Carrier and timeslot statistics

RBER

Description

The RBER (Residual Bit Error Rate) Quality statistic is derived from a ratio of number of bits inerror to total number of bits received, within error detected speech frames defined as good. Themeasurement 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 lookuptable, the ratio is converted to an RBER Quality number between 0 and 7.

RBER is supported only by MMI actions. It not reported to the OMC-R atthe end of the statistical interval period.

PeggingEvery 480 ms, during the SACCH multi-frame by the RSS/HO process.

UnitsThe RBER statistic is reported using values 0 to 7.

Table 6-4 RBER Quality number conversion

RBER Quality number RBER ratio (min:1 to max:1)

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 or greater

The bin ranges for this statistic are fixed and may not be altered by the operator.


Maintenance Information: GSM Statistics Application RBER


Reference None.

Usage Quality of service.Fault finding.RF loss.Congestion.

Basis Timeslot.



RF_LOSSES_TCH Chapter 6: Carrier and timeslot statistics

RF_LOSSES_TCH

Description

The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate TCH.

RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a pertimeslot level. The OMC-R rolls the information up to the cell level and refers tothis information as RF_LOSSES_TCH_ROLL.NOTE

Pegging

This statistic pegs the number of full rate and half rate calls that were terminated because ofRF problems. It is composed of calls lost while using a TCH. If a TCH is reconfigured asan SDCCH, only the SDCCH statistics are configured.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum number of lostcalls while using a TCH that are acceptable in normal system operations.

Reference GSM 12.04, 3.1.0, B.1.1.5.GSM 4.08, 3.8.0, 3.5.2, 9.1.27a and 10.5.2.19.

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.Installation and commissioning.Key Statistic: RF_LOSS_RATE, TCH_RF_LOSS_RATE.

Basis Timeslot.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application RF_LOSSES_TCH

RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hoppingenvironment, this statistic may not be useful at channel level; therefore, roll to cell level.


ROC Chapter 6: Carrier and timeslot statistics

ROC

Description

The ROC statistic tracks the maximum, minimum and mean Range Of Carrier between BSS and MSon a per carrier basis. The range of carrier value corresponds to the timing advance (TA) measurementreports. 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 toa maximum of 10 bins. The default bin ranges are shown in Table 6-5.

Table 6-5 Bin ranges for ROC

Bin TA Range

0 0 to 6

1 7 to 13

2 14 to 20

3 21 to 27

4 28 to 34

5 35 to 41

6 42 to 48

7 49 to 54

8 55 to 63

9 64 to 219

These bins are not displayed at the OMC but can be displayed at the MMI. To set and displaythe bin ranges refer to the chg_stat_prop and disp_stat_prop commands in Chapter 2.


Basis Carrier.



Maintenance Information: GSM Statistics Application U_BER

U_BER

Description

The U_BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for activechannels. The bit error rate value corresponds to the RXQUAL uplink measurement reports. U_BERstatistic measurements are reported only when the channel is active.

BER on SDCCH channels are affected by phantom RACHs. BER on TCHs are not affected. For acell with a non-combined BCCH configuration, there are no values presented on timeslot 0.


UnitsThis statistic is reported using values 0 to 7 that are derived from the RXQUAL values:

RXQUAL BER (min to max) Assumed

0 0 to 0.2 0.14

1 0.2 to 0.4 0.28

2 0.4 to 0.8 0.57

3 0.8 to 1.6 1.13

4 1.6 to 3.2 2.26

5 3.2 to 6.4 4.53

6 6.4 to 12.8 9.05

7 greater than 12.8 18.1

The bin ranges for this statistic may not be changed.


U_BER Chapter 6: Carrier and timeslot statistics

AnalysisThis statistic can be used to provide monitoring of uplink RXQUAL performance.

Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.

Basis Timeslot.



Maintenance Information: GSM Statistics Application UPLINK_PATH_LOSS

UPLINK_PATH_LOSS

Description

The UPLINK_PATH_LOSS statistic tracks the minimum, mean, and maximum uplinklosses on a per carrier basis. Reported values can be used to create a profile of the radio linkpropagation losses experienced by MSs served in the cell.

PeggingThis statistic is pegged every SACCH multiframe for each active call.

AnalysisThis statistic can be used for trend analysis of the uplink losses on a per carrier basis.

Reference None.

Usage RF Loss.Quality of Service.

Basis Carrier.



UPLINK_PATH_LOSS Chapter 6: Carrier and timeslot statistics



Chapter

7GPROC and DPROC statistics

GPROC and DPROC statistics track the utilization of the processing units found in varioushardware components in the BSS, for example GPROC and DPROC devices. In the GSMstatistics application, there is only one processor utilization statistic, CPU_USAGE. A fulldescription of this statistic is given in "CPU_USAGE" on page 7-2.


CPU_USAGE Chapter 7: GPROC and DPROC statistics

CPU_USAGE

Description

The CPU_USAGE statistic tracks CPU usage. Monitoring of CPU usage allows the operator to determineif the GPROC and DPROC devices at a particular site are being over, under, or properly utilized.

This statistic is updated from reports generated by the internal executive system, whichkeeps track of when CPU usage changes.

PeggingThis statistic records the maximum, minimum, and mean values of the short-term processor utilizationmeasurement (from which the 30-minute mean, statistic Mean Utilization, is calculated). This statisticis recorded for each GPROC and DPROC under the control of a BSS.

AnalysisThis statistic can be used for trend analysis of GPROC and DPROC utilization.

Reference GSM 12.07,3.0.2,4.3 bullet 1.

Usage Processor utilization.Network planning.Optimization.

Basis GPROC.



Chapter

8LMTL statistics

Location Services Message Transfer Link (LMTL) statistics are used to track events for the Location ServicesMessage Transfer Part (LMTP) of the ITU-TSS No. 7 protocol on the BSC to MSC interface. They arecategorized into subgroups, each of which are described in "LMTL statistics subgroups" on page 8-2.


LMTL statistics subgroups Chapter 8: LMTL statistics

LMTL statistics subgroups

LMTL statistics are organized into the following major subgroups:

• "LMTP C7 availablility" on page 8-2.

• "LMTP C7 performance" on page 8-2.

• "LMTP C7 utilization" on page 8-3.

LMTP C7 availablility

LMTP C7 availability statistics are used to track the duration of signalling link outages andinhibitions (local and remote) for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSCinterface. The following are the MTP C7 availability statistics:

• "LMTP_LINKFAIL" on page 8-10.

• "LMTP_LOCAL_BUSY" on page 8-11.

• "LMTP_LOCAL_MGT" on page 8-12.

• "LMTP_MGT_INHIBIT" on page 8-13.

• "LMTP_MGT_UNINHIBIT" on page 8-14.

• "LMTP_REMOTE_MGT" on page 8-19.

• "LMTP_REMOTE_PROC" on page 8-20.

• "LMTP_START_RPO" on page 8-30.

• "LMTP_STOP_RPO" on page 8-31.

• "LMTP_UNAVAILABLE" on page 8-33.

LMTP C7 performance

LMTP C7 performance statistics are used to track the different types of failure and recoverysituations for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. Thefollowing are the LMTP C7 performance statistics:

• "LMTP_CHANGEBACK" on page 8-6.

• "LMTP_CHANGEOVER" on page 8-7.

• "LMTP_LINK_INS" on page 8-9.

• "LMTP_NEG_ACKS" on page 8-17.


Maintenance Information: GSM Statistics Application LMTL statistics subgroups

• "LMTP_REMOTE_SL_CONGESTION" on page 8-26.

• "LMTP_RESTORATION" on page 8-21.

• "LMTP_SL_ACK" on page 8-24.

• "LMTP_SL_ALIGNMENT" on page 8-25.

• "LMTP_SL_ERROR_RATE" on page 8-27.

• "LMTP_SL_FAIL" on page 8-28.

• "LMTP_SL_FIBR" on page 8-29.

• "LMTP_SU_ERROR" on page 8-32.

LMTP C7 utilization

LMTP C7 utilization statistics are used to track the number of messages received, transmitted andretransmitted on signalling links and supply information on signalling link congestion for the LMTP of theITU-TSS No.7 protocol on the BSC to MSC interface. The following are the LMTP C7 utilization statistics:

• "LMTP_CONGESTION_LOST_MSU" on page 8-4.

• "LMTP_MSU_DISCARDED" on page 8-5.

• "LMTP_CONGESTION" on page 8-35.

• "LMTP_RE_TX" on page 8-18.

• "LMTP_MSU_RX" on page 8-15.

• "LMTP_MSU_TX" on page 8-16.

• "LMTP_SIB_RX" on page 8-34.

• "LMTP_SIB_TX" on page 8-36.

• "LMTP_SIF_SIO_RX" on page 8-22.

• "LMTP_SIF_SIO_TX" on page 8-23.

• "LMTP_LOCAL_SL_CONGESTION" on page 8-8.


LMTP_CONGESTION_LOST_MSU Chapter 8: LMTL statistics

LMTP_CONGESTION_LOST_MSU

Description

The LMTP_CONGESTION_LOST_MSU statistic tracks the number of times Message SignallingUnits (MSU) are being lost due to Lb-interface Signalling Link (SL) congestion.

PeggingThis statistic pegs for each congestion event on the Lb-interface which results in MSUs being lost.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of lostMSUs due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 11. LMTL: SL congestion events resulting in lossof MSUs - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.


Usage MTP C7 utilization.Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application LMTP_MSU_DISCARDED

LMTP_MSU_DISCARDED

Description

The LMTP_MSU_DISCARDED statistic tracks the number of MSUs discarded due toLb-interface Signalling Link (SL) congestion.

PeggingThis statistic pegs each time an MSU is discarded due to Lb-interface SL congestion.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of MSUs arebeing discarded due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 10. LMTL: MSUs discarded due to SL congestion- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.


Usage MTP C7 utilization.Network planning.Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


LMTP_CHANGEBACK Chapter 8: LMTL statistics

LMTP_CHANGEBACK

Description

The LMTP_CHANGEBACK statistic tracks the number of local automatic changebacksthat have been successfully completed.

PeggingThis statistic pegs when MTP traffic that has been changed over to an alternate SignallingLink (SL) is diverted back to the original SL.

AnalysisThis statistic can be used for trend analysis of automatic changebacks that have been successfully completed.


Usage MTP C7 performance.Fault finding.

Basis Lb SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application LMTP_CHANGEOVER

LMTP_CHANGEOVER

Description

The LMTP_CHANGEOVER statistic tracks the number of local automatic changeovers that havebeen successfully completed. This indicates MTP traffic is being transferred from an Lb interfaceSignalling Link (SL) that is going out of service to an alternate SL.

PeggingThis statistic pegs when MTP traffic is changed over to an alternate Lb interface SL.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of out of sequencemessages between a BSS and an SMLC that are acceptable in normal system operations.

If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.


LMTP_LOCAL_SL_CONGESTION Chapter 8: LMTL statistics

LMTP_LOCAL_SL_CONGESTION

Description

The LMTP_LOCAL_SL_CONGESTION statistic tracks once for each onset of congestionacross the Lb-interface Signalling Link (SL).

There are two types of congestion that may occur across an Lb interface SL: local congestion (thatis the MTP L2 of the BSS detects that the TX queue is full) and remote congestion (that is theBSS-based SMLC is congested). Both types of congestion may exist across an Lb-interface SL atone time; however, regardless of congestion type, the statistic is pegged only upon the entrance intothe congested state of the Lb-interface SL. Thus, if the Lb-interface SL is locally congested andremote congestion is detected, the statistic is not pegged. Likewise, if the Lb-interface SL is remotelycongested and local congestion is detected, the statistic is not pegged.

PeggingThe statistic pegs each time the Lb-interface SL goes into the congestion state at the local site.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number ofcongestion onsets that are acceptable in normal system operations.

If the specified threshold is exceeded, the 12. LMTL :SL Congestion Indications - PM alarm is generated.



Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application LMTP_LINK_INS

LMTP_LINK_INS

Description

The LMTP_LINK_INS statistic tracks the length of time that an Lb-interface SignallingLink (SL) is in the in-service state.

PeggingThe timer for this statistic is started when an SL is brought into service. The timer is stoppedwhen the Lb-interface SL is removed from service.

AnalysisThis statistic can be used for trend analysis of the utilization of in-service SLs.


Usage MTP C7 performance.

Basis Lb SS7_LINK.



LMTP_LINKFAIL Chapter 8: LMTL statistics

LMTP_LINKFAIL

Description

The LMTP_LINKFAIL statistic tracks the duration of the Lb-interface Signalling Link (SL) unavailabilitydue to SL failure. It records the total time a particular SL is out of service while trying to align to the SMLC.

PeggingThis statistic timer is started when the SL fails. It is stopped when the SL comes back into service.

AnalysisThis statistic can be used for analysis of SL unavailability due to SL failure.


Usage MTP C7 availability.Fault finding.

Basis Lb SS7_LINK.



Maintenance Information: GSM Statistics Application LMTP_LOCAL_BUSY

LMTP_LOCAL_BUSY

Description

The LMTP_LOCAL_BUSY statistic tracks the total time congestion is present on thelocal end of the Lb-interface Signalling Link (SL).

PeggingThis statistic is started when congestion is detected on an Lb-interface SL. The statisticis stopped when normal operation is resumed.

AnalysisThis statistic can be used for trend analysis on congestion durations on the local end of the SL.


Usage MTP C7 availability.Network planning.Fault finding.

Basis Lb SS7_LINK.



LMTP_LOCAL_MGT Chapter 8: LMTL statistics

LMTP_LOCAL_MGT

Description

The LMTP_LOCAL_MGT statistic tracks the total time that a local Lb-interface SignallingLink (SL) is inhibited due to local management actions.

PeggingThis statistic is started each time the SL is inhibited due to local management actions,and stopped when the link is enabled.

AnalysisThis statistic can be used for trend analysis on inhibited local SLs due to local management action.


Usage MTP C7 availability.

Basis Lb SS7_LINK.

Type Duration (total time).


Maintenance Information: GSM Statistics Application LMTP_MGT_INHIBIT

LMTP_MGT_INHIBIT

Description

The LMTP_MGT_INHIBIT statistic tracks the number of times the Lb-interfaceSignalling Link (SL) is inhibited by the operator.

PeggingThis statistic is started each time the Lb-interface SL is inhibited by the operator.

AnalysisThis statistic can be used for trend analysis on inhibited SLs using the shutdowncommand on the associated MTP link.



Basis Lb SS7_LINK.

Type Counter.


LMTP_MGT_UNINHIBIT Chapter 8: LMTL statistics

LMTP_MGT_UNINHIBIT

Description

The LMTP_MGT_UNINHIBIT statistic tracks the number of times the Lb-interfaceSignalling Link (SL) is uninhibited by the operator.

PeggingThis statistic is pegged each time the SL is uninhibited by the operator.

AnalysisThis statistic can be used for trend analysis on uninhibited SLs using the unlockcommand on the associated MTP link.



Basis Lb SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application LMTP_MSU_RX

LMTP_MSU_RX

Description

The LMTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)received on a Lb-interface signalling link.

PeggingThis statistic pegs each time MSUs are received over the Lb-interface signalling link.



Basis Lb SS7_LINK.

Type Counter.


LMTP_MSU_TX Chapter 8: LMTL statistics

LMTP_MSU_TX

Description

The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)transmitted on an Lb-interface signalling link.

PeggingThis statistic pegs each time MSUs are transmitted over the Lb-interface signalling link.



Basis Lb SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application LMTP_NEG_ACKS

LMTP_NEG_ACKS

Description

The LMTP_NEG_ACKS statistic tracks the number of out-of-sequence messages between a BSSand the BSS-based SMLC across the Lb-interface signalling link.

PeggingThis statistic pegs when the BSS detects out of order messages to the SMLC and requests retransmission.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of out of sequencemessages between a BSS and an SMLC that are acceptable in normal system operations.

If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


LMTP_RE_TX Chapter 8: LMTL statistics

LMTP_RE_TX

Description

The LMTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the SMLCbecause the SMLC has requested retransmission. This indicates how much the BSS and an SMLCare off in message sequencing by the number of octets retransmitted.

PeggingThis statistic peg the number of octets retransmitted by the BSS to the SMLC.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of octetretransmissions that are acceptable in normal system operations.

If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted - PMalarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application LMTP_REMOTE_MGT

LMTP_REMOTE_MGT

Description

The LMTP_REMOTE_MGT statistic tracks the total time an Lb-interface SignallingLink (SL) is remotely inhibited by the SMLC.

PeggingThis statistic pegs the duration of the Lb-interface SL inhibition due to remote management action.

AnalysisThis statistic can be used for trend analysis of remote management SL inhibition actions.



Basis Lb SS7_LINK.

Type Duration (total time in milliseconds (ms).


LMTP_REMOTE_PROC Chapter 8: LMTL statistics

LMTP_REMOTE_PROC

Description

The LMTP_REMOTE_PROC statistic tracks the time that a remote processor is out of service.

PeggingThis statistic pegs when a remote processor outage is identified, and stopped whenthe processor outage condition ceases.

AnalysisThis statistic can be used for trend analysis of remote processor outage occurrences in the BSS-based SMLC.



Basis Lb SS7_LINK.



Maintenance Information: GSM Statistics Application LMTP_RESTORATION

LMTP_RESTORATION

Description

The LMTP_RESTORATION statistic tracks the number of times user traffic is allowed on an Lb-interfaceSignalling Link (SL) that is in service and not inhibited. This statistic does not track recovery from link fail.

PeggingThis statistic pegs when the Lb-interface SL starts carrying user traffic. This happens when the Lb-interfaceSL comes into service, is uninhibited, or recovers from a remote processor outage.

AnalysisThis statistic can be used for trend analysis of used traffic being allowed on an SL.



Basis Lb SS7_LINK.

Type Counter.


LMTP_SIF_SIO_RX Chapter 8: LMTL statistics

LMTP_SIF_SIO_RX

Description

The LMTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or ServiceInformation Octets (SIO) that are received over an Lb-interface signalling link.

PeggingThis statistic pegs each time an SIF or SIO is received over an Lb-interface signalling link.



Basis Lb SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application LMTP_SIF_SIO_TX

LMTP_SIF_SIO_TX

Description

The LMTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or ServiceInformation Octets (SIO) that are transmitted over a signalling link by the BSC to the SMLC.

PeggingThis statistic pegs each time an SIF or SIO are transmitted over a signalling link by the BSC to the SMLC.



Basis Lb SS7_LINK.

Type Counter.


LMTP_SL_ACK Chapter 8: LMTL statistics

LMTP_SL_ACK

Description

The LMTP_SL_ACK statistic tracks the number of times that the link was lost due toan Lb-interface MTP layer 2 T7 timer expiry.

PeggingThis statistic pegs each time the link is lost due to a timer that expires when an acknowledgementfrom the BSS-based SMLC is not received.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number ofacknowledgements of MSUs not being received by the BSC that are acceptable in normal system operations.

If the specified threshold is exceeded, the 2. LMTL: SL failure - excessive delay of ACK- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application LMTP_SL_ALIGNMENT

LMTP_SL_ALIGNMENT

Description

The LMTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attemptsto align an out-of-service LMTL.

PeggingThis statistic pegs each time an out of service Signalling Link (SL) unsuccessfullytries to align with the Lb-interface.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of unsuccessfulattempts to align an out-of-service SL to the Lb-interface that are acceptable in normal system operations.

If the specified threshold is exceeded, the 5. LMTL: SL alignment failure - PM alarmis generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Minor.


LMTP_REMOTE_SL_CONGESTION Chapter 8: LMTL statistics

LMTP_REMOTE_SL_CONGESTION

Description

The LMTP_REMOTE_SL_CONGESTION statistic tracks the number of times the remotecongestion timer expires for the Lb-interface signalling link.

PeggingThis statistic pegs each time the remote congestion timer expires.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum numberof occurrences of excessive congestion duration at the remote Signalling Link (SL) thatare acceptable in normal system operations.

If the specified threshold is exceeded, the 4. LMTL: SL failure - excessive duration ofcongestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application LMTP_SL_ERROR_RATE

LMTP_SL_ERROR_RATE

Description

The LMTP_SL_ERROR_RATE statistic tracks the number of times that an Lb-interface Signalling Link(SL) is lost due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.

PeggingThis statistic pegs each time the Lb-interface SL is lost due to the SUERM timer expiration.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times an SL maybe lost due to SUERM timer expirations that are acceptable in normal system operations.

If the specified threshold is exceeded, the 3. LMTL: SL failure - excessive error rate- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.ITU-TSS Q.791 - (3.2 - 3.10).TU-TSS Q.703 - (102).


Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


LMTP_SL_FAIL Chapter 8: LMTL statistics

LMTP_SL_FAIL

Description

The LMTP_SL_FAIL statistic tracks the Lb-interface Signalling Link (SL) failure for allcauses except operator interaction through the MMI.

PeggingThis statistic is pegged when an Lb-interface SL fails for any reason except operatorinteraction through the MMI.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of SL failures, excludingthose caused by operator interaction with the MMI, that are acceptable in normal system operations.

If the specified threshold is exceeded, the 0. LMTL: SL failure - all reasons - PM alarmis generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application LMTP_SL_FIBR

LMTP_SL_FIBR

Description

The LMTP_SL_FIBR statistic tracks the number of out-of-sequence messages between a BSC and theBSS-based SMLC that result in an Lb-interface Signalling Link (SL) going out of service. This statisticis similar to the LMTP_NEG_ACKS statistic, but signals a more severe condition.

PeggingThis statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator Bit (FIB) causedby the de-synchronization of the Backward Sequence Number (BSN) and Forward Sequence Number (FSN).

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times an SL may belost due to the detection of an abnormal FIB that are acceptable in normal system operations.

If the specified threshold is exceeded, the 1. LMTL: SL failure - abnormal FIBR/BSNR- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Major.


LMTP_START_RPO Chapter 8: LMTL statistics

LMTP_START_RPO

Description

The LMTP_START_PRO statistic tracks the number of times a processor outageoccurs in the BSS-based SMLC.

PeggingThis statistic is pegged each time the BSS is notified that the BSS-based SMLC hasexperienced a processor outage.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of remoteprocessor outages that are acceptable in normal system operations.

If the specified threshold is exceeded, the 8. LMTL: Start of remote processor outage- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application LMTP_STOP_RPO

LMTP_STOP_RPO

Description

The LMTP_STOP_RPO statistic tracks the number of times a processor outagecondition has ceased in the BSS-based SMLC.

PeggingThis statistic pegs each time the remote processor outage stops.

AnalysisThis statistic can be used for trend analysis of remote processor outage condition is no longer present.



Basis Lb SS7_LINK.

Type Counter.


LMTP_SU_ERROR Chapter 8: LMTL statistics

LMTP_SU_ERROR

Description

The LMTP_SU_ERROR statistic tracks the number of times erroneous signal units arereceived on the Lb-interface Signalling Link (SL).

PeggingThis statistic pegs each time an erroneous signal unit is received on the Lb-interface SS7 SL.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times erroneoussignal units may be received on the SL that are acceptable in normal system operations.

If the specified threshold is exceeded, the 6. LMTL: Number of signal units in error- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application LMTP_UNAVAILABLE

LMTP_UNAVAILABLE

Description

The LMTP_UNAVAILABLE statistic tracks the total time an Lb-interface Signalling Link (SL)is out of service for all reasons including operator intervention.

PeggingThis statistic records the duration of Lb-interface SL unavailability for all reasons,including operator intervention through the MMI.

AnalysisThis statistic can be used for trend analysis of the duration of SL outages, includingthose caused by operator interaction.



Basis Lb SS7_LINK.



LMTP_SIB_RX Chapter 8: LMTL statistics

LMTP_SIB_RX

Description

The LMTP_SIB_RX statistic tracks the number of Status Indication Busy LSSU messagesreceived over an Lb-interface Signalling Link (SL).

PeggingThis statistic is pegged each time the BSS receives a Status Indication Busy (SIB) LSSUmessage across the Lb-interface signalling link.




Basis Lb SS7_Link.

Type Counter.


Maintenance Information: GSM Statistics Application LMTP_CONGESTION

LMTP_CONGESTION

Description

The LMTP_CONGESTION statistic tracks the time the Lb-interface Signalling Link (SL) is congested.

PeggingThe timer for this statistic is started when congestion is detected on an Lb interface signallinglink. The timer is stopped when normal operation is resumed.



Basis Lb SS7_Link.

Type Duration.


LMTP_SIB_TX Chapter 8: LMTL statistics

LMTP_SIB_TX

Description

The LMTP_SIB_TX statistic tracks the number of Status Indication Busy LSSU messagestransmitted over an Lb-interface Signalling Link (SL).

PeggingThis statistic is pegged each time the BSS transmits a Status Indication Busy (SIB) LSSUmessage across the Lb-interface signalling link.




Basis SS7_Link.

Type Counter.


Chapter

9BSS statistics for Location Servicessupport

BSS statistics for Location Services (LS) support are collected and used for the supported BSS LS. Existingcell connection establishment statistics as described in Chapter 4, "Cell statistics," are pegged for locationservices and specific LS events are captured using BSS LS statistics described in this chapter. Thesesubgroups are described in "BSS statistics for Location Services support subgroups" on page 9-2.


BSS statistics for Location Services support subgroups Chapter 9: BSS statistics for Location Services support

BSS statistics for Location Services supportsubgroups

BSS statistics for Location Services (LS) support are organized into the following subgroups:


• "Location service" on page 9-2.


Connection establishment statistics track access and channel request functions. The following statisticsare connection establishment statistics and are pegged for location services:

• "CHAN_REQ_CAUSE_ATMPT" on page 4-31.

• "OK_ACC_PROC" on page 4-82.

Location service

The following are specific location service statistics :

• "BSSLAP_ABORT_RCV" on page 9-4.

• "BSSLAP_ABORT_SENT" on page 9-5.

• "BSSLAP_MS_POS_CMD" on page 9-6

• "BSSLAP_MS_POS_RESP" on page 9-7

• "BSSLAP_REJ" on page 9-8

• "BSSLAP_RESET" on page 9-9

• "BSSLAP_TA_REQ" on page 9-10

• "BSSLAP_TA_RESP" on page 9-11

• "BSSLAP_TOA_REQ" on page 9-12

• "BSSMAP_CONLESS_INFO_RCV" on page 9-13

• "BSSMAP_CONLESS_INFO_SENT" on page 9-14

• "BSSMAP_PERF_LOC_ABORT_MSGS" on page 9-15

• "BSSMAP_PERF_LOC_REQ_MSGS" on page 9-16


Maintenance Information: GSM Statistics Application BSS statistics for Location Services support subgroups

• "BSSMAP_PERF_LOC_RESP_MSGS" on page 9-17

• "BSSMAPLE_CONLESS_INFO_RCV" on page 9-18

• "BSSMAPLE_CONLESS_INFO_SENT" on page 9-19

• "BSSMAPLE_PERF_LOC_ABORT_MSGS" on page 9-20

• "BSSMAPLE_PERF_LOC_REQ_MSGS" on page 9-21

• "BSSMAPLE_PERF_LOC_RESP_MSGS" on page 9-22


BSSLAP_ABORT_RCV Chapter 9: BSS statistics for Location Services support

BSSLAP_ABORT_RCV

Description

The BSSLAP_ABORT_RCV statistic tracks the number of BSSLAP abort messages received.

PeggingThis statistic pegs each time a BSSLAP abort message is received.

Reference GSM 03.71 v7.4.0, sect. 8.4.GSM 08.71 v7.2.0, sect. 2.2.7.


Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSLAP_ABORT_SENT

BSSLAP_ABORT_SENT

Description

The BSSLAP_ABORT_SENT statistic tracks the number of BSSLAP abort messages sent.

PeggingThis statistic pegs each time a BSSLAP abort message is sent.



Basis BSS.

Type Counter.


BSSLAP_MS_POS_CMD Chapter 9: BSS statistics for Location Services support

BSSLAP_MS_POS_CMD

Description

The BSSLAP_MS_POS_CMD statistic tracks the number of BSSLAP MS positioncommand messages received..

PeggingThis statistic pegs each time a BSSLAP MS position command message is received.

Reference GSM 03.71 v7.4.0, sect. 10.2, 10.3.GSM 08.71 v7.2.0, sect. 2.2.9.


Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSLAP_MS_POS_RESP

BSSLAP_MS_POS_RESP

Description

The BSSLAP_MS_POS_RESP statistic tracks the number of BSSLAPMS position responsemessages sent.

PeggingThis statistic pegs each time a BSSLAP MS position response message is sent.

Reference GSM 03.71 v7.4.0, sect. 10.2, 10.3.GSM 08.71 v7.2.0, sect. 2.2.10.


Basis BSS.

Type Counter.


BSSLAP_REJ Chapter 9: BSS statistics for Location Services support

BSSLAP_REJ

Description

The BSSLAP_REJ statistic tracks the number of BSSLAP reject messages sent.

PeggingThis statistic pegs each time a BSSLAP reject message is sent.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSLAP_RESET

BSSLAP_RESET

Description

The BSSLAP_RESET statistic tracks the number of BSSLAP reset messages sent.

PeggingThis statistic pegs each time a BSSLAP reset message is sent.



Basis BSS.

Type Counter.


BSSLAP_TA_REQ Chapter 9: BSS statistics for Location Services support

BSSLAP_TA_REQ

Description

The BSSLAP_TA_REQ statistic tracks the number of BSSLAP TA request messages received.

PeggingThis statistic pegs each time a BSSLAP TA request message is received.

Reference GSM 03.71 v7.4.0, sect. 8.2, 8.3, 8.4.GSM 08.71 v7.2.0, sect. 2.2.1.


Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSLAP_TA_RESP

BSSLAP_TA_RESP

Description

The BSSLAP_TA_RESP statistic tracks the number of BSSLAP TA response messages sent.

PeggingThis statistic pegs each time a BSSLAP TA response message is sent.

Reference GSM 03.71 v7.4.0, sect. 8.2, 8.3, 8.4.GSM 08.71 v7.2.0, sect. 2.2.2.


Basis BSS.

Type Counter.


BSSLAP_TOA_REQ Chapter 9: BSS statistics for Location Services support

BSSLAP_TOA_REQ

Description

The BSSLAP_TOA_REQ statistic tracks the number of BSSLAP TOA request messages received.

PeggingThis statistic pegs each time a BSSLAP TOA request message is received.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSMAP_CONLESS_INFO_RCV

BSSMAP_CONLESS_INFO_RCV

Description

The BSSMAP_CONLESS_INFO_RCV statistic tracks the number of BSSMAPconnectionless information messages received.

PeggingThis statistic pegs each time a BSSMAP connectionless information message is received.

Reference GSM 03.71 v7.4.0, sect. 7.10.


Basis BSS.

Type Counter.


BSSMAP_CONLESS_INFO_SENT Chapter 9: BSS statistics for Location Services support

BSSMAP_CONLESS_INFO_SENT

Description

The BSSMAP_CONLESS_INFO_SENT statistic tracks the number of BSSMAPconnectionless information messages sent.

PeggingThis statistic pegs each time a BSSMAP connectionless information message is sent.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSMAP_PERF_LOC_ABORT_MSGS

BSSMAP_PERF_LOC_ABORT_MSGS

Description

The BSSMAP_PERF_LOC_ABORT_MSGS statistic tracks the number of BSSMAP performlocation abort messages received on the A-interface.

PeggingThis statistic pegs each time a BSSMAP perform location abort message is received on the A-interface.

Reference GSM 03.71 v7.4.0, sect 7.11.


Basis BSS.

Type Counter.


BSSMAP_PERF_LOC_REQ_MSGS Chapter 9: BSS statistics for Location Services support

BSSMAP_PERF_LOC_REQ_MSGS

Description

The BSSMAP_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAP performlocation request messages received on the A-interface.

PeggingThis statistic pegs each time a BSSMAP perform location request message is received on A-interface.

Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.


Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSMAP_PERF_LOC_RESP_MSGS

BSSMAP_PERF_LOC_RESP_MSGS

Description

The BSSMAP_PERF_LOC_RESP_MSGS statistic tracks the number of BSSMAP performlocation response messages sent on A-interface.

PeggingThis statistic pegs each time a BSSMAP perform location response message is sent on A-interface.

Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.


Basis BSS.

Type Counter.


BSSMAPLE_CONLESS_INFO_RCV Chapter 9: BSS statistics for Location Services support

BSSMAPLE_CONLESS_INFO_RCV

Description

The BSSMAPLE_CONLESS_INFO_RCV statistic tracks the number of Lb-interfaceBSSMAP-LE connectionless information messages received.

PeggingThis statistic pegs each time a BSSMAP-LE connectionless information message is received.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSMAPLE_CONLESS_INFO_SENT

BSSMAPLE_CONLESS_INFO_SENT

Description

The BSSMAPLE_CONLESS_INFO_SENT statistic tracks the number of Lb-interfaceBSSMAP-LE connectionless information messages sent.

PeggingThis statistic pegs each time a BSSMAP-LE connectionless information message is sent.

Reference GSM 03.71 v7.4.0, sect. 7.8,


Basis BSS.

Type Counter.


BSSMAPLE_PERF_LOC_ABORT_MSGS Chapter 9: BSS statistics for Location Services support

BSSMAPLE_PERF_LOC_ABORT_MSGS

Description

The BSSMAPLE_PERF_LOC_ABORT_MSGS statistic tracks the number of BSSMAP-LEperform location abort messages sent on the Lb-interface.

PeggingThis statistic pegs each time a BSSMAP-LE perform location abort message is sent on Lb-interface.

Reference GSM 03.71 v7.4.0, sect 7.11GSM 09.31 v7.1.0, sect 9.3.


Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application BSSMAPLE_PERF_LOC_REQ_MSGS

BSSMAPLE_PERF_LOC_REQ_MSGS

Description

The BSSMAPLE_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAP-LEperform location request messages sent on the Lb-interface.

PeggingThis statistic pegs each time a BSSMAP-LE perform location request message is sent on Lb-interface.

Reference GSM 03.71 v7.4.0, sect 7.5, 7.6, 7.7, 7.11, 8.1GSM 09.31 v7.1.0,sect 9.1.


Basis BSS.

Type Counter.


BSSMAPLE_PERF_LOC_RESP_MSGS Chapter 9: BSS statistics for Location Services support

BSSMAPLE_PERF_LOC_RESP_MSGS

Description

The BSSMAPLE_PERF_LOC_RESP_MSGS statistic tracks the number of BSSMAP-LEperform location response messages received on the Lb-interface.

PeggingThis statistic pegs each time a BSSMAP-LE perform location response messageis received on the Lb-interface.

Reference GSM 03.71 v7.4.0, sect. 7.6, 7.7, 7.11.GSM 09.31 v7.1.0, sect. 9.2


Basis BSS.

Type Counter.


Chapter

10MTL statistics

Message Transfer Link (MTL) statistics are used to track events for the Message Transfer Part (MTP)of the ITU-TSS No. 7 protocol on the BSC to MSC interface. They are categorized into subgroups,each of which are described in "MTL statistics subgroups" on page 10-2.


MTL statistics subgroups Chapter 10: MTL statistics

MTL statistics subgroups

MTL statistics are organized into the following major subgroups:

• "MTP C7 availability" on page 10-2.

• "MTP C7 performance" on page 10-2.

• "MTP C7 utilization" on page 10-3.

MTP C7 availability

MTP C7 availability statistics are used to track the duration of signalling link outages andinhibitions (local and remote) for the MTP of the ITU-TSS No.7 protocol on the BSC to MSCinterface. The following are the MTP C7 availability statistics:

• "MTP_LINKFAIL" on page 10-12.

• "MTP_LOCAL_BUSY" on page 10-13.

• "MTP_LOCAL_MGT" on page 10-14.

• "MTP_MGT_INHIBIT" on page 10-15.

• "MTP_MGT_UNINHIBIT" on page 10-16.

• "MTP_REMOTE_MGT" on page 10-21.

• "MTP_REMOTE_PROC" on page 10-22.

• "MTP_START_RPO" on page 10-32.

• "MTP_STOP_RPO" on page 10-33.

• "MTP_UNAVAILABLE" on page 10-35.

MTP C7 performance

MTP C7 performance statistics are used track the different types of failure and recoverysituations for the MTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. Thefollowing are the MTP C7 performance statistics:

• "MTP_CHANGEBACK" on page 10-8.

• "MTP_CHANGEOVER" on page 10-9.

• "MTP_LINK_INS" on page 10-11.

• "MTP_NEG_ACKS" on page 10-19.


Maintenance Information: GSM Statistics Application MTL statistics subgroups

• "MTP_RESTORATION" on page 10-23.

• "MTP_SL_ACK" on page 10-26.

• "MTP_SL_ALIGNMENT" on page 10-27.

• "MTP_SL_CONGESTION" on page 10-28.

• "MTP_SL_ERROR_RATE" on page 10-29.

• "MTP_SL_FAIL" on page 10-30.

• "MTP_SL_FIBR" on page 10-31.

• "MTP_SU_ERROR" on page 10-34.

MTP C7 utilization

MTP C7 utilization statistics are used to track the number of messages received, transmitted and retransmittedon signalling links and supply information on signalling link congestion for the MTP of the ITU-TSS No.7protocol on the BSC to MSC interface. The following are the MTP C7 utilization statistics:

• "BUSY_CICS" on page 10-4.

• "CONGESTION_LOST_MSU" on page 10-6.

• "MSU_DISCARDED" on page 10-7.

• "MTP_CONGESTION" on page 10-10.

• "MTP_MSU_RX" on page 10-17.

• "MTP_MSU_TX" on page 10-18.

• "MTP_RE_TX" on page 10-20.

• "MTP_SIF_SIO_RX" on page 10-24.

• "MTP_SIF_SIO_TX" on page 10-25.

• "SIB_RX" on page 10-36.

• "SIB_RX" on page 10-36.

• "SL_CONGESTION" on page 10-38.

• "SL_STOP_CONGESTION" on page 10-39.


BUSY_CICS Chapter 10: MTL statistics

BUSY_CICS

Description

The BUSY_CICS statistic tracks the number of BUSY CICS during an interval. This weighted distributionstatistics produces a mean value indicating the average number of CICs in use during the interval.

The bin ranges may be changed using the chg_stat_prop command.

The default bin ranges for the BUSY_CICS statistic are:

Table 10-1 BUSY CICS

Bin Range

0 0 to 9

1 10 to 49

2 50 to 99

3 100 to 199

4 200 to 399

5 400 to 799

6 800 to 1199

7 1200 to 1599

8 1600 to 2199

9 2200 to 3200

PeggingThis statistic is pegged each time an allocation or deallocation of a CIC is detected. It is anindication of the amount of active calls under the MSC.

The individual bins values are incremented by the length of time that the number ofallocated CICs fall within the bin ranges.


Maintenance Information: GSM Statistics Application BUSY_CICS

AnalysisSince each call is routed via the MSC (even intra-BSS and intra-cell), the number of CICs representthe number of calls in progress under that MSC for this BSS.

Reference None.

Usage Quality of service monitoring.Network planning.Optimization.

Basis BSS.



CONGESTION_LOST_MSU Chapter 10: MTL statistics

CONGESTION_LOST_MSU

Description

The CONGESTION_LOST_MSU statistic tracks the number of times Message Signalling Units(MSU) are being lost due to Signalling Link (SL) congestion.

PeggingThis statistic pegs for each congestion event which results in MSUs being lost.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of lostMSUs due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 11. MTL: SL congestion events resulting in lossof MSUs - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application MSU_DISCARDED

MSU_DISCARDED

Description

The MSU_DISCARDED statistic tracks the number of MSUs discarded while thereis congestion on the Signalling Link (SL).

PeggingThis statistic pegs each time a MSU is discarded while there is congestion on the SL.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of MSUs arebeing discarded due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 10. MTL: MSUs discarded due to SL congestion- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


MTP_CHANGEBACK Chapter 10: MTL statistics

MTP_CHANGEBACK

Description

The MTP_CHANGEBACK statistic tracks the number of local automatic changebacksthat have been successfully completed.

PeggingThis statistic pegs when MTP traffic that has been changed over to an alternate SignallingLink (SL) is diverted back to the original SL.

AnalysisThis statistic can be used for trend analysis of automatic changebacks that have been successfully completed.



Basis SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application MTP_CHANGEOVER

MTP_CHANGEOVER

Description

The MTP_CHANGEOVER statistic tracks the number of local automatic changeovers that havebeen successfully completed. This indicates MTP traffic is being transferred from a SignallingLink (SL) that is going out of service to an alternate SL.

PeggingThis statistic pegs when MTP traffic is changed over to an alternate SL.

AnalysisThis statistic can be used for trend analysis of local automatic changeovers thathave been successfully completed.



Basis SS7_LINK.

Type Counter.


MTP_CONGESTION Chapter 10: MTL statistics

MTP_CONGESTION

Description

The MTP_CONGESTION statistic tracks the length of time that a signalling link is congested.This can be used to indicate signalling link congestion.

PeggingThe timer for this statistic is started when congestion is detected on a signalling link. Thetimer is stopped when normal operation is resumed.



Basis SS7_LINK.



Maintenance Information: GSM Statistics Application MTP_LINK_INS

MTP_LINK_INS

Description

TheMTP_LINK_INS statistic tracks the length of time that a signalling link (SL) is in the in-service state.

PeggingThe timer for this statistic is started when an SL is brought into service. The timer isstopped when the SL is removed from service.

AnalysisThis statistic can be used for trend analysis of the utilization of in-service SLs.



Basis SS7_LINK.



MTP_LINKFAIL Chapter 10: MTL statistics

MTP_LINKFAIL

Description

The MTP_LINKFAIL statistic tracks the duration of Signalling Link (SL) unavailability due to SLfailure. It records the total time a particular SL is out of service while trying to align.

PeggingThis statistic pegs each time the SL tries to align with the A interface while it is out of service. Thestatistic timer is started when the SL fails. It is stopped when the SL comes back into service.

AnalysisThis statistic can be used for analysis of SL unavailability due to SL failure.



Basis SS7_LINK.



Maintenance Information: GSM Statistics Application MTP_LOCAL_BUSY

MTP_LOCAL_BUSY

Description

The MTP_LOCAL_BUSY statistic tracks the total time congestion is present onthe local end of the Signalling Link (SL).

PeggingThis statistic is started when congestion is detected on an SL. The statistic is stoppedwhen normal operation is resumed.

AnalysisThis statistic can be used for trend analysis on congestion durations on the local end of the SL.


Usage MTP C7 availability.Network planning.Fault finding.

Basis SS7_LINK.



MTP_LOCAL_MGT Chapter 10: MTL statistics

MTP_LOCAL_MGT

Description

The MTP_LOCAL_MGT statistic tracks the total time that a local Signalling Link (SL)is inhibited due to local management actions.

PeggingThis statistic is started each time the SL is inhibited due to local management actionsand stopped when the link is enabled.

AnalysisThis statistic can be used for trend analysis on inhibited local SLs due to local management action.



Basis SS7_LINK.



Maintenance Information: GSM Statistics Application MTP_MGT_INHIBIT

MTP_MGT_INHIBIT

Description

The MTP_MGT_INHIBIT statistic tracks the number of times the Signalling Link (SL) isinhibited using the shutdown command on the MTP link.

PeggingThis statistic is started each time the SL is inhibited by the user entering the shutdowncommand on the associated MTP link.

AnalysisThis statistic can be used for trend analysis on inhibited SLs using the shutdowncommand on the associated MTP link.



Basis SS7_LINK.

Type Counter.


MTP_MGT_UNINHIBIT Chapter 10: MTL statistics

MTP_MGT_UNINHIBIT

Description

The MTP_MGT_UNINHIBIT statistic tracks the number of times the Signalling Link (SL)is uninhibited using the unlock command on the MTP link.

PeggingThis statistic is started each time the SL is uninhibited using the unlock command onan SL that was previously inhibited.

AnalysisThis statistic can be used for trend analysis on uninhibited SLs using the unlockcommand on the associated MTP link.



Basis SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application MTP_MSU_RX

MTP_MSU_RX

Description

The MTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)received on a particular signalling link.

PeggingThis statistic pegs each time MSUs are received over the signalling link.



Basis SS7_LINK.

Type Counter.


MTP_MSU_TX Chapter 10: MTL statistics

MTP_MSU_TX

Description

The MTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)transmitted on a particular signalling link.

PeggingThis statistic pegs each time MSUs are transmitted over the signalling link.



Basis SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application MTP_NEG_ACKS

MTP_NEG_ACKS

Description

TheMTP_NEG_ACKS statistic tracks when the messages between a BSS and an MSC get out of sequence.

PeggingThis statistic pegs when the BSS detects out of order messages to the MSC and request retransmission.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of out of sequencemessages between a BSS and a MSC that are acceptable in normal system operations.

If the specified threshold is exceeded, the 7. MTL: SL number of negative acks received- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


MTP_RE_TX Chapter 10: MTL statistics

MTP_RE_TX

Description

The MTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the MSCbecause the MSC has requested retransmission. This indicates how much the BSS and an MSCare off in message sequencing by the number of octets retransmitted.

PeggingThis statistic pegs the number of octets retransmitted by the BSS to the MSC.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application MTP_REMOTE_MGT

MTP_REMOTE_MGT

Description

TheMTP_REMOTE_MGT statistic tracks the total time a Signalling Link (SL) was remotely inhibited.

PeggingThis statistic pegs the duration of the SL inhibition due to remote management action until uninhibited.

AnalysisThis statistic can be used for trend analysis of remote management SL inhibition actions.



Basis SS7_LINK.



MTP_REMOTE_PROC Chapter 10: MTL statistics

MTP_REMOTE_PROC

Description

TheMTP_REMOTE_PROC statistic tracks the time that a remote processor is out of service.

PeggingThis statistic pegs when a remote processor outage is identified and stopped when theprocessor outage condition ceases.

AnalysisThis statistic can be used for trend analysis of remote processor outages.



Basis SS7_LINK.



Maintenance Information: GSM Statistics Application MTP_RESTORATION

MTP_RESTORATION

Description

TheMTP_RESTORATION statistic tracks the number of times user traffic is allowed on a Signalling Link(SL) that is in service and not inhibited. This statistic does not track recovery from link fail.

PeggingThis statistic pegs when the SL starts carrying user traffic. This happens when the SL comes intoservice, is uninhibited, or recovers from a remote processor outage.

AnalysisThis statistic can be used for trend analysis of used traffic being allowed on an SL.



Basis SS7_LINK.

Type Counter.


MTP_SIF_SIO_RX Chapter 10: MTL statistics

MTP_SIF_SIO_RX

Description

The MTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or ServiceInformation Octets (SIO) that are received over a signalling link.

PeggingThis statistic pegs each time an SIF or SIO is received over the signalling link.



Basis SS7_LINK.

Type Counter.


Maintenance Information: GSM Statistics Application MTP_SIF_SIO_TX

MTP_SIF_SIO_TX

Description

The MTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or ServiceInformation Octets (SIO) that are transmitted over a signalling link.

PeggingThis statistic pegs each time an SIF or SIO are transmitted over the signalling link.



Basis SS7_LINK.

Type Counter.


MTP_SL_ACK Chapter 10: MTL statistics

MTP_SL_ACK

Description

TheMTP_SL_ACK statistic tracks the number of times that the link was lost because a timer expireddue to an acknowledgement that a Message Signal Unit (MSU) was not sent.

PeggingThis statistic pegs each time the link is lost due to a timer that expires when anacknowledgement of an MSU is not sent.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number ofacknowledgements of MSUs not being sent that are acceptable in normal system operations.

If the specified threshold is exceeded, the 2. MTL: SL failure - excessive delay of ACK -PM alarm will be generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application MTP_SL_ALIGNMENT

MTP_SL_ALIGNMENT

Description

The MTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attempts to alignan out of service Signalling Link (SL) with the A interface.

PeggingThis statistic pegs each time an out of service SL unsuccessfully tries to align with the A interface.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of unsuccessfulattempts to align an out of service SL to the A interface that are acceptable in normal system operations.

If the specified threshold is exceeded, the 5. MTL: SL alignment failure - PM alarm is generated. Refer to theMaintenance Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Minor.


MTP_SL_CONGESTION Chapter 10: MTL statistics

MTP_SL_CONGESTION

Description

TheMTP_SL_CONGESTION statistic tracks the number of times the remote site is congested.

PeggingThis statistic pegs each time the remote congestion timer expires.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of occurrences ofexcessive congestion duration at the remote that are acceptable in normal system operations.

If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration ofcongestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application MTP_SL_ERROR_RATE

MTP_SL_ERROR_RATE

Description

TheMTP_SL_ERROR_RATE statistic tracks the number of times that a Signalling Link (SL) is lostdue to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.

PeggingThis statistic pegs each time the SL is lost due to the SUERM timer expiration. (Referto ITU-TSS specification Q. 703, Section 102.)

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times an SL maybe lost due to SUERM timer expirations that are acceptable in normal system operations.

If the specified threshold is exceeded, the 3. MTL: SL failure - excessive error rate - PMalarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Major.


MTP_SL_FAIL Chapter 10: MTL statistics

MTP_SL_FAIL

Description

The MTP_SL_FAIL statistic tracks Signalling Link (SL) failure for all causes exceptoperator interaction through the MMI.

PeggingThis statistic pegs when an SL fails for any reason except operator interaction through the MMI.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of SL failures, excludingthose caused by operator interaction with the MMI, that are acceptable in normal system operations.

If the specified threshold is exceeded, the 0. MTL: SL failure - all reasons - PM alarmis generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Major.


Maintenance Information: GSM Statistics Application MTP_SL_FIBR

MTP_SL_FIBR

Description

The MTP_SL_FIBR statistic tracks the messages between a BSS and a remote site are out ofsequence, causing the Signalling Link (SL) to go out of service. This statistic is similar to theMTP_NEG_ACKS statistic but signals a more severe condition.

PeggingThis statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator Bit (FIB) causedby the de-synchronization of the Backward Sequence Number (BSN) and Forward Sequence Number (FSN).

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times an SL may belost due to the detection of an abnormal FIB that are acceptable in normal system operations.

If the specified threshold is exceeded, the 1. MTL: SL failure - abnormal FIBR/BSNR- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Major.


MTP_START_RPO Chapter 10: MTL statistics

MTP_START_RPO

Description

TheMTP_START_PRO statistic tracks the number of times a remote processor outage occurs.

PeggingThis statistic pegs each time a remote processor outage condition is identified.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of remoteprocessor outages that are acceptable in normal system operations.

If the specified threshold is exceeded, the 8. MTL: Start of remote processor outage- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application MTP_STOP_RPO

MTP_STOP_RPO

Description

TheMTP_STOP_RPO statistic tracks the number of times a remote processor outage condition stops.

PeggingThis statistic pegs each time the remote processor outage stops.

AnalysisThis statistic can be used for trend analysis of remote processor outages and restoration.



Basis SS7_LINK.

Type Counter.


MTP_SU_ERROR Chapter 10: MTL statistics

MTP_SU_ERROR

Description

The MTP_SU_ERROR statistic tracks the number of times erroneous signal unitsare received on the Signalling Link (SL).

PeggingThis statistic pegs each time an erroneous signal unit is received on the SL.

AnalysisA threshold value should be assigned to this statistic reflecting the maximum number of times erroneoussignal units may be received on the SL that are acceptable in normal system operations.

If the specified threshold is exceeded, the 6. MTL: Number of signal units in error - PMalarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.



Basis SS7_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application MTP_UNAVAILABLE

MTP_UNAVAILABLE

Description

The MTP_UNAVAILABLE statistic tracks the total time a Signalling Link (SL) is out ofservice for all reasons including operator intervention.

PeggingThis statistic records the duration of SL unavailability for all reasons, includingoperator intervention through the MMI.

AnalysisThis statistic can be used for trend analysis of the duration of SL outages, includingthose caused by operator interaction.



Basis SS7_LINK.



SIB_RX Chapter 10: MTL statistics

SIB_RX

Description

The SIB_RX statistic provides a means of calculating MTL utilization by counting the numberof Status Indication Busy LSSU messages received.

PeggingThis statistic pegs each receipt of a Status Indication Busy (SIB) LSSU message on a per signalling link basis.




Basis SS7_Link.

Type Counter.


Maintenance Information: GSM Statistics Application SIB_TX

SIB_TX

Description

The SIB_TX statistic provides a means of calculating MTL utilization by counting the numberof Status Indication Busy LSSU messages transmitted.

PeggingThis statistic pegs each transmission of a Status Indication Busy (SIB) LSSU messageon a per signalling link basis.




Basis SS7_Link.

Type Counter.


SL_CONGESTION Chapter 10: MTL statistics

SL_CONGESTION

Description

The SL_CONGESTION statistic tracks the number of times the remote congestion timer expiresdue to excessive duration on a Signalling Link (SL) failure.

PeggingThis statistic pegs each time the remote congestion timer expires due to excessiveduration of congestion on an SL failure.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number of remotecongestion timer expirations that are acceptable in normal system operations.

If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration ofcongestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis SS7_Link.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application SL_STOP_CONGESTION

SL_STOP_CONGESTION

Description

The SL_STOP_CONGESTION statistic tracks Signalling Link (SL) congestion stoppage.

PeggingThis statistic is pegged each time the signalling link congestion indication stops.



Basis SS7_Link.

Type Counter.


SL_STOP_CONGESTION Chapter 10: MTL statistics



Chapter

11CBL, GSL, OML, RSL and XBL statistics

X.25/LAPD statistics included here, are used to track BSS data transmission information.These statistics relate to events on the following links:

• Cell Broadcast Link (CBL).

• GPRS Signalling Link (GSL).

• Operation and Maintenance Link (OML).

• Radio System Link (RSL).

• RXCDR to BSC Link (XBL).

The statistics are listed in "X.25/LAPD Level: X.25 and LAPD statistics" on page 11-2.


X.25/LAPD Level: X.25 and LAPD statistics Chapter 11: CBL, GSL, OML, RSL and XBL statistics

X.25/LAPD Level: X.25 and LAPD statistics

X.25 and LAPD statistics are used to track BSS data transmission information. Thefollowing are the X.25 and LAPD statistics:

• "ATER_CHANNEL_STATUS" on page 11-3.

• "ATER_EMERG_PREEMPT_STATUS" on page 11-5.

• "FRMR" on page 11-6.

• "I_FRAMES_RX" on page 11-7.

• "I_FRAMES_TX" on page 11-8.

• "INVALID_FRAMES_RX" on page 11-9.

• "LAPD_CONGESTION" on page 11-10.

• "N2_EXPIRY" on page 11-11.

• "SABM_TX" on page 11-12.


Maintenance Information: GSM Statistics Application ATER_CHANNEL_STATUS

ATER_CHANNEL_STATUS

Description

The ATER_CHANNEL_STATUS statistic tracks the Ater channel status on a per XBL linkset basis.


0 ATER_CHAN_REQ Counts the number of Ater channels requested.

1 ATER_CHAN_REQ_FAIL Counts the number of Ater channels requested butcould not be allocated.

2 CALL_SETUP_FAIL_COMM_ERR Counts the number of call setup failures due toBSC-RXCDR communication errors.

3 INIT_HO_CIC_FAIL_COMM_ERR Counts the number of internal call handovers andCIC remaps due to BSS-RXCDR communicationerrors.

4 ATER_SWITCH_FAIL_COMM_ERR Counts the number of Ater switchover failures dueto BSC-RXCDR communication errors.

5 CALL_SETUP_FAIL_NO_ATER Counts the number of call setups that fail due to noavailable Ater channels.

6 INIT_HO_CIC_FAIL_NO_ATER Counts the number of internal call handovers andCIC remaps due to no available Ater channels.

7 ATER_SWITCH_FAIL_NO_ATER Counts the number of Ater switchover failures dueto no available Ater channels.

8 BSC_INIT_BLOCK_CIC_LOW_ATER Counts the number of times BSC initiated blockingof CICs was invoked. The pegging of this statisticrepresents the scenario where the number ofavailable Ater channels to an associated RXCDRfalls below the darbc_block threshold (the BSC isoperating in dynamic mode). The BSC automaticallyblocks at the MSC all remaining idle CICs that arerouted through the associated RXCDR. All OOSand idle CICs will have the Low Ater Resourcesreason set.

PeggingThis statistic pegs the number of events relating to ATER allocation and assignmentscenarios on a per XBL linkset basis.

Reference None.

Usage Network planning.Fault finding.Quality of service monitoring.


ATER_CHANNEL_STATUS Chapter 11: CBL, GSL, OML, RSL and XBL statistics

Basis AXCDR.

Type Large counter array.


Maintenance Information: GSM Statistics Application ATER_EMERG_PREEMPT_STATUS

ATER_EMERG_PREEMPT_STATUS

Description

The ATER_EMERG_PREEMPT_STATUS statistic tracks the number of emergencycalls pre-empted on an Ater channel.


0 EMERG_PREEMPT_ATTEMPT Counts the total number of pre-emptions attemptedfor emergency calls using an Ater channel.

1 EMERG_PRE-EMPT_ATMPT_CALL_SETUP

Counts the number of pre-emption attempts dueto no available Ater channels for emergency callsetup.

2 EMERG_PRE-EMPT_ATMPT_ATER_SWITCH

Counts the number of pre-emption attempts due toswitchover of Ater channels for emergency calls.

3 EMERG_PREEMPT_FAIL Counts the number of call assignment failures dueto BSC-RXCDR communication errors. The BSCmessage protocol to establish an Ater resource forthe call has times out after continual attempts toallocate the Ater resource with the RXCDR.

PeggingCounts the number of events relating to ATER pre-emption for emergency call sce-narios on a per XBL linkset basis.

Reference None.

Usage Network planning, Optimization.Quality of service monitoring.

Basis AXCDR

Type Small counter array.


FRMR Chapter 11: CBL, GSL, OML, RSL and XBL statistics

FRMR

Description

The FRMR statistic tracks the number of frames that were rejected because the frames were not recoverable.

PeggingThis statistic pegs each time a frame is received that is not recoverable.

Reference ITU-TSS Q.920 - 1ITU-TSS X.20 - X.32

Usage X.25/LAPD.Fault finding.

Basis X25_LINK/LAPD_LINK.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application I_FRAMES_RX

I_FRAMES_RX

Description

The I_FRAMES_RX statistic tracks the number of Information Frames (I-Frames) received.

PeggingThis statistic pegs when an I-Frame is received.

Reference ITU-TSS Q.920 - 1.ITU-TSS X.20 - X.32.

Usage X.25/LAPD.


Type Counter.


I_FRAMES_TX Chapter 11: CBL, GSL, OML, RSL and XBL statistics

I_FRAMES_TX

Description

The I_FRAMES_TX statistic tracks the number of Information Frames (I-Frames) transmitted.

PeggingThis statistic peg when an I-Frame is transmitted.


Usage X.25/LAPD.


Type Counter.


Maintenance Information: GSM Statistics Application INVALID_FRAMES_RX

INVALID_FRAMES_RX

Description

The INVALID_FRAMES_RX statistic tracks the number of invalid frames received.

PeggingThis statistic is pegged whenever an invalid frame is received.

• X.25

On the OML (BSS-OMC-R).

On the CBL (BSS-CBC).

• LAPD

On the RSL (BSS-BTS link).

On the XBL (BSC-RXCDR link).




Type Counter.

Alarm Warning.


LAPD_CONGESTION Chapter 11: CBL, GSL, OML, RSL and XBL statistics

LAPD_CONGESTION

Description

The LAPD_CONGESTION statistic tracks the time that the LAPD or X.25 link is congested. Thisindicates the time period in milliseconds when the sending speed of the BSC/BTS processes is more thanthe link transmit capability and provides a way of monitoring when more links need to be added.

The exec-dlsp process has a bigger buffer to hold outgoing messages therefore themessages will not get dropped even during the congestion period.

PeggingThis statistic pegs when the transmit buffer gets full and stops when the buffer is available again.




Type Duration.


Maintenance Information: GSM Statistics Application N2_EXPIRY

N2_EXPIRY

Description

The N2_EXPIRY statistic tracks the number of link alignment retries attempted without success.

PeggingThis statistic pegs when the retry count threshold has been exceeded.




Type Counter.

Alarm Minor.


SABM_TX Chapter 11: CBL, GSL, OML, RSL and XBL statistics

SABM_TX

Description

The SABM_TX statistic tracks the links that come into service.

PeggingThis statistic is pegged for all Set Asynchronous Balanced Mode (SABM) frames.


Usage X.25/LAPD.


Type Counter.


Chapter

12PCU statistics

PCU statistics are captured from events occurring at the Packet Control Unit (PCU). They are categorizedinto subgroups, each of which are described in "PCU statistics subgroups" on page 12-2.


PCU statistics subgroups Chapter 12: PCU statistics

PCU statistics subgroups

PCU statistics are organized into the following major subgroups:

• "GBL statistics" on page 12-2.

• "Accessibility statistics" on page 12-2.

• "Throughput statistics" on page 12-4.

• "Dynamic allocation statistics " on page 12-6.

GBL statistics

The GBL device refers to the configured number of timeslots on an E1 link between the PCU and the ServingGPRS Support Node (SGSN). This interface is referred to as the Gb interface. The Gb interface allows manyusers to be multiplexed over a common physical resource. GPRS signalling and user data are sent on the samephysical resource, that is, no dedicated physical resources are required to be allocated for signalling purposes.

The GBL measurement types are listed as follows:

• "CELL_FLUSH_REQS" on page 12-15

• "GBL_DL_DATA_THRPUT" on page 12-60

• "GBL_DL_DATA_THRPUT_HIST" on page 12-61

• "GBL_FLOW_CTRL_SENT" on page 12-63

• "GBL_LINK_INS" on page 12-64

• "GBL_PAGING_REQS" on page 12-65

• "GBL_UL_DATA_THRPUT" on page 12-66

• "GBL_UL_DATA_THRPUT_HIST" on page 12-67

• "GBL_UNAVAILABLE" on page 12-69

Accessibility statistics

Accessibility statistics measure how effectively GPRS resources are being accessed. These measurementsassist the operator in planning the necessary resources needed for the MS to efficiently access the network.

The accessibility statistics include the following:

• {4441}"CH_REQ_UNSVCD_PCU" on page 12-16

• "CHANNEL_REQS_REC" on page 12-18


Maintenance Information: GSM Statistics Application PCU statistics subgroups

• "CHANNEL_REQS_REJECT" on page 12-19

• "CHANNEL_REQS_SUCCESS" on page 12-20

• "CODING_SCHEME_CHANGE" on page 12-22

• "CS12_ON_32K_CHAN" on page 12-26

• {23658}"EGPRS_64K_CHANNELS_SWITCHED" on page 12-55

• {23658}"EGPRS_64K_NOT_AVAIL" on page 12-56

• {3723}"EGPRS_DL_ASGN_PCCCH" on page 12-58

• {4441}"G_RACH_UNSVCD_BTS" on page 12-59

• "GPRS_32K_CHANNELS_SWITCHED" on page 12-70

• "GPRS_32K_DL_NOT_AVAIL" on page 12-71

• "GPRS_32K_UL_NOT_AVAIL" on page 12-72

• "GPRS_ACCESS_PER_AGCH" on page 12-73

• "GPRS_ACCESS_PER_RACH" on page 12-74

• "GPRS_CELL_RESELECT_ATTMPT" on page 12-77

• "GPRS_CELL_RESELECT_FAIL" on page 12-78

• "GPRS_CHANNELS_SWITCHED" on page 12-79

• {3723}"GPRS_DL_ASGN_PCCCH" on page 12-80

• "GPRS_MS_NEIGHBOR_STRONG" on page 12-85

• "GPRS_PCH_AGCH_Q_LENGTH" on page 12-86

• {3723}"GPRS_PPCH_PAGCH_Q_LENGTH" on page 12-87

• {4441}"GPRS_PRR_BLK_USG" on page 12-88

• {4441}"GPRS_RACH_ARRIVAL" on page 12-90

• "MS_CLASS_1_10_REQ" on page 12-99 (GSR7 only)



• "NO_PDTCH_AVAIL" on page 12-105

• "NO_PDTCH_AVAIL_TIME" on page 12-106



Throughput statistics

The throughput statistics are listed as follows:

• "AIR_DL_CONTROL_BLKS" on page 12-7

• "AIR_DL_DATA_BLKS" on page 12-8 (GSR7 only)

• {4445}"AIR_DL_TBF_FAILURES" on page 12-10

• "AIR_UL_CONTROL_BLKS" on page 12-11

• "AIR_UL_DATA_BLKS" on page 12-12 (GSR7 only)

• {4445}"AIR_UL_TBF_FAILURES" on page 12-14

• {4445}"CONG_REL_DL_SCTS" on page 12-24

• "DL_BUSY_PDTCH" on page 12-27

• "DL_PDTCH_CONGESTION" on page 12-29

• "DL_PDTCH_Q_LENGTH" on page 12-30

• "DL_PDTCH_SEIZURE" on page 12-31

• {23658}"DL_RADIO_BLKS_1_TS" on page 12-32




• {23658}"DL_RLC_ACK_NEW_BLKS" on page 12-40

• {23658}"DL_RLC_DDTR_BLKS" on page 12-42

• {23658}"DL_RLC_NACK_BLKS" on page 12-43

• {23658}"DL_RLC_RETX_BLKS" on page 12-45

• {23658}"DL_RLC_STALLED_BLKS" on page 12-47

• {23658}"DL_RLC_UNACK_NEW_BLKS" on page 12-49

• {23658}"DL_TBF_TIME_1_TS" on page 12-51




• {23658}"EGPRS_AVAIL_PDTCH" on page 12-57

• "GBL_DL_DATA_THRPUT" on page 12-60


Maintenance Information: GSM Statistics Application PCU statistics subgroups

• "GBL_DL_DATA_THRPUT_HIST" on page 12-61

• "GBL_UL_DATA_THRPUT" on page 12-66

• "GBL_UL_DATA_THRPUT_HIST" on page 12-67

• "GPRS_AVAIL_PDTCH" on page 12-75

• "IDLE_PDTCH_INTF_BAND1" on page 12-93




• "IMM_ASSGN_CAUSE" on page 12-97

• "PRP_LOAD" on page 12-107

• "UL_BUSY_PDTCH" on page 12-109

• "UL_PDTCH_CONGESTION" on page 12-111

• "UL_PDTCH_Q_LENGTH" on page 12-112

• "UL_PDTCH_SEIZURE" on page 12-113

• {23658}"UL_RADIO_BLKS_8PSK_1_TS" on page 12-114

• {23658}"UL_RADIO_BLKS_8PSK_2_TS" on page 12-116

• {23658}"UL_RADIO_BLKS_GMSK_1_TS" on page 12-118

• {23658}"UL_RADIO_BLKS_GMSK_2_TS" on page 12-120

• {23658}"UL_RLC_ACK_NEW_BLKS" on page 12-122

• {23658}"UL_RLC_RETX_BLKS" on page 12-124

• {23658}"UL_RLC_UNACK_NEW_BLKS" on page 12-126

• {23658}"UL_TBF_TIME_8PSK_1_TS" on page 12-128

• {23658}"UL_TBF_TIME_8PSK_2_TS" on page 12-129

• {23658}"UL_TBF_TIME_GMSK_1_TS" on page 12-130

• {23658}"UL_TBF_TIME_GMSK_2_TS" on page 12-131



Dynamic allocation statistics

The dynamic allocation statistics are listed as follows:

• "GPRS_DYNET_FAILURES" on page 12-81

• "GPRS_DYNET_RES_REQS" on page 12-83

• "GPRS_DYNET_SWI_REQS" on page 12-84


Maintenance Information: GSM Statistics Application AIR_DL_CONTROL_BLKS

AIR_DL_CONTROL_BLKS

Description

The AIR_DL_CONTROL_BLKS statistic tracks the number of downlink control Radio Link Control(RLC) blocks sent by the Packet Control Unit (PCU). Examples for downlink control blocks are:

• Packet Uplink ACK/NACK.

• Packet Uplink Assignment.

• Packet Downlink Assignment.

• Packet Timeslot Reconfigure.

• Packet Power Control/Timing Advance.

• Packet Cell Change Order.

Retransmissions of control blocks are included in this statistic.

PeggingThis statistic is pegged for each control block sent down.


AnalysisThis statistic can be used for the trend analysis of the number of Radio Link Control blocks sent by the PCU.

Reference None.

Usage Performance management.

Basis Cell.

Type Counter.


AIR_DL_DATA_BLKS Chapter 12: PCU statistics

AIR_DL_DATA_BLKS

This statistic applies to GSR7 release only. It is not valid for EGPRS.

Description

The AIR_DL_DATA_BLKS statistic tracks the number of blocks sent by the PCU to the MS foreach quality of service (QoS) level and coding scheme combination.

QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented whichis the most delay insensitive traffic class - it is defined as Best Effort.

The bins are defined in Table 12-1.

Table 12-1 AIR_DL_DATA_BLKS counters


0 QOS1_CS1 Quality of service level 1, coding scheme 1













Maintenance Information: GSM Statistics Application AIR_DL_DATA_BLKS

PeggingThe appropriate bin is incremented by the amount of data blocks sent by the PCU to the MS for thequality of service and coding scheme. Each count is rounded to the nearest 100 blocks.

Reference None.


Basis Cell.

Type Counter array.


AIR_DL_TBF_FAILURES Chapter 12: PCU statistics

AIR_DL_TBF_FAILURES

{4445}

Description

The AIR_DL_TBF_FAILURES statistic tracks the total number of downlink Temporary Block Flow (TBF)that are abnormally released in the different phases (identified in the bins) due to radio failures in a cell.

Bin Description

0 Establishment.

1 Data transfer.

2 Delayed TBF release mode.

3 Termination.

PeggingThis statistic pegs each time a downlink TBF is established and later abnormally released due toradio failures in a cell during a statistical measurement interval. The statistic pegs the appropriatebin depending on the phase where the TBF was abnormally released.


Reference None

Usage Performance management

Basis Cell.



Maintenance Information: GSM Statistics Application AIR_UL_CONTROL_BLKS

AIR_UL_CONTROL_BLKS

Description

The AIR_UL_CONTROL_BLKS statistic tracks the number of uplink control Radio Link Control(RLC) blocks received by the PCU. Examples for Uplink control blocks are:

• Packet Downlink ACK/NACK.

• Packet Control Acknowledgment.

• Packet Resource Request.

• Uplink Dummy Control Block.

Retransmissions of control blocks are included in this statistic.

PeggingThis statistic is pegged for each control block the network receives from the MS.


AnalysisThis statistic can be used for the trend analysis of Radio Link Control blocks sent by the MS.

Reference None.


Basis Cell.

Type Counter.


AIR_UL_DATA_BLKS Chapter 12: PCU statistics

AIR_UL_DATA_BLKS


Description

The AIR_UL_DATA_BLKS statistic tracks the number of data blocks received by the PCU foreach quality of service level and coding scheme combination.


The bins are defined in Table 12-2.

Table 12-2 AIR_UL_DATA_BLKS counters















Maintenance Information: GSM Statistics Application AIR_UL_DATA_BLKS

PeggingThe appropriate bin is incremented by the amount of data blocks received for the quality of serviceand coding scheme. The count is rounded to the nearest 100 blocks.

Reference None.


Basis Cell.

Type Counter array.


AIR_UL_TBF_FAILURES Chapter 12: PCU statistics

AIR_UL_TBF_FAILURES

{4445}

Description

The AIR_UL_TBF_FAILURES statistic tracks the total number of uplink Temporary Block Flow (TBF) thatare abnormally released in the different phases (identified in the bins) due to radio failures in a cell.

Bin Description

0 Establishment.

1 Data transfer.

2 Termination.

PeggingThis statistic pegs each time that an uplink TBF is established and later abnormally released due toradio failures in a cell during a statistical measurement interval. The statistic pegs the appropriatebin depending on the phase where the TBF was abnormally released.


Reference None


Basis Cell.



Maintenance Information: GSM Statistics Application CELL_FLUSH_REQS

CELL_FLUSH_REQS

Description

The CELL_FLUSH_REQS statistic tracks the number of flush requests received on the GBL(s) per cell basis.

PeggingThis statistic is pegged each time a flush request is received on the GBL to flush the LogicalLink Control (LLC) Protocol Data Unit (PDU) for a particular MS.

AnalysisThis statistic can be used for the trend analysis of the number of flush messages received by the BSS.

Reference None.

Usage Network planning.Congestion.

Basis Cell

Type Counter.

This statistic was previously known as GBL_FLUSH_REQS.


CH_REQ_UNSVCD_PCU Chapter 12: PCU statistics

CH_REQ_UNSVCD_PCU

{4441}

Description

The CH_REQ_UNSVCD_PCU statistic tracks the total number of uplink GPRSchannel requests unservice by the PCU.

The bins are:

• RACH - RSL bandwidth limitation.

• RACH - Round Trip Delay (RTD) / timeout.

• RACH - Insufficient resources.

• PRACH - Round Trip Delay (RTD) / timeout.

• PRACH - Insufficient resources.

• PRR - Round Trip Delay (RTD) / timeout.

• PRR - Insufficient resources.

• PDAK - Insufficient resources.

This statistic represents the major reasons for not servicing GPRS channel requests at the PCU. Minorcondition scenarios, such as the channel request being received in a wrong MS/TBF state due to system raceconditions, and various system delays are minimal and are not covered in any of the bins above.

PeggingThis statistic is pegged for each channel request unserviced by the PCU.



Maintenance Information: GSM Statistics Application CH_REQ_UNSVCD_PCU

AnalysisThis statistic can be used for the trend analysis of the PCU.

Reference None.


Basis Cell.

Type Counter array.


CHANNEL_REQS_REC Chapter 12: PCU statistics

CHANNEL_REQS_REC

Description

The CHANNEL_REQS_REC statistic tracks the number of channel or resourcerequest messages received by the PCU.

Bin Description

0 A GPRS One-Phase access channel request is received.

1 {3723} A GPRS One-Phase access packet channel request on PCCCH is received.

2 A GPRS single block allocation on CCCH is received.

3 {3723}A GPRS single block allocation on PCCCH is received.

4 A GPRS Packet Resource Request (PRR) message is received (second phase of twophase access).

5 A GPRS Channel Request in Packet Downlink ACK/NACK (PDAK) message is received.

6 An Enhanced One-Phase (EOP) access indication is received.

7 {23658} EGPRS One-Phase access on CCCH is received.

8 {23658} An EGPRS One-Phase access on PCCCH is received.

9 {23658} An EGPRS Single Block Allocation on CCCH is received

10 {23658} {3723} An EGPRS Single Block Allocation on PCCCH is received.

11 {23658} An EGPRS Packet Resource Request is received.

12 {23658} An EGPRS Channel Request in Packet Downlink ACK/NACK (PDAK) messageis received.

PeggingThis statistic pegs for each channel request message received. The bin that is incrementedis determined by the channel request message type.

Reference None.


Basis Cell.

Type Extra large counter array.


Maintenance Information: GSM Statistics Application CHANNEL_REQS_REJECT

CHANNEL_REQS_REJECT

Description

The CHANNEL_REQS_REJECT statistic tracks the number of rejections by the PCU for packet channelor resource requests. The PCU rejects such requests because the resources are unavailable.

PeggingThis statistic pegs when a Packet Access Reject message is sent to the MS in response to aUL Request in PDAK or to a Packet Resource Request (two-phase access) when there are noresources left to allocate. No retransmissions are pegged.


Reference None.


Basis Cell.

Type Counter.


CHANNEL_REQS_SUCCESS Chapter 12: PCU statistics

CHANNEL_REQS_SUCCESS

Description

This statistic counts the number of channel or resource requests that are actuallyallocated a TBF resource successfully.

This statistic specifically counts the number of ASSIGNMENT messages sent to theMS. Re-transmissions are excluded.

Bin Description

0 A GPRS One-Phase Access Packet Immediate Assignment (PIA) is sent on CCCH.

1 {3723} A GPRS One-Phase Access Packet Uplink Assignment (PUA) is sent on PCCCH.

2 A GPRS Single Block Allocation PIA is sent on CCCH.

3 {3723} A GPRS Single Block Allocation PUA is sent on CCCH.

4 A GPRS PUA (in response to Packet Resource Request) is sent to establish a TBF (onlythe first PUA is counted).

5 A GPRS Packet Timeslot Reconfiguration (PTR) is sent to establish a new TBF or tore-assign the downlink TBF (only the first PTR is counted).

6 An Enhanced One-Phase (EOP) Access indication is received on CCCH.

7 {3723} A GPRS PUA in response to a “channel request” received in a Packet DownlinkACK.

8 {23658} An EOP Access PIA is sent on CCCH.

9 {23658} An EOP access PUA is sent on PCCCH.

10 {23658} {3723} An EGPRS Single Block Allocation PIA is sent on CCCH.

11 {23658} An EGPRS Single Block Allocation PUA is sent on PCCCH.

12 {23658} An EGPRS PUA (in response to Packet Resource Request (PRR)) is sent toestablish a TBF (only the first PUA is counted).

13 {23658} An EGPRS PTR is sent to establish a new TBF or to re-assign the downlink TBF(only the first PTR is counted)..

14 {23658} An EGPRS PUA in response to a “channel request” in a PDAK.

PeggingThis statistic pegs for each channel request message granted on the downlink. The bin that is incrementedis determined by the channel request message type. Retransmissions are not pegged.


Maintenance Information: GSM Statistics Application CHANNEL_REQS_SUCCESS

AnalysisThe statistic can be used for the trend analysis of the number of successful uplinkGPRS calls made by a particular CELL.

Reference Digital cellular telecommunications systems (phase 2+) Version7.0.0 Jan 2000 ETSI.

Usage Congestion, network planning.

Basis Cell.

Type Extra large counter array.


CODING_SCHEME_CHANGE Chapter 12: PCU statistics

CODING_SCHEME_CHANGE

Description

The CODING_SCHEME_CHANGE statistic is obtained by measuring the number of codingscheme upgrades (from lower to higher coding scheme) and coding downgrades (from higher to lowercoding scheme) for uplink and downlink in a statistical measurement period.

Controls blocks (always sent at CS-1) will result in this statistic not being pegged.

Downlink coding scheme transitions for dummy blocks (when entering andexiting super-coattail) will not be counted.

The bins are defined in Table 12-3:

Table 12-3 CODING_SCHEME_CHANGE bins


0 CODING_SCHEME_CHANGE_0 Total number of GPRS coding scheme upgradesfor uplink.

1 CODING_SCHEME_CHANGE_1 Total number of GPRS coding scheme downgradesfor uplink.

2 CODING_SCHEME_CHANGE_2 Total number of GPRS coding scheme upgradesfor downlink.

3 CODING_SCHEME_CHANGE_3 Total number of GPRS coding scheme downgradesfor downlink.

{23658}4

CODING_SCHEME_CHANGE_4 Total number of EGPRS coding scheme upgradesfor uplink.

{23658}5

CODING_SCHEME_CHANGE_5 Total number of EGPRS coding schemedowngrades for uplink.

{23658}6

CODING_SCHEME_CHANGE_6 Total number of EGPRS coding scheme upgradesfor downlink.

{23658}7

CODING_SCHEME_CHANGE_7 Total number of EGPRS coding schemedowngrades for downlink.


Maintenance Information: GSM Statistics Application CODING_SCHEME_CHANGE

PeggingThe appropriate bin is incremented each time a change in coding scheme occurs.

AnalysisThis statistic can be used for the trend analysis of the number of Coding Scheme upgrades and downgradeson the uplink and downlink which may signify that the cell is congested.


Usage Congestion, network planning.

Basis Cell.



CONG_REL_DL_SCTS Chapter 12: PCU statistics

CONG_REL_DL_SCTS

{4445}

Description

The CONG_REL_DL_SCTS statistic tracks the total number of downlink TBF terminations under thedelayed TBF release mode (super-coattail) in a cell as cell availability goes below the following thresholds:

• 25 block periods (500ms) old super-coattail will be terminated if the:

cell availability reached is � 25%, in a cell with � 3 TS.


cell availability reached is � 10%, in a cell with > 5 TS.

• 15 block periods (300ms) old super-coattail will be terminated if the:


cell availability reached is � 30%, in a cell with > 5 TS.

The minimum super-coattail duration is 15 block periods or 300ms. No super-coattailbelow 15 block periods are terminated.

This statistic is accessible only if the Increased PRP Capacity feature introduced byEnhanced Scheduling feature RDB 4441 is unrestricted.

PeggingThis statistic pegs each time that an uplink TBF is successfully established and later released under delayedTBF release mode to relieve the congestion in a cell during a statistical measurement interval.



Maintenance Information: GSM Statistics Application CONG_REL_DL_SCTS

Reference None


Basis Cell.

Type Counter.


CS12_ON_32K_CHAN Chapter 12: PCU statistics

CS12_ON_32K_CHAN

Description

The CS12_ON_32K_CHAN statistic tracks the percentage of time in a statistics reporting period thatCS-3, CS-4 capable (32kTRAU) GPRS timeslots are used with CS-1 and CS-2 rates.

PeggingThis statistic measures the percentage of blocks for which CS-1 and CS-2 data was transmittedon a timeslot capable of CS-3 or CS-4 rates.

Reference None.


Basis Cell.

Type Percentage.


Maintenance Information: GSM Statistics Application DL_BUSY_PDTCH

DL_BUSY_PDTCH

Description

This statistic measures the mean, max and min number of occupied Packet Data CHannels(PDCH) carrying downlink packet traffic.

This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, atevery packet-scheduling period (20 millisecond).

Table 12-4 shows the ranges for each bin (measured in milliseconds).

Table 12-4 DL_BUSY_PDTCH bins

Bin Range

0 No PDTCH is busy

1 1-2 PDTCH are busy









PeggingThis statistic pegs every packet-scheduling period (20 millisecond) by sampling the numberof PDTCHs that are carrying downlink packet traffic.



DL_BUSY_PDTCH Chapter 12: PCU statistics

AnalysisThis statistic can be used for trend analysis of the number of PDTCHs that are used for downlink packet traffic.


Usage Network planning, congestion.

Basis Cell



Maintenance Information: GSM Statistics Application DL_PDTCH_CONGESTION

DL_PDTCH_CONGESTION

Description

The DL_PDTCH_CONGESTION statistic calculates the number of times a cell is congested dueto MS load on the available air resources on the downlink. Whenever the downlink resources aredetermined to be congested, the statistic is updated. When the value of the statistic is large, it indicatesthat the cell is congested and more radio resources may need to be provisioned.

PeggingThe PDTCH congestion is computed every 8s (8000ms) in 20ms block periods when the congestion thresholdis reached. The congestion threshold is configurable with values ranging from 1-4. Level 1 means averagelyone TBF per TS on a cell is considered congested. Level 4 means four TBFs per TS are considered congested.This is synonymous with the concept that one PDTCH can be shared by, at most, 4 MSs.


AnalysisThis statistic is totalled in terms of 20 millisecond block periods.



Basis Cell.

Type Counter.


DL_PDTCH_Q_LENGTH Chapter 12: PCU statistics

DL_PDTCH_Q_LENGTH

Description

This statistic is obtained by sampling the Downlink Request Queue. A Downlink Requestis triggered on arrival of LLC-PDUs at the PCU.

PeggingThis statistic pegs every 20ms. It is incremented when a request is added to the queue and isdecremented when a request is processed, that is, leaves the queue.


AnalysisThis statistic can be used for the trend analysis of the average number of downlink messageswaiting for a PDTCH to become available.



Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application DL_PDTCH_SEIZURE

DL_PDTCH_SEIZURE

Description

This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the downlink. Thepurpose of this statistic is to count the number of TBF(s) on the downlink. The statistic is obtained bymeasuring the receipt of the first RLC block (PDU) on the PDTCH from the network (downlink).

PeggingThis statistic pegs when the receipt of the first downlink RLC block (PDU) on thePDTCH from the network is obtained.


AnalysisThis statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.



Basis Cell.

Type Counter.


DL_RADIO_BLKS_1_TS Chapter 12: PCU statistics

DL_RADIO_BLKS_1_TS

{23658}

Description

The DL_RADIO_BLKS_1_TS statistic counts the total number of RLC radio blocks sent tomobiles that support a maximum of 1 TS in the downlink direction.

100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation ofactual radio blocks counted to units is performed at the end of the interval.

The RLC radio blocks are split into the four GPRS channel coding schemes and the nineEGPRS coding schemes, as shown in Table 12-5.

Table 12-5 Bin ranges for DL_RADIO_BLKS_1_TS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application DL_RADIO_BLKS_1_TS

In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shownin the following table is used to determine which statistic must be pegged for possible combinations ofNEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.

(RLC block 1, RLC block 2) DL radio block status

(NACK, NACK) NACK

(NACK, NEW) NACK

(NACK, ACK_PEND) NACK

(NEW, NEW) NEW

(NEW, ACK_PEND) NEW

(ACK_PEND, ACK_PEND) ACK_PEND

(NACK, STALL) STALL

(NEW, STALL) STALL

(STALL, STALL) STALL

PeggingThis statistic counts the RLC radio blocks for mobiles that support a maximum of 1TS in the downlink direction as follows:

• Always pegged for mobiles with multislot class 1.

• CS-1 through CS-4 are pegged if the GPRS multislot is Class 1.

• MCS-1 through MCS-9 are pegged if the EGPRS multislot is Class 1.

For examples, see 3GPP TS05.02, Annex B (normative).

The DL_RADIO_BLKS statistics are only reported for successful TBFs. Bin 0 (CS-1) andbin 4 (MCS-1), do not count super-coattail blocks.

Only RLC radio blocks are counted . No retransmissions due to any cause are pegged. The RLC radioblocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell

Type Extra large counter array



DL_RADIO_BLKS_2_TS

{23658}

Description


100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translationof actual radio blocks counted to units is done at the end of the interval.

The RLC radio blocks are split into the four GPRS channel coding schemes, and the nineEGPRS coding schemes, as shown in Table 12-6.


Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9





(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL



• Always pegged for mobiles with multislot class 2, 3 or 5.

• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobileand its GPRS multislot is class 2,3 or 5.

• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to themobile and the EGPRS multislot is class 2, 3 or 5.



Analysis

Reference None

Usage

Basis Cell




DL_RADIO_BLKS_3_TS

{23658}

Description





Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9





(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


Multislot class 13 will be treated as multislot class 9.


• Always pegged for mobiles with multislot class 4, 6, 7, 9, or 13.

• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile andits GPRS multislot is class 4, 6, 7, 9, or 13.

• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the mobileand the EGPRS multislot is class 4, 6, 7, 9, or 13.



Analysis

Reference None

Usage

Basis Cell




DL_RADIO_BLKS_4_TS

{23658}

Description





Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9





(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


Multislot classes 14–29 will be treated as multislot class 10.


• Always pegged for mobiles with multislot class 8, 10, 11, 12 or 14 through 29.

• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile and itsGPRS multislot is one of class 8, 10, 11, 12 or 14 through 29.

• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the mobileand the EGPRS multislot is one of class 8, 10, 11, 12 or 14 through 29.


Only RLC radio blocks are counted. No retransmissions due to any cause are pegged. The RLC radioblocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



DL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics

DL_RLC_ACK_NEW_BLKS

{23658}

Description

The DL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledgemode blocks sent for the first time by the PCU over the cell.



Table 12-9 Bin ranges for DL_RLC_ACK_NEW_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application DL_RLC_ACK_NEW_BLKS



(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


PeggingThis statistic counts the new RLC acknowledged radio blocks that are sent on a cell. The RLC radioblocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



DL_RLC_DDTR_BLKS Chapter 12: PCU statistics

DL_RLC_DDTR_BLKS

{23658}

Description

The DL_RLC_DDTR_BLKS statistic measures the total number of RLC blocks with dummy LLCssent in CS1 or MCS1 during the delayed downlink TBF release period over the cell.


The RLC radio blocks are split into two coding schemes, as shown in Table 12-10.

Table 12-10 Bin ranges for DL_RLC_DDTR_BLKS

Bin Range

0 CS-1

1 MCS-1

PeggingThis statistic counts the RLC radio blocks with dummy LLCs (delayed downlink TBF) blocks that are senton a cell. The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.Note that the radio blocks with LLC dummies are always sent using either CS1 or MCS1.

Analysis

Reference None

Usage

Basis Cell

Type Small counter array


Maintenance Information: GSM Statistics Application DL_RLC_NACK_BLKS

DL_RLC_NACK_BLKS

{23658}

Description

The DL_RLC_NACK_BLKS statistic measures the total number of RLC blocks sentdue to an explicit NACK from the mobile.



Table 12-11 Bin ranges for DL_RLC_NACK_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


DL_RLC_NACK_BLKS Chapter 12: PCU statistics



(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


PeggingThis statistic counts the RLC blocks that are sent due to an explicit NACK from the mobile. The RLCradio blocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



Maintenance Information: GSM Statistics Application DL_RLC_RETX_BLKS

DL_RLC_RETX_BLKS

{23658}

Description

The DL_RLC_RETX_BLKS statistic measures the total number of pre-emptive retransmissions (or ackpending blocks and acknowledged retransmissions) sent by the PCU over the cell.



Table 12-12 Bin ranges for DL_RLC_RETX_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


DL_RLC_RETX_BLKS Chapter 12: PCU statistics



(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


PeggingThis statistic counts the RLC ack pending (or pre-emptive transmissions) radio blocks that are sent on a cell.The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



Maintenance Information: GSM Statistics Application DL_RLC_STALLED_BLKS

DL_RLC_STALLED_BLKS

{23658}

Description

The DL_RLC_STALLED_BLKS statistic measures the total number of RLC blocks retransmitted due to anRLC window stall. That is, if the window is stalled, all DL radio blocks sent during this period are pegged asstalled. Stalled blocks supersede other types of transmissions of NEW, NACK and RETX blocks. For example,a NACK data block sent during a stalled window condition is treated as a stalled block and gets pegged as such.



Table 12-13 Bin ranges for DL_RLC_STALLED_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


DL_RLC_STALLED_BLKS Chapter 12: PCU statistics



(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


PeggingThis statistic counts the RLC blocks sent due to any RLC window stall in the cell. The RLC radioblocks are counted per coding scheme therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



Maintenance Information: GSM Statistics Application DL_RLC_UNACK_NEW_BLKS

DL_RLC_UNACK_NEW_BLKS

{23658}

Description

The DL_RLC_UNACK_NEW_BLKS statistic measures the total number of new RLC unacknowledgemode blocks sent for the first time by the PCU over the cell.



Table 12-14 Bin ranges for DL_RLC_UNACK_NEW_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


DL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics



(NACK, NACK) NACK

(NACK, NEW) NACK


(NEW, NEW) NEW

(NEW, ACK_PEND) NEW


(NACK, STALL) STALL

(NEW, STALL) STALL


PeggingThis statistic counts the new RLC unacknowledged radio blocks that are sent on a cell. The RLC radioblocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



Maintenance Information: GSM Statistics Application DL_TBF_TIME_1_TS

DL_TBF_TIME_1_TS

{23658}

Description

The DL_TBF_TIME_1_TS statistic counts the cumulative length in number of 20ms radio block periods ofall downlink TBFs for mobiles that support a maximum of 1 TS in the downlink direction.

PeggingThis statistic measures the time of all the TBFs in the downlink for mobiles that support amaximum of 1 TS in the downlink direction as follows:

• Always pegged for mobiles with multislot class 1.

• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 1.

• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 1.

At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF timesfor mobiles supporting a maximum of 1 TS. The TBF time is measured from the TBF set-up time tothe time the mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBFrelease phases except the very last one so as to accurately reflect the perceived throughput.

Analysis

Reference None

Usage

Basis Cell

Type Counter


DL_TBF_TIME_2_TS Chapter 12: PCU statistics

DL_TBF_TIME_2_TS

{23658}

Description



• Always pegged for mobiles with multislot class 2, 3 or 5.

• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 2,3 or 5.

• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 2, 3 or 5.


Analysis

Reference None

Usage

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application DL_TBF_TIME_3_TS

DL_TBF_TIME_3_TS

{23658}

Description



• Always pegged for mobiles with multislot class 4, 6, 7, 9, or 13.

• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 4, 6, 7, 9, or 13.

• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislotis class 4, 6, 7, 9, or 13.


Analysis

Reference None

Usage

Basis Cell

Type Counter


DL_TBF_TIME_4_TS Chapter 12: PCU statistics

DL_TBF_TIME_4_TS

{23658}

Description



• Always pegged for mobiles with multislot class 8, 10, 11, 12 or 14 through 29.

• If a GPRS TBF is assigned to the mobile and its GPRS multislot is one ofclass 8, 10, 11, 12 or 14 through 29.

• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot isone of class 8, 10, 11, 12 or 14 through 29.


Analysis

Reference None

Usage

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application EGPRS_64K_CHANNELS_SWITCHED

EGPRS_64K_CHANNELS_SWITCHED

{23658}

Description

The EGPRS_64K_CHANNELS_SWITCHED statistic counts the number of times that 64kbps EGPRStimeslots are used for circuit-switched calls in a statistics reporting period on a per-cell basis.

PeggingThis statistic pegs when a 64kbps EGPRS timeslot is successfully switched to a circuit switched call.

Analysis

Reference None

Usage

Basis Cell

Type Counter


EGPRS_64K_NOT_AVAIL Chapter 12: PCU statistics

EGPRS_64K_NOT_AVAIL

{23658}

Description

The EGPRS_64K_NOT_AVAIL statistic tracks the number of times that a TBF would havebeen able to use EGPRS coding schemes due to good radio conditions in the cell but could notbecause the mobile’s timeslot assignment was not 64k TRAU.

PeggingThis statistic pegs when an EGPRS capable mobile is allocated GPRS resources. This statisticis pegged when 64k TRAU is disabled or when the mobile is allocated GPRS timeslots and theradio conditions would allow usage of EGPRS coding schemes.

Analysis

Reference None

Usage If CS-3,4 is disabled, it counts how often CS-3,4 would have beenused resulting in increased end user throughput.

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application EGPRS_AVAIL_PDTCH

EGPRS_AVAIL_PDTCH

{23658}

Description

The EGPRS_AVAIL_PDTCH statistic measures the mean and max number of availableEGPRS Packet Data Traffic Channels (PDTCH).

This statistic is obtained by maintaining the current and total number of available EGPRS PDTCHs and theamount of time each is available over the statistical period. The PDTCH is available when its administrativestate is unlocked or shutting down and the operational state is enabled. It is unavailable when its administrativestate changes to locked or the operational state changes to disabled. The available EGPRS PDTCH countsboth reserved PDTCHs and switchable PDTCHs that are actually configured for use as an EGPRS PDTCHs.

PeggingThis statistic pegs whenever there is a change in the channel configuration for any channelin the cell (if the number of EGPRS PDTCHs has not changed within the current pegginginterval, it is pegged with the same value as before).

This statistic counts the number of timeslots available for GPRS. It treats PBCCH/PCCCH TSthe same as regular PDTCH TS, which means that each TS is counted as 1, even though 4 MScan share a regular TS, while a PBCCH/PCCCH TS can only be shared by 2 MS.

Analysis

Reference 4.60, 5.08

Usage

Basis Cell

Type Gauge


EGPRS_DL_ASGN_PCCCH Chapter 12: PCU statistics

EGPRS_DL_ASGN_PCCCH

{23658}

Description

The EGPRS_DL_ASGN_PCCCH statistic counts the total number of EGPRS packetdownlink assignments sent on the PCCCH.

PeggingThis statistic pegs whenever an EGPRS packet downlink assignment is sent on PCCCH.

Analysis

Reference None

Usage

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application G_RACH_UNSVCD_BTS

G_RACH_UNSVCD_BTS

{4441}

Description

The G_RACH_UNSVCD_BTS statistic tracks the total number of uplink GPRSRACH requests unserviced by the BTS.

The bins are:

• RSL bandwidth limitation.

• No PRR block.

• AGCH discard.

PeggingThis statistic is pegged whenever a GPRS RACH request is unserviced by the BTS.


AnalysisThis statistic can be used for the trend analysis of the BTS.

Reference None.


Basis Cell.



GBL_DL_DATA_THRPUT Chapter 12: PCU statistics

GBL_DL_DATA_THRPUT

Description

The GBL_DL_DATA_THRPUT statistic reports the quantity of data transmitted on the downlinkof the Gb link (GBL) during a given time interval. The PCU calculates the instantaneousthroughput in kilobytes per second by dividing the quantity of data transmitted by the timeinterval given by the parameter gbl_thrput_period.

PeggingThis statistic is pegged by computing a moving average in kilobytes per second of theinstantaneous throughput samples. The number of samples used for the computation isgiven by the parameter num_gbl_dl_thrput_samples.

AnalysisThis statistic can be used for the trend analysis of the average downlink throughput of the GBL.

This statistic is stored in the following columns in the gbl_statistics table:

• dl_datathrput_mean.

• dl_datathrput_max.

Reference None.


Basis GBL.

Type Gauge.


Maintenance Information: GSM Statistics Application GBL_DL_DATA_THRPUT_HIST

GBL_DL_DATA_THRPUT_HIST

Description

The GBL_DL_DATA_THRPUT_HIST statistic reports the quantity of data transmitted onthe downlink of the GBL during a given time interval.

The PCU calculates the instantaneous throughput in kilobytes per second by dividing the quantityof data transmitted by the time interval given by the parameter gbl_thrput_period.

There are 10 bins in the array. The available ranges are shown in Table 12-15.

Table 12-15 GBL_DL_DATA_THRPUT_HIST bins

Bin Range

0 0 - 30

1 31 - 70

2 71 - 110

3 111 - 140

4 141 - 170

5 171 - 230

6 231 - 300

7 301 - 400

8 401 - 500

9 501 - 600

PeggingThe GBL_DL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samplesin 10 bins. See Table 12-15 for the ranges.


GBL_DL_DATA_THRPUT_HIST Chapter 12: PCU statistics

AnalysisThis statistic can be used for the trend analysis of GBL downlink throughput.


• dl_thrput_min.

• dl_thrput_mean.

• dl_thrput_max.

Reference None.

Usage Network planning.Congestion.Quality of service monitoring: Network accessibility.

Basis GBL.

Type Normal Distribution.


Maintenance Information: GSM Statistics Application GBL_FLOW_CTRL_SENT

GBL_FLOW_CTRL_SENT

Description

The GBL_FLOW_CTRL_SENT tracks the number of flow control messages sent by theBSS to the Serving GPRS Support Node (SGSN).

Each cell has a buffer that holds downlink data. When a cell buffer reaches a predeterminedthreshold, a flow control message is sent to the SGSN.

Flow control is performed to match the flow of downlink data with air throughput.

PeggingThis statistic pegs the number of flow control messages sent by the BSS and is peggedevery time a flow control message is sent.

AnalysisThis statistic can be used for trend analysis of the number of flow control messages sent by the BSS.

Reference None.


Basis Cell.

Type Counter.


GBL_LINK_INS Chapter 12: PCU statistics

GBL_LINK_INS

Description

The GBL_LINK_INS statistic tracks the amount of time in milliseconds that a specified GBL is in service.

PeggingThe timer for this statistic starts when the GBL transitions to the B-U state (that is, returns to service). Thetimer for this statistic stops when the GBL is no longer in the B-U state (that is, goes out of service).

AnalysisThis statistic can be used for trend analysis of GBL usage.

Reference None.

Usage Network accessibility.Fault finding.Protocol utilization.

Basis GBL.

Type Duration.


Maintenance Information: GSM Statistics Application GBL_PAGING_REQS

GBL_PAGING_REQS

Description

The GBL_PAGING_REQS statistic tracks the number of paging requests received at the GBL.

PeggingThis statistic pegs each time an MS page request is received at the GBL.

AnalysisThis statistic can be used for the trend analysis of the number of circuit switched and packetswitched pages received by the BSS from the SGSN.

Reference None.


Basis PCU.

Type Counter.


GBL_UL_DATA_THRPUT Chapter 12: PCU statistics

GBL_UL_DATA_THRPUT

Description

The GBL_UL_DATA_THRPUT statistic reports the quantity of data transmitted on the uplink of the Gb link(GBL) during a given time interval. The PCU calculates the instantaneous throughput in kilobytes per secondby dividing the quantity of data transmitted by the time interval given by the parameter gbl_thrput_period.

PeggingThis statistic is pegged by computing a moving average in kilobytes per second of theinstantaneous throughput samples. The number of samples used for the computation isgiven by the parameter num_gbl_ul_thrput_samples.

AnalysisThis statistic can be used for the trend analysis of the average uplink throughput of the GBL.


• ul_datathrput_mean.

• ul_datathrput_max.

Reference None.


Basis GBL.

Type Gauge.


Maintenance Information: GSM Statistics Application GBL_UL_DATA_THRPUT_HIST

GBL_UL_DATA_THRPUT_HIST

Description

The GBL_UL_DATA_THRPUT_HIST statistic reports the quantity of data transmitted onthe uplink of the GBL during a given time interval.

The PCU calculates the instantaneous throughput in kilobytes per second by dividing the quantityof data transmitted by the time interval given by the parameter gbl_thrput_period.

PeggingThe GBL_UL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samplesin 10 bins. The ranges are shown in Table 12-16.

Table 12-16 GBL_UL_DATA_THRPUT_HIST bins

Bin Range

0 0 - 30

1 31 - 70

2 71 - 110

3 111 - 140

4 141 - 170

5 171 - 230

6 231 - 300

7 301 - 400

8 401 - 500

9 501 - 600


GBL_UL_DATA_THRPUT_HIST Chapter 12: PCU statistics

AnalysisThis statistic can be used for the trend analysis of GBL uplink throughput.


• ul_thrput_min.

• ul_thrput_mean.

• ul_thrput_max.

Reference None.


Basis GBL.



Maintenance Information: GSM Statistics Application GBL_UNAVAILABLE

GBL_UNAVAILABLE

Description

The GBL_UNAVAILABLE statistic tracks the amount of time in milliseconds that the GBL is out of service.

PeggingThe timer for this statistic is started when the GBL transitions to a state which is not B-U,that is, when he GBL goes out of service. The timer is stopped when the GBL is in theB-U state, that is, when the GBL returns to service.

AnalysisThis statistic can be used for trend analysis of the duration of GBL outages, includingthose caused by operator interaction.

Reference None.

Usage Network accessibility.Fault finding.

Basis GBL.

Type Duration.


GPRS_32K_CHANNELS_SWITCHED Chapter 12: PCU statistics

GPRS_32K_CHANNELS_SWITCHED

Description

This statistic keeps a count of the number of times that CS-3,4 capable GPRS timeslots (32k TRAU)are used for circuit-switched calls in a statistics reporting period on a per-cell basis.

PeggingThis statistic pegs when a 32kilobits per secondGPRS timeslot is successfully switched to a circuit switched call.

Reference None.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application GPRS_32K_DL_NOT_AVAIL

GPRS_32K_DL_NOT_AVAIL

Description

The GPRS_32K_DL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRStimeslots would have been switched to CS-3,4 due to good radio conditions in the cell, but couldnot because the mobile’s timeslot assignment was not 32k TRAU.

PeggingThis statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAUtimeslots and the radio conditions would allow usage of CS-3,4.

Reference None.

Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would havebeen used resulting in increased end user throughput.

Basis Cell.

Type Counter.


GPRS_32K_UL_NOT_AVAIL Chapter 12: PCU statistics

GPRS_32K_UL_NOT_AVAIL

Description

The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRStimeslots would have been switched to CS-3,4 due to good radio conditions in the cell, but couldnot because the mobile’s timeslot assignment was not 32k TRAU.

PeggingThis statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAUtimeslots and the radio conditions would allow usage of CS-3,4.

Reference None.

Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would havebeen used resulting in increased end user throughput.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application GPRS_ACCESS_PER_AGCH

GPRS_ACCESS_PER_AGCH

Description

The GPRS_ACCESS_PER_AGCH statistic tracks the number of Immediate Assignment messagessent on the Access Grant Channel (AGCH) of a cell for packet data service.

The air interface message on the AGCH for packet immediate assignment and immediateassignment reject contains only one MS.

Access Grants for more than one MS may be contained in one Access Grant message (Extended ImmediateAssignment). An Access Grant for more than one MS is only pegged once. This count includes ImmediateAssignment, Immediate Extended, and Immediate Assignment Reject messages sent on the AGCH of a cell.

PeggingThis statistic is pegged when an access grant message is sent on the AGCH on a cell for packet data service.

AnalysisThis statistic can be used for trend analysis of Immediate Assignment messages sent on the AGCH of a cell.

Reference None.


Basis Cell.

Type Counter.


GPRS_ACCESS_PER_RACH Chapter 12: PCU statistics

GPRS_ACCESS_PER_RACH

Description

The GPRS_ACCESS_PER_RACH statistic tracks the number of packet switched Channel Requestmessages successfully received on the Random Access CHannel (RACH) for GPRS purposes.

PeggingThis statistic pegs when a packet switched Channel Request message is sent on theRandom Access CHannel (RACH) of a cell.


AnalysisThis statistic can be used for trend analysis of Immediate Assignment messages sent on the RACH of a cell.

Reference None.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application GPRS_AVAIL_PDTCH

GPRS_AVAIL_PDTCH

This statistic was previously named AVAILABLE_PDTCH.

Description

This statistic measures the mean and max number of available Packet Data Traffic CHannels (PDTCH).

{3723} This statistic considers a PBCCH/PCCCH timeslot as a PDTCH therefore these will berecorded by the statistic in its total number of available channels.

This statistic is obtained by maintaining the current and total number of available PDTCH and the amount oftime each PDTCH is available over the statistical period. The corresponding mean and maximum number ofPDTCH are then computed. The PDTCH is available when its administrative state is unlocked or shuttingdown and the operational state is enabled. It is unavailable when its administrative state changes to lockedor the operational state changes to disabled. The available number of PDTCH is then incremented ordecremented when there is a change in PDTCH states as described above. The available PDTCH counts bothreserved PDTCHs and switchable PDTCHs that are actually configured as PDTCHs and not as TCHs.

The number of PDTCH = Number of switchable PDTCHs (configured as PDTCHs)+ Number of reserved PDTCHs

PeggingThe statistic pegs whenever there is a change in the channel configuration for any channelin the cell (if the number of PDTCHs has not changed within the current pegging interval,it will be pegged with the same value as before).

This statistic counts the number of timeslots available for GPRS. It treats PBCCH/PCCCH TSthe same as regular PDTCH TS, which means that each TS is counted as 1, even though 4 MScan share a regular TS, while a PBCCH/PCCCH TS can only be shared by 2 MS.


GPRS_AVAIL_PDTCH Chapter 12: PCU statistics

AnalysisThis statistic can be used for trend analysis of PDTCH availability.

By comparing the number of available PDTCHs to the total number of PDTCHs in a cell, a percentageof GPRS availability in a cell can be calculated. An analysis of the utilization information can beused to determine the requirement for additional resources before problems occur.



Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application GPRS_CELL_RESELECT_ATTMPT

GPRS_CELL_RESELECT_ATTMPT

Description

The GPRS_CELL_RESELECT_ATTMPT statistic tracks the number of Network Controlledcell reselection attempts from the originating cell.

PeggingThis statistic pegs whenever the network sends a packet cell change order message tothe mobile station (in idle or transfer mode).


AnalysisThis statistic can be used for analysis of Network Controlled cell reselect attempts from an originating cell.

Reference None.


Basis Cell.

Type Counter.


GPRS_CELL_RESELECT_FAIL Chapter 12: PCU statistics

GPRS_CELL_RESELECT_FAIL

Description

The GPRS_CELL_RESELECT_FAIL statistic tracks the number of Network Controlled cellreselect failures from the originating cell. Retries are not counted.

PeggingThis statistic pegs when a Packet Cell Change Failure message is sent by an MS.


AnalysisThis statistic can be used for analysis of Network Controlled cell reselect failures from an originating cell.

Reference None.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application GPRS_CHANNELS_SWITCHED

GPRS_CHANNELS_SWITCHED

Description

This statistic reports the number of times a 16 kilobits per second Packet Data Traffic Channel(PDTCH) has been switched to a circuit switched Traffic Channel (TCH).

PeggingThis statistic pegs when a 16 kilobits per second PDTCH is switched to a circuit switched TCH.

Reference None.


Basis Cell.

Type Counter.


GPRS_DL_ASGN_PCCCH Chapter 12: PCU statistics

GPRS_DL_ASGN_PCCCH

{3723}

Description

This statistic tracks the total number of packet downlink assignment messages received onthe Packet Common Control Channel (PCCCH).

PeggingThis statistic pegs once per packet downlink assignment on the PCCCH.



Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application GPRS_DYNET_FAILURES

GPRS_DYNET_FAILURES

Description

The GPRS_DYNET_FAILURES statistic tracks the totals for four different sourcesof terrestrial backing failure.

The sources of terrestrial backing failure are listed below.

• Terrestrial resource for a reserved GPRS timeslot is not provided when requested.

• Terrestrial backing is taken from switchable timeslots. This happens foremergency and non-emergency calls.

• Terrestrial backing is taken from reserved timeslots. This happens foremergency calls and link failures only.

• When converting a switchable GPRS timeslot from packet to circuit modeand terrestrial backing is unavailable.

There are 4 bins for this array. The ranges are shown in Table 12-17.

Table 12-17 GPRS_DYNET_FAILURES bins


0 RSV_GPRS_BLK Resource unavailable for a reserved timeslot

1 SW_GPRS_PREEMP Resource stolen from a switchable timeslot

2 RSV_GPRS_PREEMP Resource stolen from a reserved timeslot

3 CHANGEOVER_CS_FAIL Changeover to CS mode failed - resourcesreserved

PeggingThis statistic is pegged only when both dynamic allocation and GPRS are unrestricted. Thisstatistic is not pegged if either feature is restricted.


GPRS_DYNET_FAILURES Chapter 12: PCU statistics

AnalysisThis statistic can be used to analyse how effectively terrestrial backing resources are allocatedfor a particular site. Bin counts can be observed to determine the effects of blocking,preemption, and unavailable terrestrial resources with GPRS.

Reference None.

Usage Network planning.Network accessibility.

Basis Dynet.

Type Counter array.


Maintenance Information: GSM Statistics Application GPRS_DYNET_RES_REQS

GPRS_DYNET_RES_REQS

Description

The GPRS_DYNET_RES_REQS statistic tracks the time that the number of requests for backing ofreserved timeslots were in the queue. Each bin corresponds to a range of queue lengths.


Table 12-18 GPRS_DYNET_RES_REQS bins

Bin Range

0 0 - 5

1 6 - 10

2 11 - 15

3 16 - 20

4 21 - 25

5 26 - 30

6 31 - 35

7 36 - 40

8 41 - 45

9 46 - 50

PeggingWhen this statistic is pegged, the bin corresponding to the length of the queue is incremented by one.The maximum and minimum queue length and the average queue length is reported.

Reference None.


Basis Dynet.



GPRS_DYNET_SWI_REQS Chapter 12: PCU statistics

GPRS_DYNET_SWI_REQS

Description

The GPRS_DYNET_SWI_REQS statistic tracks the time that the number of requests forterrestrial backing of switchable GPRS timeslots were in the Dynamic Allocation queue.Each bin corresponds to a range of queue lengths.


Table 12-19 GPRS_DYNET_SWI_REQS bins

Bin Range

0 0 - 5

1 6 - 10

2 11 - 15

3 16 - 20

4 21 - 25

5 26 - 30

6 31 - 35

7 36 - 40

8 41 - 45

9 46 - 50

PeggingWhen this statistic is pegged, the bin corresponding to the length of the queue is incremented by one.The maximum and minimum queue length and the average queue length are reported.

Reference None.


Basis Dynet.



Maintenance Information: GSM Statistics Application GPRS_MS_NEIGHBOR_STRONG

GPRS_MS_NEIGHBOR_STRONG

Description

The GPRS_MS_NEIGHBOR_STRONG statistic tracks the number of GPRS MS(s) for which the rxlevof any neighbour cell is stronger by a certain threshold than the rxlev of the serving cell.

PeggingThis statistic pegs in NC2, whenever a Packet Measurement Report is received from an MS.


AnalysisThis statistic is obtained by measuring the number of GPRS MS/s for which the receive level (rxlev)of any neighbour cell is stronger than the rxlev of the serving cell by a defined threshold in the PacketMeasurement Report message. The counter is incremented only once for an MS if the multiplePacket Measurement Report shows a better rxlev than the serving cell.

Reference None.


Basis Cell.

Type Counter.


GPRS_PCH_AGCH_Q_LENGTH Chapter 12: PCU statistics

GPRS_PCH_AGCH_Q_LENGTH

Description

This statistic measures the mean Paging CHannel-Access Grant CHannel (PCH-AGCH) queue length.This statistic is obtained by measuring the arithmetic mean of the number of all messages waiting fortransmission on the PCH-AGCH, for GPRS purpose. This measurement is obtained once in every pagingmulti frame, taking the PCH-AGCH queue length and then taking the arithmetic mean.



AnalysisThe 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.


Usage This statistic is used to assess the impact of GPRS messaging onthe CCCH. For example, the operator could use the statistic tomonitor the growth of GPRS in an area, and possibly replan pagingparameters to account for an increase in GPRS users on the network.

Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application GPRS_PPCH_PAGCH_Q_LENGTH

GPRS_PPCH_PAGCH_Q_LENGTH

{3723}

Description

This statistic measures the mean and max of the number of all messages waiting in the PacketPaging Channel-Packet Access Grant Channel (PPCH-PAGCH) queue. This statistic is obtainedby measuring the arithmetic mean of the number of all messages waiting for transmission onthe PPCH-PAGCH. This measurement is obtained once in every paging multi frame, taking thePPCH-PAGCH queue length and then taking the arithmetic mean.


AnalysisThe 12.04 statistic B.2.1.1 is the mean of the number of messages in the PPCH-PAGCH queue.


Usage This statistic is used to assess the impact of GPRS messaging onthe PPCH. For example, the operator could use the statistic tomonitor the growth of GPRS in an area, and possibly replan pagingparameters to account for an increase in GPRS users on the network.

Basis Cell.

Type Gauge statistic.


GPRS_PRR_BLK_USG Chapter 12: PCU statistics

GPRS_PRR_BLK_USG

{4441}

Description

TheGPRS_PRR_BLK_USG statistic tracks the mean, minimum, and maximum number of PRR block usage.

The bin ranges may be changed using the chg_stat_prop command. The default bin ranges forthe GPRS_PRR_BLK_USG statistic are shown in Table 12-20.

Table 12-20 Default bin ranges for GPRS_PRR_BLK_USG

Bin Range

0 0 to 2

1 3 to 5

2 6 to 10

3 11 to 20

4 21 to 40

5 41 to 60

6 61 to 80

7 81 to 100

8 101 to 125

9 126 to 160

PeggingThis statistic is measured by obtaining the PRR block usage at a predefined interval: approximatelyone second (four multiframes) and updating the appropriate bin. At the end of the report of the statisticalinterval, the mean, minimum, and maximum PRR block usage is reported.



Maintenance Information: GSM Statistics Application GPRS_PRR_BLK_USG

Analysis

Reference None.


Basis Cell.



GPRS_RACH_ARRIVAL Chapter 12: PCU statistics

GPRS_RACH_ARRIVAL

{4441}

Description

The GPRS_RACH_ARRIVAL statistic tracks the mean, minimum, and maximum numberof GPRS RACH request arrivals over CCCH.

The bin ranges may be changed using the chg_stat_prop command. The default bin rangesfor the GPRS_RACH_ARRIVAL statistic are shown in

Table 12-21 Default bin ranges for GPRS_RACH_ARRIVAL

Bin Range

0 0 to 2

1 3 to 5

2 6 to 10

3 11 to 20

4 21 to 40

5 41 to 60

6 61 to 80

7 81 to 100

8 101 to 125

9 126 to 160

PeggingThis statistic is measured by sampling the GPRS RACH over CCCH at a predefined interval:approximately one second (four multiframes). The total GPRS RACH requests over CCCH duringthe time is obtained and the appropriate bin is updated. At the end of the report of the statisticalinterval, the mean, minimum, and maximum PRR block usage is reported.



Maintenance Information: GSM Statistics Application GPRS_RACH_ARRIVAL

Analysis

Reference None.


Basis Cell.



IDLE_PDTCH_INTF_BAND0 Chapter 12: PCU statistics

IDLE_PDTCH_INTF_BAND0

Description

The IDLE_PDTCH_INTF_BAND0 statistic tracks the maximum and mean number of idle uplinkPacket Data Traffic CHannels (PDTCHs) for interference band 0. An idle PDTCH falls into band 0 ifits average interference band is less than the value of the element interfer_bands, 0.

Idle PDTCHs are allocated to five interference bands. Each band has an associatedstatistic for tracking idle PDTCHs.

PeggingThis statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocatedfor a request. An idle PDTCH will fall into band 0 if its idle interference level is less than the valueof the elements interfer_bands 0. The mean and max are calculated from the samples.

AnalysisThis statistic can be used for trend analysis of idle packet data traffic channels.

Reference Digital cellular telecommunications systems (phase 2+) Version7.0.0 Jan 2000 ETSI..


Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND1


Description







Basis Cell.

Type Gauge.




Description







Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND3


Description







Basis Cell.

Type Gauge.




Description







Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application IMM_ASSGN_CAUSE

IMM_ASSGN_CAUSE

Description

This statistic measures the successful immediate assignment procedures, per cause. This statistic is obtainedby measuring the number of IMMEDIATE ASSIGN COMMAND messages transmitted, per cause. Thismessage contains either an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENTEXTENDED message. If an IMMEDIATE ASSIGNMENT EXTENDED message is transmitted, thecounter is incremented by two, because it contains assignment information for two MSs otherwise the counteris incremented by one. The associated bins, identifiers and establishment causes are defined in Table 12-22.

Table 12-22 IMM_ASSGN_CAUSE bins


0 orig_call Originating call.

1 emer_call Emergency call.

2 call_re_estb Call re-establishment.

3 loc_upd Location updating.

4 page_resp Paging response.

5 ul_pack_access_gprs GPRS - uplink packet access.

6 dl_pack_access_gprs GPRS - downlink packet access.

7{23658} ul_pack_access_egprs EGPRS uplink packet access

8{23658} dl_pack_access_egprs EGPRS downlink packet access

PeggingThis statistic is pegged once for every time the BSS sends an Immediate Assignment (IA) for any ofthe specified purposes over the air. IAs for other purposes are not pegged.

This statistic pegs the cause of each IMMEDIATE ASSIGN COMMAND message. If this messagecontains an IMMEDIATE ASSIGNMENT message, the cause is pegged once. If this message containsan IMMEDIATE ASSIGNMENT EXTENDED message, the cause is pegged twice.


IMM_ASSGN_CAUSE Chapter 12: PCU statistics

AnalysisIt represents the total number of IAs pegged during the statistics interval, on a per-cause basis.


Usage The statistic is used for monitoring areas where lots of callsoriginate: the operator may wish to charge more for calls made inthese high-traffic zones.It is also used for monitoring the number of calls undergoingre-establishment. High numbers of calls undergoingre-establishment means the RF coverage in an area may have a hole.Comparing the uplink against downlink GPRS usage tells theoperator how to set the Beta value for a cell (Interleaving TBFsfeature). This allows for better throughput based upon the mobilesubscriber preferences in any particular area.

Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application MS_CLASS_1_10_REQ

MS_CLASS_1_10_REQ


Description

TheMS_CLASS_1_10_REQ statistic tracks the number of requests received for the MS classes 1 through 10.

Each bin corresponds to a particular MS class as shown in Table 12-23.

Table 12-23 MS_CLASS_1_10_REQ bins


0 MS_CLASS_1_REQ Number of requests for class 1










PeggingThis is one of three statistics that is pegged every time there is an uplink request from an MS. Theother two are MS_CLASS_11_20_REQ and MS_CLASS_21_29_REQ.


MS_CLASS_1_10_REQ Chapter 12: PCU statistics

Pegging is performed only for uplink requests received on the CCCH, not foruplink requests included in the PDAK message.

Reference GSM 05.02, 6.2.0, Annex B.


Basis Cell.

Type Counter array.



MS_CLASS_11_20_REQ


Description

TheMS_CLASS_11_20_REQ statistic tracks the number of requests received for theMS classes 11 through 20.














PeggingThis is one of three stats that is pegged every time there is an uplink request from an MS. Theother two are MS_CLASS_1_10_REQ and MS_CLASS_21_29_REQ.






Basis Cell.

Type Counter array.



MS_CLASS_21_29_REQ


Description

The MS_CLASS_21_29_REQ statistic tracks the number of requests received forthe MS classes 21 through 29.













PeggingThis is one of three stats that is pegged every time there is an uplink request from an MS. Theother two are MS_CLASS_1_10_REQ and MS_CLASS_11_20_REQ.






Basis Cell.

Type Counter array.


Maintenance Information: GSM Statistics Application NO_PDTCH_AVAIL

NO_PDTCH_AVAIL

Description

The NO_PDTCH_AVAIL statistic counts the number of times neither switchablenor reserved PDTCHs are available.

PeggingWhen the last PDTCH available is taken for a voice call, the count is incremented.

Reference None.


Basis Cell.

Type Counter.


NO_PDTCH_AVAIL_TIME Chapter 12: PCU statistics

NO_PDTCH_AVAIL_TIME

Description

The NO_PDTCH_AVAIL_TIME statistic measures the amount of time in 20 millisecondperiods during the statistical collection period (between timer start and stop), when neitherswitchable nor reserved PDTCHs are available.

PeggingWhen the last PDTCH available is taken for a voice call, the timer is started and stoppedwhen at least one PDTCH becomes available.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum acceptable time that noPDTCHs are available for any of the start/stop time periods. If the specified threshold is exceeded, theTotal time all PDTCHs are unavailable - PM alarm is generated. Refer to the Maintenance Information:Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.

Reference None.


Basis Cell.

Type Duration.


Maintenance Information: GSM Statistics Application PRP_LOAD

PRP_LOAD

Description

This statistic measures the load of the Packet Resource Processor (PRP) board. The BSS transfersdata for 30 DL and 30 UL TBFs, and processes control messages for 90 UL and 90 DL TBFs in one20 millisecond block period. The load of the PRP board is determined by measuring the number oftimeslots pending service for data transfers within a 20 millisecond block period.

Table 12-26 shows the mapping between the number of timeslots pending service and the PRP load.

The statistic is kept on a per DPROC basis.

Table 12-26 Mapping between timeslots pending service and PRP load

Number of timeslots pending servicein a 20 msec block period PRP Load

0-30 0-100

31-60 101-200

61-90 201-300

91-120 301-400

Table 12-27 shows the PRP load ranges for each bin of this statistic.

Table 12-27 PRP load range

Bin Min Max

1 0 2

2 3 5

3 6 10

4 11 20

5 21 40

6 41 60

7 61 100

8 101 160

9 161 260

10 261 400


PRP_LOAD Chapter 12: PCU statistics

PeggingThis statistic pegs the appropriate bin every 20 millisecond based on the number of timeslotspending service and the bin range values that the customer configured.


AnalysisThis statistic can be used for trend analysis of the network load on a PRP board. Each bin can be analysedto determine the number of occurrences the PRP had a certain percentage of load on it.

Reference None.


Basis This statistic is based on each DPROC.



Maintenance Information: GSM Statistics Application UL_BUSY_PDTCH

UL_BUSY_PDTCH

Description

This statistic measures the mean, max and min number of occupied Packet DataCHannel (PDCH) carrying uplink packet traffic.

This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, atevery packet-scheduling period (20 millisecond).

Table 12-28 shows the ranges for each bin (measured in milliseconds).

Table 12-28 UL_BUSY_PDTCH bins

Bin Range

0 No PDTCH is busy










PeggingThis statistic pegs every packet-scheduling period (20 millisecond) by sampling the numberof PDTCHs that are carrying uplink packet traffic.



UL_BUSY_PDTCH Chapter 12: PCU statistics

AnalysisThis statistic can be used for trend analysis of the number of PDTCHs that are used for uplink packet traffic.



Basis Cell.



Maintenance Information: GSM Statistics Application UL_PDTCH_CONGESTION

UL_PDTCH_CONGESTION

Description

The UL_PDTCH_CONGESTION statistic calculates the number of times a cell is congested due toMS load on the available air resources on the uplink. Whenever the uplink resources are determinedto be congested, the statistic is updated. When the value of the statistic is large, it indicates thatthe cell is congested and more radio resources may need to be provisioned.

PeggingThe PDTCH congestion is computed every 8s (8000ms) in 20ms block periods when the congestion thresholdis reached. The congestion threshold is configurable with values ranging from 1-4. Level 1 means averagelyone TBF per TS on a cell is considered congested. Level 4 means four TBFs per TS are considered congested.This is synonymous with the concept that one PDTCH can be shared by, at most, 4 MSs.


AnalysisThis statistic is totalled in terms of 20 millisecond block periods.



Basis Cell.

Type Counter.


UL_PDTCH_Q_LENGTH Chapter 12: PCU statistics

UL_PDTCH_Q_LENGTH

Description

This statistic is obtained by sampling the Uplink Request Queue. Queued messagesare RACH, PRACH and PRR.

PeggingThis statistic pegs every 20ms. It is incremented when a request is added to the queue and isdecremented when a request is processed, that is, leaves the queue.


AnalysisThis statistic can be used for the trend analysis of the average number of uplink messageswaiting for a PDTCH to become available.

This statistic can be used for trend analysis of the number of queued uplink PDTCH requests.



Basis Cell.

Type Gauge.


Maintenance Information: GSM Statistics Application UL_PDTCH_SEIZURE

UL_PDTCH_SEIZURE

Description

This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the uplink. The purposeof this statistic is to count the number of temporary block flows (TBF) on the uplink. The statistic is obtainedby measuring the receipt of the first RLC block (PDU) on the PDTCH from the MS (uplink).

PeggingThis statistic pegs when the receipt of the first uplink RLC block (PDU) on the PDTCH from theMS is obtained.

This statistic pegs when:

• The first uplink data block is received during a two-phase uplink TBF establishment.

• A first uplink data block containing a valid Temporary Logical Link Identity (TLLI)is received during a one-phase uplink TBF establishment.


AnalysisThis statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.



Basis Cell.

Type Counter.


UL_RADIO_BLKS_8PSK_1_TS Chapter 12: PCU statistics

UL_RADIO_BLKS_8PSK_1_TS

{23658}

Description

The UL_RADIO_BLKS_8PSK_1_TS statistic counts the total number of RLC radio blocksreceived from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 1 TSin the uplink direction (mobile multislot classes 1, 2, 4, and 8).

100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translationof actual radio blocks counted to units is performed at the end of the interval.

The RLC radio blocks are split into the four GPRS coding schemes (CS-1 through CS-4) and nineEGPRS coding schemes (MCS-1 through MCS-9), as shown in Table 12-29.

Table 12-29 Bin ranges for UL_RADIO_BLKS_8PSK_1_TS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_8PSK_1_TS


(RLC block 1, RLC block 2) UL radio block status

(NEW, RETRANS) NEW

(RETRANS, NEW) NEW

(RETRANS, RETRANS) RETRANS

PeggingThis statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplinkthat support a maximum 1 TS in the uplink direction. Only RLC radio blocks are counted. Noretransmissions due to any cause shall be pegged in this statistic. The RLC radio blocks arecounted per coding scheme, therefore pegging the appropriate bin.

This statistic also pegs for 8PSK mobiles whose multislot class is not known before the end of the ULTBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.

Analysis

Reference None

Usage

Basis Cell



UL_RADIO_BLKS_8PSK_2_TS Chapter 12: PCU statistics

UL_RADIO_BLKS_8PSK_2_TS

{23658}

Description

The UL_RADIO_BLKS_8PSK_2_TS statistic counts the total number of RLC radio blocksreceived from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 2 TSin the uplink direction (mobile multislot classes 3, 5, 6, 9, and 10).

100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translationof actual radio blocks counted to units is performed at the end of the interval.

The RLC radio blocks are split into the four GPRS coding schemes (CS-1 through CS-4) and nineEGPRS coding schemes (MCS-1 through MCS-9), as shown in Table 12-30.

Table 12-30 Bin ranges for UL_RADIO_BLKS_8PSK_2_TS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_8PSK_2_TS



(NEW, RETRANS) NEW

(RETRANS, NEW) NEW


Multislot class 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.



PeggingThis statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplinkthat support a maximum 2 TS in the uplink direction. Only RLC radio blocks are counted. Noretransmissions due to any cause are pegged in this statistic. The RLC radio blocks are countedper coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



UL_RADIO_BLKS_GMSK_1_TS Chapter 12: PCU statistics

UL_RADIO_BLKS_GMSK_1_TS

{23658}

Description

The UL_RADIO_BLKS_GMSK_1_TS statistic counts the total number of RLC radio blocks received fromGPRS and EGPRS mobiles that support a maximum of 1 TS in the uplink direction (mobile multislotsclasses 1, 2, 4 and 8). The EGPRS mobile is not capable of supporting 8PSK in the uplink.

This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF. Theaccuracy of this statistic may be reduced due to these unknown multi-slot cases.


The RLC radio blocks are split into the four GPRS channel coding schemes, and the fourGMSK EGPRS coding schemes, as shown in Table 12-31.

Table 12-31 Bin ranges for UL_RADIO_BLKS_GMSK_1_TS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

PeggingThis statistic counts the RLC radio blocks for mobiles that support a maximum of 1 TS in the uplink direction.Only RLC radio block is counted. No retransmissions due to any cause are pegged in this statistic. TheRLC radio blocks are counted per coding scheme therefore pegging the appropriate bin.


Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_GMSK_1_TS

Analysis

Reference None

Usage

Basis Cell

Type Medium counter array


UL_RADIO_BLKS_GMSK_2_TS Chapter 12: PCU statistics

UL_RADIO_BLKS_GMSK_2_TS

{23658}

Description

The UL_RADIO_BLKS_GMSK_2_TS statistic counts the total number of RLC radio blocks receivedfrom GPRS mobiles and EGPRS mobiles not capable of supporting 8PSK in the uplink that supporta maximum of 2 TS in the uplink direction (mobile multislot classes 3, 5, 6, 9 and 10).

This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF. Theaccuracy of this statistic may be reduced due to these unknown multi-slot cases.


The RLC radio blocks are split into the four GPRS channel coding schemes and the fourGMSK EGPRS coding schemes, as shown in Table 12-32.

Table 12-32 Bin ranges for UL_RADIO_BLKS_GMSK_2_TS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

Multislot class 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.



PeggingThis statistic counts the RLC radio blocks for mobiles that support a maximum of 2 TS in the uplink direction.Only RLC radio blocks are counted. No retransmissions due to any cause are pegged in this statistic. TheRLC radio blocks are counted per coding scheme therefore pegging the appropriate bin.


Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_GMSK_2_TS

Analysis

Reference None

Usage

Basis Cell

Type Medium counter array


UL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics

UL_RLC_ACK_NEW_BLKS

{23658}

Description

The UL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledgemode blocks received by the PCU over the cell.



Table 12-33 Bin ranges for UL_RLC_ACK_NEW_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application UL_RLC_ACK_NEW_BLKS



(NEW, RETRANS) NEW

(RETRANS, NEW) NEW


PeggingThis statistic counts the new RLC acknowledged radio blocks that are received on a cell. The RLCradio blocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



UL_RLC_RETX_BLKS Chapter 12: PCU statistics

UL_RLC_RETX_BLKS

{23658}

Description

The UL_RLC_RETX_BLKS statistic measures the total number of pre-emptive retransmissions (or ackpending blocks and acknowledged retransmissions) received by the PCU over the cell.



Table 12-34 Bin ranges for UL_RLC_RETX_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application UL_RLC_RETX_BLKS



(NEW, RETRANS) NEW

(RETRANS, NEW) NEW


PeggingThis statistic counts the RLC ack pending (or pre-emptive transmissions) radio blocks that are received on acell. The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



UL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics

UL_RLC_UNACK_NEW_BLKS

{23658}

Description

The UL_RLC_UNACK_NEW_BLKS statistic measures the total number of new RLCunacknowledge mode blocks received by the PCU over the cell.



Table 12-35 Bin ranges for UL_RLC_UNACK_NEW_BLKS

Bin Range

0 CS-1

1 CS-2

2 CS-3

3 CS-4

4 MCS-1

5 MCS-2

6 MCS-3

7 MCS-4

8 MCS-5

9 MCS-6

10 MCS-7

11 MCS-8

12 MCS-9


Maintenance Information: GSM Statistics Application UL_RLC_UNACK_NEW_BLKS



(NEW, RETRANS) NEW

(RETRANS, NEW) NEW


PeggingThis statistic counts the new RLC unacknowledged radio blocks that are received on a cell. The RLCradio blocks are counted per coding scheme, therefore pegging the appropriate bin.

Analysis

Reference None

Usage

Basis Cell



UL_TBF_TIME_8PSK_1_TS Chapter 12: PCU statistics

UL_TBF_TIME_8PSK_1_TS

{23658}

Description

The UL_TBF_TIME_8PSK_1_TS statistic measures the duration in time (the cumulative lengthin number of 20ms radio block periods) of the uplink TBFs for EGPRS mobiles that support amaximum of 1 TS and capable of 8PSK in the uplink direction.

PeggingThis statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum of 1 TSand capable of 8PSK in the uplink direction. At the end of the statistical interval this statistic provides acumulative value of all the UL TBF times for mobiles supporting a maximum of 1 TS. The TBF time startswith the set-up of the TBF and finishes when all the uplink RLC radio blocks have been received without error.

This statistic also pegs for 8PSK mobiles whose multislot class is not known before the end of the ULTBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.

Analysis

Reference None

Usage

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application UL_TBF_TIME_8PSK_2_TS

UL_TBF_TIME_8PSK_2_TS

{23658}

Description

The UL_TBF_TIME_8PSK_2_TS statistic measures the duration in time (the cumulative lengthin number of 20ms radio block periods) of the uplink TBFs for EGPRS mobiles that support amaximum of 2 TS and capable of 8PSK in the uplink direction.

PeggingThis statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum of 2 TSand capable of 8PSK in the uplink direction. At the end of the statistical interval this statistic provides acumulative value of all the UL TBF times for mobiles supporting a maximum of 2 TS. The TBF time startswith the set-up of the TBF and finishes when all the uplink RLC radio blocks have been received without error.

Analysis

Reference None

Usage

Basis Cell

Type Counter


UL_TBF_TIME_GMSK_1_TS Chapter 12: PCU statistics

UL_TBF_TIME_GMSK_1_TS

{23658}

Description

The UL_TBF_TIME_GMSK_1_TS statistic counts the cumulative length in number of 20msradio block periods of all uplink TBFs for mobiles that support a maximum of 1 TS in theuplink direction and not capable of supporting 8PSK in the uplink.

This statistic also pegs for mobiles whose multislot class is not known before the end of the UL TBF.The accuracy of this statistic may be reduced due to these unknown multislot cases.

PeggingThis statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum of 1 TSin the uplink direction. At the end of the statistical interval this statistic provides a cumulative value of allthe UL TBF times for mobiles supporting a maximum of 1 TS. The TBF time starts with the set-up ofthe TBF and finishes when all the uplink RLC radio blocks have been received without error.

Analysis

Reference None

Usage

Basis Cell

Type Counter


Maintenance Information: GSM Statistics Application UL_TBF_TIME_GMSK_2_TS

UL_TBF_TIME_GMSK_2_TS

{23658}

Description

The UL_TBF_TIME_GMSK_2_TS statistic counts the cumulative length in number of 20ms radioblock periods of all uplink TBFs for GPRS and EGPRS mobiles that support a maximum of 2 TS in theuplink direction. The EGPRS mobile is not capable of supporting 8PSK in the uplink.

PeggingThis statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum of 2 TSin the uplink direction. At the end of the statistical interval this statistic provides a cumulative value of allthe UL TBF times for mobiles supporting a maximum of 2 TS. The TBF time starts with the set-up ofthe TBF and finishes when all the uplink RLC radio blocks have been received without error.

Analysis

Reference None

Usage

Basis Cell

Type Counter


UL_TBF_TIME_GMSK_2_TS Chapter 12: PCU statistics



Chapter

13BSS-SMLC statistics

BSS-based Serving Mobile Location Centre (SMLC) statistics track events on the signallinglink. They are categorized into subgroups, each of which are described in "BSS-basedSMLC statistics subgroups" on page 13-2.


BSS-based SMLC statistics subgroups Chapter 13: BSS-SMLC statistics

BSS-based SMLC statistics subgroups

BSS-based Serving Mobile Location Centre (SMLC) statistics are organized into two major subgroups:

• "BSS C7 utilization" on page 13-2.

• "SCCP performance & utilization" on page 13-2.

BSS C7 utilization

BSS-based SMLC C7 utilization statistics track the number of messages received and transmittedon the signalling links. This information indicates the activity level on the Signalling Links(SLs). The following are BSS C7 utilization statistics:

• "L_SIF_SIO_RX_OPC" on page 13-8.

• "L_SIF_SIO_TX_DPC" on page 13-9.

• "L_SIF_SIO_TYPE" on page 13-10.

SCCP performance & utilization

SCCP performance and utilization statistics track the performance of the Signalling ConnectionControl Part (SCCP) protocol layer of the ITU-TSS C7.

The SCCP manages the establishment and release of call related connections. A connection isestablished for each transaction. For example, location update and service request, both BSS andBSS-based SMLC maintain contexts related to the transaction; these contexts may be identified usingthe SCCP reference number. This information indicates the performance level and quality of theSCCP. The following are the SCCP performance and utilization statistics:

• "L_ROUTING_SYNTAX" on page 13-3.

• "L_ROUTING_UNKNOWN" on page 13-4.

• "L_SCCP_MSGS" on page 13-5.

• "L_SCCP_MSGS_RX" on page 13-6.

• "L_SCCP_MSGS_TX" on page 13-7.

• "L_SIF_SIO_RX_OPC" on page 13-8.

• "L_SIF_SIO_TX_DPC" on page 13-9.

• "L_SIF_SIO_TYPE" on page 13-10.

• "PAGE_REQ_FROM_SMLC_FAIL" on page 13-11.


Maintenance Information: GSM Statistics Application L_ROUTING_SYNTAX

L_ROUTING_SYNTAX

Description

This statistic tracks the number of SCCP messages with syntax errors.

PeggingThis statistic pegs when a syntax error is detected in an SCCP message on the Lb-interface.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-basedSMLC. Excessive syntax errors can result in degraded SCCP performance.

A threshold value should be assigned to this statistic which reflects the maximum number of SCCPmessages with syntax errors that are acceptable in normal system operations.

If the specified threshold is exceeded, the 18. BSS: Routing failure - syntax error detected(SMLC) - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis BSS.

Type Counter.

Alarm Warning.


L_ROUTING_UNKNOWN Chapter 13: BSS-SMLC statistics

L_ROUTING_UNKNOWN

Description

This statistic tracks the number of invalid signalling point codes (SPCs) that a BSChas received from the BSS-based SMLC.

PeggingThis statistic pegs whenever an invalid SPC is received from the BSS-based SMLC.

AnalysisAn SPC is the destination address for a message routed by the networking functions of the MTP3 protocol.If the BSC receives an incorrect SPC, it will not be able to correctly route the message.

A threshold value should be assigned to this statistic which reflects the maximum number ofinvalid SPCs that are acceptable in normal system operations.

If the specified threshold is exceeded, the 19. BSS: Routing failure - reason unknown(SMLC) - PM alarm is generated. Refer to the Maintenance Information: Alarm Handlingat the OMC-R (68P02901W26) for troubleshooting information.



Basis BSS.

Type Counter.

Alarm Warning.


Maintenance Information: GSM Statistics Application L_SCCP_MSGS

L_SCCP_MSGS

Description

This statistic tracks the total number of SCCP messages either transmitted or received betweenthe BSC and BSS-based SMLC over an Lb-interface.

PeggingThis statistic pegs when SCCP messages are transmitted or received on the signallinglink between the BSC and BSS-based SMLC.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based SMLC.This statistic can be used for trend analysis of SCCP performance and utilization.



Basis BSS.

Type Counter.


L_SCCP_MSGS_RX Chapter 13: BSS-SMLC statistics

L_SCCP_MSGS_RX

Description

This statistic tracks the total number of SCCP messages received by the BSC from BSS-basedSMLC over an Lb-interface for class 0 or class 2.

This statistic will switch on the appropriate device value so that the OMC can storeit in the relevant column of the database:

• the number of SCCP messages received for class 0 will be stored in l_sccp_msgs_rx_0.

• the number of SCCP messages received for class 2 will be stored in l_sccp_msgs_rx_2.

PeggingThis statistic pegs when SCCP messages are received on the signalling link betweenthe BSC and BSS-based SMLC.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-basedSMLC. This statistic can be used for trend analysis of the activity on an SL.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application L_SCCP_MSGS_TX

L_SCCP_MSGS_TX

Description

This statistic tracks the total number of SCCP messages transmitted by the BSC to BSS-basedSMLC over the Lb-interface for class 0 or class 2.


• the number of SCCP messages transmitted for class 0 will be stored in l_sccp_msgs_tx_0.

• the number of SCCP messages transmitted for class 2 will be stored in l_sccp_msgs_tx_2.

PeggingThis statistic pegs when SCCP messages are transmitted on the signalling link.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-basedSMLC. This statistic can be used for trend analysis of the activity over the Lb-interface.



Basis BSS.

Type Counter.


L_SIF_SIO_RX_OPC Chapter 13: BSS-SMLC statistics

L_SIF_SIO_RX_OPC

Description

This statistic tracks the total number of SIF and SIOs received on all SLs for the BSS from BSS-based SMLC.

PeggingThis statistic pegs each time Signal Information Fields (SIF) or Service Information Octets (SIO) arereceived across all signalling links between the BSS and BSS-based SMLC.

AnalysisSCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based SMLC.This statistic can be used for trend analysis of the activity on all Lb-interface SLs for a particular BSS.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application L_SIF_SIO_TX_DPC

L_SIF_SIO_TX_DPC

Description

This statistic tracks the total number of Signal Information Fields (SIF) and Service Information Octets(SIO) transmitted on all SLs of the BSS to the Lb-interface Destination Point Code (DPC).

PeggingThis statistic pegs each time SIF or SIO are transmitted across all signalling links from the BSSto the BSS-based SMLC (as indicated by the Lb-interface (DPC)).

AnalysisA DPC is part of the label in a signalling message that uniquely identifies, in a signallingnetwork, the destination point of the message. This statistic can be used for trend analysisof the activity of the signalling links on a BSS.



Basis BSS.

Type Counter.


L_SIF_SIO_TYPE Chapter 13: BSS-SMLC statistics

L_SIF_SIO_TYPE

Description

This statistic tracks the number of SIF MTP, TEST, and SCCP SIOs transmitted orreceived on all Lb-interface SLs.


• the number of SIF SCCP SIOs will be stored in l_sif_sio_type.

• the number of SIF MTP SIOs will be stored in l_sif_sio_type_mtp.

• the number of SIF TEST SIOs will be stored in l_sif_sio_type_test.

PeggingThis statistic pegs each time SIF or SIOs are transmitted or received on all signallinglinks between BSS and BSS-based SMLC.

AnalysisThis statistic can be used for trend analysis of the activity of the signalling links on a BSS over the Lb-interface.



Basis BSS.

Type Counter.


Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_SMLC_FAIL

PAGE_REQ_FROM_SMLC_FAIL

Description

This statistic tracks the number of page request messages received from the BSS-basedSMLC that fail message validation at the BSS.

PeggingThis statistic pegs each time a page request message from the BSS-based SMLCfails message validation at the BSS.

AnalysisA threshold value should be assigned to this statistic which reflects the maximum number offailures that are acceptable in normal system operations.

If the specified threshold is exceeded, the 20. BSS: Paging request from SMLC protocolerror - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at theOMC-R (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Usage Quality of service monitoring: Paging analysis.Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.


PAGE_REQ_FROM_SMLC_FAIL Chapter 13: BSS-SMLC statistics



Chapter

14Web MMI statistics

The MMI statistics are categorized as PCU real-time statistics and MMI BSC/BTS real-timestatistics. The descriptions for these are given elsewhere in the manual and are referencedin "MMI statistics subgroups" on page 14-2.


MMI statistics subgroups Chapter 14: Web MMI statistics

MMI statistics subgroups

MMU statistics are organized into the following major subgroups:

• "MMI PCU real-time statistics" on page 14-2.

• "MMI BSC/BTS real-time statistics" on page 14-2.

MMI PCU real-time statistics

The following MMI PCU real-time statistics are documented elsewhere in this manual.Table 14-1 indicates the location of these descriptions.

Table 14-1 Location of MMI PCU real-time stats descriptions

MMI PCU statistic Location in manual

CELL_FLUSH_REQS "CELL_FLUSH_REQS" on page 12-15

CHANNEL_REQS_REJ "CHANNEL_REQS_REJECT" on page 12-19

GBL_LINK_INS "GBL_LINK_INS" on page 12-64

GBL_PAGING_REQS "GBL_PAGING_REQS" on page 12-65

GBL_UNAVAILABLE "GBL_UNAVAILABLE" on page 12-69

MMI BSC/BTS real-time statistics

The following MMI BSC/BTS real-time statistics are documented elsewhere in this manual.Table 14-2 indicates the location of these descriptions.

Table 14-2 Location of MMI BSC/BTS real-time stats descriptions

MMI BSC/BTS statistic Location in manual

ALLOC_SDCCH_FAIL "ALLOC_SDCCH_FAIL" on page 4-16

ALLOC_TCH_FAIL "ALLOC_TCH_FAIL" on page 4-18

HO_FAIL_NO_RESOURCES "HO_FAIL_NO_RESOURCES" on page 4-49

HO_REQ_MSC_FAIL "HO_REQ_MSC_FAIL" on page 4-51

MA_CMD_TO_MS_BLKD "MA_CMD_TO_MS_BLKD" on page 4-72

RF_LOSSES_TCH "RF_LOSSES_TCH" on page 4-97


Chapter

15HR and AMR statistics

Half Rate (HR) and Adaptive Multi-Rate (AMR) statistics are used to gauge performance ofsystems employing Half Rate and AMR full-rate link adaptation.

The HR statistics group is shown in "HR statistics group" on page 15-2.

The AMR statistics group is shown in "AMR statistics group" on page 15-3.


HR statistics group Chapter 15: HR and AMR statistics

HR statistics group

{22064}

The group of Half Rate statistics are listed below:

The following statistics have been modified or created as a result of the GSM Half Rate feature.

•

• "ALLOC_TCH_HR" on page 15-6

• "ALLOC_TCH_FAIL_HR" on page 15-4

• "AVAILABLE_TCH_HR" on page 15-17

• "BUSY_TCH_CARR_HR" on page 15-18

• "BUSY_TCH_HR" on page 15-19

• "FER_GSM_HR" on page 15-24

• "HO_REQ_FROM_MSC" on page 15-26

• "RF_LOSSES_TCH_HR" on page 15-27

• "TCH_CONG_INNER_ZONE_HR" on page 15-28

• "TCH_CONGESTION_HR" on page 15-29


Maintenance Information: GSM Statistics Application AMR statistics group

AMR statistics group

{4322} unless marked {4415}

The group of AMR statistics are listed as follows.

The following statistics have been modified as a result of the AMR feature:

• "AMR_DECREASE_THRESH_ADJUST" on page 15-7

• "AMR_FR_DL_CODEC_MODE_USAGE" on page 15-8

• "AMR_FR_DL_ADAPTATION" on page 15-9

• "AMR_FR_UL_ADAPTATION" on page 15-10

• "AMR_FR_UL_CODEC_MODE_USAGE" on page 15-11

• "AMR_HR_DL_ADAPTATION" on page 15-12

• "AMR_HR_DL_CODEC_MODE_USAGE" on page 15-13

• "AMR_HR_UL_ADAPTATION" on page 15-14

• "AMR_HR_UL_CODEC_MODE_USAGE" on page 15-15

• "AMR_INCREASE_THRESH_ADJUST" on page 15-16

• "FER_AMR_FR" on page 15-20

• "FER_AMR_HR" on page 15-22


ALLOC_TCH_FAIL_HR Chapter 15: HR and AMR statistics

ALLOC_TCH_FAIL_HR

The ALLOC_TCH_FAIL_HR statistic replaces ALLOC_TCH_FAIL_HR_AMR.

Description

The statistic tracks the number of unsuccessful allocations of a half rate AMR and/orGSM TCH within a cell for both call origination and hand in. Cases involving ImmediateAssignment Reject are also included in the peg count.

Pegging

This statistic pegs when an attempt to allocate a half rate AMR and/or GSM TCHin a cell fails due to a lack of resources:

• Unsuccessful allocation due to call establishment including unsuccessfulallocations due to directed retries.

• Unsuccessful allocation due to intra-cell hand in.

• Unsuccessful allocation due to inter-cell/intra cell hand in.

• Unsuccessful allocation due to inter-BSS hand in.


Maintenance Information: GSM Statistics Application ALLOC_TCH_FAIL_HR

Upon failure to allocate a channel, the channel allocation failure statistic is pegged for allthe allowed channel rates. Here are some channel allocation failure scenarios:

• If a speech call for which the channel type is full rate and half rate, a failure in allocating achannel results in both ALLOC_TCH_FAIL and ALLOC_TCH_FAIL_HR being pegged.

• ALLOC_TCH_FAIL_HR is pegged for a speech call for which the channeltype specifies both full rate and half rate (with half rate preferred) but resultingin a full rate channel being allocated.

• When there is a failure to allocate a half rate channel, both ALLOC_TCH_FAILand ALLOC_TCH _FAIL_HR are pegged.

• If the channel type is half rate preferred/full rate non-preferred OR full rate preferred/halfrate non-preferred and neither channel type is allocated (a complete TCH allocation failurescenario), the ALLOC_TCH_FAIL shall be pegged twice and ALLOC_TCH_FAIL_HRstat shall be pegged once. That is, once for failed FR and once for failed HR.

• When the non-preferred channel type is successfully assigned a channel, afailure shall be pegged for the preferred type.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum number of half rate AMRand/or GSM TCH failures due to congestion that are acceptable in normal system operations.

There is no alarm generated with respect to this statistic.

Reference None.

Usage Quality of service: Call set-up.Fault finding.Optimization.Network planningLadder: Inter-BSS handover, Intra-BSS handover, Assignment toTCH.

Basis Cell.

Type Counter.


ALLOC_TCH_HR Chapter 15: HR and AMR statistics

ALLOC_TCH_HR

The ALLOC_TCH_HR statistic replaces ALLOC_TCH_HR_AMR.

Description

The statistic tracks the number of successful half rate AMR and/or GSM TCH allocationswithin a cell for both call originations and hand ins.

Pegging

This statistic pegs for successful half rate AMR and/or GSM TCH allocations within a cellas a result of a call establishment or hand in attempt:

• Successful allocation due to call establishment including successful allocationsdue to incoming directed retries.


• Successful allocation due to incoming inter-cell/intra-cell hand in.

• Successful allocation due to incoming inter-BSS hand in.

This statistic pegs before the transmission of the assignment/handover command to the MS and, therefore,does not take into account the success or failure of the assignment/hand in from an RF perspective.

Analysis

This statistic can be used for trend analysis of half rate AMR and/or GSM TCH allocations.

Reference None.

Usage Quality of service monitoring: Call setup.Network planning.Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cellhandover, Assignment to TCH.

Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application AMR_DECREASE_THRESH_ADJUST

AMR_DECREASE_THRESH_ADJUST

{4322}

Description

The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that the BSSMS monitor decreases the C/I codec mode adaptation thresholds for AMR calls on a per-cell basis.

PeggingThis statistic pegs each time that the BSS MS monitor decreases the downlink codec modeadaptation thresholds due to inaccurate C/I estimation by the MS.

Reference None.


Basis Cell.

Type Counter.


AMR_FR_DL_CODEC_MODE_USAGE Chapter 15: HR and AMR statistics

AMR_FR_DL_CODEC_MODE_USAGE

{4322}

Description

The AMR_FR_DL_CODEC_MODE_USAGE statistic keeps a count of each AMR full-rate codecmode used on the downlink of AMR full-rate calls on a per-cell basis.

The bins are:

Bin Description

0 AMR full-rate DL codec mode usage of AFS 12.2kbps





PeggingThis statistic pegs each time that a specific codec mode is used on the downlink of full-rate AMR calls.

Reference None.


Basis Cell.



Maintenance Information: GSM Statistics Application AMR_FR_DL_ADAPTATION

AMR_FR_DL_ADAPTATION

{4322}

Description

The AMR_FR_DL_ADAPTATION statistic keeps a count of the number of times the codec modeis adapted on the downlink of full-rate AMR calls on a per-cell basis.

There are up to four codecs in the Active Codec Set (ACS) and the format of this statisticallows for this. The codecs are referenced sequentially from the lowest speech coding rate tothe highest. The lowest speech coding rate is called the 1st codec. If there are less than fourcodecs in the ACS, the higher bit rates are not valid and contain the value zero.

The bins are:

Bin Description

0 AMR full-rate DL codec mode usage adaptation from 1st to 2nd codec mode.

1 AMR full-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.

2 AMR full-rate DL codec mode usage adaptation from 3rd to 4th codec mode.

3 AMR full-rate DL codec mode usage adaptation from 2nd to 1st codec mode.

4 AMR full-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.

5 AMR full-rate DL codec mode usage adaptation from 4th to 3rd codec mode.

PeggingThis statistic pegs each time that a specific codec mode is adapted on the downlink of full-rate AMR calls.

Reference None.


Basis Cell.



AMR_FR_UL_ADAPTATION Chapter 15: HR and AMR statistics

AMR_FR_UL_ADAPTATION

{4322}

Description

The AMR_FR_UL_ADAPTATION statistic keeps a count of the number of times that the codecmode is adapted on the uplink of full-rate AMR calls on a per-cell basis.


The bins are:

Bin Description

0 AMR full-rate UL codec mode usage adaptation from 1st to 2nd codec mode.

1 AMR full-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.

2 AMR full-rate UL codec mode usage adaptation from 3rd to 4th codec mode.

3 AMR full-rate UL codec mode usage adaptation from 2nd to 1st codec mode.

4 AMR full-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.

5 AMR full-rate UL codec mode usage adaptation from 4th to 3rd codec mode.

PeggingThis statistic pegs each time that a specific codec mode is adapted on the uplink of full-rate AMR calls.

Reference None.


Basis Cell.



Maintenance Information: GSM Statistics Application AMR_FR_UL_CODEC_MODE_USAGE

AMR_FR_UL_CODEC_MODE_USAGE

{4322}

Description

The AMR_FR_UL_CODEC_MODE_USAGE statistic keeps a count of each AMR full-rate codecmode used on the uplink of AMR full-rate calls on a per-cell basis.

The bins are:

Bin Description

0 AMR full-rate UL codec mode usage of AFS 12.2kbps





PeggingThis statistic pegs each time that a specific codec mode is used on the uplink of full-rate AMR calls.

Reference None.


Basis Cell.



AMR_HR_DL_ADAPTATION Chapter 15: HR and AMR statistics

AMR_HR_DL_ADAPTATION

{4322}

Description

The AMR_HR_DL_ADAPTATION statistic keeps a count of the number of times that the codecmode is adapted on the downlink of half-rate AMR calls on a per-cell basis.


The bins are:

Bin Description

0 AMR half-rate DL codec mode usage adaptation from 1st to 2nd codec mode.

1 AMR half-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.

2 AMR half-rate DL codec mode usage adaptation from 3rd to 4th codec mode.

3 AMR half-rate DL codec mode usage adaptation from 2nd to 1st codec mode.

4 AMR half-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.

5 AMR half-rate DL codec mode usage adaptation from 4th to 3rd codec mode.

PeggingThis statistic pegs each time that a specific codec mode is adapted on the downlink of half-rate AMR calls.

Reference None.


Basis Cell.



Maintenance Information: GSM Statistics Application AMR_HR_DL_CODEC_MODE_USAGE

AMR_HR_DL_CODEC_MODE_USAGE

{4322}

Description

The AMR_HR_DL_CODEC_MODE_USAGE statistic keeps a count of each AMR half-rate codecmode used on the downlink of AMR half-rate calls on a per-cell basis.

The bins are:

Bin Description

0 AMR half-rate DL codec mode usage of AFS 7.95kbps





PeggingThis statistic pegs each time that a specific codec mode is used on the downlink of half-rate AMR calls.

Reference None.


Basis Cell.



AMR_HR_UL_ADAPTATION Chapter 15: HR and AMR statistics

AMR_HR_UL_ADAPTATION

{4322}

Description

The AMR_HR_UL_ADAPTATION statistic keeps a count of the number of times that the codecmode is adapted on the uplink of half-rate AMR calls on a per-cell basis.


The bins are:

Bin Description

0 AMR half-rate UL codec mode usage adaptation from 1st to 2nd codec mode.

1 AMR half-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.

2 AMR half-rate UL codec mode usage adaptation from 3rd to 4th codec mode.

3 AMR half-rate UL codec mode usage adaptation from 2nd to 1st codec mode.

4 AMR half-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.

5 AMR half-rate UL codec mode usage adaptation from 4th to 3rd codec mode.

PeggingThis statistic pegs each time that a specific codec mode is adapted on the uplink of half-rate AMR calls.

Reference None.


Basis Cell.



Maintenance Information: GSM Statistics Application AMR_HR_UL_CODEC_MODE_USAGE

AMR_HR_UL_CODEC_MODE_USAGE

{4322}

Description

The AMR_HR_UL_CODEC_MODE_USAGE statistic keeps a count of each AMR half-rate codecmode used on the uplink of AMR half-rate calls on a per-cell basis.

The bins are:

Bin Description

0 AMR half-rate UL codec mode usage of AFS 7.95kbps





PeggingThis statistic pegs each time that a specific codec mode is used on the uplink of half-rate AMR calls.

Reference None.


Basis Cell.



AMR_INCREASE_THRESH_ADJUST Chapter 15: HR and AMR statistics

AMR_INCREASE_THRESH_ADJUST

{4322}

Description

The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that the BSSMS monitor increases the C/I codec mode adaptation thresholds for AMR calls on a per-cell basis.

PeggingThis statistic pegs each time that the BSS MS monitor increases the downlink codec modeadaptation thresholds due to inaccurate C/I estimation by the MS.

Reference None.


Basis Cell.

Type Counter.


Maintenance Information: GSM Statistics Application AVAILABLE_TCH_HR

AVAILABLE_TCH_HR

The AVAILABLE_TCH_HR statistic replaces AVAILABLE_TCH_HR_AMR.

Description

The statistic reports a maximum and average value for the amount of half rate AMR and/orGSM TCHs that are in use or available to be used within the cell.

Pegging

The statistic pegs whenever there is a change in the half rate AMR and/or GSM channel configuration inthe cell (if the number of TCHs has not changed, it will be pegged with the same value as before).Thisstatistic pegs when a change in half rate TCH availability is detected.

An idle generic timeslot is counted as one available full rate channel andtwo available half rate channels.

Reference None.

Usage Radio resource allocation.Quality of service monitoring.Network planning.Service retainability.

Basis Cell.



BUSY_TCH_CARR_HR Chapter 15: HR and AMR statistics

BUSY_TCH_CARR_HR

The BUSY_TCH_CARR_HR statistic replaces BUSY_TCH_CARR_HR_AMR.

Description

The statistic reports a maximum and average value for the amount of half rate AMRand/or GSM TCHs in use on a per carrier basis.

Pegging

This statistic is updated each time an allocation or deallocation of a half rate AMR and/or GSM TCH occurs.

Reference None.


Basis Carrier.



Maintenance Information: GSM Statistics Application BUSY_TCH_HR

BUSY_TCH_HR

The BUSY_TCH_HR statistic replaces BUSY_TCH_HR_AMR.

Description

The statistic reports a maximum and average value for the amount of half rate AMR and/or GSM TCHs in use.

Pegging

This statistic is updated each time an allocation or deallocation of a half rate AMR and/or GSM TCH occurs.

Reference None.


Basis Cell.



FER_AMR_FR Chapter 15: HR and AMR statistics

FER_AMR_FR

{4322}

Description

The uplink FER_AMR_FR Quality statistic is derived from a ratio of successfully decodedgood speech frames against unsuccessfully decoded bad frames for AMR full- rate calls. Themeasurement 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 lookuptable, the ratio is then converted to a FER_AMR_FR Quality number between 0 and 9.

For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,Table 15-1, this relates to an FER_AMR_FR Quality number of 2.

PeggingThis statistic pegs the uplink frame erasure rate for AMR full-rate calls for each carrier in a cell.

UnitsThe FER_AMR_FR is reported using values 0 to 9 as follows.

Table 15-1 FER_AMR_FR Quality number conversion

FER_AMR_FR Qualitynumber FER_AMR_FR Quality number

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

FER_AMR_FR Quality is measured on a timeslot basis for active channels after decodingde-interleaving and error correction. Data for this statistic is reported by firmware to theRSS/HO software process where it is pegged.



Maintenance Information: GSM Statistics Application FER_AMR_FR


Reference None.

Usage Quality of service, Fault finding, RF loss, Congestion.

Basis Carrier.



FER_AMR_HR Chapter 15: HR and AMR statistics

FER_AMR_HR

{4322}

Description

The uplink FER_AMR_HR Quality statistic is derived from a ratio of successfully decodedgood speech frames against unsuccessfully decoded bad frames for AMR half rate calls. Themeasurement 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 a FER_AMR_HR Quality number between 0 and 9.

For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,Table 15-2, this relates to an FER_AMR_HR Quality number of 2.

PeggingThis statistic pegs the uplink frame erasure rate for AMR half rate calls for each carrier in a cell.

UnitsThe FER_AMR_HR is reported using values 0 to 9 as follows.

Table 15-2 FER_AMR_HR Quality number conversion

FER_AMR_HR Qualitynumber FER ratio (min:1 to max:1)

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

FER_AMR_HR Quality is measured on a timeslot basis for active channels after decodingde-interleaving and error correction. Data for this statistic is reported by firmware to theRSS/HO software process where it is pegged.



Maintenance Information: GSM Statistics Application FER_AMR_HR


Reference None.

Usage Quality of service, Fault finding, RF loss, Congestion.

Basis Carrier.



FER_GSM_HR Chapter 15: HR and AMR statistics

FER_GSM_HR

{22064}

Description

The uplink FER_GSM_HR Quality statistic is derived from a ratio of successfully decodedgood speech frames against unsuccessfully decoded bad frames for GSM half rate calls. Themeasurement 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 lookuptable, the ratio is then converted to a FER_GSM_HR Quality number between 0 and 9.

For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,Table 15-3, this relates to an FER_GSM_HR Quality number of 2.

Pegging

This statistic pegs the uplink frame erasure rate for GSM half rate calls for each carrier in a cell.

Units

The FER_GSM_HR is reported using values 0 to 9 as follows.

Table 15-3 FER_GSM_HR Quality number conversion

FER_GSM_HR Qualitynumber FER ratio (min:1 to max:1)

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


Maintenance Information: GSM Statistics Application FER_GSM_HR

FER_GSM_HR Quality is measured on a timeslot basis for active channels after decodingde-interleaving and error correction. Data for this statistic is reported by firmware to theRSS/HO software process where it is pegged.



HO_REQ_FROM_MSC Chapter 15: HR and AMR statistics

HO_REQ_FROM_MSC

{4322 unless stated otherwise}

Description

The HO_REQ_FROM_MSC statistic tracks the number of handover requests foreach channel type and speech version.

The bins are:

Bin Procedures

0 PM_FR

1 PM_EFR

2 PM_AMR_FR

3 PM_AMR_HR

4 PM_SDCCH_CHAN

5 PM_Other

{22064} When the Half Rate feature is unrestricted, the HO_REQ_FROM_MSC bin tableintroduces bin procedure PM_GSM_HR as shown:

Bin Procedure

6 PM_GSM_HR

Pegging

This statistic pegs the handover request for each channel type and speech versionspeech version in the appropriate bin.

Reference GSM 8.08.

Usage Radio resource allocation.Quality of service monitoring: Call setup.Network planning.Ladder: TCH assignment successful, TCH assignmentfail-recovered to SDCCH, TCH assignment blocked.

Basis Cell.



Maintenance Information: GSM Statistics Application RF_LOSSES_TCH_HR

RF_LOSSES_TCH_HR

{22064}

The RF_LOSSES_TCH_HR statistic replaces RF_LOSSES_TCH_HR_AMR.

Description

The statistic tracks the number of calls lost while using a half rate AMR and/or GSM TCH.

Pegging

This statistic pegs the number of calls that were terminated because of RF problems. It is composedof calls lost while using a half rate AMR and/or GSM TCH.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum number of lost calls whileusing a half rate AMR and/or GSM TCH that are acceptable in normal system operations.

Reference None

Usage RF loss.Congestion.Quality of service monitoring.Fault finding.Installation and commissioning.

Basis Timeslot.

Type Counter.


TCH_CONG_INNER_ZONE_HR Chapter 15: HR and AMR statistics

TCH_CONG_INNER_ZONE_HR

{22064}

The TCH_CONG_INNER_ZONE_HR statistic replacesTCH_CONG_INNER_ZONE_HR_AMR.

Description

The statistic tracks the duration of time when there are no half rate AMR and/or GSM TCHsavailable in the inner zone of a concentric cell or dual band cell.

Pegging

When the last inner zone half rate AMR and/or GSM TCH available is allocated a timer is started.This timer is stopped when at least one inner zone half rate TCH becomes idle.

Reference None.


Basis Cell.

Type Duration.


Maintenance Information: GSM Statistics Application TCH_CONGESTION_HR

TCH_CONGESTION_HR

{22064}

The TCH_CONGESTION_HR statistic replaces TCH_CONGESTION_HR_AMR.

Description

The statistic tracks the duration of time when there are no half rate AMR and/or GSMTCHs available. For concentric cell or dual band cells, this measurement indicates half rateAMR and/or GSM TCH congestion for the outer zone.

Pegging

When the last half rate AMR and/or GSM TCH available is allocated a timer is started. Thistimer is stopped when at least one half rate TCH becomes idle.

Reference None.


Basis Cell.

Type Duration.


TCH_CONGESTION_HR Chapter 15: HR and AMR statistics



Chapter

16Call model statistics

Call model parameter values can be derived from the GSM network statistics collected at the OMC-R.

All the statistics used for determining the call model parameters must be collected during busyhours 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 equipmentdimensioning purposes. This gives more scope of averaging out the load from the network entities.

The following are call model statistics:

• "CALL_DURATION (T)" on page 16-2.

• "CALL_SETUP_TCH_BLOCKING_RATE" on page 16-3.

• "HANDOVERS_PER_CALL (H)" on page 16-4.

• "IMSI_DETACHES_TO_CALL (Id)" on page 16-5.

• "INTRA_BSS_HO_TO_ALL_HO (i)" on page 16-6.

• "LOCATION_UPDATE_FACTOR (L)" on page 16-7.

• "LOCATION_UPDATES_TO_CALLS (I)" on page 16-8.

• "PAGES_PER_CALL (PPC)" on page 16-9.

• "PAGES_PER_SECOND" on page 16-10.

• "PAGING_RATE (P)" on page 16-11.

• "SMS_TO_CALL_RATIO (S)" on page 16-12.

Refer to the System Information: BSS Equipment Planning (68P02900W21) for furtherinformation on the call model parameters.


CALL_DURATION (T) Chapter 16: Call model statistics

CALL_DURATION (T)

Description

This statistic provides the average call duration.

Formula

_ _ _ _ _ _ _ _ _

_ _

Where: is:

N the number of cells.

stat_interval_in_sec the interval over whichBUSY_TCH_MEAN valuesare measured. It is 3600 if hourlyvalues are used and 86400 if dailyvalues are used.

Usage Network planning.Optimization.

Basis Cell.

Units Seconds

Raw Statistics BUSY_TCH_MEAN.TOTAL_CALLS.ASSIGNMENT_REDIRECTION.


Maintenance Information: GSM Statistics Application CALL_SETUP_TCH_BLOCKING_RATE

CALL_SETUP_TCH_BLOCKING_RATE

Description

This statistic provides the percentage of attempts to allocate a TCH call setup that were blocked.

Formula

_ __

_ _ _ __ _ _


Basis Cell.

Units Percentage.

Raw Statistics MA_CMD_TO_MS_BLKD.MA_REQ_FROM_MSC.


HANDOVERS_PER_CALL (H) Chapter 16: Call model statistics

HANDOVERS_PER_CALL (H)

Description

This statistic provides the number of Handovers per call where the handovers maybe inter-BSS, intra-BSS or intra-cell.

Formula

_ _ _ _ _ _ _ _ __ _ _

_ _

Where: is:


The TOTAL_CALLS parameter is the count of the total circuit-switched calls in a cell. Itshould be summed for all the cells in the BSC, when used in the previous formula.


Basis Cell.

Raw Statistics OUT_INTER_BSS_REQ_TO_MSC.OUT_INTRA_BSS_HO_ATMPT.INTRA_CELL_HO_ATMPT.TOTAL_CALLS.ASSIGNMENT_REDIRECTION.


Maintenance Information: GSM Statistics Application IMSI_DETACHES_TO_CALL (Id)

IMSI_DETACHES_TO_CALL (Id)

Description

This statistic provides the ratio of IMSI detaches per call.

Formula

_ _ _

_ _

Where: is:



Basis Cell.

Raw Statistics OK_ACC_PROC .[IMSI_DETACH].TOTAL_CALLS.ASSIGNMENT_REDIRECTION.


INTRA_BSS_HO_TO_ALL_HO (i) Chapter 16: Call model statistics

INTRA_BSS_HO_TO_ALL_HO (i)

Description

This statistic provides the ratio of intra-BSS handovers to all handovers.

Formula

_ _ _ _ _ _ _

_ _ _ _ _ _ _ _ __ _ _

Where: is:



Basis Cell.

Raw Statistics OUT_INTRA_BSS_HO_ATMPT.INTRA_CELL_HO_ATMPT.OUT_INTER_BSS_REQ_TO_MAC.TOTAL_CALLS.ASSIGNMENT_REDIRECTION.


Maintenance Information: GSM Statistics Application 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 ofIMSI detaches per call (Id). For networks with IMSI detach disabled, the location updatefactor 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 theIMSI detach. When using IMSI detach type 1, the MSC clears the SCCP connection, a clearing procedurethat involves only one uplink (average size of 42 bytes) and one downlink message (average size of 30bytes). When using IMSI detach type 2, the MSC sends the CLEAR COMMAND and the BSS sendsCLEAR COMPLETE, etc., which involves three uplink (average size of 26 bytes) and three downlinkmessages (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 alocation update and a IMSI detach (type 2) takes 6/11 (approximately 0.5) of the messages of a location update.

FormulaIf IMSI detach is enabled, then depending on whether short message sequence (type 1) orlong 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)


Basis Cell.

Call Model Statistics LOCATION_UPDATES_TO_CALLS.IMSI_DETACHES_TO_CALLS.


LOCATION_UPDATES_TO_CALLS (I) Chapter 16: Call model statistics

LOCATION_UPDATES_TO_CALLS (I)

Description

This statistic provides the ratio of location updates to calls.

Formula

_ _

_ _

Where: is:



Basis Cell.

Raw Statistics OK_ACC_PROC[LOCATION UPDATE]. TOTAL_CALLS.ASSIGNMENT_REDIRECTION.


Maintenance Information: GSM Statistics Application PAGES_PER_CALL (PPC)

PAGES_PER_CALL (PPC)

Description

This statistic provides the number of pages per call.

Formula

_ _ _

_ _

Where: is:

N the number of cells under the BSC.


Basis Cell.

Call Model/Raw Statistics PAGE_REQ_FROM_MSC.TOTAL_CALLS.ASSIGNMENT_REDIRECTION.PAGING_RATE.CALL_DURATION.


PAGES_PER_SECOND Chapter 16: Call model statistics

PAGES_PER_SECOND

Description

This statistic provides the number of pages per second.

Formula

_ _ _ _ __


Basis Cell.

Raw Statistics PAGE_REQ_FROM_MSC.INTERVAL_SUM.


Maintenance Information: GSM Statistics Application PAGING_RATE (P)

PAGING_RATE (P)

Description

The paging rate is the summation of the paging messages sent to each location areaaveraged over the interval period.

Formula

_ _ _

_ _ _

Where: is:

N the number of location areas.

PAGE_REQ_FROM_MSC should be the maximum per cell value for each location area.


Basis Cell.

Raw Statistics PAGE_REQ_FROM_MSC.


SMS_TO_CALL_RATIO (S) Chapter 16: Call model statistics

SMS_TO_CALL_RATIO (S)

Description

This statistic provides the ratio of SMSs to calls.

Formula

_ _ _ _ _ __ _ _ _ _ _ _ _ _

_ _ _ _


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.


Chapter

17Key statistics

Key statistics are a set of calculated values providing an operator with a summary of system performanceduring a specific statistics collection interval. They are designed to give an overall indication of the conditionof the system and allow comparison of similar time periods to detect performance changes and trends.

Key statistics are also provided to facilitate the monitoring of the most important network parameters. Keystatistics are calculated at the OMC-R using various BSS raw statistics. Different statistics are combined at theOMC-R using a predefined formula to produce a new statistic. For example, various handover failure statisticsmay be combined and averaged over the total number of calls to produce a handover failure rate key statistic.

Key statistics may be displayed in the Performance Management window of the OMC-R.

They key statistics are categorized into subgroups, each of which are described in"Key statistics subgroups" on page 17-2.


Key statistics subgroups Chapter 17: Key statistics

Key statistics subgroups

Key statistics are organized into the following major subgroups:

• "Call summary" on page 17-2.

• "Channel usage" on page 17-2.


• "RF loss summary" on page 17-3.

• "MTL utilisation" on page 17-4.

• "Key statistics description template" on page 17-4.

Call summary

Call summary statistics are used to determine assignment and handover performance of oneor more cells. The following are call summary statistics:

• "CALL_SETUP_SUCCESS_RATE" on page 17-6.

• "HANDOVER_FAILURE_RATE" on page 17-9.

• "HANDOVER_SUCCESS_RATE" on page 17-10.

• "SUCCESS_INTERNAL_HO" on page 17-27.

• "TOTAL_CALLS_KEY" on page 17-38.

• "UNSUCCESS_INTERNAL_HO_NOREEST" on page 17-39.

• "UNSUCCESS_INTERNAL_HO_REEST" on page 17-40.

Channel usage

Channel usage statistics are used to determine SDCCH and TCH performance levels.The following are channel usage statistics:

• "MEAN_TCH_BUSY_TIME" on page 17-14.

• "SDCCH_ACCESS_SUCCESS_RATE" on page 17-18.

• "SDCCH_MEAN_ARRIVAL_RATE" on page 17-21.

• "SDCCH_MEAN_HOLDING_TIME" on page 17-22.

• "SDCCH_SETUP_BLOCKING_RATE" on page 17-20.


Maintenance Information: GSM Statistics Application Key statistics subgroups

• "SDCCH_TRAFFIC_CARRIED" on page 17-24.

• "TCH_BLOCKING_RATE" on page 17-28.

• "TCH_BLOCKING_RATE_INNER_Z" on page 17-29

• "TCH_BLOCKING_RATE_OUTER_Z" on page 17-30

• "TCH_MEAN_ARRIVAL_RATE" on page 17-31.

• "TCH_MEAN_HOLDING_TIME" on page 17-32.

• "TCH_RF_LOSS_RATE" on page 17-34

• "TCH_TRAFFIC_CARRIED" on page 17-36.


Connection statistics are used to determine the number and interval of attempted and successfulassignment requests. The following are connection establishment statistics:

• "ATTEMPT_IMMED_ASSIGN_PROC" on page 17-5.

• "MEAN_ARRIVAL_TIME_BETWEEN_CALLS" on page 17-12.

• "MEAN_INTER_ARRIVAL_TIME" on page 17-13.

• "SUCCESS_IMMED_ASSIGN_PROC" on page 17-26.

RF loss summary

RF loss summary statistics are used to determine TCH assignments within a cell and the rateof RF lost calls. The following are RF loss summary statistics:

• "CELL_TCH_ALLOCATIONS" on page 17-7.

• "CELL_TCH_ASSIGNMENTS" on page 17-8.

• "RF_LOSS_RATE" on page 17-17.

• "SDCCH_RF_LOSS_RATE" on page 17-23.



Key statistics subgroups Chapter 17: Key statistics

MTL utilisation

MTL utilisation statistics are used to provide a measure of MTL utilisation from the MSC to BSSand from the BSS to MSC. The following are MTL utilisation statistics:

• "MTL_UTILISATION_RX" on page 17-15.

• "MTL_UTILISATION_TX" on page 17-16.

Key statistics description template

Table 17-1 is a template used in the key statistic descriptions:

Table 17-1 Key statistic descriptions.

Description: A general description of what the statistic measures.

Formula: Arithmetic calculation of key statistic from raw statistics.

Reference: References to other sections of this document or other documents.

Usage: Lists the network operation related uses of the statistic.

Basis: The level at which the statistic is pegged, for example, cell, BSS.

Type: The statistic type (counter, percentage, etc.).

Raw Statistic: The raw statistics associated with this key statistic. The convention used forpresenting a specific bin of a counter array statistic is statistic name[bin name].For example, OK_ACC_PROC[CM_REESTABLISH] is the CM_REESTABLISHbin of the OK_ACC_PROC counter array statistic.

Note: Used to qualify or stress information.

The template headings are used as required and are not present for all statistics.


Maintenance Information: GSM Statistics Application ATTEMPT_IMMED_ASSIGN_PROC

ATTEMPT_IMMED_ASSIGN_PROC

Description

The ATTEMPT_IMMED_ASSIGN_PROC statistic tracks the number of attemptedimmediate assignment procedures.

Formula

_ _ _ _ _ __ _ _ _

Usage Network planning.Installation and commissioning.Optimization.

Basis Cell or BSS.

Type Counter.

Raw Statistics OK_ACC_PROC_RACH.INV_EST_CAUSE_ON_RACH.


CALL_SETUP_SUCCESS_RATE Chapter 17: Key statistics

CALL_SETUP_SUCCESS_RATE

Description

The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that resultin a successful TCH access. Network accesses which do not require a TCH are excluded; forexample, location updates, SMS, and Supplementary Service attempts.

Formula

_ __

__ _

_ __ _

_ _ _ _ __ _ __ _ _

_ _ _ __ _ _ _ _

_ _ _ _ _ __ _ _ _ _ _

_ _ _ _ __ _ _ _ _ _

Usage Quality of service.Fault finding.Service accessibility.

Basis Cell.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).MT_LCS_ON_SDCCH.OK_ACC_PROC[CM_REESTABLISH].OK_ACC_PROC[CM_SERV_REQ_CALL].OK_ACC_PROC[CM_SERV_REQ_EMERG].OK_ACC_PROC[CM_SERV_REQ_SMS].OK_ACC_PROC[LOC_FLW_ON_REQ_NORM].OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].OK_ACC_PROC[PAGE_RESPONSE].SMS_INIT_ON_SDCCH.SMS_INIT_ON_SDCCH_HO_IN.TOTAL_CALLS.


Maintenance Information: GSM Statistics Application CELL_TCH_ALLOCATIONS

CELL_TCH_ALLOCATIONS

Description

The CELL_TCH_ALLOCATIONS statistic tracks number of successful allocations of aTCH within a cell for both call originations and hand ins.

Formula

_ _ _


Basis Cell.

Type Counter.

Raw Statistics ALLOC_TCH.


CELL_TCH_ASSIGNMENTS Chapter 17: Key statistics

CELL_TCH_ASSIGNMENTS

Description

The CELL_TCH_ASSIGNMENTS statistic is the sum of the total number of calls, the total number ofsuccessful incoming inter-BSS call handovers, and the total number of incoming intra-BSS call handovers.

Formula

_ __

_ _ _ _ _ _ __ _ _ _ _ _ _


Basis Cell.

Type Counter.

Raw Statistics TOTAL_CALLS.IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].


Maintenance Information: GSM Statistics Application HANDOVER_FAILURE_RATE

HANDOVER_FAILURE_RATE

Description

The HANDOVER_FAILURE_RATE statistic tracks the percentage of handovers that were attemptedfrom the source cell (the cell for which the statistic is presented) that failed to successfully reach thetarget cell and failed to successfully recover to the source cell, that is, the handover failed and the calldropped. A handover attempt is counted when a handover command is sent to the MS.

Congestion on the target cell does not result in the BSS sending a handover command to the mobiletherefore this measurement is not impacted by target cell congestion.

Formula

__

_ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _

_ _ _ _ __ _ _ _ _ _ _

Usage Quality of service monitoring.Optimization.Fault finding.Installation and commissioning.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].


HANDOVER_SUCCESS_RATE Chapter 17: Key statistics

HANDOVER_SUCCESS_RATE

Description

The HANDOVER_SUCCESS_RATE statistic tracks the percentage of handovers that wereattempted from the source cell (cell for which the statistic is presented) that successfullyreached the target cell. A handover attempt is counted when a handover command is sent tothe MS. This key statistic includes inter-BSS Handovers.

Congestion on the target cell does not result in the BSS sending a handover command to the mobiletherefore this measurement is not impacted by target cell congestion.

Formula

__

_ _ _ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _

HANDOVER_SUCCESS_RATE + HANDOVER_FAILURE_RATE ? 100% because the callsthat fail and recover to the source cell are not included in either of these key statistics.


Maintenance Information: GSM Statistics Application HANDOVER_SUCCESS_RATE

Usage Quality of service monitoring.Optimization.Fault finding.Installation and commissioning.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_FR].INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_HR].INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_FR_HR].INTRA_CELL_HO[INTRA_CELL_HO_ATMPT_HR_FR].INTRA_CELL_HO[INTRA_CELL_HO_SUC].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


MEAN_ARRIVAL_TIME_BETWEEN_CALLS Chapter 17: Key statistics

MEAN_ARRIVAL_TIME_BETWEEN_CALLS

Description

The MEAN_ARRIVAL_TIME_BETWEEN_CALLS statistic tracks the amount of time betweenconsecutive normal and emergency call attempts originated from an MS.

Formula

_ _ __ _ _ _ _

_ _ _ _

Usage Network planning.Fault finding.Installation and commissioning.Optimization.

Basis Cell.

Type Duration (in seconds).

Raw Statistics INTERVAL.CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL].CHAN_REQ_HO_CAUSE_ATMPT[EMERGENCY_CALL].


Maintenance Information: GSM Statistics Application MEAN_INTER_ARRIVAL_TIME

MEAN_INTER_ARRIVAL_TIME

Description

TheMEAN_INTER_ARRIVAL_TIME statistic is the arithmetic mean of the sum of the time intervalsbetween consecutive normal, SMS, supplementary and emergency requests for service.

FormulaBSS Level

_ _ __ _ _ _ __ _ _ _ __ _ _ _ __ _ _ _ _


Basis BSS.


Raw Statistics INTERVAL.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].


MEAN_TCH_BUSY_TIME Chapter 17: Key statistics

MEAN_TCH_BUSY_TIME

Description

The MEAN_TCH_BUSY_TIME statistic tracks the arithmetic mean of the busytime for traffic channels in a cell.

Formula

_ _ _ _ __ _


Basis Cell.


Raw Statistics AVAILABLE_TCH.BUSY_TCH.


Maintenance Information: GSM Statistics Application MTL_UTILISATION_RX

MTL_UTILISATION_RX

Description

TheMTL_UTILISATION_RX statistic 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 followingwhich shows no number simplification:

_ _

_ _ _ _ _

_

_ _


Basis MTL.

Type Percentage.

Raw Statistics MTP_MSU_RX.MTP_SIF_SIO_RX.SIB_RX.MTP_LINK_INS.


MTL_UTILISATION_TX Chapter 17: Key statistics

MTL_UTILISATION_TX

Description

TheMTL_UTILISATION_TX statistic 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 followingwhich shows no number simplification:

_ _

_ _ _ _ _

_

_ _


Basis MTL.

Type Percentage.

Raw Statistics MTP_MSU_TX.MTP_SIF_SIO_TX.SIB_TX.MTP_LINK_INS.


Maintenance Information: GSM Statistics Application RF_LOSS_RATE

RF_LOSS_RATE

Description

The RF_LOSS_RATE statistic compares the total number of RF losses (while using bothSDCCH and TCH) with the number of calls set-up in the cell plus the number of calls handedin to the cell. It indicates the cell/system ability to preserve calls.

Formula

_ __ _

_ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ __ _ _ _

_ _ __ _ _ _

Handovers may relate to SDCCHs (as opposed to TCHs). In this case, the accuracy of the statistic isaffected. For the most part this effect is expected to be negligible. nTCH = Number of TCHs in cell.

Usage Quality of service.Fault finding and optimization.Installation and commissioning.

Basis Cell.

Type Percentage.

Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].OK_ACC_PROC: (The value used in this formula is the sum ofbins 0 to 7 of this counter array statistic.) RF_LOSSES_TCH.RF_LOSSES_SD.


SDCCH_ACCESS_SUCCESS_RATE Chapter 17: Key statistics

SDCCH_ACCESS_SUCCESS_RATE

Description

The SDCCH_ACCESS_SUCCESS_RATE statistic calculates the proportion of SDCCHactivation which is followed by successful MS access.

Formula

_ __

_ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _ __ _ _ _

_ _ _


Basis Cell.

Type Counter (calls per interval).

Raw Statistics OK_ACC_PROC_SUC_RACH.INV_EST_CAUSE_ON_RACH.CHAN_REQ_MS_BLK.OK_ACC_PROC. (The value used in this formula is the sum ofbins 0 to 7 and 10 of this counter array statistic).


Maintenance Information: GSM Statistics Application SDCCH_BLOCKING_RATE

SDCCH_BLOCKING_RATE

Description

The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an SDCCH that wereblocked due to no available SDCCH resources. This statistic includes incoming SDCCH handover attempts.

Formula

_ _ _ __ _ _

Usage Service Accessibility.Quality of Service monitoring.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics ALLOC_SDCCH.ALLOC_SDCCH_FAIL.


SDCCH_SETUP_BLOCKING_RATE Chapter 17: Key statistics

SDCCH_SETUP_BLOCKING_RATE

Description

The SDCCH_SETUP_BLOCKING_RATE statistic tracks the percentage of attempts to allocatean SDCCH that were blocked due to no available SDCCH resources for call origination only.This statistic does not include incoming SDCCH handover attempts.

Formula

_ _ _ _ _ __ _ _ _

_ _ _ _

Usage Service Accessibility.Quality of Service monitoring.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics CHAN_REQ_MS_BLK.OK_ACC_PROC_SUC_RACH.INV_EST_CAUSE_ON_RACH.


Maintenance Information: GSM Statistics Application SDCCH_MEAN_ARRIVAL_RATE

SDCCH_MEAN_ARRIVAL_RATE

Description

The SDCCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate forthe SDCCHs in the cell measured in calls per interval.

Formula

_ _ _

_ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Counter (calls per interval).

Raw Statistics INTERVAL ( statistics collection interval, measured in hours).OK_ACC_PROC. (The value used in this formula is the sum ofthe bins 0 to 7 of this counter array statistic).


SDCCH_MEAN_HOLDING_TIME Chapter 17: Key statistics

SDCCH_MEAN_HOLDING_TIME

Description

The SDCCH_MEAN_HOLDING_TIME statistic tracks the average duration ofcalls on SDCCH channels in seconds.

Formula

_ _ _ _ _ __


Basis Cell.

Type Total Time (in seconds).

Raw Statistics ALLOC_SDCCH.BUSY_SDCCH.INTERVAL_SUM (total statistics collection interval, measured inhours).



Maintenance Information: GSM Statistics Application SDCCH_RF_LOSS_RATE

SDCCH_RF_LOSS_RATE

Description

The SDCCH_RF_LOSS_RATE statistic compares the total number of RF losses (while using anSDCCH), as a percentage of the total number of call attempts for SDCCH channels. T his statisticis intended to give an indication of how good the cell/system is at preserving calls.

Formula

_ _ _ _ __ _ _ _

Usage Quality of service monitoring.Fault finding.Installation and commissioning.

Basis Cell.

Type Percentage.

Raw Statistics ALLOC_SDCCH.CHAN_REQ_MS_FAIL.RF_LOSSES_SD.


SDCCH_TRAFFIC_CARRIED Chapter 17: Key statistics

SDCCH_TRAFFIC_CARRIED

Description

The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busySDCCHs measured in Erlangs.

Formula

_ _ _ _

For an individual cell over m statistics intervals:

_ __ _

For n cells over an individual statistics interval:

_ _ _ _

For n cells over m statistics intervals:

_ __ _


Maintenance Information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED

The BUSY_SDCCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.Where BUSY_SDCCH_MEAN [ ] isBUSY_SDCCH_MEAN for statistical interval .

Usage RF Loss.Congestion.Network planning.Optimization.

Basis BSS.

Type Counter.

Raw Statistic BUSY_SDCCH.


SUCCESS_IMMED_ASSIGN_PROC Chapter 17: Key statistics

SUCCESS_IMMED_ASSIGN_PROC

Description

The SUCCESS_IMMED_ASSIGN_PROC statistic tracks the number of successfulimmediate assignment procedures.

Formula

_ _ _ _ _ _ _ _ _ __ _ _


Basis Cell or BSS.

Type Counter.

Raw Statistics CHAN_REQ_MS_BLK.INV_EST_CAUSE_ON_RACH.OK_ACC_PROC_RACH.


Maintenance Information: GSM Statistics Application SUCCESS_INTERNAL_HO

SUCCESS_INTERNAL_HO

Description

The SUCCESS_INTERNAL_HO statistic tracks the number of successful internal handovers.

Formula

_ __ _ _ _ _

_ _ _ _ _ _ _

Usage Network planning.Optimization.Quality of service.

Basis Cell.

Type Counter.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


TCH_BLOCKING_RATE Chapter 17: Key statistics

TCH_BLOCKING_RATE

Description

The TCH_BLOCKING_RATE statistic provides the percentage of all requests for TCH resources(originations and hand ins) which fail due to no available TCH resources.

Formula

_ _

_ __ _

__

_ __ _

_

Usage Quality of service monitoring.Network planning.Fault finding.

Basis Cell.

Type Percentage.

Raw Statistics ALLOC_TCH.ALLOC_TCH_FAIL.ASSIGNMENT_RESOURCE_REQ.HO_REQ.


Maintenance Information: GSM Statistics Application TCH_BLOCKING_RATE_INNER_Z

TCH_BLOCKING_RATE_INNER_Z

Description

The TCH_BLOCKING_RATE_INNER_Z statistic provides the percentage of all requests for innerzone TCH resources (originations and hand ins) which fail due to no available TCH resources.

Formula

_ __ _

_ _ _ __ _

_ _ _ __ _ _ _ _

_ _ __ _ _ _

_ __ _ _ _

_ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics ALLOC_TCH_INNER_Z.ALLOC_TCH_FAIL_INNER_Z.TCH_Q_REMOVED (Bins 2 and 3 of this counter array statistic).


TCH_BLOCKING_RATE_OUTER_Z Chapter 17: Key statistics

TCH_BLOCKING_RATE_OUTER_Z

Description

The TCH_BLOCKING_RATE_OUTER_Z statistic provides the percentage of all requests for outerzone TCH resources (originations and hand ins) which fail due to no available TCH resources.

Formula

_ __ _

_ __ _ _ _

_ __ _

_ __ _ _ _

_ _ __ _ _ _ _

__ _ _

_ __ _ _ _

_ __ _

_ __ _ _ _

_ _ __ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics ALLOC_TCH_FAIL.ALLOC_TCH_FAIL_INNER_Z.ALLOC_TCH.ALLOC_TCH_INNER_Z.TCH_Q_REMOVED (Bins 0 to 3 of this counter array statistic).


Maintenance Information: GSM Statistics Application TCH_MEAN_ARRIVAL_RATE

TCH_MEAN_ARRIVAL_RATE

Description

The TCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate incalls per interval for the cell in question.

Formula

_ _ _ _ _ _ _ _

The arrival rate of calls includes both calls set up on traffic channels withina cell and handovers into the cell.


Basis Cell.

Type Counter (calls/interval).

Raw Statistics ALLOC_TCH.ALLOC_TCH_FAIL.TCH_Q_REMOVED.


TCH_MEAN_HOLDING_TIME Chapter 17: Key statistics

TCH_MEAN_HOLDING_TIME

Description

The TCH_MEAN_HOLDING_TIME statistic tracks the average duration of callson traffic channels (TCH) in seconds.

Formula

Cell Level

{22064}

_ __

_ __ _ _

_

__ _ _

_ _ _ __ _ _

_ _ _ _

BSS Level

{22064}

_ __

_ __ _ _

_

__ _

_ __ _

_ _ __ _ _ _

Network Level


Maintenance Information: GSM Statistics Application TCH_MEAN_HOLDING_TIME

{22064}

_ __

_ __ _ _

_

__ _

_ __ _

The numerator and denominator may peg on different intervals (where a call extends acrossmultiple collection boundaries). This affects the accuracy of the statistic for the period. Therefore,this statistic should be used as a trend rather than focusing on specific values.

Analysis


Basis Cell, BSS or network.

Type Percentage.

Raw Statistics BUSY_TCH_MEAN.{22064}BUSY_TCH_HR_MEAN.TOTAL_CALLS.IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).


TCH_RF_LOSS_RATE Chapter 17: Key statistics

TCH_RF_LOSS_RATE

Description

The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that areabnormally released due to a failure on the radio interface.

Formula

Cell Level

{22064}

_ _ __ _ _ _ _

_ _ _ _ _

_ _ _ _

BSS Level

{22064}

_ _ __ _ _ _ _

_

_ _

_ _

_ _

_ _ _ _ _ _

Network Level

{22064}

_ _ __ _ _ _ _

__ _

_ __ _

Analysis

Usage Quality of service.Fault finding.

Basis Cell.


Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).IN_INTER_BSS[IN_INTER_HO_SUC].IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].RF_LOSSES_TCH.{22064}RF_LOSSES_TCH_HR.TOTAL_CALLS.


TCH_TRAFFIC_CARRIED Chapter 17: Key statistics

TCH_TRAFFIC_CARRIED

Description

The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.

Formula

For an individual cell for an individual statistics interval:

{22064}

_ _ _ _ _ _ _


{22064}

_ __ _ _ _ _


{22064}

_ _ _ _ _ _ _


{22064}

_ __ _ _ _ _

The BUSY_TCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.Where BUSY_TCH_MEAN [ ] isBUSY_TCH_MEAN for statistical interval .


Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED

Analysis

Usage Congestion.Quality of service.Network planning.Optimization.

Basis Cell.

Type Units = Erlangs.

Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).{22064}BUSY_TCH_HR (BUSY_TCH_HR_MEAN).


TOTAL_CALLS_KEY Chapter 17: Key statistics

TOTAL_CALLS_KEY

Description

The TOTAL_CALLS_KEY statistic tracks the number of calls for one or more cells during the interval.

Formula

_ _ _


Basis Cell.

Type Counter.

Raw Statistics TOTAL_CALLS.


Maintenance Information: GSM Statistics Application UNSUCCESS_INTERNAL_HO_NOREEST

UNSUCCESS_INTERNAL_HO_NOREEST

Description

The UNSUCCESS_INTERNAL_HO_NOREEST statistic tracks the number of unsuccessfulinternal handovers that result in dropping the call.

Formula

_ __

_ _ _ _ __ _ _ _ _ _ _

Usage Network planning.Quality of service.Fault finding.

Basis Cell or BSS.

Type Counter

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].


UNSUCCESS_INTERNAL_HO_REEST Chapter 17: Key statistics

UNSUCCESS_INTERNAL_HO_REEST

Description

The UNSUCCESS_INTERNAL_HO_REEST statistic tracks the number of unsuccessful internalhandovers with successful recovery to the originating cell or channel.

Formula

_ _ __ _ _ _ _

_ _ _ _ _ _ _

Usage Network planning.Fault finding.Quality of service.

Basis Cell or BSS.

Type Counter.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_RETURN].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].


Chapter

18Network health reports

Network health statistics quantify BSS performance from a subscriber perspective. A combination of rawand other network health statistics are used by the OMC-R to calculate these statistics.

Network health statistics are available for display with the Cell device statistics in theOMC-R Performance Management window.

They network health statistics are categorized into subgroups, each of which are describedin "Network health statistics subgroups" on page 18-2.


Network health statistics subgroups Chapter 18: Network health reports

Network health statistics subgroups

Network health statistics are organized into the following major subgroups:

• "GPRS performance" on page 18-2.

• "Handover performance" on page 18-3.

• "Health check" on page 18-5.

• "Paging performance" on page 18-5.

• "Radio performance" on page 18-5.

• "SDCCH congestion" on page 18-6.

• "TCH congestion" on page 18-6.

GPRS performance

The following statistics provide key performance metrics for the GPRS system:

• "AIR_INTERFACE_BW_CS1" on page 18-8.




• "CELL_UPDATE" on page 18-21.

• "CS1_USAGE_DL" on page 18-22.

• "CS1_USAGE_UL" on page 18-23.







• "DL_AIR_INTERFACE_BW_CS1" on page 18-30.



Maintenance Information: GSM Statistics Application Network health statistics subgroups



• "DOWNLINK_TRAFFIC_VOLUME" on page 18-34.

• "GBL_AVAILABILITY" on page 18-38.

• "GPRS_BW_USAGE_DL" on page 18-39.

• "GPRS_BW_USAGE_UL" on page 18-40.

• "GPRS_DL_ACT_TS" on page 18-41.

• "GPRS_UL_ACT_TS" on page 18-42.

• "PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK" on page 18-88.

• "UL_AIR_INTERFACE_BW_CS1" on page 18-120.




• "UPLINK_PDTCH_BLOCKING_RATE" on page 18-124.

• "UPLINK_TRAFFIC_VOLUME" on page 18-125.

Handover performance

The following statistics provide general handover information:

• "HO_CAUSE_ADJ_CH_INTERF" on page 18-43.

• "HO_CAUSE_BAND_HO" on page 18-44.

• "HO_CAUSE_BAND_REASSGN" on page 18-45.

• "HO_CAUSE_CONGEST" on page 18-46.

• "HO_CAUSE_DISTANCE" on page 18-47.

• "HO_CAUSE_DLINTERF" on page 18-48.

• "HO_CAUSE_DLLEVEL" on page 18-49.

• "HO_CAUSE_DLQUAL" on page 18-50.

• "HO_CAUSE_PWRBGT" on page 18-51.

• "HO_CAUSE_UPINTERF" on page 18-52.

• "HO_CAUSE_UPLEVEL" on page 18-53.



• "HO_CAUSE_UPQUAL" on page 18-54.

• "HO_PER_CALL" on page 18-55.

• "IN_INTER_BSS_HO_SUC" on page 18-56.

• "IN_INTER_CELL_HO_SUC" on page 18-57.

• "IN_INTRA_BSS_HO_SUC" on page 18-58.

• "INCOMING_HO_VOLUME" on page 18-59.

• "INTERNAL_LOST" on page 18-60.

• "INTERNAL_RECOVERED" on page 18-61.

• "INTERNAL_SUCCESS" on page 18-62.

• "INTRA_CELL_HO_FAIL_LOST_MS" on page 18-63.

• "INTRA_CELL_HO_FAIL_RECOVERED" on page 18-64.

• "INTRA_CELL_HO_SUCCESS_RATE" on page 18-65.

• "MEAN_TIME_BETWEEN_DROPS" on page 18-68.

• "MEAN_TIME_BETWEEN_HOs" on page 18-69.

• "OUT_INTER_BSS_HO_FAIL_LOST_MS" on page 18-70.

• "OUT_INTER_BSS_HO_FAIL_RECOVERED" on page 18-71.

• "OUT_INTER_BSS_HO_SUCCESS_RATE" on page 18-72.

• "OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS" on page 18-73.

• "OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS" on page 18-74.

• "OUT_INTER_CELL_HO_SUCCESS_RATE" on page 18-75.

• "OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS" on page 18-76.

• "OUT_INTRA_BSS_HO_FAIL_LOST_MS" on page 18-77.

• "OUT_INTRA_BSS_HO_SUC" on page 18-79.

• "OUTGOING_HO_VOLUME" on page 18-80.

• "PERCENTAGE_INTER_BSS_HO" on page 18-85.

• "PERCENTAGE_INTRA_BSS_HO" on page 18-86.

• "PERCENTAGE_INTRA_CELL_HO" on page 18-87.



Health check

The following statistics provide health check information:

• "CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS" on page 18-14.

• "CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS" on page 18-16.

• "CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE" on page 18-17.

• "CALL_SETUP_SUCCESS_RATE" on page 18-18.

• "CALL_SUCCESS_RATE" on page 18-19.

• "CALL_VOLUME" on page 18-20.

• "DROP_CALL_RATE" on page 18-36.

• "RANKING_FORMULA" on page 18-89.

• "SDCCH_BLOCKING_RATE" on page 18-94.

• "SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF" on page 18-108.

• "SPILL_OVER_FACTOR_DIRECTED_RETRY" on page 18-109.

• "SPILL_OVER_FACTOR_MULTIBAND" on page 18-110.

Paging performance

The following statistics provide paging performance information:

• "AIR_INTERFACE_PAGING" on page 18-12.

• "MSC_PAGING" on page 18-67.

• "PAGING_COMPRESSION_RATE" on page 18-81.

• "PAGING_OVERFLOW_RATE" on page 18-82.

• "PAGING_RESPONSE" on page 18-83.

• "PAGING_SUCCESS_RATE" on page 18-84.

Radio performance

The following statistics provide radio performance information:

• "ASSIGNMENT_SUCCESS_RATE" on page 18-13.

• "OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS" on page 18-73.



• "OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS" on page 18-74.

• "OUT_INTER_CELL_HO_SUCCESS_RATE" on page 18-75.

• "RF_ASSIGN_FAIL_RATE_LOST_MS" on page 18-90.

• "RF_ASSIGN_FAIL_RATE_RECOVERED" on page 18-91.

• "RF_ASSIGNMENT_SUCCESS_RATE" on page 18-92.

• "TCH_RF_LOSS_RATE" on page 18-116.

SDCCH congestion

The following statistics provide SDCCH congestion information:

• "SDCCH_ACCESSES" on page 18-93.

• "SDCCH_BLOCKING_RATE" on page 18-94.

• "SDCCH_CONGESTION_TIME" on page 18-95.

• "SDCCH_TRAFFIC_CARRIED" on page 18-96.

• "SDCCH_USAGE_ACCESS_FAILURE" on page 18-98.

• "SDCCH_USAGE_CALL_REESTABLISH" on page 18-99.

• "SDCCH_USAGE_EMERGENCY_CALL" on page 18-100.

• "SDCCH_USAGE_IMSI_DETACH" on page 18-101.

• "SDCCH_USAGE_LOCATION_UPDATE" on page 18-102.

• "SDCCH_USAGE_MS_ORIGINATED_CALL" on page 18-103.

• "SDCCH_USAGE_MS_ORIGINATED_SMS" on page 18-104.

• "SDCCH_USAGE_SMS_ORIGINATED_SS" on page 18-105.

• "SDCCH_USAGE_PAGING_RESPONSE" on page 18-106.

• "SDCCH_USAGE_SMS" on page 18-107.

TCH congestion

The following statistics provide TCH congestion information:

• "MAX_TCH_BUSY" on page 18-66.

• "TCH_ACCESSES" on page 18-111.



• "TCH_CONGESTION_TIME" on page 18-113.

• "TCH_CONGESTION_TIME_INNER_ZONE" on page 18-114.

• "TCH_CONGESTION_TIME_OUTER_ZONE" on page 18-115.



AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports

AIR_INTERFACE_BW_CS1

Description

The AIR_INTERFACE_BW_CS1 statistic provides the maximum bandwidth available inkilobits per second in a cell for GPRS coding scheme 1.

Formula

_ _ _ _

Usage Network planning.Radio resource allocation.

Basis Cell.

Type Counter.

Raw Statistics GPRS_AVAIL_PDTCH.


Maintenance Information: GSM Statistics Application AIR_INTERFACE_BW_CS2


Description


Formula

_ _ _ _


Basis Cell.

Type Counter.



AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports


Description


Formula

_ _ _ _


Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application AIR_INTERFACE_BW_CS4


Description


Formula

_ _ _ _


Basis Cell.

Type Counter.



AIR_INTERFACE_PAGING Chapter 18: Network health reports

AIR_INTERFACE_PAGING

Description

The AIR_INTERFACE_PAGING statistic tracks the total number of paging requestsmessages sent on the air interface.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _


Basis Cell.

Type Counter.

Raw Statistics ACCESS_PER_PCH (The value used in this formula is the sumof bins 0 to 2 of this counter array statistic).


Maintenance Information: GSM Statistics Application ASSIGNMENT_SUCCESS_RATE

ASSIGNMENT_SUCCESS_RATE

Description

The ASSIGNMENT_SUCCESS_RATE statistic measures the success rate of the A-interface assignmentprocedure which will also automatically include the impact of the air interface assignment procedure.

Formula

_ _ _ _ __ _ _

Usage Service accessibility.Radio resource allocation.Quality of service.

Basis Cell.

Type Percentage.

Raw Statistics MA_COMPLETE_TO_MSC.MA_REQ_FROM_MSC.


CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS Chapter 18: Network health reports

CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS

Description

The CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS statistic provides the percentageof air interface call set-up assignment commands that are sent to over the air interface which result inthe MS failing to access the target channel and failing to recover to the original channel. This statisticincludes the impact of successful second assignments and intra-cell handover assignment attempts.

Formula

_ _ __ _ __

_ _ __ _ _

_ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _ _

_ _ __ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ _


Maintenance Information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_FAIL_FROM_MS.INTRA_CELL_HO_SUC.INTRA_CELL_HO_RETURN.SECOND_ASSIGN_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 1 to 4 of this counter array statistic).


CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS Chapter 18: Network health reports

CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS

Description

The CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS statistic provides thepercentage of air interface call set-up assignment commands that are sent over the air interface which result inthe 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.

Formula

_ _ __ _ _

_

_ _ __ _ _

_ __ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ __ _ _ _ _

_ _


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_FAIL_FROM_MS.INTRA_CELL_HO_RETURN.SECOND_ASSIGN_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 1 to 4 of this counter array statistic).


Maintenance Information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE

CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE

Description

The CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE statistic provides the percentageof air interface call set-up assignment commands that are successfully sent over the air interfacewhich result in the MS accessing the target channel. This statistic includes the impact of successfulsecond assignments and intra-cell handover assignment attempts.

Formula

_ _ __ _

_ _ __ _ _

_ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_COMPLETE_FROM_MS.INTRA_CELL_HO_SUC.SECOND_ASSIGN_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 1 to 4 of this counter array statistic).


CALL_SETUP_SUCCESS_RATE Chapter 18: Network health reports

CALL_SETUP_SUCCESS_RATE

Description

The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that resultin a successful TCH access. Network accesses which do not require a TCH are excluded; forexample, location updates, SMS, and Supplementary Service attempts.

Formula

_ _ _ __ _ _ _ _

_ _ __ _ _

_ _ _ __ _ _ _ _

_ _ _ _ _ __ _ _ _ _ __ _ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION.MT_LCS_ON_SDCCH.OK_ACC_PROC[CM_REESTABLISH].OK_ACC_PROC[CM_SERV_REQ_CALL].OK_ACC_PROC[CM_SERV_REQ_EMERG].OK_ACC_PROC[CM_SERV_REQ_SMS].OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].OK_ACC_PROC[PAGE_RESPONSE].SMS_INIT_ON_SDCCH.TOTAL_CALLS.


Maintenance Information: GSM Statistics Application CALL_SUCCESS_RATE

CALL_SUCCESS_RATE

Description

This statistic represents the portion of MS call transactions with normal completions at the radio subsystem,providing an overall indication of network performance from a subscriber perspective.

A combination of the CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATE networkhealth statistics is used to calculate this statistic. The raw statistics used to calculate thesehealth statistics are included in the raw statistics listing.

Formula

_ _ _ _ _ _ _

Usage Quality of service.Service retainability.Service accessibility.Fault finding.

Basis Cell.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION.IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].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_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].RF_LOSSES_TCH.SMS_INIT_ON_SDCCH.TOTAL_CALLS.


CALL_VOLUME Chapter 18: Network health reports

CALL_VOLUME

Description

The CALL_VOLUME statistic tracks the number of call setups which result in a successful TCH access.

Formula

_

__ _

_ __ _

Usage Network planning.Installation and commissioning.Service accessibility.

Basis Cell.

Type Counter.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).TOTAL_CALLS.


Maintenance Information: GSM Statistics Application CELL_UPDATE

CELL_UPDATE

Description

The CELL_UPDATE statistic measures the number of cell reselections relating to a particular cell.

Formula

_ _ _


Basis Cell.

Type Counter.

Raw Statistics CELL_FLUSH_REQS.


CS1_USAGE_DL Chapter 18: Network health reports

CS1_USAGE_DL


Description

The CS1_USAGE_DL statistic provides the percentage of Radio Link Control blocks transmittedby the PCU (downlink) using GPRS coding scheme 1.

Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.

Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS1].AIR_DL_DATA_BLKS[QOS2_CS1].AIR_DL_DATA_BLKS[QOS3_CS1].AIR_DL_DATA_BLKS all bins.


Maintenance Information: GSM Statistics Application CS1_USAGE_UL

CS1_USAGE_UL


Description

The CS1_USAGE_UL statistic provides the percentage of Radio Link Control blocks receivedby the PCU (uplink) using GPRS coding scheme 1.

Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.

Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS1].AIR_UL_DATA_BLKS[QOS2_CS1].AIR_UL_DATA_BLKS[QOS3_CS1].AIR_UL_DATA_BLKS all bins.



CS2_USAGE_DL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.




CS2_USAGE_UL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.




CS3_USAGE_DL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.




CS3_USAGE_UL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.




CS4_USAGE_DL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.




CS4_USAGE_UL


Description


Formula

_ _

_ _ _ _ _ _ _ __ _ _ _

_ _ _



Basis Cell.

Type Percentage.



DL_AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports

DL_AIR_INTERFACE_BW_CS1

Description

The DL_AIR_INTERFACE_BW_CS1 statistic provides a reference value in kilobits per second for theconfigured downlink bandwidth in a cell in terms of coding scheme 1 for a statistics collection period.

FormulaFor GSR6 (Horizon II) the formula is:

_ _ _ __


Basis Cell.

Type Counter.

Raw Statistics GPRS_AVAIL_PDTCH.INTERVAL is either 0.5 for a 30 minute collection period or 1 fora 60 minute collection period.


Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS2


Description



_ _ _ __


Basis Cell.

Type Counter.



DL_AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports


Description



_ _ _ __


Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS4


Description



_ _ _ __


Basis Cell.

Type Counter.



DOWNLINK_TRAFFIC_VOLUME Chapter 18: Network health reports

DOWNLINK_TRAFFIC_VOLUME


Description

The DOWNLINK_TRAFFIC_VOLUME statistic provides a measure of the volume of downlinkRadio Link Control traffic including retransmitted blocks.

Formula

_ _

_ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ _



Maintenance Information: GSM Statistics Application DOWNLINK_TRAFFIC_VOLUME


Basis Cell.

Type Percentage.

Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS1].AIR_DL_DATA_BLKS[QOS2_CS1].AIR_DL_DATA_BLKS[QOS3_CS1].AIR_DL_DATA_BLKS[QOS1_CS2].AIR_DL_DATA_BLKS[QOS2_CS2].AIR_DL_DATA_BLKS[QOS3_CS2].AIR_DL_DATA_BLKS[QOS1_CS3].AIR_DL_DATA_BLKS[QOS2_CS3].AIR_DL_DATA_BLKS[QOS3_CS3].AIR_DL_DATA_BLKS[QOS1_CS4].AIR_DL_DATA_BLKS[QOS2_CS4].AIR_DL_DATA_BLKS[QOS3_CS4].INTERVAL is either 0.5 for a 30 minute collection period or 1 fora 60 minute collection period.


DROP_CALL_RATE Chapter 18: Network health reports

DROP_CALL_RATE

Description

The DROP_CALL_RATE statistic tracks the percentage of MSs which, having successfullyaccessed a TCH, subsequently experience an abnormal release caused by either radio or equipmentproblems. This includes RF losses and losses during handovers.

Formulas

Cell Level

{22064}

_ _

_ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ _

__ _ _ _ _ _ __ _ _ _ _ _ _

BSS Level

{22064}

_ _

_ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ _

__ _

_ __ _

_ _ _ _ _ _ _

Network Level

{22064}

_ _

_ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _ _ _

__ _

_ __ _


Maintenance Information: GSM Statistics Application DROP_CALL_RATE

Analysis

Usage Fault finding.Service retainability.

Basis Cell, BSS, or network.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formula is thesum of bins 0 to 2 of this counter array statistic).IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].OUT_INTER_BSS_HO[OUT_INTRA_BSS_HO_CLEARED].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].RF_LOSSES_TCH.{22064}RF_LOSSES_TCH_HR.TOTAL_CALLS.


GBL_AVAILABILITY Chapter 18: Network health reports

GBL_AVAILABILITY

Description

The GBL_AVAILABILITY statistic measures the availability for a particular Gb link (GBL).

Formula

_ _ _


Basis GBL.

Type Counter.

Raw Statistics GBL_LINK_INS.INTERVAL is either 0.5 for a 30 minute collection period or 1 fora 60 minute collection period.


Maintenance Information: GSM Statistics Application GPRS_BW_USAGE_DL

GPRS_BW_USAGE_DL


Description

The GPRS_BW_USAGE_DL statistic measures the bandwidth usage in the downlink direction andprovides an indication of the adequacy of the deployed cell capacity.

Formula

_ _ _ _ _ __ _


Basis Cell.

Type Percentage.

Raw Statistics AIR_DL_DATA_BLKS.GPRS_AVAIL_PDTCH.INTERVAL is either 0.5 for a 30 minute collection period or 1 fora 60 minute collection period.


GPRS_BW_USAGE_UL Chapter 18: Network health reports

GPRS_BW_USAGE_UL


Description

The GPRS_BW_USAGE_UL statistic measures the bandwidth usage in the uplink direction andprovides an indication of the adequacy of the deployed cell capacity.

Formula

_ _ _ _ _ __ _


Basis Cell.

Type Percentage.

Raw Statistics AIR_UL_DATA_BLKS.GPRS_AVAIL_PDTCH.INTERVAL is either 0.5 for a 30 minute collection period or 1 fora 60 minute collection period.


Maintenance Information: GSM Statistics Application GPRS_DL_ACT_TS

GPRS_DL_ACT_TS

Description

The GPRS_DL_ACT_TS statistic measures the utilization of busy downlink PDTCHs in a cell.

Formula

_ _ _ _ _ _


Basis Cell.

Type Counter.

Raw Statistics DL_BUSY_PDTCH.


GPRS_UL_ACT_TS Chapter 18: Network health reports

GPRS_UL_ACT_TS

Description

The GPRS_UL_ACT_TS statistic measures the utilization of busy uplink PDTCHs in a cell.

Formula

_ _ _ _ _ _


Basis Cell.

Type Counter.

Raw Statistics UL_BUSY_PDTCH.


Maintenance Information: GSM Statistics Application HO_CAUSE_ADJ_CH_INTERF

HO_CAUSE_ADJ_CH_INTERF

Description

The HO_CAUSE_ADJ_CH_INTERF statistic provides the percentage of all handoversdue to adjacent channel interference.

Formula

_ __ _

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.

Raw Statistics OUT_HO_CAUSE_ATMPT.


HO_CAUSE_BAND_HO Chapter 18: Network health reports

HO_CAUSE_BAND_HO

Description

The HO_CAUSE_BAND_HO statistic provides the percentage of all handovers due to band handover.

Formula

_ __

_ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_CAUSE_BAND_REASSGN

HO_CAUSE_BAND_REASSGN

Description

The HO_CAUSE_BAND_REASSGN statistic provides the percentage of all han-dovers due to band reassignment.

Formula

_ __

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



HO_CAUSE_CONGEST Chapter 18: Network health reports

HO_CAUSE_CONGEST

Description

The HO_CAUSE_CONGEST statistic provides the percentage of all handovers due tocongestion (directed retry or congestion relief).

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_CAUSE_DISTANCE

HO_CAUSE_DISTANCE

Description

The HO_CAUSE_DISTANCE statistic provides the percentage of all handoversdue to distance (timing advance).

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



HO_CAUSE_DLINTERF Chapter 18: Network health reports

HO_CAUSE_DLINTERF

Description

TheHO_CAUSE_DLINTERF statistic provides the percentage of all handovers due to downlink interference.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_CAUSE_DLLEVEL

HO_CAUSE_DLLEVEL

Description

The HO_CAUSE_DLLEVEL statistic provides the percentage of all handovers due to downlink level.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



HO_CAUSE_DLQUAL Chapter 18: Network health reports

HO_CAUSE_DLQUAL

Description

The HO_CAUSE_DLQUAL statistic provides the percentage of all handovers due to downlink quality.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_CAUSE_PWRBGT

HO_CAUSE_PWRBGT

Description

The HO_CAUSE_PWRBGT statistic provides the percentage of all handovers due to power budget.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



HO_CAUSE_UPINTERF Chapter 18: Network health reports

HO_CAUSE_UPINTERF

Description

The HO_CAUSE_UPINTERF statistic provides the percentage of all handovers due to uplink interference.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_CAUSE_UPLEVEL

HO_CAUSE_UPLEVEL

Description

The HO_CAUSE_UPLEVEL statistic provides the percentage of all handovers due to uplink level.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



HO_CAUSE_UPQUAL Chapter 18: Network health reports

HO_CAUSE_UPQUAL

Description

The HO_CAUSE_UPQUAL statistic provides the percentage of all handovers due to uplink quality.

Formula

_ _ _ _ __ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application HO_PER_CALL

HO_PER_CALL

Description

The HO_PER_CALL statistic tracks the average number of successful handovers per call.

FormulaCell Level

_ _

_ _ _ __ _ _ _ _ _ _

_

BSS Level

_ _

_ _ _ __ _ _ _ _ _ _

__ _

_ __ _

Network Level

_ _

_ _ _ __ _ _ _ _ _ _

__ _

_ __ _


Basis Cell, BSS or network.

Type Counter.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).INTRA_CELL_HO[INTRA_CELL_HO_SUC].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].TOTAL_CALLS.


IN_INTER_BSS_HO_SUC Chapter 18: Network health reports

IN_INTER_BSS_HO_SUC

Description

The IN_INTER_BSS_HO_SUC statistic tracks the percentage of incoming inter-BSS handover commandsthat are sent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ __

_ _ _ __ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics IN_INTER_BSS_HO_SUC.HO_REQ_ACK_TO_MSC.


Maintenance Information: GSM Statistics Application IN_INTER_CELL_HO_SUC

IN_INTER_CELL_HO_SUC

Description

The IN_INTER_CELL_HO_SUC statistic tracks the percentage of incoming inter-cell handover commandsthat are sent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ __

_ _ _ _ _ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics IN_INTRA_BSS_HO_SUC.IN_INTER_BSS_HO_SUC.IN_INTRA_BSS_HO (The value used in this formula is the sum ofbins 0 to 4 of this counter array statistic).HO_REQ_ACK_TO_MSC.


IN_INTRA_BSS_HO_SUC Chapter 18: Network health reports

IN_INTRA_BSS_HO_SUC

Description

The IN_INTRA_BSS_HO_SUC statistic tracks the percentage of incoming intra-BSS handover commandsthat are sent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ __

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ __ _ _

_ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics IN_INTRA_BSS_HO_SUC.IN_INTRA_BSS_HO (The value used in this formula is the sumof bins 0 to 4 of this counter array statistic).


Maintenance Information: GSM Statistics Application INCOMING_HO_VOLUME

INCOMING_HO_VOLUME

Description

The INCOMING_HO_VOLUME statistic provides the number of successful incoming handovers.

FormulasCell Level

_ __ _ _ _ _ _ _

_ _ _ _ _ _ _

BSS Level

_ _ _ _ _ _ _ _ _


Basis Cell or BSS.

Type Counter.

Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].


INTERNAL_LOST Chapter 18: Network health reports

INTERNAL_LOST

Description

The INTERNAL_LOST statistic tracks the percentage of BSS internal handover commands that are sentover the air interface which result in the MS failing to access the target and failing to recover to the originalchannel; that is, the call drops. This statistic includes intra-BSS and intra-cell handovers.

Formula

_

_ _ _ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].


Maintenance Information: GSM Statistics Application INTERNAL_RECOVERED

INTERNAL_RECOVERED

Description

The INTERNAL_RECOVERED statistic tracks the percentage of BSS internal handover commands thatare sent over the air interface which result in the MS failing to access the target channel and successfullyrecovering to the original channel. This statistic includes intra-BSS and intra-cell handovers.

Formula

_

_ _ _ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].INTRA_CELL_HO[INTRA_CELL_HO_RETURN].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].


INTERNAL_SUCCESS Chapter 18: Network health reports

INTERNAL_SUCCESS

Description

The INTERNAL_SUCCESS statistic tracks the percentage of BSS internal handover commandsthat are sent over the air interface which result in the MS successfully accessing the targetchannel. This statistic includes intra-BSS and intra-cell handovers.

Formula

_

_ _ _ _ _ _ __ _ _ _ _

_ _ _ _ _ _ __ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].INTRA_CELL_HO[INTRA_CELL_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


Maintenance Information: GSM Statistics Application INTRA_CELL_HO_FAIL_LOST_MS

INTRA_CELL_HO_FAIL_LOST_MS

Description

The INTRA_CELL_HO_FAIL_LOST_MS statistic tracks the percentage of intra-cell assignmentcommands that are sent over the air interface which result in the MS failing to access the targetchannel and failing to recover to the original channel; that is, the call drops.

Formula

_ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ _



Type Percentage.

Raw Statistics INTRA_CELL_HO (The value used in this formula is bin 6 andthe sum of bins 1 to 4 of this counter array statistic).


INTRA_CELL_HO_FAIL_RECOVERED Chapter 18: Network health reports

INTRA_CELL_HO_FAIL_RECOVERED

Description

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

Formula

_ _ __

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ _



Type Percentage.



Maintenance Information: GSM Statistics Application INTRA_CELL_HO_SUCCESS_RATE

INTRA_CELL_HO_SUCCESS_RATE

Description

The INTRA_CELL_HO_SUCCESS_RATE statistic tracks the percentage of intra-cell assignmentcommands that are sent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ __

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ _



Type Percentage.



MAX_TCH_BUSY Chapter 18: Network health reports

MAX_TCH_BUSY

Description

TheMAX_TCH_BUSY statistic tracks the maximum number of simultaneously busy TCHs.

Formula

_ _ _


Basis Cell.

Type Counter.

Raw Statistics BUSY_TCH[MAX].


Maintenance Information: GSM Statistics Application MSC_PAGING

MSC_PAGING

Description

The MSC_PAGING statistic tracks the total number of BSSMAP paging messagesreceived over the A-interface from the MSC.

Formula

_ _ _ _


Basis Cell.

Type Counter.

Raw Statistics PAGE_REQ_FROM_MSC.


MEAN_TIME_BETWEEN_DROPS Chapter 18: Network health reports

MEAN_TIME_BETWEEN_DROPS

Description

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

Formula

{22064}

_ __

_ __ _ _

_

_ __ _ _

_ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _

Analysis


Basis Cell.

Type Time interval.

Raw Statistics BUSY_TCH_MEAN.{22064}BUSY_TCH_HR_MEAN.RF_LOSSES_TCH_MEAN.RF_LOSSES_TCH_HR_AMR_MEAN.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].


Maintenance Information: GSM Statistics Application MEAN_TIME_BETWEEN_HOs

MEAN_TIME_BETWEEN_HOs

Description

TheMEAN_TIME_BETWEEN_HOs statistic tracks the mean time interval between inter cell handovers.

Formula

{22064}

_ __

_ __ _ _

_

_ _ _ _ _ _ __ _ _ _ _ _ _

_ _ _ _ _

Analysis


Basis Cell.

Type Time interval (in seconds).

Raw Statistics BUSY_TCH_MEAN.{22064}BUSY_TCH_HR_MEANOUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].INTRA_CELL_HO[INTRA_CELL_HO_SUC].


OUT_INTER_BSS_HO_FAIL_LOST_MS Chapter 18: Network health reports

OUT_INTER_BSS_HO_FAIL_LOST_MS

Description

The OUT_INTER_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of inter-BSS handovercommands that are sent over the air interface which result in the MS failing to access the targetchannel and failing to recover to the original channel; that is, the call drops.

Formula

_ _ _ _ __

_ _ _ __ _ _ _


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[OUT_INTER_BSS_HO_SUC].


Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO_FAIL_RECOVERED

OUT_INTER_BSS_HO_FAIL_RECOVERED

Description

The OUT_INTER_BSS_HO_FAIL_RECOVERED statistic tracks the percentage of inter-BSShandover commands that are sent over the air interface which result in the MS failing to access thetarget channel and a subsequently successful recovering to the original channel.

Formula

_ _ _ _ _ _ _ _ _ _ _ __ _ _ _ _ _ _


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 Chapter 18: Network health reports

OUT_INTER_BSS_HO_SUCCESS_RATE

Description

The OUT_INTER_BSS_HO_SUCCESS_RATE statistic tracks the percentage of inter-BSS handovercommands that are sent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ _ __

_ _ _ _ _ _ __ _ _ _ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].


Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS

OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS

Description

The OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS statistic tracks the percentage ofinter-cell handover commands that are sent over the air interface which result in the MS failingto access the target channel and failing to recover to the original channel; that is, the calldrops. This statistic does not include intra-cell handovers.

Formula

_ _ _ __ _ _

_ _ _ __ _ _ _ __ _ _ __ _ _ _


Basis Cell.

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[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].


OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS Chapter 18: Network health reports

OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS

Description

The OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS statistic tracks the percentageof inter-cell handover commands that are sent over the air interface which result in the MSfailing to access the target channel and a subsequently successful recovering to the originalchannel. This statistic does not include intra-cell handovers.

Formula

_ _ __ _ _

_

_ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ __ _ _ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].


Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_SUCCESS_RATE

OUT_INTER_CELL_HO_SUCCESS_RATE

Description

The OUT_INTER_CELL_HO_SUCCESS_RATE statistic tracks the percentage of inter-cellhandover commands that result in the MS successfully accessing the target channel. Thisstatistic includes intra-BSS and inter-BSS inter-cell handovers.

Formula

_ _ __ _

_ _ _ __ _ _ _

_ _ _ __ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS Chapter 18: Network health reports

OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS

Description

The OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS statistic tracks the percentageof inter-cell handover commands that are sent over the air interface which result in the MS successfullyaccessing the target channel and successfully re-establishing on the original channel.

Formula

_ _ __ _ _

_

_ _ _ __ _ _ __ _ _ __ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics OUT_INTRA_BSS_HO_RETURN.OUT_INTER_BSS_HO_RETURN.OUT_INTRA_BSS_HO_ATMPT.OUT_INTER_BSS_HO_ATMPT.


Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO_FAIL_LOST_MS

OUT_INTRA_BSS_HO_FAIL_LOST_MS

Description

The OUT_INTRA_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of intra-BSS handovercommands that are sent over the air interface which result in the MS failing to access the targetchannel and failing to recover to the original channel; that is, the call drops.

Formula

_ _ _ _ __

_ _ _ __ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].


OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS Chapter 18: Network health reports

OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS

Description

The OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS statistic tracks the percentage of intra-BSShandover commands that are sent over the air interface which result in the MS failing to access thetarget channel and a subsequently successful recovering to the original channel.

Formula

_ _ _ _ __

_ _ _ _ _ _ __ _ _ _ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].


Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO_SUC

OUT_INTRA_BSS_HO_SUC

Description

The OUT_INTRA_BSS_HO_SUC statistic tracks the percentage of intra-BSS handover commands that aresent over the air interface which result in the MS successfully accessing the target channel.

Formula

_ _ __

_ _ _ _ _ _ __ _ _ _ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


OUTGOING_HO_VOLUME Chapter 18: Network health reports

OUTGOING_HO_VOLUME

Description

The OUTGOING_HO_VOLUME statistic tracks the number of successful outgoing handovers.

Formula

_ _ _ _ _ _ _ _ __ _ _ _ _ _ _


Basis Cell or BSS.

Type Counter.

Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].


Maintenance Information: GSM Statistics Application PAGING_COMPRESSION_RATE

PAGING_COMPRESSION_RATE

Description

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

Formula

__

_ _ _ _ _ __ _ _ _ __ _ _ _ __ _ __ _ _


Basis Cell.

Type Percentage.

Raw Statistics ACCESS_PER_PCH (The value used in this formula is the sum ofbins 0 to 2 of this counter array statistic).PAGING_REQUESTS (The value used in this formula is the sumof bins 1 and 2 of this counter array statistic).


PAGING_OVERFLOW_RATE Chapter 18: Network health reports

PAGING_OVERFLOW_RATE

Description

The PAGING_OVERFLOW_RATE statistic tracks the percentage of pages which are droppedfrom the BSS paging queue due to paging queue overflow. There are two formulas based onthe paging purpose (circuit switched or packet switched).

FormulasCircuit switched

_ __

_ _ __ _ _

Packet switched

_ __

_ _ __ _ _



Type Percentage.

Raw Statistics PCH_PAGE_Q_DISCARD[CS].PCH_PAGE_Q_DISCARD[PS].PAGING_REQUESTS[PAGING_REQS_CS].PAGING_REQUESTS[PAGING_REQS_PS].


Maintenance Information: GSM Statistics Application PAGING_RESPONSE

PAGING_RESPONSE

Description

The PAGING_RESPONSE statistic tracks the volume of MSs which respond to apage through a successful SDCCH access.

Formula

_ _ _ _



Type Counter.

Raw Statistic OK_ACC_PROC[PAGE_RESPONSE].


PAGING_SUCCESS_RATE Chapter 18: Network health reports

PAGING_SUCCESS_RATE

Description

The PAGING_SUCCESS_RATE statistic tracks the percentage of pages which receive a successfulresponse from an MS. This statistic is measured on a location area basis.

Formula

_ _ _ _ __

where SUM (OK_ACC_PROC[PAGE_RESPONSE]) is summed across all cells in the locationarea and assuming paging is configured on a location area basis, PAGE_REQ_FROM_MSCis the maximum value occurring on any cell within the LAC.

Usage Quality of service.Fault finding

Basis Location area.

Type Percentage.

Raw Statistics OK_ACC_PROC[PAGE_RESPONSE].PAGE_REQ_FROM_MSC.


Maintenance Information: GSM Statistics Application PERCENTAGE_INTER_BSS_HO

PERCENTAGE_INTER_BSS_HO

Description

The PERCENTAGE_INTER_BSS_HO statistic calculates the percentage of all inter-BSS handover attempts.

Formula

__ _

_ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _ _

_ _ _ __ _ _

_ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTER_BSS_HO_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 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 Chapter 18: Network health reports

PERCENTAGE_INTRA_BSS_HO

Description

ThePERCENTAGE_INTRA_BSS_HO statistic calculates the percentage of all intra-BSS handover attempts.

Formula

__ _

_ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _ _

_ _ _ __ _ _

_ _ _ _


Basis BSS.

Type Percentage.

Raw Statistics OUT_INTRA_BSS_HO_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 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].


Maintenance Information: GSM Statistics Application PERCENTAGE_INTRA_CELL_HO

PERCENTAGE_INTRA_CELL_HO

Description

The PERCENTAGE_INTRA_CELL_HO statistic calculates the percentage of allintra-cell handover attempts.

Formula

__ _

_ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _

_ _ _ _ __ _ _

_ _ _ __ _ _

_ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics INTRA_CELL_HO_ATMPT.INTRA_CELL_HO (The value used in this formula is the sum ofbins 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_OF_ALL_TRAFFIC_IN_DOWNLINK Chapter 18: Network health reports

PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK


Description

The PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK statistic provides a ratio ofthe GPRS downlink traffic against the uplink traffic.

Formula

_ _ _ __

_ _ __ _ _ _ _ _


Basis Cell.

Type Percentage.

Raw Statistics AIR_DL_DATA_BLKS.AIR_UL_DATA_BLKS.


Maintenance Information: GSM Statistics Application RANKING_FORMULA

RANKING_FORMULA

Description

The RANKING_FORMULA statistic provides a measure by which cells can be ranked byperformance. This permits cells requiring optimization to be identified. The value of this statisticincreases as cells have high calling volumes and low call success rates. High values for thisstatistic indicate which cells which should be optimized first.

A combination of the CALL_SUCCESS_RATE and CALL_SETUP_SUCCESS_RATEnetwork health statistics is used to calculate this statistic. The raw statistics used to calculatethese health statistics are included in the raw statistics listing.

Formula

__ _ _

_ _ _

Usage Optimization.Service retainability.

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].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].OK_ACC_PROC[CM_REESTABLISH].OK_ACC_PROC[CM_SERV_REQ_CALL].OK_ACC_PROC[CM_SERV_REQ_EMERG].OK_ACC_PROC[CM_SERV_REQ_SMS].OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].OK_ACC_PROC[PAGE_RESPONSE].OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].RF_LOSSES_TCH.SMS_INIT_ON_SDCCH.TOTAL_CALLS.


RF_ASSIGN_FAIL_RATE_LOST_MS Chapter 18: Network health reports

RF_ASSIGN_FAIL_RATE_LOST_MS

Description

The RF_ASSIGN_FAIL_RATE_LOST_MS statistic provides the percentage of assignment commands thatare sent to over the air interface which result in the MS failing to access the target channel and failing to recoverto the original channel; that is, the call drops. This statistic includes intra-cell handover assignment attempts.

Formula

_ _ __ _

_ _ _ _ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_COMPLETE_FROM_MS.MA_FAIL_FROM_MS.


Maintenance Information: GSM Statistics Application RF_ASSIGN_FAIL_RATE_RECOVERED

RF_ASSIGN_FAIL_RATE_RECOVERED

Description

The RF_ASSIGN_FAIL_RATE_RECOVERED statistic provides the percentage of assignment commandsthat are sent over the air interface which result in the MS failing to access the target channel and subsequentlysuccessfully recovering to the original channel. This statistic includes intra-cell handover assignment attempts.

Formula

_ _ _ _ _ _ __ _ _


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_FAIL_FROM_MS.


RF_ASSIGNMENT_SUCCESS_RATE Chapter 18: Network health reports

RF_ASSIGNMENT_SUCCESS_RATE

Description

The RF_ASSIGNMENT_SUCCESS_RATE statistic provides the percentage of assignmentcommands that are successfully sent over the air interface which result in the MS accessing the targetchannel. This statistic includes intra-cell handover assignment attempts.

Formula

_ _ _ _ _ __ _ _


Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.MA_COMPLETE_FROM_MS.


Maintenance Information: GSM Statistics Application SDCCH_ACCESSES

SDCCH_ACCESSES

Description

The SDCCH_ACCESSES statistic tracks the number of SDCCH activations whichresult in a successful seizure by the MS.

Formula

_ _ _ _ _

Usage RF loss.Congestion.Quality of service.Network planning.

Basis Cell.

Type Counter.

Raw Statistics ALLOC_SDCCH.CHAN_REQ_MS_FAIL.


SDCCH_BLOCKING_RATE Chapter 18: Network health reports

SDCCH_BLOCKING_RATE

Description

The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an SDCCH that wereblocked due to no available SDCCH resources. This statistic includes incoming SDCCH handover attempts.

Formula

_ _ _ __ _ _

Usage Service accessibility.Quality of Service Monitoring.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics ALLOC_SDCCH.ALLOC_SDCCH_FAIL.


Maintenance Information: GSM Statistics Application SDCCH_CONGESTION_TIME

SDCCH_CONGESTION_TIME

Description

The SDCCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all SDCCHs are busy.

Formula

_ _ _

Usage RF loss.Congestion.Quality of service.Network planning.Optimization.

Basis Cell.

Type Duration (seconds).

Raw Statistics SDCCH_CONGESTION.


SDCCH_TRAFFIC_CARRIED Chapter 18: Network health reports

SDCCH_TRAFFIC_CARRIED

Description

The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busySDCCHs measured in Erlangs.

Formula

_ _ _ _


_ __ _


_ _ _ _


_ __ _


Maintenance Information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED

The BUSY_SDCCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.Where BUSY_SDCCH_MEAN [ ] isBUSY_SDCCH_MEAN for statistical interval .

Usage RF loss.Congestion.Network planning.Optimization.

Basis BSS.

Type Counter.

Raw Statistic BUSY_SDCCH.


SDCCH_USAGE_ACCESS_FAILURE Chapter 18: Network health reports

SDCCH_USAGE_ACCESS_FAILURE

Description

The SDCCH_USAGE_ACCESS_FAILURE statistic tracks the percentage of immediate assignmentSDCCH activations that fail to achieve successful SDCCH access.

Formula

_ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.

Raw Statistics 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_REESTABLISH].OK_ACC_PROC[LOCATION_UPDATE].OK_ACC_PROC[IMSI_DETACH].CHAN_REQ_MS_FAIL.


Maintenance Information: GSM Statistics Application SDCCH_USAGE_CALL_REESTABLISH

SDCCH_USAGE_CALL_REESTABLISH

Description

The SDCCH_USAGE_CALL_REESTABLISH statistic tracks the percentage of immediateassignment SDCCH activations that are due to call re-establish attempts.

Formula

_ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



SDCCH_USAGE_EMERGENCY_CALL Chapter 18: Network health reports

SDCCH_USAGE_EMERGENCY_CALL

Description

The SDCCH_USAGE_EMERGENCY_CALL statistic tracks the percentage of immediate assignmentSDCCH activations that are due to mobile originated emergency call attempts.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application SDCCH_USAGE_IMSI_DETACH

SDCCH_USAGE_IMSI_DETACH

Description

The SDCCH_USAGE_IMSI_DETACH statistic tracks the percentage of immediate assignmentSDCCH activations that are due to IMSI detach attempts.

Formula

_ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



SDCCH_USAGE_LOCATION_UPDATE Chapter 18: Network health reports

SDCCH_USAGE_LOCATION_UPDATE

Description

The SDCCH_USAGE_LOCATION_UPDATE statistic tracks the percentage of immediateassignment SDCCH activations that are due to location update attempts.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application SDCCH_USAGE_MS_ORIGINATED_CALL

SDCCH_USAGE_MS_ORIGINATED_CALL

Description

The SDCCH_USAGE_MS_ORIGINATED_CALL statistic tracks the percentage of immediate assignmentSDCCH activations that are due to non-emergency mobile originated call attempts.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



SDCCH_USAGE_MS_ORIGINATED_SMS Chapter 18: Network health reports

SDCCH_USAGE_MS_ORIGINATED_SMS

Description

The SDCCH_USAGE_MS_ORIGINATED_SMS statistic tracks the percentage of immediate assignmentSDCCH activations that are due to non-emergency mobile originated SMS attempts.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application SDCCH_USAGE_SMS_ORIGINATED_SS

SDCCH_USAGE_SMS_ORIGINATED_SS

Description

The SDCCH_USAGE_SMS_ORIGINATED_SS statistic tracks the percentage of immediate assignmentSDCCH activations that are due to non-emergency mobile originated Supplementary Service (SS) attempts.

Formula

_ _ _ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



SDCCH_USAGE_PAGING_RESPONSE Chapter 18: Network health reports

SDCCH_USAGE_PAGING_RESPONSE

Description

The SDCCH_USAGE_PAGING_RESPONSE statistic tracks the percentage of immediateassignment SDCCH activations that are due to mobile terminated transaction attempts (forexample, calls, SMSs or Supplementary Services).

Formula

_ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.



Maintenance Information: GSM Statistics Application SDCCH_USAGE_SMS

SDCCH_USAGE_SMS

Description

The SDCCH_USAGE_SMS statistic tracks the percentage of immediate assignment SDCCH activationsthat are due to mobile originated or mobile terminated SMS attempts.

Formula

_ _ _ _ _ __ _ _ _ __ _ _ _ _

_ _ _ _ __ _ _ _ _

_ _ __ _ _

_ _ __ _ _

_ _ _


Basis Cell.

Type Percentage.

Raw Statistics SMS_INIT_ON_SDCCH.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_REESTABLISH].OK_ACC_PROC[LOCATION_UPDATE].OK_ACC_PROC[IMSI_DETACH].CHAN_REQ_MS_FAIL.


SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF Chapter 18: Network health reports

SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF

Description

The SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF statistic tracksthe percentage of successful call set-ups initiated in a cell which caused an existing call tobe subject to a congestion relief handover attempt.

Formula

_ _ __ __

_ _ __

_ __ _

_ _


Basis Cell.

Type Percentage.

Raw Statistics CONGEST_EXIST_HO_ATMPT.ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).TOTAL_CALLS.


Maintenance Information: GSM Statistics Application SPILL_OVER_FACTOR_DIRECTED_RETRY

SPILL_OVER_FACTOR_DIRECTED_RETRY

Description

The SPILL_OVER_FACTOR_DIRECTED_RETRY statistic tracks the percentage ofsuccessful call set-ups initiated in a cell which complete TCH assignment in a neighbouringcell via directed retry or a handover during assignment.

Formula

_ _ __

_ __ _

__ _

_ __ _


Basis Cell.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulauses bins 0 to 2 of this counter array statistic).TOTAL_CALLS.


SPILL_OVER_FACTOR_MULTIBAND Chapter 18: Network health reports

SPILL_OVER_FACTOR_MULTIBAND

Description

The SPILL_OVER_FACTOR_MULTIBAND statistic tracks the percentage of successful call set-upsinitiated in a cell which completed TCH assignment in a neighbouring cell via a multiband handover.

Formula

_ _ _ _ __

_ __ _

_ _


Basis Cell.

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulauses the bins 0 to 2 of this counter array statistic).TOTAL_CALLS.


Maintenance Information: GSM Statistics Application TCH_ACCESSES

TCH_ACCESSES

Description

The TCH_ACCESSES statistic tracks the number of TCH activations which resultin a successful seizure by the MS.

FormulaCell Level

_

_

_ _ _ _

_ _ _ _

BSS Level

_

_

_ _ _ _

_ _

_ _

_ _

Network Level

_

_

_ _

_ _

_ _


TCH_ACCESSES Chapter 18: Network health reports

Usage Handover.Quality of service.Network planning.


Type Counter.

Raw Statistics ASSIGNMENT_REDIRECTION.IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].TOTAL_CALLS.


Maintenance Information: GSM Statistics Application TCH_CONGESTION_TIME

TCH_CONGESTION_TIME

Description

The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all TCHs are busy.

Formula

_ _ _


Basis Cell.

Type Duration.

Raw Statistics TCH_CONGESTION.


TCH_CONGESTION_TIME_INNER_ZONE Chapter 18: Network health reports

TCH_CONGESTION_TIME_INNER_ZONE

Description

The TCH_CONGESTION_TIME_INNER_ZONE statistic tracks the amount of timein seconds that all inner zone TCHs are busy.

Formula

_ _ __

_ _ _


Basis Cell.

Type Duration.

Raw Statistics TCH_CONGESTION_INNER_Z.


Maintenance Information: GSM Statistics Application TCH_CONGESTION_TIME_OUTER_ZONE

TCH_CONGESTION_TIME_OUTER_ZONE

Description

The TCH_CONGESTION_TIME_OUTER_ZONE statistic tracks the amount of timein seconds that all outer zone TCHs are busy.

Formula

_ _ __

_

{22064} When the Half Rate feature is unrestricted, the following formula tracks the amountof time in seconds that all outer zone half rate TCHs are busy:

_ _ __ _

_ _

Analysis


Basis Cell.

Type Duration.

Raw Statistics TCH_CONGESTION.

{22064} Additional Raw Statisticfor Half Rate

TCH_CONGESTION_HR.


TCH_RF_LOSS_RATE Chapter 18: Network health reports

TCH_RF_LOSS_RATE

Description

The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that areabnormally released due to a failure on the radio interface.

Formula

Cell Level

{22064}

_ _ __ _ _ _ _

_ _ _ _ _

_ _ _ _

BSS Level

{22064}

_ _ __ _ _ _ _

_

_ _

_ _

_ _

_ _ _ _ _ _

Network Level

{22064}

_ _ __ _ _ _ _

__ _

_ __ _

Analysis


Basis Cell.


Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE

Type Percentage.

Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formulais the sum of bins 0 to 2 of this counter array statistic).IN_INTER_BSS[IN_INTER_HO_SUC].IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].RF_LOSSES_TCH.{22064}RF_LOSSES_TCH_HR.TOTAL_CALLS.


TCH_TRAFFIC_CARRIED Chapter 18: Network health reports

TCH_TRAFFIC_CARRIED

Description

The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.

Formula

For an individual cell for an individual statistics interval:

{22064}

_ _ _ _ _ _ _


{22064}

_ __ _ _ _ _


{22064}

_ _ _ _ _ _ _


{22064}

_ __ _ _ _ _

The BUSY_TCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.Where BUSY_TCH_MEAN [ ] isBUSY_TCH_MEAN for statistical interval .


Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED

Analysis


Basis Cell.

Type Units = Erlangs.

Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).{22064}BUSY_TCH_HR (BUSY_TCH_HR_MEAN).


UL_AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports

UL_AIR_INTERFACE_BW_CS1

Description

The UL_AIR_INTERFACE_BW_CS1 statistic provides a reference value for the configured uplinkbandwidth in a cell in terms of coding scheme 1 for a statistics collection period.


_ _ _ __


Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS2


Description



_ _ _ __


Basis Cell.

Type Counter.



UL_AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports


Description



_ _ _ __


Basis Cell.

Type Counter.



Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS4


Description



_ _ _ __


Basis Cell.

Type Counter.



UPLINK_PDTCH_BLOCKING_RATE Chapter 18: Network health reports

UPLINK_PDTCH_BLOCKING_RATE

Description

The UPLINK_PDTCH_BLOCKING_RATE statistic provides the success rate of channel requests in GPRS.

Formula

–

Usage Service accessibility.Quality of Service Monitoring.Network planning.

Basis Cell.

Type Percentage.

Raw Statistics CHANNEL_REQS_REJECT.CHANNEL_REQS_REC.


Maintenance Information: GSM Statistics Application UPLINK_TRAFFIC_VOLUME

UPLINK_TRAFFIC_VOLUME


Description

The UPLINK_TRAFFIC_VOLUME statistic provides a measure of the volume of uplinkRadio Link Control traffic including retransmitted blocks.

Formula

_ _

_ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ __ _ _ __ _ _ _

_ _ _ _



UPLINK_TRAFFIC_VOLUME Chapter 18: Network health reports


Basis Cell.

Type Percentage.

Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS1].AIR_UL_DATA_BLKS[QOS2_CS1].AIR_UL_DATA_BLKS[QOS3_CS1].AIR_UL_DATA_BLKS[QOS1_CS2].AIR_UL_DATA_BLKS[QOS2_CS2].AIR_UL_DATA_BLKS[QOS3_CS2].AIR_UL_DATA_BLKS[QOS1_CS3].AIR_UL_DATA_BLKS[QOS2_CS3].AIR_UL_DATA_BLKS[QOS3_CS3].AIR_UL_DATA_BLKS[QOS1_CS4].AIR_UL_DATA_BLKS[QOS2_CS4].AIR_UL_DATA_BLKS[QOS3_CS4].


Chapter

19Ladder diagrams

Ladder diagrams show the relationships between MS, BSS, and MSC when a message flows betweenthese network elements. The following topics are described in this chapter:

• "Ladder diagram constructs" on page 19-2

• "Phone call model" on page 19-3

• "Call procedure milestones" on page 19-5

• "Call setup and handover" on page 19-6

• "Connection establishment" on page 19-9

• "Assignment to TCH" on page 19-14

• "Intra-cell handover" on page 19-17

• "Inter-BSS handover" on page 19-20

• "Intra-BSS handover" on page 19-26

• "Call clearing" on page 19-31

• "Short message service" on page 19-35

• "Congestion relief" on page 19-37

• "Directed retry" on page 19-39

• "Flow control" on page 19-41

• "Intra-BSS interband activity " on page 19-42

• "Inter-BSS interband activity " on page 19-46

• "Interband assignment" on page 19-50

• "Band Reassignment" on page 19-51

• "RSL link scenarios" on page 19-53

• "MTL link scenarios " on page 19-55

• "GBL statistics" on page 19-60

• "Accessibility statistics" on page 19-64

• "Throughput statistics" on page 19-69


Ladder diagram constructs Chapter 19: Ladder diagrams

Ladder diagram constructs

Ladder diagrams are used to:

• Show the relationships between the MS, BSS, and MSC elements represented as vertical lines.

• Provide a visual aid in tracing the statistical processes involved when an event occurs.

The message flows between the network elements are presented as horizontal lines representinga sequential flow of events. Arrows indicate the direction of the message flow. Messagenames are placed above the directional line.

Intermediate network element functions are placed on the vertical lines as a sequential reference. Parallelfunctions may also be included as separate vertical lines for additional reference.

Statistics associated with individual messages are located immediately below the directional line. All ofthe statistics that may be generated as the result of the process flow is listed on the diagram.

As an example, Figure 19-1 shows the relationships associated with an immediate assignment failure.

Figure 19-1 Diagram of immediate assignment failure

MS BSS



MSC

TIMEOUT

CHAN_REQ_MS_FAIL

OK_ACC_PROC_RACH (SEE NOTE)



Maintenance Information: GSM Statistics Application Phone call model

Phone call model

The GSM phone call model comprises:

• BSS functions

• BSC functions

• MSC functions

• Handover procedure

BSS functions

The GSM BSS is a combination of digital and RF equipment, the purpose of which is to providethe radio Air interface linking subscribers into the network and providing them with service. TheBSS function is to communicate with the Mobile Switching Centre (MSC), the Operations andMaintenance Centre - Radio (OMC-R), and the Mobile Subscribers (MSs).

BSC functions

The main functions of the BSC include managing the radio channels and transferring control messagesto and from the MS. Control channels and bearer channels are always under the control of theBSC. However, many types of call handling messages do not directly affect the BSC and for thesethe BSC serves simply as a relay point between the MSC and the MS.

The BSC also incorporates a digital switching matrix. No fixed correspondence exists between the radiochannels at the BSS and the terrestrial circuits, which connect the BSS to the MSC. While the BSC selectsthe radio channel, the terrestrial circuit is selected by the MSC, and it is the BSCs switching matrix thatis used to connect the two together. The switching matrix also allows the BSC to perform handoversbetween the BTSs under its control without involving the MSC (intra-BSS and intra-cell).

MSC functions

The MSC handles the call set up procedures and controls the location registration and handoverprocedures for all except intra-BSS and intra-cell handovers. MSC controlled intra-BSS handoverscan be set as an option at the switch. Location registration (and location update) allows MSs to reportchanges in their locations enabling automatic completion of MS-terminated calls.


Phone call model Chapter 19: Ladder diagrams

Handover procedure

The handover procedure preserves call connections as MSs move from one radio coverage area toanother during an established call. Handovers within cells controlled by a single BSC are handledby that BSC (intra-BSS and intra-cell). When handovers are between cells controlled by differentBSCs, the primary control is at the MSC (inter-BSS). Handovers can also be performed between BSSsconnected to two different MSCs (inter-MSC handover). In this case, GSM specifications definestandard procedures allowing the two MSCs to coordinate the handover.

Figure 19-2 Handover procedure

OMC-R

BSC

MSC BSC

BSS

BTS

BTS BTS

INTER-BSS

INTRA-BSS

BTS

BTS

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

TDMA FRAMES

INTRA-CELL

NOTE: Intra-cell handovers are performed primarily due to poor quality and not to poor level.


Maintenance Information: GSM Statistics Application Call procedure milestones

Call procedure milestones

A general description of the milestones in a call procedureis explained in the following paragraphs.

Call procedure

BidsThe first call procedure milestone is a request for service or resource (channel assignment request). At thispoint the MS will check the possibility of making a call, before attempting to make a call.

Bids - bids blockedA bid is made for a resource (channel assignment request) but, if all channels are busy, due to other subscribersmaking phone calls, the bid is blocked. Further bids are requested until a no blocking situation exists.

Bids - attemptsA bid is made and accepted to use a resource (channel assignment request). Now an attempt is made to assignthe user to that resource, for example with a traffic channel assignment there is an assignment request from theMSC, but at this time the assignment to the TCH is not complete. Hence, the connection is not complete.

Bids - attempts - successesAn attempt has been made to assign a resource (channel assignment request) and the assignmentis successful, hence the connection is complete.

Bids - attempt - failures (dropped)An attempt is made to assign a resource (channel assignment request) but the assignment fails.It is not possible to recover the call and the call is lost.

Bids - attempt - fail - recoveredA resource is allocated to a MS which it found to be unusable. The call in progress was notlost but was able to revert to its previous radio resource.


Call setup and handover Chapter 19: Ladder diagrams

Call setup and handover

Statistics describe the behaviour of the major call processing scenarios.

Statistics matrix

The call setup and handover statistics are shown as a matrix against call processing scenariosin Table 19-1. Each call processing scenario is broken out into six call procedure milestonesshown in the vertical columns of the matrix.

Table 19-1 Call setup and handover statistics matrix.

MilestonesProcedure

Bids Blocked Attempts Success Failed lost Failedrecovered

ImmediateAssignment

OK_ACC_PROC_RACHand AL-LOC_SD-CCH seenote 1

CHAN_REQ_MS_BLKand AL-LOC_SD-CCH_FAIL seenote 2

see note 3 OK_ACC_PROC

CHAN_REQ_MS_FAIL orINV_EST_CAUSE_IN_RACHsee note 5

N/A

ConnectionEstablish-ment

- - CONN_REQ_TO_MSC

- CONN_RE-FUSED

N/A

Assignmentto TCH atcall set-up

MA_REQ_FROM_MSC

MA_CMD_TO_MS_BLKDALLOC_TCH_FAIL

MA_CMD_TO_MSC

TO-TAL_CALLSandMA_COM-PLETE_TO_MSCALLOC_TCH

For furtherstudy

MA_FAIL_FROM_MS

HandoverIntra-cell

IN-TRA_CELL_HO_REQ

AL-LOC_SD-CCH_FAIL orHO_FAIL_NO_ RE-SOURCES(IN-TER_BSS)or AL-LOC_TCH_FAIL

IN-TRA_CELL_HO_ATMPTandMA_CMD_TO_MS

IN-TRA_CELL_HO

IN-TRA_CELL_HO_LOSTMS

IN-TRA_CELL_HO_FAILandMA_FAIL_FROM_MS


Maintenance Information: GSM Statistics Application Call setup and handover

Table 19-1 Call setup and handover statistics matrix. (Continued)

MilestonesProcedure

Bids Blocked Attempts Success Failed lost Failedrecovered

HandoverIntra-BSS(outgoing)

OUT_IN-TRA_BSS_HO_REQ

OUT_IN-TRA_HO_PRI_BLKorHO_FAIL_NO_ RE-SOURCES(IN-TRA_BSS)

OUT_IN-TRA_BSS_HO_ATMPTandOUT_HO_CAUSE_ATMPT andOUT_HO_NC_CAUSE_ATMPT

OUT_IN-TRA_BSS_HOandOUT_HO_NC_SUC

OUT_IN-TRA_BSS_HO_LOSTMS

OUT_IN-TRA_BSS_HO_FAIL

HandoverInter-BSS(outgoing)

OUT_IN-TER_BSS_REQ _TO_MSC

HO_FAIL_NO_ RE-SOURCES(IN-TER_BSS)

OUT_IN-TER_BSS_HO_ATMPTandOUT_HO_CAUSE_ATMPT andOUT_HO_NC_CAUSE_ATMPT

OUT_IN-TER_BSS_HO_SUC

OUT_IN-TER_BSS_HO_LOSTMS

OUT_IN-TER_BSS_HO_RETURN

HandoverIntra-BSS(incoming)

For furtherstudy

For furtherstudy AL-LOC_SD-CCH_FAIL or AL-LOC_TCH_FAIL

IN_INTRA_BSS_NC_ATMPTor AL-LOC_SD-CCH or AL-LOC_TCH

IN_INTRA_BSS_HO_SUCand IN_IN-TRA_BSS_NC_SUC

IN_INTRA_BSS_HO_LOSTMS

IN_INTRA_BSS_HO_RETURN

HandoverInter-BSS(incoming)

For furtherstudy

For furtherstudy seenote 4 AL-LOC_SD-CCH_FAIL or AL-LOC_TCH_FAIL

{4322}HO_REQ_ACK_TO_MSCAL-LOC_SD-CCHor AL-LOC_TCH

IN_INTER_BSS_HO

IN_INTER_BSS_HO[IN_IN-TER_BSS_MS_NO_SEIZE]

IN_INTER_BSS_HO[IN_IN-TER_BSS_MS_NO_SEIZE]


Call setup and handover Chapter 19: Ladder diagrams

NotesThe following notes refer to the call setup and handover matrix:

1. OK_ACC_PROC_SUC_RACH may be, but is not necessarily equal to ALLOC_SDCCHbecause they are pegged by different processes and filtering takes place between thetwo pegs. ALLOC_SDCCH is pegged at the target cell for SDCCH Handovers.If OK_ACC_PROC_SUC_RACH is less than ALLOC_SDCCH, some of theALLOC_SDCCH pegs are due to SDCCH Handovers into the cell. And ifALLOC_SDCCH is less than OK_ACC_PROC_SUC_RACH, some of theRACHs have been filtered between the two pegs.

2. CHAN_REQ_MS_BLK may be, but is not necessarily equal to ALLOC_SDCCH_FAIL.ALLOC_SDCCH_FAIL is pegged for Immediate Assignment and also for SDCCHHandovers. CHAN_REQ_MS_BLK is only pegged for Immediate Assignment.CHAN_REQ_MS_BLK and ALLOC_SDCCH_FAIL only peg on SDCCH blocking.

3. The total failed dropped calls is given by:(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_LOST_MS])

4. The statistic HO_REQ_MSC_FAIL covers all cases except for blocking(no resources available).

5. A phantom RACH or badly formed (invalid) channel request was detected, so noresource was allocated and the call set-up procedure ended.


Maintenance Information: GSM Statistics Application Connection establishment


Figure 19-3 to Figure 19-7 show the ladder diagrams for the connection establishment procedures.Figure 19-3 shows that connection establishment is successful after immediate assignment is successful,while Figure 19-7 shows successful mobile-terminated connection establishment.


Connection establishment Chapter 19: Ladder diagrams

Successful mobile originated

Figure 19-3 shows a successful mobile generated connection establishment.

Figure 19-3 Connection establishment successful

MS BSSCHANNEL REQUEST (RACH)


SABM + INITIAL LAYER 3 MESSAGE (SDCCH)

MSC

OK_ACC_PROC[CM SERV. REQ. - CALL] - or -OK_ACC_PROC[CM REESTABLISHMENT] - or -OK_ACC_PROC[PAGE RESPONSE] - or -OK_ACC_PROC[LOCATION UPDATE] - or -OK_ACC_PROC[IMSI DETACH]

{

OK_ACC_PROC_SUC_RACH (SEE NOTE)

ALLOC_SDCCH


CONN_REQ_TO_MSC

CONNECTION REQUEST

< CR + COMPLETE LAYER 3 MSG.>

CONNECTION CONFIRM

IMMEDIATE ASSIGNMENT

CONNECTION ESTABLISHMENT

CHAN_REQ_CAUSE_ATMPT(for one of the causes)

ACCESS_PER_RACH

ACCESS_PER_AGCH

MS_ACCESS_BY_TYPE

MOBILE ORIGINATED



Failure

Figure 19-4 shows a connection establishment failure.

Figure 19-4 Connection establishment failure

MS BSSCHANNEL REQUEST (RACH)


SABM + INITIAL LAYER 3 MESSAGE (SDCCH)

MSC

OK_ACC_PROC[CM SERV. REQ. - CALL] - or -OK_ACC_PROC[CM REESTABLISHMENT] - or -OK_ACC_PROC[PAGE RESPONSE] - or -OK_ACC_PROC[LOCATION UPDATE] - or -OK_ACC_PROC[IMSI DETACH]

{


ALLOC_SDCCH


CONN_REQ_TO_MSC

CONNECTION REQUEST




ACCESS_PER_RACH

ACCESS_PER_AGCH

MS_ACCESS_BY_TYPE

CONN_REFUSED

< CREF>

CONNECTION NOT ESTABLISHED


Connection establishment Chapter 19: Ladder diagrams

Immediate assignment blocked

Figure 19-5 shows an immediate assignment blocked.

Figure 19-5 Immediate assignment blocked

MS BSS

IMMEDIATE ASSIGNMENT REJECT (AGCH)

MSC

{NOTE: RSS Abis does additional filtering of RACH.

ALLOC_SDCCH_FAIL andCHAN_REQ_MS_BLK




ACCESS_PER_RACH

ACCESS_PER_AGCH

MS_ACCESS_BY_TYPE

Immediate assignment failure

Figure 19-6 shows an immediate assignment failure.

Figure 19-6 Immediate assignment failure

MS BSS


MSC

TIMEOUT

CHAN_REQ_MS_FAIL




ALLOC_SDCCH


ACCESS_PER_RACH

ACCESS_PER_AGCH

MS_ACCESS_BY_TYPE



Successful mobile terminated call

Figure 19-7 shows a successful connection establishment (mobile terminated call).

Figure 19-7 Connection establishment (mobile terminated call) successful

MS BSS

PAGING REQUEST


MSC

ACCESS_PER_RACH


CONNECTION REQUEST



CONN_REQ_TO_MSC

CONNECTION CONFIRM

< CC>

ACCESS_PER_PCH

PAGE_REQ_FROM_MSC

CHAN_REQ_CAUSE_ATMPT (PAGING RESPONSE)


CONNECTION ESTABLISHMENT

PAGING

MS_ACCESS_BY_TYPE

ALLOC_SDCCH

ACCESS_PER_AGCH

ACCESS_PER_AGCH


(MOBILE TERMINATED)

SABMT INITIAL LAYER 3 MESSAGE (SDCCH)

OK_ACC_PROC (PAGING_RESPONSE)


Assignment to TCH Chapter 19: Ladder diagrams

Assignment to TCH

Figure 19-8 to Figure 19-11 show the ladder diagrams for the assignment to TCH procedures.

Assignment successful

Figure 19-8 shows a successful TCH assignment.

Figure 19-8 TCH assignment successful

MS BSS MSC

MA_CMD_TO_MS

TOTAL_CALLS (SEE NOTE 1)

ASSIGNMENT COMPLETE

ASSIGNMENT REQUEST

ASSIGNMENT COMMAND (SDCCH)

ASSIGNMENT COMPLETE (TCH)

MA_REQ_FROM_MSC

MA_COMPLETE_TO_MSC

ALLOC_TCH

MS_TCH_USAGE_BY_TYPE

NOTES:

1. Pegged for the first successful TCH assignment.

2. Pegged to start the length of time spent on TCH by various typesof MS. Will not be pegged after the TCH is deallocated.

MA_COMPLETE_FROM_MS

(SEE NOTE 2)


Maintenance Information: GSM Statistics Application Assignment to TCH

Immediate assignment failure

Figure 19-9 shows an immediate assignment failure.

Figure 19-9 Immediate assignment failure

MS BSS MSC

OK_ACC_PROC_SUC_RACH (SEE NOTE 1)

INV_EST_CAUSE_ON_RACH(SEE NOTE 2)

NOTES:

1. RSS Abis does additional filtering of RACH.

2. RSS Abis filtering detects and invalid channel request on RACH.



TCH assignment blocked

Figure 19-10 shows a TCH assignment blocked.

Figure 19-10 TCH assignment blocked

MS BSS MSC

MA_REQ_FROM_MSC

MA_CMD_TO_MS_BLKD

ASSIGNMENT FAILURE

ASSIGNMENT REQUEST

NOTE: NO RADIO TCH AVAILABLE

ALLOC_TCH_FAIL


Assignment to TCH Chapter 19: Ladder diagrams

Fail recovered

Figure 19-11 shows a TCH assignment fail-recovered to a SDCCH.

Figure 19-11 TCH assignment fail-recovered to SDCCH

MS BSS

ASSIGNMENT COMMAND (SDCCH)

MSC

MA_FAIL_FROM_MS

ASSIGNMENT REQUEST

ASSIGNMENT FAILURE

ASSIGNMENT FAILURE (SDCCH)

MA_CMD_TO_MS

MA_REQ_FROM_MSC

ALLOC_TCH

NOTE: Failure to access Traffic Channel.


Maintenance Information: GSM Statistics Application Intra-cell handover

Intra-cell handover

Figure 19-12 to Figure 19-15 show the ladder diagrams for the intra-cell handover procedure. Intra-cellhandovers deal with channels within the same cell; that is, the Target Cell = Source Cell.

Handover successful

Figure 19-12 shows a successful intra-cell handover.

Figure 19-12 Handover (intra-cell) successful

MS(SOURCE CHANNEL) BSS

ASSIGNMENT COMMAND

NOTE: Need for handover is recognized within the BSS.


ASSIGNMENT COMPLETE

INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)

MA_CMD_TO_MS

MS(TARGET CHANNEL)

ALLOC_TCH or ALLOC_SDCCH

INTRA_CELL_HO (INTRA_CELL_HO_REQ)(SEE NOTE)

INTRA_CELL_HO (INTRA_CELL_HO_SUC)

MSC

HANDOVER

PERFORMED


Intra-cell handover Chapter 19: Ladder diagrams

Handover blocked

Figure 19-13 shows an intra-cell handover blocked.

Figure 19-13 Handover (intra-cell) blocked

MS(SOURCE CHANNEL)

MS(TARGET CHANNEL)

BSS

INTER_CELL_HO (INTRA_CELL_HO_REQ)(SEE NOTE)

HO_FAIL_NO_RESOURCES(INTRA_CELL_HO)

ALLOC_TCH_FAIL

NOTE: Need for handover is recognized within the BSS.

Fail recovered

Figure 19-14 shows an intra-cell handover fail-recovered to a source channel.

Figure 19-14 Handover (intra-cell) fail-recovered to source channel

BSS

ASSIGNMENT FAILURE (SEE NOTE 2)


NOTES:1. Need for handover is recognized within the BSS.2. Failure to access target channel.

INTRA_FAIL_FROM_MS

ASSIGNMENT COMMAND

MS(SOURCE CHANNEL)

MS(TARGET CHANNEL)

INTRA_CELL_HO (INTRA_CELL_HO_FAIL)

MA_CMD_TO_MS

INTRA_CELL_HO (INTRA_CELL_HO_REQ)(SEE NOTE 1)

ALLOC_TCH


Maintenance Information: GSM Statistics Application Intra-cell handover

Fail lost

Figure 19-15 shows an intra-cell handover fail-lost.

Figure 19-15 Handover (intra-cell) fail-lost

BSS


NOTES: 1. Need for handover is recognized within the BSS.2. Failure to access target channel and no message receive on source channel prior to timer expiry.

CLR_REQ_TO_MSC

ASSIGNMENT COMMAND

MS(SOURCE CHANNEL)

MS(TARGET CHANNEL)

MA_CMD_TO_MS

INTRA_CELL_HO (INTRA_CELL_HO_REQ)(SEE NOTE 1)

INTRA_CELL_HO (INTRA_CELL_HO_LOSTMS) (SEE NOTE 2)CLEAR

REQUEST

MSCTIMEOUT

ALLOC_TCH


Inter-BSS handover Chapter 19: Ladder diagrams

Inter-BSS handover

Figure 19-16 to Figure 19-19 show the ladder diagrams for the inter-BSS handover procedure.

Handover successful

Figure 19-16 shows a successful inter-BSS handover.

Figure 19-16 Handover (inter-BSS) successful

MSC BSS (SOURCE)

MS (TARGET CHANNEL TARGET CELL)

HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT

MS (SOURCE CHANNEL SOURCE CELL)

BSS(TARGET)

HANDOVER REQUIRED (SEE NOTE 1)

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains a bad handover reference number.

HANDOVER COMMAND

HANDOVER REQUEST

HANDOVER COMPLETE

HANDOVER COMPLETECLEAR

COMMAND

OUT_INTER_BSS_HO(OUT_INTER_BSSHO_SUC)

HANDOVER REQUESTACKNOWLEDGE

INTER_BSS_HO(OUT_INTER_BSS_REQ_TO_MSC)

HO_REQ_ACK_TO_MSC(SEE NOTE 2)



OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_ATMPT)

IN_INTER_BSS_HO(IN_INTER_BSS_HO_SUC)

OUT_HO_NC_SUC

{4322}

Handover blocked

Figure 19-17 shows an inter-BSS handover blocked.


Maintenance Information: GSM Statistics Application Inter-BSS handover

Figure 19-17 Handover (inter-BSS) blocked

MS(SOURCE CHANNELSOURCE CELL) BSS

(SOURCE)


HO_REQ_MSC_FAIL(SEE NOTE 3)

MSC BSS(TARGET)


NOTES:1. Need for handover is recognized within the BSS.2. If a need for handover continues to exist after timer expiry.3. This pegs due to causes other than resource unavailable.4. Reference GSM 8.08 Section 3.2.2.5 for valid "handover failure" causes.

HANDOVER REQUEST

HANDOVER FAILURE(SEE NOTE 4)


OUT_INTER_BSS_HO(OUT_INTER_BSS_REQ_TO_MSC)


ALLOC_TCH_FAIL

HO_FAIL_NO_RESOURCES (INTER_BSS_HO)



Fail recovered

Figure 19-18 shows an inter-BSS handover fail-recovered.

Figure 19-18 Handover (inter-BSS) fail-recovered

MS(SOURCE CHANNELSOURCE CELL)

BSS(SOURCE)

MS (TARGETCHANNELTARGET CELL)

HANDOVER COMMAND OUT_INTER_BSS_HO

(OUT_INTER_BSS_HO_ATMPT)

MSC BSS(TARGET)

HANDOVER REQUIRED(SEE NOTE 1)

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected which contains a bad handover reference number.

HANDOVER COMMAND

HANDOVER REQUEST


HANDOVER FAILURE



HANDOVERFAILURE

HO_REQ_MSC_FAIL


OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_RETURN)

OUT_HO_CAUSE_ATMPT


{4322})



Fail lost

Figure 19-19 shows an inter-BSS handover fail-lost.

Figure 19-19 Handover (inter-BSS) fail-lost


BSS(SOURCE)


MSC

BSS(TARGET)

HANDOVERRECOGNIZED

HANDOVERCOMMAND

HANDOVERREQUIRED HANDOVER

REQUEST

HANDOVERREQUEST ACKNOWLEDGEHANDOVER

COMMAND

(SEE NOTE)

OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_LOSTMS)

NOTE: After the handover command is sent to the MS, any of the following messages may be received at the source BSS: SCCP_RELEASED, RELEASED_DONE, MTG_EXP, RADIO_CHAN_RLSD.



Fail lost (mobile)

Figure 19-20 shows an inter-BSS handover failure with lost mobile.

Figure 19-20 Inter-BSS handover failure with lost mobile


BSS(SOURCE)

MS (TARGET CHANNEL TARGET CELL)MSC

BSS(TARGET)

HANDOVERCOMMAND

HANDOVER REQUIRED

HANDOVERREQUEST

HANDOVERREQUEST ACKNOWLEDGE

HANDOVERCOMMAND

(SEE NOTE 1)


OUT_INTER_BSS_HO (OUT_INTER_BSS_REQ_TO_MSC

OUT_HO_CAUSE_ATMPT



HO_REQ_ACK_TO_MSC

(SEE NOTE 2)

TIMEOUT(SEE NOTE 3)

OUT_HO_INTER_BSS_HO (OUT_INTER_BSS_LOSTMS)

CLEAR REQUEST

CLEARCOMMAND

CLR_REQ_TO_MSC

CLEARCOMPLETE

IN_INTER_BSS_HO (IN_INTER_BSS_MS_NO_SEIZE)

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains a bad handover reference number.3. TIMEOUT can occur at source BSS, target BSS, or switch first depending on system timer settings.

{4322}



Standard directed retry (external)

Figure 19-21 shows an inter-BSS handover directed retry external.

Figure 19-21 Inter-BSS handover directed retry external


BSS(SOURCE)

MS (TARGET CHANNEL TARGET CELL)MSC BSS

(TARGET)

HANDOVERCOMMAND

ASSIGNMENTREQUEST

HANDOVERREQUEST

CLEAR COMMAND


OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_SUC)

OUT_HO_NC_SUC


MA_REQ_FROM_MSC

CALLS_QUEUED

TCH_Q_LENGTH

HANDOVERCOMMAND


HANDOVERCOMPLETE

ALLOC_TCHor ALLOC_SDCCH


IN_INTER_BSS_HO(SUCCESSFUL)HANDOVER

COMPLETE

OUT_INTER_BSS_HO (OUT_INTER_BSS_HO_ATMPT)

OUT_HO_CAUSE_ATMPT (CONGESTION)


ASSIGNMENT FAILURE CAUSE DIRECTED RETRY(SEE NOTE 2)

QUEUEING INDICATION(SEE NOTE 1)

OUT_HO_NC_CAUSE_ATMPT (CONGESTION)

NOTES:1. Only if queueing is enabled for the cell2. The necessity in sending this message must align with MSC expectation and is controlled through the database. Message may be sent after handover required message as controlled by the database.3. The cause field in this message (either directed retry or handover cause) must align with MSC expectation and is controlled through the database.

{4322}


Intra-BSS handover Chapter 19: Ladder diagrams

Intra-BSS handover

Figure 19-22 to Figure 19-25 show the ladder diagrams for the intra-BSS handover procedure.

Handover successful

Figure 19-22 shows a successful intra-BSS handover.

Figure 19-22 Handover (intra-BSS) successful


BSS

MS (TARGET CHANNELTARGET CELL)

HANDOVERCOMMAND

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains a bad handover reference number. 3. Handover performed message sent to MSC by source cell.

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC) (SOURCE CELL)

IN_INTRA_BSS_HO (TARGET CELL) (SEE NOTE 3)

HANDOVER COMPLETE

OUT_HO_CAUSE_ATMPT (SOURCE CELL)


OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT) (SOURCE CELL)

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_REQ) (SOURCE CELL) (SEE NOTE 1)

OUT_HO_NC_CAUSE_ATMPT (SOURCE CELL) (SEE NOTE 2)


IN_INTRA_BSS_NC_ATMPT (TARGET CELL)

OUT_HO_NC_SUC (SOURCE CELL)

(IN_INTRA_BSS_NC_SUC) (TARGET CELL)

Handover- blocked

Figure 19-23 shows an intra-BSS handover-blocked.


Maintenance Information: GSM Statistics Application Intra-BSS handover

Figure 19-23 Handover (intra-BSS) blocked

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_REQ) (SEE NOTE 1)

BSSMS (TARGET CHANNELTARGET CELL)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_PRI_BLK) (SEE NOTE 2)


NOTES:1. Need for handover is recognized within the BSS, but no radio channel is available in primary target cell.2. Handover target cell list should contain at least two cells in order to peg this statistic. if there is only 1 cell, the statistic will not be pegged.

ALLOC_TCH_FAIL or ALLOC_SDCCH_FAIL

HO_FAIL_NO_RESOURCES (INTRA_BSS_HO)



Fail-recovered

Figure 19-24 shows an intra-BSS handover fail-recovered.

Figure 19-24 Handover (intra-BSS) fail-recovered

OUT_INTRA_BSS_HO

BSS

HANDOVER FAILURE


OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_RETURN) (SEE NOTE 3)


HANDOVER COMMAND

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains a bad handover reference number.3. Failure to access channel in target cell.

(SEE NOTE 2)



OUT_HO_CAUSE_ATMPT

(SEE NOTE 1)

IN_INTRA_BSS_NC_ATMPT

(OUT_INTRA_BSS_HO_REQ)


Maintenance Information: GSM Statistics Application Intra-BSS handover

Fail-lost

Figure 19-25 shows an intra-BSS handover fail-lost.

Figure 19-25 Handover (intra-BSS) fail-lost

BSS

OUT_INTRA_BSS_HO_ATMPT

CLR_REQ_TO_MSC



HANDOVER COMMAND

NOTES:1. Need for handover is recognized within the BSS.2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains a bad handover reference number.3. Failure to access channel in target cell and no message received on channel in source cell prior to timer expiry.

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_REQ) (SEE NOTE 1)

(SEE NOTE 2)

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_LOSTMS)

CLEARREQUEST

MSC TIMEOUT

(SEE NOTE 3)

IN_INTRA_BSS_NC_ATMPTOUT_INTRA_BSS_NC_ATMPT

ALLOC_SDCCH or ALLOC_TCH



Standard directed retry (internal)

Figure 19-26 displays the ladder diagram for intra-BSS handover standard directed retry.

Figure 19-26 Intra-BSS handover standard directed retry

MSC BSSASSIGNMENT REQUEST

QUEUEING INDICATION (SEE NOTE 1)

MS

CALLS_QUEUED

MA_REQ_FROM_MSC

TCH_Q_LENGTH

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_ATMPT)


HANDOVER COMMAND

INTRA_BSS_HO_CAUSE_SUC (CONGESTION)

IN_INTRA_BSS_HO(IN_INTRA_BSS_HO_SUC)


OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_SUC)

ASSIGNMENT COMPLETE

NOTES:1. Only if queuing is enabled for the cell.2. The necessity in sending this message must align with MSC expectation and is controlled through the database. Message may be sent after handover required message as controlled by the database.

3. The cause field in this message (either directed retry or handover cause) must align with MSC expectation and is controlled through the database.

MA_COMPLETE_TO_MSC



ASSIGNMENT FAILURE CAUSE DIRECTED RETRY (SEE NOTE 2)


HANDOVER COMMAND


Maintenance Information: GSM Statistics Application Call clearing

Call clearing

Figure 19-27 to Figure 19-30 show the ladder diagrams for the call clearing procedures.

Cipher mode fail

Figure 19-27 shows BSS initiated call clearing - cipher mode fail.

Figure 19-27 BSS initiated call clearing-cipher mode fail

MS BSS MSC

CLR_REQ_TO_MSC

CLEAR REQUEST

CIPHERING MODE COMMAND

CIPHER_MODE_FAIL

TIMEOUT


Call clearing Chapter 19: Ladder diagrams

RF loss on an SDCCH

Figure 19-28 shows BSS initiated call clearing (RF loss on an SDCCH).

Figure 19-28 BSS initiated call clearing (RF loss on an SDCCH)

MS BSS MSC

CLR_REQ_TO_MSC

CLEAR REQUEST

RF_LOSSES_SD

MEASUREMENT REPORT (SACCH)



TIMEOUT

(SEE NOTES 1 AND 2)

NOTES:1. MS has established on SDCCH, for example, after immediate assignment successful.2. Message sent on SACCH every 480 milliseconds.


Maintenance Information: GSM Statistics Application Call clearing

RF loss on a TCH

Figure 19-29 shows BSS initiated call clearing - RF loss on a TCH.

Figure 19-29 BSS initiated call clearing (RF loss on a TCH)

MS BSS MSC

CLR_REQ_TO_MSC

CLEAR REQUEST

RF_LOSSES_TCH




TIMEOUT

(SEE NOTES 1 AND 2)

NOTES:1. MS has established on TCH, for example, after assignment successful.2. Message sent on SACCH every 480 milliseconds.

Queueing timeout

Figure 19-30 shows BSS initiated call clearing (queueing timeout).


Call clearing Chapter 19: Ladder diagrams

Figure 19-30 BSS initiated call clearing (queueing timeout)

MS BSS MSC

CLR_REQ_TO_MSC

CLEAR REQUEST

CALLS QUEUED

NOTE: TCH assignment attempted, no resources available, and queueing enabled.

QUEUEING INDICATION (SEE NOTE)

TIMEOUT


Maintenance Information: GSM Statistics Application Short message service

Short message service

Figure 19-31 and Figure 19-32 show the ladder diagrams for the short message service procedures.

Mobile originated

Figure 19-31 shows MS originated short message service (point-to-point).

Figure 19-31 MS originated short message service (point-to-point)

MSC BSS MS

SMS MESSAGE

SMS_INIT_ON_SDCCH

ACKNOWLEDGEMENT

SAPI 3 REQUEST

orSMS_INIT_ON_TCH

NOTES:1. A SAPI 0 mode must exist before the SAPI 3 can be established.2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCHand SMS_INIT_ON_TCH is pegged if the MS is on a TCH.

SMS MESSAGE


Short message service Chapter 19: Ladder diagrams

Mobile terminated

Figure 19-32 shows mobile terminated short message service (point-to-point).

Figure 19-32 MS terminated short message service (point-to-point)

MSC BSS MS

SMS MESSAGE

SMS_INIT_ON_SDCCH

ACKNOWLEDGEMENT

SAPI 3 REQUEST

orSMS_INIT_ON_TCH

NOTES:1. A SAPI 0 mode must exist before the SAPI 3 can be established.2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCHand SMS_INIT_ON_TCH is pegged if the MS is on a TCH.

SMS MESSAGE


Maintenance Information: GSM Statistics Application Congestion relief

Congestion relief

Intra-BSS congestion relief example

Figure 19-33 shows the an example of the relationships associated with an intra-BSS congestionrelief handover procedure. In this example, an MS attempts to access a TCH in the cell which iscongested and one (or possibly multiple) MS is handed out to free a TCH.


Congestion relief Chapter 19: Ladder diagrams

Figure 19-33 Intra-BSS congestion relief handover procedure


QUEUEING INDICATION (SEE NOTE)

MS

CALLS_QUEUED

MA_REQ_FROM_MSC

TCH_Q_LENGTH



HANDOVER COMMAND




ASSIGNMENT COMPLETE

NOTE: Only if queueing is enabled for the cell.

CONGEST_EXIST_HO_ATMPT (SEE NOTE)

MA_COMPLETE_TO_MSC


ALLOC_TCH_FAIL

ALLOC_TCH

HANDOVER COMPLETE

MA_CMD_TO_MS

ASSIGNMENT COMMAND

ASSIGNMENT COMPLETE

TOTAL_CALLS

ALLOC_TCH

TCH_Q_REMOVED(assignment_resource_req)

MA_COMPLETE_FROM_MS


Maintenance Information: GSM Statistics Application Directed retry

Directed retry

Intra-BSS directed retry. example

Figure 19-34 shows an example of the relationships associated with an intra-BSS directed retry procedure.


Directed retry Chapter 19: Ladder diagrams

Figure 19-34 Intra-BSS directed retry procedure


QUEUING INDICATION (SEE NOTE 1)

MS

CALLS_QUEUED

MA_REQ_FROM_MSC

TCH_Q_LENGTH

OUT_INTRA_BSS_HO

(OUT_INTRA_BSS_HO_ATMPT)

OUT_HO_CAUSE_ATMPT

HANDOVER COMMAND




ASSIGNMENT COMPLETE (SEE NOTE 2)

NOTES:

1. Only if queuing is enabled for the cell

2. The database element msc_preference indicates that directed retry proceduresare limited to within the BSS. The BSS sends a Handover Performed message, whichindicates the new cell ID.


MA_COMPLETE_TO-MSC

ASSIGNMENT_REDIRECTION(DIRECTED RETRY)

HANDOVER COMPLETE

ALLOC_TCH

ALLOC_TCH_FAIL

TCH_Q_REMOVED(assignment_resource_req)

CONGEST_STAND_HO_ATMPT (SEE NOTE1)


Maintenance Information: GSM Statistics Application Flow control

Flow control

FLOW_CONTROL_BARRED measures the duration for which access classes are barred as a result offlow control. The statistic duration will be started when any of the access classes are barred due to flowcontrol and stopped when the last access class which was barred due to flow control is unbarred.

Example

Figure 19-35 shows an example of the relationships associated with an access procedure.

Figure 19-35 Access procedure

BSS

START OF ACCESS CLASSBARRING DUE TO FLOW CONTROL.

DURATION

FLOW_CONTROL_BARRED

LAST ACCESS CLASS UNBARRED FROM FLOW CONTROL ACTIONS.


Intra-BSS interband activity Chapter 19: Ladder diagrams

Intra-BSS interband activity

Figure 19-36 to Figure 19-38 show intra-BSS interband activity handover ladder diagrams. These diagramsspecifically show the outgoing handover statistics. By only showing outgoing handover statistics, a betterfocus is placed on the pegging aspects of INTERBAND_ACTIVITY. For a complete handover statisticpegging description (outgoing and incoming) refer to the general handover ladder diagrams in this chapter.

Handover successful

Figure 19-36 shows an established call on TCH with a subsequent successful in-tra-BSS handover to a PGSM cell.


Maintenance Information: GSM Statistics Application Intra-BSS interband activity

Figure 19-36 Successful intra-BSS handover


BSS MS (TARGET CHANNELTARGET CELL)

HANDOVERCOMMAND

NOTES:1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability2. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT an OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well (like, powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.

3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, EXCEPT that

INTERBAND_ACTIVITY will peg different bins:for GSM850 target cells, bin gsm_850_ho_atmpt pegsfor DCS1800 target cells, bin, dcs_1800_ho_atmpt pegsfor PCS1900 target cells, bin, pcs_1900_ho_atmpt pegsfor EGSM target cells, bin egsm_ho_atmpt pegs

OUT_HO_CAUSE_ATMPT

ALLOC_TCH (TARGET CELL)

MS_ACCESS_BY_TYPE (TARGET CELL) (SEE NOTE 1)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_REQ)

OUT_HO_NC_CAUSE_ATMPT(BAND_HANDOVER) (SEE NOTE 2)

INTERBAND_ACTIVITY(PGSM_HO_ATMPT) (SEE NOTE 3)


OUT_HO_NC_SUC


HANDOVERCOMPLETE


Intra-BSS interband activity Chapter 19: Ladder diagrams

Handover unsuccessful (fail recovered)

Figure 19-37 shows an established call on TCH with a subsequent handover attempt to a PGSM cell.The handover is unsuccessful with MS fail recovered to source cell (original channel).

Figure 19-37 Unsuccessful interband handover with fail-recovered source cell


BSS


HANDOVERCOMMAND

NOTES:1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well (like, powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY will peg different bins:for GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail pegfor DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail pegfor PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail pegfor EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg

OUT_HO_CAUSE_ATMPT







INTERBAND_ACTIVITY(PGSM_HO_FAIL)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_RETURN)

HANDOVER FAILURE


Maintenance Information: GSM Statistics Application Intra-BSS interband activity

Handover unsuccessful (fail recovered due to invalid frequencysupported)

Figure 19-38 shows an established call on TCH with subsequent intra-BSS handover attemptto PGSM cell. The handover is unsuccessful due to invalid frequency supported with MSfail recovered to source cell (original channel).

Figure 19-38 Unsuccessful interband handover


BSSMS (TARGET CHANNELTARGET CELL)

HANDOVERCOMMAND

OUT_HO_CAUSE_ATMPT



OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_REQ) (SOURCE CELL)


INTERBAND_ACTIVITY(PGSM_HO_ATMPT)


INTERBAND_ACTIVITY(PGSM_HO_FAIL) (SEE NOTE 3)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_RETURN)

INTERBAND_ACTIVITY(INVALID_FREQ_HO)

HANDOVER FAILURE

REASON- FREQUENCY NOT IMPLEMENTED

NOTES:1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY will peg different bins:for GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail pegfor DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail pegfor PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail pegfor EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg


Inter-BSS interband activity Chapter 19: Ladder diagrams

Inter-BSS interband activity

Figure 19-39 to Figure 19-41 show inter-BSS interband activity handover ladder diagrams. These diagramsspecifically show the outgoing handover statistics. By only showing outgoing handover statistics, a betterfocus is placed on the pegging aspects of INTERBAND_ACTIVITY. For a complete handover statisticpegging description (outgoing and incoming) refer to the general handover ladder diagrams in this chapter.

Handover successful

Figure 19-39 shows an established call on TCH with a subsequent successful in-ter-BSS handover to a PGSM cell.


Maintenance Information: GSM Statistics Application Inter-BSS interband activity

Figure 19-39 Successful inter-BSS handover

MSC BSS (SOURCE)

HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT

BSS(TARGET)


HANDOVER COMMAND

HANDOVER REQUEST

HANDOVER COMPLETECLEAR

COMMAND



OUT_INTER_BSS_HO (OUT_INTER_BSS_REQ_TO_MSC)

OUT_HO_NC_CAUSE_ATMPT (BAND HANDOVER) (SEE NOTE 4)


OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_SUC)

OUT_HO_NC_SUC


MS_ACCESS_BY_TYPE(SEE NOTE 2)

ALLOC_TCH


HANDOVER COMPLETE

{4322}


NOTES:1. Need for handover is recognized within the BSS.2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have Classmark Update message from the mobile so that the target BSS can peg the MS access type.3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected which contains a band handover reference number.4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover. Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY will peg different bins: for GSM850 target cells, bin GSM_850_HO_ATMPT pegs for DCS1800 target cells, bin DCS_1800_HO_ATMPT pegs for PCS1900 target cells, bin PCS1900_HO_ATMPT pegs for EGSM target cells, bin EGSM_HO_ATMPT pegs


Inter-BSS interband activity Chapter 19: Ladder diagrams


Figure 19-40 shows an established call on TCH with a subsequent inter-BSS handover attempt to a PGSMcell. The handover is unsuccessful with MS fail recovered to source cell (original channel).

Figure 19-40 Inter-BSS handover unsuccessful with fail-recovered source cell

MSC BSS (SOURCE)


HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT


BSS(TARGET)

HANDOVER

REQUIRED (SEE NOTE 1)

HANDOVER COMMAND

HANDOVER REQUEST



OUT_INTER_BSS_HO (OUT_INTER_BSS_REQ_TO_MSC)

MS_ACCESS_BY_TYPE(SEE NOTE 2)

ALLOC_TCH


OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_ATMPT) HO_REQ_ACK_TO_MSC

(SEE NOTE 3)

OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_RETURN)INTERBAND_ACTIVITY(PGSM_HO_FAIL) (SEE NOTE 5)

HANDOVER FAILURE

HANDOVER FAILURE

HO_REQ_MSC_FAIL

{4322}

NOTES:1. Need for handover is recognized within the BSS.2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have Classmark Update message from the mobile so that the target BSS can peg the MS access type.3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected which contains a band handover reference number.4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover. Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY will peg different bins: for GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg for PCS1900 target cells, bins PCS1900_HO_ATMPT and PCS_1900_HO_FAIL peg for EGSM target cells, bins EGSM_HO_ATMPT and EGSM_HO_FAIL peg


Maintenance Information: GSM Statistics Application Inter-BSS interband activity

Handover unsuccessful fail recovered due to invalid frequencysupported

Figure 19-41 shows an established call on a TCH with subsequent inter-BSS handoverattempt to a PGSM cell. The handover is unsuccessful due to invalid frequency supportedwith MS fail recovered to source cell (original channel).

Figure 19-41 Inter-BSS handover unsuccessful due to invalid frequency supported

MSC BSS (SOURCE)


HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT


BSS(TARGET)


HANDOVER COMMAND

HANDOVER REQUEST



OUT_INTER_BSS_HO (OUT_INTER_BSS_REQ_TO_MSC) MS_ACCESS_BY

_TYPE (SEE NOTE 2)

ALLOC_TCH




OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_RETURN)

INTERBAND_ACTIVITY(PGSM_HO_FAIL) (SEE NOTE 5)

HANDOVER FAILURE

HANDOVER FAILURE

HO_REQ_MSC_FAIL

REASON-FREQUENCYNOTIMPLEMENTED

REASON-FREQUENCYNOTIMPLEMENTED

NOTES:1. Need for handover is recognized within the BSS.2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have Classmark Update message from the mobile so that the target BSS can peg the MS access type.3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected which contains a band handover reference number.4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover. Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the mobile from its current frequency band to a preferred frequency band.5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY will peg different bins. Examples for GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg

INTERBAND_ACTIVITY(INVALID_FREQ_HO)

{4322}


Interband assignment Chapter 19: Ladder diagrams

Interband assignment

Interband activity invalid frequency at assignment

Figure 19-42 shows an invalid frequency at assignment.

Figure 19-42 Invalid frequency at assignment

MS BSS MSC

ASSIGNMENTCOMMAND

NOTE: MS_ACCESS_BY_TYPE pegs the bin that matches the MS capability.

MA_REQ_FROM_MSC

ALLOC_TCH

MA_CMD_TO_MS

MA_FAIL_FROM_MS

INTERBAND_ACTIVITY (INVALID_FREQ_ASGN)

ASSIGNMENTREQUEST

MS_ACCESS_BY_TYPE (SEE NOTE)

ASSIGNMENTFAILURE

REASON-FREQUENCY NOTIMPLEMENTED

ASSIGNMENT FAILURE

REASON-FREQUENCY NOT IMPLEMENTED


Maintenance Information: GSM Statistics Application Band Reassignment

Band Reassignment

Introduction

Figure 19-43 and Figure 19-44 show band reassign ladder diagrams. These diagrams specificallyshow the outgoing handover statistics. By only showing outgoing handover statistics, a betterfocus is placed on the pegging aspects of the band reassign cause.

Handover successful

Figure 19-43 shows an intra-BSS handover attempt of a MS from an SDCCH in the sourcecell (frequency band PGSM) to a TCH in a target cell (frequency band DCS1800). TheMS is a dual mode PGSM/DCS1800 capable mobile.

Figure 19-43 Intra-BSS handover successful

MS BSS MSC


MA_REQ_FROM_MSC

MS_ACCESS_BY_TYPE (TARGET CELL)

(MS_PGSM_DCS1800)



OUT_HO_CAUSE_ATMPT

OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)

ASSIGNMENTREQUEST

HANDOVERCOMMAND

INTERBAND_ACTIVITY

(DCS1800_HO_ATMPT)HANDOVERCOMPLETE(RECEIVED FROMTARGET CELL) OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC)

OUT_HO_NC_SUC


Band Reassignment Chapter 19: Ladder diagrams


Figure 19-44 shows an unsuccessful band reassign.

Figure 19-44 Unsuccessful band reassign

MS BSS MSC


MA_REQ_FROM_MSC

MS_ACCESS_BY_TYPE (TARGET CELL)

(MS_PGSM_DCS1800)



OUT_HO_CAUSE_ATMPT

OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)

ASSIGNMENTREQUEST

HANDOVERCOMMAND

INTERBAND_ACTIVITY

(DCS1800_HO_ATMPT)HANDOVERFAILURE

OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_RETURN)

INTERBAND_ACTIVITY

(DCS1800_HO_FAIL)


Maintenance Information: GSM Statistics Application RSL link scenarios

RSL link scenarios

Introduction

Figure 19-45 shows a ladder diagram scenario for the Radio Signalling Link (RSL) link.


RSL link scenarios Chapter 19: Ladder diagrams

RSL link scenarios

Figure 19-45 RSL link scenarios

RSL LINK

N2_EXPIRY (note 2)

SABM_TX (note 1)

lock of RSL

lock of associated MSI

lock of associated MMS

front panel reset

MSI board physically removed

transmit and or receive path terminated

unlock of RSL

unlock of associated MSI

unlock of associated MMS

front panel reset

MSI physically returned

transmit and or receive path fully restored

RSL LINK

(RSL restoral)

NOTES :1. SABM_TX will periodically repeat in attempt to restore the RSL connection.2. N2_EXPIRY may peg depending on the outage. The period this statistic is

updated is dependent on the RSL attributes lapd_n200 and lapd_t200timer, which get set during the equip of the RSL.

3. If the last RSL to a site goes OOS, then all call processing at the site willcease as all cells at the site will be barred.

STEP 1:

STEP 2 :


Maintenance Information: GSM Statistics Application MTL link scenarios

MTL link scenarios

Introduction to MTL link scenarios

Figure 19-46 to Figure 19-49 show four ladder diagrams as scenarios for theMessage Transfer Link (MTL) link.


MTL link scenarios Chapter 19: Ladder diagrams

MTL link (operator initiated outage)

Figure 19-46 MTL link scenario (Part I)

MTL LINK

MTP_LINK_INS timerstopped

MTP_UNAVAILABLE timerstarted

lock of MTL

lock of associated MSI/XCDR

lock of associated MMS

front panel reset

MSI/XCDR board physically removed

unlock of MTL

unlock of associated MSI/XCDR

unlock of associated MMS

front panel restore

MSI/XCDR board physically returnedMTL LINK

MTP_UNAVAILABLEtimer stopped

MTP_RESTORATIONincremented

MTP_LINK_INS timerstarted

NOTES:1. Lock of MTL or associated device transitions operator and admin states from

B-U to D-L2. Unlock of MTL or associated device transitions operator and admin states from

D-L to B-U.

STEP 1:

STEP 2:

Lock of MTL or associated device transitions operator and admin states from B-U to D-LUnlock of MTL or associated device transitions operator and admin states from D-L to B-U.NOTE



MTL link (transition scenarios Part II)

Figure 19-47 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait.

Figure 19-47 MTL link transition scenarios (Part II)

MTL LINK

MTP_UNAVAILABLEtimer started

MTP_SL_FAIL incremented


MTP_LINKFAIL timerstarted


MTP_SL_ALIGNMENTincremented

(MTL transitions from B-U to E-U with reason Wait)

(MTL transitions from E-U withreason Wait to B-U

MTL LINK

MTP_LINKFAIL

timer stopped




STEP 1:

STEP 2:


MTL link scenarios Chapter 19: Ladder diagrams

MTL link (transition scenarios Part III)

Figure 19-48 shows anMTL transition from B-U to D-U and D-U to B-U with reasonWait MMS not in service.

Figure 19-48 MTL link transition scenarios (Part III)

MTL LINK




MTP_LNK_INS timer started

(MTL transitions from B-U to D-U with reason Wait MMS not in service)

(MTL transitions from D-U with reason Wait MMS not in service

MTL LINK

MTP_LINKFAIL

timer stopped




STEP 1:

STEP 2:



MTL link (transition scenarios Part IV)

Figure 19-49 shows an MTL transition from B-U to E-U and E-U to B-U with reason Waitimproper timeslot mapping between BSC and MSC.

Figure 19-49 MTL link transition scenarios (Part IV)

MTL LINK




MTP_LNK_INS timer started


MTP_SL_ERROR_RATEincremented

MTP_SL_ALIGNMENT incremented(periodically repeats)

(MTL transitions from B-U to E-U with reason Wait, with impropertimeslot mapping between BSC and MSC)

(MTL transitions from E-U with reason Wait to B-U with impropertimeslot mapping between BSC and MSC

MTL LINK

MTP_LINKFAIL

timer stopped




STEP 1:

STEP 2:


GBL statistics Chapter 19: Ladder diagrams

GBL statistics

Introduction to GBL statistics

Figure 19-50 to Figure 19-54 show how the GBL statistics function within the BSS/PCU.

GBL_DL_DATA_THRPUTFigure 19-50 shows GBL_DL_DATA_THRPUT.

Figure 19-50 GBL_DL_DATA_THRPUT

Bearer chan 1

DLCI = 45

DLCI = 55

DLCI = 45

DLCI = 55


Maintenance Information: GSM Statistics Application GBL statistics

GBL_FLOW_CTRL_SENTFigure 19-51 is a ladder diagram detailing the statistic GBL_FLOW_CTRL_SENT when it is pegged.It also shows the request and the response messages sent from the BSS/PCU to the SGSN.

Figure 19-51 GBL_FLOW_CTRL_SENT

BSSGP FLOW CONTROL PDU

BSSGP FLOW CONTROL ACK PDU

BSS/PCU SGSN

GBL_FLOW_CTRL_SENT

CELL_FLUSH_REQSFigure 19-52 illustrates the statistic CELL_FLUSH_REQS when it is pegged. It also showsthe request and the response sent from the SGSN to the PS.

Figure 19-52 CELL_FLUSH_REQS

FLUSH PDU FLUSH PDU

SGSN GB FU

CELL_FLUSH_REQS

PS


GBL statistics Chapter 19: Ladder diagrams

GBL_PAGING_REQSFigure 19-53 is a ladder diagram detailing the statistic GBL_PAGING_REQS when it is pegged. It alsoshows the request and the response messages sent from the SGSN to the BSS/PCU and the MS.

Figure 19-53 GBL_PAGING_REQS

MSBSS/PCU

Channel Request (RACH)

SGSN

BSSGP PS PDU

GBL_PAGING_REQS

PACKET PAGING REQEST (PCH)

Immediate Assignment (GCH)


Maintenance Information: GSM Statistics Application GBL statistics

GBL_UL_DATA_THRPUTFigure 19-54 illustrates the statistic GBL_UL_DATA_THRPUT.

Figure 19-54 GBL_UL_DATA_THRPUT

Bearer chan 1

DLCI = 45

DLCI = 55

DLCI = 45

DLCI = 55


Accessibility statistics Chapter 19: Ladder diagrams

Accessibility statistics

Introduction to accessibility statistics

Figure 19-55 to Figure 19-59 illustrate accessibility statistics.

CHANNEL_REQ_REJFigure 19-55 is a ladder diagram detailing the statistic CHANNEL_REQ_REJ when it is pegged. It alsoshows the request and the response messages sent from the BSS/PCU to the mobile station.

Figure 19-55 Accessibility CHANNEL_REQ_REJ

Immediate Assignment (AGCH)

MSBSS/PCU

Packet Resource Request

CHANNEL_REQ_REJ

PACKET ACCESS REJECT


Maintenance Information: GSM Statistics Application Accessibility statistics

Channel request (RACH) and immediate assignment (AGCH)Figure 19-56 is a ladder diagram detailing the statistics GPRS_ACCESS_PER_RACH andGPRS_ACCESS_PER_AGCH when pegging occurs. It also shows the request and the responsemessages sent from the BSS/PCU to the mobile station.

Figure 19-56 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH

MSBSS/PCU







Accessibility and GBL statisticsFigure 19-57 is a ladder diagram detailing the statistics GBL_PAGING_REQS,GPRS_ACCESS_PER_RACH, and GPRS_ACCESS_PER_AGCH when pegging occurs. It also showsthe request and response messages sent from the SGSN to the BSS/PCU and to the MS.

Figure 19-57 Accessibility and GBL statistics

MSBSS/PCU





SGSN

BSSGP PS PDU

GBL_PAGING_REQS

PACKET PAGING REQEST (PCH)


Maintenance Information: GSM Statistics Application Accessibility statistics

Pegging for MS class types

MS class types are valid for GSR7 release only. They are not valid for EGPRS.

Figure 19-58 is a ladder diagram detailing three MS class type statistics and when pegging occurs. It alsoshows the request and response messages sent from the BSS/PCU to the mobile station.

Figure 19-58 MS CLASS statistics


MSBSS/PCU

Packet Resource Request

MS_CLASS_1_10_REQ

MS_CLASS_11_20_REQ

MS_CLASS_21_29_REQ

CHANNEL_REQ_REC



GPRS_CHANNELS_SWITCHEDFigure 19-59 details the GPRS_CHANNELS_SWITCHED statistic.

Figure 19-59 GPRS_CHANNELS_SWITCHED

TCHSW

GPRSRESSW

GPRSRESSW

GPRSSW RES

TCHSW RES

TCHRESSW

GPRSSW RES

GPRS GPRS GPRSGPRS GPRS

GPRS GPRS GPRSGPRS


Maintenance Information: GSM Statistics Application Throughput statistics

Throughput statistics

Introduction to throughput statistics

Figure 19-60 and Figure 19-61 show throughput statistics diagrams.


Throughput statistics Chapter 19: Ladder diagrams

AIR_UL_DATA_BLKS


Figure 19-60 is a ladder diagram detailing the statistic AIR_UL_DATA_BLKS and when pegging occurs.It also shows the request and response messages sent from the BSS/PCU to the MS.

Figure 19-60 Uplink data transfer

PACKET UPLINK ASSIGNMENT

MSBSS/PCU

DATA BLOCK

AIR_UL_DATA_BLKS

QOS1 QOS2 QOS3

CS1 CS1 CS1

QOS1 QOS2 QOS3

CS2 CS2 CS2


Maintenance Information: GSM Statistics Application Throughput statistics

AIR_DL_DATA_BLKS


Figure 19-61 is a ladder diagram detailing the statistic AIR_DL_DATA_BLKS and when pegging occurs.It also shows the request and response messages sent from the BSS/PCU to the MS.

Figure 19-61 Downlink data transfer

PACKET DOWNLINK ASSIGNMENT

MSBSS/PCU

DATA BLOCK

AIR_DL_DATA_BLKS

QOS1 QOS2 QOS3

CS1 CS1 CS1

QOS1 QOS2 QOS3

CS2 CS2 CS2


Throughput statistics Chapter 19: Ladder diagrams



Chapter

20Impacts on statistics

The collection, interpretation and accuracy of GSM statistics may be affected by a number of factors,for example, new software and hardware features. Although not all of the factors are directlyrelated to statistics, they all have a definite impact on them. The factors described here are listedbelow. Also provided is a list of frequently asked questions with answers.

• "Extended GSM (EGSM)" on page 20-2.

• "Approximate equality" on page 20-5.

• "Phantom RACHs" on page 20-6.

• "Questions and answers" on page 20-9.


Extended GSM (EGSM) Chapter 20: Impacts on statistics

Extended GSM (EGSM)

Overview of EGSM

EGSM900 (Extended GSM) 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 cannotuse the extended frequency band. A GSM900 cell can contain both GSM900 and EGSM900 carrier hardware.

RequirementsAlthough EGSM provides additional frequencies for use, several functions must remain in the originalGSM900 band. Functions that must be performed in the GSM900 band are:

• BCCH carrier frequency.

• SDCCH configuration.

• TCH allocation for immediate assignment.

Channel allocationChannel allocation for an EGSM MS proceeds in a way such that the search is between extended thenprimary band frequencies, starting from best to worst interference bands until a channel is found.

Forced handoversTo avoid blocking of non-EGSMMSs, an extended bandMS using a primary resource can be forced to handoverto an idle extended band resource with an interference band residing above or meeting a specified threshold.

The database parameter egsm_handover_threshold indicates the range of interference bands allowedfor handing over an extended MS using a primary resource that is needed by a non-EGSM MS. Allowedinterference bands are those above or meeting a specified threshold, which are considered quality resources.The operator also has the option to disallow forced handovers by disabling the egsm_handover_threshold flag.

Factors impacting statistics

Factors that contribute to the impacting of statistic values are:

• The relative number of primary and extended band resources at a cell compared to thenumber of EGSM and non-EGSM capable MSs trying to access the cell.

• The egsm_handover_threshold flag value.

The following examples illustrate the impact of the EGSM feature on statistics:


Maintenance Information: GSM Statistics Application Extended GSM (EGSM)

Example 1: MS access to a traffic channelThe following conditions must apply:

• EGSM MSs have used up the primary resources in the cell.

• Non-EGSM MSs are attempting to access the cell.

• The egsm_handover_threshold flag either does not allow or limits handoversfrom primary resources to extended resources.

It is more difficult for non-EGSMMSs to access a TCH since EGSMMSs are occupying the primary resources.

The statistics impacted are shown in Table 20-1.

Table 20-1 MS access to a traffic channel

Statistic Value

MA_CMD_TO_MS_BLKD will be higher

MA_COMPLETE_TO_MSC will be lower

BUSY_TCH max/mean value will be lower

TOTAL_CALLS will be lower

TCH_CONGESTION will be lower (See note)

TCH_USAGE will be lower

TCH_DELAY will be higher

TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not just the primaryband TCHs, even though congestion exists for the primary MSs in this example.

Example 2: Impact due to increased handoversThe following conditions must apply:

• The egsm_handover_flag encourages the handovers of EGSM MSs.

• Many EGSM MSs occupy primary resources.

• Non-EGSM MSs attempt to access the cell.

More intra-cell handovers are attempted to move the EGSM MSs off of primary resourcesto open up primary resources for non-EGSM MSs.

The statistics impacted are shown in Table 20-2.

Table 20-2 Impact due to increased handovers


Extended GSM (EGSM) Chapter 20: Impacts on statistics

Statistic Value

INTRA_CELL_HO will be higher

INTRA_CELL_HO_REQ will be higher

INTRA_CELL_HO_LOSTMS will be higher

INTRA_CELL_HO_ATMPT will be higher

INTRA_CELL_HO_FAIL will be higher

MA_CMD_TO_MS will be higher

MA_FAIL_TO_MS will be higher

BAD_HO_REFNUM_MS will be higher

CLR_REQ_TO_MSC will be higher

ALLOC_SDCCH_FAIL will be higher

Example 3: Impact due to congestionThe following conditions must apply:

• A network has mostly non-EGSM MSs accessing the system. Although extendedresources are available, they are used infrequently.

• Primary resources are completely used up by non-EGSM MSs.

The cell experiences congestion when other non-EGSM MSs try to access the cell, despitethe fact that not all of the resources have been allocated.

The statistics impacted are shown Table 20-3.

Table 20-3 Impact due to congestion

Statistic Value

MA_CMD_TO_MS_BLKD will be higher

MA_COMPLETE_TO_MSC will be lower

BUSY_TCH max/mean value will be lower

TOTAL_CALLS will be lower

TCH_CONGESTION will be lower (See note)

TCH_USAGE will be lower

TCH_DELAY will be higher

TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not just the primaryband TCHs, even though congestion exists for the primary MSs in this example.


Maintenance Information: GSM Statistics Application Approximate equality

Approximate equality

Description of Approximate equality

Statistics are kept by processes at the BTS and BSC. When comparing statistics, minor discrepanciesbetween different statistics may occur because when the statistic interval expires, a procedure maybe in progress and not all statistics related to that procedure have been pegged. These statisticsare pegged in the following interval upon completion of the procedure.

ExampleFigure 20-1 is an example of approximate equality.

Figure 20-1 Approximate equality procedure

9:00 9:30 10:00

MA_CMD_TO_MS

TOTAL_CALLS

MA_COMPLETE_TO_MSC

TCH Assignment Successful Procedure

MA_REQ_FROM_MSC

Although the procedure TCH assignment was successful, the statistics file for the 9:00 to9:30 interval shows the statistic MA_REQ_FROM_MSC incremented with no correspondingMA_CMD_TO_MS and TOTAL_CALLS values. Also, the 9:30 to 10:00 interval shows thestatistics MA_CMD_TO_MS, TOTAL_CALLS, and MA_COMPLETE_TO_MSC incrementedwith no corresponding MA_REQ_FROM_MSC value.


Phantom RACHs Chapter 20: Impacts on statistics

Phantom RACHs

Description of Phantom RACHs

Phantom RACHs occur primarily as the result of sporadic noise and interference. Channel requests fromdistant MSs can be affected by such noise when MS power output is low. If an MS output is high, anytransmitted signals can cause interference to other co-channel and adjacent channel cells. It is unlikelyin a Motorola implementation that cells using similar frequencies will be finely synchronized. Thiscould happen by chance as each BTS does not have frame synchronization. It is possible though forpartial synchronization to occur and contribute to the phantom RACH problem.

Diagram of Phantom RACHs procedure

Figure 20-2 provides a graphic illustration of phantom RACHs.

Figure 20-2 Phantom RACHs illustration

CHANNEL CODER CALL PROCESSINGRSS LAYER 1 RSS ABIS

CHANNEL REQUEST

CHANNEL REQUEST

CHANNEL REQUEST

(unrecognized messagecounter) OK_ACC_PROC_SUC_RACH

ACCESS_PER_RACH(1 + unrecognized message counter)

ALLOC_SDCCH(CHAN_REQ_MS_FAIL)

(INV_EST_CAUSE_ON_RACH


Maintenance Information: GSM Statistics Application Phantom RACHs

Process of Phantom RACHs occurrences

The following process describes the chain of events that take place when a phantom RACH occurs:

1. The channel coder decodes the message on the Random Access Channel from the radio.If the channel coder cannot decode the message because a field is unrecognizable, thechannel coder pegs an internal counter for the unrecognized message.

If the channel coder decodes the message, the channel coder forwards the channel request toRSS Layer 1 and included in the message is the peg count of unrecognized messages.

2. RSS layer 1 pegs the OK_ACC_PROC_SUC_RACH statistic once for the channel requestand pegs the ACCESS_PER_RACH statistic once for the channel request plus the pegcount sent by the Channel Coder. RSS layer 1 does no filtering of the RACH.

3. RSS Abis receives the channel request and verifies the one-byte message from the MS.It verifies that the three most significant bits represent a valid establishment cause (seeGSM4.08, 3.11.0, section 9.1.8 for the valid causes for Phase 1). If the three bits areverified, the RSS Abis sends a channel request to Call Processing. If the three bits are notvalid, the RSS Abis pegs the INV_EST_CAUSE_ON_RACH statistic.

The other five bits of the eight-bit message are an unformatted five-bitfield, which cannot be verified.

4. Call Processing does no filtering of the channel request, it attempts to allocate anSDCCH and pegs the ALLOC_SDCCH statistic. If the MS does not respond to theImmediate Assignment, that is, no MS ever existed for the RACH or the MS is faraway, or turned off, the CHAN_REQ_MS_FAIL statistic is pegged.

There are three levels of filtering the RACH:

At the Channel Coder.

At RSS Abis.

After attempt to allocate resource (due to guard timers expiring).


Phantom RACHs Chapter 20: Impacts on statistics

Raw statistics affected

The following statistics may be affected by phantom RACHs:

• ACCESS_PER_RACH.

• ACCESS_PER_AGCH.

• ALLOC_SDCCH.


• OK_ACC_PROC_SUC_RACH.

• CHAN_REQ_MS_BLK.

• CHAN_REQ_MS_FAIL.

• SDCCH_CONGESTION.

• BUSY_SDCCH.

• BER (SDCCH affected but not TCH).

ACCESS_PER_RACH is pegged for each phantom RACH. The remainder of the above statistics areaffected depending on whether or not the apparent channel request from the MS is known to Call Processing(Layer 3). RSS (Layer 2) filters out RACHs that are invalid. Specifically, Channel Request messagesreceived via the RACH that have invalid (reserved) values in the establishment cause field (referenceGSM 04.08) are filtered by the RSS. Therefore, a lot of phantom RACHs never make it up to the CallProcessing processes because of the gating (filtering) function performed by the RSS.


Maintenance Information: GSM Statistics Application Questions and answers

Questions and answers

Assignment failure

Q: What happens after an ASSIGNMENT FAILURE from the MS?

A: If an Assignment Failure is received from the MS during call set-up, the Assignment Failure isforwarded to the MSC and the MSC (at its discretion) clears the call. If the Assignment Failure is receivedduring a BSS-controlled intra-cell handover, the call reverts back to the old channel.

Q: After an ASSIGNMENT FAILURE from the MS is the call lost or does the systemsend another ASSIGNMENT COMMAND?

A: As explained above, during call set up the MSC decides whether or not to clear the call. Whetheror not the Assignment Command is retried is up to the MSC. If the Assignment Failure is receivedduring intra-cell handover, the call reverts back to the old channel and could send another AssignmentCommand to the MS if the BSS chooses to do another intra-cell handover.

Counters and SDCCH reconfiguration

Q: Will the following counters work correctly after an SDCCH reconfiguration?That is when a TCH is used as an SDCCH:

• ALLOC_SDCCH.


• BUSY_SDCCH.

• BUSY_TCH.

• RF_LOSSES_SD.

• RF_LOSSES_TCH.

• SDCCH_CONGESTION.

• TCH_CONGESTION.

• TCH_USAGE.

A: For example, SDCCH congestion timer gets started when there are no free SDCCHs available atthe cell. If a TCH gets reconfigured to eight SDCCHs, the congestion timer stops because the cell isno longer congested as far as SDCCHs are concerned. The statistics reflect the current status of thesystem. The reconfiguration issue should not affect the accuracy of the statistics.


Questions and answers Chapter 20: Impacts on statistics

Dynamic SDCCH configuration

Q: If configuration of SDCCHs, for example, can occur manually or more importantly occurdynamically during a busy period, would the previous peg information for that half hourperiod be lost, and would this affect key statistic results?

A: No, CHAN_REQ_MS_FAIL (the statistic which is pegged per channel) is not deleted when the channel isconfigured or reconfigured. The process pegging creates the statistic for all possible SDs. This statistic is neverdeleted, so that the statistic for each half hour shows the amount of pegs for the channel for the entire half hour.

Established call loss

Q: Is failed handover and RF_LOSSES_TCH the only possible reason for losing an established call?

A: A call could also be lost because of other procedure failures, like ciphering and Mode Modify.

Location update reject

Q: Why is there no value for LOCATION UPDATE REJECT?

A: The BSS should not have to peg Location Update Rejects. This is a DTAP procedureand the MSC should keep track of this.

Phantom RACHs

Q: How can it be determined how many phantom RACHs have been assigned to an SDCCH?

A: CHAN_REQ_MS_FAIL pegs due to timeout, if the MS is out of range or switched off.After the SDCCH is allocated, an attempt is made to communicate with the MS, and it willnot respond (because it never existed to begin with).

Q: Does updated BTS hardware have any effect on Phantom RACHs?

A: ACCESS_PER_RACH counts reduce considerably between BTS5s and BTS4Ds(3000 > 300), which have full diversity.

Q: What happens after a SDCCH has been seized by a phantom RACH? Will CLR_REQ_TO_MSC,CHAN_REQ_MS_FAIL and RF_LOSSES_SD be pegged?

A: Only CHAN_REQ_MS_FAIL is pegged. CLR_REQ_TO_MSC and RF_LOSSES_SDis not pegged for phantom RACHs.


Index

Index

A

ACCESS_PER_AGCH . . . . . . . . . . . . . 4-8ACCESS_PER_PCH . . . . . . . . . . . . . . 4-9ACCESS_PER_PPCH . . . . . . . . . . . . . 4-11ACCESS_PER_RACH . . . . . . . . . . . . . 4-13Accessibility statistics . . . . . . . . . 12-2, 19-64ADJ_CHAN_INTF. . . . . . . . . . . . . . . 4-85AIR_DL_CONTROL_BLKS . . . . . . . . . . 12-7AIR_DL_DATA_BLKS. . . . . . . . . . . . . 12-8AIR_DL_TBF_FAILURES . . . . . . . . . . 12-10AIR_INTERFACE_BW_CS1 . . . . . . . . . . 18-8AIR_INTERFACE_BW_CS2 . . . . . . . . . . 18-9AIR_INTERFACE_BW_CS3 . . . . . . . . . 18-10AIR_INTERFACE_BW_CS4 . . . . . . . . . 18-11AIR_INTERFACE_PAGING . . . . . . . . . 18-12AIR_UL_CONTROL_BLKS . . . . . . . . . 12-11AIR_UL_DATA_BLKS. . . . . . . . . . . . 12-12AIR_UL_TBF_FAILURES . . . . . . . . . . 12-14ALLOC_SDCCH . . . . . . . . . . . . . . . 4-14ALLOC_SDCCH_CARR . . . . . . . . . . . . 6-4ALLOC_SDCCH_FAIL . . . . . . . . . . . . 4-16ALLOC_TCH . . . . . . . . . . . . . . . . . 4-17ALLOC_TCH_CARR . . . . . . . . . . . . . 6-5ALLOC_TCH_FAIL . . . . . . . . . . . . . . 4-18ALLOC_TCH_FAIL_HR . . . . . . . . . . . . 15-4ALLOC_TCH_HR . . . . . . . . . . . . . . . 15-6AMR_DECREASE_THRESH_ADJUST . . . . 15-7AMR_FR_DL_ADAPTATION . . . . . . . . . 15-9AMR_FR_DL_CODEC_MODE_USAGE . . . . 15-8AMR_FR_UL_ADAPTATION . . . . . . . . 15-10AMR_FR_UL_CODEC_MODE_USAGE . . . 15-11AMR_HR_DL_ADAPTATION . . . . . . . . 15-12AMR_HR_DL_CODEC_MODE_USAGE . . . 15-13AMR_HR_UL_ADAPTATION . . . . . . . . 15-14AMR_HR_UL_CODEC_MODE_USAGE . . . 15-15AMR_INCREASE_THRESH_ADJUST . . . . 15-16approximate equality . . . . . . . . . . . . . . 20-5assignment to TCHassignment successful . . . . . . . . . . . 19-14

assignment to TCH (contd.)fail recovered . . . . . . . . . . . . . . . 19-16immediate assignment failure . . . . . . . . 19-15TCH assignment blocked . . . . . . . . . . 19-15

ASSIGNMENT_REDIRECTION . . . . . . . . 4-19ASSIGNMENT_RESOURCE. . . . . . . . . 4-110ASSIGNMENT_RESOURCE_REQ_IN-NER_Z . . . . . . . . . . . . . . . . . . . 4-110ASSIGNMENT_SUCCESS_RATE . . . . . . 18-13ATER_CHANNEL_STATUS . . . . . . . . . . 11-3ATER_EMERG_PREEMPT_STATUS. . . . . . 11-5ATTEMPT_IMMED_ASSIGN_PROC . . . . . 17-5AVAILABLE_SDCCH . . . . . . . . . . . . . 4-20AVAILABLE_TCH. . . . . . . . . . . . . . . 4-21

B

BAD_HO_REFNUM_MS . . . . . . . . . . . 4-22 Band reassignment

68P02901W56-Q IX-124 May 2004 CONTROLLED INTRODUCTION

Index

Band reassignment (contd.)introductionfail recovered . . . . . . . . . . . . . . 19-52handover successful . . . . . . . . . . . 19-51handover unsuccessful . . . . . . . . . . 19-52

BAND_HANDOVER . . . . . . . . . . . . . 4-85BAND_RE_ASSIGN. . . . . . . . . . . . . . 4-85BER. . . . . . . . . . . . . . . . . . . . . . 6-6Bin ranges . . . . . . . . . . . . . . . . . . . 2-16BSCfunctions . . . . . . . . . . . . . . . . . . 19-3

BSSfunctions . . . . . . . . . . . . . . . . . . 19-3

BSS_OVLD_MSGS_TX . . . . . . . . . . . . 3-4BSSLAP_ABORT_RCV . . . . . . . . . . . . 9-4BSSLAP_ABORT_SENT. . . . . . . . . . . . 9-5BSSLAP_MS_POS_CMD . . . . . . . . . . . 9-6BSSLAP_MS_POS_RESP . . . . . . . . . . . 9-7BSSLAP_REJ . . . . . . . . . . . . . . . . . 9-8

BSSLAP_RESET . . . . . . . . . . . . . . . 9-9BSSLAP_TA_REQ. . . . . . . . . . . . . . . 9-10BSSLAP_TA_RESP . . . . . . . . . . . . . . 9-11BSSLAP_TOA_REQ . . . . . . . . . . . . . . 9-12BSSMAP_CONLESS_INFO_RCV . . . . . . . 9-13BSSMAP_CONLESS_INFO_SENT. . . . . . . 9-14BSSMAP_PERF_LOC_ABORT_MSGS. . . . . 9-15BSSMAP_PERF_LOC_REQ_MSGS . . . . . . 9-16BSSMAP_PERF_LOC_RESP_MSGS . . . 9-17, 9-21BSSMAPLE_CONLESS_INFO_RCV . . . . . . 9-18BSSMAPLE_CONLESS_INFO_SENT . . . . . 9-19BSSMAPLE_PERF_LOC_ABORT_MSGS . . . 9-20BSSMAPLE_PERF_LOC_RESP_MSGS . . . . 9-22BUSY_CICS. . . . . . . . . . . . . . . . . . 10-4BUSY_SDCCH . . . . . . . . . . . . . . . . 4-23BUSY_TCH . . . . . . . . . . . . . . . . . . 4-25BUSY_TCH_CARR . . . . . . . . . . . . . . 4-27BUSY_TCH_CARR_HR . . . . . . . . . . . 15-18BUSY_TCH_HR. . . . . . . . . . . . 15-17, 15-19

C

C_SETUP_SUCCESS_RATE . . . . . . . . . 18-18C_SETUP_TCH_BLOCKING_RATE . . . . . . 16-3C_SP_VERS_DOWNGRADE_MONITOR . . . 4-28C_SUCCESS_RATE . . . . . . . . . . . . . 18-19C_VOLUME. . . . . . . . . . . . . . . . . 18-20call clearingcipher mode fail . . . . . . . . . . . . . . 19-31queueing timeout. . . . . . . . . . . . . . 19-33RF loss on a TCH . . . . . . . . . . . . . 19-33RF loss on an SDCCH . . . . . . . . . . . 19-32

Call model statistics . . . . . . . . . . . . . . 16-1C_SETUP_TCH_BLOCKING_RATE. . . . . 16-3HANDOVERS_PER_C (H) . . . . . . . . . 16-4IMSI_DETACHES_TO_C (Id) . . . . . . . . 16-5INTRA_BSS_HO_TO__HO (i) . . . . . . . . 16-6LOCATION_UPDATE_FACTOR (L) . . . . . 16-7LOCATION_UPDATES_TO_CS (I) . . . . . 16-8PAGES_PER_C (PPC) . . . . . . . . . . . . 16-9PAGES_PER_SECOND . . . . . . . . . . 16-10PAGING_RATE (P) . . . . . . . . . . . . 16-11SMS_TO_C_RATIO (S) . . . . . . . . . . 16-12

call procedurebids . . . . . . . . . . . . . . . . . . . . . 19-5bids-attempt-fail-recovered . . . . . . . . . . 19-5bids-attempt-failures . . . . . . . . . . . . . 19-5bids-attempts . . . . . . . . . . . . . . . . 19-5bids-attempts-successes . . . . . . . . . . . 19-5bids-bids blocked . . . . . . . . . . . . . . 19-5

call setup and handover matrix . . . . . . . . . 19-6call statisticscall_statistics . . . . . . . . . . . . . . . . 4-75

CALL_SETUP_RF_ASSIGN-MENT_FAIL_RATE_LOST_MS . . . . . . . 18-14CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RE-COVERED_MS . . . . . . . . . . . . . . . 18-16CALL_SETUP_RF_ASSIGNMENT_SUC-CESS_RATE. . . . . . . . . . . . . . . . . 18-17cell statisticsintroduction . . . . . . . . . . . . . . . . . 4-2

CELL_FLUSH_REQS . . . . . . . . . . . . 12-15CELL_TCH_ASSIGNMENTS . . . . . . . . . 17-8CELL_TCH_OCATIONS. . . . . . . . . . . . 17-7CELL_UPDATE . . . . . . . . . . . . . . . 18-21CH_REQ_UNSVCD_PCU . . . . . . . . . . 12-16CHAN_DL_TX_PWR_LVL . . . . . . . . . . 6-8CHAN_REQ_CAUSE_ATMPT . . . . . . . 4-31, 9-2CHAN_REQ_MS_BLK . . . . . . . . . . . . 4-32CHAN_REQ_MS_FAIL . . . . . . . . . . 4-33, 6-9CHAN_UL_TX_PWR_LVL . . . . . . . . . . 6-11CHANNEL_REQS_REC . . . . . . . . . . . 12-18CHANNEL_REQS_REJ . . . . . . . . . . . 12-19CHANNEL_REQS_SUCCESS . . . . . . . . 12-20chg_stat_prop . . . . . . . . . . . . . . . . . 2-15chg_stat_prop command . . . . . . . . . . . . 2-13CIPHER_MODE_FAIL. . . . . . . . . . . . . 4-34CLASSMK_UPDATE_FAIL . . . . . . . . . . 4-35CLR_CMD_FROM_MSC . . . . . . . . . . . 4-36CLR_REQ_TO_MSC . . . . . . . . . . . . . 4-37cm_lcs_request. . . . . . . . . . . . . . . . . 4-82CM_REESTABLISH . . . . . . . . . . . . . . 4-82CM_SERV_REQ_C . . . . . . . . . . . . . . 4-82

IX-2 68P02901W56-QCONTROLLED INTRODUCTION 24 May 2004

Maintenance Information: GSM Statistics Application Index

CM_SERV_REQ_EMERG . . . . . . . . . . . 4-82CM_SERV_REQ_SMS . . . . . . . . . . . . . 4-82CM_SERV_REQ_SUPP . . . . . . . . . . . . 4-82CODING_SCHEME_CHANGE . . . . . . . 12-22CONG_REL_DL_SCTS . . . . . . . . . . . 12-24CONGEST_EXIST_HO_ATMPT . . . . . . . . 4-39CONGEST_STAND_HO_ATMPT . . . . . . . 4-40CONGESTION . . . . . . . . . . . . . . . . 4-85Congestion reliefintra-BSS . . . . . . . . . . . . . . . . . 19-37

CONGESTION_LOST_MSU . . . . . . . . . . 10-6CONN_REFUSED . . . . . . . . . . . . . . . 4-41CONN_REQ_TO_MSC . . . . . . . . . . . . 4-43connection establishmentfailurefailute. . . . . . . . . . . . . . . . . . 19-11

immediate assignment blocked . . . . . . . 19-12immediate assignment failure . . . . . . . . 19-12successfulmobile originated . . . . . . . . . . . . 19-10mobile terminated call . . . . . . . . . . 19-13

Counter array statistics . . . . . . . . . . . . . 1-7Counter array bins . . . . . . . . . . . . . . 1-7Interval expiry . . . . . . . . . . . . . . . . 1-7Maximum values. . . . . . . . . . . . . . . 1-7

Counter statistics . . . . . . . . . . . . . . 1-6, 2-14Interval expiry . . . . . . . . . . . . . . . . 1-6Maximum value . . . . . . . . . . . . . . . 1-6Threshold event reporting. . . . . . . . . . . 1-6

CPU_USAGE . . . . . . . . . . . . . . . . . 7-2CS_QUEUED . . . . . . . . . . . . . . . . . 4-30CS1_USAGE_DL . . . . . . . . . . . . . . 18-22CS1_USAGE_UL . . . . . . . . . . . . . . 18-23CS12_ON_32K_CHAN . . . . . . . . . . . 12-26CS2_USAGE_DL . . . . . . . . . . . . . . 18-24CS2_USAGE_UL . . . . . . . . . . . . . . 18-25CS3_USAGE_DL . . . . . . . . . . . . . . 18-26CS3_USAGE_UL . . . . . . . . . . . . . . 18-27CS4_USAGE_DL . . . . . . . . . . . . . . 18-28CS4_USAGE_UL . . . . . . . . . . . . . . 18-29Custom statistics . . . . . . . . . . . . . . . . 1-4

D

default values . . . . . . . . . . . . . . . . . 2-2Dictionary = brAverage call duration . . . . . . . . . . . . . 16-2C_DURATION . . . . . . . . . . . . . . . 16-2Call model statisticsC_DURATION . . . . . . . . . . . . . . 16-2

Directed retryintra-BSS . . . . . . . . . . . . . . . . . 19-39

disabling a statisticdisable a statistic . . . . . . . . . . . . . . . 2-3

disp_interval command . . . . . . . . . . . . . 2-11disp_stat_prop command . . . . . . . . . . . . 2-17disp_stats command . . . . . . . . . . . . . . 2-7Displaying a counter array statistic. . . . . . . . 2-22Displaying a counter statistic . . . . . . . . . . 2-18Displaying a distribution statistic . . . . . . . . 2-20Displaying a duration statistic . . . . . . . . . . 2-24Displaying a gauge statistic . . . . . . . . . . . 2-19Displaying statistic properties . . . . . . . . . . 2-17Displaying a counter array statistic . . . . . . 2-22Displaying a counter statistic . . . . . . . . . 2-18Displaying a distribution statistic . . . . . . . 2-20Displaying a duration statistic . . . . . . . . . 2-24Displaying a gauge statistic . . . . . . . . . . 2-19

Displaying statistic values. . . . . . . . . . . . 2-7Displaying the statistics interval . . . . . . . . . 2-10Displaying the statistics interval start times. . . . 2-11DISTANCE . . . . . . . . . . . . . . . . . . 4-85Distribution statistics . . . . . . . . . . . . . . 1-9

DL_AIR_INTERFACE_BW_CS1 . . . . . . . 18-30DL_AIR_INTERFACE_BW_CS2 . . . . . . . 18-31DL_AIR_INTERFACE_BW_CS3 . . . . . . . 18-32DL_AIR_INTERFACE_BW_CS4 . . . . . . . 18-33DL_BUSY_PDTCH . . . . . . . . . . . . . 12-27DL_PDTCH_CONGESTION . . . . . . . . . 12-29DL_PDTCH_Q_LENGTH . . . . . . . . . . 12-30DL_PDTCH_SEIZURE . . . . . . . . . . . 12-31DL_RADIO_BLKS_1_TS . . . . . . . . . . 12-32DL_RADIO_BLKS_2_TS . . . . . . . . . . 12-34DL_RADIO_BLKS_3_TS . . . . . . . . . . 12-36DL_RADIO_BLKS_4_TS . . . . . . . . . . 12-38DL_RLC_ACK_NEW_BLKS. . . . . . . . . 12-40DL_RLC_DDTR_BLKS . . . . . . . . . . . 12-42DL_RLC_NACK_BLKS . . . . . . . . . . . 12-43DL_RLC_RETX_BLKS . . . . . . . . . . . 12-45DL_RLC_STED_BLKS . . . . . . . . . . . 12-47DL_RLC_UNACK_NEW_BLKS . . . . . . . 12-49DL_TBF_TIME_1_TS . . . . . . . . . . . . 12-51DL_TBF_TIME_2_TS . . . . . . . . . . . . 12-52DL_TBF_TIME_3_TS . . . . . . . . . . . . 12-53DL_TBF_TIME_4_TS . . . . . . . . . . . . 12-54DOWNINTERF . . . . . . . . . . . . . . . . 4-85DOWNLEVEL. . . . . . . . . . . . . . . . . 4-85DOWNLINK_TRAFFIC_VOLUME . . . . . 18-34DOWNQUAL . . . . . . . . . . . . . . . . . 4-85DROP_C_RATE . . . . . . . . . . . . . . . 18-36Duration statistics . . . . . . . . . . . . . . . 1-8Interval expiry . . . . . . . . . . . . . . . . 1-8


Index

Maximum value . . . . . . . . . . . . . . . 1-8Period counter and mean value . . . . . . . . 1-8Total duration . . . . . . . . . . . . . . . . 1-8Wraparound to next day . . . . . . . . . . . 1-8

Dynamic allocation statistics . . . . . . . . . . 12-6DYNET_ASSIGN_FAIL . . . . . . . . . . . . 4-44DYNET_C_REJECTS . . . . . . . . . . . . . 4-45

E

EGPRS_64K_CHANNELS_SWITCHED . . . 12-55EGPRS_64K_NOT_AVAIL . . . . . . . . . . 12-56EGPRS_AVAIL_PDTCH . . . . . . . . . . . 12-57EGPRS_DL_ASGN_PCCCH . . . . . . . . . 12-58EGSM (extended GSM) . . . . . . . . . . . . 20-2enabling a statisticenable a statistic . . . . . . . . . . . . . . . 2-3

ER_INTRA_CELL_HO_ATMPT . . . . . . . . 4-46

ER_INTRA_CELL_HO_SUC. . . . . . . . . . 4-47

F

feature22064 . . . . . . . . . . . . . . . . . . . 4-28,4-52, 4-67, 4-106 to 4-107, 6-12, 15-4, 15-6, 15-17 to15-18, 15-26 to 15-29, 17-32, 17-34 to 17-36, 18-36,18-68 to 18-69, 18-115 to 18-116, 18-11823658 . . . . . . . . . . . . . . . 4-9, 4-11, 12-3to 12-5, 12-7, 12-10 to 12-11, 12-14, 12-16, 12-18 to12-20, 12-22, 12-24, 12-27, 12-29 to 12-32, 12-34,12-36, 12-38, 12-40, 12-42 to 12-43, 12-45, 12-47,12-49, 12-51 to 12-59, 12-74, 12-77 to 12-78, 12-85 to12-86, 12-88, 12-90, 12-97, 12-108 to 12-109, 12-111to 12-114, 12-116, 12-118, 12-120, 12-122, 12-124,12-126, 12-128 to 12-13124661 . . . . . 2-15, 3-3 to 3-4, 3-10 to 3-11, 3-15

feature (contd.)3723 . . . . . . . . . . . . . . . 4-3, 4-7, 4-11,4-95, 12-3, 12-18, 12-75, 12-80, 12-874322 . . . . . . . . . . . . . . . . . . . . 3-6,4-5, 4-28, 4-52, 4-62 to 4-63, 4-67 to 4-68, 4-70, 6-12,15-3, 15-7 to 15-16, 15-20, 15-22, 15-26, 19-74415 . . . . . . . . . . . . . . . . . . . . 15-34441 . . . 12-2 to 12-3, 12-16, 12-59, 12-88, 12-904445 . . . . . . . . . . 12-4, 12-10, 12-14, 12-24

FER_AMR_FR . . . . . . . . . . . . . . . 15-20FER_AMR_HR . . . . . . . . . . . . . . . 15-22FER_GSM_FR_EFR . . . . . . . . . . . . . . 6-12FER_GSM_HR . . . . . . . . . . . . . . . 15-24FLOW_CONTROL_BARRED . . . . . . . . . 4-48FRMR. . . . . . . . . . . . . . . . . . . . . 11-6

G

G_RACH_UNSVCD_BTS . . . . . . . . . . 12-59Gauge statistics . . . . . . . . . . . . . . . . 1-7Interval expiry . . . . . . . . . . . . . . . . 1-7Threshold event reporting. . . . . . . . . . . 1-7

Gb interface . . . . . . . . . . . . . . . . . . 12-2GBL statistics . . . . . . . . . . . . . 12-2, 19-60GBL_AVAILABILITY . . . . . . . . . . . . 18-38GBL_DL_DATA_THRPUT. . . . . . . . . . 12-60GBL_DL_DATA_THRPUT_HIST . . . . . . 12-61GBL_FLOW_CTRL_SENT. . . . . . . . . . 12-63

GBL_FLUSH_REQSsee CELL_FLUSH_REQS . . . . . . . . . 12-15

GBL_LINK_INS . . . . . . . . . . . . . . . 12-64GBL_PAGING_REQS . . . . . . . . . . . . 12-65GBL_UL_DATA_THRPUT. . . . . . . . . . 12-66GBL_UL_DATA_THRPUT_HIST . . . . . . 12-67GBL_UNAVAILABLE . . . . . . . . . . . . 12-69GPRS performance . . . . . . . . . . . . . . . 18-2GPRS_32K_CHANNELS_SWITCHED . . . . 12-70GPRS_32K_DL_NOT_AVAIL . . . . . . . . 12-71



GPRS_32K_UL_NOT_AVAIL . . . . . . . . 12-72GPRS_ACCESS_PER_AGCH . . . . . . . . 12-73GPRS_ACCESS_PER_RACH . . . . . . . . 12-74GPRS_AVAIL_PDTCH. . . . . . . . . . . . 12-75GPRS_BW_USAGE_DL . . . . . . . . . . . 18-39GPRS_BW_USAGE_UL . . . . . . . . . . . 18-40GPRS_CELL_RESELECT_ATTMPT . . . . . 12-77GPRS_CELL_RESELECT_FAIL . . . . . . . 12-78GPRS_CHANNELS_SWITCHED . . . . . . 12-79GPRS_DL_ACT_TS . . . . . . . . . . . . . 18-41GPRS_DL_ASGN_PCCCH. . . . . . . . . . 12-80

GPRS_DYNET_FAILURES . . . . . . . . . 12-81GPRS_DYNET_RES_REQS . . . . . . . . . 12-83GPRS_DYNET_SWI_REQS . . . . . . . . . 12-84GPRS_MS_NEIGHBOR_STRONG . . . . . . 12-85GPRS_PCH_AGCH_Q_LENGTH . . . . . . 12-86GPRS_PPCH_PAGCH_Q_LENGTHGPRS_PCH_AGCH_Q_LENGTH . . . . . 12-87

GPRS_PRR_BLK_USG . . . . . . . . . . . 12-88GPRS_RACH_ARRIVAL . . . . . . . . . . 12-90GPRS_UL_ACT_TS . . . . . . . . . . . . . 18-42

H

handover. . . . . . . . . . . . . . . . . . . . 19-4handover performance . . . . . . . . . . . . . 18-3Handover successfulband reassignmentintroduction . . . . . . . . . . . . . . . 19-51

HANDOVER_FAILURE_RATE . . . . . . . . 17-9HANDOVER_SUCCESS_RATE . . . . . . . 17-10Handoversratio per call . . . . . . . . . . . . . . . . . 16-4

HANDOVERS_PER_C. . . . . . . . . . . . . 16-4health check . . . . . . . . . . . . . . . . . . 18-5HO_CAUSE_ADJ_CH_INTERF . . . . . . . 18-43HO_CAUSE_BAND_HO. . . . . . . . . . . 18-44HO_CAUSE_BAND_REASSGN . . . . . . . 18-45HO_CAUSE_CONGEST . . . . . . . . . . . 18-46HO_CAUSE_DISTANCE . . . . . . . . . . 18-47

HO_CAUSE_DLINTERF . . . . . . . . . . 18-48HO_CAUSE_DLLEVEL . . . . . . . . . . . 18-49HO_CAUSE_DLQUAL . . . . . . . . . . . 18-50HO_CAUSE_PWRBGT . . . . . . . . . . . 18-51HO_CAUSE_UPINTERF. . . . . . . . . . . 18-52HO_CAUSE_UPLEVEL . . . . . . . . . . . 18-53HO_CAUSE_UPQUAL . . . . . . . . . . . 18-54HO_FAIL_NO_RESOURCES . . . . . . . . . 4-49HO_PER_C . . . . . . . . . . . . . . . . . 18-55HO_REQ . . . . . . . . . . . . . . . . . . 4-110HO_REQ_ACK_TO_MSC . . . . . . . . . . . 4-52HO_REQ_FROM_MSC . . . . . . . . . . . 15-26HO_REQ_INNER_Z . . . . . . . . . . . . . 4-110HO_REQ_MSC_FAIL . . . . . . . . . . . . . 4-51HO_REQ_MSC_PROTO . . . . . . . . . . . . 3-5


Index

I

I_FRAMES_RX . . . . . . . . . . . . . . . . 11-7I_FRAMES_TX . . . . . . . . . . . . . . . . 11-8IDLE_PDTCH_INTF_BAND0 . . . . . . . . 12-92IDLE_PDTCH_INTF_BAND1 . . . . . . . . 12-93IDLE_PDTCH_INTF_BAND2 . . . . . . . . 12-94IDLE_PDTCH_INTF_BAND3 . . . . . . . . 12-95IDLE_PDTCH_INTF_BAND4 . . . . . . . . 12-96IDLE_TCH_INTF_BAND0. . . . . . . . . . . 4-54IDLE_TCH_INTF_BAND1. . . . . . . . . . . 4-55IDLE_TCH_INTF_BAND2. . . . . . . . . . . 4-56IDLE_TCH_INTF_BAND3. . . . . . . . . . . 4-57IDLE_TCH_INTF_BAND4. . . . . . . . . . . 4-58IMM_ASSGN_CAUSE. . . . . . . . . . . . 12-97IMSI detachesratio per call . . . . . . . . . . . . . . . . . 16-5

IMSI_DETACH . . . . . . . . . . . . . . . . 4-82IMSI_DETACHES_TO_C . . . . . . . . . . . 16-5IN_INTER_BSS_EQUIP_FAIL . . . . . . . . . 4-59IN_INTER_BSS_HO. . . . . . . . . . . . . . 4-59IN_INTER_BSS_HO_CLEARED. . . . . . . . 4-59IN_INTER_BSS_HO_SEIZE . . . . . . . . . . 4-59IN_INTER_BSS_HO_SUC . . . . . . . 4-59, 18-56IN_INTER_CELL_HO_SUC . . . . . . . . . 18-57IN_INTER_CELL_HO_TO_IN_ZONE . . . . 4-116to 4-117IN_INTRA_BSS_EQUIP_FAIL . . . . . . . . . 4-60IN_INTRA_BSS_HO. . . . . . . . . . . . . . 4-60IN_INTRA_BSS_HO_CLEARED. . . . . . . . 4-60IN_INTRA_BSS_HO_LOSTMS . . . . . . . . 4-60IN_INTRA_BSS_HO_RETURN . . . . . . . . 4-60IN_INTRA_BSS_HO_SUC. . . . . . . 4-60, 18-58IN_INTRA_BSS_NC_ATMPT . . . . . . . . . 5-8IN_INTRA_BSS_NC_SUC . . . . . . . . . . . 5-9INCOMING_HO_VOLUME . . . . . . . . . 18-59INNER_TO_OUTER_ZONE . . . . . 4-116 to 4-117inter-BSS handoverfail lost . . . . . . . . . . . . . . . . . . 19-23fail lost mobile . . . . . . . . . . . . . . . 19-24fail recovered . . . . . . . . . . . . . . . 19-22handover blocked . . . . . . . . . . . . . 19-20handover successful . . . . . . . . . . . . 19-20standard directed retryexternal . . . . . . . . . . . . . . . . . 19-25

Interband activityinter-BSSfail recovered . . . . . . . . . . . . . . 19-48handover successful . . . . . . . . . . . 19-46handover unsuccessful . . . . . . . . . . 19-48invalid frequency supported . . . . . . . 19-49

Interband activity (contd.)intra-BSSfail recovered . . . . . . . . . . . . . . 19-44handover unsuccessful . . . . . . . . . . 19-44invalid frequency supported . . . . . . . 19-45

Interband assignmentinvalid frequency . . . . . . . . . . . . . 19-50

INTERBAND_ACTIVITY . . . . . . . . . . . 4-61INTERNAL_LOST. . . . . . . . . . . . . . 18-60INTERNAL_RECOVERED . . . . . . . . . 18-61INTERNAL_SUCCESS . . . . . . . . . . . 18-62INTF_ON_IDLE . . . . . . . . . . . . . . . . 6-14Intra-BSScongestion relief . . . . . . . . . . . . . . 19-37directed retry . . . . . . . . . . . . . . . 19-39

intra-BSS handoverfail-lost . . . . . . . . . . . . . . . . . . 19-29fail-recovered . . . . . . . . . . . . . . . 19-28handover blocked . . . . . . . . . . . . . 19-26handover successful . . . . . . . . . . . . 19-26standard directed retryinternal . . . . . . . . . . . . . . . . . 19-30

Intra-BSS handovers . . . . . . . . . . . . . . 16-6INTRA_BSS_HO_CAUSE_SUC . . . . . . . . 3-6INTRA_BSS_HO_TO__HO . . . . . . . . . . 16-6intra-cell handoverfail lost . . . . . . . . . . . . . . . . . . 19-19fail recovered . . . . . . . . . . . . . . . 19-18handover blocked . . . . . . . . . . . . . 19-18handover successful . . . . . . . . . . . . 19-17

INTRA_CELL_EQUIP_FAIL. . . . . . . . . . 4-62INTRA_CELL_HO. . . . . . . . . . . . . . . 4-62INTRA_CELL_HO_ATMPT_FR_FR . . . . . . 4-62INTRA_CELL_HO_ATMPT_FR_HR . . . . . . 4-62INTRA_CELL_HO_ATMPT_HR_FR . . . . . . 4-62INTRA_CELL_HO_ATMPT_HR_HR. . . . . . 4-62INTRA_CELL_HO_CLEARED . . . . . . . . 4-62INTRA_CELL_HO_FAIL_LOST_MS. . . . . 18-63INTRA_CELL_HO_FAIL_RECOVERED . . . 18-64INTRA_CELL_HO_LOSTMS . . . . . . . . . 4-62INTRA_CELL_HO_REQ. . . . . . . . . . . . 4-62INTRA_CELL_HO_RETURN . . . . . . . . . 4-62INTRA_CELL_HO_SUC. . . . . . . . . . . . 4-62INTRA_CELL_HO_SUCCESS_RATE . . . . 18-65INTRA_ZONE. . . . . . . . . . . . 4-116 to 4-117INV_EST_CAUSE_ON_RACH. . . . . . . . . 4-64INVALID_FRAMES_RX. . . . . . . . . . . . 11-9



K

key statistics . . . . . . . . . . . . 1-3, 17-2 to 17-4ATTEMPT_IMMED_ASSIGN_PROC . . . . 17-5call summary . . . . . . . . . . . . . . . . 17-2CELL_TCH_ASSIGNMENTS . . . . . . . . 17-8CELL_TCH_OCATIONS . . . . . . . . . . 17-7channel usage . . . . . . . . . . . . . . . . 17-2connection establishment . . . . . . . . . . . 17-3HANDOVER_FAILURE_RATE . . . . . . . 17-9HANDOVER_SUCCESS_RATE . . . . . . 17-10loss summary . . . . . . . . . . . . . . . . 17-3MEAN_ARRIVAL_TIME_BE-TWEEN_CS. . . . . . . . . . . . . . . . 17-12MEAN_INTER_ARRIVAL_TIME . . . . . 17-13MEAN_TCH_BUSY_TIME . . . . . . . . 17-14MTL_UTILISATION_RX . . . . . . . . . 17-15MTL_UTILISATION_TX . . . . . . . . . 17-16RF_LOSS_RATE . . . . . . . . . . . . . 17-17SDCCH_ACCESS_SUCCESS_RATE. . . . 17-18SDCCH_BLOCKING_RATE. . . . . . . . 17-19

key statistics (contd.)SDCCH_MEAN_ARRIVAL_RATE. . . . . 17-21SDCCH_MEAN_HOLDING_TIME . . . . 17-22SDCCH_RF_LOSS_RATE . . . . . . . . . 17-23SDCCH_SETUP_BLOCKING_RATE . . . 17-20SDCCH_TRAFFIC_CARRIED. . . . . . . 17-24SUCCESS_IMMED_ASSIGN_PROC . . . 17-26SUCCESS_INTERNAL_HO . . . . . . . . 17-27TCH_BLOCKING_RATE . . . . . . . . . 17-28TCH_BLOCKING_RATE_INNER_Z . . . . 17-29TCH_BLOCKING_RATE_OUTER_Z . . . 17-30TCH_MEAN_ARRIVAL_RATE . . . . . . 17-31TCH_MEAN_HOLDING_TIME . . . . . . 17-32TCH_TRAFFIC_CARRIED . . . . 17-36, 18-118template . . . . . . . . . . . . . . . . . . . 17-4TOTAL_CS_KEY . . . . . . . . . . . . . 17-38UNSUCCESS_INTER-NAL_HO_NOREEST . . . . . . . . . . . 17-39UNSUCCESS_INTERNAL_HO_REEST . . 17-40

L

L_ROUTING_SYNTAX . . . . . . . . . . . . 13-3L_ROUTING_UNKNOWN. . . . . . . . . . . 13-4L_SCCP_MSGS . . . . . . . . . . . . . . . . 13-5L_SCCP_MSGS_RX . . . . . . . . . . . . . . 13-6l_sccp_msgs_rx_0 . . . . . . . . . . . . . . . 13-6l_sccp_msgs_rx_2 . . . . . . . . . . . . . . . 13-6L_SCCP_MSGS_TX . . . . . . . . . . . . . . 13-7l_sccp_msgs_tx_0 . . . . . . . . . . . . . . . 13-7l_sccp_msgs_tx_2 . . . . . . . . . . . . . . . 13-7L_SIF_SIO_RX_OPC . . . . . . . . . . . . . 13-8L_SIF_SIO_TX_OPC . . . . . . . . . . . . . 13-9l_sif_sio_type . . . . . . . . . . . . . . . . 13-10L_SIF_SIO_TYPE . . . . . . . . . . . . . . 13-10l_sif_sio_type_mtp . . . . . . . . . . . . . . 13-10l_sif_sio_type_test . . . . . . . . . . . . . . 13-10LAPD_CONGESTION . . . . . . . . . . . . 11-10LMTP_CHANGEBACK . . . . . . . . . . . . 8-6LMTP_CHANGEOVER . . . . . . . . . . . . 8-7LMTP_CONGESTION . . . . . . . . . . . . . 8-35LMTP_LINK_INS . . . . . . . . . . . . . . . 8-9LMTP_LINKFAIL . . . . . . . . . . . . . . . 8-10LMTP_LOCAL_BUSY. . . . . . . . . . . . . 8-11LMTP_LOCAL_MGT . . . . . . . . . . . . . 8-12LMTP_LOCAL_SL_CONGESTION . . . . . . 8-8LMTP_MGT_INHIBIT. . . . . . . . . . . . . 8-13LMTP_MGT_UNINHIBIT . . . . . . . . . . . 8-14LMTP_MSU_DISCARDED . . . . . . . . . . 8-5LMTP_MSU_RX . . . . . . . . . . . . . . . 8-15

LMTP_MSU_TX . . . . . . . . . . . . . . . 8-16LMTP_NEG_ACKS . . . . . . . . . . . . . . 8-17LMTP_RE_TX. . . . . . . . . . . . . . . . . 8-18LMTP_REMOTE_MGT . . . . . . . . . . . . 8-19LMTP_REMOTE_PROC . . . . . . . . . . . . 8-20LMTP_RESTORATION . . . . . . . . . . . . 8-21LMTP_SIB_RX . . . . . . . . . . . . . . . . 8-34LMTP_SIB_TX . . . . . . . . . . . . . . . . 8-36LMTP_SIF_SIO_RX . . . . . . . . . . . . . . 8-22LMTP_SIF_SIO_TX . . . . . . . . . . . . . . 8-23LMTP_SL_ACK . . . . . . . . . . . . . . . . 8-24LMTP_SL_ALIGNMENT . . . . . . . . . . . 8-25LMTP_SL_CONGESTION . . . . . . . . . . . 8-26LMTP_SL_ERROR_RATE . . . . . . . . . . . 8-27LMTP_SL_FAIL . . . . . . . . . . . . . . . . 8-28LMTP_SL_FIBR. . . . . . . . . . . . . . . . 8-29LMTP_START_RPO . . . . . . . . . . . . . . 8-30LMTP_STOP_RPO . . . . . . . . . . . . . . 8-31LMTP_SU_ERROR . . . . . . . . . . . . . . 8-32LMTP_UNAVAILABLE . . . . . . . . . . . . 8-33LOC_FLW_ON_REQ_NORM . . . . . . . . . 4-82LOC_FLW_ON_REQ_SMS . . . . . . . . . . 4-82Location updatesratio per call . . . . . . . . . . . . . . . . . 16-8

LOCATION_SERVICES . . . . . . . . . . . . 4-82LOCATION_UPDATE . . . . . . . . . . . . . 4-82LOCATION_UPDATE_FACTOR . . . . . . . . 16-7LOCATION_UPDATES_TO_CS . . . . . . . . 16-8


Index

M

MA_CMD_TO_MSMS_CMD_TO_MS . . . . . . . . . . . . . 4-65

MA_CMD_TO_MS_BLKD. . . . . . . . . . . 4-72MA_COMPLETE_TO_MS . . . . . . . . . . . 4-66MA_COMPLETE_TO_MSC . . . . . . . . . . 4-67MA_FAIL_FROM_MS . . . . . . . . . . . . . 4-69MA_REQ_FROM_MSC . . . . . . . . . . . . 4-70MA_REQ_FROM_MSC_FAIL . . . . . . . . . 3-8MAX_TCH_BUSY. . . . . . . . . . . . . . 18-66MEAN_ARRIVAL_TIME_BETWEEN_CS . . 17-12MEAN_INTER_ARRIVAL_TIME . . . . . . 17-13MEAN_TCH_BUSY_TIME . . . . . . . . . 17-14MEAN_TIME_BETWEEN_DROPS . . . . . 18-68MEAN_TIME_BETWEEN_HOs . . . . . . . 18-69MMI BSC/BTS statisticsHO_FAIL_NO_RESOURCES . . . . . . . . 14-2HO_REQ_MSC_FAIL . . . . . . . . . . . . 14-2MA_CMD_TO_MS_BLKD . . . . . . . . . 14-2OC_SDCCH_FAIL . . . . . . . . . . . . . 14-2OC_TCH_FAIL . . . . . . . . . . . . . . . 14-2RF_LOSSES_TCH. . . . . . . . . . . . . . 14-2

MMI PCU statisticCELL_FLUSH_REQS . . . . . . . . . . . . 14-2CHANNEL_REQS_REJ . . . . . . . . . . . 14-2GBL_LINK_INS. . . . . . . . . . . . . . . 14-2GBL_PAGING_REQS . . . . . . . . . . . . 14-2GBL_UNAVAILABLE . . . . . . . . . . . . 14-2

Monitoring faults . . . . . . . . . . . . . . . . 1-16MS_ACCESS_BY_TYPE . . . . . . . . . . . 4-73MS_CLASS_1_10_REQ . . . . . . . . . . . 12-99MS_CLASS_11_20_REQ. . . . . . . . . . . 12-101MS_CLASS_21_29_REQ . . . . . . . . . . 12-103MS_TCH_USAGE_BY_TYPE . . . . . . . . . 4-74MS_TCH_USAGE_BY_TYPE_PCS . . . . . . 4-75MSC functionsMSC function . . . . . . . . . . . . . . . . 19-3

MSC_OLVD_MSGS_RX4322 . . . . . . . . . . . . . . . . . . . . 3-9

MSC_PAGING. . . . . . . . . . . . . . . . 18-67MSGS_DISCARD_ON_GPROC . . . . . . . . 3-10MSGS_DISCARD_ON_RSL . . . . . . . . . . 3-11MSU_DISCARDED . . . . . . . . . . . . . . 10-7MT_LCS_ON_SDCCH. . . . . . . . . . . . . 4-77MTLoperator initiated outage . . . . . . . . . . 19-56transition scenarios . . . . . . . . . . . . . 19-57

MTL_UTILISATION_RX . . . . . . . . . . 17-15MTL_UTILISATION_TX . . . . . . . . . . 17-16MTP_CHANGEBACK . . . . . . . . . . . . . 10-8MTP_CHANGEOVER . . . . . . . . . . . . . 10-9MTP_CONGESTION . . . . . . . . . . . . 10-10MTP_LINK_INS. . . . . . . . . . . . . . . 10-11MTP_LINKFAIL. . . . . . . . . . . . . . . 10-12MTP_LOCAL_BUSY . . . . . . . . . . . . 10-13MTP_LOCAL_MGT . . . . . . . . . . . . . 10-14MTP_MGT_INHIBIT . . . . . . . . . . . . 10-15MTP_MGT_UNINHIBIT. . . . . . . . . . . 10-16MTP_MSU_RX . . . . . . . . . . . . . . . 10-17MTP_MSU_TX . . . . . . . . . . . . . . . 10-18MTP_NEG_ACKS . . . . . . . . . . . . . . 10-19MTP_RE_TX . . . . . . . . . . . . . . . . 10-20MTP_REMOTE_MGT . . . . . . . . . . . . 10-21MTP_REMOTE_PROC . . . . . . . . . . . 10-22MTP_RESTORATION . . . . . . . . . . . . 10-23MTP_SIF_SIO_RX . . . . . . . . . . . . . 10-24MTP_SIF_SIO_TX. . . . . . . . . . . . . . 10-25MTP_SL_ACK . . . . . . . . . . . . . . . 10-26MTP_SL_ALIGNMENT . . . . . . . . . . . 10-27MTP_SL_CONGESTION . . . . . . . . . . 10-28MTP_SL_ERROR_RATE . . . . . . . . . . 10-29MTP_SL_FAIL . . . . . . . . . . . . . . . 10-30MTP_SL_FIBR . . . . . . . . . . . . . . . 10-31MTP_START_RPO . . . . . . . . . . . . . 10-32MTP_STOP_RPO . . . . . . . . . . . . . . 10-33MTP_SU_ERROR . . . . . . . . . . . . . . 10-34MTP_UNAVAILABLE . . . . . . . . . . . . 10-35

N

N2_EXPIRY . . . . . . . . . . . . . . . . . 11-11Network health statistics . . . . . . . . . . . . 1-3AIR_INTERFACE_BW_CS1 . . . . . . . . . 18-8AIR_INTERFACE_BW_CS2 . . . . . . . . . 18-9AIR_INTERFACE_BW_CS3 . . . . . . . . 18-10AIR_INTERFACE_BW_CS4 . . . . . . . . 18-11AIR_INTERFACE_PAGING . . . . . . . . 18-12

Network health statistics (contd.)ASSIGNMENT_SUCCESS_RATE . . . . . 18-13C_SETUP_SUCCESS_RATE. . . . . 17-6, 18-18C_SUCCESS_RATE . . . . . . . . . . . . 18-19C_VOLUME . . . . . . . . . . . . . . . 18-20CALL_SETUP_RF_ASSIGN-MENT_FAIL_RATE_LOST_MS . . . . . . 18-14



Network health statistics (contd.)CALL_SETUP_RF_ASSIGN-MENT_FAIL_RATE_RECOV-ERED_MS . . . . . . . . . . . . . . . . 18-16CALL_SETUP_RF_ASSIGNMENT_SUC-CESS_RATE . . . . . . . . . . . . . . . 18-17CELL_UPDATE . . . . . . . . . . . . . . 18-21CS1_USAGE_DL . . . . . . . . . . . . . 18-22CS1_USAGE_UL . . . . . . . . . . . . . 18-23CS2_USAGE_DL . . . . . . . . . . . . . 18-24CS2_USAGE_UL . . . . . . . . . . . . . 18-25CS3_USAGE_DL . . . . . . . . . . . . . 18-26CS3_USAGE_UL . . . . . . . . . . . . . 18-27CS4_USAGE_DL . . . . . . . . . . . . . 18-28CS4_USAGE_UL . . . . . . . . . . . . . 18-29DL_AIR_INTERFACE_BW_CS1 . . . . . 18-30DL_AIR_INTERFACE_BW_CS2 . . . . . 18-31DL_AIR_INTERFACE_BW_CS3 . . . . . 18-32DL_AIR_INTERFACE_BW_CS4 . . . . . 18-33DOWNLINK_TRAFFIC_VOLUME . . . . 18-34DROP_C_RATE . . . . . . . . . . . . . . 18-36GBL_AVAILABILITY . . . . . . . . . . . 18-38GPRS performance. . . . . . . . . . . . . . 18-2GPRS_BW_USAGE_DL. . . . . . . . . . 18-39GPRS_BW_USAGE_UL. . . . . . . . . . 18-40GPRS_DL_ACT_TS . . . . . . . . . . . . 18-41GPRS_UL_ACT_TS . . . . . . . . . . . . 18-42handover performance . . . . . . . . . . . . 18-3health check . . . . . . . . . . . . . . . . . 18-5HO_CAUSE_ADJ_CH_INTERF . . . . . . 18-43HO_CAUSE_BAND_HO . . . . . . . . . 18-44HO_CAUSE_BAND_REASSGN . . . . . . 18-45HO_CAUSE_CONGEST. . . . . . . . . . 18-46HO_CAUSE_DISTANCE . . . . . . . . . 18-47HO_CAUSE_DLINTERF . . . . . . . . . 18-48HO_CAUSE_DLLEVEL . . . . . . . . . . 18-49HO_CAUSE_DLQUAL . . . . . . . . . . 18-50HO_CAUSE_PWRBGT . . . . . . . . . . 18-51HO_CAUSE_UPINTERF . . . . . . . . . 18-52HO_CAUSE_UPLEVEL . . . . . . . . . . 18-53HO_CAUSE_UPQUAL . . . . . . . . . . 18-54HO_PER_C . . . . . . . . . . . . . . . . 18-55IN_INTER_BSS_HO_SUC. . . . . . . . . 18-56IN_INTER_CELL_HO_SUC . . . . . . . . 18-57IN_INTRA_BSS_HO_SUC . . . . . . . . 18-58INCOMING_HO_VOLUME . . . . . . . . 18-59INTERNAL_LOST . . . . . . . . . . . . 18-60INTERNAL_RECOVERED . . . . . . . . 18-61INTERNAL_SUCCESS . . . . . . . . . . 18-62INTRA_CELL_HO_FAIL_LOST_MS . . . 18-63INTRA_CELL_HO_FAIL_RECOV-ERED . . . . . . . . . . . . . . . . . . . 18-64INTRA_CELL_HO_SUCCESS_RATE . . . 18-65MAX_TCH_BUSY . . . . . . . . . . . . 18-66

Network health statistics (contd.)MEAN_TIME_BETWEEN_DROPS . . . . 18-68MEAN_TIME_BETWEEN_HOs . . . . . . 18-69MSC_PAGING . . . . . . . . . . . . . . 18-67OUT_IN-TER_BSS_HO_FAIL_LOST_MS. . . . . . 18-70OUT_INTER_BSS_HO_FAIL_RECOV-ERED . . . . . . . . . . . . . . . . . . . 18-71OUT_INTER_BSS_HO_SUC-CESS_RATE . . . . . . . . . . . . . . . 18-72OUT_IN-TER_CELL_HO_FAIL_RATE_LOST_MS . . 18-73OUT_INTER_CELL_HO_FAIL_RATE_RECOV-ERED_MS . . . . . . . . . . . . . . . . 18-74OUT_INTER_CELL_HO_SUC-CESS_RATE . . . . . . . . . . . . . . . 18-75OUT_INTER_CELL_HO_SUCCESS_RATE_RE-COVERED_MS . . . . . . . . . . . . . . 18-76OUT_IN-TRA_BSS_HO_FAIL_LOST_MS . . . . . 18-77OUT_INTRA_BSS_HO_FAIL_RECOV-ERED_MS . . . . . . . . . . . . . . . . 18-78OUT_INTRA_BSS_HO_SUC . . . . . . . 18-79OUTGOING_HO_VOLUME. . . . . . . . 18-80paging performance . . . . . . . . . . . . . 18-5PAGING_COMPRESSION_RATE . . . . . 18-81PAGING_OVERFLOW_RATE . . . . . . . 18-82PAGING_RESPONSE . . . . . . . . . . . 18-83PAGING_SUCCESS_RATE . . . . . . . . 18-84PERCENTAGE_INTER_BSS_HO . . . . . 18-85PERCENTAGE_INTRA_BSS_HO . . . . . 18-86PERCENTAGE_INTRA_CELL_HO . . . . 18-87PERCENTAGE_OF__TRAFFIC_IN_DOWN-LINK . . . . . . . . . . . . . . . . . . . 18-88radio performance reports. . . . . . . . . . . 18-5RANKING_FORMULA . . . . . . . . . . 18-89RF_ASSIGN_FAIL_RATE_LOST_MS . . . 18-90RF_ASSIGN_FAIL_RATE_RECOV-ERED . . . . . . . . . . . . . . . . . . . 18-91RF_ASSIGNMENT_SUCCESS_RATE . . . 18-92SDCCH congestion . . . . . . . . . . . . . 18-6SDCCH_ACCESSES . . . . . . . . . . . 18-93SDCCH_BLOCKING_RATE. . . . . . . . 18-94SDCCH_CONGESTION_TIME . . . . . . 18-95SDCCH_TRAFFIC_CARRIED. . . . . . . 18-96SDCCH_USAGE_ACCESS_FAILURE . . . 18-98SDCCH_USAGE_CALL_REESTAB-LISH . . . . . . . . . . . . . . . . . . . 18-99SDCCH_USAGE_EMER-GENCY_CALL . . . . . . . . . . . . . . 18-100SDCCH_USAGE_IMSI_DETACH . . . . . 18-101SDCCH_USAGE_LOCATION_UP-DATE . . . . . . . . . . . . . . . . . . . 18-102


Index

Network health statistics (contd.)SDCCH_USAGE_MS_ORIGI-NATED_CALL . . . . . . . . . . . . . . 18-103SDCCH_USAGE_MS_ORIGI-NATED_SMS . . . . . . . . . . . . . . . 18-104SDCCH_USAGE_PAGING_RE-SPONSE . . . . . . . . . . . . . . . . . 18-106SDCCH_USAGE_SMS . . . . . . . . . . 18-107SDCCH_USAGE_SMS_ORIGI-NATED_SS . . . . . . . . . . . . . . . . 18-105SPILL_OVER_FACTOR_ATTEMPTS_AT_CON-GESTION_RELIEF . . . . . . . . . . . . 18-108SPILL_OVER_FACTOR_DI-RECTED_RETRY . . . . . . . . . . . . . 18-109SPILL_OVER_FACTOR_MULTI-BAND . . . . . . . . . . . . . . . . . . 18-110TCH congestion . . . . . . . . . . . . . . . 18-6TCH_ACCESSES . . . . . . . . . . . . . 18-111TCH_CONGESTION_TIME . . . . . . . . 18-113TCH_CONGESTION_TIME_IN-NER_ZONE . . . . . . . . . . . . . . . . 18-114TCH_CONGES-TION_TIME_OUTER_ZONE . . . . . . . 18-115TCH_RF_LOSS_RATE . . . . . . 17-34, 18-116UL_AIR_INTERFACE_BW_CS1 . . . . . 18-120UL_AIR_INTERFACE_BW_CS2 . . . . . 18-121UL_AIR_INTERFACE_BW_CS3 . . . . . 18-122UL_AIR_INTERFACE_BW_CS4 . . . . . 18-123UPLINK_PDTCH_BLOCKING_RATE . . . 18-124UPLINK_TRAFFIC_VOLUME . . . . . . 18-125

network interface statisticsBSSLAP_ABORT_RCV . . . . . . . . . . . 9-4BSSLAP_ABORT_SENT . . . . . . . . . . 9-5BSSLAP_MS_POS_CMD . . . . . . . . . . 9-6BSSLAP_MS_POS_RESP . . . . . . . . . . 9-7BSSLAP_REJ . . . . . . . . . . . . . . . . 9-8BSSLAP_RESET . . . . . . . . . . . . . . 9-9BSSLAP_TA_REQ . . . . . . . . . . . . . 9-10BSSLAP_TA_RESP . . . . . . . . . . . . . 9-11BSSLAP_TOA_REQ . . . . . . . . . . . . 9-12BSSMAP_CONLESS_INFO_RCV . . . . . . 9-13BSSMAP_CONLESS_INFO_SENT . . . . . 9-14BSSMAP_PERF_LOC_ABORT_MSGS . . . 9-15BSSMAP_PERF_LOC_REQ_MSGS . . . . . 9-16BSSMAP_PERF_LOC_RESP_MSGS. . . . . 9-17BSSMAPLE_CONLESS_INFO_RCV . . . . 9-18BSSMAPLE_CONLESS_INFO_SENT . . . . 9-19BSSMAPLE_PERF_LOC_ABORT_MSGS . . 9-20BSSMAPLE_PERF_LOC_REQ_MSGS. . . . 9-21BSSMAPLE_PERF_LOC_RESP_MSGS . . . 9-22

network interface statistics (contd.)L_ROUTING_SYNTAX . . . . . . . . . . . 13-3L_ROUTING_UNKNOWN . . . . . . . . . 13-4L_SCCP_MSGS . . . . . . . . . . . . . . . 13-5L_SCCP_MSGS_RX. . . . . . . . . . . . . 13-6L_SCCP_MSGS_TX. . . . . . . . . . . . . 13-7L_SIF_SIO_RX_OPC . . . . . . . . . . . . 13-8L_SIF_SIO_TX_OPC . . . . . . . . . . . . 13-9L_SIF_SIO_TYPE . . . . . . . . . . . . . 13-10LMTP_CHANGEBACK . . . . . . . . . . . 8-6LMTP_CHANGEOVER . . . . . . . . . . . 8-7LMTP_CONGESTION_LOST_MSU . . . . . 8-4LMTP_LINK_INS . . . . . . . . . . . . . . 8-9LMTP_LINKFAIL . . . . . . . . . . . . . . 8-10LMTP_LOCAL_BUSY . . . . . . . . . . . 8-11LMTP_LOCAL_MGT . . . . . . . . . . . . 8-12LMTP_LOCAL_SL_CONGESTION . . . . . 8-8LMTP_MGT_INHIBIT . . . . . . . . . . . 8-13LMTP_MGT_UNINHIBIT . . . . . . . . . . 8-14LMTP_MSU_DISCARDED . . . . . . . . . 8-5LMTP_MSU_RX . . . . . . . . . . . . . . 8-15LMTP_MSU_TX . . . . . . . . . . . . . . 8-16LMTP_NEG_ACKS . . . . . . . . . . . . . 8-17LMTP_RE_TX . . . . . . . . . . . . . . . 8-18LMTP_REMOTE_MGT . . . . . . . . . . . 8-19LMTP_REMOTE_PROC. . . . . . . . . . . 8-20LMTP_RESTORATION . . . . . . . . . . . 8-21LMTP_SIF_SIO_RX. . . . . . . . . . . . . 8-22LMTP_SIF_SIO_TX . . . . . . . . . . . . . 8-23LMTP_SL_ACK. . . . . . . . . . . . . . . 8-24LMTP_SL_ALIGNMENT . . . . . . . . . . 8-25LMTP_SL_CONGESTION. . . . . . . . . . 8-26LMTP_SL_ERROR_RATE. . . . . . . . . . 8-27LMTP_SL_FAIL. . . . . . . . . . . . . . . 8-28LMTP_SL_FIBR . . . . . . . . . . . . . . 8-29LMTP_START_RPO. . . . . . . . . . . . . 8-30LMTP_STOP_RPO . . . . . . . . . . . . . 8-31LMTP_SU_ERROR . . . . . . . . . . . . . 8-32LMTP_UNAVAILABLE . . . . . . . . . . . 8-33

NO_PDTCH_AVAIL . . . . . . . . . . . . . 12-105NO_PDTCH_AVAIL_TIME . . . . . . . . . 12-106Normal distribution statistics . . . . . . . . . . 1-9Bins. . . . . . . . . . . . . . . . . . . . . 1-9Histogram . . . . . . . . . . . . . . . . . . 1-9Interval expiry . . . . . . . . . . . . . . . . 1-9Mean value . . . . . . . . . . . . . . . . . 1-9

NUM_EMERG_ACCESS . . . . . . . . . . . 4-78NUM_EMERG_REJECTED . . . . . . . . . . 4-79NUM_EMERG_TCH_KILL . . . . . . . . . . 4-80NUM_EMERG_TERM_SDCCH . . . . . . . . 4-81



O

OK_ACC_PROC. . . . . . . . . . . . . . 4-82, 9-2OK_ACC_PROC_SUC_RACH . . . . . . . . . 4-84OUT_HO_CAUSE_ATMPT . . . . . . . . . . 4-85OUT_HO_NC_CAUSE_ATMPT . . . . . . . . 5-10OUT_HO_NC_SUC . . . . . . . . . . . . . . 5-12OUT_INTER_BSS_EQUIP_FAIL. . . . . . . . 4-87OUT_INTER_BSS_HO . . . . . . . . . . . . 4-87OUT_INTER_BSS_HO_ATMPT . . . . . . . . 4-87OUT_INTER_BSS_HO_CLEARED . . . . . . 4-87OUT_INTER_BSS_HO_FAIL_LOST_MS. . . 18-70OUT_INTER_BSS_HO_FAIL_RECOV-ERED . . . . . . . . . . . . . . . . . . . . 18-71OUT_INTER_BSS_HO_LOSTMS . . . . . . . 4-87OUT_INTER_BSS_HO_RETURN . . . . . . . 4-87OUT_INTER_BSS_HO_SUC. . . . . . . . . . 4-87OUT_INTER_BSS_HO_SUCCESS_RATE . . 18-72OUT_INTER_BSS_REQ_TO_MSC. . . . . . . 4-87OUT_IN-TER_CELL_FAIL_RATE_LOST_MS . . . . . 18-73

OUT_INTER_CELL_HO_FAIL_RATE_RECOV-ERED_MS. . . . . . . . . . . . . . . . . . 18-74OUT_INTER_CELL_HO_SUC-CESS_RATE. . . . . . . . . . . . . . . . . 18-75OUT_INTER_CELL_HO_SUCCESS_RATE_RECOV-ERED_MS. . . . . . . . . . . . . . . . . . 18-76OUT_INTRA_BSS_EQUIP_FAIL . . . . . . . 4-89OUT_INTRA_BSS_HO . . . . . . . . . . . . 4-89OUT_INTRA_BSS_HO_ATMPT . . . . . . . . 4-89OUT_INTRA_BSS_HO_CLEARED . . . . . . 4-89OUT_INTRA_BSS_HO_FAIL_LOST_MS . . 18-77OUT_INTRA_BSS_HO_FAIL_RECOV-ERED_MS. . . . . . . . . . . . . . . . . . 18-78OUT_INTRA_BSS_HO_LOSTMS . . . . . . . 4-89OUT_INTRA_BSS_HO_PRI_BLK . . . . . . . 4-89OUT_INTRA_BSS_HO_REQ . . . . . . . . . 4-89OUT_INTRA_BSS_HO_RETURN . . . . . . . 4-89OUT_INTRA_BSS_HO_SUC . . . . . 4-89, 18-79OUTER_TO_INNER_ZONE . . . . . 4-116 to 4-117OUTGOING_HO_VOLUME . . . . . . . . . 18-80

P

PAGE_REQ_FROM_MSC . . . . . . . . . . . 4-91PAGE_REQ_FROM_MSC_FAIL . . . . . . . . 3-12PAGE_REQ_FROM_SMLC_FAIL . . . . . . 13-11PAGE_RESPONSE . . . . . . . . . . . . . . 4-82PAGES_PER_C . . . . . . . . . . . . . . . . 16-9PAGES_PER_SECOND . . . . . . . . . . . 16-10paging performance . . . . . . . . . . . . . . 18-5PAGING_COMPRESSION_RATE . . . . . . 18-81PAGING_OVERFLOW_RATE . . . . . . . . 18-82PAGING_RATE . . . . . . . . . . . . . . . 16-11PAGING_REQS_CS . . . . . . . . . . . . . . 4-92PAGING_REQS_PS . . . . . . . . . . . . . . 4-92PAGING_REQS_TOT . . . . . . . . . . . . . 4-92PAGING_REQUESTS . . . . . . . . . . . . . 4-92PAGING_RESPONSE . . . . . . . . . . . . 18-83PAGING_SUCCESS_RATE . . . . . . . . . 18-84

PATH_BALANCE . . . . . . . . . . . . . . . 6-16PCH_AGCH_Q_LENGTH . . . . . . . . . . . 4-93PCH_Q_PAGE_DISCARDPCH_Q_PAGE_DISACRD . . . . . . . . . . 4-94

PERCENTAGE_INTER_BSS_HO . . . . . . 18-85PERCENTAGE_INTRA_BSS_HO . . . . . . 18-86PERCENTAGE_INTRA_CELL_HO . . . . . 18-87PERCENTAGE_OF__TRAFFIC_IN_DOWN-LINK . . . . . . . . . . . . . . . . . . . . 18-88phantom RACHs . . . . . . . . . . . . . 4-64, 20-6raw statistics affected. . . . . . . . . . . . . 20-8

POWERBDGT. . . . . . . . . . . . . . . . . 4-85PPCH_Q_PAGE_DISCARDPPCH_Q_PAGE_DISACRD . . . . . . . . . 4-95

PRP_LOAD . . . . . . . . . . . . . . . . . 12-107

Q

Quality of Service (QoS) . . . . . . . . 12-8, 12-12 Questions and answers . . . . . . . . . . . . . 20-9

R

radio performance reports . . . . . . . . . . . . 18-5


Index

radio performance reports (contd.)CALL_SETUP_RF_ASSIGN-MENT_FAIL_RATE_LOST_MS . . . . . . 18-14CALL_SETUP_RF_ASSIGN-MENT_FAIL_RATE_RECOV-ERED_MS . . . . . . . . . . . . . . . . 18-16CALL_SETUP_RF_ASSIGNMENT_SUC-CESS_RATE . . . . . . . . . . . . . . . 18-17PERCENTAGE_INTER_BSS_HO . . . . . 18-85PERCENTAGE_INTRA_BSS_HO . . . . . 18-86PERCENTAGE_INTRA_CELL_HO . . . . 18-87RF_ASSIGNMENT_SUCCESS_RATE . . . 18-92

RANKING_FORMULA . . . . . . . . . . . 18-89Raw statistics . . . . . . . . . . . . . . . . . 1-2RBER . . . . . . . . . . . . . . . . . . . . . 6-18

RF_ASSIGN_FAIL_RATE_LOST_MS . . . . 18-90RF_ASSIGN_FAIL_RATE_RECOVERED . . 18-91RF_ASSIGNMENT_SUCCESS_RATE . . . . 18-92RF_LOSS_RATE . . . . . . . . . . . . . . 17-17RF_LOSSES_SD. . . . . . . . . . . . . . . . 4-96RF_LOSSES_TCH . . . . . . . . . . . . 4-97, 6-20RF_LOSSES_TCH_HR . . . . . . . . . . . 15-27ROC . . . . . . . . . . . . . . . . . . . . . 6-22ROUTING_SYNTAX . . . . . . . . . . . . . 3-13ROUTING_UNKNOWN . . . . . . . . . . . . 3-14RSLCongestion Control . . . . . . . . . . . . . 3-3link scenarios . . . . . . . . . . . . . . . 19-53

RSL_LCF_CONGESTION . . . . . . . . . . . 3-15

S

SABM_TX . . . . . . . . . . . . . . . . . 11-12SCCP_MSGS . . . . . . . . . . . . . . . . . 3-16SCCP_MSGS_RX . . . . . . . . . . . . . . . 3-17SCCP_MSGS_TX . . . . . . . . . . . . . . . 3-18SDCCH congestion. . . . . . . . . . . . . . . 18-6SDCCH_ACCESS_SUCCESS_RATE . . . . . 17-18SDCCH_ACCESSES. . . . . . . . . . . . . 18-93SDCCH_BLOCKING_RATE . . . . . . . . . 17-19to 17-20, 18-94SDCCH_CONGESTION . . . . . . . . . . . . 4-99SDCCH_CONGESTION_TIME . . . . . . . 18-95SDCCH_MEAN_ARRIVAL_RATE . . . . . . 17-21SDCCH_MEAN_HOLDING_TIME. . . . . . 17-22SDCCH_RF_LOSS_RATE . . . . . . . . . . 17-23SDCCH_TRAFFIC_CARRIED . . . . . 17-24, 18-96SDCCH_USAGE_ACCESS_FAILURE . . . . 18-98SDCCH_USAGE_CALL_REESTABLISH . . 18-99SDCCH_USAGE_EMERGENCY_CALL . . . 18-100SDCCH_USAGE_IMSI_DETACH . . . . . . 18-101SDCCH_USAGE_LOCATION_UPDATE . . . 18-102SDCCH_USAGE_MS_ORIGI-NATED_CALL . . . . . . . . . . . . . . . 18-103SDCCH_USAGE_MS_ORIGI-NATED_SMS . . . . . . . . . . . . . . . . 18-104SDCCH_USAGE_PAGING_RESPONSE . . . 18-106SDCCH_USAGE_SMS. . . . . . . . . . . . 18-107SDCCH_USAGE_SMS_ORIGI-NATED_SS . . . . . . . . . . . . . . . . . 18-105SECOND_ASSIGN_ATMPT . . . . . . . . . 4-100SECOND_ASSIGN_SUC . . . . . . . . . . 4-101Setting a statistic interval . . . . . . . . . . . . 2-9

Setting a threshold . . . . . . . . . . . . . . . 2-13counter statistics . . . . . . . . . . . . . . . 2-14

Setting statistic properties . . . . . . . . . . . . 2-13Setting a threshold . . . . . . . . . . . . . . 2-13

short message servicemobile originated . . . . . . . . . . . . . 19-35mobile terminated . . . . . . . . . . . . . 19-36

SIB_RX . . . . . . . . . . . . . . . . . . . 10-36SIB_TX . . . . . . . . . . . . . . . . . . . 10-37SIF_SIO_RX_OPC. . . . . . . . . . . . . . . 3-19SIF_SIO_TX_OPC . . . . . . . . . . . . . . . 3-20SIF_SIO_TYPE . . . . . . . . . . . . . . . . 3-21SL_CONGESTION . . . . . . . . . . . . . 10-38SL_STOP_CONGESTION . . . . . . . . . . 10-39SMSratio per call . . . . . . . . . . . . . . . . 16-12

SMS_INIT_ON_SDCCH . . . . . . . . . . . 4-102SMS_INIT_ON_SDCCH_HO_IN . . . . . . . 4-103SMS_INIT_ON_TCH . . . . . . . . . . . . 4-104SMS_NO_BCAST_MSG . . . . . . . . . . . 4-105SMS_TO_C_RATIO . . . . . . . . . . . . . 16-12SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGES-TION_RELIEF. . . . . . . . . . . . . . . . 18-108SPILL_OVER_FACTOR_DI-RECTED_RETRY . . . . . . . . . . . . . . 18-109SPILL_OVER_FACTOR_MULTIBAND . . . 18-110stat_interval command . . . . . . . . . . 2-9 to 2-10stat_mode command . . . . . . . . . . . . . . 2-2SUCCESS_IMMED_ASSIGN_PROC . . . . . 17-26SUCCESS_INTERNAL_HO . . . . . . . . . 17-27



T

TCH congestion . . . . . . . . . . . . . . . . 18-6TCH_ACCESSES . . . . . . . . . . . . . . 18-111TCH_ASSIGN_TO_INNER_ZONE . . . . . . 4-116to 4-117TCH_BLOCKING_RATE . . . . . . . . . . 17-28TCH_BLOCKING_RATE_INNER_Z . . . . . 17-29TCH_BLOCKING_RATE_OUTER_Z. . . . . 17-30TCH_CONG_INNER_ZONE . . . . . . . . . 4-107TCH_CONG_INNER_ZONE_HR. . . . . . . 15-28TCH_CONGESTION . . . . . . . . . . . . 4-106TCH_CONGESTION_HR . . . . . . . . . . 15-29TCH_CONGESTION_TIME . . . . . . . . . 18-113TCH_CONGESTION_TIME_IN-NER_ZONE . . . . . . . . . . . . . . . . . 18-114

TCH_CONGES-TION_TIME_OUTER_ZONE . . . . . . . . 18-115TCH_DELAY . . . . . . . . . . . . . . . . 4-108TCH_MEAN_ARRIVAL_RATE . . . . . . . 17-31TCH_MEAN_HOLDING_TIME . . . . . . . 17-32TCH_Q_LENGTH . . . . . . . . . . . . . . 4-109TCH_Q_REMOVED . . . . . . . . . . . . . 4-110TCH_RF_LOSS_RATE. . . . . . . . 17-34, 18-116TCH_TRAFFIC_CARRIED . . . . . 17-36, 18-118TCH_USAGE . . . . . . . . . . . . . . . . 4-111TCH_USAGE_EXT_RANGE. . . . . . . . . 4-113TCH_USAGE_INNER_ZONE . . . . . . . . 4-114Throughput statistics . . . . . . . . . . 12-4, 19-69TOTAL_CS . . . . . . . . . . . . . . . . . 4-115TOTAL_CS_KEY . . . . . . . . . . . . . . 17-38

U

U_BER . . . . . . . . . . . . . . . . . . . . 6-23UL_AIR_INTERFACE_BW_CS1 . . . . . . . 18-120UL_AIR_INTERFACE_BW_CS2 . . . . . . . 18-121UL_AIR_INTERFACE_BW_CS3 . . . . . . . 18-122UL_AIR_INTERFACE_BW_CS4 . . . . . . . 18-123UL_BUSY_PDTCH . . . . . . . . . . . . . 12-109UL_PDTCH_CONGESTION . . . . . . . . . 12-111UL_PDTCH_Q_LENGTH . . . . . . . . . . 12-112UL_PDTCH_SEIZURE . . . . . . . . . . . 12-113UL_RADIO_BLKS_8PSK_1_TS . . . . . . . 12-114UL_RADIO_BLKS_8PSK_2_TS . . . . . . . 12-116UL_RADIO_BLKS_GMSK_1_TS . . . . . . 12-118UL_RADIO_BLKS_GMSK_2_TS . . . . . . 12-120UL_RLC_ACK_NEW_BLKS. . . . . . . . . 12-122UL_RLC_RETX_BLKS . . . . . . . . . . . 12-124

UL_RLC_UNACK_NEW_BLKS . . . . . . . 12-126UL_TBF_TIME_8PSK_1_TS . . . . . . . . . 12-128UL_TBF_TIME_8PSK_2_TS . . . . . . . . . 12-129UL_TBF_TIME_GMSK_1_TS . . . . . . . . 12-130UL_TBF_TIME_GMSK_2_TS . . . . . . . . 12-131UNSUCCESS_INTER-NAL_HO_NOREEST . . . . . . . . . . . . 17-39UNSUCCESS_INTERNAL_HO_REEST . . . 17-40UPINTERF . . . . . . . . . . . . . . . . . . 4-85UPLEVEL . . . . . . . . . . . . . . . . . . . 4-85UPLINK_PATH_LOSS . . . . . . . . . . . . . 6-25UPLINK_PDTCH_BLOCKING_RATE . . . . 18-124UPLINK_TRAFFIC_VOLUME. . . . . . . . 18-125UPQUAL . . . . . . . . . . . . . . . . . . . 4-85

W

Weighted distribution statistics . . . . . . . . . 1-10Bins. . . . . . . . . . . . . . . . . . . . . 1-10Histogram . . . . . . . . . . . . . . . . . . 1-10Interval expiry . . . . . . . . . . . . . . . . 1-10

Weighted distribution statistics (contd.)Mean value . . . . . . . . . . . . . . . . . 1-10Wraparound to next day . . . . . . . . . . . 1-10

Z

ZONE_CHANGE_ATMPT . . . . . . . . . . 4-116 ZONE_CHANGE_SUC . . . . . . . . . . . 4-117


Documents

motorola BSS counters