alcatel counters

Alcatel-Lucent GSM

PM Counters

OMC Document

Reference Guide

Release B10

3BK 21255 AAAA PCZZA Ed.07

Status RELEASED

Short title PM Counters

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 1256 3BK 21255 AAAA PCZZA Ed.07

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 BSC-TYPE 1 - Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571.4 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

2 BSC-TYPE 2 - Resource availability measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792.1 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3 BSC-TYPE 3 - Resource usage on CCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.1 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

4 BSC-TYPE 4 - Resource usage on SDCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . 1034.1 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5 BSC-TYPE 5 - Resource usage on TCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.1 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

6 BSC-TYPE 6 - TCH handover measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

7 BSC-TYPE 7 - LapD measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

7.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

8 BSC-TYPE 8 - X25 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1848.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

9 BSC-TYPE 9 - N7 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

9.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1909.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

10 BSC-TYPE 18 - A interface measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21310.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21410.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

11 BSC-TYPE 19 - SMS PP measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

11.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

12 BSC-TYPE 25 - SCCP measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24512.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24612.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

13 BSC-TYPE 26 - TCH outgoing handover per adjacency measurements . . . . . . . . . . . . . . . . . . . . . 25713.1 Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

14 BSC-TYPE 27 - 2G TCH incoming handover per adjacency measurements . . . . . . . . . . . . . . . . . 26714.1 Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

15 BSC-TYPE 28 - SDCCH handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

15.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

16 BSC-TYPE 29 - Directed retry measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32316.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

3BK 21255 AAAA PCZZA Ed.07 3 / 1256

Contents

17 BSC-TYPE 30 - SMS CB measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34917.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35017.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

18 BSC-TYPE 31 - Radio Measurement Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35518.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35618.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

19 BSC-TYPE 32 - Change of frequency band measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41119.1 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

20 BSC-TYPE 33 - Electro-Magnetic Emission counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42120.1 Electro-Magnetic Emission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

21 BSC-TYPE 34 - Voice Group Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42521.1 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42621.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42821.3 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43721.4 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

22 BSC-TYPE 110 - Overview measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44722.1 – . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44822.2 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45722.3 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54222.4 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61422.5 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

23 BSC-TYPE 180 - 2G Traffic flow measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70323.1 Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704

24 MFS-GPRS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

24.1 Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70824.2 Resource availability and usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90924.3 Traffic load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079

25 MFS-LCS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121725.1 Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121825.2 Traffic load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240

4 / 1256 3BK 21255 AAAA PCZZA Ed.07

Preface

Preface

Purpose The PM Counters include description of:

GSM Counters

GPRS Counters

LCS Counters.

What’s New In Edition 07This document was generated from the BSC Counters database edition 09rland from the MFS Counters database edition 06rl.In Edition 06This document was generated from the BSC Counters database edition 08rland from the MFS Counters database edition 05rl.In Edition 05This document was generated from the BSC Counters database edition 08rland from the MFS Counters database edition 02rl.In Edition 04This document was generated from the BSC Counters database edition 07rland from the MFS Counters database edition 02rl.In Edition 03This document was generated from the BSC Counters database edition 04rland from the MFS Counters database edition 02rl.In Edition 02This document was generated from the BSC Counters database edition 03rland from the MFS Counters database edition 02rl.

In Edition 01First official release of document.

This document was generated from the BSC Counters database edition 02rland from the MFS Counters database edition 02rl.

3BK 21255 AAAA PCZZA Ed.07 5 / 1256

Preface

Audience This manual is designed for Operations & Maintenance Center-Radio (OMC-R)users, O&M technicians and system designers.

Assumed Knowledge Not applicable.

6 / 1256 3BK 21255 AAAA PCZZA Ed.07

1 BSC-TYPE 1 - Traffic measurements


3BK 21255 AAAA PCZZA Ed.07 7 / 1256


1.1 Handover

1.1.1 TCH

1.1.1.1 Outgoing

1.1.1.1.1 –

1.1.1.1.1.1 C710 - NB_TCH_OUT_HO_REQ_TRX

Long Name NB_TCH_OUT_HO_REQ_TRX

Definition Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercelland external handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC710 = C710

Trigger condition 1) Intracell HO: Whenever the BSC process responsible for the handoverprocedure starts an intra cell TCH handover procedure.2) Internal intercell HO:Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell TCH handover.3)External HO: Whenever a 48.008 HANDOVER REQUIRED message is sent onA interface to the MSC. If more than one 48.008 HANDOVER REQUIRED issent in the frame of the same Handover procedure, the counter is incrementedonly once.48.008 HANDOVER REQUIRED is sent in following situations:1) Anexternal handover alarm has been raised, with corresponding list of candidatecells.2) The list of candidate cells for the current alarm has been updated.Note:This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH

Sub Domain 2 Outgoing

Sub Domain 3 –

Measured Object TRX

Type Name Traffic measurements

Type Definition Set of counters related to the traffic evaluation per telecom procedures

External Comment –

8 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2 Quality of Service

1.2.1 Directed Retry

1.2.1.1 Internal

1.2.1.1.1 Success

1.2.1.1.1.1 C717a - NB_INC_IDR_SUCC_TRX

Long Name NB_INC_IDR_SUCC_TRX

Definition Number of incoming directed retry (towards a TCH channel in HR or FR usage)successes, per TRX.MC717a = C717a

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel involved in an internal directedretry procedure.

Sub Domain 1 Directed Retry

Sub Domain 2 Internal

Sub Domain 3 Success

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 9 / 1256


1.2.2 Established Phase

1.2.2.1 SDCCH

1.2.2.1.1 Failure

1.2.2.1.1.1 C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB

Long Name NB_SDCCH_DROP_EST_PHAS_BSS_PB

Definition MC137=C137, Number of SDCCH drops in SDCCH established phase due toBSS problem.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the call is released.

Trigger condition 1) LapD failure detected during the stable phase of an SDCCH transaction.2)SDCCH was released due to 48.058 ERROR REPORT with any cause valuebeing received during the stable phase of an SDCCH transaction.3) TelecomSupervisory module caused the call to be cleared.4) SDCCH was released dueto 0180 CLEAR_CMD message being received from BSSAPduring the stablephase of an SDCCH transaction : O&M has disabled the DTC

Sub Domain 1 Established Phase

Sub Domain 2 SDCCH

Sub Domain 3 Failure

Measured Object Common cell




10 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.2.1.1.2 C138 - NB_SDCCH_DROP_EST_PHAS_RLF

Long Name NB_SDCCH_DROP_EST_PHAS_RLF

Definition Number of SDCCH drops on SDCCH established phase due to radio link failure(radio link timeout or Lapdm timer expiry).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with acause value of "radio link failure" is received on Abis interface for an SDCCHchannel.2) Whenever an 48.058 ERROR INDICATION message is received onAbis interface and leads to a loss of channel.


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 11 / 1256


1.2.2.2 TCH

1.2.2.2.1 Failure

1.2.2.2.1.1 C14c - NB_TCH_DROP_EST_PHAS_BSS_PB

Long Name NB_TCH_DROP_EST_PHAS_BSS_PB

Definition Number of TCH (in HR or FR usage) drops in TCH established phase due toBSS problem.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the call is released.This counter takes into account TCH intraffic or in signaling mode. It is not incremented in case of TCH drop during anormal assignment, a handover or a DTM assignment.

Trigger condition 1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&Mintervention" is received on Abis interface after TCH seizure and leads to a lossof call.2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with acause value of "message sequence error" is received on Abis interface after TCHseizure and leads to a loss of call.3) Whenever a LAPD failure is reported to theLayer 3 of the BSC (for an RSL supporting a TCH transaction after successfulTCH seizure) and leads to a loss of call.4) Whenever a TCH call release isinitiated by the BSS O&M FAULT MANAGEMENT application part or by the BSSTELECOM application part as the result of a system defense action which maybe due to BSS equipment failures external to the BSC (e.g. RSL failure or CUrecovery failure), or due to BSC internal hardware problems (e.g. TCU failureor DTC failure) or due to BSC internal software problems (e.g. inconsistenciesdetected between software modules or lack of software resources (memory,timer reference, file reference...) or communication problems between differentprocessor boards).Notes : 1. TCH call releases which are due to O&M operatoractions on BTS or BSC should not be counted. Indeed, in case of numerousfailures due to O&M commands, this counter will overestimate failures whichare due to problems which are internal to the BSS.However, due to the currentimplementation which does not allow to be aware of the origin of the failure,O&M operator actions will also be counted. 2. It may happen that the countercan not be incremented since it is implemented within the faulty entity.


Sub Domain 2 TCH






12 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.2.2.1.2 C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF

Long Name NB_TCH_DROP_DTAP_EST_PHAS_RLF

Definition Number of TCH (in HR or FR usage) drops in TCH DTAP established phase dueto radio link failure (radio link timeout or Lapdm timer expiry).After an externalhandover, the target BSC considers that the CONNECT ACK has not alreadybeen received.

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message witha cause value of "radio link failure" is received on Abis interface for a TCHchannel (after successful DTAP establishment).2) Whenever an 48.058 ERRORINDICATION message is received on Abis interface and leads to a loss of call.


Sub Domain 2 TCH






3BK 21255 AAAA PCZZA Ed.07 13 / 1256


1.2.2.2.1.3 C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB

Long Name NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB

Definition Number of TCH (in HR or FR usage) drops in TCH DTAP established phase dueto BSS problem.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the call is released.After an external handover, the target BSCconsiders that the CONNECT ACK has not already been received.

Trigger condition 1) Whenever an 48.058 ERROR REPORT message with a cause value of "O&Mintervention" is received on Abis interface after TCH seizure and leads to a lossof call.2) Whenever an 48.058 ERROR REPORT message on SAPI 0 with acause value of "message sequence error" is received on Abis interface afterTCHDTAP establishment and leads to a loss of call.3) Whenever a LAPD failureis reported to the Layer 3 of the BSC (for an RSL supporting a TCH transactionafter successful TCH seizure) and leads to a loss of call.4) Whenever a TCHcall release is initiated by the BSS O&M FAULT MANAGEMENT application partor by the BSS TELECOM application part as the result of a system defenseaction which may be due to BSS equipment failures external to the BSC (e.g.RSL failure or CU recovery failure), or due to BSC internal hardware problems(e.g. TCU failure or DTC failure) or due to BSC internal software problems(e.g. inconsistencies detected between software modules or lack of softwareresources (memory, timer reference, file reference...) or communicationproblems between different processor boards).Notes : 1. TCH call releaseswhich are due to O&M operator actions on BTS or BSC should not be counted.Indeed, in case of numerous failures due to O&M commands, this counterwill overestimate failures which are due to problems which are internal to theBSS.However, due to the current implementation which does not allow to beaware of the origin of the failure, O&M operator actions will also be counted. 2.It may happen that the counter can not be incremented since it is implementedwithin the faulty entity.


Sub Domain 2 TCH






14 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.2.2.1.4 C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL

Long Name NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL

Definition Number of TCH (in HR or FR usage) drops in TCH DTAP established phasedue to remote transcoder failure. This counter is not concerned by the channelchange procedure.

Trigger condition Whenever a 48.058 CONNECTION FAILURE INDICATION message with acause value of "remote transcoder failure" is received on Abis interface for aTCH channel (for an established call).


Sub Domain 2 TCH






3BK 21255 AAAA PCZZA Ed.07 15 / 1256


1.2.2.2.1.5 C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX

Long Name NB_TCH_DROP_EST_PHAS_RLF_TRX

Definition Number of TCH (in HR or FR usage) drops in TCH established phase dueto radio link failure (radio link timeout or Lapdm timer expiry), per TRX. Thiscounter takes into account TCH in traffic or in signaling mode.MC736 = C736

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message witha cause value of "radio link failure" is received on Abis interface for a TCHchannel (after successful seizure).2) Whenever an 48.058 ERROR INDICATIONmessage is received on Abis interface and leads to a loss of call.


Sub Domain 2 TCH


Measured Object TRX




16 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.2.2.1.6 C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Long Name NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Definition Number of TCH (in HR or FR usage) drops in TCH established phase due toremote transcoder failures (per TRX).

Trigger condition The counter is incremented whenever a 48.058 CONNECTION FAILUREINDICATION message with cause "Remote Transcoder Failure" is receivedon Abis interface for an established TCH connection. The BSC considers aTCH connection as "established" once a 44.018 ASSIGNMENT COMPLETEmessage (in case of normal assignments or an internal intra-cell handovers) ora 44.018 HANDOVER COMPLETE message (in case of an internal inter-cellincoming HO or an external inter-cell incomingHO) has been received for theTCH connection.Note 1: MC739 = C739.Note 2: The counter is incrementedonly once per established TCH connection. Thus, even if the BTS sends several48.058 CONNECTION FAILURE INDICATION messages with cause "RemoteTranscoder Failure" for a particular established TCH connection, BSC willincrement the counter only once for that connection."


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 17 / 1256


1.2.3 Handover

1.2.3.1 SDCCH

1.2.3.1.1 Failure

1.2.3.1.1.1 C07 - NB_SDCCH_DROP_OUT_HO

Long Name NB_SDCCH_DROP_OUT_HO

Definition MC07=C07, Number of SDCCH drops during any outgoing SDCCH handover.

Trigger condition Internal inter-cell SDCCH handover: whenever the timer supervising thehandover procedure (T3103) expires.

Sub Domain 1 Handover

Sub Domain 2 SDCCH






18 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.3.1.2 Success

1.2.3.1.2.1 C03 - NB_OUT_SDCCH_HO_SUCC

Long Name NB_OUT_SDCCH_HO_SUCC

Definition MC03=C03, Number of outgoing SDCCH handover (any kind) successes.

Trigger condition External SDCCH handover in the following cases:1/ 48.008 CLEAR COMMAND(cause= "handover successful") is received on the serving BSC.2/ 48.008CLEAR COMMAND (cause= "normal event/call control") received while T8 isrunning.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 19 / 1256


1.2.3.1.2.2 C10 - NB_INC_SDCCH_HO_SUCC

Long Name NB_INC_SDCCH_HO_SUCC

Definition MC10=C10, Number of incoming SDCCH handover (any kind) successes.

Trigger condition Internal inter-cell or external SDCCH handover: whenever a 44.018 HANDOVERCOMPLETE message is received on Abis interface from the target cell foran SDCCH Sub-channel.Note: This counter counts both inter-PLMN andintra-PLMN handover events.


Sub Domain 2 SDCCH






20 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.3.2 TCH

1.2.3.2.1 Failure

1.2.3.2.1.1 C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB

Long Name NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB

Definition Number of TCH (in HR or FR usage) drops due to BSS problem during any TCHhandover preparation and execution phases.This counter is incremented on thecell on which the problem occurs(In the case of internal inter-cell handovers,it is not incremented on both serving and target cell). For problems that arenot related to a specific cell, the counter related to the serving cell will beincremented.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the handover procedure fails. This counter takes into accounthandovers from TCH in traffic or in signaling mode.

3BK 21255 AAAA PCZZA Ed.07 21 / 1256


Trigger condition 1) Whenever the BSC receives on Abis interface from the target cell negativeacknowledgment to the TCH channel activation involved in the handoverprocedure.2) Whenever the timer supervising the Channel Activation procedure(T9103) expires on the target cell during activation of a TCH channel involved inthe handover procedure.3) Whenever an 48.058 ERROR REPORT messagewith a cause value of "O&M intervention" is received on Abis interface fromeither the serving or the target cell during the external or internal inter-cellhandover procedure and leads to a transaction failure.4) Whenever an 48.058ERROR REPORT message with a cause value of "O&M intervention" isreceived on Abis interface on either the old or the new channel during theinternal intra-cell handover procedure and leads to a transaction failure.5)Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause valueof "message sequence error" is received on Abis interface from the servingcell between the sending of the 48.058 CHANNEL ACTIVATION message andthe reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENTduring the internal inter-cell TCH handover and leads to a transaction failure.6)Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause valueof "message sequence error" is received on Abis interface on the old channelbetween the sending of the 48.058 CHANNEL ACTIVATION message and thereception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during theinternal intra-cell TCH handover and leads to a transaction failure.7) Whenevera LAPD failure related to either serving or target cell is reported to the Layer 3of the BSC (for an RSL supporting a TCH transaction for handover purpose)and leads to a transaction failure.8) Whenever an TCH handover abortion isinitiated by the BSS O&M FAULT MANAGEMENT application part or by the BSSTELECOM application part as the result of a system defense action which maybe due to BSS equipment failures external to the BSC (e.g. RSL failure or CUrecovery failure), or due to BSC internal hardware problems (e.g. TCU failureor DTC failure) or due to BSC internal software problems (e.g. inconsistenciesdetected between software modules or lack of software resources (memory,timer reference, file reference...) or communication problems between differentprocessor boards).9) Whenever a 48.058 CONNECTION FAILURE INDICATIONmessage with a cause value of "remote transcoder failure" is received on Abisinterface from the old channel between the sending of the 48.058 CHANNELACTIVATION message and the reception of the 48.058 CHANNEL ACTIVATIONACKNOWLEDGE during an internal intra-cell or inter-cellTCH handoverprocedure and leads to a transaction failure.Notes : 1. TCH handover failureswhich are due to O&M operator actions on BTS or BSC should not be counted.Indeed, in case of numerous failures due to O&M commands, this counterwill overestimate failures which are due to problems which are internal to theBSS.However, due to the current implementation which does not allow to beaware of the origin of the failure, O&M operator actions will also be counted. 2.It may happen that the counter can not be incremented since it is implementedwithin the faulty entity.


Sub Domain 2 TCH




22 / 1256 3BK 21255 AAAA PCZZA Ed.07




3BK 21255 AAAA PCZZA Ed.07 23 / 1256


1.2.3.2.1.2 C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX

Long Name NB_TCH_DROP_OUT_HO_EXEC_TRX

Definition Number of TCH drops during the execution of any TCH outgoing handover,per TRX. This counter takes into account handovers from TCH in traffic or insignaling mode.MC621 = C621

Trigger condition 1) Inter-cell TCH handover: whenever the timer supervising the handoverprocedure (T3103) expires.2) External TCH handover (2G -> 2G): wheneverthe timer supervising the handover procedure on the serving cell (T8) expires,except if a 48.008 CLEAR COMMAND with "normal event/call control" causewas received from the MSC, leading to a normal call release. In such a case,the handover is considered as successful.3) Intra-cell TCH handover: wheneverthe timer supervising the handover procedure (T3107) expires.4) 2G -> 3G HO:whenever the timer supervising the 2G-3G handover procedure on the servingcell (T3121) expires, except if a 48.008 CLEAR COMMAND with "normalevent/call control" cause was received from the MSC, leading to a normal callrelease. In such a case, the 2G->3G handover is considered as successful.


Sub Domain 2 TCH


Measured Object TRX




24 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.3.2.1.3 C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX

Long Name NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX

Definition Nb of outgoing TCH handover -preparation failures due to congestion, per TRX.Intracell, internal intercell and external handovers are counted together. Thiscounter takes into account handovers from TCH in traffic or in signaling mode. Itdoes not take into account DTM Assignments.MC711 = C711

Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover cannot be performed,because there is no free TCH channel to allocate the handover to.2) Internalinter-cell HO: Whenever a internal inter-cell TCH handover cannot be performed,because there is no free TCH channel to allocate the handover to.3) ExternalHO: Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "noradio resource available" is received from the MSC by the serving BSC for anoutgoing external TCH HO.Note : the counter will be incremented for externalTCH HO if and only if the parameter RESP_REQ is set to 1.Note: This countercounts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 25 / 1256


1.2.3.2.1.4 C713 - NB_TCH_OUT_HO_FAIL_REV_TRX

Long Name NB_TCH_OUT_HO_FAIL_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problemwith reversion of the mobile to the old channel. Intracell, internal intercell andexternal handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC713 = C713

Trigger condition 1) External HO: Whenever a 44.018 HANDOVER FAILURE message is receivedon Abis interface from the serving cell, during an external TCH handover.2)Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message isreceived on Abis interface from the serving cell, during an internal inter-cellTCH handover.3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILUREmessage is received on Abis interface on the serving channel, during aninternal intra-cell TCH handover.Note: This counter counts both inter-PLMN andintra-PLMN handover events.Note: This counter counts handover to UMTS.


Sub Domain 2 TCH


Measured Object TRX




26 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.3.2.1.5 C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Long Name NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problemwithout reversion of the mobile to the old channel (call drop). Intracell, internalintercell and external handovers are counted together. This counter takes intoaccount handovers from TCH in traffic or in signaling mode. It does not take intoaccount DTM Assignments.MC714 = C714

Trigger condition 1) External TCH HO: Whenever the timer supervising the handover procedureon the serving cell (T8) expires, except if a 48.008 CLEAR COMMAND with"normal event/call control" cause was received from the MSC, leading to anormal call release. In such a case, the handover is considered as successful.2)Internal intercell TCH HO: Whenever the timer supervising the handoverprocedure (T3103) expires during an internal inter-cell TCH handover.3) IntracellTCH HO: Whenever the timer supervising the handover procedure (T3107)expires during an internal intra-cellNote: This counter counts both inter-PLMNand intra-PLMN handover events.Note: This counter counts hantover to UMTS


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 27 / 1256


1.2.3.2.2 Success

1.2.3.2.2.1 C712 - NB_TCH_OUT_HO_SUCC_TRX

Long Name NB_TCH_OUT_HO_SUCC_TRX

Definition Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercelland external handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC712 = C712

Trigger condition 1) External HO in the following cases:1a) 48.008CLEAR COMMAND (cause ="handover successful") is received on the serving BSC on the TCH channel.1b)48.008 CLEAR COMMAND (cause = "normal event/call control") is receivedwhile T8 is running.2) Internal inter-cell HO: whenever 44.018HANDOVERCOMPLETE is received from the MS via the target cell on the TCH channel.3)Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is receivedfrom the MS via the cell on the TCH channel.Note 1: This counter counts bothinter-PLMN and intra-PLMN handover events.Note 2: This counter countshandover to UMTS.


Sub Domain 2 TCH


Measured Object TRX




28 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.3.2.2.2 C717b - NB_INC_TCH_HO_SUCC_TRX

Long Name NB_INC_TCH_HO_SUCC_TRX

Definition Number of incoming internal and external TCH (in HR or FR usage) handoversuccesses per TRX; since there are no reliable means at the target BSC todistinguish external directed retry from external handover, the external directedretries are counted by this counter.MC717b = C717b

Trigger condition 1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVERCOMPLETE message is received on Abis interface from the target cell fora TCH channel.2) Intra-cell handover: whenever an 44.018 ASSIGNMENTCOMPLETE message is received on Abis interface on the target channel.Note:This counter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 29 / 1256


1.2.4 Speech

1.2.4.1 TFO

1.2.4.1.1 –

1.2.4.1.1.1 C170 - NB_CALL_TFO

Long Name NB_CALL_TFO

Definition Number of TCHs assigned in the serving cell for which TFO has beensuccessfully established.

Trigger condition For each assigned TCH, the counter is incremented the first time a 48.058 TFOREPORT message is received by the BSC, indicating that TFO is established(i.e. TFO = 1 in the TFO Status IE).Note 1: This counter shall be incrementedonly once per assigned TCH (i.e. the first time it is received for the assignedTCH).Note 2: A TCH is seen as assigned in the serving cell between thesending of 48.058 CHANNEL ACTIVATION message and the receipt of the48.058 RF CHANNEL RELEASE message. This means that the counter canbe incremented either if the TCH is assigned to serve a normal assignment orif the TCH is assigned to serve an incoming internal (inter-cell or intra-cell) orexternal handover.Note 3: MC170 = C170

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





30 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.4.1.1.2 C171 - NB_TFO_CODEC_REQ

Long Name NB_TFO_CODEC_REQ

Definition Number of codec mismatch resolutions or codec optimisations requested tothe BSC.

Trigger condition Whenever a 48.058 REMOTE CODEC CONFIGURATION REPORT is receivedby the BSC.

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 31 / 1256


1.2.5 Telecom Procedure (QoS)

1.2.5.1 –

1.2.5.1.1 –

1.2.5.1.1.1 C901 - NB_Suspend_Resume_req

Long Name NB_Suspend_Resume_req

Definition Number of suspend / Resume requests.A request could lead to a success, afailure or a stop.

Trigger condition Emission of MS Suspend message by the BSC to the MFSEmission of MSResume message by the BSC to the MFSA suspend message received fromMS with a "suspend cause" filtered by BSC will not be counted. Stop causescould be:1) External handover2) MS channel failure.

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 –

Sub Domain 3 –





32 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.1.1.2 C902 - Nb_Suspend_fail

Long Name Nb_Suspend_fail

Definition Number of suspend/resume procedure failures.

Trigger condition Reception of -Suspend nack or resume nack, or expiration of T_GPRS_Resume.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 33 / 1256


1.2.5.1.1.3 C903 - Nb_Suspend_succ

Long Name Nb_Suspend_succ

Definition Number of suspensions successes.

Trigger condition Reception of Resume ack message from MFS.


Sub Domain 2 –

Sub Domain 3 –





34 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.1.2 Failure

1.2.5.1.2.1 C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP

Long Name NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP

Definition Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (inHR or FR usage) is available in the cell, timer T11 (case MSC requests forqueuing whatever QUEUE_ANYWAY value may be) or timer T11_forced(case QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) isstarted, and no free TCH can be found before timer expiry, consequently therequest is rejected (by 48.008 CLEAR REQUEST cause: "no radio resourceavailable").Remark: If an internal directed retry is attempted and failed whileT11/T11_forced is running, the request is un-holded and the BSC waits for theexpiry of the relevant timer. Consequently, this counter must not be incrementedupon the failure of an internal directed retry.

Trigger condition The counter is incremented upon the sending of 48.008 CLEAR REQUEST(cause : "no radio resource available") -following the expiry of T11 or T11forced for a queued TCH normal assignment.Note 1: The HMI name of theparameter QUEUE_ANYWAY is "FORCED_QUEUING".Note 2: In case of MxBSC, "no TCH available" could happen when the TCH processing capacity ofCCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In thiscase, this counter and MC926 are incremented by one.Note 3: In IP mode, thiscounter is increased by 1 if:- the cell mapped on a BTS is in IP congestionstatus;- or the TCH processing capacity of AbisBTSGroup reaches the limitdefined by the NB_MAX_ACTIVE_TCH_TS parameter


Sub Domain 2 –






3BK 21255 AAAA PCZZA Ed.07 35 / 1256


1.2.5.2 DTAP Assignment

1.2.5.2.1 Success

1.2.5.2.1.1 C161a - NB_DTAP_MO_NOR_ASS_SUCC

Long Name NB_DTAP_MO_NOR_ASS_SUCC

Definition Number of mobile originating normal assignment - DTAP successes.

Trigger condition Whenever a 44.018 CONNECT ACK is received on Abis interface.


Sub Domain 2 DTAP Assignment






36 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.2.1.2 C161b - NB_DTAP_MT_NOR_ASS_SUCC

Long Name NB_DTAP_MT_NOR_ASS_SUCC

Definition Number of mobile terminating normal assignment - DTAP successes.

Trigger condition Whenever a 44.018 CONNECT ACK is sent on Abis interface.








3BK 21255 AAAA PCZZA Ed.07 37 / 1256


1.2.5.3 Immediate Assignment

1.2.5.3.1 Failure

1.2.5.3.1.1 C04 - NB_IMM_ASS_PREP_FAIL_CONG

Long Name NB_IMM_ASS_PREP_FAIL_CONG

Definition MC04=C04, number of immediate assignment preparation failures due tocongestion.

Trigger condition All SDCCH sub-channels in the required cell were either Busy or Out of Service,when the 48.058 CHANNEL REQUIRED message was received.


Sub Domain 2 Immediate Assignment






38 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.1.2 C149 - NB_IMM_ASS_EXEC_FAIL_RADIO

Long Name NB_IMM_ASS_EXEC_FAIL_RADIO

Definition Number of immediate assignment -execution failures due to MS access problem.

Trigger condition Whenever the timer supervising the Immediate Assignment Procedure (T3101)expires during the establishment of an SDCCH sub-channel.








3BK 21255 AAAA PCZZA Ed.07 39 / 1256


1.2.5.3.2 Success

1.2.5.3.2.1 C01 - NB_IMM_ASS_SUCC_MT

Long Name NB_IMM_ASS_SUCC_MT

Definition Number of immediate assignment plus SDCCH normal assignment successesfor Mobile Terminating procedure.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received froma CELL, with the L3_INFORMATION field including a 44.018 PAGINGRESPONSE message.








40 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.2.2 C02 - NB_IMM_ASS_SUCC_MO

Long Name NB_IMM_ASS_SUCC_MO

Definition Number of immediate assignment successesfor Mobile Originating procedure.MC02 = C02 =C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i.Thefollowing counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecomprocedures on SDCCH.

Trigger condition –








3BK 21255 AAAA PCZZA Ed.07 41 / 1256


1.2.5.3.2.3 C02a - NB_IMM_ASS_SUCC_MO_LOC_UPD

Long Name NB_IMM_ASS_SUCC_MO_LOC_UPD

Definition case: Location Update request (except the "follow on" procedure)

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from acell, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to LOCATION UPDATING REQUEST and with an MIELocation updating type not set to a RESERVED value and a bit FOR set to0.This counter is incremented only if the L3 info message received has to beforwarded to the MSC.








42 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.2.4 C02b - NB_IMM_ASS_SUCC_MO_SMS

Long Name NB_IMM_ASS_SUCC_MO_SMS

Definition case: SMS procedure on SDCCH

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and with an MIE CM servicetype set to "SMS".This counter is incremented only if the L3 info messagereceived has to be forwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 43 / 1256


1.2.5.3.2.5 C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV

Long Name NB_IMM_ASS_SUCC_MO_SUP_SERV

Definition case: Supplementary Service

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and with an MIE CM servicetype set to "Supplementary Service".This counter is incremented only if the L3info message received has to be forwarded to the MSC.








44 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.2.6 C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON

Long Name NB_IMM_ASS_SUCC_MO_FOLLOW_ON

Definition case: Location Update request ("follow on" procedure)

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to LOCATION UPDATING REQUEST and with an MIELocation updating type not set to a RESERVED value and a bit FOR set to1.This counter is incremented only if the L3 info message received has to beforwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 45 / 1256


1.2.5.3.2.7 C02e - NB_IMM_ASS_SUCC_MO_CM_REEST

Long Name NB_IMM_ASS_SUCC_MO_CM_REEST

Definition case: CM Re-establishment procedure

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM RE-ESTABLISHMENT REQUEST message.Thiscounter is incremented only if the L3 info message received has to be forwardedto the MSC.








46 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.2.8 C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW

Long Name NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW

Definition MC02f=C02f, number of immediate assignment successes for MobileOriginationg procedure, in case of L3 Info (within 48.058 ESTABLISHINDICATION) unknown by the BSC but transferred to the MSC.









3BK 21255 AAAA PCZZA Ed.07 47 / 1256


1.2.5.3.2.9 C02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH

Long Name NB_IMM_ASS_SUCC_MO_IMSI_DETACH

Definition MC02g=C02g, number of immediate assignment successes for MobileOriginationg procedure, in case of IMSI Detach Indication.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with L3_INFORMATION field containing a 44.018 L3 message withan MIE message type set to IMSI DETACH INDICATION. This counter isincremented only if the L3 info message received has to be forwarded to theMSC.








48 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.3.2.10 C02h - NB_IMM_ASS_SUCC_MO_CALL_EST

Long Name NB_IMM_ASS_SUCC_MO_CALL_EST

Definition case: normal or emergency call establishment

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containg a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and an MIE CM servicetype set to either :- "emergency call establishment",- or "mobile originating callestablishment"This counter is incremented only if the L3 info message receivedhas to be forwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 49 / 1256


1.2.5.3.2.11 C02i - NB_IMM_ASS_SUCC_MO_LCS

Long Name NB_IMM_ASS_SUCC_MO_LCS

Definition case: Mobile originated LCS procedure on SDCCH

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a cell,with the L3 INFORMATION field containing a 44.018 L3 message with an MIEmessage type set to CM SERVICE REQUEST and with an MIE CM service typeset to "Location Services" (LCS).This counter is incremented only if the L3 infomessage received has to be forwarded to the MSC








50 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.4 Normal Assignment

1.2.5.4.1 Failure

1.2.5.4.1.1 C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE

Long Name NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE

Definition Number of TCH (in HR or FR usage) normal assignment preparation failuresbecause of the non-queuing of the ASSIGNMENT REQUEST message.Case:48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received whenno TCH is available in the cell. The request is rejected (by 48.008ASSIGNMENTFAILURE, cause: "no radio resource available"), because the queuing procedureis either:1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR(T11_forced=0 and QUEUE_ANYWAY=1)), or2) enabled within the BSC, i.e.T11 <> 0, but not requested by the MSC when QUEUE_ANYWAY=0.

Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENTFAILURE (cause: "no radio resource available") for a TCH channel becauseno TCH is available and either the queuing is disabled in the BSC (T11=0and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or thequeuing is enabled, QUEUE_ANYWAY=0, and the MSC does not requesta queuing.Note 1: The HMI name of the parameter QUEUE_ANYWAY is"FORCED_QUEUING".Note 2: In case of Mx BSC, "no TCH available" couldhappen when the TCH processing capacity of CCP reaches the limit defined bythe MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 areincremented by one.Note 3: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter


Sub Domain 2 Normal Assignment






3BK 21255 AAAA PCZZA Ed.07 51 / 1256


1.2.5.4.1.2 C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL

Definition MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (in FR or HRusage) is received when no TCH is available in the cell. The queuing is enabledwithin the BSC, but the request is rejected (by 48.008ASSIGNMENT FAILURE,cause: "no radio resource available"), because the queue is full and no requestof lower priority can be dequeued from the BSC queue.

Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENTFAILURE (cause: "no radio resource available") for a TCH channel because thequeue is full and no request of lower priority can be de-queued.Note 1: In caseof Mx BSC, "no TCH available" could happen when the TCH processing capacityof CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. Inthis case, this counter and MC926 are incremented by one.Note 2: In IP mode,this counter is increased by 1 if:- the cell mapped on a BTS is in IP congestionstatus;- or the TCH processing capacity of AbisBTSGroup reaches the limitdefined by the NB_MAX_ACTIVE_TCH_TS parameter








52 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.4.1.3 C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Definition Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (inHR or FR usage) is available in the cell, timer T11 (case MSC requests forqueuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (caseQUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started,and before the timer expiry, the request is dequeued due to the receipt of ahigher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the BSC sends48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for thefirst transaction.Remark: As soon as an internal directed retry is attempted,the request is blocked within the BSC and cannot be dequeued by a higherpriority request.

Trigger condition The counter is incremented upon the sending of the 48.008 ASSIGMENTFAILURE (cause: "no radio resource available") for a de-queued TCHrequest (i.e. normal assignment) due to the receipt of a higher priorityrequest.Note 1: The HMI name of the parameter QUEUE_ANYWAY is"FORCED_QUEUING".Note 2: In case of Mx BSC, "no TCH available" couldhappen when the TCH processing capacity of CCP reaches the limit defined bythe MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 areincremented by one.Note 3: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter








3BK 21255 AAAA PCZZA Ed.07 53 / 1256


1.2.5.4.1.4 C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX

Long Name NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX

Definition Number of TCH (in HR or FR usage) normal assignment -execution failuresdue to MS access problem, per TRX. This counter also takes into accountDTM assignment -execution failures due to MS access problem for TCHestablishment in signaling mode (FR usage only).MC746b = C746b

Trigger condition 1) The timer T3107 in the BSS supervising the TCH channel seizure by themobile expires (following the sending of 44.018 ASSIGNMENT COMMAND for aTCH channel that is not involved in a handover procedure).2) The timer T3107in the BSS supervising the TCH channel seizure by the mobile expires, followingthe sending of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel insignaling mode.3) The BSC receives a 44.018 ASSIGNMENT FAILURE onthe old (SDCCH) channel during the normal assignment procedure except incase of multiband cell, when the normal assignment procedure is performedin the inner zone and the ASSIGNMENT FAILURE is received with the cause"protocol error unspecified".4) The BSC receives a 44.018 DTM ASSIGNMENTFAILURE on the old (SDCCH) channel during the DTM assignment procedure,for a TCH in signaling mode.




Measured Object TRX




54 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.2.5.4.1.5 C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS

Long Name NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS

Definition MC812 = C812 = C612a + C612b + C612c + C612d









3BK 21255 AAAA PCZZA Ed.07 55 / 1256


1.2.5.4.2 Success

1.2.5.4.2.1 C718 - NB_TCH_NOR_ASS_SUCC_TRX

Long Name NB_TCH_NOR_ASS_SUCC_TRX

Definition Number of TCH (in HR or FR usage) normal assignment successes, per TRX.This counter also takes into account normal assignment successes for TCHestablishment in signaling mode (FR usage only), for DTM.MC718 = C718

Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abisinterface for a TCH channel that is not involved in a handover procedure, intraffic or in signaling mode.




Measured Object TRX




56 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3 Resource Availability & Usage

1.3.1 Resource Allocation & Management

1.3.1.1 –

1.3.1.1.1 –

1.3.1.1.1.1 C443 - NB_TIMES_TRAF_DETECTED_LOW

Long Name NB_TIMES_TRAF_DETECTED_LOW

Definition Number of times the traffic_load is "low", i.e. when a certain number(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each:AV_LOAD < LOW_THRESHOLD. The traffic_load is evaluated per cellat each A_TRAFFIC_LOAD period.This counter permits to tune thefollowing parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD andLOW_THRESHOLD.This counter relates to the number of free TCH timeslots.

Trigger condition At each A_TRAFFIC_LOAD period, whenever the BSC decision processdetects a "low" traffic_load.Remark : the number of "indefinite" trafficload can be deduced from the counters NB_LOW_TRAFFIC_LOAD andNB_HIGH_TRAFFIC_LOAD over the Accumulation Period.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 57 / 1256


1.3.1.2 E-GSM

1.3.1.2.1 –

1.3.1.2.1.1 C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU

Long Name NB_EGSM_MS_ACCESS_EXCEPT_LU

Definition Number of initial accesses for call establishments (except location update) ofMS supporting the E-GSM band, on a CELL basis.MC706 = C706

Trigger condition Whenever a 44.018 CLASSMARK CHANGE message in the context of anyestablishment causes different from location update is received on Abisinterface with a "Mobile Station Classmark 3" or a "Mobile Station Classmark 2"Information Element field specifying that the MS supports the E-GSM band.Thecounter is incremented only once per SCCP connection in the serving cell, i.e.on receipt of the first 44.018 CLASSMARK CHANGE message.


Sub Domain 2 E-GSM

Sub Domain 3 –





58 / 1256 3BK 21255 AAAA PCZZA Ed.07



1.3.1.3.1 –

1.3.1.3.1.1 C442 - NB_TIMES_TRAF_DETECTED_HIGH

Long Name NB_TIMES_TRAF_DETECTED_HIGH

Definition Number of times the traffic_load is "high", i.e. when a certain number(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each:AV_LOAD > HIGH_THRESHOLD. The traffic_load is evaluated percell at each A_TRAFFIC_LOAD period.This counter permits to tunethe following parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD andHIGH_THRESHOLD.This counter relates to the number of free TCH timeslots.

Trigger condition At each A_TRAFFIC_LOAD period, whenever the BSC decision process detectsa "high" traffic_load.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 59 / 1256


1.3.1.4 Service

1.3.1.4.1 –

1.3.1.4.1.1 C701a - NB_TCH_FR_REQ

Long Name NB_TCH_FR_REQ

Definition Number of TCH normal assignments requests from FR only mobiles (afterpossible filtering from the MSC).

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withonly GSM speech coding algorithm version 1 full rate allowed.


Sub Domain 2 Service

Sub Domain 3 –





60 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3.1.4.1.2 C701b - NB_TCH_DR_REQ

Long Name NB_TCH_DR_REQ

Definition Number of TCH normal assignments requests from dual rate mobiles.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withonly GSM speech coding algorithm version 1 full rate and GSM speech codingalgorithm version 1 half rate allowed.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 61 / 1256


1.3.1.4.1.3 C701c - NB_TCH_DR_EFR_REQ

Long Name NB_TCH_DR_EFR_REQ

Definition Number of TCH normal assignment requests from mobiles supporting FR, HRand EFR.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withGSM speech coding algorithm version 1 full rate, GSM speech coding algorithmversion 1 half rate and GSM speech coding algorithm version 2 full rate allowed.



Sub Domain 3 –





62 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3.1.4.1.4 C701d - NB_TCH_AMR_REQ

Long Name NB_TCH_AMR_REQ

Definition Number of TCH normal assignment requests from AMR mobiles.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withGSM speech coding algorithm version 3 full rate or half rate allowed.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 63 / 1256


1.3.1.4.1.5 C701e - NB_TCH_DATA_REQ

Long Name NB_TCH_DATA_REQ

Definition Number of TCH normal assignment requests for data calls.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.



Sub Domain 3 –





64 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3.1.4.1.6 C702a - NB_TCH_NOR_FR_ALLOC

Long Name NB_TCH_NOR_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR usage - whose channelis allocated in the BSC. This counter takes into account mode modify from TCHsignaling to TCH traffic (following a DTM assignment with a TCH in signalingmode).

Trigger condition 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS,indicating a FR channel with GSM speech coding algorithm version 1, notrelated to handover.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 65 / 1256


1.3.1.4.1.7 C702b - NB_TCH_NOR_HR_ALLOC

Long Name NB_TCH_NOR_HR_ALLOC

Definition number of TCH normal assignment/mode modify in HR usage - whose channelis allocated in the BSC.

Trigger condition 48.058 CHANNEL ACTIVATION / MODE MODIFY about to be sent to theBTS, indicating a HR channel with GSM speech coding algorithm version 1,not related to handover.



Sub Domain 3 –





66 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3.1.4.1.8 C702c - NB_TCH_NOR_EFR_ALLOC

Long Name NB_TCH_NOR_EFR_ALLOC

Definition Number of TCH normal assignment/mode modify in EFR usage - whosechannel is allocated in the BSC. This counter takes into account mode modifyfrom TCH signaling to TCH traffic (following a DTM assignment with a TCH insignaling mode).




Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 67 / 1256


1.3.1.4.1.9 C704a - NB_TCH_NOR_AMR_FR_ALLOC

Long Name NB_TCH_NOR_AMR_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR AMR usage - whosechannel is allocated in the BSC. This counter takes into account mode modifyfrom TCH signaling to TCH traffic (following a DTM assignment with a TCH insignaling mode).




Sub Domain 3 –





68 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.3.1.4.1.10 C704b - NB_TCH_NOR_AMR_HR_ALLOC

Long Name NB_TCH_NOR_AMR_HR_ALLOC

Definition number of TCH normal assignment/mode modify in HR AMR usage - whosechannel is allocated in the BSC.

Trigger condition 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS,indicating a HR channel with GSM speech coding algorithm version 3, notrelated to handover.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 69 / 1256


1.3.1.4.1.11 C705 - NB_TCH_NOR_DATA_ALLOC

Long Name NB_TCH_NOR_DATA_ALLOC

Definition Number of TCH normal assignment/mode modify for data - whose channel isallocated in the BSC. This counter takes into account mode modify from TCHsignaling to TCH traffic (following a DTM assignment with a TCH in signalingmode).

Trigger condition 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS,indicating a data call, not related to handover.



Sub Domain 3 –





70 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.4 Traffic Load

1.4.1 Telecom Procedure (Traffic Load)

1.4.1.1 Directed Retry

1.4.1.1.1 Internal

1.4.1.1.1.1 C15a - NB_INC_IDR_ALLOC

Long Name NB_INC_IDR_ALLOC

Definition MC15a=C15a, Number of incoming internal directed retry (towards a TCHchannel in HR or FR usage) whose target channel is allocated by the BSC.

Trigger condition The counter is incremented on the target cell whenever the 48.058 CHANNELACTIVATION message of a TCH channel is about to be sent during an internaldirected retry.

Sub Domain 1 Telecom Procedure (Traffic Load)







3BK 21255 AAAA PCZZA Ed.07 71 / 1256


1.4.1.2 Handover

1.4.1.2.1 SDCCH

1.4.1.2.1.1 C147 - NB_INC_SDCCH_HO_ALLOC

Long Name NB_INC_SDCCH_HO_ALLOC

Definition MC147=C147, Number of incoming internal or external SDCCH handovers-whose target SDCCH channel is allocated by the BSC.

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent onAbis Interface to activate an SDCCH channel for any handover purposes.Note:This counter counts both inter-PLMN and intra-PLMN handover events.



Sub Domain 3 SDCCH





72 / 1256 3BK 21255 AAAA PCZZA Ed.07


1.4.1.2.2 TCH

1.4.1.2.2.1 C13b - NB_INC_EXT_TCH_HO_QUEUED

Long Name NB_INC_EXT_TCH_HO_QUEUED

Definition Number of TCH (in HR or FR usage) incoming external handover requests thatare put in BSC queue

Trigger condition Further to the receipt of a 48.008 HANDOVER REQUEST message forTCH, the counter is incremented:i) upon the sending of a 48.008 QUEUINGINDICATION message if the queuing is authorised by the MSC, or,ii) when thehandover request is queued in the cell if the queuing is not authorised by theMSC and the request has its pre-emption indicator set (provided that the flagEN_TCH_PREEMPT is set to 'Enable').Note: MC13b = C13bNote: This countercounts both inter-PLMN and intra-PLMN handover events.



Sub Domain 3 TCH





3BK 21255 AAAA PCZZA Ed.07 73 / 1256


1.4.1.2.2.2 C15b - NB_INC_TCH_HO_ALLOC

Long Name NB_INC_TCH_HO_ALLOC

Definition Number of incoming TCH (in HR or FR usage) handover (internal or external)-whose target channel is allocated by the BSC.Since there are no reliable meansat the target BSC to distinguish external directed retry from external handover,the external directed retries are counted by this counter.

Trigger condition The counter is incremented on the target cell whenever the 48.058 CHANNELACTIVATION message of a TCH channel is about to be sent during anyhandover procedure.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.



Sub Domain 3 TCH





74 / 1256 3BK 21255 AAAA PCZZA Ed.07



1.4.1.3.1 –

1.4.1.3.1.1 C148 - NB_IMM_ASS_ALLOC

Long Name NB_IMM_ASS_ALLOC

Definition Number of immediate assignment plus SDCCH normal assignments -whoseSDCCH channel is allocated by the BSC.

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be senton Abis Interface to activate an SDCCH channel for any purpose other thanhandover.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 75 / 1256


1.4.1.4 Multiband

1.4.1.4.1 –

1.4.1.4.1.1 C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

Long Name NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

Definition Number of initial accesses for call establishments (location update apart)initiated by multiband mobile stations. The counter is defined on a per cellbasis.A MS is considered as multiband if it supports:- the P-GSM (or E-GSMor R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDSparameter is set to "GSM900 and DCS1800 bands", or,- the GSM850 andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to"GSM850 and DCS1800 bands", or,- the GSM850 and the DCS1900 bands ifthe PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".

Trigger condition Whenever a 44.018 Classmark Change message in the context of anyestablishment cause different from location update is received on Abisinterface from the MS with a "Mobile Station Classmark 3" Information Elementspecifying that the MS supports:- the P-GSM (or E-GSM or R-GSM) andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is setto "GSM900 and DCS1800 bands", or,- the GSM850 and the DCS1800bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850and DCS1800 bands", or,- the GSM850 and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".The counter is incremented only once per SCCP connection in theserving cell, i.e. on receipt of the first 44.018 CLASSMARK CHANGE message.


Sub Domain 2 Multiband

Sub Domain 3 –





76 / 1256 3BK 21255 AAAA PCZZA Ed.07



1.4.1.5.1 –

1.4.1.5.1.1 C13a - NB_TCH_NOR_ASS_QUEUED

Long Name NB_TCH_NOR_ASS_QUEUED

Definition Number of TCH (in HR or FR usage) normal assignment requests that areput in BSC queue.

Trigger condition Further to the receipt of a 48.008 ASSIGNMENT REQUEST message forTCH, the counter is incremented:i) upon the sending of a 48.008 QUEUINGINDICATION message if the queuing is authorised by the MSC, or,ii) whenthe assignment request is queued in the cell if the queuing is not authorisedby the MSC and the parameter QUEUE_ANYWAY is set, or,iii) when theassignment request is queued in the cell if the queuing is not authorised by theMSC and the request has its pre-emption indicator set (provided that the flagEN_TCH_PREEMPT is set to 'Enable').Note 1: MC13a = C13aNote 2: The HMIname of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 77 / 1256


1.4.1.5.1.2 C703 - NB_TCH_NOR_ASS_ALLOC_TRX

Long Name NB_TCH_NOR_ASS_ALLOC_TRX

Definition Number of TCH (in HR or FR usage) normal assignment whose RTCH channelis allocated in the BSC, per TRX. This counter also takes into account normalassignment whose RTCH channel is allocated in the BSC in signaling mode (FRusage only), for DTM.MC703 = C703

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent onAbis Interface to activate a TCH channel for normal assignment, or for DTMassignment with a TCH in signaling mode.



Sub Domain 3 –

Measured Object TRX




78 / 1256 3BK 21255 AAAA PCZZA Ed.07

2 BSC-TYPE 2 - Resource availability measurements


3BK 21255 AAAA PCZZA Ed.07 79 / 1256



2.1.1 Channel

2.1.1.1 CCCH

2.1.1.1.1 Availability

2.1.1.1.1.1 C27 - AV_NB_AVAIL_CCCH

Long Name AV_NB_AVAIL_CCCH

Definition Average number of available CCCH channels.

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value (real) is rounded up or down to the nearestinteger value.

Sub Domain 1 Channel

Sub Domain 2 CCCH

Sub Domain 3 Availability


Type Name Resource availability measurements

Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels


80 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.2 SDCCH

2.1.1.2.1 –

2.1.1.2.1.1 C803 - TIME_SDCCH_CONGESTION

Long Name TIME_SDCCH_CONGESTION

Definition Cumulated time (in seconds) during which the SDCCH request(s) are not servedbecause no SDCCH sub-channel is available.

Trigger condition The time counter is started whenever a SDCCH request cannot be served.Thetime counter is stopped whenever one of the following conditions is checked:- ifa SDCCH sub-channel becomes free and usable on a static SDCCH timeslotor on a dynamic timeslot allocated as SDCCH (i.e. when the timeslot is knownfrom the SDCCH_RM module). The term "usable" means here that the SDCCHsub-channel is not mapped on a TCU in a very high overload state, or,- if aSDCCH request is served successfully. This condition corresponds to the casethe SDCCH_RM module requests the TCH_RM module for a dynamic SDCCHtimeslot.


Sub Domain 2 SDCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 81 / 1256



2.1.1.2.2.1 C26 - AV_NB_AVAIL_SDCCH

Long Name AV_NB_AVAIL_SDCCH

Definition Average number of available static SDCCH sub-channels (i.e. on static SDCCHtimeslots).

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value (real) is rounded up or down to the nearestinteger value.Note: "Available" has here to be understood as the operationalstate of a timeslot. The timeslot is available if it is not "blocked" or "out ofservice".


Sub Domain 2 SDCCH






82 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.2.3 Usage

2.1.1.2.3.1 C30 - AV_NB_BUSY_SDCCH

Long Name AV_NB_BUSY_SDCCH

Definition Average number of busy SDCCH subchannels, taking into account the followingSDCCH sub-channels: 1) Static SDCCH/x sub-channels, 2) Dynamic SDCCHsub-channels which are dynamically allocated on the dynamic SDCCH/8timeslots.

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. In order to provide one decimal place, the average value (real) ismultiplied by ten and then rounded up or down to the nearest integer value.Notethat the counter value that is indicated in the ASCII file, which can be obtainedvia the OBSYNT interface, still has to be divided by 10, whereas the value thatis provided at the user interface is the correct one.


Sub Domain 2 SDCCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 83 / 1256


2.1.1.2.3.2 C31 - NB_MAX_SIMUL_BUSY_SDCCH

Long Name NB_MAX_SIMUL_BUSY_SDCCH

Definition Maximum number of simultaneously busy SDCCH subchannels, taking intoaccount the following SDCCH sub-channels: 1) Static SDCCH/x sub-channels,2) Dynamic SDCCH sub-channels which are dynamically allocated on thedynamic SDCCH/8 timeslots.

Trigger condition At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to thecell:C31 = MAX ["old" C31 value (i.e. before the channel activation), number ofbusy SDCCH subchannels observed for the cell].


Sub Domain 2 SDCCH

Sub Domain 3 Usage





84 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.3 TCH


2.1.1.3.1.1 C250 - AV_NB_AVAIL_TCH

Long Name AV_NB_AVAIL_TCH

Definition Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (forHR or FR usage) or PDCH).

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value is rounded up or down to the nearest integervalue.Note 1: "Available" has here to be understood as the operational state of atimeslot. The timeslot is available if it is not "blocked" or "out of service".Note 2:The dynamic SDCCH timeslots are not taken into account in this counter.


Sub Domain 2 TCH






3BK 21255 AAAA PCZZA Ed.07 85 / 1256


2.1.1.3.2 Usage

2.1.1.3.2.1 C141 - AV_NB_TCH_QUEUED

Long Name AV_NB_TCH_QUEUED

Definition Average number of queued TCH (in HR or FR usage) normal assignment orexternal handover requests.

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. In order to provide one decimal place, the averaged value (real) ismultiplied by ten and then rounded up or down to the nearest integer value.Notethat the counter value that is indicated in the ASCII file, which can be obtainedvia the OBSYNT interface, still has to be divided by 10, whereas the value thatis provided at the user interface is the correct one.


Sub Domain 2 TCH

Sub Domain 3 Usage





86 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.3.2.2 C28a - AV_NB_BUSY_CS_TS

Long Name AV_NB_BUSY_CS_TS

Definition Average number of busy TCH radio timeslot (in FR or HR usage, in traffic or insignaling mode) and busy dynamic SDCCH/8 radio timeslot allocated as TCH.

Trigger condition The BSC takes periodically a sample of the number of busy TCH radio timeslotsand busy dynamic SDCCH/8 radio timeslots allocated as TCH. The samplingperiod is set to the value indicated in the Status Inspection field. At the expiry ofthe accumulation period, all samples are averaged (i.e. summed and dividedby the number of samples). The averaged value is rounded up or down to thenearest value with an accuracy of 0.1.A TCH radio timeslot is considered asbusy during the time it is allocated to a given MS for TCH traffic (in HR or FRusage). A dynamic SDCCH/8 timeslot allocated as TCH is considered as busyduring the time it is allocated to a given MS for TCH traffic.Note 1: the countervalue that is indicated in the ASCII file (which can be obtained via the OBSYNTinterface) is an integer value (i.e. it is as if the BSC multiplies by 10 the average).The reported value shall then be divided by 10 afterwards so that the value thatis displayed to the end-user is the correct one.Note 2: This counter does nottake into account the PDCH radio timeslots allocated to the MFS.


Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 87 / 1256


2.1.1.3.2.3 C29a - NB_MAX_SIMUL_BUSY_CS_TS

Long Name NB_MAX_SIMUL_BUSY_CS_TS

Definition Maximum number of simultaneously busy TCH radio timeslots (in HR orFR usage, in traffic or in signaling mode) and simultaneously busy dynamicSDCCH/8 radio timeslots allocated as TCH.

Trigger condition Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocatedas TCH becomes busy, the BSC determines the current number of busy TCHradio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslotsallocated as TCH. This counter is the maximum value of this number duringthe accumulation period.This counter does not take into account the PDCHsallocated to the MFS.


Sub Domain 2 TCH

Sub Domain 3 Usage





88 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.3.2.4 C320a - AV_NB_IDLE_TCH_INTERF_BAND1

Long Name AV_NB_IDLE_TCH_INTERF_BAND1

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslotsbelonging to the interference band 1. This number is updated upon the receiptof 48.058 RF RESOURCE INDICATION.



Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 89 / 1256


2.1.1.3.2.5 C320b - AV_NB_IDLE_TCH_INTERF_BAND2



Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The average value (real) is rounded up or down to the nearestinteger value.


Sub Domain 2 TCH

Sub Domain 3 Usage





90 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.3.2.6 C320c - AV_NB_IDLE_TCH_INTERF_BAND3





Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 91 / 1256


2.1.1.3.2.7 C320d - AV_NB_IDLE_TCH_INTERF_BAND4


Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FRor HR usage belonging to the interference band 4. This number is updated uponthe receipt of 48.058 RF RESOURCE INDICATION.



Sub Domain 2 TCH

Sub Domain 3 Usage





92 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.3.2.8 C320e - AV_NB_IDLE_TCH_INTERF_BAND5





Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 93 / 1256


2.1.1.4 TRX_TS


2.1.1.4.1.1 C24 - AV_NB_NOT_AVAIL_TRX_TS

Long Name AV_NB_NOT_AVAIL_TRX_TS

Definition Average number of not available radio timeslots (TRX_TS).



Sub Domain 2 TRX_TS






94 / 1256 3BK 21255 AAAA PCZZA Ed.07


2.1.1.4.2 Usage

2.1.1.4.2.1 C34 - TIME_ALL_AVAIL_TRX_TS_BUSY

Long Name TIME_ALL_AVAIL_TRX_TS_BUSY

Definition Cumulated time (in seconds) during which there is no free FR TCH sub-channelto serve an incoming FR TCH request. A TCH sub-channel is seen as busy:i)if the TCH sub-channel is occupied by a HR or FR CS call (in particular if it isoccupied by the CS part of a DTM call), orii) if the TCH sub-channel is allocatedto the MFS to carry PS traffic.

Trigger condition The counter is started when there is no free FR TCH sub-channel to serve anincoming FR TCH request.The counter is stopped when there is a free FR TCHsub-channel to serve an incoming FR TCH request.


Sub Domain 2 TRX_TS

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 95 / 1256


96 / 1256 3BK 21255 AAAA PCZZA Ed.07

3 BSC-TYPE 3 - Resource usage on CCCH channel measurements

3 BSC-TYPE 3 - Resource usage on CCCH channelmeasurements

3BK 21255 AAAA PCZZA Ed.07 97 / 1256


3.1 Traffic Load

3.1.1 Channel

3.1.1.1 CCCH

3.1.1.1.1 –

3.1.1.1.1.1 C8a - NB_PAGING_CMD

Long Name NB_PAGING_CMD

Definition PCH load: number of 48.058 PAGING COMMAND messages sent either for PStraffic or for CS traffic on Abis towards the selected cell.

Trigger condition Whenever a 48.058 PAGING COMMAND message (either for PS traffic or forCS traffic) is about to be sent on Abis interface to the cell on the related TRXtimeslot.


Sub Domain 2 CCCH

Sub Domain 3 –

Measured Object TRX_TS

Type Name Resource usage on CCCH channel measurements

Type Definition Set of counters related to the usage of the CCCH channel (PCH load, AGCHload, RACH load)


98 / 1256 3BK 21255 AAAA PCZZA Ed.07


3.1.1.1.1.2 C8b - NB_IMM_ASS_CMD

Long Name NB_IMM_ASS_CMD

Definition AGCH load: number of 48.058 IMMEDIATE ASSIGN COMMAND messagessent for CS traffic on Abis to the MS.

Trigger condition Whenever a 48.058 IMMEDIATE ASSIGN COMMAND message for CS traffic isabout to be sent on Abis interface to the cell on the related TRX timeslot.Note:This counter does not take into account the 48.058 IMMEDIATE ASSIGNCOMMAND messages sent for PS traffic.


Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 99 / 1256


3.1.1.1.1.3 C8c - NB_CHAN_REQD

Long Name NB_CHAN_REQD

Definition RACH load: number of 48.058 CHANNEL REQUIRED received via theselected cell.All the CHANNEL REQUIRED messages are counted whateverthe Establishment Cause is.

Trigger condition Whenever a 48.058 CHANNEL REQUIRED message (either for PS traffic or forCS traffic) is received on Abis interface from the cell on the related TRX timeslot.


Sub Domain 2 CCCH

Sub Domain 3 –





100 / 1256 3BK 21255 AAAA PCZZA Ed.07


3.1.1.1.1.4 C8d - NB_IMM_ASS_REJ

Long Name NB_IMM_ASS_REJ

Definition Number of 48.058 CHANNEL REQUIRED received while no SDCCH can beallocated by the BSC (congestion), i.e. the number of 44.018IMMEDIATEASSIGNMENT REJECT sent to the MS via the selected cell.

Trigger condition Whenever a 48.058 IMMEDIATE ASSIGNMENT COMMAND message isabout to be sent on Abis interface to the cell on the related TRX timeslot witha "Full Immediate Assignment" Info Element containing a 44.018 IMMEDIATEASSIGNMENT REJECT message.Note: This counter only applies to CS traffic.


Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 101 / 1256


102 / 1256 3BK 21255 AAAA PCZZA Ed.07

4 BSC-TYPE 4 - Resource usage on SDCCH channel measurements

4 BSC-TYPE 4 - Resource usage on SDCCH channelmeasurements

3BK 21255 AAAA PCZZA Ed.07 103 / 1256



4.1.1 Channel

4.1.1.1 SDCCH

4.1.1.1.1 Usage

4.1.1.1.1.1 C39 - NB_TIMES_SDCCH_BUSY

Long Name NB_TIMES_SDCCH_BUSY

Definition Number of times the SDCCH sub-channels belonging to the radio timeslot arebusy.

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent to aCELL to activate an SDCCH Sub-channel on the related TRX timeslot.


Sub Domain 2 SDCCH

Sub Domain 3 Usage


Type Name Resource usage on SDCCH channel measurements

Type Definition Set of counters related to the usage of the SDCCH channel


104 / 1256 3BK 21255 AAAA PCZZA Ed.07


4.2 Traffic Load

4.2.1 Channel

4.2.1.1 SDCCH

4.2.1.1.1 –

4.2.1.1.1.1 C40 - TIME_SDCCH_BUSY

Long Name TIME_SDCCH_BUSY

Definition Cumulated time during which the SDCCH sub-channels belonging to the relatedstatic or dynamic SDCCH timeslot are busy.

Trigger condition For the related static or dynamic SDCCH timeslot, the counter cumulates, overthe Accumulation Period, all time unit during which a SDCCH sub-channel isbusy.For each SDCCH allocation of the sub-channel:1) The counter starts beingincremented after the sending of the 48.058 CHANNEL ACTIVATION messageconcerning an SDCCH sub-channel on the related TRX timeslot.2) Thecounter stops being incremented after the reception of a 48.058 RF CHANNELRELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACKtwice (supervising 48.058 RF CHANNEL RELEASE message) concerning theSDCCH sub-channel previously activated on the related static or dynamicSDCCH timeslot.Example;Let us consider that on a given static SDCCH/8timeslot,- SDCCH sub-channel 1 has been busy for 10 s,- SDCCH sub-channel2 has been busy for 20 s,- SDCCH sub-channel n (with 3 <= n <= 8) has notbeen busy at all.Then, at the expiry of the reporting period, the value reportedby this counter is 10 + 20 = 30 s.


Sub Domain 2 SDCCH

Sub Domain 3 –


Type Name Resource usage on SDCCH channel measurements

Type Definition Set of counters related to the usage of the SDCCH channel


3BK 21255 AAAA PCZZA Ed.07 105 / 1256


106 / 1256 3BK 21255 AAAA PCZZA Ed.07

5 BSC-TYPE 5 - Resource usage on TCH channel measurements

5 BSC-TYPE 5 - Resource usage on TCH channelmeasurements

3BK 21255 AAAA PCZZA Ed.07 107 / 1256



5.1.1 Channel

5.1.1.1 TCH

5.1.1.1.1 Usage

5.1.1.1.1.1 C370a - NB_TCH_FR_ALLOC

Long Name NB_TCH_FR_ALLOC

Definition Number of times a TCH radio timeslot or a dynamic SDCCH/8 timeslot isallocated in FR usage, for normal assignment, for DTM assignment or handover,in traffic or in signaling mode.

Trigger condition Whenever a 48.058CHANNEL_ACTIVATION message is about to be sent tothe cell to activate a full rate TCH channel for normal assignment, for DTMassignment or handover, in traffic or in signaling mode.


Sub Domain 2 TCH

Sub Domain 3 Usage


Type Name Resource usage on TCH channel measurements

Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)


108 / 1256 3BK 21255 AAAA PCZZA Ed.07


5.1.1.1.1.2 C370b - NB_TCH_HR_ALLOC

Long Name NB_TCH_HR_ALLOC

Definition Number of times a TCH radio timeslot or a dynamic SDCCH/8 timeslot isallocated in HR usage (i.e. the upper or lower HR sub-channel of the radiotimeslot is allocated), for normal assignment or handover.

Trigger condition Whenever a CHANNEL_ACTIVATION message is about to be sent to thecell to activate a half rate TCH subchannel (either upper or lower) for normalassignment or handover.


Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 109 / 1256


5.2 Traffic Load

5.2.1 Channel

5.2.1.1 TCH

5.2.1.1.1 –

5.2.1.1.1.1 C380a - TIME_FR_TCH_BUSY

Long Name TIME_FR_TCH_BUSY

Definition Time (in seconds) during which a TCH radio timeslot or a dynamic SDCCH/8timeslot in FR usage (in traffic or in signaling mode) is busy.

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all unittimes during which the TCH FR channel is busy.For each channel allocation:1)The counter starts being incremented after the sending of the 48.058 CHANNELACTIVATION message to the cell concerning a full rate TCH channel (intraffic or in signaling mode) for the related TRX timeslot.2) The counter stopsbeing incremented after the reception of a 48.058 RF CHANNEL RELEASEACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after thesending of the 48.058 RF CHANNEL RELEASE message) concerning the TCHchannel previously activated on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –





110 / 1256 3BK 21255 AAAA PCZZA Ed.07


5.2.1.1.1.2 C380b - TIME_HR_TCH_BUSY

Long Name TIME_HR_TCH_BUSY

Definition Time during which a TCH radio timeslot or a dynamic SDCCH/8 timeslot inHR usage is busy.

Trigger condition The counter cumulates, over the Accumulation Period, per half radio timeslot,all unit times during which the TCH HR channel (or the dynamic SDCCH/8timeslot) is busy. Both "HR timeslots" are counted independently.For eachchannel allocation:1) The counter starts being incremented after the sending ofthe 48.058 CHANNEL ACTIVATION message concerning a dynamic SDCCH/8timeslot or an half rate TCH sub-channel mapped either on the upper half or thelower half of the related TRX timeslot.2) The counter stops being incrementedwhen no HR sub-channel is active anymore on the related TRX channel.Thisis after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGEmessage or the expiry of timer T_RCR_ACK twice (after the sending of the48.058 RF CHANNEL RELEASE message) or the BSC internal radio resourcerelease due to any BSS problem concerning the last HR TCH channel (or thedynamic SDCCH/8 timeslot) which was active on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 111 / 1256


5.2.1.1.1.3 C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS

Long Name TIME_FR_TCH_BUSY_BY_MULTIBAND_MS

Definition Time (in seconds) during which the TCH radio timeslot or the dynamic SDCCH/8timeslot in FR usage (in traffic or in signaling mode) is busy by a multiband mobilestation.A MS is considered as multiband if it supports:- the P-GSM (or E-GSMor R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDSparameter is set to "GSM900 and DCS1800 bands", or,- the GSM850 andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to"GSM850 and DCS1800 bands", or,- the GSM850 and the DCS1900 bands ifthe PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot,all unit times during which the TCH FR channel (or the dynamic SDCCH/8timeslot) is busy (in traffic or in signaling mode).For each channel allocation:1) The counter starts being incremented after the sending of the 48.058CHANNEL ACTIVATION message to the cell concerning : - a full rateTCH channel (or the dynamic SDCCH/8 timeslot) for the related TRXtimeslot- a mobile which has sent a 44.018 CLASSMARK CHANGEmessage with a "Mobile Station Classmark 3" Information Element fieldspecifying that the MS supports:- the P-GSM (or E-GSM or R-GSM) andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is setto "GSM900 and DCS1800 bands", or,- the GSM850 and the DCS1800bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850and DCS1800 bands", or,- the GSM850 and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".2) The counter stops being incremented after the reception of a 48.058RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timerT_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE.


Sub Domain 2 TCH

Sub Domain 3 –





112 / 1256 3BK 21255 AAAA PCZZA Ed.07


5.2.1.1.1.4 C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS

Long Name TIME_HR_TCH_BUSY_BY_MULTIBAND_MS

Definition Time during which the TCH radio timeslot or the dynamic SDCCH/8 timeslotin HR usage is busy by a multiband mobile station. A TCH radio timeslot (or adynamic SDCCH/8 timeslot) in HR usage is said busy by a multiband mobilestation when one or two HR sub-channels are busy by a multiband mobilestation.A MS is considered as multiband if it supports:- the P-GSM (or E-GSMor R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDSparameter is set to "GSM900 and DCS1800 bands", or,- the GSM850 andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to"GSM850 and DCS1800 bands", or,- the GSM850 and the DCS1900 bands ifthe PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".

Trigger condition The counter cumulates, over the Accumulation Period, per radio timeslot,all unit times during which the TCH HR channel (or the dynamic SDCCH/8timeslot) is busy.For each channel allocation:1) The counter starts beingincremented after the sending of the 48.058 CHANNEL ACTIVATION messageconcerning : - an half rate TCH channel (or a dynamic SDCC/8 timeslot)mapped either on the upper half or the lower half of the related TRX timeslot.-a mobile which has sent a 44.018 CLASSMARK CHANGE message witha "Mobile Station Classmark 3" Information Element field specifying that itis a multiband MS. the MS supports:- the P-GSM (or E-GSM or R-GSM)and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter isset to "GSM900 and DCS1800 bands", or,- the GSM850 and the DCS1800bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850and DCS1800 bands", or,- the GSM850 and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".2) The counter stops being incremented when no HR sub-channel (or thedynamic SDCCH/8 timeslot) concerning a multiband mobile is active anymoreon the related TRX channel.This is after the reception of a 48.058 RF CHANNELRELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice(after the sending of the 48.058 RF CHANNEL RELEASE message) or the BSCinternal radio resource release due to any BSS problem, concerning the last HRTCH channel (or the dynamic SDCCH/8 timeslot) related to a multiband mobile.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 113 / 1256


114 / 1256 3BK 21255 AAAA PCZZA Ed.07

6 BSC-TYPE 6 - TCH handover measurements


3BK 21255 AAAA PCZZA Ed.07 115 / 1256


6.1 Handover

6.1.1 SDCCH+TCH

6.1.1.1 Cause

6.1.1.1.1 –

6.1.1.1.1.1 C440 - NB_TCH_HO_ATPT_23_TrafHandover

Long Name NB_TCH_HO_ATPT_23_TrafHandover

Definition MC440=C440, Number of inter-cell internal or external handover attempts, withthe cause 23: "traffic handover" on a TCH channel (in HR or FR usage).

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 23. This counter is incremented in the serving cell.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH+TCH

Sub Domain 2 Cause

Sub Domain 3 –


Type Name TCH handover measurements

Type Definition Set of counters related to the TCH handover procedure. The counters areprovided per handover category : incoming and outgoing, internal (inter-cell andintra-cell) and external. The handover causes are also provided.


116 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2 TCH

6.1.2.1 Cause

6.1.2.1.1 –

6.1.2.1.1.1 C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover

Long Name NB_TCH_HO_ATPT_24_GenCaptureHandover

Definition Number of inter-cell internal or external handover attempts, with the cause 24:"general capture handover" on a TCH channel (in HR or FR usage).


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 117 / 1256


6.1.2.1.1.2 C447 - NB_TCH_HO_ATPT_26_BadQualHR

Long Name NB_TCH_HO_ATPT_26_BadQualHR

Definition Number of intracell handover attempts, with the cause 26: "HR to FR channeladaptation due to bad radio quality" on a TCH channel.

Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTSbecause of cause 26 on TCH.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





118 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.3 C448 - NB_TCH_HO_ATPT_27_GoodQualFR

Long Name NB_TCH_HO_ATPT_27_GoodQualFR

Definition Number of intracell handover attempts, with the cause 27: "FR to HR channeladaptation due to good radio quality" on a TCH channel.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 119 / 1256


6.1.2.1.1.4 C449 - NB_TCH_HO_ATPT_28_FastTraffic

Long Name NB_TCH_HO_ATPT_28_FastTraffic

Definition Number of handover attempts, with the cause 28 (Fast Traffic Handover).

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 28 on TCH. This counter is incremented in the serving cell.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





120 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.5 C450 - NB_TCH_HO_ATPT_22_TooShortDistance

Long Name NB_TCH_HO_ATPT_22_TooShortDistance

Definition Number of inter-cell internal or external handovers attempts, with cause 22: "tooshort MS-BTS distance" on a TCH channel (in HR or FR usage). Only the outerzones of extended cells are concerned by this counter.

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the mobile via the BTSbecause of cause 22 on TCH. This counter is incremented in the servingcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 121 / 1256


6.1.2.1.1.6 C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES

Long Name NB_TCH_HO_ALLOC_EMERGENCY_PRES

Definition Number of high priority TCH requests served when the number of free TCHtimeslots is less than or equal to NUM_TCH_EGNCY_HO.

Trigger condition The counter is incremented on the serving cell whenever the 48.058 CHANNELACTIVATION message allocating a TCH channel is sent and the followingtwo conditions are both fulfilled:1) the TCH is allocated to serve i) an internalhandover Cause 2, 3, 4, 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 22, 27, or, ii) anexternal handover Cause "Uplink quality", "Uplink strength", "Downlink quality","Downlink strength", "Distance", or iii) a normal assignment or an externalhandover with the preemption indicator set (i.e. Preemption Capability Indicator= 1 and EN_TCH_PREEMPT = Enable).2) the number of free TCH timeslotsis less than or equal to NUM_TCH_EGNCY_HO.Note 1: This counter countsboth inter-PLMN and intra-PLMN handover events.Note 2: The HMI name of theparameter NUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





122 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.7 C461 - NB_TCH_HO_ATPT_29_TFO

Long Name NB_TCH_HO_ATPT_29_TFO

Definition Number of intra-cell handover - attempts, with the cause 29 (TFO mismatchresolution, TFO optimisation).MC461 = C461


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 123 / 1256


6.1.2.1.1.8 C470 - NB_TCH_HO_ATPT_2_TooLowQualUp

Long Name NB_TCH_HO_ATPT_2_TooLowQualUp

Definition Number of inter-cell internal or external handover attempts, with cause 2: "uplinkquality too low" on a TCH channel (in HR or FR usage). This counter takes intoaccount handovers from TCH in traffic or in signaling mode.

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 2. This counter is incremented in the serving cell,Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





124 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.9 C471 - NB_TCH_HO_ATPT_3_TooLowLevUp

Long Name NB_TCH_HO_ATPT_3_TooLowLevUp

Definition Number of inter-cell internal or external handover attempts, with cause 2: "uplinkquality too low" on a TCH channel (in HR or FR usage). This counter takes intoaccount handovers from TCH in traffic or in signaling mode.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 125 / 1256


6.1.2.1.1.10 C472 - NB_TCH_HO_ATPT_4_TooLowQualDown

Long Name NB_TCH_HO_ATPT_4_TooLowQualDown

Definition Number of inter-cell internal or external handover attempts, with cause 4:"downlink quality too low" on a TCH channel (in HR or FR usage). This countertakes into account handovers from TCH in traffic or in signaling mode.

Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 4. This counter is incremented in the serving cell.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





126 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.11 C473 - NB_TCH_HO_ATPT_5_TooLowLevDown

Long Name NB_TCH_HO_ATPT_5_TooLowLevDown

Definition Number of inter-cell internal or external handover attempts, with cause 5:"downlink level too low" on a TCH channel (in HR or FR usage). This countertakes into account handovers from TCH in traffic or in signaling mode.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 127 / 1256


6.1.2.1.1.12 C474 - NB_TCH_HO_ATPT_6_TooLongDistance

Long Name NB_TCH_HO_ATPT_6_TooLongDistance

Definition Number of inter-cell internal or external handover attempts, with cause 6:"MS-BTS distance too long" on a TCH channel (in HR or FR usage). Thiscounter takes into account handovers from TCH in traffic or in signaling mode.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





128 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.13 C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp

Long Name NB_TCH_HO_ATPT_15_TooHighLevInterfUp

Definition Number of intra-cell handover attempts, with cause 15: "too high levelinterference on uplink" on a TCH channel (in HR or FR usage). This countertakes into account handovers from TCH in traffic or in signaling mode.

Trigger condition Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTSbecause of cause 15.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 129 / 1256


6.1.2.1.1.14 C477 - NB_TCH_HO_ATPT_16_TooHighLevInterfDown

Long Name NB_TCH_HO_ATPT_16_TooHighLevInterfDown

Definition Number of intra-cell handover attempts, with cause 16: "too high levelinterference on downlink" on a TCH channel (in HR or FR usage). This countertakes into account handovers from TCH in traffic or in signaling mode.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





130 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.15 C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg

Long Name NB_TCH_HO_ATPT_12_TooLowPowBudg

Definition Number of inter-cell internal or external handover attempts, with cause 12: "toolow power budget" on a TCH channel (in FR or FR usage). This counter takesinto account handovers from TCH in traffic or in signaling mode.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 131 / 1256


6.1.2.1.1.16 C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand

Long Name NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand

Definition Number of inter-cell internal or external handover attempts, with cause 21: "highlevel in neighbour cell in the preferred band" on a TCH channel (in HR or FRusage). This counter is related to multiband.

Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 21 on TCH. This counter is incremented in the servingcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





132 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.17 C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell

Long Name NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell

Definition Number of inter-cell internal or external handover attempts, with cause 7:"several consecutive bad SACCH frames received in a micro cell" on a TCHchannel (in HR or FR usage). This counter takes into account handoversfrom TCH in traffic or in signaling mode. This counter is related to micro cellenvironment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 133 / 1256


6.1.2.1.1.18 C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell

Long Name NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell

Definition Number of inter-cell internal or external handovers attempts, with cause 17:"too low level on the uplink in a microcell compared to a high threshold" on aTCH channel (in HR or FR usage). This counter takes into account handoversfrom TCH in traffic or in signaling mode.This counter is related to micro cellenvironment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





134 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.19 C585e - NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell

Long Name NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell

Definition Number of inter-cell internal or external handovers attempts, with cause 18: "toolow level on the downlink in a microcell compared to a high threshold" on aTCH channel (in HR or FR usage). This counter takes into account handoversfrom TCH in traffic or in signaling mode.This counter is related to micro cellenvironment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 135 / 1256


6.1.2.1.1.20 C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS

Long Name NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS

Definition Number of inter-cell internal or external handover attempts, with cause 14: "highlevel in neighbour lower layer for slow mobile" on a TCH channel (in HR or FRusage). This counter is related to micro cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





136 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.21 C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone

Long Name NB_TCH_HO_ATPT_10_TooLowLevUpInZone

Definition Number of intra-cell handover attempts, with cause 10 "Inner zone uplink leveltoo low" on TCH channel (in HR or FR usage). This counter is related toconcentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 137 / 1256


6.1.2.1.1.22 C586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone

Long Name NB_TCH_HO_ATPT_11_TooLowLevDownInZone

Definition Number of intra-cell handover attempts, with cause 11: "Inner zone downlinklevel too low" on TCH channel (in HR or FR usage). This counter is related toconcentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





138 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.1.1.23 C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone

Long Name NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone

Definition Number of intra-cell handover attempts, with cause 13: "Outer zone uplink anddownlink levels too high" on TCH channel (in HR or FR usage). This counter isrelated to concentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 139 / 1256


6.1.2.1.1.24 C75 - NB_TCH_HO_MSC_TRIG

Long Name NB_TCH_HO_MSC_TRIG

Definition Number of external handovers triggered by the MSC but not required by the BSS.

Trigger condition Whenever a 48.008 HANDOVER COMMAND message is received on Ainterface from the MSC and timer T_HO_REQ_LOST is not running.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.Note: Thiscounter does not count hantover to UMTS

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





140 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.2 Incoming External

6.1.2.2.1 –

6.1.2.2.1.1 C220 - NB_INC_EXT_TCH_HO_REQ

Long Name NB_INC_EXT_TCH_HO_REQ

Definition Number of incoming external TCH (in HR or FR usage) handover requests.

Trigger condition Whenever 48.008HANDOVER REQUEST received by the target BSC for thetarget cell on TCH.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 TCH

Sub Domain 2 Incoming External

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 141 / 1256


6.1.2.2.1.2 C221 - NB_INC_EXT_TCH_HO_ATPT

Long Name NB_INC_EXT_TCH_HO_ATPT

Definition Number of incoming external TCH (in HR or FR usage) handover attempts.

Trigger condition Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSCcontaining the 44.018HANDOVER COMMAND towards the target cell onTCH.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 TCH


Sub Domain 3 –





142 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.2.1.3 C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to A-traffic-channel status mismatch between the BSC and the MSC.

Trigger condition 1) Whenever a 48.008 HANDOVER FAILURE message with a cause value of"requested terrestrial resource unavailable" is sent on A interface from the targetBSC to the MSC.2) Whenever a 48.008 HANDOVER FAILURE message witha cause value of "terrestrial circuit already allocated" is sent on A interfacefrom the target BSC to the MSC.3) Whenever a 48.008 HANDOVER FAILUREmessage with a cause value of "BSS not equipped" is sent on A interface fromthe target BSC to the MSC.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 143 / 1256


6.1.2.2.1.4 C42 - NB_INC_EXT_TCH_HO_SUCC

Long Name NB_INC_EXT_TCH_HO_SUCC

Definition Number of incoming external TCH (in HR or FR usage) handover successes.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel that is involved in an externalTCH handover.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 TCH


Sub Domain 3 –





144 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.2.1.5 C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS

Definition Number of incoming external TCH (in HR or FR usage) handover -executionfailures due to MS access problem.

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with acause value of "handover access failure" is received on Abis interface from thetarget cell for a TCH channel during an external TCH handover.2) Whenever thetimer supervising the handover procedure on the target cell (T9113), expiresduring an external TCH handover.3) Whenever a 48.008 CLEAR COMMANDwith a cause value of "radio interface failure - reversion to old channel" isreceived on A interface on the target BSC from the MSC during an externalTCH handover.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 145 / 1256


6.1.2.2.1.6 C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to congestion (C541a), or A-traffic-channel status mismatchbetween the BSC and the MSC (C41b).

Trigger condition Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





146 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.2.1.7 C541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to congestion.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of"no radio resource available" is sent on A interface from the target BSC tothe MSC during an external TCH handover.Note 1: This counter counts bothinter-PLMN and intra-PLMN handover events.Note 2: In MX BSC, this counter isincremented whenever a 48.008 HANDOVER FAILURE message with a causevalue of "no radio resource available" is sent due to the TCH processing capacityof CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. Inthis case, MC926 is also incremented by one.Note 3: In IP mode, this counteris increased by 1 if:- the cell mapped on a BTS is in IP congestion status;- orthe TCH processing capacity of AbisBTSGroup reaches the limit defined by theNB_MAX_ACTIVE_TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 147 / 1256


6.1.2.3 Incoming Internal

6.1.2.3.1 –

6.1.2.3.1.1 C230 - NB_INC_INT_TCH_HO_REQ

Long Name NB_INC_INT_TCH_HO_REQ

Definition Number of incoming internal inter cell TCH (in HR or FR usage) handoverrequests.

Trigger condition Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell TCH handover.

Sub Domain 1 TCH

Sub Domain 2 Incoming Internal

Sub Domain 3 –





148 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.3.1.2 C231 - NB_INC_INT_TCH_HO_ATPT

Long Name NB_INC_INT_TCH_HO_ATPT

Definition Number of incoming internal inter cell TCH (in HR or FR usage) handoverattempts.

Trigger condition 44.018HANDOVER COMMAND is sent to the serving BTS for internal inter cellTCH handover. However, the counter is incremented in the TARGET cell, basedon the target cell ID indicated by the HO Command message,

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 149 / 1256


6.1.2.3.1.3 C52 - NB_INC_INT_TCH_HO_SUCC

Long Name NB_INC_INT_TCH_HO_SUCC

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handoversuccesses.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel that is involved in an internalinter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





150 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.3.1.4 C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover-execution failures due to MS access problem; the mobile either reverts or doesnot to the old channel.

Trigger condition Whenever the timer supervising the handover procedure (T3103) expires duringan internal inter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 151 / 1256


6.1.2.3.1.5 C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover-preparation failures due to congestion.

Trigger condition Whenever an internal inter-cell TCH handover cannot be performed, becausethe target cell is congested (no free TCH channel).Note 1: In MX BSC, thiscounter is incremented whenever an internal inter-cell TCH handover cannotbe performed due to the TCH processing capacity of CCP reaches the limitdefined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is alsoincremented by one.Note 2: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

Sub Domain 1 TCH


Sub Domain 3 –





152 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.4 Intra

6.1.2.4.1 –

6.1.2.4.1.1 C270 - NB_INTRA_TCH_HO_REQ

Long Name NB_INTRA_TCH_HO_REQ

Definition Number of intra cell TCH (in HR or FR usage) handover requests. This countertakes into account handovers from TCH in traffic or in signaling mode. It doesnot take into account DTM Assignments.

Trigger condition Whenever the BSC process responsible for the handover procedure starts anintra cell TCH handover procedure.

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 153 / 1256


6.1.2.4.1.2 C271 - NB_INTRA_TCH_HO_ATPT

Long Name NB_INTRA_TCH_HO_ATPT

Definition Number of intra cell TCH (in HR or FR usage) handover attempts. This countertakes into account handovers from TCH in traffic or in signaling mode. It doesnot take into account DTM Assignments.

Trigger condition 44.018 ASSIGNMENT COMMAND is sent to the BTS for intra cell handoveron TCH.

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





154 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.4.1.3 C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of intra-cell TCH (in HR or FR usage) handover -preparation failuresdue to congestion. This counter takes into account handovers from TCH intraffic or in signaling mode. It does not take into account DTM Assignments.

Trigger condition Whenever a internal intra-cell TCH handover cannot be performed, becausethere is no free TCH channel to serve the handover.Note 1: In MX BSC,this counter is incremented whenever an intra-cell TCH handover cannot beperformed due to the TCH processing capacity of CCP reaches the limitdefined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is alsoincremented by one.Note 2: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 155 / 1256


6.1.2.4.1.4 C62 - NB_INTRA_TCH_HO_SUCC

Long Name NB_INTRA_TCH_HO_SUCC

Definition Number of intra-cell TCH (in HR or FR usage) handover successes. Thiscounter takes into account handovers from TCH in traffic or in signaling mode. Itdoes not take into account DTM Assignments.

Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abisinterface on the target channel for a TCH channel that is involved in an internalintra-cell TCH handover.

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





156 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.4.1.5 C63 - NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV

Long Name NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV

Definition Number of intra-cell TCH (in HR or FR usage) handover execution failuresdue MS access problem; the mobile is lost. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.

Trigger condition Whenever the timer supervising the handover procedure (T3107) expires duringan internal intra-cell.

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 157 / 1256


6.1.2.4.1.6 C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV

Long Name NB_INTRA_TCH_HO_EXEC_FAIL_REV

Definition Number of intra-cell TCH (in HR or FR usage) handover -execution failures dueto MS access problem with reversion of the mobile to the old channel. Thiscounter takes into account handovers from TCH in traffic or in signaling mode. Itdoes not take into account DTM Assignments.

Trigger condition Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abisinterface on the serving channel, during an internal intra-cell TCH handover.

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





158 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.5 Outgoing External

6.1.2.5.1 –

6.1.2.5.1.1 C45a - NB_OUT_EXT_TCH_REAL_HO_REQ

Long Name NB_OUT_EXT_TCH_REAL_HO_REQ

Definition Number of outgoing external TCH (in HR or FR usage) handover requests. Thiscounter takes into account handovers from TCH in traffic or in signaling mode.

Trigger condition Whenever a 48.008 HANDOVER REQUIRED message with the cellidentification discriminator set to a value identifying a GSM handover is senton A interface to the MSC for a TCH handover towards a 2G cell. If morethan one 48.008 HANDOVER REQUIRED is sent in the frame of the sameHandover procedure, the counter is incremented only once.48.008 HANDOVERREQUIRED is sent in following situations:1) An external handover alarm hasbeen raised, with corresponding list of candidate cells.2) The list of candidatecells for the current alarm has been updated.Note: This counter counts bothinter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH

Sub Domain 2 Outgoing External

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 159 / 1256


6.1.2.5.1.2 C46 - NB_OUT_EXT_TCH_HO_SUCC

Long Name NB_OUT_EXT_TCH_HO_SUCC

Definition Number of outgoing external TCH (in HR or FR usage) handover successes.This counter takes into account handovers from TCH in traffic or in signalingmode.

Trigger condition External TCH handover in the following cases:1/ a 48.008 CLEAR COMMANDmessage with a cause value of "handover successful" is received on A interfaceon the serving BSC from the MSC.2/ 48.008 CLEAR COMMAND (cause="normal event/call control") is received while T8 is running.Note: This countercounts both inter-PLMN and intra-PLMN handover events.Note: This counterdoesnt count hantover to UMTS

Sub Domain 1 TCH


Sub Domain 3 –





160 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.5.1.3 C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV

Long Name NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV

Definition Number of outgoing external TCH (in HR or FR usage) handover -executionfailures due to MS access problem with reversion of the mobile to the oldchannel. This counter takes into account handovers from TCH in traffic or insignaling mode.

Trigger condition Whenever a 44.018 HANDOVER FAILURE message is received on Abisinterface from the serving cell , during an external TCH handover.Note 1: Thiscounter counts both inter-PLMN and intra-PLMN handover events.Note 2: Thiscounter does not count hantover to UMTS.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 161 / 1256


6.1.2.5.1.4 C48 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV

Definition Number of outgoing external TCH (in HR or FR usage) handover executionfailures due to MS access problem without reversion of the mobile to the oldchannel (call drop). This counter takes into account handovers from TCH intraffic or in signaling mode.

Trigger condition Whenever the timer supervising the handover procedure on the serving cell(T8), expires during an external TCH handover, except if a 48.008 CLEARCOMMAND with "normal event/call control" cause was received from the MSC,leading to a normal call release. In such a case, the handover is consideredas successful.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.Note: This counter does not count handover to UMTS

Sub Domain 1 TCH


Sub Domain 3 –





162 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.5.1.5 C50 - NB_OUT_EXT_TCH_HO_ATPT

Long Name NB_OUT_EXT_TCH_HO_ATPT

Definition Number of outgoing external TCH (in HR or FR usage) handover attempts. Thiscounter takes into account handovers from TCH in traffic or in signaling mode.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent onAbis interface on the serving channel, during an external TCH handoverprocedure.Note 1: This counter counts both inter-PLMN and intra-PLMNhandover events.Note 2: This counter does not count handover to UMTS

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 163 / 1256


6.1.2.6 Outgoing Internal

6.1.2.6.1 –

6.1.2.6.1.1 C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ

Long Name NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handoverrequests, plus the number of internal directed retries requests, towards theinner zone of a target concentric cell.

Trigger condition Whenever the BSC process responsible for the handover procedure at theserving cell generates an HO alarm towards the inner zone of a target concentriccell for internal inter-cell TCH handover, or for an internal directed retry.

Sub Domain 1 TCH

Sub Domain 2 Outgoing Internal

Sub Domain 3 –





164 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.6.1.2 C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL

Long Name NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover-executions failures, plus the number of internal directed retries -executionfailures due to MS access problem, towards the inner zone of a target concentriccell.This counter permits to tune the EN_BETTER_ZONE_HO parameter.

Trigger condition 1) Receipts of 44.018HANDOVER FAILURE (cause=radio interface failure,reversion to old channel).2) Timer T3103 expiry (this timer starts upon thesending of 44.018HANDOVER COMMAND and is stopped upon the receiptof 44.018HANDOVER COMPLETE).

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 165 / 1256


6.1.2.6.1.3 C55a - NB_OUT_INT_TCH_HO_REQ

Long Name NB_OUT_INT_TCH_HO_REQ

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handoverrequests. This counter takes into account handovers from TCH in traffic or insignaling mode.

Trigger condition Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





166 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.6.1.4 C56 - NB_OUT_INT_TCH_HO_SUCC

Long Name NB_OUT_INT_TCH_HO_SUCC

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handoversuccesses. This counter takes into account handovers from TCH in traffic or insignaling mode.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell , during an internal inter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 167 / 1256


6.1.2.6.1.5 C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV

Long Name NB_OUT_INT_TCH_HO_EXEC_FAIL_REV

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover-execution failures due to MS access problem with reversion of the mobile tothe old channel. This counter takes into account handovers from TCH in trafficor in signaling mode.

Trigger condition Whenever a 44.018 HANDOVER FAILURE message is received on Abisinterface from the serving cell, during an internal inter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





168 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.1.2.6.1.6 C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover-execution failures due to MS access problem without reversion of the mobileto the old channel (call drop). This counter takes into account handovers fromTCH in traffic or in signaling mode.

Trigger condition Whenever the timer supervising the handover procedure (T3103) expires duringan internal inter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 169 / 1256


6.1.2.6.1.7 C60 - NB_OUT_INT_TCH_HO_ATPT

Long Name NB_OUT_INT_TCH_HO_ATPT

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handoverattempts. This counter takes into account handovers from TCH in traffic or insignaling mode.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface on the serving channel, during an internal inter-cell TCH handoverprocedure.

Sub Domain 1 TCH


Sub Domain 3 –





170 / 1256 3BK 21255 AAAA PCZZA Ed.07


6.2 Traffic Load



6.2.1.1.1 –

6.2.1.1.1.1 C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC

Long Name NB_TCH_NOR_ASS_INNER_ZONE_ALLOC

Definition Number of TCH (in HR or FR usage) normal assignment -whose ressource isallocated in the BSC, in the inner zone of a concentric cell.

Trigger condition Whenever 48.058CHANNEL ACTIVATION is about to be send on Abis toactivate a TCH channel in the inner zone of the concentric cell for any normalassignment.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 171 / 1256


172 / 1256 3BK 21255 AAAA PCZZA Ed.07

7 BSC-TYPE 7 - LapD measurements


3BK 21255 AAAA PCZZA Ed.07 173 / 1256



7.1.1 Interface

7.1.1.1 Abis

7.1.1.1.1 LapD

7.1.1.1.1.1 L1.12 - NB_LAPD_CRC_ERROR

Long Name NB_LAPD_CRC_ERROR

Definition Number of frames received with CRC error on the LapD link.

Trigger condition Whenever the HDLC Formatter handling the Physical LAPD link detects a CRCerror in a received Frame.Note 1: In case of LapD over UDP, this counter ismeaningless and shall always be set to 0.

Sub Domain 1 Interface

Sub Domain 2 Abis

Sub Domain 3 LapD

Measured Object LapD

Type Name LapD measurements

Type Definition Set of counters related to the LapD logical links


174 / 1256 3BK 21255 AAAA PCZZA Ed.07


7.1.1.1.1.2 L1.15 - NB_LAPD_INFO_FRAME_RESENT

Long Name NB_LAPD_INFO_FRAME_RESENT

Definition Number of Information frames re-transmitted on the LapD link.

Trigger condition Whenever an Information Frame is retransmitted on a logical LAPD link.


Sub Domain 2 Abis

Sub Domain 3 LapD





3BK 21255 AAAA PCZZA Ed.07 175 / 1256


7.1.1.1.1.3 L1.17 - NB_LAPD_EST

Long Name NB_LAPD_EST

Definition Number of data link establishment, re-establishment and reset on the LapD link.

Trigger condition 1) Whenever the layer 2 receives a SABME frame in state MF Established orTimer recovery (data link reset initiated by the BTS).2) Whenever the layer2 receives an UA frame in the state Awaiting Establishment (i.e. data linkestablishment, re-establishment or link reset initiated by the BSC).


Sub Domain 2 Abis

Sub Domain 3 LapD





176 / 1256 3BK 21255 AAAA PCZZA Ed.07


7.1.1.1.1.4 L1.18 - TIME_LAPD_CONG

Long Name TIME_LAPD_CONG

Definition Time in seconds during which the LapD link is congested in transmission inthe BSC.

Trigger condition This counter will be incremented with the number of seconds elapsedbetween the reception of L2_CONGESTION_IND and the reception ofL2_END_CONGESTION_IND by the Layer 3 in the BSC


Sub Domain 2 Abis

Sub Domain 3 LapD





3BK 21255 AAAA PCZZA Ed.07 177 / 1256


7.1.1.1.1.5 L1.5 - NB_LAPD_RNR_SENT

Long Name NB_LAPD_RNR_SENT

Definition Number of Receive Not Ready (RNR) frames transmitted on the LapD link.

Trigger condition Whenever an RNR Frame is transmitted on a logical LAPD link.


Sub Domain 2 Abis

Sub Domain 3 LapD





178 / 1256 3BK 21255 AAAA PCZZA Ed.07


7.1.1.1.1.6 L1.6 - NB_LAPD_RNR_REC

Long Name NB_LAPD_RNR_REC

Definition Number of Receive Not Ready (RNR) frames received on the LapD link.

Trigger condition Whenever an RNR Frame is received on a logical LAPD link.


Sub Domain 2 Abis

Sub Domain 3 LapD





3BK 21255 AAAA PCZZA Ed.07 179 / 1256



7.2.1 Interface

7.2.1.1 Abis


7.2.1.1.1.1 L1.16 - TIME_LAPD_UNAVAIL

Long Name TIME_LAPD_UNAVAIL

Definition Time (in seconds) during which the LapD link is unavailable for any cause.

Trigger condition 1) This counter will be incremented with the number of seconds elapsedbetween LAPD layer entities initiation (first DL_ESTABLISH_ REQUESTprimitive sent by Layer 3 to Layer 2 for that logical LAPD link) and receptionof the DL-ESTABLISH-CONFIRM primitive for that logical LAPD link.2) Thiscounter will also be incremented with the number of seconds elapsed betweenreception of the DL-RELEASE-INDICATION primitive and reception of theDL_ESTABLISH-CONFIRM primitive for that logical LAPD link.


Sub Domain 2 Abis






180 / 1256 3BK 21255 AAAA PCZZA Ed.07


7.3 Traffic Load

7.3.1 Interface

7.3.1.1 Abis

7.3.1.1.1 LapD

7.3.1.1.1.1 L1.1 - NB_LAPD_INFO_FRAME_SENT

Long Name NB_LAPD_INFO_FRAME_SENT

Definition Number of Information frames transmitted on the LapD link, excluding there-transmissions.

Trigger condition Whenever an Information Frame is transmitted on a logical LAPD link, which isnot a retransmission of a previous Information Frame.


Sub Domain 2 Abis

Sub Domain 3 LapD





3BK 21255 AAAA PCZZA Ed.07 181 / 1256


7.3.1.1.1.2 L1.2 - NB_LAPD_INFO_FRAME_REC

Long Name NB_LAPD_INFO_FRAME_REC

Definition Number of Information frames received on the LapD link, excluding there-transmissions.

Trigger condition Whenever an Information Frame is received on a logical LAPD link.


Sub Domain 2 Abis

Sub Domain 3 LapD





182 / 1256 3BK 21255 AAAA PCZZA Ed.07

8 BSC-TYPE 8 - X25 measurements


3BK 21255 AAAA PCZZA Ed.07 183 / 1256



8.1.1 Interface

8.1.1.1 OMC-BSC

8.1.1.1.1 X25

8.1.1.1.1.1 X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED

Long Name NB_X25_INC_CALL_ABNORM_CLOSED

Definition Number of incoming X.25 calls that are closed in an abnormal way, as seenby the BSC.

Trigger condition Whenever an incoming X.25 CALL is closed in an abnormal way.


Sub Domain 2 OMC-BSC

Sub Domain 3 X25

Measured Object X25

Type Name X25 measurements

Type Definition Set of counters related to the X25 links OMC-BSC


184 / 1256 3BK 21255 AAAA PCZZA Ed.07


8.1.1.1.1.2 X3.23 - NB_X25_OUT_CALL_ABNORM_CLOSED

Long Name NB_X25_OUT_CALL_ABNORM_CLOSED

Definition Number of outgoing X.25 calls that are closed in an abnormal way, as seenby the BSC.

Trigger condition Whenever an outgoing X.25 CALL is closed in an abnormal way.



Sub Domain 3 X25

Measured Object X25




3BK 21255 AAAA PCZZA Ed.07 185 / 1256


8.2 Traffic Load

8.2.1 Interface

8.2.1.1 OMC-BSC

8.2.1.1.1 X25

8.2.1.1.1.1 X3.20 - NB_X25_INC_CALL_SUCC_CLOSED

Long Name NB_X25_INC_CALL_SUCC_CLOSED

Definition Number of incoming X.25 calls that are successfully closed by the BSC.

Trigger condition Whenever an incoming X.25 CALL is successfully closed.



Sub Domain 3 X25

Measured Object X25




186 / 1256 3BK 21255 AAAA PCZZA Ed.07


8.2.1.1.1.2 X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED

Long Name NB_X25_OUT_CALL_SUCC_CLOSED

Definition Number of outgoing X.25 calls that are successfully closed by the BSC.

Trigger condition Whenever an outgoing X.25 CALL is successfully closed.



Sub Domain 3 X25

Measured Object X25




3BK 21255 AAAA PCZZA Ed.07 187 / 1256


188 / 1256 3BK 21255 AAAA PCZZA Ed.07

9 BSC-TYPE 9 - N7 measurements


3BK 21255 AAAA PCZZA Ed.07 189 / 1256



9.1.1 Interface

9.1.1.1 A

9.1.1.1.1 Layers1-2-3

9.1.1.1.1.1 N1.10 - NB_N7_CHANGEOVER

Long Name NB_N7_CHANGEOVER

Definition Number of changeovers from the primary (observed) N7 SL to anothersecondary one.

Trigger condition Whenever a changeover is made from using the primary signalling link to thesecondary signalling link.


Sub Domain 2 A

Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link

Type Name N7 measurements

Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context,the Link Set and the Route Set are identical.


190 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.2 N1.11 - NB_N7_CHANGEBACK

Long Name NB_N7_CHANGEBACK

Definition Number of changebacks from the secondary (observed) N7 SL to the primaryone.

Trigger condition Whenever a change back is made from using the secondary signalling linkto the primary signalling link.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 191 / 1256


9.1.1.1.1.3 N1.12 - NB_N7_RESTORATION

Long Name NB_N7_RESTORATION

Definition Number of N7 SL restorations (i.e. correctly aligned after a failure).

Trigger condition Whenever the No.7 Signalling channel between the MSC and BSS is correctlyaligned after the removal of a failure condition, this counter will be incremented.


Sub Domain 2 A






192 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.4 N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE

Long Name NB_N7_LINK_FAIL_ANY_CAUSE

Definition Number of N7 SL failures (any reason).

Trigger condition 1) Whenever a No.7 Signalling Link failure is detected due to an abnormalForward Indicator Bit (FIB) being received by the BSS.2) Whenever a No.7Signalling Link failure is detected due to an abnormal Backward SequenceNumber (BSN) being received by the BSS.3) Whenever the timer supervisingthe reception of an acknowledgement message (T7) expires.4) Whenever aNo.7 Signalling Link failure is detected due to an excessive signal unit error ratebeing detected.5) Whenever a No.7 Signalling Link failure is detected due toan excessive duration of Signalling Link congestion.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 193 / 1256


9.1.1.1.1.5 N1.3 - NB_N7_LINK_FAIL_FIB_BSN

Long Name NB_N7_LINK_FAIL_FIB_BSN

Definition Number of Forward Indicator Bits (FIB) and Backward Sequence Number (BSN)on the N7 SL.

Trigger condition 1) Whenever any two Forward Indicator Bit values in 3 concecutive recievedMSUs or fill-in SUs indicate the start of a retransmission when no NACKhas been sent.2) Whenever two Backward Sequence Number values in 3concecutive received MSUs or fill-in SUs are not the same as the previous one orany of the Forward Sequence Number values of SUs in retransmission buffers.


Sub Domain 2 A






194 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.6 N1.4 - NB_N7_LINK_FAIL_T7_EXP

Long Name NB_N7_LINK_FAIL_T7_EXP

Definition Number of N7 SL failures due to non acknowledgment in time.

Trigger condition Whenever the timer supervising the reception of an acknowledgement message(T7) expires.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 195 / 1256


9.1.1.1.1.7 N1.5 - NB_N7_LINK_FAIL_SU_ERROR_RATE

Long Name NB_N7_LINK_FAIL_SU_ERROR_RATE

Definition Number of N7 SL failures due to exessive signal unit error rate.

Trigger condition Whenever a No.7 Signalling Link failure is detected due to an excessive SignalUnit error rate.


Sub Domain 2 A






196 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.8 N1.6 - NB_N7_LINK_FAIL_CONG

Long Name NB_N7_LINK_FAIL_CONG

Definition Number of N7 SL failures due to congestion during an extended period of time.

Trigger condition Whenever a No.7 Signalling Link failure is detected due to an excessive durationof Signalling Link congestion.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 197 / 1256


9.1.1.1.1.9 N1.7 - NB_N7_LINK_FAIL_ALIGNMENT

Long Name NB_N7_LINK_FAIL_ALIGNMENT

Definition Number of N7 SL failures due to expiry of timer supervising the alignment.

Trigger condition Whenever the timer supervising the alignment of the Signalling Link (T2) expires.


Sub Domain 2 A






198 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.10 N1.8 - NB_N7_SU_REC_WITH_ERROR

Long Name NB_N7_SU_REC_WITH_ERROR

Definition Number of Signalling Units received with errors on the N7 SL.

Trigger condition Whenever a Signalling Unit is received which is found to be in error.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 199 / 1256


9.1.1.1.1.11 N1.9 - NB_N7_NEG_ACK_REC

Long Name NB_N7_NEG_ACK_REC

Definition Number of Negative Acknowledgment receieved on the N7 SL.

Trigger condition Whenever a Negative Acknowledgement (NACK) is received.


Sub Domain 2 A






200 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.1.1.1.1.12 N3.10 - NB_N7_MSU_DISC_DUE_CONG

Long Name NB_N7_MSU_DISC_DUE_CONG

Definition Number Message Signalling Units (MSU) discarded due to a message bufferoverflow caused by an extended period of Signalling Link congestion.

Trigger condition Whenever an Message Signalling Unit (MSU) is discarded due to SignallingLink congestion.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 201 / 1256


9.1.1.1.1.13 N3.11 - NB_N7_CONG_WITH_MSU_LOST

Long Name NB_N7_CONG_WITH_MSU_LOST

Definition Number of times one (or more) Message Signalling Units (MSU) are lost dueto congestion on the N7 SL.

Trigger condition Whenever 1 or more MSU's are lost due to congestion on the signalling link.


Sub Domain 2 A






202 / 1256 3BK 21255 AAAA PCZZA Ed.07



9.2.1 Interface

9.2.1.1 A


9.2.1.1.1.1 N1.1 - TIME_N7_ALIGNED

Long Name TIME_N7_ALIGNED

Definition Time (in seconds) during which the N7 SL is correctly aligned.

Trigger condition Whenever the No.7 Signalling channel between the MSC and BSS is correctlyaligned, this counter will be incremented every second.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 203 / 1256


9.2.1.1.1.2 N2.7 - TIME_N7_UNAVAIL_ERROR_SL

Long Name TIME_N7_UNAVAIL_ERROR_SL

Definition Time (in seconds) during which the N7 SL is not correctly aligned due to afault on the N7 SL.

Trigger condition Whenever the No.7 Signalling channel between the MSC and BSS fails, until thetime when the fault has been removed and the link aligned, this counter will beincremented every second.


Sub Domain 2 A






204 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.2.1.1.1.3 N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE

Long Name TIME_N7_UNAVAIL_MSC_PROC_OUTAGE

Definition Time (in seconds) during which the N7 SL is not available due to a remoteMSC processor outage.

Trigger condition Whenever the MSC indicates to the BSS that it is unable to process signallingtraffic due to an outage, this counter will be incremented every second.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 205 / 1256


9.2.1.1.1.4 N3.7 - TIME_N7_UNAVAIL_CONG

Long Name TIME_N7_UNAVAIL_CONG

Definition Time (in seconds) during which the N7 SL is not available due to congestion.

Trigger condition Whenever the signalling link is congested, this counter will be incrementedevery second.


Sub Domain 2 A






206 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.2.1.1.1.5 N4.2 - TIME_N7_UNAVAIL_LINK_SET

Long Name TIME_N7_UNAVAIL_LINK_SET

Definition Time (in seconds) during which the Link Set towards the MSC is not availableon the N7.

Trigger condition Whenever the Link Set towards the MSC is unavailable, this counter will beupdated every second.


Sub Domain 2 A


Measured Object N7 Link Set




3BK 21255 AAAA PCZZA Ed.07 207 / 1256


9.3 Traffic Load

9.3.1 Interface

9.3.1.1 A

9.3.1.1.1 Layers1-2-3

9.3.1.1.1.1 N3.1 - NB_N7_SIF_SIO_SENT

Long Name NB_N7_SIF_SIO_SENT

Definition Number of octets of Signalling Information (SIF) and Service Information Octets(SIO) transmitted on the N7 SL.

Trigger condition When sending an MSU, this counter is incremented by the length of the SIF, plusone for the SIO octet.


Sub Domain 2 A






208 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.3.1.1.1.2 N3.2 - NB_N7_OCTETS_RESENT

Long Name NB_N7_OCTETS_RESENT

Definition Number of octets re-transmitted on the N7 SL.

Trigger condition Whenever an octet has to be re-transmitted.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 209 / 1256


9.3.1.1.1.3 N3.3 - NB_N7_MSU_SENT

Long Name NB_N7_MSU_SENT

Definition Number of Message Signalling Units (MSU) transmitted on the N7 SL.

Trigger condition Whenever a Message Signalling Unit (MSU) is transmitted.


Sub Domain 2 A






210 / 1256 3BK 21255 AAAA PCZZA Ed.07


9.3.1.1.1.4 N3.4 - NB_N7_SIF_SIO_REC

Long Name NB_N7_SIF_SIO_REC

Definition Number of octets of Signalling Information Field (SIF) and Service InformationOctets (SIO) received on the N7 SL.

Trigger condition 1) Whenever an octet of the Signalling Information Field (SIF) is received.2)Whenever a Service Information Octet is received.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 211 / 1256


9.3.1.1.1.5 N3.5 - NB_N7_MSU_REC

Long Name NB_N7_MSU_REC

Definition Number of Message Signalling Units (MSU) received on the N7 SL.

Trigger condition Whenever a Message Signalling Unit (MSU) is received.


Sub Domain 2 A






212 / 1256 3BK 21255 AAAA PCZZA Ed.07

10 BSC-TYPE 18 - A interface measurements


3BK 21255 AAAA PCZZA Ed.07 213 / 1256



10.1.1 Interface

10.1.1.1 A

10.1.1.1.1 BSSAP

10.1.1.1.1.1 C180a - NB_N7_CLEAR_REQ_RadioIntMessFail

Long Name NB_N7_CLEAR_REQ_RadioIntMessFail

Definition Number of 48.008CLEAR REQUEST (cause="radio interface message failure")sent to the MSC.

Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of "radiointerface message failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC

Type Name A interface measurements

Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and08.08ASSIGNMENT FAILURE


214 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.2 C180b - NB_N7_CLEAR_REQ_O&Minterv

Long Name NB_N7_CLEAR_REQ_O&Minterv

Definition Number of 48.008CLEAR REQUEST (cause="O&M intervention") sent to theMSC.

Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of "O&Mintervention" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 215 / 1256


10.1.1.1.1.3 C180c - NB_N7_CLEAR_REQ_EquipFail

Long Name NB_N7_CLEAR_REQ_EquipFail

Definition Number of 48.008CLEAR REQUEST (cause="equipment failure") sent to theMSC.

Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of"equipment failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




216 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.4 C180d - NB_N7_CLEAR_REQ_RadioIntFail

Long Name NB_N7_CLEAR_REQ_RadioIntFail

Definition Number of 48.008CLEAR REQUEST (cause="radio interface failure") sent tothe MSC.

Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of "radiointerface failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 217 / 1256


10.1.1.1.1.5 C180e - NB_N7_CLEAR_REQ_NoRadioResAvail

Long Name NB_N7_CLEAR_REQ_NoRadioResAvail

Definition Number of 48.008CLEAR REQUEST (cause="no radio resource available")sent to the MSC.

Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of "no radioresource available" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




218 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.6 C181a - NB_N7_ASS_FAIL_RadioIntMessFail

Long Name NB_N7_ASS_FAIL_RadioIntMessFail

Definition Number of 48.008ASSIGNMENT FAILURE (cause="radio interface messagefailure") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"radio interface message failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 219 / 1256


10.1.1.1.1.7 C181b - NB_N7_ASS_FAIL_O&Minterv

Long Name NB_N7_ASS_FAIL_O&Minterv

Definition Number of 48.008ASSIGNMENT FAILURE (cause="O&M intervention") sentto the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"O&M intervention" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




220 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.8 C181c - NB_N7_ASS_FAIL_EquipFail

Long Name NB_N7_ASS_FAIL_EquipFail

Definition Number of 48.008ASSIGNMENT FAILURE (cause="equipment failure") sentto the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"equipment failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 221 / 1256


10.1.1.1.1.9 C181d - NB_N7_ASS_FAIL_NoRadioResAvail

Long Name NB_N7_ASS_FAIL_NoRadioResAvail

Definition Number of 48.008ASSIGNMENT FAILURE (cause="no radio resourceavailable") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"no radio resource available" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




222 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.10 C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc

Long Name NB_N7_ASS_FAIL_ReqTerResUnav/Alloc

Definition Number of 48.008ASSIGNMENT FAILURE (cause="requested terrestrialresource unavailable", or "terrestrial resource already allocated") sent to theMSC.

Trigger condition 1) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"requested terrestrial resource unavailable" is sent on A interface to the MSC.2)Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"terrestrial resource already allocated" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 223 / 1256


10.1.1.1.1.11 C181f - NB_N7_ASS_FAIL_ReqTrans/RateUnav

Long Name NB_N7_ASS_FAIL_ReqTrans/RateUnav

Definition Number of 48.008ASSIGNMENT FAILURE (cause="requested transcoding/rateadaptation unavailable") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"requested transcoding/rate adaptation unavailable" is sent on A interface tothe MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




224 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.12 C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan

Long Name NB_N7_ASS_FAIL_RadioIntFailRevOldChan

Definition Number of 48.008ASSIGNMENT FAILURE (cause="radio interface failure-reversion to old channel") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"radio interface failure - reversion to old channel" is sent on A interface to theMSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 225 / 1256


10.1.1.1.1.13 C181h - NB_N7_ASS_FAIL_RadioIntFail

Long Name NB_N7_ASS_FAIL_RadioIntFail

Definition Number of 48.008ASSIGNMENT FAILURE (cause="radio interface failure")sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"radio interface failure" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




226 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.14 C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp

Long Name NB_N7_ASS_FAIL_CipherAlgoNotSupp

Definition Number of 48.008ASSIGNMENT FAILURE (cause="ciphering algorithm notsupported") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"cipher algorithm not supported" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 227 / 1256


10.1.1.1.1.15 C181j - NB_N7_ASS_FAIL_BSSnotEquip

Long Name NB_N7_ASS_FAIL_BSSnotEquip

Definition Number of 48.008ASSIGNMENT FAILURE (cause="BSS not equiped") sentto the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"BSS not equiped" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




228 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.16 C181k - NB_N7_ASS_FAIL_ProtocolError

Long Name NB_N7_ASS_FAIL_ProtocolError

Definition Number of 48.008ASSIGNMENT FAILURE (cause="protocol error betweenBSC and MSC") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"protocol error between BSC and MSC" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 229 / 1256


10.1.1.1.1.17 C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav

Long Name NB_N7_ASS_FAIL_ReqSpeechVersUnav

Definition Number of 48.008ASSIGNMENT FAILURE (cause="requested speech versionunavailable") sent to the MSC.

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of"requested speech version unavailable" is sent on A interface to the MSC.


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




230 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.1.1.1.1.18 C182 - NB_N7_CLEAR_REQ_EST_PHAS

Long Name NB_N7_CLEAR_REQ_EST_PHAS

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for calls in TCHestablished phase, and for internal inter-cell and external TCH handoverfailures.Intra-cell handover failures are not taken into account.This counter takesinto account TCH in traffic mode or in signaling mode.

Trigger condition 1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is senton A interface to the MSC, for a call in TCH established phase. Note that thistrigger takes into account TCH in traffic mode or in signaling mode.2) Whenevera 48.008 CLEAR REQUEST message is sent on A interface to the MSC, after aHandover command is sent, during a TCH internal inter-cell HO.3) Whenever a48.008 CLEAR REQUEST message is sent on A interface to the MSC, after aHandover command is sent, during a TCH external HO.4) Whenever a 48.008CLEAR REQUEST message is sent on A interface to the MSC, after a DTMAssignment Command is sent, during a DTM assignment, for a MS whichalready had a TCH allocated (i.e. the TCH in DTM Assignment Command isestablished in traffic mode).


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 231 / 1256


10.2 Traffic Load

10.2.1 Interface

10.2.1.1 A

10.2.1.1.1 –

10.2.1.1.1.1 C750 - TIME_A_CHANNEL_BUSY

Long Name TIME_A_CHANNEL_BUSY

Definition Time (in seconds) during which the A channel is busy.

Trigger condition The counter cumulates over the Accumulation Period, all unit times during whichthe A channel is busy.For each channel allocation:1) The counter starts beingincremented when the A channel is activated (see C751)2) The counter stopsbeing incremented when the A channel is deallocated after the reception of a48.058 RF CHANNEL RELEASE ACKNOWLEDGE message or the expiryof timer T_RCR_ACK twice (after the sending of the 48.058 RF CHANNELRELEASE message).


Sub Domain 2 A

Sub Domain 3 –

Measured Object A interface channel




232 / 1256 3BK 21255 AAAA PCZZA Ed.07


10.2.1.1.1.2 C751 - NB_A_CHANNEL_ALLOC

Long Name NB_A_CHANNEL_ALLOC

Definition Number of allocations of the A-channel.

Trigger condition 1) Whenever a A channel is allocated following the reception of 48.008ASSIGNMENT REQUEST.2) Whenever a A channel is allocated followingthe reception of 48.008 HANDOVER REQUEST3) Whenever a A channel isallocated during an internal handover procedure


Sub Domain 2 A

Sub Domain 3 –

Measured Object A interface channel




3BK 21255 AAAA PCZZA Ed.07 233 / 1256


234 / 1256 3BK 21255 AAAA PCZZA Ed.07

11 BSC-TYPE 19 - SMS PP measurements


3BK 21255 AAAA PCZZA Ed.07 235 / 1256



11.1.1 Short Message Service

11.1.1.1 Point to Point

11.1.1.1.1 Failure

11.1.1.1.1.1 C194a - NB_SMS_PP_CON_REJ_RadioIntFail

Long Name NB_SMS_PP_CON_REJ_RadioIntFail

Definition Number of SMS connection rejections by the BSC with the cause "radiointerface failure".

Trigger condition Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 is sent fromBSC to MSC with a cause value of "radio interface failure".

Sub Domain 1 Short Message Service

Sub Domain 2 Point to Point



Type Name SMS PP measurements

Type Definition Set of counters related to the Short Message Service Point to Point. The SMStransactions on SDCCH and SACCH channels, originating or terminating, arecounted.


236 / 1256 3BK 21255 AAAA PCZZA Ed.07


11.1.1.1.1.2 C194b - NB_SMS_PP_CON_REJ_BSSnotEquip

Long Name NB_SMS_PP_CON_REJ_BSSnotEquip

Definition Number of SMS connection rejections by the BSC with the cause "BSS notequipped",

Trigger condition Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 with a causevalue of "BSS not equipped" is sent on A interface from BSC to MSC.








3BK 21255 AAAA PCZZA Ed.07 237 / 1256


11.1.1.1.1.3 C194c - NB_SMS_PP_CON_REJ_ProtocolError

Long Name NB_SMS_PP_CON_REJ_ProtocolError

Definition Number of SMS connection rejections by the BSC with the cause "protocolerror between BSC and MSC".

Trigger condition Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 with a causevalue of "protocol error between BSC and MSC" is sent on A interface fromBSC to MSC.








238 / 1256 3BK 21255 AAAA PCZZA Ed.07


11.1.1.1.1.4 C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR

Long Name NB_SMS_PP_CON_REL_LAPDM_ERROR

Definition Number of SMS connection releases of established SMS SAPI 3 connections bythe BSC due to a LAPDm error.

Trigger condition Whenever an 48.058 ERROR INDICATION message related to SAPI 3 isreceived by the BSC with one of the following cause values :a) timer T200expired (N200+1) timesb) unsolicited DM response, multiple frame establishedstatec) sequence error.








3BK 21255 AAAA PCZZA Ed.07 239 / 1256


11.1.1.1.2 Success

11.1.1.1.2.1 C190 - NB_SMS_PP_CON_MO_SDCCH

Long Name NB_SMS_PP_CON_MO_SDCCH

Definition Number of Mobile Originating SMS connections on SDCCH.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION (SAPI = 3) message related toan SDCCH sub-channel is received by the BSC.








240 / 1256 3BK 21255 AAAA PCZZA Ed.07


11.1.1.1.2.2 C191 - NB_SMS_PP_CON_MT_SDCCH

Long Name NB_SMS_PP_CON_MT_SDCCH

Definition Number of Mobile Terminating SMS connections on SDCCH.

Trigger condition Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SDCCHsub-channel is received by the BSC.








3BK 21255 AAAA PCZZA Ed.07 241 / 1256


11.1.1.1.2.3 C192 - NB_SMS_PP_CON_MO_SACCH

Long Name NB_SMS_PP_CON_MO_SACCH

Definition Number of Mobile Originating SMS connections on SACCH.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION (SAPI = 3) message related toan SACCH sub-channel is received by the BSC.








242 / 1256 3BK 21255 AAAA PCZZA Ed.07


11.1.1.1.2.4 C193 - NB_SMS_PP_CON_MT_SACCH

Long Name NB_SMS_PP_CON_MT_SACCH

Definition Number of Mobile Terminating SMS connections on SACCH.

Trigger condition Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SACCHsub-channel is received by the BSC.








3BK 21255 AAAA PCZZA Ed.07 243 / 1256


244 / 1256 3BK 21255 AAAA PCZZA Ed.07

12 BSC-TYPE 25 - SCCP measurements


3BK 21255 AAAA PCZZA Ed.07 245 / 1256



12.1.1 Interface

12.1.1.1 A

12.1.1.1.1 SCCP

12.1.1.1.1.1 C153a - NB_N7_CON_EST_FAIL_DUE_NSS

Long Name NB_N7_CON_EST_FAIL_DUE_NSS

Definition Number of BSS originating SCCP connection failures due to the NSS.

Trigger condition 1) CREF received.2) RLSD received for a connection that was not established(this could indicate that the Connection Confirm from the MSC was not received).


Sub Domain 2 A

Sub Domain 3 SCCP


Type Name SCCP measurements

Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links


246 / 1256 3BK 21255 AAAA PCZZA Ed.07


12.1.1.1.1.2 C153b - NB_N7_CON_EST_FAIL_DUE_BSS

Long Name NB_N7_CON_EST_FAIL_DUE_BSS

Definition Number of BSS originating SCCP connection failures due to the BSS.

Trigger condition N_DISC_REQ received from BSSAP for a connection that was not yetestablished.


Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 247 / 1256


12.1.1.1.1.3 C257 - NB_N7_CON_REF_SENT

Long Name NB_N7_CON_REF_SENT

Definition Number of CONNECTION REFUSED sent to the MSC.

Trigger condition Whenever a CONNECTION REFUSED message is sent on A interface fromthe BSC to the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





248 / 1256 3BK 21255 AAAA PCZZA Ed.07


12.1.1.1.1.4 C258 - NB_N7_CON_REF_REC

Long Name NB_N7_CON_REF_REC

Definition Number of CONNECTION REFUSED received from the MSC.

Trigger condition Whenever a CONNECTION REFUSED message is received on A interfacefrom the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 249 / 1256


12.2 Traffic Load

12.2.1 Interface

12.2.1.1 A

12.2.1.1.1 SCCP

12.2.1.1.1.1 C251 - NB_N7_UNIT_DATA_SENT

Long Name NB_N7_UNIT_DATA_SENT

Definition Number of connectionless Unit Data messages class 0 sent to the MSC.

Trigger condition Whenever a UNIT DATA message (with protocol class parameter equal to 0) issent from the BSC to the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





250 / 1256 3BK 21255 AAAA PCZZA Ed.07


12.2.1.1.1.2 C252 - NB_N7_UNIT_DATA_REC

Long Name NB_N7_UNIT_DATA_REC

Definition Number of connectionless Unit Data messages class 0 received from the MSC.

Trigger condition Whenever a UNIT DATA message (with protocol class parameter equal to 0) isreceived from the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 251 / 1256


12.2.1.1.1.3 C253 - NB_N7_CON_REQ_SENT

Long Name NB_N7_CON_REQ_SENT

Definition Number of CONNECTION REQUEST sent to the MSC.

Trigger condition Whenever a CONNECTION REQUEST message is sent on A interface fromthe BSC to the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





252 / 1256 3BK 21255 AAAA PCZZA Ed.07


12.2.1.1.1.4 C254 - NB_N7_CON_REQ_REC

Long Name NB_N7_CON_REQ_REC

Definition Number of CONNECTION REQUEST received from the MSC.

Trigger condition Whenever a CONNECTION REQUEST message is received on A interfacefrom the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 253 / 1256


12.2.1.1.1.5 C255 - NB_N7_CON_CONF_SENT

Long Name NB_N7_CON_CONF_SENT

Definition Number of CONNECTION CONFIRM sent to the MSC.

Trigger condition Whenever a CONNECTION CONFIRM message is sent on A interface fromthe BSC to the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





254 / 1256 3BK 21255 AAAA PCZZA Ed.07


12.2.1.1.1.6 C256 - NB_N7_CON_CONF_REC

Long Name NB_N7_CON_CONF_REC

Definition Number of CONNECTION CONFIRM received from the MSC.

Trigger condition Whenever a CONNECTION CONFIRM message is received on A interfacefrom the MSC.


Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 255 / 1256


256 / 1256 3BK 21255 AAAA PCZZA Ed.07

13 BSC-TYPE 26 - TCH outgoing handover per adjacency measurements

13 BSC-TYPE 26 - TCH outgoing handover per adjacencymeasurements

3BK 21255 AAAA PCZZA Ed.07 257 / 1256


13.1 Adjacency

13.1.1 Fixed serving Cell

13.1.1.1 –

13.1.1.1.1 –

13.1.1.1.1.1 C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT

Long Name NB_ADJ_SCELL_OUT_TCH_HO_ATPT

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover attempts. Note that for outgoing external handover, the "Cell Identifier"OIE is not always provided, so the counter is incremented only if this field isprovided. This counter takes into account handovers from TCH in traffic or insignaling mode.

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the fixedserving cell for an external or internal inter-cell TCH handover towards thevariable target cell.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 Fixed serving Cell

Sub Domain 2 –

Sub Domain 3 –

Measured Object Adjacency-CGI

Type Name TCH outgoing handover per adjacency measurements

Type Definition Set of counters related to outgoing TCH handover provided per adjacency.


258 / 1256 3BK 21255 AAAA PCZZA Ed.07


13.1.1.1.1.2 C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC

Long Name NB_ADJ_SCELL_OUT_TCH_HO_SUCC

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover successes. This counter takes into account handovers from TCH intraffic or in signaling mode.

Trigger condition 1) Internal handover: whenever 44.018 HANDOVER_COMPLETE messageis received on Abis interface from the variable target cell during an internalinter-cell TCH handover attempted from the fixed serving cell.2) Externalhandover from the fixed serving cell to the 2G target cell in the followingcases:2a) 48.008 CLEAR COMMAND (cause = "handover successful") isreceived at the serving BSC from the MSC.2b) 48.008 CLEAR COMMAND(cause = "normal event/call control") is received while T8 is running.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 259 / 1256


13.1.1.1.1.3 C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover -execution failures due to MS access problem with reversion of themobile to the old channel. This counter takes into account handovers fromTCH in traffic or in signaling mode.

Trigger condition Whenever a 44.018 HANDOVER FAILURE message is received on Abisinterface from the fixed serving cell during an external or internal inter-cell TCHhandover attempted towards the variable 2G target cell.Note: This countercounts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





260 / 1256 3BK 21255 AAAA PCZZA Ed.07


13.1.1.1.1.4 C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover -execution failures due to MS access problem, without reversion ofthe mobile to the old channel. This counter takes into account handovers fromTCH in traffic or in signaling mode.

Trigger condition 1) Internal handover: whenever the timer supervising the internal inter-cell TCHhandover procedure (T3103) from the fixed serving cell to the variable target cellexpires.2) External handover: whenever the timer supervising the external TCHhandover procedure (T8) from the fixed serving cell to the variable target cellexpires, except if a 48.008 CLEAR COMMAND with "normal event/call control"cause was received from the MSC, leading to a normal call release. In such acase, the handover is considered as successful.Note: This counter counts bothinter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 261 / 1256


13.1.1.1.1.5 C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover attempts with emergency cause. This counter takes into accounthandovers from TCH in traffic or in signaling mode.

Trigger condition Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND issent to the MS via the serving cell, for an outgoing handover cause 2, 3, 4, 5,6, 7, 17, 18, 22 on a TCH channel, from the fixed serving cell to the variabletarget cell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.


Sub Domain 2 –

Sub Domain 3 –





262 / 1256 3BK 21255 AAAA PCZZA Ed.07


13.1.1.1.1.6 C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT

Long Name NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover attempts with better cell cause. This counter takes into accounthandovers from TCH in traffic or in signaling mode.

Trigger condition Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND issent to the MS via the serving cell, for an outgoing handover cause 12, 14, 21on a TCH channel, from the fixed serving cell to the variable target cell.Note:This counter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 263 / 1256


13.1.1.1.1.7 C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT

Long Name NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage)handover attempts with traffic cause. This counter takes into account handoversfrom TCH in traffic or in signaling mode.

Trigger condition Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND issent to the MS via the serving cell, for an outgoing handover cause 23,24, 28 ona TCH channel, from the fixed serving cell to the variable target cell.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





264 / 1256 3BK 21255 AAAA PCZZA Ed.07


13.1.1.1.1.8 C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT

Long Name NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT

Definition Number of outgoing (external or internal) inter-cell directed retries attempts withForced directed retry cause.

Trigger condition Whenever a 44.018 HANDOVER COMMAND message is sent to the MS foran outgoing (external or internal) inter-cell directed retry Cause 20 from theserving cell to a given target cell.Note: This counter counts both inter-PLMNand intra-PLMN directed retry events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 265 / 1256


266 / 1256 3BK 21255 AAAA PCZZA Ed.07

14 BSC-TYPE 27 - 2G TCH incoming handover per adjacency measurements

14 BSC-TYPE 27 - 2G TCH incoming handover peradjacency measurements

3BK 21255 AAAA PCZZA Ed.07 267 / 1256


14.1 Adjacency

14.1.1 Fixed target Cell

14.1.1.1 –

14.1.1.1.1 –

14.1.1.1.1.1 C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT

Long Name NB_ADJ_TCELL_INC_TCH_HO_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR orFR usage) handover attempts.

Trigger condition 1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to theMS via the variable serving cell for an internal inter-cell TCH handover towardsthe fixed target cell.2) External handover : whenever 48.008HANDOVERREQUEST ACK is sent to the MSC from the target BSC for an external TCHhandover from the variable 2G serving cell towards the fixed target cell. TheCell-identity of the serving and target cells is provided in the 48.008HANDOVERREQUEST. Only handovers from a 2G cell shall be taken into account (if thefield Cell Identifier discriminator in the I.E. Cell Identifier (serving) of the 48.008HANDOVER REQUEST is set to 0000 or 0001).Note: This counter counts bothinter-PLMN and intra-PLMN handover events.

Sub Domain 1 Fixed target Cell

Sub Domain 2 –

Sub Domain 3 –


Type Name 2G TCH incoming handover per adjacency measurements

Type Definition Set of counters related to incoming TCH handover provided per adjacency.Only handovers from 2G cells are taken into account (i.e. handovers from 3Gare not counted in type 27).


268 / 1256 3BK 21255 AAAA PCZZA Ed.07


14.1.1.1.1.2 C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC

Long Name NB_ADJ_TCELL_INC_TCH_HO_SUCC

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover successes.

Trigger condition 1) Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the fixed target cell during an external or internal inter-cell TCHhandover attempted from the variable serving cell. Only handovers from a 2Gcell shall be taken into account (if the field Cell Identifier discriminator in theI.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 269 / 1256


14.1.1.1.1.3 C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC

Long Name NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover -execution failures due to MS access problem, with or withoutreversion of the mobile to the old channel.

Trigger condition 1) Internal handover : - 44.018HANDOVER FAILURE (cause= "radio interfacefailure, reversion to old channel") received from the variable serving cell duringan internal inter-cell TCH handover towards the fixed target cell.- T3103 expiry2) External handover : - 48.058CONNECTION FAILURE INDICATION (cause="handover access failure") received on the new channel from the fixed targetcell- 48.008CLEAR COMMAND (cause= "radio interface failure, reversion to oldchannel") received on the target BSC.Only handovers from a 2G cell shall betaken into account (if the field Cell Identifier discriminator in the I.E. Cell Identifier(serving) of the 48.008 HANDOVER REQUEST is set to 0000 or 0001).Note:This counter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





270 / 1256 3BK 21255 AAAA PCZZA Ed.07


14.1.1.1.1.4 C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT

Long Name NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover attempts, with emergency cause.

Trigger condition 1) Internal inter-cell handover : whenever 44.018HANDOVER COMMANDis sent to the MS via the variable serving cell for an internal inter-cell TCHhandover towards the fixed target cell, with cause 2, 3, 4, 5, 6, 7, 17, 18, 22 2)External handover : whenever 48.008HANDOVER REQUEST ACK is sent tothe MSC from the target BSC for an external TCH handover from the variableserving cell towards the fixed target cell. The Cell-identity of the serving andtarget cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause2, 3, 4, 5, 6Only handovers from a 2G cell shall be taken into account (if thefield Cell Identifier discriminator in the I.E. Cell Identifier (serving) of the 48.008HANDOVER REQUEST is set to 0000 or 0001).Note: This counter counts bothinter-PLMN and intra-PLMN handover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 271 / 1256


14.1.1.1.1.5 C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT

Long Name NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover attempts, with better cell cause.

Trigger condition 1) Internal intercell handover : whenever 44.018HANDOVER COMMAND is sentto the MS via the variable serving cell for an internal inter-cell TCH handovertowards the fixed target cell, with cause 12, 14, 212) External handover :whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from thetarget BSC for an external TCH handover from the variable serving cell towardsthe fixed target cell. The Cell-identity of the serving and target cells is providedin the 48.008HANDOVER REQUEST with 48.008 cause 12Only handoversfrom a 2G cell shall be taken into account (if the field Cell Identifier discriminatorin the I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is setto 0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 –

Sub Domain 3 –





272 / 1256 3BK 21255 AAAA PCZZA Ed.07


14.1.1.1.1.6 C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT

Long Name NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover attempts, with traffic cause.

Trigger condition 1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to theMS via the variable serving cell for an internal inter-cell TCH handover towardsthe fixed target cell, with cause 23, 24, 282) External handover : whenever48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSCfor an external TCH handover from the variable serving cell towards the fixedtarget cell. The Cell-identity of the serving and target cells is provided in the48.008HANDOVER REQUEST with 48.008 cause 15.Only handovers from a2G cell shall be taken into account (if the field Cell Identifier discriminator inthe I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 273 / 1256


14.1.1.1.1.7 C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT

Long Name NB_ADJ_TCELL_INC_FORCED_DR_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell directed retriesattempts, with Forced directed retry cause.

Trigger condition 1) Internal handover : whenever 44.018HANDOVER COMMAND is sent tothe MS via the variable serving cell for an internal inter-cell TCH handovertowards the fixed target cell, with cause 202) External handover : whenever48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSCfor an external TCH handover from the variable serving cell towards the fixedtarget cell. The Cell-identity of the serving and target cells is provided in the48.008HANDOVER REQUEST with 48.008 cause 13.Only handovers from a2G cell shall be taken into account (if the field Cell Identifier discriminator inthe I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 –

Sub Domain 3 –





274 / 1256 3BK 21255 AAAA PCZZA Ed.07


14.1.1.1.1.8 C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT

Long Name NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FRusage) handover attempts, with unknown or missing cause.

Trigger condition 1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to theMS via the variable serving cell for an internal inter-cell TCH handover towardsthe fixed target cell, with unknown or missing cause.2) External handover :whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from thetarget BSC for an external TCH handover from the variable serving cell towardsthe fixed target cell. The Cell-identity of the serving and target cells is providedin the 48.008HANDOVER REQUEST with unknown or missing 48.008 cause,or 48.008 cause different from 2, 3, 4, 5, 6, 12, 13, 15.Only handovers from a2G cell shall be taken into account (if the field Cell Identifier discriminator inthe I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 275 / 1256


276 / 1256 3BK 21255 AAAA PCZZA Ed.07

15 BSC-TYPE 28 - SDCCH handover


3BK 21255 AAAA PCZZA Ed.07 277 / 1256


15.1 Handover

15.1.1 SDCCH

15.1.1.1 Cause

15.1.1.1.1 –

15.1.1.1.1.1 C115 - NB_SDCCH_HO_MSC_TRIG

Long Name NB_SDCCH_HO_MSC_TRIG

Definition Number of external handovers triggered by the MSC but not required by the BSS.

Trigger condition Whenever a 48.008 HANDOVER COMMAND message is received on Ainterface from the MSC and timer T_HO_REQ_LOST is not running.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –


Type Name SDCCH handover

Type Definition Set of counters related to SDCCH handover procedure.The counters areprovided per handover category : incoming and outgoing, internal (inter-cell andintra-cell) and external. The handover causes are also provided.


278 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.2 C445 - NB_SDCCH_HO_ATPT_23_TrafHandover

Long Name NB_SDCCH_HO_ATPT_23_TrafHandover

Definition Number of inter-cell internal or external handover attempts, with the cause 23:"traffic handover" on SDCCH. This counter counts also the directed retries.

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 23 on SDCCH. This counter is incremented in the servingcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 279 / 1256


15.1.1.1.1.3 C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover

Long Name NB_SDCCH_HO_ATPT_24_GenCaptureHandover

Definition Number of inter-cell internal or external handover attempts, with the cause 24:"general capture handover" on SDCCH. This counter counts also the directedretries.

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 24 on SDCCH. This counter is incremented in the servingcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





280 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.4 C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance

Long Name NB_SDCCH_HO_ATPT_22_TooShortDistance

Definition Number of SDCCH inter-cell internal or external handover attempts with cause22: "too short MS-BTS distance". This cause is restricted to the extendedcells.This counter counts also the directed retries.

Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the mobile via the BTSbecause of cause 22 on SDCCH. This counter is incremented in the servingcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 281 / 1256


15.1.1.1.1.5 C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp

Long Name NB_SDCCH_HO_ATPT_2_TooLowQualUp

Definition Number of SDCCH inter-cell internal or external handover attempts triggeredwith cause 2: "uplink quality too low".

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 2. This counter is incremented in the serving cell.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





282 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.6 C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp

Long Name NB_SDCCH_HO_ATPT_3_TooLowLevUp

Definition Number of SDCCH inter-cell internal or external handover attempts with cause3: "uplink level too low".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 283 / 1256


15.1.1.1.1.7 C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown

Long Name NB_SDCCH_HO_ATPT_4_TooLowQualDown

Definition Number of SDCCH inter-cell internal or external handover attempts with cause4: "downlink quality too low".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





284 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.8 C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown

Long Name NB_SDCCH_HO_ATPT_5_TooLowLevDown

Definition Number of SDCCH inter-cell internal or external handover attempts triggeredwith cause 5: "downlink level too low".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 285 / 1256


15.1.1.1.1.9 C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance

Long Name NB_SDCCH_HO_ATPT_6_TooLongDistance

Definition Number of SDCCH inter-cell internal or external handover attempts with cause6: "MS-BTS distance too long".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





286 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.10 C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp

Long Name NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp

Definition Number of SDCCH intra-cell handover attempts with cause 15: "too high levelinterference on uplink".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 287 / 1256


15.1.1.1.1.11 C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown

Long Name NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown

Definition Number of SDCCH intra-cell handover attempts with cause 16: "too high levelinterference on downlink".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





288 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.12 C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg

Long Name NB_SDCCH_HO_ATPT_12_TooLowPowBudg

Definition Number of SDCCH inter-cell internal or external handover attempts with cause12: "too low power budget".


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 289 / 1256


15.1.1.1.1.13 C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand

Long Name NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand

Definition Number of SDCCH inter-cell internal or external handover attempts with cause21: "high level in neighbour cell in the preferred band". This counter is relatedto multiband.


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





290 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.14 C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell

Long Name NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause7: "several consecutive bad SACCH frames received in a micro cell". Thiscounter is related to micro cell environment.


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 291 / 1256


15.1.1.1.1.15 C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell

Long Name NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause17 "too low level on the uplink in a microcell compared to a high threshold". Thiscounter is related to micro cell environment.


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





292 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.16 C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell

Long Name NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause18: "too low level on the downlink in a microcell compared to a high threshold".This counter is related to micro cell environment.


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 293 / 1256


15.1.1.1.1.17 C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS

Long Name NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS

Definition Number of SDCCH inter-cell internal or external handover attempts with cause14: "high level in neighbour lower layer cell for slow mobile". This counter isrelated to micro cell environment.


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





294 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.1.1.18 C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR

Long Name NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR

Definition Number of SDCCH inter-cell internal or external handover attempts with cause20: "forced directed retry". This counter is related to a forced directed retry(internal or external).


Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 295 / 1256



15.1.1.2.1 –

15.1.1.2.1.1 C310 - NB_INC_EXT_SDCCH_HO_REQ

Long Name NB_INC_EXT_SDCCH_HO_REQ

Definition Number of incoming external SDCCH handover requests.

Trigger condition 48.008HANDOVER REQUEST is received by the target BSC for the targetcell on the SDCCH channel.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





296 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.2.1.2 C311 - NB_INC_EXT_SDCCH_HO_ATPT

Long Name NB_INC_EXT_SDCCH_HO_ATPT

Definition Number of incoming external SDCCH handover attempts.

Trigger condition 48.008HANDOVER REQUEST ACK is sent by the target BSC containingthe 44.018HANDOVER COMMAND towards the target cell on the SDCCHchannel.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 297 / 1256


15.1.1.2.1.3 C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG

Definition MC81=C81, Number of incoming external SDCCH handover -preparationfailures due to congestion.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of"no radio resource available" is sent on A interface from the target BSC to theMSC during an external SDCCH handover.Note: This counter counts bothinter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





298 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.2.1.4 C82 - NB_INC_EXT_SDCCH_HO_SUCC

Long Name NB_INC_EXT_SDCCH_HO_SUCC

Definition Number of incoming external SDCCH handover successes.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for an SDCCH Sub-channel that is involved in anexternal SDCCH handover.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 299 / 1256


15.1.1.2.1.5 C83 - NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS

Definition Number of incoming external SDCCH handover -execution failures due to MSaccess problem.

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with acause value of "handover access failure" is received on Abis interface from thetarget cell, for an SDCCH Sub-channel during an external SDCCH handover.2)Whenever the timer supervising the handover procedure on the target cell(T9113), expires during an external SDCCH handover.3) Whenever a 48.008CLEAR COMMAND with a cause value of "radio interface failure - reversion toold channel" is received on A interface on the target BSC from the MSC duringan external SDCCH handover.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





300 / 1256 3BK 21255 AAAA PCZZA Ed.07



15.1.1.3.1 –

15.1.1.3.1.1 C330 - NB_INC_INT_SDCCH_HO_REQ

Long Name NB_INC_INT_SDCCH_HO_REQ

Definition Number of incoming internal inter-cell SDCCH handover requests.

Trigger condition Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 301 / 1256


15.1.1.3.1.2 C331 - NB_INC_INT_SDCCH_HO_ATPT

Long Name NB_INC_INT_SDCCH_HO_ATPT

Definition Number of incoming internal inter-cell SDCCH handover attempts.

Trigger condition 44.018HANDOVER COMMAND is sent to the MS via the serving cell for internalinter cell SDCCH handover. However, the counter is incremented in the TARGETcell, based on the target cell ID indicated by the HO Command message,

Sub Domain 1 SDCCH


Sub Domain 3 –





302 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.3.1.3 C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG

Definition MC91=C91, Number of incoming internal inter-cell SDCCH handover-preparation failures due to congestion.

Trigger condition Whenever a internal inter-cell SDCCH handover cannot be performed, becausethere is no free SDCCH Sub-channel to allocate the handover to.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 303 / 1256


15.1.1.3.1.4 C92 - NB_INC_INT_SDCCH_HO_SUCC

Long Name NB_INC_INT_SDCCH_HO_SUCC

Definition Number of incoming internal inter-cell SDCCH handover successes.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell during an internal inter-cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





304 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.3.1.5 C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS

Definition Number of incoming internal inter-cell SDCCH handover -execution failuresdue to MS access problem.

Trigger condition 1) Whenever the timer supervising the handover procedure (T3103) expiresduring an internal inter-cell SDCCH handover.2) Whenever a HANDOVERFAILURE message is received on Abis interface from the serving cell during andinternal inter-cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 305 / 1256


15.1.1.4 Intra

15.1.1.4.1 –

15.1.1.4.1.1 C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INTRA_SDCCH_HO_PREP_FAIL_CONG

Definition MC101=C101, Number of intra-cell SDCCH handover -preparation failures dueto congestion.

Trigger condition Whenever a internal intra-cell SDCCH handover cannot be performed, becausethere is no free SDCCH Sub-channel to allocate the handover to.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





306 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.4.1.2 C102 - NB_INTRA_SDCCH_HO_SUCC

Long Name NB_INTRA_SDCCH_HO_SUCC

Definition Number of intra-cell SDCCH handover successes.

Trigger condition Whenever a ASSIGNEMENT COMPLETE message is received on the targetchannel during an internal intra-cell SDCCH handover.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 307 / 1256


15.1.1.4.1.3 C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV

Long Name NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV

Definition Number of intra-cell SDCCH handover -execution failures due to MS accessproblem without reversion to the old channel.

Trigger condition Whenever the timer supervising the internal intra-cell SDCCH handoverprocedure (T3107) expires.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





308 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.4.1.4 C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV

Long Name NB_INTRA_SDCCH_HO_EXEC_FAIL_REV

Definition Number of intra-cell SDCCH handover -execution failures due to MS accessproblem with reversion to the old channel.

Trigger condition Whenever a 44.018 ASSIGNMENT FAILURE message is received on theServing Sub-channel, during an internal intra-cell SDCCH handover.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 309 / 1256


15.1.1.4.1.5 C360 - NB_INTRA_SDCCH_HO_REQ

Long Name NB_INTRA_SDCCH_HO_REQ

Definition Number of intra-cell SDCCH handover requests.

Trigger condition Whenever the BSC process responsible for the handover procedure starts anintra cell SDCCH handover procedure.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





310 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.4.1.6 C361 - NB_INTRA_SDCCH_HO_ATPT

Long Name NB_INTRA_SDCCH_HO_ATPT

Definition Number of intra-cell SDCCH handover attempts.

Trigger condition 44.018ASSIGNMENT COMMAND is sent to the MS via the cell for intra cellhandover on SDCCH.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 311 / 1256



15.1.1.5.1 –

15.1.1.5.1.1 C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ

Long Name NB_OUT_EXT_SDCCH_REAL_HO_REQ

Definition Number of outgoing external SDCCH handover requests.

Trigger condition Whenever a 48.008 HANDOVER REQUIRED message is sent on A interfaceto the MSC for a SDCCH handover. If more than one 48.008 HANDOVERREQUIRED is sent in the frame of the same Handover procedure, the counteris incremented only once.48.008 HANDOVER REQUIRED is sent in followingsituations :1) An external handover alarm has been raised, with correspondinglist of candidate cells.2) The list of candidate cells for the current alarm hasbeen updated.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





312 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.5.1.2 C86 - NB_OUT_EXT_SDCCH_HO_SUCC

Long Name NB_OUT_EXT_SDCCH_HO_SUCC

Definition Number of outgoing external SDCCH handover successes.

Trigger condition External SDCCH handover in the following cases:1/ a 48.008 CLEARCOMMAND message with a cause of "handover successful" is received onA interface on the serving BSC from the MSC.2/ 48.008 CLEAR COMMAND(cause= "normal event/call control") received while T8 is running.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 313 / 1256


15.1.1.5.1.3 C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV

Long Name NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV

Definition Number of outoing external SDCCH handover -execution failures due to MSaccess problem with reversion to the old channel.

Trigger condition Whenever a HANDOVER FAILURE message is received on Abis interface fromthe serving cell, during an external SDCCH handover.Note: This counter countsboth inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





314 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.5.1.4 C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV

Definition Number outoing external SDCCH handover -execution failures due to MSaccess problem without reversion to the old channel.

Trigger condition Whenever the timer supervising the handover procedure on the serving cell(T8), expires during an external SDCCH handover, except if a 48.008 CLEARCOMMAND with "normal event/call control" cause was received from the MSC,leading to a normal call release. In such a case, the handover is consideredas successful.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 315 / 1256


15.1.1.5.1.5 C90 - NB_OUT_EXT_SDCCH_HO_ATPT

Long Name NB_OUT_EXT_SDCCH_HO_ATPT

Definition Number of outgoing external SDCCH handover attempts.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface on the serving channel, during an external SDCCH handoverprocedure.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 SDCCH


Sub Domain 3 –





316 / 1256 3BK 21255 AAAA PCZZA Ed.07



15.1.1.6.1 –

15.1.1.6.1.1 C100 - NB_OUT_INT_SDCCH_HO_ATPT

Long Name NB_OUT_INT_SDCCH_HO_ATPT

Definition Number of outgoing internal inter-cell SDCCH handover attempts.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface to the mobile via the serving cell, during an internal inter-cell SDCCHhandover procedure.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 317 / 1256


15.1.1.6.1.2 C95a - NB_OUT_INT_SDCCH_HO_REQ

Long Name NB_OUT_INT_SDCCH_HO_REQ

Definition Number of outgoing internal inter-cell SDCCH handover requests.

Trigger condition Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





318 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.6.1.3 C96 - NB_OUT_INT_SDCCH_HO_SUCC

Long Name NB_OUT_INT_SDCCH_HO_SUCC

Definition Number of outgoing internal inter-cell SDCCH handover successes.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell, during an internal inter-cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 319 / 1256


15.1.1.6.1.4 C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV

Long Name NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV

Definition Number of outoing internal inter-cell SDCCH handover execution failures due toMS access problem with reversion to the old channel.

Trigger condition Whenever a HANDOVER FAILURE message is received on Abis interface fromthe serving cell, during an internal inter-cell SDCCH handover.

Sub Domain 1 SDCCH


Sub Domain 3 –





320 / 1256 3BK 21255 AAAA PCZZA Ed.07


15.1.1.6.1.5 C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV

Definition Number outoing internal inter-cell SDCCH handover -execution failures due toMS access problem without reversion to the old channel.

Trigger condition Whenever the timer supervising the internal inter-cell handover procedure(T3103) expires.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 321 / 1256


322 / 1256 3BK 21255 AAAA PCZZA Ed.07

16 BSC-TYPE 29 - Directed retry measurements


3BK 21255 AAAA PCZZA Ed.07 323 / 1256


16.1 Handover


16.1.1.1 External

16.1.1.1.1 Outgoing

16.1.1.1.1.1 C142b - NB_OUT_FORCED_EDR_SUCC

Long Name NB_OUT_FORCED_EDR_SUCC

Definition Number of outgoing forced external directed retry (towards a TCH channel inHR or FR usage) successes.

Trigger condition Forced external directed retry in the following cases:1/ 48.008CLEARCOMMAND (cause = "handover successful") is received on the serving BSC2/48.008 CLEAR COMMAND (cause = "normal event/call control") received whileT8 is running.Note: This counter counts both inter-PLMN and intra-PLMNdirected retry events.


Sub Domain 2 External



Type Name Directed retry measurements

Type Definition Set of counters related to the directed retry procedure. The counters areprovided per directed retry category : incoming and outgoing, internal andexternal, forced and normal.


324 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.1.1.2 C142d - NB_OUT_NOR_EDR_SUCC

Long Name NB_OUT_NOR_EDR_SUCC

Definition Number of outgoing normal external directed retry (towards a TCH channel inHR or FR usage) successes.

Trigger condition Normal external directed retry in the following cases:1/ 48.008 CLEARCOMMAND (cause = "handover successful") is received on the serving BSC2/48.008 CLEAR COMMAND (cause = "normal event/call control") received whileT8 is running.Note: This counter counts both inter-PLMN and intra-PLMNdirected retry events.








3BK 21255 AAAA PCZZA Ed.07 325 / 1256


16.1.1.1.1.3 C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV

Long Name NB_OUT_FORCED_EDR_EXEC_FAIL_REV

Definition Number of outgoing forced external directed retry -execution failures due to MSaccess problem with reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Whenever 44.018 HANDOVER FAILURE is received from the MS via the servingcell on the old channel (SDCCH).Note: This counter counts both inter-PLMNand intra-PLMN directed retry events.








326 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.1.1.4 C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV

Long Name NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV

Definition Number of outgoing forced external directed retry -execution failures due to MSaccess problem without reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Whenever the timer supervising the handover procedure (T8) expires duringa forced external directed retry, except if a 48.008 CLEAR COMMAND with"normal event/call control" cause was received from the MSC, leading toa normal call release. In such a case, the directed retry is considered assuccessful.Note: This counter counts both inter-PLMN and intra-PLMN directedretry events.








3BK 21255 AAAA PCZZA Ed.07 327 / 1256


16.1.1.1.1.5 C143g - NB_OUT_NOR_EDR_EXEC_FAIL_REV

Long Name NB_OUT_NOR_EDR_EXEC_FAIL_REV

Definition Number of outgoing normal external directed retry -execution failures due to MSaccess problem with reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Whenever 44.018 HANDOVER FAILURE is received from the MS via the servingcell on the old channel (SDCCH).Note: This counter counts both inter-PLMNand intra-PLMN directed retry events.








328 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.1.1.6 C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV

Long Name NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV

Definition Number of outgoing normal external directed retry -execution failures due to MSaccess problem without reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Whenever the timer supervising the handover procedure (T8) expires duringa normal external directed retry, except if a 48.008 CLEAR COMMAND with"normal event/call control" cause was received from the MSC, leading toa normal call release. In such a case, the directed retry is considered assuccessful.Note: This counter counts both inter-PLMN and intra-PLMN directedretry events.








3BK 21255 AAAA PCZZA Ed.07 329 / 1256


16.1.1.1.1.7 C144b - NB_OUT_FORCED_EDR_REQ

Long Name NB_OUT_FORCED_EDR_REQ

Definition Number of outgoing forced external directed retry requests. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever the BSC process responsible for handover procedure starts a forcedexternal directed retry from the serving cell.Note: This counter counts bothinter-PLMN and intra-PLMN directed retry events.








330 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.1.1.8 C144d - NB_OUT_NOR_EDR_REQ

Long Name NB_OUT_NOR_EDR_REQ

Definition Number of outgoing normal external directed retry requests. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever the BSC process responsible for handover procedure starts a normalexternal directed retry from the serving cell.Note: This counter counts bothinter-PLMN and intra-PLMN directed retry events.








3BK 21255 AAAA PCZZA Ed.07 331 / 1256


16.1.1.1.1.9 C145b - NB_OUT_FORCED_EDR_ATPT

Long Name NB_OUT_FORCED_EDR_ATPT

Definition Number of outgoing forced external directed retry attempts. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the servingcell on the SDCCH channel for a forced external directed retry.Note: Thiscounter counts both inter-PLMN and intra-PLMN directed retry events.








332 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.1.1.10 C145d - NB_OUT_NOR_EDR_ATPT

Long Name NB_OUT_NOR_EDR_ATPT

Definition Number of outgoing normal external directed retry attempts. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the servingcell on the SDCCH channel for a normal external directed retry.Note: Thiscounter counts both inter-PLMN and intra-PLMN directed retry events.








3BK 21255 AAAA PCZZA Ed.07 333 / 1256


16.1.1.2 Internal

16.1.1.2.1 Incoming

16.1.1.2.1.1 C151 - NB_INC_IDR_SUCC (29)

Long Name NB_INC_IDR_SUCC (29)

Definition Number of incoming internal directed retry (forced or normal, towards a TCHchannel in HR or FR usage) successes.

Trigger condition Whenever 44.018HANDOVER COMPLETE is received from the MS via thetarget cell, for a forced or internal internal directed retry procedure.



Sub Domain 3 Incoming





334 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.1.2 C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_IDR_EXEC_FAIL_MS_ACCESS

Definition Number of incoming internal directed retry (forced or normal) -execution failuresdue to MS access problem. The target TCH channel can be in HR or FR usage.

Trigger condition 1) 44.018HANDOVER FAILURE on SDCCH received from the MS via theserving cell2) timer T3103 expiry (this timer supervizes the 44.018HANDOVERCOMMAND)








3BK 21255 AAAA PCZZA Ed.07 335 / 1256


16.1.1.2.1.3 C153 - NB_INC_IDR_REQ

Long Name NB_INC_IDR_REQ

Definition MC153=C153, Number of incoming internal directed retry (forced or normal)requests. The target TCH channel can be in HR or FR usage.

Trigger condition Whenever the BSC process responsible for handover procedure selects thetarget cell for forced or normal internal directed retry.








336 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.1.4 C154 - NB_INC_IDR_ATPT

Long Name NB_INC_IDR_ATPT

Definition Number of incoming internal directed retry (forced or normal) attempts. Thetarget TCH channel can be in HR or FR usage.

Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the servingcell on the SDCCH. However, the counter is incremented in the TARGET cell,based on the target cell ID indicated by the HO Command message,








3BK 21255 AAAA PCZZA Ed.07 337 / 1256


16.1.1.2.1.5 C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_IDR_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming internal directed retry (forced or normal) -preparationfailures due to congestion (on Air or A-bis interface). The target TCH channelcan be in HR or FR usage.

Trigger condition 1) Whenever there are no free TCH in the target cell during a forced or normalinternal directed retry.2) Whenever no TCH resource is available on A-bisinterface for a forced or normal internal directed retry. (not valid in B7).Note 1: InMX BSC, this counter is incremented whenever a TCH cannot be not allocateddue to the TCH processing capacity of CCP reaches the limit defined by theMAX_TCH_PER_CCP parameter. In this case, MC926 is also incrementedby one.Note 2: In IP mode, this counter is increased by 1 if:- the cell mappedon a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter








338 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.2 Outgoing

16.1.1.2.2.1 C142a - NB_OUT_FORCED_IDR_SUCC

Long Name NB_OUT_FORCED_IDR_SUCC

Definition Number of outgoing forced internal directed retry (towards a TCH channel inHR or FR usage) successes.

Trigger condition Whenever 44.018HANDOVER COMPLETE is received from the MS via thetarget cell, for a forced internal directed retry procedure.








3BK 21255 AAAA PCZZA Ed.07 339 / 1256


16.1.1.2.2.2 C142c - NB_OUT_NOR_IDR_SUCC

Long Name NB_OUT_NOR_IDR_SUCC

Definition Number of outgoing normal internal directed retry (towards a TCH channel inHR or FR usage) successes.

Trigger condition Whenever 44.018HANDOVER COMPLETE is received from the MS via thetarget cell, for a normal internal directed retry procedure.








340 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.2.3 C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV

Long Name NB_OUT_FORCED_IDR_EXEC_FAIL_REV

Definition Number of outgoing forced internal directed retry -execution failures due to MSaccess problem with reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition 44.018HANDOVER FAILURE on SDCCH received from the MS via the servingcell.








3BK 21255 AAAA PCZZA Ed.07 341 / 1256


16.1.1.2.2.4 C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV

Long Name NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV

Definition Number of outgoing forced internal directed retry -execution failures due to MSaccess problem without reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).








342 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.2.5 C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV

Long Name NB_OUT_NOR_IDR_EXEC_FAIL_REV

Definition Number of outgoing normal internal directed retry -execution failures due to MSaccess problem with reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition 44.018HANDOVER FAILURE on SDCCH received from the MS via the servingcell.








3BK 21255 AAAA PCZZA Ed.07 343 / 1256


16.1.1.2.2.6 C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV

Long Name NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV

Definition Number of outgoing normal internal directed retry -execution failures due to MSaccess problem without reversion to the old channel. The target TCH channelcan be in HR or FR usage.

Trigger condition Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).








344 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.2.7 C144a - NB_OUT_FORCED_IDR_REQ

Long Name NB_OUT_FORCED_IDR_REQ

Definition Number of outgoing forced internal directed retry (towards a TCH channel inHR or FR usage) requests.

Trigger condition Whenever the BSC process responsible for handover procedure initiates aforced internal directed retry from the serving cell.








3BK 21255 AAAA PCZZA Ed.07 345 / 1256


16.1.1.2.2.8 C144c - NB_OUT_NOR_IDR_REQ

Long Name NB_OUT_NOR_IDR_REQ

Definition Number of outgoing normal internal directed retry requests. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever the BSC process responsible for handover procedure initiates anormal internal directed retry from the serving cell.








346 / 1256 3BK 21255 AAAA PCZZA Ed.07


16.1.1.2.2.9 C145a - NB_OUT_FORCED_IDR_ATPT

Long Name NB_OUT_FORCED_IDR_ATPT

Definition Number of outgoing forced internal directed retry attempts. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the servingcell on the SDCCH channel for a forced internal directed retry.








3BK 21255 AAAA PCZZA Ed.07 347 / 1256


16.1.1.2.2.10 C145c - NB_OUT_NOR_IDR_ATPT

Long Name NB_OUT_NOR_IDR_ATPT

Definition Number of outgoing normal internal directed retry attempts. The target TCHchannel can be in HR or FR usage.

Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the servingcell on the SDCCH channel for a normal internal directed retry.








348 / 1256 3BK 21255 AAAA PCZZA Ed.07

17 BSC-TYPE 30 - SMS CB measurements


3BK 21255 AAAA PCZZA Ed.07 349 / 1256




17.1.1.1 Cell Broadcast

17.1.1.1.1 Failure

17.1.1.1.1.1 CB603 - NB_SMS_CB_FAIL_IND

Long Name NB_SMS_CB_FAIL_IND

Definition Each time a FAILURE INDICATION sent to the CBC, number of cells implicatedby the failure.The BSC detects a failure and request the CBC (by the FAILUREINDICATION message) to stop the sending of messages to a list of cells.

Trigger condition Whenever a FAILURE INDICATION is sent to the CBC, the counter isincremented by the Cell-List mandatory IE.


Sub Domain 2 Cell Broadcast


Measured Object BSC

Type Name SMS CB measurements

Type Definition Set of counters related to the Short Message Service Cell Broadcast.


350 / 1256 3BK 21255 AAAA PCZZA Ed.07


17.1.1.1.1.2 CB604 - NB_SMS_CB_WRITE_REP_KILL_MESS_REJ

Long Name NB_SMS_CB_WRITE_REP_KILL_MESS_REJ

Definition Number of cells rejected for a WRITE REPLACE or KILL MESSAGE request.AWRITE REPLACE or a KILL MESSAGE request coming from the CBC isreceived by the BSC. This request is addressed to a list of cells. The BSC isable to process the request either :- entirely (i.e. for all cells of the list) : the BSCsends a REPORT SUCCESS to the CBC- partially (i.e. for a part of the list) :the BSC returns a REPORT SUCCESS to the CBC- not at all (i.e. for no cell): the BSC returns a REPORT FAILURE to the CBC if the cause of the rejectis the same for all cells, otherwise a REPORT SUCCESS is returned.When aREPORT SUCCESS is returned, the Failure-List optional Information Elementspecifies for each cell whose request has not been completed, the cause anddiagnostic of the failure.

Trigger condition 1) Whenever a WRITE REPLACE or a KILL MESSAGE request is totallyrejected by REPORT FAILURE (then, for all cells with the same cause), thecounter is incremented by the Cell-List IE value provided within the requestmessage.2) Whenever a REPORT SUCCESS to a WRITE REPLACE or a KILLMESSAGE request is returned to the CBC, the counter is incremented by thenumber of cells provided within the Failure-List IE of the REPORT SUCCESS.




Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 351 / 1256


17.2 Traffic Load


17.2.1.1 Short Message Service

17.2.1.1.1 Cell Broadcast

17.2.1.1.1.1 CB601 - NB_SMSCB_WRITE_REPL_SUCC

Long Name NB_SMSCB_WRITE_REPL_SUCC

Definition Number of cells successfully served for a WRITE REPLACE.A WRITEREPLACE request coming from the CBC is received by the BSC. This requestis addressed to a list of cells. The BSC is able to process the request either :-entirely (i.e. for all cells of the list) : the BSC sends a REPORT SUCCESSto the CBC- partially (i.e. for a part of the list) : the BSC returns a REPORTSUCCESS to the CBC- not at all (i.e. for no cell) : the BSC returns a REPORTFAILURE to the CBC if the cause of the reject is the same for all cells, otherwisea REPORT SUCCESS is returned.When a REPORT SUCCESS is returned,the No-of-Broadcasts-completed-list optional Information Element specifies thenumber of cells successfully served by the request. This IE is not providedwhen no cells can be served.

Trigger condition Whenever a REPORT SUCCESS to a WRITE REPLACE is sent to the CBC,the counter is incremented by the No-of-Broadcasts-completed-list optional IE(if not provided; the counter is not incremented, since it means that no cellsare served).




Measured Object BSC




352 / 1256 3BK 21255 AAAA PCZZA Ed.07


17.2.1.1.1.2 CB602 - NB_SMSCB_KILL_MESS_SUCC

Long Name NB_SMSCB_KILL_MESS_SUCC

Definition Number of cells successfully served for a KILL MESSAGE.A KILL MESSAGErequest coming from the CBC is received by the BSC. This request is addressedto a list of cells. The BSC is able to process the request either :- entirely (i.e.for all cells of the list) : the BSC sends a REPORT SUCCESS to the CBC-partially (i.e. for a part of the list) : the BSC returns a REPORT SUCCESS tothe CBC- not at all (i.e. for no cell) : the BSC returns a REPORT FAILUREto the CBC if the cause of the reject is the same for all cells, otherwise aREPORT SUCCESS is returned.When a REPORT SUCCESS is returned, theNo-of-Broadcasts-completed-list optional Information Element specifies thenumber of cells successfully served by the request. This IE is not providedwhen no cells can be served.

Trigger condition Whenever a REPORT SUCCESS to a KILL MESSAGE is sent to the CBC, thecounter is incremented by the No-of-Broadcasts-completed-list optional IE (ifnot provided, the counter is not incremented, since it means that no cells areserved).




Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 353 / 1256


354 / 1256 3BK 21255 AAAA PCZZA Ed.07

18 BSC-TYPE 31 - Radio Measurement Statistics


3BK 21255 AAAA PCZZA Ed.07 355 / 1256



18.1.1 RMS

18.1.1.1 –

18.1.1.1.1 –

18.1.1.1.1.1 RMS10 - VQ_NOISY_UL_INTERFERENCE

Long Name VQ_NOISY_UL_INTERFERENCE

Definition Number of calls suffering from problem of interference on the uplink path.

Trigger condition Whenever a call verifies : 100*(INTERFERED_UL_SAMPLES /NUM_UL_SAMPLES) > VQ_INTF_THRESHOLDThis calculation is donewhen 48.058 RF CHANNEL RELEASE is received for the observedcall.INTERFERED_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ> VQ_RXQUAL and AV_RXLEV_UL_VQ>VQ_RXLEVAV_RXQUAL_UL_VQ :average on VQ_AVERAGE measurements of RXQUAL_ULAV_RXLEV_UL_VQ: average on VQ_AVERAGE measurements of RXLEV_ULNUM_UL_SAMPLES: total number of averages calculated on UL measurements during the call onthe considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX

Type Name Radio Measurement Statistics

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.


356 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.2 RMS11 - VQ_NOISY_DL_INTERFERENCE

Long Name VQ_NOISY_DL_INTERFERENCE

Definition Number of calls suffering from problems of interference on the downlink path.

Trigger condition Whenever a call verifies : 100*(INTERFERED_DL_SAMPLES /NUM_DL_SAMPLES) > VQ_INTF_THRESHOLDThis calculation is donewhen 48.058 RF CHANNEL RELEASE is received for the observedcall.INTERFERED_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ> VQ_RXQUAL and AV_RXLEV_DL_VQ>VQ_RXLEVAV_RXQUAL_DL_VQ :average on VQ_AVERAGE measurements of RXQUAL_DLAV_RXLEV_DL_VQ: average on VQ_AVERAGE measurements of RXLEV_DLNUM_DL_SAMPLES: total number of averages calculated on DL measurements during the call onthe considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 357 / 1256


18.1.1.1.1.3 RMS12 - VQ_NOISY_UL_COVERAGE

Long Name VQ_NOISY_UL_COVERAGE

Definition Number of calls suffering from bad coverage on the uplink path.

Trigger condition Whenever a call verifies : 100*(BAD_COVERAGE_UL_SAMPLES/ NUM_UL_SAMPLES) > VQ_INTF_THRESHOLDThis calculationis done when 48.058 RF CHANNEL RELEASE is receivedfor the observed call.BAD_COVERAGE_UL_SAMPLES = nbof times where AV_RXQUAL_UL_VQ > VQ_RXQUAL andAV_RXLEV_UL_VQ<=VQ_RXLEVAV_RXQUAL_UL_VQ : averageon VQ_AVERAGE measurements of RXQUAL_ULAV_RXLEV_UL_VQ :average on VQ_AVERAGE measurements of RXLEV_ULNUM_UL_SAMPLES :total number of averages calculated on DL measurements during the call on theconsidered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




358 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.4 RMS13 - VQ_NOISY_DL_COVERAGE

Long Name VQ_NOISY_DL_COVERAGE

Definition Number of calls suffering from bad coverage on the downlink path.

Trigger condition Whenever a call verifies : 100*(BAD_COVERAGE_DL_SAMPLES/ NUM_DL_SAMPLES) > VQ_INTF_THRESHOLDThis calculationis done when 48.058 RF CHANNEL RELEASE is receivedfor the observed call.BAD_COVERAGE_DL_SAMPLES = nbof times where AV_RXQUAL_DL_VQ > VQ_RXQUAL andAV_RXLEV_DL_VQ<=VQ_RXLEVAV_RXQUAL_DL_VQ : averageon VQ_AVERAGE measurements of RXQUAL_DLAV_RXLEV_DL_VQ :average on VQ_AVERAGE measurements of RXLEV_DLNUM_DL_SAMPLES :total number of averages calculated on DL measurements during the call on theconsidered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 359 / 1256


18.1.1.1.1.5 RMS14 - VQ_NOISY_UL_UNDEFINED

Long Name VQ_NOISY_UL_UNDEFINED

Definition Number of calls suffering from both problem of interference and bad coverageon the uplink path.These calls are not counted in VQ_NOISY_UL_COVERAGEor VQ_NOISY_UL_INTERFERENCE.

Trigger condition Whenever a call verifies : 100*(BAD_COVERAGE_UL_SAMPLES/ NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLDand100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) <=VQ_INTF_THRESHOLDand100*(BAD_QUALITY_UL_SAMPLES /NUM_UL_SAMPLES) > VQ_INTF_THRESHOLDThis calculationis done when 48.058 RF CHANNEL RELEASE is receivedfor the observed call.BAD_COVERAGE_UL_SAMPLES =nb of times where AV_RXQUAL_UL_VQ > VQ_RXQUAL andAV_RXLEV_UL_VQ<=VQ_RXLEVINTERFERED_UL_SAMPLES = nb oftimes when AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ >VQ_RXLEVBAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES +BAD_COVERAGE_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ >VQ_RXQUALAV_RXQUAL_UL_VQ : average on VQ_AVERAGE measurementsof RXQUAL_ULAV_RXLEV_UL_VQ : average on VQ_AVERAGE measurementsof RXLEV_ULNUM_UL_SAMPLES : total number of averages calculated on ULmeasurements during the call on the considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




360 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.6 RMS15 - VQ_NOISY_DL_UNDEFINED

Long Name VQ_NOISY_DL_UNDEFINED

Definition Number of calls suffering from both problem of interference and bad coverage onthe downlink path.These calls are not counted in VQ_NOISY_DL_COVERAGEor VQ_NOISY_DL_INTERFERENCE.

Trigger condition Whenever a call verifies : 100*(BAD_COVERAGE_DL_SAMPLES/ NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLDand100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) <=VQ_INTF_THRESHOLDand100*(BAD_QUALITY_DL_SAMPLES /NUM_DL_SAMPLES) > VQ_INTF_THRESHOLDThis calculationis done when 48.058 RF CHANNEL RELEASE is receivedfor the observed call.BAD_COVERAGE_DL_SAMPLES =nb of times where AV_RXQUAL_DL_VQ > VQ_RXQUAL andAV_RXLEV_DL_VQ<=VQ_RXLEVINTERFERED_DL_SAMPLES = nb oftimes when AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ >VQ_RXLEVBAD_QUALITY_DL_SAMPLES = INTERFERED_DL_SAMPLES +BAD_COVERAGE_DL_SAMPLES = nb of times when AV_RXQUAL_DL_VQ >VQ_RXQUALAV_RXQUAL_DL_VQ : average on VQ_AVERAGE measurementsof RXQUAL_DLAV_RXLEV_DL_VQ : average on VQ_AVERAGE measurementsof RXLEV_DLNUM_DL_SAMPLES : total number of averages calculated on DLmeasurements during the call on the considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 361 / 1256


18.1.1.1.1.7 RMS16 - VQ_NOISY_UL_BAD_FER

Long Name VQ_NOISY_UL_BAD_FER

Definition Number of calls with bad quality measurements and with bad FERmeasurements on the uplink path.

Trigger condition Whenever a call verifies :100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) >VQ_INTF_THRESHOLDand100*(BAD_QUAL_BAD_FER_UL_SAMPLES /BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLDThis calculationis done when 48.058 RF CHANNEL RELEASE is received for theobserved call.In the equations above, the following notations are used:*BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES +BAD_COVERAGE_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ >VQ_RXQUAL* BAD_QUAL_BAD_FER_UL_SAMPLES = nb of times whenAV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER and AV_RXFER_UL_VQ> VQ_BAD_RXFER* AV_RXQUAL_UL_VQ : average on VQ_AVERAGEmeasurements of RXQUAL_UL* AV_RXLEV_UL_VQ : average onVQ_AVERAGE measurements of RXLEV_UL* NUM_UL_SAMPLES : totalnumber of averages calculated on UL measurements during the call onthe considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




362 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.8 RMS17 - VQ_NOISY_UL_GOOD_FER

Long Name VQ_NOISY_UL_GOOD_FER

Definition Number of calls with bad quality measurements but with good FERmeasurements on the uplink path.

Trigger condition Whenever a call verifies :100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) >VQ_INTF_THRESHOLDand100*(BAD_QUAL_GOOD_FER_UL_SAMPLES /BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLDThis calculation isdone when 48.058 RF CHANNEL RELEASE is received for the observedcall.BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES +BAD_COVERAGE_UL_SAMPLES= nb of times when AV_RXQUAL_UL_VQ >VQ_RXQUALBAD_QUAL_GOOD_FER_UL_SAMPLES = nb of times whenAV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER and AV_RXFER_UL_VQ<= VQ_GOOD_RXFERAV_RXQUAL_UL_VQ : average on VQ_AVERAGEmeasurements of RXQUAL_ULAV_RXFER_UL_VQ : average onVQ_AVERAGE measurements of FER_ULNUM_UL_SAMPLES : totalnumber of averages calculated on UL measurements during the call onthe considered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 363 / 1256


18.1.1.1.1.9 RMS18 - VQ_ABNORMAL_BAD_FER

Long Name VQ_ABNORMAL_BAD_FER

Definition Number of calls with fair quality measurements but with bad FER measurementson the uplink path.

Trigger condition Whenever a call verifies : 100*(FAIR_QUAL_BAD_FER_UL_SAMPLES/ FAIR_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLDThiscalculation is done when 48.058 RF CHANNEL RELEASE is receivedfor the observed call.FAIR_QUAL_BAD_FER_UL_SAMPLES = nb oftimes when AV_RXQUAL_UL_VQ<VQ_RXQUAL_VS_RXFER andAV_RXFER_UL_VQ>VQ_BAD_RXFERAV_RXQUAL_UL_VQ : average onVQ_AVERAGE measurements of RXQUAL_ULAV_RXFER_UL_VQ : averageon VQ_AVERAGE measurements of FER_ULNUM_UL_SAMPLES : totalnumber of averages calculated on UL measurements during the call on theconsidered TRX

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




364 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.10 RMS32 - TOT_MEAS

Long Name TOT_MEAS

Definition Number of MEASUREMENT RESULTS messages sent and used for RMScomputation in the concerned cell.

Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS,and used for RMS.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 365 / 1256


18.1.1.1.1.11 RMS33 - TOT_MEAS_L1INFO_NOL3INFO

Long Name TOT_MEAS_L1INFO_NOL3INFO

Definition Number of MEASUREMENT RESULTS messages sent without Layer 3information but with Layer 1 present.The result is first calculated by the BTS at aTRX level, then compilated by the BSC at a cell level.This counter reflects theuplink quality, it is incremented due to bad uplink radio quality or long handoverinterruptions.

Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTSwithout Layer 3 information but with Layer 1 present, and used for RMS.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




366 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.12 RMS34 - TOT_MEAS_DTX_UL

Long Name TOT_MEAS_DTX_UL

Definition Number of measurement results used for RMS, where DTX is used on theuplink path.

Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS,with DTX_UL=1, used for RMS.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 367 / 1256


18.1.1.1.1.13 RMS35 - TOT_MEAS_DTX_DL

Long Name TOT_MEAS_DTX_DL

Definition Number of measurement results indicating that DTX is used on the downlinkpath, used for RMS.

Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS,with DTX_UL=1, and used for RMS.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




368 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.14 RMS36 - PERC_TA_GT_TA_STAT

Long Name PERC_TA_GT_TA_STAT

Definition Reserved for internal Alcatel-Lucent usage (PS detection on TS basis for Edgecapable TRX)


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 369 / 1256


18.1.1.1.1.15 RMS38 - TOT_EMR

Long Name TOT_EMR

Definition Total number of Extended Measurement Results.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




370 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.16 RMS3a - TPR_RXQUAL_UL_RXLEV_UL

Long Name TPR_RXQUAL_UL_RXLEV_UL

Definition Table of 3x 8x10 results.Each cell (i,j) of the table contains :1) number of reportsin which UL RXQUAL is equal to j and UL RXLEV is reported in level bandi (Cij)2) corresponding averaged value of MS power level3) correspondingaveraged value of Timing AdvanceFor Cij, the result is given as follows :Cij=Vij x254 / Max_i, where Vij represents the real number of measurements, and Max_ithe greatest value of Vij, for i given (see RMS3b).Cij=0 indicates 'number ofmeasurements = 0'Cij=254 indicates 'number of measurements = Max_i'Cij=255is reserved to indicate overflow.The values of the average MS power level (2)and the average Timing Advance (3) are directly given, both with a precisionof 0.25. Note that these values (2 and 3) that are indicated in the ASCII file,which can be obtained via the OBSYNT interface, still have to be divided by4, whereas the values that are provided at the user interface are the correctones.UL RXQUAL can take values from 0 to 7.Level band i is defined by :MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_iMEAS_STAT_LEV_0= -47 dBm, MEAS_STAT_LEV_10 = -110 dBmAccording to 3GPP, values ofRXLEV lower than -110 dBm are considered as equal to -110 dBm

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT uplink RXQUAL is equal to j,while uplink RXLEV for the same call is in the given interval of MEAS_STAT_LEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 371 / 1256


18.1.1.1.1.17 RMS3b - TMR_RXQUAL_UL_RXLEV_UL

Long Name TMR_RXQUAL_UL_RXLEV_UL

Definition Table of 10 maximum results.Each cell Ci of the table indicates the greatestvalue of the Vij for a i given in RMS3a.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




372 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.18 RMS41a - AMR_WB_GMSK_FR_UL_BAD

Long Name AMR_WB_GMSK_FR_UL_BAD

Definition Table of 3 resultsEach cell (i) of the table contains:number of FR AMR WBGMSK UL bad speech frames.The result is given as follows :- Ci=MAX(Round[Vix 254 / Max], 1), where Vi represents the real number of measurements,and Max the greatest value of Vi (see RMS41b).- Ci=0 indicates 'number ofmeasurements = 0'- Ci=254 indicates 'number of measurements = Max'- Ci=255is reserved to indicate overflow.FR AMR WB GMSK codecs are defined by :-codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s, codec 3 = 12.65 kbit/s.

Trigger condition The TRE counts for each AMR WB call and for each FR AMR WB GMSK codecthe number of bad speech frames received from the MS (or sent to the TC) inuplink. Only speech frames of type "Speech_Degraded", "Speech_Bad" or"SID_Bad" shall be taken into account.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX



External Comment This counter is only reported for cells mapped on Evolium BTS.

3BK 21255 AAAA PCZZA Ed.07 373 / 1256


18.1.1.1.1.19 RMS41b - MAX_AMR_WB_GMSK_FR_UL_BAD

Long Name MAX_AMR_WB_GMSK_FR_UL_BAD

Definition Greatest values of the Vi in RM41a.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




374 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.20 RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL

Long Name AMR_WB_GMSK _FR_UL_RXLEV_UL

Definition Table of 3x10 resultsEach cell (i,k) of the table contains:1) number of correctUL speech frames using FR AMR WB GMSK codec k for which UL RXLEV isreported in level band i. The result is given as follows:- Cik=MAX(Round[Vikx 254 / Max_i], 1), where Vik represents the real number of measurements,and Max_i the greatest value of Vik, for i given (see RMS42b).- Cik=0indicates 'number of measurements = 0'- Cik=254 indicates 'number ofmeasurements = Max_i'- Cik=255 is reserved to indicate overflow.Level bandi is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_Ij = i1MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBmFR AMRWB GMSK codecs are defined by:codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s,codec 3 = 12.65 kbit/s.According to 3GPP, values of RXLEV lower than -110dBm are considered as equal to -110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each FR AMR WBGMSK call and for each FR AMR WB GMSK codec the number of correctspeech frames received from the MS (or sent to the TRAU) in uplink. To insureconsistency of the results, only speech frames of type "Speech_Good" or"SID_Update" shall be taken into account.At reception of the measurementreport of a given MS, the results are gathered in the line of the matrixcorresponding to reported UL RXLEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 375 / 1256


18.1.1.1.1.21 RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL

Long Name MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL

Definition Table of 10 maximum results.Each cell Ci of the table indicates the greatestvalue of the Vik for a i given in RMS42a.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




376 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.22 RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL

Long Name AMR_WB_GMSK_FR_DL_RXLEV_DL

Definition Table of 3x10 resultsEach cell (i,k) of the table contains :1) number of correctDL speech frames using FR AMR WB GMSK codec k for which DL RXLEV isreported in level band i.The result is given as follows :Cik=MAX(Round[Vikx 254 / Max_i], 1), where Vik represents the real number of measurements,and Max_I the greatest value of Vik, for i given (see RMS43b).Cik=0indicates 'number of measurements = 0'Cik=254 indicates 'number ofmeasurements = Max_i'Cik=255 is reserved to indicate overflow.Level bandi is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_ij = i -1MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBmFR AMRWB GMSK codecs are defined by:codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s,codec 3 = 12.65 kbit/s.According to 3GPP, values of RXLEV lower than -110dBm are considered as equal to -110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each FR AMR WBcall and for each FR AMR WB codec the number of correct speech framesreceived from the TC (or sent to the MS) in downlink. To insure consistency ofthe results, only speech frames of type "Speech_Good" or "SID_Update" shallbe taken into account.At reception of the measurement report of a given MS, theresults are gathered in the line of the matrix

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 377 / 1256


18.1.1.1.1.23 RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL

Long Name MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




378 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.24 RMS44a - AMR_FR_UL_BAD

Long Name AMR_FR_UL_BAD

Definition Table of 8 resultsEach cell (i) of the table contains :number of AMR FR ULbad speech frames.The result is given as follows :Ci=MAX(Round[Vi x 254 /Max], 1), where Vi represents the real number of measurements, and Max thegreatest value of Vi (see RMS44b).Ci=0 indicates 'number of measurements= 0'Ci=254 indicates 'number of measurements = Max'Ci=255 is reserved toindicate overflow.AMR FR codecs are defined by :codec 1 = 4.75 kbit/s, codec2 = 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s,codec 6 = 7.95 kbit/s, codec 7 = 10.2 kbit/s, codec 8 = 12.2 kbit/s

Trigger condition The TRE counts for each AMR call and for each AMR FR codec the numberof bad speech frames received from the MS (or sent to the TC) in uplink. Onlyspeech frames of type "Speech_Degraded", "Speech_Bad" or "SID_Bad" shallbe taken into account.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 379 / 1256


18.1.1.1.1.25 RMS44b - MAX_AMR_FR_UL_BAD

Long Name MAX_AMR_FR_UL_BAD

Definition Greatest value of the Vi in RM44a.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




380 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.26 RMS45a - AMR_HR_UL_BAD

Long Name AMR_HR_UL_BAD

Definition Table of 5 resultsEach cell (i) of the table contains :number of AMR HR ULbad speech frames.The result is given as follows :Ci=MAX(Round[Vi x 254 /Max], 1), where Vi represents the real number of measurements, and Max thegreatest value of Vi (see RMS45b).Ci=0 indicates 'number of measurements= 0'Ci=254 indicates 'number of measurements = Max'Ci=255 is reserved toindicate overflow.AMR HR codecs are defined by :codec 1 = 4.75 kbit/s, codec 2= 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s

Trigger condition The TRE counts for each AMR call and for each AMR HR codec the numberof bad speech frames received from the MS (or sent to the TC) in uplink. Onlyspeech frames of type "Speech_Degraded", "Speech_Bad" or "SID_Bad" shallbe taken into account.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 381 / 1256


18.1.1.1.1.27 RMS45b - MAX_AMR_HR_UL_BAD

Long Name MAX_AMR_HR_UL_BAD



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




382 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.28 RMS46a - AMR_FR_UL_RXLEV_UL

Long Name AMR_FR_UL_RXLEV_UL

Definition Table of 8x10 resultsEach cell (i,k) of the table contains :1) number of correct ULspeech frames using AMR FR codec k for which UL RXLEV is reported in levelband i.The result is given as follows :Cik=MAX(Round[Vik x 254 / Max_i], 1),where Vik represents the real number of measurements, and Max_i the greatestvalue of Vik, for i given (see RMS46b).Cik=0 indicates 'number of measurements= 0'Cik=254 indicates 'number of measurements = Max_i'Cik=255 is reserved toindicate overflow.Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV< MEAS_STAT_LEV_iMEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 =-110 dBmAMR FR codecs are defined by :codec 1 = 4.75 kbit/s, codec 2 = 5.15kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s, codec 6= 7.95 kbit/s, codec 7 = 10.2 kbit/s, codec 8 = 12.2 kbit/sAccording to 3GPP,values of RXLEV lower than -110 dBm are considered as equal to -110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each AMR call andfor each AMR FR codec the number of correct speech frames received from theMS (or sent to the TRAU) in uplink. To insure consistency of the results, onlyspeech frames of type "Speech_Good" or "SID_Update" shall be taken intoaccount.At reception of the measurement report of a given MS, the results aregathered in the line of the matrix corresponding to reported UL RXLEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 383 / 1256


18.1.1.1.1.29 RMS46b - MAX_AMR_FR_UL_RXLEV_UL

Long Name MAX_AMR_FR_UL_RXLEV_UL



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




384 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.30 RMS47a - AMR_FR_DL_RXLEV_DL

Long Name AMR_FR_DL_RXLEV_DL

Definition Table of 8x10 resultsEach cell (i,k) of the table contains :1) number of correct DLspeech frames using AMR FR codec k for which DL RXLEV is reported in levelband i.The result is given as follows :Cik=MAX(Round[Vik x 254 / Max_i], 1),where Vik represents the real number of measurements, and Max_i the greatestvalue of Vik, for i given (see RMS47b).Cik=0 indicates 'number of measurements= 0'Cik=254 indicates 'number of measurements = Max_i'Cik=255 is reserved toindicate overflow.Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV< MEAS_STAT_LEV_iMEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 =-110 dBmAMR FR codecs are defined by :codec 1 = 4.75 kbit/s, codec 2 = 5.15kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s, codec 6= 7.95 kbit/s, codec 7 = 10.2 kbit/s, codec 8 = 12.2 kbit/sAccording to 3GPP,values of RXLEV lower than -110 dBm are considered as equal to -110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each AMR call andfor each AMR FR codec the number of correct speech frames received from theTC (or sent to the MS) in downlink. To insure consistency of the results, onlyspeech frames of type "Speech_Good" or "SID_Update" shall be taken intoaccount.At reception of the measurement report of a given MS, the results aregathered in the line of the matrix corresponding to reported DL RXLEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 385 / 1256


18.1.1.1.1.31 RMS47b - MAX_AMR_FR_DL_RXLEV_DL

Long Name MAX_AMR_FR_DL_RXLEV_DL



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




386 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.32 RMS48a - AMR_HR_UL_RXLEV_UL

Long Name AMR_HR_UL_RXLEV_UL

Definition Table of 5x10 resultsEach cell (i,k) of the table contains :1) number of correctspeech frames using AMR HR codec k for which UL RXLEV is reported in levelband i.The result is given as follows :Cik=MAX(Round[Vik x 254 / Max_i], 1),where Vik represents the real number of measurements, and Max_i the greatestvalue of Vik, for i given (see RMS46b).Cik=0 indicates 'number of measurements= 0'Cik=254 indicates 'number of measurements = Max_i'Cik=255 is reserved toindicate overflow.Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV< MEAS_STAT_LEV_iMEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 =-110 dBmAMR HR codecs are defined by :codec 1 = 4.75 kbit/s, codec 2 = 5.15kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s.Accordingto 3GPP, values of RXLEV lower than -110 dBm are considered as equal to-110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each AMR call andfor each AMR HR codec the number of correct speech frames received from theMS (or sent to the TRAU) in uplink. To insure consistency of the results, onlyspeech frames of type "Speech_Good" or "SID_Update" shall be taken intoaccount.At reception of the measurement report of a given MS, the results aregathered in the line of the matrix corresponding to reported UL RXLEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 387 / 1256


18.1.1.1.1.33 RMS49a - AMR_HR_DL_RXLEV_DL

Long Name AMR_HR_DL_RXLEV_DL

Definition Table of 5x10 resultsEach cell (i,k) of the table contains :1) number of correct DLspeech frames using AMR HR codec k for which DL RXLEV is reported in levelband i.The result is given as follows :Cik=MAX(Round[Vik x 254 / Max_i], 1),where Vik represents the real number of measurements, and Max_i the greatestvalue of Vik, for i given (see RMS46b).Cik=0 indicates 'number of measurements= 0'Cik=254 indicates 'number of measurements = Max_i'Cik=255 is reserved toindicate overflow.Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV< MEAS_STAT_LEV_iMEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 =-110 dBmAMR HR codecs are defined by :codec 1 = 4.75 kbit/s, codec 2 = 5.15kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s.Accordingto 3GPP, values of RXLEV lower than -110 dBm are considered as equal to-110 dBm

Trigger condition In the period of the SACCH multiframe, the TRE counts for each AMR call andfor each AMR HR codec the number of correct speech frames received from theTC (or sent to the MS) in downlink. To insure consistency of the results, onlyspeech frames of type "Speech_Good" or "SID_Update" shall be taken intoaccount.At reception of the measurement report of a given MS, the results aregathered in the line of the matrix corresponding to reported DL RXLEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




388 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.34 RMS49b - MAX_AMR_HR_DL_RXLEV_DL

Long Name MAX_AMR_HR_DL_RXLEV_DL


Trigger condition .

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 389 / 1256


18.1.1.1.1.35 RMS4a - TPR_RXQUAL_DL_RXLEV_DL

Long Name TPR_RXQUAL_DL_RXLEV_DL

Definition Table of 3x 8x10 results.Each cell (i,j) of the table contains :1) number of reportsin which DL RXQUAL is equal to j and DL RXLEV is reported in level band I (Cij)2)corresponding averaged value of BS power level :For G2 BTS : correspondingaveraged value of [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)]ForEvolium BTS : corresponding averaged value of [ MAX_POWER_PER_TRX-abs(BS_TXPWR)].BS_TXPWR is the BTS transmitted power defined relativelyto the maximum absolute output power of the BTS. BS_TXPWR is expressedin dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. Notethat the formula is written independently of the coding used for the variables.The function abs() gives the absolute value of its argument.3) correspondingaveraged value of Timing AdvanceFor Cij, the result is given as follows :Cij=Vij x254 / Max_i, where Vij represents the real number of measurements, and Max_ithe greatest value of Vij, for i given (see RMS4b).Cij=0 indicates 'number ofmeasurements = 0'Cij=254 indicates 'number of measurements = Max_i'Cij=255is reserved to indicate overflow.The values of the average BS power level (2)and the average Timing Advance (3) are directly given, both with a precisionof 0.25. Note that these values (2 and 3) that are indicated in the ASCII file,which can be obtained via the OBSYNT interface, still have to be divided by4, whereas the values that are provided at the user interface are the correctones.DL RXQUAL can take values from 0 to 7.Level band i is defined by :MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_iMEAS_STAT_LEV_0= -47 dBm, MEAS_STAT_LEV_10 = -110 dBmAccording to 3GPP, values ofRXLEV lower than -110 dBm are considered as equal to -110 dBm

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT DL RXQUAL is equal to j,while DL RXLEV for the same call is in the given interval of MEAS_STAT_LEV.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




390 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.36 RMS4b - TMR_RXQUAL_DL_RXLEV_DL

Long Name TMR_RXQUAL_DL_RXLEV_DL



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 391 / 1256


18.1.1.1.1.37 RMS50a - TPR_TIMING_ADVANCE

Long Name TPR_TIMING_ADVANCE

Definition Table of 10 resultsEach cell (i) of the table contains :1) number of reportsin which Timing Advance is in Timing Advance band iThe result is givenas follows :Ci=MAX(ROUND[Vi x 254 / Max], 1), where Vi represents thereal number of measurements, and Max the greatest value of Vi, (seeRMS50b).Ci=0 indicates 'number of measurements = 0'Ci=254 indicates'number of measurements = Max'Ci=255 is reserved to indicate overflow.TimingAdvancee band is defined by : MEAS_STAT_TA_(i-1)<= Timing Advance <MEAS_STAT_TA_iMEAS_STAT_TA_0 = -110 dB, MEAS_STAT_TA_10 = 110 dB

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is inthe given interval of MEAS_STAT_TA.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




392 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.38 RMS50b - MAX_TIMING_ADVANCE

Long Name MAX_TIMING_ADVANCE



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 393 / 1256


18.1.1.1.1.39 RMS51 - TPR_UL_RXLEV_TA_BAND

Long Name TPR_UL_RXLEV_TA_BAND

Definition Table of 10 resultsEach cell (i) of the table contains :average value of UpLinkRxlev of reports in TA band i.Averaged Rxlev is given with a precision of2 digits after the comma (step size for coding = 0.01, -110 dBm coded 0,-109.99 dBm coded 1...).i = 1...10TA band i is defined by : MEAS_STAT_TA_(i-1)<= Timing Advance < MEAS_STAT_TA_iMEAS_STAT_TA_0 = 0 bper,MEAS_STAT_LEV_10 = 63 bper.According to 3GPP, values of RXLEV lowerthan -110 dBm are considered as equal to -110 dBm

Trigger condition Whenever a MEASUREMENT RESULT is received, UL RXLEV is stored.Atthe end of the measurement period, UL RXLEV corresponding to the sameTA band are averaged.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




394 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.40 RMS52 - TPR_DL_RXLEV_TA_BAND

Long Name TPR_DL_RXLEV_TA_BAND

Definition Table of 10 resultsEach cell (i) of the table contains :average value of DownLinkRxlev of reports in TA band i.Averaged Rxlev is given with a precision of2 digits after the comma (step size for coding = 0.01, -110 dBm coded 0,-109.99 dBm coded 1...).i = 1...10TA band i is defined by : MEAS_STAT_TA_(i-1)<= Timing Advance < MEAS_STAT_TA_iMEAS_STAT_TA_0 = 0 bper,MEAS_STAT_LEV_10 = 63 bper.According to 3GPP, values of RXLEV lowerthan -110 dBm are considered as equal to -110 dBm

Trigger condition Whenever a MEASUREMENT RESULT is received, DL RXLEV is stored.Atthe end of the measurement period, DL RXLEV corresponding to the sameTA band are averaged.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 395 / 1256


18.1.1.1.1.41 RMS53 - TPR_UL_RXQUAL_TA_BAND

Long Name TPR_UL_RXQUAL_TA_BAND

Definition Table of 10 resultsEach cell (i) of the table contains :average value of UpLinkRxqual of reports in TA band i.Averaged Rxqual is given with a precision of 2digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01 coded 1,...).i = 1...10TA band i is defined by : MEAS_STAT_TA_ (i-1)<= Timing Advance< MEAS_STAT_TA_iMEAS_STAT_TA_0 = 0 bper, MEAS_STAT_LEV_10 = 63bper.

Trigger condition Whenever a MEASUREMENT RESULT is received, UL RXQUAL is stored.Atthe end of the measurement period, UL RXQUAL corresponding to the sameTA band are averaged.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




396 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.42 RMS54 - TPR_DL_RXQUAL_TA_BAND

Long Name TPR_DL_RXQUAL_TA_BAND

Definition Table of 10 resultsEach cell (i) of the table contains :average value of DownLinkRxqual of reports in TA band i.Averaged Rxqual is given with a precision of 2digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01 coded 1,...).i = 1...10TA band i is defined by : MEAS_STAT_TA_ (i-1)<= Timing Advance< MEAS_STAT_TA_iMEAS_STAT_TA_0 = 0 bper, MEAS_STAT_LEV_10 = 63bper.

Trigger condition Whenever a MEASUREMENT RESULT is received, DL RXQUAL is stored.Atthe end of the measurement period, DL RXQUAL corresponding to the sameTA band are averaged.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 397 / 1256


18.1.1.1.1.43 RMS5a - TPR_BFI_RXLEV_UL

Long Name TPR_BFI_RXLEV_UL

Definition Table of 10x10 resultsEach cell (i,j) of the table contains :1) number of reportsin which consecutive BFI counter is in BFI band j and UL RXLEV is reportedin level band I (Cij)The result is given as follows :Cij=Vij x 254 / Max_i, whereVij represents the real number of measurements, and Max_i the greatest valueof Vij, for i given (see RMS5b).Cij=0 indicates 'number of measurements =0'Cij=254 indicates 'number of measurements = Max_i'Cij=255 is reserved toindicate overflow.BFI band is defined by : MEAS_STAT_BFI_(j-1)<= ConsecutiveBFI counter < MEAS_STAT_BFI_jMEAS_STAT_BFI_0 = 0, MEAS_STAT_BFI_10= 25Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV <MEAS_STAT_LEV_iMEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10= -110 dBmAccording to 3GPP, values of RXLEV lower than -110 dBm areconsidered as equal to -110 dBm

Trigger condition Whenever the Consecutive BFI counter is in the given interval ofMEAS_STAT_BFI, while RXLEV_UL for the same call is in the given intervalof MEAS_STAT_LEV.RMS5a is not incremented while DTX is applied on theuplink path.Consecutive BFI counter is incremented :1) Whenever, within theperiod of the SACCH multiframe, a speech frame with BFI=1 is received whilethe previous speech frame had also BFI=1. The counter must hold concurrentlyseveral periods of consecutive bad speech frames within the SACCH multiframe.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




398 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.44 RMS5b - TMR_BFI_RXLEV_UL

Long Name TMR_BFI_RXLEV_UL



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 399 / 1256


18.1.1.1.1.45 RMS6a - TPR_RADIO_LINK

Long Name TPR_RADIO_LINK

Definition Table of 10 resultsEach cell (i) of the table contains :1) number of reports inwhich Radio linkI counter is in S band iThe result is given as follows :Ci=Vi x254 / Max_i, where Vi represents the real number of measurements, and Max_ithe greatest value of Vi (see RMS6b).Ci=0 indicates 'number of measurements= 0'Ci=254 indicates 'number of measurements = Max_i'Ci=255 is reservedto indicate overflow.S band is defined by : MEAS_STAT_S_(i-1)<= Radio linkcounter < MEAS_STAT_S_iMEAS_STAT_S_0 = 0, MEAS_STAT_S_10 = 128

Trigger condition Whenever the Radio Link counter (S) is in the given interval of MEAS_STAT_S.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




400 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.46 RMS6b - MAX_RADIO_LINK

Long Name MAX_RADIO_LINK

Definition Greatest value of the Vi in RMS6a.


Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 401 / 1256


18.1.1.1.1.47 RMS7a - TPR_PATH_BALANCE

Long Name TPR_PATH_BALANCE

Definition Table of 10 resultsEach cell (i) of the table contains :1) number of reportsin which Path Balance is in Path Balance band iThe result is given asfollows :Ci=Vi x 254 / Max_i, where Vi represents the real number ofmeasurements, and Max_i the greatest value of Vi, (see RMS7b).Ci=0indicates 'number of measurements = 0'Ci=254 indicates 'number ofmeasurements = Max_i'Ci=255 is reserved to indicate overflow.Path Balanceband is defined by : MEAS_STAT_PATH_BALANCE_(i-1)<= Path balance <MEAS_STAT_PATH_BALANCE_iMEAS_STAT_PATH_BALANCE_0 = -110 dB,MEAS_STAT_PATH_BALANCE_10 = 110 dB

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Path Balance isin the given interval of MEAS_STAT_PATH_BALANCE.Path Balance =(RXLEV_UL-MS_TXPWR) - (RXLEV_DL - [BTS_MAX_OUTPUT_POWER -abs(BS_TXPWR)]), where BS_TXPWR is the BTS transmitted power definedrelatively to the maximum absolute output power of the BTS. BS_TXPWRis expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed indBm. RXLEV_UL and RXLEV_DL are the received signal levels by the basestation and by the mobile station respectively. They are expressed in dBm.MS_TXPWR is the transmission power of the mobile station and expressed indBm, too. Note that the formula is written independently of the coding used forthe variables. The function abs() gives the absolute value of its argument.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




402 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.48 RMS7b - MAX_PATH_BALANCE

Long Name MAX_PATH_BALANCE



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 403 / 1256


18.1.1.1.1.49 RMS8a - TPR_CIN

Long Name TPR_CIN

Definition Table of 10 results per neighbour cell.Each cell i of the table contains :1) numberof reports in which the C/I related to the neighbour cell is reported in C/I bandi.The result is given as follows :Ci=Vi x 254 / RMS8b, where Vi representsthe real number of measurementsCi=0 indicates 'number of measurements= 0'Ci=254 indicates 'number of measurements = Max_i'Ci=255 is reservedto indicate overflow.C/I band is defined by : MEAS_STAT_PATH_C_I_(i-1)<=C/I < MEAS_STAT_C_I_iMEAS_STAT_PATH_C_I_0 = -63 dB,MEAS_STAT_PATH_C_I_10 = 63 dBIf EN_BALANCED_CI = TRUE thenC/I (dB)= RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELLNotethat the formula is written independently of the coding used for the variables.RXLEV_DL and RXLEV_NCELL are the received signal levels of the servingand of the neighbour cells, expressed in dBm. BS_TXPWR is the BTStransmitted power and BS_TXPWR_MAX is the maximum allowed BTStransmission power. Both are defined relatively to the maximum absoluteoutput power of the BTS (BTS_MAX_OUTPUT_POWER). BS_TXPWR andBS_TXPWR_MAX are expressed in dB. The function abs() gives the absolutevalue of its argument.elseC/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)

Trigger condition Whenever a measurement report indicates that C/I value for the call related tothe neighbour cell is included in the corresponding interval.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




404 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.50 RMS8b - MR_CIN

Long Name MR_CIN



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 405 / 1256


18.1.1.1.1.51 RMS9a - TPR_CIF

Long Name TPR_CIF

Definition Table of 10 results per frequency reported by extended measurement.Eachcell i of the table contains :1) number of reports in which the C/I relatedto the extended measurement frequency is reported in C/I band i.Theresult is given as follows :Ci=Vi x 254 / RMS9b, where Vi represents thereal number of measurementsCi=0 indicates 'number of measurements =0'Ci=254 indicates 'number of measurements = Max_i'Ci=255 is reserved toindicate overflow.C/I band is defined by : MEAS_STAT_PATH_C_I_(i-1)<=C/I < MEAS_STAT_C_I_iMEAS_STAT_PATH_C_I_0 = -63 dBm,MEAS_STAT_PATH_C_I_10 = 63 dBmIf EN_BALANCED_CI = TRUEthenC/I (dB) = RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) -RXLEV_NCELLNote that the formula is written independently of the codingused for the variables. RXLEV_DL and RXLEV_NCELL are the received signallevels of the serving and of the neighbour cells, expressed in dBm. BS_TXPWRis the BTS transmitted power and BS_TXPWR_MAX is the maximum allowedBTS transmission power. Both are defined relatively to the maximum absoluteoutput power of the BTS (BTS_MAX_OUTPUT_POWER). BS_TXPWR andBS_TXPWR_MAX are expressed in dB. The function abs() gives the absolutevalue of its argument.elseC/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)

Trigger condition Whenever a measurement report indicates that C/I value for the extendedmeasurement frequency is included in the corresponding interval.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




406 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.1.1.1.52 RMS9b - MR_CIF

Long Name MR_CIF



Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 407 / 1256


18.1.1.1.1.53 RMSPw3 - MAX_POWER_PER_TRX

Long Name MAX_POWER_PER_TRX

Definition Maximum GMSK TRX power level applied at the BTS antenna output connectorin dBm.The power takes into account the different losses (cables, internalcombiners) and the internal/ external leveling but it does not take into accountthe BS-TXPWR-MAX, attenuation required by the OMC_R.If the feature"unbalancing TRX output power per BTS sector" is activated (parameter"En-Unbalanced-Output-Power" set to 1), the counter is set by the BTS to thepower required by the BSC for the corresponding TRE (i.e. for the TRE onwhich is mapped that TRX).

Trigger condition Information provided by the BTS in RMS_DATA_IND message.

Sub Domain 1 RMS

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




408 / 1256 3BK 21255 AAAA PCZZA Ed.07


18.1.2 Speech

18.1.2.1 –

18.1.2.1.1 –

18.1.2.1.1.1 RMS48b - MAX_AMR_HR_UL_RXLEV_UL

Long Name MAX_AMR_HR_UL_RXLEV_UL



Sub Domain 1 Speech

Sub Domain 2 –

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 409 / 1256



18.2.1 Channel

18.2.1.1 TCH

18.2.1.1.1 Usage

18.2.1.1.1.1 RMS31 - TOT_SEIZ_TCH

Long Name TOT_SEIZ_TCH

Definition Number of successful TCH seizures for the concerned cell. This counter takesinto account TCH in traffic or in signaling mode.

Trigger condition Whenever an ESTABLISH INDICATION message is received from the MS toindicate the activation of a TCH channel for normal assignment or handover.


Sub Domain 2 TCH

Sub Domain 3 Usage

Measured Object TRX




410 / 1256 3BK 21255 AAAA PCZZA Ed.07

19 BSC-TYPE 32 - Change of frequency band measurements

19 BSC-TYPE 32 - Change of frequency bandmeasurements

3BK 21255 AAAA PCZZA Ed.07 411 / 1256



19.1.1 Handover

19.1.1.1 TCH

19.1.1.1.1 –

19.1.1.1.1.1 C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT

Long Name NB_INC_EXT_TCH_HO_NEW_BAND_ATPT

Definition Number of incoming external TCH (in HR or FR usage) handover attemptsincluding a change of the (TCH) frequency band.

Trigger condition Whenever 48.008 HANDOVER_REQUEST_ACK is sent by the target BSCcontaining the 44.018HANDOVER COMMAND towards the target cell on TCHand the target and serving cell belong to different frequency bands. Remark:The change of the (TCH) frequency band for an incoming external handover canonly be detected and taken into account if the adjacency link is defined in bothdirections. In case of multiband cells, the BCCH frequency band of the servingcell will be taken as reference.Note: This counter counts both inter-PLMN andintra-PLMN handover events.


Sub Domain 2 TCH

Sub Domain 3 –


Type Name Change of frequency band measurements

Type Definition Set of counters related to handovers including a change of the TCH frequencyband.


412 / 1256 3BK 21255 AAAA PCZZA Ed.07


19.1.1.1.1.2 C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC

Long Name NB_INC_EXT_TCH_HO_NEW_BAND_SUCC

Definition Number of incoming external TCH (in HR or FR usage) handover successesincluding a change of the (TCH) frequency band.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel that is involved in an externalTCH handover with a change of the frequency band.Remark: The change of the(TCH) frequency band for an incoming external handover can only be detectedand taken into account if the adjacency link is defined in both directions. Incase of multiband cells, the BCCH frequency band of the serving cell will betaken as reference.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 413 / 1256


19.1.1.1.1.3 C404a - NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT

Long Name NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT

Definition Number of outgoing external TCH (in HR or FR usage) handover attemptsincluding a change of the (TCH) frequency band.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface on the serving channel, during an external TCH handover procedureincluding a change of the (TCH) frequency band.Note: This counter counts bothinter-PLMN and intra-PLMN handover events.In case of multiband cells, theBCCH frequency band of the target cell will be taken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





414 / 1256 3BK 21255 AAAA PCZZA Ed.07


19.1.1.1.1.4 C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC

Long Name NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC

Definition Number of outgoing external TCH (in HR or FR usage) handover successesincluding a change of the (TCH) frequency band.

Trigger condition External TCH handover including a change of the TCH frequency band, in thefollowing cases:1/ 48.008 CLEAR COMMAND message with a cause valueof "handover successful" is received.2/ 48.008 CLEAR COMMAND (cause ="normal event/call control") is received while T8 is running.Note: This countercounts both inter-PLMN and intra-PLMN handover events.In case of multibandcells, the BCCH frequency band of the target cell will be taken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 415 / 1256


19.1.1.1.1.5 C420a - NB_INC_INT_TCH_HO_NEW_BAND_ATPT

Long Name NB_INC_INT_TCH_HO_NEW_BAND_ATPT

Definition Number of incoming internal TCH (in HR or FR usage) handover attemptsincluding a change of the (TCH) frequency band.

Trigger condition Whenever a 44.018HANDOVER COMMAND with a target cell belonging to adifferent frequency band is sent to the serving BTS for internal inter cell TCHhandover. However, the counter is incremented in the TARGET cell, based onthe target cell ID indicated by the HO Command message.In case of multibandcells, the BCCH frequency band of the target cell will be taken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





416 / 1256 3BK 21255 AAAA PCZZA Ed.07


19.1.1.1.1.6 C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC

Long Name NB_INC_INT_TCH_HO_NEW_BAND_SUCC

Definition Number of incoming internal TCH (in HR or FR usage) handover successesincluding a change of the (TCH) frequency band.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel that is involved in an internalinter-cell TCH handover including a change of the (TCH) frequency band.Incase of multiband cells, the BCCH frequency band of the target cell will betaken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 417 / 1256


19.1.1.1.1.7 C421a - NB_OUT_INT_TCH_HO_NEW_BAND_ATPT

Long Name NB_OUT_INT_TCH_HO_NEW_BAND_ATPT

Definition Number of outgoing internal TCH (in HR or FR usage) handover attemptsincluding a change of the (TCH) frequency band.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface on the serving channel, during an internal inter-cell TCH handoverprocedure including a change of the (TCH) frequency band.In case of multibandcells, the BCCH frequency band of the target cell will be taken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





418 / 1256 3BK 21255 AAAA PCZZA Ed.07


19.1.1.1.1.8 C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC

Long Name NB_OUT_INT_TCH_HO_NEW_BAND_SUCC

Definition Number of outgoing internal TCH (in HR or FR usage) handover successesincluding a change of the (TCH) frequency band.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell , during an internal inter-cell TCH handoverincluding a change of the (TCH) frequency band.In case of multiband cells, theBCCH frequency band of the target cell will be taken as reference.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 419 / 1256


420 / 1256 3BK 21255 AAAA PCZZA Ed.07

20 BSC-TYPE 33 - Electro-Magnetic Emission counters


3BK 21255 AAAA PCZZA Ed.07 421 / 1256


20.1 Electro-Magnetic Emission

20.1.1 –

20.1.1.1 –

20.1.1.1.1 –

20.1.1.1.1.1 E01 - EME_PWR_GSM

Long Name EME_PWR_GSM

Definition Average emitted power at the BTS antenna output connector for the GSMfrequency band (GSM850 or E-GSM or P-GSM).Counter coded in tenth of Watt.Value 0 indicates that the TRX frequency is neither GSM850 nor E-GSM norP-GSM band. Value FFFFh indicates overflow of the measurement period.

Trigger condition TRE collects permanently power data. At the end of each measurement period,triggered by reception of EME_DATA_REQ message from the BSC, the averageemitted power is calculated and sent back to the BSC.

Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –


Type Name Electro-Magnetic Emission counters

Type Definition Set of counters related to electromagetic emission measurements in the BTS.

External Comment Counter coded in tenth of Watt. Value 0 indicates that TRX frequency isneither 900 MHz nor 850 MHz.This counter is only reported for cells mappedon Evolium BTS.

422 / 1256 3BK 21255 AAAA PCZZA Ed.07


20.1.1.1.1.2 E02 - EME_PWR_DCS

Long Name EME_PWR_DCS

Definition Average emitted power at the BTS antenna output connector for the DCSfrequency band (DCS1800 or DCS1900).Counter coded in tenth of Watt. Value0 indicates that the TRX frequency is neither DCS1800 nor DCS1900 band.Value FFFFh indicates overflow of the measurement period.

Trigger condition TRE collects permanently power data. At the end of each measurement period,triggered by reception of EME_DATA_REQ message from the BSC, the averageemitted power is calculated and sent back to the BSC.

Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –


Type Name Electro-Magnetic Emission counters

Type Definition Set of counters related to electromagetic emission measurements in the BTS.


3BK 21255 AAAA PCZZA Ed.07 423 / 1256


424 / 1256 3BK 21255 AAAA PCZZA Ed.07

21 BSC-TYPE 34 - Voice Group Call Services


3BK 21255 AAAA PCZZA Ed.07 425 / 1256


21.1 Handover

21.1.1 TCH

21.1.1.1 –

21.1.1.1.1 –

21.1.1.1.1.1 V09 - NB_INC_VGCS_HO_SUCC

Long Name NB_INC_VGCS_HO_SUCC

Definition Number of successful incoming handover for VGC-talker per cell duringobservation period.Since there are no reliable means at the target BSC todistinguish external directed retry from external handover, the external directedretries are counted by this counter.Intracell handover are not counted.

Trigger condition This counter is incremented for internal inter-cell or external handover, i. e. :whenever a 44.018 HANDOVER COMPLETE message is received from the MSin the target cell for the channel of the VGCS talker.

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –


Type Name Voice Group Call Services

Type Definition Set of counters related to Voice Group Call Services (VGCS).


426 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.1.1.1.1.2 V10 - NB_INC_VGCS_HO_ATPT

Long Name NB_INC_VGCS_HO_ATPT

Definition Number of incoming handover attempts for VGC-talker per cell duringobservation period.Intracell, internal intercell and external handovers arecounted together.Intracell handover are not counted.

Trigger condition External handover :Whenever 48.008HANDOVER REQUEST ACK is sent bythe target BSC containing the 44.018HANDOVER COMMAND towards thetarget cell on TCH, for a VGC-talker.Internal intercell handover :Whenever a44.018HANDOVER COMMAND is sent to the serving BTS for internal intercell TCH handover, for a VGC talker. However, the counter is incremented inthe TARGET cell, based on the target cell ID indicated by the HO Commandmessage.

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 427 / 1256




21.2.1.1 –

21.2.1.1.1 –

21.2.1.1.1.1 V06 - NB_VGC_RELEASED_VGCS

Long Name NB_VGC_RELEASED_VGCS

Definition Number of released VGC per cell during observation period.

Trigger condition This counter is incremented each time a 48.008 CLEAR COMMAND is receivedfrom the MSC on the VGCS resource controlling SCCP connection, i. e. on theSCCP connection initiated with VGCS/VBS ASSIGNMENT REQUEST.


Sub Domain 2 –

Sub Domain 3 –





428 / 1256 3BK 21255 AAAA PCZZA Ed.07



21.2.2.1 –

21.2.2.1.1 –

21.2.2.1.1.1 V03 - NB_VGCS_ESTABLISHMENT_REQ

Long Name NB_VGCS_ESTABLISHMENT_REQ

Definition Number of VGC establishment requests per cell during observation period.

Trigger condition This counter is incremented each time the BSS receives a 48.008 VGCS/VBSASSIGNMENT REQUEST from the MSC.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 429 / 1256


21.2.2.1.1.2 V04 - NB_VGCS_ESTABLISHMENT_SUCC

Long Name NB_VGCS_ESTABLISHMENT_SUCC

Definition Number of successfully established VGC per cell during observation period.

Trigger condition This counter is incremented each time the BSS sends the first 48.008VGCS/VBS ASSIGNMENT RESULT to the MSC corresponding to a VGCS/VBSASSIGNMENT REQUEST.


Sub Domain 2 –

Sub Domain 3 –





430 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.2.2.1.1.3 V05 - NB_CM_SERV_REQ_VGCS

Long Name NB_CM_SERV_REQ_VGCS

Definition Number of received CM_SERVICE-REQ for VGC per cell during observationperiod.

Trigger condition This counter is incremented each time the BSS receives a CM SERVICEREQUEST message with parameter CM Service Type set to "Voice group callestablishment (1001)".


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 431 / 1256


21.2.2.1.1.4 V12 - NB_VGC_BLOCKED_VGCS

Long Name NB_VGC_BLOCKED_VGCS

Definition Number of blocked VGC due to lack of resources per cell during observationperiod.

Trigger condition This counter is incremented when the BSC cannot allocate the VGCH, i. e.sends to the MSC:- The 48.008 VGCS/VBS ASSIGNMENT FAILURE messagewith cause parameter set to "Resource unavailable (010)" whenever 1/ no TCHis available and either: - queuing was not requested by the MSC (parameter"priority.qa" set to "queuing not allowed 0") in case of immediate allocation(parameter "assignment requirement" set to "immediate and the resources shallnot be de-allocated until the end of the call (channel establishment on demandforbidden by the MSC) 00000001" or "immediate and the resources may furtherbe de-allocated by the BSS (channel establishment on demand forbidden by theMSC) 00000010" ; - queuing was requested by the MSC (parameter "priority.qa"set to "queuing allowed 1") but disabled in the BSC ; - queuing was requested bythe MSC but the queue is full and no request of lower priority can be dequeued ;- the request is dequeued due to the reception of higher priority request ; -the request is dequeued due to T14 timer expiry ;2/ the maximum number ofTCH allowed for VGCs has been reached ;- the 48.008 CLEAR REQUESTmessage with cause parameter set to "resource unavailable 010" in case ofdelayed allocation for a VGCH (i. e. sent over an SCCP connection previouslyestablished with a 48.008 VGCS/VBS ASSIGNMENT REQUEST messagewith parameter "assignment requirement" set to "delay allowed 00000000" andparameter "priority.qa" set to "queuing not allowed 0", whenever no more TCH isavailable or the maximum number of TCH allowed for VGCs has been reached.


Sub Domain 2 –

Sub Domain 3 –





432 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.2.2.1.1.5 V14 - NB_ASS_REQ_ABLE_PREEMT

Long Name NB_ASS_REQ_ABLE_PREEMT

Definition Number of ASSIGNEMENT REQUEST able to pre-empt per cell duringobservation period.

Trigger condition This counter is incremented each time the BSC receives a 48.008ASSIGNEMENT REQUEST message with "Preemption Capability indicator(pci)" of "Priority" parameter set to "this allocation request may preempt anexisting connection (1)".Notes :1) This counter is not limited to VGC, so italso counts messages related to point-to-point calls.2) Repetitions of theASSIGNMENT REQUEST message in case of channel modification are notcounted.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 433 / 1256


21.2.2.1.1.6 V15 - NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT

Long Name NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT

Definition Number of VGCS/VBS ASSIGNEMENT REQUEST able to pre-empt per cellduring observation period.

Trigger condition This counter is incremented each time the BSC receives from the MSC aVGCS/VBS ASSIGNEMENT REQUEST message with "Preemption Capabilityindicator (pci)" of "Priority" parameter set to "this allocation request may preemptan existing connection (1)".


Sub Domain 2 –

Sub Domain 3 –





434 / 1256 3BK 21255 AAAA PCZZA Ed.07



21.2.2.2.1 –

21.2.2.2.1.1 V01 - NB_PTP_CALL_PREEMPTED_VGCS

Long Name NB_PTP_CALL_PREEMPTED_VGCS

Definition Number of point-to-point CS-calls pre-empted for VGC channels per cell duringobservation period.

Trigger condition This counter is incremented each time a 48.008 CLEAR REQUEST message issent to the MSC under the three following conditions :- "Cause" parameter is setto "Premption (0101001)" ;- sent on a point-to-point SCCP connection, excludingthe VGCS talker connexion ;- sent further to the reception and processing ofeither - a 48.008 VGCS/VBS ASSIGNEMENT REQUEST message receivedfrom the MSC with "Priority" parameter having the information element"Preemption Capability indicator (pci)" set to "this allocation request may preemtan existing connection (1)" ; or - a 48.008 ASSIGNEMENT REQUEST messagereceived from the MSC with "talker flag" parameter present and with "Priority"parameter having the information element "Preemption Capability indicator(pci)" set to "this allocation request may preemt an existing connection (1)".



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 435 / 1256



21.2.3.1 –

21.2.3.1.1 –

21.2.3.1.1.1 V18 - NB_PREEMTED_TCH_VGCS

Long Name NB_PREEMTED_TCH_VGCS

Definition Number of pre-empted TCHper cell during observation period.

Trigger condition This counter is incremented each time a 48.008 CLEAR REQUEST or a 48.008UPLINK RELEASE INDICATIONwith parameter "Cause" set to "pre-emption(0101001)" is sent to the MSC.Note 1: Any pre-empted TCH is counted (i. e.point-to-point call TCH, VGC talker TCH, VGC listener TCH).Note 2: Whateverthe TCH is pre-emted for (point-to-point call TCH, VGC talker TCH, VGC listenerTCH), the counter is incremented.


Sub Domain 2 –

Sub Domain 3 –





436 / 1256 3BK 21255 AAAA PCZZA Ed.07



21.3.1 Channel

21.3.1.1 TCH

21.3.1.1.1 –

21.3.1.1.1.1 V021 - AV_PARALLEL_TCH_VGCS

Long Name AV_PARALLEL_TCH_VGCS

Definition Average number of parallel TCH in use for VGCS per cell during observationperiod.TCH used for VGC listening service and TCH used for VGC talkingservice are both counted.

Trigger condition The BSC takes periodically a sample of the number of busy TCH radio timeslotsallocated for VGCS.The sampling period is set to the value indicated in theStatus Inspection field.At the expiry of the accumulation period, all samples areaveraged with an accuracy of 0.1 (i.e. summed, multiplied by 10 and dividedby the number of samples). The averaged value is rounded up or down to thenearest value.Note : The reported value shall then be divided by 10 so that thevalue that is taken into acount (interger and decimal parts) is the correct one.


Sub Domain 2 TCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 437 / 1256


21.3.1.1.1.2 V022 - MAX_PARALLEL_TCH_VGCS

Long Name MAX_PARALLEL_TCH_VGCS

Definition Maximum number of parallel TCH in use for VGCS per cell during observationperiod.TCH used for VGC listening service and TCH used for VGC talkingservice are both counted.

Trigger condition Whenever a TCH radio timeslot is allocated for VGCS, the BSC determines thecurrent number of busy TCH radio timeslots allocated to VGCS. This counter isthe maximum value of this number during the accumulation period.Note: bothtalker TCH and listener TCH are counted.


Sub Domain 2 TCH

Sub Domain 3 –





438 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.4 Traffic Load

21.4.1 Channel

21.4.1.1 –

21.4.1.1.1 –

21.4.1.1.1.1 V13 - NB_VGCS_NOTIFIFICATION_FACCH

Long Name NB_VGCS_NOTIFIFICATION_FACCH

Definition Number of VGC notifications sent over FACCH per cell during observationperiod.

Trigger condition This counter is incremented each time the BSC sends a 48.058 UNIT DATAREQUEST (NOTIFICATION/FACCH) message to the BTS with the indication"Group Call Information".Note : this counter does not include paging requests.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 439 / 1256


21.4.1.1.1.2 V19 - NB_PAGING_FACCH

Long Name NB_PAGING_FACCH

Definition Number of PTP pagings sent over FACCH per cell during observation period.

Trigger condition This counter is incremented each time the BSC sends a 48.058 UNIT DATAREQUEST (NOTIFICATION/FACCH) message to the BTS with the indication"Paging Information".Note : this counter does not include notification of VGCS.


Sub Domain 2 –

Sub Domain 3 –





440 / 1256 3BK 21255 AAAA PCZZA Ed.07



21.4.2.1 –

21.4.2.1.1 –

21.4.2.1.1.1 V07 - NB_OUT_VGCS_HO_ATPT

Long Name NB_OUT_VGCS_HO_ATPT

Definition Number of outgoing handover attempts for VGC-talker per cell duringobservation period.Intracell, internal intercell and external handovers arecounted together.

Trigger condition Internal intercell HO, external HO :This counter is incremented each time the44.018 HANDOVER COMMAND message is sent to the MS on the servingchannel, during a TCH handover procedure for a VGCS talker.Intracell HO:This counter is incremented each time a 44.018 ASSIGNMENT COMMANDmessage is sent to the MS for a TCH handover procedure for a VGCS talker.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 441 / 1256


21.4.2.1.1.2 V08 - NB_OUT_VGCS_HO_SUCC

Long Name NB_OUT_VGCS_HO_SUCC

Definition Number of successful outgoing handover for VGC-talker per cell duringobservation period.Intracell, internal intercell and external handovers arecounted together.

Trigger condition This counter is incremented in following cases :1) External HO: whenever48.008 CLEAR COMMAND (cause="handover successful") is received on theserving BSC on the channel of the CGCS talker ;2) Internal inter-cell HO:whenever 44.018 HANDOVER COMPLETE is received from the MS via thetarget cell on the channel of the VGCS talker ;3) Internal intra-cell HO: whenever44.018 ASSIGNMENT COMPLETE is received from the MS via the cell on thechannel of the VGCS talker.


Sub Domain 2 –

Sub Domain 3 –





442 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.4.2.1.1.3 V11 - NB_TALKER_CHANGE_VGCS

Long Name NB_TALKER_CHANGE_VGCS

Definition Number of talker change in the BSC during observation period.This counter isthe TOTAL number of talker change in the BSC during the observation period.

Trigger condition This counter is increment each time the BSC sends a 48.008 UPLINKREQUEST CONFIRMATION message to the MSC.


Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 443 / 1256


21.4.2.1.1.4 V16 - NB_VGCS_QUEUED

Long Name NB_VGCS_QUEUED

Definition Number of VGC queued per cell during the polling period.

Trigger condition This counter is incremented each time a VGCS/VBS QUEUING INDICATIONmessage is sent to the MSC.


Sub Domain 2 –

Sub Domain 3 –





444 / 1256 3BK 21255 AAAA PCZZA Ed.07


21.4.2.1.1.5 V17 - NB_VGCS_ESTABLISHED

Long Name NB_VGCS_ESTABLISHED

Definition Number of VGC successfully established per BSC during the observation period.

Trigger condition This counter is incremented each time the BSC sens a 48.008 VGCS/VBSSETUP ACKNOWLEDGE message to the MSC.


Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 445 / 1256


446 / 1256 3BK 21255 AAAA PCZZA Ed.07

22 BSC-TYPE 110 - Overview measurements


3BK 21255 AAAA PCZZA Ed.07 447 / 1256


22.1 –

22.1.1 –

22.1.1.1 –

22.1.1.1.1 –

22.1.1.1.1.1 MC940 - Reserve_BSC_1

Long Name Reserve_BSC_1

Definition For future usage

Trigger condition The value of this provisioned counter shall be set to "0"

Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type


448 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.1.1.1.1.2 MC941 - Reserve_BSC_2




Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 449 / 1256


22.1.1.1.1.3 MC942 - Reserve_BSC_3




Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




450 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.1.1.1.1.4 MC943 - Reserve_BSC_4


Definition For Future usage


Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 451 / 1256


22.1.1.1.1.5 MC944 - Reserve_BSC_5




Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




452 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.1.1.1.1.6 MC945 - Reserve_BSC_6




Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 453 / 1256


22.1.1.1.1.7 MC938 - NB_CALL_TFO_AMR

Long Name NB_CALL_TFO_AMR

Definition For future usage (Number of TCH assigned using AMR for which TFO hasbeen successfully established).

Trigger condition The value of this provisioned counter shall be set to "0".

Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –





454 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.1.1.1.1.8 MC939 - NB_HO_INTER_TFO_AMR

Long Name NB_HO_INTER_TFO_AMR

Definition For future usage (Number of TCH assigned using AMR for which TFO has beensuccessfully established after an inter cell handover).


Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 455 / 1256


22.1.1.1.1.9 MC950 - NB_HO_EXT_TFO_AMR

Long Name NB_HO_EXT_TFO_AMR

Definition For future usage (Number of TCH assigned using AMR for which TFO has beensuccessfully established after an external handover).


Sub Domain 1 –

Sub Domain 2 –

Sub Domain 3 –





456 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2 Handover


22.2.1.1 Internal

22.2.1.1.1 Incoming

22.2.1.1.1.1 MC151 - NB_INC_IDR_SUCC (29)

Long Name NB_INC_IDR_SUCC (29)

Definition Number of incoming internal directed retry (forced or normal, towards a TCHchannel in HR or FR usage) successes.

Trigger condition Whenever 44.018HANDOVER COMPLETE is received from the MS via thetarget cell, for a forced or internal internal directed retry procedure.








3BK 21255 AAAA PCZZA Ed.07 457 / 1256


22.2.1.1.1.2 MC153 - NB_INC_IDR_REQ

Long Name NB_INC_IDR_REQ

Definition MC153=C153, Number of incoming internal directed retry (forced or normal)requests. The target TCH channel can be in HR or FR usage.

Trigger condition Whenever the BSC process responsible for handover procedure selects thetarget cell for forced or normal internal directed retry.








458 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.1.1.1.3 MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_IDR_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming internal directed retry (forced or normal) -preparationfailures due to congestion (on Air or A-bis interface). The target TCH channelcan be in HR or FR usage.

Trigger condition 1) Whenever there are no free TCH in the target cell during a forced or normalinternal directed retry.2) Whenever no TCH resource is available on A-bisinterface for a forced or normal internal directed retry. (not valid in B7).Note 1: InMX BSC, this counter is incremented whenever a TCH cannot be not allocateddue to the TCH processing capacity of CCP reaches the limit defined by theMAX_TCH_PER_CCP parameter. In this case, MC926 is also incrementedby one.Note 2: In IP mode, this counter is increased by 1 if:- the cell mappedon a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter








3BK 21255 AAAA PCZZA Ed.07 459 / 1256



22.2.2.1 –

22.2.2.1.1 –

22.2.2.1.1.1 MC480 - NB_TCH_HO_REQ_30_ReturnCSZone

Long Name NB_TCH_HO_REQ_30_ReturnCSZone

Definition Number of TCH intracell HO cause 30 requests

Trigger condition Whenever the BSC detects that a TCH needs to be moved from PS zone toCS zone, I.e. whenever at MAX_SPDCH_LIMIT calculation time, the BSCdetects that 1 TCH is allocated in both MAX_SPDCH_LIMIT zone and the nonpre-emptable PS zone and EN_RETURN_CS_ZONE_HO = Enabled.


Sub Domain 2 –

Sub Domain 3 –





460 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.2.1.1.2 MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone

Long Name NB_TCH_HO_ATPT_30_ReturnCSZone

Definition Number of TCH intracell HO cause 30 attempts.

Trigger condition Whenever a 44.018 Assignment Command is sent to the MS for a TCH HOcause 30.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 461 / 1256


22.2.2.1.1.3 MC922g - NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG

Long Name NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG

Definition Number of 3G to 2G TCH hand over failures in preparation phase due to 3Ghigh load in the target cell.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message is sent to the MSC withcause "no radio resource available" for a TCH HO request coming from 3G, dueto 3G high load in the target cell. This counter shall be incremented only ifTHR_CELL_LOAD_3G_REJECT < 100%.


Sub Domain 2 –

Sub Domain 3 –





462 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.3 SDCCH

22.2.3.1 Cause

22.2.3.1.1 –

22.2.3.1.1.1 MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR

Long Name NB_SDCCH_HO_20_HighLevNeigCellForcDR

Definition MC607=C607, Number of SDCCH inter-cell internal or external handoverattempts with cause 20: "forced directed retry". This counter is related to aforced directed retry (internal or external).

Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 20.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 463 / 1256



22.2.3.2.1 –

22.2.3.2.1.1 MC81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG

Definition MC81=C81, Number of incoming external SDCCH handover -preparationfailures due to congestion.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of"no radio resource available" is sent on A interface from the target BSC to theMSC during an external SDCCH handover.Note: This counter counts bothinter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 3 –





464 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.2.3.3.1 –

22.2.3.3.1.1 MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG

Definition MC91=C91, Number of incoming internal inter-cell SDCCH handover-preparation failures due to congestion.

Trigger condition Whenever a internal inter-cell SDCCH handover cannot be performed, becausethere is no free SDCCH Sub-channel to allocate the handover to.

Sub Domain 1 SDCCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 465 / 1256


22.2.3.4 Intra

22.2.3.4.1 –

22.2.3.4.1.1 MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG

Long Name NB_INTRA_SDCCH_HO_PREP_FAIL_CONG

Definition MC101=C101, Number of intra-cell SDCCH handover -preparation failures dueto congestion.

Trigger condition Whenever a internal intra-cell SDCCH handover cannot be performed, becausethere is no free SDCCH Sub-channel to allocate the handover to.

Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 –





466 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4 SDCCH+TCH

22.2.4.1 –

22.2.4.1.1 –

22.2.4.1.1.1 MC922a - NB_INC_EXT_3G_2G_HO_REQ

Long Name NB_INC_EXT_3G_2G_HO_REQ

Definition Number of incoming external SDCCH and TCH HO requests from a UMTSsystem.

Trigger condition 48.008 HANDOVER REQUEST received by the BSC for an SDCCH or TCHexternal handover towards the target cell. Only handovers from a UMTS systemshall be taken into account (if the field Cell Identifier discriminator in the I.E. CellIdentifier (serving) of the 48.008 HANDOVER REQUEST is set to 1011)


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 467 / 1256


22.2.4.1.1.2 MC922b - NB_INC_EXT_3G_2G_HO_SUCC

Long Name NB_INC_EXT_3G_2G_HO_SUCC

Definition Number of incoming external SDCCH and TCH HO successes from a UMTSsystem.

Trigger condition 44.018HANDOVER_COMPLETE message received from the MS. Onlyhandovers from a UMTS system shall be taken into account (if the field CellIdentifier discriminator in the I.E. Cell Identifier (serving) of the corresponding48.008 HANDOVER REQUEST is set to 1011).


Sub Domain 2 –

Sub Domain 3 –





468 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.1.1.3 MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC

Long Name NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC

Definition Number of incoming external TCH and SDCCH UMTS to GSM HO executionfailures due to MS access problem, with or without reversion of the mobile tothe old channel.

Trigger condition 1) Reception of 48.058CONNECTION FAILURE INDICATION (cause="handover access failure") for a HO from a UMTS system.2) Reception of48.008CLEAR COMMAND (cause= "radio interface failure, reversion to oldchannel") for a HO from a UMTS system. Handovers from a UMTS system areidentified as follows: the field Cell Identifier discriminator in the I.E. Cell Identifier(serving) of the 48.008 HANDOVER REQUEST is set to 1011)


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 469 / 1256


22.2.4.1.1.4 MC922d - NB_INC_EXT_3G_2G_HO_ATPT

Long Name NB_INC_EXT_3G_2G_HO_ATPT

Definition Number of incoming external SDCCH and TCH HO attempts from a UMTSsystem.

Trigger condition Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSCcontaining the 44.018HANDOVER COMMAND towards the target cell. Onlyhandovers from a UMTS system shall be taken into account (if the field CellIdentifier discriminator in the I.E. Cell Identifier (serving) of the corresponding48.008 HANDOVER REQUEST is set to 1011)


Sub Domain 2 –

Sub Domain 3 –





470 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2 Cause

22.2.4.2.1 –

22.2.4.2.1.1 MC1040 - NB_HO_ATPT_23_TrafHandover

Long Name NB_HO_ATPT_23_TrafHandover

Definition MC1040=C440+C445



Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 471 / 1256


22.2.4.2.1.2 MC1044 - NB_HO_ATPT_24_gencapture

Long Name NB_HO_ATPT_24_gencapture




Sub Domain 2 Cause

Sub Domain 3 –





472 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.3 MC1050 - NB_HO_22_TooShortDistance

Long Name NB_HO_22_TooShortDistance




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 473 / 1256


22.2.4.2.1.4 MC670 - NB_HO_2_TooLowQualUp

Long Name NB_HO_2_TooLowQualUp




Sub Domain 2 Cause

Sub Domain 3 –





474 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.5 MC671 - NB_HO_3_TooLowLevUp

Long Name NB_HO_3_TooLowLevUp




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 475 / 1256


22.2.4.2.1.6 MC672 - NB_HO_4_TooLowQualDown

Long Name NB_HO_4_TooLowQualDown




Sub Domain 2 Cause

Sub Domain 3 –





476 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.7 MC673 - NB_HO_5_TooLowLevDown

Long Name NB_HO_5_TooLowLevDown




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 477 / 1256


22.2.4.2.1.8 MC674 - NB_HO_6_TooLongDistance

Long Name NB_HO_6_TooLongDistance




Sub Domain 2 Cause

Sub Domain 3 –





478 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.9 MC675 - NB_HO_MSC_TRIG

Long Name NB_HO_MSC_TRIG




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 479 / 1256


22.2.4.2.1.10 MC676 - NB_HO_15_TooHighLevInterfUp

Long Name NB_HO_15_TooHighLevInterfUp




Sub Domain 2 Cause

Sub Domain 3 –





480 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.11 MC677 - NB_HO_16_TooHighLevInterfDown

Long Name NB_HO_16_TooHighLevInterfDown




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 481 / 1256


22.2.4.2.1.12 MC678 - NB_HO_12_TooLowPowBudg

Long Name NB_HO_12_TooLowPowBudg




Sub Domain 2 Cause

Sub Domain 3 –





482 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.13 MC679 - NB_HO_21_HighLevNeigCellPrefBand

Long Name NB_HO_21_HighLevNeigCellPrefBand




Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 483 / 1256


22.2.4.2.1.14 MC785a - NB_HO_7_ConsBadSACCHmicroCell

Long Name NB_HO_7_ConsBadSACCHmicroCell

Definition MC785a=C585a+C605a



Sub Domain 2 Cause

Sub Domain 3 –





484 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.15 MC785d - NB_HO_17_TooLowLevUpMicroCell

Long Name NB_HO_17_TooLowLevUpMicroCell

Definition MC785d=C585d+C605d



Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 485 / 1256


22.2.4.2.1.16 MC785e - NB_HO_18_TooLowLevDownMicroCell

Long Name NB_HO_18_TooLowLevDownMicroCell

Definition MC785e=C585e+C605e



Sub Domain 2 Cause

Sub Domain 3 –





486 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.2.1.17 MC785f - NB_HO_14_HighLevNeigLowCellSlowMS

Long Name NB_HO_14_HighLevNeigLowCellSlowMS

Definition MC785f=C585f+C605f



Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 487 / 1256



22.2.4.3.1 –

22.2.4.3.1.1 MC642 - NB_INC_EXT_HO_SUCC

Long Name NB_INC_EXT_HO_SUCC





Sub Domain 3 –





488 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.3.1.2 MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 489 / 1256


22.2.4.3.1.3 MC820 - NB_INC_EXT_HO_REQ

Long Name NB_INC_EXT_HO_REQ





Sub Domain 3 –





490 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.3.1.4 MC821 - NB_INC_EXT_HO_ATPT

Long Name NB_INC_EXT_HO_ATPT





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 491 / 1256



22.2.4.4.1 –

22.2.4.4.1.1 MC652 - NB_INC_INT_HO_SUCC

Long Name NB_INC_INT_HO_SUCC





Sub Domain 3 –





492 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.4.1.2 MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS

Long Name NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 493 / 1256


22.2.4.4.1.3 MC830 - NB_INC_INT_HO_REQ

Long Name NB_INC_INT_HO_REQ





Sub Domain 3 –





494 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.4.1.4 MC831 - NB_INC_INT_HO_ATPT

Long Name NB_INC_INT_HO_ATPT





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 495 / 1256


22.2.4.5 Intra

22.2.4.5.1 –

22.2.4.5.1.1 MC662 - NB_INTRA_HO_SUCC

Long Name NB_INTRA_HO_SUCC




Sub Domain 2 Intra

Sub Domain 3 –





496 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.5.1.2 MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV

Long Name NB_INTRA_HO_EXEC_FAIL_NO_REV




Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 497 / 1256


22.2.4.5.1.3 MC667 - NB_INTRA_HO_EXEC_FAIL_REV

Long Name NB_INTRA_HO_EXEC_FAIL_REV




Sub Domain 2 Intra

Sub Domain 3 –





498 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.5.1.4 MC870 - NB_INTRA_HO_REQ

Long Name NB_INTRA_HO_REQ




Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 499 / 1256


22.2.4.5.1.5 MC871 - NB_INTRA_HO_ATPT

Long Name NB_INTRA_HO_ATPT




Sub Domain 2 Intra

Sub Domain 3 –





500 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.2.4.6.1 –

22.2.4.6.1.1 MC645a - NB_OUT_EXT_REAL_HO_REQ

Long Name NB_OUT_EXT_REAL_HO_REQ

Definition MC645a = C45a + C85a

Trigger condition Whenever a 48.008 HANDOVER REQUIRED message with the cellidentification discriminator set to a value identifying a GSM handover issent on A interface from the serving cell to the MSC for a TCH handover(C45a) or an SDCCH handover (C85a) towards a 2G cell. If more than one48.008 HANDOVER REQUIRED is sent in the frame of the same Handoverprocedure, the respective counter is incremented only once.48.008 HANDOVERREQUIRED is sent in following situations:1) An external handover alarm hasbeen raised, with corresponding list of candidate cells.2) The list of candidatecells for the current alarm has been updated.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 501 / 1256


22.2.4.6.1.2 MC646 - NB_OUT_EXT_HO_SUCC

Long Name NB_OUT_EXT_HO_SUCC





Sub Domain 3 –





502 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.6.1.3 MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV

Long Name NB_OUT_EXT_HO_EXEC_FAIL_REV





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 503 / 1256


22.2.4.6.1.4 MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_EXT_HO_EXEC_FAIL_NO_REV





Sub Domain 3 –





504 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.6.1.5 MC650 - NB_OUT_EXT_HO_ATPT

Long Name NB_OUT_EXT_HO_ATPT





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 505 / 1256



22.2.4.7.1 –

22.2.4.7.1.1 MC655a - NB_OUT_INT_HO_REQ

Long Name NB_OUT_INT_HO_REQ

Definition MC655a=C55a+C95a




Sub Domain 3 –





506 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.7.1.2 MC656 - NB_OUT_INT_HO_SUCC

Long Name NB_OUT_INT_HO_SUCC





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 507 / 1256


22.2.4.7.1.3 MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV

Long Name NB_OUT_INT_HO_EXEC_FAIL_REV





Sub Domain 3 –





508 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.4.7.1.4 MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_INT_HO_EXEC_FAIL_NO_REV





Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 509 / 1256


22.2.4.7.1.5 MC660 - NB_OUT_INT_HO_ATPT

Long Name NB_OUT_INT_HO_ATPT





Sub Domain 3 –





510 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.5 Speech

22.2.5.1 TFO

22.2.5.1.1 –

22.2.5.1.1.1 MC936 - NB_HO_INTER_TFO_AMR_WB

Long Name NB_HO_INTER_TFO_AMR_WB

Definition Number of TCH assigned using AMR-WB for which TFO has been successfullyestablished after an inter cell handover

Trigger condition For each assigned TCH further to an inter cell handover, the counter isincremented the first time a 48.058 TFO REPORT message is received by theBSC, indicating that TFO is established (i.e. TFO = 1 in the TFO Status IE) andthe used codec is an AMR WB one (i.e. FR sv5).Note 1: This counter shall beincremented only once per assigned TCH (i.e. the first time it is received for theassigned TCH).Note 2: This means that the counter is incremented only if theTCH is assigned to serve an incoming inter-cell handover.

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 511 / 1256


22.2.5.1.1.2 MC937 - NB_HO_EXT_TFO_AMR_WB

Long Name NB_HO_EXT_TFO_AMR_WB

Definition Number of TCH assigned using AMR-WB for which TFO has been successfullyestablished after an external handover

Trigger condition For each assigned TCH further to an external handover, the counter isincremented the first time a 48.058 TFO REPORT message is received by theBSC, indicating that TFO is established (i.e. TFO = 1 in the TFO Status IE) andthe used codec is an AMR WB one (i.e. FR sv5).Note 1: This counter shall beincremented only once per assigned TCH (i.e. the first time it is received for theassigned TCH).Note 2: This means that the counter is incremented only if theTCH is assigned to serve an incoming iexternal handover.

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





512 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6 TCH

22.2.6.1 –

22.2.6.1.1 –

22.2.6.1.1.1 MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ

Long Name NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ

Definition Number of incoming 3G to 2G external inter-cell TCH (in HR or FR usage)handover requests, with emergency cause.

Trigger condition Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAIin the source cell identifier and indicating an emergency cause (uplink quality,uplink strength, downlink quality, downlink strength, distance).

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 513 / 1256


22.2.6.1.1.2 MC922f - NB_INC_EXT_TCH_3G_2G_HO_REQ

Long Name NB_INC_EXT_TCH_3G_2G_HO_REQ

Definition Number of incoming 3G to 2G external inter-cell TCH (in HR or FR usage)handover requests.

Trigger condition Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAI inthe source cell identifier

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





514 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.2 Cause

22.2.6.2.1 –

22.2.6.2.1.1 MC448a - NB_TCH_HO_ATPT_26_BadQualHR

Long Name NB_TCH_HO_ATPT_26_BadQualHR

Definition Number of intracell handover attempts, with the cause 26: "HR to FR channeladaptation due to bad radio quality" on a TCH channel.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 515 / 1256


22.2.6.2.1.2 MC448b - NB_TCH_HO_ATPT_27_GoodQualFR

Long Name NB_TCH_HO_ATPT_27_GoodQualFR

Definition Number of intracell handover attempts, with the cause 27: "FR to HR channeladaptation due to good radio quality" on a TCH channel.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





516 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.2.1.3 MC449 - NB_TCH_HO_ATPT_28_FastTraffic

Long Name NB_TCH_HO_ATPT_28_FastTraffic

Definition Number of handover attempts, with the cause 28 (Fast Traffic Handover).

Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTSbecause of cause 28 on TCH. This counter is incremented in the serving cell.

Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 517 / 1256


22.2.6.2.1.4 MC461 - NB_TCH_HO_ATPT_29_TFO

Long Name NB_TCH_HO_ATPT_29_TFO

Definition Number of intra-cell handover - attempts, with the cause 29 (TFO mismatchresolution, TFO optimisation).MC461 = C461


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





518 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.2.1.5 MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone

Long Name NB_TCH_HO_ATPT_10_TooLowLevUpInZone

Definition Number of intra-cell handover attempts, with cause 10 "Inner zone uplink leveltoo low" on TCH channel (in HR or FR usage). This counter is related toconcentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 519 / 1256


22.2.6.2.1.6 MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone

Long Name NB_TCH_HO_ATPT_11_TooLowLevDownInZone

Definition Number of intra-cell handover attempts, with cause 11: "Inner zone downlinklevel too low" on TCH channel (in HR or FR usage). This counter is related toconcentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





520 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.2.1.7 MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone

Long Name NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone

Definition Number of intra-cell handover attempts, with cause 13: "Outer zone uplink anddownlink levels too high" on TCH channel (in HR or FR usage). This counter isrelated to concentric cell environment.


Sub Domain 1 TCH

Sub Domain 2 Cause

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 521 / 1256


22.2.6.2.2 Success

22.2.6.2.2.1 MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION

Long Name NB_TCH_EMERGENCY_HO_PRESERVATION

Definition Number of high priority TCH requests served when1) the number of free TCHtimeslots is less than or equal to NUM_TCH_EGNCY_HO and,2) the queue forthis cell is not empty.

Trigger condition The counter is incremented on the serving cell whenever the 48.058 CHANNELACTIVATION message allocating a TCH channel is sent and the followingtwo conditions are both fulfilled:1) the TCH is allocated to serve i) an internalhandover Cause 2, 3, 4, 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 22, 27, or, ii) anexternal handover Cause "Uplink quality", "Uplink strength", "Downlink quality","Downlink strength", "Distance", or iii) a normal assignment or an externalhandover with the preemption indicator set (i.e. Preemption Capability Indicator= 1 and EN_TCH_PREEMPT = Enable).2) the number of free TCH timeslotsis less than or equal to NUM_TCH_EGNCY_HO and there is at least onerequest queued for this cell.Note 1: This counter counts both inter-PLMNand intra-PLMN handover events.Note 2: The HMI name of the parameterNUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".

Sub Domain 1 TCH

Sub Domain 2 Cause






522 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.2.6.3.1 –

22.2.6.3.1.1 MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to A-traffic-channel status mismatch between the BSC and the MSC.

Trigger condition 1) Whenever a 48.008 HANDOVER FAILURE message with a cause value of"requested terrestrial resource unavailable" is sent on A interface from the targetBSC to the MSC.2) Whenever a 48.008 HANDOVER FAILURE message witha cause value of "terrestrial circuit already allocated" is sent on A interfacefrom the target BSC to the MSC.3) Whenever a 48.008 HANDOVER FAILUREmessage with a cause value of "BSS not equipped" is sent on A interface fromthe target BSC to the MSC.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 523 / 1256


22.2.6.3.1.2 MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ

Long Name NB_INC_INTER_PLMN_TCH_HO_REQ

Definition Number of inter-PLMN TCH incoming handover or directed retry requests

Trigger condition Whenever a 48.008 HANDOVER REQUEST message is received from theMSC on A interface for an external TCH handover or an external directed retrytriggered towards the target cell from a serving cell belonging to a PLMNdifferent from the PLMN of the target cell.

Sub Domain 1 TCH


Sub Domain 3 –





524 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.3.1.3 MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT

Long Name NB_INC_INTER_PLMN_TCH_HO_ATPT

Definition Number of inter-PLMN TCH incoming handover or directed retry attempts

Trigger condition Whenever a 48.008 HANDOVER REQUEST ACK message is sent by the targetBSC containing the 44.018 HANDOVER COMMAND message for an externalTCH handover or an external directed retry triggered towards the target cell froma serving cell belonging to a PLMN different from the PLMN of the target cell.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 525 / 1256


22.2.6.3.1.4 MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC

Long Name NB_INC_INTER_PLMN_TCH_HO_SUCC

Definition Number of inter-PLMN TCH incoming handover or directed retry successes

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received from theMS on Abis interface for an external TCH handover or an external directedretry triggered towards the target cell from a serving cell belonging to a PLMNdifferent from the PLMN of the target cell.

Sub Domain 1 TCH


Sub Domain 3 –





526 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.3.1.5 MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to congestion (C541a), or A-traffic-channel status mismatchbetween the BSC and the MSC (C41b).

Trigger condition Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 527 / 1256


22.2.6.3.1.6 MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to congestion.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of"no radio resource available" is sent on A interface from the target BSC tothe MSC during an external TCH handover.Note 1: This counter counts bothinter-PLMN and intra-PLMN handover events.Note 2: In MX BSC, this counter isincremented whenever a 48.008 HANDOVER FAILURE message with a causevalue of "no radio resource available" is sent due to the TCH processing capacityof CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. Inthis case, MC926 is also incremented by one.Note 3: In IP mode, this counteris increased by 1 if:- the cell mapped on a BTS is in IP congestion status;- orthe TCH processing capacity of AbisBTSGroup reaches the limit defined by theNB_MAX_ACTIVE_TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 3 –





528 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.3.1.7 MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparationfailures due to A interface mismatch between the BSC and the MSC.

Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of"circuit pool mismatch" is sent on A interface from the target BSC to theMSC.Note: This counter counts both inter-PLMN and intra-PLMN handoverevent

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 529 / 1256



22.2.6.4.1 –

22.2.6.4.1.1 MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover-preparation failures due to congestion.

Trigger condition Whenever an internal inter-cell TCH handover cannot be performed, becausethe target cell is congested (no free TCH channel).Note 1: In MX BSC, thiscounter is incremented whenever an internal inter-cell TCH handover cannotbe performed due to the TCH processing capacity of CCP reaches the limitdefined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is alsoincremented by one.Note 2: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

Sub Domain 1 TCH


Sub Domain 3 –





530 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.5 Intra

22.2.6.5.1 –

22.2.6.5.1.1 MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS

Long Name NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of intra-cell TCH (in HR or FR usage) handover -preparation failuresdue to congestion. This counter takes into account handovers from TCH intraffic or in signaling mode. It does not take into account DTM Assignments.

Trigger condition Whenever a internal intra-cell TCH handover cannot be performed, becausethere is no free TCH channel to serve the handover.Note 1: In MX BSC,this counter is incremented whenever an intra-cell TCH handover cannot beperformed due to the TCH processing capacity of CCP reaches the limitdefined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is alsoincremented by one.Note 2: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 531 / 1256


22.2.6.6 Outgoing

22.2.6.6.1 –

22.2.6.6.1.1 MC710 - NB_TCH_OUT_HO_REQ_TRX

Long Name NB_TCH_OUT_HO_REQ_TRX

Definition Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercelland external handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC710 = C710

Trigger condition 1) Intracell HO: Whenever the BSC process responsible for the handoverprocedure starts an intra cell TCH handover procedure.2) Internal intercell HO:Whenever the BSC process responsible for the handover procedure selects atarget cell (among a list of target cells) for internal inter cell TCH handover.3)External HO: Whenever a 48.008 HANDOVER REQUIRED message is sent onA interface to the MSC. If more than one 48.008 HANDOVER REQUIRED issent in the frame of the same Handover procedure, the counter is incrementedonly once.48.008 HANDOVER REQUIRED is sent in following situations:1) Anexternal handover alarm has been raised, with corresponding list of candidatecells.2) The list of candidate cells for the current alarm has been updated.Note:This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –

Measured Object TRX




532 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.2.6.7.1 –

22.2.6.7.1.1 MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ

Long Name NB_OUT_INTER_PLMN_TCH_HO_REQ

Definition Number of inter-PLMN TCH outgoing handover or directed retry requests. Thiscounter takes into account TCH in traffic or in signaling mode.

Trigger condition Whenever a 48.008 HANDOVER REQUIRED message with the cellidentification discriminator set to a value identifying a GSM handover is sent tothe MSC on A interface for an external TCH handover or an external directedretry triggered towards a 2G cell belonging to a PLMN different from the PLMNof the serving cell.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 533 / 1256


22.2.6.7.1.2 MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT

Long Name NB_OUT_INTER_PLMN_TCH_HO_ATPT

Definition Number of inter-PLMN TCH outgoing handover or directed retry attempts. Thiscounter takes into account TCH in traffic or in signaling mode.

Trigger condition Whenever a 44.018 HANDOVER COMMAND message is sent to the MS onAbis interface for an external TCH handover or an external directed retrytriggered towards a 2G cell belonging to a PLMN different from the PLMN ofthe serving cell.

Sub Domain 1 TCH


Sub Domain 3 –





534 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.7.1.3 MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC

Long Name NB_OUT_INTER_PLMN_TCH_HO_SUCC

Definition Number of inter-PLMN TCH outgoing handover or directed retry successes.This counter takes into account TCH in traffic or in signaling mode.

Trigger condition External handover or directed retry towards a 2G cell belonging to a PLMNdifferent from the PLMN of the serving cell in the following cases:1/ 48.008CLEAR COMMAND message with Cause "Handover successful" is receivedfrom the MSC.2/ 48.008 CLEAR COMMAND (cause = "normal event/callcontrol") received while T8 is running.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 535 / 1256


22.2.6.7.1.4 MC924b - NB_OUT_2G_3G_HO_REQ

Long Name NB_OUT_2G_3G_HO_REQ

Definition Number of outgoing external TCH (in HR or FR usage) handover requests to a3G cell.

Trigger condition Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface tothe MSC for a TCH handover to a 3G FDD cell.48.008 HANDOVER REQUIREDis sent in following situations :1) An external handover alarm has been raised,with corresponding list of candidate cells including a 3G cell.2) The list ofcandidate cells for the current alarm has been updated.Note: This countercounts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





536 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.7.1.5 MC924c - NB_OUT_2G_3G_HO_SUCC

Long Name NB_OUT_2G_3G_HO_SUCC

Definition Number of outgoing external TCH (in HR or FR usage) handover successesto a 3G cell.

Trigger condition External TCH handover to a 3G cell, in the following cases:1/ 48.008 CLEARCOMMAND message with a cause value of "handover successful" is receivedon A interface on the serving BSC from the MSC.2/ 48.008 CLEAR COMMAND(cause = "normal event/call control") received while T3121 is running.Note: Thiscounter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 537 / 1256


22.2.6.7.1.6 MC924d - NB_OUT_2G_3G_HO_ATPT

Long Name NB_OUT_2G_3G_HO_ATPT

Definition Number of outgoing external TCH (in HR or FR usage) handover attempts to a3G cell.

Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abisinterface on the serving channel, during an external TCH handover procedure toa 3G cell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 TCH


Sub Domain 3 –





538 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.7.1.7 MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV

Long Name NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV

Definition Number of outgoing external TCH (in HR or FR usage) handover executionfailures to a 3G cell due to MS access problem without reversion of the mobileto the old channel (call drop).

Trigger condition Whenever the timer supervising the handover procedure on the serving cell(T3121), expires during an external TCH handover to a 3G cell, except if a48.008 CLEAR COMMAND with "normal event/call control" cause was receivedfrom the MSC, leading to a normal call release. In such a case, the handoveris considered as successful.Note: This counter counts both inter-PLMN andintra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 539 / 1256


22.2.6.7.1.8 MC924f - NB_OUT_2G_3G_HO_EXEC_FAIL_REV

Long Name NB_OUT_2G_3G_HO_EXEC_FAIL_REV

Definition Number of outgoing external TCH (in HR or FR usage) handover -executionfailures to a 3G cell due to MS access problem with reversion of the mobile tothe old channel.

Trigger condition Whenever a 44.018 HANDOVER FAILURE message is received on Abisinterface from the serving cell , during an external TCH handover to a 3Gcell.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.

Sub Domain 1 TCH


Sub Domain 3 –





540 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.2.6.7.1.9 MC924g - NB_OUT_2G_3G_HO_PREP_FAIL

Long Name NB_OUT_2G_3G_HO_PREP_FAIL

Definition Nb of outgoing TCH handover -preparation failures to a 3G cell.

Trigger condition Whenever a 48.008 HANDOVER REQUIRED REJECT is received from theMSC by the serving BSC for an outgoing external TCH HO to a 3G cell.Note :the counter will be incremented for external TCH HO if and only if the parameterRESP_REQ is set to 1.

Sub Domain 1 TCH


Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 541 / 1256




22.3.1.1 Internal

22.3.1.1.1 Failure

22.3.1.1.1.1 MC142f - NB_OUT_EDR_SUCC

Long Name NB_OUT_EDR_SUCC

Definition MC142f=C142b+C142d









542 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.1.1.2 Success

22.3.1.1.2.1 MC142e - NB_OUT_IDR_SUCC

Long Name NB_OUT_IDR_SUCC

Definition MC142e=C142a+C142c









3BK 21255 AAAA PCZZA Ed.07 543 / 1256


22.3.1.1.2.2 MC717a - NB_INC_IDR_SUCC_TRX

Long Name NB_INC_IDR_SUCC_TRX

Definition Number of incoming directed retry (towards a TCH channel in HR or FR usage)successes, per TRX.MC717a = C717a

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abisinterface from the target cell for a TCH channel involved in an internal directedretry procedure.




Measured Object TRX




544 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.3.2.1 SDCCH

22.3.2.1.1 Failure

22.3.2.1.1.1 MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB

Long Name NB_SDCCH_DROP_EST_PHAS_BSS_PB

Definition MC137=C137, Number of SDCCH drops in SDCCH established phase due toBSS problem.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the call is released.

Trigger condition 1) LapD failure detected during the stable phase of an SDCCH transaction.2)SDCCH was released due to 48.058 ERROR REPORT with any cause valuebeing received during the stable phase of an SDCCH transaction.3) TelecomSupervisory module caused the call to be cleared.4) SDCCH was released dueto 0180 CLEAR_CMD message being received from BSSAPduring the stablephase of an SDCCH transaction : O&M has disabled the DTC


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 545 / 1256


22.3.2.1.1.2 MC138 - NB_SDCCH_DROP_EST_PHAS_RLF

Long Name NB_SDCCH_DROP_EST_PHAS_RLF

Definition Number of SDCCH drops on SDCCH established phase due to radio link failure(radio link timeout or Lapdm timer expiry).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with acause value of "radio link failure" is received on Abis interface for an SDCCHchannel.2) Whenever an 48.058 ERROR INDICATION message is received onAbis interface and leads to a loss of channel.


Sub Domain 2 SDCCH






546 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.2.2 TCH

22.3.2.2.1 Failure

22.3.2.2.1.1 MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB

Long Name NB_TCH_DROP_EST_PHAS_BSS_PB

Definition Number of TCH (in HR or FR usage) drops in TCH established phase due toBSS problem.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the call is released.This counter takes into account TCH intraffic or in signaling mode. It is not incremented in case of TCH drop during anormal assignment, a handover or a DTM assignment.

Trigger condition 1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&Mintervention" is received on Abis interface after TCH seizure and leads to a lossof call.2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with acause value of "message sequence error" is received on Abis interface after TCHseizure and leads to a loss of call.3) Whenever a LAPD failure is reported to theLayer 3 of the BSC (for an RSL supporting a TCH transaction after successfulTCH seizure) and leads to a loss of call.4) Whenever a TCH call release isinitiated by the BSS O&M FAULT MANAGEMENT application part or by the BSSTELECOM application part as the result of a system defense action which maybe due to BSS equipment failures external to the BSC (e.g. RSL failure or CUrecovery failure), or due to BSC internal hardware problems (e.g. TCU failureor DTC failure) or due to BSC internal software problems (e.g. inconsistenciesdetected between software modules or lack of software resources (memory,timer reference, file reference...) or communication problems between differentprocessor boards).Notes : 1. TCH call releases which are due to O&M operatoractions on BTS or BSC should not be counted. Indeed, in case of numerousfailures due to O&M commands, this counter will overestimate failures whichare due to problems which are internal to the BSS.However, due to the currentimplementation which does not allow to be aware of the origin of the failure,O&M operator actions will also be counted. 2. It may happen that the countercan not be incremented since it is implemented within the faulty entity.


Sub Domain 2 TCH






3BK 21255 AAAA PCZZA Ed.07 547 / 1256


22.3.2.2.1.2 MC162 - NB_TCH_DROP_DTAP_EST_PHAS

Long Name NB_TCH_DROP_DTAP_EST_PHAS

Definition MC162 = C162a + C162b + C162c



Sub Domain 2 TCH






548 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.2.2.1.3 MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX

Long Name NB_TCH_DROP_EST_PHAS_RLF_TRX

Definition Number of TCH (in HR or FR usage) drops in TCH established phase dueto radio link failure (radio link timeout or Lapdm timer expiry), per TRX. Thiscounter takes into account TCH in traffic or in signaling mode.MC736 = C736

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message witha cause value of "radio link failure" is received on Abis interface for a TCHchannel (after successful seizure).2) Whenever an 48.058 ERROR INDICATIONmessage is received on Abis interface and leads to a loss of call.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 549 / 1256


22.3.2.2.1.4 MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Long Name NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Definition Number of TCH (in HR or FR usage) drops in TCH established phase due toremote transcoder failures (per TRX).

Trigger condition The counter is incremented whenever a 48.058 CONNECTION FAILUREINDICATION message with cause "Remote Transcoder Failure" is receivedon Abis interface for an established TCH connection. The BSC considers aTCH connection as "established" once a 44.018 ASSIGNMENT COMPLETEmessage (in case of normal assignments or an internal intra-cell handovers) ora 44.018 HANDOVER COMPLETE message (in case of an internal inter-cellincoming HO or an external inter-cell incomingHO) has been received for theTCH connection.Note 1: MC739 = C739.Note 2: The counter is incrementedonly once per established TCH connection. Thus, even if the BTS sends several48.058 CONNECTION FAILURE INDICATION messages with cause "RemoteTranscoder Failure" for a particular established TCH connection, BSC willincrement the counter only once for that connection."


Sub Domain 2 TCH


Measured Object TRX




550 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.3 Handover

22.3.3.1 SDCCH

22.3.3.1.1 Failure

22.3.3.1.1.1 MC07 - NB_SDCCH_DROP_OUT_HO

Long Name NB_SDCCH_DROP_OUT_HO

Definition MC07=C07, Number of SDCCH drops during any outgoing SDCCH handover.

Trigger condition Internal inter-cell SDCCH handover: whenever the timer supervising thehandover procedure (T3103) expires.


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 551 / 1256


22.3.3.1.2 Success

22.3.3.1.2.1 MC03 - NB_OUT_SDCCH_HO_SUCC

Long Name NB_OUT_SDCCH_HO_SUCC

Definition MC03=C03, Number of outgoing SDCCH handover (any kind) successes.

Trigger condition External SDCCH handover in the following cases:1/ 48.008 CLEAR COMMAND(cause= "handover successful") is received on the serving BSC.2/ 48.008CLEAR COMMAND (cause= "normal event/call control") received while T8 isrunning.Note: This counter counts both inter-PLMN and intra-PLMN handoverevents.


Sub Domain 2 SDCCH






552 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.3.1.2.2 MC10 - NB_INC_SDCCH_HO_SUCC

Long Name NB_INC_SDCCH_HO_SUCC

Definition MC10=C10, Number of incoming SDCCH handover (any kind) successes.

Trigger condition Internal inter-cell or external SDCCH handover: whenever a 44.018 HANDOVERCOMPLETE message is received on Abis interface from the target cell foran SDCCH Sub-channel.Note: This counter counts both inter-PLMN andintra-PLMN handover events.


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 553 / 1256


22.3.3.2 TCH

22.3.3.2.1 Failure

22.3.3.2.1.1 MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB

Long Name NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB

Definition Number of TCH (in HR or FR usage) drops due to BSS problem during any TCHhandover preparation and execution phases.This counter is incremented on thecell on which the problem occurs(In the case of internal inter-cell handovers,it is not incremented on both serving and target cell). For problems that arenot related to a specific cell, the counter related to the serving cell will beincremented.It may happen that several causes of failures mentioned beloware detected consecutively. In that case, the counter will only be incrementedonce, as soon as the handover procedure fails. This counter takes into accounthandovers from TCH in traffic or in signaling mode.

554 / 1256 3BK 21255 AAAA PCZZA Ed.07


Trigger condition 1) Whenever the BSC receives on Abis interface from the target cell negativeacknowledgment to the TCH channel activation involved in the handoverprocedure.2) Whenever the timer supervising the Channel Activation procedure(T9103) expires on the target cell during activation of a TCH channel involved inthe handover procedure.3) Whenever an 48.058 ERROR REPORT messagewith a cause value of "O&M intervention" is received on Abis interface fromeither the serving or the target cell during the external or internal inter-cellhandover procedure and leads to a transaction failure.4) Whenever an 48.058ERROR REPORT message with a cause value of "O&M intervention" isreceived on Abis interface on either the old or the new channel during theinternal intra-cell handover procedure and leads to a transaction failure.5)Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause valueof "message sequence error" is received on Abis interface from the servingcell between the sending of the 48.058 CHANNEL ACTIVATION message andthe reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENTduring the internal inter-cell TCH handover and leads to a transaction failure.6)Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause valueof "message sequence error" is received on Abis interface on the old channelbetween the sending of the 48.058 CHANNEL ACTIVATION message and thereception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during theinternal intra-cell TCH handover and leads to a transaction failure.7) Whenevera LAPD failure related to either serving or target cell is reported to the Layer 3of the BSC (for an RSL supporting a TCH transaction for handover purpose)and leads to a transaction failure.8) Whenever an TCH handover abortion isinitiated by the BSS O&M FAULT MANAGEMENT application part or by the BSSTELECOM application part as the result of a system defense action which maybe due to BSS equipment failures external to the BSC (e.g. RSL failure or CUrecovery failure), or due to BSC internal hardware problems (e.g. TCU failureor DTC failure) or due to BSC internal software problems (e.g. inconsistenciesdetected between software modules or lack of software resources (memory,timer reference, file reference...) or communication problems between differentprocessor boards).9) Whenever a 48.058 CONNECTION FAILURE INDICATIONmessage with a cause value of "remote transcoder failure" is received on Abisinterface from the old channel between the sending of the 48.058 CHANNELACTIVATION message and the reception of the 48.058 CHANNEL ACTIVATIONACKNOWLEDGE during an internal intra-cell or inter-cellTCH handoverprocedure and leads to a transaction failure.Notes : 1. TCH handover failureswhich are due to O&M operator actions on BTS or BSC should not be counted.Indeed, in case of numerous failures due to O&M commands, this counterwill overestimate failures which are due to problems which are internal to theBSS.However, due to the current implementation which does not allow to beaware of the origin of the failure, O&M operator actions will also be counted. 2.It may happen that the counter can not be incremented since it is implementedwithin the faulty entity.


Sub Domain 2 TCH




3BK 21255 AAAA PCZZA Ed.07 555 / 1256




556 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.3.2.1.2 MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX

Long Name NB_TCH_DROP_OUT_HO_EXEC_TRX

Definition Number of TCH drops during the execution of any TCH outgoing handover,per TRX. This counter takes into account handovers from TCH in traffic or insignaling mode.MC621 = C621

Trigger condition 1) Inter-cell TCH handover: whenever the timer supervising the handoverprocedure (T3103) expires.2) External TCH handover (2G -> 2G): wheneverthe timer supervising the handover procedure on the serving cell (T8) expires,except if a 48.008 CLEAR COMMAND with "normal event/call control" causewas received from the MSC, leading to a normal call release. In such a case,the handover is considered as successful.3) Intra-cell TCH handover: wheneverthe timer supervising the handover procedure (T3107) expires.4) 2G -> 3G HO:whenever the timer supervising the 2G-3G handover procedure on the servingcell (T3121) expires, except if a 48.008 CLEAR COMMAND with "normalevent/call control" cause was received from the MSC, leading to a normal callrelease. In such a case, the 2G->3G handover is considered as successful.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 557 / 1256


22.3.3.2.1.3 MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX

Long Name NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX

Definition Nb of outgoing TCH handover -preparation failures due to congestion, per TRX.Intracell, internal intercell and external handovers are counted together. Thiscounter takes into account handovers from TCH in traffic or in signaling mode. Itdoes not take into account DTM Assignments.MC711 = C711

Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover cannot be performed,because there is no free TCH channel to allocate the handover to.2) Internalinter-cell HO: Whenever a internal inter-cell TCH handover cannot be performed,because there is no free TCH channel to allocate the handover to.3) ExternalHO: Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "noradio resource available" is received from the MSC by the serving BSC for anoutgoing external TCH HO.Note : the counter will be incremented for externalTCH HO if and only if the parameter RESP_REQ is set to 1.Note: This countercounts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 TCH


Measured Object TRX




558 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.3.2.1.4 MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX

Long Name NB_TCH_OUT_HO_FAIL_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problemwith reversion of the mobile to the old channel. Intracell, internal intercell andexternal handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC713 = C713

Trigger condition 1) External HO: Whenever a 44.018 HANDOVER FAILURE message is receivedon Abis interface from the serving cell, during an external TCH handover.2)Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message isreceived on Abis interface from the serving cell, during an internal inter-cellTCH handover.3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILUREmessage is received on Abis interface on the serving channel, during aninternal intra-cell TCH handover.Note: This counter counts both inter-PLMN andintra-PLMN handover events.Note: This counter counts handover to UMTS.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 559 / 1256


22.3.3.2.1.5 MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Long Name NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problemwithout reversion of the mobile to the old channel (call drop). Intracell, internalintercell and external handovers are counted together. This counter takes intoaccount handovers from TCH in traffic or in signaling mode. It does not take intoaccount DTM Assignments.MC714 = C714

Trigger condition 1) External TCH HO: Whenever the timer supervising the handover procedureon the serving cell (T8) expires, except if a 48.008 CLEAR COMMAND with"normal event/call control" cause was received from the MSC, leading to anormal call release. In such a case, the handover is considered as successful.2)Internal intercell TCH HO: Whenever the timer supervising the handoverprocedure (T3103) expires during an internal inter-cell TCH handover.3) IntracellTCH HO: Whenever the timer supervising the handover procedure (T3107)expires during an internal intra-cellNote: This counter counts both inter-PLMNand intra-PLMN handover events.Note: This counter counts hantover to UMTS


Sub Domain 2 TCH


Measured Object TRX




560 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.3.2.2 Success

22.3.3.2.2.1 MC712 - NB_TCH_OUT_HO_SUCC_TRX

Long Name NB_TCH_OUT_HO_SUCC_TRX

Definition Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercelland external handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into accountDTM Assignments.MC712 = C712

Trigger condition 1) External HO in the following cases:1a) 48.008CLEAR COMMAND (cause ="handover successful") is received on the serving BSC on the TCH channel.1b)48.008 CLEAR COMMAND (cause = "normal event/call control") is receivedwhile T8 is running.2) Internal inter-cell HO: whenever 44.018HANDOVERCOMPLETE is received from the MS via the target cell on the TCH channel.3)Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is receivedfrom the MS via the cell on the TCH channel.Note 1: This counter counts bothinter-PLMN and intra-PLMN handover events.Note 2: This counter countshandover to UMTS.


Sub Domain 2 TCH


Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 561 / 1256


22.3.3.2.2.2 MC717b - NB_INC_TCH_HO_SUCC_TRX

Long Name NB_INC_TCH_HO_SUCC_TRX

Definition Number of incoming internal and external TCH (in HR or FR usage) handoversuccesses per TRX; since there are no reliable means at the target BSC todistinguish external directed retry from external handover, the external directedretries are counted by this counter.MC717b = C717b

Trigger condition 1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVERCOMPLETE message is received on Abis interface from the target cell fora TCH channel.2) Intra-cell handover: whenever an 44.018 ASSIGNMENTCOMPLETE message is received on Abis interface on the target channel.Note:This counter counts both inter-PLMN and intra-PLMN handover events.


Sub Domain 2 TCH


Measured Object TRX




562 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.4 LCS

22.3.4.1 –

22.3.4.1.1 –

22.3.4.1.1.1 MC923c - NB_LCS_FAIL_LB

Long Name NB_LCS_FAIL_LB

Definition Number of LCS requests rejected by the SMLC. The failed LCS requestsindicated by the SMLC to the BSC encompass the failure to determinegeographic location estimate and the failure of LCS assistance data delivery.

Trigger condition Whenever a 09.31 PERFORM LOCATION RESPONSE message is receivedfrom the SMLC with the OIE LCS Cause.

Sub Domain 1 LCS

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 563 / 1256


22.3.4.1.1.2 MC923d - NB_LCS_ABORT

Long Name NB_LCS_ABORT

Definition Number of LCS procedures aborted on request from the MSC in CS domain.

Trigger condition Whenever a 48.008 PERFORM LOCATION ABORT message is received by theBSC from the MSC while an LCS procedure is ongoing.

Sub Domain 1 LCS

Sub Domain 2 –

Sub Domain 3 –





564 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.4.1.2 SCCP

22.3.4.1.2.1 MC923a - NB_LCS_REQ

Long Name NB_LCS_REQ

Definition Number of LCS requests received from the MSC in CS domain. The LCSrequests encompass the geographic location requests and the LCS assistancedata requests.

Trigger condition Whenever a 48.008 PERFORM LOCATION REQUEST message is received bythe BSC from the MSC.

Sub Domain 1 LCS

Sub Domain 2 –

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 565 / 1256


22.3.4.1.2.2 MC923b - NB_LCS_SUCC

Long Name NB_LCS_SUCC

Definition Number of successful LCS requests.The successful LCS requests encompassthe successful geographic location estimate and the successful LCS assistancedata delivery.

Trigger condition Whenever a 48.008 PERFORM LOCATION RESPONSE message is sent to theMSC without including the OIE LCS Cause.

Sub Domain 1 LCS

Sub Domain 2 –

Sub Domain 3 SCCP





566 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.3.5.1 Point to Point

22.3.5.1.1 Failure

22.3.5.1.1.1 MC197 - NB_SMS_PP_CON_FAIL

Long Name NB_SMS_PP_CON_FAIL

Definition MC197=C194a+C194b+C194c+C195









3BK 21255 AAAA PCZZA Ed.07 567 / 1256


22.3.5.1.2 Success

22.3.5.1.2.1 MC191 - NB_SMS_PP_CON_MT_SDCCH

Long Name NB_SMS_PP_CON_MT_SDCCH

Definition Number of Mobile Terminating SMS connections on SDCCH.

Trigger condition Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SDCCHsub-channel is received by the BSC.








568 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.5.1.2.2 MC196 - NB_SMS_PP_CON_SUCC

Long Name NB_SMS_PP_CON_SUCC

Definition MC196=C190+C191+C192+C193









3BK 21255 AAAA PCZZA Ed.07 569 / 1256


22.3.6 Speech

22.3.6.1 TFO

22.3.6.1.1 –

22.3.6.1.1.1 MC170 - NB_CALL_TFO

Long Name NB_CALL_TFO

Definition Number of TCHs assigned in the serving cell for which TFO has beensuccessfully established.

Trigger condition For each assigned TCH, the counter is incremented the first time a 48.058 TFOREPORT message is received by the BSC, indicating that TFO is established(i.e. TFO = 1 in the TFO Status IE).Note 1: This counter shall be incrementedonly once per assigned TCH (i.e. the first time it is received for the assignedTCH).Note 2: A TCH is seen as assigned in the serving cell between thesending of 48.058 CHANNEL ACTIVATION message and the receipt of the48.058 RF CHANNEL RELEASE message. This means that the counter canbe incremented either if the TCH is assigned to serve a normal assignment orif the TCH is assigned to serve an incoming internal (inter-cell or intra-cell) orexternal handover.Note 3: MC170 = C170

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





570 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.6.1.1.2 MC935 - NB_CALL_TFO_AMR_WB

Long Name NB_CALL_TFO_AMR_WB

Definition Number of TCH assigned using AMR-WB for which TFO has been successfullyestablished.

Trigger condition For each assigned TCH, the counter is incremented the first time a 48.058 TFOREPORT message is received by the BSC, indicating that TFO is established(i.e. TFO = 1 in the TFO Status IE) and the used codec is an AMR WB one (i.e.FR sv5).Note 1: This counter shall be incremented only once per assignedTCH (i.e. the first time it is received for the assigned TCH).Note 2: A TCH isseen as assigned in the serving cell between the sending of 48.058 CHANNELACTIVATION message and the receipt of the 48.058 RF CHANNEL RELEASEmessage. This means that the counter can be incremented either if the TCH isassigned to serve a normal assignment or if the TCH is assigned to serve anincoming internal (inter-cell or intra-cell) or external handover.

Sub Domain 1 Speech

Sub Domain 2 TFO

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 571 / 1256


22.3.7 TCH

22.3.7.1 –

22.3.7.1.1 –

22.3.7.1.1.1 MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL

Definition Number of TCH drops due to Cause 2 (Too low quality in UL).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expires duringthe inter-cell TCH handover.4) Whenever the timer supervising the handoverprocedure on the serving cell (T8) expires during the external TCH handover.TheBSC uses the last valid measurements (Note) received for this MS. The counteris incremented if the following condition is fulfilled: AV_RXQUAL_UL_HO> L_RXQUAL_UL_H + OFFSET_RXQUAL_FHAndAV_RXLEV_UL_HO <=RXLEV_UL_IHNote: "Last valid measurements" means the last received 48.058MEASUREMENT RESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





572 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.7.1.1.2 MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL

Definition Number of TCH drops due to Cause 3 (Too low level in UL).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expiresduring the inter-cell TCH handover.4) Whenever the timer supervising thehandover procedure on the serving cell (T8) expires during the external TCHhandover.The BSC uses the last valid measurements received for this MS(Note). The counter is incremented if the following condition is fulfilled: a)the Cause 2 (MC928a) and Cause 4 (MC928c) are not eligible;b) and thefollowing condition is fulfilled:AV_RXQUAL_UL_HO <= L_RXQUAL_UL_H+ OFFSET_RXQUAL_FHAndAV_RXLEV_UL_HO < L_RXLEV_UL_HNote:"Last valid measurements" means the last received 48.058 MEASUREMENTRESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 573 / 1256


22.3.7.1.1.3 MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL

Definition Number of TCH drops due to Cause 4 (Too low quality on the downlink).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expires duringthe inter-cell TCH handover.4) Whenever the timer supervising the handoverprocedure on the serving cell (T8) expires during the external TCH handover.TheBSC uses the last valid measurements received for this MS (Note). The counteris incremented if the following condition is fulfilled: a) the Cause 2 (MC928a)is not eligible.b) and the following condition is fulfilled:AV_RXQUAL_DL_HO> L_RXQUAL_DL_H + OFFSET_RXQUAL_FHAndAV_RXLEV_DL_HO <=RXLEV_DL_IHNote: "Last valid measurements" means the last received 48.058MEASUREMENT RESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





574 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.7.1.1.4 MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL

Definition Number of TCH drops due to Cause 5 (Too low level in DL).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expires duringthe inter-cell TCH handover.4) Whenever the timer supervising the handoverprocedure on the serving cell (T8) expires during the external TCH handover.TheBSC uses the last valid measurements received for this MS (Note). Thecounter is incremented if the following condition is fulfilled: a) the Cause 2(MC928a), Cause 4 (MC928c) and Cause 3 (MC928b) are not eligible;b) andthe following condition is fulfilled:AV_RXQUAL_DL_HO <= L_RXQUAL_DL_H+ OFFSET_RXQUAL_FHAndAV_RXLEV_DL_HO < L_RXLEV_DL_HNote:"Last valid measurements" means the last received 48.058 MEASUREMENTRESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 575 / 1256


22.3.7.1.1.5 MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE

Long Name NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE

Definition Number of TCH drops due to Cause 6 (Too long MS-BS distance).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expires duringthe inter-cell TCH handover.4) Whenever the timer supervising the handoverprocedure on the serving cell (T8) expires during the external TCH handover.TheBSC uses the last valid measurements received for this MS (Note). Thecounter is incremented if the following condition is fulfilled: a) the Cause 2(MC928a), Cause 4 (MC928c), Cause 3 (MC928b) and Cause 5 (MC928d)are not eligible;b) and the following condition is fulfilled:AV_RANGE_HO >U_TIME_ADVANCENote: "Last valid measurements" means the last received48.058 MEASUREMENT RESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





576 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.7.1.1.6 MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE

Long Name NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE

Definition Number of TCH drops due to Cause 22 (Too short MS-BS distance).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel(after successful seizure).2) Whenever an 48.058 ERROR INDICATIONmessage is received on Abis interface after TCH seizure and leads to a lossof call.3) Whenever the timer supervising the handover procedure (T3103)expires during the inter-cell TCH handover.4) Whenever the timer supervisingthe handover procedure on the serving cell (T8) expires during the externalTCH handover.The BSC uses the last valid measurements received for thisMS (Note). The counter is incremented if the following condition is fulfilled:a) the Cause 2 (MC928a), Cause 4 (MC928c), Cause 3 (MC928b), Cause5 (MC928d) and Cause 6 (MC928e) are not eligible;b) and the followingcondition is fulfilled:AV_RANGE_HO <= L_TIME_ADVANCENote: "Last validmeasurements" means the last received 48.058 MEASUREMENT RESULTmessages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 577 / 1256


22.3.7.1.1.7 MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UPLINK

Long Name NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UPLINK

Definition Number of TCH drops due to Cause 15 (Too high interference level on theuplink).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3107) expiresduring the intra-cell TCH handover.The BSC uses the last valid measurementsreceived for this MS (Note). The counter is incremented if the followingcondition is fulfilled: a) the Cause 2 (MC928a), Cause 4 (MC928c), Cause 3(MC928b), Cause 5 (MC928d), Cause 6 (MC928e) and Cause 22 (MC928f) arenot eligible;b) and the following condition is fulfilled:AV_RXQUAL_UL_HO >THR_RXQUAL_CAUSE_15 + OFFSET_RXQUAL_FHAndAV_RXLEV_UL_HO> RXLEV_UL_IHNote: "Last valid measurements" means the last received48.058 MEASUREMENT RESULT messages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





578 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.7.1.1.8 MC928h -NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK

Long Name NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK

Definition Number of TCH drops due to Cause 16 (Too high interference level on thedownlink).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel(after successful seizure).2) Whenever an 48.058 ERROR INDICATIONmessage is received on Abis interface after TCH seizure and leads to a lossof call.3) Whenever the timer supervising the handover procedure (T3107)expires during the intra-cell TCH handover.The BSC uses the last validmeasurements received for this MS (Note). The counter is incrementedif the following condition is fulfilled: a) the Cause 2 (MC928a), Cause 3(MC928b), Cause 4 (MC928c), Cause 5 (MC928d), Cause 6 (MC928e), Cause22 (MC928f) and Cause 15 (MC928g) are not eligible;b) and the followingcondition is fulfilled:AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 +OFFSET_RXQUAL_FHAndAV_RXLEV_DL_HO > RXLEV_DL_IHNote: "Lastvalid measurements" means the last received 48.058 MEASUREMENT RESULTmessages with S-BFI flag set to "0".

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 579 / 1256


22.3.7.1.1.9 MC928i - NB_TCH_DROP_OTHER_CAUSES

Long Name NB_TCH_DROP_OTHER_CAUSES

Definition Number of TCH drops due to other causes than Cause 2 (Too low quality in UL),Cause 3 (Too low level in UL), Cause 4 (Too low quality on the downlink), Cause5 (Too low level in DL), Cause 6 (Too long MS-BS distance), Cause 15 (Too highinterference level on the uplink), Cause 16 (Too high interference level on thedownlink), Cause 22 (Too short MS-BS distance).

Trigger condition 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message withcause "radio link failure" is received on Abis interface for a TCH channel (aftersuccessful seizure).2) Whenever an 48.058 ERROR INDICATION messageis received on Abis interface after TCH seizure and leads to a loss of call.3)Whenever the timer supervising the handover procedure (T3103) expires duringthe inter-cell TCH handover.4) Whenever the timer supervising the handoverprocedure (T3107) expires during the intra-cell TCH handover.5) Whenever thetimer supervising the handover procedure on the serving cell (T8) expires duringthe external TCH handover.The BSC uses the last measurements receivedfor this MS. The counter is incremented if the following condition is fulfilled:a) the Cause 2 (MC928a), Cause 3 (MC928b), Cause 4 (MC928c), Cause 5(MC928e), Cause 6 (MC928e), Cause 22 (MC928f), Cause 15 (MC928g) andCause 16 (MC928h) are not eligible.

Sub Domain 1 TCH

Sub Domain 2 –

Sub Domain 3 –





580 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.3.8.1 –

22.3.8.1.1 –

22.3.8.1.1.1 MC901 - NB_Suspend_Resume_req

Long Name NB_Suspend_Resume_req

Definition Number of suspend / Resume requests.A request could lead to a success, afailure or a stop.

Trigger condition Emission of MS Suspend message by the BSC to the MFSEmission of MSResume message by the BSC to the MFSA suspend message received fromMS with a "suspend cause" filtered by BSC will not be counted. Stop causescould be:1) External handover2) MS channel failure.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 581 / 1256


22.3.8.1.1.2 MC902 - Nb_Suspend_fail

Long Name Nb_Suspend_fail

Definition Number of suspend/resume procedure failures.

Trigger condition Reception of -Suspend nack or resume nack, or expiration of T_GPRS_Resume.


Sub Domain 2 –

Sub Domain 3 –





582 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.1.1.3 MC903 - Nb_Suspend_succ

Long Name Nb_Suspend_succ

Definition Number of suspensions successes.

Trigger condition Reception of Resume ack message from MFS.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 583 / 1256


22.3.8.1.2 Failure

22.3.8.1.2.1 MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP

Long Name NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP

Definition Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (inHR or FR usage) is available in the cell, timer T11 (case MSC requests forqueuing whatever QUEUE_ANYWAY value may be) or timer T11_forced(case QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) isstarted, and no free TCH can be found before timer expiry, consequently therequest is rejected (by 48.008 CLEAR REQUEST cause: "no radio resourceavailable").Remark: If an internal directed retry is attempted and failed whileT11/T11_forced is running, the request is un-holded and the BSC waits for theexpiry of the relevant timer. Consequently, this counter must not be incrementedupon the failure of an internal directed retry.

Trigger condition The counter is incremented upon the sending of 48.008 CLEAR REQUEST(cause : "no radio resource available") -following the expiry of T11 or T11forced for a queued TCH normal assignment.Note 1: The HMI name of theparameter QUEUE_ANYWAY is "FORCED_QUEUING".Note 2: In case of MxBSC, "no TCH available" could happen when the TCH processing capacity ofCCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In thiscase, this counter and MC926 are incremented by one.Note 3: In IP mode, thiscounter is increased by 1 if:- the cell mapped on a BTS is in IP congestionstatus;- or the TCH processing capacity of AbisBTSGroup reaches the limitdefined by the NB_MAX_ACTIVE_TCH_TS parameter


Sub Domain 2 –






584 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.2 DTAP Assignment

22.3.8.2.1 Success

22.3.8.2.1.1 MC161 - NB_DTAP_NOR_ASS_SUCC

Long Name NB_DTAP_NOR_ASS_SUCC

Definition MC161 = C161a + C161b

Trigger condition Whenever a 44.018 CONNECT ACK is received on Abis interface.








3BK 21255 AAAA PCZZA Ed.07 585 / 1256



22.3.8.3.1 Failure

22.3.8.3.1.1 MC04 - NB_IMM_ASS_PREP_FAIL_CONG

Long Name NB_IMM_ASS_PREP_FAIL_CONG

Definition MC04=C04, number of immediate assignment preparation failures due tocongestion.

Trigger condition All SDCCH sub-channels in the required cell were either Busy or Out of Service,when the 48.058 CHANNEL REQUIRED message was received.








586 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.1.2 MC149 - NB_IMM_ASS_EXEC_FAIL_RADIO

Long Name NB_IMM_ASS_EXEC_FAIL_RADIO

Definition Number of immediate assignment -execution failures due to MS access problem.

Trigger condition Whenever the timer supervising the Immediate Assignment Procedure (T3101)expires during the establishment of an SDCCH sub-channel.








3BK 21255 AAAA PCZZA Ed.07 587 / 1256


22.3.8.3.2 Success

22.3.8.3.2.1 MC01 - NB_IMM_ASS_SUCC_MT

Long Name NB_IMM_ASS_SUCC_MT

Definition Number of immediate assignment plus SDCCH normal assignment successesfor Mobile Terminating procedure.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received froma CELL, with the L3_INFORMATION field including a 44.018 PAGINGRESPONSE message.








588 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.2.2 MC02 - NB_IMM_ASS_SUCC_MO

Long Name NB_IMM_ASS_SUCC_MO

Definition Number of immediate assignment successesfor Mobile Originating procedure.MC02 = C02 =C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i.Thefollowing counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecomprocedures on SDCCH.









3BK 21255 AAAA PCZZA Ed.07 589 / 1256


22.3.8.3.2.3 MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD

Long Name NB_IMM_ASS_SUCC_MO_LOC_UPD

Definition case: Location Update request (except the "follow on" procedure)

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from acell, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to LOCATION UPDATING REQUEST and with an MIELocation updating type not set to a RESERVED value and a bit FOR set to0.This counter is incremented only if the L3 info message received has to beforwarded to the MSC.








590 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.2.4 MC02b - NB_IMM_ASS_SUCC_MO_SMS

Long Name NB_IMM_ASS_SUCC_MO_SMS

Definition case: SMS procedure on SDCCH

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and with an MIE CM servicetype set to "SMS".This counter is incremented only if the L3 info messagereceived has to be forwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 591 / 1256


22.3.8.3.2.5 MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV

Long Name NB_IMM_ASS_SUCC_MO_SUP_SERV

Definition case: Supplementary Service

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and with an MIE CM servicetype set to "Supplementary Service".This counter is incremented only if the L3info message received has to be forwarded to the MSC.








592 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.2.6 MC02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON

Long Name NB_IMM_ASS_SUCC_MO_FOLLOW_ON

Definition case: Location Update request ("follow on" procedure)

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to LOCATION UPDATING REQUEST and with an MIELocation updating type not set to a RESERVED value and a bit FOR set to1.This counter is incremented only if the L3 info message received has to beforwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 593 / 1256


22.3.8.3.2.7 MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST

Long Name NB_IMM_ASS_SUCC_MO_CM_REEST

Definition case: CM Re-establishment procedure

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containing a 44.018 L3 message with anMIE message type set to CM RE-ESTABLISHMENT REQUEST message.Thiscounter is incremented only if the L3 info message received has to be forwardedto the MSC.








594 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.2.8 MC02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW

Long Name NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW

Definition MC02f=C02f, number of immediate assignment successes for MobileOriginationg procedure, in case of L3 Info (within 48.058 ESTABLISHINDICATION) unknown by the BSC but transferred to the MSC.









3BK 21255 AAAA PCZZA Ed.07 595 / 1256


22.3.8.3.2.9 MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH

Long Name NB_IMM_ASS_SUCC_MO_IMSI_DETACH

Definition MC02g=C02g, number of immediate assignment successes for MobileOriginationg procedure, in case of IMSI Detach Indication.

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with L3_INFORMATION field containing a 44.018 L3 message withan MIE message type set to IMSI DETACH INDICATION. This counter isincremented only if the L3 info message received has to be forwarded to theMSC.








596 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.3.2.10 MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST

Long Name NB_IMM_ASS_SUCC_MO_CALL_EST

Definition case: normal or emergency call establishment

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from aCELL, with the L3 INFORMATION field containg a 44.018 L3 message with anMIE message type set to CM SERVICE REQUEST and an MIE CM servicetype set to either :- "emergency call establishment",- or "mobile originating callestablishment"This counter is incremented only if the L3 info message receivedhas to be forwarded to the MSC.








3BK 21255 AAAA PCZZA Ed.07 597 / 1256


22.3.8.3.2.11 MC02i - NB_IMM_ASS_SUCC_MO_LCS

Long Name NB_IMM_ASS_SUCC_MO_LCS

Definition case: Mobile originated LCS procedure on SDCCH

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a cell,with the L3 INFORMATION field containing a 44.018 L3 message with an MIEmessage type set to CM SERVICE REQUEST and with an MIE CM service typeset to "Location Services" (LCS).This counter is incremented only if the L3 infomessage received has to be forwarded to the MSC








598 / 1256 3BK 21255 AAAA PCZZA Ed.07



22.3.8.4.1 –

22.3.8.4.1.1 MC140a - NB_TCH_NOR_ASS_REQ

Long Name NB_TCH_NOR_ASS_REQ

Definition 1) Number of normal assignment requests for TCH establishment (in HR or FRusage).2) Number of BSCGP DTM assignment command received from MFS,for MS camping on a SDCCH (i.e. the cases where a TCH was already allocatedto the MS are not taken into account). In this case, the TCH is establishedin signaling mode

Trigger condition 1) Whenever a 48.008 ASSIGNMENT REQUEST message for a normalTCH assignment is received from the MSC.2) Whenever a BSCGP DTMASSIGNMENT COMMAND message is received from MFS for a MS campingon a SDCCH



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 599 / 1256


22.3.8.4.1.2 MC140b - NB_TCH_NOR_ASS_ATPT

Long Name NB_TCH_NOR_ASS_ATPT

Definition Number of normal assignment attempts for TCH establishment (in HR or FRusage). This counter also takes into account DTM assignment commands forTCH establishment in signaling mode (FR usage only).

Trigger condition 1) Whenever a 44.018 ASSIGNMENT COMMAND message for a normal TCHassignment is sent to the MS. In case of multiband cell, only the first 44.018ASSIGNMENT COMMAND message is counted (when sent in the inner zone);the second 44.018 ASSIGNMENT COMMAND message sent in the outer zone(further to the ASSIGNEMENT FAILURE received with the cause protocolerror unspecified in the inner zone) is not counted.2) Whenever a 44.018DTM ASSIGNMENT COMMAND message is sent to the MS, containing theassignment of a TCH in signaling mode.



Sub Domain 3 –





600 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.1.3 MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT

Long Name NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT

Definition Number of TCH Normal Assignment- and incoming external TCHHandover/Directed Retry Requests with the ability to preempt another call withlower priority.

Trigger condition 1) Whenever the BSC receives a 48.008 ASSIGNMENT REQUEST messagewith the pre-emption capability indication set (pci bit=1 in the Priority IE),repetitions of the ASSIGNMENT REQUEST message in case of channelmodification are not counted, or2) Whenever the BSC receives a 48.008HANDOVER REQUEST message requesting a TCH channel withi) thepre-emption capability indication set (pci bit=1) and Extra Information IE (or OldBSS to New BSS IE) is absent, or ii) the pre-emption capability indication set(pci bit = 1) and the Pre-emption Recommendation of the Extra Information IE isset (prec bit = 1).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 601 / 1256


22.3.8.4.1.4 MC921b - NB_PREEMPT_CAP_ALLOC_SUCC

Long Name NB_PREEMPT_CAP_ALLOC_SUCC

Definition Number of preemption capable calls served with resources in the cell (with orwithout using the preemption feature).

Trigger condition Whenever the BSC has selected a channel to activate a TCH channel relatedto either 48.008 ASIGNMENT REQUEST, 48.008 VGCS/VBS ASSIGNMENTREQUEST, 48.008 HANDOVER REQUEST, 48.008 ESTABLISH INDICATIONwith the L3_INFORMATION field including a 44.018 NOTIFICATIONRESPONSE message and the call has the ability to pre-empt another call withlower priority (i.e. pci = 1).



Sub Domain 3 –





602 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.1.5 MC921c - NB_PREEMPTED_CALLS

Long Name NB_PREEMPTED_CALLS

Definition Number of pre-empted calls in the cell.

Trigger condition Whenever a 48.008 CLEAR REQUEST or UPLINK RELEASE INDICATIONmessage with preemption cause is sent to the MSC.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 603 / 1256


22.3.8.4.1.6 MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC

Long Name NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC

Definition Number of preemption capable call establishment requests that are successfullyserved in a neighbour cell with the help of the directed retry procedure.

Trigger condition Whenever a queued request for a preemption capable call is de-queued in theserving cell during the directed retry procedure because this call has beensuccessfully established in the target cell.



Sub Domain 3 –





604 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.1.7 MC921e - NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE

Long Name NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE

Definition Number of TCH Normal Assignment- and incoming (internal and external) TCHHandover/Directed Retry Successes indicating the facility of being preempt-ableby a call with a higher priority.

Trigger condition 1) Whenever the BSC sends a 48.008 ASSIGNMENT COMPLETE messageand the context of the call indicates that the preemption vulnerability indicationis set (pvi bit=1), or2) Whenever the BSC sends a 48.008 HANDOVERCOMPLETE message and the context of the call indicates that the preemptionvulnerability indication is set (pvi bit=1), or3) Whenever the BSC sends a 48.008HANDOVER PERFORMED message and the context of the call indicates thatthe preemption vulnerability indication is set (pvi bit=1).Note: This countercounts both inter-PLMN and intra-PLMN handover events.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 605 / 1256


22.3.8.4.1.8 MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS

Long Name NB_TCH_NOR_ASS_PREP_FAIL_PMIS

Definition Number of TCH (in HR or FR usage) normal assignment preparation failuresdue to A interface mismatch between the BSC and the MSC.

Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENTFAILURE (cause: "circuit pool mismatch")



Sub Domain 3 –





606 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.2 Failure

22.3.8.4.2.1 MC19 - NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110)

Long Name NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110)

Definition Number of TCH (in HR or FR usage) normal assignment and external handover-preparation failures due to A-channel status mismatch between the BSC andthe MSC.

Trigger condition 1) Whenever an 48.008 ASSIGNMENT REQUEST message selects a TTCHwhich is found to be unavailable by the BSS (Blocked or Busy).2) Whenever a48.008 HANDOVER REQUEST message selects a TTCH which is found tobe unavailable by the BSS (Blocked or Busy).Note: This counter counts bothinter-PLMN and intra-PLMN handover events.




Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 607 / 1256


22.3.8.4.2.2 MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE

Long Name NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE

Definition Number of TCH (in HR or FR usage) normal assignment preparation failuresbecause of the non-queuing of the ASSIGNMENT REQUEST message.Case:48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received whenno TCH is available in the cell. The request is rejected (by 48.008ASSIGNMENTFAILURE, cause: "no radio resource available"), because the queuing procedureis either:1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR(T11_forced=0 and QUEUE_ANYWAY=1)), or2) enabled within the BSC, i.e.T11 <> 0, but not requested by the MSC when QUEUE_ANYWAY=0.

Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENTFAILURE (cause: "no radio resource available") for a TCH channel becauseno TCH is available and either the queuing is disabled in the BSC (T11=0and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or thequeuing is enabled, QUEUE_ANYWAY=0, and the MSC does not requesta queuing.Note 1: The HMI name of the parameter QUEUE_ANYWAY is"FORCED_QUEUING".Note 2: In case of Mx BSC, "no TCH available" couldhappen when the TCH processing capacity of CCP reaches the limit defined bythe MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 areincremented by one.Note 3: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter








608 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.2.3 MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL

Definition MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (in FR or HRusage) is received when no TCH is available in the cell. The queuing is enabledwithin the BSC, but the request is rejected (by 48.008ASSIGNMENT FAILURE,cause: "no radio resource available"), because the queue is full and no requestof lower priority can be dequeued from the BSC queue.

Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENTFAILURE (cause: "no radio resource available") for a TCH channel because thequeue is full and no request of lower priority can be de-queued.Note 1: In caseof Mx BSC, "no TCH available" could happen when the TCH processing capacityof CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. Inthis case, this counter and MC926 are incremented by one.Note 2: In IP mode,this counter is increased by 1 if:- the cell mapped on a BTS is in IP congestionstatus;- or the TCH processing capacity of AbisBTSGroup reaches the limitdefined by the NB_MAX_ACTIVE_TCH_TS parameter








3BK 21255 AAAA PCZZA Ed.07 609 / 1256


22.3.8.4.2.4 MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Definition Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (inHR or FR usage) is available in the cell, timer T11 (case MSC requests forqueuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (caseQUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started,and before the timer expiry, the request is dequeued due to the receipt of ahigher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the BSC sends48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for thefirst transaction.Remark: As soon as an internal directed retry is attempted,the request is blocked within the BSC and cannot be dequeued by a higherpriority request.

Trigger condition The counter is incremented upon the sending of the 48.008 ASSIGMENTFAILURE (cause: "no radio resource available") for a de-queued TCHrequest (i.e. normal assignment) due to the receipt of a higher priorityrequest.Note 1: The HMI name of the parameter QUEUE_ANYWAY is"FORCED_QUEUING".Note 2: In case of Mx BSC, "no TCH available" couldhappen when the TCH processing capacity of CCP reaches the limit defined bythe MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 areincremented by one.Note 3: In IP mode, this counter is increased by 1 if:- the cellmapped on a BTS is in IP congestion status;- or the TCH processing capacity ofAbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter








610 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.2.5 MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX

Long Name NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX

Definition Number of TCH (in HR or FR usage) normal assignment -execution failuresdue to MS access problem, per TRX. This counter also takes into accountDTM assignment -execution failures due to MS access problem for TCHestablishment in signaling mode (FR usage only).MC746b = C746b

Trigger condition 1) The timer T3107 in the BSS supervising the TCH channel seizure by themobile expires (following the sending of 44.018 ASSIGNMENT COMMAND for aTCH channel that is not involved in a handover procedure).2) The timer T3107in the BSS supervising the TCH channel seizure by the mobile expires, followingthe sending of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel insignaling mode.3) The BSC receives a 44.018 ASSIGNMENT FAILURE onthe old (SDCCH) channel during the normal assignment procedure except incase of multiband cell, when the normal assignment procedure is performedin the inner zone and the ASSIGNMENT FAILURE is received with the cause"protocol error unspecified".4) The BSC receives a 44.018 DTM ASSIGNMENTFAILURE on the old (SDCCH) channel during the DTM assignment procedure,for a TCH in signaling mode.




Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 611 / 1256


22.3.8.4.2.6 MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS

Long Name NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS

Definition MC812 = C812 = C612a + C612b + C612c + C612d









612 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.3.8.4.3 Success

22.3.8.4.3.1 MC718 - NB_TCH_NOR_ASS_SUCC_TRX

Long Name NB_TCH_NOR_ASS_SUCC_TRX

Definition Number of TCH (in HR or FR usage) normal assignment successes, per TRX.This counter also takes into account normal assignment successes for TCHestablishment in signaling mode (FR usage only), for DTM.MC718 = C718

Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abisinterface for a TCH channel that is not involved in a handover procedure, intraffic or in signaling mode.




Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 613 / 1256



22.4.1 Channel

22.4.1.1 A channel


22.4.1.1.1.1 MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV

Long Name AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV

Definition Average number of A-traffic-channels (i.e. all A-channels except for N7, SPCand synchro) that are blocked or out of service.

Trigger condition Every 20 seconds, the TTCHs that satisfy one of the following conditions arecounted : a) Maintenance state is either IN TRAFFIC or FAULTY IN TRAFFIC orWAIT TRAFFIC CLEAR and Telephonic state is blockedb) Maintenance state iseither OPERATOR OUT OF SERVICE or FAULTY OUT OF SERVICENote:Thiscounter is not incremented if the channel is in the Maintenance state NOTEQUIPPED, or if the channel is in use for signalling (N7), for a semi-permanentconnection (SPC), or for synchronisation (channel 0).


Sub Domain 2 A channel


Measured Object BSC




614 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.1.1.2 MC36 - AV_NB_AVAIL_A_TRAF_CHAN

Long Name AV_NB_AVAIL_A_TRAF_CHAN

Definition Average number of available A-traffic-channels channels (i.e. all A-channelsexcept for N7, SPC and synchro).

Trigger condition Every 20 seconds, the TTCHs that satisfay one of the following conditions arecounted :Maintenance state is either IN TRAFFIC or FAULTY IN TRAFFIC orWAIT TRAFFIC CLEAR and Telephonic state is available free or availablebusy.Note:This counter is not incremented if the channel is in the Maintenancestate NOT EQUIPPED, or if the channel is in use for signalling (N7), for asemi-permanent connection (SPC), or for synchronisation (channel 0).


Sub Domain 2 A channel


Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 615 / 1256


22.4.1.2 CCCH


22.4.1.2.1.1 MC27 - AV_NB_AVAIL_CCCH

Long Name AV_NB_AVAIL_CCCH

Definition Average number of available CCCH channels.



Sub Domain 2 CCCH






616 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.3 SDCCH

22.4.1.3.1 –

22.4.1.3.1.1 MC803 - TIME_SDCCH_CONGESTION

Long Name TIME_SDCCH_CONGESTION

Definition Cumulated time (in seconds) during which the SDCCH request(s) are not servedbecause no SDCCH sub-channel is available.

Trigger condition The time counter is started whenever a SDCCH request cannot be served.Thetime counter is stopped whenever one of the following conditions is checked:- ifa SDCCH sub-channel becomes free and usable on a static SDCCH timeslotor on a dynamic timeslot allocated as SDCCH (i.e. when the timeslot is knownfrom the SDCCH_RM module). The term "usable" means here that the SDCCHsub-channel is not mapped on a TCU in a very high overload state, or,- if aSDCCH request is served successfully. This condition corresponds to the casethe SDCCH_RM module requests the TCH_RM module for a dynamic SDCCHtimeslot.


Sub Domain 2 SDCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 617 / 1256



22.4.1.3.2.1 MC26 - AV_NB_AVAIL_SDCCH

Long Name AV_NB_AVAIL_SDCCH

Definition Average number of available static SDCCH sub-channels (i.e. on static SDCCHtimeslots).

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value (real) is rounded up or down to the nearestinteger value.Note: "Available" has here to be understood as the operationalstate of a timeslot. The timeslot is available if it is not "blocked" or "out ofservice".


Sub Domain 2 SDCCH






618 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.3.2.2 MC800 - AV_NB_AVAIL_DYN_TS

Long Name AV_NB_AVAIL_DYN_TS

Definition Average number of available dynamic SDCCH/8 timeslots.

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value is rounded up or down to the nearest integervalue.


Sub Domain 2 SDCCH






3BK 21255 AAAA PCZZA Ed.07 619 / 1256


22.4.1.3.3 Usage

22.4.1.3.3.1 MC31 - NB_MAX_SIMUL_BUSY_SDCCH

Long Name NB_MAX_SIMUL_BUSY_SDCCH

Definition Maximum number of simultaneously busy SDCCH subchannels, taking intoaccount the following SDCCH sub-channels: 1) Static SDCCH/x sub-channels,2) Dynamic SDCCH sub-channels which are dynamically allocated on thedynamic SDCCH/8 timeslots.

Trigger condition At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to thecell:C31 = MAX ["old" C31 value (i.e. before the channel activation), number ofbusy SDCCH subchannels observed for the cell].


Sub Domain 2 SDCCH

Sub Domain 3 Usage





620 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.3.3.2 MC390 - NB_TIMES_SDCCH_BUSY (110)

Long Name NB_TIMES_SDCCH_BUSY (110)

Definition MC390=SUM (all TRX_TS of the TRX) C39, C39 is NB_TIMES_SDCCH_BUSYin type 4.



Sub Domain 2 SDCCH

Sub Domain 3 Usage

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 621 / 1256


22.4.1.3.3.3 MC802a - AV_NB_BUSY_DYN_SDCCH

Long Name AV_NB_BUSY_DYN_SDCCH

Definition Average number of busy SDCCH sub-channels allocated on the dynamicSDCCH/8 timeslots.

Trigger condition The BSC takes periodically a sample of the number of busy dynamic SDCCHsub-channels. The sampling period is set to the value indicated in the StatusInspection field. At the expiry of the accumulation period, all samples areaveraged (i.e. summed and divided by the number of samples). The averagedvalue is rounded up or down to the nearest value with an accuracy of 0.1.Adynamic SDCCH sub-channel is considered as busy during the time it isallocated to a given MS for SDCCH traffic.Note that the counter value that isindicated in the ASCII file (which can be obtained via the OBSYNT interface)is an integer value (i.e. it is as if the BSC multiplies by 10 the average). Thereported value shall then be divided by 10 afterwards so that the value that isdisplayed to the end-user is the correct one


Sub Domain 2 SDCCH

Sub Domain 3 Usage





622 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.3.3.4 MC802b - MAX_NB_BUSY_DYN_SDCCH

Long Name MAX_NB_BUSY_DYN_SDCCH

Definition Maximum number of busy dynamic SDCCH sub-channels allocated on thedynamic SDCCH/8 timeslots.

Trigger condition Whenever a dynamic SDCCH sub-channel becomes busy, the BSC determinesthe current number of busy dynamic SDCCH sub-channels. Counter MC802b isthe maximum value of this number during the accumulation period.


Sub Domain 2 SDCCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 623 / 1256


22.4.1.4 TCH


22.4.1.4.1.1 MC250 - AV_NB_AVAIL_TCH

Long Name AV_NB_AVAIL_TCH

Definition Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (forHR or FR usage) or PDCH).

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. The averaged value is rounded up or down to the nearest integervalue.Note 1: "Available" has here to be understood as the operational state of atimeslot. The timeslot is available if it is not "blocked" or "out of service".Note 2:The dynamic SDCCH timeslots are not taken into account in this counter.


Sub Domain 2 TCH






624 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2 Usage

22.4.1.4.2.1 MC141 - AV_NB_TCH_QUEUED

Long Name AV_NB_TCH_QUEUED

Definition Average number of queued TCH (in HR or FR usage) normal assignment orexternal handover requests.

Trigger condition At Accumulation Period expiry, all observations of this counter done at eachpolling period are averaged, i.e. summed and divided by the number ofobservations. In order to provide one decimal place, the averaged value (real) ismultiplied by ten and then rounded up or down to the nearest integer value.Notethat the counter value that is indicated in the ASCII file, which can be obtainedvia the OBSYNT interface, still has to be divided by 10, whereas the value thatis provided at the user interface is the correct one.


Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 625 / 1256


22.4.1.4.2.2 MC28a - AV_NB_BUSY_CS_TS

Long Name AV_NB_BUSY_CS_TS

Definition Average number of busy TCH radio timeslot (in FR or HR usage, in traffic or insignaling mode) and busy dynamic SDCCH/8 radio timeslot allocated as TCH.

Trigger condition The BSC takes periodically a sample of the number of busy TCH radio timeslotsand busy dynamic SDCCH/8 radio timeslots allocated as TCH. The samplingperiod is set to the value indicated in the Status Inspection field. At the expiry ofthe accumulation period, all samples are averaged (i.e. summed and dividedby the number of samples). The averaged value is rounded up or down to thenearest value with an accuracy of 0.1.A TCH radio timeslot is considered asbusy during the time it is allocated to a given MS for TCH traffic (in HR or FRusage). A dynamic SDCCH/8 timeslot allocated as TCH is considered as busyduring the time it is allocated to a given MS for TCH traffic.Note 1: the countervalue that is indicated in the ASCII file (which can be obtained via the OBSYNTinterface) is an integer value (i.e. it is as if the BSC multiplies by 10 the average).The reported value shall then be divided by 10 afterwards so that the value thatis displayed to the end-user is the correct one.Note 2: This counter does nottake into account the PDCH radio timeslots allocated to the MFS.


Sub Domain 2 TCH

Sub Domain 3 Usage





626 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2.3 MC29a - NB_MAX_SIMUL_BUSY_CS_TS

Long Name NB_MAX_SIMUL_BUSY_CS_TS

Definition Maximum number of simultaneously busy TCH radio timeslots (in HR orFR usage, in traffic or in signaling mode) and simultaneously busy dynamicSDCCH/8 radio timeslots allocated as TCH.

Trigger condition Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocatedas TCH becomes busy, the BSC determines the current number of busy TCHradio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslotsallocated as TCH. This counter is the maximum value of this number duringthe accumulation period.This counter does not take into account the PDCHsallocated to the MFS.


Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 627 / 1256


22.4.1.4.2.4 MC320a - AV_NB_IDLE_TCH_INTERF_BAND1





Sub Domain 2 TCH

Sub Domain 3 Usage





628 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2.5 MC320b - AV_NB_IDLE_TCH_INTERF_BAND2





Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 629 / 1256


22.4.1.4.2.6 MC320c - AV_NB_IDLE_TCH_INTERF_BAND3





Sub Domain 2 TCH

Sub Domain 3 Usage





630 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2.7 MC320d - AV_NB_IDLE_TCH_INTERF_BAND4


Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FRor HR usage belonging to the interference band 4. This number is updated uponthe receipt of 48.058 RF RESOURCE INDICATION.



Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 631 / 1256


22.4.1.4.2.8 MC320e - AV_NB_IDLE_TCH_INTERF_BAND5





Sub Domain 2 TCH

Sub Domain 3 Usage





632 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2.9 MC370a - NB_TRX_FR_ALLOC

Long Name NB_TRX_FR_ALLOC

Definition MC370A= SUM(all TRX_TS of the TRX) (C370A)



Sub Domain 2 TCH

Sub Domain 3 Usage

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 633 / 1256


22.4.1.4.2.10 MC370b - NB_TRX_HR_ALLOC

Long Name NB_TRX_HR_ALLOC

Definition MC370B= SUM(all TRX_TS of the TRX) (C370B)



Sub Domain 2 TCH

Sub Domain 3 Usage

Measured Object TRX




634 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.4.2.11 MC801a - AV_NB_BUSY_DYN_TCH

Long Name AV_NB_BUSY_DYN_TCH

Definition Average number of busy dynamic SDCCH/8 timeslots allocated as TCH (in FR orHR usage). This counter takes into account TCH in traffic or in signaling mode.

Trigger condition The BSC takes periodically a sample of the number of busy dynamic SDCCH/8timeslots allocated as TCH. The sampling period is set to the value indicated inthe Status Inspection field. At the expiry of the accumulation period, all samplesare averaged (i.e. summed and divided by the number of samples). Theaveraged value is rounded up or down to the nearest value with an accuracyof 0.1.A dynamic SDCCH/8 timeslot is considered as busy and allocated asTCH during the time it is allocated to a given MS for TCH traffic (in FR or HRusage).Note that the counter value that is indicated in the ASCII file (which canbe obtained via the OBSYNT interface) is an integer value (i.e. it is as if the BSCmultiplies by 10 the average). The reported value shall then be divided by 10afterwards so that the value that is displayed to the end-user is the correct one


Sub Domain 2 TCH

Sub Domain 3 Usage





3BK 21255 AAAA PCZZA Ed.07 635 / 1256


22.4.1.4.2.12 MC801b - MAX_NB_BUSY_DYN_TCH

Long Name MAX_NB_BUSY_DYN_TCH

Definition Maximum number of busy dynamic SDCCH/8 timeslots allocated as TCH (inFR or HR usage). This counter takes into account TCH in traffic or in signalingmode.

Trigger condition Whenever a dynamic SDCCH/8 timeslot allocated as TCH becomes busy, theBSC determines the current number of busy dynamic SDCCH/8 timeslotsallocated as TCH (in HR or FR usage). Counter MC801b is the maximum valueof this number during the accumulation period.


Sub Domain 2 TCH

Sub Domain 3 Usage





636 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.1.5 TRX_TS


22.4.1.5.1.1 MC24 - AV_NB_NOT_AVAIL_TRX_TS

Long Name AV_NB_NOT_AVAIL_TRX_TS

Definition Average number of not available radio timeslots (TRX_TS).



Sub Domain 2 TRX_TS






3BK 21255 AAAA PCZZA Ed.07 637 / 1256


22.4.1.5.2 Usage

22.4.1.5.2.1 MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY

Long Name TIME_ALL_AVAIL_TRX_TS_BUSY

Definition Cumulated time (in seconds) during which there is no free FR TCH sub-channelto serve an incoming FR TCH request. A TCH sub-channel is seen as busy:i)if the TCH sub-channel is occupied by a HR or FR CS call (in particular if it isoccupied by the CS part of a DTM call), orii) if the TCH sub-channel is allocatedto the MFS to carry PS traffic.

Trigger condition The counter is started when there is no free FR TCH sub-channel to serve anincoming FR TCH request.The counter is stopped when there is a free FR TCHsub-channel to serve an incoming FR TCH request.


Sub Domain 2 TRX_TS

Sub Domain 3 Usage





638 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.2 Interface

22.4.2.1 A


22.4.2.1.1.1 MN1.1 - TIME_N7_ALIGNED

Long Name TIME_N7_ALIGNED

Definition Time (in seconds) during which the N7 SL is correctly aligned.

Trigger condition Whenever the No.7 Signalling channel between the MSC and BSS is correctlyaligned, this counter will be incremented every second.


Sub Domain 2 A






3BK 21255 AAAA PCZZA Ed.07 639 / 1256



22.4.3.1 –

22.4.3.1.1 –

22.4.3.1.1.1 MC922h - TIME_3G_HOReject_HL

Long Name TIME_3G_HOReject_HL

Definition Cumulative time (in seconds) during which the Cell is in 3G high load state.

Trigger condition Whenever the 3G_HOReject_Load State in the cell is reported as high orreported as indefinite while the previous state was high. This counter shall beincremented only if THR_CELL_LOAD_3G_REJECT < 100%.


Sub Domain 2 –

Sub Domain 3 –





640 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.2 DTM Assignment

22.4.3.2.1 –

22.4.3.2.1.1 MC927a - NB_DTM_UL_TCH_ASS_ATPT

Long Name NB_DTM_UL_TCH_ASS_ATPT

Definition Number of UL TBF establishment attempts in DTM with reallocation of the TCH(sending of DTM Assignment Command with UL TBF).

Trigger condition Whenever the BSC sends (through the BTS) 44.018 DTM ASSIGNMENTCOMMAND message that includes the "Description of the Uplink PacketChannel Assignment" optional IE.


Sub Domain 2 DTM Assignment

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 641 / 1256


22.4.3.2.1.2 MC927b - NB_DTM_DL_TCH_ASS_ATPT

Long Name NB_DTM_DL_TCH_ASS_ATPT

Definition Number of DL TBF establishment attempts in DTM with reallocation of the TCH(sending of DTM Assignment Command with DL TBF)

Trigger condition Whenever the BSC sends (through the BTS) 44.018 DTM ASSIGNMENTCOMMAND message that includes the "Description of the Downlink PacketChannel Assignment" optional IE.



Sub Domain 3 –





642 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.2.1.3 MC927c - NB_DTM_UL_PACKET_ASS_ATPT

Long Name NB_DTM_UL_PACKET_ASS_ATPT

Definition Number of UL TBF establishment attempts in DTM without reallocation of theTCH (sending of Packet Assignment Command with UL TBF).

Trigger condition Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENTmessage that includes the "Description of the Uplink Packet ChannelAssignment" optional IE.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 643 / 1256


22.4.3.2.1.4 MC927d - NB_DTM_DL_PACKET_ASS_ATPT

Long Name NB_DTM_DL_PACKET_ASS_ATPT

Definition Number of DL TBF establishment attempts in DTM without reallocation of theTCH (sending of Packet Assignment Command with DL TBF).

Trigger condition Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENTmessage that includes the "Description of the Downlink Packet ChannelAssignment" optional IE.



Sub Domain 3 –





644 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.2.1.5 MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO

Long Name NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO

Definition Number of UL TBF establishment in DTM with reallocation of the TCH -execution failures due to MS access problem.

Trigger condition 1) Whenever the BSC receives from the BTS a DATA INDICATION (DTMASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018DTM ASSIGNMENT COMMAND message that includes the "Description of theUplink Packet Channel Assignment" optional IE.2) After having sent (throughthe BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the"Description of the Uplink Packet Channel Assignment" optional IE, upon T3107expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE (on theold channel) nor ASSIGNMENT COMPLETE (on the new channel) messages.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 645 / 1256


22.4.3.2.1.6 MC927f - NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO

Long Name NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO

Definition Number of DL TBF establishment in DTM with reallocation of the TCH -execution failures due to MS access problem.

Trigger condition 1) Whenever the BSC receives from the BTS a DATA INDICATION (DTMASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018DTM ASSIGNMENT COMMAND message that includes the "Description of theDownlink Packet Channel Assignment" optional IE.2) After having sent (throughthe BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the"Description of the Downlink Packet Channel Assignment" optional IE, uponT3107 expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE(on the old channel) nor ASSIGNMENT COMPLETE (on the new channel)messages.



Sub Domain 3 –





646 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.3 E-GSM

22.4.3.3.1 –

22.4.3.3.1.1 MC706 - NB_EGSM_MS_ACCESS_EXCEPT_LU

Long Name NB_EGSM_MS_ACCESS_EXCEPT_LU

Definition Number of initial accesses for call establishments (except location update) ofMS supporting the E-GSM band, on a CELL basis.MC706 = C706

Trigger condition Whenever a 44.018 CLASSMARK CHANGE message in the context of anyestablishment causes different from location update is received on Abisinterface with a "Mobile Station Classmark 3" or a "Mobile Station Classmark 2"Information Element field specifying that the MS supports the E-GSM band.Thecounter is incremented only once per SCCP connection in the serving cell, i.e.on receipt of the first 44.018 CLASSMARK CHANGE message.


Sub Domain 2 E-GSM

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 647 / 1256


22.4.3.4 Service

22.4.3.4.1 –

22.4.3.4.1.1 MC701a - NB_TCH_FR_REQ

Long Name NB_TCH_FR_REQ

Definition Number of TCH normal assignments requests from FR only mobiles (afterpossible filtering from the MSC).

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withonly GSM speech coding algorithm version 1 full rate allowed.



Sub Domain 3 –





648 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.2 MC701b - NB_TCH_DR_REQ

Long Name NB_TCH_DR_REQ

Definition Number of TCH normal assignments requests from dual rate mobiles.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withonly GSM speech coding algorithm version 1 full rate and GSM speech codingalgorithm version 1 half rate allowed.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 649 / 1256


22.4.3.4.1.3 MC701c - NB_TCH_DR_EFR_REQ

Long Name NB_TCH_DR_EFR_REQ

Definition Number of TCH normal assignment requests from mobiles supporting FR, HRand EFR.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withGSM speech coding algorithm version 1 full rate, GSM speech coding algorithmversion 1 half rate and GSM speech coding algorithm version 2 full rate allowed.



Sub Domain 3 –





650 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.4 MC701d - NB_TCH_AMR_REQ

Long Name NB_TCH_AMR_REQ

Definition Number of TCH normal assignment requests from AMR mobiles.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withGSM speech coding algorithm version 3 full rate or half rate allowed.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 651 / 1256


22.4.3.4.1.5 MC701e - NB_TCH_DATA_REQ

Long Name NB_TCH_DATA_REQ

Definition Number of TCH normal assignment requests for data calls.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.



Sub Domain 3 –





652 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.6 MC701f - NB_TCH_FR_EFR_REQ

Long Name NB_TCH_FR_EFR_REQ

Definition Number of TCH normal assignments requests from mobiles supporting only FRand EFR (after possible filtering from the MSC).

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withonly GSM speech coding algorithm version 1 full rate and GSM speech codingalgorithm version 2 full rate allowed.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 653 / 1256


22.4.3.4.1.7 MC701g - NB_TCH_NO_FR_REQ

Long Name NB_TCH_NO_FR_REQ

Definition Number of TCH normal assignments requests from mobiles with followingspeech capability (after possible filtering of the MSC):- HR only, - EFR&HRonly, - EFR only

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech callwith:- only GSM speech coding algorithm version 1 half rate allowed- only GSMspeech coding algorithm version 1 half rate and version 2 full rate allowed- onlyGSM speech coding algorithm version 2 full rate allowed



Sub Domain 3 –




External Comment 1) From 3GPP point of view, HR only, EFR&HR only, EFR only are not allowed,as support of FR is mandatory. They are however counted for completion2) MSsupporting AMR and not FR are taken into account in MC701d (although suchconfiguration is also forbidden by 3GPP).

654 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.8 MC702a - NB_TCH_NOR_FR_ALLOC

Long Name NB_TCH_NOR_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR usage - whose channelis allocated in the BSC. This counter takes into account mode modify from TCHsignaling to TCH traffic (following a DTM assignment with a TCH in signalingmode).




Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 655 / 1256


22.4.3.4.1.9 MC702b - NB_TCH_NOR_HR_ALLOC

Long Name NB_TCH_NOR_HR_ALLOC

Definition number of TCH normal assignment/mode modify in HR usage - whose channelis allocated in the BSC.

Trigger condition 48.058 CHANNEL ACTIVATION / MODE MODIFY about to be sent to theBTS, indicating a HR channel with GSM speech coding algorithm version 1,not related to handover.



Sub Domain 3 –





656 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.10 MC702c - NB_TCH_NOR_EFR_ALLOC

Long Name NB_TCH_NOR_EFR_ALLOC

Definition Number of TCH normal assignment/mode modify in EFR usage - whosechannel is allocated in the BSC. This counter takes into account mode modifyfrom TCH signaling to TCH traffic (following a DTM assignment with a TCH insignaling mode).




Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 657 / 1256


22.4.3.4.1.11 MC704a - NB_TCH_NOR_AMR_FR_ALLOC

Long Name NB_TCH_NOR_AMR_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR AMR usage - whosechannel is allocated in the BSC. This counter takes into account mode modifyfrom TCH signaling to TCH traffic (following a DTM assignment with a TCH insignaling mode).




Sub Domain 3 –





658 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.12 MC704b - NB_TCH_NOR_AMR_HR_ALLOC

Long Name NB_TCH_NOR_AMR_HR_ALLOC

Definition number of TCH normal assignment/mode modify in HR AMR usage - whosechannel is allocated in the BSC.

Trigger condition 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS,indicating a HR channel with GSM speech coding algorithm version 3, notrelated to handover.



Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 659 / 1256


22.4.3.4.1.13 MC705 - NB_TCH_NOR_DATA_ALLOC

Long Name NB_TCH_NOR_DATA_ALLOC

Definition Number of TCH normal assignment/mode modify for data - whose channel isallocated in the BSC. This counter takes into account mode modify from TCHsignaling to TCH traffic (following a DTM assignment with a TCH in signalingmode).

Trigger condition 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS,indicating a data call, not related to handover.



Sub Domain 3 –





660 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.4.3.4.1.14 MC931 - NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC

Long Name NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR AMR WB GMSK usage- whose channel is allocated in the BSC. This counter takes into account modemodify from TCH signaling to TCH traffic (following a DTM assignment with aTCH in signaling mode).




Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 661 / 1256


22.4.3.4.1.15 MC932 - NB_TCH_AMR_WB_GMSK_REQ

Long Name NB_TCH_AMR_WB_GMSK_REQ

Definition Number of TCH normal assignment requests from AMR WB GMSK mobiles

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call withGSM speech coding algorithm version 5 full rate allowed.



Sub Domain 3 –





662 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5 Traffic Load

22.5.1 BSC

22.5.1.1 –

22.5.1.1.1 –

22.5.1.1.1.1 MC926 - TCH_BLOCKING_OCCURENCES_BSC

Long Name TCH_BLOCKING_OCCURENCES_BSC

Definition Number of TCH channel allocation rejected for cause : Maximum TCHprocessing capacity of CCP reached

Trigger condition Whenever a TCH cannot be allocated due to the TCH processing capacity ofCCP reaches the limit defined by the MAX_TCH_PER_CCP parameter.

Sub Domain 1 BSC

Sub Domain 2 –

Sub Domain 3 –

Measured Object BSC




3BK 21255 AAAA PCZZA Ed.07 663 / 1256


22.5.2 Channel

22.5.2.1 –

22.5.2.1.1 –

22.5.2.1.1.1 MC925a - NB_AGCH_USEFUL_BLOCKS_SENT

Long Name NB_AGCH_USEFUL_BLOCKS_SENT

Definition Number of useful blocks sent on AGCH channel (The dummy blocks are notcounted).

Trigger condition This counter is increased each time an IMMEDIATE ASSIGNMENT orIMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENTREJECT or PACKET UPLINK ASSIGNMENT or PACKET DOWNLINKASSIGNMENT message is taken from one AGCH queue and put on AGCHchannel.Note: for cells mapped on non-Evolium BTS, the value of this counteris set to zero.


Sub Domain 2 –

Sub Domain 3 –





664 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.1.1.2 MC925b - NB_PCH_USEFUL_BLOCKS_SENT

Long Name NB_PCH_USEFUL_BLOCKS_SENT

Definition Number of useful blocks sent on PCH channel (The dummy blocks are notcounted).

Trigger condition This counter is increased each time a PAGING REQUEST message is takenfrom one Paging_Group FIFO and put on PCH channel.Note: for cells mappedon non-Evolium BTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 665 / 1256


22.5.2.1.1.3 MC925c - NB_BUSY_RACH_SLOTS

Long Name NB_BUSY_RACH_SLOTS

Definition Number of busy RACH slots.

Trigger condition Each 51-multiframes the Layer 1 reports the load on the RACH via theRACH_MEASUREMENTS_RESULTS message, which contains the followinginformation:- N_VRACH: number of Access Bursts successfully decoded-N_BUSY: number of RACH busy slotsOn reception of this message, the followingcounters are updated:- NB_BUSY_RACH_SLOTS = NB_BUSY_RACH_SLOTS+ N_BUSYNote: for cells mapped on non-Evolium BTS, the value of this counteris set to zero.


Sub Domain 2 –

Sub Domain 3 –





666 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.1.1.4 MC925d - NB_CHANNEL_RQ_RADIO

Long Name NB_CHANNEL_RQ_RADIO

Definition Number of channel request messages received on the radio interface or numberof access bursts successfully decoded.

Trigger condition Each 51-multiframes the Layer 1 reports the load on the RACH via theRACH_MEASUREMENTS_RESULTS message, which contains thefollowing information:- N_VRACH: number of Access Bursts successfullydecoded- N_BUSY: number of RACH busy slotsOn reception of thismessage, the following counters are updated:- NB_CHANNEL_RQ_RADIO= NB_CHANNEL_RQ_RADIO + N_VRACHNote: for cells mapped onnon-Evolium BTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 667 / 1256


22.5.2.1.1.5 MC925e - NB_ASSIGN_CMD_RECEIVED_ABIS

Long Name NB_ASSIGN_CMD_RECEIVED_ABIS

Definition Number of 48.058 IMMEDIATE ASSIGN COMMAND messages received by theBTS on Abis and had to be sent for CS and PS traffic to the MS. Note: Thiscounter does not count what it is really sent on the interface radio on the AGCHchannel because some messages can be discarded due to congestion someothers can be merged in one message (Immediate assignment extended) andsome others sent in PCH channel when the AGCH is up to 100%.

Trigger condition This counter is increased each time an IMMEDIATE ASSIGNMENT COMMANDmessage is received on Abis interface.Note: for cells mapped on non-EvoliumBTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





668 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.1.1.6 MC925f - NB_ASSIGN_CMD_DISCARDED

Long Name NB_ASSIGN_CMD_DISCARDED

Definition Number of 48.058 IMMEDIATE ASSIGN COMMAND messages received by theBTS on Abis and discarded due to congestion.

Trigger condition This counter is increased each time an IMMEDIATE ASSIGNMENT COMMANDmessages is discarded on detection of AGCH FIFO overload.Note: for cellsmapped on non-Evolium BTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 669 / 1256


22.5.2.1.1.7 MC925g - NB_PAGING_CMD_RECEIVED_ABIS

Long Name NB_PAGING_CMD_RECEIVED_ABIS

Definition Number of PAGING COMMAND received by the BTS on Abis and had to besent for CS and PS traffic to the MS.Note: This counter does not count what it isreally sent on the PCH channel of radio interface because some messages canbe discarded due to congestion and some others can be merged in one

Trigger condition 1) Applicable to the legacy BSC only: this counter is increased by one each timea PAGING COMMAND message is received on Abis interface.2) Applicableto the BSC Evolution only: a) This counter is increased by one each time aPAGING COMMAND message is received on Abis interface.b) This counteris increased by "n" each time a MULTIPLE PAGING COMMAND message isreceived on Abis interface ("n" is the number of PAGING COMMAND containedin the received MULTIPLE PAGING COMMAND message).Note: for cellsmapped on non-Evolium BTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





670 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.1.1.8 MC925h - NB_PAGING_CMD_DISCARDED

Long Name NB_PAGING_CMD_DISCARDED

Definition Number of PAGING COMMAND received by the BTS on Abis and discardeddue to congestion.

Trigger condition 1) Applicable to the legacy BSC only: this counter is increased by one eachtime a PAGING COMMAND is discarded on detection of Paging_Group FIFOoverload.2) Applicable to the BSC Evolution only: This counter is increasedby one each time a PAGING COMMAND is discarded on detection of PagingGroup FIFO overloaded (Note 1).Note 1: It does not matter whether thediscarded (and counted) PAGING COMMAND was received in an individualPAGING COMMAND message or if it was received (as one of several PAGINGCOMMANDs) within a MULTIPLE PAGING COMMAND message.Note: for cellsmapped on non-Evolium BTS, the value of this counter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 671 / 1256


22.5.2.1.1.9 MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED

Long Name NB_ABIS_PAGING_MESSAGE_RECEIVED

Definition Number of PAGING COMMAND / MULTIPLE PAGING COMMAND messagereceived by the BTS on Abis.

Trigger condition For legacy BSC, the value of this counter shall be set to "0".For BSCEVOLUTION:a) This counter is increased by one each time a PAGINGCOMMAND message is received on Abis interface.b) This counter is increasedby one each time a MULTIPLE PAGING COMMAND message is received onAbis interface.Note: for cells mapped on non-Evolium BTS, the value of thiscounter is set to zero.


Sub Domain 2 –

Sub Domain 3 –





672 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.2 CCCH

22.5.2.2.1 –

22.5.2.2.1.1 MC804a - NB_UL_SINGLE_BLOCK_SIG_RACH

Long Name NB_UL_SINGLE_BLOCK_SIG_RACH

Definition Number of Channel Request messages with access cause "Single block packetaccess" received by the BSS.

Trigger condition Whenever a 48.058 CHANNEL REQUIRED message with access cause "Singleblock packet access" is received on Abis interface.


Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 673 / 1256


22.5.2.2.1.2 MC804b - NB_UL_ONE_PHASE_SIG_RACH

Long Name NB_UL_ONE_PHASE_SIG_RACH

Definition Number of Channel Request messages with access cause "One phase packetaccess with request for single timeslot uplink transmission" received by the BSS.

Trigger condition This counter is incremented whenever a 48.058 CHANNEL REQUIREDmessage with access cause "One phase packet access with request for singletimeslot uplink transmission" is received on Abis interface.


Sub Domain 2 CCCH

Sub Domain 3 –





674 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.2.1.3 MC805a - NB_CHANNEL_ASSIGN_DL_AGCH

Long Name NB_CHANNEL_ASSIGN_DL_AGCH

Definition Number of Immediate Assignment messages sent on AGCH for GPRS traffic.

Trigger condition Whenever a BSCGP Channel Assignment Downlink message is received forMS in non-DRX mode.


Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 675 / 1256


22.5.2.2.1.4 MC805b - NB_CHANNEL_ASSIGN_DL_PCH

Long Name NB_CHANNEL_ASSIGN_DL_PCH

Definition Number of Immediate Assignment messages sent on PCH for GPRS traffic.

Trigger condition Whenever a BSCGP Channel Assignment Downlink message is received forMS in DRX mode.


Sub Domain 2 CCCH

Sub Domain 3 –





676 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.2.1.5 MC8a - NB_CELL_PAGING_CMD

Long Name NB_CELL_PAGING_CMD

Definition MC8A= SUM (all TRX_TS of the Cell) C8A



Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 677 / 1256


22.5.2.2.1.6 MC8b - NB_CELL_IMM_ASS_CMD

Long Name NB_CELL_IMM_ASS_CMD

Definition MC8B= SUM (all TRX_TS of the Cell) C8B



Sub Domain 2 CCCH

Sub Domain 3 –





678 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.2.1.7 MC8c - NB_CELL_CHAN_REQD

Long Name NB_CELL_CHAN_REQD

Definition MC8C= SUM (all TRX_TS of the cell) C8C



Sub Domain 2 CCCH

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 679 / 1256


22.5.2.2.1.8 MC8d - NB_CELL_IMM_ASS_REJ

Long Name NB_CELL_IMM_ASS_REJ

Definition MC8D= SUM (all TRX_TS of the cell) C8D



Sub Domain 2 CCCH

Sub Domain 3 –





680 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.3 SDCCH

22.5.2.3.1 –

22.5.2.3.1.1 MC400 - TIME_TRX_SDCCH_BUSY

Long Name TIME_TRX_SDCCH_BUSY

Definition MC400= SUM (all TRX_TS of the TRX) C40



Sub Domain 2 SDCCH

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 681 / 1256


22.5.2.4 TCH

22.5.2.4.1 –

22.5.2.4.1.1 MC380a - TIME_TRX_FR_BUSY

Long Name TIME_TRX_FR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot in FR usage is busy

Trigger condition MC380A= SUM (all TRX_TS of the TRX) (C380A)


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




682 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.4.1.2 MC380b - TIME_TRX_HR_BUSY

Long Name TIME_TRX_HR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot in HR usage is busy

Trigger condition MC380B= SUM (all TRX_TS of the TRX) (C380B)


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 683 / 1256


22.5.2.4.1.3 MC380c - TIME_TRX_GSM_FR_BUSY

Long Name TIME_TRX_GSM_FR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8timeslot in the GSM frequency band is busy in FR usage. This counter takesinto account TCH in traffic or in signaling mode.

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all unittimes during which the TCH FR channel in the GSM frequency band is busy. Foreach channel allocation: The counter starts being incremented after the sendingof the 48.058 CHANNEL ACTIVATION message to the cell concerning a full rateTCH channel for the related TRX timeslot. The counter stops being incrementedafter the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGEmessage or the expiry of timer T_RCR_ACK twice (after the sending of the48.058 RF CHANNEL RELEASE message) concerning the TCH channelpreviously activated on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




684 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.4.1.4 MC380d - TIME_TRX_GSM_HR_BUSY

Long Name TIME_TRX_GSM_HR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8timeslot in the GSM frequency band is busy in HR usage.

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all unittimes during which the TCH HR channel in the GSM frequency band is busy.For each channel allocation: The counter starts being incremented after thesending of the 48.058 CHANNEL ACTIVATION message to the cell concerninga half rate TCH channel for the related TRX timeslot. The counter stopsbeing incremented after the reception of a 48.058 RF CHANNEL RELEASEACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after thesending of the 48.058 RF CHANNEL RELEASE message) concerning the TCHchannel previously activated on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 685 / 1256


22.5.2.4.1.5 MC380e - TIME_TRX_DCS_FR_BUSY

Long Name TIME_TRX_DCS_FR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8timeslot in the DCS/PCS frequency band is busy in FR usage. This countertakes into account TCH in traffic or in signaling mode.

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, allunit times during which the TCH FR channel in the DCS/PCS frequency bandis busy. For each channel allocation: The counter starts being incrementedafter the sending of the 48.058 CHANNEL ACTIVATION message to thecell concerning a full rate TCH channel for the related TRX timeslot. Thecounter stops being incremented after the reception of a 48.058 RF CHANNELRELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice(after the sending of the 48.058 RF CHANNEL RELEASE message) concerningthe TCH channel previously activated on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




686 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.4.1.6 MC380f - TIME_TRX_DCS_HR_BUSY

Long Name TIME_TRX_DCS_HR_BUSY

Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8timeslot in the DCS/PCS frequency band is busy in HR usage.

Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, allunit times during which the TCH HR channel in the DCS/PCS frequency bandis busy. For each channel allocation: The counter starts being incrementedafter the sending of the 48.058 CHANNEL ACTIVATION message to thecell concerning a half rate TCH channel for the related TRX timeslot. Thecounter stops being incremented after the reception of a 48.058 RF CHANNELRELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice(after the sending of the 48.058 RF CHANNEL RELEASE message) concerningthe TCH channel previously activated on the related TRX timeslot.


Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 687 / 1256


22.5.2.4.1.7 MC381 - TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS

Long Name TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS

Definition MC381= SUM (over all TRX_TS of the TRX) (C381A+C381B)



Sub Domain 2 TCH

Sub Domain 3 –

Measured Object TRX




688 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.2.4.1.8 MC924a - TIME_SPDCH_LIMIT_HIGH_LOAD

Long Name TIME_SPDCH_LIMIT_HIGH_LOAD

Definition Time during which the cell is in high load situation for PS traffic. This situationimpacts the number of slave PDCHs that can be allocated to the MFS.

Trigger condition The timer starts whenever MAX_SPDCH_LIMIT calculated by the BSC is equalor below MAX_SPDCH_HIGH_LOAD. MAX_SPDCH_HIGH_LOAD is calculatedby the BSC based on MAX_PDCH_HIGH_LOAD and NB_TS_MPDCHO&M parameters.The timer stops when MAX_SPDCH_LIMIT is greater thanMAX_SPDCH_HIGH_LOAD.


Sub Domain 2 TCH

Sub Domain 3 –




External Comment This counter replaces the B8 MFS counter P1.

3BK 21255 AAAA PCZZA Ed.07 689 / 1256


22.5.3 Interface

22.5.3.1 A

22.5.3.1.1 SCCP

22.5.3.1.1.1 MC350 - NB_N7_CON_REQ

Long Name NB_N7_CON_REQ




Sub Domain 2 A

Sub Domain 3 SCCP





690 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.3.1.1.2 MC351 - NB_N7_CON_CONF

Long Name NB_N7_CON_CONF




Sub Domain 2 A

Sub Domain 3 SCCP





3BK 21255 AAAA PCZZA Ed.07 691 / 1256



22.5.4.1 Directed Retry

22.5.4.1.1 External

22.5.4.1.1.1 MC144f - NB_OUT_EDR_REQ

Long Name NB_OUT_EDR_REQ

Definition MC144f=C144b+C144d









692 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.4.1.2 Internal

22.5.4.1.2.1 MC144e - NB_OUT_IDR_REQ

Long Name NB_OUT_IDR_REQ

Definition MC144e=C144a+C144c









3BK 21255 AAAA PCZZA Ed.07 693 / 1256


22.5.4.1.2.2 MC15a - NB_INC_IDR_ALLOC

Long Name NB_INC_IDR_ALLOC

Definition MC15a=C15a, Number of incoming internal directed retry (towards a TCHchannel in HR or FR usage) whose target channel is allocated by the BSC.

Trigger condition The counter is incremented on the target cell whenever the 48.058 CHANNELACTIVATION message of a TCH channel is about to be sent during an internaldirected retry.








694 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.4.2 Handover

22.5.4.2.1 SDCCH

22.5.4.2.1.1 MC147 - NB_INC_SDCCH_HO_ALLOC

Long Name NB_INC_SDCCH_HO_ALLOC

Definition MC147=C147, Number of incoming internal or external SDCCH handovers-whose target SDCCH channel is allocated by the BSC.

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent onAbis Interface to activate an SDCCH channel for any handover purposes.Note:This counter counts both inter-PLMN and intra-PLMN handover events.



Sub Domain 3 SDCCH





3BK 21255 AAAA PCZZA Ed.07 695 / 1256


22.5.4.2.2 TCH

22.5.4.2.2.1 MC13b - NB_INC_EXT_TCH_HO_QUEUED

Long Name NB_INC_EXT_TCH_HO_QUEUED

Definition Number of TCH (in HR or FR usage) incoming external handover requests thatare put in BSC queue

Trigger condition Further to the receipt of a 48.008 HANDOVER REQUEST message forTCH, the counter is incremented:i) upon the sending of a 48.008 QUEUINGINDICATION message if the queuing is authorised by the MSC, or,ii) when thehandover request is queued in the cell if the queuing is not authorised by theMSC and the request has its pre-emption indicator set (provided that the flagEN_TCH_PREEMPT is set to 'Enable').Note: MC13b = C13bNote: This countercounts both inter-PLMN and intra-PLMN handover events.



Sub Domain 3 TCH





696 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.4.2.2.2 MC15b - NB_INC_TCH_HO_ALLOC

Long Name NB_INC_TCH_HO_ALLOC

Definition Number of incoming TCH (in HR or FR usage) handover (internal or external)-whose target channel is allocated by the BSC.Since there are no reliable meansat the target BSC to distinguish external directed retry from external handover,the external directed retries are counted by this counter.

Trigger condition The counter is incremented on the target cell whenever the 48.058 CHANNELACTIVATION message of a TCH channel is about to be sent during anyhandover procedure.Note: This counter counts both inter-PLMN and intra-PLMNhandover events.



Sub Domain 3 TCH





3BK 21255 AAAA PCZZA Ed.07 697 / 1256



22.5.4.3.1 –

22.5.4.3.1.1 MC148 - NB_IMM_ASS_ALLOC

Long Name NB_IMM_ASS_ALLOC

Definition Number of immediate assignment plus SDCCH normal assignments -whoseSDCCH channel is allocated by the BSC.

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be senton Abis Interface to activate an SDCCH channel for any purpose other thanhandover.



Sub Domain 3 –





698 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.4.4 Multiband

22.5.4.4.1 –

22.5.4.4.1.1 MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

Long Name NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

Definition Number of initial accesses for call establishments (location update apart)initiated by multiband mobile stations. The counter is defined on a per cellbasis.A MS is considered as multiband if it supports:- the P-GSM (or E-GSMor R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDSparameter is set to "GSM900 and DCS1800 bands", or,- the GSM850 andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to"GSM850 and DCS1800 bands", or,- the GSM850 and the DCS1900 bands ifthe PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".

Trigger condition Whenever a 44.018 Classmark Change message in the context of anyestablishment cause different from location update is received on Abisinterface from the MS with a "Mobile Station Classmark 3" Information Elementspecifying that the MS supports:- the P-GSM (or E-GSM or R-GSM) andthe DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is setto "GSM900 and DCS1800 bands", or,- the GSM850 and the DCS1800bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850and DCS1800 bands", or,- the GSM850 and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900bands".The counter is incremented only once per SCCP connection in theserving cell, i.e. on receipt of the first 44.018 CLASSMARK CHANGE message.


Sub Domain 2 Multiband

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 699 / 1256



22.5.4.5.1 –

22.5.4.5.1.1 MC13a - NB_TCH_NOR_ASS_QUEUED

Long Name NB_TCH_NOR_ASS_QUEUED

Definition Number of TCH (in HR or FR usage) normal assignment requests that areput in BSC queue.

Trigger condition Further to the receipt of a 48.008 ASSIGNMENT REQUEST message forTCH, the counter is incremented:i) upon the sending of a 48.008 QUEUINGINDICATION message if the queuing is authorised by the MSC, or,ii) whenthe assignment request is queued in the cell if the queuing is not authorisedby the MSC and the parameter QUEUE_ANYWAY is set, or,iii) when theassignment request is queued in the cell if the queuing is not authorised by theMSC and the request has its pre-emption indicator set (provided that the flagEN_TCH_PREEMPT is set to 'Enable').Note 1: MC13a = C13aNote 2: The HMIname of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".



Sub Domain 3 –





700 / 1256 3BK 21255 AAAA PCZZA Ed.07


22.5.4.5.1.2 MC703 - NB_TCH_NOR_ASS_ALLOC_TRX

Long Name NB_TCH_NOR_ASS_ALLOC_TRX

Definition Number of TCH (in HR or FR usage) normal assignment whose RTCH channelis allocated in the BSC, per TRX. This counter also takes into account normalassignment whose RTCH channel is allocated in the BSC in signaling mode (FRusage only), for DTM.MC703 = C703

Trigger condition Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent onAbis Interface to activate a TCH channel for normal assignment, or for DTMassignment with a TCH in signaling mode.



Sub Domain 3 –

Measured Object TRX




3BK 21255 AAAA PCZZA Ed.07 701 / 1256


702 / 1256 3BK 21255 AAAA PCZZA Ed.07

23 BSC-TYPE 180 - 2G Traffic flow measurements


3BK 21255 AAAA PCZZA Ed.07 703 / 1256


23.1 Adjacency

23.1.1 BSC

23.1.1.1 –

23.1.1.1.1 –

23.1.1.1.1.1 C400 - NB_ADJ_BSC_INC_HO_REQ

Long Name NB_ADJ_BSC_INC_HO_REQ

Definition Number of incoming 2G to 2G external or internal inter-cell SDCCH or TCH (inHR or FR usage) handover requests. The internal and external directed retriesare counted.

Trigger condition 1) Internal handover : whenever an internal inter-cell SDCCH or TCH handoveris initiated by the handover process within the BSC from the serving cell to thetarget cell.2) External handover : 48.008 HANDOVER REQUEST received(including the MIE "Cell identifier" of the serving cell) by the BSC for an SDCCHor TCH external handover towards the target cell.Only handovers from a 2Gcell shall be taken into account (if the field Cell Identifier discriminator in theI.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 BSC

Sub Domain 2 –

Sub Domain 3 –


Type Name 2G Traffic flow measurements

Type Definition Set of incoming external or internal inter-cell SDCCH or TCH (in HR or FRusage) handover counters provided per adjacency: variable serving cell -variable target cell. The internal and external directed retries are counted. Onlyhandovers / directed retries from 2G cells are taken into account (i.e. handoversfrom 3G are not counted in type 180).


704 / 1256 3BK 21255 AAAA PCZZA Ed.07


23.1.1.1.1.2 C401 - NB_ADJ_BSC_INC_HO_ATPT

Long Name NB_ADJ_BSC_INC_HO_ATPT

Definition Number of incoming 2G to 2G external or internal inter cell SDCCH or TCH (inHR or FR usage) handover attempts. The internal and external directed retriesare counted.

Trigger condition 1) Internal handover : 44.018 HANDOVER COMMAND sent to the MS via theserving cell for an internal inter-cell SDCCH or TCH handover towards the targetcell.2) External handover : 48.008 HANDOVER REQUEST ACK sent to theMSC from the target BSC for an external SDCCH or TCH handover from theserving cell to the target cell. The MIE "Cell-Identifier" of the serving cell&targetcell are provided in 48.008 HANDOVER REQUEST.Only handovers from a2G cell shall be taken into account (if the field Cell Identifier discriminator inthe I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to0000 or 0001).Note: This counter counts both inter-PLMN and intra-PLMNhandover events.

Sub Domain 1 BSC

Sub Domain 2 –

Sub Domain 3 –





3BK 21255 AAAA PCZZA Ed.07 705 / 1256


23.1.1.1.1.3 C402 - NB_ADJ_BSC_INC_HO_SUCC

Long Name NB_ADJ_BSC_INC_HO_SUCC

Definition Number of incoming 2G to 2G external or internal inter cell SDCCH or TCH(in HR or FR usage) handover successes. The internal and external directedretries are counted.

Trigger condition 44.018HANDOVER_COMPLETE message received from the MS via the targetcell for an external or internal inter-cell SDCCH or TCH handover from theserving cell.Only handovers from a 2G cell shall be taken into account (if thefield Cell Identifier discriminator in the I.E. Cell Identifier (serving) of the 48.008HANDOVER REQUEST is set to 0000 or 0001).Note: This counter counts bothinter-PLMN and intra-PLMN handover events.

Sub Domain 1 BSC

Sub Domain 2 –

Sub Domain 3 –





706 / 1256 3BK 21255 AAAA PCZZA Ed.07

24 MFS-GPRS Counters


3BK 21255 AAAA PCZZA Ed.07 707 / 1256


24.1 Quality of service

24.1.1 Ater interface

24.1.1.1 LapD

24.1.1.1.1 N/A

24.1.1.1.1.1 P2a - NB_LAPD_INFO_FRAME_RESENT

Long Name NB_LAPD_INFO_FRAME_RESENT

Definition Number of Info frames retransmitted on the logical LapD link.

Trigger Condition Whenever an Info frame is retransmitted on the logical LapD link.

Sub Domain 1 Ater interface

Sub Domain 2 LapD

Sub Domain 3 N/A


External Comment The (decimal) value 1 000 000 means Driver LAPD not available. LAPD notestablished.Note : P32 indicates the time the LAPD is not available

708 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.1.1.1.2 P2b - NB_LAPD_RNR_SENT

Long Name NB_LAPD_RNR_SENT

Definition Number of Receive Not Ready (RNR) frames sent on the LapD logical link.

Trigger Condition Whenever an RNR frame is sent on the LapD logical link.


Sub Domain 2 LapD

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 709 / 1256


24.1.1.1.1.3 P2c - NB_LAPD_RNR_REC

Long Name NB_LAPD_RNR_REC

Definition Number of Receive Not Ready (RNR) frames received on the LapD logical link.

Trigger Condition Whenever an RNR frame is received on the LapD logical link.


Sub Domain 2 LapD

Sub Domain 3 N/A



710 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.1.1.1.4 P2d - NB_LAPD_EST

Long Name NB_LAPD_EST

Definition Number of data link establishment, re-establishment and reset on the LapD logicallink.

Trigger Condition 1) Whenever the MFS receives SABME while the LapD is in established state.2)Whenever the MFS receives the acknowledgment UA of SABME sent to the BSCin LapD established state.


Sub Domain 2 LapD

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 711 / 1256


24.1.2 Gb interface

24.1.2.1 Bearer Channel

24.1.2.1.1 N/A

24.1.2.1.1.1 P3a - NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS

Long Name NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS

Definition Number of frames discarded received on the Bearer Channel because of invalidFCS.

Trigger Condition Whenever a frame received on the Bearer Channel is discarded due to invalid FCS.

Sub Domain 1 Gb interface

Sub Domain 2 Bearer Channel

Sub Domain 3 N/A

Measured Object Bearer Channel


712 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.2.1.1.2 P3b - NB_BEAR_CHAN_FRAMES_DISC_INVALID_ADDR

Long Name NB_BEAR_CHAN_FRAMES_DISC_INVALID_ADDR

Definition Number of frames discarded received on the Bearer Channel because of invalidaddress format.

Trigger Condition Whenever a frame received on the Bearer Channel is discarded due to invalidaddress format.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 713 / 1256


24.1.2.2 PVC

24.1.2.2.1 N/A

24.1.2.2.1.1 P6a - NB_PVC_FRAMES_DISC_7_CONSEC_1

Long Name NB_PVC_FRAMES_DISC_7_CONSEC_1

Definition Number of frames discarded received on the PVC because of seven consecutivebits set to "1".

Trigger Condition Whenever a frame received on the PVC is discarded due to seven bits set to "1".


Sub Domain 2 PVC

Sub Domain 3 N/A



714 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.2.2.1.2 P6b - NB_PVC_FRAMES_DISC_ZERO_INSER

Long Name NB_PVC_FRAMES_DISC_ZERO_INSER

Definition Number of frames discarded received on the PVC because of a non integralnumber of octetes (zero insertion failure).

Trigger Condition Whenever a frame received on the PVC is discarded due to a non integral numberof octets (zero insertion failure).


Sub Domain 2 PVC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 715 / 1256


24.1.2.2.1.3 P6c - NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE

Long Name NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE

Definition Number of frames discarded received on the PVC because of length greater thanthe maximum allowed (FR-INFO-SIZE.Max).

Trigger Condition Whenever a frame received on the PVC is discarded due to the length greater thanthe maximum allowed.


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


716 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.2.2.1.4 P6d - NB_PVC_FRAMES_DISC_LENGTH_TOO_SHORT

Long Name NB_PVC_FRAMES_DISC_LENGTH_TOO_SHORT

Definition Number of frames discarded received on the PVC because of length shorter thanthe minimum allowed (FR-INFO-SIZE.Min).

Trigger Condition Whenever a frame received on the PVC is discarded due to the length lower thanthe minimum allowed.


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


3BK 21255 AAAA PCZZA Ed.07 717 / 1256


24.1.3 Radio interface

24.1.3.1 Cell reselections

24.1.3.1.1 NACC

24.1.3.1.1.1 P212 - TIME_SOURCE_NACC_CELL_RESEL

Long Name TIME_SOURCE_NACC_CELL_RESEL

Definition Cumulated time of the successful Network Assisted cell reselection duration inNC0 mode.

Trigger Condition Within the granularity period, the MFS cumulates the duration of each successfuloutgoing NACC cell reselections triggered by the BSS in the source cell.Theduration of a NACC cell reselection is measured in the source cell between thestart of emission of Packet Neighbour Cell Data messages (following the receptionof the Packet Cell Change Notification message) and the reception of the Flush-LLmessage. The source cell is the cell where the cell reselections are outgoing.

Sub Domain 1 Radio interface

Sub Domain 2 Cell reselections

Sub Domain 3 NACC

Measured Object Cell


718 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.1.1.2 P213 - NB_SOURCE_NACC_CELL_RESEL

Long Name NB_SOURCE_NACC_CELL_RESEL

Definition Number of successful Network Assisted cell reselection in the source cell in NC0mode.

Trigger Condition Within the granularity period, the MFS counts the number of each successfuloutgoing NACC cell reselections triggered by the BSS in the source cell.A NACCcell reselection is successful when in the source cell after the start of emissionof Packet Neighbour Cell Data messages (following the reception of the PacketCell Change Notification message) , the reception of the Flush-LL message isreceived. The source cell is the cell where the cell reselections are outgoing.



Sub Domain 3 NACC



3BK 21255 AAAA PCZZA Ed.07 719 / 1256


24.1.3.1.1.3 P458 - NB_NEIGH_PSI_PROC

Long Name NB_NEIGH_PSI_PROC

Definition Nb of times the procedure of broadcast of neighbour (P)SI messages is invoked

Trigger Condition In NC0 mode : Whenever neighbour (P)SI messages are sent by RRM to RLCfollowing a reception of PACKET CELL CHANGE



Sub Domain 3 NACC



720 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.1.1.4 P460b - MAX_SOURCE_NACC_CELL_RESEL_TIME

Long Name MAX_SOURCE_NACC_CELL_RESEL_TIME

Definition Maximum Network Assisted cell reselection duration in NC0 mode.

Trigger Condition Tide mark recording the maximum value of Counter P212.



Sub Domain 3 NACC



3BK 21255 AAAA PCZZA Ed.07 721 / 1256


24.1.3.1.1.5 P460c - MIN_SOURCE_NACC_CELL_RESEL_TIME

Long Name MIN_SOURCE_NACC_CELL_RESEL_TIME

Definition Minimum Network Assisted cell reselection duration in NC0 mode.

Trigger Condition Tide mark recording the minimum value of Counter P212.



Sub Domain 3 NACC



722 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.1.2 Packet (P)SI status

24.1.3.1.2.1 P456 - NB_PSI_PROC

Long Name NB_PSI_PROC

Definition Number of times the procedure of broadcast of serving cell PSI for Packet PSIStatus or the procedure of sending of Packet Serving Cell Data for Packet SIStatus is invoked.

Trigger Condition Whenever RRM sends a request to PTU to send serving cell (P)SI to the MS forPacket (P)SI Status procedure.The primitive used as trigger is PCC-PSCD-REQ.



Sub Domain 3 Packet (P)SI status



3BK 21255 AAAA PCZZA Ed.07 723 / 1256


24.1.3.2 Cell reselections in NC0

24.1.3.2.1 N/A

24.1.3.2.1.1 P397 - NB_FLUSH_MESSAGES

Long Name NB_FLUSH_MESSAGES

Definition Number of successful NC0 or NC2 cell reselections for MS in GMM Ready state(either in packet idle mode or packet transfer mode)

Trigger Condition Whenever the MFS receives a FLUSH-LL PDU from the SGSN.


Sub Domain 2 Cell reselections in NC0

Sub Domain 3 N/A


External Comment Note that NC2 cell reselections can only be triggered if the MS is in packet transfermode

724 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.2.1.2 P436 - NB_NC0_CELL_RESEL_Mstrans

Long Name NB_NC0_CELL_RESEL_Mstrans

Definition Number of successful NC0 cell reselections (for MS in packet transfer mode)

Trigger Condition This counter is incremented upon receipt of a Flush-LL message corresponding toa NC0 cell reselection triggered while the MS was in packet transfer mode in theold cell in the previous T_WAIT_FLUSH seconds.The counter is then incrementedfor MS operating in NC0 mode whenever one of the following events occurs:i)a Flush-LL message is received from the SGSN and this Flush-LL messageconcerns a DL or UL TBF which is(are) still on-going(s),ii) a Flush-LL messageis received from the SGSN and this Flush-LL message concerns a DL or ULTBF which has(have) been abnormally released in the previous T_WAIT_FLUSHseconds.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 725 / 1256


24.1.3.3 Cell reselections in NC2

24.1.3.3.1 N/A

24.1.3.3.1.1 P209 - TIME_SOURCE_NC2_CELL_RESEL

Long Name TIME_SOURCE_NC2_CELL_RESEL

Definition Cumulated time duration of successful outgoing NC2 cell reselections (measuredin the source cell).

Trigger Condition Within the granularity period, the MFS cumulates the duration of each successfuloutgoing NC2 cell reselections triggered by the BSS in the source cell.Theduration of a NC2 cell reselection is measured in the source cell between theacknowledgement of the Packet Cell Change Order message and the reception ofthe Flush-LL message. The source cell is the cell where the NC cell reselectionsare outgoing.



Sub Domain 3 N/A


External Comment The MFS can measure the duration of a NC cell reselection provided that theFlush-LL message is received while the timer T_WAIT_FLUSH is still running. Thismeans that NC cell reselection duration longer than the timer T_WAIT_FLUSHcannot be measured by this counter.

726 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.2 P210 - TIME_TARGET_NC2_CELL_RESEL

Long Name TIME_TARGET_NC2_CELL_RESEL

Definition Cumulated time duration of successful incoming intra-RA intra-MFS NC2 cellreselections (measured in the target cell).

Trigger Condition Within the granularity period, the MFS cumulates the duration of the successfulincoming intra-RA intra-MFS NC2 cell reselections triggered by the BSS in thesource cell.The duration of a NC2 cell reselection is measured in the source cellsbetween the acknowledgement of the Packet Cell Change Order message andthe reception of the Flush-LL message. These measures are forwarded to thetarget cell in the intra-MFS TLLI Rerouting Confirm message and then cumulatedin the target cell.The source cells are the cells where the NC cell reselectionsare outgoing, whereas the target cell is the cell where the NC cell reselectionsare incoming.



Sub Domain 3 N/A


External Comment 1) Only NC2 cell reselections involving a source cell which belongs to the samerouting area and same MFS as the target cell are taken into account in thisaverage.2) The MFS can measure the duration of a NC cell reselection providedthat the Flush-LL message is received while the timer T_WAIT_FLUSH is stillrunning. This means that NC cell reselection duration longer than the timerT_WAIT_FLUSH cannot be measured by this counter.

3BK 21255 AAAA PCZZA Ed.07 727 / 1256


24.1.3.3.1.3 P211 - NB_TARGET_NC2_CELL_RESEL

Long Name NB_TARGET_NC2_CELL_RESEL

Definition Number of successful incoming intra-RA intra-MFS NC2 cell reselections(measured in the target cell).

Trigger Condition Within the granularity period, the MFS counts the number of each successfuloutgoing NC2 cell reselections triggered by the BSS in the source cell.A NC2 cellreselection is successful when in the source cells after the acknowledgement ofthe Packet Cell Change Order message is received , the Flush-LL message isreceived.These measures are forwarded to the target cell in the intra-MFS TLLIRerouting Confirm message and then cumulated in the target cell.The source cellsare the cells where the NC cell reselections are outgoing, whereas the target cellis the cell where the NC cell reselections are incoming.



Sub Domain 3 N/A


External Comment 1) Only NC2 cell reselections involving a source cell which belongs to the samerouting area and same MFS as the target cell are taken into account in thisaverage.2) The MFS can measure the duration of a NC cell reselection providedthat the Flush-LL message is received while the timer T_WAIT_FLUSH is stillrunning. This means that NC cell reselection duration longer than the timerT_WAIT_FLUSH cannot be measured by this counter.

728 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.4 P221 - NB_PCCO_ACK_UL_NC2_CELL_RESEL

Long Name NB_PCCO_ACK_UL_NC2_CELL_RESEL

Definition Number of Packet Cell Change Order acknowledged by the MS while in ULtransfert.

Trigger Condition The counter is incremented each time a Packet Control Acknowledgement isreceived in acknowledgement of a Packet Cell Change Order while in UL transfert.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 729 / 1256


24.1.3.3.1.5 P222 - NB_PCCO_ACK_DL_NC2_CELL_RESEL

Long Name NB_PCCO_ACK_DL_NC2_CELL_RESEL

Definition Number of Packet Cell Change Order acknowledged by the MS while in DLtransfert.

Trigger Condition The counter is incremented each time a Packet Control Acknowledgement isreceived in acknowledgement of a Packet Cell Change Order while in DL transfert.



Sub Domain 3 N/A



730 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.6 P223 - NB_PCCO_NC2_CELL_RESEL_DL_TBF

Long Name NB_PCCO_NC2_CELL_RESEL_DL_TBF

Definition Number of Packet Cell Change Order messages sent while in DL transfer.

Trigger Condition This counter is incremented whenever the MFS sends a Packet Cell Change Ordermessage to the MS while it has an ongoing DL TBF.



Sub Domain 3 N/A


External Comment If a PCCO is sent for a MS supporting a DL TBF and an UL TBF, then both P223and P226 are incremented.

3BK 21255 AAAA PCZZA Ed.07 731 / 1256


24.1.3.3.1.7 P224 - NB_FLUSH_NC2_CELL_RESEL_DL_TBF

Long Name NB_FLUSH_NC2_CELL_RESEL_DL_TBF

Definition Number of FLUSH-LL PDU received after a Packet Cell Change Order has beensent to the MS while in DL transfer.

Trigger Condition Whenever the MFS receives a FLUSH-LL PDU from the SGSN after a PacketCell Change Order message has been sent to the MS while it has an ongoing inDL TBF .



Sub Domain 3 N/A


External Comment If a FLUSH is received for a MS supporting a DL TBF and an UL TBF, then bothP224 and P227 are incremented.

732 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.8 P225 - NB_PCCF_NC2_CELL_RESEL_DL_TBF

Long Name NB_PCCF_NC2_CELL_RESEL_DL_TBF

Definition Number of Packet Cell Change Failure received from the MS after a Packet CellChange Order has been sent to the MS while in DL transfer.

Trigger Condition Whenever the MFS receives a Packet Cell Change Failure message from the MSafter a Packet Cell Change Order message has been sent to the MS while it hasan ongoing DL TBF .



Sub Domain 3 N/A


External Comment If a PCCF is received for a MS supporting a DL TBF and an UL TBF, then bothP225 and P228 are incremented

3BK 21255 AAAA PCZZA Ed.07 733 / 1256


24.1.3.3.1.9 P226 - NB_PCCO_NC2_CELL_RESEL_UL_TBF

Long Name NB_PCCO_NC2_CELL_RESEL_UL_TBF

Definition Number of Packet Cell Change Order messages sent while in UL transfer.

Trigger Condition This counter is incremented whenever the MFS sends a Packet Cell Change Ordermessage to the MS while it has an ongoing UL TBF.



Sub Domain 3 N/A


External Comment If a PCCO is sent for a MS supporting a DL TBF and an UL TBF, then both P223and P226 are incremented.

734 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.10 P227 - NB_FLUSH_NC2_CELL_RESEL_UL_TBF

Long Name NB_FLUSH_NC2_CELL_RESEL_UL_TBF

Definition Number of FLUSH-LL PDU received after a Packet Cell Change Order has beensent to the MS while in UL transfer.

Trigger Condition Whenever the MFS receives a FLUSH-LL PDU from the SGSN after a Packet CellChange Order message has been sent to the MS while it has an ongoing UL TBF .



Sub Domain 3 N/A


External Comment If a FLUSH is received for a MS supporting a DL TBF and an UL TBF, then bothP224 and P227 are incremented.

3BK 21255 AAAA PCZZA Ed.07 735 / 1256


24.1.3.3.1.11 P228 - NB_PCCF_NC2_CELL_RESEL_UL_TBF

Long Name NB_PCCF_NC2_CELL_RESEL_UL_TBF

Definition Number of Packet Cell Change Failure received from the MS after a Packet CellChange Order has been sent to the MS while in UL transfer.

Trigger Condition Whenever the MFS receives a Packet Cell Change Failure message from the MSafter a Packet Cell Change Order message has been sent to the MS while it hasan ongoing UL TBF .



Sub Domain 3 N/A


External Comment If a PCCF is received for a MS supporting a DL TBF and an UL TBF, then bothP225 and P228 are incremented.

736 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.12 P431b - MAX_SOURCE_NC2_CELL_RESEL_TIME

Long Name MAX_SOURCE_NC2_CELL_RESEL_TIME

Definition Maximum duration of successful outgoing NC2 cell reselections (measured inthe source cell)

Trigger Condition Tide mark recording the maximum value of Counter P209



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 737 / 1256


24.1.3.3.1.13 P431c - MIN_SOURCE_NC2_CELL_RESEL_TIME

Long Name MIN_SOURCE_NC2_CELL_RESEL_TIME

Definition Minimum duration of successful outgoing NC2 cell reselections (measured inthe source cell)

Trigger Condition Tide mark recording the minimum value of Counter P209



Sub Domain 3 N/A



738 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.14 P432b - MAX_TARGET_NC2_CELL_RESEL_TIME

Long Name MAX_TARGET_NC2_CELL_RESEL_TIME

Definition Maximum duration of successful incoming intra-RA intra-MFS NC2 cellreselections (measured in the target cell).

Trigger Condition Tide mark recording the maximum value of Counter P210



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 739 / 1256


24.1.3.3.1.15 P432c - MIN_TARGET_NC2_CELL_RESEL_TIME

Long Name MIN_TARGET_NC2_CELL_RESEL_TIME

Definition Minimum duration of successful incoming intra-RA intra-MFS NC2 cell reselections(measured in the target cell).

Trigger Condition Tide mark recording the minimum value of Counter P210



Sub Domain 3 N/A



740 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.16 P433a - NB_NC2_CELL_RESEL_REQ_PT1

Long Name NB_NC2_CELL_RESEL_REQ_PT1

Definition Number of NC2 cell reselection requests for a MS in packet transfer mode dueto a "too low downlink received signal" (Cause PT1)

Trigger Condition This counter is incremented whenever the RRM layer sends to the MS a PacketCell Change Order message for a NC2 cell reselection triggered due a "too lowdownlink received signal" (Cause PT1).The repetitions of the Packet Cell ChangeOrder message for a given NC2 cell reselection alarm are not counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 741 / 1256


24.1.3.3.1.17 P433b - NB_NC2_CELL_RESEL_REQ_PT2


Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due toa "detection of a better neighbour cell" (Cause PT2)

Trigger Condition This counter is incremented whenever the RRM layer sends to the MS a PacketCell Change Order message for a NC2 cell reselection triggered due the "detectionof a better neighbour cell" (Cause PT2).The repetitions of the Packet Cell ChangeOrder message for a given NC2 cell reselection alarm are not counted.



Sub Domain 3 N/A



742 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.18 P433c - NB_NC2_CELL_RESEL_REQ_PT3


Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due toa "too bad downlink radio quality" (Cause PT3)

Trigger Condition This counter is incremented whenever the RRM layer sends to the MS a PacketCell Change Order message for a NC2 cell reselection triggered due a "too baddownlink radio quality" (Cause PT3).The repetitions of the Packet Cell ChangeOrder message for a given NC2 cell reselection alarm are not counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 743 / 1256


24.1.3.3.1.19 P433d - NB_NC2_CELL_RESEL_REQ_PT4


Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due toa "too bad uplink radio quality" (Cause PT4)

Trigger Condition This counter is incremented whenever the RRM layer sends to the MS a PacketCell Change Order message for a NC2 cell reselection triggered due a "too baduplink radio quality" (Cause PT4).The repetitions of the Packet Cell Change Ordermessage for a given NC2 cell reselection alarm are not counted.



Sub Domain 3 N/A



744 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.20 P435a - NB_NC2_CELL_RESEL_SUCC_PT1

Long Name NB_NC2_CELL_RESEL_SUCC_PT1

Definition Number of NC2 cell reselection successes for a MS in packet transfer mode dueto a "too low downlink received signal" (Cause PT1)

Trigger Condition This counter is incremented upon receipt of a Flush-LL message correspondingto a NC2 cell reselection triggered due to a "too low downlink received signal"(Cause PT1).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 745 / 1256


24.1.3.3.1.21 P435b - NB_NC2_CELL_RESEL_SUCC_PT2


Definition Number of NC2 cell reselection successes for a MS in packet transfer mode dueto a "detection of a better neighbour cell" (Cause PT2)

Trigger Condition This counter is incremented upon receipt of a Flush-LL message correspondingto a NC2 cell reselection triggered due to a "detection of a better neighbour cell"(Cause PT2).



Sub Domain 3 N/A



746 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.22 P435c - NB_NC2_CELL_RESEL_SUCC_PT3


Definition Number of NC2 cell reselection successes for a MS in packet transfer mode dueto a "too bad downlink radio quality" (Cause PT3)

Trigger Condition This counter is incremented upon receipt of a Flush-LL message correspondingto a NC2 cell reselection triggered due to a "too bad downlink radio quality"(Cause PT3).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 747 / 1256


24.1.3.3.1.23 P435d - NB_NC2_CELL_RESEL_SUCC_PT4


Definition Number of NC2 cell reselection successes for a MS in packet transfer mode dueto a "too bad uplink radio quality" (Cause PT4)

Trigger Condition This counter is incremented upon receipt of a Flush-LL message correspondingto a NC2 cell reselection triggered due to a "too bad uplink radio quality" (CausePT4).



Sub Domain 3 N/A



748 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.24 P437a - NB_NC2_CELL_RESEL_FAIL_REJECT_CELL

Long Name NB_NC2_CELL_RESEL_FAIL_REJECT_CELL

Definition Number of NC2 cell reselection failures reported by the MS which leads to rejectthe target cell for a while.

Trigger Condition This counter is incremented upon receipt of a 3GPP TS 04.60 Packet Cell ChangeFailure message with Causes "Frequency not implemented", "No response ontarget cell", or "Immediate Assign Reject or Packet Access Reject on target cell".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 749 / 1256


24.1.3.3.1.25 P437b - NB_NC2_CELL_RESEL_FAIL_NO_REJECT_CELL

Long Name NB_NC2_CELL_RESEL_FAIL_NO_REJECT_CELL

Definition Number of NC2 cell reselection failures reported by the MS which does not lead toreject the target cell for a while.

Trigger Condition This counter is incremented upon receipt of a 3GPP TS 04.60 Packet Cell ChangeFailure message with Causes "On going CS connection", "MS in GMM Standbystate", or "Forced to the Standby state".



Sub Domain 3 N/A



750 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.3.1.26 P464 - NB_NC2_CELL_RESEL_FAIL_LOAD

Long Name NB_NC2_CELL_RESEL_FAIL_LOAD

Definition Number of NC2 cell reselection failures reported by the MS due to load (cause :"immediate assign reject" or "packet access reject on target cell")

Trigger Condition Whenever a Packet Cell Change Failure is received with a cause "immediateassign reject" or "packet access rejact on target cell".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 751 / 1256


24.1.3.4 DL TBF establishments

24.1.3.4.1 N/A

24.1.3.4.1.1 P105c - NB_DL_TBF_EST_FAIL_GPU_CONG

Long Name NB_DL_TBF_EST_FAIL_GPU_CONG

Definition Number of DL TBF establishment failures due to GPU congestion.Note: Thiscounter applies to GPRS and EGPRS MS.

Trigger Condition When a DL TBF cannot be established, due to GPU congestion (cause of thefailure of the last attempt before PDU life time expiry). GPU congestion meansthat the maximum capacity of at least one DSP on the GPU is reached in termsof resources GCH and/or PDCH.Generally, for all counters related to TBFestablishment failures, only the last reported failure cause is taken into account.


Sub Domain 2 DL TBF establishments

Sub Domain 3 N/A



752 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.2 P105e - NB_DL_TBF_EST_FAIL_CPU_GPU

Long Name NB_DL_TBF_EST_FAIL_CPU_GPU

Definition Number of DL TBF establishment failures due to CPU processing power limitationsof the GPU.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition Whenever a DL TBF cannot be established due to CPU processing powerlimitations of the GPU.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 753 / 1256


24.1.3.4.1.3 P105g - NB_DL_TBF_EST_FAIL_CONG_ATER

Long Name NB_DL_TBF_EST_FAIL_CONG_ATER

Definition Number of DL TBF establishment failures due to a lack of Ater resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a DL TBF establishment fails due to a lackof Ater resources.A lack of Ater resources occurs when there is not enough GCHto serve the DL TBF request.For BTS evolium :the number of GCH that can beestablished and/or redistributed is < Nb_GCH_FOR_TBF_ESTAB and the numberof free Ater nibbles is < Nb_GCH_FOR_TBF_ESTAB.For DRFU BTS :Lack of freeAter nibbles to serve the GCHs.The counter is incremented at the expiry of thePDU lifetime when the last attempt fails to establish the DL TBF due to a lack oftransmission resources.



Sub Domain 3 N/A



754 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.4 P105i - NB_DL_TBF_EST_FAIL_CONG_ABIS

Long Name NB_DL_TBF_EST_FAIL_CONG_ABIS

Definition Number of DL TBF establishment failures due to a lack of Abis resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a DL TBF establishment fails due to a lackof Abis resources.A lack of Abis transmission resources occurs when there is notenough Abis nibbles to serve the DL TBF request.For BTS evolium :the number ofGCH that can be established and or redistributed is < Nb_GCH_FOR_TBF_ESTABand the number of free Abis nibbles is < Nb_GCH_FOR_TBF_ESTAB.For DRFUBTS :The counter is always 0.The counter is incremented at the expiry of thePDU lifetime when the last attempt fails to establish the DL TBF due to a lack oftransmission resources.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 755 / 1256


24.1.3.4.1.5 P105k - NB_DL_TBF_EST_FAIL_TOO_MANY_TBF

Long Name NB_DL_TBF_EST_FAIL_TOO_MANY_TBF

Definition Number of DL TBF establishment failures due to:- a too low number of GCH toguarantee a minimum throughput for the DL TBF.- This may happen when thenumber of TBFs is too high compared to the number of available GCHs.- or theMAX_TBF_TRX_DL constraint.Note: This counter applies to GPRS and EGPRSMS.

Trigger Condition The counter is incremented whenever a DL TBF establishment fails due to:1)a too low number of available GCH.For BTS evolium :The number of GCHavailable to serve the DL TBF is < Min_Nb_GCH.For DRFU BTS :Counter notincremented (=0).2) or the MAX_TBF_TRX_DL constraint:For BTS evolium :TheMAX_TBF_TRX_DL limit is reached on all the TRXs available for PS traffic in thecell.For DRFU BTS :Counter not incremented (=0).Note : This counter is not beincremented for RT PFCs.The counter is incremented at the expiry of the PDUlifetime when the last attempt to establish the DL TBF has failed due to too lownumber of available GCH (too many TBF on the TRX compared to the number ofavailable GCH) or due to the MAX_TBF_TRX_DL constraint.



Sub Domain 3 N/A



756 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.6 P14 - NB_DL_TBF_EST_FAIL_CONG

Long Name NB_DL_TBF_EST_FAIL_CONG

Definition Number of DL TBF establishment failures due to a lack of radio resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a DL TBF establishment fails due to a lackof radio resources. A lack of radio resource occurs:i) if the maximum number ofMSs per slave PDCH in downlink is reached for all the slave PDCHs allocated tothe MFS, orii) if there is no TAI or TFI left in the MFS.oriii) if no PDCH are grantedto MFS due to a CS congestion and max_pdch_high_load is null.The counteris incremented at the expiry of the PDU lifetime when the last attempt fails toestablish the DL TBF due to a lack of radio resources.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 757 / 1256


24.1.3.4.1.7 P15 - NB_DL_TBF_EST_FAIL_RADIO_PB

Long Name NB_DL_TBF_EST_FAIL_RADIO_PB

Definition Number of DL TBF establishment failures due to radio problem.The cell operationalstate is "enabled" and the GCHs carrying the TBF are available for traffic.

Trigger Condition Whenever the 04.60 Packet CONTROL ACKNOWLEDGMENT message awaitedon PACCH from the mobile during a DL TBF establishment procedure is notreceived on the scheduled block. The DL TBF establishment procedure maybe concurrent to an UL TBF reallocation procedure (trigger T2).Generally, forall counters related to TBF establishment failures, only the last reported failurecause is taken into account. That is the counter is incremented only afterMax_retrans_DL attempts to establish a DL TBF and no acknowledgement isreceived from the Mobile Station. If the acknowledgement is received beforeMax_retrans_DL retransmissions of the assignment message, then the counter isnot incremented at all.



Sub Domain 3 N/A



758 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.8 P203 - NB_DL_TBF_EST_FAIL_PTU_DSP_LOAD

Long Name NB_DL_TBF_EST_FAIL_PTU_DSP_LOAD

Definition Number of DL TBF establishment failures due to DSPs that are in CPU load /overload state.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented each time a DL TBF establishment fails due to theinternal cause CPU_DSP_LOAD.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 759 / 1256


24.1.3.4.1.9 P422 -NB_DL_TBF_TRANSFER_RESUMPTION_IN_DELAYED_REL_STATE

Long Name NB_DL_TBF_TRANSFER_RESUMPTION_IN_DELAYED_REL_STATE

Definition Number of DL TBF transfer resumptions in delayed release state.

Trigger Condition The counter is incremented each time a DL TBF state changes from "delayedrelease" to "active". It corresponds to the TBF becoming active again after acertain duration of delayed release state. This counter therefore provides thenumber of DL TBF establishments which have been avoided by the delayeddownlink TBF release feature.



Sub Domain 3 N/A



760 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.10 P65 - NB_DL_TBF_EST_FAIL_GB_PB

Long Name NB_DL_TBF_EST_FAIL_GB_PB

Definition Number of DL TBF establishment failures due to the unavailability of the BVC (Gbinterface problem) associated with the cell.

Trigger Condition Whenever the BVC associated with the cell is unavailable (which implies: celloperational state "disabled"), the counter is incremented with the number of DLTBF in establishment phase. All pending LLC PDUs in the MFS are discarded forthe cell.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 761 / 1256


24.1.3.4.1.11 P90a - NB_DL_TBF_EST_SUCC_MS_Idle_DRX_MPDCH

Long Name NB_DL_TBF_EST_SUCC_MS_Idle_DRX_MPDCH

Definition Number of DL TBF successfully established on PCCCH when the MS is in packetidle mode and DRX mode.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBFestablishment performed on PCCCH for a MS in packet idle mode and DRX mode.



Sub Domain 3 N/A



762 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.12 P90b - NB_DL_TBF_EST_SUCC_MS_Transfer_UL

Long Name NB_DL_TBF_EST_SUCC_MS_Transfer_UL

Definition Number of DL TBF successfully established when MS is in uplink packet transfermode.Note: This counter applies to GPRS and EGPRS MS

Trigger Condition This counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBFestablishment performed on PACCH for a MS in packet transfer mode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 763 / 1256


24.1.3.4.1.13 P90c - NB_DL_TBF_EST_SUCC_MS_IDLE_DRX_NO_MPDCH

Long Name NB_DL_TBF_EST_SUCC_MS_IDLE_DRX_NO_MPDCH

Definition Number of DL TBF successfully established on CCCH when the MS is in packetidle mode and DRX mode.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBFestablishment performed on CCCH for a MS in packet idle mode and DRX mode.



Sub Domain 3 N/A



764 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.14 P90d - NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH

Long Name NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH

Definition Number of DL TBF successfully established on PCCCH when the MS is in packetidle mode and non-DRX mode.Note: This counter applies to GPRS and EGPRSMS.

Trigger Condition This counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DLTBF establishment performed on PCCCH for a MS in packet idle mode andnon-DRX mode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 765 / 1256


24.1.3.4.1.15 P90e - NB_DL_TBF_EST_SUCC_T3192

Long Name NB_DL_TBF_EST_SUCC_T3192

Definition Number of DL TBF successfully established on PACCH while the timer T3192 isrunning at BSS side.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBFestablishment triggered while the timer T3192n was running.



Sub Domain 3 N/A



766 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.16 P90f - NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH

Long Name NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH

Definition Number of DL TBF successfully established on CCCH when the MS is in packetidle mode and non-DRX mode.Note: This counter applies to GPRS and EGPRSMS.

Trigger Condition This counter is incremented whenever a PACKET CONTROLACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBFestablishment performed on CCCH for a MS in packet idle mode and non-DRXmode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 767 / 1256


24.1.3.4.1.17 P91a - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_MPDCH

Long Name NB_DL_TBF_EST_REQ_MS_IDLE_DRX_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle modeand DRX mode in case there is at least one PCCCH established in the cell.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever the MFS receives a DL LLC PDU for aMS in packet idle mode and in DRX mode in case there is at least one PCCCHestablished in the cell.Generally, all counters related to TBF establishmentrequests only take into account the first attempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



768 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.18 P91b - NB_DL_TBF_EST_REQ_MS_Transfer_UL

Long Name NB_DL_TBF_EST_REQ_MS_Transfer_UL

Definition Number of DL TBF establishment requests when MS is in uplink packet transfermode.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented each time a DL LLC PDU is received for an MS inuplink packet transfer mode.Note that the counter is incremented whether therequest is served with a (EGPRS) PACKET DOWNLINK ASSIGNMENT or aPACKET TIMESLOT RECONFIGURE (which means that the UL TBF resourcesare re-assigned upon concurrent DL TBF establishment).Generally, all countersrelated to TBF establishment requests only take into account the first attempt,i.e. no repetitions are counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 769 / 1256


24.1.3.4.1.19 P91c - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH

Long Name NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle modeand DRX mode in case there is no PCCCH established in the cell.Note: Thiscounter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever the MFS receives a DL LLC PDU for a MSin packet idle mode and in DRX mode in case there is no PCCCH established inthe cell.Generally, all counters related to TBF establishment requests only takeinto account the first attempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



770 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.20 P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH

Long Name NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle modeand non-DRX mode in case there is at least one PCCCH established in thecell.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever the MFS receives a DL LLC PDU for a MSin packet idle mode and in non-DRX mode in case there is at least one PCCCHestablished in the cell.Generally, all counters related to TBF establishmentrequests only take into account the first attempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 771 / 1256


24.1.3.4.1.21 P91e - NB_DL_TBF_EST_REQ_T3192

Long Name NB_DL_TBF_EST_REQ_T3192

Definition Number of DL TBF establishment requests received while the timer T3192 isrunning at BSS side.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a DL LLC PDU is received while the timerT3192n is running.Generally, all counters related to TBF establishment requestsonly take into account the first attempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



772 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.4.1.22 P91f - NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH

Long Name NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle modeand non-DRX mode , in case there is no PCCCH established in the cell.Note: Thiscounter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented whenever the MFS receives a DL LLC PDU for a MSin packet idle mode and in non-DRX mode in case there is no PCCCH establishedin the cell.Generally, all counters related to TBF establishment requests only takeinto account the first attempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 773 / 1256


24.1.3.5 DL TBF re-allocations

24.1.3.5.1 T1

24.1.3.5.1.1 P403a - NB_DL_RES_REALLOC_REQ_T1

Long Name NB_DL_RES_REALLOC_REQ_T1

Definition Number of downlink TBFs for which the corresponding Mobile Station has at leastone of its TBFs impacted by a CS pre-emption process over the granularity period.Resource reallocation will then be called for the TBFs of those Mobile Stations(thanks to trigger T1).

Trigger Condition The counter is incremented by one each time a downlink TBF is impacted bya CS pre-emption process. Two cases are possible :- a downlink TBF has itsPACCH impacted by a soft PDCH pre-emption,- the maximum allowed (M)CS ofa downlink TBF will no longer be possible to serve because of an M-EGCH linksize reduction due to a soft PDCH pre-emption. The M-EGCH link to consideris the one of the TRX currently supporting the downlink TBF. That case is onlyvalid for Evolium BTSs and can only occur in case the basic Abis nibbles ofsome of the soft-preempted PDCHs are currently being used by GCHs withinthe considered M-EGCH link. Example : if a downlink EGPRS TBF has MCS-9as its maximum allowed (M)CS and is established on a TRX whose M-EGCHlink owns 5 GCHs, then if the CS preemption process leads to an M-EGCH linkhaving only 4 GCHs left (because one of the GCHs of the M-EGCH link is usinga basic Abis nibble mapped to a pre-empted PDCH), then the downlink TBF willbe impacted, and the counter incremented.The counter is also incremented byone each time a downlink TBF has a concurrent uplink TBF impacted by the CSpreemption process (the same conditions as the above ones apply for the uplinkdirection), in case the downlink TBF was not impacted.In both cases, the MFSwill try to reallocate the resources of the MS, which will require reallocating theTBFs in one or in both directions.


Sub Domain 2 DL TBF re-allocations

Sub Domain 3 T1



774 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.1.2 P405a - NB_DL_RES_REALLOC_SUCC_T1

Long Name NB_DL_RES_REALLOC_SUCC_T1

Definition Number of resource reallocation attempts that lead to reallocating successfully adownlink TBF (due to trigger T1).

Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for that downlink TBF due to T1. If the PACKET CONTROLACKNOWLEDGEMENT acknowledges reallocation of both an uplink and adownlink TBF, this counter shall be incremented as well as P406a.If after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T1, only the resources of the uplink TBF need to be reallocated,the procedure shall be considered successful for the downlink TBF, irrespectiveof the reallocation protocol outcome. Indeed, even if the reallocation protocolfails for the uplink TBF, the downlink TBF will not be released and therefore thiscan be considered as a success. This is another trigger for incrementing thiscounter. This is required since P403a has been incremented.Similarly, if after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T1, there is a preparation failure but the PACCH of the downlinkTBF is not impacted by soft PDCH pre-emption, then the downlink TBF will remainalive and this counter shall be incremented.The counter can be used to computethe success rate of the reallocation execution phase.Note: this counter takes intoaccount also the successful T1 reallocations where the MAX_(M)CS of a DL TBFis decreased without any change of its radio allocation.



Sub Domain 3 T1



3BK 21255 AAAA PCZZA Ed.07 775 / 1256


24.1.3.5.1.3 P407a - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T1

Long Name NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T1

Definition Number of resource reallocation attempts that lead to reallocating a downlinkTBF but the procedure failed due to radio problems and the TBF was released(due to trigger T1).

Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T1 for a downlink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocationprotocol was attempted but failed had two TBFs and both were being reallocated,then both counters P407a and P408a shall be incremented.



Sub Domain 3 T1



776 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.1.4 P423a - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1

Long Name NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1

Definition Number of attempts for downlink TBFs impacted by a CS pre-emption process, T1resource reallocation has been attempted but no candidate allocation could befound. The TBF could therefore not be reallocated.

Trigger Condition The counter is incremented each time a downlink TBF is impacted by a CSpre-emption process , the resource reallocation algorithm is run but no candidateallocation can be found for the downlink TBF. As such, it corresponds to a resourcereallocation preparation failure.



Sub Domain 3 T1



3BK 21255 AAAA PCZZA Ed.07 777 / 1256


24.1.3.5.1.5 P425a - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1

Long Name NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1

Definition Number of downlink TBFs for which the resource reallocation protocol is runningfollowing T1 and an external TBF release request is received which forces tostop the on-going resource reallocation (FLUSH-LL from the SGSN or GPRSSUSPENSION REQUEST from the BSC).

Trigger Condition The counter is incremented each time the resources of a downlink TBF arebeing reallocated (ie either a PACKET DOWNLINK ASSIGNMENT or a PACKETTIMESLOT RECONFIGURE message has been sent to the MS to reallocate itsdownlink resources) and:- a FLUSH-LL is received from the SGSN, or- a GPRSSUSPENSION REQUEST is received from the BSCfor that Mobile Station beforethe PACKET CONTROL ACKNOWLEDGEMENT is received.



Sub Domain 3 T1



778 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.2 T2

24.1.3.5.2.1 P403b - NB_DL_RES_REALLOC_REQ_T2


Definition Number of downlink TBFs which are candidate for resource reallocation uponconcurrent uplink TBF establishment.

Trigger Condition The counter is incremented by one each time a concurrent uplink TBFestablishment request is received and the downlink TBF is candidate for resourcereallocation.



Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 779 / 1256


24.1.3.5.2.2 P405b - NB_DL_RES_REALLOC_SUCC_T2



Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for that TBF due to T2, i.e. due to the establishment of aconcurrent uplink TBF. Note that this counter shall be incremented only once evenif two TBF establishments are actually acknowledged.The counter can be used tocompute the success rate of the reallocation execution phase.



Sub Domain 3 T2



780 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.2.3 P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2



Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T2 for a downlink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS.Note : because the corresponding uplink TBFcould not be established too, then P28 is also incremented.



Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 781 / 1256


24.1.3.5.2.4 P423b - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2


Definition Number of attempts for downlink TBFs which were candidate for T2 resourcereallocation upon concurrent uplink TBF establishment but for which no bettercandidate allocation could be found. The downlink TBFs were therefore notreallocated.

Trigger Condition Upon concurrent uplink TBF establishments, the counter is incremented when:i)The uplink TBF cannot be served because the on-going donwlink TBF cannot bere-allocated and concurrence constraints make the uplink TBF establishmentimpossible on the on-going downlink TBF.



Sub Domain 3 T2



782 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.2.5 P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2






Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 783 / 1256


24.1.3.5.3 T3

24.1.3.5.3.1 P403c - NB_DL_RES_REALLOC_REQ_T3


Definition Number of downlink TBFs for which the corresponding Mobile Station wascandidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry(due to trigger T3). Only candidate MSs for which the resource allocation algorithmwas called are taken into account.

Trigger Condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incrementedby the number of DL TBFs for which the corresponding Mobile Station iscandidate for resource reallocation and for which the resource allocation algorithmwill be run to try and find a better allocation. This means that it is limited toN_MAX_PERIODIC_REALLOC_T3 attempts upon each timer expiry.Note 1: alldownlink TBFs for which the resource allocation algorithm is run have to becounted, even if the corresponding Mobile Station has an uplink-biased transferand therefore the MS is registered in the uplink list.Note 2: in case a givenmobile station has got two TBF(s) on-going and its resources are attempted to bereallocated, then both P403c and P404c shall be incremented.



Sub Domain 3 T3



784 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.3.2 P405c - NB_DL_RES_REALLOC_SUCC_T3



Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for a downlink TBF due to T3. If the PACKET CONTROLACKNOWLEDGEMENT acknowledges reallocation of both an uplink and adownlink TBF, both P405c and P406c shall be incremented.If after the resourcereallocation algorithm is run for a candidate Mobile Station having two TBFsfollowing T3, only the resources of the uplink TBF need to be reallocated, theprocedure shall be considered successful for the downlink TBF, irrespective of thereallocation protocol outcome. Indeed, even if the reallocation protocol fails forthe uplink TBF, the downlink TBF will not be released and therefore this can beconsidered as a success. This is another trigger for incrementing this counter.This is required since P403c has been incremented.The counter can be used tocompute the success rate of the reallocation execution phase.



Sub Domain 3 T3



3BK 21255 AAAA PCZZA Ed.07 785 / 1256


24.1.3.5.3.3 P407c - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3



Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T3 for a downlink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocation wasattempted but failed had two TBFs and both were being reallocated, then bothcounters P407c and P408c shall be incremented.



Sub Domain 3 T3



786 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.3.4 P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3


Definition Number of periodic attempts for downlink TBFs which were candidate for resourcereallocation due to T3 but for which no better candidate allocation could be found.The downlink TBFs were therefore not reallocated.

Trigger Condition The counter is incremented each time a downlink TBF is candidate for resourcereallocation due to T3 but after the radio resource reallocation algorithm is run,it is decided not to change its current allocation. As such, it corresponds to aresource reallocation preparation failure.



Sub Domain 3 T3



3BK 21255 AAAA PCZZA Ed.07 787 / 1256


24.1.3.5.3.5 P425c - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3






Sub Domain 3 T3



788 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.4 T4

24.1.3.5.4.1 P403d - NB_DL_RES_REALLOC_REQ_T4


Definition Number of downlink TBFs for which the corresponding Mobile Station wascandidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry(due to Trigger T4). Only candidate MSs for which the resource allocationalgorithm was called are taken into account.

Trigger Condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incrementedby the number of DL TBFs which are candidate for resource reallocation andfor which the resource allocation algorithm will tend to free EGPRS radioresources.This means that it is limited to N_MAX_PERIODIC_REALLOC_T4attempts upon each timer expiry.Note that in case a given mobile station has gotan UL and DL TBFs on-going and its resources are attempted to be reallocateddue to Trigger T4, then both P403d and P404d shall be incremented.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 789 / 1256


24.1.3.5.4.2 P405d - NB_DL_RES_REALLOC_SUCC_T4


Definition Number of T4 resource reallocation attempts that lead to reallocating successfullya downlink TBF.

Trigger Condition A Packet Control Acknowledgement message is received following a resourcereallocation attempt for a downlink TBF due to Trigger T4.Note that if the PacketControl Acknowledgement message acknowledges reallocation of both an uplinkand a downlink TBF, both P405d and P406d shall be incremented.If after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T4, only the resources of the uplink TBF need to be reallocated,the procedure shall be considered successful for the downlink TBF, irrespective ofthe reallocation protocol outcome. Indeed, even if the reallocation protocol failsfor the uplink TBF, the downlink TBF will not be released and therefore this canbe considered as a success. This is another trigger for incrementing this counter.This is required since P403d has been incremented.



Sub Domain 3 T4


External Comment The counter can be used to compute the success rate of the reallocation executionphase.

790 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.4.3 P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4


Definition Number of T4 resource reallocation attempts that lead to reallocating a downlinkTBF but the procedure failed due to radio problems and the TBF was released.

Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to Trigger T4 for a downlink TBF but it was neverreceived, the TBF is released and this counter is incremented.Assuming that theMS is not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocation wasattempted but failed had two TBFs and both were being reallocated, then bothcounters P407d and P408d shall be incremented.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 791 / 1256


24.1.3.5.4.4 P423d - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4


Definition Number of periodic attempts for downlink TBFs which were candidate for T4resource reallocation but for which no suitable candidate allocation could be found.The downlink TBFs were therefore not re-allocated.

Trigger Condition The counter is incremented each time a downlink TBF is candidate for resourcereallocation due to Trigger T4 but after the radio resource reallocation algorithm isrun, it is decided not to change its current allocation. As such, it corresponds to aresource reallocation preparation failure.



Sub Domain 3 T4



792 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.5.4.5 P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4


Definition Number of downlink TBFs for which the resource reallocation protocol is runningfollowing T4 and an external TBF release request is received which forces to stopthe on-going resource reallocation (Flush-LL from the SGSN or GPRS suspensionrequest from the BSC)

Trigger Condition The counter is incremented each time the resources of a downlink TBF are beingreallocated due Trigger T4 (i.e. either a Packet Uplink Assignment or a PacketTimeslot Reconfigure message has been sent to the MS to reallocate its uplinkresources) and:- a FLUSH-LL is received from the SGSN, or- a GPRS SuspensionRequest is received from the BSCfor that Mobile Station before the Packet ControlAcknowledgement message is received.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 793 / 1256


24.1.3.6 DL TBF releases

24.1.3.6.1 N/A

24.1.3.6.1.1 P11 - NB_DL_TBF_REL_GB_PB_MStransDL

Long Name NB_DL_TBF_REL_GB_PB_MStransDL

Definition Number of DL TBF release due to the unavailability of the BVC (Gb interfaceproblem) associated with the cell when the MS is in packet transfer mode DL(the DL TBF is established).

Trigger Condition When the BVC associated with the cell is unavailable, the counter is incrementedby the number of DL TBF established on this cell. All pending LLC PDU in theMFS are discarded.


Sub Domain 2 DL TBF releases

Sub Domain 3 N/A



794 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.2 P146 - NB_DL_TBF_REL_PREEMPTradio

Long Name NB_DL_TBF_REL_PREEMPTradio

Definition Number of DL TBF release due to fast preemption or due to too high number ofTBF on a TRX (according the number of GCHs that will remain on the TRX afterthe CS preemption process).

Trigger Condition Each time that upon T_PDCH pre-emption timer expiry for lack of resources(T1 TBF reallocation failure), a DL TBF is released.Each time that there areNb_TBFs_To_Release_DL TBF to release. The counter is incremented by thevalue of Nb_TBFs_To_Release_DL.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 795 / 1256


24.1.3.6.1.3 P207 - NB_DL_TBF_REL_DL_DELAYED

Long Name NB_DL_TBF_REL_DL_DELAYED

Definition Number of times a DL TBF is released because of a radio failure when the TBFis in downlink delayed phase.

Trigger Condition Each time a DL TBF is released because of a radio failure when it is in downlinkdelayed phase.Considered radio failures are: - a radio link lost due to N3105(N3105 exceeds its limit)- too low TX efficiency.



Sub Domain 3 N/A



796 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.4 P302b_1 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105

Long Name NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105

Definition Number of times a DL TBF is released because of a radio failure.Considered radiofailure is: - a radio link lost due to N3105 (N3105 exceeds its limit)

Trigger Condition A DL TBF is released because of a radio failure.Considered radio failure is: - aradio link lost due to N3105 (N3105 exceeds its limit)



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 797 / 1256


24.1.3.6.1.5 P302b_2 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF

Long Name NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF

Definition Number of times a DL TBF is released because of a radio failure.Consideredradio failure is: - too low TX efficiency.

Trigger Condition A DL TBF is released because of a radio failure.Considered radio failure is: -too low TX efficiency.



Sub Domain 3 N/A



798 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.6 P303a - NB_ABNORMAL_DL_TBF_REL

Long Name NB_ABNORMAL_DL_TBF_REL

Definition Number of abnormal DL TBF releases due to the following reasons:- becauseduring the DL TBF no Packet Downlink Ack/Nack message is received for too longa time, or,- because at the end of the DL TBF established in RLC acknowledgedmode no final Packet Downlink Ack/Nack message in RLC acknowledgedmode is received, or,- because at the end of the DL TBF established in RLCunacknowledged mode no final Packet Control Acknowledgement message isreceived.

Trigger Condition The counter is incremented whenever a DL TBF is released:i) because thetimer T_TBF_ACTIV has expired, or,ii) because the timer T_TBF_BCK_RELhas expired.Note 1: The timer T_TBF_ACTIV is used to monitor the receiptof the first DL LLC PDU after the TBF has been activated.Note 2: The timerT_TBF_BCK_REL is used for three purposes:- during a DL TBF to monitor thereceipt of the Packet Downlink Ack/Nack messages when the transmit windowis stalled,- at the end of a DL TBF to monitor the receipt of the final PacketDownlink Ack/Nack message (in RLC acknowledged mode) or final Packet ControlAcknowledgement message (in RLC unacknowledged mode),- at the end of anUL TBF to monitor the receipt of the Packet Control Acknowledgement messageacknowledging the final Packet Uplink Ack/Nack message,



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 799 / 1256


24.1.3.6.1.7 P385a - NB_DL_TBF_REL_STAGWINDOW

Long Name NB_DL_TBF_REL_STAGWINDOW

Definition Number of DL TBF releases because the transmit window has been stagnatingfor too long a time.

Trigger Condition The counter is incremented whenever a DL TBF is released becausethe RLC counter N_StagnatingWindowDL exceeds the system parameterN_STAGNATING_WINDOW_DL_LIMIT.In RLC acknowledged mode, the RLCcounter N_StagnatingWindowDL is incremented when the same oldest RLC datablock in the transmit window is not acknowledged by the received bitmap of thelast (EGPRS) Packet Downlink Ack/Nack message.Note: The cases where a DLTBF is released because the transmit window has been stagnating for too long atime should be due to MS errors.



Sub Domain 3 N/A



800 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.8 P396a - NB_RLC_DL_TBF_RELEASE_REQ_FOR_CR

Long Name NB_RLC_DL_TBF_RELEASE_REQ_FOR_CR

Definition Number of downlink TBF releases requested by RRM to RLC upon receipt ofthe Flush message.

Trigger Condition Whenever a DL TBF (establishing or on-going) is released due to the receipt of aFlush message. Note that if the downlink TBF has already been released by RLC(before the receipt of the Flush message), the counter is not incremented. Theinternal PCC-RLC-RELEASE-cnf primitive is used for incrementing the counter.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 801 / 1256


24.1.3.6.1.9 P434b - NB_NC2_DL_TBF_RELEASE

Long Name NB_NC2_DL_TBF_RELEASE

Definition Number of DL TBF releases due to NC2 cell reselections

Trigger Condition This counter is incremented whenever the MFS detects an abnormal transitionfrom packet downlink transfer mode to packet idle mode further to the sending ofthe first Packet Cell Change Order message. The counter is then incrementedwhenever one of the following events occurs after the sending of the Packet CellChange Order message:i) an TBF-RELEASE-ind message with an abnormalcause is received from RLC layer (for the DL TBF) while the MFS is waiting for theacknowledgement of the Packet Cell Change Order message or while the MFS iswaiting for the FLUSH-LL message, or,ii) an TBF-RELEASE-cnf message is sentto RLC layer (for the DL TBF) further to the receipt of the acknowledgement ofthe Packet Cell Change Order message or further to the receipt of the Flush-LLmessage.The counter is incremented only once per NC cell reselection execution.



Sub Domain 3 N/A



802 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.10 P434d - NB_NC0_DL_TBF_RELEASE

Long Name NB_NC0_DL_TBF_RELEASE

Definition Number of DL TBF releases due to NC0 cell reselections

Trigger Condition This counter is incremented whenever a NC0 cell reselection leads to the releaseof a DL TBF. The counter is then incremented for MS operating in NC0 modewhenever one of the following events occurs:i) a Flush-LL message is receivedfrom the SGSN and this Flush-LL message concerns a DL TBF which is stillon-going,ii) a Flush-LL message is received from the SGSN and this Flush-LLmessage concerns a DL TBF which has been abnormally released in the previousT_WAIT_FLUSH seconds.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 803 / 1256


24.1.3.6.1.11 P9 - NB_DL_TBF_NORM_REL

Long Name NB_DL_TBF_NORM_REL

Definition Number of DL TBF normal release.

Trigger Condition Whenever the DL TBF normally released by the MFS: upon receipt of the reply tothe 04.60 RLC DATA BLOCK (FBI=1, polling) sent by the MFS for the last RLCblock to send, ie 04.60 (EGPRS) PACKET DOWNLINK ACK/NACK from themobile, with no DL retransmision required.This counter is also incremented incase of DL TBF release due to concurrent establisment (UL + DL) i.e when theMS is accessing the network via a Channel Request. (crossing cases DL dataand Channel Request from the MS).



Sub Domain 3 N/A



804 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.6.1.12 P98a - NB_DL_TBF_REL_SUSP

Long Name NB_DL_TBF_REL_SUSP

Definition Number of DL TBF release due to a suspension from MS.

Trigger Condition Whenever MFS receives a suspend message from BSC when the MS is in DLpacket transfer, the counter is incremented at each released TBF.When the TBFis released due to a radio link failure linked to suspension, this counter is notincremented (P302b is incremented in this case).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 805 / 1256


24.1.3.6.1.13 P98e - NB_SUSP_DL_TBF_REL

Long Name NB_SUSP_DL_TBF_REL

Definition Number of DL TBF releases due to the suspend procedure

Trigger Condition This counter is incremented whenever :1) a Suspend message is received fromBSC and the suspend procedure concerns a DL TBF which is still on-going2) aSuspend message is received from BSC and the suspend procedure concernsa DL TBF which has been abnormally released in the previous T_WAIT_FLUSHseconds.



Sub Domain 3 N/A



806 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.7 DL/UL TBF monitoring per GPU

24.1.3.7.1 N/A

24.1.3.7.1.1 P106 - NB_TBF_EST_SUCC_GPU

Long Name NB_TBF_EST_SUCC_GPU

Definition Number of DL and UL establishments successes.Sum of P90a,b,c,d,e,f andP30a,b,c (cell counters) for each cell mapped on GPU.

Trigger Condition –


Sub Domain 2 DL/UL TBF monitoring per GPU

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


3BK 21255 AAAA PCZZA Ed.07 807 / 1256


24.1.3.7.1.2 P107 - NB_TBF_EST_REQ_GPU

Long Name NB_TBF_EST_REQ_GPU

Definition Number of Dl and UL establishments requestsSum of P91a,b,c,d,e,f and P62a,b,c(cell counter ) for each cell mapped on GPU.



Sub Domain 2 DL/UL TBF monitoring per GPU

Sub Domain 3 N/A



808 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8 DTM

24.1.3.8.1 N/A

24.1.3.8.1.1 P500 - NB_DTM_CAPABLE_MS_CONTEXT_GPU

Long Name NB_DTM_CAPABLE_MS_CONTEXT_GPU

Definition Number of MS contexts created for DTM capable mobile stations.

Trigger Condition When in a MS context , the MS radio access capabilities indicating that the MSis DTM capable are available.Note: To be able to compare this counter with e.g.P450b, it shall be incremented only on reception of Radio Access Capabilities ofthe MS i.e. independently of information received from the BSC.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 809 / 1256


24.1.3.8.1.2 P501 - NB_DTM_MS_CONTEXT_CELL

Long Name NB_DTM_MS_CONTEXT_CELL

Definition Number of DTM contexts created.

Trigger Condition Incremented each time a DTM context is created following:- the reception of BSCShared DTM Info Indication with CS flag = 1 or- at reception of BSCGP DTMREQUEST when no BSC Shared DTM Info Indication with CS flag had beenreceived previously for this MSor- at reception of BSCGP DTM GPRS informationcarying an UL LLC PDU .


Sub Domain 2 DTM

Sub Domain 3 N/A



810 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.3 P502 - CUMULATED_DTM_TIME

Long Name CUMULATED_DTM_TIME

Definition Cumulated time during which a DTM capable MS is operating in DTM mode.

Trigger Condition Starting: when in dedicated mode on the establishment of the first UL or DL TBF.(the first UL RLC data Blocks are received from the MS (case of UL TBF) or thefirst Packet downlink Ack/Nack message is received from the MS (case of DLTBF)). Stopping : when in DTM mode the CS session or PS session are , normallyor abnormally , released. Note: The common duration during which a UL and aDL are established is counted as one duration (UL and DL common time durationsare not cumulated).The time is provided in seconds with one significant value afterthe comma (i.e. ROUND(10x) / 10).Note 1: The time duration of all periods (activeand delayed/extended) is taken into account.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 811 / 1256


24.1.3.8.1.4 P503 - CUMULATED_DTM_DEDICATED_TIME

Long Name CUMULATED_DTM_DEDICATED_TIME

Definition Cumulated time during which a DTM capable MS is operating in dedicated mode.

Trigger Condition The timer is the sum of all the unit times-Starting : When the indication of startof a CS session is received (first BSCGP BSC Shared DTM Info Indication withCS=1 received) or when , in DTM mode , PS session is , normally or abnormally ,released.-Stopping :When in dedicated mode, the first UL RLC data Blocks arereceived from the MS (case of UL TBF) or the first Packet downlink Ack/Nackmessage is received from the MS (case of DL TBF) or when in dedicated mode ,an indication of stop of CS session is received (BSCGP BSC Shared DTM InfoIndication with CS=0 received) or when in dedicated mode , an indication of stopof CS session is received.The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).


Sub Domain 2 DTM

Sub Domain 3 N/A



812 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.5 P504 - CUMULATED_DTM_PTM_TIME

Long Name CUMULATED_DTM_PTM_TIME

Definition Cumulated time during which a DTM capable MS is operating in packet transfermode.

Trigger Condition Cumulated time duration of all UL / DL TBFs established over the Granularityperiod. Note : DTM capability of the MS is given in RA capabilities, which areknown only :- in case a DL LLC PDU has been received for this MS- in caseonly an UL TBF exists, once the procedure for RA capability update is finished(provided EN_RA_CAP_UPDATE = 1)


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 813 / 1256


24.1.3.8.1.6 P505 - NB_DTM_DL_TBF_EST_REQ

Long Name NB_DTM_DL_TBF_EST_REQ

Definition Number of DL TBF establishment requests on DCCH for MS operating in DTM.

Trigger Condition This counter is incremented when the MFS receives the first DL LLC PDU for aMS in dedicated mode (and in GMM ready state).Note : - This counter applies onlyto DTM capable mobiles.- DL LLC PDU sent with BSCGP DTM GPRS informationare not taken into account.


Sub Domain 2 DTM

Sub Domain 3 N/A



814 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.7 P506 - NB_DTM_DL_TBF_EST_SUCC

Long Name NB_DTM_DL_TBF_EST_SUCC

Definition Number of DL TBF establishment successes on DCCH for MS operating in DTM.

Trigger Condition This counter is incremented when the MFS receives the first Packet Downlink ack(following the reception of a DL LLC PDU for a MS in dedicated mode).Note 1 :This counter applies only to DTM capable mobiles.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 815 / 1256


24.1.3.8.1.8 P507 - NB_DTM_UL_TBF_EST_REQ

Long Name NB_DTM_UL_TBF_EST_REQ

Definition Number of UL TBF establishment requests on DCCH for MS operating in DTM.

Trigger Condition This counter is incremented when MFS receives the BSCGP DTM Requestmessage.


Sub Domain 2 DTM

Sub Domain 3 N/A



816 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.9 P508 - NB_DTM_UL_TBF_EST_SUCC

Long Name NB_DTM_UL_TBF_EST_SUCC

Definition Number of UL TBF establishment successes on DCCH for MS operating in DTM.

Trigger Condition This counter is incremented when the MFS receives the first UL RLC data blockfor a MS in dedicated mode.Note 1 : This counter applies only to DTM capablemobiles.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 817 / 1256


24.1.3.8.1.10 P509 - NB_DTM_CS_DL_TBF_RELEASE

Long Name NB_DTM_CS_DL_TBF_RELEASE

Definition Number of DL TBF releases due to the release of the CS connection when theMS leaves the dual transfer mode or due to the establishment of a CS connectionwhen the MS enters the dual transfer mode.This counter also counts the DL TBFrelease due to a handover.

Trigger Condition This counter is incremented for DTM capable MS with ongoing DL TBF established, when an abnormal DL TBF release, occurs :- when the DTM mode is leaved (release of the CS connection in DTM mode).- when in DTM mode an intercell oran intracell handover occurs.- when in PTM the dedicated mode is entered.


Sub Domain 2 DTM

Sub Domain 3 N/A



818 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.11 P510 - NB_DTM_CS_UL_TBF_RELEASE

Long Name NB_DTM_CS_UL_TBF_RELEASE

Definition Number of UL TBF releases due to the release of the CS connection when theMS leaves the dual transfer mode or due to the establishment of a CS connectionwhen the MS enters the dual transfer mode.This counter also counts the UL TBFrelease due to an handover.

Trigger Condition This counter is incremented for DTM capable MS with ongoing UL TBFsestablished , when an abnormal UL TBF release, occurs :- when the DTM modeis leaved ( release of the CS connection in DTM mode)- when in DTM mode anintercell or an intracell handover occurs - when in PTM the dedicated mode isentered.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 819 / 1256


24.1.3.8.1.12 P511 - NB_DTM_DL_TBF_FAIL_CONG

Long Name NB_DTM_DL_TBF_FAIL_CONG

Definition Number of DL TBF establishment failures on DCCH for MS operating in DTM dueto a lack of radio resources.

Trigger Condition This counter is incremented when MFS has no suitable radio resources to enter inDTM mode.


Sub Domain 2 DTM

Sub Domain 3 N/A



820 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.13 P512 - NB_DTM_UL_TBF_FAIL_CONG

Long Name NB_DTM_UL_TBF_FAIL_CONG

Definition Number of UL TBF establishment failures on DCCH for MS operating in DTM dueto a lack of radio resources.

Trigger Condition This counter is incremented when the MFS sends the BSCGP DTM rejectmessage in case of lack of radio resources available.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 821 / 1256


24.1.3.8.1.14 P513 - NB_UL_LLC_BYTES_GTTP

Long Name NB_UL_LLC_BYTES_GTTP

Definition Number of bytes received from the MS with the GTTP protocol.

Trigger Condition This counter is incremented by the number of bytes of the UL LLC PDU carried inthe BSCGP DTM GPRS information messages received in MFS.


Sub Domain 2 DTM

Sub Domain 3 N/A



822 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.15 P514 - NB_DL_LLC_BYTES_GTTP

Long Name NB_DL_LLC_BYTES_GTTP

Definition Number of bytes sent to the MS with the GTTP protocol.

Trigger Condition This counter is incremented by the number of bytes of the DL LLC PDU carriedin the BSCGP DTM GPRS information messages sent by MFS.Note : Possiblerepetitions of the messages are not taken into account i.e only the DL_LLC_PDUacknowledged by BSCGP DTM GPRS information ack message are take intoaccount.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 823 / 1256


24.1.3.8.1.16 P515 - NB_RT_PFC_CREATION_DTM_DEDICATED

Long Name NB_RT_PFC_CREATION_DTM_DEDICATED

Definition Number of RT PFC creation request for a DTM MS in dedicated mode.

Trigger Condition The counter is incremented for a DTM MS in dedicated mode , each time aPFC-CREATION is received and the PFC indicates streaming or conversational.


Sub Domain 2 DTM

Sub Domain 3 N/A



824 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.17 P516 - NB_RT_PFC_DOWNGRADED_DTM_DEDICATED

Long Name NB_RT_PFC_DOWNGRADED_DTM_DEDICATED

Definition Number of RT PFC downgraded to Best Effort for a DTM MS in dedicated mode.

Trigger Condition For a DTM MS in dedicated mode, this counter is - Incremented when MFSproposes a Default Best Effort ABQP in response to a RT-PFC creation receivedin the cell.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 825 / 1256


24.1.3.8.1.18 P518 - NB_RT_PFC_CREATION_DTM_MODE

Long Name NB_RT_PFC_CREATION_DTM_MODE

Definition Number of RT PFC creation request for a MS in DTM mode.

Trigger Condition The counter is incremented for a DTM MS in DTM mode , each time aPFC-CREATION is received and the PFC indicates streaming or conversational.


Sub Domain 2 DTM

Sub Domain 3 N/A



826 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.8.1.19 P519 - NB_RT_PFC_DOWNGRADED_DTM_MODE

Long Name NB_RT_PFC_DOWNGRADED_DTM_MODE

Definition Number of RT PFC downgraded to Best Effort for a DTM MS in DTM mode.

Trigger Condition For a DTM MS in DTM mode, this counter is - Incremented when MFS proposes aDefault Best Effort ABQP in response to a RT-PFC creation received in the cell.


Sub Domain 2 DTM

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 827 / 1256


24.1.3.9 EDA

24.1.3.9.1 N/A

24.1.3.9.1.1 P594 - NB_EDA_MS_CONTEXT_GPU

Long Name NB_EDA_MS_CONTEXT_GPU

Definition Number of EDA-capable GPRS and EGPRS MS contexts.

Trigger Condition For a MS context, the MS Radio Access Capability indicates the support of EDAeither in GPRS mode or in EGPRS mode or in both modes.If EDA is supported inboth modes, the counter shall be incremented only by one.


Sub Domain 2 EDA

Sub Domain 3 N/A



828 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.9.1.2 P595 - CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE

Long Name CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE

Definition Cumulated overall time of UL TBF in active state operating in EDA mode .

Trigger Condition The counter measures the cumulated time duration of all UL TBFs connectionsin active phase and operating in EDA mode , whatever the UL pdch EDAconfiguration used, in the cell over the granularity period.The counter starts :whenan UL TBF in active phase and in DA mode is reallocated in EDA mode, or whenan UL TBF in EDA mode and in Extended Uplink TBF Mode wakes upor whenan UL TBF is established directly in EDA mode (in this case the start of activephase is taken into account).The counter stops:when an UL TBF in EDA modegoes to Extended Uplink TBF Mode, or when an UL TBF in active phase and inEDA mode is reallocated in DA mode, or when an UL TBF in EDA mode ends(normally or not).Note1 : This counter applies to both GPRS and EGPRS TBFsand to both acknowledge or unacknowledge mode.Note 2 :The case the UL TBFis released due to a NC cell reselection is managed as an abnormal UL TBFrelease.The time is provided in seconds with one significant value after the comma(i.e. ROUND(10x) / 10).


Sub Domain 2 EDA

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 829 / 1256


24.1.3.9.1.3 P596 - NB_EDA_USED_UL_TBF

Long Name NB_EDA_USED_UL_TBF

Definition Number of UL TBF that have used at least one time the EDA mode during theirlifetime.

Trigger Condition This counter is incremented when an UL TBF is directly allocated in EDA mode oris reallocated in EDA mode at least one time during its lifetime.Note: The countershall be incremented at most by one per uplink TBF.


Sub Domain 2 EDA

Sub Domain 3 N/A



830 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.9.1.4 P597 - NB_EDA_ALLOWED_UL_TBF

Long Name NB_EDA_ALLOWED_UL_TBF

Definition Number of UL TBF belonging to mobile stations allowed using the EDA mode butthat did not necessarily use it (due to all conditions not fulfilled).

Trigger Condition This counter is incremented when- At UL TBF establishment, the bias is knownto be uplink and the mobile station is allowed to use the EDA mode.- The bias iscomputed and equal to uplink and the mobile station is allowed to use the EDAmode.Notes:- A mobile station is known here as allowed to use the EDA mode ifit supports EDA and if the OMC setting allows it using EDA. Note:- This meansthe N_UL_BIAS_FOR_EDA (when superior to 1) and BIAS_LIMIT_EDA (whensuperior to 1) conditions are not taken into account for this counter.-The countershall be incremented at most by one per uplink TBF.


Sub Domain 2 EDA

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 831 / 1256


24.1.3.9.1.5 P598 - NB_DA_EDA_REALLOC_UL_TBF

Long Name NB_DA_EDA_REALLOC_UL_TBF

Definition Number of reallocations between DA and EDA modes for UL TBF.

Trigger Condition This counter is incremented each time an UL TBF is re-allocated from DA modeto EDA mode or from EDA mode to DA mode.Note : Such TBF have necessarilyused at least one time the EDA mode during their lifetime.


Sub Domain 2 EDA

Sub Domain 3 N/A



832 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.10 Inter-NSE DL LLC PDU re-routing

24.1.3.10.1 N/A

24.1.3.10.1.1 P440a - NB_REROUTING_INTRA_NSE

Long Name NB_REROUTING_INTRA_NSE

Definition Within the granularity period, the MFS counts the number of times it receives anorder from the SGSN to reroute DL LLC PDUs to another cell belonging to thesame NSE (even if there is actually no PDU to reroute).

Trigger Condition Receipt of a FLUSH-LL message containing the new BVCI and, if the SGSNsupports the INR option, not the new NSEI


Sub Domain 2 Inter-NSE DL LLC PDU re-routing

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 833 / 1256


24.1.3.10.1.2 P440b - NB_REROUTING_INTER_NSE_INTRA_BSS

Long Name NB_REROUTING_INTER_NSE_INTRA_BSS

Definition Within the granularity period, the MFS counts the number of times conditions arefulfilled to reroute DL LLC PDUs to another cell belonging to another NSE but tothe same BSS (even if there is actually no PDU to reroute).

Trigger Condition The counter is incremented in the two following cases:i) either the SGSN supportsthe Inter-NSE Rerouting feature and the MFS receives a FLUSH-LL messagecontaining the new BVCI and the new NSEI and the new NSEI is part of theserving BSS,ii) or the SGSN does not support the Inter-NSE Rerouting featureand the autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTING setto enabled) and the MFS receives a FLUSH-LL message following a cell changeoccuring between two NSEs within the same BSS and within the same routingarea.



Sub Domain 3 N/A



834 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.10.1.3 P440c - NB_REROUTING_INTER_NSE_INTER_BSS

Long Name NB_REROUTING_INTER_NSE_INTER_BSS

Definition Within the granularity period, the MFS counts the number of times conditions arefulfilled to reroute DL LLC PDUs to another cell belonging to another NSE and toanother BSS (even if there is actually no PDU to reroute).

Trigger Condition The counter is incremented in the two following cases:i) either the SGSNsupports the Inter-NSE Rerouting feature and the MFS receives a FLUSH-LLmessage containing the new BVCI and the new NSEI and the new NSEI is partof a different BSS than the BSS of the source cellii) or the SGSN does notsupport the Inter-NSE Rerouting feature and the autonomous rerouting is enabled(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives aFLUSH-LL message following a cell change occuring between two NSEs andbetween two different BSSs , within the same routing area.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 835 / 1256


24.1.3.10.1.4 P441a - NB_IMPOSSIBLE_OR_UNREQUESTED_REROUTING_INR

Long Name NB_IMPOSSIBLE_OR_UNREQUESTED_REROUTING_INR

Definition Within the granularity period, if the SGSN supports the Inter-NSE Reroutingfeature, the MFS counts the number of times the SGSN does not request rerouting.

Trigger Condition The counter is incremented in the following case:- the SGSN supports theInter-NSE Rerouting feature and the MFS receives a FLUSH-LL message notcontaining the new BVCI



Sub Domain 3 N/A



836 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.10.1.5 P441b - NB_UNREQUESTED_REROUTING_NOT_INR

Long Name NB_UNREQUESTED_REROUTING_NOT_INR

Definition Within the granularity period, if the SGSN does not support the Inter-NSE Reroutingfeature and autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTINGset to enabled), the MFS counts the number of times the MFS receives an order(in the FLUSH-LL message) from the SGSN not to reroute DL LLC PDUs followinga cell change occuring within the same routing area and within the same NSE.

Trigger Condition The counter is incremented in the following case:- the SGSN does notsupport the Inter-NSE Rerouting feature and autonomous rerouting is enabled(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives aFLUSH-LL message not containing the new BVCI following a cell change occuringwithin the same routing area and within the same NSE.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 837 / 1256


24.1.3.10.1.6 P441c - NB_IMPOSSIBLE_REROUTING_NOT_INR

Long Name NB_IMPOSSIBLE_REROUTING_NOT_INR

Definition Within the granularity period, if the SGSN does not support the Inter-NSE Reroutingfeature and autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTINGset to enabled), the MFS counts the number of times the MFS receives aFLUSH-LL message following a cell change occuring between two differentrouting areas.

Trigger Condition The counter is incremented in the following case: the SGSN does notsupport the Inter-NSE Rerouting feature and autonomous rerouting is enabled(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives aFLUSH-LL message following a cell change occuring between two differentrouting areas.



Sub Domain 3 N/A



838 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11 PFC

24.1.3.11.1 N/A

24.1.3.11.1.1 P200 - NB_DOWNGRADED_MOVING_RT_PFC

Long Name NB_DOWNGRADED_MOVING_RT_PFC

Definition Number of time a RT-PFC is downgraded because of the moving of a MS intothe cell.

Trigger Condition - Incremented, in the target cell, when PCC cannot accept a RT-PFC getting intothe cell because of lack of resource and downgrades the RT-PFC to the DefaultBest Effort ABQP.-Incremented when PCC cannot accept a RT-PFC getting intothe cell because the flag EN_STREAMING in the cell is set to OFF.Note : MS indedicated mode or in DTM mode are not taken into account.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 839 / 1256


24.1.3.11.1.2 P220 - NB_MOVING_RT_PFC

Long Name NB_MOVING_RT_PFC

Definition Number of RT-PFCs created by cell reselection.

Trigger Condition - Incremented, in the target cell, when a RT-PFC is forwarded from another cellfollowing a cell reselection.


Sub Domain 2 PFC

Sub Domain 3 N/A



840 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.3 P229 - NB_RT_PFC_PREEMPTED

Long Name NB_RT_PFC_PREEMPTED

Definition Number of time a RT-PFC is impacted by a CS pre-emption.

Trigger Condition When a CS pre-emption is detected, RRM-PCC increments the counter eachtime a RT-PFC is impacted.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 841 / 1256


24.1.3.11.1.4 P231 - NB_DOWNGRADED_RT_PFC_DEFENCE

Long Name NB_DOWNGRADED_RT_PFC_DEFENCE

Definition Number of time a RT-PFC is downgraded due to defense mechanism.

Trigger Condition Incremented, in the current cell, when MFS downgrades a RT-PFC to the DefaultBest Effort ABQP due to defense mechanism (lack of resources) during its time life.


Sub Domain 2 PFC

Sub Domain 3 N/A



842 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.5 P232 - NB_MOVING_RT_PFC_TARGET

Long Name NB_MOVING_RT_PFC_TARGET

Definition Number of RT-PFC that are successfully moved in another cell following a cellreselection of the MS.

Trigger Condition Incremented, in the source cell, when a RT-PFC is successfully forwardedto another cell following a cell reselection.Note: This counter can be onlyincremented if the MFS manages the target cell.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 843 / 1256


24.1.3.11.1.6 P463 - NB_PFC_DOWNLOAD

Long Name NB_PFC_DOWNLOAD

Definition Number of time RRM-PCC initiates a PFC-DOWNLOAD towards SGSN.

Trigger Condition Incremented by RRM-PCC each time a PFM-DOWNLOAD-BSS-PFC.req is sentto BSSGP. Note : Repetitions of PFC-DOWNLOAD performed by BSSGP arenot taken into account.


Sub Domain 2 PFC

Sub Domain 3 N/A



844 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.7 P488 - NB_RT_DL_TBF

Long Name NB_RT_DL_TBF

Definition Number of time the established DL TBF is in RT mode.

Trigger Condition - Incremented by RRM-PCC each time a DL TBF is established in RT mode.-Incremented by RRM-PCC each time an established NRT DL TBF passes toRT mode.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 845 / 1256


24.1.3.11.1.8 P489 - NB_RT_UL_TBF

Long Name NB_RT_UL_TBF

Definition Number of time the established UL TBF is in RT mode.

Trigger Condition - Incremented by RRM-PCC each time a UL TBF is established in RT mode.-Incremented by RRM-PCC each time an established NRT UL TBF passes toRT mode.


Sub Domain 2 PFC

Sub Domain 3 N/A



846 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.9 P490 - NB_UNACK_NRT_PFC_CREATION

Long Name NB_UNACK_NRT_PFC_CREATION

Definition Number of time a NRT-PFC-CREATION of mode RLC unacknowledged isreceived by RRM-PCC.

Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received with the 2following characteristics :- The received PFC indicates either a background or aninteractive,- The received PFC indicates an unacknowledged RLC mode.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 847 / 1256


24.1.3.11.1.10 P491 - NB_UNACK_RT_PFC_CREATION

Long Name NB_UNACK_RT_PFC_CREATION

Definition Number of time a RT-PFC-CREATION of mode RLC unacknowledged is receivedby RRM-PCC.

Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received with the 2following characteristics :- The received PFC indicates a streaming ,- The receivedPFC indicates an unacknowledged RLC mode.


Sub Domain 2 PFC

Sub Domain 3 N/A



848 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.11 P492 - NB_DOWNGRADED_RT_PFC

Long Name NB_DOWNGRADED_RT_PFC

Definition Number of time a RT-PFC is downgraded, whatever the cause listed below.

Trigger Condition - Incremented when PCC proposes a Default Best Effort ABQP in response toa RT-PFC creation received in the cell.- Incremented when PCC downgrades aRT-PFC to the Default Best Effort ABQP by defense mechanism.- Incrementedwhen the received RT-PFC creation indicates streaming and EN_STREAMINGis false.- Incremented when the received PFC creation contains an inconsistentABQP content. - The MS RA capability cannot be retrieved from SGSN.Note : MSin dedicated mode or in DTM mode are not taken into account.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 849 / 1256


24.1.3.11.1.12 P493 - NB_PFC_REJECTED

Long Name NB_PFC_REJECTED

Definition Number of time a PFC is rejected.

Trigger Condition Incremented when a PFC is rejected because the received PFI is not correct, orbecause it is a RT-PFC with RLC unacknowledged mode.Incremented when themaximum number of PFC per MS is reached.


Sub Domain 2 PFC

Sub Domain 3 N/A



850 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.13 P494 - NB_PFC_DOWNLOAD_FAIL

Long Name NB_PFC_DOWNLOAD_FAIL

Definition Number of time the BSS cannot get the PFC characteristics from SGSN

Trigger Condition Incremented by RRM-PCC when a PFM-DOWNLOAD-BSS-PFC-failure.ind isreceived from BSSGP.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 851 / 1256


24.1.3.11.1.14 P497 - NB_RT_PFC_CREATION

Long Name NB_RT_PFC_CREATION

Definition Number of time a RT-PFC-CREATION is received by RRM-PCC.

Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received and the PFCis either a streaming or a conversational.


Sub Domain 2 PFC

Sub Domain 3 N/A



852 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.11.1.15 P498 - NB_NRT_PFC_CREATION

Long Name NB_NRT_PFC_CREATION

Definition Number of time a NRT-PFC-CREATION is received by RRM-PCC.

Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received and the PFCis either a background or an interactive.


Sub Domain 2 PFC

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 853 / 1256


24.1.3.11.1.16 P499 - NB_RT_PFC_CREATION_OK

Long Name NB_RT_PFC_CREATION_OK

Definition Number of time a RT-PFC-CREATION is received and proceeded successfullyby RRM-PCC.

Trigger Condition Incremented by RRM-PCC each time a streaming PFC-CREATION is receivedand the PFC is created successfully without any downgrading.


Sub Domain 2 PFC

Sub Domain 3 N/A



854 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.12 Suspend / Resume

24.1.3.12.1 N/A

24.1.3.12.1.1 P98c - NB_SUSPEND_REQ_FOR_DL_TBF

Long Name NB_SUSPEND_REQ_FOR_DL_TBF

Definition Number of suspend messages for a DL TBF received from MS (via BSC).

Trigger Condition Whenever MFS receives a suspend message from BSC for a DL TBF.


Sub Domain 2 Suspend / Resume

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 855 / 1256


24.1.3.12.1.2 P98d - NB_SUSPEND_REQ_FOR_UL_TBF

Long Name NB_SUSPEND_REQ_FOR_UL_TBF

Definition Number of suspend messages for a UL TBF received from MS (via BSC).

Trigger Condition Whenever MFS receives a suspend message from BSC for an UL TBF.


Sub Domain 2 Suspend / Resume

Sub Domain 3 N/A



856 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13 UL TBF establishments

24.1.3.13.1 N/A

24.1.3.13.1.1 P105d - NB_UL_TBF_EST_FAIL_GPU_CONG

Long Name NB_UL_TBF_EST_FAIL_GPU_CONG

Definition Number of UL TBF establishment failures due to GPU congestion.Note: Thiscounter applies to GPRS and EGPRS MS.

Trigger Condition When an UL TBF cannot be established, due to GPU congestion. GPU congestionmeans that the maximum capacity of at least one DSP on the GPU is reachedin terms of resources GCH and/or PDCH.Generally, for all counters related toTBF establishment failures, only the last reported failure cause is taken intoaccount.Note: This counter may also be incremented when the MS have requesteda single block access on CCCH to send a 04.60 PACKET MEASUREMENTREPORT message or a 04.60 PACKET CELL CHANGE FAILURE message.


Sub Domain 2 UL TBF establishments

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 857 / 1256


24.1.3.13.1.2 P105f - NB_UL_TBF_EST_FAIL_CPU_GPU

Long Name NB_UL_TBF_EST_FAIL_CPU_GPU

Definition Number of UL TBF establishment failures due to CPU processing power limitationsof the GPU.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition Whenever a UL TBF cannot be established due to CPU processing powerlimitations of the GPU.Note: This counter may also be incremented when theMS have requested a single block access on CCCH to send a 04.60 PACKETMEASUREMENT REPORT message or a 04.60 PACKET CELL CHANGEFAILURE message.



Sub Domain 3 N/A



858 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.3 P105h - NB_UL_TBF_EST_FAIL_CONG_ATER

Long Name NB_UL_TBF_EST_FAIL_CONG_ATER

Definition Number of UL TBF establishment failures due to a lack of Ater resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a UL TBF establishment fails due to a lackof Ater resources.A lack of Ater resources occurs when there is not enough Aternibbles to serve the UL TBF request.For BTS evolium :the number of GCH thatcan be established and/or redistributed is < Nb_GCH_FOR_TBF_ESTAB andthe number of free Ater nibbles is < Nb_GCH_FOR_TBF_ESTAB.For DRFUBTS :Lack of free Ater nibbles to serve the GCHs.The counter is incrementedon receipt of an (EGPRS) PACKET CHANNEL_REQUEST on (P)RACH, or onreceipt of an (EGPRS) PACKET DL ACK/NACK (with a Channel Request IE) onPACCH, or receipt of a CHANNEL REQUEST on RACH when the UL TBF cannotbe served due to a lack of transmission resources.Note: This counter may alsobe incremented when the MS have requested a single block access on CCCH tosend a 04.60 PACKET MEASUREMENT REPORT message or a 04.60 PACKETCELL CHANGE FAILURE message.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 859 / 1256


24.1.3.13.1.4 P105j - NB_UL_TBF_EST_FAIL_CONG_ABIS

Long Name NB_UL_TBF_EST_FAIL_CONG_ABIS

Definition Number of UL TBF establishment failures due to a lack of Abis resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever a UL TBF establishment fails dueto a lack of Abis resources.A lack of Abis transmission resources occurswhen there is not enough Abis nibbles to serve the UL TBF request.For BTSevolium only :the number of GCH that can be established and or redistributedis < Nb_GCH_FOR_TBF_ESTAB and the number of free Abis nibbles is <Nb_GCH_FOR_TBF_ESTAB.For DRFU BTS :The counter is always 0.Thecounter is incremented at the expiry of the PDU lifetime when the last attempt failsto establish the UL TBF due to a lack of transmission resources.The counteris incremented on receipt of an (EGPRS) PACKET CHANNEL_REQUEST on(P)RACH, or on receipt of an (EGPRS) PACKET DL ACK/NACK (with a ChannelRequest IE) on PACCH, or receipt of a CHANNEL REQUEST on RACH when theUL TBF cannot be served due to a lack of transmission resources. Note: Thiscounter may also be incremented when the MS have requested a single blockaccess on CCCH to send a 04.60 PACKET MEASUREMENT REPORT messageor a 04.60 PACKET CELL CHANGE FAILURE message.



Sub Domain 3 N/A



860 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.5 P105l - NB_UL_TBF_EST_FAIL_TOO_MANY_TBF

Long Name NB_UL_TBF_EST_FAIL_TOO_MANY_TBF

Definition Number of UL TBF establishment failures due to:- a too low number of GCH toguarantee a minimum throughput for the UL TBF.- This may happen when thenumber of TBFs is too high compared to the number of available GCHs.- - or theMAX_TBF_TRX_UL constraint.Note: This counter applies to GPRS and EGPRSMS.

Trigger Condition The counter is incremented whenever a UL TBF establishment fails due to:1)a too low number of available GCH.For BTS evolium :The number of GCHavailable to serve the UL TBF is < Min_Nb_GCH.For DRFU BTS :Counter notincremented (=0).2) or the MAX_TBF_TRX_UL constraint:For BTS evolium :TheMAX_TBF_TRX_UL limit is reached on all the TRXs available for PS traffic in thecell.For DRFU BTS :Counter not incremented (=0).The counter is incrementedat the expiry of the PDU lifetime (T_ul_access_max) or when the attempt failsto establish the UL TBF due to too low number of available GCH (too manyTBFs on the TRX compared to the number of available GCHs) or due to theMAX_TBF_TRX_UL constraint.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 861 / 1256


24.1.3.13.1.6 P204 - NB_UL_TBF_EST_FAIL_PTU_DSP_LOAD

Long Name NB_UL_TBF_EST_FAIL_PTU_DSP_LOAD

Definition Number of UL TBF establishment failures due to DSPs that are in CPU load /overload state.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented each time a UL TBF establishment fails due to theinternal cause CPU_DSP_LOAD.The counter is incremented on receipt of an(EGPRS) PACKET CHANNEL_REQUEST on (P)RACH, or on receipt of an(EGPRS) PACKET DL ACK/NACK (with a Channel Request IE) on PACCH, orreceipt of a CHANNEL REQUEST on RACH when the UL TBF cannot be serveddue to DSP CPU load / overload.Note: This counter may also be incrementedwhen the MS have requested a single block access on CCCH to send a 04.60PACKET MEASUREMENT REPORT message or a 04.60 PACKET CELLCHANGE FAILURE message.



Sub Domain 3 N/A



862 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.7 P214 - NB_UL_TBF_ENT_EXTENDED_UPLINK

Long Name NB_UL_TBF_ENT_EXTENDED_UPLINK

Definition Number of established UL TBF entering the extended uplink state for the first time.

Trigger Condition Each time an active UL TBF enters for the first time the extended uplink state.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 863 / 1256


24.1.3.13.1.8 P215 - NB_UL_TBF_RESUME_IN_EXTENDED_UPLINK

Long Name NB_UL_TBF_RESUME_IN_EXTENDED_UPLINK

Definition Number of UL TBF transfer resumptions in extended uplink state.

Trigger Condition The counter is incremented each time a UL TBF state changes from "extendeduplink" to "active".It corresponds to the UL TBF becoming active again withinthe extended uplink phase duration.



Sub Domain 3 N/A



864 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.9 P27 - NB_UL_TBF_EST_FAIL_CONG

Long Name NB_UL_TBF_EST_FAIL_CONG

Definition Number of UL TBF establishment failures due to a lack of radio resources.Note:This counter applies to GPRS and EGPRS MS.

Trigger Condition The counter is incremented whenever an UL TBF establishment fails due to a lackof radio resources. A lack of radio resource occurs:i) if the maximum number ofMSs per slave PDCH in uplink is reached for all the slave PDCHs allocated to theMFS, orii) if there is no TAI or TFI left in the MFS.oriii) if no PDCH are grantedto MFS due to a CS congestion and max_pdch_high_load is null.The counteris incremented on receipt of an (EGPRS) PACKET CHANNEL_REQUEST on(P)RACH, or on receipt of an (EGPRS) PACKET DL ACK/NACK (with a ChannelRequest IE) on PACCH, or on receipt of a CHANNEL REQUEST on RACH whenthe UL TBF cannot be served due to a lack of radio resources.Note: This countermay also be incremented when the MS have requested a single block access onCCCH to send a 04.60 PACKET MEASUREMENT REPORT message or a 04.60PACKET CELL CHANGE FAILURE message.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 865 / 1256


24.1.3.13.1.10 P28 - NB_UL_TBF_EST_FAIL_RADIO_PB

Long Name NB_UL_TBF_EST_FAIL_RADIO_PB

Definition Number of UL TBF establishment failures due to radio problem.The cell operationalstate is "enabled" and the GCHs carrying the TBF are available for traffic.

Trigger Condition Either at expiry of the timer monitoring the beginning of the UL transfer.- Or onreception of PCC-RLC-RELEASE-ind with Cause = "no transfer start"- Or afterMax_Retrans_DL attempts to obtain acknowledgement from the MS for resourcereallocation due to T2 for a downlink TBF (with uplink TBF establishment) butit was never received.Generally, for all counters related to TBF establishmentfailures, only the last reported failure cause is taken into account



Sub Domain 3 N/A



866 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.11 P30a - NB_UL_TBF_EST_SUCC_MSidle_MastChan

Long Name NB_UL_TBF_EST_SUCC_MSidle_MastChan

Definition Number of UL TBFs successfully established on PCCCH when:- the MS is inpacket idle mode- the MS have requested an uplink TBF establishmentNote: Thiscounter applies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented i) when the TLLI is received during a one phaseaccess UL TBF establishment triggered on PRACH, orii) when the TBF startindication is received during a two phase access UL TBF establishment triggeredon PRACH.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 867 / 1256


24.1.3.13.1.12 P30b - NB_UL_TBF_EST_SUCC_MStransDL

Long Name NB_UL_TBF_EST_SUCC_MStransDL

Definition Number of UL TBFsuccesfully established when the MS is in downlink packettransfer mode.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition When the TBF start indication is received during an UL TBF establishment onPACCH.



Sub Domain 3 N/A



868 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.13 P30c - NB_UL_TBF_EST_SUCC_MSidle_NO_MastChan

Long Name NB_UL_TBF_EST_SUCC_MSidle_NO_MastChan

Definition Number of UL TBFs successfully established on CCCH when:- the MS is in packetidle mode- the MS have requested an uplink TBF establishmentNote: This counterapplies to GPRS and EGPRS MS.

Trigger Condition This counter is incremented i) when the TLLI is received during a one phaseaccess UL TBF establishment triggered on RACH, orii) when the TBF startindication is received during a two phase access UL TBF establishment triggeredon RACH.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 869 / 1256


24.1.3.13.1.14 P62a - NB_UL_TBF_EST_REQ_MSidle_MastChan

Long Name NB_UL_TBF_EST_REQ_MSidle_MastChan

Definition Number of UL TBF establishment requests on PCCCH when :- the MS is in packetidle mode- the MS requests an uplink TBF establishmentNote 1: This counterapplies to GPRS and EGPRS MS.Note 2: The access cause "Single Block withoutTBF establishment" is not taken into account in this counter, as this access causedoes not lead to the establishment of an uplink TBF.

Trigger Condition This counter is incremented whenever a 04.60 (EGPRS) PACKET CHANNELREQUEST is received on PRACH from the MS requesting an uplink TBFestablishment (i.e. all access causes except the access cause "Single blockwithout TBF establishment").Generally, all counters related to TBF establishmentrequests only take into account the first attempt, i.e. no network repetitions arecounted. (Repetitions from the MS are counted.)



Sub Domain 3 N/A



870 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.15 P62b - NB_UL_TBF_EST_REQ_MStransDL

Long Name NB_UL_TBF_EST_REQ_MStransDL

Definition Number of UL TBF establishment requests when the MS is in downlink packettransfer mode.Note: This counter applies to GPRS and EGPRS MS.

Trigger Condition Whenever a 04.60 (EGPRS) PACKET DL ACK/NACK [with Channel Request IE] isreceived on PACCH channel from the MS.Note that the counter is incrementedwhether the request is served with a PACKET UPLINK ASSIGNMENT or aPACKET TIMESLOT RECONFIGURE (which means that the DL TBF resourcesare re-assigned upon concurrent UL TBF establishment).Generally, all countersrelated to TBF establishment requests only take into account the first attempt,i.e. no repetitions are counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 871 / 1256


24.1.3.13.1.16 P62c - NB_UL_TBF_EST_REQ_MSidle_NO_MastChan

Long Name NB_UL_TBF_EST_REQ_MSidle_NO_MastChan

Definition Number of UL access requests on CCCH when the MS is in packet idle mode.Note1: This counter applies to GPRS and EGPRS MS.Note 2: This counter takes intoaccount requests leading to both an uplink TBF establishment or a single blockallocation used to carry a 04.60 PACKET MEASUREMENT REPORT messageor a 04.60 PACKET CELL CHANGE FAILURE message (when the NC2 featureis activated).

Trigger Condition This counter is incremented whenever a 04.18 CHANNEL REQUEST messagewith access cause "One phase packet access" or "Single block packet access", ora 04.18 EGPRS PACKET CHANNEL REQUEST is received on RACH from theMS.Generally, all counters related to TBF establishment requests only take intoaccount the first attempt, i.e. no network repetitions are counted. (Repetitionsfrom the MS are counted.)



Sub Domain 3 N/A



872 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.13.1.17 P66 - NB_UL_TBF_EST_FAIL_GB_PB

Long Name NB_UL_TBF_EST_FAIL_GB_PB

Definition Number of UL TBF establishment failures due to the unavailability of the BVC (Gbinterface problem) associated with the cell.

Trigger Condition Whenever the BVC associated with the cell is unavailable (which implies: celloperational state "disabled"), the counter is incremented with the nb of UL TBF inestablishment phase.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 873 / 1256


24.1.3.14 UL TBF re-allocations

24.1.3.14.1 T1

24.1.3.14.1.1 P404a - NB_UL_RES_REALLOC_REQ_T1

Long Name NB_UL_RES_REALLOC_REQ_T1

Definition Number of uplink TBFs for which the corresponding Mobile Station has at leastone of its TBFs impacted by a CS pre-emption process over the granularity period.Resource reallocation will then be called for the TBFs of those Mobile Stations(thanks to trigger T1).

Trigger Condition The counter is incremented by one each time a uplink TBF is impacted by a CSpre-emption process. Two cases are possible :- a uplink TBF has its PACCHimpacted by a soft PDCH pre-emption,- the maximum allowed (M)CS of a uplinkTBF will no longer be possible to serve because of an M-EGCH link size reductiondue to a soft PDCH pre-emption. The M-EGCH link to consider is the one of theTRX currently supporting the uplink TBF. That case is only valid for Evolium BTSsand can only occur in case the basic Abis nibbles of some of the soft-preemptedPDCHs are currently being used by GCHs within the considered M-EGCH link.Example : if a uplink EGPRS TBF has MCS-9 as its maximum allowed (M)CSand is established on a TRX whose M-EGCH link owns 5 GCHs, then if the CSpreemption process leads to an M-EGCH link having only 4 GCHs left (becauseone of the GCHs of the M-EGCH link is using a basic Abis nibble mapped toa pre-empted PDCH), then the uplink TBF will be impacted, and the counterincremented.The counter is also incremented by one each time a uplink TBF hasa concurrent downlink TBF impacted by the CS preemption process (the sameconditions as the above ones apply for the downlink direction), in case the uplinkTBF was not impacted.In both cases, the MFS will try to reallocate the resourcesof the MS, which will require reallocating the TBFs in one or in both directions.


Sub Domain 2 UL TBF re-allocations

Sub Domain 3 T1



874 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.1.2 P406a - NB_UL_RES_REALLOC_SUCC_T1

Long Name NB_UL_RES_REALLOC_SUCC_T1

Definition Number of resource reallocation attempts that lead to reallocating successfully anuplink TBF (due to trigger T1).

Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for that uplink TBF due to T1. If the PACKET CONTROLACKNOWLEDGEMENT acknowledges reallocation of both an uplink and adownlink TBF, this counter shall be incremented as well as P405a.If after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T1, only the resources of the downlink TBF need to be reallocated,the procedure shall be considered successful for the uplink TBF, irrespective ofthe reallocation protocol outcome. Indeed, even if the reallocation protocol failsfor the downlink TBF, the uplink TBF will not be released and therefore this canbe considered as a success. This is another trigger for incrementing this counter.This is required since P404a has been incremented.Similarly, if after the resourcereallocation algorithm is run for a candidate Mobile Station having two TBFsfollowing T1, there is a preparation failure but the PACCH of the uplink TBF is notimpacted by soft PDCH pre-emption, then the uplink TBF will remain alive and thiscounter shall be incremented.The counter can be used to compute the successrate of the reallocation execution phase.Note: this counter takes into account alsothe successful T1 reallocations where the MAX_(M)CS of an UL TBF is decreasedwithout any change of its radio allocation.



Sub Domain 3 T1



3BK 21255 AAAA PCZZA Ed.07 875 / 1256


24.1.3.14.1.3 P408a - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T1

Long Name NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T1

Definition Number of resource reallocation attempts that lead to reallocating an uplink TBFbut the procedure failed due to radio problems and the TBF was released (dueto trigger T1).

Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T1 for an uplink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocationprotocol was attempted but failed had two TBFs and both were being reallocated,then both counters P407a and P408a shall be incremented.



Sub Domain 3 T1



876 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.1.4 P424a - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1

Long Name NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1

Definition Number of attempts for uplink TBFs impacted by a CS pre-emption process, T1resource reallocation has been attempted but no candidate allocation could befound. The TBF could therefore not be reallocated.

Trigger Condition The counter is incremented each time a uplink TBF is impacted by a CSpre-emption process , the resource reallocation algorithm is run but no candidateallocation can be found for the uplink TBF. As such, it corresponds to a resourcereallocation preparation failure.



Sub Domain 3 T1



3BK 21255 AAAA PCZZA Ed.07 877 / 1256


24.1.3.14.1.5 P426a - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1

Long Name NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1

Definition Number of uplink TBFs for which the resource reallocation protocol is runningfollowing T1 and an external TBF release request is received which forces tostop the on-going resource reallocation (FLUSH-LL from the SGSN or GPRSSUSPENSION REQUEST from the BSC).

Trigger Condition The counter is incremented each time the resources of an uplink TBF arebeing reallocated (ie either a PACKET UPLINK ASSIGNMENT or a PACKETTIMESLOT RECONFIGURE message has been sent to the MS to reallocate itsuplink resources) and:- a FLUSH-LL is received from the SGSN, or- a GPRSSUSPENSION REQUEST is received from the BSCfor that Mobile Station beforethe PACKET CONTROL ACKNOWLEDGEMENT is received.



Sub Domain 3 T1



878 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.2 T2

24.1.3.14.2.1 P404b - NB_UL_RES_REALLOC_REQ_T2


Definition Number of uplink TBFs which are candidate for resource reallocation uponconcurrent downlink TBF establishment.

Trigger Condition The counter is incremented by one each time a concurrent downlink TBFestablishment request is received and the uplink TBF is candidate for resourcereallocation.



Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 879 / 1256


24.1.3.14.2.2 P406b - NB_UL_RES_REALLOC_SUCC_T2



Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for that TBF due to T2, i.e. due to the establishment of aconcurrent downlink TBF. Note that this counter shall be incremented only onceeven if two TBF establishments are actually acknowledged.The counter can beused to compute the success rate of the reallocation execution phase.



Sub Domain 3 T2



880 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.2.3 P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2

Long Name NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2


Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T2 for an uplink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS.Note : because the corresponding downlink TBFcould not be established, then P15 is also incremented.



Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 881 / 1256


24.1.3.14.2.4 P424b - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2


Definition Number of attempts for uplink TBFs which were candidate for T2 resourcereallocation upon concurrent downlink TBF establishment but for which nocandidate allocation could be found apart from their current allocation. The uplinkTBFs were therefore not reallocated.

Trigger Condition Upon concurrent downlink TBF establishments, the counter is incrementedwhen :i) The downlink TBF cannot be served because the on-going uplink TBFcannot be re-allocated and concurrence constraints make the downlink TBFestablishment impossible on the on-going uplink TBF.



Sub Domain 3 T2



882 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.2.5 P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2






Sub Domain 3 T2



3BK 21255 AAAA PCZZA Ed.07 883 / 1256


24.1.3.14.3 T3

24.1.3.14.3.1 P404c - NB_UL_RES_REALLOC_REQ_T3


Definition Number of uplink TBFs for which the corresponding Mobile Station was candidatefor resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due totrigger T3). Only candidate MSs for which the resource allocation algorithm wascalled are taken into account.

Trigger Condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incrementedby the number of UL TBFs for which the corresponding Mobile Station iscandidate for resource reallocation and for which the resource allocation algorithmwill be run to try and find a better allocation. This means that it is limited toN_MAX_PERIODIC_REALLOC_T3 attempts upon each timer expiry.Note 1:all uplink TBFs for which the resource allocation algorithm is run have to becounted, even if the corresponding Mobile Station has a downlink-biased transferand therefore the MS is registered in the downlink list.Note 2: in case a givenmobile station has got two TBF(s) on-going and its resources are attempted tobe reallocated,



Sub Domain 3 T3



884 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.3.2 P406c - NB_UL_RES_REALLOC_SUCC_T3



Trigger Condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resourcereallocation attempt for an uplink TBF due to T3. If the PACKET CONTROLACKNOWLEDGEMENT acknowledges reallocation of both an uplink and adownlink TBF, this counter shall be incremented as well as P405c.If after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T3, only the resources of the downlink TBF need to be reallocated,the procedure shall be considered successful for the uplink TBF, irrespective ofthe reallocation protocol outcome. Indeed, even if the reallocation protocol failsfor the downlink TBF, the uplink TBF will not be released and therefore this canbe considered as a success. This is another trigger for incrementing this counter.This is required since P404c has been incremented.The counter can be used tocompute the success rate of the reallocation execution phase.



Sub Domain 3 T3



3BK 21255 AAAA PCZZA Ed.07 885 / 1256


24.1.3.14.3.3 P408c - NB_UL_TBF_RADIO_PB_RES_REALLOC_T3

Long Name NB_UL_TBF_RADIO_PB_RES_REALLOC_T3


Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to T3 for an uplink TBF but it was never received,the TBF is released and this counter is incremented. Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocation wasattempted but failed had two TBFs and both were being reallocated, then bothcounters P407c and P408c shall be incremented.



Sub Domain 3 T3



886 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.3.4 P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3


Definition Number of periodic attempts for uplink TBFs which were candidate for resourcereallocation due to T3 but for which no candidate allocation could be found apartfrom their current allocation. The uplink TBFs were therefore not reallocated.

Trigger Condition The counter is incremented each time an uplink TBF is candidate for resourcereallocation due to T3 but after the radio resource reallocation algorithm is run,it is decided not to change its current allocation. As such, it corresponds to aresource reallocation preparation failure.



Sub Domain 3 T3



3BK 21255 AAAA PCZZA Ed.07 887 / 1256


24.1.3.14.3.5 P426c - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3






Sub Domain 3 T3



888 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.4 T4

24.1.3.14.4.1 P404d - NB_UL_RES_REALLOC_REQ_T4


Definition Number of uplink TBFs for which the corresponding Mobile Station was candidatefor resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due toTrigger T4). Only candidate MSs for which the resource allocation algorithm wascalled are taken into account.

Trigger Condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incrementedby the number of UL TBFs which are candidate for resource reallocation andfor which the resource allocation algorithm will tend to free EGPRS radioresources.This means that it is limited to N_MAX_PERIODIC_REALLOC_T4attempts upon each timer expiry.Note that in case a given mobile station has gotan UL and DL TBFs on-going and its resources are attempted to be reallocateddue to Trigger T4, then both P403d and P404d shall be incremented.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 889 / 1256


24.1.3.14.4.2 P406d - NB_UL_RES_REALLOC_SUCC_T4


Definition Number of T4 resource reallocation attempts that lead to reallocating successfullyan uplink TBF

Trigger Condition A Packet Control Acknowledgement message is received following a resourcereallocation attempt for an uplink TBF due to Trigger T4.Note that if the PacketControl Acknowledgement message acknowledges reallocation of both an uplinkand a downlink TBFs, both P405d and P406d shall be incremented.If after theresource reallocation algorithm is run for a candidate Mobile Station having twoTBFs following T4, only the resources of the downlink TBF need to be reallocated,the procedure shall be considered successful for the uplink TBF, irrespective ofthe reallocation protocol outcome. Indeed, even if the reallocation protocol failsfor the downlink TBF, the uplink TBF will not be released and therefore this canbe considered as a success. This is another trigger for incrementing this counter.This is required since P404d has been incremented.



Sub Domain 3 T4


External Comment The counter can be used to compute the success rate of the reallocation executionphase.

890 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.4.3 P408d - NB_UL_TBF_RADIO_PB_RES_REALLOC_T4

Long Name NB_UL_TBF_RADIO_PB_RES_REALLOC_T4

Definition Number of T4 resource reallocation attempts that lead to reallocating an uplinkTBF but the procedure failed due to radio problems and the TBF was released.

Trigger Condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS forresource reallocation due to Trigger T4 for an uplink TBF but it was never received,the TBF is released and this counter is incremented.Assuming that the MSis not bugged, it means that the radio conditions were too poor for the MS toeither correctly receive the reassignment message or for the MFS to receive theacknowledgement from the MS. If an MS for which the resource reallocation wasattempted but failed had two TBFs and both were being reallocated, then bothcounters P407d and P408d shall be incremented.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 891 / 1256


24.1.3.14.4.4 P424d - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4


Definition Number of periodic attempts for uplink TBFs which were candidate for T4 resourcereallocation but for which no suitable candidate allocation could be found apartfrom their current allocation. The uplink TBFs were therefore not re-allocated.

Trigger Condition The counter is incremented each time an uplink TBF is candidate for resourcereallocation due to Trigger T4 but after the radio resource reallocation algorithm isrun, it is decided not to change its current allocation. As such, it corresponds to aresource reallocation preparation failure.



Sub Domain 3 T4



892 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.14.4.5 P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4


Definition Number of uplink TBFs for which the resource reallocation protocol is runningfollowing T4 and an external TBF release request is received which forces to stopthe on-going resource reallocation (Flush-LL from the SGSN or GPRS suspensionrequest from the BSC).

Trigger Condition The counter is incremented each time the resources of an uplink TBF are beingreallocated due Trigger T4 (i.e. either a Packet Uplink Assignment or a PacketTimeslot Reconfigure message has been sent to the MS to reallocate its uplinkresources) and:- a FLUSH-LL is received from the SGSN, or- a GPRS SuspensionRequest is received from the BSCfor that Mobile Station before the Packet ControlAcknowledgement message is received.



Sub Domain 3 T4



3BK 21255 AAAA PCZZA Ed.07 893 / 1256


24.1.3.15 UL TBF releases

24.1.3.15.1 N/A

24.1.3.15.1.1 P147 - NB_UL_TBF_REL_PREEMPTradio

Long Name NB_UL_TBF_REL_PREEMPTradio

Definition Number of UL TBF release due to fast preemption or due to too high number ofTBF on a TRX (according the number of GCHs that will remain on the TRX afterthe CS preemption process).

Trigger Condition Each time that upon T_PDCH_pre-emption timer expiry for lack of resources(T1 TBF reallocation failure), an UL TBF is released.Each time that there areNb_TBFs_To_Release_UL TBF to release. The counter is incremented by thevalue of Nb_TBFs_To_Release_UL.


Sub Domain 2 UL TBF releases

Sub Domain 3 N/A



894 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.2 P208 - NB_UL_TBF_REL_EXTENDED_UL

Long Name NB_UL_TBF_REL_EXTENDED_UL

Definition Number of times a UL TBF is released because of a radio failure when it is inextended uplink phase.

Trigger Condition Each time a UL TBF is released because of a radio failure when it is inextended uplink phase.Considered radio failures are: - a radio link lost due toN3101 or N3103 (N3101 or N3103 exceeds its limit)- Too low TX efficiency.-N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 895 / 1256


24.1.3.15.1.3 P22 - NB_UL_TBF_NORM_REL

Long Name NB_UL_TBF_NORM_REL

Definition Number of UL TBF normal release.

Trigger Condition Whenever the UL TBF is normally released by the MS: upon the receipt of thereply to the 04.60 PACKET ACK/NACK (FINAL, polling) sent by the MFS on thelast received RLC block, with no UL retransmission required.



Sub Domain 3 N/A



896 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.4 P24 - NB_UL_TBF_REL_GB_PB_MStransUL

Long Name NB_UL_TBF_REL_GB_PB_MStransUL

Definition Number of UL TBF release due to the unavailability of the BVC (Gb interfaceproblem) associated with the cell when the MS is in packet transfer mode UL(the UL TBF is established).

Trigger Condition When the BVC associated with the cell is unavailable, the counter is incrementedby the number of UL TBF established in this cell.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 897 / 1256


24.1.3.15.1.5 P302c_1 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101

Definition Number of times a UL TBF is released because of a radio failure.Considered radiofailure is: - a radio link lost due to N3101 (N3101 exceeds its limit)

Trigger Condition A UL TBF is released because of a radio failure.Considered radio failure is: - aradio link lost due to N3101 (N3101 exceeds its limit)



Sub Domain 3 N/A



898 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.6 P302c_2 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103

Definition Number of times a UL TBF is released because of a radio failure.Considered radiofailure is: - a radio link lost due to N3103 (N3103 exceeds its limit)

Trigger Condition A UL TBF is released because of a radio failure.Considered radio failure is: - aradio link lost due to N3103 (N3103 exceeds its limit)



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 899 / 1256


24.1.3.15.1.7 P302c_3 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF

Definition Number of times a UL TBF is released because of a radio failure.Consideredradio failure is: - too low TX efficiency.

Trigger Condition A UL TBF is released because of a radio failure.Considered radio failure is: -Too low TX efficiency.



Sub Domain 3 N/A



900 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.8 P302c_4 -NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM

Definition Number of times a UL TBF is released because of a radio failure.Consideredradio failure is: - a radio link lost due to N_POLLING_EUTM (N_POLLING_EUTMexceeds its limit)

Trigger Condition A UL TBF is released because of a radio failure.Considered radio failure is: - aradio link lost due to N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit)



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 901 / 1256


24.1.3.15.1.9 P303b - NB_ABNORMAL_UL_TBF_REL

Long Name NB_ABNORMAL_UL_TBF_REL

Definition Number of abnormal UL TBF releases due to the following reasons:- becauseduring the UL TBF no UL RLC blocks is received for too long a time, or- becauseat the end of the UL TBF no answer to the final Packet Uplink Akc/Nack messageis received.

Trigger Condition The counter is incremented whenever an UL TBF is released:i) because the RLCcounter N_UL_DUMMY exceeds the system parameter N_UL_DUMMY_LIMIT,or,ii) because the timer T_TBF_BCK_REL has expired.Note 1: The RLC counterN_UL_DUMMY is incremented whenever a dummy UL RLC block is received fromthe MS.Note 2: The timer T_TBF_BCK_REL is used for three purposes:- during aDL TBF to monitor the receipt of the Packet Downlink Ack/Nack messages whenthe transmit window is stalled,- at the end of a DL TBF to monitor the receiptof the final Packet Downlink Ack/Nack message (in RLC acknowledged mode)or final Packet Control Acknowledgement message (in RLC unacknowledgedmode),- at the end of an UL TBF to monitor the receipt of the Packet ControlAcknowledgement message acknowledging the final Packet Uplink Ack/Nackmessage,



Sub Domain 3 N/A



902 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.10 P385b - NB_UL_TBF_REL_STAGWINDOW

Long Name NB_UL_TBF_REL_STAGWINDOW

Definition Number of UL TBF releases because the receive window has been stagnatingfor too long a time.

Trigger Condition The counter is incremented whenever an UL TBF is released becausethe RLC counter N_StagnatingWindowUL exceeds the system parameterN_STAGNATING_WINDOW_UL_LIMIT.The RLC counter N_StagnatingWindowULis incremented provided that the receive window is stalled whenever an UL RLCdata block whose BSN is different from the receive window state variable V(Q)and is received a round trip delay after the previous sending of a Packet UplinkAck/Nack message.Note 1: The receive window state variable V(Q) denotes thelowest BSN not yet received (modulo SNS). It corresponds to the oldest ULRLC data block in the received window.Note 2: The cases where an UL TBF isreleased because the receive window has been stagnating for too long a timeshould be due to MS errors or radio problems (due to the non-receipt of Packet ULAck/Nack messages).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 903 / 1256


24.1.3.15.1.11 P396b - NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR

Long Name NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR

Definition Number of uplink TBF releases requested by RRM to RLC upon receipt of theFlush message.

Trigger Condition Whenever a UL TBF (establishing or on-going) is released due to the receipt of aFlush message. Note that if the uplink TBF has already been released by RLC(before the receipt of the Flush message), the counter is not incremented. Theinternal PCC-RLC-RELEASE-cnf primitive is used for incrementing the counter.



Sub Domain 3 N/A



904 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.12 P434a - NB_NC2_UL_TBF_RELEASE

Long Name NB_NC2_UL_TBF_RELEASE

Definition Number of UL TBF releases due to NC2 cell reselections

Trigger Condition This counter is incremented whenever the MFS detects an abnormal transitionfrom packet uplink transfer mode to packet idle mode further to the sending ofthe first Packet Cell Change Order message. The counter is then incrementedwhenever one of the following events occurs after the sending of the Packet CellChange Order message:i) an TBF-RELEASE-ind message with an abnormalcause is received from RLC layer (for the UL TBF) while the MFS is waiting for theacknowledgement of the Packet Cell Change Order message or while the MFS iswaiting for the FLUSH-LL message, or,ii) an TBF-RELEASE-cnf message is sentto RLC layer (for the UL TBF) further to the receipt of the acknowledgement ofthe Packet Cell Change Order message or further to the receipt of the Flush-LLmessage.The counter is incremented only once per NC cell reselection execution.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 905 / 1256


24.1.3.15.1.13 P434c - NB_NC0_UL_TBF_RELEASE

Long Name NB_NC0_UL_TBF_RELEASE

Definition Number of UL TBF releases due to NC0 cell reselections

Trigger Condition This counter is incremented whenever a NC0 cell reselection leads to the releaseof an UL TBF. The counter is then incremented for MS operating in NC0 modewhenever one of the following events occurs:i) a Flush-LL message is receivedfrom the SGSN and this Flush-LL message concerns an UL TBF which is stillon-going,ii) a Flush-LL message is received from the SGSN and this Flush-LLmessage concerns an UL TBF which has been abnormally released in theprevious T_WAIT_FLUSH seconds.



Sub Domain 3 N/A



906 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.1.3.15.1.14 P98b - NB_UL_TBF_REL_SUSP

Long Name NB_UL_TBF_REL_SUSP

Definition Number of UL TBF release due to a suspension from MS.

Trigger Condition Whenever MFS receives a suspend message from BSC when the MS is in ULpacket transfer, the counter is incremented at each released TBF.When the TBFis released due to a radio link failure linked to suspension, this counter is notincremented (P302c is incremented in this case).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 907 / 1256


24.1.3.15.1.15 P98f - NB_SUSP_UL_TBF_REL

Long Name NB_SUSP_UL_TBF_REL

Definition Number of UL TBF releases due to the suspend procedure.

Trigger Condition This counter is incremented whenever :1) a Suspend message is received fromBSC and the suspend procedure concerns an UL TBF which is still on-going2) aSuspend message is received from BSC and the suspend procedure concernsan UL TBF which has been abnormally released in the previous T_WAIT_FLUSHseconds.



Sub Domain 3 N/A



908 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2 Resource availability and usage

24.2.1 Abis interface

24.2.1.1 GCH

24.2.1.1.1 N/A

24.2.1.1.1.1 P465 - MAX_NB_USED_EXTRA_BONUS_ABIS_NIBBLES

Long Name MAX_NB_USED_EXTRA_BONUS_ABIS_NIBBLES

Definition Maximum number of extra and bonus Abis nibbles currently used in the cell (bya GCH channel).

Trigger Condition An internal counter tracks the current number of extra and bonus Abis nibbles usedin the cell.An Abis nibble is said used when it is either reserved for establishmentor used by a GCH.Whenever this internal counter is incremented, its new valueis compared with the stored maximum number of extra and bonus nibbles in thecell. If this value is higher than the stored maximum value, the value becomes thenew maximum.In the particular case of a cell shared over two BTSs, the number iscomputed in the BTS sector which contains the PS-capable TRXs of the cell.

Sub Domain 1 Abis interface

Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 909 / 1256


24.2.1.1.1.2 P466 - CUMULATED_TIME_USED_EXTRA_BONUS_ABIS_NIBBLES

Long Name CUMULATED_TIME_USED_EXTRA_BONUS_ABIS_NIBBLES

Definition Cumulated time during which extra and bonus Abis nibbles are used in the cell,cumulated over all extra and bonus Abis nibbles.

Trigger Condition The counter cumulates over the reporting period the time during which an extra ora bonus Abis nibble is used in the cell.An Abis nibble is said used when it is eitherreserved for establishment or used by a GCH.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x) / 10).


Sub Domain 2 GCH

Sub Domain 3 N/A



910 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.1.1.1.3 P472 - CUMULATED_TIME_FREE_EXTRA_BONUS_ABIS_NIBBLES

Long Name CUMULATED_TIME_FREE_EXTRA_BONUS_ABIS_NIBBLES

Definition Cumulative time (in seconds), per BTS ,during which there are free extra andbonus Abis nibbles available.Free extra and bonus nibbles are extra and bonusnibbles not currently used in a GCH Notes: 1) This only concerns Evolium BTS.

Trigger Condition Within the Granularity period, the number of free extra and bonus Abis nibbles isobserved .For each free bonus or extra Abis nibble, the counter cumulates overthe reporting period the time during which this nibble is free.An Abis nibble is saidfree when it is neither reserved for establishment nor used by a GCH.


Sub Domain 2 GCH

Sub Domain 3 N/A

Measured Object BTS


3BK 21255 AAAA PCZZA Ed.07 911 / 1256


24.2.1.1.1.4 P484 - MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE

Long Name MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE

Definition Minimum number of free extra and bonus Abis nibbles.Free extra and bonusnibbles are extra and bonus nibbles not currently used in a GCH.

Trigger Condition This counter gives the lowest value (not null) of the number of free extra and bonusAbis nibbles among all the values of free extra and bonus Abis nibbles obtainedover the granularity period.An Abis nibble is said free when it is neither reservedfor establishment nor used by a GCH.At the beginning of each granularity period,the counter is initialized with the number of extra and bonus abis nibbles grantedto the MFS for the concerned BTS.


Sub Domain 2 GCH

Sub Domain 3 N/A

Measured Object BTS


912 / 1256 3BK 21255 AAAA PCZZA Ed.07



24.2.2.1 GCH

24.2.2.1.1 N/A

24.2.2.1.1.1 P100c - CUMULATED_TIME_BUSY_GCH_CELL

Long Name CUMULATED_TIME_BUSY_GCH_CELL

Definition Cumulative time (in seconds) during which a GCH (16k channel) is busy in the cell.The counter is integrated over all the GCH available in the cell.For a DRFU BTS, aGCH is said busy when it is connected to a given PDCH.For an Evolium BTS, aGCH is said busy when it is connected to a given TRX (as part as an M-EGCH).

Trigger Condition The counter cumulates over the reporting period the time during which a GCH isbusy in the cell.For a given GCH, the counter starts when the associated Ater nibblebecomes busy and stops on the sending of BSCGP ABIS-NIBBLES-ALLOCATIONmessage indicating the GCH deallocation.An Ater nibble is said busy when it iseither reserved for establishment or used by a GCH.The transmission resourcesconnected to carry master PDCHs are included in this counter.


Sub Domain 2 GCH

Sub Domain 3 N/A


External Comment This counter shall be aggegrated at GPU level by NPA.It is the equivalent ofP100a (B8), at cell level.

3BK 21255 AAAA PCZZA Ed.07 913 / 1256


24.2.2.1.1.2 P100d - MAX_NB_BUSY_GCH_CELL

Long Name MAX_NB_BUSY_GCH_CELL

Definition Maximum number of busy GCH (16k channel) in the cell.For a DRFU BTS, a GCHis said busy when it is connected to a given PDCH.For an Evolium BTS, a GCH issaid busy when it is connected to a given TRX (as part as an M-EGCH).

Trigger Condition An internal counter tracks the current number of busy GCH in the cell. This internalcounter is incremented when the associated Ater nibble of a GCH becomes busyor decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATION messageindicating the GCH deallocation.An Ater nibble is said busy when it is eitherreserved for establishment or used by a GCH.Whenever this internal counter isincremented, its new value is compared with the stored maximum number ofbusy GCH in the cell. If this value is higher than the stored maximum value, thevalue becomes the new maximum.At the begining of each granularity period , thecounter is initialized with the current number of busy GCH.


Sub Domain 2 GCH

Sub Domain 3 N/A


External Comment This counter shall be aggregated by NPA at cell level.It is the equivalent of P100b(B8) at cell level.

914 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.1.1.3 P100e - MIN_NB_BUSY_GCH_CELL

Long Name MIN_NB_BUSY_GCH_CELL

Definition Minimum number of busy GCH (16k channel) in the GPU.For a DRFU BTS, aGCH is said busy when it is connected to a given PDCH.For an Evolium BTS, aGCH is said busy when it is connected to a given TRX (as part as an M-EGCH).

Trigger Condition An internal counter tracks the current number of busy GCH in the cell. This internalcounter is incremented when the associated Ater nibble of a GCH becomes busyor decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATION messageindicating the GCH deallocation.An Ater nibble is said busy when it is eitherreserved for establishment or used by a GCH.Whenever this internal counter isincremented, its new value is compared with the stored minimum number of busyGCH in the cell. If this value is lower than the stored minimum value, the valuebecomes the new minimum.At the begining of each granularity period , the counteris initialised with the current number of busy GCH.


Sub Domain 2 GCH

Sub Domain 3 N/A


External Comment This counter shall be aggregated by NPA at cell level.

3BK 21255 AAAA PCZZA Ed.07 915 / 1256


24.2.2.1.1.4 P100f - MAX_NB_GCH_BUSY_GPU

Long Name MAX_NB_GCH_BUSY_GPU

Definition Maximum number of busy GCH (16k channel) in the GPU.For a DRFU BTS, aGCH is said busy when it is connected to a given PDCH.For an Evolium BTS, aGCH is said busy when it is connected to a given TRX (as part as an M-EGCH).

Trigger Condition An internal counter tracks the current number of busy GCH in the GPU. Thisinternal counter is incremented when the associated Ater nibble of a GCH becomesbusy or decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATIONmessage indicating the GCH deallocation.An Ater nibble is said busy when it iseither reserved for establishment or used by a GCH.Whenever this internal counteris incremented, its new value is compared with the stored maximum number ofbusy GCH in the GPU. If this value is higher than the stored maximum value, thevalue becomes the new maximum.At the begining of each granularity period , thecounter is initialized with the current number of busy GCH.


Sub Domain 2 GCH

Sub Domain 3 N/A


External Comment It is the equivalent of P100b (B8) at GPU level.

916 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.1.1.5 P101 - CUMULATED_TIME_AVAIL_GCH_GPU

Long Name CUMULATED_TIME_AVAIL_GCH_GPU

Definition Cumulative time (in seconds) during which a GCH resource (16k channel) isavailable in the GPU. The counter is integrated over all the GCH resourcesconfigured in the GPU.Notes: 1) The term "available" refers to the operationalstate of the GCH resource. A GCH resource is available if it is able to carryPS traffic. A GCH resource is unavailable if it is not able to carry PS traffic, forinstance further to a PCM alarm or BSC indicates a GCH not-available.2) A GCHcorresponds here to an Ater nibble.

Trigger Condition The counter cumulates over the reporting period and over all the GCH resourcesdefined in the GPU the time during which a GCH resource is available in theGPU.For a given GCH resource, the counter starts when the resource becomesavailable and stops when the resource becomes unavailable.


Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 917 / 1256


24.2.2.1.1.6 P383a - TIME_ATERMUX_CONG

Long Name TIME_ATERMUX_CONG

Definition Atermux congestion duration (in seconds) due to a lack of Ater nibbles on theAtermux interface.

Trigger Condition The counter is:- Started: when a GPU enters the Atermux congestion state(i.e. when the number of free Ater TS on the GPU is strictly less thanN_ATER_TS_MARGIN_GPU),- Stopped: when a GPU leaves the Atermuxcongestion state (i.e. when there is at least N_ATER_TS_MARGIN_GPU freeAter TS on the GPU).


Sub Domain 2 GCH

Sub Domain 3 N/A



918 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.1.1.7 P383b - TIME_HIGH_ATER_USAGE

Long Name TIME_HIGH_ATER_USAGE

Definition Time (cumulated over a granularity period) during which the GPU remains in"high" Ater usage

Trigger Condition - started: when the percentage of used Ater nibbles, in the GPU, reachesAter_Usage_Threshold- stopped: when the percentage of used Ater nibbles, inthe GPU, drops below Ater_Usage_Threshold


Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 919 / 1256


24.2.2.1.1.8 P469 - MAX_NB_DEFICIT_GCH

Long Name MAX_NB_DEFICIT_GCH

Definition Maximum number of GCH in deficit reached in the cell.

Trigger Condition This counter gives the greatest value of the number of GCH in deficit amongall the values of GCH in deficit obtained over the granularity period.1) ForEvolium BTS:value = greatest value of the (Max(0,sum over all TRX in thecell of Average_Target_Nb_GCH - Current_Nb_GCH)) values encounteredin the granularity period.Average_Target_Nb_GCH shall be computedlike Target_Nb_GCH but by replacing: - Nb_GCH(MAX_GPRS_CS) byNb_GCH(R_AVERAGE_GPRS)" - and Nb_GCH(MAX_EGPRS_MCS) byNb_GCH(R_AVERAGE_EGPRS).The computing of Average_Target_Nb_GCHwill only differ from the one of Target_Nb_GCH for the long data" MS transfers.To simplify, it is considered that all the GCHs established for the short data MStransfers on a TRX are necessary. Hence, for the short data MS transfers,the computing of Average_Target_Nb_GCH will be similar to the one ofTarget_Nb_GCH (Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shall notbe replaced by Nb_GCH(R_AVERAGE_(E)GPRS) in the formulas).Note:Nb_GCH(R_AVERAGE_(E)GPRS) shall be computed in incremental steps: - ifR_AVERAGE_EGPRS is < 11,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS) =Nb_GCH(MCS-1) as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in therange [11,2;14,8[ kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-2)as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in the range [44,8;54,4[kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-7) as definedin RRM-PRH, - if R_AVERAGE_EGPRS is in the range [54,4;59,2[ kbps, thenNb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-8) as defined in RRM-PRH, - ifR_AVERAGE_EGPRS is >= 59,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS) =Nb_GCH(MCS-9) as defined in RRM-PRH. 2) For DRFU BTS:value = 0


Sub Domain 2 GCH

Sub Domain 3 N/A



920 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.1.1.9 P470 - CUMULATED_TIME_DEFICIT_GCH

Long Name CUMULATED_TIME_DEFICIT_GCH

Definition Cumulative time (in seconds), per cell , during which there is a deficit of GCHresources (16k channel).Note : GCH resources cover the established and thereserved GCH.

Trigger Condition The counter cumulates over the Granularity period and over all TRX of the cellthe time during which the GCH resources are in deficit.Deficit is computed asfollow : 1) For Evolium BTS:Deficit value = Max(0,sum over all TRX in the cell ofAverage_Target_Nb_GCH - Current_Nb_GCH).Average_Target_Nb_GCH shallbe computed like Target_Nb_GCH but by replacing: - Nb_GCH(MAX_GPRS_CS)by Nb_GCH(R_AVERAGE_GPRS)" - and Nb_GCH(MAX_EGPRS_MCS) byNb_GCH(R_AVERAGE_EGPRS).The computing of Average_Target_Nb_GCHwill only differ from the one of Target_Nb_GCH for the long data MS transfers.To simplify, it is considered that all the GCHs established for the short data MStransfers on a TRX are necessary. Hence, for the short data MS transfers,the computing of Average_Target_Nb_GCH will be similar to the one ofTarget_Nb_GCH (Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shall notbe replaced by Nb_GCH(R_AVERAGE_(E)GPRS) in the formulas).Note:Nb_GCH(R_AVERAGE_(E)GPRS) shall be computed in incremental steps: - ifR_AVERAGE_EGPRS is < 11,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS) =Nb_GCH(MCS-1) as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in therange [11,2;14,8[ kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-2)as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in the range [44,8;54,4[kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-7) as definedin RRM-PRH, - if R_AVERAGE_EGPRS is in the range [54,4;59,2[ kbps, thenNb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-8) as defined in RRM-PRH, - ifR_AVERAGE_EGPRS is >= 59,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS)= Nb_GCH(MCS-9) as defined in RRM-PRH. 2) For DRFU BTS:Deficit value =0Within the Granularity period, the deficit of GCH is observed. At each changeof value of the deficit (increase or decrease) the previous value of the deficit ismultiplied its time duration and summed with the cumulated time.


Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 921 / 1256


24.2.2.1.1.10 P471 - CUMULATED_TIME_EXCESS_GCH

Long Name CUMULATED_TIME_EXCESS_GCH

Definition Cumulative time (in seconds), per cell ,during which there is a excess of GCHresources (16k channel).Note : GCH resources cover the established and thereserved GCH.

Trigger Condition The counter cumulates over the Granularity period and over all TRX of the cellthe time during which the GCH resources are in excess .Excess is computed asfollow : 1) For Evolium BTS:Excess value = Max(0,sum over all TRX in the cell ofCurrent_Nb_GCH - Average_Target_Nb_GCH).Average_Target_Nb_GCH shallbe computed like Target_Nb_GCH but by replacing: - Nb_GCH(MAX_GPRS_CS)"by Nb_GCH(R_AVERAGE_GPRS)" - and Nb_GCH(MAX_EGPRS_MCS)" byNb_GCH(R_AVERAGE_EGPRS).The computing of Average_Target_Nb_GCHwill only differ from the one of Target_Nb_GCH for the long data MS transfers.To simplify, it is considered that all the GCHs established for the short data MStransfers on a TRX are necessary. Hence, for the short data MS transfers,the computing of Average_Target_Nb_GCH will be similar to the one ofTarget_Nb_GCH ("Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shallnot be replaced by Nb_GCH(R_AVERAGE_(E)GPRS) in the formulas).Note:Nb_GCH(R_AVERAGE_(E)GPRS) shall be computed in incremental steps: - ifR_AVERAGE_EGPRS is < 11,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS) =Nb_GCH(MCS-1) as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in therange [11,2;14,8[ kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-2)as defined in RRM-PRH, - if R_AVERAGE_EGPRS is in the range [44,8;54,4[kbps, then Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-7) as definedin RRM-PRH, - if R_AVERAGE_EGPRS is in the range [54,4;59,2[ kbps, thenNb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-8) as defined in RRM-PRH, - ifR_AVERAGE_EGPRS is >= 59,2 kbps, then Nb_GCH(R_AVERAGE_EGPRS) =Nb_GCH(MCS-9) as defined in RRM-PRH.2) For DRFU BTS:Excess value = 0(all the established PDCHs are needed in a DRFU BTS , as there is no M-EGCHstatistical Multiplexing).In this case , the counter value can be considered as nonsignificant.Within the Granularity period, the excess of GCH is observed. Ateach change of value of the excess (increase or decrease) the previous value ofthe deficit is multiplied its time duration and summed with the cumulated time.The time is provided in seconds with one significant value after the comma (i.e.ROUND(10x) / 10).


Sub Domain 2 GCH

Sub Domain 3 N/A



922 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.1.1.11 P474 - CUMULATED_TIME_FREE_ATER_NIBBLES

Long Name CUMULATED_TIME_FREE_ATER_NIBBLES

Definition Cumulative time (in seconds), per GPU ,during which there are free Ater nibbles.Afree Ater nibble is an Ater nibble which is neither reserved for establishment norcurrently used by a GCH.

Trigger Condition This counter can be computed by the difference between the counter P101 andthe sum over all the cells of P100c.


Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 923 / 1256


24.2.2.1.1.12 P486 - MIN_NB_FREE_ATER_NIBBLE

Long Name MIN_NB_FREE_ATER_NIBBLE

Definition Minimum number of free Ater nibbles.A free Ater nibble is an Ater nibble which isneither reserved for establishment nor currently used by a GCH.

Trigger Condition This counter gives the lowest value (not null) of the number of free Ater nibblesamong all the values of free Ater nibbles obtained over the granularity period.Atthe beginning of each granularity period, the counter is initialized with the currentnumber of free Ater nibbles.


Sub Domain 2 GCH

Sub Domain 3 N/A



924 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.2.2 LapD

24.2.2.2.1 N/A

24.2.2.2.1.1 P32 - TIME_LAPD_NOT_AVAIL

Long Name TIME_LAPD_NOT_AVAIL

Definition Time during which the LapD is not available.

Trigger Condition The time starts whenever the LapD operational state is "disabled" or theadministrative state "locked", and stops whenever the LapD operational state is"enabled" and the administrative state "unlocked".The time is provided in secondswith one significant value after the comma (ie ROUND(10x) / 10).


Sub Domain 2 LapD

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 925 / 1256


24.2.3 Gb interface

24.2.3.1 Bearer Channel

24.2.3.1.1 N/A

24.2.3.1.1.1 P33 - TIME_BEAR_CHAN_NOT_AVAIL

Long Name TIME_BEAR_CHAN_NOT_AVAIL

Definition Time during which the Bearer Channel is not available.

Trigger Condition The time starts whenever the Bearer Channel operational state is "disabled" (LMlink integrity procedure failure as described in Q933 annex A), and stops wheneverthe Bearer Channel operational state is "enabled" (LM link integrity procedurerecovery).The time is provided in seconds with one significant value after thecomma (ie ROUND(10x) / 10).



Sub Domain 3 N/A



926 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.3.2 BVC (Cell)

24.2.3.2.1 N/A

24.2.3.2.1.1 P67 - TIME_BVC_NOT_AVAIL

Long Name TIME_BVC_NOT_AVAIL

Definition Time during which the BVC (associated with one cell) is not available.

Trigger Condition The time starts whenever the PTP BVC status is NOT "Operational, started", andstops whenever the PTP BVC status is "Operational, started".The time is providedin seconds with one significant value after the comma (i.e. ROUND(10x) / 10).


Sub Domain 2 BVC (Cell)

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 927 / 1256


24.2.3.3 PVC

24.2.3.3.1 N/A

24.2.3.3.1.1 P34 - TIME_PVC_NOT_AVAIL

Long Name TIME_PVC_NOT_AVAIL

Definition Time during which the PVC is not available.

Trigger Condition The time starts whenever the PVC operational state is "disabled", and stopswhenever the PVC operational state is "enabled".The time is provided in secondswith one significant value after the comma (ie ROUND(10x) / 10).


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


928 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.3.3.1.2 P4 - TIME_PVC_CONG_FRAME_RELAY

Long Name TIME_PVC_CONG_FRAME_RELAY

Definition Time during which the PVC is congested in uplink because of Frame Relaynetwork.

Trigger Condition The time starts whenever S consecutive frames are received from the FrameRelay with the BECN bit set while the PVC is not already in congestion state.The MFS stops the transmission towards the SGSN on this PVC during a fixeddelay, after which the time is stopped.The time is provided in seconds with onesignificant value after the comma (ie ROUND(10x) / 10).


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


3BK 21255 AAAA PCZZA Ed.07 929 / 1256


24.2.3.3.1.3 P5 - TIME_PVC_CONG_LEVEL1

Long Name TIME_PVC_CONG_LEVEL1

Definition Time during which the PVC is congested at level1 in uplink.The PVC congestion ismanaged by an hysteresis mechanism with two thresholds.The PVC enters thecongestion-level1 state whenever its occupation queue exceeds PVC-LEVEL1-UPwhile the PVC was not congested.The PVC exits the congestion-level1 statewhenever its occupation queue is smaller than PVC-LEVEL1-DOWN.

Trigger Condition The time starts whenever the PVC enters the congestion-level1 state, and stopswhenever the PVC exits this state.The time is provided in seconds with onesignificant value after the comma (ie ROUND(10x) / 10).


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


930 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.3.4 SGSN_IP_NSVC

24.2.3.4.1 N/A

24.2.3.4.1.1 P34a - TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP

Long Name TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP

Definition Time during which the SGSN IP endpoint is not available.

Trigger Condition The time starts whenever the SGSN IP endpoint operational state is "disabled",and stops whenever the SGSN IP endpoint operational state is "enabled".


Sub Domain 2 SGSN_IP_NSVC

Sub Domain 3 N/A

Measured Object SGSN_IP_NSVC


3BK 21255 AAAA PCZZA Ed.07 931 / 1256



24.2.4.1 DL LLC data flow

24.2.4.1.1 N/A

24.2.4.1.1.1 P531b_1 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1

Definition First class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 1.EGPRS LLC throughput class 1is defined by : EGPRS_LLC_throughput_THR_0<= LLC throughput <EGPRS_LLC_throughput_THR_1EGPRS_LLC_throughput_THR_0 = 0 kbit/s

Trigger Condition During MS context lifetime , the DL LLC PDU size sent in the TBF established inEGPRS mode and their transfer duration are cumulated.When the MS context isdeleted , the DL LLC throughput (cumulated DL LLC PDU size/cumulated transferduration) is estimated and the suitable class of the distribution is incremented byone.Note : - Only DL LLC PDU whose traffic type is data are taken into account.-The transfer duration of one (or a set of DL LLC PDU) is estimated by RRM whena LLC PDU (or a set of DL LLC PDU) have been correctly received by the MS .


Sub Domain 2 DL LLC data flow

Sub Domain 3 N/A



932 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Tenth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 10.EGPRS LLC throughput class 10is defined by : EGPRS_LLC_throughput_THR_9<= LLC throughput <EGPRS_LLC_throughput_THR_10




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 933 / 1256




Definition Eleventh class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 11.EGPRS LLC throughput class 11is defined by : EGPRS_LLC_throughput_THR_10 <= LLC throughput <EGPRS_LLC_throughput_THR_11




Sub Domain 3 N/A



934 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 2.EGPRS LLC throughput class 2is defined by : EGPRS_LLC_throughput_THR_1<= LLC throughput <EGPRS_LLC_throughput_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 935 / 1256




Definition Fifth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 5.EGPRS LLC throughput class 5is defined by : EGPRS_LLC_throughput_THR_4<= LLC throughput <EGPRS_LLC_throughput_THR_5




Sub Domain 3 N/A



936 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 6.EGPRS LLC throughput class 6is defined by : EGPRS_LLC_throughput_THR_5<= LLC throughput <EGPRS_LLC_throughput_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 937 / 1256




Definition Eighth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 8.EGPRS LLC throughput class 8is defined by : EGPRS_LLC_throughput_THR_7<= LLC throughput <EGPRS_LLC_throughput_THR_8




Sub Domain 3 N/A



938 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.1.1.8 P532b_1 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1

Definition First class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 1.GPRS LLC throughput class 1is defined by : GPRS_LLC_throughput_THR_0<= LLC throughput <GPRS_LLC_throughput_THR_1GPRS_LLC_throughput_THR_0 = 0 kbit/s

Trigger Condition During MS context lifetime , the DL LLC PDU size sent in the TBF established inGPRS mode and their transfer duration are cumulated.When the MS context isdeleted , the DL LLC throughput (cumulated DL LLC PDU size/cumulated transferduration) is estimated and the suitable class of the distribution is incremented byone.Note : - Only DL LLC PDU whose traffic type is data are taken into account.-The transfer duration of one (or a set of DL LLC PDU) is estimated by RRM whena LLC PDU (or a set of DL LLC PDU) have been correctly received by the MS .



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 939 / 1256




Definition Tenth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 10.GPRS LLC throughput class 10is defined by : GPRS_LLC_throughput_THR_9<= LLC throughput <GPRS_LLC_throughput_THR_10




Sub Domain 3 N/A



940 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 2.GPRS LLC throughput class 2is defined by : GPRS_LLC_throughput_THR_1<= LLC throughput <GPRS_LLC_throughput_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 941 / 1256




Definition Third class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 3.GPRS LLC throughput class 3is defined by : GPRS_LLC_throughput_THR_2<= LLC throughput <GPRS_LLC_throughput_THR_3




Sub Domain 3 N/A



942 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fourth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 4.GPRS LLC throughput class 4is defined by : GPRS_LLC_throughput_THR_3<= LLC throughput <GPRS_LLC_throughput_THR_4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 943 / 1256




Definition Fifth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 5.GPRS LLC throughput class 5is defined by : GPRS_LLC_throughput_THR_4<= LLC throughput <GPRS_LLC_throughput_THR_5




Sub Domain 3 N/A



944 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 6.GPRS LLC throughput class 6is defined by : GPRS_LLC_throughput_THR_5<= LLC throughput <GPRS_LLC_throughput_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 945 / 1256




Definition Seventh class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 7.GPRS LLC throughput class 7is defined by : GPRS_LLC_throughput_THR_6<= LLC throughput <GPRS_LLC_throughput_THR_7




Sub Domain 3 N/A



946 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 8.GPRS LLC throughput class 8is defined by : GPRS_LLC_throughput_THR_7<= LLC throughput <GPRS_LLC_throughput_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 947 / 1256




Definition Ninth class of the distribution on number of GPRS DL LLC throughput.Itcontains :1) number of GPRS DL LLC throughput whose throughputis in GPRS LLC throughput class 9.GPRS LLC throughput class 9is defined by : GPRS_LLC_throughput_THR_8<= LLC throughput <GPRS_LLC_throughput_THR_9




Sub Domain 3 N/A



948 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.2 DL TBF duration

24.2.4.2.1 N/A

24.2.4.2.1.1 P16 - CUMULATED_OVERALL_DL_CONNECTION_TIME

Long Name CUMULATED_OVERALL_DL_CONNECTION_TIME

Definition Cumulated overall time (i.e. active and delayed) of DL TBF connections.

Trigger Condition The counter measures the cumulated time duration of all DL TBF connections inthe cell over the Granularity period. Active as well as delayed release periodsare taken into account.Each time duration starts upon reception from the MobileStation of 04.60 PACKET CONTROL ACKNOWLEDGMENT on PACCH/U duringthe DL TBF establishment procedure (either in response to a PACKET DOWNLINKASSIGNMENT or PACKET TIMESLOT RECONFIGURE, whichever is applicable).In case of normal DL TBF releases, the counter stops for a given DL TBF uponreception of the reply to the 04.60 RLC DATA BLOCK (FBI=1, polling) sent by theMFS for the last RLC block to send, i.e. 04.60 (EGPRS) PACKET DOWNLINKACK/NACK from the MS and there is no retransmission required, if the TBF was inRLC acknowledged mode or 04.60 PACKET CONTROL ACK if the TBF was inRLC unacknowledged mode. This last RLC data block is the last actual data blockof the TBF, i.e. the last useful RLC data block for a TBF in normal release mode,or the last dummy RLC data block for a TBF in delayed release mode.In case ofabnormal DL TBF releases during active phase (i.e. not delayed phase), thecounter stops for a given DL TBF:- at the time when the RRM layer has receivedthe acknowledgment of the last DL LLC PDU (in case of RLC acknowledgedmode), or,- at the time when the RRM layer has sent the last DL LLC PDU tothe RLC layer (in case of RLC unacknowledged mode).In case of abnormal DLTBF releases during delayed phase, the counter stops for a given DL TBF at thetime when the RRM layer has been informed that the DL TBF has entered thedelayed phase.The case the DL TBF is released due to a NC cell reselection ismanaged as an abnormal DL TBF release.The time is provided in seconds withone significant value after the comma (I.e. ROUND(10x)/10).The DL TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the DL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.


Sub Domain 2 DL TBF duration

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 949 / 1256


24.2.4.2.1.2 P409 -CUMULATED_TIME_DL_BIASED_AND_OPTIMAL_DL_ALLOCATION

Long Name CUMULATED_TIME_DL_BIASED_AND_OPTIMAL_DL_ALLOCATION

Definition Cumulated time during which downlink TBFs are granted the maximum number ofPDCHs they need and the corresponding MSs are engaged in downlink-biasedtransfers.

Trigger Condition The counter is incremented by the duration during which all downlink TBFs of a cellwhich serve a downlink-biased transfer are granted as many timeslots as needed.The results are cumulated over the granularity period.When determining thenumber of timeslots needed by the mobile station for the DL TBF, the MFS takesinto account:i) The MS multislot class (or the MS high multislot class if allowed inthe cell). The GPRS or EGPRS (possibly high) multislot class is used dependingon the DL TBF establishment mode (in GPRS mode or EGPRS mode).ii) The biasof the transfer. For instance, for an MS belonging to multislot class 6, for whichthe transfer is deemed downlink-biased, the requested number of timeslots indownlink is 3 and not 2. iii) The value of the "traffic type" (signalling or data) ofthis MS. If the traffic type is signalling, only one PDCH is required. However, the"optimality" may change during the life of the TBF, due to change in the traffic typefrom signalling to data.In case of abnormal DL TBF releases during active phase(i.e. not delayed phase), the counter stops for a given DL TBF:- at the time whenthe RRM layer has received the acknowledgment of the last DL LLC PDU (in caseof RLC acknowledged mode), or,- at the time when the RRM layer has sent thelast DL LLC PDU to the RLC layer (in case of RLC unacknowledged mode).Incase of abnormal DL TBF releases during delayed phase, the counter stops for agiven DL TBF at the time when the RRM layer has been informed that the DL TBFhas entered the delayed phase.The case the DL TBF is released due to a NC cellreselection is managed as an abnormal DL TBF release.The time is provided inseconds with one significant value after the comma (i.e. ROUND(10x) / 10).TheDL TBFs still established at the expiration of the granularity period are not takeninto account in the cumulated value. They are taken into account only when the DLTBFs are released. In case of traffic profile including a lot of "very long" TBF, thismay lead to a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A


External Comment - when the traffic type changes from "signalling" to "data" , the optimality isre-assessed. - Once the traffic type is set to data, it can not be changed tosignalling, whatever the T-bit value.

950 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.2.1.3 P411 - CUMULATED_TIME_DL_BIASED_DL_TBF

Long Name CUMULATED_TIME_DL_BIASED_DL_TBF

Definition Cumulated time during which MSs are engaged in downlink-biased transfers andthere is a DL TBF serving the MS.

Trigger Condition The counter is incremented by the duration during which MSs are deemed in adownlink-biased transfer. Only the time during which there is a DL TBF servingthe MS is taken into account.In case of abnormal DL TBF releases during activephase (i.e. not delayed phase), the counter stops for a given DL TBF:- at the timewhen the RRM layer has received the acknowledgment of the last DL LLC PDU (incase of RLC acknowledged mode), or,- at the time when the RRM layer has sentthe last DL LLC PDU to the RLC layer (in case of RLC unacknowledged mode).Incase of abnormal DL TBF releases during delayed phase, the counter stops for agiven DL TBF at the time when the RRM layer has been informed that the DL TBFhas entered the delayed phase.The case the DL TBF is released due to a NC cellreselection is managed as an abnormal DL TBF release.The time is provided inseconds with one significant value after the comma (i.e. ROUND(10x) / 10).TheDL biased TBFs still established at the expiration of the granularity period arenot taken into account in the cumulated value. They are taken into account onlywhen the DL TBFs are released. In case of traffic profile including a lot of "verylong" TBF, this may lead to a temporary under-estimated (then over-estimated)cumulated value.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 951 / 1256


24.2.4.2.1.4 P419 - CUMULATED_TIME_DL_BIASED

Long Name CUMULATED_TIME_DL_BIASED

Definition Cumulated time during which MSs are engaged in downlink-biased transfers.

Trigger Condition The counter is incremented by the duration during which MSs are deemed in adownlink-biased transfer.When an MS context is created :If it is downlink-biased,then the timer is started for that MS. When the bias changes to uplink, then thetimer is stopped. When it changes back to downlink, the timer is restarted.If it isuplink-biased, then the timer is started for that MS when the bias changes todownlink. When it changes back to uplink, then the timer is stopped.When thesession ends, the timer for the MS is cumulated to P419.Note that when the MScontext is deemed downlink-biased and T3192 is running, even if there is noon-going TBF, that duration shall be taken into account in this timer.In case theMS has no on-going UL TBF and an abnormal DL TBF release is detected duringactive phase (i.e. not delayed phase), the counter stops for the given MS:- at thetime when the RRM layer has received the acknowledgment of the last DL LLCPDU (in case of RLC acknowledged mode), or,- at the time when the RRM layerhas sent the last DL LLC PDU to the RLC layer (in case of RLC unacknowledgedmode).In case the MS has no on-going UL TBF and an abnormal DL TBF releaseis detected during delayed phase, the counter stops for the given MS at the timewhen the RRM layer has been informed that the DL TBF has entered the delayedphase.In case the MS has no on-going DL TBF and an abnormal UL TBF releaseis detected, the counter stops for the given MS at the time when the RRM layerhas received the last UL LLC PDU.The case the DL TBF is released due to aNC cell reselection is managed as an abnormal DL TBF release. Similarly, thecase the UL TBF is released due to a NC cell reselection is managed as anabnormal UL TBF release.The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).The MSs still DL biased at theexpiration of the granularity period are not taken into account in the cumulatedvalue. They are taken into account only when the biais change to UL. In case oftraffic profile including a lot of "very long" TBF with no bias changes, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



952 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.2.1.5 P453b_1 - DISTRIB_DL_TBF_DURATION_1

Long Name DISTRIB_DL_TBF_DURATION_1

Definition First cell of the duration on DL TBF duration.It contains :1) numberof DL TBFs whose duration is in duration band 1Duration band1 is defined by : PD_DL_TBF_DURATION_THR_0<= duration <PD_DL_TBF_DURATION_THR_1PD_DL_TBF_DURATION_THR_0 = 0 sec

Trigger Condition DL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLCunacknowledged mode are taken into account. Only the active phase of the TBFis taken into account.The duration is measured as for P52a, P52b, P52c, P52d.



Sub Domain 3 N/A

Measured Object DistCell


3BK 21255 AAAA PCZZA Ed.07 953 / 1256




Definition Tenth cell of the duration on DL TBF duration.It contains :1) numberof DL TBFs whose duration is in duration band 10Duration band10 is defined by : PD_DL_TBF_DURATION_THR_9<= duration <PD_DL_TBF_DURATION_THR_10PD_DL_TBF_DURATION_THR_10 = 16384

Trigger Condition DL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLCunacknowledged mode are taken into account. Only the active phase of theTBF is taken into account.The duration is measured as for P52a, P52b, P52c,P52d.Whenever a TBF duration exceeds PD_DL_TBF_DURATION_THR_10,then it is not taken into account.



Sub Domain 3 N/A



954 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 2Duration band 2 is defined by :PD_DL_TBF_DURATION_THR_1<= duration < PD_DL_TBF_DURATION_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 955 / 1256




Definition Third cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 3Duration band 3 is defined by :PD_DL_TBF_DURATION_THR_2<= duration < PD_DL_TBF_DURATION_THR_3




Sub Domain 3 N/A



956 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fourth cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 4Duration band 4 is defined by :PD_DL_TBF_DURATION_THR_3<= duration < PD_DL_TBF_DURATION_THR_4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 957 / 1256




Definition Fifth cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 5Duration band 5 is defined by :PD_DL_TBF_DURATION_THR_4<= duration < PD_DL_TBF_DURATION_THR_5




Sub Domain 3 N/A



958 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 6Duration band 6 is defined by :PD_DL_TBF_DURATION_THR_5<= duration < PD_DL_TBF_DURATION_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 959 / 1256




Definition Seventh cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 7.Duration band 7 is defined by :PD_DL_TBF_DURATION_THR_6<= duration < PD_DL_TBF_DURATION_THR_7




Sub Domain 3 N/A



960 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 8Duration band 8 is defined by :PD_DL_TBF_DURATION_THR_7<= duration < PD_DL_TBF_DURATION_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 961 / 1256




Definition Ninth cell of the duration on DL TBF duration.It contains :1) number of DLTBFs whose duration is in duration band 9Duration band 9 is defined by :PD_DL_TBF_DURATION_THR_8<= duration < PD_DL_TBF_DURATION_THR_9




Sub Domain 3 N/A



962 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.2.1.15 P52a - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_ACK

Long Name CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_ACK

Definition Cumulated time duration of all active DL TBFs established in GPRS mode andRLC acknowledged modeNote: An active DL TBF connection is a DL TBF not indelayed release state.

Trigger Condition The counter measures the cumulated time duration of all active DL TBFsestablished in GPRS mode and in RLC acknowledged mode in the cell over thegranularity period.For a given DL TBF, the counter starts at the establishmentof the DL TBF in GPRS mode and RLC acknowledged mode upon the receiptfrom the Mobile Station of 04.60 a PACKET CONTROL ACKNOWLEDGEMENTmessage on PACCH/U during the DL TBF establishment procedure.Once the DLTBF enters the delayed release state, the counter is suspended upon the receiptfrom the mobile station of an 04.60 PACKET DOWNLINK ACK/NACK messageacknowledging the correct reception of all the useful LLC PDUs. The counter isresumed once the TBF becomes active again, i.e. when a new downlink LLC PDUis sent to the Mobile Station.In case of normal DL TBF releases, the counter stopsfor a given DL TBF upon the receipt of the RLC indication indicating that the TBFhas entered the delayed phase. The DL TBF enters the delayed phase upon thereceipt of the acknowledgment of the last useful RLC data block with (FBI = 0 anda polling indication).In case of abnormal DL TBF releases, the counter stops for agiven DL TBF at the time when the RRM layer has received the acknowledgmentof the last DL LLC PDU. The case the DL TBF is released due to a NC cellreselection is managed as an abnormal DL TBF release.The time is provided inseconds with one significant value after the comma (i.e. ROUND(10x)/10).The DLTBFs still established at the expiration of the granularity period are not taken intoaccount in the cumulated value. They are taken into account only when the DLTBFs are released. In case of traffic profile including a lot of "very long" TBF, thismay lead to a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 963 / 1256


24.2.4.2.1.16 P52b - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_NACK

Long Name CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_NACK

Definition Cumulated time duration of all active DL TBFs established in GPRS mode andRLC unacknowledged modeNote: An active DL TBF connection is a DL TBFnot in delayed release state.

Trigger Condition The counter measures the cumulated time duration of all active DL TBFsestablished in GPRS mode and in RLC unacknowledged mode in the cell overthe granularity period.For a given DL TBF, the counter starts at the establishmentof the DL TBF in GPRS mode and RLC unacknowledged mode upon the receiptfrom the Mobile Station of 04.60 a PACKET CONTROL ACKNOWLEDGEMENTmessage on PACCH/U during the DL TBF establishment procedure.Once the DLTBF enters the delayed release state, the counter is suspended upon receptionfrom the mobile station of an 04.60 PACKET DOWNLINK ACK/NACK messageacknowledging the reception of the first RLC data block of the last useful DL LLCPDUs. The counter is resumed once the TBF becomes active again, i.e. when anew downlink LLC PDU is sent to the Mobile Station.In case of normal DL TBFreleases, the counter stops for a given TBF upon the receipt of the RLC indicationindicating that the TBF has entered the delayed phase. The DL TBF enters thedelayed phase at the sending of the last useful RLC data block with (FBI = 0 and apolling indication).In case of abnormal DL TBF releases, the counter stops for agiven DL TBF at the time when the RRM layer has sent the last DL LLC PDU tothe RLC layer. The case the DL TBF is released due to a NC cell reselection ismanaged as an abnormal DL TBF release.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x)/10).The DL TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the DL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



964 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.2.1.17 P52c - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_ACK

Long Name CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_ACK

Definition Cumulated time duration of all active DL TBFs established in EGPRS mode andRLC acknowledged mode.Note: An active DL TBF connection is a DL TBF not indelayed release state.

Trigger Condition The counter measures the cumulated time duration of all active DL TBFsestablished in EGPRS mode and in RLC acknowledged mode in the cell over thegranularity period.For a given DL TBF, the counter starts at the establishment ofthe DL TBF in EGPRS mode and RLC acknowledged mode upon the receiptfrom the Mobile Station of 04.60 a PACKET CONTROL ACKNOWLEDGEMENTmessage on PACCH/U during the DL TBF establishment procedure.Once the DLTBF enters the delayed release state, the counter is suspended upon the receiptfrom the mobile station of an 04.60 EGPRS PACKET DOWNLINK ACK/NACKmessage acknowledging the receipt of first DL RLC data block of the last DL LLCPDU. The counter is resumed once the TBF becomes active again, i.e. when anew downlink LLC PDU is sent to the Mobile Station.In case of normal DL TBFreleases, the counter stops for a given DL TBF upon the receipt of the RLCindication indicating that the TBF has entered the delayed phase. The DL TBFenters the delayed phase upon the receipt of the acknowledgment of the lastuseful RLC data block with (FBI = 0 and a polling indication).In case of abnormalDL TBF releases, the counter stops for a given DL TBF at the time when the RRMlayer has received the acknowledgment of the last DL LLC PDU. The case theDL TBF is released due to a NC cell reselection is managed as an abnormal DLTBF release.The time is provided in seconds with one significant value after thecomma (i.e. ROUND(10x)/10).The DL TBFs still established at the expiration ofthe granularity period are not taken into account in the cumulated value. They aretaken into account only when the DL TBFs are released. In case of traffic profileincluding a lot of "very long" TBF, this may lead to a temporary under-estimated(then over-estimated) cumulated value.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 965 / 1256


24.2.4.2.1.18 P52d - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_NACK

Long Name CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_NACK

Definition Cumulated time duration of all active DL TBFs established in EGPRS mode andRLC unacknowledged mode.Note: An active DL TBF connection is a DL TBFnot in delayed release state.

Trigger Condition The counter measures the cumulated time duration of all active DL TBFsestablished in EGPRS mode and in RLC unacknowledged mode in the cell overthe granularity period.For a given DL TBF, the counter starts at the establishmentof the DL TBF in EGPRS mode and RLC unacknowledged mode upon the receiptfrom the Mobile Station of 04.60 a PACKET CONTROL ACKNOWLEDGEMENTmessage on PACCH/U during the DL TBF establishment procedure.Once the DLTBF enters the delayed release state, the counter is suspended upon the receiptfrom the mobile station of an 04.60 EGPRS PACKET DOWNLINK ACK/NACKmessage acknowledging the reception of the first RLC data block of the last usefulDL LLC PDUs. The counter is resumed once the TBF becomes active again, i.e.when a new downlink LLC PDU is sent to the Mobile Station.In case of normalDL TBF releases, the counter stops for a given TBF upon the receipt of the RLCindication indicating that the TBF has entered the delayed phase. The DL TBFenters the delayed phase at the sending of the last useful RLC data block with (FBI= 0 and a polling indication).In case of abnormal DL TBF releases, the counterstops for a given DL TBF at the time when the RRM layer has sent the last DLLLC PDU to the RLC layer. The case the DL TBF is released due to a NC cellreselection is managed as an abnormal DL TBF release.The time is provided inseconds with one significant value after the comma (i.e. ROUND(10x)/10).The DLTBFs still established at the expiration of the granularity period are not taken intoaccount in the cumulated value. They are taken into account only when the DLTBFs are released. In case of traffic profile including a lot of "very long" TBF, thismay lead to a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



966 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.3 DL TBF LLC volume

24.2.4.3.1 N/A

24.2.4.3.1.1 P454a_3 - DISTRIB_UL_TBF_VOLUME_3

Long Name DISTRIB_UL_TBF_VOLUME_3

Definition Third cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 3.LLCvolume band 1 is defined by : PD_UL_TBF_VOLUME_THR_2<= LLC volume <PD_UL_TBF_VOLUME_THR_3

Trigger Condition TBF in GPRS and EGPRS mode, in RLC acknowledged and RLC unacknowledgedmode are taken into account.The volume is calculated as in P44.


Sub Domain 2 DL TBF LLC volume

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 967 / 1256




Definition Fourth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 4.LLCvolume band 1 is defined by : PD_UL_TBF_VOLUME_THR_3<= LLC volume <PD_UL_TBF_VOLUME_THR_4




Sub Domain 3 N/A



968 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.3.1.3 P454b_1 - DISTRIB_DL_TBF_VOLUME_1

Long Name DISTRIB_DL_TBF_VOLUME_1

Definition First cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 1.LLCvolume band 1 is defined by : PD_DL_TBF_VOLUME_THR_0<= LLC volume <PD_DL_TBF_VOLUME_THR_1PD_DL_TBF_VOLUME_THR_0 = 0 byte




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 969 / 1256




Definition Tenth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 10.LLCvolume band 1 is defined by : PD_DL_TBF_VOLUME_THR_9<= LLC volume <PD_DL_TBF_VOLUME_THR_10PD_DL_TBF_VOLUME_THR_10 = 100 000000 bytes

Trigger Condition TBF in GPRS and EGPRS mode, in RLC acknowledged and RLC unacknowledgedmode are taken into account.The volume is calculated as in P43.Whenever aTBF volume exceeds PD_DL_TBF_VOLUME_THR_10, then it is not taken intoaccount.



Sub Domain 3 N/A



970 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 2.LLCvolume band 2 is defined by : PD_DL_TBF_VOLUME_THR_1<= LLC volume <PD_DL_TBF_VOLUME_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 971 / 1256




Definition Third cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 3.LLCvolume band 3 is defined by : PD_DL_TBF_VOLUME_THR_2<= LLC volume <PD_DL_TBF_VOLUME_THR_3




Sub Domain 3 N/A



972 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fourth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 4.LLCvolume band 4 is defined by : PD_DL_TBF_VOLUME_THR_3<= LLC volume <PD_DL_TBF_VOLUME_THR_4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 973 / 1256




Definition Fifth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 5.LLCvolume band 5 is defined by : PD_DL_TBF_VOLUME_THR_4<= LLC volume <PD_DL_TBF_VOLUME_THR_5




Sub Domain 3 N/A



974 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 6.LLCvolume band 6 is defined by : PD_DL_TBF_VOLUME_THR_5<= LLC volume <PD_DL_TBF_VOLUME_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 975 / 1256




Definition Seventh cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 7.LLCvolume band 7 is defined by : PD_DL_TBF_VOLUME_THR_6<= LLC volume <PD_DL_TBF_VOLUME_THR_7




Sub Domain 3 N/A



976 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 8.LLCvolume band 1 is defined by : PD_DL_TBF_VOLUME_THR_7<= LLC volume <PD_DL_TBF_VOLUME_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 977 / 1256




Definition Ninth cell of the distribution on volume of DL TBF.It contains :1) number of DLTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 9.LLCvolume band 9 is defined by : PD_DL_TBF_VOLUME_THR_8<= LLC volume <PD_DL_TBF_VOLUME_THR_9




Sub Domain 3 N/A



978 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4 PDCH

24.2.4.4.1 N/A

24.2.4.4.1.1 P13 - TIME_DL_PDCH_CONG

Long Name TIME_DL_PDCH_CONG

Definition Time during which the DL TBF establishment is impossible due to congestion(no radio resource in the MFS).

Trigger Condition The time starts whenever:1) No slave PDCH resource is available in theMFS, ie: - the maximum number of MSs per PDCH in downlink (set byMAX_DL_TBF_SPDCH) is reached for all the slave PDCHs of the cell, and - allMAX_SPDCH_LIMIT PDCHs granted by the BSC are used.OR2) no resources(TAI, TFI, PDCH) are available at MFS side to serve the mobile.The time stops assoon as the above conditions are false.The time is provided in seconds with onesignificant value after the comma (i.e. ROUND(10x) / 10).


Sub Domain 2 PDCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 979 / 1256


24.2.4.4.1.2 P26 - TIME_UL_PDCH_CONG

Long Name TIME_UL_PDCH_CONG

Definition Time during which the UL TBF establishment is impossible due to congestion(no radio resource in the MFS).

Trigger Condition The time starts whenever:1) No slave PDCH resource are available inthe BSC, i.e.:- the maximum number of MSs per PDCH in uplink (set byMAX_UL_TBF_SPDCH) is reached for all the slave PDCHs of the cell, and - allMAX_SPDCH_LIMIT PDCHs granted by the BSC are used.OR2) no resources(TAI, TFI, PDCH) are available at MFS side to serve the mobile.The time stops assoon as the above conditions are false.The time is provided in seconds with onesignificant value after the comma (i.e. ROUND(10x) / 10).


Sub Domain 2 PDCH

Sub Domain 3 N/A



980 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4.1.3 P38b - CUMULATED_TIME_PDCH_USED

Long Name CUMULATED_TIME_PDCH_USED

Definition Cumulated time during which the slave PDCHs carry at least one UL or DL TBF(TBF established in GPRS mode or EGPRS mode).

Trigger Condition The timer is the sum of all unit times per slave PDCH during which the a slavePDCH supported carries at least one UL or DL TBF (TBF established in GPRSmode or EGPRS mode).Note 1: For downlink TBF, active , delayed phases aretaken into account.Note 2: The time is provided in seconds with one significantdigit after the comma (i.e. ROUND(10x) / 10).Note 3 : For uplink TBF, active ,delayed final PUAN , extended phases are taken into account.


Sub Domain 2 PDCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 981 / 1256


24.2.4.4.1.4 P38c - CUMULATED_TIME_PDCH_USED_EGPRS

Long Name CUMULATED_TIME_PDCH_USED_EGPRS

Definition Cumulated time during which the slave PDCHs carry at least one UL or DL TBFestablished in EGPRS mode.

Trigger Condition The timer is the sum of all unit times per slave PDCH during which the slavePDCH supported at least one UL or DL TBF established in EGPRS mode.The timeis provided in seconds with one significant digit after the comma (i.e. ROUND(10x)/ 10).


Sub Domain 2 PDCH

Sub Domain 3 N/A



982 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4.1.5 P38e - CUMULATED_TIME_PDCH_USED_DL_CELL

Long Name CUMULATED_TIME_PDCH_USED_DL_CELL

Definition Cumulated time during which a PDCH is used by at least one DL TBF (in GPRS orEGPRS mode), cumulated over all the PDCHs of the cell.

Trigger Condition The timer is the sum of all unit times per slave PDCH during which the slavePDCH supported at least one DL TBF (established in GPRS mode or EGPRSmode).Note: Only Active, delayed, extended phases of the TBF are taken intoaccount.The time is provided in seconds with one significant value after thecomma (i.e. ROUND(10x) / 10).


Sub Domain 2 PDCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 983 / 1256


24.2.4.4.1.6 P38f - CUMULATED_TIME_PDCH_USED_UL_CELL

Long Name CUMULATED_TIME_PDCH_USED_UL_CELL

Definition Cumulated time during which a PDCH is used by at least one UL TBF (in GPRS orEGPRS mode), cumulated over all the PDCHs of the cell.

Trigger Condition The timer is the sum of all unit times per slave PDCH during which the slavePDCH supported at least one UL TBF (established in GPRS mode or EGPRSmode).Note: Only Active, delayed, extended phases of the TBF are taken intoaccount.The time is provided in seconds with one significant value after thecomma (i.e. ROUND(10x) / 10).


Sub Domain 2 PDCH

Sub Domain 3 N/A



984 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4.1.7 P414bis - CUMULATED_TIME_ALLOCATED_SPDCH

Long Name CUMULATED_TIME_ALLOCATED_SPDCH

Definition This counter integrates over time the values of the allocated SPDCH during thewhole granularity period.

Trigger Condition When the granularity period starts, the counter is reset to 0. The current valueof SPDCHs allocated to the MFS by the BSC is multiplied by the duration untilthe next allocated SPDCH update is received from the BSC (I.e. reception ofa (BSCGP) RADIO RESOURCE ALLOCATION INDICATION indicating a newnumber of SPDCHs allocated to the MFS). Then the new value of allocatedSPDCH is multiplied by the duration until the next allocated SPDCH update , andso on.The counter is the sum of all the computed values.


Sub Domain 2 PDCH

Sub Domain 3 N/A


External Comment Replaces P414 (B8 counter).

3BK 21255 AAAA PCZZA Ed.07 985 / 1256


24.2.4.4.1.8 P415bis - MAX_OF_ALLOCATED_SPDCH

Long Name MAX_OF_ALLOCATED_SPDCH

Definition This counter gives the maximum value of allocated SPDCH during the wholegranularity period.

Trigger Condition During the granularity period , at each receipt of the RADIO RESOURCEALLOCATION INDICATION


Sub Domain 2 PDCH

Sub Domain 3 N/A



986 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4.1.9 P416bis - MIN_OF_ALLOCATED_SPDCH

Long Name MIN_OF_ALLOCATED_SPDCH

Definition This counter gives the minimum value of allocated SPDCH during the wholegranularity period.

Trigger Condition During the granularity period , at each receipt of the RADIO RESOURCEALLOCATION INDICATION the value of allocated SPDCH is stored.At the endof the granularity period, the minimum value of all the stored values is usedto update the counter.


Sub Domain 2 PDCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 987 / 1256


24.2.4.4.1.10 P417 - NB_PREEMPTED_PDCH

Long Name NB_PREEMPTED_PDCH

Definition This counter measures the overall number of slave PDCHs which have beenreleased after having been marked by the soft pre-emption procedure in the cellover the granularity period.

Trigger Condition Each time the MFS receives a BSCGP RR ALLOCATION INDICATION messagefrom the BSC with a SPDCHs Allocation bitmap containing less PDCHs thanthe current number of allocated slave PDCHs, the MFS has to mark the slavePDCHs in excess as soft pre-empted. The counter is incremented by one eachtime a slave PDCH is released due to pre-emption (i.e. it is incremented alsowhen a non-marked PDCH gets released and allows unmarking another PDCH).Note that even if a slave PDCH has no TBF at the time of soft pre-emption andtherefore the PDCH is given back immediately to the BSC, it shall be consideredin the calculation.


Sub Domain 2 PDCH

Sub Domain 3 N/A



988 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.4.1.11 P495 - MAX_NB_USED_SPDCH_CELL

Long Name MAX_NB_USED_SPDCH_CELL

Definition Maximum number of used slave PDCHs in the cell.Note: An used PDCH is aPDCH that carries at least one UL or DL TBF.

Trigger Condition An internal counter tracks the current number of used slave PDCH in the cell.This internal counter is - Incremented when one UL or DL TBF is carried bya salve PDCH. - Decremented when no UL or DL TBF is carried by a slavePDCH.Whenever this internal counter is incremented, its new value is comparedwith the stored maximum number of used PDCHs in the cell. If this value is higherthan the stored maximum value, the value becomes the new maximum.The masterPDCHs are excluded from this counter.


Sub Domain 2 PDCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 989 / 1256


24.2.4.4.1.12 P496 - MIN_NB_USED_SPDCH_CELL

Long Name MIN_NB_USED_SPDCH_CELL

Definition Minimum number of used slave PDCHs in the Note: An used PDCH is a PDCHthat carries at least one UL or DL TBF.

Trigger Condition An internal counter tracks the current number of used slave PDCH in the cell.This internal counter is - Incremented when one UL or DL TBF is carried bya salve PDCH. - Decremented when no UL or DL TBF is carried by a slavePDCH.Whenever this internal counter is decremented, its new value is comparedwith the stored minimum number of used PDCHs in the cell. If this value is lowerthan the stored minimum value, the value becomes the new minimum.


Sub Domain 2 PDCH

Sub Domain 3 N/A



990 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.5 PDCH allocation for DL TBF

24.2.4.5.1 N/A

24.2.4.5.1.1 P160 - NB_DL_TBF_1_succ

Long Name NB_DL_TBF_1_succ

Definition Number of downlink TBF establishment requests ( 1 slot allocated) which aresatisfied at once by the initial allocation.

Trigger Condition Whenever the MFS allocates 1 PDCH for a DL TBF in case of an MS requesting1 (or several) slot DL. When determining the number of timeslots requestedby the mobile station for the DL TBF, the MFS takes into account:i) The MSmultislot class. The GPRS or EGPRS multislot class is used depending on theDL TBF establishment mode (in GPRS mode or EGPRS mode).ii) The bias of thetransfer.iii) The value of the T-bit indicated in the DL LLC PDU triggering the DLTBF establishment. If the T-bit is set to signalling, only one PDCH is required.


Sub Domain 2 PDCH allocation for DL TBF

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 991 / 1256


24.2.4.5.1.2 P162 - NB_DL_TBF_2_3_succ

Long Name NB_DL_TBF_2_3_succ

Definition Number of downlink TBF establishment requests requesting 2 or 3 slots whichare totally satisfied at once by the initial allocation.

Trigger Condition Whenever the MFS allocates exactly 2 PDCHs (or 3 PDCHs) for a DL TBF in caseof an MS requesting 2 slots DL (or 3 slots DL).When determining the number oftimeslots requested by the mobile station for the DL TBF, the MFS takes intoaccount:i) The MS multislot class. The GPRS or EGPRS multislot class is useddepending on the DL TBF establishment mode (in GPRS mode or EGPRSmode).ii) The bias of the transfer. For instance, for an MS belonging to multislotclass 10, for which the transfer is deemed uplink-biased, the requested number oftimeslots in downlink is 3 and not 4.iii) The value of the T-bit indicated in the DLLLC PDU triggering the DL TBF establishment. If the T-bit is set to signalling, onlyone PDCH is required.



Sub Domain 3 N/A



992 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.5.1.3 P164 - NB_DL_TBF_4_5_succ

Long Name NB_DL_TBF_4_5_succ

Definition Number of downlink TBF establishment requests requesting 4 or 5 slots whichare totally satisfied at once by the initial allocation.

Trigger Condition Whenever the system MFS allocates exactly 4 PDCHs (or 5 PDCHs) for a DL TBFin case of an MS requesting 4 slots DL (or 5 slots DL).When determining thenumber of timeslots requested by the mobile station for the DL TBF, the MFS takesinto account:i) The MS multislot class (or the MS high multislot class if allowed inthe cell). The GPRS or EGPRS (possibly high) multislot class is used dependingon the DL TBF establishment mode (in GPRS mode or EGPRS mode).ii) The biasof the transfer. For instance, for an MS belonging to multislot class 12, for which thetransfer is deemed downlink-biased, the requested number of timeslots in downlinkis 4 and not 1.iii) The value of the T-bit indicated in the DL LLC PDU triggering theDL TBF establishment. If the T-bit is set to signalling, only one PDCH is required.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 993 / 1256


24.2.4.5.1.4 P35 - MAX_NB_DL_TBF_SIMUL_EST

Long Name MAX_NB_DL_TBF_SIMUL_EST

Definition Maximum number of DL TBF simultaneously established over the Granularityperiod.

Trigger Condition Within the Granularity period, the number of established DL TBF is observed ateach GAUGE-POLLING value; the maximum value is kept for the counter.



Sub Domain 3 N/A



994 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.5.1.5 P36 - AV_NB_DL_TBF_SIMUL_EST

Long Name AV_NB_DL_TBF_SIMUL_EST

Definition Average number of DL TBF simulataneously established over the Granularityperiod.

Trigger Condition Within the Granularity period, the number of established DL TBF is observed ateach GAUGE-POLLING value. At Granularity period expiry, these observationsare averaged, ie summed and divided by the number of observations. Theaveraged value (real) is multiplied by 10 and then rounded up or down to thenearest interger value (ie ROUND(10x) / 10).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 995 / 1256


24.2.4.5.1.6 P451b - CUMULATED_TIME_PDCH_DL_TBF_CELL

Long Name CUMULATED_TIME_PDCH_DL_TBF_CELL

Definition Cumulated time during which an DL TBF uses one PDCH, for all PDCHs of theTBF, and for all TBFs of the cell (in GPRS or EGPRS mode).

Trigger Condition The counter shall consider the resource allocation changes that occur further toa DL TBF re-allocation.Note: Active , delayed, extended phases of the TBF aretaken into account (only).The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).



Sub Domain 3 N/A



996 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.5.1.7 P452 - CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL

Long Name CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL

Definition Cumulated time during which a DL TBF established for GMM signalling purposesuses a PDCH (in GPRS or EGPRS mode), for all TBFs of the cell.

Trigger Condition For a given DL TBF, this counter is started at the establishment of the DL TBFsestablished to carry GMM signalling traffic to the MS. It is stopped at the end ofthe active phase of the DL TBF or on receipt of a DL LLC PDU without the T-bitset.Note : such TBFs only have one PDCH allocated.The time is provided inseconds with one significant value after the comma (i.e. ROUND(10x) / 10).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 997 / 1256


24.2.4.5.1.8 P455b_1 - DISTRIB_DL_PDCH_UNIT_ALLOC_1

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_1

Definition First cell of the distribution on units of PDCH allocated to DL TBFs.Itcontains :1) number of DL TBFs whose number of PDCH allocatedunits is in PDCH units band 1.PDCH units band 1 is defined by: PD_DL_PDCH_UNIT_ALLOC_THR_0<= allocated PDCH units <PD_DL_PDCH_UNIT_ALLOC_THR_1PD_DL_PDCH_UNIT_ALLOC_THR_0 = 0.

Trigger Condition This distribution measures the number of PDCH units assigned to the MS in DLat the release of the DL TBF. A DL PDCH unit represents the percentage of thePDCHs that is used by the assigned DL TBF. This distribution is computed at therelease of each DL TBF (i.e. at the expiry of timer T3192).The number of PDCHunits is calculated as follows :1) if EN_QOS_FEATURE is disable ( the PDCHsallocated to the MS are shared only by best effort TBFs) , then for each PDCH,the number of units allocated to this TBF = 1/ (nb of DL TBF on this PDCH)Thesum on all PDCHs allocated to the TBF gives the number of PDCH units allocatedin DL.2) ) if EN_QOS_FEATURE is enable (the PDCHs allocated to the MS areshared by best effort and GBR TBFs), then for each PDCH, the number of unitsallocated to this TBF is :



Sub Domain 3 N/A



998 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Tenth cell of the distribution on units of PDCH allocated to DL TBFs.Itcontains :1) number of DL TBFs whose number of PDCH allocatedunits is in PDCH units band 10.PDCH units band 10 is defined by: PD_DL_PDCH_UNIT_ALLOC_THR_9<= allocated PDCH units <PD_DL_PDCH_UNIT_ALLOC_THR_10PD_DL_PDCH_UNIT_ALLOC_THR_10= 5.




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 999 / 1256




Definition Second cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band2.PDCH units band 2 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_1<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_2




Sub Domain 3 N/A



1000 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Third cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band3.PDCH units band 3 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_2<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_3




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1001 / 1256




Definition Fourth cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band4.PDCH units band 4 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_3<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_4




Sub Domain 3 N/A



1002 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fifth cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band5.PDCH units band 5 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_4<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_5




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1003 / 1256




Definition Sixth cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band6.PDCH units band 6 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_5<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_6




Sub Domain 3 N/A



1004 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Seventh cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band7.PDCH units band 7 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_6<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_7




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1005 / 1256




Definition Eighth cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band8.PDCH units band 8 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_7<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_8




Sub Domain 3 N/A



1006 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Ninth cell of the distribution on units of PDCH allocated to DL TBFs.It contains :1)number of DL TBFs whose number of PDCH allocated units is in PDCH units band9.PDCH units band 9 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_8<=allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_9




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1007 / 1256


24.2.4.5.1.18 P62d - NB_UL_TBF_EST_REQ_EGPRS_PIM

Long Name NB_UL_TBF_EST_REQ_EGPRS_PIM

Definition Number of UL TBF establishment requests on (P)CCCH for EGPRS capableMS in packet idle mode.

Trigger Condition The counter is incremented by one whenever the MFS receives:- An 04.18EGPRS PACKET CHANNEL REQUEST message on RACH, or- An 04.60 EGPRSPACKET CHANNEL REQUEST message on PRACH, or- An 04.60 PACKETRESOURCE REQUEST message from an EGPRS capable MS.Generally, allcounters related to TBF establishment requests only take into account the firstattempt, i.e. no repetitions are counted.



Sub Domain 3 N/A



1008 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.5.1.19 P90g - NB_DL_TBF_EST_SUCC_EGPRS_PIM

Long Name NB_DL_TBF_EST_SUCC_EGPRS_PIM

Definition Number of DL TBF establishments on (P)CCCH for EGPRS capable MS in packetidle mode successfully served in EGPRS mode.

Trigger Condition The counter is incremented whenever the MFS receives a PACKET CONTROLACKNOWLEDGEMENT message indicating that the DL TBF has beensuccessfully established on (P)CCCH in EGPRS mode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1009 / 1256


24.2.4.5.1.20 P91g - NB_DL_TBF_EST_REQ_EGPRS_PIM

Long Name NB_DL_TBF_EST_REQ_EGPRS_PIM

Definition Number of DL TBF establishment requests for EGPRS capable MS in packetidle mode

Trigger Condition The counter is incremented by one whenever the MFS receives a DL LLCPDU for an EGPRS capable MS in packet idle mode. Note: If transmissionresources are available, this event will trigger a DL TBF establishment on(P)CCCH (in GPRS mode or in EGPRS mode).Generally, all counters relatedto TBF establishment requests only take into account the first attempt, i.e. norepetitions are counted.Note: This counter only applies in an EGPRS cell.In caseof GPRS-only cell, this counter is not incremented.



Sub Domain 3 N/A



1010 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.6 PDCH allocation for UL TBF

24.2.4.6.1 N/A

24.2.4.6.1.1 P161 - NB_UL_TBF_1_succ

Long Name NB_UL_TBF_1_succ

Definition Number of uplink TBF establishment requests (1 slot allocated) which are satisfiedat once by the initial allocation..

Trigger Condition Whenever the MFS allocates 1 PDCH for an UL TBF in case of an MS requesting1 (or several) slot UL.When determining the number of timeslots requestedby the mobile station for the UL TBF, the MFS takes into account:i) The MSmultislot class. The GPRS or EGPRS multislot class is used depending on theUL TBF establishment mode (in GPRS mode or EGPRS mode).ii) The bias ofthe transfer. For instance, for an MS belonging to multislot class 6, for whichthe transfer is deemed downlink-biased, the requested number of timeslots inuplink is 1 and not 2.


Sub Domain 2 PDCH allocation for UL TBF

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1011 / 1256


24.2.4.6.1.2 P163 - NB_UL_TBF_2_3_succ

Long Name NB_UL_TBF_2_3_succ

Definition Number of uplink TBF establishment requests requesting 2 or 3 slots which aretotally satisfied at once by the initial allocation..

Trigger Condition Whenever the MFS allocates exactly 2 PDCHs (or 3 PDCHs) for an UL TBF incase of an MS requesting 2 slots UL (or 3 slots UL).When determining the numberof timeslots requested by the mobile station for the UL TBF, the MFS takes intoaccount:i) The MS multislot class. The GPRS or EGPRS multislot class is useddepending on the UL TBF establishment mode (in GPRS mode or EGPRSmode).ii) The bias of the transfer. For instance, for an MS belonging to multislotclass 6, for which the transfer is deemed uplink-biased, the requested number oftimeslots in uplink is 2 and not 1.



Sub Domain 3 N/A



1012 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.6.1.3 P165 - NB_UL_TBF_4_5_succ

Long Name NB_UL_TBF_4_5_succ

Definition Number of uplink TBF establishment requests requesting 4 or 5 slots which aretotally satisfied at once by the initial allocation.

Trigger Condition Whenever the MFS allocates exactly 4 PDCHs (or 5 PDCHs) for an UL TBF incase of an MS requesting 4 slots UL (or 5 slots UL).When determining the numberof timeslots requested by the mobile station for the UL TBF, the MFS takes intoaccount:i) The MS multislot class. The GPRS or EGPRS multislot class is useddepending on the UL TBF establishment mode (in GPRS mode or EGPRSmode).ii) The bias of the transfer. For instance, for an MS belonging to multislotclass 12, for which the transfer is deemed uplink-biased, the requested number oftimeslots in uplink is 4 and not 1.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1013 / 1256


24.2.4.6.1.4 P30d - NB_UL_TBF_EST_SUCC_EGPRS_PIM

Long Name NB_UL_TBF_EST_SUCC_EGPRS_PIM

Definition Number of UL TBF establishments on (P)CCCH for EGPRS MS in packet idlemode successfully served in EGPRS mode.

Trigger Condition The counter is incremented in one of the following conditions:- whenever theTLLI is received during a one phase access EGPRS UL TBF establishment, or-whenever the TBF start indication is received during a two-phase access EGPRSUL TBF establishment.



Sub Domain 3 N/A



1014 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.6.1.5 P39 - MAX_NB_UL_TBF_SIMUL_EST

Long Name MAX_NB_UL_TBF_SIMUL_EST

Definition Maximum number of UL TBF simultaneously established over the Granularityperiod.

Trigger Condition Within the Granularity period, the number of established UL TBF is observed ateach GAUGE-POLLING value; the maximum value is kept for the counter.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1015 / 1256


24.2.4.6.1.6 P40 - AV_NB_UL_TBF_SIMUL_EST

Long Name AV_NB_UL_TBF_SIMUL_EST

Definition Average number of UL TBF simutaneously established over the Granularity period.

Trigger Condition Within the Granularity period, the number of established UL TBF is observed ateach GAUGE-POLLING value. At Granularity period expiry, these observationsare averaged, ie summed and divided by the number of observations. Theaveraged value (real) is multiplied by 10 and then rounded up or down to thenearest interger value (ie ROUND(10x) / 10).



Sub Domain 3 N/A



1016 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.6.1.7 P451a - CUMULATED_TIME_PDCH_UL_TBF_CELL

Long Name CUMULATED_TIME_PDCH_UL_TBF_CELL

Definition Cumulated time during which an UL TBF uses one PDCH, for all PDCHs of theTBF, and for all TBFs of the cell (in GPRS or EGPRS mode).

Trigger Condition The counter shall consider the resource allocation changes that occur further toa UL TBF re-allocation.Note: Active , delayed, extended phases of the TBF aretaken into account (only).The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1017 / 1256


24.2.4.6.1.8 P455a_1 - DISTRIB_UL_PDCH_UNIT_ALLOC_1

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_1

Definition First cell of the distribution on units of PDCH allocated to UL TBFs.Itcontains :1) number of UL TBFs whose number of PDCH allocatedunits is in PDCH units band 1.PDCH units band 1 is defined by: PD_UL_PDCH_UNIT_ALLOC_THR_0<= allocated PDCH units <PD_UL_PDCH_UNIT_ALLOC_THR_1PD_UL_PDCH_UNIT_ALLOC_THR_0 = 0.

Trigger Condition This distribution measures the number of PDCH units assigned to the MS in ULat the release of the UL TBF. An UL PDCH unit represents the percentage ofthe PDCHs that is used by the assigned UL TBF. This distribution is computedat the release of each UL TBF (i.e. indication of reception of acknowledgementof final PUAN).The number of PDCH units is calculated as follows :1) ifEN_QOS_FEATURE is disable ( the PDCHs allocated to the MS are shared onlyby best effort TBFs) , then for each PDCH, the number of units allocated to thisTBF = 1/ (nb of UL TBF on this PDCH)The sum on all PDCHs allocated to the TBFgives the number of PDCH units allocated in UL.2) ) if EN_QOS_FEATURE isenable (the PDCHs allocated to the MS are shared by best effort and GBR TBFs),then for each PDCH, the number of units allocated to this TBF is :



Sub Domain 3 N/A



1018 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Tenth cell of the distribution on units of PDCH allocated to UL TBFs.Itcontains :1) number of UL TBFs whose number of PDCH allocatedunits is in PDCH units band 10.PDCH units band 10 is defined by: PD_UL_PDCH_UNIT_ALLOC_THR_9<= allocated PDCH units <PD_UL_PDCH_UNIT_ALLOC_THR_10PD_UL_PDCH_UNIT_ALLOC_THR_10= 5.




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1019 / 1256




Definition Second cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band2.PDCH units band 2 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_1<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_2




Sub Domain 3 N/A



1020 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Third cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band3.PDCH units band 3 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_2<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_3




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1021 / 1256




Definition Fourth cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band4.PDCH units band 4 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_3<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_4




Sub Domain 3 N/A



1022 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fifth cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band5.PDCH units band 5 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_4<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_5




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1023 / 1256




Definition Sixth cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band6.PDCH units band 6 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_5<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_6




Sub Domain 3 N/A



1024 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Seventh cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band7.PDCH units band 7 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_6<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_7




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1025 / 1256




Definition Eighth cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band8.PDCH units band 8 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_7<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_8




Sub Domain 3 N/A



1026 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Ninth cell of the distribution on units of PDCH allocated to UL TBFs.It contains :1)number of UL TBFs whose number of PDCH allocated units is in PDCH units band9.PDCH units band 9 is defined by : PD_UL_PDCH_UNIT_ALLOC_THR_8<=allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_9




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1027 / 1256


24.2.4.7 UL LLC data flow

24.2.4.7.1 N/A

24.2.4.7.1.1 P531a_1 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1

Definition First class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 1.EGPRS LLC throughput class 1is defined by : EGPRS_LLC_throughput_THR_0<= LLC throughput <EGPRS_LLC_throughput_THR_1EGPRS_LLC_throughput_THR_0 = 0 kbit/s

Trigger Condition During MS context lifetime , the size of the UL LLC PDU received in the TBFestablished in EGPRS mode and their transfert duration are cumulated.Whenthe MS context is deleted , the UL LLC throughput (cumulated UL LLC PDUsize/cumulated transfer time) is estimated and the suitable class of the distributionis incremented by one.Note : -Only UL LLC PDU whose TBF traffic type is data aretaken into account.- The size and transfer duration of a UL LLC PDU is estimatedby RRM when a UL LLC PDU have been correctly received from the MS.


Sub Domain 2 UL LLC data flow

Sub Domain 3 N/A



1028 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Tenth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 10.EGPRS LLC throughput class 10is defined by : EGPRS_LLC_throughput_THR_9<= LLC throughput <EGPRS_LLC_throughput_THR_10




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1029 / 1256




Definition Eleventh class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 11.EGPRS LLC throughput class 11is defined by : EGPRS_LLC_throughput_THR_10<= LLC throughput <EGPRS_LLC_throughput_THR_11




Sub Domain 3 N/A



1030 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 2.EGPRS LLC throughput class 2is defined by : EGPRS_LLC_throughput_THR_1<= LLC throughput <EGPRS_LLC_throughput_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1031 / 1256




Definition Third class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 3.EGPRS LLC throughput class 3is defined by : EGPRS_LLC_throughput_THR_2<= LLC throughput <EGPRS_LLC_throughput_THR_3




Sub Domain 3 N/A



1032 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fourth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 4.EGPRS LLC throughput class 4is defined by : EGPRS_LLC_throughput_THR_3<= LLC throughput <EGPRS_LLC_throughput_THR_4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1033 / 1256




Definition Fifth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 5.EGPRS LLC throughput class 5is defined by : EGPRS_LLC_throughput_THR_4<= LLC throughput <EGPRS_LLC_throughput_THR_5




Sub Domain 3 N/A



1034 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 6.EGPRS LLC throughput class 6is defined by : EGPRS_LLC_throughput_THR_5<= LLC throughput <EGPRS_LLC_throughput_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1035 / 1256




Definition Seventh class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 7.EGPRS LLC throughput class 7is defined by : EGPRS_LLC_throughput_THR_6<= LLC throughput <EGPRS_LLC_throughput_THR_7




Sub Domain 3 N/A



1036 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 8.EGPRS LLC throughput class 8is defined by : EGPRS_LLC_throughput_THR_7<= LLC throughput <EGPRS_LLC_throughput_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1037 / 1256




Definition Ninth class of the distribution on number of EGPRS UL LLC throughput.Itcontains :1) number of EGPRS UL LLC throughput whose throughputis in EGPRS LLC throughput class 9.EGPRS LLC throughput class 9is defined by : EGPRS_LLC_throughput_THR_8<= LLC throughput <EGPRS_LLC_throughput_THR_9




Sub Domain 3 N/A



1038 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Third class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class3.EGPRS LLC throughput class 3is defined by : EGPRS_LLC_throughput_THR_2<= LLC throughput <EGPRS_LLC_throughput_THR_3




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1039 / 1256




Definition Fourth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 4.EGPRS LLC throughput class 4is defined by : EGPRS_LLC_throughput_THR_3<= LLC throughput <EGPRS_LLC_throughput_THR_4




Sub Domain 3 N/A



1040 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Seventh class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 7.EGPRS LLC throughput class 7is defined by : EGPRS_LLC_throughput_THR_6<= LLC throughput <EGPRS_LLC_throughput_THR_7




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1041 / 1256




Definition Ninth class of the distribution on number of EGPRS DL LLC throughput.Itcontains :1) number of EGPRS DL LLC throughput whose throughputis in EGPRS LLC throughput class 9.EGPRS LLC throughput class 9is defined by : EGPRS_LLC_throughput_THR_8<= LLC throughput <EGPRS_LLC_throughput_THR_9




Sub Domain 3 N/A



1042 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.7.1.16 P532a_1 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1

Definition First class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 1.GPRS LLC throughput class 1is defined by : GPRS_LLC_throughput_THR_0<= LLC throughput <GPRS_LLC_throughput_THR_1GPRS_LLC_throughput_THR_0 = 0 kbit/s

Trigger Condition During MS context lifetime , the size of the UL LLC PDU received in the TBFestablished in GPRS mode and their transfert duration are cumulated.Whenthe MS context is deleted , the UL LLC throughput (cumulated UL LLC PDUsize/cumulated transfer time) is estimated and the suitable class of the distributionis incremented by one.Note : -Only UL LLC PDU whose TBF traffic type is data aretaken into account.– The size and transfer duration of a UL LLC PDU is estimatedby RRM when a UL LLC PDU have been correctly received from the MS.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1043 / 1256




Definition Tenth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 10.GPRS LLC throughput class 10is defined by : GPRS_LLC_throughput_THR_9<= LLC throughput <GPRS_LLC_throughput_THR_10

Trigger Condition During MS context lifetime , the size of the UL LLC PDU received in the TBFestablished in GPRS mode and their transfert duration are cumulated.Whenthe MS context is deleted , the UL LLC throughput (cumulated UL LLC PDUsize/cumulated transfer time) is estimated and the suitable class of the distributionis incremented by one.Note : -Only UL LLC PDU whose TBF traffic type is data aretaken into account.- The size and transfer duration of a UL LLC PDU is estimatedby RRM when a UL LLC PDU have been correctly received from the MS.



Sub Domain 3 N/A



1044 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 2.GPRS LLC throughput class 2is defined by : GPRS_LLC_throughput_THR_1<= LLC throughput <GPRS_LLC_throughput_THR_2

Trigger Condition During MS context lifetime , the size of the UL LLC PDU received in the TBFestablished in GPRS mode and their transfert duration are cumulated.Whenthe MS context is deleted , the UL LLC throughput (cumulated UL LLC PDUsize/cumulated transfer time) is estimated and the suitable class of the distributionis incremented by one.Note : -Only UL LLC PDU whose TBF traffic type is data aretaken into account.- The size and transfer duration of a UL LLC PDU is providedby RLC to RRM when a UL LLC PDU have been correctly received from the MS.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1045 / 1256




Definition Third class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 3.GPRS LLC throughput class 3is defined by : GPRS_LLC_throughput_THR_2<= LLC throughput <GPRS_LLC_throughput_THR_3




Sub Domain 3 N/A



1046 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fourth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 4.GPRS LLC throughput class 4is defined by : GPRS_LLC_throughput_THR_3<= LLC throughput <GPRS_LLC_throughput_THR_4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1047 / 1256




Definition Fifth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 5.GPRS LLC throughput class 5is defined by : GPRS_LLC_throughput_THR_4<= LLC throughput <GPRS_LLC_throughput_THR_5




Sub Domain 3 N/A



1048 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 6.GPRS LLC throughput class 6is defined by : GPRS_LLC_throughput_THR_5<= LLC throughput <GPRS_LLC_throughput_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1049 / 1256




Definition Seventh class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 7.GPRS LLC throughput class 7is defined by : GPRS_LLC_throughput_THR_6<= LLC throughput <GPRS_LLC_throughput_THR_7




Sub Domain 3 N/A



1050 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 8.GPRS LLC throughput class 8is defined by : GPRS_LLC_throughput_THR_7<= LLC throughput <GPRS_LLC_throughput_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1051 / 1256




Definition Ninth class of the distribution on number of GPRS UL LLC throughput.Itcontains :1) number of GPRS UL LLC throughput whose throughputis in GPRS LLC throughput class 9.GPRS LLC throughput class 9is defined by : GPRS_LLC_throughput_THR_8<= LLC throughput <GPRS_LLC_throughput_THR_9




Sub Domain 3 N/A



1052 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.8 UL TBF duration

24.2.4.8.1 N/A

24.2.4.8.1.1 P129a - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_ACK

Long Name CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_ACK

Definition Cumulated time duration of all active UL TBFs established in GPRS mode andRLC acknowledged mode.Note: An active UL TBF connection is an UL TBF not inextended phase.

Trigger Condition The counter measures the cumulated time duration of all UL TBFs established inGPRS mode and RLC acknowledged Mode in the cell over the granularity period.Note 1 : The time during which the emission of the final Packet Uplink Ack/Nackmessage is delayed and the time during which the UL is in extended phase are nottaken into account Note 2 : In case of abnormal UL TBF releases, the counterstops at the time when the RRM layer has received the last UL LLC PDU.Note 3 :The case the UL TBF is released due to a NC cell reselection is managed as anabnormal UL TBF release.The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).The UL TBFs still established at theexpiration of the granularity period are not taken into account in the cumulatedvalue. They are taken into account only when the UL TBFs are released. In caseof traffic profile including a lot of "very long" TBF, this may lead to a temporaryunder-estimated (then over-estimated) cumulated value.


Sub Domain 2 UL TBF duration

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1053 / 1256


24.2.4.8.1.2 P129b - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_NACK

Long Name CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_NACK

Definition Cumulated time duration of all active UL TBFs established in GPRS mode andRLC unacknowledged mode.Note: An active UL TBF connection is an UL TBFnot in extended phase.

Trigger Condition The counter measures the cumulated time duration of all UL TBFs establishedin GPRS mode and RLC unacknowledged mode in the cell over the granularityperiod.Note1 : The time during which the emission of the final Packet UplinkAck/Nack message is delayed and the time during which the UL is in extendedphase not taken into account.Note 2 :In case of abnormal UL TBF releases, thecounter stops at the time when the RRM layer has received the last UL LLCPDU. Note 3 :The case the UL TBF is released due to a NC cell reselection ismanaged as an abnormal UL TBF release.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x) / 10).The UL TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the UL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



1054 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.8.1.3 P129c - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_ACK

Long Name CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_ACK

Definition Cumulated time duration of all active UL TBFs established in EGPRS mode andRLC acknowledged mode.Note: An active UL TBF connection is an UL TBF not inextended phase.

Trigger Condition The counter measures the cumulated time duration of all UL TBFs establishedin EGPRS mode and RLC acknowledged Mode in the cell over the granularityperiod.Note 1 : The time during which the emission of the final Packet UplinkAck/Nack message and the time during which the UL is in extended phasedelayed is not taken into account.Note 2 : In case of abnormal UL TBF releases,the counter stops at the time when the RRM layer has received the last UL LLCPDU.Note 3 : The case the UL TBF is released due to a NC cell reselection ismanaged as an abnormal UL TBF release.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x) / 10).The UL TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the UL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1055 / 1256


24.2.4.8.1.4 P129d - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_NACK

Long Name CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_NACK

Definition Cumulated time duration of all active UL TBFs established in EGPRS mode andRLC unacknowledged mode.Note: An active UL TBF connection is an UL TBFnot in extended phase.

Trigger Condition The counter measures the cumulated time duration of all UL TBFs establishedin EGPRS mode and RLC unacknowledged mode in the cell over the granularityperiod.Note1 : The time during which the emission of the final Packet UplinkAck/Nack message and the time during which the UL is in extended phasedelayed is not taken into account.Note 2 :In case of abnormal UL TBF releases,the counter stops at the time when the RRM layer has received the last UL LLCPDU. Note 3 :The case the UL TBF is released due to a NC cell reselection ismanaged as an abnormal UL TBF release.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x) / 10).The UL TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the UL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



1056 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.8.1.5 P410 -CUMULATED_TIME_UL_BIASED_AND_OPTIMAL_UL_ALLOCATION

Long Name CUMULATED_TIME_UL_BIASED_AND_OPTIMAL_UL_ALLOCATION

Definition Cumulated time during which uplink TBFs are granted the maximum numberof PDCHs they need and the corresponding MSs are engaged in uplink-biasedtransfers.

Trigger Condition The counter is incremented by the duration during which all uplink TBFs of a cellwhich serve an uplink-biased transfer are granted as many timeslots as needed.The results are cumulated over the granularity period.When determining thenumber of timeslots needed by the mobile station for the UL TBF, the MFS takesinto account:i) The MS multislot class. The GPRS or EGPRS multislot class isused depending on the UL TBF establishment mode (in GPRS mode or EGPRSmode).ii) The bias of the transfer. For instance, for an MS belonging to multislotclass 6, for which the transfer is deemed uplink-biased, the requested number oftimeslots in uplink is 2 and not 1. iii) The value of the "traffic type" (signalling ordata) of this MS. If the traffic type is signalling, only one PDCH is required.However,the "optimality" may change during the life of the TBF, due to change in the traffictype from signalling to data.In case of abnormal UL TBF releases, the counterstops at the time when the RRM layer has received the last UL LLC PDU. Thecase the UL TBF is released due to a NC cell reselection is managed as anabnormal UL TBF release.The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).The optimal UL biaised TBFs stillestablished at the expiration of the granularity period are not taken into accountin the cumulated value. They are taken into account only when the UL TBFs arereleased. In case of traffic profile including a lot of "very long" TBF, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A


External Comment - when the traffic type changes from "signalling" to "data", the optimality isre-assessed. - Once the traffic type is set to data, it can not be changed tosignalling, whatever the T-bit value.

3BK 21255 AAAA PCZZA Ed.07 1057 / 1256


24.2.4.8.1.6 P412 - CUMULATED_TIME_UL_BIASED_UL_TBF

Long Name CUMULATED_TIME_UL_BIASED_UL_TBF

Definition Cumulated time during which MSs are engaged in uplink-biased transfers andthere is an UL TBF serving the MS.

Trigger Condition The counter is incremented by the duration during which MSs are deemed in anuplink-biased transfer. Only the time during which there is an UL TBF serving theMS is taken into account.In case of abnormal UL TBF releases, the counter stopsat the time when the RRM layer has received the last UL LLC PDU. The case theUL TBF is released due to a NC cell reselection is managed as an abnormal ULTBF release.The time is provided in seconds with one significant value after thecomma (i.e. ROUND(10x) / 10).The UL TBFs still established at the expiration ofthe granularity period are not taken into account in the cumulated value. They aretaken into account only when the UL TBFs are released. In case of traffic profileincluding a lot of "very long" TBF, this may lead to a temporary under-estimated(then over-estimated) cumulated value.



Sub Domain 3 N/A



1058 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.8.1.7 P420 - CUMULATED_TIME_UL_BIASED

Long Name CUMULATED_TIME_UL_BIASED

Definition Cumulated time during which MSs are engaged in uplink-biased transfers.

Trigger Condition The counter is incremented by the duration during which MSs are deemed inan uplink-biased transfer.When an MS context is created :If it is uplink-biased,then the timer is started for that MS. When the bias changes to downlink, thenthe timer is stopped. When it changes back to uplink, the timer is restarted.If itis downlink-biased, then the timer is started for that MS when the bias changesto uplink. When it changes back to downlink, then the timer is stopped.Whenthe session ends, the timer for the MS is cumulated to P420.Note that when theMS context is deemed uplink-biased and T3192 is running, even if there is noon-going TBF, that duration shall be taken into account in this timer.In case theMS has no on-going UL TBF and an abnormal DL TBF release is detected duringactive phase (i.e. not delayed phase), the counter stops for the given MS:- at thetime when the RRM layer has received the acknowledgment of the last DL LLCPDU (in case of RLC acknowledged mode), or,- at the time when the RRM layerhas sent the last DL LLC PDU to the RLC layer (in case of RLC unacknowledgedmode).In case the MS has no on-going UL TBF and an abnormal DL TBF releaseis detected during delayed phase, the counter stops for the given MS at the timewhen the RRM layer has been informed that the DL TBF has entered the delayedphase.In case the MS has no on-going DL TBF and an abnormal UL TBF releaseis detected, the counter stops for the given MS at the time when the RRM layerhas received the last UL LLC PDU.The case the DL TBF is released due to aNC cell reselection is managed as an abnormal DL TBF release. Similarly, thecase the UL TBF is released due to a NC cell reselection is managed as anabnormal UL TBF release.The time is provided in seconds with one significantvalue after the comma (i.e. ROUND(10x) / 10).The MSs still UL biaised at theexpiration of the granularity period are not taken into account in the cumulatedvalue. They are taken into account only when the biais change to DL. In case oftraffic profile including a lot of "very long" TBF with no bias changes, this may leadto a temporary under-estimated (then over-estimated) cumulated value.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1059 / 1256


24.2.4.8.1.8 P453a_1 - DISTRIB_UL_TBF_DURATION_1

Long Name DISTRIB_UL_TBF_DURATION_1

Definition First cell of the distribution on UL TBF duration.It contains :1) numberof UL TBFs whose duration is in duration band 1Duration band1 is defined by : PD_UL_TBF_DURATION_THR_0<= duration <PD_UL_TBF_DURATION_THR_1PD_UL_TBF_DURATION_THR_0 = 0 sec.

Trigger Condition UL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLCunacknowledged mode are taken into account. Only the active phase of the TBFis taken into account.Duration is measured as for P129a, P129b, P129c, P129d.



Sub Domain 3 N/A



1060 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Tenth cell of the distribution on UL TBF duration.It contains :1) numberof UL TBFs whose duration is in duration band 10Duration band10 is defined by : PD_UL_TBF_DURATION_THR_9<= duration <PD_UL_TBF_DURATION_THR_10PD_UL_TBF_DURATION_THR_10 = 16384

Trigger Condition UL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLCunacknowledged mode are taken into account. Only the active phase of theTBF is taken into account.Duration is measured as for P129a, P129b, P129c,P129d.Whenever a TBF duration exceeds PD_UL_TBF_DURATION_THR_10,then it is not taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1061 / 1256




Definition Second cell of the distribution on UL TBF duration.It contains :1) number ofUL TBFs whose duration is in duration band 2Duration band 2 is defined by :PD_UL_TBF_DURATION_THR_1<= duration < PD_UL_TBF_DURATION_THR_2




Sub Domain 3 N/A



1062 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Third cell of the distribution on UL TBF duration.It contains :1) number of ULTBFs whose duration is in duration band 3Duration band 3 is defined by :PD_UL_TBF_DURATION_THR_2<= duration < PD_UL_TBF_DURATION_THR_3




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1063 / 1256




Definition Fourth cell of the distribution on UL TBF duration.It contains :1) number ofUL TBFs whose duration is in duration band 4Duration band 4 is defined by :PD_UL_TBF_DURATION_THR_3<= duration < PD_UL_TBF_DURATION_THR_4




Sub Domain 3 N/A



1064 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Fifth cell of the distribution on UL TBF duration.It contains :1) number of ULTBFs whose duration is in duration band 5Duration band 5 is defined by :PD_UL_TBF_DURATION_THR_4<= duration < PD_UL_TBF_DURATION_THR_5




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1065 / 1256




Definition Sixth cell of the distribution on UL TBF duration.It contains :1) number of ULTBFs whose duration is in duration band 6Duration band 6 is defined by :PD_UL_TBF_DURATION_THR_5<= duration < PD_UL_TBF_DURATION_THR_6




Sub Domain 3 N/A



1066 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Seventh cell of the distribution on UL TBF duration.It contains :1) number ofUL TBFs whose duration is in duration band 7Duration band 7 is defined by :PD_UL_TBF_DURATION_THR_6<= duration < PD_UL_TBF_DURATION_THR_7




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1067 / 1256




Definition Eighth cell of the distribution on UL TBF duration.It contains :1) number ofUL TBFs whose duration is in duration band 8Duration band 8 is defined by :PD_UL_TBF_DURATION_THR_7<= duration < PD_UL_TBF_DURATION_THR_8




Sub Domain 3 N/A



1068 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Nineth cell of the distribution on UL TBF duration.It contains :1) number ofUL TBFs whose duration is in duration band 9Duration band 9 is defined by :PD_UL_TBF_DURATION_THR_8<= duration < PD_UL_TBF_DURATION_THR_9




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1069 / 1256


24.2.4.8.1.18 P461 - CUMULATED_ACT_EXT_UL_CONNECTION_TIME

Long Name CUMULATED_ACT_EXT_UL_CONNECTION_TIME

Definition Cumulated overall time of UL TBF connections (in active state or extended phase).

Trigger Condition The counter measures the cumulated time duration of all UL TBFs connections inactive or extended phase in the cell over the granularity period.The counter starts:For a given UL TBF, at the establishment of the UL TBF in (E)GPRS mode (thefirst UL RLC data block has been received).The counter stops : For a given ULTBF, at the release of the UL TBF in (E)GPRS mode.Note : This counter appliesto both GPRS and EGPRS TBFs and to both acknowledge or unacknowledgemode.Note1 : The time during which the emission of the final Packet UplinkAck/Nack message is delayed and the time during which the UL is in extendedphase are taken into account.Note 2 :In case of abnormal UL TBF releases, thecounter stops at the time when the RRM layer has received the last UL LLCPDU. Note 3 :The case the UL TBF is released due to a NC cell reselection ismanaged as an abnormal UL TBF release.The time is provided in seconds withone significant value after the comma (i.e. ROUND(10x) / 10).



Sub Domain 3 N/A



1070 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.2.4.9 UL TBF LLC volume

24.2.4.9.1 N/A



Definition First cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 1.LLCvolume band 1 is defined by : PD_UL_TBF_VOLUME_THR_0<= LLC volume <PD_UL_TBF_VOLUME_THR_1PD_UL_TBF_VOLUME_THR_0 = 0 byte



Sub Domain 2 UL TBF LLC volume

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1071 / 1256




Definition Tenth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 10.LLCvolume band 10 is defined by : PD_UL_TBF_VOLUME_THR_9<= LLC volume< PD_UL_TBF_VOLUME_THR_10PD_UL_TBF_VOLUME_THR_10 = 100 000000 bytes

Trigger Condition TBF in GPRS and EGPRS mode, in RLC acknowledged and RLC unacknowledgedmode are taken into account.The volume is calculated as in P44.Whenever aTBF volume exceeds PD_UL_TBF_VOLUME_THR_10, then it is not taken intoaccount.



Sub Domain 3 N/A



1072 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Second cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 2.LLCvolume band 2 is defined by : PD_UL_TBF_VOLUME_THR_1<= LLC volume <PD_UL_TBF_VOLUME_THR_2




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1073 / 1256




Definition Fifth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 5.LLCvolume band 5 is defined by : PD_UL_TBF_VOLUME_THR_4<= LLC volume <PD_UL_TBF_VOLUME_THR_5




Sub Domain 3 N/A



1074 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Sixth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 6.LLCvolume band 1 is defined by : PD_UL_TBF_VOLUME_THR_5<= LLC volume <PD_UL_TBF_VOLUME_THR_6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1075 / 1256




Definition Seventh cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 7.LLCvolume band 7 is defined by : PD_UL_TBF_VOLUME_THR_6<= LLC volume <PD_UL_TBF_VOLUME_THR_7




Sub Domain 3 N/A



1076 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Eighth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 81.LLCvolume band 8 is defined by : PD_UL_TBF_VOLUME_THR_7<= LLC volume <PD_UL_TBF_VOLUME_THR_8




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1077 / 1256




Definition Ninth cell of the distribution on volume of UL TBF.It contains :1) number of ULTBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 9.LLCvolume band 9 is defined by : PD_UL_TBF_VOLUME_THR_8<= LLC volume <PD_UL_TBF_VOLUME_THR_9




Sub Domain 3 N/A



1078 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3 Traffic load


24.3.1.1 GCH

24.3.1.1.1 N/A

24.3.1.1.1.1 P103 - NB_ERROR_UL_GCH_FRAME

Long Name NB_ERROR_UL_GCH_FRAME

Definition Number of GCH frames badly received by the MFS (due to a bad CRC).

Trigger Condition Whenever the EGCH layer detects that a GCH frame has not been correctlydecoded in the MFS (due a bad CRC).


Sub Domain 2 GCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1079 / 1256


24.3.1.2 LapD

24.3.1.2.1 N/A

24.3.1.2.1.1 P41 - NB_KBYTES_SENT_TO_BSC

Long Name NB_KBYTES_SENT_TO_BSC

Definition Number of kilo bytes sent to the BSC on the LapD link.

Trigger Condition For each message sent to the BSC on the LapD link, the counter is incrementedby the number of bytes of the message. The result is expressed in kilo bytes.


Sub Domain 2 LapD

Sub Domain 3 N/A



1080 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.1.2.1.2 P42 - NB_KBYTES_RECEIVED_FROM_BSC

Long Name NB_KBYTES_RECEIVED_FROM_BSC

Definition Number of kilo bytes received from the BSC on the LapD link.

Trigger Condition For each message received from the BSC on the LapD link, the counter isincremented by the number of bytes of the message. The result is expressedin kilo bytes.


Sub Domain 2 LapD

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1081 / 1256


24.3.2 Gb interface

24.3.2.1 BVC (Cell)

24.3.2.1.1 N/A

24.3.2.1.1.1 P43 - NB_DL_LLC_BYTES

Long Name NB_DL_LLC_BYTES

Definition Number of DL LLC bytes received from the SGSN at BSSGP level per cell.

Trigger Condition Whenever the MFS receives a DL 08.18 UNITDATA from the SGSN to transmit tothe cell, the counter is incremented by the number of bytes of the LLC PDU(s).



Sub Domain 3 N/A



1082 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.2.1.1.2 P44 - NB_UL_LLC_BYTES

Long Name NB_UL_LLC_BYTES

Definition Number of UL LLC bytes received from the MS at BSSGP (08.18) sublayer per cell.

Trigger Condition Whenever the BSSGP sublayer receives an UL 08.18 UNITDATA from theMAC/RLC sublayer to transmit to the SGSN, the counter is incremented by thenumber of bytes of the LLC PDU(s).



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1083 / 1256


24.3.2.2 PVC

24.3.2.2.1 N/A

24.3.2.2.1.1 P45 - NB_KBYTES_RECEIVED_FROM_SGSN

Long Name NB_KBYTES_RECEIVED_FROM_SGSN

Definition Number of kilo bytes received from the SGSN at SNS sublayer.

Trigger Condition For each message received from the SGSN, the counter is incremented by thenumber of bytes of the message. The result is expressed in kilo bytes.


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


1084 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.2.2.1.2 P46 - NB_KBYTES_SENT_TO_SGSN

Long Name NB_KBYTES_SENT_TO_SGSN

Definition Number of kilo bytes sent to the SGSN.

Trigger Condition For each message sent to the SGSN, the counter is incremented by the number ofbytes of the message. The result is expressed in kilo bytes.


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


3BK 21255 AAAA PCZZA Ed.07 1085 / 1256


24.3.2.3 SGSN_IP_NSVC

24.3.2.3.1 N/A

24.3.2.3.1.1 P45a - NB_KBYTES_RECEIVED_FROM_SGSN_GBIP

Long Name NB_KBYTES_RECEIVED_FROM_SGSN_GBIP

Definition Number of kilo bytes received from the SGSN at SNS sublayer.

Trigger Condition For each message received from the SGSN, the counter is incremented by thenumber of bytes of the message. The result is expressed in kilo bytes.



Sub Domain 3 N/A



1086 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.2.3.1.2 P46a - NB_KBYTES_SENT_TO_SGSN_GBIP

Long Name NB_KBYTES_SENT_TO_SGSN_GBIP

Definition Number of kilo bytes sent to the SGSN.

Trigger Condition For each message sent to the SGSN, the counter is incremented by the number ofbytes of the message. The result is expressed in kilo bytes.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1087 / 1256



24.3.3.1 AGCH

24.3.3.1.1 N/A

24.3.3.1.1.1 P49 - NB_IMM_ASS_AGCH

Long Name NB_IMM_ASS_AGCH

Definition Number of (BSCGP) IMMEDIATE ASSIGNMENT sent to the MS (through the BSCwhich manages the AGCH resource)- for an UL TBF establisment,- for a DL TBFestablishment when the MS is in non-DRX mode,- for the allocation of an ULblock.This counter gives an indication of the AGCH load used for GPRS.

Trigger Condition Whenever a (BSCGP) IMMEDIATE_ASSIGNMENT is sent to the MS on AGCH.


Sub Domain 2 AGCH

Sub Domain 3 N/A



1088 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.2 DL LLC data flow

24.3.3.2.1 N/A

24.3.3.2.1.1 P10 - NB_DL_LLC_BYTES_DISC_CONG

Long Name NB_DL_LLC_BYTES_DISC_CONG

Definition Number of DL LLC bytes discarded due to congestion.

Trigger Condition 1) Whenever the PDU life time of a DL LLC PDU expires, the counter isincremented by the number of bytes of the LLC PDU.2) Whenever the MFSreceives a DL LLC PDU and the buffer in reception on the Gb interface is full, thecounter is incremented by the number of bytes of the LLC PDU to discard.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1089 / 1256


24.3.3.2.1.2 P43a - NB_DL_LLC_BYTES_GPRS_ACK

Long Name NB_DL_LLC_BYTES_GPRS_ACK

Definition Number of DL LLC bytes that have been transmitted and acknowledged by theRLC layer on DL TBFs established in GPRS mode and RLC acknowledged mode.

Trigger Condition Whenever the RRM layer is informed that an DL LLC PDU has been correctlyreceived by the MS on a DL TBF established in GPRS mode and RLCacknowledged mode, the counter is incremented by the number of bytes of thecorresponding DL LLC PDU.



Sub Domain 3 N/A



1090 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.2.1.3 P43b - NB_DL_LLC_BYTES_GPRS_NACK

Long Name NB_DL_LLC_BYTES_GPRS_NACK

Definition Number of DL LLC bytes that have been transmitted by the RLC layer on DL TBFsestablished in GPRS mode and RLC unacknowledged mode.

Trigger Condition Whenever the RRM layer is informed that an DL LLC PDU has been correctlytransmitted to the MS on a DL TBF established in GPRS mode and RLCunacknowledged mode, the counter is incremented by the number of bytes of thecorresponding DL LLC PDU.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1091 / 1256


24.3.3.2.1.4 P43c - NB_DL_LLC_BYTES_EGPRS_ACK

Long Name NB_DL_LLC_BYTES_EGPRS_ACK

Definition Number of DL LLC bytes that have been transmitted and acknowledged by the RLClayer on DL TBFs established in EGPRS mode and RLC acknowledged mode.

Trigger Condition Whenever the RRM layer is informed that an DL LLC PDU has been correctlyreceived by the MS on a DL TBF established in EGPRS mode and RLCacknowledged mode, the counter is incremented by the number of bytes of thecorresponding DL LLC PDU.



Sub Domain 3 N/A



1092 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.2.1.5 P43d - NB_DL_LLC_BYTES_EGPRS_NACK

Long Name NB_DL_LLC_BYTES_EGPRS_NACK

Definition Number of DL LLC bytes that have been transmitted by the RLC layer on DL TBFsestablished in EGPRS mode and RLC unacknowledged mode.

Trigger Condition Whenever the RRM layer is informed that a DL LLC PDU has been correctlytransmitted to the MS on a DL TBF established in GPRS mode and RLCunacknowledged mode, the counter is incremented by the number of bytes of thecorresponding DL LLC PDU.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1093 / 1256


24.3.3.2.1.6 P74 - NB_DL_PDU_TRANSMITTED

Long Name NB_DL_PDU_TRANSMITTED

Definition Number of DL LLC PDUs transmitted to the RLC layer

Trigger Condition The counter is incremented whenever a DL LLC PDU is transmitted to PTU.Note:An DL LLC PDU may have been transmitted to the RLC layer and then may bediscarded by the RRM layer (e.g. when a transmission problem is encountered onthe radio interface) without having been sent on the radio interface.



Sub Domain 3 N/A



1094 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.2.1.7 P95 - NB_DL_LLC_BYTES_REROUTED

Long Name NB_DL_LLC_BYTES_REROUTED

Definition Number of DL LLC bytes rerouted (i.e. sent) from cell to another one.

Trigger Condition Flush message received in the serving cell with rerouting conditions fulfilled.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1095 / 1256


24.3.3.2.1.8 P96 - NB_DL_LLC_BYTES_NOT_REROUTED

Long Name NB_DL_LLC_BYTES_NOT_REROUTED

Definition Number of DL LLC bytes discarded during a cell change.

Trigger Condition Flush message received in the serving cell with rerouting conditions not fulfilled.



Sub Domain 3 N/A



1096 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.2.1.9 P97 - NB_DL_LLC_BYTES_REROUTED_RECEIVED

Long Name NB_DL_LLC_BYTES_REROUTED_RECEIVED

Definition Number of DL LLC bytes rerouted (i.e. received) from another cell.

Trigger Condition Receipt of rerouted data from another cell.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1097 / 1256


24.3.3.2.1.10 P99 - NB_LLC_BYTES_DISC_SUSPEND

Long Name NB_LLC_BYTES_DISC_SUSPEND

Definition Number of LLC bytes discarded due to the suspend procedure.

Trigger Condition Suspend message received from BSC while DL PDUs are stored by RRM for thismobile. Queued PDUs or incoming PDUs received until suspend ack receptionfrom SGSN are deleted. The counter is expressed in "bytes".



Sub Domain 3 N/A



1098 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.3 DL PACCH

24.3.3.3.1 N/A

24.3.3.3.1.1 P438b - SIG_BLKS_NC2_DL_PACCH_PTM_LOAD

Long Name SIG_BLKS_NC2_DL_PACCH_PTM_LOAD

Definition Number of DL RLC control blocks sent on PACCH/D for MS in packet transfermode and used to carry NC2 signalling messages.

Trigger Condition The counter is incremented whenever the MFS sends a DL RLC control block onPACCH/D due to the NC2 mode of operation for MS in packet transfer mode.Therefore, this counter shall count the following downlink messages:- PacketMeasurement Order- Packet Cell Change Order.


Sub Domain 2 DL PACCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1099 / 1256


24.3.3.3.1.2 P457 - NB_PSI_MES

Long Name NB_PSI_MES

Definition Signalling load induced in the cell by the procedure of broadcast of (P)SI messages

Trigger Condition Number of RLC blocks used :1) To broadcast a PSI message for Packet PSIStatus feature2) To send a PACKET SERVING CELL DATA message for PacketSI Status feature.



Sub Domain 3 N/A



1100 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.3.1.3 P459 - NB_NEIGH_PSI_MES

Long Name NB_NEIGH_PSI_MES

Definition Signalling load induced in the cell by the procedure of broadcast of neighbour(P)SI messages

Trigger Condition Whenever a RLC block sent to the MS contains a PACKET NEIGHBOUR CELLDATA message for NACC feature.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1101 / 1256


24.3.3.3.1.4 P59 - NB_DL_RLC_BLOCK_PACCH

Long Name NB_DL_RLC_BLOCK_PACCH

Definition Number of DL RLC blocks sent on PACCH (excluding the dummy blocks). Theretransmitted blocks are counted.

Trigger Condition Whenever the MFS sends a DL RLC Block (different from a dummy block) onPACCH (RLC/MAC control messages).Note : PSCD/PNCD blocks are not takeninto account.



Sub Domain 3 N/A



1102 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4 DL RLC data flow

24.3.3.4.1 N/A

24.3.3.4.1.1 P20a - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1

Definition In acknowledged mode, number of DL RLC blocks (except RLC blocks containingLLC Dummy UI Commands only) on PDTCH encoded in CS-1 retransmitted dueto unacknowledgement of the MS.

Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emissionwindow) on PDTCH encoded in CS-1 is retransmitted to the MS. Theretransmissions of DL RLC DATA blocks in PENDING status within the emissionwindow are not counted (these blocks may be re-transmitted at the end of aTBF to speed up the release).In unacknowledged mode, P20a is equal to 0 (noretransmission). Note that RLC blocks containing LLC Dummy UI Commandsonly and that can be inserted by RLC to delay the release of the DL TBF arenot taken into account.


Sub Domain 2 DL RLC data flow

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1103 / 1256


24.3.3.4.1.2 P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2



Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emissionwindow) on PDTCH encoded in CS-2 is retransmitted to the MS. Theretransmissions of DL RLC DATA blocks in PENDING status within the emissionwindow are not counted (these blocks may be re-transmitted at the end of a TBFto speed up the release).In unacknowledged mode, the counter is equal to 0 (noretransmission). Note that RLC blocks containing LLC Dummy UI Commandsonly and that can be inserted by RLC to delay the release of the DL TBF arenot taken into account.



Sub Domain 3 N/A



1104 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.3 P20c - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3



Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emissionwindow) on PDTCH encoded in CS-3 is retransmitted to the MS. Theretransmissions of DL RLC DATA blocks in PENDING status within the transmitwindow are not counted (these blocks may be re-transmitted at the end of aTBF to speed up the release).In unacknowledged mode, P20c is equal to 0 (noretransmission).Note 1: This counter does not count the blocks re-transmitted atthe end of a TBF to speed up the release or when the RLC transmit window isstalled.Note 2: This counter does not count the RLC blocks containing LLC DummyUI Commands that can be inserted by RLC to delay the release of the DL TBF.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1105 / 1256


24.3.3.4.1.4 P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4



Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emissionwindow) on PDTCH encoded in CS-4 is retransmitted to the MS. Theretransmissions of DL RLC DATA blocks in PENDING status within the transmitwindow are not counted (these blocks may be re-transmitted at the end of aTBF to speed up the release).In unacknowledged mode, P20d is equal to 0 (noretransmission).Note 1: This counter does not count the blocks re-transmitted atthe end of a TBF to speed up the release or when the RLC transmit window isstalled.Note 2: This counter does not count the RLC blocks containing LLC DummyUI Commands that can be inserted by RLC to delay the release of the DL TBF.



Sub Domain 3 N/A



1106 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.5 P20f - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1

Definition In acknowledged mode, number of DL RLC data blocks (except RLC blockscontaining LLC Dummy UI Commands only) on PDTCH encoded in MCS-1retransmitted due to unacknowledgement of the MS.

Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emissionwindow) on PDTCH encoded in MCS-1 is retransmitted to the MS, the counter isincremented .The retransmissions of DL RLC DATA blocks in PENDING statuswithin the transmit window are not counted. In unacknowledged mode, the counteris equal to 0 (no retransmission).Note 1: This counter does not count the RLCblocks re-transmitted at the end of a TBF to speed up the releaseor when the RLCtransmit window is stalled.Note 2: This counter does not count the RLC blockscontaining LLC Dummy UI Commands that can be inserted by RLC to delay therelease of the DL TBF.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1107 / 1256


24.3.3.4.1.6 P20g - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2






Sub Domain 3 N/A



1108 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.7 P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1109 / 1256


24.3.3.4.1.8 P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4






Sub Domain 3 N/A



1110 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.9 P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1111 / 1256


24.3.3.4.1.10 P20k - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6






Sub Domain 3 N/A



1112 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.11 P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1113 / 1256


24.3.3.4.1.12 P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8






Sub Domain 3 N/A



1114 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.13 P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1115 / 1256


24.3.3.4.1.14 P350a - NB_DL_RADIO_BLOCK_PDTCH

Long Name NB_DL_RADIO_BLOCK_PDTCH

Definition Number of DL RLC/MAC data blocks sent on PDTCH. The retransmitted radioblocks are counted.

Trigger Condition The counter is incremented whenever the MFS sends a DL RLC/MAC data blockon PDTCH. Note that the RLC/MAC blocks containing LLC Dummy UI Commandsare also counted.



Sub Domain 3 N/A



1116 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.15 P421 - NB_DUMMY_RLC_DATA_BLOCKS

Long Name NB_DUMMY_RLC_DATA_BLOCKS

Definition Number of RLC data blocks containing only Dummy LLC UI Command PDUs thathave been sent on the radio interface.Note: This counter applies to both GPRSand EGPRS TBFs.

Trigger Condition Each time one RLC data block is sent, if this RLC data block contains onlyDummy LLC UI Command PDUs, this counter is incremented.Note that both initialtransmissions and retransmissions are counted.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1117 / 1256


24.3.3.4.1.16 P55a - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS1

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS1

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCHencoded in CS-1. The retransmitted blocks and RLC blocks containing LLCDummy UI Commands only are not counted.

Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-1 isacknowledged by the MS for the first time (previously in PENDING or UNACKstate within the emission window).Note that RLC blocks containing LLC DummyUI Commands only and that have been inserted by RLC to delay the release ofthe DL TBF are not taken into account.



Sub Domain 3 N/A



1118 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.17 P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1119 / 1256


24.3.3.4.1.18 P55c - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3






Sub Domain 3 N/A



1120 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.19 P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1121 / 1256


24.3.3.4.1.20 P55e - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCHencoded in MCS-1.

Trigger Condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-1 isacknowledged by the MS for the first time.If a DL RLC data block needs to bere-transmitted using a more robust MCS, the counter is incremented on receipt ofthe first acknowledgement of the corresponding re-transmitted block(s). In thiscase, only the counter corresponding to the MCS of the re-transmitted block(s) isincremented.Only the blocks successfully acknowledged by the MS are countedand these blocks are counted only once.Note that RLC blocks containing LLCDummy UI Commands only and that have been inserted by RLC to delay therelease of the DL TBF are not taken into account.



Sub Domain 3 N/A



1122 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.21 P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1123 / 1256


24.3.3.4.1.22 P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3






Sub Domain 3 N/A



1124 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.23 P55h - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCHencoded in MCS-4




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1125 / 1256


24.3.3.4.1.24 P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5






Sub Domain 3 N/A



1126 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.25 P55j - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCHencoded in MCS-6




Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1127 / 1256


24.3.3.4.1.26 P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7






Sub Domain 3 N/A



1128 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.27 P55l - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1129 / 1256


24.3.3.4.1.28 P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9






Sub Domain 3 N/A



1130 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.4.1.29 P72c - NB_DL_RLC_BYTES_PDTCH_LOST_CS

Long Name NB_DL_RLC_BYTES_PDTCH_LOST_CS

Definition In unacknowledged mode, number of DL RLC data bytes (except RLC blockscontaining LLC Dummy UI Commands only) on PDTCH encoded in CS-x (with x= 1 to 4) that are lost.

Trigger Condition In unacknowledged mode, the counter is incremented at reception of 04.60PACKET DL ACK/NACK by the number of DL RLC data bytes of the DL 04.60 RLCDATA BLOCK sent on PDTCH (encoded in CS-x with x = 1 to 4) since the previous04.60 PACKET DL ACK/NACK that are unacknowledged (NACK status in the RBBbitmap).In acknowledged mode, the value of the counter is equal to 0.Note thatRLC blocks containing LLC Dummy UI Commands only are not taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1131 / 1256


24.3.3.4.1.30 P72d - NB_DL_RLC_BYTES_PDTCH_LOST_MCS

Long Name NB_DL_RLC_BYTES_PDTCH_LOST_MCS

Definition In unacknowledged mode, number of DL RLC data bytes (except RLC blockscontaining LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x= 1 to 9) that are lost.

Trigger Condition In unacknowledged mode, the counter is incremented at reception of 04.60EGPRS PACKET DL ACK/NACK by the number of DL RLC data bytes of the DL04.60 RLC DATA BLOCK sent on PDTCH (encoded in MCS-x with x = 1 to 9) sincethe previous 04.60 EGPRS PACKET DL ACK/NACK that are unacknowledged(NACK status in the RBB bitmap).In acknowledged mode, the value of the counteris equal to 0.Note that RLC blocks containing LLC Dummy UI Commands only arenot taken into account.



Sub Domain 3 N/A



1132 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5 GPU load

24.3.3.5.1 N/A

24.3.3.5.1.1 P104 - NB_LLC_PDU_GPU

Long Name NB_LLC_PDU_GPU

Definition Number of LLC PDU transferred (UL+ DL), Sum of P74 and P75 (cell counters) foreach cells mapped on GPU.



Sub Domain 2 GPU load

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1133 / 1256


24.3.3.5.1.2 P201 - TIME_PTU_CPU_DSP_LOAD

Long Name TIME_PTU_CPU_DSP_LOAD

Definition This counter cumulates the time during which at least a DSP is in CPU load state.

Trigger Condition During the granularity period, the cumulated time during which at least a DSP isloaded is computed.The time is provided in seconds with one significant valueafter the comma (i.e. ROUND(10x) / 10). Note :A DSP is said loaded when itsCPU load is > =DSP_LOAD_THR1 and < DSP_LOAD_THR2.



Sub Domain 3 N/A



1134 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5.1.3 P202 - TIME_PTU_CPU_DSP_OVERLOAD

Long Name TIME_PTU_CPU_DSP_OVERLOAD

Definition This counter cumulates the time during which at least a DSP is in CPU overloadstate.

Trigger Condition During the granularity period, the cumulated time during which at least a DSP isoverloaded is computed.The time is provided in seconds with one significant valueafter the comma (i.e. ROUND(10x) / 10).Note : A DSP is said overloaded whenits CPU load is > =DSP_LOAD_THR2.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1135 / 1256


24.3.3.5.1.4 P384 - Time_DSP_Cong

Long Name Time_DSP_Cong

Definition DSP congestion duration (in seconds).

Trigger Condition The counter is started when a DSP of a GPU enters the congestion statebecause one of the following conditions is met:i) the maximum number ofGCHs that can be handled by a DSP is reached (MAX_GCH_DSP value -N_ATER_TS_MARGIN_GPU value) ,ii) the maximum number of TRXs that can behandled by a DSP is reached (MAX_TRX_DSP value) ,iii) the maximum numberof TBFs that can be handled by a DSP is reached (MAX_TBF_DSP value),iv) the maximum number of PDCHs that can be handled by a DSP is reached(MAX_PDCH_DSP value) ,v) the percentage of RLC memory resources usedwithin a DSP does not allow to serve new TBF (on this DSP) (current DSP memorycongestion state is different from NO_CONGESTION).The counter is stopped:when all the DSP have left the congestion state.



Sub Domain 3 N/A



1136 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5.1.5 P391a - NB_PS_PAGING_REQ_GPU

Long Name NB_PS_PAGING_REQ_GPU

Definition Number of PS paging requests processed by the GPU.

Trigger Condition Whenever a PS paging request is received from the SGSN.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1137 / 1256


24.3.3.5.1.6 P391b - NB_CS_PAGING_REQ_GPU

Long Name NB_CS_PAGING_REQ_GPU

Definition Number of CS paging requests processed by the GPU.

Trigger Condition Whenever a CS paging request is received from the SGSN.



Sub Domain 3 N/A



1138 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5.1.7 P392a - AV_NB_MS_CONTEXTS

Long Name AV_NB_MS_CONTEXTS

Definition Average number of contexts of MS (in RRM) observed during the granularityperiod.

Trigger Condition The number of contexts of MS (in RRM) is observed at each GAUGE polling value.At the end of the granularity period, the value is averaged.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1139 / 1256


24.3.3.5.1.8 P392b - MAX_NB_MS_CONTEXTS

Long Name MAX_NB_MS_CONTEXTS

Definition Maximum number of active contexts of MS (in RRM) observed during thegranularity period.

Trigger Condition Tide mark of counter P392a.



Sub Domain 3 N/A



1140 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5.1.9 P402 - TIME_PMU_OVERLOAD

Long Name TIME_PMU_OVERLOAD

Definition Cumulative time during which the GPU stays in the PMU CPU overload state dueto PMU CPU power limitations.

Trigger Condition The counter is:- Starts when the GPU enters the PMU CPU overload state,i.e. when the PMU CPU power budget is strictly higher than the thresholdPMU_CPU_Overload.- Stops when the GPU leaves the PMU CPU overloadstate, i.e. when the PMU CPU power budget is below or equal to the thresholdPMU_CPU_Overload



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1141 / 1256


24.3.3.5.1.10 P413 - NB_GPRS_SESSIONS

Long Name NB_GPRS_SESSIONS

Definition Number of (E)GPRS sessions. A session corresponds to a mobile station and theBSS exchanging packet data using downlink TBFs, uplink TBFs or both. There isalways at least one TBF active across the whole duration of a session or T3192 isrunning.

Trigger Condition A (E)GPRS session starts when for one mobile station, there was no on-goingTBF and one TBF is established. It ends when for that mobile station, there wasone (or two) on-going TBF(s) and one (or both) is (are) released and T3192 is nolonger running. During a session, TBFs may be established and released in bothdirections provided there is always at least one direction for which there is anon-going TBF or T3192 is running.The detailed triggers are described below:1) ifan MS has got no TBF established and a DL or UL TBF is established then thesession starts when the first RLC data block is sent or received on that TBF;2)in case an MS has got an UL TBF only, the current session ends when thelast UL RLC data block is received (and no retransmission is required in RLCacknowledged mode);3) in case an MS has got a DL TBF only, the current sessionends when the final (EGPRS) PACKET DOWNLINK ACK/NACK is received and noretransmission is required in RLC acknowledged mode, if T3192 is not started (i.e.T3192 = 0);4) in case an MS has got a DL TBF only, the final (EGPS) PACKETDOWNLINK ACK/NACK is received and no retransmission is required in RLCacknowledged mode, if T3192 is started, the session continues;5) in case an MShas got a DL (resp UL) TBF on-going and an UL (resp DL) TBF is established,then the session continues;6) in case an MS has got both a DL and an UL TBFson-going and one of the TBFs gets released, then the session continues;7) in casean MS has got both a DL and an UL TBFs on-going and both TBFs are releasedat the same time, but the timer T3192 is started, then the session continues(otherwise if T3192=0, then the session ends);8) in case an MS has got no TBFestablished, T3192 is running and reaches its expiry value, the session ends.



Sub Domain 3 N/A



1142 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.5.1.11 P76a - AV_PMU_CPU_POWER_BUDGET

Long Name AV_PMU_CPU_POWER_BUDGET

Definition Average PMU CPU power budget observed during the granularity period.

Trigger Condition The counter is the average value of all the samples of the PMU CPU power budgetover the granularity period.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1143 / 1256


24.3.3.5.1.12 P77a - MAX_PMU_CPU_POWER_BUDGET

Long Name MAX_PMU_CPU_POWER_BUDGET

Definition Maximum value of the PMU CPU power budget observed during the granularityperiod.

Trigger Condition Tidemark of the counter P76a.



Sub Domain 3 N/A



1144 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.6 Link control at RLC layer

24.3.3.6.1 N/A

24.3.3.6.1.1 P310a - NB_STALL_IND_MS_GPRS

Long Name NB_STALL_IND_MS_GPRS

Definition Number of stall indications from the MS for an GPRS uplink TBF.

Trigger Condition Detected transitions from SI=0 to SI=1 for an GPRS uplink TBF (stall indicationsfrom the MS).


Sub Domain 2 Link control at RLC layer

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1145 / 1256


24.3.3.6.1.2 P310b - NB_STALL_IND_MS_EGPRS

Long Name NB_STALL_IND_MS_EGPRS

Definition Number of stall indications from MS for an EGPRS uplink TBF.

Trigger Condition Detected transitions from SI=0 to SI=1 for an EGPRS uplink TBF (stall indicationsfrom the MS).



Sub Domain 3 N/A



1146 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.6.1.3 P310c - NB_STALL_STATE_GPRS_DL_TBF

Long Name NB_STALL_STATE_GPRS_DL_TBF

Definition Number of times the MFS RLC transmit window enters the stall state for a GPRSDL TBF.

Trigger Condition Whenever the MFS RLC transmit window enters the stall state for a GPRS DL TBF.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1147 / 1256


24.3.3.6.1.4 P310d - NB_STALL_STATE_EGPRS_DL_TBF

Long Name NB_STALL_STATE_EGPRS_DL_TBF

Definition Number of times the MFS RLC transmit window enters the stall state for anEGPRS DL TBF.

Trigger Condition Whenever the MFS RLC transmit window enters the stall state for an EGPRSDL TBF.



Sub Domain 3 N/A



1148 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.6.1.5 P335 - AV_DL_TX_EFF_GPRS

Long Name AV_DL_TX_EFF_GPRS

Definition Average TX_EFFICIENCY computed on DL TBFs established in GPRS mode.

Trigger Condition Each time TX_EFFICIENCY is tested on a DL TBF established in GPRS mode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1149 / 1256


24.3.3.6.1.6 P336 - AV_UL_TX_EFF_GPRS

Long Name AV_UL_TX_EFF_GPRS

Definition Average TX_EFFICIENCY computed on UL TBFs established in GPRS mode.

Trigger Condition Each time TX_EFFICIENCY is tested on an UL TBF established in GPRS mode.



Sub Domain 3 N/A



1150 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.6.1.7 P351a - NB_DL_CS_ADAPT_INCREASE

Long Name NB_DL_CS_ADAPT_INCREASE

Definition Number of coding scheme adaptations from a given coding scheme to a lessrobust coding scheme in the downlink direction for GPRS TBFs.

Trigger Condition The counter is incremented whenever the RLC layer triggers a change of codingscheme towards a less robust coding scheme in the downlink direction for aGPRS TBF.Note 1: This counter is never incremented when the data transfer isresumed while the DL TBF is in DL TBF delayed.Note 2: This counter does notapply to EGPRS TBFs.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1151 / 1256


24.3.3.6.1.8 P351b - NB_DL_CS_ADAPT_DECREASE

Long Name NB_DL_CS_ADAPT_DECREASE

Definition Number of coding scheme adaptations from a given coding scheme to a morerobust coding scheme in the downlink direction for GPRS TBFs.

Trigger Condition The counter is incremented whenever the RLC layer triggers a change of codingscheme towards a more robust coding scheme in the downlink direction (withthe exception below) for a GPRS TBF.Although the coding scheme may bechanged to become more robust, this counter is not incremented in the followingsituations:- When entering the delayed DL TBF release state to send Dummy UICommand,- When ordered by the RRM layer (e.g. in reallocation when old andnew TRX having different radio configuration),- When a consecutive lost of 04.60PACKET DOWNLINK ACK/NACK messages is detected,- When the data transferis resumed while the DL TBF is in DL TBF delayed state.Note: This counter doesnot apply to EGPRS TBFs.



Sub Domain 3 N/A



1152 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.6.1.9 P352a - NB_UL_CS_ADAPT_INCREASE

Long Name NB_UL_CS_ADAPT_INCREASE

Definition Number of coding scheme adaptations from a given coding scheme to a lessrobust coding scheme in the uplink direction for GPRS TBFs.

Trigger Condition The counter is incremented whenever the RLC layer triggers a change of codingscheme towards a less robust coding scheme in the uplink direction for a GPRSTBF.Note: This counter does not apply to EGPRS TBFs.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1153 / 1256


24.3.3.6.1.10 P352b - NB_UL_CS_ADAPT_DECREASE

Long Name NB_UL_CS_ADAPT_DECREASE

Definition Number of coding scheme adaptations from a given coding scheme to a morerobust coding scheme in the uplink direction for GPRS TBFs.

Trigger Condition The counter is incremented whenever the RLC layer triggers a change of codingscheme towards a more robust coding scheme in the uplink direction for a GPRSTBF.Although the coding scheme may be changed to become more robust, thiscounter is not incremented in the following situations:- When ordered by theRRM layer (e.g. in reallocation when old and new TRX having different radioconfiguration),- When the network receives an invalid UL RLC data block ornothing from the MS a certain number of times.Note: This counter does not applyto EGPRS TBFs.



Sub Domain 3 N/A



1154 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.7 MS capability

24.3.3.7.1 N/A

24.3.3.7.1.1 P450a - NB_R97_R98_MS_CONTEXT_GPU

Long Name NB_R97_R98_MS_CONTEXT_GPU

Definition Number of MS contexts created for Releases 1997 or 1998 mobile stations.

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context in the GPU and indicates that the MS is compliant to the3GPP standard Releases 1997 or 1998.


Sub Domain 2 MS capability

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1155 / 1256


24.3.3.7.1.2 P450b - NB_GPRS_R99_MS_CONTEXT_GPU

Long Name NB_GPRS_R99_MS_CONTEXT_GPU

Definition Number of MS contexts created for non-EGPRS capable Release 1999 onwardsmobile stations.

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context in the GPU and indicates that the MS is non-EGPRScapable and compliant to the 3GPP standard Release 1999 onwards.



Sub Domain 3 N/A



1156 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.7.1.3 P450c - NB_EGPRS_R99_MS_CONTEXT_GPU

Long Name NB_EGPRS_R99_MS_CONTEXT_GPU

Definition Number of MS contexts created for EGPRS capable Release 1999 onwardsmobile stations.

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context in the GPU and indicates that the MS is EGPRS capableand compliant to the 3GPP standard Release 1999 onwards.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1157 / 1256


24.3.3.7.1.4 P450d - NB_MS_CONTEXT_GPU

Long Name NB_MS_CONTEXT_GPU

Definition Number of MS contexts created.

Trigger Condition The counter is incremented the first time the MS Radio Access Capability isreceived for a given MS context Note : This counter is incremented whatever theMS release or feature supported by the MS.



Sub Domain 3 N/A



1158 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.7.1.5 P450e - NB_GERAN_FEATURE_PACK1_MS_CONTEXT_GPU

Long Name NB_GERAN_FEATURE_PACK1_MS_CONTEXT_GPU

Definition Number of MS contexts created for MS supporting the Geran feature package 1.

Trigger Condition The counter is incremented the first time the MS radio access capability isreceived for a given MS context and indicates that the MS supports the Geranfeature package 1.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1159 / 1256


24.3.3.7.1.6 P530a_1 - NB_MS_MULTISLOT_CLASS_0_TO_10

Long Name NB_MS_MULTISLOT_CLASS_0_TO_10

Definition Number of MS contexts created for MS whose multislot class belongs to the set ofmultislot classes 0 to 10.

Trigger Condition The counter is incremented the first time the MS radio access capability isreceived for a given MS context and indicates that the MS multislot class belongsto the set of multislot classes 0 to 10.Note :- In the MS Radio Access Capabilityparameter, only the GPRS multislot class, EGPRS multislot class , and HighMultislot Capability fields are taken into account if available.-If several multislotclass are available for the same MS (e-g GPRS MS class, EDGE MS class), thenonly one will be taken into consideration to increment the proper counter, basedon the following priorities in decreasing order:0-> EGPRS high multislot class,1->EGPRS multislot class,2-> GPRS high multislot class,3-> GPRS multislot class.



Sub Domain 3 N/A



1160 / 1256 3BK 21255 AAAA PCZZA Ed.07




Definition Number of MS contexts created for MS whose multislot class belongs to the setof multislot classes 11 to 12.

Trigger Condition The counter is incremented the first time the MS radio access capability isreceived for a given MS context and indicates that the MS multislot class belongsto the set of multislot classes 11 to 12.Note :- In the MS Radio Access Capabilityparameter, only the GPRS multislot class, EGPRS multislot class , and HighMultislot Capability fields are taken into account if available.-If several multislotclass are available for the same MS (e-g GPRS MS class, EDGE MS class), thenonly one will be taken into consideration to increment the proper counter, basedon the following priorities in decreasing order:0-> EGPRS high multislot class,1->EGPRS multislot class,2-> GPRS high multislot class,3-> GPRS multislot class.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1161 / 1256


24.3.3.7.1.8 P530a_3 - NB_MS_MULTISLOT_CLASS_3X

Long Name NB_MS_MULTISLOT_CLASS_3X

Definition Number of MS contexts created for MS whose multislot class belongs to the set ofmultislot classes of type 3X .

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context and indicates that the MS multislot class belongs to theset of multislot classes of type 3X.Note :- In the MS Radio Access Capabilityparameter, only the GPRS multislot class, EGPRS multislot class , and HighMultislot Capability fields are taken into account if available.-If several multislotclass are available for the same MS (e-g GPRS MS class, EDGE MS class), thenonly one will be taken into consideration to increment the proper counter, basedon the following priorities in decreasing order:0-> EGPRS high multislot class,1->EGPRS multislot class,2-> GPRS high multislot class,3-> GPRS multislot class.



Sub Domain 3 N/A



1162 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.7.1.9 P530a_4 - NB_MS_MULTISLOT_CLASS_4X

Long Name NB_MS_MULTISLOT_CLASS_4X

Definition Number of MS contexts created for MS whose multislot class belongs to the set ofmultislot classes of type 4X .

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context and indicates that the MS multislot class belongs to theset of multislot classes of type 4X.Note :- In the MS Radio Access Capabilityparameter, only the GPRS multislot class, EGPRS multislot class , and HighMultislot Capability fields are taken into account if available.-If several multislotclass are available for the same MS (e-g GPRS MS class, EDGE MS class), thenonly one will be taken into consideration to increment the proper counter, basedon the following priorities in decreasing order:0-> EGPRS high multislot class,1->EGPRS multislot class,2-> GPRS high multislot class,3-> GPRS multislot class.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1163 / 1256




Definition Number of MS contexts created for MS whose (PTM) high multislot class belongsto 30-34.

Trigger Condition The counter is incremented the first time the MS radio access capability isreceived for a given MS context and indicates that the MS (PTM) high multislotclass belongs to 30-34.Note :- In the MS Radio Access Capability parameter, onlythe GPRS multislot class, EGPRS multislot class, and High Multislot Capabilityfields are taken into account if available.-If several multislot classes are availablefor the same MS, then only one will be taken into consideration to increment theproper counter, based on the following priorities in decreasing order:0-> EGPRShigh multislot class,1-> EGPRS multislot class,2-> GPRS high multislot class,3->GPRS multislot class.



Sub Domain 3 N/A



1164 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.7.1.11 P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_34


Definition Number of MS contexts created for MS whose DTM high multislot class belongsto 31-34.

Trigger Condition The counter is incremented the first time the MS radio access capability is receivedfor a given MS context and indicates that the MS DTM high multislot class belongsto 31-34.Note :- In the MS Radio Access Capability parameter, only the DTMGPRS high multislot class and DTM EGPRS high multislot class fields are takeninto account if available.-If DTM GPRS and EGPRS high multislot classes areavailable for the same MS, then only one will be taken into consideration, basedon the following priorities in decreasing order:0-> DTM EGPRS high multislotclass,1-> DTM GPRS high multislot class,



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1165 / 1256


24.3.3.8 PAGCH

24.3.3.8.1 N/A

24.3.3.8.1.1 P400 - SIG_BLKS_PAGCH_LOAD

Long Name SIG_BLKS_PAGCH_LOAD

Definition Dedicated PAGCH signalling load on all the existing MPDCHs.The dedicatedPAGCH signalling load represents the number of blocks dedicated to Packet UplinkAssignment and Packet Access Reject messages over the granularity period.It evaluated as the weighted sum of these messages sent over the granularityperiod.A weight of 1 is given to the Packet UL Assignment messages sent onPAGCH or PPCH.A weight of 0.5 (assuming that 2 access rejects are gatheredin one single block) is given to a Packet Access Reject sent either on PAGCH orPPCH.Note that the Packet UL Assignment and Packet Access Reject messagessent on PPCH are counted with P400.

Trigger Condition The counter is incremented by 1 whenever a Packet UL Assignment is sent onPAGCH or PPCH.The counter is incremented by 0.5 whenever a Packet Accessreject message is sent on PAGCH or PPCH.


Sub Domain 2 PAGCH

Sub Domain 3 N/A



1166 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.9 PCH

24.3.3.9.1 N/A

24.3.3.9.1.1 P53a - NB_PS_PAGING_REQ_PCH

Long Name NB_PS_PAGING_REQ_PCH

Definition Number of (BSCGP) PAGING REQUEST for PS paging sent to the MS (throughthe BSC which manages the PCH resource).This counter gives an indication ofthe PCH load used for GPRS.

Trigger Condition Whenever a (BSCGP) PAGING REQUEST is sent to the MS for PS pagingwhatever may be the paging area (RA, LA, ...)


Sub Domain 2 PCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1167 / 1256


24.3.3.9.1.2 P53b - NB_CS_PAGING_REQ_PCH

Long Name NB_CS_PAGING_REQ_PCH

Definition Number of (BSCGP) PAGING REQUEST for CS paging sent to the MS (throughthe BSC which manages the PCH resource).This counter gives an indication ofthe PCH load used for GPRS.

Trigger Condition Whenever a (BSCGP) PAGING REQUEST is sent to the MS for CS pagingwhatever may be the paging area (RA, LA, ...)


Sub Domain 2 PCH

Sub Domain 3 N/A



1168 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.9.1.3 P53c - NB_IMM_ASS_PCH

Long Name NB_IMM_ASS_PCH

Definition Number of (BSCGP) IMMEDIATE ASSIGNMENT sent to the MS (through theBSC which manages the PCH resource) for a DL TBF establisment when the MSis in DRX mode.

Trigger Condition Whenever a (BSCGP) IMMEDIATE_ASSIGNMENT is sent to the MS on PCH.


Sub Domain 2 PCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1169 / 1256


24.3.3.10 PPCH

24.3.3.10.1 N/A

24.3.3.10.1.1 P61 - SIG_BLKS_PPCH_LOAD

Long Name SIG_BLKS_PPCH_LOAD

Definition Dedicated PPCH signalling load on all the existing MPDCHs.The dedicated PPCHsignalling load represents the number of PPCH blocks dedicated to CS/PS Pagingrequests and Packet Downlink Assignment messages over the granularity period.It is evaluated as the weighted sum of these messages sent over the granularityperiod. A weight of 0.5 (assuming that 2 paging requests are gathered in onesingle block) is given to a CS and PS paging sent on PPCH. A weight of 1 is givento the Packet DL Assignment messages sent on PPCH (in DRX and non DRXmode).Note that the Packet UL Assignment and Packet Access Reject messagessent on PPCH are not counted with P61, but with P400.

Trigger Condition The counter is incremented by 0.5 whenever a CS or PS paging is sent onPPCH.The counter is incremented by 1 whenever a Packet DL Assignment issent on PPCH.


Sub Domain 2 PPCH

Sub Domain 3 N/A



1170 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.10.1.2 P61a - NB_PACK_PS_PAGING_REQ_PPCH

Long Name NB_PACK_PS_PAGING_REQ_PPCH

Definition Number of 04.06 PACKET PAGING REQUEST for PS paging sent to the MS onPPCH.This counter gives an indication of the PPCH load.

Trigger Condition Whenever a 04.06 PACKET PAGING REQUEST is sent to the MS for PS paging.


Sub Domain 2 PPCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1171 / 1256


24.3.3.10.1.3 P61b - NB_PACK_CS_PAGING_REQ_PPCH

Long Name NB_PACK_CS_PAGING_REQ_PPCH

Definition Number of 04.06 PACKET PAGING REQUEST for CS paging sent to the MS onPPCH.This counter gives an indication of the PPCH load.

Trigger Condition Whenever a 04.06 PACKET PAGING REQUEST is sent to the MS for CS paging.


Sub Domain 2 PPCH

Sub Domain 3 N/A



1172 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.11 PRACH

24.3.3.11.1 N/A

24.3.3.11.1.1 P399 - SIG_BLKS_PRACH_LOAD

Long Name SIG_BLKS_PRACH_LOAD

Definition PRACH signalling load (expressed in blocks) on all the existing MPDCHs.ThePRACH signalling load is the weighted sum of the used PRACH bursts over thegranularity period. A weight of 0.25 (4 bursts per block) is given to a PRACH burstoccurrence carrying a (EGPRS) Packet Channel Request, whereas a weight of0.5 (1 collision = 2 MS attempts) is given to a PRACH burst occurrence on which acollision has been detected.

Trigger Condition The counter is updated whenever RRM receives from MAC the internal primitivePRH-PRACH-COLLISION-REPORT-cnf indicating the number of PRACH burstoccurrences carrying a (EGPRS) Packet Channel Request message, and thenumber of PRACH occurrences on which a collision has been detected.Remark:The primitive PRH-PRACH-COLLISION-REPORT-cnf is regularly sent by thePTU (on PMU demand).


Sub Domain 2 PRACH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1173 / 1256


24.3.3.11.1.2 P438d - SIG_BLKS_NC2_PRACH_LOAD

Long Name SIG_BLKS_NC2_PRACH_LOAD

Definition Number of Packet Channel Request messages with cause "Single block accesswithout TBF establishment".

Trigger Condition The counter is incremented whenever the MFS receives a Packet ChannelRequest messages with cause "Single block access without TBF establishment".


Sub Domain 2 PRACH

Sub Domain 3 N/A



1174 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.12 UL LLC data flow

24.3.3.12.1 N/A

24.3.3.12.1.1 P23 - NB_UL_LLC_BYTES_DISC_CONG

Long Name NB_UL_LLC_BYTES_DISC_CONG

Definition Number of UL LLC bytes discarded due to congestion in the SNS sublayer (theMS is obviously in packet transfer mode UL).

Trigger Condition Whenever an UL LLC PDU is discarded by the SNS sublayer due to congestionsituation on the Frame Relay.



Sub Domain 3 N/A

Measured Object PVC


3BK 21255 AAAA PCZZA Ed.07 1175 / 1256


24.3.3.12.1.2 P44a - NB_UL_LLC_BYTES_GPRS_ACK

Long Name NB_UL_LLC_BYTES_GPRS_ACK

Definition Number of UL LLC bytes received at RRM layer on UL TBFs established in GPRSmode and RLC acknowledged mode.

Trigger Condition Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an ULTBF established in GPRS mode and RLC acknowledged mode, the counter isincremented by the number of bytes of the received UL LLC PDU.



Sub Domain 3 N/A



1176 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.12.1.3 P44b - NB_UL_LLC_BYTES_GPRS_NACK

Long Name NB_UL_LLC_BYTES_GPRS_NACK

Definition Number of UL LLC bytes received at RRM layer on UL TBFs established in GPRSmode and RLC unacknowledged mode.

Trigger Condition Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an ULTBF established in GPRS mode and RLC unacknowledged mode, the counter isincremented by the number of bytes of the received UL LLC PDU.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1177 / 1256


24.3.3.12.1.4 P44c - NB_UL_LLC_BYTES_EGPRS_ACK

Long Name NB_UL_LLC_BYTES_EGPRS_ACK

Definition Number of UL LLC bytes received at RRM layer on UL TBFs established inEGPRS mode and RLC acknowledged mode.

Trigger Condition Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an ULTBF established in EGPRS mode and RLC acknowledged mode, the counter isincremented by the number of bytes of the received UL LLC PDU.



Sub Domain 3 N/A



1178 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.12.1.5 P44d - NB_UL_LLC_BYTES_EGPRS_NACK

Long Name NB_UL_LLC_BYTES_EGPRS_NACK

Definition Number of UL LLC bytes received at RRM layer on UL TBFs established inEGPRS mode and RLC unacknowledged mode.

Trigger Condition Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an ULTBF established in EGPRS mode and RLC unacknowledged mode, the counter isincremented by the number of bytes of the received UL LLC PDU.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1179 / 1256


24.3.3.12.1.6 P75 - NB_UL_PDU_TRANSMITTED

Long Name NB_UL_PDU_TRANSMITTED

Definition Number of LLC PDUs transmitted in UL during one granularity period.

Trigger Condition Whenever a LLC PDU is transmitted to SGSN.



Sub Domain 3 N/A



1180 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.13 UL PACCH

24.3.3.13.1 N/A

24.3.3.13.1.1 P401 - SIG_BLKS_PACCH_UL_LOAD

Long Name SIG_BLKS_PACCH_UL_LOAD

Definition UL PACCH signalling load on all the existing PCCCHs.The UL PACCH signallingload counts the number of PACCH/UL blocks used on PCCCHs over thegranularity period. The following messages are taken into account:- PacketControl Ack reported on UL path sent in answer to Packet DL Assignment sent onPCCCH;- Packet Resource Request reported on UL path sent in answer to PacketUL Assignment sent on PCCCH;- Packet Cell Change Failure sent in an UL RLCcontrol block on PCCCH;- Packet Measurement Report sent in an UL RLC controlblock on PCCCH.The messages sent on PACCH/UL of an on-going TBF are notcounted (Packet DL Ack/Nack, Packet Resource Request, Packet Control Ack).

Trigger Condition The counter is incremented by 1 whenever: - a Packet DL Assignment (with polling)is sent on PCCCH, or;- a Packet Resource Request is received in answer to aPacket UL Assignment sent on PCCCH;- a Packet Cell Change Failure or a PacketMeasurement Report message is received in an UL RLC control block on PCCCH.


Sub Domain 2 UL PACCH

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1181 / 1256


24.3.3.13.1.2 P438a - SIG_BLKS_NC2_UL_PACCH_PTM_LOAD

Long Name SIG_BLKS_NC2_UL_PACCH_PTM_LOAD

Definition Number of UL RLC control blocks received on PACCH/U for MS in packet transfermode and used to carry NC2 signalling messages.

Trigger Condition The counter is incremented whenever the MFS receives an UL RLC controlblock on PACCH/U due to the NC2 mode of operation for MS in packet transfermode. Therefore, this counter shall count the following uplink messages:- PacketMeasurement Report- Packet Cell Change Failure- Acknowledgement (valid ornot) of a Packet Cell Change Order message.



Sub Domain 3 N/A



1182 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.13.1.3 P438c - SIG_BLKS_NC2_UL_PACCH_CCCH_LOAD

Long Name SIG_BLKS_NC2_UL_PACCH_CCCH_LOAD

Definition Number of UL RLC control blocks received on PACCH/U for MS in packetidle mode and used to carry NC2 signalling messages (when no PCCCH isestablished in the cell)

Trigger Condition The counter is incremented whenever the MFS receives a Packet MeasurementReport or a Packet Cell Change Failure message on a non-PCCCH from a MS inpacket idle mode.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1183 / 1256


24.3.3.13.1.4 P439 - SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD

Long Name SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD

Definition Number of Packet Resource Request messages received on PACCH/U for MS inpacket idle mode (when no PCCCH is established in the cell).

Trigger Condition The counter is incremented whenever the MFS receives a Packet ResourceRequest message on a slave PDCH (i.e. on a PDCH not carrying any PCCCH)from a MS in packet idle mode.



Sub Domain 3 N/A



1184 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.13.1.5 P60 - NB_UL_RLC_BLOCK_PACCH

Long Name NB_UL_RLC_BLOCK_PACCH

Definition Number of UL RLC blocks received on PACCH (excluding the dummy blocks).The retransmitted blocks are counted.

Trigger Condition Whenever the MFS receives an UL RLC Block (different from a dummy block) onPACCH (RLC/MAC control message in normal burst format) whatever the modeof the MS is (packet transfer or packet idle mode).On slave PDCHs, the counteris incremented on receipt of one of the following messages:- a 04.60 PACKETRESOURCE REQUEST message,- a 04.60 (EGPRS) PACKET DOWNLINKACK/NACK message,- a 04.60 PACKET CELL CHANGE FAILURE message,- a04.60 PACKET MEASUREMENT REPORT message.- a 04.60 PACKET CELLCHANGE NOTIFICATION message.- a 04.60 PACKET PSI STATUS message.- a04.60 PACKET SI STATUS message.- a 04 60 PACKET MOBILE TBF STATUSmessage.On master PDCHs, the counter is incremented on receipt of one ofthe following messages:- a 04.60 PACKET RESOURCE REQUEST message,-a 04.60 PACKET CELL CHANGE FAILURE message,- a 04.60 PACKETMEASUREMENT REPORT message.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1185 / 1256


24.3.3.14 UL RLC data flow

24.3.3.14.1 N/A

24.3.3.14.1.1 P21a - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1

Definition In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-1retransmitted due to unacknowledgement of the MFS.

Trigger Condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded inCS-1 is correctly received by the MFS. In unacknowledged mode, the counteris equal to 0 (no retransmission).The Packet Uplink Dummy Control Blocks forExtended UL TBF mode feature shall not be taken into account.


Sub Domain 2 UL RLC data flow

Sub Domain 3 N/A



1186 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.2 P21b - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2



Trigger Condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded inCS-2 is correctly received by the MFS. In unacknowledged mode, the counteris equal to 0 (no retransmission).The Packet Uplink Dummy Control Blocks forExtended UL TBF mode feature shall not be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1187 / 1256


24.3.3.14.1.3 P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3



Trigger Condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded inCS-3 is correctly received by the MFS.In unacknowledged mode, the counteris equal to 0 (no retransmission).The Packet Uplink Dummy Control Blocks forExtended UL TBF mode feature shall not be taken into account.



Sub Domain 3 N/A



1188 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.4 P21d - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4



Trigger Condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded inCS-4 is correctly received by the MFS.In unacknowledged mode, the counteris equal to 0 (no retransmission).The Packet Uplink Dummy Control Blocks forExtended UL TBF mode feature shall not be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1189 / 1256


24.3.3.14.1.5 P21f - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1

Definition In acknowledged mode, number of UL RLC data blocks received on PDTCHencoded in MCS-1 retransmitted due to unacknowledgement of the MFS.

Trigger Condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encodedin MCS-1 is correctly received by the MFS, the counter is incremented.Inunacknowledged mode, the counter is equal to 0 (no retransmission).The PacketUplink Dummy Control Blocks for Extended UL TBF mode feature shall not betaken into account.



Sub Domain 3 N/A



1190 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.6 P21g - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1191 / 1256


24.3.3.14.1.7 P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3






Sub Domain 3 N/A



1192 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.8 P21i - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1193 / 1256


24.3.3.14.1.9 P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5






Sub Domain 3 N/A



1194 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.10 P21k - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1195 / 1256


24.3.3.14.1.11 P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7






Sub Domain 3 N/A



1196 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.12 P21m - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1197 / 1256


24.3.3.14.1.13 P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9






Sub Domain 3 N/A



1198 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.14 P350b - NB_UL_RADIO_BLOCK_PDTCH

Long Name NB_UL_RADIO_BLOCK_PDTCH

Definition Number of UL RLC/MAC data blocks received on PDTCH. The retransmittedradio blocks are counted.

Trigger Condition This counter is incremented whenever the MFS receives an UL RLC/MAC datablock on PDTCH.Packet Uplink Dummy Control Blocks shall not be taken intoaccount.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1199 / 1256


24.3.3.14.1.15 P462 - NB_DUMMY_UL_BLOCKS

Long Name NB_DUMMY_UL_BLOCKS

Definition Number of Packet Uplink Dummy Control blocks received on the radiointerface.Note: This counter applies to both GPRS and EGPRS TBFs.

Trigger Condition



Sub Domain 3 N/A



1200 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.16 P57a - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS1

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS1

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCHencoded in CS-1. The retransmitted blocks are not counted.

Trigger Condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-1 isreceived by the MFS for the first time.Packet Uplink Dummy Control Blocks shallnot be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1201 / 1256


24.3.3.14.1.17 P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2






Sub Domain 3 N/A



1202 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.18 P57c - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3



Trigger Condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-3/4 isreceived by the MFS for the first time.Packet Uplink Dummy Control Blocks shallnot be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1203 / 1256


24.3.3.14.1.19 P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4






Sub Domain 3 N/A



1204 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.20 P57e - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCHencoded in MCS-1.

Trigger Condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-1is received by the MFS for the first time.The retransmitted blocks are notcounted.Packet Uplink Dummy Control Blocks shall not be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1205 / 1256


24.3.3.14.1.21 P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2






Sub Domain 3 N/A



1206 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.22 P57g - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1207 / 1256


24.3.3.14.1.23 P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4






Sub Domain 3 N/A



1208 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.24 P57i - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1209 / 1256


24.3.3.14.1.25 P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6






Sub Domain 3 N/A



1210 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.26 P57k - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1211 / 1256


24.3.3.14.1.27 P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8






Sub Domain 3 N/A



1212 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.28 P57m - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9






Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1213 / 1256


24.3.3.14.1.29 P73c - NB_UL_RLC_BYTES_PDTCH_LOST_CS

Long Name NB_UL_RLC_BYTES_PDTCH_LOST_CS

Definition In unacknowledged mode, number of UL RLC data bytes on PDTCH encodedin CS-x (with x = 1 to 4) lost.

Trigger Condition In unacknowledged mode, whenever a UL 04.60 RLC DATA BLOCK on PDTCHencoded in CS-x (with x = 1 to 4) is not received (the awaited block defined to theMS by the USF is not received), the counter is incremented by the DL RLC databytes expected in the UL RLC data block.In acknowledged mode, the value of thecounter is equal to 0.Lost RLC data block corresponding to the USFs scheduledduring the UL extension phase shall not be taken into account.



Sub Domain 3 N/A



1214 / 1256 3BK 21255 AAAA PCZZA Ed.07


24.3.3.14.1.30 P73d - NB_UL_RLC_BYTES_PDTCH_LOST_MCS

Long Name NB_UL_RLC_BYTES_PDTCH_LOST_MCS

Definition In unacknowledged mode, number of UL RLC data bytes on PDTCH encoded inMCS-x (with x = 1 to 9) lost.

Trigger Condition In unacknowledged mode, whenever a UL 04.60 RLC DATA BLOCK on PDTCHencoded in MCS-x (with x = 1 to 9) is not received (the awaited block defined to theMS by the USF is not received), the counter is incremented by the DL RLC databytes expected in the UL RLC data block.In acknowledged mode, the value of thecounter is equal to 0.Lost RLC data block corresponding to the USFs scheduledduring the UL extension phase shall not be taken into account.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1215 / 1256


1216 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25 MFS-LCS Counters

3BK 21255 AAAA PCZZA Ed.07 1217 / 1256

25 MFS-LCS Counters

25.1 Quality of service


25.1.1.1 Assistance data for MS

25.1.1.1.1 N/A

25.1.1.1.1.1 P801 - NB_ASSIST_DATA_REQ

Long Name NB_ASSIST_DATA_REQ

Definition Number of received LCS requests for GPS assistance data (initially requested bythe MS) received from the BSC.

Trigger Condition Incremented each times the SMLC receives a BSCLP PERFORM LOCATIONREQUEST from the BSC with MIE Location Type set to "location assistanceinformation for the target MS" and CIE "GPS Assistance Data" is present.


Sub Domain 2 Assistance data for MS

Sub Domain 3 N/A

Measured Object LcsCell


1218 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.1.1.2 P802 - NB_ASSIST_DATA_SUCC

Long Name NB_ASSIST_DATA_SUCC

Definition Number of successful GPS assistance data delivery (initially requested by theMS) responses sent to the BSC.

Trigger Condition Incremented each times the SMLC sends a BSCLP PERFORM LOCATIONRESPONSE to the BSC without containing neither the OIE Location estimate northe OIE LCS cause (response in case of successful assistance data delivery).


Sub Domain 2 Assistance data for MS

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1219 / 1256

25 MFS-LCS Counters

25.1.1.2 Location estimate

25.1.1.2.1 N/A

25.1.1.2.1.1 P800 - NB_LOC_REQ

Long Name NB_LOC_REQ

Definition Number of received LCS requests for MS positioning received from the BSC.

Trigger Condition Incremented whenever the SMLC receives a BSCLP PERFORM LOCATIONREQUEST from BSC with MIE Location Type set to "current geographic location"


Sub Domain 2 Location estimate

Sub Domain 3 N/A



1220 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.2.1.2 P803 - NB_LOC_TA_SUCC

Long Name NB_LOC_TA_SUCC

Definition Number of successful location responses sent to the BSC using TA positioningmethod.

Trigger Condition Incremented each times the SMLC sends to the BSC a BSCLP PERFORMLOCATION RESPONSE message with the OIE Location Estimate and the OIEPositioning Data containing field Positioning Method set to "Timing Advance", andthe associated field "usage" set to "Results used to generate location".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1221 / 1256

25 MFS-LCS Counters

25.1.1.2.1.3 P804 - NB_LOC_CONV_GPS_SUCC

Long Name NB_LOC_CONV_GPS_SUCC

Definition Number of successful location response sent to the BSC using ConventionalGPS positioning method.

Trigger Condition Incremented each times the SMLC sends to the BSC a BSCLP PERFORMLOCATION RESPONSE message with the OIE Location Estimate and the OIEPositioning Data containing field Positioning Method set to "Conventional GPS",and the associated field "usage" set to "Results used to generate location".



Sub Domain 3 N/A



1222 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.2.1.4 P805 - NB_LOC_MA_AGPS_SUCC

Long Name NB_LOC_MA_AGPS_SUCC

Definition Number of successful location responses sent to the BSC using MS AssistedA-GPS positioning method.

Trigger Condition Incremented each times the SMLC sends to the BSC a BSCLP PERFORMLOCATION RESPONSE message with the OIE Location Estimate and the OIEPositioning Data containing field Positioning Method set to "Mobile assisted GPS",and the associated field "usage" set to "Results used to generate location".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1223 / 1256

25 MFS-LCS Counters

25.1.1.2.1.5 P806 - NB_LOC_MB_AGPS_SUCC

Long Name NB_LOC_MB_AGPS_SUCC

Definition Number of successful location response sent to the BSC using MS Based A-GPSpositioning method.

Trigger Condition Incremented each times the SMLC sends to the BSC a BSCLP PERFORMLOCATION RESPONSE message with the OIE Location Estimate and the OIEPositioning Data containing field Positioning Method set to "Mobile based GPS",and the associated field "usage" set to "results used to generate location".



Sub Domain 3 N/A



1224 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.3 Location estimate / Assistance data for MS

25.1.1.3.1 N/A

25.1.1.3.1.1 P814 - NB_LCS_PROTOCOL_ERROR

Long Name NB_LCS_PROTOCOL_ERROR

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due to LCS protocol error.

Trigger Condition Incremented whenever the SMLC sends to the BSC a BSCLP PERFORMLOCATION RESPONSE with LCS cause IEset to:- Unspecified- protocol error-Data missing in position request- Unexpected data value in position request-Target MS Unreachable- Location request aborted


Sub Domain 2 Location estimate / Assistance data for MS

Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1225 / 1256

25 MFS-LCS Counters

25.1.1.3.1.2 P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO

Long Name NB_LCS_INTERRUPTED_INTRA_BSC_HO

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due to intra-BSC handover.

Trigger Condition Incremented whenever the SMLC receives a BSCLPPERFORM_LOCATION_ABORT with cause "Intra-BSC hand-over complete"or when it receives either a BSCLP COI RESET or a BSCLP COI ABORTwith cause "intra-BSS hand-over".



Sub Domain 3 N/A



1226 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.3.1.3 P816 - NB_LCS_INTERRUPTED_INTER_BSC_HO

Long Name NB_LCS_INTERRUPTED_INTER_BSC_HO

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due to inter-BSC hand-over.

Trigger Condition Incremented whenever the SMLC receives a BSCLPPERFORM_LOCATION_ABORT with cause "Inter-BSC hand-over on-going" orwhen it receives a BSCLP COI ABORT with cause "inter-BSS hand-over".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1227 / 1256

25 MFS-LCS Counters

25.1.1.3.1.4 P817 - NB_LCS_FAILURE_RRLP

Long Name NB_LCS_FAILURE_RRLP

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due to RRLP problem.

Trigger Condition Incremented each times the SMLC receives a 04.31 RRLP (Protocol error)from the MS, or each times any 04.31 RRLP message from the MS is notcomplete/understandable.



Sub Domain 3 N/A



1228 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.3.1.5 P818 - NB_LCS_FAILURE_TIMER_EXPIRY

Long Name NB_LCS_FAILURE_TIMER_EXPIRY

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due to LCS guard timer expiry.

Trigger Condition Incremented whenever one of the timer set to control the location processexpires in the SMLC (Timer currently defined are: T_LCS_LowDelay,T_LCS_DelayTolerent, T_RRLP_LowDelay, T_RRLP_DelayTolerent)



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1229 / 1256

25 MFS-LCS Counters

25.1.1.3.1.6 P819 - NB_LCS_FAILURE_INTERNAL

Long Name NB_LCS_FAILURE_INTERNAL

Definition Number of failed LCS procedures (considering LCS requests for MS positioningand LCS requests for GPS assistance data) due internal problem detected by theMFS/SMLC.

Trigger Condition Incremented each times PRCF or PCF returns an error which is not linked to timerexpiry or to BSCLP/RRLP protocol error.and/orIncremented whenever the SMLCsends to the BSC a BSCLP PERFORM LOCATION RESPONSE with LCS causeIE set to:- System Failure- Congestion



Sub Domain 3 N/A



1230 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.3.1.7 P820 - NB_UNKNOWN_LCS_REQ

Long Name NB_UNKNOWN_LCS_REQ

Definition Number of LCS requests rejected because not supported by the SMLC.

Trigger Condition Incremented each times the SMLC receives a BSCLP PERFORM LOCATIONREQUEST from BSC:- with MIE Location Type neither set to "Current geographiclocation", nor to "Location assistance information for the target MS"- or with MIELocation Type set to "Location assistance information for the target MS" but CIE"GPS Assistance Data" is not present.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1231 / 1256

25 MFS-LCS Counters

25.1.1.4 Positioning method

25.1.1.4.1 N/A

25.1.1.4.1.1 P807 - NB_LOC_TA_PCF_REQ

Long Name NB_LOC_TA_PCF_REQ

Definition Number of location calculation attempts with TA positioning PCF.

Trigger Condition Incremented each times a geographical location is processed using PCF "CI+TA"


Sub Domain 2 Positioning method

Sub Domain 3 N/A



1232 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.4.1.2 P808 - NB_LOC_TA_PCF_SUCC

Long Name NB_LOC_TA_PCF_SUCC

Definition Number of location calculations successfully performed with TA positioning PCF.

Trigger Condition Incremented each times "CI+TA" PCF algorithm returns a positioning estimationwithout error indications.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1233 / 1256

25 MFS-LCS Counters

25.1.1.4.1.3 P809 - NB_LOC_CONV_GPS_PCF_REQ

Long Name NB_LOC_CONV_GPS_PCF_REQ

Definition Number of location calculation attempts with Conventional GPS PCF.

Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF"Conventional GPS".



Sub Domain 3 N/A



1234 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.4.1.4 P810 - NB_LOC_MA_AGPS_PCF_REQ

Long Name NB_LOC_MA_AGPS_PCF_REQ

Definition Number of location calculation attempts with MS Assisted A-GPS PCF.

Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF"MS assisted GPS".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1235 / 1256

25 MFS-LCS Counters

25.1.1.4.1.5 P811 - NB_LOC_MA_AGPS_PCF_SUCC

Long Name NB_LOC_MA_AGPS_PCF_SUCC

Definition Number of location calculations successfully performed with MS Assisted A-GPSPCF.

Trigger Condition Incremented each times the PCF "MS-assisted A-GPS" returns a position estimatewithout error indications.



Sub Domain 3 N/A



1236 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.4.1.6 P812 - NB_LOC_MB_AGPS_PCF_REQ

Long Name NB_LOC_MB_AGPS_PCF_REQ

Definition Number of location calculation attempts with MS Based A-GPS PCF.

Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF"MS-based A-GPS".



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1237 / 1256

25 MFS-LCS Counters

25.1.1.4.1.7 P813 - NB_LOC_MB_AGPS_PCF_SUCC

Long Name NB_LOC_MB_AGPS_PCF_SUCC

Definition Number of location calculations successfully performed with MS Based A-GPS.

Trigger Condition Incremented each times PCF "MS-based A-GPS" returns a position estimatewith no error indication.



Sub Domain 3 N/A



1238 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.1.1.4.1.8 P821 - NB_LOC_CONV_GPS_PCF_SUCC

Long Name NB_LOC_CONV_GPS_PCF_SUCC

Definition Number of location calculations successfully performed with Conventional GPSPCF.

Trigger Condition Incremented each times "Conventional GPS" PCF returns a position estimationwithout error indication.



Sub Domain 3 N/A



3BK 21255 AAAA PCZZA Ed.07 1239 / 1256

25 MFS-LCS Counters

25.2 Traffic load


25.2.1.1 Positioning statistics

25.2.1.1.1 Conventional GPS

25.2.1.1.1.1 P824 - AV_CONV_GPS_LAT

Long Name AV_CONV_GPS_LAT

Definition Averaged latitude of the mobile stations obtained with Conventional GPS PCF

Trigger Condition The MFS maintains a sum of the latitudes obtained with Conventional GPS PCFas well as the number of latitude measurements obtained with Conventional GPSPCF. Whenever Conventional GPS PCF algorithm returns a positioning estimationwithout error indications,- the sum is incremented by the latitude of the mobilestation.- the number of latitude measurements is incremented by one.At the expiryof the reporting period, the MFS computes the average by dividing the obtainedsum by the obtained number of measurements.


Sub Domain 2 Positioning statistics

Sub Domain 3 Conventional GPS



1240 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.1.2 P825 - AV_CONV_GPS_LONG

Long Name AV_CONV_GPS_LONG

Definition Averaged longitude of the mobile stations obtained with Conventional GPS PCF

Trigger Condition The MFS maintains a sum of the longitudes obtained with Conventional GPS PCFas well as the number of longitude measurements obtained with ConventionalGPS PCF. Whenever Conventional GPS PCF algorithm returns a positioningestimation without error indications,- the sum is incremented by the longitudeof the mobile station.- the number of longitude measurements is incrementedby one.At the expiry of the reporting period, the MFS computes the average bydividing the obtained sum by the obtained number of measurements.






3BK 21255 AAAA PCZZA Ed.07 1241 / 1256

25 MFS-LCS Counters

25.2.1.1.1.3 P832 - ST_DEV_CONV_GPS_LAT

Long Name ST_DEV_CONV_GPS_LAT

Definition Standard deviation of the latitude of the mobile stations obtained with ConventionalGPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared latitudes obtained with ConventionalGPS PCF,- a second sum S2 of latitudes obtained with Conventional GPSPCF,- the number N of latitude measurements obtained with Conventional GPSPCF.Whenever Conventional GPS PCF algorithm returns a positioning estimationwithout error indications,- the first sum S1 is incremented by the squared latitudeof the mobile station,- the second sum S2 is incremented by the latitude of themobile station,- the number N of latitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the standard deviation asfollows:Standard_Deviation = Square_Root(Variance)whereVariance = S1/N -(S2/N)^2.






1242 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.1.4 P833 - ST_DEV_CONV_GPS_LONG

Long Name ST_DEV_CONV_GPS_LONG

Definition Standard deviation of the longitude of the mobile stations obtained withConventional GPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared longitudes obtained withConventional GPS PCF,- a second sum S2 of longitudes obtained withConventional GPS PCF,- the number N of longitude measurements obtainedwith Conventional GPS PCF.Whenever Conventional GPS PCF algorithmreturns a positioning estimation without error indications,- the first sum S1 isincremented by the squared longitude of the mobile station,- the second sum S2is incremented by the longitude of the mobile station,- the number N of longitudemeasurements is incremented by one.At the expiry of the reporting period,the MFS computes the standard deviation as follows:Standard_Deviation =Square_Root(Variance)whereVariance = S1/N - (S2/N)^2.






3BK 21255 AAAA PCZZA Ed.07 1243 / 1256

25 MFS-LCS Counters

25.2.1.1.2 MS assisted A-GPS

25.2.1.1.2.1 P826 - AV_MA_AGPS_LAT

Long Name AV_MA_AGPS_LAT

Definition Averaged latitude of the mobile stations obtained with MS Assisted A-GPS PCF

Trigger Condition The MFS maintains a sum of the latitudes obtained with MS Assisted A-GPSPCF as well as the number of latitude measurements obtained with MS AssistedA-GPS PCF. Whenever MS Assisted A-GPS PCF algorithm returns a positioningestimation without error indications,- the sum is incremented by the latitude of themobile station.- the number of latitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the average by dividing theobtained sum by the obtained number of measurements.



Sub Domain 3 MS assisted A-GPS



1244 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.2.2 P827 - AV_MA_AGPS_LONG

Long Name AV_MA_AGPS_LONG

Definition Averaged longitude of the mobile stations obtained with MS Assisted A-GPS PCF

Trigger Condition The MFS maintains a sum of the longitudes obtained with MS Assisted A-GPSPCF as well as the number of longitude measurements obtained with MS AssistedA-GPS PCF. Whenever MS Assisted A-GPS PCF algorithm returns a positioningestimation without error indications,- the sum is incremented by the longitudeof the mobile station.- the number of longitude measurements is incrementedby one.At the expiry of the reporting period, the MFS computes the average bydividing the obtained sum by the obtained number of measurements.






3BK 21255 AAAA PCZZA Ed.07 1245 / 1256

25 MFS-LCS Counters

25.2.1.1.2.3 P834 - ST_DEV_MA_AGPS_LAT

Long Name ST_DEV_MA_AGPS_LAT

Definition Standard deviation of the latitude of the mobile stations obtained with MS AssistedA-GPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared latitudes obtained with MS AssistedA-GPS PCF,- a second sum S2 of latitudes obtained with MS Assisted A-GPSPCF,- the number N of latitude measurements obtained with MS Assisted A-GPSPCF.Whenever MS Assisted A-GPS PCF algorithm returns a positioning estimationwithout error indications,- the first sum S1 is incremented by the squared latitudeof the mobile station,- the second sum S2 is incremented by the latitude of themobile station,- the number N of latitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the standard deviation asfollows:Standard_Deviation = Square_Root(Variance)whereVariance = S1/N -(S2/N)^2.






1246 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.2.4 P835 - ST_DEV_MA_AGPS_LONG

Long Name ST_DEV_MA_AGPS_LONG

Definition Standard deviation of the longitude of the mobile stations obtained with MSAssisted A-GPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared longitudes obtained with MSAssisted A-GPS PCF,- a second sum S2 of longitudes obtained with MSAssisted A-GPS PCF,- the number N of longitude measurements obtainedwith MS Assisted A-GPS PCF.Whenever MS Assisted A-GPS PCF algorithmreturns a positioning estimation without error indications,- the first sum S1 isincremented by the squared longitude of the mobile station,- the second sum S2is incremented by the longitude of the mobile station,- the number N of longitudemeasurements is incremented by one.At the expiry of the reporting period,the MFS computes the standard deviation as follows:Standard_Deviation =Square_Root(Variance)whereVariance = S1/N - (S2/N)^2.






3BK 21255 AAAA PCZZA Ed.07 1247 / 1256

25 MFS-LCS Counters

25.2.1.1.3 MS based A-GPS

25.2.1.1.3.1 P828 - AV_MB_AGPS_LAT

Long Name AV_MB_AGPS_LAT

Definition Averaged latitude of the mobile stations obtained with MS Based A-GPS PCF

Trigger Condition The MFS maintains a sum of the latitudes obtained with MS Based A-GPS PCFas well as the number of latitude measurements obtained with MS Based A-GPSPCF. Whenever MS Based A-GPS PCF algorithm returns a positioning estimationwithout error indications,- the sum is incremented by the latitude of the mobilestation.- the number of latitude measurements is incremented by one.At the expiryof the reporting period, the MFS computes the average by dividing the obtainedsum by the obtained number of measurements.



Sub Domain 3 MS based A-GPS



1248 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.3.2 P829 - AV_MB_AGPS_LONG

Long Name AV_MB_AGPS_LONG

Definition Averaged longitude of the mobile stations obtained with MS Based A-GPS PCF

Trigger Condition The MFS maintains a sum of the longitudes obtained with MS Based A-GPS PCFas well as the number of longitude measurements obtained with MS Based A-GPSPCF. Whenever MS Based A-GPS PCF algorithm returns a positioning estimationwithout error indications,- the sum is incremented by the longitude of the mobilestation.- the number of longitude measurements is incremented by one.At theexpiry of the reporting period, the MFS computes the average by dividing theobtained sum by the obtained number of measurements.






3BK 21255 AAAA PCZZA Ed.07 1249 / 1256

25 MFS-LCS Counters

25.2.1.1.3.3 P836 - ST_DEV_MB_AGPS_LAT

Long Name ST_DEV_MB_AGPS_LAT

Definition Standard deviation of the latitude of the mobile stations obtained with MS BasedA-GPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared latitudes obtained with MS BasedA-GPS PCF,- a second sum S2 of latitudes obtained with MS Based A-GPSPCF,- the number N of latitude measurements obtained with MS Based A-GPSPCF.Whenever MS Based A-GPS PCF algorithm returns a positioning estimationwithout error indications,- the first sum S1 is incremented by the squared latitudeof the mobile station,- the second sum S2 is incremented by the latitude of themobile station,- the number N of latitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the standard deviation asfollows:Standard_Deviation = Square_Root(Variance)whereVariance = S1/N -(S2/N)^2.At the expiry of the reporting period, the MFS computes the varianceby dividing the obtained sum by the obtained number of measurements. Thestandard deviation is obtained by computing the square root of the variance.






1250 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.3.4 P837 - ST_DEV_MB_AGPS_LONG

Long Name ST_DEV_MB_AGPS_LONG

Definition Standard deviation of the longitude of the mobile stations obtained with MS BasedA-GPS PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared longitudes obtained with MS BasedA-GPS PCF,- a second sum S2 of longitudes obtained with MS Based A-GPSPCF,- the number N of longitude measurements obtained with MS Based A-GPSPCF.Whenever MS Based A-GPS PCF algorithm returns a positioning estimationwithout error indications,- the first sum S1 is incremented by the squared longitudeof the mobile station,- the second sum S2 is incremented by the longitude ofthe mobile station,- the number N of longitude measurements is incrementedby one.At the expiry of the reporting period, the MFS computes the standarddeviation as follows:Standard_Deviation = Square_Root(Variance)whereVariance= S1/N - (S2/N)^2.






3BK 21255 AAAA PCZZA Ed.07 1251 / 1256

25 MFS-LCS Counters

25.2.1.1.4 TA positioning

25.2.1.1.4.1 P822 - AV_TA_LAT

Long Name AV_TA_LAT

Definition Averaged latitude of the mobile stations obtained with TA positioning PCF

Trigger Condition The MFS maintains a sum of the latitudes obtained with TA positioning PCF aswell as the number of latitude measurements obtained with TA positioning PCF.Whenever "CI+TA" PCF algorithm returns a positioning estimation without errorindications,- the sum is incremented by the latitude of the mobile station.- thenumber of latitude measurements is incremented by one.At the expiry of thereporting period, the MFS computes the average by dividing the obtained sum bythe obtained number of measurements.



Sub Domain 3 TA positioning



1252 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.4.2 P823 - AV_TA_LONG

Long Name AV_TA_LONG

Definition Averaged longitude of the mobile stations obtained with TA positioning PCF

Trigger Condition The MFS maintains a sum of the longitudes obtained with TA positioning PCF aswell as the number of longitude measurements obtained with TA positioning PCF.Whenever "CI+TA" PCF algorithm returns a positioning estimation without errorindications,- the sum is incremented by the longitude of the mobile station.- thenumber of longitude measurements is incremented by one.At the expiry of thereporting period, the MFS computes the average by dividing the obtained sum bythe obtained number of measurements.






3BK 21255 AAAA PCZZA Ed.07 1253 / 1256

25 MFS-LCS Counters

25.2.1.1.4.3 P830 - ST_DEV_TA_LAT

Long Name ST_DEV_TA_LAT

Definition Standard deviation of the latitude of the mobile stations obtained with TApositioning PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared latitudes obtained with TApositioning PCF,- a second sum S2 of latitudes obtained with TA positioningPCF,- the number N of latitude measurements obtained with TA positioningPCF.Whenever "CI+TA" PCF algorithm returns a positioning estimation withouterror indications,- the first sum S1 is incremented by the squared latitude ofthe mobile station,- the second sum S2 is incremented by the latitude of themobile station,- the number N of latitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the standard deviation asfollows:Standard_Deviation = Square_Root(Variance)whereVariance = S1/N(S2/N)^2.






1254 / 1256 3BK 21255 AAAA PCZZA Ed.07

25 MFS-LCS Counters

25.2.1.1.4.4 P831 - ST_DEV_TA_LONG

Long Name ST_DEV_TA_LONG

Definition Standard deviation of the longitude of the mobile stations obtained with TApositioning PCF

Trigger Condition The MFS maintains:- a first sum S1 of squared longitudes obtained with TApositioning PCF,- a second sum S2 of longitudes obtained with TA positioningPCF,- the number N of longitude measurements obtained with TA positioningPCF.Whenever "CI+TA" PCF algorithm returns a positioning estimation withouterror indications,- the first sum S1 is incremented by the squared longitude of themobile station,- the second sum S2 is incremented by the longitude of the mobilestation,- the number N of longitude measurements is incremented by one.Atthe expiry of the reporting period, the MFS computes the standard deviation asfollows:Standard_Deviation = Square_Root(Variance)whereVariance = S1/N -(S2/N)^2.






3BK 21255 AAAA PCZZA Ed.07 1255 / 1256

25 MFS-LCS Counters

BLANK PAGE BREAK

1256 / 1256 3BK 21255 AAAA PCZZA Ed.07

alcatel counters

Documents

system defense

imsi detach

normal eventcall

dynamic sdcch8

radio link

message sequence

assign command

ms access