68p02901w56-L-uk GSM Statistics Application

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

CA

LL

MO

DE

L S

TAT

IST

ICS

CH

AP

TE

R 11

CB

L, G

SL

, OM

L, R

SL

AN

DX

BL

STA

TIS

TIC

S

CH

AP

TE

R 17

NE

TW

OR

K H

EA

LTH

RE

PO

RT

S

CH

AP

TE

R 18

LA

DD

ER

DIA

GR

AM

SC

HA

PT

ER

19IM

PAC

TS

ON

STA

TIS

TIC

SIN

DE

XC

HA

PT

ER

16K

EY

STA

TIS

TIC

S

MAINTENANCE INFORMATIONGSM STATISTICS APPLICATION

GSM SOFTWARE RELEASE 6

GSR6

68P02901W56-L

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

6

GSR6

68P02901W56-L

14 Feb 2003

Maintenance Information: GSM Statistics Application

68P02901W56-L i

Software Release GSR6

Maintenance InformationGSM Statistics Application

E Motorola 1993 - 2003All Rights ReservedPrinted in the UK.

GSR6

14 Feb 2003ii


68P02901W56-L

Copyrights, notices and trademarks

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computerprograms stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola certain exclusive rights for copyright computer programs, including theexclusive right to copy or reproduce in any form the copyright computer program. Accordingly, anycopyright Motorola computer programs contained in the Motorola products described in this documentmay not be copied or reproduced in any manner without the express written permission of Motorola.Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or byimplication, estoppel or otherwise, any license under the copyrights, patents or patent applications ofMotorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a licenseagreement and may be used and/or disclosed only in accordance with the terms of the agreement.Software and documentation are copyright materials. Making unauthorized copies is prohibited bylaw. No part of the software or documentation may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any language or computer language, in any form or by anymeans, without prior written permission of Motorola.

AccuracyWhile reasonable efforts have been made to assure the accuracy of this document, Motorolaassumes no liability resulting from any inaccuracies or omissions in this document, or from the useof the information obtained herein. Motorola reserves the right to make changes to any productsdescribed herein to improve reliability, function, or design, and reserves the right to revise thisdocument and to make changes from time to time in content hereof with no obligation to notify anyperson of revisions or changes. Motorola does not assume any liability arising out of the applicationor use of any product or circuit described herein; neither does it convey license under its patentrights of others.

Trademarks

and MOTOROLA 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.

.

.

.

GSR6

14 Feb 2003


68P02901W56-L iii

Contents

Issue status of this manual 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General information 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reporting safety issues 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warnings and cautions 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General warnings 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General cautions 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Devices sensitive to static 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola manual set 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GMR amendment 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GMR amendment record 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1Introduction to statistics 1–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GSM Statistics Manual 1–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistics 1–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network management and planning 1–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Raw statistics 1–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key statistics 1–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network health statistics 1–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom statistics 1–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistic terms 1–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Types of raw statistics 1–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 1–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter statistics 1–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter array statistics 1–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gauge statistics 1–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duration statistics 1–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal distribution statistics 1–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted distribution statistics 1–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistic usages 1–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of service monitoring 1–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service accessibility 1–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service integrity 1–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service retainability 1–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault finding 1–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization 1–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network planning 1–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation and commissioning 1–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ladder diagrams 1–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About ladder diagrams 1–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2Statistical operations 2–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistical operations 2–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to statistical operations 2–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enabling/disabling a statistic 2–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default enabled statistics 2–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling a statistic 2–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling a statistic 2–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003iv


68P02901W56-L

Displaying enabled statistics 2–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying all enabled statistics 2–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying statistic values 2–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting the statistic interval 2–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying the statistic interval 2–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying the statistic interval start times 2–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting statistic properties 2–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a threshold 2–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter statistics 2–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting bin ranges 2–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying statistic properties 2–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 2–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a counter statistic 2–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a gauge statistic 2–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a distribution statistic 2–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a counter array statistic 2–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a duration statistic 2–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3BSS statistics 3–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BSS Statistics 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS C7 utilization 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced full rate 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS handover 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP performance and utilization 3–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EFR_REQ_FROM_MSC 3–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HO_REQ_MSC_PROTO 3–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_BSS_HO_CAUSE_SUC 3–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_REQ_FROM_MSC_FAIL 3–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSC_OVLD_MSGS_RX 3–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGE_REQ_FROM_MSC_FAIL 3–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ROUTING_SYNTAX 3–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ROUTING_UNKNOWN 3–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SCCP_MSGS 3–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SCCP_MSGS_RX 3–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SCCP_MSGS_TX 3–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIF_SIO_RX_OPC 3–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIF_SIO_TX_DPC 3–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIF_SIO_TYPE 3–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L v

Chapter 4Cell statistics 4–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Cell Statistics 4–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 4–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call clearing 4–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concentric cell 4–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection establishment 4–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry 4–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency call access 4–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended range cell 4–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General handover 4–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS handover 4–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS handover 4–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-cell handover 4–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiband 4–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH assignment 4–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage congestion 4–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DYNET failures 4–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interference bands 4–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACCESS_PER_AGCH 4–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACCESS_PER_PCH 4–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACCESS_PER_RACH 4–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_SDCCH 4–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_SDCCH_FAIL 4–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_TCH 4–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_TCH_FAIL 4–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASSIGNMENT_REDIRECTION 4–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AVAILABLE_SDCCH 4–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AVAILABLE_TCH 4–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BAD_HO_REFNUM_MS 4–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BUSY_SDCCH 4–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BUSY_TCH 4–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BUSY_TCH_CARR 4–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_SP_VERS_REQUEST_MONITOR 4–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALLS_QUEUED 4–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_REQ_CAUSE_ATMPT 4–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_REQ_MS_BLK 4–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_REQ_MS_FAIL 4–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CIPHER_MODE_FAIL 4–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CLASSMK_UPDATE_FAIL 4–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CLR_CMD_FROM_MSC 4–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CLR_REQ_TO_MSC 4–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONGEST_EXIST_HO_ATMPT 4–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONGEST_STAND_HO_ATMPT 4–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003vi


68P02901W56-L

CONN_REFUSED 4–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONN_REQ_TO_MSC 4–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DYNET_ASSIGN_FAIL 4–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DYNET_CALL_REJECTS 4–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ER_INTRA_CELL_HO_ATMPT 4–39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ER_INTRA_CELL_HO_SUC 4–40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FLOW_CONTROL_BARRED 4–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HO_FAIL_NO_RESOURCES 4–42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HO_REQ_MSC_FAIL 4–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HO_REQ_MSC_OK 4–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IDLE_TCH_INTF_BAND0 4–45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





IN_INTER_BSS_HO 4–50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IN_INTRA_BSS_HO 4–51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTERBAND_ACTIVITY 4–52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_CELL_HO 4–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INV_EST_CAUSE_ON_RACH 4–55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_CMD_TO_MS 4–56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_COMPLETE_FROM_MS 4–57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_COMPLETE_TO_MSC 4–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_FAIL_FROM_MS 4–59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_REQ_FROM_MSC 4–60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MA_CMD_TO_MS_BLKD 4–61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_ACCESS_BY_TYPE 4–62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_TCH_USAGE_BY_TYPE 4–63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_TCH_USAGE_BY_TYPE_PCS 4–64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MT_LCS_ON_SDCCH 4–65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NUM_EMERG_ACCESS 4–66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NUM_EMERG_REJECTED 4–67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NUM_EMERG_TCH_KILL 4–68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NUM_EMERG_TERM_SDCCH 4–69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OK_ACC_PROC 4–70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OK_ACC_PROC_SUC_RACH 4–72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_HO_CAUSE_ATMPT 4–73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_BSS_HO 4–75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTRA_BSS_HO 4–77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L vii

PAGE_REQ_FROM_MSC 4–79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGING_REQUESTS 4–80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCH_AGCH_Q_LENGTH 4–81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCH_Q_PAGE_DISCARD 4–82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_LOSSES_SD 4–83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_LOSSES_TCH 4–84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_CONGESTION 4–85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECOND_ASSIGN_ATMPT 4–86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECOND_ASSIGN_SUC 4–87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SMS_INIT_ON_SDCCH 4–88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SMS_INIT_ON_TCH 4–89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SMS_NO_BCAST_MSG 4–90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_CONGESTION 4–91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_CONG_INNER_ZONE 4–92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_DELAY 4–93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_Q_LENGTH 4–94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_Q_REMOVED 4–95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_USAGE 4–96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_USAGE_EXT_RANGE 4–98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_USAGE_INNER_ZONE 4–99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TOTAL_CALLS 4–100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ZONE_CHANGE_ATMPT 4–101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ZONE_CHANGE_SUC 4–102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5Neighbour statistics 5–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Neighbour Statistics 5–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 5–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour 5–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outgoing neighbour cell statistics 5–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming neighbour statistics 5–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of notation and initial situation 5–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IN_INTRA_BSS_NC_ATMPT 5–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IN_INTRA_BSS_NC_SUC 5–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_HO_NC_CAUSE_ATMPT 5–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_HO_NC_SUC 5–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6Carrier and timeslot statistics 6–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier and timeslot statistics introduction 6–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of carrier statistics 6–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_SDCCH_CARR 6–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ALLOC_TCH_CARR 6–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003viii


68P02901W56-L

BER 6–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_DL_TX_PWR_LVL 6–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_REQ_MS_FAIL 6–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAN_UL_TX_PWR_LVL 6–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FER 6–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTF_ON_IDLE 6–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PATH_BALANCE 6–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RBER 6–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_LOSSES_TCH 6–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ROC 6–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U_BER 6–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UPLINK_PATH_LOSS 6–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7GPROC and DPROC statistics 7–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPROC and DPROC statistics 7–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPU_USAGE 7–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8LMTL statistics 8–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to LMTL statistics 8–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 8–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_CONGESTION_LOST_MSU 8–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_MSU_DISCARDED 8–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_CHANGEBACK 8–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_CHANGEOVER 8–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_LOCAL_SL_CONGESTION 8–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_LINK_INS 8–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_LINKFAIL 8–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_LOCAL_BUSY 8–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_LOCAL_MGT 8–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_MGT_INHIBIT 8–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_MGT_UNINHIBIT 8–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_MSU_RX 8–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_MSU_TX 8–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_NEG_ACKS 8–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_RE_TX 8–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_REMOTE_MGT 8–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_REMOTE_PROC 8–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_RESTORATION 8–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SIF_SIO_RX 8–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L ix

LMTP_SIF_SIO_TX 8–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SL_ACK 8–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SL_ALIGNMENT 8–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_REMOTE_SL_CONGESTION 8–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SL_ERROR_RATE 8–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SL_FAIL 8–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SL_FIBR 8–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_START_RPO 8–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_STOP_RPO 8–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SU_ERROR 8–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_UNAVAILABLE 8–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SIB_RX 8–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_SIB_TX 8–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LMTP_CONGESTION 8–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9BSS statistics for Location Services support 9–1 . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS statistics for supported location services 9–3 . . . . . . . . . . . . . . . . . . . . .

Description 9–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection establishment 9–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP_PERF_LOC_REQ_MSGS 9–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP_PERF_LOC_ABORT_MSGS 9–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP_PERF_LOC_RESP_MSGS 9–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAPLE_PERF_LOC_REQ_MSGS 9–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAPLE_PERF_LOC_ABORT_MSGS 9–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAPLE_PERF_LOC_RESP_MSGS 9–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_TA_REQ 9–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_TA_RESP 9–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_TOA_REQ 9–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_REJ 9–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_RESET 9–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_ABORT_SENT 9–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_ABORT_RCV 9–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_MS_POS_CMD 9–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSLAP_MS_POS_RESP 9–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP_CONLESS_INFO_RCV 9–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAP_CONLESS_INFO_SENT 9–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAPLE_CONLESS_INFO_RCV 9–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSSMAPLE_CONLESS_INFO_SENT 9–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10MTL statistics 10–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to MTL Statistics 10–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Description 10–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003x


68P02901W56-L

BUSY_CICS 10–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONGESTION_LOST_MSU 10–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSU_DISCARDED 10–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_CHANGEBACK 10–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_CHANGEOVER 10–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_CONGESTION 10–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_LINK_INS 10–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_LINKFAIL 10–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_LOCAL_BUSY 10–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_LOCAL_MGT 10–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_MGT_INHIBIT 10–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_MGT_UNINHIBIT 10–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_MSU_RX 10–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_MSU_TX 10–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_NEG_ACKS 10–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_RE_TX 10–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_REMOTE_MGT 10–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_REMOTE_PROC 10–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_RESTORATION 10–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SIF_SIO_RX 10–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SIF_SIO_TX 10–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_ACK 10–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_ALIGNMENT 10–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_CONGESTION 10–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_ERROR_RATE 10–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_FAIL 10–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SL_FIBR 10–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_START_RPO 10–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_STOP_RPO 10–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_SU_ERROR 10–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTP_UNAVAILABLE 10–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIB_RX 10–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIB_TX 10–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SL_CONGESTION 10–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SL_STOP_CONGESTION 10–39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11CBL, GSL, OML, RSL and XBL statistics 11–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CBL GSL OML RSL and XBL statistics 11–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to CBL, GSL, OML, RSL, and XBL statistics 11–3 . . . . . . . . . . . . . . . . . . .

ATER_PREEMPT_STATUS 11–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xi

ATER_STATUS 11–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FRMR 11–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I_FRAMES_RX 11–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I_FRAMES_TX 11–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INVALID_FRAMES_RX 11–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LAPD_CONGESTION 11–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N2_EXPIRY 11–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SABM_TX 11–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12PCU statistics 12–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU Statistics 12–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 12–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of Gb interface 12–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL statistics 12–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessibility statistics 12–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput statistics 12–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic allocation statistics 12–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AIR_DL_CONTROL_BLKS 12–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AIR_DL_DATA_BLKS 12–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AIR_UL_CONTROL_BLKS 12–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AIR_UL_DATA_BLKS 12–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AVAILABLE_PDTCH 12–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CELL_FLUSH_REQS 12–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHANNEL_REQS_REC 12–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHANNEL_REQS_REJECT 12–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHANNEL_REQS_SUCCESS 12–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CODING_SCHEME_CHANGE 12–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS12_ON_32K_CHAN 12–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DL_BUSY_PDTCH 12–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DL_PDTCH_CONGESTION 12–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DL_PDTCH_Q_LENGTH 12–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DL_PDTCH_SEIZURE 12–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_DL_DATA_THRPUT 12–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_DL_DATA_THRPUT_HIST 12–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_FLOW_CTRL_SENT 12–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_LINK_INS 12–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_PAGING_REQS 12–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_UL_DATA_THRPUT 12–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_UL_DATA_THRPUT_HIST 12–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_UNAVAILABLE 12–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_32K_CHANNELS_SWITCHED 12–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003xii


68P02901W56-L

GPRS_32K_DL_NOT_AVAIL 12–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_32K_UL_NOT_AVAIL 12–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_ACCESS_PER_AGCH 12–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_CELL_RESELECT_ATTMPT 12–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_CELL_RESELECT_FAIL 12–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_ACCESS_PER_RACH 12–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_CHANNELS_SWITCHED 12–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_DYNET_FAILURES 12–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_DYNET_RES_REQS 12–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_DYNET_SWI_REQS 12–39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_MS_NEIGHBOR_STRONG 12–40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_PCH_AGCH_Q_LENGTH 12–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IDLE_PDTCH_INTF_BAND0 12–42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





IMM_ASSGN_CAUSE 12–47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_CLASS_1_10_REQ 12–49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_CLASS_11_20_REQ 12–50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS_CLASS_21_29_REQ 12–51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NO_PDTCH_AVAIL 12–52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NO_PDTCH_AVAIL_TIME 12–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRP_LOAD 12–54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UL_BUSY_PDTCH 12–56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UL_PDTCH_CONGESTION 12–57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UL_PDTCH_Q_LENGTH 12–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UL_PDTCH_SEIZURE 12–59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 13BSS-SMLC statistics 13–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BSS-based SMLC statistics 13–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 13–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS C7 utilization 13–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP performance & utilization 13–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGE_REQ_FROM_SMLC_FAIL 13–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_ROUTING_SYNTAX 13–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_ROUTING_UNKNOWN 13–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_SCCP_MSGS 13–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_SCCP_MSGS_RX 13–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_SCCP_MSGS_TX 13–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xiii

L_SIF_SIO_RX_OPC 13–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_SIF_SIO_TX_DPC 13–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

L_SIF_SIO_TYPE 13–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 14Web MMI statistics 14–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MMI Statistics 14–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 15Call model statistics 15–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to call model statistics 15–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 15–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_DURATION (T) 15–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_SETUP_BLOCKING_RATE 15–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HANDOVERS_PER_CALL (H) 15–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IMSI_DETACHES_TO_CALL (Id) 15–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_BSS_HO_TO_ALL_HO (i) 15–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LOCATION_UPDATE_FACTOR (L) 15–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LOCATION_UPDATES_TO_CALLS (I) 15–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGES_PER_CALL (PPC) 15–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGES_PER_SECOND 15–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGING_RATE (P) 15–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SMS_TO_CALL_RATIO (S) 15–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 16Key statistics 16–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Key statistics 16–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 16–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call summary 16–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel usage 16–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection establishment 16–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF loss summary 16–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL utilisation 16–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Template 16–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ATTEMPT_IMMED_ASSIGN_PROC 16–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_SETUP_SUCCESS_RATE 16–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CELL_TCH_ALLOCATIONS 16–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CELL_TCH_ASSIGNMENTS 16–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HANDOVER_FAILURE_RATE 16–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HANDOVER_SUCCESS_RATE 16–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MEAN_ARRIVAL_TIME_BETWEEN_CALLS 16–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MEAN_INTER_ARRIVAL_TIME 16–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MEAN_TCH_BUSY_TIME 16–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003xiv


68P02901W56-L

MTL_UTILISATION_RX 16–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTL_UTILISATION_TX 16–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_LOSS_RATE 16–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_BLOCKING_RATE 16–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_MEAN_ARRIVAL_RATE 16–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_MEAN_HOLDING_TIME 16–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_RF_LOSS_RATE 16–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_TRAFFIC_CARRIED 16–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SUCCESS_IMMED_ASSIGN_PROC 16–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SUCCESS_INTERNAL_HO 16–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_BLOCKING_RATE 16–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_MEAN_ARRIVAL_RATE 16–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_MEAN_HOLDING_TIME 16–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_RF_LOSS_RATE 16–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_TRAFFIC_CARRIED 16–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TOTAL_CALLS_KEY 16–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UNSUCCESS_INTERNAL_HO_NOREEST 16–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UNSUCCESS_INTERNAL_HO_REEST 16–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 17Network health reports 17–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network health statistics 17–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 17–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS performance 17–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover performance 17–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health check 17–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging performance 17–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio performance 17–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH congestion 17–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH congestion 17–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AIR_INTERFACE_BW_CS1 17–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




AIR_INTERFACE_PAGING 17–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASSIGNMENT_SUCCESS_RATE 17–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_SETUP_SUCCESS_RATE 17–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_SUCCESS_RATE 17–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CALL_VOLUME 17–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CELL_UPDATE 17–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS1_USAGE_DL 17–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS1_USAGE_UL 17–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xv

CS2_USAGE_DL 17–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS2_USAGE_UL 17–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS3_USAGE_DL 17–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS3_USAGE_UL 17–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS4_USAGE_DL 17–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CS4_USAGE_UL 17–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DL_AIR_INTERFACE_BW_CS1 17–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




DOWNLINK_TRAFFIC_VOLUME 17–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DROP_CALL_RATE 17–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL_AVAILABILITY 17–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_BW_USAGE_DL 17–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_BW_USAGE_UL 17–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_DL_ACT_TS 17–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_UL_ACT_TS 17–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_DL_BANDWIDTH_EFFICIENCY 17–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS_UL_BANDWIDTH_EFFICIENCY 17–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HO_PER_CALL 17–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INCOMING_HO_VOLUME 17–39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTERNAL_LOST 17–40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTERNAL_RECOVERED 17–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTERNAL_SUCCESS 17–42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_CELL_HO_FAIL_LOST_MS 17–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_CELL_HO_FAIL_RECOVERED 17–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INTRA_CELL_HO_SUCCESS_RATE 17–45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MAX_TCH_BUSY 17–46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MEAN_TIME_BETWEEN_HOs 17–47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSC_PAGING 17–48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_BSS_HO_FAIL_LOST_MS 17–49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_BSS_HO_FAIL_RECOVERED 17–50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_BSS_HO_SUCCESS_RATE 17–51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_CELL_HO_FAIL_LOST_MS 17–52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_CELL_HO_FAIL_RECOVERED 17–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUT_INTER_CELL_HO_SUCCESS_RATE 17–54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OUTGOING_HO_VOLUME 17–55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGING_COMPRESSION_RATE 17–56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGING_OVERFLOW_RATE 17–57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003xvi


68P02901W56-L

PAGING_RESPONSE 17–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAGING_SUCCESS_RATE 17–59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK 17–60 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RANKING_FORMULA 17–61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_ASSIGN_FAIL_RATE_LOST_MS 17–62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_ASSIGN_FAIL_RATE_RECOVERED 17–63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF_ASSIGNMENT_SUCCESS_RATE 17–64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_ACCESSES 17–65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_BLOCKING_RATE 17–66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_CONGESTION_TIME 17–67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH_TRAFFIC_CARRIED 17–68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_ACCESSES 17–69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_CONGESTION_TIME 17–70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_RF_LOSS_RATE 17–71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH_TRAFFIC_CARRIED 17–72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UL_AIR_INTERFACE_BW_CS1 17–73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




UPLINK_PDTCH_BLOCKING_RATE 17–77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UPLINK_TRAFFIC_VOLUME 17–78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 18Ladder diagrams 18–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to ladder diagrams 18–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of ladder diagrams 18–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Phone call model 18–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS functions 18–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC functions 18–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC functions 18–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover procedure 18–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call procedure milestones 18–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call procedure 18–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call setup and handover 18–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 18–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Matrix 18–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connection establishment 18–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful mobile originated 18–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure 18–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Immediate assignment blocked 18–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Immediate assignment failure 18–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful mobile terminated call 18–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xvii

Assignment to TCH 18–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment successful 18–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Immediate assignment failure 18–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH assignment blocked 18–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail recovered 18–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intra-cell handover 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover blocked 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail recovered 18–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail lost 18–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inter-BSS handover 18–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover blocked 18–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail recovered 18–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail lost 18–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail lost (mobile) 18–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard directed retry (external) 18–23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intra-BSS handover 18–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover- blocked 18–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail-recovered 18–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fail-lost 18–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard directed retry (internal) 18–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call clearing 18–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cipher mode fail 18–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF loss on an SDCCH 18–28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF loss on a TCH 18–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Queueing timeout 18–29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Short message service 18–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile originated 18–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile terminated 18–30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Congestion Relief 18–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS congestion relief 18–31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Directed retry 18–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS directed retry 18–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Flow control 18–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description 18–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Intra-BSS interband activity 18–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover unsuccessful (fail recovered) 18–35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover unsuccessful (fail recovered due to invalid frequency supported) 18–36 . . .

Inter-BSS interband activity 18–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover unsuccessful (fail recovered) 18–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover unsuccessful fail recovered due to invalid frequency supported 18–39 . . . . .

GSR6

14 Feb 2003xviii


68P02901W56-L

Interband assignment 18–40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interband activity invalid frequency at assignment 18–40 . . . . . . . . . . . . . . . . . . . . . . . . .

Band Reassignment 18–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover successful 18–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover unsuccessful (fail recovered) 18–42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RSL link scenarios 18–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 18–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSL link scenarios 18–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTL link scenarios 18–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to MTL link scenarios 18–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL link (operator initiated outage) 18–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL link (transition scenarios Part II) 18–45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL link (transition scenarios Part III) 18–46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL link (transition scenarios Part IV) 18–47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GBL statistics 18–48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GBL statistics 18–48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessibility statistics 18–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to accessibility statistics 18–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Throughput statistics 18–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to throughput statistics 18–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 19Impacts on statistics 19–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to EGSM, approximate equality, and phantom RACHs 19–3 . . . . . . . . . . . . . . . . Introduction 19–3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of EGSM, approximate equality, and phantom RACHs 19–3 . . . . . . . . . . .

Extended GSM (EGSM) 19–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of EGSM 19–4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Factors impacting statistics 19–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Approximate equality 19–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of Approximate equality 19–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Phantom RACHs 19–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of Phantom RACHs 19–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagram of Phantom RACHs procedure 19–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process of Phantom RACHs occurrences 19–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Raw statistics affected 19–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Questions and answers 19–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment failure 19–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counters and SDCCH reconfiguration 19–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic SDCCH configuration 19–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Established call loss 19–12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location update reject 19–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phantom RACHs 19–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index I–1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xix

List of Figures

Figure 1-1 Histogram of a normal distribution statistic 1–9 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-2 Histogram of a weighted distribution statistic 1–11 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-3 Diagram of immediate assignment failure 1–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-1 Diagram of immediate assignment failure 18–3 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-2 Handover procedure 18–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-3 Connection establishment successful 18–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-4 Connection establishment failure 18–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-5 Immediate assignment blocked 18–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-6 Immediate assignment failure 18–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-7 Connection establishment (mobile terminated call) successful 18–12 . . . . . . . . .

Figure 18-8 TCH assignment successful 18–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-9 Immediate assignment failure 18–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-10 TCH assignment blocked 18–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-11 TCH assignment fail-recovered to SDCCH 18–15 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-12 Handover (intra-cell) successful 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-13 Handover (intra-cell) blocked 18–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-14 Handover (intra-cell) fail-recovered to source channel 18–17 . . . . . . . . . . . . . . .

Figure 18-15 Handover (intra-cell) fail-lost 18–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-16 Handover (inter-BSS) successful 18–18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-17 Handover (inter-BSS) blocked 18–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-18 Handover (inter-BSS) fail-recovered 18–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-19 Handover (inter-BSS) fail-lost 18–21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-20 Inter-BSS handover failure with lost mobile 18–22 . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-21 Inter-BSS handover directed retry external 18–23 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-22 Handover (intra-BSS) successful 18–24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-23 Handover (intra-BSS) blocked 18–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-24 Handover (intra-BSS) fail-recovered 18–25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-25 Handover (intra-BSS) fail-lost 18–26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-26 Intra-BSS handover standard directed retry 18–27 . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-27 BSS initiated call clearing–cipher mode fail 18–28 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-28 BSS initiated call clearing (RF loss on an SDCCH) 18–28 . . . . . . . . . . . . . . . . . .

Figure 18-29 BSS initiated call clearing (RF loss on a TCH) 18–29 . . . . . . . . . . . . . . . . . . . . . .

Figure 18-30 BSS initiated call clearing (queueing timeout) 18–29 . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-31 MS originated short message service (point-to-point) 18–30 . . . . . . . . . . . . . . . .

Figure 18-32 MS terminated short message service (point-to-point) 18–30 . . . . . . . . . . . . . . .

Figure 18-33 Intra-BSS congestion relief handover procedure 18–31 . . . . . . . . . . . . . . . . . . . .

Figure 18-34 Intra-BSS directed retry procedure 18–32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-35 Access procedure 18–33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003xx


68P02901W56-L

Figure 18-36 Successful intra–BSS handover 18–34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-37 Unsuccessful interband handover with fail–recovered source cell 18–35 . . . . .

Figure 18-38 Unsuccessful interband handover 18–36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-39 Successful inter-BSS handover 18–37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-40 Inter-BSS handover unsuccessful with fail–recovered source cell 18–38 . . . . .

Figure 18-41 Inter-BSS handover unsuccessful due to invalid frequency supported 18–39 . .

Figure 18-42 Invalid frequency at assignment 18–40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-43 Intra-BSS handover successful 18–41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-44 Unsuccessful band reassign 18–42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-45 RSL link scenarios 18–43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-46 MTL link scenario (Part I) 18–44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-47 MTL link transition scenarios (Part II) 18–45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-48 MTL link transition scenarios (Part III) 18–46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-49 MTL link transition scenarios (Part IV) 18–47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-50 GBL_DL_DATA_THRPUT 18–48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-51 GBL_FLOW_CTRL_SENT 18–49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-52 CELL_FLUSH_REQS 18–50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-53 GBL_PAGING_REQS 18–51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-54 GBL_UL_DATA_THRPUT 18–52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-55 Accessibility CHANNEL_REQ_REJ 18–53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-56 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH 18–54 . . . .

Figure 18-57 Accessibility and GBL statistics 18–55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-58 MS CLASS statistics 18–56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-59 CHANNELS_SWITCHED 18–57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-60 Uplink data transfer 18–58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18-61 Downlink data transfer 18–59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 19-1 Approximate equality procedure 19–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 19-2 Phantom RACHs illustration 19–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003


68P02901W56-L xxi

List of Tables

Table 2-1 Counter statistics 2–14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-1 Default bin ranges for BUSY_SDCCH 4–19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-2 Default bin ranges for BUSY_TCH 4–20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-1 Neighbour cell statistics pegged 5–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-1 FER Quality number conversion 6–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-2 Default bin ranges for INTF_ON_IDLE 6–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-3 Signal level 6–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-4 RBER Quality number conversion 6–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-5 Bin ranges for ROC 6–17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 10-1 BUSY CICS 10–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-1 AIR_DL_DATA_BLKS counters 12–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-2 AIR_UL_DATA_BLKS counters 12–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-3 GBL_DL_DATA_THRPUT_HIST bins 12–22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-4 GBL_UL_DATA_THRPUT_HIST bins 12–27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-5 GPRS_DYNET_RES_REQS bins 12–38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-6 GPRS_DYNET_SWI_REQS bins 12–39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-7 IMM_ASSGN_CAUSE bins 12–47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-8 MS_CLASS_1_10_REQ bins 12–49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-9 MS_CLASS_11_20_REQ bins 12–50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-10 MS_CLASS_21_29_REQ bins 12–51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-11 Mapping between timeslots pending service and PRP load 12–54 . . . . . . . . . . . .

Table 12-12 PRP load range 12–54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-13 UL_BUSY_PDTCH bins 12–56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 14-1 Location of MMI PCU real-time stats descriptions 14–3 . . . . . . . . . . . . . . . . . . . . .

Table 14-2 Location of MMI BSC/BTS PCU real-time stats descriptions 14–3 . . . . . . . . . . . .

Table 16-1 Key statistic descriptions. 16–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 18-1 Call setup and handover matrix. 18–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 19-1 MS access to a traffic channel 19–5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 19-2 Impact due to increased handovers 19–6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 19-3 Impact due to congestion 19–7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6

14 Feb 2003xxii


68P02901W56-L

GSR6 Issue status of this manual

14 Feb 2003


68P02901W56-L 1

Issue status of this manual

Introduction

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 manual issue:

Manualissue

Date ofissue

Remarks

O 3 Oct 94 Original issue – Software release 1.2.2.x

A 30 Dec 94 Issue A – Software release 1.2.3.x

B 1 Sep 95 Issue B – Software release 1.3.0.x

C 31 May 96 Issue C – Software release 1.4.0.x

D 28 Mar 97 Issue D – Software release 1.4.1.x

E 29 Aug 97 Issue E – GSM Software Release 2

F 27 Apr 98 Issue F – GSM Software Release 3

G 12 Mar 99 Issue G – GSM Software Release 4

H 14 Jul 00 Issue H – GSM Software Release 1.6.1.3

J 31 Jul 01 Issue J – GSM Software Release 5

K 31 May 02 Issue K – GSM Software Release 5.1

L 14 Feb 03 Issue L – GSM Software Release 6

GSR6Issue status of this manual

14 Feb 20032


68P02901W56-L

Resolution of Service Requests

The following Service Requests are now resolved in this manual:

ServiceRequest

GMRNumber

Remarks

SR1006967 N/A Path balance modified.

SR1007637 N/A Congestion relief ladder diag amended.

SR1009375 N/A Ref to stats cols added.

SR1011461 N/A MS_ACCESS_BY_TYPE pegging amended.

SR1016595 N/A MS changed to BTS.

SR1017213 N/A TCH_Q_REMOVED statistic added.

SR1018442 N/A Path balance units changed to db.

SR1019869 N/A Units corrected in Chapter12.

SR1021506 N/A CHANNEL_REQS_REJ modified.

SR1025262 N/A Nomenclature has been addressed in Chapter12.

SR1032732 N/A DYN_POW_INCR_XX_Q, DYN_POW_INCR_XX_L,DYN_POW_RED_XX removed from Chapter 4.

SR1034257 N/A TOTAL_AIR_DL/UL_AVAILABLE_BW stats modified.

SR1034536 N/A GPRS_CHANNELS_SWITCHED description has beenmodified in Chapter 12.

SR1034875 N/A CONGEST_ASSIGN_HO_SUC removed fromformulae. ASSIGNMENT_REDIRECTION included.

SR1037679 N/A ASSIGNMENT_SUCCESS_RATE description includedin Chapter 17.

SR1037681 N/A GBL_DL_DATA_THRPUT,GBL_DL_DATA_THRPUT_HIST,GBL_UL_DATA_THRPUT,GBL_UL_DATA_THRPUT_HIST descriptions modifiedin chapter 12.

SR1037304 N/A Chapter 4, INTRA CELL, INTRA/INTER BSS peggingincluded.

SR1049283 N/A GPRS_CHANNELS_SWITCHED description has beenmodified in Chapter 12.

SR1053116 N/A GPRS_32K_CHANNELS_SWITCHED,GPRS_32K_DL_NOT_AVAIL andGPRS_32K_UL_NOT_AVAIL descriptions have beenmodified in Chapter 12.

SR1053368 N/A Quality of Service explanation included in Chapters 12and 17.

SR1056850 N/A GPRS_ACCESS_PER_RACH description has beenmodified in Chapter 12.

GSR6 General information

14 Feb 2003


68P02901W56-L 3

General information

Important notice

If this manual was obtained when attending a Motorola training course, it will not beupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then corrections will be supplied automatically by Motorola in the form ofGeneral Manual Revisions (GMRs).

Purpose

Motorola cellular communications manuals are intended to instruct and assist personnelin the operation, installation and maintenance of the Motorola cellular infrastructureequipment and ancillary devices. It is recommended that all personnel engaged in suchactivities be properly trained by Motorola.

WARNING Failure to comply with Motorola’s operation, installation andmaintenance instructions may, in exceptional circumstances,lead to serious injury or death.

These manuals are not intended to replace the system and equipment training offered byMotorola, although they can be used to supplement and enhance the knowledge gainedthrough such training.

About this manual

The manual provides context information and detailed descriptions of the GSR6 raw, key,and network health statistics sets supported by Motorola GSM cellular equipment.

Detailed information on previous GSR statistical information, for example GSR5 andGSR5.1, can be obtained from the appropriate GSM Statistics Application manual.

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

GSR6General information

14 Feb 20034


68P02901W56-L

Feature referencesMost of the manuals in the set, of which this manual is part, are revised to accommodatefeatures released at Motorola General System Releases (GSRn) or GPRS Support Node(GSNn) releases. In these manuals, new and amended features are tagged to help usersto assess the impact on installed networks. The tags are the appropriate MotorolaRoadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP)numbers. The tags include index references which are listed in the manual Index. TheIndex includes the entry feature which is followed by a list of the RDB or RDP numbersfor the released features, with page references and hot links in electronic copy.

The tags have the format: {nnnn} or {nnnnn}

Where: . is: .

. {nnnn} . the RDB number

. {nnnnn} . the RDP number

The tags are positioned in text as follows:

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:

S Full sections under a main heading

S Full paragraphs under subheadings

Immediately after the headings as follows:

S Main heading

S Subheading

New or amended complete Figures andTables

After the Figure or Table number andbefore the title text.

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

General command syntax, operator inputor displays (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 inthis software release, refer to the manual System Information: Overview(68P02901W01), or to the manual System Information: GPRS Overview(68P02903W01).

Data encryptionIn order to avoid electronic eavesdropping, data passing between certain elements in theGSM and GPRS network is encrypted. In order to comply with the export and importrequirements of particular countries, this encryption occurs at different levels asindividually standardised, or may not be present at all in some parts of the network inwhich it is normally implemented. The manual set, of which this manual is a part, coversencryption as if fully implemented. Because the rules differ in individual countries,limitations on the encryption included in the particular software being delivered, arecovered in the Release Notes that accompany the individual software release.

Cross referencesThroughout this manual, cross references are made to the chapter numbers and sectionnames. The section name cross references are printed bold 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.

GSR6 General information

14 Feb 2003


68P02901W56-L 5

Text conventions

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

Input

Characters typed in at the keyboard are shown like this.

Output

Messages, prompts, file listings, directories, utilities, andenvironmental variables that appear on the screen are shown likethis.

Special key sequences

Special key sequences are represented as follows:

CTRL–c Press the Control and c keys at the same time.

ALT–f Press the Alt and f keys at the same time.

| Press the pipe symbol key.

CR or RETURN Press the Return key.

GSR6Reporting safety issues

14 Feb 20036


68P02901W56-L

Reporting safety issues

Introduction

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

Procedure

Whenever a safety issue arises:

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 68437733 (telephone) and follow up with awritten report by fax, Swindon +44 (0)1793 430987 or China +86 1068423633 (fax).

4. Collect evidence from the equipment under the guidance of the Customer NetworkResolution Centre.

GSR6 Warnings and cautions

14 Feb 2003


68P02901W56-L 7

Warnings and cautions

Introduction

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

Warnings

Definition of Warning

A warning is used to alert the reader to possible hazards that could cause loss of life,physical injury, or ill health. This includes hazards introduced during maintenance, forexample, the use of adhesives and solvents, as well as those inherent in the equipment.

Example and format

WARNING Do not look directly into fibre optic cables or data in/outconnectors. Laser radiation can come from either the data in/outconnectors or unterminated fibre optic cables connected to datain/out connectors.

Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these warnings,or with specific warnings elsewhere in the Motorola manuals, or on the equipmentitself, violates safety standards of design, manufacture and intended use of theequipment. Motorola assumes no liability for the customer’s failure to complywith these requirements.

Cautions

Definition of Caution

A caution means that there is a possibility of damage to systems, software or individualitems of equipment within a system. However, this presents no danger to personnel.

Example and format

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

GSR6General warnings

14 Feb 20038


68P02901W56-L

General warnings

Introduction

Observe the following specific warnings during all phases of operation, installation andmaintenance of the equipment described in the Motorola manuals:

S Potentially hazardous voltage

S Electric shock

S RF radiation

S Laser radiation

S Heavy equipment

S Parts substitution

S Battery supplies

S Lithium batteries

Failure to comply with these warnings, or with specific warnings elsewhere in theMotorola manuals, violates safety standards of design, manufacture and intended use ofthe equipment. Motorola assumes no liability for the customer’s failure to comply withthese requirements.

Warning labels

Warnings particularly applicable to the equipment are positioned on the equipment.Personnel working with or operating Motorola equipment must comply with any warninglabels fitted to the equipment. Warning labels must not be removed, painted over orobscured in any way.

GSR6 General warnings

14 Feb 2003


68P02901W56-L 9

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 must any other warnings given in text, in the illustrations and on the equipment.

Potentially hazardous voltage

WARNING This equipment operates from a hazardous voltage of 230 Vac single phase or 415 V ac three phase supply. To achieveisolation of the equipment from the ac supply, the ac inputisolator must be set to off and locked.

When working with electrical equipment, reference must be made to the Electricity atWork Regulations 1989 (UK), or to the relevant electricity at work legislation for thecountry in which the equipment is used.

NOTE Motorola GSM equipment does not utilise high voltages.

Electric shock

WARNING Do not touch the victim with your bare hands until theelectric circuit is broken.Switch off. If this is not possible, protect yourself with dryinsulating material and pull or push the victim clear of theconductor.ALWAYS send for trained first aid or medical assistanceIMMEDIATELY.

In cases of low voltage electric shock (including public supply voltages), serious injuriesand even death, may result. Direct electrical contact can stun a casualty causingbreathing, and even the heart, to stop. It can also cause skin burns at the points of entryand exit of the current.

In the event of an electric shock it may be necessary to carry out artificial respiration.ALWAYS send for trained first aid or medical assistance IMMEDIATELY.

If the casualty is also suffering from burns, flood the affected area with cold water to cool,until trained first aid or medical assistance arrives.

RF radiation

WARNING High RF potentials and electromagnetic fields are present inthis equipment when in operation. Ensure that alltransmitters are switched off when any antenna connectionshave to be changed. Do not key transmitters connected tounterminated cavities or feeders.

Relevant standards (USA and EC), to which regard should be paid when working with RFequipment are:

S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

GSR6General warnings

14 Feb 200310


68P02901W56-L

Laser radiation

WARNING Do not look directly into fibre optic cables or optical datain/out connectors. Laser radiation can come from either thedata in/out connectors or unterminated fibre optic cablesconnected to data in/out connectors.

Lifting equipment

WARNING When dismantling heavy assemblies, or removing orreplacing equipment, a competent responsible person mustensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations.

When dismantling heavy assemblies, or removing or replacing equipment, the competentresponsible person must ensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations. When equipments have to bemanhandled, reference must be made to the Manual Handling of Loads Regulations1992 (UK) or to the relevant manual handling of loads legislation for the country in whichthe equipment is used.

Parts substitution

WARNING Do not install substitute parts or perform any unauthorizedmodification of equipment, because of the danger ofintroducing additional hazards. Contact Motorola if in doubtto ensure that safety features are maintained.

Battery supplies

WARNING Do not wear earth straps when working with standby batterysupplies.

Lithium batteries

WARNING Lithium batteries, if subjected to mistreatment, may burstand ignite. Defective lithium batteries must not be removedor replaced. Any boards containing defective lithiumbatteries must be returned to Motorola for repair.

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

GSR6 General cautions

14 Feb 2003


68P02901W56-L 11

General cautions

Introduction

Observe the following cautions during operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these cautions orwith specific cautions elsewhere in the Motorola manuals may result in damage to theequipment. Motorola assumes no liability for the customer’s failure to comply with theserequirements.

Caution labels

Personnel working with or operating Motorola equipment must comply with any cautionlabels fitted to the equipment. Caution labels must not be removed, painted over orobscured in any way.

Specific cautions

Cautions particularly applicable to the equipment are positioned within the text of thismanual. These must be observed by all personnel at all times when working with theequipment, as must any other cautions given in text, on the illustrations and on theequipment.

Fibre optics

CAUTION Fibre optic cables must not be bent in a radius of less than30 mm.

Static discharge

CAUTION Motorola equipment contains CMOS devices. These metaloxide semiconductor (MOS) devices are susceptible todamage from electrostatic charge. See the section Devicessensitve to static in the preface of this manual for furtherinformation.

GSR6Devices sensitive to static

14 Feb 200312


68P02901W56-L

Devices sensitive to static

Introduction

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 appliedto the leads of the device could cause irreparable damage.

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

MOS devices are normally despatched from the manufacturers with the leads shortedtogether, for example, by metal foil eyelets, wire strapping, or by inserting the leads intoconductive plastic foam. Provided the leads are shorted it is safe to handle the device.

Special handling techniques

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

S Always wear an earth strap which must be connected to the electrostatic point(ESP) on the equipment.

S Leave the short circuit on the leads until the last moment. It may be necessary toreplace the conductive foam by a piece of wire to enable the device to be fitted.

S Do not wear outer clothing made of nylon or similar man made material. A cottonoverall is preferable.

S If possible work on an earthed metal surface or anti-static mat. Wipe insulatedplastic work surfaces with an anti-static cloth before starting the operation.

S All metal tools should be used and when not in use they should be placed on anearthed surface.

S Take care when removing components connected to electrostatic sensitivedevices. These components may be providing protection to the device.

When mounted onto printed circuit boards (PCBs), MOS devices are normally lesssusceptible to electrostatic damage. However PCBs should be handled with care,preferably by their edges and not by their tracks and pins, they should be transferreddirectly from their packing to the equipment (or the other way around) and never leftexposed on the workbench.

GSR6 Motorola manual set

14 Feb 2003


68P02901W56-L 13

Motorola manual set

Introduction

The following manuals provide the information needed to operate, install and maintain theMotorola equipment. CD-ROMs are available, with full navigation, for GSM, and GPRSmanual sets.Each CD-ROM includes all manuals related to a specified main GSM or GPRS softwarerelease, together with current versions of appropriate hardware manuals. A snapshotcopy of online documentation is also included, though it will not be updated in line withsubsequent point releases.The CD-ROM does not include Release Notes or documentation supporting specialistproducts such as MARS or COP.

Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals arerelease dependent:

Identification/Order number Name

68P02901W01 System Information: Overview68P02901W14 * Operating Information: GSM System Operation68P02901W19 Operating Information: OMC-R System Administration68P02901W34** Technical Description: OMC-R Database Schema68P02901W36 Technical Description: BSS Implementation68P02901W23 Technical Description: BSS Command Reference68P02901W17 Installation & Configuration: GSM System Configuration68P02901W43 Installation & Configuration: BSS Optimization68P02901W47 Installation & Configuration: OMC-R Clean Install68P02901W26 Maintenance Information: Alarm Handling at the OMC-R68P02901W58 Maintenance Information: BSS Timers68P02901W57 Maintenance Information: Device State Transitions68P02901W51 Maintenance Information: BSS Field Troubleshooting68P02901W56 Maintenance Information: GSM Statistics Application68P02901W72 Software Release Notes: BSS/RXCDR68P02901W74 Software Release Notes: OMC-R System

* Not on paper - In the OMC-R Online Help as Network Operations. A snapshot of online help is available on CD-ROM.

** Not on paper - On CD-ROM only.

GSR6Motorola manual set

14 Feb 200314


68P02901W56-L

Related GSM manuals

The following are related Motorola GSM manuals:


68P02900W21 System Information: BSS Equipment Planning68P02900W22 System Information: DataGen68P02900W76 Software Release Notes: DataGen68P02900W25 System Information: GSM Advance Operational Impact68P02900W36 System Information: Network Health Analyst68P02900W77 Software Release Notes: Network Health Analyst68P02900W90 System Information: Cell Optimization (COP)68P02900W94 System Information: Motorola Analysis and Reporting System

(MARS)68P02900W69 Software Release Notes: Cell Optimization (COP)68P02900W68 Software Release Notes: Motorola Analysis and Reporting System

(MARS)68P02901W10 Operating Information: OMC-R System Administration (OSI)68P02901W39 Installation & Configuration: OSI Clean Install68P02901W70 Software Release Notes: OMC-R OSI System

Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals arerelease dependent:


68P02903W01 System Information: GPRS Overview68P02903W03 Operating Information: OMC-G System Administration68P02903W37 Operating Information: GSN System Administration68P02903W46 Technical Description: OMC-G Database Schema68P02903W18 * Technical Description: GSN Command Reference68P02903W47 Installation & Configuration: GSN Clean Install68P02903W04 Installation & Configuration: OMC-G Clean Install68P02903W19 * Maintenance Information: Alarm Handling at the OMC-G68P02903W20 Maintenance Information: GSN Statistics Application68P02903W76 Software Release Notes: GSN System68P02903W70 Software Release Notes: OMC-G System

* Not on paper - In the OMC-G Online Help as Alarm Handling and GSN Commands/Parameters. A snapshot of online help is

available on CD-ROM.

GSR6 Motorola manual set

14 Feb 2003


68P02901W56-L 15

Related GPRS manualsThe following are related Motorola GPRS manuals:


68P02903W02 System Information: GPRS Equipment Planning68P02903W38 System Information: GSN Advance Operational Impact

BSS service manualsThe following are the Motorola Base Station Subsystem service manuals, these manualsare not release dependent. The internal organization and makeup of service manual setsmay vary, they may consist of from one to four separate manuals, but they can all beordered using the overall catalogue number shown below:


68P02901W37 Service Manual: BTS68P02901W38 Service Manual: BSC/RXCDR68P02901W75 Service Manual: M-Cell268P02901W85 Service Manual: M-Cell668P02901W95 Service Manual: M-Cellcity and M-Cellcity+68P02901W65 Service Manual: M-Cellaccess68P02901W90 Service Manual: M-Cellmicro68P02902W36 Service Manual: Horizonmicro68P02902W15 Service Manual: Horizoncompact68P02902W06 Service Manual: Horizonmacro Indoor68P02902W12 Service Manual: Horizonmacro Outdoor68P02902W61 Service Manual: Horizonmicro2 Horizoncompact268P02902W66 Service Manual: Horizonmacro 12 Carrier Outdoor

GPRS service manualsThe following are the Motorola GPRS service manuals, these manuals include thePacket Control Unit (PCU) service manual which becomes part of the BSS for GPRS:


68P02903W05 Service Manual:GPRS Support Nodes (GSN)68P02903W10 Service Manual: Packet Control Unit (PCU)

Order numberThe Motorola 68P order (catalogue) number is used to order manuals.

Ordering manualsAll orders for Motorola manuals must be placed with your Motorola Local Office orRepresentative. Manuals are ordered using the order (catalogue) number.

Manuals are available on the following media:

Printed hard copy

Electronic:

S On the Motorola service web.

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

GSR6GMR amendment

14 Feb 200316


68P02901W56-L

GMR amendment

Introduction to GMRs

Changes to a manual that occur after the printing date are incorporated into the manualusing General Manual Revisions (GMRs). GMRs are issued to correct Motorola manualsas and when required. A GMR has the same identity as the target manual. Each GMR isidentified by a number in a sequence that starts at 01 for each manual at each issue.

GMR availability

GMRs are published as follows:

S Printed hard copy - Complete replacement content or loose leaf pages withamendment list.

– Remove and replace pages in this manual, as detailed on the GMRinstruction sheet.

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

S CD-ROM - Updated periodically as required.

GSR6 GMR amendment record

14 Feb 2003


68P02901W56-L 17

GMR amendment record

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 itin a suitable place in this manual for future reference.

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 . .

21 . .

22 . .

23 . .

24 . .

25 . .

GSR6GMR amendment record

14 Feb 200318


68P02901W56-L

14 Feb 2003


68P02901W56-L 1–1

Chapter 1

Introduction to statistics

GSR6

14 Feb 20031–2


68P02901W56-L

GSR6 Introduction to GSM Statistics Manual

14 Feb 2003


68P02901W56-L 1–3

Introduction to GSM Statistics Manual

Statistics

This manual describes the statistical measurements generated by the BSS in responseto monitored network and system events. The statistics include statistical measurementsdefined in the GSM Technical Specification 12.04, plus additional Motorola-definedstatistics.

Network management and planning

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

S Quality of service monitoring.

– Service accessibility.

– Service integrity.

– Service retainability.

S Fault finding.

S Optimization.

S Network planning.

S Installation and commissioning.

Raw statistics

The BSS generates raw statistics for reporting individual network performance. TheOMC-R processes raw statistics to create key, network health and custom statistics.These statistics include call processing, interface, and processor utilizationmeasurements.

Call statistics

Call processing functions and features generate statistics that show how the system isperforming.

Interface statistics

Terrestrial interface activities generate interface statistics that show the activity on andcondition of the interface links. The interface links are the physical connections betweenthe MS, BSS, and MSC network elements.

Processor utilization statistics

Processor utilization statistics show the percentage of GPROC utilization.

GSR6Introduction to GSM Statistics Manual

14 Feb 20031–4


68P02901W56-L

Key statistics

Key statistics are generated at the OMC-R by processing raw statistics generated by theBSS, using predefined algorithms. These statistics are designed to give an overallindication of the condition of the system and allow comparisons of similar time periodsover a span of time, to help detect congestion trends and possible performancedegradation.

Key statistics are also provided to facilitate the monitoring of the most important networkparameters. For example, various handover failure statistics may be combined andaveraged over the total number of calls, to produce a handover failure rate key statistic.

The following are the key statistics groupings:

S Call Summary.

S Channel Usage.

S Connection Establishment.

S RF Loss Summary.

S MTL Utilization.

Network health statistics

Network health statistics are calculated at the OMC-R using a combination of raw andkey statistics. These statistics are used to create BSS network performance reports.These reports provide an indication of the networks health from the subscribersperspective.

The following are the network health report groupings:

S Health check.

S GPRS performance.

S Handover performance.

S TCH congestion.

S SDCCH congestion.

S Paging performance.

S Radio performance.

Custom statistics

The OMC-R permits the creation of custom statistics using the algebraic combination ofexisting raw and key statistics. Refer to the Installation and Configuration: GSM SystemConfiguration (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

GSR6 Introduction to GSM Statistics Manual

14 Feb 2003


68P02901W56-L 1–5

counter array statistics.

Distribution statistics:

The use of a bin is for measuring the frequency of an event. The measurementcan be done by time (weighted distributions) or by occurrences (normaldistributions). There are 10 bins (numbered 0 – 9). Each bin has a low to highrange.

Counter array statistics:

The use of a bin is for counting the number of occurrences on a per scenario orcause basis. The number of bins varies based on the number of causes beingtracked.

Cumulative value – The total value for the entire interval.

Default time interval – The key statistics default time interval is 0.5 hours whencomputing all key statistics.

The interval used for two key statistics, TCH_MEAN_HOLDING_TIME andSDCCH_MEAN_HOLDING_TIME, is specified in seconds. To convert the defaultvalue of 0.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.

Number of samples – The value used in calculating the mean for distributions. For anormal distribution, this value is incremented by one each time a value is reported. For aweighted distribution, this value is incremented by the time difference since the lastreported 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 amathematical formula for one or more cells selected in the OMC-R GUI PerformanceManagement window. The mathematical formula may include a single raw statistic or aset 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 managementdatabase using the MMI. When the reported value for a statistic equals the thresholdvalue, an alarm is sent from the BSS to the OMC-R. Thresholds may also be specifiedfor individual bins in counter array statistics.

GSR6Types of raw statistics

14 Feb 20031–6


68P02901W56-L

Types of raw statistics

Introduction

The BSS reports the following six types of statistics:

S Counter.

S Counter array.

S Gauge.

S Duration.

S Normal distribution.

S Weighted distribution.

Counter statistics

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

Threshold event reporting

A counter statistic may have a user specified threshold that can generate an alarm whenreached. The BSS only reports one alarm to the OMC for a specific statistic during aninterval.

Maximum value

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

Interval expiry

Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves thecounter statistic value then resets it to zero.

GSR6 Types of raw statistics

14 Feb 2003


68P02901W56-L 1–7

Counter array statistics

Counter array statistics are the total number of times an event occurs and a breakdownof the causes or reasons why the event occurred during an interval. When an eventoccurs, the BSS increments the individual cause or reason by the value reported by theapplication at the interval expiry. The OK_ACC_PROC statistic is an example of acounter array statistic.

Display convention

The convention used in this manual for presenting a specific bin of a counter arraystatistic is COUNTER ARRAY STATISTIC NAME[bin name]. For example,OK_ACC_PROC[CM_REESTABLISH] is the CM_REESTABLISH bin of theOK_ACC_PROC counter array statistic.

Counter array bins

A bin is a storage area in a counter array for cumulative cause or reason values. Thenumber of bins in a counter array statistic depends on the number of causes or reasonsassociated with a specific event.

Maximum value

The maximum value for the total and individual cumulative values is 65534 (hex=0xffff). Ifa bin count reaches this value during a period, the bin contents will remain at themaximum value until the interval expiry.

Interval expiry

Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves thecounter array total 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, thecumulative value may not be a negative value. The BSS checks the cumulative beforecalculating the mean value, and if the result is a negative number, it will set the meanzero.

Threshold event reporting

A gauge statistic may have a user specified threshold that can generate an alarm whenreached. The BSS only reports one alarm to the OMC for a specific statistic during aninterval.

Interval expiry

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


14 Feb 20031–8


68P02901W56-L

Duration statistics

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

Total duration

The OMC only reports the total duration.

The total duration is the length of time an event occurs during an interval. It is acumulative value reported in milliseconds. When the event starts, the BSS saves thestart time of day (in milliseconds). When the event ends, the BSS saves the stop time ofday (in milliseconds). The BSS calculates the total duration using the following formula:

stop time – start time

Wraparound to next day

The 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 value

The BSS calculates the mean duration by dividing the total duration by the periodcounter. The BSS increments the period counter each time a measured event occursduring an interval.

mean = total time / period counter

Maximum value

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

Interval expiry

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

S If no events occur during the interval, the BSS sets the duration minimum value isto zero. The BSS saves this minimum value then resets it to 0xffffffff.

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

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

S The BSS stops and resets any active timers.


14 Feb 2003


68P02901W56-L 1–9

Normal distribution statistics

Normal distribution statistics are the number of times the reported value of an event fallswithin a specified range. A distribution statistic is a single row array of 10 bins, numbered0–9. The BSS also saves the minimum reported value, the maximum reported value, anda calculated mean of the reported values. The OMC only reports the distribution mean,maximum, and minimum values.

Bins

Each bin represents a range of values reported by an application. Each time anapplication reports a value, the BSS increments the bin corresponding to the reportedvalue by one. The BSS also increments the sample count by one and calculates the totalof all reported values during the interval. The disp_stats command displays theindividual bin values.

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

Mean value

The BSS calculates the mean value by dividing the cumulative total of the reportedvalues by the sample count.

NOTE If there are gaps in the bin ranges, some occurrences of reportedevents are not included in the bin counts. For example, if theassigned range of values of two adjacent bins are 10–15 and17–20, a reported event with a value of 16 is not recorded. Themean value does not account for the unrecorded event.

Histogram

A normal distribution statistic may be illustrated as a histogram. Figure 1-1 shows therange of values assigned to bin 0 is 0–10, bin 1 is 11–20, and bin 7 is 71–80. Thehistogram shows bins 0 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


14 Feb 20031–10


68P02901W56-L

Interval expiry

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

1. The mean value is calculated. If the number of reported events is not equal to 0,the mean value is calculated by dividing the cumulative value of all of the reportedevents 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 statisticsWeighted distribution statistics are the length of time that the reported value of an eventfalls within a specified range. These statistics are placed in a single row array of 10 bins,numbered 0–9, and a mean duration of the reported events. The minimum and maximumdurations of the reported values are also saved and reported at the end of the interval.

Bins

Each bin is defined to represent a range of values. Each time an application processreports a value, the bin corresponding to the reported value is incremented by the lengthof time the reported value stays within the bin’s specified range. This allows the numberof times a reported value falls 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 of values may be sized based on the focus of the analysis to be performed.For example, when measuring a statistic, the range of values assigned to the bins maybe assigned to reflect the periods of greatest activity. By narrowing the bin ranges, theperiods of greatest activity may be more closely examined.

If there are gaps in the bin ranges, some occurrences of reported events arenot included in the bin counts. For example, if the assigned range of values oftwo adjacent bins are 10–15 and 17–20, a reported event with a value of 16 isnot recorded. The mean value does not account for the unrecorded event.

NOTE

Wraparound to next day

A check is automatically made to determine if the interval started before midnight andended after midnight. If the start time is greater than the stop time, the total duration iscalculated using the following formula:

(86400000 – start time) + stop time

Mean value

The mean value is the statistical average of all of the reported values divided by thenumber of reported events.

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

NOTE


14 Feb 2003


68P02901W56-L 1–11

Histogram

A weighted distribution statistic may be illustrated as a histogram. Figure 1-2 shows therange of values assigned to bin 0 is 0–10 and bin 7 is 71–80. The following histogramshows that the duration of the event reporting values from 0–10 was 40 milliseconds andthe duration of the 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 expiry

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

1. Stop any running timers.

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

3. The distribution minimum value is saved and reset to 0xffffffff. If no value wasreceived during 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.

GSR6Statistic usages

14 Feb 20031–12


68P02901W56-L

Statistic usages

Quality of service monitoringQuality of service is determined by statistics related to service accessibility, integrity, andretainability.

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

S Mobile registration.

S Mobile paging.

S Network accessibility.

S Call set up time.

S Call release time.

S Call release delay.

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

S Call clarity.

S Interference.

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

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

S Mobile registration and paging.

S Network accessibility.

S Call set up time.

S Call release time.

S Call release delay.

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

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

Several outcomes are possible when the registration is not successful, either due to theprocedure running correctly and the network providing a meaningful answer, possiblydenying service or the procedure running incorrectly and the network providing ananswer that is meaningless.

If the MS satisfactorily updates its location, it can then be paged by the MSC when anincoming call arrives. The MSC provides the concerned BSC with the ID of the MS to bepaged and the list of cells in which the paging should be issued. The BSC is in charge ofmanaging the grouping and scheduling of paging messages and initial assignment ofmessages.

GSR6 Statistic usages

14 Feb 2003


68P02901W56-L 1–13

Network accessibility

A registered MS should be able to access the network. Access denial is divided intothree main categories:

S Call blocking.

– No signalling channel (SDCCH) is available.

– No Traffic Channel (TCH) is available.

S 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).

S Refusal by the MSC for network access.

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

Call set-up time

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

S Post-selection delay.

Post-selection delay is the time from dialling the last digit on the fixed network, orpressing the “send” button on a MS, to receiving the appropriate tone. Onepossible reason for this delay is that all resources have been allocated to othercalls, which may result in a queueing delay.

S Answer signal delay.

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

The raw statistics TCH_DELAY and CALLS_QUEUED are associated with call set-uptime and answer signal delay.

Call release time

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

Call release delay

Call release delay is the time between releasing one call and being able to originateanother. The only aspect of concern to the BSS is queueing. All other areas aretransparent to the BSS.

Service integrity

Service integrity is determined by the processes affecting the following:

S Call clarity.

S Lack of interference.

S Correct tones and announcements.

GSR6Statistic usages

14 Feb 20031–14


68P02901W56-L

Call clarity

Call clarity is measured by the uplink–downlink path loss difference on the air interface.The raw statistic PATH_BALANCE is the only measurement associated with call clarity.

Lack of interference

The lack of interference is measured by the bit error rate and the interference level onmonitored idle channels. The raw statistics BER and INTF_ON_IDLE are the onlymeasurements associated with lack of interference.

Correct tones and announcements

Subscriber perceptions of service integrity are influenced by the delivery of correct tonesand announcements when using the system. No statistics are available to measurecorrect tones and announcements.

Service retainability

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

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

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

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

S 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 18.

Fault finding

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

Monitoring Faults

Hard failures are normally identified via alarm surveillance. However, it is possible for asystem component to deteriorate over time, while still continuing to function. Thedeterioration may manifest itself in a number of ways such as an increase in dropped callrate, or a lower call completion rate. Monitoring of these system parameters over timecan provide the operator with an early indication of performance degradation due todeterioration in hardware components.

Types of faults

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

S Damaged antennas.

S Frequency drift.

S Electromechanical problems.

– Problems with remote combiners.

– Noisy channels.

GSR6 Statistic usages

14 Feb 2003


68P02901W56-L 1–15

Optimization

Optimization of system parameters is necessary to ensure that the installed cellularinfrastructure is utilized as efficiently as possible. Statistics can be used to monitor andverify the effects of optimization activities. For example, if handover thresholds areadjusted, statistics may be used to verify that the new threshold results in an improvedhandover success rate.

Optimization of a GSM network is a process whereby several BSS database parametersare fine-tuned from their default values and antenna installations are adjusted to improvecall success rate and quality.

By optimizing a network, the performance of the cellular equipment is verified and abenchmark obtained for the system that may be used for subsequent expansion. Theresults may also be used to 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 theoffered traffic load. Statistics that monitor resource utilization and congestion can be usedto determine when the network needs to be expanded, (or contracted, if resources arebeing under utilized).

Installation and commissioning

Installation and commissioning of cellular equipment is a complex procedure that must beverified after completion. Part of the verification procedure uses statistics to ensure thatthe 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.

NOTE This activity is currently supported via the Call Trace feature

GSR6Ladder diagrams

14 Feb 20031–16


68P02901W56-L

Ladder diagrams

About ladder diagrams

The relationship between statistics and call processing elements and functions aregraphically represented as ladder diagrams in Chapter 18 – Ladder diagrams.

Ladder diagrams show the relationships between the MS, BSS, and MSC elements,represented as vertical lines.

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

Intermediate network element functions are placed on the vertical lines as a sequentialreference. Parallel functions may also be included as separate vertical lines for additionalreference.

Statistics associated with individual messages are located immediately below thedirectional line. All of the statistics that may be generated as the result of the processflow 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.

14 Feb 2003


68P02901W56-L 2–1

Chapter 2

Statistical operations

GSR6

14 Feb 20032–2


68P02901W56-L

GSR6 Statistical operations

14 Feb 2003


68P02901W56-L 2–3

Statistical operations

Introduction to statistical operations

This chapter describes the operations associated with statistics, including:

S Enabling and disabling statistics.

S Displaying enabled statistics on a selected basis.

S Displaying statistic values.

S Setting and displaying statistic intervals.

S Setting and displaying statistic properties.

GSR6Enabling/disabling a statistic

14 Feb 20032–4


68P02901W56-L

Enabling/disabling a statistic

DescriptionStatistics must be enabled to obtain statistical data. The stat_mode command enablesand disables 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:

S ACCESS_PER_PCH.

S ALLOC_SDCCH.

S ALLOC_SDCCH_FAIL.

S ALLOC_TCH.

S ALLOC_TCH_FAIL.

S BUSY_SDCCH.

S BUSY_TCH.

S IN_INTER_BSS_HO.

S IN_INTRA_BSS_HO.

S INTRA_CELL_HO.

S MA_CMD_TO_MS_BLKD.

S MA_REQ_FROM_MSC.

S OK_ACC_PROC.

S OUT_INTER_BSS_HO.

S OUT_INTRA_BSS_HO.

S RF_LOSSES_SD.

S TOTAL_CALLS.

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

S RF_LOSSES_TCH.

Enabling a statisticA statistic is enabled by entering the stat_mode command using the following syntax:

stat_mode <meas_type> on [<location>] [<cell_desc>]

Where: meas_type is: the statistic being enabled

on enable mode

location the location of the statisticbeing enabled, if required

cell_desc the cell name or number, ifrequired

GSR6 Enabling/disabling a statistic

14 Feb 2003


68P02901W56-L 2–5

Example

stat_mode rf_losses_tch on cell_name=mid34a

Where: rf_losses_tch is: 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: meas_type is: the statistic being disabled

off disable mode

location the location of the statisticbeing disabled, if required


Example

stat_mode mtp_link_ins off

Where: mtp_link_ins is: meas_type

off disable mode

System response:

COMMAND ACCEPTED

GSR6Displaying enabled statistics

14 Feb 20032–6


68P02901W56-L

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) for a detailed description of the disp_enable_stat command.

Specific listings may be generated based on the arguments entered with thedisp_enable_stat command, including:

S No argument – A listing of all currently enabled statistics will be presented.

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

S cell_desc – A listing of all of the currently enabled statistics for the specified cellwill be presented.

S location – A listing of all of the currently enabled statistics for the specified site willbe presented.

S 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 thedisp_enable_stat command 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_rpomtp_mgt_inhibitmtp_mgt_uninhibitmtp_re_txmtp_sif_sio_rxmtp_msu_txmtp_msu_rxsl_congestionsl_stop_congestionmsu_discardedcongestion_lost_msu

GSR6 Displaying enabled statistics

14 Feb 2003


68P02901W56-L 2–7

sif_sio_rx_opcsif_sio_tx_dpcsif_sio_typerouting_syntaxrouting_unknownsccp_msgssccp_msgs_txsccp_msgs_rxinvalid_frames_rxi_frames_rxi_frames_txsabm_txfrmrn2_expirymtp_link_insmtp_unavailablemtp_local_mgtmtp_remote_mgtmtp_linkfailmtp_remote_procmtp_local_busymtp_congestioncpu_usage...Enabled Statistics for Cell 001 01 03e7h 0028hrf_losses_tchrf_losses_sdintra_cell_hoin_inter_hoout_inter_hointra_bss_hoaccess_per_rach...tch_delayintf_on_idlebusy_tchbusy_sdcchber...

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

GSR6Displaying statistic values

14 Feb 20032–8


68P02901W56-L

Displaying statistic values

Description

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

NOTE The value of a statistic for the current interval cannot bedisplayed. The disp_interval command may be used to displaycompleted intervals.

When counter array statistics are displayed, the values for the individual bins aredisplayed. A total value of all of the bins may also be displayed for some counter arraystatistics. Refer to 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: interval is: a completed statisticalinterval

meas_type the name of the statistic tobe displayed


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.

Example

This 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 6198634944

Where: 5 is: interval

out_ho_cause_atmpt statistic

5 4 3 2 1 61986 34944 cell_number

GSR6 Displaying statistic values

14 Feb 2003


68P02901W56-L 2–9

System response:

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

Total: 110

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

GSR6Setting the statistic interval

14 Feb 20032–10


68P02901W56-L

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.

NOTE The OMC-R can calculate key statistics at 60 minute intervals ifit is configured to handle 60 minute statistic files.

The stat_interval is specified by entering the chg_element command using thefollowing syntax:

chg_element stat_interval <30 or 60> <location>

Where: stat_interval is: parameter name

30 or 60 valid values for theparameter, in minutes

location This is a BSS-wideparameter and 0 is theonly valid value for thisargument.

Example

This example shows the interaction required to change the statistical interval to 60minutes.

chg_element stat_interval 60 0


60 60 minutes

0 location

System response:

COMMAND ACCEPTED

GSR6 Displaying the statistic interval

14 Feb 2003


68P02901W56-L 2–11

Displaying the statistic interval

Description

The stat_interval is a non-statistical parameter that is used to specify the interval. Thecurrent interval may be displayed using the disp_element command using the followingsyntax:

disp_element stat_interval <location>


location This is a BSS-wideparameter and 0 is theonly valid value for thisargument.

Example

This example shows the interaction required to display the statistical interval.

chg_element stat_interval 0


0 location

System response:

stat_interval = 30

GSR6Displaying the statistic interval start times

14 Feb 20032–12


68P02901W56-L

Displaying the statistic interval start times

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

On startup, the first start time (interval 0) corresponds to current time of the systemclock. The second start time (interval 1) automatically becomes synchronized to the nexthour (:00) or half hour (:30), depending upon the current statistic interval.

ExampleThis example shows the interaction required to display the starting times of the statisticalintervals where the statistic interval is 30 and the disp_interval command was enteredat 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 commandis entered. When the command is entered, the current set of 12 start times is presented.If the command is entered after interval 11 would be completed, the listing displays thenext set of 12 interval start times.

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

disp_interval

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

GSR6 Setting statistic properties

14 Feb 2003


68P02901W56-L 2–13

Setting statistic properties

Description

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

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

S The alarm threshold may be changed for counter and gauge statistics if an alarmis associated with the statistic.

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

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

Setting a threshold

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

A threshold is specified by entering the chg_stat_prop command using the followingsyntax:

chg_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: meas_type is: a counter or gaugestatistic

location the location of the statisticwhose threshold is beingset, if required


Example

This 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: rf_losses_tch is: meas_type

cell_name=mn14b cell_desc

System response:

Enter the alarm threshold: 500COMMAND ACCEPTED

Counter statistics

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

GSR6Setting statistic properties

14 Feb 20032–14


68P02901W56-L

Table 2-1 Counter statistics

Statistical name Alarmseverity

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


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

GSR6 Setting statistic properties

14 Feb 2003


68P02901W56-L 2–15

Statistical name BasisValid valuesAlarmseverity

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

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


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

SL_CONGESTION Warning min: 1 max: 2147483647

SS7 link

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

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

Setting bin rangesDistribution statistics include 10 bins, numbered 0 to 9. Each bin represents a range ofvalues. When events are reported, the bin corresponding to the reported value isincremented. The range of values for the individual bins in a distribution statistic may bespecified with the chg_stat_prop command using the following syntax:

chg_stat_prop <meas_type> [<location>] [<cell_desc>]

Where: meas_type is: a normal or weighteddistribution statistic

location the location of the statisticwhose bin range is beingset, if required


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

GSR6Setting statistic properties

14 Feb 20032–16


68P02901W56-L

Bin ranges

Distribution statistics include 10 bins, numbered 0 to 9. The range of values to bemeasured by the statistic must be considered when assigning values for the individualbins in the distribution. For example, if the possible range of values to be measured isfrom 0 to 100, then the minimum value for bin 0 should be 0, and the maximum value forbin 9 should be 100.

Gaps in the range of values covered should be avoided when assigning the minimum andmaximum values for the individual bins. For example, if bin 0 covers values from 0 to 10and bin 1 covers values from 12 to 15, a gap would exist for the value 11. This wouldcause 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. Thisallows a specific value to be reported within the overall distribution. For example, if theminimum and maximum values for a bin are both specified to be 10, the bin is peggedeach time a value of 10 is reported.

Default ranges

Distribution statistics have default ranges for bins.

Example

This example shows the interaction required to change the minimum and maximumvalues for two bins of the BUSY_TCH statistic for all cells at site 1.

chg_stat_prop busy_tch 1 all

Where: busy_tch is: meas_type

1 location

all all cells at the specifiedsite

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: <carriage return>Enter the max value for bin 1: 7COMMAND ACCEPTED

GSR6 Displaying statistic properties

14 Feb 2003


68P02901W56-L 2–17

Displaying statistic properties

DescriptionThe properties of individual statistics may be displayed using the disp_stat_propcommand. The information and presentation format are dependent upon the statistictype, including:

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

S Bin ranges are displayed for normal and weighted statistics.

S The cause is displayed for the counter array statistics.

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

Displaying a counter statisticCounter statistic properties are displayed by entering the disp_stat_prop commandusing the following syntax:

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

Where: meas_type is: a counter statistic

location the location of the statisticwhose properties arebeing displayed, ifrequired


Example

This example shows the interaction required to display the properties for theTOTAL_CALLS statistic for all cells at site 1.

disp_stat_prop total_calls 1 all

Where: total_calls is: meas_type

1 location

all all cells at the specifiedlocation

System response:STATISTIC: TOTAL_CALLS SITE: 1TYPE: PER CELL OBJECT: COUNTER

ALARM ALARMCELL # MODE SEVERITYTHRESHOLD––––––––––––––––––– –––– –––––––––––––––––543 21 61698 (f102h) 34776 (87d8h) ENABLED NO ALARM N/A543 21 61698 (f102h) 34777 (87d9h) ENABLED NO ALARM N/A543 21 61698 (f102h) 34778 (87dah) ENABLED NO ALARM N/A543 21 61698 (f102h) 34779 (87dbh) ENABLED NO ALARM N/A543 21 61698 (f102h) 34780 (87dch) ENABLED NO ALARM N/A

GSR6Displaying statistic properties

14 Feb 20032–18


68P02901W56-L

Displaying a gauge statisticGauge statistic properties are displayed by entering the disp_stat_prop command usingthe following syntax:


Where: meas_type is: a gauge statistic



ExampleThis example shows the interaction required to display the properties for theCHANNELS_DISABLED statistic 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 6169834776

Where: available_tch is: meas_type

1 location

cell_number=5 4 3 2 161698 34776

cell_desc

System response:STATISTIC: AVAILABLE_TCH SITE: 1TYPE: PER CELL OBJECT: GAUGE

ALARM ALARMCELL # MODE SEVERITYTHRESHOLD––––––––––––––––––– –––– –––––––––––––––––543 21 61698 (f102h) 34776 (87d8h) ENABLED NO ALARM N/A

Displaying a distribution statisticDistribution statistic properties are displayed by entering the disp_stat_prop commandusing the following syntax:


Where: meas_type is: 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

GSR6 Displaying statistic properties

14 Feb 2003


68P02901W56-L 2–19

Where: busy_tch is: meas_type

1 location

5 4 3 2 1 61698 34776 cell_desc

System response:STATISTIC: BUSY_TCH SITE: 1TYPE: 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 162147174832 9214174833 2141749879

Displaying a counter array statisticCounter array statistic properties are displayed by entering the disp_stat_propcommand using the following syntax:


Where: meas_type is: 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 622598736

Where: out_ho_cause_atmpt is: meas_type

5 4 3 2 1 62259 8736 cell_desc

GSR6Displaying statistic properties

14 Feb 20032–20


68P02901W56-L

System response:STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 2TYPE: PER CELL OBJECT: COUNTER ARRAY

BIN# CAUSE –––– ––––– 0 Uplink Quality 1 Uplink Level 2 Downlink Quality 3 Downlink Level 4 Distance 5 Uplink Interference 6 Downlink Interference 7 Power Budget 8 Congestion 9 Adjacent Channel Interference

CELL# MODE –––––––––––––––––––––––––––––––––––––– –––– 543 21 62259 (f333h) 8736 (2220h) DISABLED

Displaying a duration statisticDuration statistic properties are displayed by entering the disp_stat_prop commandusing the following syntax:


Where: meas_type is: 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: flow_control_barred is: meas_type

2 location

5 4 3 2 1 62259 8736 cell_desc

System response:STATISTIC: FLOW_CONTROL_BARRED SITE: 2TYPE: PER CELL OBJECT: TOTAL TIME

CELL# MODE –––––––––––––––––––––––––––––––––––––– –––– 543 21 62259 (f333h) 8736 (2220h) DISABLED

14 Feb 2003


68P02901W56-L 3–1

Chapter 3

BSS statistics

GSR6

14 Feb 20033–2


68P02901W56-L

GSR6 Introduction to BSS Statistics

14 Feb 2003


68P02901W56-L 3–3

Introduction to BSS Statistics

DescriptionThis chapter includes descriptions of the BSS statistics. BSS statistics are organized intofour major subgroups:

S BSS C7 utilization.

S Enhanced full rate.

S Intra-BSS handover.

S SCCP performance and utilization.

BSS C7 utilizationBSS 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:

S SIF_SIO_RX_OPC.

S SIF_SIO_TX_DPC.

S SIF_SIO_TYPE.

Enhanced full rateA single statistic tracks the number of channel requests by MSs capable of EnhancedFull Rate (EFR) operation.

S EFR_REQ_FROM_MSC.

Intra-BSS handoverA single counter array statistic tracks the number of successful intra-BSS handovers.

S INTRA_BSS_HO_CAUSE_SUC.

SCCP performance and utilizationSCCP performance and utilization statistics track the performance of the SignallingConnection Control Part (SCCP) protocol layer of the ITU–TSS C7.

The SCCP manages the establishment and release of call related connections. Aconnection is established for each transaction. For example, location update and servicerequest, both BSS and MSC maintain contexts related to the transaction; these contextsmay be identified using the SCCP reference number. This information indicates theperformance level and quality of the SCCP. The following are the SCCP performanceand utilization statistics:

S HO_REQ_MSC_PROTO.

S MA_REQ_FROM_MSC_FAIL.

S MSC_OVLD_MSGS_RX.

S PAGE_REQ_FROM_MSC_FAIL.

S ROUTING_SYNTAX.

S ROUTING_UNKNOWN.

S SCCP_MSGS.

S SCCP_MSGS_RX.

S SCCP_MSGS_TX.

GSR6EFR_REQ_FROM_MSC

14 Feb 20033–4


68P02901W56-L

EFR_REQ_FROM_MSC

Description

This statistic tracks the number of channel requests for Enhanced Full Rate (EFR) viathe Assignment Request or any Handover Request from the MSC indicating the MS isEFR capable.

NOTE More than one Assignment Request or Handover Request maybe received from the MSC for a single call. This may occur whenthe channel mode procedure occurs, or when more than onehandover occurs for a call. The incidence of these occurrencesshould not significantly impact the validity of this statistic.

Pegging

This statistic is pegged each time an Assignment Request or Handover Request isreceived from the MSC indicating that the MS is EFR capable.

Analysis

In systems without the EFR feature, this statistic can be used to determine if the EFRfeature should be acquired, if not currently installed.

In systems with the EFR feature, this statistic can be used to track the number ofchannel requests by EFR capable MSs.

Reference None.

Usage Quality of service.

Network planning.

Radio resource allocation.

Basis BSS.

Type Counter.

GSR6 HO_REQ_MSC_PROTO

14 Feb 2003


68P02901W56-L 3–5

HO_REQ_MSC_PROTO

Description

This statistic tracks the number of Handover Request messages received from the MSCthat fail message validation. Validation failure may occur due to protocol errors whichmay occur if the message is badly formatted or incompatible database elements exist inthe BSS and MSC.

Pegging

This statistic is pegged each time a Handover Request message from the MSC failsmessage validation at the BSS. Currently, this statistic is not pegged.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof message validation failures that are acceptable in normal system operations.

If the specified threshold is exceeded, the 17. BSS: HO Request from the MSCprotocol error – 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.2.2.

Usage Handover.

Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6INTRA_BSS_HO_CAUSE_SUC

14 Feb 20033–6


68P02901W56-L

INTRA_BSS_HO_CAUSE_SUC

Description

This statistic tracks the number of successful intra BSS handovers on a per cause basis.A total 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 uplinkinterference.

6 DOWNLINK_INTERFERENCE Handovers due to downlinkinterference.

7 POWER_BUDGET Handovers due to power budget.

8 CONGESTION Handovers due to congestion.

Pegging

The bin corresponding to the cause of the successful handover is pegged each time aHandover Performed message is sent from the BSS to the MSC.

Analysis

This statistic can be used for trend analysis permitting early identification of problemsbefore 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.

GSR6 MA_REQ_FROM_MSC_FAIL

14 Feb 2003


68P02901W56-L 3–7

MA_REQ_FROM_MSC_FAIL

Description

This statistic tracks the number of Assignment Request messages received from theMSC that fail message validation. Validation failure may occur due to protocol errorswhich may occur if the message is badly formatted or incompatible database elementsexist in the BSS and MSC.

Pegging

This statistic pegs each time an Assignment Request message from the MSC failsmessage validation at the BSS.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof failures that are acceptable in normal system operations.

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

Reference GSM 8.08, 3.9.2, 3.2.2.5 and 3.2.1.3.


Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6MSC_OVLD_MSGS_RX

14 Feb 20033–8


68P02901W56-L

MSC_OVLD_MSGS_RX

Description

This statistic tracks the number of OVERLOAD messages that have been received bythe BSS from the MSC. This statistic pegs independently of the MSC Overload Controlfeature being enable or disabled.

Pegging

This statistic pegs each time an OVERLOAD message is received by the BSS from theMSC.

Analysis

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

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


Network planning.

Basis BSS.

Type Counter.

GSR6 PAGE_REQ_FROM_MSC_FAIL

14 Feb 2003


68P02901W56-L 3–9

PAGE_REQ_FROM_MSC_FAIL

Description

This statistic tracks the number of Page Request messages received from the MSC thatfail message validation. Validation failure may occur due to protocol errors which mayoccur if the message is badly formatted. A protocol error does not indicate pagingsuccess or failure.

Pegging

This statistic pegs each time a Page Request message from the MSC fails messagevalidation at the BSS.

Analysis

A 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 atthe OMC (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.

GSR6ROUTING_SYNTAX

14 Feb 20033–10


68P02901W56-L

ROUTING_SYNTAX

Description

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

Pegging

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

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andMSC. Excessive syntax errors can result in degraded SCCP performance. A thresholdvalue 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 1. BSS: Routing failure - syntax errordetected – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-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.

GSR6 ROUTING_UNKNOWN

14 Feb 2003


68P02901W56-L 3–11

ROUTING_UNKNOWN

Description

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

Pegging

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

Analysis

An SPC is the destination address for a message routed by the networking functions ofthe MTP3 protocol. If the BSC receives an incorrect SPC, it will not be able to correctlyroute the message. A threshold value should be assigned to this statistic which reflectsthe maximum number of invalid 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6SCCP_MSGS

14 Feb 20033–12


68P02901W56-L

SCCP_MSGS

Description

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

Pegging

This statistic pegs when SCCP messages are transmitted or received on the signallinglink.

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andMSC. This statistic can be used for trend analysis of SCCP performance and utilization.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6 SCCP_MSGS_RX

14 Feb 2003


68P02901W56-L 3–13

SCCP_MSGS_RX

Description

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

Pegging

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

Analysis

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

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6SCCP_MSGS_TX

14 Feb 20033–14


68P02901W56-L

SCCP_MSGS_TX

Description

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

Pegging

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

Analysis

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

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6 SIF_SIO_RX_OPC

14 Feb 2003


68P02901W56-L 3–15

SIF_SIO_RX_OPC

Description

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

Pegging

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

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andMSC. This statistic can be used for trend analysis of the activity on all SLs for aparticular BSS.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).

Usage MTP C7 utilization.

Basis BSS.

Type Counter.

GSR6SIF_SIO_TX_DPC

14 Feb 20033–16


68P02901W56-L

SIF_SIO_TX_DPC

Description

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

Pegging

This statistic pegs each time SIF or SIO are transmitted across all signalling links to aBSS.

Analysis

A 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 trendanalysis of the activity of the signalling links on a BSS.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6 SIF_SIO_TYPE

14 Feb 2003


68P02901W56-L 3–17

SIF_SIO_TYPE

Description

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

Pegging

This statistic pegs each time SIF or SIO octets are transmitted or received on eachsignalling link.

Analysis

This statistic can be used for trend analysis of the activity of the signalling links on aBSS.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6SIF_SIO_TYPE

14 Feb 20033–18


68P02901W56-L

14 Feb 2003


68P02901W56-L 4–1

Chapter 4

Cell statistics

GSR6

14 Feb 20034–2


68P02901W56-L

GSR6 Introduction to Cell Statistics

14 Feb 2003


68P02901W56-L 4–3

Introduction to Cell Statistics

DescriptionThis chapter includes descriptions of the cell statistics. Cell statistics are organized intothe following groups:

S Call clearing.

S Concentric cell.

S Connection establishment.

S Directed retry.

S Emergency call access.

S Extended range cell.

S General handover.

S Inter-BSS handover.

S Intra-BSS handover.

S Intra-cell handover.

S Multiband.

S TCH assignment.

S Usage congestion.

S DYNET failures.

S Interference bands.

Call clearingCall clearing statistics track the number calls lost due to RF failures, cipher modefailures, or procedure timeouts. The following are call clearing statistics:

S CIPHER_MODE_FAIL.

S CLASSMK_UPDATE_FAIL.

S CLR_REQ_TO_MSC.

S CLR_CMD_FROM_MSC.

S RF_LOSSES_SD.

S RF_LOSSES_TCH.

Concentric cellConcentric cell statistics track concentric cell feature processes. The following areconcentric cell statistics:

S TCH_CONG_INNER_ZONE.

S TCH_USAGE_INNER_ZONE.

S ZONE_CHANGE_ATMPT.

S ZONE_CHANGE_SUC.

GSR6Introduction to Cell Statistics

14 Feb 20034–4


68P02901W56-L

Connection establishmentConnection establishment statistics track access, allocation, channel request, and MSCpage request functions. The following are connection establishment statistics:

S ACCESS_PER_AGCH.

S ACCESS_PER_PCH.

S ACCESS_PER_RACH.

S ALLOC_SDCCH.

S ALLOC_SDCCH_FAIL.

S ALLOC_TCH.

S ALLOC_TCH_FAIL.

S CHAN_REQ_CAUSE_ATMPT.

S CHAN_REQ_MS_BLK.

S CHAN_REQ_MS_FAIL.

S CONN_REFUSED.

S CONN_REQ_TO_MSC.

S INV_EST_CAUSE_ON_RACH.

S OK_ACC_PROC.

S OK_ACC_PROC_SUC_RACH.

S PAGE_REQ_FROM_MSC.

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

S CONGEST_EXIST_HO_ATMPT.

S CONGEST_STAND_HO_ATMPT.

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

S NUM_EMERG_ACCESS.

S NUM_EMERG_REJECTED.

S NUM_EMERG_TCH_KILL.

S NUM_EMERG_TERM_SDCCH.

Extended range cellExtended range statistics track extended range feature processes. The following areextended range cell statistics:

S ER_INTRA_CELL_HO_ATMPT.

S ER_INTRA_CELL_HO_SUC.

S TCH_USAGE_EXT_RANGE.


14 Feb 2003


68P02901W56-L 4–5

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

S ASSIGNMENT_REDIRECTION .

S BAD_HO_REFNUM_MS.

S HO_FAIL_NO_RESOURCES.

Inter-BSS handoverInter-BSS handover statistics track inter-BSS handover processes. The following areinter-BSS handover statistics:


S HO_REQ_MSC_FAIL.

S HO_REQ_MSC_OK.

S IN_INTER_BSS_HO.

S OUT_INTER_BSS_HO.

Intra-BSS handoverIntra-BSS handover statistics track intra-BSS handover processes. The following areintra-BSS handover statistics:


S IN_INTRA_BSS_HO.

S OUT_HO_CAUSE_ATMPT

S OUT_INTRA_BSS_HO.

Intra-cell handoverIntra-cell handover statistics track intra-cell handover processes. The following is theonly intra-cell handover statistic:


S INTRA_CELL_HO.

MultibandMultiband statistics track multiband feature processes. The following are multibandstatistics:


S INTERBAND_ACTIVITY.

S MS_ACCESS_BY_TYPE.

S MS_TCH_USAGE_BY_TYPE.

S MS_TCH_USAGE_BY_TYPE_PCS.

S OUT_HO_CAUSE_ATMPT.

GSR6Introduction to Cell Statistics

14 Feb 20034–6


68P02901W56-L

TCH assignmentTCH assignment statistics track successful, unsuccessful, and total traffic channelassignment processes. The following are TCH assignment statistics:

S MA_CMD_TO_MS.

S MA_CMD_TO_MS_BLKD.

S MA_FAIL_FROM_MS.

S MA_REQ_FROM_MSC.

S TCH_Q_REMOVED.

S TOTAL_CALLS.

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

S AVAILABLE_SDCCH.

S AVAILABLE_TCH.

S BUSY_SDCCH.

S BUSY_TCH.

S BUSY_TCH_CARR.

S CAL_SP_VERS_REQUEST_MONITOR.

S CALLS_QUEUED.

S CLASSMK_UPDATE_FAIL.

S FLOW_CONTROL_BARRED .

S MA_COMPLETE_FROM_MS .

S MA_COMPLETE_TO_MSC.

S MT_LCS_ON_SDCCH.

S PAGING_REQUESTS

S PCH_AGCH_Q_LENGTH.

S PCH_Q_PAGE_DISCARD.

S SDCCH_CONGESTION.

S SECOND_ASSIGN_ATMPT.

S SECOND_ASSIGN_SUC.

S SMS_INIT_ON_SDCCH.

S SMS_INIT_ON_TCH.

S SMS_NO_BCAST_MSG.

S TCH_CONGESTION.

S TCH_DELAY.

S TCH_Q_LENGTH.

S TCH_USAGE.


14 Feb 2003


68P02901W56-L 4–7

DYNET failures

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

S DYNET_ASSIGN_FAIL.

S DYNET_CALL_REJECTS.

Interference bands

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

S IDLE_TCH_INTF_BAND0.





GSR6ACCESS_PER_AGCH

14 Feb 20034–8


68P02901W56-L

ACCESS_PER_AGCH

Description

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

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

Pegging

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

Analysis

This statistic can be used for trend analysis of Intermediate Assignment messages senton 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.

NOTE This statistic is affected by phantom Random Access CHannel(RACH).The level of congestion on the AGCH cannot bedetermined using current statistics

GSR6 ACCESS_PER_PCH

14 Feb 2003


68P02901W56-L 4–9

ACCESS_PER_PCH

Description

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

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

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

{3750} This statistic is obtained by measuring the number of PAGING REQUESTmessages sent on the PCH. This statistic counts the number of attempts.

The bins are:


0 ACCESS_PER_PCH_PS_CS Both CS and PS pages within thePAGING REQUEST message.

1 ACCESS_PER_PCH_CS Only CS pages within the PAGINGREQUEST message

2 ACCESS_PER_PCH_PS Only PS pages within the PAGINGREQUEST message.

Pegging

This statistic pegs received requests that:

S Succeeded (resulting in channel assignment).

S Failed (did not result in channel assignment).

Analysis

This statistic can be used for trend analysis of Paging Request messages sent on thePCH 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.


Network planning.

Basis Cell.

Type Counter array.

NOTE The ACCESS_PER_PCH statistic pegs a second time if the MSdoes not answer the first page. This is because there is no wayfor the BSS to distinguish between a retry of a page to one MSand an attempt to page a different mobile.

GSR6ACCESS_PER_RACH

14 Feb 20034–10


68P02901W56-L

ACCESS_PER_RACH

Description

The ACCESS_PER_RACH statistic tracks Channel Request messages received by theBSS on the Random Access CHannel (RACH) of a cell for Circuit Switched (CS) andPacket Switched (PS) related messages.

A Channel Request message is used by the MS to request allocation of a dedicatedchannel (to be used as an SDCCH) by the network, in response to a paging message(incoming call) from the network or as a result of an outgoing call/supplementary shortmessage service dialled from the MS. It is also used as part of the call re-establishmentprocedure.

Pegging

This statistic pegs received requests that:

S Succeeded (resulting in channel assignment).

S Failed (did not result in channel assignment).

Analysis

This statistic can be used for trend analysis of Channel Request messages sent on theRACH 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 and 9.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.


Network planning.

Basis Cell.

Type Counter.

NOTE This statistic is affected by phantom RACHs. The counter isincremented at least once for each phantom RACH.

GSR6 ALLOC_SDCCH

14 Feb 2003


68P02901W56-L 4–11

ALLOC_SDCCH

Description

The ALLOC_SDCCH statistic is the sum of the number of times a SDCCH issuccessfully seized. If a TCH is reconfigured as an SDCCH, only the SDCCH statisticswill be configured.

A Channel Request message is used by the MS to request allocation of a dedicatedchannel (to be used as an SDCCH) by the network, in response to a paging message(incoming call) from the network or as a result of an outgoing call/supplementary shortmessage service dialled from the MS. It is also used as part of the call re-establishmentprocedure.

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

Pegging

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

S Successful handover on an SDCCH channel.

S Successful immediate assignment on an SDCCH channel.

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

Analysis

This 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.2to 9.1.4, 9.1.14 to 9.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.

NOTE This statistic is affected by phantom RACHs.

GSR6ALLOC_SDCCH_FAIL

14 Feb 20034–12


68P02901W56-L

ALLOC_SDCCH_FAIL

Description

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

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

Pegging

This statistic pegs when an Immediate Assignment Reject message is sent to the MS inresponse to a channel request because no SDCCH channels were available to beallocated. It is also pegged in the target cell when rejecting a handover due to a lack ofresources.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof SDCCH failures 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.


Network planning.

Fault finding.

Optimization.

Ladder: Immediate assignment blocked,Connection establishment.

Key statistic : SDCCH_CONGESTION.

Basis Cell.

Type Counter.

Alarm Major.


GSR6 ALLOC_TCH

14 Feb 2003


68P02901W56-L 4–13

ALLOC_TCH

Description

The ALLOC_TCH statistic tracks the number of successful TCH allocations within a cellfor both call originations and hand ins.

Pegging

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

S Successful allocation due to call establishment including successful allocations dueto directed retries.

S Successful allocation due to intra-cell hand in.

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

S Successful allocation due to inter-BSS hand in.

This statistic pegs before the transmission of the assignment/handover command to theMS and, therefore, does not take into account the success or failure of theassignment/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-BSShandover, Intra-cell handover, Assignment toTCH.

Key statistics: TCH_MEAN_ARRIVAL_RATE,TCH_MEAN_HOLDING_TIME ,CELL_TCH_ASSIGNMENTS ,TCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.

GSR6ALLOC_TCH_FAIL

14 Feb 20034–14


68P02901W56-L

ALLOC_TCH_FAIL

Description

The ALLOC_TCH_FAIL statistic tracks the number of unsuccessful allocations of a TCHwithin a cell for both call origination and hand in. Cases involving Immediate AssignmentReject 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 ofresources:

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


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

S Unsuccessful allocation due to inter-BSS hand in.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof TCH failures due to congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 25. CELL: Attempt at allocating an TCHfailed – PM alarm is generated. Refer to the Maintenance Information: Alarm Handling atthe OMC-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.

GSR6 ASSIGNMENT_REDIRECTION

14 Feb 2003


68P02901W56-L 4–15

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 wereexecuted as the result of standarddirected retry.

1 DURING_ASSIGNMENTS Tracks the handovers that occurredduring the assignment for normalradio reasons.

2 MULTIBAND_BAND Tracks the handovers that wereexecuted as the result of multibandreassign procedure.

Pegging

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

Analysis

This statistic can be used for trend analysis of the number of successful internal andexternal handovers 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.


Network planning.

Basis Cell.

Type Counter array.

GSR6AVAILABLE_SDCCH

14 Feb 20034–16


68P02901W56-L

AVAILABLE_SDCCH

Description

The AVAILABLE_SDCCH statistic tracks the average number of available SDCCHs thatare in use or available for use.

The SDCCH is available when its administrative state is unlocked or shutting downand its operational state is enabled. The SDCCH is unavailable when its administrativestate is locked and its operational state is disabled.

Pegging

{3750} The statistic pegs whenever there is a change in the channel configuration forany channel in the cell (if the number of TCHs has not changed, it will be pegged withthe same value as before).

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

Analysis

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

By comparing the number of available SDCCHs to the total number of SDCCHs in asystem, a percentage of utilization can be calculated. An analysis of the utilizationinformation can be used to determine the requirement for additional resources beforeproblems occur.

Reference GSM 12.04, 4.2.1, B.2.1.21

Usage Congestion.

Network planning.

Basis Cell.

Type Gauge.

GSR6 AVAILABLE_TCH

14 Feb 2003


68P02901W56-L 4–17

AVAILABLE_TCH

Description

{3750} The AVAILABLE_TCH statistic tracks the mean and max number of availableTCHs that are in use or available for use.

The TCH is available when its administrative state is unlocked or shutting down andits operational state is enabled. The TCH is unavailable when its administrative state islocked and its operational state is disabled.

{3750} This statistic is modified to exclude all PDTCHs, both switchable and reservedunless the switchable PDTCH is configured as TCH.

{3750} This statistic is obtained by maintaining the current and total number of availableTCH and the amount of time each TCH is available over the statistical period. Thecorresponding mean and maximum number of TCH available are then computed. TheTCH is available when its administrative state is unlocked or shutting down and theoperational state is enabled and is unavailable when the its administrative state changesto locked or the operational state changes to disabled. The available number of TCH isthen incremented or decremented when there is a change in TCH states as describedabove.

{3750} This statistic only counts those traffic channels, which are configured as TCH atthe time of measurement. Switchable PDTCHs will be included only if they are configuredas TCHs.

Pegging

{3750} The statistic pegs whenever there is a change in the channel configuration forany channel in the cell (if the number of TCHs has not changed, it will be pegged withthe same value as before).

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

Analysis

This 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, apercentage of utilization can be calculated. An analysis of the utilization information canbe used to determine the requirement for additional resources before problems occur.

Reference GSM 12.04, 4.2.1, B.2.1.10

Usage Congestion.

Network planning.

Basis Cell.

Type Gauge.

GSR6BAD_HO_REFNUM_MS

14 Feb 20034–18


68P02901W56-L

BAD_HO_REFNUM_MS

Description

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

Pegging

This statistic is pegged once for each time a MS has accessed a channel with aHandover Reference Number that the BSS was not expecting. This field is anunformatted random number. The BSS only compares what it received with what itexpected, for example, potentially up to four times for each logical handover detect forthe SDCCH processed at the BSS.

The MS will continue to attempt access until a good Handover Reference Number isreceived, therefore, the handover can be successful and the statistic will still peg. Thisstatistics pegs if the handover fails and recovers, or fails and loses the mobile.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof MS accesses of channels with Handover Reference Numbers that the BSS was notexpecting that are acceptable in normal system operations.

High values reported for this statistic may not be because a handover access meant forone cell can be detected by another, but the channel at the target cell is susceptibleduring the time between channel activation and when the MS actually arrives. This issimilar to “Phantom RACHs.”

If the specified threshold is exceeded, the 19. CELL: Bad HO reference numbers fromthe MS – PM alarm will be generated. Refer to the Maintenance Information: AlarmHandling at 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.

GSR6 BUSY_SDCCH

14 Feb 2003


68P02901W56-L 4–19

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 theaverage number of SDCCHs in use during the interval.

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

This statistic is affected by phantom RACHs.

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

Pegging

The individual bin values are incremented by the length of time that the number ofallocated SDCCHs fall within the bin range of values. Bin values are pegged each time aSDCCH is allocated or de-allocated.

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

Analysis

This 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.


Network planning.

Optimization.

Key statistic: SDCCH_MEAN_HOLDING_TIME,SDCCH _TRAFFIC_CARRIED.

Basis Cell.

Type Weighted distribution.

GSR6BUSY_TCH

14 Feb 20034–20


68P02901W56-L

BUSY_TCH

Description:

The BUSY_TCH statistic tracks the number of TCHs allocated during an interval.

This is a weighted distribution statistic and produces a mean value indicating the averagenumber of TCHs in use during the interval. It is an indication of the average capacity foradditional traffic in the cell. This statistic includes TCHs used as a Dedicated ControlCHannel (DCCH) in immediate assignment mode. The BUSY_TCH time includes theguard time (the time allowed between ending a call and being allowed to start another).Since the channel is not available to be used again until the guard timer expires, it is notconsidered to be free until then.

The bin ranges may be changed using the chg_stat_prop command. The default binranges for 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 ofallocated TCHs fall within the bin range of values. Bin values peg each time a TCH isallocated or de-allocated.

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

Analysis

The value of this statistic is not dependent on the number of transceivers. Rather it isdependent on the number (however large) of simultaneously busy channels. The onlydependence on the number of transceivers is that the value reported may be larger ifmore traffic channels are used simultaneously.

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

GSR6 BUSY_TCH

14 Feb 2003


68P02901W56-L 4–21

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.


Network planning.

Optimization.

Key statistic: TCH_MEAN_HOLDING_TIME ,TCH_TRAFFIC_CARRIED.

Basis Cell.


GSR6BUSY_TCH_CARR

14 Feb 20034–22


68P02901W56-L

BUSY_TCH_CARR

Description

The BUSY_TCH_CARR statistic tracks the number of TCHs allocated during an interval.

This is a gauge 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 additionaltraffic in the cell. This statistic includes TCHs used as a Dedicated Control CHannel(DCCH) in immediate assignment mode. The BUSY_TCH_CARR time includes theguard time (the time allowed between ending a call and being allowed to start another).Since the channel is not available to be used again until the guard timer expires, it is notconsidered to be free until then.

Pegging

This statistic pegs when a change in the number of TCHs in use is detected.

Analysis

This statistic can be used for trend analysis of the amount of RF signalling traffic in thecell TCHs. 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, B1.1.1.GSM 4.08, 3.8.0, 3.3.1.2.1.

Usage Congestion.

Network planning.

Optimization.

Basis Carrier.

Type Gauge.

GSR6 CALL_SP_VERS_REQUEST_MONITOR

14 Feb 2003


68P02901W56-L 4–23

CALL_SP_VERS_REQUEST_MONITOR{3938}

DescriptionThis statistic tracks the number of call rejects and call downgrades due to not supportingrequested speech versions.


0 EFR_REQ_REJECT Pegged when the call is rejecteddue to CIC capabilities:

Assignment request for or includingEFR

Handover request for or includingEFR

In-call modification request for orincluding EFR

1 EFR_REQ_DOWNGRADE Pegged when the call isdowngraded due to CIC capabilities:

Assignment request for or includingEFR

Handover request for or includingEFR

In-call modification request for orincluding EFR

2 AMR_CALL_REQUEST Pegged when the AMR call isrequested:

Assignment request for or includingAMR

Handover request for or includingAMR

In-call modification request for orincluding AMR

PeggingThe bin corresponding to the cause of the call downgrade or reject is as indicated indescription above.

AnalysisThis statistic can be used for analysis of non-support of requested speech versions. Noalarms are raised by this statistic.

Reference GSM 08.08



Network planning.

Optimization.

Basis BSS.

Type Counter array.

GSR6CALLS_QUEUED

14 Feb 20034–24


68P02901W56-L

CALLS_QUEUED

Description

The CALLS_QUEUED statistic tracks the Assignment Requests that are queued duringan interval. If queuing has been allowed and no resources exist, the CRM queues anassignment request and informs the RRSM with a force queue message.

This statistic does not track handovers.

Pegging

This statistic pegs when queueing is enabled in an assignment request and availablequeue blocks are used to queue the call successfully.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof calls queued for each cell on the BSS that are acceptable in normal systemoperations.

If the specified threshold is exceeded, the 20. CELL: Number of calls queued – PMalarm will be generated. Refer to the Maintenance Information: Alarm Handling at theOMC-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.

GSR6 CHAN_REQ_CAUSE_ATMPT

14 Feb 2003


68P02901W56-L 4–25

CHAN_REQ_CAUSE_ATMPT

Description

The CHAN_REQ_CAUSE_ATMPT statistic tracks the number of Channel Requestmessages received by the network from a MS (or LMU) by cause. A total count of allsuccessful results is also tracked.


0 ORIGINATING_CALL Number of MS requests fororiginating service.

1 EMERGENCY_CALL Number of MS requests foremergency call service.

2 CM_REESTABLISH Number of failed MS requests forservice in which the call recoveredto the original cell.

3 LOCATION_UPDATE Number of MS location updaterequests.

4 PAGE_RESPONSE Number of MS page requestresponses.

5 {3974}LMU_ESTABLISHMENT Number of channel requests fromLocation Measurement Unit devices.(An LMU is a special device usedfor certain kinds of LocationServices).

Pegging

This statistic pegs the cause of each Channel Request message received by the networkfrom a MS.

Analysis

This statistic can be used for trend analysis of the type of Channel Request messagesthat are received from MSs. This information can be used to used to determine therequirement for additional resources before problems occur.

Reference GSM 12.04, 4.21, B.2.1.6.

GSM 4.08, v4.15.0, 9.1.8.



Network planning.

Basis Cell.

Type Counter array.

GSR6CHAN_REQ_MS_BLK

14 Feb 20034–26


68P02901W56-L

CHAN_REQ_MS_BLK

Description

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

An Immediate Assignment Reject message was sent to the MS on CCCH. This eventindicates that the MS has requested allocation of a dedicated channel, and the networkhas responded by refusing immediate access to a channel. Pegging of this counterindicates that there are no channels available for assignment in the cell. The counterpegs once for each Channel Request Reference in the message announcing theblocking. The cell is therefore fully used, and it will not be possible to hand over existingcalls 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 aradio resource, it will be impossible for the MS to initiate a call. Handover of calls may beprevented. This will result in call blocking and loss.

Pegging

This statistic pegs when an Immediate Assignment Reject message is sent to the MS onCCCH thus indicating that there are no channels available for assignment in the cell.

Analysis

This statistic can be used for trend analysis of the number of times channel access hasbeen denied. This information can be used to used to determine the requirement foradditional 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.


GSR6 CHAN_REQ_MS_FAIL

14 Feb 2003


68P02901W56-L 4–27

CHAN_REQ_MS_FAIL

Description

This statistic is the number of times that the BSS times out waiting for the MS toestablish on the SDCCH that was assigned to it during the immediate assignmentprocedure (see Chapter 6, Carrier and timeslot statistics, CHAN_REQ_MS_FAIL)

GSR6CIPHER_MODE_FAIL

14 Feb 20034–28


68P02901W56-L

CIPHER_MODE_FAIL

Description

The CIPHER_MODE_FAIL statistic pegs when an internal Motorola-defined timer in theBSS expires to indicate that the MS did not respond to the Cipher Mode Commandmessage with the Cipher Mode Complete message within the allowable time period orresponded improperly. It indicates that the MS probably did not switch correctly intoencrypted communication mode when commanded to do so.

Pegging

This statistic pegs when the MS fails to respond to a Cipher Mode Command from theBSS.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof times that MS failures to respond to BSS Cipher Mode Command messages areacceptable 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: AlarmHandling at 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.


Fault finding.

Ladder: BSS initiated call clearing.

Basis Cell.

Type Counter.

Alarm Minor.

GSR6 CLASSMK_UPDATE_FAIL

14 Feb 2003


68P02901W56-L 4–29

CLASSMK_UPDATE_FAIL

Description

The CLASSMK_UPDATE_FAIL statistic tracks the number of classmark updatescontaining errors. The classmark update procedure allows the MS to inform the networkof a change to its classmark.

Pegging

This statistic pegs when the validation of the Classmark Update message from the MSfails.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof classmark updates containing errors that are acceptable in normal system operations.

If the specified threshold is exceeded, the 4. CELL: Class-mark update from MSprotocol error – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-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.


Fault finding.

Basis Cell.

Type Counter.

Alarm Minor.

GSR6CLR_CMD_FROM_MSC

14 Feb 20034–30


68P02901W56-L

CLR_CMD_FROM_MSC

Description

The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commandsreceived from the MSC for SDCCH and TCH resources thereby allowing the analysis ofdropped calls.

Pegging

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


0 CLR_CMD_FROM_MSC_SD Counts the number of clearcommands received from the MSCfor an SDCCH.

1 CLR_CMD_FROM_MSC_FR Counts the number of clearcommands received from the MSCfor a Full Rate TCH.

2 CLR_CMD_FROM_MSC_HR Counts the number of clearcommands received from the MSCfor a Half Rate TCH.

Analysis

This statistic can be used for trend analysis of the number of Clear commands receivedfrom the MSC. This information can be used to identify and correct problems before theybecome 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.



Fault finding.

Network planning.

Basis Cell.

Type Counter array.

GSR6 CLR_REQ_TO_MSC

14 Feb 2003


68P02901W56-L 4–31

CLR_REQ_TO_MSC

Description

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

Generating

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

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

S Radio interface message failure.

S Protocol error.

S Ciphering algorithm not supported.

Sending

All Clear Requests are sent per GSM 8.08 specifications. The Clear Request messagesare sent to the MSC because of radio channel failure or a timeout during a procedure. Inthis case a timeout means a required message was not received during a procedure.The procedures are:

S Immediate Assignment.

S Assignment.

S Channel Mode Modify.

S Ciphering.

S Handover – Intra-cell, Inter-cell and External.

Pegging

This statistic pegs when the BSS sends a Clear Request message to the MSC.CLR_REQ_TO_MSC is pegged for numerous reasons related to timer expiry. It is a mixof both GSM and internal Motorola timers. Normal release of a call either from a MS orLand site never cause it to be pegged. A call must have at least been assigned to anSDCCH or TCH in order for this to be pegged. It is not pegged when on an AGCHoverload. RF loss is the major cause of pegging.


0 CLR_REQ_TO_MSC_SD Counts the number of clear requestssent to the MSC for an SDCCH.

1 CLR_REQ_TO_MSC_FR Counts the number of clear requestssent to the MSC for a Full RateTCH.

2 CLR_REQ_TO_MSC_HR Counts the number of clear requestssent to the MSC for a Half RateTCH.

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 noassociated statistic is pegged. For example, if during an assignment the BSS determinesthat the cell is barred, CLR_REQ_TO_MSC is pegged but no associated statistic ispegged.

GSR6CLR_REQ_TO_MSC

14 Feb 20034–32


68P02901W56-L

Analysis

This statistic can be used for trend analysis of the number of Clear Request messagessent to the MSC. This information can be used to identify and correct problems beforethey 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.



Fault finding.

Network planning.

Ladder : BSS initiated call clearing, handover(Intra-cell) fail/lost, handover (Intra-BSS) fail/lost.

NOTE Adding up the statistics in the ladder diagrams will not totalCLR_REQ_TO_MSC.

Basis Cell.

Type Counter array.

GSR6 CONGEST_EXIST_HO_ATMPT

14 Feb 2003


68P02901W56-L 4–33

CONGEST_EXIST_HO_ATMPT

Description

The CONGEST_EXIST_HO_ATMPT statistic tracks the number of attempted inter-cellhandovers (internal or external to the BSS) of calls on a TCH due to TCH congestionfrom the source cell.

Pegging

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

Analysis

This statistic can be used for trend analysis of the number of internal and externalhandovers attempts due to TCH congestion from source cells.


GSM 3.09, 4.50.

GSM 4.08, 4.11.0.

Usage Optimization.

Network planning.

Basis Cell.

Type Counter.

GSR6CONGEST_STAND_HO_ATMPT

14 Feb 20034–34


68P02901W56-L

CONGEST_STAND_HO_ATMPT

Description

The CONGEST_STAND_HO_ATMPT statistic tracks the number of attemptedhandovers of a MS due to standard Directed Retry procedure caused by TCH congestionfrom the source cell. These inter-cell handovers (internal or external to the BSS) involvechanging the channel mode during the handover.

Pegging

This statistic pegs each time a Directed Retry handover procedure is attempted for bothinter-cell and external handovers.

Analysis

This statistic can be used for trend analysis of the number of attempted internal orexternal handovers due to standard Directed Retry mechanisms caused by TCHcongestion.


GSM 3.09, 4.50.

GSM 4.08, 4.11.0.

Usage Optimization.

Network planning.

Basis Cell.

Type Counter.

GSR6 CONN_REFUSED

14 Feb 2003


68P02901W56-L 4–35

CONN_REFUSED

Description

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

Pegging

This 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 aBSS generated SCCP Connection Request (CR) message, as a result of

S MS access for a location update.

S MS originated call establishment.

S MS terminated call establishment.

S SMS activity.

S Supplementary service activity.

S IMSI detach.

S Call re-establishment.

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

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

NOTE Some MSCs may generate a Connection Refused Messageduring a successful IMSI Detach rather than a ConnectionConfirm, so a high value for the CONN_REFUSED statistic maynot indicate a system problem. The MSC performance duringIMSI Detach procedures should be investigated beforeinterpreting the CONN_REFUSED statistic.

Analysis

This statistic can be used for trend analysis of the reasons for connections refused fromthe 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.


Optimization.

Network planning.

Ladder: Connection establishment failure.

Basis Cell.

Type Counter.

GSR6CONN_REQ_TO_MSC

14 Feb 20034–36


68P02901W56-L

CONN_REQ_TO_MSC

Description

The CONN_REQ_TO_MSC statistic tracks the number of connection requests that theBSS sends to the MSC.

Pegging

The statistic pegs only for connection establishments initiated by the BSS. Thismessage is sent by the MS when it is requesting set-up of the connections for severaltypes of transactions, including location updates, connection establishments (includingre-establishment on failure, short message transfer, and supplementary servicerequests), and paging responses.

Analysis

This statistic can be used for trend analysis of the number of connection requests sentfrom the BSS to the MSC.

Reference GSM 8.06, 3.5.0, 6.1.

GSM 8.08, 3.9.2, 3.1.16.


Network planning.

Ladder: Connection establishment successful,connection establishment failure.

Basis Cell.

Type Counter.

GSR6 DYNET_ASSIGN_FAIL

14 Feb 2003


68P02901W56-L 4–37

DYNET_ASSIGN_FAIL

Description

The DYNET_ASSIGN_FAIL statistic tracks the number of times assignments have faileddue to insufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.

Pegging

This statistic pegs each time an assignment procedure fails due to the lack of terrestrialbacking resources.

Usage Quality of service monitoring.


Network planning.

Basis BSS.

Type Counter.

Alarm None.

GSR6DYNET_CALL_REJECTS

14 Feb 20034–38


68P02901W56-L

DYNET_CALL_REJECTS

Description

The DYNET_CALL_REJECTS statistic tracks the number of times calls have beenblocked or preempted due to insufficient terrestrial backhaul resources on a BTSDynamic Allocation Network.

Bin Procedures Description

0 NON_EMRG_CALL_BLK A non-emergency call is notallocated a TCH due to the lack ofterrestrial backing resources in aBTS network.

1 EMRG_CALL_BLK An emergency call is not allocated aTCH due to the lack of terrestrialbacking resources in a BTSnetwork.

2 NON_EMRG_RESERVED A non-emergency call is notallocated a TCH due to the cellexceeding its reserve amount ofterrestrial backing resources and nofurther backing resources areavailable.

3 NON_EMRG_PREEMP A non-emergency call is preemptedto provide terrestrial backingresources for an emergency call.

4 LOSS_OF_RESOURCES An emergency or non-emergencycall is preempted due to the loss ofof terrestrial backing resources.

Pegging

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


Networking planning.


Basis DYNET.

Type Counter array.

Alarm None.

GSR6 ER_INTRA_CELL_HO_ATMPT

14 Feb 2003


68P02901W56-L 4–39

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 rangecell. A total count of attempted handover is also maintained.

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


0 NORM_TO_EXT_HO Number of intra-cell handoverattempts from normal rangechannels to extended rangechannels.

1 EXT_TO_NORM_HO Number of intra-cell handoverattempts from extended rangechannels to normal range channels.

Pegging

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

Analysis

This statistic can be used for trend analysis of the attempted intra-cell handoversbetween normal and extended range channels in an extended range cell. The number ofattempted extended range intra-cell handovers can be used to determine the number ofextended range timeslots to configure in an extended range cell.

Reference None.


Network planning.


Basis Cell.

Type Counter array.

GSR6ER_INTRA_CELL_HO_SUC

14 Feb 20034–40


68P02901W56-L

ER_INTRA_CELL_HO_SUC

Description

The ER_INTRA_CELL_HO_SUC tracks the number of successful intra-cell handoversbetween normal range and extended range channels in an extended range cell. Thevalues reported for this statistic can be used to configure normal and extended rangetraffic 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 andenabled for the cell.


0 NORM_TO_EXT_HO Number of successful intra-cellhandovers from normal rangechannels to extended rangechannels.

1 EXT_TO_NORM_HO Number of successful intra-cellhandovers from extended rangechannels to normal range channels.

Pegging

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

Analysis

This statistic can be used for trend analysis of the successful intra-cell handoversbetween normal and extended range channels in an extended range cell. The number ofsuccessful extended range intra-cell handovers can be used to determine the number ofextended range timeslots to configure in an extended range cell.

Reference None.


Network planning.


Basis Cell.

Type Counter array.

GSR6 FLOW_CONTROL_BARRED

14 Feb 2003


68P02901W56-L 4–41

FLOW_CONTROL_BARRED

Description

The FLOW_CONTROL_BARRED statistic tracks the duration for which access classesare barred as a result of flow control. This statistic gives an indication when flow controlactions have been taken to prevent overload.

Pegging

The statistic duration is 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 isunbarred.

Analysis

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

Usage Quality of Service.

Network Planning.

Optimization.

Basis Cell.

Type Duration (total time).

GSR6HO_FAIL_NO_RESOURCES

14 Feb 20034–42


68P02901W56-L

HO_FAIL_NO_RESOURCES

Description

The HO_FAIL_NO_RESOURCES tracks the number of handover failures due to a lackof available resources.

Bin Scenario Description

0 INTRA_BSS Number of intra-BSS handoverfailures due to a lack of availableresources.

1 INTER_BSS Number of inter-BSS handoverfailures due to a lack of availableresources.

2 INTRA_CELL Number of intra-cell handoverfailures due to a lack of availableresources.

3 INTRA_BSS_DYNET Number of BTS Dynamic Allocationintra-BSS handover failures due to alack of available resources.

4 INTER_BSS_DYNET Number of BTS Dynamic Allocationinter-cell handover failures due to alack of available resources.

5 INTRA_CELL_DYNET Number of BTS Dynamic Allocationintra-cell handover failures due to alack of available resources.

Pegging

These individual bins are incremented on a per scenario basis.

Analysis

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

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

S The channel is unavailable, that is there is congestion at the target cell and thequeue timer is expired.

S Incoming handovers are turned off at the target.

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

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

Reference Metrica.



Network planning.

Basis Cell.

Type Counter array.

GSR6 HO_REQ_MSC_FAIL

14 Feb 2003


68P02901W56-L 4–43

HO_REQ_MSC_FAIL

Description

The HO_REQ_MSC_FAIL statistic tracks the number of handover request failuremessages sent to the MSC, except for no channel resources available. This message issent to notify the MSC that the BSS could not reserve the radio resource that the MSCrequested in the Handover Request message.

Pegging

This 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 thetarget cell. This could indicate one of the following problems: terrestrial circuitunavailable, terrestrial circuit in use, ciphering algorithm not supported, or radioresources unavailable.

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

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof handover failures for any reason other than lack of channel resources that areacceptable in normal system operations.

If the specified threshold is exceeded, the 18. CELL: HO failure to the MSC due to allpossible errors except no channels – PM alarm is generated. Refer to theMaintenance Information: Alarm Handling at the OMC-R (68P02901W26) fortroubleshooting 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.

NOTE HO_REQ_MSC_FAIL can be equal to INTER_BSS_MS_FAIL ifthe cell has never been the target for a failed handover.

GSR6HO_REQ_MSC_OK

14 Feb 20034–44


68P02901W56-L

HO_REQ_MSC_OK

Description

The HO_REQ_MSC_OK statistic tracks the number of handover acknowledge messagessent to the MSC by the destination cell in an inter-BSS (external) handover.

Pegging

This statistic pegs when the BSS sends a Handover Request Acknowledge message tothe MSC. This message is sent to notify the MSC that the BSS has reserved the radioresource that the MSC asked for in the Handover Request message.

Analysis

This statistic can be used for trend analysis of successful radio resource reservations bythe BSS in response to MSC Handover Request messages.

Reference GSM 8.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.

Type Counter.

GSR6 IDLE_TCH_INTF_BAND0

14 Feb 2003


68P02901W56-L 4–45

IDLE_TCH_INTF_BAND0

Description

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

NOTE Idle TCHs are allocated to five interference bands. Each bandhas an associated statistic for tracking idle TCHs.

Pegging

This statistic is reported periodically using the rf_res_ind_period element.

Analysis

This 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.

GSR6IDLE_TCH_INTF_BAND1

14 Feb 20034–46


68P02901W56-L

IDLE_TCH_INTF_BAND1

Description



Pegging


Analysis


Reference GSM 12.04, 4.2.1, B.2.1.13.


Fault finding.

Basis Cell.

Type Gauge.


14 Feb 2003


68P02901W56-L 4–47

IDLE_TCH_INTF_BAND2

Description



Pegging


Analysis


Reference GSM 12.04, 4.2.1, B.2.1.13.


Fault finding.

Basis Cell.

Type Gauge.

GSR6IDLE_TCH_INTF_BAND3

14 Feb 20034–48


68P02901W56-L

IDLE_TCH_INTF_BAND3

Description



Pegging


Analysis


Reference GSM 12.04, 4.2.1, B.2.1.13.


Fault finding.

Basis Cell.

Type Gauge.


14 Feb 2003


68P02901W56-L 4–49

IDLE_TCH_INTF_BAND4

Description



Pegging


Analysis


Reference GSM 12.04, 4.2.1, B.2.1.13.


Fault finding.

Basis Cell.

Type Gauge.

GSR6IN_INTER_BSS_HO

14 Feb 20034–50


68P02901W56-L

IN_INTER_BSS_HO

Description

The IN_INTER_BSS_HO statistic tracks incoming inter-BSS handover procedures on aper scenario basis. A total value for this statistic is not meaningful and is not displayed.


0 IN_INTER_BSS_HO_SUC Number of successful incominginter-BSS handovers.

1 IN_INTER_BSS_MS_NO_SEIZE Number of times an MS does notseize an allocated channel.

This statistic is not currentlypegged.

2 IN_INTER_BSS_EQUIP_FAIL Number of incoming inter-BSShandovers that fail due to equipmentfailure.

3 IN_INTER_BSS_HO_CLEARED Number of incoming inter-BSShandovers aborted due to callclearing. This scenario correspondsto the receipt of a Clear Command,SCCP Released, or Release Done(internal message) during thehandover procedure.

Pegging

These individual bins are incremented on a per cause basis.

Analysis

This statistic can be used for trend analysis of incoming inter-BSS handover procedureson a per scenario basis.

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



Network planning.

Fault finding.

Handover.

Basis Cell.

Type Counter array.

GSR6 IN_INTRA_BSS_HO

14 Feb 2003


68P02901W56-L 4–51

IN_INTRA_BSS_HO

Description

The IN_INTRA_BSS_HO statistic tracks incoming intra-BSS handover procedures on aper scenario basis. A total value for this statistic is not meaningful and is not displayed.


0 IN_INTRA_BSS_HO_SUC Number of successful incomingintra-cell handovers.

1 IN_INTRA_BSS_HO_LOSTMS Number of failed incoming intra-BSShandovers that also failed to recoverto the original cell.

2 IN_INTRA_BSS_EQUIP_FAIL Number of failed incoming intra-BSShandovers that fail due to equipmentfailure.

3 IN_INTRA_BSS_HO_RETURN Number of failed incoming intra-BSShandovers that recover to theoriginal cell/channel.

4 IN_INTRA_BSS_HO_CLEARED Number of incoming intra-BSShandovers aborted due to callclearing. This scenario correspondsto the receipt of a Clear Command,SCCP Released, or Release Done(internal message) during thehandover procedure.

Pegging

These individual bins are incremented on a per scenario basis.

Analysis

This statistic can be used for trend analysis of incoming intra-BSS handover procedureson a per scenario basis.

Reference Metrica.

GSM 8.08, 3.9.2, 3.1.7, 3.1.5.2.1, 3.2.1.12.



Network planning.

Service retainability.

Fault finding.

Handover.

Basis Cell.

Type Counter array.

GSR6INTERBAND_ACTIVITY

14 Feb 20034–52


68P02901W56-L

INTERBAND_ACTIVITY

Description

The INTERBAND_ACTIVITY statistic tracks inter-band handover attempts in the BSS.Assignment and handover failures due to incorrect or unsupported frequency informationare also tracked. The Multiband option must be enabled for this statistic to be enabled,disabled, or displayed.


0 PGSM_HO_ATMPT Attempts to handover to base GSMband.

1 EGSM_HO_ATMPT Attempts to handover to extendedGSM band.

2 DCS1800_HO_ATMPT Attempts to handover to DSC1800band.

3 PCS1900_HO_ATMPT Attempts to handover to PCS1900band.

4 PGSM_HO_FAIL Handover failures to base GSMband.

5 EGSM_HO_FAIL Handover failures to extended GSMband.

6 DCS1800_HO_FAIL Handover failures to DCS1800band.

7 PCS1900_HO_FAIL Handover failures to PCS1900band.

8 INVALID_FREQ_ASGN Frequency not implemented forassignment request.

9 INVALID_FREQ_HO Frequency not implemented forhandover.

Pegging

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

Analysis

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

Reference None.

Usage Handover.


Network planning.


Basis Cell.

Type Counter array.

GSR6 INTRA_CELL_HO

14 Feb 2003


68P02901W56-L 4–53

INTRA_CELL_HO

Description

The INTRA_CELL_HO statistic tracks intra-cell handovers on a per scenario basis. Atotal 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 thehandover evaluator process.

1 INTRA_CELL_HO_ATMPT Number of assignment commands sent toMS during an intra-cell handover.

2 INTRA_CELL_HO_SUC Number of successful intra-cell handovers.

3 INTRA_CELL_HO_LOSTMS Number of failed intra-cell handovers thatalso failed to recover to the original cell.

4 INTRA_CELL_HO_RETURN Number of failed intra-cell handovers thatrecovered to the original cell/channel.

5 INTRA_CELL_EQUIP_FAIL Number of attempted intra-cell handoverfailures due to equipment failure.

6 INTRA_CELL_HO_CLEARED Number of incoming intra-cell handoversaborted due to call clearing. This scenariocorresponds to the receipt of a ClearCommand, SCCP Released, or ReleaseDone (internal message) during thehandover procedure.

Pegging

INTRA_CELL_HO_REQ is pegged just before sending the intra–cell handover message.

INTRA_CELL_HO_ATMPT is pegged after the channel activation message is receivedand just before the assignment command is sent to the MS.

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

INTRA_CELL_HO_LOSTMS is pegged when a radio channel released message isreceived.

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

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 anintra–cell handover.

Analysis

This statistic can be used for trend analysis of intra-cell handovers on a per scenariobasis.

GSR6INTRA_CELL_HO

14 Feb 20034–54


68P02901W56-L

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.



Network planning.

Fault finding.


Basis Cell.

Type Counter array.

GSR6 INV_EST_CAUSE_ON_RACH

14 Feb 2003


68P02901W56-L 4–55

INV_EST_CAUSE_ON_RACH

Description

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

Pegging

This statistic pegs when the establishment cause is not validated.

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

Analysis

This 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, and 9.2.4.

GSM 4.03, 3.03, and 4.3.2.1.

Usage Handover.


Fault finding.

Ladder: Immediate Assignment Failure.

Basis Cell.

Type Counter.

GSR6MA_CMD_TO_MS

14 Feb 20034–56


68P02901W56-L

MA_CMD_TO_MS

Description

The MA_CMD_TO_MS statistic tracks the number of Assignment Commands sent to theMS.

Pegging

This statistic pegs when the BSS initiates the channel assignment procedure by sendingan Assignment Command to the MS on the main SDCCH. Assignment Command issent to the MS at call setup (traffic channel assignment) and at intra-cell handovers. Thiscauses the MS to:

S Release its link layer connections.

S Disconnect from its current physical channels.

S Switch to the assigned channels.

S Initiate re-establishment of the lower layer connections.

Analysis

This statistic can be used for trend analysis of BSS initiated channel assignmentprocedures to the MS.

Reference GSM 4.08, 3.8.0, 3.4.3.1 and 9.1.2.


Call setup.

Ladder: TCH assignment successful, TCHassignment fail-recovered to SDCCH, handover(Intra-cell) successful, handover (Intra-cell)fail-recovered, handover (Intra-cell) fail-lost.

Basis Cell.

Type Counter.

GSR6 MA_COMPLETE_FROM_MS

14 Feb 2003


68P02901W56-L 4–57

MA_COMPLETE_FROM_MS

Description

The MA_COMPLETE_FROM_MS statistic tracks the number of Assignment Completemessages received from MSs.

Pegging

This statistic pegs when the BSS receives an Assignment Complete message from theMS.

Analysis

This statistic can be used for trend analysis.

Reference GSM 12.04, 4.2.1, B.2.1.15


Quality of service: Call set-up.

Network planning.

Ladder: TCH assignment successful.

Basis Cell.

Type Counter.

GSR6MA_COMPLETE_TO_MSC

14 Feb 20034–58


68P02901W56-L

MA_COMPLETE_TO_MSC

Description

The MA_COMPLETE_TO_MSC statistic tracks the number of successful TCH seizures.

Pegging

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

Analysis

This statistic can be used for trend analysis of successful TCH seizures.

Reference GSM 12.04, 4.2.1, B.2.1.15


Quality of service: Call set-up.

Network planning.


Basis Cell.

Type Counter.

GSR6 MA_FAIL_FROM_MS

14 Feb 2003


68P02901W56-L 4–59

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(traffic channel assignment) and at intra cell handovers.

Pegging

This statistic pegs when the BSS receives an Assignment Failure message from the MS.If the MS detects a lower layer failure on the new channels before the AssignmentComplete message has been sent:

S It deactivates the new channels.

S Reactivates the old channels.

S Reconnects any TCHs.

S Triggers establishment of the main signalling link.

S 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.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof assignment failures for MSs that are acceptable in normal system operations.

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


GSM 12.07, 3.0.2, 2.8.6.c.

GSM 4.08, 3.8.0, 3.4.3.3 and 9.1.4.


Quality of service monitoring: Call setup.

Fault finding.

Ladder: TCH assignment fail-recovered toSDCCH, handover (Intra-cell) fail-recovered.

Basis Cell.

Type Counter.

Alarm Warning.

GSR6MA_REQ_FROM_MSC

14 Feb 20034–60


68P02901W56-L

MA_REQ_FROM_MSC

Description

The MA_REQ_FROM_MSC statistic tracks the number of times the MSC asked the BSSto allocate radio resources. The MSC sends the BSS an Assignment request messagecontaining details of the type of resource required. The type of resource is based on theMSC analysis of the call control information received from the MS.

Pegging

This statistic pegs the radio resource request made to a BSS by the MSC.

Analysis

This statistic can be used for trend analysis of MSC request to the BSS to allocate radioresources.




Network planning.

Ladder: TCH assignment successful, TCHassignment fail-recovered to SDCCH, TCHassignment blocked.

Basis Cell.

Type Counter.

GSR6 MA_CMD_TO_MS_BLKD

14 Feb 2003


68P02901W56-L 4–61

MA_CMD_TO_MS_BLKD

Description

The MA_CMD_TO_MS_BLKD statistic tracks the number of times an assignmentrequest from the MSC could not be processed (assignment command could not begenerated and sent to the mobile station) as there were no traffic channels available atthe cell due to congestion.

Pegging

This statistic is pegged by the BSS when the MSC requests the BSS to allocate radioresource to an MS, and the BSS finds it has no channels available to allocate. Thepegging of this statistic indicates no channels were available in the currently allocatedcell. It is indicated by an Assignment Failure message with cause: No radio resourceavailable.

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

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof times traffic channels that may be congested due to a lack of radio resources that areacceptable in normal system operations.

If the specified threshold is exceeded, the 2. CELL: Mobile assign command to MSblocked (no channel available) – PM alarm is generated. Refer to the MaintenanceInformation: Alarm Handling at the OMC-R (68P02901W26) for troubleshootinginformation.



Quality of service monitoring: Call setup andhandover.

Fault finding.

Network planning.

Optimization.

Ladder: TCH assignment blocked.

Basis Cell.

Type Counter.

Alarm Minor.

GSR6MS_ACCESS_BY_TYPE

14 Feb 20034–62


68P02901W56-L

MS_ACCESS_BY_TYPE

Description

The MS_ACCESS_BY_TYPE statistic tracks the number of system accesses by thevarious types of 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 forthe 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, andDCS1800 bands.

6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.

7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, andPCS1900 bands.

Pegging

The MS_ACCESS_BY_TYPE statistic is pegged by RRSM after the sending of the initiallayer 3 information by the MS, on receipt of the classmark of the MS. It can also bepegged if the MS sends a CLASSMARK CHANGE message whilst in dedicated mode.

Analysis

This 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.

GSR6 MS_TCH_USAGE_BY_TYPE

14 Feb 2003


68P02901W56-L 4–63

MS_TCH_USAGE_BY_TYPE

Description

The MS_TCH_USAGE_BY_TYPE statistic tracks the length of time spent on TCHs bythe various types of MSs. Duration is measured in deciminutes. (One deciminute equalssix seconds. For example, if MS_TCH_USAGE_BY_TYPE = 31, the call duration was3.1 minutes or 186 seconds). The type of MS is included in the MS Classmark 3information.

This statistic may only be enabled if the Multiband feature is unrestricted and enabled forthe 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, andDCS1800 bands.

6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.

7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, andPCS1900 bands.

Pegging

Each bin is updated by the cell resource manager when the duration for an activechannel is recorded. A total duration is calculated which is the sum for all channelsusage time by MSs in a given cell.

Analysis

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

Usage Service accessibility.

Network planning.

Basis Cell.

Type Counter array.

GSR6MS_TCH_USAGE_BY_TYPE_PCS

14 Feb 20034–64


68P02901W56-L

MS_TCH_USAGE_BY_TYPE_PCS

Description

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

This statistic may only be enabled if either the PCS1900 or GSM850 frequency band isallowed on 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.

Pegging

Each bin is updated by the cell resource manager when the duration for an activechannel is recorded. A total duration is calculated which is the sum for all channelsusage time by MSs in a given cell.

Analysis

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


Network planning.

Basis Cell.

Type Counter array.

GSR6 MT_LCS_ON_SDCCH

14 Feb 2003


68P02901W56-L 4–65

MT_LCS_ON_SDCCH

Description

This statistic counts the number of mobile–terminated SDCCH sessions for LocationServices.

NOTE The statistic has been introduced to allow the Call SetupSuccess Rate key statistic (see Chapter 17) to work following theintroduction of the Location Services feature.

Pegging

This 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 anSDCCH. Any of the following messages received over the A–interface are consideredLCS transaction initiations: BSSLAP TA Request, BSSLAP MS Position Command,BSSMAP Perform Location Request (only applies in the case of a BSS based SMLC).

Reference GSM 03.71 v7.4.0.

Usage Fault finding.

Basis Cell.

Type Counter.

GSR6NUM_EMERG_ACCESS

14 Feb 20034–66


68P02901W56-L

NUM_EMERG_ACCESS

Description

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

Pegging

This statistic pegs after the receipt of an emergency RACH.

Analysis

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

Usage Quality of Service monitoring.

Network planning.

Basis Cell.

Type Counter.

GSR6 NUM_EMERG_REJECTED

14 Feb 2003


68P02901W56-L 4–67

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 resourcesand another call cannot be pre-empted to allow it access.

Pegging

This statistic pegs the number of emergency calls that are rejected because all channelswere occupied by other emergency or high priority calls.

Analysis

This statistic can be used for trend analysis of emergency call accesses that failedbecause all channels were occupied by other emergency or high priority calls.


Network planning.

Basis Cell.

Type Counter.

GSR6NUM_EMERG_TCH_KILL

14 Feb 20034–68


68P02901W56-L

NUM_EMERG_TCH_KILL

Description

The NUM_EMERG_TCH_KILL statistic tracks the number of times a call is lost due toemergency call 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.

Pegging

This statistic pegs the number of active calls that are terminated in order to make a TCHavailable for an emergency call. This situation arises if all TCHs are occupied and anemergency access requires a channel. This statistic pegs only if the emergencypre-emption feature is enabled.

Analysis

This statistic can be used for trend analysis of the number of times that calls are lost dueto emergency call pre-emption only.


Network planning.

Basis Cell

Type Counter.

GSR6 NUM_EMERG_TERM_SDCCH

14 Feb 2003


68P02901W56-L 4–69

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 wasallocated an SDCCH but could not be allocated a TCH.

Pegging

This statistic pegs each time an emergency call is assigned to an SDCCH but must beterminated because no TCHs are available to complete the call. This statistic is peggedregardless of the status of the emergency preemption feature.

Analysis

This statistic can be used for trend analysis of the number of times that emergencyaccesses are terminated after SDCCH congestion.


Network planning.

Basis Cell.

Type Counter.

GSR6OK_ACC_PROC

14 Feb 20034–70


68P02901W56-L

OK_ACC_PROC

Description

The OK_ACC_PROC tracks successful accesses by procedure. A total count of allsuccessful accesses is also maintained.

Bin Procedure Description

0 CM_SERV_REQ_CALL Number of MS requests fororiginating service.

1 CM_SERV_REQ_SMS Number of MS requests for SMSservice.

2 CM_SERV_REQ_SUPP Number of MS requests forsupplementary services.

3 CM_SERV_REQ_EMERG Number of MS requests foremergency call service.

4 CM_REESTABLISH Number of failed MS requests forservice in which the call recoveredto the original cell.

5 LOCATION_UPDATE Number of MS location updaterequests.

6 IMSI_DETACH Number of received IMSI detachmessages.

7 PAGE_RESPONSE Number of MS page requestresponses.

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 {3974}LOCATION _SERVICES Number of Location MeasurementUnit (LMU) service requests forlocation services.

NOTE LOCATION_SERVICES is stored in column cm_lcs_request ofthe OMC database.

Pegging

{3974}This statistic pegs the total number of successful results per procedure includinglocation services.

Analysis

This statistic can be used for trend analysis of the number of successful accesses byprocedure.

GSR6 OK_ACC_PROC

14 Feb 2003


68P02901W56-L 4–71

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.



Network planning.

Ladder: Immediate assignment successful.

Key Statistics: RF_LOSS_RATE,SDCCH_MEAN_HOLDING_TIME,SDCCH_MEAN_ARRIVAL_RATE,SDCCH_RF_LOSS_RATE.

Basis Cell.

Type Counter array.

GSR6OK_ACC_PROC_SUC_RACH

14 Feb 20034–72


68P02901W56-L

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 usedas a 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 dialledfrom the MS.

Pegging

This statistic pegs what it determines to be a valid Channel Request (RACH). This doesnot necessarily result in a seizure attempt of an SDCCH.

Analysis

This statistic can be used for trend analysis of the number of successful channelrequests 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 assignment successful,Immediate assignment blocked, Immediateassignment failure.

Basis Cell.

Type Counter.


GSR6 OUT_HO_CAUSE_ATMPT

14 Feb 2003


68P02901W56-L 4–73

OUT_HO_CAUSE_ATMPT

Description

The OUT_HO_CAUSE_ATMPT statistic tracks the number of handover attempts per cellper 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 source cell.

2 DOWNQUAL Number of times an outgoing inter-cell handover isattempted due to the Downlink signal quality in sourcecell.

3 DOWNLEVEL Number of times an outgoing inter-cell handover isattempted due to the Downlink signal level in sourcecell.

4 DISTANCE Number of times an outgoing inter-cell handover isattempted due to a weakening signal strength to/fromMS because of the distance from signal source.

5 UPINTERF Number of times an outgoing inter-cell handover isattempted due to the Uplink signal interference insource cell.

6 DOWNINTERF Number of times an outgoing inter-cell handover isattempted due to the Downlink signal interference insource 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) congestion inthe 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.

NOTE When a specific bin is included in descriptions or formulae in thismanual, the convention used for the presentation of the statisticand the bin identification will be OUT_HO_CAUSE_ATMPT[binname]. An example of this convention isOUT_HO_CAUSE_ATMPT[UPQUAL].

Pegging

This statistic pegs the total number of handover attempts out of a specific cell and thecause for each attempt. This statistic is pegged at the source cell.

GSR6OUT_HO_CAUSE_ATMPT

14 Feb 20034–74


68P02901W56-L

Analysis

This statistic can be used for trend analysis of the number of handover attempts per cellper 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.

GSR6 OUT_INTER_BSS_HO

14 Feb 2003


68P02901W56-L 4–75

OUT_INTER_BSS_HO

Description

The OUT_INTER_BSS_HO statistic tracks a range of handover actions associated withoutgoing inter-BSS handovers. A total value for this statistic is not meaningful and is notdisplayed.


0 OUT_INTER_BSS_REQ_TO_MSC Number of outgoing inter-BSShandover requests to the MSC.

1 OUT_INTER_BSS_HO_ATMPT Number of assignment commandssent to MS during an inter-BSShandover.

2 OUT_INTER_BSS_HO_SUC Number of successful inter-BSShandovers.

3 OUT_INTER_BSS_HO_LOSTMS Number of failed intra-BSShandovers in which the MS alsofailed to recover to the originalBSS.This statistic is not currentlypegged.

4 OUT_INTER_BSS_HO_RETURN Number of failed inter-BSShandovers in which the MSrecovered to the originalBSS/channel.

5 OUT_INTER_BSS_EQUIP_FAIL Number of attempted inter-BSShandover failures due to equipmentfailure.

6 OUT_INTER_BSS_HO_CLEARED Number of outgoing inter-BSShandovers aborted due to callclearing. This scenario correspondsto the receipt of a Clear Command,SCCP Released, or Release Done(internal message) during thehandover procedure.

Pegging

OUT_INTER_BSS_REQ_TO_MSC is pegged each time a handover required message issent to the MSC.

OUT_INTER_BSS_HO_ATMPT is pegged when the handover command is forwarded tothe 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 handovermessage 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 aninter–BSS handover.

GSR6OUT_INTER_BSS_HO

14 Feb 20034–76


68P02901W56-L

Analysis

This statistic can be used for trend analysis of inter-BSS handovers on a per handoverscenario 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.16 and 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.



Network planning.

Fault finding.


Basis Cell.

Type Counter array.

GSR6 OUT_INTRA_BSS_HO

14 Feb 2003


68P02901W56-L 4–77

OUT_INTRA_BSS_HO

Description

The OUT_INTRA_BSS_HO statistic tracks a range of handover actions associated withoutgoing intra-BSS handovers. A total value for this statistic is not meaningful and is notdisplayed.


0 OUT_INTRA_BSS_HO_REQ Number of times an intra-BSSHandover Recognized message isreceived. This message is sentwhen the system recognizes ahandover is needed.

1 OUT_INTRA_BSS_HO_PRI_BLK Number of times an intra-BSShandover to the primary target cellwas blocked.

2 OUT_INTRA_BSS_HO_ATMPT Number of assignment commandssent to MS during an intra-BSShandover.

3 OUT_INTRA_BSS_HO_SUC Number of successful intra-BSShandovers.

4 OUT_INTRA_BSS_HO_LOSTMS Number of failed intra-BSShandovers in which the MS alsofailed to recover to the original BSS.

5 OUT_INTRA_BSS_HO_RETURN Number of failed intra-BSShandovers in which the MSrecovered to the originalBSS/channel.

6 OUT_INTRA_BSS_EQUIP_FAIL Number of attempted intra-BSShandover failures due to equipmentfailure.

7 OUT_INTRA_BSS_HO_CLEARED Number of outgoing intra-BSShandovers aborted due to callclearing. This scenario correspondsto the receipt of a Clear Command,SCCP Released, or Release Done(internal message) during thehandover procedure.

GSR6OUT_INTRA_BSS_HO

14 Feb 20034–78


68P02901W56-L

Pegging

OUT_INTRA_BSS_HO_REQ is pegged each time an intra–BSS handover message isreceived.

OUT_INTRA_BSS_HO_PRI_BLK is pegged when resources not available message isreceived.

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 isreceived.

OUT_INTRA_BSS_EQUIP_FAIL is pegged when an assignment failure messagecontains an equipment failure cause or KSW/highway fault.

OUT_INTRA_BSS_HO_CLEARED is pegged when a call is cleared down during anintra–BSS handover.

Analysis

This 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 and3.2.1.12 & 3.2.1.25.

Metrica.



Network planning.

Fault finding.


Basis Cell.

Type Counter array.

GSR6 PAGE_REQ_FROM_MSC

14 Feb 2003


68P02901W56-L 4–79

PAGE_REQ_FROM_MSC

Description

The PAGE_REQ_FROM_MSC statistic tracks the number of paging requests receivedfrom the MSC.

This message is sent by the network when attempting to locate the MS. Each Pagemessage refers to only one MS. The BSS in turn transmits a paging message whichmay include identities for more than one MS (see ACCESS_PER_PCH).

Pegging

This statistic pegs the number of Paging messages received from the MSC by the BSS.This statistic is pegged when a Paging message is received pertaining to the cell in whichthe MS is paged.

Analysis

This statistic can be used for trend analysis of the number of paging requests receivedfrom 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.


Basis Cell.

Type Counter.

GSR6PAGING_REQUESTS

14 Feb 20034–80


68P02901W56-L

PAGING_REQUESTS

Description

{3750}This statistic accounts for any message making use of a PCH block. This statisticis similar to PCH_Q_PAGE_DISCARD except the messages are sent, not discarded.This statistic is obtained by measuring the number of paging requests received from thenetwork for transmission on the PCH.

The bins are:


0 PAGING_REQS_TOT Number of Paging requestsreceived to be transmitted on thePCH.

1 PAGING_REQS_CS Number of Paging requestsreceived to be transmitted on theCS .

2 PAGING_REQS_PS Number of Paging requestsreceived to be transmitted on thePS.

Pegging

This statistic pegs every multiframe for each message going over a paging block (PCH).

Analysis

This statistic can be used for trend analysis of the number of paging requests received.

Reference Reference Digital cellular telecommunicationssystems (phase 2+) Version 7.0.0 Jan 2000ETSI.


Basis Cell.

Type Counter array.

GSR6 PCH_AGCH_Q_LENGTH

14 Feb 2003


68P02901W56-L 4–81

PCH_AGCH_Q_LENGTH

Description

The PCH_AGCH_Q_LENGTH statistic tracks the mean number of messages reported inthe PCH-AGCH queue.

{3750} The statistic is modified to support Circuit Switched (CS) pages only.

Pegging

This statistic pegs once per paging multiframe, by summing the total number ofmessages in the paging queue. At the end of the interval, the mean number ofmessages are calculated and reported.

Analysis

The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCHqueue.

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.

GSR6PCH_Q_PAGE_DISCARD

14 Feb 20034–82


68P02901W56-L

PCH_Q_PAGE_DISCARD

Description

The PCH_Q_PAGE_DISCARD statistic tracks the number of paging messagesdiscarded from the PCH queue before they could be transmitted.

A page may be discarded from the queue for the following reasons: queue overflow,priority insertion causing an overflow, and an in_queue timer expiry. The only cause fordiscarding pages in the Motorola BSS is queue overflow.

{3750} The statistic is modified to count both Circuit Switched (CS) and Packet Switch(PS) pages.

{3750} The bins are:

S CS pages discarded.

S PS pages discarded.

{3750} This statistic is obtained by measuring the number of Paging requests, which arediscarded from the PCH queue before they could be transmitted. Pages can bediscarded from the queues (assuming queuing is in operation) for a number of reasons,including queue overflow, priority insertion in the queue causing an overflow and in-queuetimer expiry.

Pegging

This statistic pegs each time a page from the MSC is overwritten while in the queue.

{3750} The statistic also pegs for CS and PS pages as well as the assignments whichthe BSS was going to send over the PCH.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof paging messages that may be discarded from the PCH queue that are acceptable innormal system operations.

Reference GSM 12.04, 4.2.1, B.2.1.8

Usage Quality of service: Paging analysis.

Optimization.

Network planning.

Basis Cell.

Type Counter.

Alarm Major.

GSR6 RF_LOSSES_SD

14 Feb 2003


68P02901W56-L 4–83

RF_LOSSES_SD

Description

The RF_LOSSES_SD statistic tracks the number of calls lost while using a SDCCH. If aTCH is reconfigured as a SDCCH, only the SDCCH statistics are configured.

Pegging

This statistic pegs the number of calls that were terminated because of RF problems.This statistic will only peg for lost calls after the call has been established. This statisticwill not be pegged when the CHAN_REQ_MS_FAIL statistic is pegged.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof lost calls while using a SDCCH that are acceptable in normal system operations.

If the specified threshold is exceeded, the 0. CELL: Radio frequency losses whileusing an SDCCH – PM alarm is generated. Refer to the Maintenance Information:Alarm Handling at the 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 and10.5.2.19.

Usage RF loss.

Congestion.


Fault finding.

Installation and commissioning.

Key statistic: RF_LOSS_RATE,SDCCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.

Alarm Major.

GSR6RF_LOSSES_TCH

14 Feb 20034–84


68P02901W56-L

RF_LOSSES_TCH

Description

The RF_LOSSES_TCH statistic tracks the number of calls lost while using a TCH.

RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSSon a per timeslot level. The OMC-R rolls the information up to the cell leveland refers to this information as RF_LOSSES_TCH_ROLL .

NOTE

Pegging

This statistic pegs the number of calls that were terminated because of RF problems. Itis composed of calls lost while using a TCH. If a TCH is reconfigured as an SDCCH,only the SDCCH statistics are configured.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof lost calls 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.


Fault finding.


Key Statistic: RF_LOSS_RATE,TCH_RF_LOSS_RATE.

Basis Timeslot.

Type Counter.

Alarm Major.

NOTE RF_LOSSES_TCH is not pegged with any handover failurestatistic. In a frequency hopping environment, this statistic maynot be useful at channel level; therefore, roll to cell level.

GSR6 SDCCH_CONGESTION

14 Feb 2003


68P02901W56-L 4–85

SDCCH_CONGESTION

Description

The SDCCH_CONGESTION statistic tracks the amount of time that no SDCCH channelwas available in a cell.

Pegging

This statistic records the sum of the duration of periods when all the SDCCH channels ina cell were busy. The statistic also collects the mean, maximum, and minimum time ofSDCCH congestion. If a TCH is reconfigured as an SDCCH, only the SDCCH statisticsare recorded.

Although the mean, maximum and minimum values are collected for this statistic, theycan only be viewed through the MMI using the disp_stats command.

Analysis

This statistic can be used for trend analysis of the length of time during which SDCCHchannels were not available.

Reference GSM 12.04, 3.1.0, B.1.3.5.

Usage RF loss.

Congestion.


Network planning.

Optimization.

Basis Cell.

Type Duration (total time in milliseconds).


GSR6SECOND_ASSIGN_ATMPT

14 Feb 20034–86


68P02901W56-L

SECOND_ASSIGN_ATMPT

Description

The SECOND_ASSIGN_ATMPT statistic tracks the number of times the networkinitiated a second assignment procedure on receipt of an Assignment Failure messagefrom the MS.

Pegging

The BSS only attempts (initiates) a second assignment procedure on receipt of anAssignment Failure message if the per BSS element second_asgnmnt is set.

Reference None.

Usage Congestion.

Basis Cell.

Type Counter.

GSR6 SECOND_ASSIGN_SUC

14 Feb 2003


68P02901W56-L 4–87

SECOND_ASSIGN_SUC

Description

The SECOND_ASSIGN_SUC statistic tracks the number of times that a secondassignment procedure initiated by the network is successfully completed, upon receipt ofan Assignment Complete message from the MS.

Pegging

The BSS only attempts (initiates) a second assignment procedure on receipt of anAssignment Failure message if the per BSS element second_asgnmnt is set.

Reference None.

Usage Congestion.

Basis Cell.

Type Counter.

GSR6SMS_INIT_ON_SDCCH

14 Feb 20034–88


68P02901W56-L

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 is created, a SMS requires a logical SAPI3 connection. Additionally,the statistic can be used to determine how SDCCHs are being used (for example, forSMS as opposed to location update).

Pegging

This statistic is incremented on one successful Service Access Point (SAPI3) connectionrelated to a SDCCH.

Analysis

This statistic can be used for trend analysis of how many SMS transactions occurred ona cell.


Basis Cell.

Type Counter.

GSR6 SMS_INIT_ON_TCH

14 Feb 2003


68P02901W56-L 4–89

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 is created, a SMS requires a logical SAPI3 connection. Additionally,the statistic can be used to determine how TCHs are being utilized (for example, for SMSas opposed to normal voice traffic).

Pegging

This statistic is incremented upon successful SAPI3 connection related to a TCH.

Analysis

This statistic can be used for trend analysis of how many SMS transactions occurred ona cell related to a TCH.


Basis Cell.

Type Counter.

GSR6SMS_NO_BCAST_MSG

14 Feb 20034–90


68P02901W56-L

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.

Pegging

This statistic pegs each time a message is broadcast on the CBCH.

Analysis

This statistic can be used for trend analysis of how many times a message has beenbroadcast on a per cell basis.


Basis Cell.

Type Counter.

GSR6 TCH_CONGESTION

14 Feb 2003


68P02901W56-L 4–91

TCH_CONGESTION

Description

The TCH_CONGESTION statistic indicates the amount of time that no TCH channelswere available in that cell.

The TCH_CONGESTION statistic will only be used for outer zone resources when TCHcongestion is being measured for Concentric Cells.

A congestion (or blocking) state occurs when all channels available to traffic within a cell(the number may vary over time due to failure or maintenance actions) are busy, wherebusy means unavailable for allocation to a new call attempt.

Pegging

This statistic pegs the sum of the duration of periods when all TCHs were busy. Thestatistic also reports the mean, maximum and minimum time of TCH congestion. If aTCH is configured as an SDCCH only the SDCCH statistics will be configured.

Reference GSM 12.04, 3.1.0, B.1.1.12

Usage RF loss.

Congestion.


Network planning.

Optimization.

Basis Cell.

Type Duration (total time in milliseconds).

GSR6TCH_CONG_INNER_ZONE

14 Feb 20034–92


68P02901W56-L

TCH_CONG_INNER_ZONE

Description

The TCH_CONG_INNER_ZONE statistic tracks the total length of time in which all of theTCHs in the inner zone of a concentric cell are busy. The Concentric Cell option must beenabled for this statistic to be enabled, disabled, or displayed.

Pegging

The timer for this statistic is started when all TCHs belonging to TCHs in the inner zoneare busy. The timer is stopped when an inner zone TCH is freed.

Analysis

This statistic can be used for trend analysis of the length of time in which all of the TCHsin the inner zone of a concentric cell are busy.

Reference None.

Usage Network planning.

Basis Cell.

Type Duration.

GSR6 TCH_DELAY

14 Feb 2003


68P02901W56-L 4–93

TCH_DELAY

Description

The TCH_DELAY statistic tracks the mean delay and the statistical distribution of thedelay between an assignment request or handover request and a TCH being allocatedfor each cell on the BSS.

As more calls (in proportion to the total number of calls) are queued, the mean delay willbe longer. Queueing is only done if the assignment or Handover Request indicates thatqueueing is allowed for that request. This statistic will measure the queueing delayeffectively. It is possible to have assignments and handovers for which there is no delayin resource allocation. These no-delay assignments are included in the mean delaystatistic.

Pegging

A timer is started when the request is queued and stopped when the request is allocated.

Analysis

This statistic can be used for trend analysis of the queueing delay for a traffic channelbeing 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.

GSR6TCH_Q_LENGTH

14 Feb 20034–94


68P02901W56-L

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.

Pegging

This measurement is obtained by sampling the TCH queue length and reporting thecurrent length. The mean TCH queue length includes the number of queued assignmentand external handover requests.

Analysis

This statistic can be used for trend analysis of the number of queued TCH assignmentprocedures.

Reference GSM 12.04, 4.2.1, B.2.1.15

Usage Quality of service: Network accessibility.

Network planning.

Optimization.

Basis Cell.


GSR6 TCH_Q_REMOVED

14 Feb 2003


68P02901W56-L 4–95

TCH_Q_REMOVED

Description

The TCH_Q_REMOVED statistic tracks when a queued call is assigned to a TrafficChannel (TCH).


0 ASSIGNMENT_RESOURCE_REQ Number of times an assignmentresource is requested.

1 HO_REQ Number of times a handover isrequested.

Pegging

These bins are pegged upon removal of either an assignment request or handoverrequest from the TCH queue.

Analysis

This statistic can be used for trend analysis of the number of queued TCH assignmentprocedures.

Reference None.

Usage Quality of service: Network accessibility.

Network planning.

Optimization.

Basis Cell.

Type Counter array.

GSR6TCH_USAGE

14 Feb 20034–96


68P02901W56-L

TCH_USAGE

Description

The TCH_USAGE statistic gives an indication of the total amount of traffic carried by thecell. Active means connected (capable of transmitting circuit mode user data) andactivated, for example, used as a DCCH.

The TCH_USAGE statistic is used only for outer zone resources when TCH usage isbeing measured for Concentric Cells.

The TCH_USAGE statistic measures only the usage of normal range channels inExtended Range Cells.

Both TCH_USAGE and BUSY_TCH include the guard timer value. This is a countervalue. The sum equals the amount of time in milliseconds the TCH was busy, kept byinternal timers. Therefore, when the interval expires, TCH usage may not be reporteduntil the next interval. Exercise caution if using this value over short interval periods. Forexample:

S Interval 0 starts.

S TCH 0 starts call – internal timer starts.

S TCH 1 starts call – internal timer starts.

S TCH 0 ends call – internal timer stops.

S TCH_USAGE counter incremented by time.

S Difference for TCH 0.

S Interval 0 expires.

The value reported for the interval will only include the call for TCH0.

S Interval 1 starts.

S TCH 1 ends a call – internal timer stopped.

S TCH_USAGE counter incremented by time.

S Difference for TCH 1.

Pegging

This statistic is the sum of the time that each TCH was active with a call for all TCHs onthe cell. If a TCH is reconfigured as an SDCCH, only the SDCCH statistics will beconfigured.

Analysis

This statistic can be used for trend analysis of the total amount of traffic carried by thecell.

Reference GSM 4.08, 3.8.0, 3.1.4.

Usage RF loss.

Congestion.


Network planning.

Optimization.

GSR6 TCH_USAGE

14 Feb 2003


68P02901W56-L 4–97

Basis Cell.

Type Counter.

GSR6TCH_USAGE_EXT_RANGE

14 Feb 20034–98


68P02901W56-L

TCH_USAGE_EXT_RANGE

Description

The TCH_USAGE_EXT_RANGE statistic tracks the number of extended range trafficchannels in use.

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

Pegging

This statistic pegs each time an extended range traffic channel is used.

Analysis

This statistic can be used for trend analysis of the number of extended range trafficchannels in use.

Reference None.


Network planning.


Basis Cell.

Type Counter.

GSR6 TCH_USAGE_INNER_ZONE

14 Feb 2003


68P02901W56-L 4–99

TCH_USAGE_INNER_ZONE

Description

The TCH_USAGE_INNER_ZONE statistic tracks the usage of TCHs belonging tocarriers in the inner zone of a concentric cell. The Concentric Cell option must beenabled for this statistic to be enabled, disabled, or displayed.

The TCH_USAGE statistic is used only for outer zone resources when the ConcentricCells feature is unrestricted.

Pegging

This statistic pegs when a TCH belonging to a carrier in the inner zone is used.

Analysis

This statistic can be used for trend analysis of the usage of TCHs belonging to carriers inthe inner zone of a concentric cell.

Reference None.


Basis Cell.

Type Counter.

GSR6TOTAL_CALLS

14 Feb 20034–100


68P02901W56-L

TOTAL_CALLS

Description

The TOTAL_CALLS statistic tracks the total number of calls originated for each cell onthe BSS.

Pegging

This statistic indicates the number of circuit oriented calls that are originated in the cell.It is pegged only once per connection at the time of the first successful TCH assignmentprocedure. 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 havebeen assigned to the TCH. For example, if the call fails to send a Direct TransferApplication Part (DTAP) Connect Acknowledge, it still looks successful to the base.

NOTE This statistic is not pegged on the short message service

Analysis

This statistic can be used for trend analysis of the total number of calls originated foreach cell on the BSS.

Reference GSM 4.08, 3.8.0, 5.2.


Quality of service monitoring : Call setup.

Network planning.


Key Statistics: RF_LOSS_RATE,TCH_MEAN_HOLDING_TIME ,TCH_MEAN_ARRIVAL_RATE,TCH_RF_LOSS_RATE.

Basis Cell.

Type Counter.

GSR6 ZONE_CHANGE_ATMPT

14 Feb 2003


68P02901W56-L 4–101

ZONE_CHANGE_ATMPT

Description

The ZONE_CHANGE_ATMPT statistic tracks attempts of each type of concentric cellspecific handover. The Concentric Cell option must be enabled for this statistic to beenabled, disabled, or displayed.


0 INNER_TO_OUTER_ZONE Number of handover attempts frominner zone to outer zone.

1 OUTER_TO_INNER_ZONE Number of handover attempts fromouter zone to inner zone.

2 INTRA_ZONE Number of intra-zone handoverattempts.

3 TCH_ASSIGN_TO_INNER_ZONE Number of TCH assignmentattempts to inner zone cells.

4 IN_INTER_CELL_HO_TO_IN_ZONE Number of internal inter-cellhandover attempts to inner zone.

Pegging

Each bin is pegged when a corresponding concentric cell handover is attempted.

Analysis

This statistic can be used for trend analysis of the attempts of each type of concentriccell specific handover.

Reference None.


Basis Cell.

Type Counter array.

GSR6ZONE_CHANGE_SUC

14 Feb 20034–102


68P02901W56-L

ZONE_CHANGE_SUC

Description

The ZONE_CHANGE_SUC statistic tracks each type of successful Concentric Cellspecific handover. The Concentric Cell option must be enabled for this statistic to beenabled, disabled, or displayed.


0 INNER_TO_OUTER_ZONE Number of successful handoversfrom inner zone to outer zone.

1 OUTER_TO_INNER_ZONE Number of successful handoversfrom outer zone to inner zone.

2 INTRA_ZONE Number of successful intra-zonehandovers.

3 TCH_ASSIGN_TO_INNER_ZONE Number of successful TCHassignments to inner zone cells.

4 IN_INTER_CELL_HO_TO_IN_ZONE Number of successful internalinter-cell handovers to inner zone.

Pegging

Each bin is pegged when a corresponding concentric cell handover is successful.

Analysis

This statistic can be used for trend analysis of each type of successful concentric cellspecific handover.

Reference None.


Basis Cell.

Type Counter array.

14 Feb 2003


68P02901W56-L 5–1

Chapter 5

Neighbour statistics

GSR6

14 Feb 20035–2


68P02901W56-L

GSR6 Introduction to Neighbour Statistics

14 Feb 2003


68P02901W56-L 5–3

Introduction to Neighbour Statistics

DescriptionThis chapter includes descriptions of the per neighbour statistics.

NeighbourWhen the BSS is configured to control inter-cell handovers, four of the handoverstatistics may be used to track handovers. These neighbour statistics provide thedestination cell of an outgoing handover or the origination cell of an incoming handover.

Each of the neighbour statistics keep track of handover information for a pair of sourceand neighbour cells.

The following are neighbour statistics:

S IN_INTRA_BSS_NC_ATMPT.

S IN_INTRA_BSS_NC_SUC.

S OUT_HO_NC_CAUSE_ATMPT.

S OUT_HO_NC_SUC.

Definitions

Following terms are used in the description of neighbour cells:

S Source cell – the cell in which a handover is initiated. Each source cell may haveup to 32 target (neighbour) cells.

S Target cell – the neighbour cell into which the MS may be handed over. There isno limit on the number of source cells that may handover calls to a target cell.

Limitations

S Each neighbour statistic can be enabled for a maximum of 16 cells in a BSS. Thecells for 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 thecopy_cell command will be disabled. The individual statistics for the new cell willhave to be enabled individually including the neighbour statistics.

S IN_INTRA_BSS_NC_ATMPT and IN_INTRA_BSS_NC_SUC statistics areincremented in the target cell and can only be pegged for up to 32 source cells.

S OUT_HO_NC_CAUSE_ATMPT and OUT_HO_NC_SUC statistics areincremented in the source cell and can only be pegged for up to 32 target cells.

S If the BSS is configured to have the MSC control intra-BSS handovers, theincoming per cell statistics are affected, and may not be used to track handovers.

Outgoing neighbour cell statisticsOutgoing neighbour statistics track the number of attempted and successful handoversfrom a source cell into a neighbour cell. The outgoing neighbour statistics are:

S OUT_HO_NC_CAUSE_ATMPT.

S OUT_HO_NC_SUC.

GSR6Introduction to Neighbour Statistics

14 Feb 20035–4


68P02901W56-L

Example of tracked statistics

In 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:

S Originating in cell_0 that hand into cell_1.


S .

S .


Example showing effects of the del_neighbor command

If the del_neighbor command is used to delete one of the neighbour cells of a sourcecell, 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_ATMPT statistic is enabled at cell_0. The del_neighborcommand is used to delete cell_32 as a neighbour cell of cell_0.

The BSS will track intra-BSS handover attempts:

S originating in cell_0 that hand into cell_1


S .

S .


Example showing effects of the add_neighbor command

If the del_neighbor command is used to delete one of the neighbour cells of a sourcecell, only the 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_ATMPT statistic is enabled at cell_0. The add_neighborcommand is used to add cell_32 as a neighbour cell of cell_0.



S originating in cell_0 that hand into cell_2.

S .

S .


Incoming neighbour statisticsIncoming neighbour statistics track the number of attempted and successful handoversinto a neighbour cell from a source cell. Handovers are tracked for only 32 cells for eachneighbour cell, even if a neighbour cell has more than 32 source cells. The incomingneighbour statistics are:

S IN_INTRA_BSS_NC_ATMPT.

S IN_INTRA_BSS_NC_SUC.


14 Feb 2003


68P02901W56-L 5–5

Choosing source cellsAn algorithm chooses which source cells to track for the incoming neighbour statistics.The source 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 source whichhas 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 betracked.

3. If new source cells can be added, reciprocal neighbours are added first, followedby non-reciprocal neighbours, which are chosen by sequentially looking throughthe database.

Example of tracked statisticsIn this example, the BSS has 90 cells (cell_0 through cell_89), cell_1 through cell_10have cell_0 as a neighbour, and the IN_INTRA_BSS_NC_ATMPT statistic is enabled atcell_0.


S that hand into cell_0 originating from cell_1


S .

S .


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 asneighbours. Cell_1 through cell_50 each have cell_0 as a neighbour. The incomingneighbour statistics are enabled at cell_0. While cell_1 through cell_50 can hand intocell_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 throughcell_50 are 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 asneighbours. Cell_1 through cell_50 each have cell_0 as a neighbour. The incomingneighbour statistics are enabled at cell_0. While cell_1 through cell_50 can hand intocell_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 throughcell_50 are 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 reciprocalneighbour pair. The cells being tracked will not be changed just because a new reciprocalneighbour pair has been added because it is already at the maximum number of cells itcan track.


14 Feb 20035–6


68P02901W56-L

Example of when a neighbour cell is deleted

In this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 asneighbours. Cell_1 through cell_50 each have cell_0 as a neighbour. The incomingneighbour statistics are enabled at cell_0. While cell_1 through cell_50 can hand intocell_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 throughcell_50 are 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 reciprocalneighbour pair. The cells being tracked will not be changed just because a new reciprocalneighbour pair has been added because it is already at the maximum number of cells itcan track.

Neighbour cell_0 is deleted from cell_18. When this cell is deleted, cell_0 only tracks 31source cells. Because 32 cells may be tracked, a search is done to see if there are anyreciprocal neighbours.

Since cell_45 was added creating a reciprocal pair, cell_45 would now be tracked. If areciprocal pair had not been available, cell_33 would have been chosen as the nextnon–reciprocal source not already tracked.

Examples of notation and initial situation

The following are examples of typical handover situations to show how neighbour cellstatistics are pegged.

Notation

An 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 situation

Table 5-1 shows an example of three cells: cell_A, cell_B, and cell_C. All four neighbourcell statistics are enabled at cell_A. For this example, all cells are internal to the sameBSS.

cell_C

cell_Bcell_A


14 Feb 2003


68P02901W56-L 5–7

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_B

cell_C is a neighbour of cell_A andcell_A is a neighbour of cell_C

IN_INTRA_BSS_NC_ATMPT

IN_INTRA_BSS_NC_SUC


IN_INTRA_BSS_NC_SUC

OUT_HO_NC_CAUSE_ATMPT

OUT_HO_NC_SUC


OUT_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)

A MS that originated in cell_B performs a successful handover into cell_A. The followingstatistics are updated:


IN_INTRA_BSS_NC_SUC


IN_INTRA_BSS_NC_SUC


OUT_HO_NC_SUC


OUT_HO_NC_SUC

1 (B–A)

1 (B–A)

0 (C–A)

0 (C–A)

0 (A–B)

0 (A–B)

0 (A–C)

0 (A–C)

Successful handover (A–C)

The MS, which is now in cell_A, performs another successful handover into cell_C. Thefollowing statistics are updated.


IN_INTRA_BSS_NC_SUC


IN_INTRA_BSS_NC_SUC


OUT_HO_NC_SUC


OUT_HO_NC_SUC

1 (B–A)

1 (B–A)

0 (C–A)

0 (C–A)

0 (A–B)

0 (A–B)

1 (A–C)

1 (A–C)

Unsuccessful handover (C–A)

The MS in cell_C attempts a handover into cell_A, but is unsuccessful. The followingstatistics are updated.


14 Feb 20035–8


68P02901W56-L


IN_INTRA_BSS_NC_SUC


IN_INTRA_BSS_NC_SUC


OUT_HO_NC_SUC


OUT_HO_NC_SUC

1 (B–A)

1 (B–A)

1 (C–A)

0 (C–A)

0 (A–B)

0 (A–B)

1 (A–C)

1 (A–C)

GSR6 IN_INTRA_BSS_NC_ATMPT

14 Feb 2003


68P02901W56-L 5–9


Description

The IN_INTRA_BSS_NC_ATMPT statistic tracks the number of intra-BSS handoverattempts into a cell and the location of the cell originating the handover attempt. Allowsstudy of the handover performance of a specific cell for each of its source cells. Providesinformation to determine quality of service and to support optimization.

This statistic can be enabled for a maximum of 16 cells. For each cell where the statisticis enabled, a maximum of 32 source cells can be tracked.

Pegging

This statistic is pegged in the target cell against a specific source cell. This is done eachtime the SSM decides to perform an intra-BSS handover where the target is an internalneighbour which is placed first in the Handover Recognized message.

Analysis

This statistic can be used for trend analysis of the number of handover attempts into acell and the location of the cells originating the handover attempts.

Reference GSM 12.04, 4.0.0, B.2.2.1

GSM 4.08, 8.08, 8.58

Usage Handover.

Quality of Service.

Network Planning.

Optimization.

Fault Finding.

Basis NCell (Neighbour cell).

Type Counter.

GSR6IN_INTRA_BSS_NC_SUC

14 Feb 20035–10


68P02901W56-L

IN_INTRA_BSS_NC_SUC

Description

The IN_INTRA_BSS_NC_SUC statistic tracks the successful incoming internal inter-cellhandovers per originating cell.

This statistic can be enabled for a maximum of 16 cells. For each cell where the statisticis enabled, a maximum of 32 source cells can be tracked.

Pegging

This statistic is pegged in the target cell upon notification of a successful intra-BSShandover from a specific cell.

Analysis

This statistic can be used for trend analysis of incoming internal inter-cell handovers peroriginating cell.

Reference GSM 12.04, 4.0.0, B.2.2.2

GSM 4.08, 8.08, 8.58

Usage Handover.

Quality of Service.

Network Planning.

Optimization.

Fault Finding.


Type Counter.

GSR6 OUT_HO_NC_CAUSE_ATMPT

14 Feb 2003


68P02901W56-L 5–11


Description

The OUT_HO_NC_CAUSE_ATMPT statistic tracks the number of handovers perneighbour per cause. This statistic can be enabled for a maximum of 16 cells. For eachcell where the statistic is enabled, a maximum of 32 target cells can be tracked.

This statistic provides information to determine quality of service and to supportoptimization. Allows study of the handover performance of a specific cell for each of itsneighbouring 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 uplinkinterference.

6 DOWNINTERF Handovers due to downlinkinterference.

7 POWERBDGT Handovers due to power budget.

8 CONGESTION Handovers due to congestion.

9 ADJ_CHAN_INTF Handovers due to adjacent channelinterference.

10 BAND_RE_ASSIGN Handovers due to bandreassignment.

11 BAND_HANDOVER Handovers between bands.

Pegging

This statistic pegs the total number of handover attempts out of a specific cell, thelocation of the target cell, and the cause for each attempt. This statistic is pegged at thesource cell.

Analysis

This statistic can be used for trend analysis of handover attempts per neighbour on a percause basis.

GSR6OUT_HO_NC_CAUSE_ATMPT

14 Feb 20035–12


68P02901W56-L

Reference GSM 12.04, 4.0.0, B.2.2.3

GSM 4.08, 8.08, 8.58

GSM 12.04, 4.2.1

Usage Handover.

Quality of Service.

Network Planning.

Optimization.

Fault Finding.

Ladder: Intra-BSS handover.


Type Counter array.

GSR6 OUT_HO_NC_SUC

14 Feb 2003


68P02901W56-L 5–13

OUT_HO_NC_SUC

Description

The OUT_HO_NC_SUC statistic tracks the number of successful outgoing inter-cellhandovers per target cell. This statistic can be enabled for a maximum of 16 cells. Foreach cell where the statistic is enabled, a maximum of 32 target cells can be tracked.

Pegging

This statistic pegs the total number of successful handovers out of a specific cell and thelocation of the target cell for each successful handover.

Analysis

This statistic can be used for trend analysis of handover performance of specific cells foreach of its neighbouring target cells.

Reference GSM 12.04, 4.0.0, B.2.2.4

GSM 4.08, 8.08, 8.58

Usage Handover.

Quality of Service.

Network Planning.

Optimization.

Fault Finding.


Type Counter.

GSR6OUT_HO_NC_SUC

14 Feb 20035–14


68P02901W56-L

14 Feb 2003


68P02901W56-L 6–1

Chapter 6

Carrier and timeslot statistics

GSR6

14 Feb 20036–2


68P02901W56-L

GSR6 Carrier and timeslot statistics introduction

14 Feb 2003


68P02901W56-L 6–3

Carrier and timeslot statistics introduction

Description of carrier statisticsThis chapter includes descriptions of the carrier statistics which are organized into thefollowing groups:

S Downlink RXQUAL (BER).

S Uplink RXQUAL (U_BER).

S Link balance verification.

S BTS dynamic allocation.

S Timing advance.

S Miscellaneous.

Downlink RXQUAL (BER)Downlink receive quality statistics are used to track the Bit Error Rate (BER) of activechannels. The following is the only downlink RXQUAL statistic:

S BER.

Uplink RXQUAL (U_BER)Uplink receive quality statistics are used to track the Bit Error Rate (BER) of activechannels. The following is the only uplink RXQUAL statistic:

S U_BER.

Link balance verificationLink balance verification statistics are used to track the link balance between air interfaceof the uplink and downlink path loss. The following are the link balance statistics:

S CHAN_DL_TX_PWR_LVL.

S CHAN_UL_TX_PWR_LVL.

S PATH_BALANCE.

S UPLINK_PATH_LOSS.

BTS dynamic allocationBTS dynamic allocation statistics are used to track utilization of dynet channels. Thefollowing are the BTS dynamic allocation statistics:

S ALLOC_SDCCH_CARR.

S ALLOC_TCH_CARR.

Timing advanceThe timing advance statistic ROC is used to monitor the timing advance measurements.

MiscellaneousMiscellaneous statistics are used to track several unrelated carrier and timeslot statistics.The following are the miscellaneous carrier statistics:

S CHAN_REQ_MS_FAIL.

S FER.

S INTF_ON_IDLE.

S RBER.

S RF_LOSSES_TCH.

GSR6ALLOC_SDCCH_CARR

14 Feb 20036–4


68P02901W56-L

ALLOC_SDCCH_CARR

Description

The ALLOC_SDCCH_CARR statistic is the sum of the number of SDCCH allocationsper carrier within a cell.

Pegging

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

S Successful handover on an SDCCH channel.

S Successful immediate assignment on an SDCCH channel.

This statistic pegs for reasons other than calls requiring a traffic channel, such aslocation updates.

Analysis

This statistic can be used for trend analysis of SDCCH allocations and allows thecalculation of 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.2to 9.1.4, 9.1.14 to 9.1.19.

Usage RF loss.

Congestion.


Network planning.

Ladder: Immediate assignment successful,Intra-cell handover, Inter-BSS handover,Connection establishment, Intra-BSS handover.

Basis Carrier.

Type Counter.


GSR6 ALLOC_TCH_CARR

14 Feb 2003


68P02901W56-L 6–5

ALLOC_TCH_CARR

Description

The ALLOC_TCH_CARR statistic provides the number of successful TCH allocationsper carrier within a cell for both call originations and hand ins.

Pegging

This statistic pegs for successful TCH allocations per carrier within a cell as a result of acall establishment or hand in attempt:

S Successful allocation due to call establishment including successful allocations dueto directed retries.


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

S Successful allocation due to inter-BSS hand in.

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

Analysis

This 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-BSShandover, Intra-cell handover, Assignment toTCH.

Key statistics: TCH_MEAN_ARRIVAL_RATE,TCH_MEAN_HOLDING_TIME ,CELL_TCH_ALLOCATIONS,TCH_RF_LOSS_RATE.

Basis Carrier.

Type Counter.

GSR6BER

14 Feb 20036–6


68P02901W56-L

BER

Description

The BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) foractive channels. The bit error rate value corresponds to the RXQUAL downlinkmeasurement reports. BER statistic measurements are reported only when the channelis active.

NOTE BER on SDCCH channels are affected by phantom RACHs.BER on TCHs are not affected. For a cell with a non-combinedBCCH configuration, there are no values presented on timeslot0.

Pegging

The statistic pegs every 480 ms (corresponding to each SACCH multiframe).

Units

This 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

NOTE The bin ranges for this statistic may not be changed.

Analysis

This 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 and10.5.2.11.

GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.

Usage RF loss.

Congestion.


Fault finding.

Basis Timeslot.


GSR6 CHAN_DL_TX_PWR_LVL

14 Feb 2003


68P02901W56-L 6–7

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.

Pegging

This statistic pegs every SACCH multiframe.

Analysis

This 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.


GSR6CHAN_REQ_MS_FAIL

14 Feb 20036–8


68P02901W56-L

CHAN_REQ_MS_FAIL

Description

The CHAN_REQ_MS_FAIL statistic tracks the number of times that the BSS times outwhile waiting for the MS to establish on the SDCCH that was assigned to it during theimmediate 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 outof range, the MS is failing, or the MS is switched off. However, frequent occurrences ofthis event within a short period of time and/or geographically clustered may indicate ahardware failure.

NOTE CHAN_REQ_MS_FAIL is the BSS MMI name of the statistickept by the BSS on a per timeslot level. The OMC-R rolls theinformation up to the cell level and refers to this information asCHAN_REQ_MS_FAIL_ROLL.

Pegging

This statistic pegs when the MS does not reply with Set Asynchronous Balanced Mode(SABM) on the SDCCH.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof BSS timeouts while waiting for an MS to establish on the SDCCH assigned during theimmediate assignment 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 Handlingat the OMC (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.


Ladder: Immediate assignment blocked.

Basis Timeslot.

Type Counter.

Alarm Minor.


GSR6 CHAN_UL_TX_PWR_LVL

14 Feb 2003


68P02901W56-L 6–9

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.

Pegging

This statistic pegs every SACCH multiframe.

Analysis

This statistic can be used for trend analysis of mean MS transmit power levels.

Reference GSM 12.04, 4.2.1, B.2.1.29.


Quality of service.

Basis Carrier.


GSR6FER

14 Feb 20036–10


68P02901W56-L

FER

Description

The FER (Frame Erasure Rate) Quality statistic is derived from a ratio of successfullydecoded good speech frames against unsuccessfully decoded bad frames. 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 toa lookup table, the ratio is then converted to an FER Quality number between 0 and 9.

For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookuptable, Table 6-1, this relates to an FER Quality number of 2.

Pegging

This statistic pegs every 480 ms during the SACCH multi-frame by the RSS/HO process.

Units

The FER is reported using values 0 to 9 and shows the complete lookup table.

Table 6-1 FER Quality number conversion

FER Quality number 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_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.

The values of the bins are fixed and are not adjustable by the operator.

Analysis

This statistic can be used for trend analysis for target optimization effects on cell/radioswith regards to quality.

Reference None.

Usage Quality of service, Fault finding, RF loss,Congestion.

Basis Timeslot.


GSR6 INTF_ON_IDLE

14 Feb 2003


68P02901W56-L 6–11

INTF_ON_IDLE

Description

The INTF_ON_IDLE statistic indicates the maximum, minimum, and mean interferencelevels experienced on idle channels as determined by the BSS.

The bin ranges may be changed using the chg_stat_prop command. The default binranges for 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 recordingmeasurements of received signal strength taken when the channel is idle. Thismeasurement parallels the activity of the channel selection algorithm of the CellResource Manager which uses the same data to rank idle channels, giving preference tothe channels with a lower interference level. The measured signal level is mapped to anRXLEV value between 0 and 63. Each RXLEV value corresponds to a dBm value, asshown 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

Pegging

This statistic pegs every 480 ms.

Analysis

This statistic can be used for trend analysis of interference levels experienced on idlechannels.

GSR6INTF_ON_IDLE

14 Feb 20036–12


68P02901W56-L

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.


Network planning.

Fault finding.

Basis Timeslot.


GSR6 PATH_BALANCE

14 Feb 2003


68P02901W56-L 6–13

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.

NOTE The actual value for path_balance depends on the type of RFcombining used.

Pegging

This 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

NOTE The rxlev_ul and rxlev_dl values reflect the latest reported valueand are not averaged values. PATH_BALANCE is not peggedwhen 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 withnormal use. A deviation of ±10 is acceptable, but this is to be understood as a practicalguide and not as product tolerance. If the deviation is greater than ±10, the RF pathshould be checked.

NOTE If a low noise amplifier (LNA) is fitted, a deviation of –20 ispossible.

Typically, the path loss should be similar in both the uplink and downlink directions. Whendiversity gain is enabled, the path balance will be just below 110, indicating a lower uplinkpath loss.

Mismatch of Horizon and Horizonmacro database and hardware.

The path_balance statistic will be incorrect if the the Horizon and Horizonmacro cabinetand database are mismatched. The following table describes the two mismatchscenarios between the cabinet and database.

GSR6PATH_BALANCE

14 Feb 20036–14


68P02901W56-L

If... Then...

the Horizon cabinet isequipped with Horizonmacrodatabase, the path_balancestatistic will be incorrect.

the SITE alarm 28 “data configurationand Horizon hardware mismatch” will begenerated

operators should change either thehardware or the database accordingly.

Consult the manual, MaintenanceInformation: Alarm Handling At The OMC(68P02901W26).

the Horizonmacro cabinet isequipped with Horizondatabase, the path_balancestatistic will be incorrect.

the SITE alarm 28 “data configurationand Horizon hardware mismatch” will begenerated.

operators should change either thehardware or the database accordingly.

Consult the manual, MaintenanceInformation: Alarm Handling At The OMC(68P02901W26).

NOTE If the Horizonmacro booster unit is faulty or not present, thepath_balance statistic is incorrect. Operators should disregardthis statistic until the booster is replaced. Network plannersshould check with the OMC operator to determine if anyHorizonmacro alarms (SITE alarms 25, 26 or 27) have beengenerated.

Analysis

This 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.

GSR6 RBER

14 Feb 2003


68P02901W56-L 6–15

RBER

Description

The RBER (Residual Bit Error Rate) Quality statistic is derived from a ratio of number ofbits in error to total number of bits received, within error detected speech frames definedas good. The measurement period over which the calculation is made is 480 ms.

During this period, 24 speech frames are decoded and a ratio calculated. By referring toa lookup table, the ratio is converted to an RBER Quality number between 0 and 7.

NOTE RBER is supported only by MMI actions. It not reported to theOMC-R at the end of the statistical interval period.

Pegging

Every 480 ms, during the SACCH multi-frame by the RSS/HO process.

Units

The 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.

Analysis

This statistic can be used for trend analysis for target optimization effects on cell/radioswith regards to quality.

Reference None.


Fault finding.

RF loss.

Congestion.

Basis Timeslot.


GSR6RF_LOSSES_TCH

14 Feb 20036–16


68P02901W56-L

RF_LOSSES_TCH

Description

The RF_LOSSES_TCH statistics tracks the number of calls lost while using a TCH.

NOTE RF_LOSSES_TCH is the BSS MMI name of the statistic kept bythe BSS on a per timeslot level. The OMC-R rolls theinformation up to the cell level and refers to this information asRF_LOSSES_TCH_ROLL .

Pegging

This statistic pegs the number of calls that were terminated because of RF problems. It iscomposed of calls lost while using a TCH. If a TCH is reconfigured as an SDCCH, onlythe SDCCH statistics will be configured.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof lost calls while using a TCH that are acceptable in normal system operations.

If the specified threshold is exceeded, the 0. TIMESLOT: Radio frequency losseswhile using a TCH – PM alarm is generated. Refer to the Maintenance Information:Alarm Handling at the OMC (68P02901W26) for troubleshooting information.

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.


Fault finding.


Key Statistic: RF_LOSS_RATE,TCH_RF_LOSS_RATE.

Basis Timeslot.

Type Counter.

Alarm Major.

NOTE RF_LOSSES_TCH is not pegged with any handover failurestatistic. In a frequency hopping environment, this statistic maynot be useful at channel level, therefore roll to cell level.

GSR6 ROC

14 Feb 2003


68P02901W56-L 6–17

ROC

Description

The ROC statistic tracks the maximum, minimum and mean Range Of Carrier betweenBSS and MS on a per carrier basis. The range of carrier value corresponds to the timingadvance (TA) measurement reports. ROC statistic measurements are only reported foractive channels.

The bin ranges for the ROC statistic correspond to a number of user definable TA rangesup to a 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

NOTE These bins are not displayed at the OMC but can be displayed atthe MMI. To set and display the bin ranges refer to thechg_stat_prop and disp_stat_prop commands in Chapter 2.

Pegging


Basis Carrier.


GSR6U_BER

14 Feb 20036–18


68P02901W56-L

U_BER

Description

The U_BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) foractive channels. The bit error rate value corresponds to the RXQUAL uplinkmeasurement reports. U_BER statistic measurements are reported only when thechannel is active.

NOTE BER on SDCCH channels are affected by phantom RACHs.BER on TCHs are not affected. For a cell with a non-combinedBCCH configuration, there are no values presented on timeslot0.

Pegging


Units

This 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

NOTE The bin ranges for this statistic may not be changed.

Analysis

This 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 and10.5.2.11.

GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.

Usage RF loss.

Congestion.


Fault finding.

Basis Timeslot.


GSR6 UPLINK_PATH_LOSS

14 Feb 2003


68P02901W56-L 6–19

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 theradio link propagation losses experienced by MSs served in the cell.

Pegging

This statistic is pegged every SACCH multiframe for each active call.

Analysis

This 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.


GSR6UPLINK_PATH_LOSS

14 Feb 20036–20


68P02901W56-L

14 Feb 2003


68P02901W56-L 7–1

Chapter 7

GPROC and DPROC statistics

GSR6

14 Feb 20037–2


68P02901W56-L

GSR6 GPROC and DPROC statistics

14 Feb 2003


68P02901W56-L 7–3

GPROC and DPROC statistics

Introduction

This chapter includes descriptions of the Generic Processor (GPROC) and DataProcessor (DPROC) statistics. These statistics apply only to the utilization of theprocessing units found in various hardware components in the BSS, for example GPROCand DPROC devices.

Processor utilization

Processor utilization statistic tracks the utilization of the processing units found in varioushardware components in the GPROC and DPROC devices.

GSR6CPU_USAGE

14 Feb 20037–4


68P02901W56-L

CPU_USAGE

Description

The CPU_USAGE statistic tracks CPU usage. Monitoring of CPU usage allows theoperator to determine if the GPROC and DPROC devices at a particular site are beingover, under, or properly utilized.

This statistic is updated from reports generated by the internal executive system, whichkeeps track of when CPU usage changes.

Pegging

This statistic records the maximum, minimum, and mean values of the short-termprocessor utilization measurement (from which the 30-minute mean, statistic MeanUtilization, is calculated). This statistic is recorded for each GPROC and DPROC underthe control of a BSS.

Analysis

This 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.


14 Feb 2003


68P02901W56-L 8–1

Chapter 8

LMTL statistics

GSR6

14 Feb 20038–2


68P02901W56-L

GSR6 Introduction to LMTL statistics

14 Feb 2003


68P02901W56-L 8–3

Introduction to LMTL statistics{3974}

DescriptionThis chapter includes descriptions of the Location Services Message Transfer Link(LMTL) statistics. LMTL statistics are organized into the following groups:

S LMTP C7 availability.

S LMTP C7 performance.

S LMTP C7 utilization.

LMTP C7 availabilityMTP 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 toMSC interface. The following are the MTP C7 availability statistics:

S LMTP_LINKFAIL.

S LMTP_LOCAL_BUSY.

S LMTP_LOCAL_MGT.

S LMTP_MGT_INHIBIT.

S LMTP_MGT_UNINHIBIT.

S LMTP_REMOTE_MGT.

S LMTP_REMOTE_PROC .

S LMTP_START_RPO.

S LMTP_STOP_RPO.

S LMTP_UNAVAILABLE.

LMTP C7 performanceLMTP C7 performance statistics are used to track the different types of failure andrecovery situations for the Location SERVICES Message Transfer Part (LMTP) of theITU-TSS No.7 protocol on the BSC to MSC interface. The following are the LMTP C7performance statistics:

S LMTP_CHANGEBACK.

S LMTP_CHANGEOVER.

S LMTP_LINK_INS.

S LMTP_NEG_ACKS.

S LMTP_RESTORATION.

S LMTP_SL_ACK.

S LMTP_SL_ALIGNMENT.

S LMTP_REMOTE_SL_CONGESTION .

S LMTP_SL_ERROR_RATE.

S LMTP_SL_FAIL.

S LMTP_SL_FIBR.

S LMTP_SU_ERROR.

GSR6Introduction to LMTL statistics

14 Feb 20038–4


68P02901W56-L

LMTP C7 utilization

LMTP C7 utilization statistics are used to track the number of messages received,transmitted and retransmitted on signalling links and supply information on signalling linkcongestion for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSC interface.The following are the LMTP C7 utilization statistics:

S LMTP_CONGESTION_LOST_MSU .

S LMTP_MSU_DISCARDED.

S LMTP_CONGESTION .

S LMTP_RE_TX.

S LMTP_MSU_RX.

S LMTP_MSU_TX.

S LMTP_SIB_RX.

S LMTP_SIB_TX.

S LMTP_SIF_SIO_RX .

S LMTP_SIF_SIO_TX .

S LMTP_LOCAL_SL_CONGESTION .

GSR6 LMTP_CONGESTION_LOST_MSU

14 Feb 2003


68P02901W56-L 8–5

LMTP_CONGESTION_LOST_MSU{3974}

Description

The LMTP_CONGESTION_LOST_MSU statistic tracks the number of times MessageSignalling Units (MSU) are being lost due to Lb-interface Signalling Link (SL) congestion.

Pegging

This statistic pegs for each congestion event on the Lb-interface which results in MSUsbeing lost.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof lost MSUs due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 11. LMTL: SL congestion events resultingin loss of MSUs – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6LMTP_MSU_DISCARDED

14 Feb 20038–6


68P02901W56-L

LMTP_MSU_DISCARDED{3974}

Description

The LMTP_MSU_DISCARDED statistic tracks the number of MSUs discarded due toLb-interface Signalling Link (SL) congestion.

Pegging

This statistic pegs each time an MSU is discarded due to Lb-interface SL congestion.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof MSUs are being discarded due to SL congestion that are acceptable in normal systemoperations.

If the specified threshold is exceeded, the 10. LMTL: MSUs discarded due to SLcongestion – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 LMTP_CHANGEBACK

14 Feb 2003


68P02901W56-L 8–7

LMTP_CHANGEBACK{3974}

Description

The LMTP_CHANGEBACK statistic tracks the number of local automatic changebacksthat have been successfully completed.

Pegging

This statistic pegs when MTP traffic that has been changed over to an alternateSignalling Link (SL) is diverted back to the original SL.

Analysis

This statistic can be used for trend analysis of automatic changebacks that have beensuccessfully completed.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).

Usage MTP C7 performance.

Fault finding.

Basis Lb SS7_LINK.

Type Counter.

GSR6LMTP_CHANGEOVER

14 Feb 20038–8


68P02901W56-L

LMTP_CHANGEOVER{3974}

Description

The LMTP_CHANGEOVER statistic tracks the number of local automatic changeoversthat have been successfully completed. This indicates MTP traffic is being transferredfrom an Lb interface Signalling Link (SL) that is going out of service to an alternate SL.

Pegging

This statistic pegs when MTP traffic is changed over to an alternate Lb interface SL.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof out of sequence messages between a BSS and an SMLC that are acceptable innormal system operations.

If the specified threshold is exceeded, the 7. LMTL: SL number of negative acksreceived – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_LOCAL_SL_CONGESTION

14 Feb 2003


68P02901W56-L 8–9

LMTP_LOCAL_SL_CONGESTION{3974}

Description

The LMTP_LOCAL_SL_CONGESTION statistic tracks once for each onset ofcongestion across the Lb-interface Signalling Link (SL).

There are two types of congestion that may occur across an Lb interface SL: localcongestion (that is the MTP L2 of the BSS detects that the TX queue is full) and remotecongestion (that is the BSS-based SMLC is congested). Both types of congestion mayexist across an Lb-interface SL at one time; however, regardless of congestion type, thestatistic is pegged only upon the entrance into the congested state of the Lb-interface SL.Thus, if the Lb-interface SL is locally congested and remote congestion is detected, thestatistic is not pegged. Likewise, if the Lb-interface SL is remotely congested and localcongestion is detected, the statistic is not pegged.

Pegging

The statistic pegs each time the Lb-interface SL goes into the congestion state at thelocal site.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof congestion onsets that are acceptable in normal system operations.

If the specified threshold is exceeded, the 12. LMTL :SL Congestion Indications – PMalarm is generated.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6LMTP_LINK_INS

14 Feb 20038–10


68P02901W56-L

LMTP_LINK_INS{3974}

Description

The LMTP_LINK_INS statistic tracks the length of time that an Lb-interface SignallingLink (SL) is in the in-service state.

Pegging

The timer for this statistic is started when an SL is brought into service. The timer isstopped when the Lb–interface SL is removed from service.

Analysis

This statistic can be used for trend analysis of the utilization of in-service SLs.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.


GSR6 LMTP_LINKFAIL

14 Feb 2003


68P02901W56-L 8–11

LMTP_LINKFAIL{3974}

Description

The LMTP_LINKFAIL statistic tracks the duration of the Lb-interface Signalling Link (SL)unavailability due to SL failure. It records the total time a particular SL is out of servicewhile trying to align to the SMLC.

Pegging

This statistic timer is started when the SL fails. It is stopped when the SL comes backinto service.

Analysis

This statistic can be used for analysis of SL unavailability due to SL failure.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).

Usage MTP C7 availability.

Fault finding.

Basis Lb SS7_LINK.


GSR6LMTP_LOCAL_BUSY

14 Feb 20038–12


68P02901W56-L

LMTP_LOCAL_BUSY{3974}

Description

The LMTP_LOCAL_BUSY statistic tracks the total time congestion is present on thelocal end of the Lb-interface Signalling Link (SL).

Pegging

This statistic is started when congestion is detected on an Lb-interface SL. The statisticis stopped when normal operation is resumed.

Analysis

This statistic can be used for trend analysis on congestion durations on the local end ofthe SL.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis Lb SS7_LINK.


GSR6 LMTP_LOCAL_MGT

14 Feb 2003


68P02901W56-L 8–13

LMTP_LOCAL_MGT{3974}

Description

The LMTP_LOCAL_MGT statistic tracks the total time that a local Lb-interface SignallingLink (SL) is inhibited due to local management actions.

Pegging

This statistic is started each time the SL is inhibited due to local management actions,and stopped when the link is enabled.

Analysis

This statistic can be used for trend analysis on inhibited local SLs due to localmanagement action.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.


GSR6LMTP_MGT_INHIBIT

14 Feb 20038–14


68P02901W56-L

LMTP_MGT_INHIBIT{3974}

Description

The LMTP_MGT_INHIBIT statistic tracks the number of times the Lb-interface SignallingLink (SL) is inhibited by the operator.

Pegging

This statistic is started each time the Lb-interface SL is inhibited by the operator.

Analysis

This statistic can be used for trend analysis on inhibited SLs using the shutdowncommand on the associated MTP link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_MGT_UNINHIBIT

14 Feb 2003


68P02901W56-L 8–15

LMTP_MGT_UNINHIBIT{3974}

Description

The LMTP_MGT_UNINHIBIT statistic tracks the number of times the Lb-interfaceSignalling Link (SL) is uninhibited by the operator.

Pegging

This statistic is pegged each time the SL is uninhibited by the operator.

Analysis

This statistic can be used for trend analysis on uninhibited SLs using the unlockcommand on the associated MTP link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6LMTP_MSU_RX

14 Feb 20038–16


68P02901W56-L

LMTP_MSU_RX{3974}

Description

The LMTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)received on a Lb-interface signalling link.

Pegging

This statistic pegs each time MSUs are received over the Lb-interface signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_MSU_TX

14 Feb 2003


68P02901W56-L 8–17

LMTP_MSU_TX{3974}

Description

The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)transmitted on an Lb-interface signalling link.

Pegging

This statistic pegs each time MSUs are transmitted over the Lb-interface signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6LMTP_NEG_ACKS

14 Feb 20038–18


68P02901W56-L

LMTP_NEG_ACKS{3974}

Description

The LMTP_NEG_ACKS statistic tracks the number of out-of-sequence messagesbetween a BSS and the BSS-based SMLC across the Lb-interface signalling link.

Pegging

This statistic pegs when the BSS detects out of order messages to the SMLC andrequests retransmission.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof out of sequence messages between a BSS and an SMLC that are acceptable innormal system operations.

If the specified threshold is exceeded, the 7. LMTL: SL number of negative acksreceived – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 LMTP_RE_TX

14 Feb 2003


68P02901W56-L 8–19

LMTP_RE_TX{3974}

Description

The LMTP_RE_TX statistic tracks the number of octets that the BSS has retransmittedto the SMLC because the SMLC has requested retransmission. This indicates howmuch the BSS and an SMLC are off in message sequencing by the number of octetsretransmitted.

Pegging

This statistic peg the number of octets retransmitted by the BSS to the SMLC.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof octet retransmissions that are acceptable in normal system operations.

If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted –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).


Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6LMTP_REMOTE_MGT

14 Feb 20038–20


68P02901W56-L

LMTP_REMOTE_MGT{3974}

Description

The LMTP_REMOTE_MGT statistic tracks the total time an Lb-interface Signalling Link(SL) is remotely inhibited by the SMLC.

Pegging

This statistic pegs the duration of the Lb-interface SL inhibition due to remotemanagement action.

Analysis

This statistic can be used for trend analysis of remote management SL inhibition actions.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Duration (total time in milliseconds (ms).

GSR6 LMTP_REMOTE_PROC

14 Feb 2003


68P02901W56-L 8–21

LMTP_REMOTE_PROC{3974}

Description

The LMTP_REMOTE_PROC statistic tracks the time that a remote processor is out ofservice.

Pegging

This statistic pegs when a remote processor outage is identified, and stopped when theprocessor outage condition ceases.

Analysis

This statistic can be used for trend analysis of remote processor outage occurrences inthe BSS-based SMLC.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Duration (total time in milliseconds (ms).

GSR6LMTP_RESTORATION

14 Feb 20038–22


68P02901W56-L

LMTP_RESTORATION{3974}

Description

The LMTP_RESTORATION statistic tracks the number of times user traffic is allowed onan Lb-interface Signalling Link (SL) that is in service and not inhibited. This statistic doesnot track recovery from link fail.

Pegging

This statistic pegs when the Lb–interface SL starts carrying user traffic. This happenswhen the Lb–interface SL comes into service, is uninhibited, or recovers from a remoteprocessor outage.

Analysis

This statistic can be used for trend analysis of used traffic being allowed on an SL.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_SIF_SIO_RX

14 Feb 2003


68P02901W56-L 8–23

LMTP_SIF_SIO_RX{3974}

Description

The LMTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) orService Information Octets (SIO) that are received over an Lb-interface signalling link.

Pegging

This statistic pegs each time an SIF or SIO is received over an Lb-interface signallinglink.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6LMTP_SIF_SIO_TX

14 Feb 20038–24


68P02901W56-L

LMTP_SIF_SIO_TX{3974}

Description

The LMTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) orService Information Octets (SIO) that are transmitted over a signalling link by the BSC tothe SMLC.

Pegging

This statistic pegs each time an SIF or SIO are transmitted over a signalling link by theBSC to the SMLC.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_SL_ACK

14 Feb 2003


68P02901W56-L 8–25

LMTP_SL_ACK{3974}

Description

The LMTP_SL_ACK statistic tracks the number of times that the link was lost due to anLb-interface MTP layer 2 T7 timer expiry.

Pegging

This statistic pegs each time the link is lost due to a timer that expires when anacknowledgement from the BSS-based SMLC is not received.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof acknowledgements of MSUs not being received by the BSC that are acceptable innormal system operations.

If the specified threshold is exceeded, the 2. LMTL: SL failure - excessive delay ofACK – PM alarm is generated. Refer to the Maintenance Information: Alarm Handling atthe OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6LMTP_SL_ALIGNMENT

14 Feb 20038–26


68P02901W56-L

LMTP_SL_ALIGNMENT{3974}

Description

The LMTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attempts toalign an out-of-service LMTL.

Pegging

This statistic pegs each time an out of service Signalling Link (SL) unsuccessfully tries toalign with the Lb-interface.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof unsuccessful attempts to align an out-of-service SL to the Lb-interface that areacceptable in normal system operations.

If the specified threshold is exceeded, the 5. LMTL: SL alignment failure – PM alarm isgenerated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

Alarm Minor.

GSR6 LMTP_REMOTE_SL_CONGESTION

14 Feb 2003


68P02901W56-L 8–27

LMTP_REMOTE_SL_CONGESTION{3974}

Description

The LMTP_REMOTE_SL_CONGESTION statistic tracks the number of times theremote congestion timer expires for the Lb-interface signalling link.

Pegging

This statistic pegs each time the remote congestion timer expires.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofoccurrences of excessive congestion duration at the remote Signalling Link (SL) that areacceptable 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: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6LMTP_SL_ERROR_RATE

14 Feb 20038–28


68P02901W56-L

LMTP_SL_ERROR_RATE{3974}

Description

The LMTP_SL_ERROR_RATE statistic tracks the number of times that an Lb-interfaceSignalling Link (SL) is lost due to the expiration of the Signal Unit Error Rate Monitor(SUERM) timer.

Pegging

This statistic pegs each time the Lb-interface SL is lost due to the SUERM timerexpiration.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes an SL may be lost due to SUERM timer expirations that are acceptable in normalsystem 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).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6 LMTP_SL_FAIL

14 Feb 2003


68P02901W56-L 8–29

LMTP_SL_FAIL{3974}

Description

The LMTP_SL_FAIL statistic tracks the Lb-interface Signalling Link (SL) failure for allcauses except operator interaction through the MMI.

Pegging

This statistic is pegged when an Lb-interface SL fails for any reason except operatorinteraction through the MMI.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofSL failures, excluding those caused by operator interaction with the MMI, that areacceptable 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6LMTP_SL_FIBR

14 Feb 20038–30


68P02901W56-L

LMTP_SL_FIBR{3974}

Description

The LMTP_SL_FIBR statistic tracks the number of out-of-sequence messages betweena BSC and the BSS-based SMLC that result in an Lb-interface Signalling Link (SL) goingout of service. This statistic is similar to the LMTP_NEG_ACKS statistic, but signals amore severe condition.

Pegging

This statistic pegs when the SL is lost due to the detection of an abnormal ForwardIndicator Bit (FIB) caused by the de-synchronization of the Backward Sequence Number(BSN) and Forward Sequence Number (FSN).

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes an SL may be lost due to the detection of an abnormal FIB that are acceptable innormal 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Major.

GSR6 LMTP_START_RPO

14 Feb 2003


68P02901W56-L 8–31

LMTP_START_RPO{3974}

Description

The LMTP_START_PRO statistic tracks the number of times a processor outage occursin the BSS-based SMLC.

Pegging

This statistic is pegged each time the BSS is notified that the BSS-based SMLC hasexperienced a processor outage.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofremote processor 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6LMTP_STOP_RPO

14 Feb 20038–32


68P02901W56-L

LMTP_STOP_RPO{3974}

Description

The LMTP_STOP_RPO statistic tracks the number of times a processor outagecondition has ceased in the BSS-based SMLC.

Pegging

This statistic pegs each time the remote processor outage stops.

Analysis

This statistic can be used for trend analysis of remote processor outage condition is nolonger present.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

GSR6 LMTP_SU_ERROR

14 Feb 2003


68P02901W56-L 8–33

LMTP_SU_ERROR{3974}

Description

The LMTP_SU_ERROR statistic tracks the number of times erroneous signal units arereceived on the Lb-interface Signalling Link (SL).

Pegging

This statistic pegs each time an erroneous signal unit is received on the Lb-interface SS7SL.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes erroneous signal units may be received on the SL that are acceptable in normalsystem 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.

Type Counter.

Alarm Warning.

GSR6LMTP_UNAVAILABLE

14 Feb 20038–34


68P02901W56-L

LMTP_UNAVAILABLE{3974}

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.

Pegging

This statistic records the duration of Lb-interface SL unavailability for all reasons,including operator intervention through the MMI.

Analysis

This statistic can be used for trend analysis of the duration of SL outages, including thosecaused by operator interaction.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis Lb SS7_LINK.


GSR6 LMTP_SIB_RX

14 Feb 2003


68P02901W56-L 8–35

LMTP_SIB_RX{3974}

Description

The LMTP_SIB_RX statistic tracks the number of Status Indication Busy LSSUmessages received over an Lb-interface Signalling Link (SL).

Pegging

This statistic is pegged each time the BSS receives a Status Indication Busy (SIB) LSSUmessage across the Lb-interface signalling link.

Analysis


Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis Lb SS7_Link.

Type Counter.

GSR6LMTP_SIB_TX

14 Feb 20038–36


68P02901W56-L

LMTP_SIB_TX{3974}

Description

The LMTP_SIB_TX statistic tracks the number of Status Indication Busy LSSUmessages transmitted over an Lb-interface Signalling Link (SL).

Pegging

This statistic is pegged each time the BSS transmits a Status Indication Busy (SIB)LSSU message across the Lb-interface signalling link.

Analysis


Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_Link.

Type Counter.

GSR6 LMTP_CONGESTION

14 Feb 2003


68P02901W56-L 8–37

LMTP_CONGESTION{3974}

Description

The LMTP_CONGESTION statistic tracks the time the Lb-interface Signalling Link (SL)is congested.

Pegging

The timer for this statistic is started when congestion is detected on an Lb interfacesignalling link. The timer is stopped when normal operation is resumed.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis Lb SS7_Link.

Type Duration.

GSR6LMTP_CONGESTION

14 Feb 20038–38


68P02901W56-L

14 Feb 2003


68P02901W56-L 9–1

Chapter 9

BSS statistics for Location

Services support

GSR6

14 Feb 20039–2


68P02901W56-L

GSR6 Introduction to BSS statistics for supported location services

14 Feb 2003


68P02901W56-L 9–3

Introduction to BSS statistics for supported location services{3974}

Description

This chapter includes descriptions of statistics for the supported BSS location services.

Connection establishment

Connection establishment statistics track access and channel request functions. Thefollowing statistics are connection establishment statistics and are pegged for locationservices:

S CHAN_REQ_CAUSE_ATMPT.

S OK_ACC_PROC.

GSR6BSSMAP_PERF_LOC_REQ_MSGS

14 Feb 20039–4


68P02901W56-L

BSSMAP_PERF_LOC_REQ_MSGS{3974}

Description

The BSSMAP_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAPperform location request messages received on the A-interface.

Pegging

This statistic pegs each time a BSSMAP perform location request message isreceived on A-interface.

Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSMAP_PERF_LOC_ABORT_MSGS

14 Feb 2003


68P02901W56-L 9–5

BSSMAP_PERF_LOC_ABORT_MSGS{3974}

Description

The BSSMAP_PERF_LOC_ABORT_MSGS statistic tracks the number of BSSMAPperform location abort messages received on the A-interface.

Pegging

This statistic pegs each time a BSSMAP perform location abort message is receivedon the A-interface.

Reference GSM 03.71 v7.4.0, sect 7.11.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSMAP_PERF_LOC_RESP_MSGS

14 Feb 20039–6


68P02901W56-L

BSSMAP_PERF_LOC_RESP_MSGS{3974}

Description

The BSSMAP_PERF_LOC_RESP_MSGS statistic tracks the number of BSSMAPperform location response messages sent on A-interface.

Pegging

This statistic pegs each time a BSSMAP perform location response message is senton A-interface.

Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSMAPLE_PERF_LOC_REQ_MSGS

14 Feb 2003


68P02901W56-L 9–7

BSSMAPLE_PERF_LOC_REQ_MSGS{3974}

Description

The BSSMAPLE_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAP-LEperform location request messages sent on the Lb-interface.

Pegging

This statistic pegs each time a BSSMAP-LE perform location request message is senton Lb-interface.

Reference GSM 03.71 v7.4.0, sect 7.5, 7.6, 7.7, 7.11, 8.1

GSM 09.31 v7.1.0, sect 9.1.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSMAPLE_PERF_LOC_ABORT_MSGS

14 Feb 20039–8


68P02901W56-L

BSSMAPLE_PERF_LOC_ABORT_MSGS{3974}

Description

The BSSMAPLE_PERF_LOC_ABORT_MSGS statistic tracks the number ofBSSMAP-LE perform location abort messages sent on the Lb-interface.

Pegging

This statistic pegs each time a BSSMAP-LE perform location abort message is senton Lb-interface.

Reference GSM 03.71 v7.4.0, sect 7.11

GSM 09.31 v7.1.0, sect 9.3.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSMAPLE_PERF_LOC_RESP_MSGS

14 Feb 2003


68P02901W56-L 9–9

BSSMAPLE_PERF_LOC_RESP_MSGS{3974}

Description

The BSSMAPLE_PERF_LOC_RESP_MSGS statistic tracks the number ofBSSMAP-LE perform location response messages received on the Lb-interface.

Pegging

This statistic pegs each time a BSSMAP-LE perform location response message isreceived 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


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSLAP_TA_REQ

14 Feb 20039–10


68P02901W56-L

BSSLAP_TA_REQ{3974}

Description

The BSSLAP_TA_REQ statistic tracks the number of BSSLAP TA request messagesreceived.

Pegging

This statistic pegs each time a BSSLAP TA request message is received.


GSM 08.71 v7.2.0, sect. 2.2.1.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSLAP_TA_RESP

14 Feb 2003


68P02901W56-L 9–11

BSSLAP_TA_RESP{3974}

Description

The BSSLAP_TA_RESP statistic tracks the number of BSSLAP TA responsemessages sent.

Pegging

This statistic pegs each time a BSSLAP TA response message is sent.


GSM 08.71 v7.2.0, sect. 2.2.2.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSLAP_TOA_REQ

14 Feb 20039–12


68P02901W56-L

BSSLAP_TOA_REQ{3974}

Description

The BSSLAP_TOA_REQ statistic tracks the number of BSSLAP TOA requestmessages received.

Pegging

This statistic pegs each time a BSSLAP TOA request message is received.

Reference GSM 03.71 v7.4.0, sect. 9.1.

GSM 08.71 v7.2.0, sect. 2.2.3.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSLAP_REJ

14 Feb 2003


68P02901W56-L 9–13

BSSLAP_REJ{3974}

Description

The BSSLAP_REJ statistic tracks the number of BSSLAP reject messages sent.

Pegging

This statistic pegs each time a BSSLAP reject message is sent.


GSM 08.71 v7.2.0, sect. 2.2.5.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSLAP_RESET

14 Feb 20039–14


68P02901W56-L

BSSLAP_RESET{3974}

Description

The BSSLAP_RESET statistic tracks the number of BSSLAP reset messages sent.

Pegging

This statistic pegs each time a BSSLAP reset message is sent.


GSM 08.71 v7.2.0, sect. 2.2.6.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSLAP_ABORT_SENT

14 Feb 2003


68P02901W56-L 9–15

BSSLAP_ABORT_SENT{3974}

Description

The BSSLAP_ABORT_SENT statistic tracks the number of BSSLAP abort messagessent.

Pegging

This statistic pegs each time a BSSLAP abort message is sent.


GSM 08.71 v7.2.0, sect. 2.2.7.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSLAP_ABORT_RCV

14 Feb 20039–16


68P02901W56-L

BSSLAP_ABORT_RCV{3974}

Description

The BSSLAP_ABORT_RCV statistic tracks the number of BSSLAP abort messagesreceived.

Pegging

This statistic pegs each time a BSSLAP abort message is received.


GSM 08.71 v7.2.0, sect. 2.2.7.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSLAP_MS_POS_CMD

14 Feb 2003


68P02901W56-L 9–17

BSSLAP_MS_POS_CMD{3974}

Description

The BSSLAP_MS_POS_CMD statistic tracks the number of BSSLAP MS positioncommand messages received..

Pegging

This 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.


Fault finding.

Basis BSS.

Type Counter.

GSR6BSSLAP_MS_POS_RESP

14 Feb 20039–18


68P02901W56-L

BSSLAP_MS_POS_RESP{3974}

Description

The BSSLAP_MS_POS_RESP statistic tracks the number of BSSLAP MS positionresponse messages sent.

Pegging

This 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.


Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSMAP_CONLESS_INFO_RCV

14 Feb 2003


68P02901W56-L 9–19

BSSMAP_CONLESS_INFO_RCV{3974}

Description

The BSSMAP_CONLESS_INFO_RCV statistic tracks the number of BSSMAPconnectionless information messages received.

Pegging

This statistic pegs each time a BSSMAP connectionless information message isreceived.



Fault finding.

Basis BSS.

Type Counter.

GSR6BSSMAP_CONLESS_INFO_SENT

14 Feb 20039–20


68P02901W56-L

BSSMAP_CONLESS_INFO_SENT{3974}

Description

The BSSMAP_CONLESS_INFO_SENT statistic tracks the number of BSSMAPconnectionless information messages sent.

Pegging

This statistic pegs each time a BSSMAP connectionless information message is sent.



Fault finding.

Basis BSS.

Type Counter.

GSR6 BSSMAPLE_CONLESS_INFO_RCV

14 Feb 2003


68P02901W56-L 9–21

BSSMAPLE_CONLESS_INFO_RCV{3974}

Description

The BSSMAPLE_CONLESS_INFO_RCV statistic tracks the number of Lb-interfaceBSSMAP-LE connectionless information messages received.

Pegging

This statistic pegs each time a BSSMAP-LE connectionless information message isreceived.



Fault finding.

Basis BSS.

Type Counter.

GSR6BSSMAPLE_CONLESS_INFO_SENT

14 Feb 20039–22


68P02901W56-L

BSSMAPLE_CONLESS_INFO_SENT{3974}

Description

The BSSMAPLE_CONLESS_INFO_SENT statistic tracks the number of Lb-interfaceBSSMAP-LE connectionless information messages sent.

Pegging

This statistic pegs each time a BSSMAP-LE connectionless information message issent.

Reference GSM 03.71 v7.4.0, sect. 7.8,


Fault finding.

Basis BSS.

Type Counter.

14 Feb 2003


68P02901W56-L 10–1

Chapter 10

MTL statistics

GSR6

14 Feb 200310–2


68P02901W56-L

GSR6 Introduction to MTL Statistics

14 Feb 2003


68P02901W56-L 10–3

Introduction to MTL Statistics

DescriptionThis chapter includes descriptions of the Message Transfer Link (MTL) statistics. MTLstatistics are organized into the following Message Transfer Part (MTP) groups:

S MTP C7 availability.

S MTP C7 performance.

S MTP C7 utilization.

MTP C7 availabilityMTP 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 toMSC interface. The following are the MTP C7 availability statistics:

S MTP_LINKFAIL.

S MTP_LOCAL_BUSY.

S MTP_LOCAL_MGT.

S MTP_MGT_INHIBIT.

S MPT_MGT_UNINHIBIT.

S MTP_REMOTE_MGT.

S MTP_REMOTE_PROC.

S MTP_START_RPO.

S MTP_STOP_RPO.

S MTP_UNAVAILABLE.

MTP C7 performanceMTP C7 performance statistics are used track the different types of failure and recoverysituations for the Message Transfer Part (MTP) of the ITU-TSS No.7 protocol on theBSC to MSC interface. The following are the MTP C7 performance statistics:

S MTP_CHANGEBACK.

S MTP_CHANGEOVER.

S MTP_LINK_INS.

S MTP_NEG_ACKS.

S MTP_RESTORATION.

S MTP_SL_ACK.

S MTP_SL_ALIGNMENT.

S MTP_SL_CONGESTION .

S MTP_SL_ERROR_RATE.

S MTP_SL_FAIL.

S MTP_SL_FIBR.

S MTP_SU_ERROR.

GSR6Introduction to MTL Statistics

14 Feb 200310–4


68P02901W56-L

MTP C7 utilization

MTP C7 utilization statistics are used to track the number of messages received,transmitted and retransmitted on signalling links and supply information on signalling linkcongestion for the MTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. Thefollowing are the MTP C7 utilization statistics:

S BUSY_CICS.

S CONGESTION_LOST_MSU .

S MSU_DISCARDED.

S MTP_CONGESTION .

S MTP_MSU_RX.

S MTP_MSU_TX.

S MTP_RE_TX.

S MTP_SIF_SIO_RX.

S MTP_SIF_SIO_TX .

S SIB_RX.

S SIB_TX.

S SL_CONGESTION.

S SL_STOP_CONGESTION .

GSR6 BUSY_CICS

14 Feb 2003


68P02901W56-L 10–5

BUSY_CICS

Description

The BUSY_CICS statistic tracks the number of BUSY CICS during an interval. Thisweighted distribution statistics produces a mean value indicating the average number ofCICs 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

Pegging

This statistic is pegged each time an allocation or deallocation of a CIC is detected. It isan indication 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.

Analysis

Since each call is routed via the MSC (even intra-BSS and intra-cell), the number of CICsrepresent the number of calls in progress under that MSC for this BSS.

Reference None.


Network planning.

Optimization.

Basis BSS.


GSR6CONGESTION_LOST_MSU

14 Feb 200310–6


68P02901W56-L

CONGESTION_LOST_MSU

Description

The CONGESTION_LOST_MSU statistic tracks the number of times Message SignallingUnits (MSU) are being lost due to Signalling Link (SL) congestion.

Pegging

This statistic pegs for each congestion event which results in MSUs being lost.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof lost MSUs due to SL congestion that are acceptable in normal system operations.

If the specified threshold is exceeded, the 11. MTL: SL congestion events resulting inloss of MSUs – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 MSU_DISCARDED

14 Feb 2003


68P02901W56-L 10–7

MSU_DISCARDED

Description

The MSU_DISCARDED statistic tracks the number of MSUs discarded while there iscongestion on the Signalling Link (SL).

Pegging

This statistic pegs each time a MSU is discarded while there is congestion on the SL.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof MSUs are being discarded due to SL congestion that are acceptable in normal systemoperations.

If the specified threshold is exceeded, the 10. MTL: MSUs discarded due to SLcongestion – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6MTP_CHANGEBACK

14 Feb 200310–8


68P02901W56-L

MTP_CHANGEBACK

Description

The MTP_CHANGEBACK statistic tracks the number of local automatic changebacksthat have been successfully completed.

Pegging

This statistic pegs when MTP traffic that has been changed over to an alternateSignalling Link (SL) is diverted back to the original SL.

Analysis

This statistic can be used for trend analysis of automatic changebacks that have beensuccessfully completed.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

GSR6 MTP_CHANGEOVER

14 Feb 2003


68P02901W56-L 10–9

MTP_CHANGEOVER

Description

The MTP_CHANGEOVER statistic tracks the number of local automatic changeoversthat have been successfully completed. This indicates MTP traffic is being transferredfrom a Signalling Link (SL) that is going out of service to an alternate SL.

Pegging

This statistic pegs when MTP traffic is changed over to an alternate SL.

Analysis

This statistic can be used for trend analysis of local automatic changeovers that havebeen successfully completed.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

GSR6MTP_CONGESTION

14 Feb 200310–10


68P02901W56-L

MTP_CONGESTION

Description

The MTP_CONGESTION statistic tracks the length of time that a signalling link iscongested. This can be used to indicate signalling link congestion.

Pegging

The timer for this statistic is started when congestion is detected on a signalling link. Thetimer is stopped when normal operation is resumed.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_LINK.


GSR6 MTP_LINK_INS

14 Feb 2003


68P02901W56-L 10–11

MTP_LINK_INS

Description

The MTP_LINK_INS statistic tracks the length of time that a signalling link (SL) is in thein-service state.

Pegging

The timer for this statistic is started when an SL is brought into service. The timer isstopped when the SL is removed from service.

Analysis

This statistic can be used for trend analysis of the utilization of in-service SLs.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.


GSR6MTP_LINKFAIL

14 Feb 200310–12


68P02901W56-L

MTP_LINKFAIL

Description

The MTP_LINKFAIL statistic tracks the duration of Signalling Link (SL) unavailability dueto SL failure. It records the total time a particular SL is out of service while trying to align.

Pegging

This statistic pegs each time the SL tries to align with the A interface while it is out ofservice. The statistic timer is started when the SL fails. It is stopped when the SL comesback into service.

Analysis

This statistic can be used for analysis of SL unavailability due to SL failure.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.


GSR6 MTP_LOCAL_BUSY

14 Feb 2003


68P02901W56-L 10–13

MTP_LOCAL_BUSY

Description

The MTP_LOCAL_BUSY statistic tracks the total time congestion is present on the localend of the Signalling Link (SL).

Pegging

This statistic is started when congestion is detected on an SL. The statistic is stoppedwhen normal operation is resumed.

Analysis

This statistic can be used for trend analysis on congestion durations on the local end ofthe SL.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_LINK.


GSR6MTP_LOCAL_MGT

14 Feb 200310–14


68P02901W56-L

MTP_LOCAL_MGT

Description

The MTP_LOCAL_MGT statistic tracks the total time that a local Signalling Link (SL) isinhibited due to local management actions.

Pegging

This statistic is started each time the SL is inhibited due to local management actionsand stopped when the link is enabled.

Analysis

This statistic can be used for trend analysis on inhibited local SLs due to localmanagement action.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.


GSR6 MTP_MGT_INHIBIT

14 Feb 2003


68P02901W56-L 10–15

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.

Pegging

This statistic is started each time the SL is inhibited by the user entering the shutdowncommand on the associated MTP link.

Analysis

This statistic can be used for trend analysis on inhibited SLs using the shutdowncommand on the associated MTP link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6MTP_MGT_UNINHIBIT

14 Feb 200310–16


68P02901W56-L

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.

Pegging

This statistic is started each time the SL is uninhibited using the unlock command on anSL that was previously inhibited.

Analysis

This statistic can be used for trend analysis on uninhibited SLs using the unlockcommand on the associated MTP link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6 MTP_MSU_RX

14 Feb 2003


68P02901W56-L 10–17

MTP_MSU_RX

Description

The MTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)received on a particular signalling link.

Pegging

This statistic pegs each time MSUs are received over the signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6MTP_MSU_TX

14 Feb 200310–18


68P02901W56-L

MTP_MSU_TX

Description

The MTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)transmitted on a particular signalling link.

Pegging

This statistic pegs each time MSUs are transmitted over the signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6 MTP_NEG_ACKS

14 Feb 2003


68P02901W56-L 10–19

MTP_NEG_ACKS

Description

The MTP_NEG_ACKS statistic tracks when the messages between a BSS and an MSCget out of sequence.

Pegging

This statistic pegs when the BSS detects out of order messages to the MSC and requestretransmission.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof out of sequence messages between a BSS and a MSC that are acceptable in normalsystem operations.

If the specified threshold is exceeded, the 7. MTL: SL number of negative acksreceived – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6MTP_RE_TX

14 Feb 200310–20


68P02901W56-L

MTP_RE_TX

Description

The MTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted tothe MSC because the MSC has requested retransmission. This indicates how much theBSS and an MSC are off in message sequencing by the number of octets retransmitted.

Pegging

This statistic pegs the number of octets retransmitted by the BSS to the MSC.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 MTP_REMOTE_MGT

14 Feb 2003


68P02901W56-L 10–21

MTP_REMOTE_MGT

Description

The MTP_REMOTE_MGT statistic tracks the total time a Signalling Link (SL) wasremotely inhibited.

Pegging

This statistic pegs the duration of the SL inhibition due to remote management actionuntil uninhibited.

Analysis

This statistic can be used for trend analysis of remote management SL inhibition actions.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Duration (total time in milliseconds (ms)).

GSR6MTP_REMOTE_PROC

14 Feb 200310–22


68P02901W56-L

MTP_REMOTE_PROC

Description

The MTP_REMOTE_PROC statistic tracks the time that a remote processor is out ofservice.

Pegging

This statistic pegs when a remote processor outage is identified and stopped when theprocessor outage condition ceases.

Analysis

This statistic can be used for trend analysis of remote processor outages.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Duration (total time in milliseconds (ms)).

GSR6 MTP_RESTORATION

14 Feb 2003


68P02901W56-L 10–23

MTP_RESTORATION

Description

The MTP_RESTORATION statistic tracks the number of times user traffic is allowed on aSignalling Link (SL) that is in service and not inhibited. This statistic does not trackrecovery from link fail.

Pegging

This statistic pegs when the SL starts carrying user traffic. This happens when the SLcomes into service, is uninhibited, or recovers from a remote processor outage.

Analysis

This statistic can be used for trend analysis of used traffic being allowed on an SL.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6MTP_SIF_SIO_RX

14 Feb 200310–24


68P02901W56-L

MTP_SIF_SIO_RX

Description

The MTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) orService Information Octets (SIO) that are received over a signalling link.

Pegging

This statistic pegs each time an SIF or SIO is received over the signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6 MTP_SIF_SIO_TX

14 Feb 2003


68P02901W56-L 10–25

MTP_SIF_SIO_TX

Description

The MTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) orService Information Octets (SIO) that are transmitted over a signalling link.

Pegging

This statistic pegs each time an SIF or SIO are transmitted over the signalling link.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

GSR6MTP_SL_ACK

14 Feb 200310–26


68P02901W56-L

MTP_SL_ACK

Description

The MTP_SL_ACK statistic tracks the number of times that the link was lost because atimer expired due to an acknowledgement that a Message Signal Unit (MSU) was notsent.

Pegging

This statistic pegs each time the link is lost due to a timer that expires when anacknowledgement of an MSU is not sent.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof acknowledgements of MSUs not being sent that are acceptable in normal systemoperations.

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 atthe OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

Alarm Major.

GSR6 MTP_SL_ALIGNMENT

14 Feb 2003


68P02901W56-L 10–27

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.

Pegging

This statistic pegs each time an out of service SL unsuccessfully tries to align with the Ainterface.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof unsuccessful attempts to align an out of service SL to the A interface that areacceptable in normal system operations.

If the specified threshold is exceeded, the 5. MTL: SL alignment failure – PM alarm isgenerated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

Alarm Minor.

GSR6MTP_SL_CONGESTION

14 Feb 200310–28


68P02901W56-L

MTP_SL_CONGESTION

Description

The MTP_SL_CONGESTION statistic tracks the number of times the remote site iscongested.

Pegging

This statistic pegs each time the remote congestion timer expires.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofoccurrences of excessive congestion duration at the remote that are acceptable innormal 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: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis SS7_LINK.

Type Counter.

Alarm Major.

GSR6 MTP_SL_ERROR_RATE

14 Feb 2003


68P02901W56-L 10–29

MTP_SL_ERROR_RATE

Description

The MTP_SL_ERROR_RATE statistic tracks the number of times that a Signalling Link(SL) is lost due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.

Pegging

This statistic pegs each time the SL is lost due to the SUERM timer expiration. (Refer toITU-TSS specification Q. 703, Section 102.)

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes an SL may be lost due to SUERM timer expirations that are acceptable in normalsystem operations.

If the specified threshold is exceeded, the 3. MTL: 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).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Major.

GSR6MTP_SL_FAIL

14 Feb 200310–30


68P02901W56-L

MTP_SL_FAIL

Description

The MTP_SL_FAIL statistic tracks Signalling Link (SL) failure for all causes exceptoperator interaction through the MMI.

Pegging

This statistic pegs when an SL fails for any reason except operator interaction throughthe MMI.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofSL failures, excluding those caused by operator interaction with the MMI, that areacceptable 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Major.

GSR6 MTP_SL_FIBR

14 Feb 2003


68P02901W56-L 10–31

MTP_SL_FIBR

Description

The MTP_SL_FIBR statistic tracks the messages between a BSS and a remote site areout of sequence, causing the Signalling Link (SL) to go out of service. This statistic issimilar to the MTP_NEG_ACKS statistic but signals a more severe condition.

Pegging

This statistic pegs when the SL is lost due to the detection of an abnormal ForwardIndicator Bit (FIB) caused by the de-synchronization of the Backward Sequence Number(BSN) and Forward Sequence Number (FSN).

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes an SL may be lost due to the detection of an abnormal FIB that are acceptable innormal 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Major.

GSR6MTP_START_RPO

14 Feb 200310–32


68P02901W56-L

MTP_START_RPO

Description

The MTP_START_PRO statistic tracks the number of times a remote processor outageoccurs.

Pegging

This statistic pegs each time a remote processor outage condition is identified.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number ofremote processor 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 MTP_STOP_RPO

14 Feb 2003


68P02901W56-L 10–33

MTP_STOP_RPO

Description

The MTP_STOP_RPO statistic tracks the number of times a remote processor outagecondition stops.

Pegging

This statistic pegs each time the remote processor outage stops.

Analysis

This statistic can be used for trend analysis of remote processor outages and restoration.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.

Type Counter.

GSR6MTP_SU_ERROR

14 Feb 200310–34


68P02901W56-L

MTP_SU_ERROR

Description

The MTP_SU_ERROR statistic tracks the number of times erroneous signal units arereceived on the Signalling Link (SL).

Pegging

This statistic pegs each time an erroneous signal unit is received on the SL.

Analysis

A threshold value should be assigned to this statistic reflecting the maximum number oftimes erroneous signal units may be received on the SL that are acceptable in normalsystem operations.

If the specified threshold is exceeded, the 6. MTL: Number of signal units in error –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).


Fault finding.

Basis SS7_LINK.

Type Counter.

Alarm Warning.

GSR6 MTP_UNAVAILABLE

14 Feb 2003


68P02901W56-L 10–35

MTP_UNAVAILABLE

Description

The MTP_UNAVAILABLE statistic tracks the total time a Signalling Link (SL) is out ofservice for all reasons including operator intervention.

Pegging

This statistic records the duration of SL unavailability for all reasons, including operatorintervention through the MMI.

Analysis

This statistic can be used for trend analysis of the duration of SL outages, including thosecaused by operator interaction.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis SS7_LINK.


GSR6SIB_RX

14 Feb 200310–36


68P02901W56-L

SIB_RX

Description

The SIB_RX statistic provides a means of calculating MTL utilization by counting thenumber of Status Indication Busy LSSU messages received.

Pegging

This statistic pegs each receipt of a Status Indication Busy (SIB) LSSU message on aper signalling link basis.

Analysis


Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_Link.

Type Counter.

GSR6 SIB_TX

14 Feb 2003


68P02901W56-L 10–37

SIB_TX

Description

The SIB_TX statistic provides a means of calculating MTL utilization by counting thenumber of Status Indication Busy LSSU messages transmitted.

Pegging

This statistic pegs each transmission of a Status Indication Busy (SIB) LSSU messageon a per signalling link basis.

Analysis


Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_Link.

Type Counter.

GSR6SL_CONGESTION

14 Feb 200310–38


68P02901W56-L

SL_CONGESTION

Description

The SL_CONGESTION statistic tracks the number of times the remote congestion timerexpires due to excessive duration on a Signalling Link (SL) failure.

Pegging

This statistic pegs each time the remote congestion timer expires due to excessiveduration of congestion on an SL failure.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof remote congestion 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: AlarmHandling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_Link.

Type Counter.

Alarm Warning.

GSR6 SL_STOP_CONGESTION

14 Feb 2003


68P02901W56-L 10–39

SL_STOP_CONGESTION

Description

The SL_STOP_CONGESTION statistic tracks Signalling Link (SL) congestion stoppage.

Pegging

This statistic is pegged each time the signalling link congestion indication stops.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Network planning.

Fault finding.

Basis SS7_Link.

Type Counter.

GSR6SL_STOP_CONGESTION

14 Feb 200310–40


68P02901W56-L

14 Feb 2003


68P02901W56-L 11–1

Chapter 11

CBL, GSL, OML, RSL and XBL

statistics

GSR6

14 Feb 200311–2


68P02901W56-L

GSR6 CBL GSL OML RSL and XBL statistics

14 Feb 2003


68P02901W56-L 11–3

CBL GSL OML RSL and XBL statistics

Introduction to CBL, GSL, OML, RSL, and XBL statistics

This chapter includes descriptions of the Cell Broadcast Link (CBL), GPRS SignallingLink (GSL), Operation and Maintenance Link (OML), Radio System Link (RSL), andRXCDR to BSC Link (XBL) statistics.

X.25/LAPD Level: X.25 and LAPD

X.25 and LAPD statistics are used to track BSS data transmission information. Thefollowing are the X.25 and LAPD statistics:

S ATER_PREEMPT_STATUS.

S ATER_STATUS.

S FRMR.

S I_FRAMES_RX.

S I_FRAMES_TX.

S INVALID_FRAMES_RX.

S LAPD_CONGESTION.

S N2_EXPIRY.

S SABM_TX.

GSR6ATER_PREEMPT_STATUS

14 Feb 200311–4


68P02901W56-L

ATER_PREEMPT_STATUS

Description

The ATER_PREEMPT_STATUS statistic tracks the number of calls pre-empted on anAter channel.


0 PREEMPT_ATTEMPT Counts the total number ofpre-emptions attempted of callsusing an Ater channel.

1 CALL_LEG_PREEMPT_EMERG_CALL Counts the number of call legspre-empted to support anemergency call. The emergency callwas able to pre-empt a lower prioritycall for an Ater resource.

2 CALL_LEG_PREEMPT_PRI_CALL Counts the number of call legspre-empted to support a high prioritynon-emergency call. The highpriority call was able to pre-empt alower priority call for an Aterresource.

3 PREEMPT_ATMPT_ATER_UNAVAIL Counts the number of pre-emptionattempts initiated due to no Aterchannels available. When a callassignment fails or a handover failsdue to no available Ater channels,the BSC will attempt tp pre-empt alower priority call to obtain an Aterresource.

4 PREEMPT_ATMPT_ATER_SWITCH Counts the number of pre-emptionattempts performed due toswitchover of Ater channels.

5 PREEMPT_FAIL_NO_VULN_CALL Counts the number of pre-emptionfailures because no call with a lowerpriority was found to pre-empt inwhich to obtain an ATER resource(eg a caller with a high priority wasunable to obtain access to thenetwork because it was fully utilizedwith callers of even higherpriorities).

6 PREEMPT_FAIL_COMM_ERR Counts the number of pre-emptionfailures due to BSC-RXCDRcommunication errors. The BSCmessage protocol to pre-empt anAter resource has timed out aftercontinual attempts to coordinate thepre-emption of the Ater resourcewith the RXCDR.

GSR6 ATER_PREEMPT_STATUS

14 Feb 2003


68P02901W56-L 11–5

Pegging

Counts the number of events relating to ATER pre-emption scenarios on a per XBLlinkset basis.

Reference None.

Usage Network planning, Optimization.


Basis AXCDR

Type Counter array.

GSR6ATER_STATUS

14 Feb 200311–6


68P02901W56-L

ATER_STATUS

Description

The ATER_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 requestedbut could not be allocated.

2 CALL_ASSIGN_FAIL_COMM_ERR

Counts the number of call assignment failuresdue to BSC-RXCDR communication errors. TheBSC message protocol to establish an Aterresource for the handover has timed out aftercontinual attempts tp allocate the Ater resourcewith the RXCDR.

3 HO_FAIL_COMM_ERR Counts the number of handover failures due toBSS-RXCDR communication errors. The BSCmessage protocol to establish an Ater resourcefor the handover has timed out after continualattempts to allocate the Ater resource with theRXCDR.

4 CALL_ASSIGN_FAIL_NO_ATER

Counts the number of call assignment failuresdue to no available Ater channels. When anassignment failure occurs due to no availableAter channels, the BSC will attempt to pre-emptany existing calls to obtain an Ater resource. Theability to pre-empt depends upon theemergency/priority setting for the call as well asthe emergency/priority settings of existing cal ls.

5 HO_FAIL_NO_ATER Counts the number of handover failures due tono available Ater channels. When a handoverfailure occurs due to no available Ater channels.the BSC will attempt to pre-empt any existingcalls to obtain an Ater resource. The ability topre-empt depends upon the emergency/prioritysetting for the call as well as theemergency/priority settings of existing calls.

6 BSC_INIT_BLK_CICS_LOW_ATER

Counts the number of times the event BSCinitiated blocking of CICs occurred. The peggingof this statistic represents the scenario where thenumber of available Ater channels to anassociated RXCDR falls below thedarbc_threshold when the BSC is operating inthe dynamic allocation mode. The BScautomatically blocks at the MSC all remainingidle CICs that are routed through the associatedRXCDR. All out of service and idle CICs willhave the “Low Channel Resources to theRXCDR” reason set.

Pegging

This statistic pegs the number of events relating to ATER allocation and assignmentoccasions on a per XBL linkback basis.

GSR6 ATER_STATUS

14 Feb 2003


68P02901W56-L 11–7

Reference None.


Fault finding.


Basis AXCDR.

Type Counter array.

GSR6FRMR

14 Feb 200311–8


68P02901W56-L

FRMR

Description

The FRMR statistic tracks the number of frames that were rejected because the frameswere not recoverable.

Pegging

This statistic pegs each time a frame is received that is not recoverable.

Reference ITU-TSS Q.920 – 1

ITU-TSS X.20 – X.32

Usage X.25/LAPD.

Fault finding.

Basis X25_LINK/LAPD_LINK.

Type Counter.

Alarm Warning.

GSR6 I_FRAMES_RX

14 Feb 2003


68P02901W56-L 11–9

I_FRAMES_RX

Description

The I_FRAMES_RX statistic tracks the number of Information Frames (I-Frames)received.

Pegging

This 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.

GSR6I_FRAMES_TX

14 Feb 200311–10


68P02901W56-L

I_FRAMES_TX

Description

The I_FRAMES_TX statistic tracks the number of Information Frames (I-Frames)transmitted.

Pegging

This statistic peg when an I-Frame is transmitted.



Usage X.25/LAPD.


Type Counter.

GSR6 INVALID_FRAMES_RX

14 Feb 2003


68P02901W56-L 11–11

INVALID_FRAMES_RX

Description

The INVALID_FRAMES_RX statistic tracks the number of invalid frames received.

Pegging

This statistic is pegged whenever an invalid frame is received.

S X.25

– On the OML (BSS–OMC-R).

– On the CBL (BSS–CBC).

S LAPD

– On the RSL (BSS–BTS link).

– On the XBL (BSC–RXCDR link).



Usage X.25/LAPD.

Fault finding.


Type Counter.

Alarm Warning.

GSR6LAPD_CONGESTION

14 Feb 200311–12


68P02901W56-L

LAPD_CONGESTION

Description

The LAPD_CONGESTION statistic tracks the time that the LAPD or X.25 link iscongested. This indicates the time period in milliseconds when the sending speed of theBSC/BTS processes is more than the link transmit capability and provides a way ofmonitoring when more links need to be added.

NOTE The exec–dlsp process has a bigger buffer to hold outgoingmessages therefore the messages will not get dropped evenduring the congestion period.

Pegging

This statistic pegs when the transmit buffer gets full and stops when the buffer isavailable again.



Usage X.25/LAPD.

Fault finding.


Type Duration.

GSR6 N2_EXPIRY

14 Feb 2003


68P02901W56-L 11–13

N2_EXPIRY

Description

The N2_EXPIRY statistic tracks the number of link alignment retries attempted withoutsuccess.

Pegging

This statistic pegs when the retry count threshold has been exceeded.



Usage X.25/LAPD.

Fault finding.


Type Counter.

Alarm Minor.

GSR6SABM_TX

14 Feb 200311–14


68P02901W56-L

SABM_TX

Description

The SABM_TX statistic tracks the links that come into service.

Pegging

This statistic is pegged for all Set Asynchronous Balanced Mode (SABM) frames.



Usage X.25/LAPD.


Type Counter.

14 Feb 2003


68P02901W56-L 12–1

Chapter 12

PCU statistics

GSR6

14 Feb 200312–2


68P02901W56-L

GSR6 PCU Statistics

14 Feb 2003


68P02901W56-L 12–3

PCU Statistics

Introduction

This chapter describes the Packet Control Unit (PCU) statistics. PCU statistics areorganized in the following groups:

S Gb link (GBL) statistics.

S Accessibility statistics.

S Throughput statistics.

S Dynamic allocation statistics.

To facilitate easy access, this chapter presents the statistics in alphabeticalorder.

NOTE

Description of Gb interface

The GBL device refers to the configured number of timeslots on an E1 link between thePCU and the Serving GPRS Support Node (SGSN). This interface is referred to as theGb interface. The Gb interface allows many users to be multiplexed over a commonphysical resource. GPRS signalling and user data are sent on the same physicalresource, that is, no dedicated physical resources are required to be allocated forsignalling purposes.

GBL statistics

The GBL measurement types are listed as follows:

S CELL_FLUSH_REQS.

S GBL_DL_DATA_THRPUT.

S GBL_DL_DATA_THRPUT_HIST.

S GBL_FLOW_CTRL_SENT.

S GBL_LINK_INS.

S GBL_PAGING_REQS.

S GBL_UL_DATA_THRPUT.

S GBL_UL_DATA_THRPUT_HIST.

S GBL_UNAVAILABLE.

GSR6PCU Statistics

14 Feb 200312–4


68P02901W56-L

Accessibility statistics

Accessibility statistics measure how effectively GPRS resources are being accessed.These measurements assist the operator in planning the necessary resources needed forthe MS to efficiently access the network.

The accessibility statistics include the following:

S CHANNEL_REQS_REC.

S CHANNEL_REQS_REJECT.

S {3750}{4386} CHANNEL_REQS_SUCCESS.

S {3750} CODING_SCHEME_CHANGE.

S CS12_ON_32K_CHAN.

S {3635} GPRS_32K_CHANNELS_SWITCHED.

S {3635} GPRS_32K_DL_NOT_AVAIL.

S {3635} GPRS_32K_UL_NOT_AVAIL.

S GPRS_ACCESS_PER_AGCH.

S GPRS_ACCESS_PER_RACH.

S {3969} GPRS_CELL_RESELECT_ATTMPT.

S {3969} GPRS_CELL_RESELECT_FAIL.

S GPRS_CHANNELS_SWITCHED.

S {3969} GPRS_MS_NEIGHBOR_STRONG .

S {3750} GPRS_PCH_AGCH_Q_LENGTH.

S MS_CLASS_1_10_REQ.



S {3725}NO_PDTCH_AVAIL.

S {3725}NO_PDTCH_AVAIL_TIME.

GSR6 PCU Statistics

14 Feb 2003


68P02901W56-L 12–5

Throughput statistics

The throughput statistics are listed as follows:

S {4253} AIR_DL_CONTROL_BLKS.

S AIR_DL_DATA_BLKS.

S {4253} AIR_UL_CONTROL_BLKS.

S AIR_UL_DATA_BLKS.

S {3750} AVAILABLE_PDTCH.

S {3750} DL_BUSY_PDTCH.

S {3750}{3969} DL_PDTCH_CONGESTION .

S {3750}{3969} DL_PDTCH_Q_LENGTH.

S {3750} DL_PDTCH_SEIZURE.

S GBL_DL_DATA_THRPUT.

S GBL_DL_DATA_THRPUT_HIST.

S GBL_UL_DATA_THRPUT.

S GBL_UL_DATA_THRPUT_HIST.

S {3750} IDLE_PDTCH_INTF_BAND0.





S {3750} IMM_ASSGN_CAUSE.

S {4253} PRP_LOAD.

S {3750} UL_BUSY_PDTCH.

S {3750}{3969} UL_PDTCH_CONGESTION .

S {3750} UL_PDTCH_Q_LENGTH.

S {3750}{4386} UL_PDTCH_SEIZURE.

Dynamic allocation statistics

The dynamic allocation statistics are listed as follows:

S GPRS_DYNET_FAILURES.

S GPRS_DYNET_RES_REQS.

S GPRS_DYNET_SWI_REQS.

GSR6AIR_DL_CONTROL_BLKS

14 Feb 200312–6


68P02901W56-L

AIR_DL_CONTROL_BLKS{4253}

Description

The AIR_DL_CONTROL_BLKS statistic tracks the number of downlink control RadioLink Control (RLC) blocks sent by the Packet Control Unit (PCU). Retransmissions ofcontrol blocks are included in this statistic.

Pegging

This statistic is pegged for each control block sent down.

Analysis

This statistic can be used for the trend analysis of the number of Radio Link Controlblocks sent by the PCU.

Reference None.

Usage Performance management.

Basis Cell.

Type Counter.

GSR6 AIR_DL_DATA_BLKS

14 Feb 2003


68P02901W56-L 12–7

AIR_DL_DATA_BLKS

Description

The AIR_DL_DATA_BLKS statistic tracks the number of blocks sent by the PCU to theMS for each quality of service (QoS) level and coding scheme combination.

NOTE QoS identifies how delay sensitive the traffic is. Currently onlyQoS3 is implemented which is the most delay insensitive trafficclass – 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












Pegging

The appropriate bin is incremented by the amount of data blocks sent by the PCU to theMS for the quality of service and coding scheme. Each count is rounded to the nearest100 blocks.

Reference None.


Basis Cell.

Type Counter array.

GSR6AIR_UL_CONTROL_BLKS

14 Feb 200312–8


68P02901W56-L

AIR_UL_CONTROL_BLKS{4253}

Description

The AIR_UL_CONTROL_BLKS statistic tracks the number of uplink control Radio LinkControl (RLC) blocks sent by the MS. Retransmissions of control blocks are included inthis statistic.

Pegging

This statistic is pegged for each control block sent down.

Analysis

This statistic can be used for the trend analysis of Radio Link Control blocks sent by theMS.

Reference None.

Usage Performance management.

Basis Cell.

Type Counter.

GSR6 AIR_UL_DATA_BLKS

14 Feb 2003


68P02901W56-L 12–9

AIR_UL_DATA_BLKS

Description

The AIR_UL_DATA_BLKS statistic tracks the number of data blocks received by thePCU for each quality of service level and coding scheme combination.


The bins are defined in Table 12-2.

Table 12-2 AIR_UL_DATA_BLKS counters














Pegging

The appropriate bin is incremented by the amount of data blocks received for the qualityof service and coding scheme. The count is rounded to the nearest 100 blocks.

Reference None.


Basis Cell.

Type Counter array.

GSR6AVAILABLE_PDTCH

14 Feb 200312–10


68P02901W56-L

AVAILABLE_PDTCH{3750}

Description

This statistic measures the mean and max number of available Packet Data TrafficCHannels (PDTCH).

This statistic is obtained by maintaining the current and total number of available PDTCHand the amount of time each PDTCH is available over the statistical period. Thecorresponding mean and maximum number of PDTCH are then computed. The PDTCHis available when its administrative state is unlocked or shutting down and theoperational state is enabled. It is unavailable when its administrative state changes tolocked or the operational state changes to disabled. The available number of PDTCHis then incremented or decremented when there is a change in PDTCH states asdescribed above. The available PDTCH counts both reserved PDTCHs and switchablePDTCHs 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

Pegging

The statistic pegs whenever there is a change in the channel configuration for anychannel in the cell (if the number of PDTCHs has not changed, it will be pegged with thesame value as before).

Analysis

This statistic can be used for trend analysis of PDTCH availability.

By comparing the number of available PDTCHs to the total number of PDTCHs in asystem, a percentage of utilization can be calculated. An analysis of the utilizationinformation can be used to determine the requirement for additional resources beforeproblems occur.

Reference Digital cellular telecommunications systems(phase 2+) Version 7.0.0 Jan 2000 ETSI.

Usage Congestion.

Network planning.

Basis Cell.

Type Gauge.

GSR6 CELL_FLUSH_REQS

14 Feb 2003


68P02901W56-L 12–11

CELL_FLUSH_REQS{3750}

Description

The CELL_FLUSH_REQS statistic tracks the number of flush requests received on theGBL(s) per cell basis.

Pegging

This statistic is pegged each time a flush request is received on the GBL to flush theLogical Link Control (LLC) Protocol Data Unit (PDU) for a particular MS.

Analysis

This statistic can be used for the trend analysis of the number of flushable messagesreceived by the BSS.

Reference None.


Congestion.

Basis Cell

Type Counter.

NOTE This statistic was previously known as GBL_FLUSH_REQS.

GSR6CHANNEL_REQS_REC

14 Feb 200312–12


68P02901W56-L

CHANNEL_REQS_REC

Description

The CHANNEL_REQS_REC statistic tracks the number of channel or resource requestmessages received by the PCU.

Pegging

This statistic pegs for each channel request message received by the PCU.

{4386} This statistic pegs when:

S A one phase channel request is received.

S An Enhanced One–Phase (EOP) access indication is received.

S A Packet Resource Request (PRR) message is received.

S A Packet Downlink Ack/Nack (PDAK) message is received.

Reference None.


Basis Cell.

Type Counter.

GSR6 CHANNEL_REQS_REJECT

14 Feb 2003


68P02901W56-L 12–13

CHANNEL_REQS_REJECT

Description

The CHANNEL_REQS_REJECT statistic tracks the number of rejections by the PCU forpacket channel or resource requests. The PCU rejects such requests because theresources are unavailable.

Pegging

This statistic pegs when an packet access reject message is sent to the MS in responseto a packet resource request when there are no resources left to allocate.

Reference None.


Congestion.

Basis Cell.

Type Counter.

GSR6CHANNEL_REQS_SUCCESS

14 Feb 200312–14


68P02901W56-L

CHANNEL_REQS_SUCCESS{3750} {4386}

Description

This statistic measures the number of packet resource assignments sent to the mobile.

This statistic counts the number of PACKET UPLINK ASSIGNMENT messages sent tothe MS. Re-transmissions are excluded.

Pegging

This statistic pegs each time a PACKET UPLINK ASSIGNMENT message is sent to themobile. Retransmissions are not pegged.


S A one phase Immediate Assignment (IA) is sent.

S An Enhanced One–Phase (EOP) access indication is received.

S A Packet Uplink Assignment (PUA) is initially sent to establish the TemporaryBlock Flow (TBF).

S A Packet Timeslot Reconfigure (PTR) is initially sent to establish an uplink TBFwhen a downlink TBF is in progress.

Analysis

The statistic can be used for the trend analysis of the number of successful uplink GPRScalls made by a particular CELL.


Usage Congestion, network planning.

Basis Cell.

Type Counter.

GSR6 CODING_SCHEME_CHANGE

14 Feb 2003


68P02901W56-L 12–15

CODING_SCHEME_CHANGE{3750}

Description

The CODING_SCHEME_CHANGE statistic is obtained by measuring the number ofcoding scheme upgrades (from lower to higher coding scheme) and coding downgrades(from higher to lower coding scheme) for uplink and downlink in a statisticalmeasurement period.

The bins are:

S Total number of coding scheme upgrades for uplink.

S Total number of coding scheme downgrades for uplink.

S Total number of coding scheme upgrades for downlink.

S Total number of coding scheme downgrades for downlink.

Pegging

The appropriate bin is incremented each time a change in coding scheme occurs.

Analysis

This statistic can be used for the trend analysis of the number of Coding Schemeupgrades and downgrades on the uplink and downlink which may signify that thecell is congested.


Usage Congestion, network planning.

Basis Cell.

Type Counter array.

GSR6CS12_ON_32K_CHAN

14 Feb 200312–16


68P02901W56-L

CS12_ON_32K_CHAN{3635}

Description

The CS12_ON_32K_CHAN statistic tracks the percentage of time in a statistics reportingperiod that 32 kilobits per second GPRS timeslots are used with CS–1 and CS–2 rates.

Pegging

This statistic measures the percentage of blocks for which CS–1 and CS–2 data wastransmitted on a timeslot capable of CS–3 or CS–4 rates.

Reference None.


Network planning.

Basis Cell.

Type Percentage.

GSR6 DL_BUSY_PDTCH

14 Feb 2003


68P02901W56-L 12–17

DL_BUSY_PDTCH{3750}

Description

This statistic measures the mean, max and min number of occupied Packet DataCHannels (PDCH) carrying downlink packet traffic.

This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, atevery packet-scheduling period (20 millisecond).

The bins are:

S No PDTCH is busy (time duration).

S 1-2 PDTCH are busy (time duration).









Pegging

This statistic pegs every packet-scheduling period (20 millisecond) by sampling thenumber of PDTCHs that are carrying downlink packet traffic.

Analysis

This statistic can be used for trend analysis of the number of PDTCHs that are used fordownlink packet traffic.


Usage Network planning, congestion.

Basis Cell


GSR6DL_PDTCH_CONGESTION

14 Feb 200312–18


68P02901W56-L

DL_PDTCH_CONGESTION{3750} {3969}

Description

The DL_PDTCH_CONGESTION statistic calculates all available Packet Data Channel(PDCH) allocated time for downlink. This statistic is obtained by measuring the totalnumber (in terms of block period – 20 millisecond) of times a cell is congested due to MSload on the available air resources on the downlink (that is, a 4 timeslot MS allocated in acell with 4 PDCHs).

Pegging

This statistic pegs every 20 millisecond when a Packet Data Traffic CHannel (PDTCH) isnot available on the downlink due to congestion.

Analysis

This statistic is totalled in terms of 20 millisecond block periods.



Basis Cell.

Type Counter.

GSR6 DL_PDTCH_Q_LENGTH

14 Feb 2003


68P02901W56-L 12–19

DL_PDTCH_Q_LENGTH{3750}{3969}

Description

{3969}This statistic is obtained by sampling the Downlink Request Queue. The statistic isupdated at every 8000 millisecond.

NOTE In the current Motorola PCU implementation, there is nodownlink queueing. Downlink requests are always successful.

Pegging

This statistic pegs each time a new message enters the downlink PDTCH queue or whena message waiting in the downlink PDTCH queue gets processed.

Analysis

This statistic can be used for the trend analysis of the average number of downlinkmessages waiting for a PDTCH to become available.


Usage {3969}Network planning, congestion.

Basis Cell.

Type Gauge.

GSR6DL_PDTCH_SEIZURE

14 Feb 200312–20


68P02901W56-L

DL_PDTCH_SEIZURE{3750}

Description

This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on thedownlink. The purpose of this statistic is to count the number of TBF(s) on the downlink.The statistic is obtained by measuring the receipt of the first RLC block (PDU) on thePDTCH from the network (downlink).

Pegging

This statistic pegs when the receipt of the first downlink RLC block (PDU) on the PDTCHfrom the network is obtained.

Analysis

This statistic can be used for the trend analysis of the total number of TBFs on thedownlink for a CELL.



Basis Cell.

Type Counter.

GSR6 GBL_DL_DATA_THRPUT

14 Feb 2003


68P02901W56-L 12–21

GBL_DL_DATA_THRPUT

Description

The GBL_DL_DATA_THRPUT statistic reports the quantity of data transmitted on thedownlink of the Gb link (GBL) during a given time interval. The PCU calculates theinstantaneous throughput in kilobytes per second by dividing the quantity of datatransmitted by the time interval given by the parameter gbl_thrput_period .

Pegging

This 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 .

Analysis

This statistic can be used for the trend analysis of the average downlink throughput of theGBL.

This statistic is stored in the following columns in the gbl_statistics table:

S dl_datathrput_mean.

S dl_datathrput_max.

Reference None.


Congestion.

Basis GBL.

Type Gauge.

GSR6GBL_DL_DATA_THRPUT_HIST

14 Feb 200312–22


68P02901W56-L

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 thequantity of data transmitted by the time interval given by the parametergbl_thrput_period .

There are 10 bins in the array. The available ranges are shown in Table 12-3.

Table 12-3 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

Pegging

The GBL_DL_DATA_THRPUT_HIST statistic pegs the instantaneous throughputsamples in 10 bins. See Table 12-3 for the ranges.

Analysis

This statistic can be used for the trend analysis of GBL downlink throughput.


S dl_thrput_min.

S dl_thrput_mean.

S dl_thrput_max.

Reference None.


Congestion.

Quality of service monitoring: Networkaccessibility.

Basis GBL.

Type Normal Distribution.

GSR6 GBL_FLOW_CTRL_SENT

14 Feb 2003


68P02901W56-L 12–23

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 apredetermined threshold, a flow control message is sent to the SGSN.

Flow control is performed to match the flow of downlink data with air throughput.

Pegging

This statistic pegs the number of flow control messages sent by the BSS and is peggedevery time a flow control message is sent.

Analysis

This statistic can be used for trend analysis of the number of flow control messages sentby the BSS.

Reference None.


Congestion.


Basis Cell.

Type Counter.

GSR6GBL_LINK_INS

14 Feb 200312–24


68P02901W56-L

GBL_LINK_INS

Description

The GBL_LINK_INS statistic tracks the amount of time in milliseconds that a specifiedGBL is in service.

Pegging

The timer for this statistic starts when the GBL transitions to the B-U state (that is,returns to service). The timer for this statistic stops when the GBL is no longer in theB-U state (that is, goes out of service).

Analysis

This statistic can be used for trend analysis of GBL usage.

Reference None.

Usage Network accessibility.

Fault finding.

Protocol utilization.

Basis GBL.

Type Duration.

GSR6 GBL_PAGING_REQS

14 Feb 2003


68P02901W56-L 12–25

GBL_PAGING_REQS

Description

The GBL_PAGING_REQS statistic tracks the number of paging requests received at theGBL.

Pegging

This statistic pegs each time an MS page request is received at the GBL.

Analysis

This statistic can be used for the trend analysis of the number of circuit switched andpacket switched pages received by the BSS from the SGSN.

Reference None.


Congestion.

Basis BSS.

Type Counter.

GSR6GBL_UL_DATA_THRPUT

14 Feb 200312–26


68P02901W56-L

GBL_UL_DATA_THRPUT

Description

The GBL_UL_DATA_THRPUT statistic reports the quantity of data transmitted on theuplink of the Gb link (GBL) during a given time interval. The PCU calculates theinstantaneous throughput in kilobytes per second by dividing the quantity of datatransmitted by the time interval given by the parameter gbl_thrput_period .

Pegging

This 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 .

Analysis

This statistic can be used for the trend analysis of the average uplink throughput of theGBL.


S ul_datathrput_mean.

S ul_datathrput_max.

Reference None.


Congestion.

Basis GBL.

Type Gauge.

GSR6 GBL_UL_DATA_THRPUT_HIST

14 Feb 2003


68P02901W56-L 12–27

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 thequantity of data transmitted by the time interval given by the parametergbl_thrput_period .

Pegging

The GBL_UL_DATA_THRPUT_HIST statistic pegs the instantaneous throughputsamples in 10 bins. The ranges are shown in Table 12-4.

There are 10 bins for this array.

Table 12-4 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

Analysis

This statistic can be used for the trend analysis of GBL uplink throughput.


S ul_thrput_min.

S ul_thrput_mean.

S ul_thrput_max.

Reference None.


Congestion.


Basis GBL.


GSR6GBL_UNAVAILABLE

14 Feb 200312–28


68P02901W56-L

GBL_UNAVAILABLE

Description

The GBL_UNAVAILABLE statistic tracks the amount of time in milliseconds that theGBL is out of service.

Pegging

The 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.

Analysis

This 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.

GSR6 GPRS_32K_CHANNELS_SWITCHED

14 Feb 2003


68P02901W56-L 12–29

GPRS_32K_CHANNELS_SWITCHED{3635}

Description

This statistic keeps a count of the number of times that 32 kilobits per second GPRStimeslots are used for circuit–switched calls in a statistics reporting period on a per–cellbasis.

Pegging

This statistic pegs when a 32kilobits per second GPRS timeslot is successfully switchedto a circuit switched call.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6GPRS_32K_DL_NOT_AVAIL

14 Feb 200312–30


68P02901W56-L

GPRS_32K_DL_NOT_AVAIL{3635}

Description

The GPRS_32K_DL_NOT_AVAIL statistic tracks the number of times that 32 kilobits persecond GPRS timeslots could not be allocated when needed for downlink codingschemes 3 and 4 transfers in a statistics reporting period on a per–cell basis.

Pegging

This statistic is pegged when a 32 kilobits per second GPRS air timeslot is needed tocomplete a downlink transfer and none is available. There is no specific messageinvolved in the pegging, the pegging is activated when a downlink request cannot beserviced.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6 GPRS_32K_UL_NOT_AVAIL

14 Feb 2003


68P02901W56-L 12–31

GPRS_32K_UL_NOT_AVAIL{3635}

Description

The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 32 kilobits persecond GPRS timeslots could not be allocated when needed for uplink coding schemes 3and 4 transfers in a statistics reporting period on a per–cell basis.

Pegging

This statistic is pegged when a 32 kilobits per second GPRS air timeslot is needed tocomplete an uplink transfer and none is available. There is no specific message involvedin the pegging, the pegging is activated when an uplink request cannot be serviced.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6GPRS_ACCESS_PER_AGCH

14 Feb 200312–32


68P02901W56-L

GPRS_ACCESS_PER_AGCH

Description

The GPRS_ACCESS_PER_AGCH statistic tracks the number of Immediate Assignmentmessages sent on the Access Grant Channel (AGCH) of a cell for packet data service.

The air interface message on the AGCH for packet immediate assignment andimmediate assignment reject contains only one MS.

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

Pegging

This statistic is pegged when an access grant message is sent on the AGCH on a cell forpacket data service.

Analysis

This statistic can be used for trend analysis of Immediate Assignment messages sent onthe AGCH of a cell.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6 GPRS_CELL_RESELECT_ATTMPT

14 Feb 2003


68P02901W56-L 12–33

GPRS_CELL_RESELECT_ATTMPT{3969}

Description

The GPRS_CELL_RESELECT_ATTMPT statistic tracks the number of NetworkControlled cell reselect attempts from the originating cell.

Pegging

This statistic pegs when the BSS initiates a cell change order procedure for an MS inpacket idle mode by sending an Immediate Assignment message with a downlink singleblock allocation in a CCCH block monitored by an MS.

Analysis

This statistic can be used for analysis of Network Controlled cell reselect attempts froman originating cell.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6GPRS_CELL_RESELECT_FAIL

14 Feb 200312–34


68P02901W56-L

GPRS_CELL_RESELECT_FAIL{3969}

Description

The GPRS_CELL_RESELECT_FAIL statistic tracks the number of Network Controlledcell reselect failures from the originating cell. Retries are not counted.

Pegging

This statistic pegs when a Packet Cell Change Failure message is sent by an MS.

Analysis

This statistic can be used for analysis of Network Controlled cell reselect failures from anoriginating cell.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6 GPRS_ACCESS_PER_RACH

14 Feb 2003


68P02901W56-L 12–35

GPRS_ACCESS_PER_RACH

Description

{3750} The GPRS_ACCESS_PER_RACH statistic tracks the number of packetswitched Channel Request messages successfully received on the Random AccessCHannel (RACH) for GPRS purposes.

Pegging

This statistic pegs when a packet switched Channel Request message is sent on theRandom Access CHannel (RACH) of a cell.

Analysis

This statistic can be used for trend analysis of Immediate Assignment messages sent onthe RACH of a cell.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6GPRS_CHANNELS_SWITCHED

14 Feb 200312–36


68P02901W56-L

GPRS_CHANNELS_SWITCHED

Description

This statistic reports the number of times a 16 kilobits per second Packet Data TrafficChannel (PDTCH) has been switched to a circuit switched Traffic Channel (TCH).

Pegging

This statistic pegs when a 16 kilobits per second PDTCH is switched to a circuit switchedTCH.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6 GPRS_DYNET_FAILURES

14 Feb 2003


68P02901W56-L 12–37

GPRS_DYNET_FAILURES

Description

The GPRS_DYNET_FAILURES statistic tracks the totals for four different sources ofterrestrial backing failure.

The sources of terrestrial backing failure are listed below.

S Terrestrial resource for a reserved GPRS timeslot is not provided when requested.

S Terrestrial backing is taken from switchable timeslots. This happens foremergency and non-emergency calls.

S Terrestrial backing is taken from reserved timeslots. This happens for emergencycalls and link failures only.

S When converting a switchable GPRS timeslot from packet to circuit mode andterrestrial backing is unavailable.


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

Pegging

This statistic is pegged only when both dynamic allocation and GPRS are unrestricted.This statistic is not pegged if either feature is restricted.

Analysis

This statistic can be used to analyse how effectively terrestrial backing resources areallocated for a particular site. Bin counts can be observed to determine the effects ofblocking, preemption, and unavailable terrestrial resources with GPRS.

Reference None.


Network accessibility.

Basis Dynet.

Type Counter array.

GSR6GPRS_DYNET_RES_REQS

14 Feb 200312–38


68P02901W56-L

GPRS_DYNET_RES_REQS

Description

The GPRS_DYNET_RES_REQS statistic tracks the time that the number of requests forbacking of reserved timeslots were in the queue. Each bin corresponds to a range ofqueue lengths.

There are 10 bins for this array. The ranges are shown in Table 12-5.

Table 12-5 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

Pegging

When this statistic is pegged, the bin corresponding to the length of the queue isincremented by one. The maximum and minimum queue length and the average queuelength is reported.

Reference None.


Basis Dynet.


GSR6 GPRS_DYNET_SWI_REQS

14 Feb 2003


68P02901W56-L 12–39

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.

There are 10 bins for this array. The ranges are shown in Table 12-6.

Table 12-6 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

Pegging

When this statistic is pegged, the bin corresponding to the length of the queue isincremented by one. The maximum and minimum queue length and the average queuelength are reported.

Reference None.


Basis Dynet.


GSR6GPRS_MS_NEIGHBOR_STRONG

14 Feb 200312–40


68P02901W56-L

GPRS_MS_NEIGHBOR_STRONG{3969}

Description

The GPRS_MS_NEIGHBOR_STRONG statistic tracks the number of GPRS MS(s) forwhich the rxlev of any neighbour cell is stronger by a certain threshold than the rxlev ofthe serving cell.

Pegging

This statistic pegs whenever a Packet Measurement Report is received from an MS.

Analysis

This statistic is obtained by measuring the number of GPRS MS/s for which the receivelevel (rxlev) of any neighbour cell is stronger than the rxlev of the serving cell by adefined threshold in the Packet Measurement Report message. The counter isincremented only once for an MS if the multiple Packet Measurement Report shows abetter rxlev than the serving cell.

Reference None.


Network planning.

Basis Cell.

Type Counter.

GSR6 GPRS_PCH_AGCH_Q_LENGTH

14 Feb 2003


68P02901W56-L 12–41

GPRS_PCH_AGCH_Q_LENGTH{3750}

Description

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 allmessages waiting for transmission on the PCH-AGCH, for GPRS purpose. Thismeasurement is obtained once in every paging multi frame, taking the PCH-AGCH queuelength and then taking the arithmetic mean.

Pegging

This statistic pegs once per paging multiframe, by summing the total number ofmessages in the paging queue. At the end of the interval, the mean number ofmessages are calculated and reported.

Analysis

The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCHqueue.


Usage This statistic is used to assess the impact ofGPRS messaging on the CCCH. For example,the operator could use the statistic to monitor thegrowth of GPRS in an area, and possibly replanpaging parameters to account for an increase inGPRS users on the network.

Basis Cell.

Type Gauge.

GSR6IDLE_PDTCH_INTF_BAND0

14 Feb 200312–42


68P02901W56-L

IDLE_PDTCH_INTF_BAND0{3750}

Description

The IDLE_PDTCH_INTF_BAND0 statistic tracks the maximum and mean number of idleuplink Packet Data Traffic CHannels (PDTCHs) for interference band 0. An idle PDTCHfalls into band 0 if its average interference band is less than the value of the elementinterfer_bands, 0.

NOTE Idle PDTCHs are allocated to five interference bands. Eachband has an associated statistic for tracking idle PDTCHs.

Pegging

This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it canbe allocated for a request. An idle PDTCH will fall into band 0 if its idle interference levelis less than the value of the elements interfer_bands 0. The mean and max arecalculated from the samples.

Analysis

This statistic can be used for trend analysis of idle packet data traffic channels.

Reference Digital cellular telecommunications systems(phase 2+) Version 7.0.0 Jan 2000 ETSI..


Fault finding.

Basis Cell.

Type Gauge.

GSR6 IDLE_PDTCH_INTF_BAND1

14 Feb 2003


68P02901W56-L 12–43


Description



Pegging


Analysis




Fault finding.

Basis Cell.

Type Gauge.


14 Feb 200312–44


68P02901W56-L


Description



Pegging


Analysis




Fault finding.

Basis Cell.

Type Gauge.

GSR6 IDLE_PDTCH_INTF_BAND3

14 Feb 2003


68P02901W56-L 12–45


Description



Pegging


Analysis




Fault finding.

Basis Cell.

Type Gauge.


14 Feb 200312–46


68P02901W56-L


Description



Pegging


Analysis




Fault finding.

Basis Cell.

Type Gauge.

GSR6 IMM_ASSGN_CAUSE

14 Feb 2003


68P02901W56-L 12–47

IMM_ASSGN_CAUSE{3750}

Description

This statistic measures the successful immediate assignment procedures, per cause.This statistic is obtained by measuring the number of IMMEDIATE ASSIGN COMMAND messages transmitted, per cause. This message contains either an IMMEDIATEASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message. If anIMMEDIATE ASSIGNMENT EXTENDED message is transmitted, the counter isincremented by two, because it contains assignment information for two MSs otherwisethe counter is incremented by one. The associated bins, identifiers and establishmentcauses are as follows:

Table 12-7 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.

Pegging

This statistic is pegged once for every time the BSS sends an Immediate Assignment(IA) for any of the specified purposes over the air. IAs for other purposes are notpegged.

This statistic pegs the cause of each IMMEDIATE ASSIGN COMMAND message. If thismessage contains an IMMEDIATE ASSIGNMENT message, the cause is pegged once.If this message contains an IMMEDIATE ASSIGNMENT EXTENDED message, thecause is pegged twice.

Analysis

It represents the total number of IAs pegged during the statistics interval, on a per-causebasis.


GSR6IMM_ASSGN_CAUSE

14 Feb 200312–48


68P02901W56-L

Usage The statistic is used for monitoring areas wherelots of calls originate: the operator may wish tocharge more for calls made in these high-trafficzones.

It is also used for monitoring the number of callsundergoing re-establishment. High numbers ofcalls undergoing re-establishment means the RFcoverage in an area may have a hole.

Comparing the uplink against downlink GPRSusage tells the operator how to set the Betavalue for a cell (Interleaving TBFs feature). Thisallows for better throughput based upon themobile subscriber preferences in any particulararea.

Basis Cell.

Type Counter array.

GSR6 MS_CLASS_1_10_REQ

14 Feb 2003


68P02901W56-L 12–49

MS_CLASS_1_10_REQ

Description

The MS_CLASS_1_10_REQ statistic tracks the number of requests received for the MSclasses 1 through 10.

Each bin corresponds to a particular MS class as shown in Table 12-8.

Table 12-8 MS_CLASS_1_10_REQ bins


0 MS_CLASS_1_REQ Number of requests for class 1










Pegging

This is one of three statistics that is pegged every time there is an uplink request from anMS. The other two are MS_CLASS_11_20_REQ and MS_CLASS_21_29_REQ.

Reference GSM 05.02, 6.2.0, Annex B.


Basis Cell.

Type Counter array.

GSR6MS_CLASS_11_20_REQ

14 Feb 200312–50


68P02901W56-L

MS_CLASS_11_20_REQ

Description

The MS_CLASS_11_20_REQ statistic tracks the number of requests received for theMS classes 11 through 20.














Pegging

This is one of three stats that is pegged every time there is an uplink request from anMS. The other two are MS_CLASS_1_10_REQ and MS_CLASS_21_29_REQ.



Basis Cell.

Type Counter array.

GSR6 MS_CLASS_21_29_REQ

14 Feb 2003


68P02901W56-L 12–51

MS_CLASS_21_29_REQ

Description

The MS_CLASS_21_29_REQ statistic tracks the number of requests received for theMS classes 21 through 29.













Pegging

This is one of three stats that is pegged every time there is an uplink request from anMS. The other two are MS_CLASS_1_10_REQ and MS_CLASS_11_20_REQ.



Basis Cell.

Type Counter array.

GSR6NO_PDTCH_AVAIL

14 Feb 200312–52


68P02901W56-L

NO_PDTCH_AVAIL{3725}

Description

The NO_PDTCH_AVAIL statistic counts the number of times neither switchable norreserved PDTCHs are available.

Pegging

When the last PDTCH available is taken for a voice call, the count is incremented.

Reference None.



Basis Cell.

Type Counter.

GSR6 NO_PDTCH_AVAIL_TIME

14 Feb 2003


68P02901W56-L 12–53

NO_PDTCH_AVAIL_TIME{3725}

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), whenneither switchable nor reserved PDTCHs are available.

Pegging

When the last PDTCH available is taken for a voice call, the timer is started and stoppedwhen at least one PDTCH becomes available.

Analysis

A threshold value should be assigned to this statistic which reflects the maximumacceptable time that no PDTCHs are available for any of the start/stop time periods. Ifthe specified threshold is exceeded, the Total time all PDTCHs are unavailable – PMalarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R(68P02901W26) for troubleshooting information.

Reference None.



Basis Cell.

Type Duration.

GSR6PRP_LOAD

14 Feb 200312–54


68P02901W56-L

PRP_LOAD {4253}

Description

This statistic measures the load of the Packet Resource Processor (PRP) board. TheBSS transfers data for 30 DL and 30 UL TBFs, and processes control messages for 90 UL and 90 DL TBFs in one 20 millisecond block period. The load of the PRP board isdetermined by measuring the number of timeslots pending service for data transferswithin a 20 millisecond block period.

Table 12-11 shows the mapping between the number of timeslots pending service andthe PRP load.

The statistic is kept on a per DPROC basis.

Table 12-11 Mapping between timeslots pending service and PRP load

Number of timeslots pendingservice in a 20 msec block period

PRP Load

0-30 0-100

31-60 101-200

61-90 201-300

91-120 301-400

Each bin of this statistic represents the following PRP load range.

Table 12-12 PRP load range

Bin Number 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

Pegging

This statistic pegs the appropriate bin every 20 millisecond based on the number oftimeslots pending service and the bin range values that the customer configured.

Analysis

This statistic can be used for trend analysis of the network load on a PRP board. Eachbin can be analysed to determine the number of occurrences the PRP had a certainpercentage of load on it.

GSR6 PRP_LOAD

14 Feb 2003


68P02901W56-L 12–55

Reference None.


Basis This statistic is based on each DPROC.


GSR6UL_BUSY_PDTCH

14 Feb 200312–56


68P02901W56-L

UL_BUSY_PDTCH{3750}

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).

The bins are:

Table 12-13 UL_BUSY_PDTCH bins

Bin Range

0 No PDTCH is busy

1 1-2 PDTCH are busy









Pegging

This statistic pegs every packet-scheduling period (20 millisecond) by sampling thenumber of PDTCHs that are carrying uplink packet traffic.

Analysis

This statistic can be used for trend analysis of the number of PDTCHs that are used foruplink packet traffic.



Basis Cell.


GSR6 UL_PDTCH_CONGESTION

14 Feb 2003


68P02901W56-L 12–57

UL_PDTCH_CONGESTION{3750} {3969}

Description

The UL_PDTCH_CONGESTION statistic measures all available Packet Data CHannel(PDCH) allocated time for uplink. This statistic is obtained by measuring the totalnumber (in terms of block period – 20 millisecond) of times a cell is congested due to MSload on the available air resources on the uplink (that is, a 4 timeslot MS allocated in acell with 4 PDCHs).

Pegging

This statistic pegs every 20 millisecond when a Packet Data Traffic CHannel (PDTCH) isnot available on the uplink due to congestion.

Analysis

This statistic is totalled in terms of 20 millisecond block periods.



Basis Cell.

Type Counter.

GSR6UL_PDTCH_Q_LENGTH

14 Feb 200312–58


68P02901W56-L

UL_PDTCH_Q_LENGTH{3750}

Description

{3969}This statistic is obtained by sampling the Uplink Request Queue. The statistic isupdated at every 8000 millisecond.

Pegging

This statistic pegs each time a new message enters the uplink PDTCH queue or when amessage waiting in the uplink PDTCH queue gets processed.

Analysis

This statistic can be used for the trend analysis of the average number of uplinkmessages waiting for a PDTCH to become available.

{3969}This statistic can be used for trend analysis of the number of queued uplinkPDTCH requests.


Usage {3969}Network planning, congestion.

Basis Cell.

Type Gauge.

GSR6 UL_PDTCH_SEIZURE

14 Feb 2003


68P02901W56-L 12–59

UL_PDTCH_SEIZURE{3750}{4386}

Description

This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on theuplink. The purpose of this statistic is to count the number of temporary block flows(TBF) on the uplink. The statistic is obtained by measuring the receipt of the first RLCblock (PDU) on the PDTCH from the MS (uplink).

Pegging

This statistic pegs when the receipt of the first uplink RLC block (PDU) on the PDTCHfrom the MS is obtained.


S The first uplink data block is received during a two–phase uplink TBFestablishment.

S A first uplink data block containing a valid Temporary Logical Link Identity (TLLI) isreceived during a one–phase uplink TBF establishment.

Analysis

This statistic can be used for the trend analysis of the total number of TBFs on thedownlink for a CELL.



Basis Cell.

Type Counter.

GSR6UL_PDTCH_SEIZURE

14 Feb 200312–60


68P02901W56-L

14 Feb 2003


68P02901W56-L 13–1

Chapter 13

BSS-SMLC statistics

GSR6

14 Feb 200313–2


68P02901W56-L

GSR6 Introduction to BSS-based SMLC statistics

14 Feb 2003


68P02901W56-L 13–3

Introduction to BSS-based SMLC statistics{3974}

Description

This chapter includes descriptions of the BSS-based SMLC statistics. BSS-basedServing Mobile Location Centre (SMLC) statistics are organized into two majorsubgroups:

S BSS C7 utilization.

S SCCP performance and utilization.

BSS C7 utilization

BSS-based SMLC C7 utilization statistics track the number of messages received andtransmitted on the signalling links. This information indicates the activity level on theSignalling Links (SLs). The following are BSS C7 utilization statistics:

S L_SIF_SIO_RX_OPC.

S L_SIF_SIO_TX_DPC.

S L_SIF_SIO_TYPE .

SCCP performance & utilization

SCCP performance and utilization statistics track the performance of the SignallingConnection Control Part (SCCP) protocol layer of the ITU–TSS C7.

The SCCP manages the establishment and release of call related connections. Aconnection is established for each transaction. For example, location update and servicerequest, both BSS and BSS-based SMLC maintain contexts related to the transaction;these contexts may be identified using the SCCP reference number. This informationindicates the performance level and quality of the SCCP. The following are the SCCPperformance and utilization statistics:

S PAGE_REQ_FROM_SMLC_FAIL.

S L_ROUTING_SYNTAX.

S L_ROUTING_UNKNOWN.

S L_SCCP_MSGS.

S L_SCCP_MSGS_RX.

S L_SCCP_MSGS_TX.

S L_SIF_SIO_RX_OPC.

S L_SIF_SIO_TX_DPC.

S L_SIF_SIO_TYPE .

GSR6PAGE_REQ_FROM_SMLC_FAIL

14 Feb 200313–4


68P02901W56-L

PAGE_REQ_FROM_SMLC_FAIL{3974}

Description

This statistic tracks the number of page request messages received from the BSS-basedSMLC that fail message validation at the BSS.

Pegging

This statistic pegs each time a page request message from the BSS-based SMLC failsmessage validation at the BSS.

Analysis

A threshold value should be assigned to this statistic which reflects the maximum numberof failures that are acceptable in normal system operations.

If the specified threshold is exceeded, the 20. BSS: Paging request from SMLCprotocol error – PM alarm is generated. Refer to the Maintenance Information: AlarmHandling at the OMC (68P02901W26) for troubleshooting information.

Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.


Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6 L_ROUTING_SYNTAX

14 Feb 2003


68P02901W56-L 13–5

L_ROUTING_SYNTAX{3974}

Description

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

Pegging

This statistic pegs when a syntax error is detected in an SCCP message on theLb-interface.

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andBSS-based SMLC. Excessive syntax errors can result in degraded SCCP performance.

A threshold value should be assigned to this statistic which reflects the maximum numberof SCCP messages with syntax errors that are acceptable in normal system operations.

If the specified threshold is exceeded, the 18. BSS: Routing failure - syntax errordetected (SMLC) – PM alarm is generated. Refer to the Maintenance Information:Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6L_ROUTING_UNKNOWN

14 Feb 200313–6


68P02901W56-L

L_ROUTING_UNKNOWN{3974}

Description

This statistic tracks the number of invalid signalling point codes (SPCs) that a BSC hasreceived from the BSS-based SMLC.

Pegging

This statistic pegs whenever an invalid SPC is received from the BSS-based SMLC.

Analysis

An SPC is the destination address for a message routed by the networking functions ofthe MTP3 protocol. If the BSC receives an incorrect SPC, it will not be able to correctlyroute the message.

A threshold value should be assigned to this statistic which reflects the maximum numberof invalid 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.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Fault finding.

Basis BSS.

Type Counter.

Alarm Warning.

GSR6 L_SCCP_MSGS

14 Feb 2003


68P02901W56-L 13–7

L_SCCP_MSGS{3974}

Description

This statistic tracks the total number of SCCP messages either transmitted or receivedbetween the BSC and BSS-based SMLC over an Lb-interface.

Pegging

This statistic pegs when SCCP messages are transmitted or received on the signallinglink between the BSC and BSS-based SMLC.

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andBSS-based SMLC. This statistic can be used for trend analysis of SCCP performanceand utilization.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6L_SCCP_MSGS_RX

14 Feb 200313–8


68P02901W56-L

L_SCCP_MSGS_RX{3974}

Description

This statistic tracks the total number of SCCP messages received by the BSC fromBSS-based SMLC over an Lb-interface for class 0 or class 2.

This statistic will switch on the appropriate device value so that the OMC can store it inthe relevant column of the database:

S the number of SCCP messages received for class 0 will be stored inl_sccp_msgs_rx_0.

S the number of SCCP messages received for class 2 will be stored inl_sccp_msgs_rx_2.

Pegging

This statistic pegs when SCCP messages are received on the signalling link between theBSC and BSS-based SMLC.

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andBSS-based SMLC. This statistic can be used for trend analysis of the activity on an SL.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6 L_SCCP_MSGS_TX

14 Feb 2003


68P02901W56-L 13–9

L_SCCP_MSGS_TX{3974}

Description

This statistic tracks the total number of SCCP messages transmitted by the BSC toBSS-based SMLC over the Lb-interface for class 0 or class 2.


S the number of SCCP messages transmitted for class 0 will be stored inl_sccp_msgs_tx_0.

S the number of SCCP messages transmitted for class 2 will be stored inl_sccp_msgs_tx_2.

Pegging

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

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andBSS-based SMLC. This statistic can be used for trend analysis of the activity over theLb-interface.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6L_SIF_SIO_RX_OPC

14 Feb 200313–10


68P02901W56-L

L_SIF_SIO_RX_OPC{3974}

Description

This statistic tracks the total number of SIF and SIOs received on all SLs for the BSSfrom BSS-based SMLC.

Pegging

This statistic pegs each time Signal Information Fields (SIF) or Service InformationOctets (SIO) are received across all signalling links between the BSS and BSS-basedSMLC.

Analysis

SCCP is an SS7 protocol used in transferring signalling messages between the BSC andBSS-based SMLC. This statistic can be used for trend analysis of the activity on allLb-interface SLs for a particular BSS.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6 L_SIF_SIO_TX_DPC

14 Feb 2003


68P02901W56-L 13–11

L_SIF_SIO_TX_DPC{3974}

Description

This statistic tracks the total number of Signal Information Fields (SIF) and ServiceInformation Octets (SIO) transmitted on all SLs of the BSS to the Lb-interfaceDestination Point Code (DPC).

Pegging

This statistic pegs each time SIF or SIO are transmitted across all signalling links fromthe BSS to the BSS-based SMLC (as indicated by the Lb-interface (DPC)).

Analysis

A 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 trendanalysis of the activity of the signalling links on a BSS.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

GSR6L_SIF_SIO_TYPE

14 Feb 200313–12


68P02901W56-L

L_SIF_SIO_TYPE{3974}

Description

This statistic tracks the number of SIF MTP, TEST, and SCCP SIOs transmitted orreceived on all Lb-interface SLs.


S the number of SIF SCCP SIOs will be stored in l_sif_sio_type.

S the number of SIF MTP SIOs will be stored in l_sif_sio_type_mtp.

S the number of SIF TEST SIOs will be stored in l_sif_sio_type_test.

Pegging

This statistic pegs each time SIF or SIOs are transmitted or received on all signallinglinks between BSS and BSS-based SMLC.

Analysis

This statistic can be used for trend analysis of the activity of the signalling links on a BSSover the Lb-interface.

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).


Basis BSS.

Type Counter.

14 Feb 2003


68P02901W56-L 14–1

Chapter 14

Web MMI statistics

GSR6

14 Feb 200314–2


68P02901W56-L

GSR6 MMI Statistics

14 Feb 2003


68P02901W56-L 14–3

MMI Statistics

Introduction

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 Chapter 12

CHANNEL_REQS_REJ Chapter 12

GBL_LINK_INS Chapter 12

GBL_PAGING_REQS Chapter 12

GBL_UNAVAILABLE Chapter 12

The following MMI BSC/BTS real-time statistics are documented elsewhere in thismanual. Table 14-2 indicates the location of these descriptions.

Table 14-2 Location of MMI BSC/BTS PCU real-time stats descriptions

MMI BSC/BTS statistic Location in manual

ALLOC_SDCCH_FAIL Chapter 4

ALLOC_TCH_FAIL Chapter 4

HO_FAIL_NO_RESOURCES Chapter 4

HO_REQ_MSC_FAIL Chapter 4

MA_CMD_TO_MS_BLKD Chapter 4

RF_LOSSES_TCH Chapter 6

GSR6MMI Statistics

14 Feb 200314–4


68P02901W56-L

14 Feb 2003


68P02901W56-L 15–1

Chapter 15

Call model statistics

GSR6

14 Feb 200315–2


68P02901W56-L

GSR6 Introduction to call model statistics

14 Feb 2003


68P02901W56-L 15–3

Introduction to call model statistics

Description

This chapter describes the derivation of call model parameter values from the GSMnetwork statistics collected at the OMC–R.

All the statistics used for determining the call model parameters must be collected duringbusy hours and averaged over a reasonable period of time (3 months or more).

The call model parameters should be averaged over the entire network or at the BSClevel for equipment dimensioning purposes. This gives more scope of averaging out theload from the network entities.

The following are call model statistics:

S CALL_DURATION (T).

S CALL_SETUP_BLOCKING_RATE.

S HANDOVERS_PER_CALL (H).

S IMSI_DETACHES_TO_CALLS (Id).

S INTRA_BSS_HO_TO_ALL_HO (i).

S LOCATION_UPDATE_FACTOR (L).

S LOCATION_UPDATES_TO_CALLS (l).

S PAGES_PER_CALL (Ppc).

S PAGES_PER_SECOND.

S PAGING_RATE (P).

S SMS_TO_CALL_RATIO (S).

Refer to the System Information: BSS Equipment Planning (68P02900W21) for furtherinformation on the call model parameters.

GSR6CALL_DURATION (T)

14 Feb 200315–4


68P02901W56-L

CALL_DURATION (T)

Description

This statistic provides the average call duration.

Formula

T +

�Ni+1

(BUSY_TCH_MEAN) * stat_interval_in_sec

�Ni+1

(TOTAL_CALLS ) ASSIGNMENT_REDIRECTION)

Where: N is: the number of cells.

stat_interval_in_sec the interval over whichBUSY_TCH_MEAN values aremeasured. It is 3600 if hourlyvalues are used and 86400 if dailyvalues are used.

The ASSIGNMENT_REDIRECTION statistic is only available from softwarerelease GSR5 onwards.

NOTE


Optimization.

Basis Cell.

Units Seconds

RawStatistics

BUSY_TCH_MEAN.

TOTAL_CALLS.

ASSIGNMENT_REDIRECTION .

GSR6 CALL_SETUP_BLOCKING_RATE

14 Feb 2003


68P02901W56-L 15–5

CALL_SETUP_BLOCKING_RATE

Description

This statistic provides the percentage of attempts to allocate a TCH call setup that wereblocked.

Formula

CALL_SETUP_BLOCKING_RATE +MA_CMD_TO_MS_BLKD * 100

MA_REQ_FROM_MSC


Optimization.

Basis Cell.

Units Percentage.

RawStatistics

MA_CMD_TO_MS_BLKD.

MA_REQ_FROM_MSC.

GSR6HANDOVERS_PER_CALL (H)

14 Feb 200315–6


68P02901W56-L

HANDOVERS_PER_CALL (H)

Description

This statistic provides the number of Handovers per call where the handovers may beinter-BSS, intra-BSS or intra-cell.

Formula

H +

�Ni+1

(OUT_INTER_BSS_REQ_TO_MSC ) OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)

�Ni+1



The TOTAL_CALLS parameter is the count of the total circuit-switched calls ina cell. It should be summed for all the cells in the BSC, when used in theprevious formula.

NOTE


Optimization.

Basis Cell.

RawStatistics

OUT_INTER_BSS_REQ_TO_MSC.

OUT_INTRA_BSS_HO_ATMPT.

INTRA_CELL_HO_ATMPT.

TOTAL_CALLS.


GSR6 IMSI_DETACHES_TO_CALL (Id)

14 Feb 2003


68P02901W56-L 15–7

IMSI_DETACHES_TO_CALL (Id)

Description

This statistic provides the ratio of IMSI detaches per call.

Formula

Id +

�Ni+1

OK_ACC_PROC[IMSI_DETACH]

�Ni+1




Optimization.

Basis Cell.

RawStatistics

OK_ACC_PROC [IMSI_DETACH].

TOTAL_CALLS.


GSR6INTRA_BSS_HO_TO_ALL_HO (i)

14 Feb 200315–8


68P02901W56-L

INTRA_BSS_HO_TO_ALL_HO (i)

Description

This statistic provides the ratio of intra–BSS handovers to all handovers.

Formula

i +

�Ni+1

(OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)

�Ni+1

OUT_INTER_BSS_REQ_TO_MAC ) OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)



Optimization.

Basis Cell.

RawStatistics

OUT_INTRA_BSS_HO_ATMPT.

INTRA_CELL_HO_ATMPT.

OUT_INTER_BSS_REQ_TO_MAC.

TOTAL_CALLS.


GSR6 LOCATION_UPDATE_FACTOR (L)

14 Feb 2003


68P02901W56-L 15–9

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 afterreceiving the IMSI detach. When using IMSI detach type 1, the MSC clears the SCCPconnection, a clearing procedure that involves only one uplink (average size of 42 bytes)and one downlink message (average size of 30 bytes). When using IMSI detach type 2,the MSC sends the CLEAR COMMAND and the BSS sends CLEAR COMPLETE, etc.,which involves three uplink (average size of 26 bytes) and three downlink messages(average size of 30 bytes). A location update procedure itself takes five downlinkmessages (average size of 30 bytes) and six uplink messages (average size of 26bytes).

Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number ofmessages as a location update and a IMSI detach (type 2) takes 6/11 (approximately0.5) of the messages of a location update.

Formula

If IMSI detach is enabled, then depending on whether short message sequence (type 1)or long message sequence (type 2) is used, L is calculated as:

S L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled i.e. Id=0 )

S L = LOCATION_UPDATES_TO_CALLS + 0.2* IMSI_DETACHES_TO_CALLS(type 1)

S L = LOCATION_UPDATES_TO_CALLS + 0.5* IMSI_DETACHES_TO_CALLS(type 2)


Optimization.

Basis Cell.

Call ModelStatistics

LOCATION_UPDATES_TO_CALLS.

IMSI_DETACHES_TO_CALLS.

GSR6LOCATION_UPDATES_TO_CALLS (I)

14 Feb 200315–10


68P02901W56-L

LOCATION_UPDATES_TO_CALLS (I)

Description

This statistic provides the ratio of location updates to calls.

Formula

I +

�Ni+1

OK_ACC_PROC[LOCATION UPDATE]

�Ni+1




Optimization.

Basis Cell.

RawStatistics

OK_ACC_PROC [LOCATION UPDATE].

TOTAL_CALLS.


GSR6 PAGES_PER_CALL (PPC)

14 Feb 2003


68P02901W56-L 15–11

PAGES_PER_CALL (PPC)

Description

This statistic provides the number of pages per call.

Formula

Ppc +

�Ni+1

PAGE_REQ_FROM_MSC

�Ni+1


Where: N is: the number of cells under the BSC.


Optimization.

Basis Cell.

CallModel/RawStatistics

PAGE_REQ_FROM_MSC.

TOTAL_CALLS.


PAGING_RATE.

CALL_DURATION.

GSR6PAGES_PER_SECOND

14 Feb 200315–12


68P02901W56-L

PAGES_PER_SECOND

Description

This statistic provides the number of pages per second.

Formula

PAGES_PER_SECOND +PAGE_REQ_FROM_MSCINTERVAL_SUM * 3600


Optimization.

Basis Cell.

Raw Statistics PAGE_REQ_FROM_MSC.

INTERVAL_SUM.

GSR6 PAGING_RATE (P)

14 Feb 2003


68P02901W56-L 15–13

PAGING_RATE (P)

Description

The paging rate is the summation of the paging messages sent to each location areaaveraged over the interval period.

Formula

P +

�Ni+1

(PAGE_REQ_FROM_MSC)

stat_interval_in_seconds [ith location area in BSC]

Where: N is: the number of location areas.

PAGE_REQ_FROM_MSC should be the maximum per cell value for eachlocation area.

NOTE


Optimization.

Basis Cell.

RawStatistics

PAGE_REQ_FROM_MSC.

GSR6SMS_TO_CALL_RATIO (S)

14 Feb 200315–14


68P02901W56-L

SMS_TO_CALL_RATIO (S)

Description

This statistic provides the ratio of SMSs to calls.

Formula

S +(SMS_INIT_ON_SDCCH) SMS_INIT_ON_TCH)

((CM_SERV_REQ_CALL)CM_SERV_REQ_SMS)CM_SERV_REQ_EMERG) PAGE_RESPONSE)* (SMS_INIT_ON_SDCCH))


Optimization.

Basis Cell.

RawStatistics

SMS_INIT_ON_SDCCH.

SMS_INIT_ON_TCH.

CM_SERV_REQ_CALL.

CM_SERV_REQ_SMS.

CM_SERV_REQ_EMERG.

PAGE_RESPONSE.

14 Feb 2003


68P02901W56-L 16–1

Chapter 16

Key statistics

GSR6

14 Feb 200316–2


68P02901W56-L

GSR6 Key statistics

14 Feb 2003


68P02901W56-L 16–3

Key statistics

DescriptionKey statistics are a set of calculated values providing an operator with a summary ofsystem performance during a specific statistics collection interval. They are designed togive an overall indication of the condition of the system and allow comparison of similartime periods to detect performance changes and trends.

Key statistics are also provided to facilitate the monitoring of the most important networkparameters. Key statistics are calculated at the OMC-R using various BSS rawstatistics. Different statistics are combined at the OMC-R using a predefined formula toproduce a new statistic. For example, various handover failure statistics may becombined and averaged over the total number of calls to produce a handover failure ratekey statistic.

Key statistics may be displayed in the Performance Management window of theOMC-R.

The key statistics are divided into the following groups:

S Call summary.

S Channel usage.

S Connection establishment.

S RF loss summary.

S MTL utilisation.

Call summaryCall summary statistics are used to determine assignment and handover performance ofone or more cells. The following are call summary statistics:

S CALL_SETUP_SUCCESS_RATE.

S HANDOVER_FAILURE_RATE.

S HANDOVER_SUCCESS_RATE.

S SUCCESS_INTERNAL_HO.

S TOTAL_CALLS_KEY.

S UNSUCCESS_INTERNAL_HO_NOREEST.

S UNSUCCESS_INTERNAL_HO_REEST.

Channel usageChannel usage statistics are used to determine SDCCH and TCH performance levels.The following are channel usage statistics:

S MEAN_TCH_BUSY_TIME.

S SDCCH_BLOCKING_RATE.

S SDCCH_MEAN_ARRIVAL_RATE.

S SDCCH_MEAN_HOLDING_TIME.

S SDCCH_TRAFFIC_CARRIED.

S TCH_BLOCKING_RATE.

S TCH_MEAN_ARRIVAL_RATE.

S TCH_MEAN_HOLDING_TIME .

S TCH_TRAFFIC_CARRIED.

GSR6Key statistics

14 Feb 200316–4


68P02901W56-L


Connection statistics are used to determine the number and interval of attempted andsuccessful assignment requests. The following are connection establishment statistics:

S ATTEMPT_IMMED_ASSIGN_PROC .

S MEAN_ARRIVAL_TIME_BETWEEN_CALLS .

S MEAN_INTER_ARRIVAL_TIME.

S SUCCESS_IMMED_ASSIGN_PROC.

RF loss summary

RF loss summary statistics are used to determine TCH assignments within a cell and therate of RF lost calls. The following are RF loss summary statistics:

S CELL_TCH_ALLOCATIONS.

S CELL_TCH_ASSIGNMENTS .

S RF_LOSS_RATE.

S SDCCH_RF_LOSS_RATE.

S TCH_RF_LOSS_RATE.

MTL utilisation

MTL utilisation statistics are used to provide a measure of MTL utilisation from the MSCto BSS and from the BSS to MSC. The following are MTL utilisation statistics:

S MTL_UTILISATION_RX.

S MTL_UTILISATION_TX.

GSR6 Key statistics

14 Feb 2003


68P02901W56-L 16–5

Template

Table 16-1 is a template used in the key statistic descriptions:

Table 16-1 Key statistic descriptions.

Description: A general description of what the statisticmeasures.

Formula: Arithmetic calculation of key statistic from rawstatistics.

Reference: References to other sections of this documentor other documents.

Usage: Lists the network operation related uses of thestatistic.

Basis: The level at which the statistic is pegged, forexample, cell, BSS.

Type: The statistic type (counter, percentage, etc.).

Raw Statistic: The raw statistics associated with this keystatistic. The convention used for presenting aspecific bin of a counter array statistic isstatistic name[bin name]. For example,OK_ACC_PROC[CM_REESTABLISH] is theCM_REESTABLISH bin of theOK_ACC_PROC counter array statistic.

Note: Used to qualify or stress information.

NOTE The template headings are used as required and are not presentfor all statistics.

GSR6ATTEMPT_IMMED_ASSIGN_PROC

14 Feb 200316–6


68P02901W56-L

ATTEMPT_IMMED_ASSIGN_PROC

Description

The ATTEMPT_IMMED_ASSIGN_PROC statistic tracks the number of attemptedimmediate assignment procedures.

Formula

ATTEMPT_IMMED_ASSIGN_PROC = (OK_ACC_PROC_RACH −INV_EST_CAUSE_ON_RACH)



Optimization.

Basis Cell or BSS.

Type Counter.

RawStatistics

OK_ACC_PROC_RACH.

INV_EST_CAUSE_ON_RACH.

GSR6 CALL_SETUP_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 16–7

CALL_SETUP_SUCCESS_RATE

Description

The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attemptsthat result in a successful TCH access. Network accesses which do not require a TCHare excluded; for example, location updates, SMS, and Supplementary Service attempts.

Formula

CALL_SETUP_SUCCESS_RATE=(TOTAL CALLS + ASSIGNMENT_REDIRECTION )

* 100%(OK_ACC_PROC[CM_SERV_REQ_CALL] +OK_ACC_PROC[CM_REESTABLISH] +OK_ACC_PROC[PAGE_RESPONSE] +OK_PROC[CM_SERV_REQ_SMS] +

OK_ACC_PROC[CM_SERV_REQ_EMERG] +OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL] +

OK_ACC_PROC[LOC_FLW_ON_REQ_SMS] −SMS_INIT_ON_SDCCH−MT_LCS_ON_SDCCH)


Fault finding.

Service accessibility.

Basis Cell.

Type Percentage.

RawStatistics


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.

TOTAL_CALLS.

GSR6CELL_TCH_ALLOCATIONS

14 Feb 200316–8


68P02901W56-L

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

CELL_TCH_ALLOCATIONS = SUM(ALLOC_TCH)


Basis Cell.

Type Counter.

RawStatistics

ALLOC_TCH.

GSR6 CELL_TCH_ASSIGNMENTS

14 Feb 2003


68P02901W56-L 16–9

CELL_TCH_ASSIGNMENTS

Description

The CELL_TCH_ASSIGNMENTS statistic is the sum of the total number of calls, thetotal number of successful incoming inter-BSS call handovers, and the total number ofincoming intra-BSS call handovers.

Formula

CELL_TCH_ASSIGNMENTS =TOTAL_CALLS +

IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]


Basis Cell.

Type Counter.

RawStatistics

TOTAL_CALLS.

IN_INTER_BSS_HO.[IN_INTER_BSS_HO_SUC].

IN_INTRA_BSS_HO.[IN_INTRA_BSS_HO_SUC].

GSR6HANDOVER_FAILURE_RATE

14 Feb 200316–10


68P02901W56-L

HANDOVER_FAILURE_RATE

Description

The HANDOVER_FAILURE_RATE statistic tracks the percentage of handovers thatwere attempted from the source cell (the cell for which the statistic is presented) thatfailed to successfully reach the target cell and failed to successfully recover to the sourcecell, that is, the handover failed and the call dropped. A handover attempt is countedwhen a handover command is sent to the MS.

Congestion on the target cell does not result in the BSS sending a handover command tothe mobile therefore this measurement is not impacted by target cell congestion.

Formula

HANDOVER_FAILURE_RATE =

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT])

* 100%

(INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] + (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] – OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])


Optimization.

Fault finding.


Network planning.

Basis Cell.

Type Percentage.

RawStatistics

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] .

GSR6 HANDOVER_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 16–11

HANDOVER_SUCCESS_RATE

Description

The HANDOVER_SUCCESS_RATE statistic tracks the percentage of handovers thatwere attempted from the source cell (cell for which the statistic is presented) thatsuccessfully reached the target cell. A handover attempt is counted when a handovercommand is sent to the MS. This key statistic includes inter-BSS Handovers.

Congestion on the target cell does not result in the BSS sending a handover command tothe mobile therefore this measurement is not impacted by target cell congestion.

Formula

HANDOVER_SUCCESS_RATE =

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] + INTRA_CELL_HO[INTRA_CELL_HO_SUC] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT])

* 100%

HANDOVER_SUCCESS_RATE + HANDOVER_FAILURE_RATE � 100%because the calls that fail and recover to the source cell are not included ineither of these key statistics.

NOTE


Optimization.

Fault finding.


Network planning.

Basis Cell.

Type Percentage.

RawStatistics


INTRA_CELL_HO[INTRA_CELL_HO_SUC] .

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ ATMPT].


OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ ATMPT].

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] .

GSR6MEAN_ARRIVAL_TIME_BETWEEN_CALLS

14 Feb 200316–12


68P02901W56-L

MEAN_ARRIVAL_TIME_BETWEEN_CALLS

Description

The MEAN_ARRIVAL_TIME_BETWEEN_CALLS statistic tracks the amount of timebetween consecutive normal and emergency call attempts originated from an MS.

Formula

MEAN_ARRIVAL_TIME_BETWEEN_CALLS

* 3600SUM (INTERVAL)

(CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL] +CHAN_REQ_CAUSE_ATMPT[EMERGENCY_CALL])

=


Fault finding.


Optimization.

Basis Cell.

Type Duration (in seconds).

RawStatistics

INTERVAL

CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL].

CHAN_REQ_HO_CAUSE_ATMPT[EMERGENCY_CALL] .

GSR6 MEAN_INTER_ARRIVAL_TIME

14 Feb 2003


68P02901W56-L 16–13

MEAN_INTER_ARRIVAL_TIME

Description

The MEAN_INTER_ARRIVAL_TIME statistic is the arithmetic mean of the sum of thetime intervals between consecutive normal, SMS, supplementary and emergencyrequests for service.

Formula

BSS Level

MEAN_INTER_ARRIVAL_TIME = * 3600SUM (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])



Optimization.

Basis BSS.


RawStatistics

INTERVAL



OK_ACC_PROC[CM_SERV_REQ_SUPP].


GSR6MEAN_TCH_BUSY_TIME

14 Feb 200316–14


68P02901W56-L

MEAN_TCH_BUSY_TIME

Description

The MEAN_TCH_BUSY_TIME statistic tracks the arithmetic mean of the busy time fortraffic channels in a cell.

Formula

MEAN_TCH_BUSY_TIME = * INTERVAL * 3600 (BUSY_TCH_MEAN)

(AVAILABLE_TCH_MEAN)

Usage Optimization.

Network planning.

Basis Cell.


RawStatistics

AVAILABLE_TCH.

BUSY_TCH.

GSR6 MTL_UTILISATION_RX

14 Feb 2003


68P02901W56-L 16–15

MTL_UTILISATION_RX

Description

The MTL_UTILISATION_RX statistic provides a measure of MTL utilisation for the MSCto BSS direction.

Formula

MTL_UTILISATION_RX = * 100((MTP_MSU_RX * 6) + MTP_SIF_SIO_RX) + (SIB_RX * 7)

(MTP_LINK_INS * 8)

NOTE: As an explanation as to how the formula was derived, refer to the following whichshows no number simplification:

MTL_UTILISATION_RX = * 100((MTP_MSU_RX * 6bytes/msu) + MTP_SIF_SIO_RX) + (SIB_RX * 7bytes/sib)

(MTP_LINK_INS * 1sec/1000msec) * (64000bits per sec/8 bits)

Usage Optimization.

Network planning.

Basis MTL.

Type Percentage.

RawStatistics

MTP_MSU_RX.

MTP_SIF_SIO_RX.

SIB_RX.

MTP_LINK_INS.

GSR6MTL_UTILISATION_TX

14 Feb 200316–16


68P02901W56-L

MTL_UTILISATION_TX

Description

The MTL_UTILISATION_TX statistic provides a measure of MTL utilisation for the BSSto MSC direction.

Formula

MTL_UTILISATION_TX = * 100((MTP_MSU_TX * 6) + MTP_SIF_SIO_TX) + (SIB_TX * 7)

(MTP_LINK_INS * 8)

NOTE: As an explanation as to how the formula was derived, refer to the following whichshows no number simplification:

MTL_UTILISATION_TX = * 100((MTP_MSU_TX * 6bytes/msu) + MTP_SIF_SIO_TX) + (SIB_TX * 7bytes/sib)

(MTP_LINK_INS * 1sec/1000msec) * (64000bits per sec/8 bits)

Usage Optimization.

Network planning.

Basis MTL.

Type Percentage.

RawStatistics

MTP_MSU_TX.

MTP_SIF_SIO_TX .

SIB_TX.

MTP_LINK_INS.

GSR6 RF_LOSS_RATE

14 Feb 2003


68P02901W56-L 16–17

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 callshanded in to the cell. It indicates the cell/system ability to preserve calls.

Formula

* 100%RF_LOSS_RATE =

[RF_LOSSES_SD + ( RF_LOSSES_TCH [1] + .... + RF_LOSSES_TCH [nTCH] )]

OK_ACC_PROC[CM_SERV_REQ_CALL +OK_ACC_PROC[CM_SERV_REQ_SMS] +OK_ACC_PROC[CM_SERV_REQ_SUPP] +OK_ACC_PROC[CM_SERV_REQ_EMERG]+ OK_ACC_PROC[CM_REESTABLISH] +OK_ACC_PROC[LOCATION_UPDATE] +

OK_ACC_PROC[IMSI_DETACH] + OK_ACC_PROC[PAGE_RESPONSE]

(IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]+

IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])+

Handovers may relate to SDCCHs (as opposed to TCHs). In this case, theaccuracy of the statistic is affected. For the most part this effect is expectedto be negligible. nTCH = Number of TCHs in cell.

NOTE


Fault finding and optimization.


Basis Cell.

Type Percentage.

RawStatistics

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 of bins0 to 7 of this counter array statistic.)

RF_LOSSES_TCH.

RF_LOSSES_SD.

GSR6SDCCH_BLOCKING_RATE

14 Feb 200316–18


68P02901W56-L

SDCCH_BLOCKING_RATE

Description

The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocatean SDCCH that were blocked due to no available SDCCH resources. This statisticincludes incoming SDCCH handover attempts.

Formula

SDCCH_BLOCKING_RATE = * 100%(ALLOC_SDCCH_FAIL)

(ALLOC_SDCCH + ALLOC_SDCCH_FAIL)

Usage Service Accessibility.

Quality of Service monitoring.

Network planning.

Basis Cell.

Type Percentage.

RawStatistics

ALLOC_SDCCH.

ALLOC_SDCCH_FAIL.

GSR6 SDCCH_MEAN_ARRIVAL_RATE

14 Feb 2003


68P02901W56-L 16–19

SDCCH_MEAN_ARRIVAL_RATE

Description

The SDCCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate for theSDCCHs in the cell measured in calls per interval.

Formula

SDCCH_MEAN_ARRIVAL_TIME =SUM (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]

+OK_ACC_PRO[CM_REESTABLISH] + OK_ACC_PROC[LOCATION_UPDATE] + OK_ACC_PROC[IMSI_DETACH] + OK_ACC_PROC[PAGE_RESPONSE]


Basis Cell.

Type Counter (calls per interval).

RawStatistics

INTERVAL ( statistics collection interval,measured in hours).

OK_ACC_PROC. (The value used in thisformula is the sum of the bins 0 to 7 of thiscounter array statistic).

GSR6SDCCH_MEAN_HOLDING_TIME

14 Feb 200316–20


68P02901W56-L

SDCCH_MEAN_HOLDING_TIME

Description

The SDCCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls onSDCCH channels in seconds.

Formula

SDCCH_MEAN_HOLDING_TIME =

(BUSY_SDCCH_MEAN * INTERVAL_SUM * 3600)

ALLOC_SDCCH


Optimization.

Basis Cell.

Type Total Time (in seconds).

RawStatistics

ALLOC_SDCCH.

BUSY_SDCCH.

INTERVAL_SUM (total statistics collectioninterval, measured in hours).


GSR6 SDCCH_RF_LOSS_RATE

14 Feb 2003


68P02901W56-L 16–21

SDCCH_RF_LOSS_RATE

Description

The SDCCH_RF_LOSS_RATE statistic compares the total number of RF losses (whileusing an SDCCH), as a percentage of the total number of call attempts for SDCCHchannels. T his statistic is intended to give an indication of how good the cell/system is atpreserving calls.

Formula

SDCCH_RF_LOSS_RATE =

RF_LOSSES_SD* 100

(ALLOC_SDCCH � CHAN_REQ_MS_FAIL)


Fault finding.


Basis Cell.

Type Percentage.

RawStatistics

ALLOC_SDCCH.

CHAN_REQ_MS_FAIL.

RF_LOSSES_SD.

GSR6SDCCH_TRAFFIC_CARRIED

14 Feb 200316–22


68P02901W56-L

SDCCH_TRAFFIC_CARRIED

Description

The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHsmeasured in Erlangs.

Formula

SDCCH_TRAFFIC_CARRIED = BUSY_SDCCH_MEAN

For an individual cell over m statistics intervals:

SDCCH_TRAFFIC_CARRIED = S BUSY_SDCCH_MEAN [k]m

k = 1

m

For n cells over an individual statistics interval:

SDCCH_TRAFFIC_CARRIED = S BUSY_SDCCH_MEAN [k]n

k = 1

For n cells over m statistics intervals:

SDCCH_TRAFFIC_CARRIED =S BUSY_SDCCH_MEAN

[k]

m

k = 1

m

n

k = 1

S

The BUSY_SDCCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.

Where BUSY_SDCCH_MEAN [k] is BUSY_SDCCH_MEAN for statisticalinterval k.

NOTE

Usage RF Loss.

Congestion.

Network planning.

Optimization.

Basis BSS.

Type Counter.

Raw Statistic BUSY_SDCCH.

GSR6 SUCCESS_IMMED_ASSIGN_PROC

14 Feb 2003


68P02901W56-L 16–23

SUCCESS_IMMED_ASSIGN_PROC

Description

The SUCCESS_IMMED_ASSIGN_PROC statistic tracks the number of successfulimmediate assignment procedures.

Formula

SUCCESS_IMMED_ASSIGN_PROC = (OK_ACC_PROC_RACH − INV_EST_CAUSE_ON_RACH− CHAN_REQ_MS_BLK)



Optimization.

Basis Cell or BSS.

Type Counter.

RawStatistics

CHAN_REQ_MS_BLK.

INV_EST_CAUSE_ON_RACH.

OK_ACC_PROC_RACH.

GSR6SUCCESS_INTERNAL_HO

14 Feb 200316–24


68P02901W56-L

SUCCESS_INTERNAL_HO

Description

The SUCCESS_INTERNAL_HO statistic tracks the number of successful internalhandovers.

Formula

SUCCESS_INTERNAL_HO = (INTRA_CELL_HO[INTRA_CELL_HO_SUC] +OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])


Optimization.

Quality of service.

Basis Cell.

Type Counter.

RawStatistics



GSR6 TCH_BLOCKING_RATE

14 Feb 2003


68P02901W56-L 16–25

TCH_BLOCKING_RATE

Description

The TCH_BLOCKING_RATE statistic provides the percentage of all requests for TCHresources (originations and hand ins) which fail due to no available TCH resources.

Formula

TCH_BLOCKING_RATE = * 100%(ALLOC_TCH_FAIL − TCH_Q_REMOVED)

(ALLOC_TCH + ALLOC_TCH_FAIL − TCH_Q_REMOVED)


Network planning.

Fault finding.

Basis Cell.

Type Percentage.

RawStatistics

ALLOC_TCH.

ALLOC_TCH_FAIL.

TCH_Q_REMOVED.

GSR6TCH_MEAN_ARRIVAL_RATE

14 Feb 200316–26


68P02901W56-L

TCH_MEAN_ARRIVAL_RATE

Description

The TCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate in callsper interval for the cell in question.

Formula

(ALLOC_TCH + ALLOC_TCH_FAIL − TCH_Q_REMOVED)

SUM(INTERVAL)TCH_MEAN_ARRIVAL_RATE =

The arrival rate of calls includes both calls set up on traffic channels within acell and handovers into the cell.

NOTE


Basis Cell.

Type Counter (calls/interval).

RawStatistics

ALLOC_TCH.

ALLOC_TCH_FAIL.

TCH_Q_REMOVED.

GSR6 TCH_MEAN_HOLDING_TIME

14 Feb 2003


68P02901W56-L 16–27

TCH_MEAN_HOLDING_TIME

Description

The TCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls on trafficchannels (TCH) in seconds.

Formula

(BUSY_TCH_MEAN * INTERVAL_SUM * 3600)

ALLOC_TCH

TCH_MEAN_HOLDING_TIME =

The numerator and denominator may peg on different intervals (where a callextends across multiple collection boundaries). This affects the accuracy ofthe statistic for the period. Therefore, this statistic should be used as a trendrather than focusing on specific values.

NOTE


Basis Cell.

Type Total Time in seconds.

RawStatistics

ALLOC_TCH.

BUSY_TCH_MEAN.

GSR6TCH_RF_LOSS_RATE

14 Feb 200316–28


68P02901W56-L

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

TCH_RF_LOSS_RATE =

Cell Level

BSS Level

Network Level

RF_LOSSES_TCH

(TOTAL_CALLS + IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]IN_INTER_BSS[IN_INTER_BSS_HO_SUC])

TCH_RF_LOSS_RATE = RF_LOSSES_TCH

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION +IN_INTER_BSS[IN_INTER_BSS_HO_SUC])


TOTAL_CALLS + ASSIGNMENT_REDIRECTION

* 100%

* 100%

* 100%


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics


IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]

IN_INTER_BSS[IN_INTER_BSS_HO_SUC].

RF_LOSSES_TCH.

TOTAL_CALLS.

GSR6 TCH_TRAFFIC_CARRIED

14 Feb 2003


68P02901W56-L 16–29

TCH_TRAFFIC_CARRIED

Description

The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHsmeasured in Erlangs.

Formula

For an individual cell for an individual statistics interval:

TCH_TRAFFIC_CARRIED = BUSY_TCH_MEAN


TCH_TRAFFIC_CARRIED = S BUSY_TCH_MEAN [k]m

k = 1

m


TCH_TRAFFIC_CARRIED = S BUSY_TCH_MEAN [k]n

k = 1


TCH_TRAFFIC_CARRIED =S BUSY_TCH_MEAN [k]m

k = 1

m

n

k = 1

S

The BUSY_TCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.

Where BUSY_TCH_MEAN [k] is BUSY_TCH_MEAN for statistical interval k.

NOTE

GSR6TCH_TRAFFIC_CARRIED

14 Feb 200316–30


68P02901W56-L

Usage Congestion.

Quality of service.

Network planning.

Optimization.

Basis Cell.

Type Units = Erlangs.

RawStatistics

BUSY_TCH (BUSY_TCH_MEAN).

GSR6 TOTAL_CALLS_KEY

14 Feb 2003


68P02901W56-L 16–31

TOTAL_CALLS_KEY

Description

The TOTAL_CALLS_KEY statistic tracks the number of calls for one or more cellsduring the interval.

Formula

TOTAL_CALLS_KEY = ( TOTAL_CALLS )


Fault finding.

Basis Cell.

Type Counter.

RawStatistics

TOTAL_CALLS.

GSR6UNSUCCESS_INTERNAL_HO_NOREEST

14 Feb 200316–32


68P02901W56-L

UNSUCCESS_INTERNAL_HO_NOREEST

Description

The UNSUCCESS_INTERNAL_HO_NOREEST statistic tracks the number ofunsuccessful internal handovers that result in dropping the call.

Formula

UNSUCCESS_INTERNAL_HO_NOREEST = INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS]


Quality of service.

Fault finding.

Basis Cell or BSS.

Type Counter

RawStatistics



GSR6 UNSUCCESS_INTERNAL_HO_REEST

14 Feb 2003


68P02901W56-L 16–33

UNSUCCESS_INTERNAL_HO_REEST

Description

The UNSUCCESS_INTERNAL_HO_REEST statistic tracks the number of unsuccessfulinternal handovers with successful recovery to the originating cell or channel.

Formula

SUCCESS_INTERNAL_HO_REEST = (INTRA_CELL_HO[INTRA_CELL_HO_RETURN] +OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN])


Fault finding.

Quality of service.

Basis Cell or BSS.

Type Counter.

RawStatistics

INTRA_CELL_HO[INTRA_CELL_HO_RETURN] .

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] .

GSR6UNSUCCESS_INTERNAL_HO_REEST

14 Feb 200316–34


68P02901W56-L

14 Feb 2003


68P02901W56-L 17–1

Chapter 17

Network health reports

GSR6

14 Feb 200317–2


68P02901W56-L

GSR6 Network health statistics

14 Feb 2003


68P02901W56-L 17–3

Network health statistics

Description

Network health statistics quantify BSS performance from a subscriber perspective. Acombination of raw and other network health statistics are used by the OMC-R tocalculate these statistics.

Network health statistics are available for display with the Cell device statistics in theOMC-R Performance Management window.

The network health statistics are organized as a suite of reports, including:

S GPRS performance.

S Handover performance.

S Health check.

S Paging performance.

S Radio performance.

S SDCCH congestion.

S TCH congestion.

GSR6Network health statistics

14 Feb 200317–4


68P02901W56-L

GPRS performance

The following statistics provide key performance metrics for the GPRS system:

S AIR_INTERFACE_BW_CS1




S CELL_UPDATE

S CS1_USAGE_DL

S CS1_USAGE_UL

S CS2_USAGE_DL

S CS2_USAGE_UL

S CS3_USAGE_DL

S CS3_USAGE_UL

S CS4_USAGE_DL

S CS4_USAGE_UL

S DL_AIR_INTERFACE_BW_CS1




S DOWNLINK_TRAFFIC_VOLUME

S GBL_AVAILABILITY

S GPRS_BW_USAGE_DL

S GPRS_BW_USAGE_UL

S GPRS_DL_ACT_TS

S GPRS_DL_BANDWIDTH_EFFICIENCY

S GPRS_UL_ACT_TS

S GPRS_UL_BANDWIDTH_EFFICIENCY

S PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK

S UL_AIR_INTERFACE_BW_CS1




S UPLINK_PDTCH_BLOCKING_RATE

S UPLINK_TRAFFIC_VOLUME

GSR6 Network health statistics

14 Feb 2003


68P02901W56-L 17–5

Handover performanceThe following statistics provide general handover information:

S HO_PER_CALL.

S INCOMING_HO_VOLUME .

S INTERNAL_LOST.

S INTERNAL_RECOVERED.

S INTERNAL_SUCCESS.

S INTRA_CELL_HO_FAIL_LOST_MS.

S INTRA_CELL_HO_FAIL_RECOVERED.

S INTRA_CELL_HO_SUCCESS_RATE.

S MEAN_TIME_BETWEEN_HOs.

S OUT_INTER_BSS_HO_FAIL_LOST_MS.

S OUT_INTER_BSS_HO_FAIL_RECOVERED.

S OUT_INTER_BSS_HO_SUCCESS_RATE.

S OUT_INTER_CELL_HO_FAIL_LOST_MS.

S OUT_INTER_CELL_HO_FAIL_RECOVERED.

S OUT_INTER_CELL_HO_SUCCESS_RATE.

S OUTGOING_HO_VOLUME .

Health checkThe following statistics provide health check information:

S CALL_SETUP_SUCCESS_RATE.

S CALL_SUCCESS_RATE.

S CALL_VOLUME.

S DROP_CALL_RATE.

S RANKING_FORMULA.


S TCH_TRAFFIC_CARRIED

Paging performanceThe following statistics provide paging performance information:

S AIR_INTERFACE_PAGING.

S MSC_PAGING.

S PAGING_COMPRESSION_RATE.

S PAGING_OVERFLOW_RATE.

S PAGING_RESPONSE.

S PAGING_SUCCESS_RATE.

GSR6Network health statistics

14 Feb 200317–6


68P02901W56-L

Radio performance

The following statistics provide radio performance information:

S ASSIGNMENT_SUCCESS_RATE.

S OUT_INTER_CELL_HO_FAIL_LOST_MS.

S OUT_INTER_CELL_HO_FAIL_RECOVERED.

S OUT_INTER_CELL_HO_SUCCESS_RATE.

S RF_ASSIGN_FAIL_RATE_LOST_MS.

S RF_ASSIGN_FAIL_RATE_RECOVERED.

S TCH_RF_LOSS_RATE.

SDCCH congestion

The following statistics provide SDCCH congestion information:

S SDCCH_ACCESSES.


S SDCCH_CONGESTION_TIME .

S SDCCH_TRAFFIC_CARRIED.

TCH congestion

The following statistics provide TCH congestion information:

S MAX_TCH_BUSY.

S TCH_ACCESSES

S TCH_CONGESTION_TIME .

S TCH_TRAFFIC_CARRIED.

GSR6 AIR_INTERFACE_BW_CS1

14 Feb 2003


68P02901W56-L 17–7

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

AIR_INTERFACE_BW_CS1 = AVAILABLE_PDTCH * 9.05



Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.

GSR6AIR_INTERFACE_BW_CS2

14 Feb 200317–8


68P02901W56-L


Description


Formula




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.

GSR6 AIR_INTERFACE_BW_CS3

14 Feb 2003


68P02901W56-L 17–9


Description


Formula




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.

GSR6AIR_INTERFACE_BW_CS4

14 Feb 200317–10


68P02901W56-L


Description


Formula




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.

GSR6 AIR_INTERFACE_PAGING

14 Feb 2003


68P02901W56-L 17–11

AIR_INTERFACE_PAGING

Description

The AIR_INTERFACE_PAGING statistic tracks the total number of paging requestsmessages sent on the air interface.

Formula

AIR_INTERFACE_PAGING = ACCESS_PER_PCH



Basis Cell.

Type Counter.

RawStatistics

ACCESS_PER_PCH.

GSR6ASSIGNMENT_SUCCESS_RATE

14 Feb 200317–12


68P02901W56-L

ASSIGNMENT_SUCCESS_RATE

Description

The ASSIGNMENT_SUCCESS_RATE statistic measures the success rate of theA–interface assignment procedure which will also automatically include the impact of theair interface assignment procedure.

Formula

ASSIGNMENT_SUCCESS_RATE=MA_REQ_FROM_MSC

* 100%MA_COMPLETE_TO_MSC



Quality of service.

Basis Cell.

Type Percentage.

RawStatistics

MA_COMPLETE_TO_MSC.

MA_REQ_FROM_MSC

GSR6 CALL_SETUP_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 17–13

CALL_SETUP_SUCCESS_RATE

Description

The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attemptsthat result in a successful TCH access. Network accesses which do not require a TCHare excluded; for example, location updates, SMS, and Supplementary Service attempts.

Formula

CALL_SETUP_SUCCESS_RATE=(TOTAL CALLS + ASSIGNMENT_REDIRECTION )

* 100%(OK_ACC_PROC[CM_SERV_REQ_CALL] +OK_ACC_PROC[CM_REESTABLISH] +OK_ACC_PROC[PAGE_RESPONSE] +OK_PROC[CM_SERV_REQ_SMS] +

OK_ACC_PROC[CM_SERV_REQ_EMERG] +OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL] +

OK_ACC_PROC[LOC_FLW_ON_REQ_SMS] −SMS_INIT_ON_SDCCH−MT_LCS_ON_SDCCH)


Fault finding.


Basis Cell.

Type Percentage.

RawStatistics


MT_LCS_ON_SDCCH





OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL]

OK_ACC_PROC[LOC_FLW_ON_REQ_SMS]


SMS_INIT_ON_SDCCH.

TOTAL_CALLS.

GSR6CALL_SUCCESS_RATE

14 Feb 200317–14


68P02901W56-L

CALL_SUCCESS_RATE

Description

This statistic represents the portion of MS call transactions with normal completions atthe radio subsystem, providing an overall indication of network performance from asubscriber perspective.

A combination of the CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATEnetwork health statistics is used to calculate this statistic. The raw statistics used tocalculate these health statistics are included in the raw statistics listing.

Formula

CALL_SUCCESS_RATE = 1 –CALL_SETUP_SUCCESS_RATE *DROP_CALL_RATE

100




Fault finding.

Basis Cell.

Type Percentage.

RawStatistics










OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].


OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED] .


RF_LOSSES_TCH.

SMS_INIT_ON_SDCCH.

TOTAL_CALLS.

GSR6 CALL_VOLUME

14 Feb 2003


68P02901W56-L 17–15

CALL_VOLUME

Description

The CALL_VOLUME statistic tracks the number of call setups which result in asuccessful TCH access.

Formula

CALL_VOLUME = TOTAL_CALLS + ASSIGNMENT_REDIRECTION




Basis Cell.

Type Counter.

RawStatistics


TOTAL_CALLS.

GSR6CELL_UPDATE

14 Feb 200317–16


68P02901W56-L

CELL_UPDATE

Description

The CELL_UPDATE statistic measures the number of cell reselections relating to aparticular cell.

Formula

CELL_UPDATE = CELL_FLUSH_REQS



Basis Cell.

Type Counter.

RawStatistics

CELL_FLUSH_REQS.

GSR6 CS1_USAGE_DL

14 Feb 2003


68P02901W56-L 17–17

CS1_USAGE_DL

Description

The CS1_USAGE_DL statistic provides the percentage of Radio Link Control blockstransmitted by the PCU (downlink) using GPRS coding scheme 1.

Formula

CS1_USAGE_DL =

(AIR_DL_DATA_BLKS)

* 100%

(AIR_DL_DATA_BLKS[QOS1_CS1] + AIR_DL_DATA_BLKS[QOS2_CS1] +AIR_DL_DATA_BLKS[QOS3_CS1])




Basis Cell.

Type Percentage.

RawStatistics

AIR_DL_DATA_BLKS[QOS1_CS1].



AIR_DL_DATA_BLKS all bins.

GSR6CS1_USAGE_UL

14 Feb 200317–18


68P02901W56-L

CS1_USAGE_UL

Description

The CS1_USAGE_UL statistic provides the percentage of Radio Link Control blocksreceived by the PCU (uplink) using GPRS coding scheme 1.

Formula

CS1_USAGE_UL =

(AIR_UL_DATA_BLKS)

* 100%

(AIR_UL_DATA_BLKS[QOS1_CS1] + AIR_UL_DATA_BLKS[QOS2_CS1] +AIR_UL_DATA_BLKS[QOS3_CS1])




Basis Cell.

Type Percentage.

RawStatistics

AIR_UL_DATA_BLKS[QOS1_CS1].



AIR_UL_DATA_BLKS all bins.

GSR6 CS2_USAGE_DL

14 Feb 2003


68P02901W56-L 17–19

CS2_USAGE_DL

Description


Formula

CS2_USAGE_DL =

(AIR_DL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6CS2_USAGE_UL

14 Feb 200317–20


68P02901W56-L

CS2_USAGE_UL

Description


Formula

CS2_USAGE_UL =

(AIR_UL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6 CS3_USAGE_DL

14 Feb 2003


68P02901W56-L 17–21

CS3_USAGE_DL

Description


Formula

CS3_USAGE_DL =

(AIR_DL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6CS3_USAGE_UL

14 Feb 200317–22


68P02901W56-L

CS3_USAGE_UL

Description


Formula

CS3_USAGE_UL =

(AIR_UL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6 CS4_USAGE_DL

14 Feb 2003


68P02901W56-L 17–23

CS4_USAGE_DL

Description


Formula

CS4_USAGE_DL =

(AIR_DL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6CS4_USAGE_UL

14 Feb 200317–24


68P02901W56-L

CS4_USAGE_UL

Description


Formula

CS4_USAGE_UL =

(AIR_UL_DATA_BLKS)

* 100%





Basis Cell.

Type Percentage.

RawStatistics





GSR6 DL_AIR_INTERFACE_BW_CS1

14 Feb 2003


68P02901W56-L 17–25

DL_AIR_INTERFACE_BW_CS1

Description

The DL_AIR_INTERFACE_BW_CS1 statistic provides a reference value in kilobits persecond for the configured downlink bandwidth in a cell in terms of coding scheme 1 for astatistics collection period.

Formula

For GSR6 the formula is:

DL_AIR_INTERFACE_BW_CS1 =

(50 * 3600) * INTERVAL

((AVAILABLE_PDTCH * 90000) * 9.05)

For GSR5.1 the formula is:


(50 * 3600) * INTERVAL

(TOTAL_AIR_DL_AVAILABLE_BW * 9.05)



Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.

INTERVAL is either 0.5 for a 30 minute collectionperiod or 1 for a 60 minute collection period.

TOTAL_AIR_DL_AVAILABLE_BW (GSR5.1).

GSR6DL_AIR_INTERFACE_BW_CS2

14 Feb 200317–26


68P02901W56-L


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.



GSR6 DL_AIR_INTERFACE_BW_CS3

14 Feb 2003


68P02901W56-L 17–27


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.


TOTAL_AIR_DL_AVAILABLE_BW (GSR5.1)

GSR6DL_AIR_INTERFACE_BW_CS4

14 Feb 200317–28


68P02901W56-L


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.



GSR6 DOWNLINK_TRAFFIC_VOLUME

14 Feb 2003


68P02901W56-L 17–29

DOWNLINK_TRAFFIC_VOLUME

Description

The DOWNLINK_TRAFFIC_VOLUME statistic provides a measure of the volume ofdownlink Radio Link Control traffic including retransmitted blocks.

Formula

DOWNLINK_TRAFFIC_VOLUME=

(1024 * 3600 * INTERVAL)

* 100%(AIR_DL_DATA_BLKS[QOS1_CS1] + AIR_DL_DATA_BLKS[QOS2_CS1] +

AIR_DL_DATA_BLKS[QOS3_CS1]) * 22) +(AIR_DL_DATA_BLKS[QOS1_CS2] + AIR_DL_DATA_BLKS[QOS2_CS2] +



AIR_DL_DATA_BLKS[QOS3_CS4]) * 52)




Basis Cell.

Type Percentage.

RawStatistics














GSR6DROP_CALL_RATE

14 Feb 200317–30


68P02901W56-L

DROP_CALL_RATE

Description

The DROP_CALL_RATE statistic tracks the percentage of MSs which, havingsuccessfully accessed a TCH, subsequently experience an abnormal release caused byeither radio or equipment problems. This includes RF losses and losses duringhandovers.

Formulas

DROP_CALL_RATE =

Cell Level

BSS Level

Network Level

(RF_LOSSES_TCH +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]) * 100

DROP_CALL_RATE =(TOTAL_CALLS + ASSIGNMENT_REDIRECTION +

IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC])

(RF_LOSSES_TCH +INTRA_CELL[INTRA_CELL_HO_LOSTMS] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED])

* 100

DROP_CALL_RATE =

(RF_LOSSES_TCH +INTRA_CELL[INTRA_CELL_HO_LOSTMS] +

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED])

* 100

(TOTAL_CALLS + IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)



Basis Cell, BSS, or network.

Type Percentage.

RawStatistics

ASSIGNMENT_REDIRECTION.




OUT_INTER_BSS_HO[OUT_INTRA_BSS_HO_CLEARED] .


RF_LOSSES_TCH.

TOTAL_CALLS.

GSR6 GBL_AVAILABILITY

14 Feb 2003


68P02901W56-L 17–31

GBL_AVAILABILITY

Description

The GBL_AVAILABILITY statistic measures the availability for a particular Gb link(GBL).

Formula

GBL_AVAILABILITY =

(3600000 * INTERVAL)

GBL_LINK_INS



Basis GBL.

Type Counter.

RawStatistics

GBL_LINK_INS.


GSR6GPRS_BW_USAGE_DL

14 Feb 200317–32


68P02901W56-L

GPRS_BW_USAGE_DL

Description

The GPRS_BW_USAGE_DL statistic measures the bandwidth usage in the downlinkdirection and provides an indication of the adequacy of the deployed cell capacity.

Formula

GPRS_BW_USAGE_DL =

(AVAILABLE_PDTCH_MEAN * 50 * 3600* INTERVAL)

((AIR_DL_DATA_BLKS * 100) * 100)



Basis Cell.

Type Percentage.

RawStatistics

AIR_DL_DATA_BLKS.

AVAILABLE_PDTCH.


GSR6 GPRS_BW_USAGE_UL

14 Feb 2003


68P02901W56-L 17–33

GPRS_BW_USAGE_UL

Description

The GPRS_BW_USAGE_UL statistic measures the bandwidth usage in the uplinkdirection and provides an indication of the adequacy of the deployed cell capacity.

Formula

GPRS_BW_USAGE_UL =

(AVAILABLE_PDTCH_MEAN * 50 * 3600* INTERVAL)

((AIR_UL_DATA_BLKS * 100) * 100)



Basis Cell.

Type Percentage.

RawStatistics

AIR_UL_DATA_BLKS.

AVAILABLE_PDTCH.


GSR6GPRS_DL_ACT_TS

14 Feb 200317–34


68P02901W56-L

GPRS_DL_ACT_TS

Description

The GPRS_DL_ACT_TS statistic measures the utilization of busy downlink PDTCHs in acell.

Formula

GPRS_DL_ACT_TS = DL_BUSY_PDTCH_MEAN



Basis Cell.

Type Counter.

RawStatistics

DL_BUSY_PDTCH.

GSR6 GPRS_UL_ACT_TS

14 Feb 2003


68P02901W56-L 17–35

GPRS_UL_ACT_TS

Description

The GPRS_UL_ACT_TS statistic measures the utilization of busy uplink PDTCHs in acell.

Formula

GPRS_UL_ACT_TS = UL_BUSY_PDTCH_MEAN



Basis Cell.

Type Counter.

RawStatistics

UL_BUSY_PDTCH.

GSR6GPRS_DL_BANDWIDTH_EFFICIENCY

14 Feb 200317–36


68P02901W56-L

GPRS_DL_BANDWIDTH_EFFICIENCY

Description

The GPRS_DL_BANDWIDTH_EFFICIENCY statistic measures the utilization of theGPRS bandwidth allocated in the downlink direction in the cells controlled by the PCU.

Formula


GPRS_DL_BANDWIDTH_EFFICIENCY =

(AVAILABLE_PDTCH * 90000)



GPRS_DL_BANDWIDTH_EFFICIENCY =

(TOTAL_AIR_DL_AVAILABLE_BW)




Basis Cell.

Type Percentage.

RawStatistics

AIR_DL_DATA_BLKS.

AVAILABLE_PDTCH.


GSR6 GPRS_UL_BANDWIDTH_EFFICIENCY

14 Feb 2003


68P02901W56-L 17–37

GPRS_UL_BANDWIDTH_EFFICIENCY

Description

The GPRS_UL_BANDWIDTH_EFFICIENCY statistic measures the utilization of theGPRS bandwidth allocated in the uplink direction in the cells controlled by the PCU.

Formula


GPRS_UL_BANDWIDTH_EFFICIENCY =

(AVAILABLE_PDTCH * 90000)



GPRS_UL_BANDWIDTH_EFFICIENCY =

(TOTAL_AIR_UL_AVAILABLE_BW)




Basis Cell.

Type Percentage.

RawStatistics

AIR_UL_DATA_BLKS.

AVAILABLE_PDTCH.

TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1)

GSR6HO_PER_CALL

14 Feb 200317–38


68P02901W56-L

HO_PER_CALL

Description

The HO_PER_CALL statistic tracks the average number of successful handovers percall.

Formula

HO_PER_CALL =

Cell Level

BSS Level

Network Level

(OUT_INTER_BSS_HO_SUC +OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC) * 100%

HO_PER_CALL =(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

* 100%

HO_PER_CALL =

(OUT_INTER_BSS_HO_SUC +OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC)

* 100%

TOTAL_CALLS

(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

(OUT_INTER_BSS_HO_SUC +OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC)


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





TOTAL_CALLS.

GSR6 INCOMING_HO_VOLUME

14 Feb 2003


68P02901W56-L 17–39

INCOMING_HO_VOLUME

Description

The INCOMING_HO_VOLUME statistic provides the number of successful incominghandovers.

Formulas

INCOMING_HO_VOLUME =Cell Level

BSS LevelINCOMING_HO_VOLUME = IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]

(IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])


Fault finding.

Basis Cell or BSS.

Type Counter.

RawStatistics



GSR6INTERNAL_LOST

14 Feb 200317–40


68P02901W56-L

INTERNAL_LOST

Description

The INTERNAL_LOST statistic tracks the percentage of BSS internal handovercommands that are sent over the air interface which result in the MS failing to access thetarget and failing to recover to the original channel; that is, the call drops. This statisticincludes intra-BSS and intra-cell handovers.

Formula

INTERNAL_LOST =

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +INTRA_CELL_HO[INTRA_CELL_HO_ATMPT])

* 100%

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS])


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





GSR6 INTERNAL_RECOVERED

14 Feb 2003


68P02901W56-L 17–41

INTERNAL_RECOVERED

Description

The INTERNAL_RECOVERED statistic tracks the percentage of BSS internal handovercommands that are sent over the air interface which result in the MS failing to access thetarget channel and successfully recovering to the original channel. This statistic includesintra-BSS and intra-cell handovers.

Formula

INTERNAL_RECOVERED =

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT])

* 100%

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] + INTRA_CELL_HO[INTRA_CELL_HO_RETURN])


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





GSR6INTERNAL_SUCCESS

14 Feb 200317–42


68P02901W56-L

INTERNAL_SUCCESS

Description

The INTERNAL_SUCCESS statistic tracks the percentage of BSS internal handovercommands that are sent over the air interface which result in the MS successfullyaccessing the target channel. This statistic includes intra-BSS and intra-cell handovers.

Formula

INTERNAL_SUCCESS =

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT])

* 100%

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] +INTRA_CELL_HO[INTRA_CELL_HO_SUC])


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





GSR6 INTRA_CELL_HO_FAIL_LOST_MS

14 Feb 2003


68P02901W56-L 17–43

INTRA_CELL_HO_FAIL_LOST_MS

Description

The INTRA_CELL_HO_FAIL_LOST_MS statistic tracks the percentage of intra-cellassignment 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.

Formula

INTRA_CELL_HO_FAIL_LOST_MS = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

* 100%INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS]


Fault finding.


Type Percentage.

RawStatistics

INTRA_CELL_HO[INTRA_CELL_HO_ ATMPT]


GSR6INTRA_CELL_HO_FAIL_RECOVERED

14 Feb 200317–44


68P02901W56-L

INTRA_CELL_HO_FAIL_RECOVERED

Description

The INTRA_CELL_HO_FAIL_RECOVERED statistic tracks the percentage of intra-cellassignment commands that are sent over the air interface which result in the MS failingto access the target channel and subsequently successfully recovering to the originalchannel.

Formula

INTRA_CELL_HO_FAIL_RECOVERED = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

* 100%INTRA_CELL_HO[INTRA_CELL_HO_RETURN]


Fault finding.


Type Percentage.

RawStatistics



GSR6 INTRA_CELL_HO_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 17–45

INTRA_CELL_HO_SUCCESS_RATE

Description

The INTRA_CELL_HO_SUCCESS_RATE statistic tracks the percentage of intra-cellassignment commands that are sent over the air interface which result in the MSsuccessfully accessing the target channel.

Formula

INTRA_CELL_HO_SUCCESS_RATE = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

* 100%INTRA_CELL_HO[INTRA_CELL_HO_SUC]


Fault finding.


Type Percentage.

RawStatistics



GSR6MAX_TCH_BUSY

14 Feb 200317–46


68P02901W56-L

MAX_TCH_BUSY

Description

The MAX_TCH_BUSY statistic tracks the maximum number of simultaneously busyTCHs.

Formula

MAX_TCH_BUSY = BUSY_TCH[MAX]

Usage Congestion.

Quality of service.

Network planning.

Optimization.

Basis Cell.

Type Counter.

RawStatistics

BUSY_TCH[MAX].

GSR6 MEAN_TIME_BETWEEN_HOs

14 Feb 2003


68P02901W56-L 17–47

MEAN_TIME_BETWEEN_HOs

Description

The MEAN_TIME_BETWEEN_HOs statistic tracks the mean time interval between intercell handovers.

Formula

MEAN_TIME_BETWEEN_HOs=

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] +OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC]) * 1000

TCH_USAGE


Fault finding.

Basis Cell.

Type Time interval (in seconds).

RawStatistics



TCH_USAGE.

GSR6MSC_PAGING

14 Feb 200317–48


68P02901W56-L

MSC_PAGING

Description

The MSC_PAGING statistic tracks the total number of BSSMAP paging messagesreceived over the A-interface from the MSC.

Formula

MSC_PAGING = PAGE_REQ_FROM_MSC



Basis Cell.

Type Counter.

RawStatistics

PAGE_REQ_FROM_MSC.

GSR6 OUT_INTER_BSS_HO_FAIL_LOST_MS

14 Feb 2003


68P02901W56-L 17–49

OUT_INTER_BSS_HO_FAIL_LOST_MS

Description

The OUT_INTER_BSS_HO_FAIL_LOST_MS statistic tracks the percentage ofinter-BSS handover commands that are sent over the air interface which result in the MSfailing to access the target channel and failing to recover to the original channel; that is,the call drops.

Formula

OUT_INTER_BSS_HO_FAIL_LOST_MS =

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]* 100%

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] –

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])


Fault finding.

Basis BSS.

Type Percentage.

RawStatistics




GSR6OUT_INTER_BSS_HO_FAIL_RECOVERED

14 Feb 200317–50


68P02901W56-L

OUT_INTER_BSS_HO_FAIL_RECOVERED

Description

The OUT_INTER_BSS_HO_FAIL_RECOVERED statistic tracks the percentage ofinter-BSS 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 theoriginal channel.

Formula

OUT_INTER_BSS_HO_FAIL_RECOVERED = OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]

* 100%

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN]


Fault finding.

Basis BSS.

Type Percentage.

RawStatistics



GSR6 OUT_INTER_BSS_HO_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 17–51

OUT_INTER_BSS_HO_SUCCESS_RATE

Description

The OUT_INTER_BSS_HO_SUCCESS_RATE statistic tracks the percentage ofinter-BSS handover commands that are sent over the air interface which result in the MSsuccessfully accessing the target channel.

Formula

OUT_INTER_BSS_HO_SUCCESS_RATE = OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]

* 100%OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]


Fault finding.

Basis BSS.

Type Percentage.

RawStatistics



GSR6OUT_INTER_CELL_HO_FAIL_LOST_MS

14 Feb 200317–52


68P02901W56-L

OUT_INTER_CELL_HO_FAIL_LOST_MS

Description

The OUT_INTER_CELL_HO_FAIL_LOST_MS statistic tracks the percentage ofinter-cell handover commands that are sent over the air interface which result in the MSfailing to access the target channel and failing to recover to the original channel; that is,the call drops. This statistic does not include intra-cell handovers.

Formula

OUT_INTER_CELL_HO_FAIL_LOST_MS =

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS]+ OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –

OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] –OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])

* 100%(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT])


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics






GSR6 OUT_INTER_CELL_HO_FAIL_RECOVERED

14 Feb 2003


68P02901W56-L 17–53

OUT_INTER_CELL_HO_FAIL_RECOVERED

Description

The OUT_INTER_CELL_HO_FAIL_RECOVERED statistic tracks the percentage ofinter-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 theoriginal channel. This statistic does not include intra-cell handovers.

Formula

OUT_INTER_CELL_HO_FAIL_RECOVERED=

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +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_RETURN])

* 100%


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





GSR6OUT_INTER_CELL_HO_SUCCESS_RATE

14 Feb 200317–54


68P02901W56-L

OUT_INTER_CELL_HO_SUCCESS_RATE

Description

The OUT_INTER_CELL_HO_SUCCESS_RATE statistic tracks the percentage ofinter-cell handover commands that result in in the MS successfully accessing the targetchannel. This statistic includes intra-BSS and inter-BSS inter-cell handovers.

Formula

OUT_INTER_CELL_HO_SUCCESS_RATE =

(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +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_SUC])

* 100%


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics





GSR6 OUTGOING_HO_VOLUME

14 Feb 2003


68P02901W56-L 17–55

OUTGOING_HO_VOLUME

Description

The OUTGOING_HO_VOLUME statistic tracks the number of successful outgoinghandovers.

Formula

OUTGOING_HO_VOLUME =

Cell Level

BSS Level

OUTGOING_HO_VOLUME = OUT_INTER_BSS_HO_SUC

(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] +OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])


Fault finding.

Basis Cell or BSS.

Type Counter.

RawStatistics



GSR6PAGING_COMPRESSION_RATE

14 Feb 200317–56


68P02901W56-L

PAGING_COMPRESSION_RATE

Description

The PAGING_COMPRESSION_RATE statistic provides a measure of page packing onthe air interface.

Formula

PAGING_COMPRESSION_RATE =PAGE_REQ_FROM_MSC

ACCESS_PER_PCH* 100%


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics

ACCESS_PER_PCH

PAGE_REQ_FROM_MSC.

GSR6 PAGING_OVERFLOW_RATE

14 Feb 2003


68P02901W56-L 17–57

PAGING_OVERFLOW_RATE

Description

The PAGING_OVERFLOW_RATE statistic tracks the percentage of pages which aredropped from the BSS paging queue due to paging queue overflow.

Formula

PAGING_OVERFLOW_RATE =PAGE_REQ_FROM_MSC

PCH_PAGE_Q_DISCARD* 100%


Fault finding.


Type Percentage.

RawStatistics

PAGE_REQ_FROM_MSC.

PCH_PAGE_Q_DISCARD.

GSR6PAGING_RESPONSE

14 Feb 200317–58


68P02901W56-L

PAGING_RESPONSE

Description

The PAGING_RESPONSE statistic tracks the volume of MSs which respond to a pagethrough a successful SDCCH access.

Formula

PAGING_RESPONSE = OK_ACC_PROC[PAGE_RESPONSE]


Fault finding.


Type Counter.

Raw Statistic OK_ACC_PROC[PAGE_RESPONSE]

GSR6 PAGING_SUCCESS_RATE

14 Feb 2003


68P02901W56-L 17–59

PAGING_SUCCESS_RATE

Description

The PAGING_SUCCESS_RATE statistic tracks the percentage of pages which receive asuccessful response from an MS. This statistic is measured on a location area basis.

Formula

PAGING_SUCCESS_RATE =PAGE_REQ_FROM_MSC

SUM (ACC_PROC[PAGE_RESPONSE])* 100%

where SUM (OK_ACC_PROC[PAGE_RESPONSE]) is summed across all cells in thelocation area and assuming paging is configured on a location area basis,PAGE_REQ_FROM_MSC is the maximum value occurring on any cell within the LAC.


Fault finding

Basis Location area.

Type Percentage.

RawStatistics

OK_ACC_PROC[PAGE_RESPONSE]

PAGE_REQ_FROM_MSC.

GSR6PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK

14 Feb 200317–60


68P02901W56-L

PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK

Description

The PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK statistic provides a ratio of theGPRS downlink traffic against the uplink traffic.

Formula

PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK =AIR_DL_DATA_BLKS + AIR_UL_DATA_BLKS

AIR_DL_DATA_BLKS * 100



Basis Cell.

Type Percentage.

RawStatistics

AIR_DL_DATA_BLKS

AIR_UL_DATA_BLKS.

GSR6 RANKING_FORMULA

14 Feb 2003


68P02901W56-L 17–61

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 thisstatistic increases as cells have high calling volumes and low call success rates. Highvalues for this statistic 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 tocalculate these health statistics are included in the raw statistics listing.

Formula

RANKING_FORMULA = (100 – CALL_SUCCESS_RATE) *CALL_SETUP_SUCCESS_RATE

TOTAL_CALLS

Usage Optimization.


Basis Cell.

Type Counter.

RawStatistics



MT_LCS_ON_SDCCH.







OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].




OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED] .

RF_LOSSES_TCH.

SMS_INIT_ON_SDCCH.

TOTAL_CALLS.

GSR6RF_ASSIGN_FAIL_RATE_LOST_MS

14 Feb 200317–62


68P02901W56-L

RF_ASSIGN_FAIL_RATE_LOST_MS

Description

The RF_ASSIGN_FAIL_RATE_LOST_MS statistic provides the percentage ofassignment commands that are sent to over the air interface which result in the MSfailing to access the target channel and failing to recover to the original channel; that is,the call drops. This statistic includes intra-cell handover assignment attempts.

Formula

RF_ASSIGN_FAIL_RATE_LOST_MS =

(MA_CMD_TO_MS – MA_COMPLETE_FROM_MS –MA_FAIL_FROM_MS) * 100

MA_CMD_TO_MS


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics

MA_CMD_TO_MS.

MA_COMPLETE_FROM_MS .

MA_FAIL_FROM_MS.

GSR6 RF_ASSIGN_FAIL_RATE_RECOVERED

14 Feb 2003


68P02901W56-L 17–63

RF_ASSIGN_FAIL_RATE_RECOVERED

Description

The RF_ASSIGN_FAIL_RATE_RECOVERED statistic provides the percentage ofassignment commands that are sent sent over the air interface which result in the MSfailing to access the target channel and subsequently successfully recovering to theoriginal channel. This statistic includes intra-cell handover assignment attempts.

Formula

RF_ASSIGN_FAIL_RATE_RECOVERED =MA_CMD_TO_MS

MA_FAIL_FROM_MS* 100


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics

MA_CMD_TO_MS.

MA_FAIL_FROM_MS.

GSR6RF_ASSIGNMENT_SUCCESS_RATE

14 Feb 200317–64


68P02901W56-L

RF_ASSIGNMENT_SUCCESS_RATE

Description

The RF_ASSIGNMENT_SUCCESS_RATE statistic provides the percentage ofassignment commands that are successfully sent over the air interface which result in theMS accessing the target channel. This statistic includes intra-cell handover assignmentattempts.

Formula

RF_ASSIGNMENT_SUCCESS_RATE =MA_CMD_TO_MS

MA_COMPLETE_FROM_MS* 100


Fault finding.

Basis Cell.

Type Percentage.

Raw Statistics MA_CMD_TO_MS.

MA_COMPLETE_FROM_MS .

GSR6 SDCCH_ACCESSES

14 Feb 2003


68P02901W56-L 17–65

SDCCH_ACCESSES

Description

The SDCCH_ACCESSES statistic tracks the number of SDCCH activations which resultin a successful seizure by the MS.

Formula

SDCCH_ACCESSES = (ALLOC_SDCCH – CHAN_REQ_MS_FAIL)

Usage RF loss.

Congestion.

Quality of service.

Network planning.

Basis Cell.

Type Counter.

RawStatistics

ALLOC_SDCCH.

CHAN_REQ_MS_FAIL.

GSR6SDCCH_BLOCKING_RATE

14 Feb 200317–66


68P02901W56-L

SDCCH_BLOCKING_RATE

Description

The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocatean SDCCH that were blocked due to no available SDCCH resources. This statisticincludes incoming SDCCH handover attempts.

Formula

SDCCH_BLOCKING_RATE =(ALLOC_SDCCH + ALLOC_SDCCH_FAIL)

ALLOC_SDCCH_FAIL* 100%


Quality of Service Monitoring.

Network planning.

Basis Cell.

Type Percentage.

RawStatistics

ALLOC_SDCCH.

ALLOC_SDCCH_FAIL.

GSR6 SDCCH_CONGESTION_TIME

14 Feb 2003


68P02901W56-L 17–67

SDCCH_CONGESTION_TIME

Description

The SDCCH_CONGESTION_TIME statistic tracks the amount of time in seconds that allSDCCHs are busy.

Formula

SDCCH_CONGESTION_TIME =1000

SDCCH_CONGESTION

Usage RF loss.

Congestion.

Quality of service.

Network planning.

Optimization.

Basis Cell.

Type Duration (seconds).

RawStatistics

SDCCH_CONGESTION.

GSR6SDCCH_TRAFFIC_CARRIED

14 Feb 200317–68


68P02901W56-L

SDCCH_TRAFFIC_CARRIED

Description

The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHsmeasured in Erlangs.

Formula

SDCCH_TRAFFIC_CARRIED = BUSY_SDCCH_MEAN


SDCCH_TRAFFIC_CARRIED = S BUSY_SDCCH_MEAN [k]m

k = 1

m


SDCCH_TRAFFIC_CARRIED = S BUSY_SDCCH_MEAN [k]n

k = 1


SDCCH_TRAFFIC_CARRIED =S BUSY_SDCCH_MEAN

[k]

m

k = 1

m

n

k = 1

S

The BUSY_SDCCH_MEAN statistic reports the mean number of busy trafficchannels during a collection interval.

Where BUSY_SDCCH_MEAN [k] is BUSY_SDCCH_MEAN for statisticalinterval k.

NOTE

Usage RF loss.

Congestion.

Network planning.

Optimization.

Basis BSS.

Type Counter.

Raw Statistic BUSY_SDCCH.

GSR6 TCH_ACCESSES

14 Feb 2003


68P02901W56-L 17–69

TCH_ACCESSES

Description

The TCH_ACCESSES statistic tracks the number of TCH activations which result in asuccessful seizure by the MS.

Formula

TCH_ACCESSES =

Cell Level

BSS Level

Network Level

TCH_ACCESSES =

TCH_ACCESSES = (TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

(TOTAL_CALLS +IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])

(TOTAL_CALLS + IN_INTER_BSS_HO_SUC +ASSIGNMENT_REDIRECTION)

Usage Handover.

Quality of service.

Network planning.


Type Counter.

RawStatistics




TOTAL_CALLS.

GSR6TCH_CONGESTION_TIME

14 Feb 200317–70


68P02901W56-L

TCH_CONGESTION_TIME

Description

The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that allTCHs are busy.

Formula

TCH_CONGESTION_TIME =1000

TCH_CONGESTION

Usage Congestion.

Quality of service.

Network planning.

Optimization.

Basis Cell.

Type Duration.

RawStatistics

TCH_CONGESTION.

GSR6 TCH_RF_LOSS_RATE

14 Feb 2003


68P02901W56-L 17–71

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

TCH_RF_LOSS_RATE =

Cell Level

BSS Level

Network Level

RF_LOSSES_TCH

(TOTAL_CALLS + IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC]+ IN_INTER_BSS[IN_INTER_BSS_HO_SUC])


(TOTAL_CALLS + ASSIGNMENT_REDIRECTION +IN_INTER_BSS[IN_INTER_HO_SUC])


TOTAL_CALLS + ASSIGNMENT_REDIRECTION

* 100%

* 100%

* 100%


Fault finding.

Basis Cell.

Type Percentage.

RawStatistics


IN_INTER_BSS[IN_INTER_HO_SUC].

IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC]

RF_LOSSES_TCH.

TOTAL_CALLS.

GSR6TCH_TRAFFIC_CARRIED

14 Feb 200317–72


68P02901W56-L

TCH_TRAFFIC_CARRIED

Description

The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHsmeasured in Erlangs.

Formula

For an individual cell for an individual statistics interval:

TCH_TRAFFIC_CARRIED = BUSY_TCH_MEAN


TCH_TRAFFIC_CARRIED = S BUSY_TCH_MEAN [k]m

k = 1

m


TCH_TRAFFIC_CARRIED = S BUSY_TCH_MEAN [k]n

k = 1


TCH_TRAFFIC_CARRIED =S BUSY_TCH_MEAN [k]m

k = 1

m

n

k = 1

SNOTE The BUSY_TCH_MEAN statistic reports the mean number of

busy traffic channels during a collection interval, whereBUSY_TCH_MEAN [k] is BUSY_TCH_MEAN for statisticalinterval k.

Usage Congestion.

Quality of service.

Network planning.

Optimization.

Basis Cell.

Type Units = Erlangs.

RawStatistics

BUSY_TCH (BUSY_TCH_MEAN).

GSR6 UL_AIR_INTERFACE_BW_CS1

14 Feb 2003


68P02901W56-L 17–73

UL_AIR_INTERFACE_BW_CS1

Description

The UL_AIR_INTERFACE_BW_CS1 statistic provides a reference value for theconfigured uplink bandwidth in a cell in terms of coding scheme 1 for a statisticscollection period.

Formula


UL_AIR_INTERFACE_BW_CS1 =

(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL

(TOTAL_AIR_UL_AVAILABLE_BW * 9.05)



Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.


TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1)

GSR6UL_AIR_INTERFACE_BW_CS2

14 Feb 200317–74


68P02901W56-L


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.


TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1).

GSR6 UL_AIR_INTERFACE_BW_CS3

14 Feb 2003


68P02901W56-L 17–75


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.



GSR6UL_AIR_INTERFACE_BW_CS4

14 Feb 200317–76


68P02901W56-L


Description


Formula



(50 * 3600) * INTERVAL




(50 * 3600) * INTERVAL




Basis Cell.

Type Counter.

RawStatistics

AVAILABLE_PDTCH.



GSR6 UPLINK_PDTCH_BLOCKING_RATE

14 Feb 2003


68P02901W56-L 17–77

UPLINK_PDTCH_BLOCKING_RATE

Description

The UPLINK_PDTCH_BLOCKING_RATE statistic provides the success rate of channelrequests in GPRS.

Formula

UPLINK_PDTCH_BLOCKING_RATE =CHANNEL_REQS_REC

CHANNEL_REQS_REJECT * 100%


Quality of Service Monitoring.

Network planning.

Basis Cell.

Type Percentage.

RawStatistics

CHANNEL_REQS_REJECT.

CHANNEL_REQS_REC.

GSR6UPLINK_TRAFFIC_VOLUME

14 Feb 200317–78


68P02901W56-L

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=

(1024 * 3600 * INTERVAL)

* 100%(AIR_UL_DATA_BLKS[QOS1_CS1] + AIR_UL_DATA_BLKS[QOS2_CS1] +

AIR_UL_DATA_BLKS[QOS3_CS1]) * 22) +(AIR_UL_DATA_BLKS[QOS1_CS2] + AIR_UL_DATA_BLKS[QOS2_CS2] +



AIR_UL_DATA_BLKS[QOS3_CS4]) * 52)




Basis Cell.

Type Percentage.

RawStatistics













14 Feb 2003


68P02901W56-L 18–1

Chapter 18

Ladder diagrams

GSR6

14 Feb 200318–2


68P02901W56-L

GSR6 Introduction to ladder diagrams

14 Feb 2003


68P02901W56-L 18–3

Introduction to ladder diagrams

Description of ladder diagrams

Ladder diagrams show the relationships between the MS, BSS, and MSC elementsrepresented as vertical lines.

The message flows between the network elements are presented as horizontal linesrepresenting a sequential flow of events. Arrows indicate the direction of the messageflow. Message names are placed above the directional line.

Intermediate network element functions are placed on the vertical lines as a sequentialreference. Parallel functions may also be included as separate vertical lines for additionalreference.

Statistics associated with individual messages are located immediately below thedirectional line. All of the statistics that may be generated as the result of the processflow is listed on the diagram.

Example

Figure 18-1 shows the relationships associated with an immediate assignment failure.

Figure 18-1 Diagram of immediate assignment failure

MS BSS



MSC

TIMEOUT

CHAN_REQ_MS_FAIL

OK_ACC_PROC_RACH (SEE NOTE)


GSR6Phone call model

14 Feb 200318–4


68P02901W56-L

Phone call model

BSS functions

The GSM BSS is a combination of digital and RF equipment, the purpose of which is toprovide the radio Air interface linking subscribers into the network and providing themwith service. It communicates with the Mobile Switching Centre (MSC), the Operationsand Maintenance Centre - Radio (OMC-R), and the Mobile Subscribers (MSs).

BSC functions

The main functions of the BSC include managing the radio channels and transferringcontrol messages to and from the MS. Control channels and bearer channels are alwaysunder the control of the BSC. However, many types of call handling messages do notdirectly affect the BSC and for these the BSC serves simply as a relay point between theMSC and the MS.

The BSC also incorporates a digital switching matrix. No fixed correspondence existsbetween the radio channels at the BSS and the terrestrial circuits, which connect theBSS to the MSC. While the BSC selects the radio channel, the terrestrial circuit isselected by the MSC, and it is the BSCs switching matrix that is used to connect the twotogether. The switching matrix also allows the BSC to perform handovers between theBTSs 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 andhandover procedures for all except intra-BSS and intra-cell handovers. MSC controlledintra-BSS handovers can be set as an option at the switch. Location registration (andlocation update) allows MSs to report changes in their locations enabling automaticcompletion of MS-terminated calls.

Handover procedure

The handover procedure preserves call connections as MSs move from one radiocoverage area to another during an established call. Handovers within cells controlled bya single BSC are handled by that BSC (intra-BSS and intra-cell). When handovers arebetween cells controlled by different BSCs, the primary control is at the MSC (inter-BSS).Handovers can also be performed between BSSs connected to two different MSCs(inter-MSC handover). In this case, GSM specifications define standard proceduresallowing the two MSCs to coordinate the handover.

GSR6 Phone call model

14 Feb 2003


68P02901W56-L 18–5

Figure 18-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.

GSR6Call procedure milestones

14 Feb 200318–6


68P02901W56-L

Call procedure milestones

Introduction

A general description of the milestones in a call is explained in the following paragraphs.

Call procedure

Bids

The first call procedure milestone is a request for service or resource (channelassignment request). At this point the MS will check the possibility of making a call,before attempting to make a call.

Bids – bids blocked

A bid is made for a resource (channel assignment request) but, if all channels are busy,due to other subscribers making phone calls, the bid is blocked. Further bids arerequested until a no blocking situation exists.

Bids – attempts

A bid is made and accepted to use a resource (channel assignment request). Now anattempt is made to assign the user to that resource, for example with a traffic channelassignment there is an assignment request from the MSC, but at this time theassignment to the TCH is not complete. Hence, the connection is not complete.

Bids – attempts – successes

An attempt has been made to assign a resource (channel assignment request) and theassignment is successful, hence the connection is complete.

Bids – attempt – failures (dropped)

An attempt is made to assign a resource (channel assignment request) but theassignment fails. It is not possible to recover the call and the call is lost.

Bids – attempt – fail – recovered

A resource is allocated to a MS which it found to be unusable. The call in progress wasnot lost but was able to revert to its previous radio resource.

GSR6 Call setup and handover

14 Feb 2003


68P02901W56-L 18–7

Call setup and handover

Description

Statistics describe the behaviour of the major call processing scenarios. Each scenario isbroken out into six milestones as shown in the vertical columns of Table 18-1.

Matrix

Table 18-1 shows the call setup and handover matrix:

Table 18-1 Call setup and handover matrix.

Procedure Milestones

Bids Blocked Attempts Success Failedlost

Failedrecovered

Immediate

Assignment

OK_ACC_PROC_RACH

and

ALLOC_SDCCH

see note 1

CHAN_REQ_MS_BLK

and

ALLOC_SDCCH_FAIL

see note 2

see note 3 OK_ACC_PROC CHAN_REQ_MS_FAIL

or

INV_EST_CAUSE_IN_

RACH

see note 5

N/A

Connection

Establishment

– – CONN_REQ_TO_MSC – CONN_REFUSED N/A

Assignment

to TCH at call set-up

MA_REQ_FROM_MSC MA_CMD_TO_MS_

BLKD

ALLOC_TCH_FAIL

MA_CMD_TO_MSC TOTAL_CALLS

and

MA_COMPLETE_TO_MSC

ALLOC_TCH

For further study MA_FAIL_FROM_MS

Handover

Intra-cell

INTRA_CELL_HO_REQ ALLOC_SDCCH_FAIL

or

HO_FAIL_NO_

RESOURCES

(INTER_BSS)

or

ALLOC_TCH_FAIL

INTRA_CELL_HO_AT

MPT

and

MA_CMD_TO_MS

INTRA_CELL_HO INTRA_CELL_HO_LOSTMS INTRA_CELL_HO_FAIL

and

MA_FAIL_FROM_MS

Handover

Intra-BSS

(outgoing)

OUT_INTRA_BSS_HO_

REQ

OUT_INTRA_HO_PRI

_BLK

or

HO_FAIL_NO_

RESOURCES

(INTRA_BSS)

OUT_INTRA_BSS_HO

_ATMPT

and

OUT_HO_CAUSE_AT

MPT

and

OUT_HO_NC_CAUSE

_ATMPT

OUT_INTRA_BSS_HO

and

OUT_HO_NC_SUC

OUT_INTRA_BSS_HO

_LOSTMS

OUT_INTRA_BSS_HO_

FAIL

Handover

Inter-BSS

(outgoing)

OUT_INTER_BSS_REQ

_TO_MSC

HO_FAIL_NO_

RESOURCES

(INTER_BSS)

OUT_INTER_BSS_HO

_ATMPT

and

OUT_HO_CAUSE_AT

MPT

and

OUT_HO_NC_CAUSE

_ATMPT

OUT_INTER_BSS_HO

_SUC

OUT_INTER_BSS_HO

_LOSTMS

OUT_INTER_BSS_HO

_RETURN

GSR6Call setup and handover

14 Feb 200318–8


68P02901W56-L

Procedure Milestones

Bids Blocked Attempts Success Failedlost

Failedrecovered

Handover

Intra-BSS

(incoming)

For further study For further study

ALLOC_SDCCH_FAIL

or

ALLOC_TCH_FAIL

IN_INTRA_BSS_NC_A

TMPT

or

ALLOC_SDCCH

or

ALLOC_TCH

IN_INTRA_BSS_HO_SUC

and

IN_INTRA_BSS_NC_SUC

IN_INTRA_BSS_HO

_LOSTMS

IN_INTRA_BSS_HO

_RETURN

Handover

Inter-BSS

(incoming)

For further study For further study

see note 4

ALLOC_SDCCH_FAIL

or

ALLOC_TCH_FAIL

HO_REQ_MSC_OK

ALLOC_SDCCH

or

ALLOC_TCH

IN_INTER_BSS_HO IN_INTER_BSS_HO

[IN_INTER_BSS_MS_

NO_SEIZE]

IN_INTER_BSS_HO

[IN_INTER_BSS_MS_N

O_SEIZE]

Notes

The following notes refer to the call setup and handover matrix:

1. OK_ACC_PROC_SUC_RACH may be, but is not necessarily equal toALLOC_SDCCH because they are pegged by different processes and filteringtakes place between the two pegs. ALLOC_SDCCH is pegged at the target cell forSDCCH Handovers. If OK_ACC_PROC_SUC_RACH is less thanALLOC_SDCCH, some of the ALLOC_SDCCH pegs are due to SDCCHHandovers into the cell. And if ALLOC_SDCCH is less thanOK_ACC_PROC_SUC_RACH, some of the RACHs have been filtered betweenthe two pegs.

2. CHAN_REQ_MS_BLK may be, but is not necessarily equal toALLOC_SDCCH_FAIL. ALLOC_SDCCH_FAIL is pegged for ImmediateAssignment and also for SDCCH Handovers. CHAN_REQ_MS_BLK is onlypegged for Immediate Assignment. CHAN_REQ_MS_BLK andALLOC_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 (noresources available).

5. A phantom RACH or badly formed (invalid) channel request was detected, so noresource was allocated and the call set-up procedure ended.

GSR6 Connection establishment

14 Feb 2003


68P02901W56-L 18–9


Introduction

Figure 18-3 to Figure 18-7 show the ladder diagrams for the connection establishmentprocedures. Figure 18-3 shows that connection establishment is successful afterimmediate assignment is successful, while Figure 18-7 shows successfulmobile–terminated connection establishment.

Successful mobile originated

Figure 18-3 shows a successful mobile generated connection establishment.

Figure 18-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

GSR6Connection establishment

14 Feb 200318–10


68P02901W56-L

Failure

Figure 18-4 shows a connection establishment failure.

Figure 18-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

GSR6 Connection establishment

14 Feb 2003


68P02901W56-L 18–11

Immediate assignment blocked

Figure 18-5 shows an immediate assignment blocked.

Figure 18-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 18-6 shows an immediate assignment failure.

Figure 18-6 Immediate assignment failure

MS BSS


MSC

TIMEOUT

CHAN_REQ_MS_FAIL




ALLOC_SDCCH


ACCESS_PER_RACH

ACCESS_PER_AGCH

MS_ACCESS_BY_TYPE

GSR6Connection establishment

14 Feb 200318–12


68P02901W56-L

Successful mobile terminated call

Figure 18-7 shows a successful connection establishment (mobile terminated call).

Figure 18-7 Connection establishment (mobile terminated call) successful

MS BSS

PAGING REQUEST


MSC

ACCESS_PER_RACH


CONNECTION REQUEST



ACCESS_PER_PCH

PAGE_REQ_FROM_MSC

CHAN_REQ_CAUSE_ATMPT(PAGING RESPONSE)


CONN_REQ_TO_MSC

CONNECTION ESTABLISHMENT

PAGING

MS_ACCESS_BY_TYPE

ALLOC_SDCCH

ACCESS_PER_AGCH

ACCESS_PER_AGCH


CONNECTION CONFIRM

< CC>

(MOBILE TERMINATED)

SABMT INITIAL LAYER 3 MESSAGE (SDCCH)

OK_ACC_PROC (PAGING_RESPONSE)

GSR6 Assignment to TCH

14 Feb 2003


68P02901W56-L 18–13

Assignment to TCH

Introduction

Figure 18-8 to Figure 18-11 show the ladder diagrams for the assignment to TCHprocedures.

Assignment successful

Figure 18-8 shows a successful TCH assignment.

Figure 18-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 types of MS. Will not be pegged after the TCH is deallocated.

MA_COMPLETE_FROM_MS

(SEE NOTE 2)

GSR6Assignment to TCH

14 Feb 200318–14


68P02901W56-L

Immediate assignment failure

Figure 18-9 shows an immediate assignment failure.

Figure 18-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 18-10 shows a TCH assignment blocked.

Figure 18-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

GSR6 Assignment to TCH

14 Feb 2003


68P02901W56-L 18–15

Fail recovered

Figure 18-11 shows a TCH assignment fail-recovered to a SDCCH.

Figure 18-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

NOTE: Failure to access Traffic Channel.

MA_REQ_FROM_MSC

ALLOC_TCH

GSR6Intra-cell handover

14 Feb 200318–16


68P02901W56-L

Intra-cell handover

IntroductionFigure 18-12 to Figure 18-15 show the ladder diagrams for the intra-cell handoverprocedure. Intra-cell handovers deal with channels within the same cell; that is, theTarget Cell = Source Cell.

Handover successfulFigure 18-12 shows a successful intra-cell handover.

Figure 18-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

Handover blockedFigure 18-13 shows an intra-cell handover blocked.

Figure 18-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.

GSR6 Intra-cell handover

14 Feb 2003


68P02901W56-L 18–17

Fail recovered

Figure 18-14 shows an intra-cell handover fail-recovered to a source channel.

Figure 18-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

Fail lost

Figure 18-15 shows an intra-cell handover fail-lost.

Figure 18-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

GSR6Inter-BSS handover

14 Feb 200318–18


68P02901W56-L

Inter-BSS handover

Introduction

Figure 18-16 to Figure 18-19 show the ladder diagrams for the inter-BSS handoverprocedure.

Handover successful

Figure 18-16 shows a successful inter-BSS handover.

Figure 18-16 Handover (inter-BSS) successful

MSC BSS(SOURCE)

MS (TARGET CHANNEL TARGET CELL)

HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT

MS (SOURCECHANNELSOURCE 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_MSC_OK(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

GSR6 Inter-BSS handover

14 Feb 2003


68P02901W56-L 18–19

Handover blocked

Figure 18-17 shows an inter-BSS handover blocked.

Figure 18-17 Handover (inter-BSS) blocked

MS(SOURCE CHANNELSOURCE CELL)

BSS(SOURCE)


HO_REQ_MSC_FAIL(SEE NOTE 3)

MSC BSS(TARGET)

HANDOVERREQUIRED(SEE NOTE 1)

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)

HANDOVER REQUIRED(SEE NOTE 2)

OUT_INTER_BSS_HO(OUT_INTER_BSS_REQ_TO_MSC)


ALLOC_TCH_FAIL

HO_FAIL_NO_RESOURCES

(INTER_BSS_HO)


14 Feb 200318–20


68P02901W56-L

Fail recovered

Figure 18-18 shows an inter-BSS handover fail-recovered.

Figure 18-18 Handover (inter-BSS) fail-recovered

MS(SOURCECHANNELSOURCE CELL)

BSS(SOURCE)

MS (TARGETCHANNELTARGET CELL)

HANDOVER COMMAND


MSC BSS(TARGET)


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



14 Feb 2003


68P02901W56-L 18–21

Fail lost

Figure 18-19 shows an inter-BSS handover fail-lost.

Figure 18-19 Handover (inter-BSS) fail-lost


BSS(SOURCE)

MS (TARGET CHANNEL TARGET CELL)MSC

BSS(TARGET)

HANDOVERRECOGNIZED

HANDOVERCOMMAND

HANDOVERREQUIRED HANDOVER

REQUEST

HANDOVERREQUESTACKNOWLEDGEHANDOVER

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.


14 Feb 200318–22


68P02901W56-L

Fail lost (mobile)

Figure 18-20 shows an inter-BSS handover failure with lost mobile.

Figure 18-20 Inter-BSS handover failure with lost mobile


BSS(SOURCE)

MS (TARGET CHANNEL TARGET CELL)MSC

BSS(TARGET)

HANDOVERCOMMAND

HANDOVER REQUIRED

HANDOVERREQUEST

HANDOVERREQUESTACKNOWLEDGE

HANDOVERCOMMAND

(SEE NOTE 1)


OUT_INTER_BSS_HO(OUT_INTER_BSS_REQ_TO_MSC

OUT_HO_CAUSE_ATMPT


ALLOC_TCH orALLOC_SDCCH

HO_REQ_MSC_OK

(SEE NOTE 2)

TIMEOUT(SEENOTE 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.


14 Feb 2003


68P02901W56-L 18–23

Standard directed retry (external)

Figure 18-21 shows an inter–BSS handover directed retry external.

Figure 18-21 Inter-BSS handover directed retry external


BSS(SOURCE)


MSC BSS(TARGET)

HANDOVERCOMMAND

ASSIGNMENTREQUEST

HANDOVERREQUEST


MA_REQ_FROM_MSC

CALLS_QUEUED

TCH_Q_LENGTH

HANDOVERCOMMAND

CLEAR COMMAND


OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_SUC)

OUT_HO_NC_SUC


HANDOVERCOMPLETE

ALLOC_TCHor ALLOC_SDCCH


IN_INTER_BSS_HO(SUCCESSFUL)HANDOVER

COMPLETE


OUT_HO_CAUSE_ATMPT(CONGESTION)


QUEUEING INDICATION(SEE NOTE 1)ASSIGNMENT FAILURECAUSE DIRECTED RETRY(SEE NOTE 2)

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.

GSR6Intra-BSS handover

14 Feb 200318–24


68P02901W56-L

Intra-BSS handover

Introduction

Figure 18-22 to Figure 18-25 show the ladder diagrams for the intra-BSS handoverprocedure.

Handover successful

Figure 18-22 shows a successful intra-BSS handover.

Figure 18-22 Handover (intra-BSS) successful


BSSMS (TARGETCHANNELTARGET 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)

GSR6 Intra-BSS handover

14 Feb 2003


68P02901W56-L 18–25

Handover- blockedFigure 18-23 shows an intra-BSS handover-blocked.

Figure 18-23 Handover (intra-BSS) blocked

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_REQ)(SEE NOTE 1)


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-recoveredFigure 18-24 shows an intra-BSS handover fail-recovered.

Figure 18-24 Handover (intra-BSS) fail-recovered

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_REQ)

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)


GSR6Intra-BSS handover

14 Feb 200318–26


68P02901W56-L

Fail-lost

Figure 18-25 shows an intra-BSS handover fail-lost.

Figure 18-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

GSR6 Intra-BSS handover

14 Feb 2003


68P02901W56-L 18–27

Standard directed retry (internal)

Figure 18-26 displays the ladder diagram for intra-BSS handover standard directed retry.

Figure 18-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_HO_CAUSE_ATMPT (CONGESTION)

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

OUT_HO_NC_CAUSE_ATMPT(CONGESTION)


ASSIGNMENT FAILURE CAUSE DIRECTED RETRY (SEE NOTE 2)


HANDOVER COMMAND

GSR6Call clearing

14 Feb 200318–28


68P02901W56-L

Call clearing

IntroductionFigure 18-27 to Figure 18-30 show the ladder diagrams for the call clearing procedures.

Cipher mode failFigure 18-27 shows BSS initiated call clearing – cipher mode fail.

Figure 18-27 BSS initiated call clearing–cipher mode fail

MS BSS MSC

CLR_REQ_TO_MSC

CLEAR REQUEST

CIPHERING MODE COMMAND

CIPHER_MODE_FAIL

TIMEOUT

RF loss on an SDCCHFigure 18-28 shows BSS initiated call clearing (RF loss on an SDCCH).

Figure 18-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.

GSR6 Call clearing

14 Feb 2003


68P02901W56-L 18–29

RF loss on a TCH

Figure 18-29 shows BSS initiated call clearing – RF loss on a TCH.

Figure 18-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 18-30 shows BSS initiated call clearing (queueing timeout).

Figure 18-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

GSR6Short message service

14 Feb 200318–30


68P02901W56-L

Short message service

Introduction

Figure 18-31 and Figure 18-32 show the ladder diagrams for the short message serviceprocedures.

Mobile originated

Figure 18-31 shows MS originated short message service (point-to-point).

Figure 18-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

Mobile terminated

Figure 18-32 shows mobile terminated short message service (point-to-point).

Figure 18-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

GSR6 Congestion Relief

14 Feb 2003


68P02901W56-L 18–31

Congestion Relief

Intra-BSS congestion relief

Example

Figure 18-33 shows the relationships associated with an intra-BSS congestion reliefhandover procedure. An MS attempts to access a TCH in the cell which is congestedand one (or possibly multiple) MS is handed out to free a TCH.

Figure 18-33 Intra-BSS congestion relief handover procedure


QUEUEING INDICATION (SEE NOTE)

MS

CALLS_QUEUED

MA_REQ_FROM_MSC

TCH_Q_LENGTH


OUT_HO_CAUSE_ATMPT(CONGESTION)

HANDOVER COMMAND




ASSIGNMENT COMPLETE

NOTE: Only if queueing is enabled for the cell.

CONGEST_EXIST_HO_ATMPT(SEE NOTE)

MA_COMPLETE_TO_MSC

OUT_HO_NC_CAUSE_ATMPT(CONGESTION)

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

GSR6Directed retry

14 Feb 200318–32


68P02901W56-L

Directed retry

Intra-BSS directed retry

Example

Figure 18-34 shows the relationships associated with an intra-BSS directed retryprocedure.

Figure 18-34 Intra-BSS directed retry procedure


QUEUING INDICATION (SEE NOTE 1)

MS

CALLS_QUEUED

MA_REQ_FROM_MSC

TCH_Q_LENGTH


OUT_HO_CAUSE_ATMPT

CONGEST_STAND_HO_ATMPT (SEE NOTE1)

HANDOVER COMMAND




ASSIGNMENT COMPLETE (SEE NOTE 2)

NOTES:1. Only if queuing is enabled for the cell2. The database element msc_preference indicates that directed retry procedures are limited towithin the BSS. The BSS sends a Handover Performed message, which indicates 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)

GSR6 Flow control

14 Feb 2003


68P02901W56-L 18–33

Flow control

Description

Flow Control barred measures the duration for which access classes are barred as aresult of flow control. The statistic duration will be started when any of the accessclasses are barred due to flow control and stopped when the last access class which wasbarred due to flow control is unbarred.

Example

Figure 18-35 shows the relationships associated with an access procedure.

Figure 18-35 Access procedure

BSS

START OF ACCESS CLASS-BARRING DUE TO FLOWCONTROL.

DURATION

FLOW_CONTROL_BARRED

LAST ACCESS CLASS UN-BARRED FROM FLOW CON-TROL ACTIONS.

GSR6Intra-BSS interband activity

14 Feb 200318–34


68P02901W56-L

Intra-BSS interband activity

IntroductionFigure 18-36 to Figure 18-38 show interband activity handover ladder diagrams. Thesediagrams specifically show the outgoing handover statistics. By only showing outgoinghandover statistics, a better focus is placed on the pegging aspects ofINTERBAND_ACTIVITY. For a complete handover statistic pegging description(outgoing and incoming) refer to the general handover ladder diagrams in this chapter.

Handover successfulFigure 18-36 shows an established call on TCH with a subsequent successful intra-BSShandover to a PGSM cell.

Figure 18-36 Successful intra–BSS handover


BSS MS (TARGETCHANNELTARGET 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_HO_NC_CAUSE_ATMPT(BAND_HANDOVER) (SEE NOTE 2)

INTERBAND_ACTIVITY(PGSM_HO_ATMPT) (SEE NOTE 3)


OUT_HO_NC_SUC


HANDOVERCOMPLETE

GSR6 Intra-BSS interband activity

14 Feb 2003


68P02901W56-L 18–35

Handover unsuccessful (fail recovered)

Figure 18-37 shows an established call on TCH with a subsequent handover attempt to aPGSM cell. The handover is unsuccessful with MS fail recovered to source cell (originalchannel).

Figure 18-37 Unsuccessful interband handover with fail–recovered source cell



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_ATMPT) (SEE NOTE 3)


INTERBAND_ACTIVITY(PGSM_HO_FAIL)

OUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_RETURN)

HANDOVER FAILURE

GSR6Intra-BSS interband activity

14 Feb 200318–36


68P02901W56-L

Handover unsuccessful (fail recovered due to invalid frequency supported)

Figure 18-38 shows an established call on TCH with subsequent intra-BSS handoverattempt to PGSM cell. The handover is unsuccessful due to invalid frequency supportedwith MS fail recovered to source cell (original channel).

Figure 18-38 Unsuccessful interband handover



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– FREQUENCYNOT 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

GSR6 Inter-BSS interband activity

14 Feb 2003


68P02901W56-L 18–37

Inter-BSS interband activity

Handover successful

Figure 18-39 shows an established call on TCH with a subsequent successful inter-BSShandover to a PGSM cell.

Figure 18-39 Successful inter-BSS handover

MSC BSS(SOURCE)


HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT


BSS(TARGET)


HANDOVER COMMAND

HANDOVER REQUEST

HANDOVER COMPLETECLEAR

COMMAND

INTERBAND_ACTIVITY(PGSM_HO_ATMPT)(SEE NOTE 5)



MS_ACCESS_BY_TYPE(SEE NOTE 2)

ALLOC_TCH

OUT_HO_NC_CAUSE_ATMPT (BANDHANDOVER) (SEE NOTE 4)


HO_REQ_MSC_OK

(SEE NOTE 3)

OUT_INTER_BSS_HO(OUT_INTER_BSS_HO_SUC)

OUT_HO_NC_SUC

HANDOVER COMPLETE

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

GSR6Inter-BSS interband activity

14 Feb 200318–38


68P02901W56-L


Figure 18-40 shows an established call on TCH with a subsequent inter-BSS handoverattempt to a PGSM cell. The handover is unsuccessful with MS fail recovered to sourcecell (original channel).

Figure 18-40 Inter-BSS handover unsuccessful with fail–recovered source cell

MSC BSS(SOURCE)


HANDOVER COMMAND

OUT_HO_CAUSE_ATMPT


BSS(TARGET)


HANDOVER COMMAND

HANDOVER REQUEST




MS_ACCESS_BY_TYPE(SEE NOTE 2)

ALLOC_TCH



HO_REQ_MSC_OK

(SEE NOTE 3)


INTERBAND_ACTIVITY(PGSM_HO_FAIL)(SEE NOTE 5)

HANDOVER FAILURE

HANDOVER FAILURE

HO_REQ_MSC_FAIL

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

GSR6 Inter-BSS interband activity

14 Feb 2003


68P02901W56-L 18–39

Handover unsuccessful fail recovered due to invalid frequency supported

Figure 18-41 shows an established call on a TCH with subsequent inter-BSS handoverattempt to a PGSM cell. The handover is unsuccessful due to invalid frequencysupported with MS fail recovered to source cell (original channel).

Figure 18-41 Inter-BSS handover unsuccessful due to invalid frequency supported

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



HO_REQ_MSC_OK

(SEE NOTE 3)


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)

GSR6Interband assignment

14 Feb 200318–40


68P02901W56-L

Interband assignment

Interband activity invalid frequency at assignment

Figure 18-42 shows an invalid frequency at assignment.

Figure 18-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

GSR6 Band Reassignment

14 Feb 2003


68P02901W56-L 18–41

Band Reassignment

Introduction

Figure 18-43 and Figure 18-44 show band reassign ladder diagrams. These diagramsspecifically show the outgoing handover statistics. By only showing outgoing handoverstatistics, a better focus is placed on the pegging aspects of the band reassign cause.

Handover successful

Figure 18-43 shows an intra-BSS handover attempt of a MS from an SDCCH in thesource cell (frequency band PGSM) to a TCH in a target cell (frequency band DCS1800).The MS is a dual mode PGSM/DCS1800 capable mobile.

Figure 18-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)HANDOVER

COMPLETE(RECEIVED FROMTARGET CELL)


OUT_HO_NC_SUC

GSR6Band Reassignment

14 Feb 200318–42


68P02901W56-L


Figure 18-44 shows an unsuccessful band reassign.

Figure 18-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)HANDOVER

FAILUREOUT_INTRA_BSS_HO(OUT_INTRA_BSS_HO_RETURN)

INTERBAND_ACTIVITY(DCS1800_HO_FAIL)

GSR6 RSL link scenarios

14 Feb 2003


68P02901W56-L 18–43

RSL link scenarios

Introduction

Figure 18-45 shows a ladder diagram scenario for the Radio Signalling Link (RSL) link.

RSL link scenarios

Figure 18-45 RSL link scenarios

RSL LINK

N2_EXPIRY (note 2)

SABM_TX (note 1)

STEP 1:

lock of RSLlock of associated MSIlock of associated MMSfront panel resetMSI board physically removedtransmit and or receive path terminated

STEP 2 :

unlock of RSLunlock of associated MSIunlock of associated MMSfront panel resetMSI physically returnedtransmit 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_t200 timer, 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 will cease as all cells at the site will be barred.

GSR6MTL link scenarios

14 Feb 200318–44


68P02901W56-L

MTL link scenarios

Introduction to MTL link scenariosFigure 18-46 to Figure 18-49 show four ladder diagrams as scenarios for the MessageTransfer Link (MTL) link.

MTL link (operator initiated outage)

Figure 18-46 MTL link scenario (Part I)

MTL LINK

MTP_LINK_INStimer stopped

MTP_UNAVAILABLEtimer started

STEP 1:

lock of MTLlock of associated MSI/XCDRlock of associated MMSfront panel resetMSI/XCDR board physically removed

STEP 2:

unlock of MTLunlock of associated MSI/XCDRunlock of associated MMSfront panel restoreMSI/XCDR board physically returned

MTL LINK

MTP_UNAVAILABLEtimer stopped

MTP_RESTORATIONincremented

MTP_LINK_INStimer started

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.

Lock of MTL or associated device transitions operator and admin states fromB–U to D–L

Unlock of MTL or associated device transitions operator and admin states fromD–L to B–U.

NOTE

GSR6 MTL link scenarios

14 Feb 2003


68P02901W56-L 18–45

MTL link (transition scenarios Part II)

Figure 18-47 shows an MTL transition from B–U to E–U and E–U to B–U with reasonWait.

Figure 18-47 MTL link transition scenarios (Part II)

MTL LINK


MTP_SL_FAILincremented

STEP 1: (MTL transitions from B–U to E–U with reason Wait)

STEP 2: (MTL transitions from E–U withreason Wait to B–U

MTL LINK

MTP_LINKFAILtimer stopped




MTP_LINKFAIL timerstarted


MTP_SL_ALIGNMENTincremented


GSR6MTL link scenarios

14 Feb 200318–46


68P02901W56-L

MTL link (transition scenarios Part III)

Figure 18-48 shows an MTL transition from B–U to D–U and D–U to B–U with reasonWait MMS not in service.

Figure 18-48 MTL link transition scenarios (Part III)

MTL LINK



STEP 1: (MTL transitions from B–U to D–U with reason Wait MMS not in service)

STEP 2: (MTL transitions from D–U with reason Wait MMS not in service

MTL LINK





MTP_LNK_INStimer started


GSR6 MTL link scenarios

14 Feb 2003


68P02901W56-L 18–47

MTL link (transition scenarios Part IV)

Figure 18-49 shows an MTL transition from B–U to E–U and E–U to B–U with reasonWait improper timeslot mapping between BSC and MSC.

Figure 18-49 MTL link transition scenarios (Part IV)

MTL LINK



STEP 1: (MTL transitions from B–U to E–U with reason Wait, with improper timeslotmapping between BSC and MSC)

STEP 2: (MTL transitions from E–U with reason Wait to B–U with impropertimeslot mapping between BSC and MSC

MTL LINK





MTP_LNK_INStimer started


MTP_SL_ERROR_RATEincremented


MTP_SL_ALIGNMENTincremented (periodically repeats)

GSR6GBL statistics

14 Feb 200318–48


68P02901W56-L

GBL statistics

Introduction to GBL statisticsFigure 18-50 to Figure 18-54 show how the GBL statistics function within the BSS/PCU.

GBL_DL_DATA_THRPUTFigure 18-50 shows GBL_DL_DATA_THRPUT.

Figure 18-50 GBL_DL_DATA_THRPUT

GBL_DL_DATA_THRPUT

GBL_DL_DATA_THRPUT_TIME_PERIOD

Bearer chan 1

DLCI = 45

DLCI = 55

DLCI = 45

DLCI = 55

GSR6 GBL statistics

14 Feb 2003


68P02901W56-L 18–49

GBL_FLOW_CTRL_SENT

Figure 18-51 is a ladder diagram detailing the statistic GBL_FLOW_CTRL_SENT whenit is pegged. It also shows the request and the response messages sent from theBSS/PCU to the SGSN.

Figure 18-51 GBL_FLOW_CTRL_SENT

BSSGP FLOW CONTROL PDU

BSSGP FLOW CONTROL ACK PDU

BSS/PCU SGSN

GBL_FLOW_CTRL_SENT

GSR6GBL statistics

14 Feb 200318–50


68P02901W56-L

CELL_FLUSH_REQS

Figure 18-52 illustrates the statistic CELL_FLUSH_REQS when it is pegged. It alsoshows the request and the response sent from the SGSN to the PS.

Figure 18-52 CELL_FLUSH_REQS

FLUSH PDU FLUSH PDU

SGSN GB FU

CELL_FLUSH_REQS

PS

GSR6 GBL statistics

14 Feb 2003


68P02901W56-L 18–51

GBL_PAGING_REQS

Figure 18-53 is a ladder diagram detailing the statistic GBL_PAGING_REQS when it ispegged. It also shows the request and the response messages sent from the SGSN tothe BSS/PCU and the MS.

Figure 18-53 GBL_PAGING_REQS

MSBSS/PCU

Channel Request (RACH)

SGSN

BSSGP PS PDU

GBL_PAGING_REQS

PACKET PAGING REQEST (PCH)

Immediate Assignment (GCH)

GSR6GBL statistics

14 Feb 200318–52


68P02901W56-L

GBL_UL_DATA_THRPUT

Figure 18-54 illustrates the statistic GBL_UL_DATA_THRPUT.

Figure 18-54 GBL_UL_DATA_THRPUT

GBL_UL_DATA_THRPUT

GBL_UL_DATA_THRPUT_TIME_PERIOD

Bearer chan 1

DLCI = 45

DLCI = 55

DLCI = 45

DLCI = 55

GSR6 Accessibility statistics

14 Feb 2003


68P02901W56-L 18–53

Accessibility statistics

Introduction to accessibility statistics

Figure 18-55 to Figure 18-59 illustrate accessibility statistics.

CHANNEL_REQ_REJ

Figure 18-55 is a ladder diagram detailing the statistic CHANNEL_REQ_REJ when it ispegged. It also shows the request and the response messages sent from the BSS/PCUto the mobile station.

Figure 18-55 Accessibility CHANNEL_REQ_REJ

Immediate Assignment (AGCH)

MSBSS/PCU

Packet Resource Request

CHANNEL_REQ_REJ

PACKET ACCESS REJECT

GSR6Accessibility statistics

14 Feb 200318–54


68P02901W56-L

Channel request (RACH) and immediate assignment (AGCH)

Figure 18-56 is a ladder diagram detailing the statistics GPRS_ACCESS_PER_RACHand GPRS_ACCESS_PER_AGCH when pegging occurs. It also shows the request andthe response messages sent from the BSS/PCU to the mobile station.

Figure 18-56 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH

MSBSS/PCU






14 Feb 2003


68P02901W56-L 18–55

Accessibility and GBL statistics

Figure 18-57 is a ladder diagram detailing the statistics GBL_PAGING_REQS,GPRS_ACCESS_PER_RACH, and GPRS_ACCESS_PER_AGCH when peggingoccurs. It also shows the request and response messages sent from the SGSN to theBSS/PCU and to the MS.

Figure 18-57 Accessibility and GBL statistics

MSBSS/PCU





SGSN

BSSGP PS PDU

GBL_PAGING_REQS

PACKET PAGING REQUEST (PCH)

GSR6Accessibility statistics

14 Feb 200318–56


68P02901W56-L

Pegging for MS class types

Figure 18-58 is a ladder diagram detailing three MS class type statistics and whenpegging occurs. It also shows the request and response messages sent from theBSS/PCU to the mobile station.

Figure 18-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


14 Feb 2003


68P02901W56-L 18–57


Figure 18-59 details the GPRS_CHANNELS_SWITCHED statistic.

Figure 18-59 CHANNELS_SWITCHED

TCHSW

GPRSRESSW

GPRSRESSW

GPRSSW RES

TCHSW RES

TCHRESSW

GPRSSW RES


GPRS GPRS GPRSGPRS

GPRS GPRS GPRSGPRS GPRS

GSR6Throughput statistics

14 Feb 200318–58


68P02901W56-L

Throughput statistics

Introduction to throughput statistics

Figure 18-60 and Figure 18-61 show throughput statistics diagrams.

AIR_UL_DATA_BLKS

Figure 18-60 is a ladder diagram detailing the statistic AIR_UL_DATA_BLKS and whenpegging occurs. It also shows the request and response messages sent from theBSS/PCU to the MS.

Figure 18-60 Uplink data transfer

PACKET UPLINK ASSIGNMENT

MSBSS/PCU

DATA BLOCK

AIR_UL_DATA_BLKS

QOS1 QOS2 QOS3CS1 CS1 CS1


GSR6 Throughput statistics

14 Feb 2003


68P02901W56-L 18–59

AIR_DL_DATA_BLKS

Figure 18-61 is a ladder diagram detailing the statistic AIR_DL_DATA_BLKS and whenpegging occurs. It also shows the request and response messages sent from theBSS/PCU to the MS.

Figure 18-61 Downlink data transfer

PACKET DOWNLINK ASSIGNMENT

MSBSS/PCU

DATA BLOCK

AIR_DL_DATA_BLKS



GSR6Throughput statistics

14 Feb 200318–60


68P02901W56-L

14 Feb 2003


68P02901W56-L 19–1

Chapter 19

Impacts on statistics

GSR6

14 Feb 200319–2


68P02901W56-L

GSR6 Introduction to EGSM, approximate equality, and phantom RACHs

14 Feb 2003


68P02901W56-L 19–3

Introduction to EGSM, approximate equality, and phantomRACHs

Introduction

This chapter contains two main sections:

S EGSM, approximate equality, and phantom RACHs.

S Questions and answers.

Description of EGSM, approximate equality, and phantom RACHs

The collection, interpretation and accuracy of GSM statistics may be affected by anumber of factors, for example, new software and hardware features. Although not all ofthe factors are directly related to statistics, they all have a definite impact on them.

The following items have an impact on statistics:

S Extended GSM (EGSM).

S Approximate equality.

S Phantom RACHs.

GSR6Extended GSM (EGSM)

14 Feb 200319–4


68P02901W56-L

Extended GSM (EGSM)

Overview of EGSM

EGSM900 (Extended GSM) provides the BSS with a further range of frequencies for MSand BSS transmit. EGSM MSs can use the extended frequency band as well as theprimary band, while non-EGSM MSs cannot use the extended frequency band. AGSM900 cell can contain both GSM900 and EGSM900 carrier hardware.

Requirements

Although EGSM provides additional frequencies for use, several functions must remain inthe original GSM900 band. Functions that must be performed in the GSM900 band are:

S BCCH carrier frequency.

S SDCCH configuration.

S TCH allocation for immediate assignment.

Channel allocation

Channel allocation for an EGSM MS proceeds in a way such that the search is betweenextended then primary band frequencies, starting from best to worst interference bandsuntil a channel is found.

Forced handovers

To avoid blocking of non-EGSM MSs, an extended band MS using a primary resourcecan be forced to handover to an idle extended band resource with an interference bandresiding above or meeting a specified threshold.

The database parameter egsm_handover_threshold indicates the range of interferencebands allowed for handing over an extended MS using a primary resource that is neededby a non-EGSM MS. Allowed interference bands are those above or meeting a specifiedthreshold, which are considered quality resources. The operator also has the option todisallow forced handovers by disabling the egsm_handover_threshold flag.

GSR6 Extended GSM (EGSM)

14 Feb 2003


68P02901W56-L 19–5

Factors impacting statistics

Factors that contribute to the impacting of statistic values are:

S The relative number of primary and extended band resources at a cell compared tothe number of EGSM and non-EGSM capable MSs trying to access the cell.

S The egsm_handover_threshold flag value.

The following examples illustrate the impact of the EGSM feature on statistics:

Example 1: MS access to a traffic channel

The following conditions must apply:

S EGSM MSs have used up the primary resources in the cell.

S Non-EGSM MSs are attempting to access the cell.

S The egsm_handover_threshold flag either does not allow or limits handoversfrom primary resources to extended resources.

It is more difficult for non-EGSM MSs to access a TCH since EGSM MSs are occupyingthe primary resources.

The statistics impacted are shown in Table 19-1.

Table 19-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

NOTE TCH_CONGESTION is lower because it is pegged when allTCHs are busy, not just the primary band TCHs, even thoughcongestion exists for the primary MSs in this example.

GSR6Extended GSM (EGSM)

14 Feb 200319–6


68P02901W56-L

Example 2: Impact due to increased handovers


S The egsm_handover_flag encourages the handovers of EGSM MSs.

S Many EGSM MSs occupy primary resources.

S Non-EGSM MSs attempt to access the cell.

More intra-cell handovers are attempted to move the EGSM MSs off of primaryresources to open up primary resources for non-EGSM MSs.

The statistics impacted are shown in Table 19-2.

Table 19-2 Impact due to increased handovers

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

GSR6 Extended GSM (EGSM)

14 Feb 2003


68P02901W56-L 19–7

Example 3: Impact due to congestion


S A network has mostly non-EGSM MSs accessing the system. Although extendedresources are available, they are used infrequently.

S Primary resources are completely used up by non-EGSM MSs.

The cell experiences congestion when other non-EGSM MSs try to access the cell,despite the fact that not all of the resources have been allocated.

The statistics impacted are shown Table 19-3.

Table 19-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

NOTE TCH_CONGESTION is lower because it is pegged when allTCHs are busy, not just the primary band TCHs, even thoughcongestion exists for the primary MSs in this example.

GSR6Approximate equality

14 Feb 200319–8


68P02901W56-L

Approximate equality

Description of Approximate equality

Statistics are kept by processes at the BTS and BSC. When comparing statistics, minordiscrepancies between different statistics may occur because when the statistic intervalexpires, a procedure may be in progress and not all statistics related to that procedurehave been pegged. These statistics are pegged in the following interval upon completionof the procedure.

Example

Figure 19-1 is an example of approximate equality.

Figure 19-1 Approximate equality procedure

9:00

TCH Assignment Successful Procedure

9:30 10:00

MA_REQ_FROM_MSC

MA_CMD_TO_MS

TOTAL_CALLS

MA_COMPLETE_TO_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 nocorresponding MA_CMD_TO_MS and TOTAL_CALLS values. Also, the 9:30 to 10:00interval shows the statistics MA_CMD_TO_MS, TOTAL_CALLS, andMA_COMPLETE_TO_MSC incremented with no corresponding MA_REQ_FROM_MSCvalue.

GSR6 Phantom RACHs

14 Feb 2003


68P02901W56-L 19–9

Phantom RACHs

Description of Phantom RACHs

Phantom RACHs occur primarily as the result of sporadic noise and interference.Channel requests from distant MSs can be affected by such noise when MS poweroutput is low. If an MS output is high, any transmitted signals can cause interference toother co-channel and adjacent channel cells. It is unlikely in a Motorola implementationthat cells using similar frequencies will be finely synchronized. This could happen bychance 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 19-2 provides a graphic illustration of phantom RACHs.

Figure 19-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 messagecounter)

ALLOC_SDCCH

(CHAN_REQ_MS_FAIL)

(INV_EST_CAUSE_ON_RACH

GSR6Phantom RACHs

14 Feb 200319–10


68P02901W56-L

Process of Phantom RACHs occurrences

The following process describes the chain of events that take place when a phantomRACH occurs:

1. The channel coder decodes the message on the Random Access Channel fromthe radio. If the channel coder cannot decode the message because a field isunrecognizable, the channel coder pegs an internal counter for the unrecognizedmessage.

If the channel coder decodes the message, the channel coder forwards thechannel request to RSS Layer 1 and included in the message is the peg count ofunrecognized messages.

2. RSS layer 1 pegs the OK_ACC_PROC_SUC_RACH statistic once for the channelrequest and pegs the ACCESS_PER_RACH statistic once for the channel requestplus the peg count sent by the Channel Coder. RSS layer 1 does no filtering of theRACH.

3. RSS Abis receives the channel request and verifies the one-byte message fromthe MS. It verifies that the three most significant bits represent a validestablishment cause (see GSM4.08, 3.11.0, section 9.1.8 for the valid causes forPhase 1). If the three bits are verified, the RSS Abis sends a channel request toCall Processing. If the three bits are not valid, the RSS Abis pegs theINV_EST_CAUSE_ON_RACH statistic.

NOTE The other five bits of the eight-bit message are an unformattedfive-bit field, 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 tothe Immediate Assignment, that is, no MS ever existed for the RACH or the MS isfar away, 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).

GSR6 Phantom RACHs

14 Feb 2003


68P02901W56-L 19–11

Raw statistics affected

The following statistics may be affected by phantom RACHs:

S ACCESS_PER_RACH.

S ACCESS_PER_AGCH.

S ALLOC_SDCCH.

S ALLOC_SDCCH_FAIL.

S OK_ACC_PROC_SUC_RACH.

S CHAN_REQ_MS_BLK.

S CHAN_REQ_MS_FAIL.

S SDCCH_CONGESTION.

S BUSY_SDCCH.

S BER (SDCCH affected but not TCH).

ACCESS_PER_RACH is pegged for each phantom RACH. The remainder of the abovestatistics are affected depending on whether or not the apparent channel request fromthe MS is known to Call Processing (Layer 3). RSS (Layer 2) filters out RACHs that areinvalid. Specifically, Channel Request messages received via the RACH that have invalid(reserved) values in the establishment cause field (reference GSM 04.08) are filtered bythe RSS. Therefore, a lot of phantom RACHs never make it up to the Call Processingprocesses because of the gating (filtering) function performed by the RSS.

GSR6Questions and answers

14 Feb 200319–12


68P02901W56-L

Questions and answers

Assignment failureQ: What happens after an ASSIGNMENT FAILURE from the MS?

A: If an Assignment Failure is received from the MS during call set-up, the AssignmentFailure is forwarded to the MSC and the MSC (at its discretion) clears the call. If theAssignment Failure is received during a BSS-controlled intra-cell handover, the callreverts 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 thecall. Whether or not the Assignment Command is retried is up to the MSC. If theAssignment Failure is received during intra-cell handover, the call reverts back to the oldchannel and could send another Assignment Command to the MS if the BSS chooses todo another intra-cell handover.

Counters and SDCCH reconfigurationQ: Will the following counters work correctly after an SDCCH reconfiguration? That iswhen a TCH is used as an SDCCH:

S ALLOC_SDCCH.

S ALLOC_SDCCH_FAIL.

S BUSY_SDCCH.

S BUSY_TCH.

S RF_LOSSES_SD.

S RF_LOSSES_TCH.

S SDCCH_CONGESTION.

S TCH_CONGESTION.

S TCH_USAGE.

A: For example, SDCCH congestion timer gets started when there are no free SDCCHsavailable at the cell. If a TCH gets reconfigured to eight SDCCHs, the congestion timerstops because the cell is no longer congested as far as SDCCHs are concerned. Thestatistics reflect the current status of the system. The reconfiguration issue should notaffect the accuracy of the statistics.

Dynamic SDCCH configurationQ: If configuration of SDCCHs, for example, can occur manually or more importantlyoccur dynamically during a busy period, would the previous peg information for that halfhour period be lost, and would this affect key statistic results?

A: No, CHAN_REQ_MS_FAIL (the statistic which is pegged per channel) is not deletedwhen the channel is configured or reconfigured. The process pegging creates thestatistic for all possible SDs. This statistic is never deleted, so that the statistic for eachhalf hour shows the amount of pegs for the channel for the entire half hour.

Established call lossQ: Is failed handover and RF_LOSSES_TCH the only possible reason for losing anestablished call?

A: A call could also be lost because of other procedure failures, like ciphering and ModeModify.

GSR6 Questions and answers

14 Feb 2003


68P02901W56-L 19–13

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 anSDCCH?

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 itwill not 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? WillCLR_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.

GSR6Questions and answers

14 Feb 200319–14


68P02901W56-L

14 Feb 2003


68P02901W56-L I–1

Index

GSR6

14 Feb 2003 I–2


68P02901W56-L

GSR6

14 Feb 2003


68P02901W56-L I–3

AACCESS_PER_AGCH, 4–8

ACCESS_PER_PCH, 4–9

ACCESS_PER_RACH, 4–10

Accessibility statistics, 12–4, 18–53

ADJ_CHAN_INTF, 4–73

AIR_DL_CONTROL_BLKS, 12–6

AIR_DL_DATA_BLKS, 12–7

AIR_INTERFACE_BW_CS1, 17–7




AIR_INTERFACE_PAGING, 17–11

AIR_UL_CONTROL_BLKS, 12–8

AIR_UL_DATA_BLKS, 12–9

ALLOC_SDCCH, 4–11

ALLOC_SDCCH_CARR, 6–4

ALLOC_SDCCH_FAIL, 4–12

ALLOC_TCH, 4–13

ALLOC_TCH_CARR, 6–5

ALLOC_TCH_FAIL, 4–14

approximate equality, 19–8

assignment to TCHassignment successful, 18–13fail recovered, 18–15immediate assignment failure, 18–14TCH assignment blocked, 18–14

ASSIGNMENT_REDIRECTION, 4–15

ASSIGNMENT_RESOURCE, 4–95

ASSIGNMENT_SUCCESS_RATE, 17–12

ATER_PREEMPT_STATUS, 11–4

ATER_STATUS, 11–6

ATTEMPT_IMMED_ASSIGN_PROC, 16–6

AVAILABLE_PDTCH, 12–10

AVAILABLE_SDCCH, 4–16

AVAILABLE_TCH, 4–17

Average call duration, 15–4

BBAD_HO_REFNUM_MS, 4–18

Band reassignment, introductionfail recovered, 18–42handover successful, 18–41handover unsuccessful, 18–42

BAND_HANDOVER, 4–73

BAND_RE_ASSIGN, 4–73

BER, 6–6

Bin ranges, 2–16

BSC, functions, 18–4

BSS, functions, 18–4

BSSLAP_ABORT_RCV, 9–16

BSSLAP_ABORT_SENT, 9–15

BSSLAP_MS_POS_CMD, 9–17

BSSLAP_MS_POS_RESP, 9–18

BSSLAP_REJ, 9–13

BSSLAP_RESET, 9–14

BSSLAP_TA_REQ, 9–10

BSSLAP_TA_RESP, 9–11

BSSLAP_TOA_REQ, 9–12

BSSMAP_CONLESS_INFO_RCV, 9–19

BSSMAP_CONLESS_INFO_SENT, 9–20

BSSMAP_PERF_LOC_ABORT_MSGS, 9–5

BSSMAP_PERF_LOC_REQ_MSGS, 9–4

BSSMAP_PERF_LOC_RESP_MSGS, 9–6, 9–7

BSSMAPLE_CONLESS_INFO_RCV, 9–21

BSSMAPLE_CONLESS_INFO_SENT, 9–22

BSSMAPLE_PERF_LOC_ABORT_MSGS, 9–8

BSSMAPLE_PERF_LOC_RESP_MSGS, 9–9

BUSY_CICS, 10–5

BUSY_SDCCH, 4–19

BUSY_TCH, 4–20

BUSY_TCH_CARR, 4–22

Ccall clearing

cipher mode fail, 18–28queueing timeout, 18–29RF loss on a TCH, 18–29RF loss on an SDCCH, 18–28

GSR6

14 Feb 2003 I–4


68P02901W56-L

Call model statistics, 15–3CALL_DURATION, 15–4CALL_SETUP_BLOCKING_RATE, 15–5HANDOVERS_PER_CALL (H), 15–6IMSI_DETACHES_TO_CALL (Id), 15–7INTRA_BSS_HO_TO_ALL_HO (i), 15–8LOCATION_UPDATE_FACTOR (L), 15–9LOCATION_UPDATES_TO_CALLS (I), 15–10PAGES_PER_CALL (PPC), 15–11PAGES_PER_SECOND, 15–12PAGING_RATE (P), 15–13SMS_TO_CALL_RATIO (S), 15–14

call procedurebids, 18–6bids–attempt–fail–recovered, 18–6bids–attempt–failures, 18–6bids–attempts, 18–6bids–attempts–successes, 18–6bids–bids blocked, 18–6

call setup and handover matrix, 18–7

CALL_DURATION, 15–4

CALL_SETUP_BLOCKING_RATE, 15–5

CALL_SETUP_SUCCESS_RATE, 17–13

CALL_SP_VERS_REQUEST_MONITOR, 4–23

call statistics, MS_TCH_USAGE_BY_TYPE_PCS,4–64

CALL_SUCCESS_RATE, 17–14

CALL_VOLUME, 17–15

CALLS_QUEUED, 4–24

cell statistics, introduction, 4–3

CELL_FLUSH_REQS, 12–11

CELL_TCH_ALLOCATIONS, 16–8

CELL_TCH_ASSIGNMENTS, 16–9

CELL_UPDATE, 17–16

CHAN_DL_TX_PWR_LVL, 6–7

CHAN_REQ_CAUSE_ATMPT, 4–25, 9–3

CHAN_REQ_MS_BLK, 4–26

CHAN_REQ_MS_FAIL, 4–27, 6–8

CHAN_UL_TX_PWR_LVL, 6–9

CHANNEL_REQS_REC, 12–12

CHANNEL_REQS_REJ, 12–13

CHANNEL_REQS_SUCCESS, 12–14

chg_stat_prop, 2–15

chg_stat_prop command, 2–13

CIPHER_MODE_FAIL, 4–28

CLASSMK_UPDATE_FAIL, 4–29

CLR_CMD_FROM_MSC, 4–30

CLR_REQ_TO_MSC, 4–31

cm_lcs_request, 4–70

CM_REESTABLISH, 4–70

CM_SERV_REQ_CALL, 4–70

CM_SERV_REQ_EMERG, 4–70

CM_SERV_REQ_SMS, 4–70

CM_SERV_REQ_SUPP, 4–70

CODING_SCHEME_CHANGE, 12–15

CONGEST_EXIST_HO_ATMPT, 4–33

CONGEST_STAND_HO_ATMPT, 4–34

CONGESTION, 4–73

Congestion relief, intra–BSS, 18–31

CONGESTION_LOST_MSU, 10–6

CONN_REFUSED, 4–35

CONN_REQ_TO_MSC, 4–36

connection establishment, 18–9failure, 18–10immediate assignment blocked, 18–11immediate assignment failure, 18–11successful

mobile originated, 18–9mobile terminated call, 18–12

Counter array statistics, 1–7Counter array bins, 1–7Interval expiry, 1–7Maximum values, 1–7

Counter statistics, 1–6, 2–13Interval expiry, 1–6Maximum value, 1–6Threshold event reporting, 1–6

CPU_USAGE, 7–4

CS1_USAGE_DL, 17–17

CS1_USAGE_UL, 17–18

CS12_ON_32K_CHAN, 12–16







Custom statistics, 1–4

Ddefault values, 2–4

GSR6

14 Feb 2003


68P02901W56-L I–5

Directed retry, intra–BSS, 18–32

disabling a statistic, 2–5

disp_interval command, 2–12

disp_stat_prop command, 2–17

disp_stats command, 2–8

Displaying a gauge statistic, 2–18

Displaying a counter array statistic, 2–19

Displaying a counter statistic, 2–17

Displaying a distribution statistic, 2–18

Displaying a duration statistic, 2–20

Displaying statistic properties, 2–17Displaying a counter array statistic, 2–19Displaying a counter statistic, 2–17Displaying a distribution statistic, 2–18Displaying a duration statistic, 2–20Displaying a gauge statistic, 2–18

Displaying statistic values, 2–8

Displaying the statistics interval, 2–11

Displaying the statistics interval start times, 2–12

DISTANCE, 4–73

Distribution statistics, 1–9

DL_AIR_INTERFACE_BW_CS1, 17–25




DL_BUSY_PDTCH, 12–17

DL_PDTCH_CONGESTION, 12–18

DL_PDTCH_Q_LENGTH, 12–19

DL_PDTCH_SEIZURE, 12–20

DOWNINTERF, 4–73

DOWNLEVEL, 4–73

DOWNLINK_TRAFFIC_VOLUME, 17–29

DOWNQUAL, 4–73

DROP_CALL_RATE, 17–30

Duration statistics, 1–8Interval expiry, 1–8Maximum value, 1–8Period counter and mean value, 1–8Total duration, 1–8Wraparound to next day, 1–8

Dynamic allocation statistics, 12–5

DYNET_ASSIGN_FAIL, 4–37

DYNET_CALL_REJECTS, 4–38

EEFR_REQ_FROM_MSC, 3–4

EGSM (extended GSM), 19–4

enabling a statistic, 2–4

ER_INTRA_CELL_HO_ATMPT, 4–39

ER_INTRA_CELL_HO_SUC, 4–40

Ffeature

3635, 12–4, 12–16, 12–29, 12–30, 12–313725, 12–4, 12–52, 12–533750, 4–9, 4–16, 4–17, 4–80, 4–81, 4–82, 12–4,

12–5, 12–10, 12–11, 12–14, 12–15, 12–17,12–18, 12–19, 12–20, 12–35, 12–41, 12–42,12–43, 12–44, 12–45, 12–46, 12–47, 12–56,12–57, 12–58, 12–59

3938, 4–233969, 12–4, 12–5, 12–18, 12–19, 12–33, 12–34,

12–40, 12–57, 12–583974, 4–25, 4–70, 8–3, 8–5, 8–6, 8–7, 8–8, 8–9,

8–10, 8–11, 8–12, 8–13, 8–14, 8–15, 8–16,8–17, 8–18, 8–19, 8–20, 8–21, 8–22, 8–23,8–24, 8–25, 8–26, 8–27, 8–28, 8–29, 8–30,8–31, 8–32, 8–33, 8–34, 8–35, 8–36, 8–37, 9–3,9–4, 9–5, 9–6, 9–7, 9–8, 9–9, 9–10, 9–11, 9–12,9–13, 9–14, 9–15, 9–16, 9–17, 9–18, 9–19,9–20, 9–21, 9–22, 13–3, 13–4, 13–5, 13–6,13–7, 13–8, 13–9, 13–10, 13–11, 13–12

4253, 12–5, 12–6, 12–8, 12–544386, 12–4, 12–5, 12–14, 12–59references, 4tag format, 4

FER, 6–10

Flow control, description, 18–33

FLOW_CONTROL_BARRED, 4–41

FRMR, 11–8

GGauge statistics, 1–7

Interval expiry, 1–7Threshold event reporting, 1–7

Gb interface, 12–3Gb link, 12–3

GBL statistics, 12–3, 18–48

GBL_AVAILABILITY, 17–31

GBL_DL_DATA_THRPUT, 12–21

GBL_DL_DATA_THRPUT_HIST, 12–22

GSR6

14 Feb 2003 I–6


68P02901W56-L

GBL_FLOW_CTRL_SENT, 12–23

GBL_FLUSH_REQS, see CELL_FLUSH_REQS,12–11

GBL_LINK_INS, 12–24

GBL_PAGING_REQS, 12–25

GBL_UL_DATA_THRPUT, 12–26

GBL_UL_DATA_THRPUT_HIST, 12–27

GBL_UNAVAILABLE, 12–28

GPRS performance, 17–4

GPRS_32K_CHANNELS_SWITCHED, 12–29

GPRS_32K_DL_NOT_AVAIL, 12–30

GPRS_32K_UL_NOT_AVAIL, 12–31

GPRS_ACCESS_PER_AGCH, 12–32

GPRS_ACCESS_PER_RACH, 12–35

GPRS_BW_USAGE_DL, 17–32

GPRS_BW_USAGE_UL, 17–33

GPRS_CELL_RESELECT_ATTMPT, 12–33

GPRS_CELL_RESELECT_FAIL, 12–34

GPRS_CHANNELS_SWITCHED, 12–36

GPRS_DL_ACT_TS, 17–34

GPRS_DL_BANDWIDTH_EFFICIENCY, 17–36

GPRS_DYNET_FAILURES, 12–37

GPRS_DYNET_RES_REQS, 12–38

GPRS_DYNET_SWI_REQS, 12–39

GPRS_MS_NEIGHBOR_STRONG, 12–40

GPRS_PCH_AGCH_Q_LENGTH, 12–41

GPRS_UL_ACT_TS, 17–35

GPRS_UL_BANDWIDTH_EFFICIENCY, 17–37

Hhandover, 18–4

handover performance, 17–5

Handover successful, band reassignment,introduction, 18–41

HANDOVER_FAILURE_RATE, 16–10

HANDOVER_SUCCESS_RATE, 16–11

Handovers, ratio per call, 15–6

HANDOVERS_PER_CALL, 15–6

health check, 17–5

HO_FAIL_NO_RESOURCES, 4–42

HO_PER_CALL, 17–38

HO_REQ, 4–95

HO_REQ_MSC_FAIL, 4–43

HO_REQ_MSC_OK, 4–44

HO_REQ_MSC_PROTO, 3–5

II_FRAMES_RX, 11–9

I_FRAMES_TX, 11–10

IDLE_PDTCH_INTF_BAND0, 12–42





IDLE_TCH_INTF_BAND0, 4–45





IMM_ASSGN_CAUSE, 12–47

IMSI detaches, ratio per call, 15–7

IMSI_DETACH, 4–70

IMSI_DETACHES_TO_CALL, 15–7

IN_INTER_BSS_EQUIP_FAIL, 4–50

IN_INTER_BSS_HO, 4–50

IN_INTER_BSS_HO_CLEARED, 4–50

IN_INTER_BSS_HO_SEIZE, 4–50

IN_INTER_BSS_HO_SUC, 4–50

IN_INTER_CELL_HO_TO_IN_ZONE, 4–101, 4–102

IN_INTRA_BSS_EQUIP_FAIL, 4–51

IN_INTRA_BSS_HO, 4–51

IN_INTRA_BSS_HO_CLEARED, 4–51

IN_INTRA_BSS_HO_LOSTMS, 4–51

IN_INTRA_BSS_HO_RETURN, 4–51

IN_INTRA_BSS_HO_SUC, 4–51

IN_INTRA_BSS_NC_ATMPT, 5–9

IN_INTRA_BSS_NC_SUC, 5–10

INCOMING_HO_VOLUME, 17–39

INNER_TO_OUTER_ZONE, 4–101, 4–102

inter–BSS handoverfail lost, 18–21fail lost mobile, 18–22fail recovered, 18–20handover blocked, 18–19handover successful, 18–18standard directed retry, external, 18–23

GSR6

14 Feb 2003


68P02901W56-L I–7

Interband activityinter–BSS

handover successful, 18–37handover unsuccessful, 18–38fail recovered, 18–38invalid frequency supported, 18–39

intra–BSSfail recovered, 18–35handover successful, 18–34handover unsuccessful, 18–35unsuccessful , invalid frequency supported,

18–36

Interband assignment, invalid frequency, 18–40

INTERBAND_ACTIVITY, 4–52

INTERNAL_LOST, 17–40

INTERNAL_RECOVERED, 17–41

INTERNAL_SUCCESS, 17–42

INTF_ON_IDLE, 6–11

Intra–BSScongestion relief, 18–31directed retry, 18–32

intra–BSS handoverfail–lost, 18–26fail–recovered, 18–25handover blocked, 18–25handover successful, 18–24standard directed retry, internal, 18–27

Intra–BSS handovers, 15–8

intra–cell handoverfail lost, 18–17fail recovered, 18–17handover blocked, 18–16handover successful, 18–16

INTRA_BSS_HO_CAUSE_SUC, 3–6

INTRA_BSS_HO_TO_ALL_HO, 15–8

INTRA_CELL_EQUIP_FAIL, 4–53

INTRA_CELL_HO, 4–53

INTRA_CELL_HO_ATMPT, 4–53

INTRA_CELL_HO_CLEARED, 4–53

INTRA_CELL_HO_FAIL_LOST_MS, 17–43

INTRA_CELL_HO_FAIL_RECOVERED, 17–44

INTRA_CELL_HO_LOSTMS, 4–53

INTRA_CELL_HO_REQ, 4–53

INTRA_CELL_HO_RETURN, 4–53

INTRA_CELL_HO_SUC, 4–53

INTRA_CELL_HO_SUCCESS_RATE, 17–45

INTRA_ZONE, 4–101, 4–102

INV_EST_CAUSE_ON_RACH, 4–55

INVALID_FRAMES_RX, 11–11

Kkey statistics, 1–4, 16–3, 16–4, 16–5

ATTEMPT_IMMED_ASSIGN_PROC, 16–6call summary, 16–3CELL_TCH_ALLOCATIONS, 16–8CELL_TCH_ASSIGNMENTS, 16–9channel usage, 16–3connection establishment, 16–4HANDOVER_FAILURE_RATE, 16–10HANDOVER_SUCCESS_RATE, 16–11loss summary, 16–4MEAN_ARRIVAL_TIME_BETWEEN_CALLS,

16–12MEAN_INTER_ARRIVAL_TIME, 16–13MEAN_TCH_BUSY_TIME, 16–14MTL_UTILISATION_RX, 16–15MTL_UTILISATION_TX, 16–16RF_LOSS_RATE, 16–17SDCCH_BLOCKING_RATE, 16–18SDCCH_MEAN_ARRIVAL_RATE, 16–19SDCCH_MEAN_HOLDING_TIME, 16–20SDCCH_RF_LOSS_RATE, 16–21SDCCH_TRAFFIC_CARRIED, 16–22SUCCESS_IMMED_ASSIGN_PROC, 16–23SUCCESS_INTERNAL_HO, 16–24TCH_BLOCKING_RATE, 16–25TCH_MEAN_ARRIVAL_RATE, 16–26TCH_MEAN_HOLDING_TIME, 16–27TCH_RF_LOSS_RATE, 16–28TCH_TRAFFIC_CARRIED, 16–29template, 16–5TOTAL_CALLS_KEY, 16–31UNSUCCESS_INTERNAL_HO_NOREEST,

16–32UNSUCCESS_INTERNAL_HO_REEST, 16–33

LL_ROUTING_SYNTAX, 13–5

L_ROUTING_UNKNOWN, 13–6

L_SCCP_MSGS, 13–7

L_SCCP_MSGS_RX, 13–8

l_sccp_msgs_rx_0, 13–8

l_sccp_msgs_rx_2, 13–8

L_SCCP_MSGS_TX, 13–9

l_sccp_msgs_tx_0, 13–9

GSR6

14 Feb 2003 I–8


68P02901W56-L

l_sccp_msgs_tx_2, 13–9

L_SIF_SIO_RX_OPC, 13–10

L_SIF_SIO_TX_OPC, 13–11

L_SIF_SIO_TYPE, 13–12

l_sif_sio_type, 13–12

l_sif_sio_type_mtp, 13–12

l_sif_sio_type_test, 13–12

LAPD_CONGESTION, 11–12

LMTP_CHANGEBACK, 8–7

LMTP_CHANGEOVER, 8–8

LMTP_CONGESTION, 8–37

LMTP_LINK_INS, 8–10

LMTP_LINKFAIL, 8–11

LMTP_LOCAL_BUSY, 8–12

LMTP_LOCAL_MGT, 8–13

LMTP_LOCAL_SL_CONGESTION, 8–9

LMTP_MGT_INHIBIT, 8–14

LMTP_MGT_UNINHIBIT, 8–15

LMTP_MSU_DISCARDED, 8–6

LMTP_MSU_RX, 8–16

LMTP_MSU_TX, 8–17

LMTP_NEG_ACKS, 8–18

LMTP_RE_TX, 8–19

LMTP_REMOTE_MGT, 8–20

LMTP_REMOTE_PROC, 8–21

LMTP_RESTORATION, 8–22

LMTP_SIB_RX, 8–35

LMTP_SIB_TX, 8–36

LMTP_SIF_SIO_RX, 8–23

LMTP_SIF_SIO_TX, 8–24

LMTP_SL_ACK, 8–25

LMTP_SL_ALIGNMENT, 8–26

LMTP_SL_CONGESTION, 8–27

LMTP_SL_ERROR_RATE, 8–28

LMTP_SL_FAIL, 8–29

LMTP_SL_FIBR, 8–30

LMTP_START_RPO, 8–31

LMTP_STOP_RPO, 8–32

LMTP_SU_ERROR, 8–33

LMTP_UNAVAILABLE, 8–34

LOC_FLW_ON_REQ_NORM, 4–70

LOC_FLW_ON_REQ_SMS, 4–70

Location updates, ratio per call, 15–10

LOCATION_SERVICES, 4–70

LOCATION_UPDATE, 4–70

LOCATION_UPDATE_FACTOR, 15–9

LOCATION_UPDATES_TO_CALLS, 15–10

MMA_CMD_TO_MS_BLKD, 4–61

MA_COMPLETE_TO_MS, 4–57

MA_COMPLETE_TO_MSC, 4–58

MA_FAIL_FROM_MS, 4–59

MA_REQ_FROM_MSC, 4–60

MA_REQ_FROM_MSC_FAIL, 3–7

MAX_TCH_BUSY, 17–46

MEAN_ARRIVAL_TIME_BETWEEN_CALLS, 16–12

MEAN_INTER_ARRIVAL_TIME, 16–13

MEAN_TCH_BUSY_TIME, 16–14

MEAN_TIME_BETWEEN_HOs, 17–47

MMI BSC/BTS statisticsALLOC_SDCCH_FAIL, 14–3ALLOC_TCH_FAIL, 14–3HO_FAIL_NO_RESOURCES, 14–3HO_REQ_MSC_FAIL, 14–3MA_CMD_TO_MS_BLKD, 14–3RF_LOSSES_TCH, 14–3

MMI PCU statisticCELL_FLUSH_REQS, 14–3CHANNEL_REQS_REJ, 14–3GBL_LINK_INS, 14–3GBL_PAGING_REQS, 14–3GBL_UNAVAILABLE, 14–3

Monitoring faults, 1–14

MS_ACCESS_BY_TYPE, 4–62

MS_CLASS_1_10_REQ, 12–49



MA_CMD_TO_MS, 4–56

MS_TCH_USAGE_BY_TYPE, 4–63

MS_TCH_USAGE_BY_TYPE_PCS, 4–64

MSC functions, 18–4

MSC_OLVD_MSGS_RX, 3–8

GSR6

14 Feb 2003


68P02901W56-L I–9

MSC_PAGING, 17–48

MSU_DISCARDED, 10–7

MT_LCS_ON_SDCCH, 4–65

MTLoperator initiated outage, 18–44transition scenarios, 18–45

MTL_UTILISATION_RX, 16–15

MTL_UTILISATION_TX, 16–16

MTP_CHANGEBACK, 10–8

MTP_CHANGEOVER, 10–9

MTP_CONGESTION, 10–10

MTP_LINK_INS, 10–11

MTP_LINKFAIL, 10–12

MTP_LOCAL_BUSY, 10–13

MTP_LOCAL_MGT, 10–14

MTP_MGT_INHIBIT, 10–15

MTP_MGT_UNINHIBIT, 10–16

MTP_MSU_RX, 10–17

MTP_MSU_TX, 10–18

MTP_NEG_ACKS, 10–19

MTP_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

NN2_EXPIRY, 11–13Network health statistics, 1–4, 17–3

AIR_INTERFACE_BW_CS1, 17–7AIR_INTERFACE_BW_CS2, 17–8AIR_INTERFACE_BW_CS3, 17–9AIR_INTERFACE_BW_CS4, 17–10AIR_INTERFACE_PAGING, 17–11ASSIGNMENT_SUCCESS_RATE, 17–12CALL_SETUP_SUCCESS_RATE, 16–7, 17–13CALL_SUCCESS_RATE, 17–14CALL_VOLUME, 17–15CELL_UPDATE, 17–16CS1_USAGE_DL, 17–17CS1_USAGE_UL, 17–18CS2_USAGE_DL, 17–19CS2_USAGE_UL, 17–20CS3_USAGE_DL, 17–21CS3_USAGE_UL, 17–22CS4_USAGE_DL, 17–23CS4_USAGE_UL, 17–24DL_AIR_INTERFACE_BW_CS1, 17–25DL_AIR_INTERFACE_BW_CS2, 17–26DL_AIR_INTERFACE_BW_CS3, 17–27DL_AIR_INTERFACE_BW_CS4, 17–28DOWNLINK_TRAFFIC_VOLUME, 17–29DROP_CALL_RATE, 17–30GBL_AVAILABILITY, 17–31GPRS performance, 17–4GPRS_BW_USAGE_DL, 17–32

GSR6

14 Feb 2003 I–10


68P02901W56-L

GPRS_BW_USAGE_UL, 17–33GPRS_DL_ACT_TS, 17–34GPRS_DL_BANDWIDTH_EFFICIENCY, 17–36GPRS_UL_ACT_TS, 17–35GPRS_UL_BANDWIDTH_EFFICIENCY, 17–37handover performance, 17–5health check, 17–5HO_PER_CALL, 17–38INCOMING_HO_VOLUME, 17–39INTERNAL_LOST, 17–40INTERNAL_RECOVERED, 17–41INTERNAL_SUCCESS, 17–42INTRA_CELL_HO_FAIL_LOST_MS, 17–43INTRA_CELL_HO_FAIL_RECOVERED, 17–44INTRA_CELL_HO_SUCCESS_RATE, 17–45MAX_TCH_BUSY, 17–46MEAN_TIME_BETWEEN_HOs, 17–47MSC_PAGING, 17–48OUT_INTER_BSS_HO_FAIL_LOST_MS, 17–49OUT_INTER_BSS_HO_FAIL_RECOVERED,

17–50OUT_INTER_BSS_HO_SUCCESS_RATE, 17–51OUT_INTER_CELL_HO_FAIL_LOST_MS, 17–52OUT_INTER_CELL_HO_FAIL_RECOVERED,

17–53OUT_INTER_CELL_HO_SUCCESS_RATE,

17–54OUTGOING_HO_VOLUME, 17–55paging performance, 17–5PAGING_COMPRESSION_RATE, 17–56PAGING_OVERFLOW_RATE, 17–57PAGING_RESPONSE, 17–58PAGING_SUCCESS_RATE, 17–59PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLI

NK, 17–60radio performance reports, 17–6RANKING_FORMULA, 17–61RF_ASSIGN_FAIL_RATE_LOST_MS, 17–62RF_ASSIGN_FAIL_RATE_RECOVERED, 17–63RF_ASSIGNMENT_SUCCESS_RATE, 17–64SDCCH congestion, 17–6SDCCH_ACCESSES, 17–65SDCCH_BLOCKING_RATE, 17–66SDCCH_CONGESTION_TIME, 17–67SDCCH_TRAFFIC_CARRIED, 17–68TCH congestion, 17–6TCH_ACCESSES, 17–69TCH_CONGESTION_TIME, 17–70TCH_RF_LOSS_RATE, 17–71TCH_TRAFFIC_CARRIED, 17–72UL_AIR_INTERFACE_BW_CS1, 17–73UL_AIR_INTERFACE_BW_CS2, 17–74UL_AIR_INTERFACE_BW_CS3, 17–75UL_AIR_INTERFACE_BW_CS4, 17–76UPLINK_PDTCH_BLOCKING_RATE, 17–77UPLINK_TRAFFIC_VOLUME, 17–78

network interface statisticsBSSLAP_ABORT_RCV, 9–16BSSLAP_ABORT_SENT, 9–15BSSLAP_MS_POS_CMD, 9–17BSSLAP_MS_POS_RESP, 9–18BSSLAP_REJ, 9–13BSSLAP_RESET, 9–14BSSLAP_TA_REQ, 9–10BSSLAP_TA_RESP, 9–11BSSLAP_TOA_REQ, 9–12BSSMAP_CONLESS_INFO_RCV, 9–19BSSMAP_CONLESS_INFO_SENT, 9–20BSSMAP_PERF_LOC_ABORT_MSGS, 9–5BSSMAP_PERF_LOC_REQ_MSGS, 9–4BSSMAP_PERF_LOC_RESP_MSGS, 9–6BSSMAPLE_CONLESS_INFO_RCV, 9–21BSSMAPLE_CONLESS_INFO_SENT, 9–22BSSMAPLE_PERF_LOC_ABORT_MSGS, 9–8BSSMAPLE_PERF_LOC_REQ_MSGS, 9–7BSSMAPLE_PERF_LOC_RESP_MSGS, 9–9L_ROUTING_SYNTAX, 13–5L_ROUTING_UNKNOWN, 13–6L_SCCP_MSGS, 13–7L_SCCP_MSGS_RX, 13–8L_SCCP_MSGS_TX, 13–9L_SIF_SIO_RX_OPC, 13–10L_SIF_SIO_TX_OPC, 13–11L_SIF_SIO_TYPE, 13–12LMTP_MSU_DISCARDED, 8–6LMTP_CHANGEBACK, 8–7LMTP_CHANGEOVER, 8–8LMTP_CONGESTION_LOST_MSU, 8–5LMTP_LINK_INS, 8–10LMTP_LINKFAIL, 8–11LMTP_LOCAL_BUSY, 8–12LMTP_LOCAL_MGT, 8–13LMTP_LOCAL_SL_CONGESTION, 8–9LMTP_MGT_INHIBIT, 8–14LMTP_MGT_UNINHIBIT, 8–15LMTP_MSU_RX, 8–16LMTP_MSU_TX, 8–17LMTP_NEG_ACKS, 8–18LMTP_RE_TX, 8–19LMTP_REMOTE_MGT, 8–20LMTP_REMOTE_PROC, 8–21LMTP_RESTORATION, 8–22LMTP_SIF_SIO_RX, 8–23LMTP_SIF_SIO_TX, 8–24LMTP_SL_ACK, 8–25LMTP_SL_ALIGNMENT, 8–26LMTP_SL_CONGESTION, 8–27LMTP_SL_ERROR_RATE, 8–28LMTP_SL_FAIL, 8–29LMTP_SL_FIBR, 8–30LMTP_START_RPO, 8–31LMTP_STOP_RPO, 8–32

GSR6

14 Feb 2003


68P02901W56-L I–11

LMTP_SU_ERROR, 8–33LMTP_UNAVAILABLE, 8–34

NO_PDTCH_AVAIL, 12–52

NO_PDTCH_AVAIL_TIME, 12–53

Normal distribution statistics, 1–9Bins, 1–9Histogram, 1–9Interval expiry, 1–9Mean value, 1–9

NUM_EMERG_ACCESS, 4–66

NUM_EMERG_REJECTED, 4–67

NUM_EMERG_TCH_KILL, 4–68

NUM_EMERG_TERM_SDCCH, 4–69

OOK_ACC_PROC, 4–70, 9–3

OK_ACC_PROC_SUC_RACH, 4–72

OUT_HO_CAUSE_ATMPT, 4–73

OUT_HO_NC_CAUSE_ATMPT, 5–11

OUT_HO_NC_SUC, 5–13

OUT_INTER_BSS_EQUIP_FAIL, 4–75

OUT_INTER_BSS_HO, 4–75

OUT_INTER_BSS_HO_ATMPT, 4–75

OUT_INTER_BSS_HO_CLEARED, 4–75

OUT_INTER_BSS_HO_FAIL_LOST_MS, 17–49

OUT_INTER_BSS_HO_FAIL_RECOVERED, 17–50

OUT_INTER_BSS_HO_LOSTMS, 4–75

OUT_INTER_BSS_HO_RETURN, 4–75

OUT_INTER_BSS_HO_SUC, 4–75

OUT_INTER_BSS_HO_SUCCESS_RATE, 17–51

OUT_INTER_BSS_REQ_TO_MSC, 4–75

OUT_INTER_CELL_FAIL_LOST_MS, 17–52

OUT_INTER_CELL_HO_FAIL_RECOVERED, 17–53

OUT_INTER_CELL_HO_SUCCESS_RATE, 17–54

OUT_INTRA_BSS_EQUIP_FAIL, 4–77

OUT_INTRA_BSS_HO, 4–77

OUT_INTRA_BSS_HO_ATMPT, 4–77

OUT_INTRA_BSS_HO_CLEARED, 4–77

OUT_INTRA_BSS_HO_LOSTMS, 4–77

OUT_INTRA_BSS_HO_PRI_BLK, 4–77

OUT_INTRA_BSS_HO_REQ, 4–77

OUT_INTRA_BSS_HO_RETURN, 4–77

OUT_INTRA_BSS_HO_SUC, 4–77

OUTER_TO_INNER_ZONE, 4–101, 4–102

OUTGOING_HO_VOLUME, 17–55

PPAGE_REQ_FROM_MSC, 4–79

PAGE_REQ_FROM_MSC_FAIL, 3–9

PAGE_REQ_FROM_SMLC_FAIL, 13–4

PAGE_RESPONSE, 4–70

PAGES_PER_CALL, 15–11

PAGES_PER_SECOND, 15–12

paging performance, 17–5

PAGING_COMPRESSION_RATE, 17–56

PAGING_OVERFLOW_RATE, 17–57

PAGING_RATE, 15–13

PAGING_REQS_CS, 4–80

PAGING_REQS_PS, 4–80

PAGING_REQS_TOT, 4–80

PAGING_REQUESTS, 4–80

PAGING_RESPONSE, 17–58

PAGING_SUCCESS_RATE, 17–59

PATH_BALANCE, 6–13

PCH_AGCH_Q_LENGTH, 4–81

PCH_Q_PAGE_DISCARD, 4–82

PCU statistics, 12–3

PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK,17–60

phantom RACHs, 4–55, 19–9raw statistics affected, 19–11

POWERBDGT, 4–73

PRP_LOAD, 12–54

QQuality of Service (QoS), 12–7, 12–9, 17–17, 17–18,

17–19, 17–20, 17–21, 17–22, 17–23, 17–24,17–29, 17–78

Questions and answers, 19–12

Rradio performance reports, 17–6

RF_ASSIGNMENT_SUCCESS_RATE, 17–64

GSR6

14 Feb 2003 I–12


68P02901W56-L

RANKING_FORMULA, 17–61

Raw statistics, 1–3

RBER, 6–15

RF_ASSIGN_FAIL_RATE_LOST_MS, 17–62

RF_ASSIGN_FAIL_RATE_RECOVERED, 17–63

RF_ASSIGNMENT_SUCCESS_RATE, 17–64

RF_LOSS_RATE, 16–17

RF_LOSSES_SD, 4–83

RF_LOSSES_TCH, 4–84, 6–16

ROC, 6–17

ROUTING_SYNTAX, 3–10

ROUTING_UNKNOWN, 3–11

RSL , link scenarios, 18–43

SSABM_TX, 11–14

SCCP_MSGS, 3–12

SCCP_MSGS_RX, 3–13

SCCP_MSGS_TX, 3–14

SDCCH congestion, 17–6

SDCCH_ACCESSES, 17–65

SDCCH_BLOCKING_RATE, 16–18, 17–66

SDCCH_CONGESTION, 4–85

SDCCH_CONGESTION_TIME, 17–67

SDCCH_MEAN_ARRIVAL_RATE, 16–19

SDCCH_MEAN_HOLDING_TIME, 16–20

SDCCH_RF_LOSS_RATE, 16–21

SDCCH_TRAFFIC_CARRIED, 16–22, 17–68

SECOND_ASSIGN_ATMPT, 4–86

SECOND_ASSIGN_SUC, 4–87

Setting a statistic interval, 2–10

Setting a threshold, 2–13counter statistics, 2–13

Setting statistic properties, 2–13Setting a threshold, 2–13

short message servicemobile originated, 18–30mobile terminated, 18–30

SIB_RX, 10–36

SIB_TX, 10–37

SIF_SIO_RX_OPC, 3–15

SIF_SIO_TX_OPC, 3–16

SIF_SIO_TYPE, 3–17

SL_CONGESTION, 10–38

SL_STOP_CONGESTION, 10–39

SMS, ratio per call, 15–14

SMS_INIT_ON_SDCCH, 4–88

SMS_INIT_ON_TCH, 4–89

SMS_NO_BCAST_MSG, 4–90

SMS_TO_CALL_RATIO, 15–14

stat_interval command, 2–10, 2–11

stat_mode command, 2–4

SUCCESS_IMMED_ASSIGN_PROC, 16–23

SUCCESS_INTERNAL_HO, 16–24

TTCH congestion, 17–6

TCH_ACCESSES, 17–69

TCH_ASSIGN_TO_INNER_ZONE, 4–101, 4–102

TCH_BLOCKING_RATE, 16–25

TCH_CONG_INNER_ZONE, 4–92

TCH_CONGESTION, 4–91

TCH_CONGESTION_TIME, 17–70

TCH_DELAY, 4–93

TCH_MEAN_ARRIVAL_RATE, 16–26

TCH_MEAN_HOLDING_TIME, 16–27

TCH_Q_LENGTH, 4–94

TCH_Q_REMOVED, 4–95

TCH_RF_LOSS_RATE, 16–28, 17–71

TCH_TRAFFIC_CARRIED, 16–29, 17–72

TCH_USAGE, 4–96

TCH_USAGE_EXT_RANGE, 4–98

TCH_USAGE_INNER_ZONE, 4–99

Throughput statistics, 12–5, 18–58

TOTAL_CALLS, 4–100

TOTAL_CALLS_KEY, 16–31

UU_BER, 6–18

UL_AIR_INTERFACE_BW_CS1, 17–73


GSR6

14 Feb 2003


68P02901W56-L I–13



UL_BUSY_PDTCH, 12–56

UL_PDTCH_CONGESTION, 12–57

UL_PDTCH_Q_LENGTH, 12–58

UL_PDTCH_SEIZURE, 12–59

UNSUCCESS_INTERNAL_HO_NOREEST, 16–32

UNSUCCESS_INTERNAL_HO_REEST, 16–33

UPINTERF, 4–73

UPLEVEL, 4–73

UPLINK_PATH_LOSS, 6–19

UPLINK_PDTCH_BLOCKING_RATE, 17–77

UPLINK_TRAFFIC_VOLUME, 17–78

UPQUAL, 4–73

WWeighted distribution statistics, 1–10

Bins, 1–10Histogram, 1–10Interval expiry, 1–10Mean value, 1–10Wraparound to next day, 1–10

ZZONE_CHANGE_ATMPT, 4–101

ZONE_CHANGE_SUC, 4–102

GSR6

14 Feb 2003 I–14


68P02901W56-L

Documents

68p02901w56-L-uk GSM Statistics Application