B10 PM Counter Ed9 PDF

Alcatel-Lucent GSM
PM Counters
OMC Document
Reference Guide
Release B10
3BK 21255 AAAA PCZZA Ed.09
BLANK PAGE BREAK
Status
RELEASED
Short title
PM Counters
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel-Lucent.
2 / 1392
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1
10
11
12
BSC-TYPE 1 - Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1
All TYPE 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3
Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4
Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
1.5
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
BSC-TYPE 2 - Resource availability measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.1
All TYPE 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2.2
Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
BSC-TYPE 3 - Resource usage on CCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.1
All TYPE 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.2
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
BSC-TYPE 4 - Resource usage on SDCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.1
All TYPE 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.2
Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
BSC-TYPE 5 - Resource usage on TCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.1
All TYPE 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.2
5.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
BSC-TYPE 6 - TCH handover measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
6.1
All TYPE 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.2
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
BSC-TYPE 7 - LapD measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7.1
All TYPE 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.2
Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3
7.4
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
BSC-TYPE 8 - X25 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
8.1
All TYPE 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
8.2
8.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
BSC-TYPE 9 - N7 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
9.1
All TYPE 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
9.2
9.3
9.4
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
BSC-TYPE 18 - A interface measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.1
All TYPE 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
10.2
10.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
BSC-TYPE 19 - SMS PP measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
11.1
All TYPE 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
11.2
BSC-TYPE 25 - SCCP measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
12.1
All TYPE 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
3 / 1392
Contents
13
14
15
16
17
18
19
20
21
22
23
24
25
12.2
12.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
BSC-TYPE 26 - TCH outgoing handover per adjacency measurements . . . . . . . . . . . . . . . . . . . . . 287
13.1
All TYPE 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
13.2
Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
BSC-TYPE 27 - 2G TCH incoming handover per adjacency measurements . . . . . . . . . . . . . . . . . 297
14.1
All TYPE 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
14.2
Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
BSC-TYPE 28 - SDCCH handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
15.1
All TYPE 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
15.2
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
BSC-TYPE 29 - Directed retry measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
16.1
All TYPE 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
16.2
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
BSC-TYPE 30 - SMS CB measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
17.1
All TYPE 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
17.2
17.3
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
BSC-TYPE 31 - Radio Measurement Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
18.1
All TYPE 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
18.2
18.3
BSC-TYPE 32 - Change of frequency band measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
19.1
All TYPE 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
19.2
BSC-TYPE 33 - Electro-Magnetic Emission counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
20.1
All TYPE 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
20.2
Electro-Magnetic Emission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
BSC-TYPE 34 - Voice Group Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
21.1
All TYPE 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
21.2
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
21.3
21.4
21.5
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
BSC-TYPE 110 - Overview measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
22.1
All TYPE 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
22.2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
22.3
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
22.4
22.5
22.6
Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
BSC-TYPE 180 - 2G Traffic flow measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
23.1
All TYPE 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
23.2
Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
MFS-GPRS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
24.1
All MFS-GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
24.2
Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
24.3
Resource availability and usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
24.4
Traffic load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
MFS-LCS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
25.1
All MFS-LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1352
4 / 1392
Contents
25.2
25.3
Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353

Traffic load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
5 / 1392
Contents
6 / 1392
Preface
Preface
Purpose
The PM Counters include description of:

GSM Counters
GPRS Counters
LCS Counters.
Whats New
In Edition 09
This document was generated from the BSC Counters database edition 13rl
after update GCD_B10MR1_BSC_Counters table and from the MFS Counters
database edition 07rl.
In Edition 08
and from the MFS Counters database edition 07rl.
In Edition 07
In Edition 06
In Edition 05
In Edition 04
In Edition 03
In Edition 02
7 / 1392
Preface
In Edition 01
First official release of document.
Audience
Assumed Knowledge
8 / 1392
This manual is designed for Operations & Maintenance Center-Radio (OMC-R)

users, O&M technicians and system designers.
Not applicable.
1 BSC-TYPE 1 - Traffic measurements
9 / 1392
1.1 All TYPE 1

C01 - NB_IMM_ASS_SUCC_MT (Section 1.3.6.4.3.1 )
C02 - NB_IMM_ASS_SUCC_MO (Section 1.3.6.4.3.2 )
C02a - NB_IMM_ASS_SUCC_MO_LOC_UPD (Section 1.3.6.4.3.3 )
C02b - NB_IMM_ASS_SUCC_MO_SMS (Section 1.3.6.4.3.4 )
C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV (Section 1.3.6.4.3.5 )
C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON (Section 1.3.6.4.3.6 )
C02e - NB_IMM_ASS_SUCC_MO_CM_REEST (Section 1.3.6.4.3.7 )
C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW (Section 1.3.6.4.3.8 )
C02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH (Section 1.3.6.4.3.9 )
C02h - NB_IMM_ASS_SUCC_MO_CALL_EST (Section 1.3.6.4.3.10 )
C02i - NB_IMM_ASS_SUCC_MO_LCS (Section 1.3.6.4.3.11 )
C03 - NB_OUT_SDCCH_HO_SUCC (Section 1.3.4.2.3.1 )
C04 - NB_IMM_ASS_PREP_FAIL_CONG (Section 1.3.6.4.2.1 )
C07 - NB_SDCCH_DROP_OUT_HO (Section 1.3.4.2.2.1 )
C10 - NB_INC_SDCCH_HO_SUCC (Section 1.3.4.2.3.2 )
C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB (Section 1.3.3.2.2.1 )
C138 - NB_SDCCH_DROP_EST_PHAS_RLF (Section 1.3.3.2.2.2 )
C13a - NB_TCH_NOR_ASS_QUEUED (Section 1.5.2.6.2.1 )
C13b - NB_INC_EXT_TCH_HO_QUEUED (Section 1.5.2.3.3.1 )
C147 - NB_INC_SDCCH_HO_ALLOC (Section 1.5.2.3.2.1 )
C148 - NB_IMM_ASS_ALLOC (Section 1.5.2.4.2.1 )
C149 - NB_IMM_ASS_EXEC_FAIL_RADIO (Section 1.3.6.4.2.2 )
C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB (Section
1.3.4.3.2.1 )
C14c - NB_TCH_DROP_EST_PHAS_BSS_PB (Section 1.3.3.3.2.1 )
C15a - NB_INC_IDR_ALLOC (Section 1.5.2.2.2.1 )
C15b - NB_INC_TCH_HO_ALLOC (Section 1.5.2.3.3.2 )
C161a - NB_DTAP_MO_NOR_ASS_SUCC (Section 1.3.6.3.2.1 )
C161b - NB_DTAP_MT_NOR_ASS_SUCC (Section 1.3.6.3.2.2 )
C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF (Section 1.3.3.3.2.2 )
C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB (Section 1.3.3.3.2.3 )
C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL (Section
1.3.3.3.2.4 )
C170 - NB_CALL_TFO (Section 1.3.5.2.2.1 )
C171 - NB_TFO_CODEC_REQ (Section 1.3.5.2.2.2 )
C442 - NB_TIMES_TRAF_DETECTED_HIGH (Section 1.4.2.4.2.1 )
C443 - NB_TIMES_TRAF_DETECTED_LOW (Section 1.4.2.2.2.1 )
C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE (Section 1.3.6.5.2.1 )
10 / 1392
C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL (Section 1.3.6.5.2.2

)
C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP (Section 1.3.6.2.3.1 )
C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ (Section 1.3.6.5.2.3 )
C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX (Section 1.3.4.3.2.2 )
C701a - NB_TCH_FR_REQ (Section 1.4.2.5.2.1 )
C701b - NB_TCH_DR_REQ (Section 1.4.2.5.2.2 )
C701c - NB_TCH_DR_EFR_REQ (Section 1.4.2.5.2.3 )
C701d - NB_TCH_AMR_REQ (Section 1.4.2.5.2.4 )
C701e - NB_TCH_DATA_REQ (Section 1.4.2.5.2.5 )
C702a - NB_TCH_NOR_FR_ALLOC (Section 1.4.2.5.2.6 )
C702b - NB_TCH_NOR_HR_ALLOC (Section 1.4.2.5.2.7 )
C702c - NB_TCH_NOR_EFR_ALLOC (Section 1.4.2.5.2.8 )
C703 - NB_TCH_NOR_ASS_ALLOC_TRX (Section 1.5.2.6.2.2 )
C704a - NB_TCH_NOR_AMR_FR_ALLOC (Section 1.4.2.5.2.9 )
C704b - NB_TCH_NOR_AMR_HR_ALLOC (Section 1.4.2.5.2.10 )
C705 - NB_TCH_NOR_DATA_ALLOC (Section 1.4.2.5.2.11 )
C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU (Section 1.4.2.3.2.1 )
C710 - NB_TCH_OUT_HO_REQ_TRX (Section 1.2.2.2.2.1 )
C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX (Section 1.3.4.3.2.3 )
C712 - NB_TCH_OUT_HO_SUCC_TRX (Section 1.3.4.3.3.1 )
C713 - NB_TCH_OUT_HO_FAIL_REV_TRX (Section 1.3.4.3.2.4 )
C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX (Section 1.3.4.3.2.5 )
C717a - NB_INC_IDR_SUCC_TRX (Section 1.3.2.2.2.1 )
C717b - NB_INC_TCH_HO_SUCC_TRX (Section 1.3.4.3.3.2 )
C718 - NB_TCH_NOR_ASS_SUCC_TRX (Section 1.3.6.5.3.1 )
C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX (Section 1.3.3.3.2.5 )
C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX (Section
1.3.3.3.2.6 )
C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX (Section 1.3.6.5.2.4 )
C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS (Section 1.3.6.5.2.5
)
C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL (Section
1.5.2.5.2.1 )
C901 - NB_Suspend_Resume_req (Section 1.3.6.2.2.1 )
C902 - Nb_Suspend_fail (Section 1.3.6.2.2.2 )
C903 - Nb_Suspend_succ (Section 1.3.6.2.2.3 )
11 / 1392
1.2 Handover
1.2.1 All Handover
1.2.2 TCH
1.2.2.1 All TCH
1.2.2.2 Outgoing
1.2.2.2.1 All Outgoing
1.2.2.2.2
1.2.2.2.2.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 intercell

and external handovers are counted together. This counter takes into account
handovers from TCH in traffic or in signaling mode. It does not take into account
DTM Assignments. MC710 = C710
Trigger condition
1) Intracell HO: Whenever the BSC process responsible for the handover
procedure starts an intra cell TCH handover procedure. 2) Internal intercell HO:
Whenever the BSC process responsible for the handover procedure selects a
target 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 on
A interface to the MSC. If more than one 48.008 HANDOVER REQUIRED is
sent in the frame of the same Handover procedure, the counter is incremented
only once. 48.008 HANDOVER REQUIRED is sent in following situations: 1) An
external handover alarm has been raised, with corresponding list of candidate
cells. 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
12 / 1392
1.3 Quality of Service

1.3.1 All Quality of Service
1.3.4.3.2.1 )
1.3.3.3.2.4 )
)
13 / 1392

1.3.3.3.2.6 )
)
1.3.2 Directed Retry

1.3.2.1 All Directed Retry
1.3.2.2 Internal
1.3.2.2.1 All Internal
1.3.2.2.2 Success
1.3.2.2.2.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 Abis

interface from the target cell for a TCH channel involved in an internal directed
retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
14 / 1392
1.3.3 Established Phase

1.3.3.1 All Established Phase
1.3.3.3.2.4 )
1.3.3.3.2.6 )
1.3.3.2 SDCCH
1.3.3.2.1 All SDCCH
1.3.3.2.2 Failure
1.3.3.2.2.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 to

BSS problem.It may happen that several causes of failures mentioned below
are detected consecutively. In that case, the counter will only be incremented
once, 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 value
being received during the stable phase of an SDCCH transaction. 3) Telecom
Supervisory module caused the call to be cleared. 4) SDCCH was released due
to 0180 CLEAR_CMD message being received from BSSAPduring the stable
phase 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
Type Name
Type Definition
External Comment
15 / 1392
1.3.3.2.2.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 a

cause value of "radio link failure" is received on Abis interface for an SDCCH
channel. 2) Whenever an 48.058 ERROR INDICATION message is received on
Abis interface and leads to a loss of channel.
Sub Domain 1
Established Phase
Sub Domain 2
SDCCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
16 / 1392
1.3.3.3 TCH
1.3.3.3.1 All TCH
1.3.3.3.2.4 )
1.3.3.3.2.6 )
17 / 1392
1.3.3.3.2 Failure
1.3.3.3.2.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 to

BSS problem. It may happen that several causes of failures mentioned below
once, as soon as the call is released. This counter takes into account TCH in
traffic or in signaling mode. It is not incremented in case of TCH drop during a
normal assignment, a handover or a DTM assignment.
Trigger condition
1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M

intervention" is received on Abis interface after TCH seizure and leads to a loss
of call. 2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with a
cause value of "message sequence error" is received on Abis interface after TCH
seizure and leads to a loss of call. 3) Whenever a LAPD failure is reported to the
Layer 3 of the BSC (for an RSL supporting a TCH transaction after successful
TCH seizure) and leads to a loss of call. 4) Whenever a TCH call release is
initiated by the BSS O&M FAULT MANAGEMENT application part or by the BSS
TELECOM application part as the result of a system defense action 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 software resources (memory,
timer reference, file reference...) or communication problems between different
processor boards). Notes : 1. TCH call releases which 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 counter will overestimate failures which
are due to problems which are internal to the BSS. However, due to the current
implementation 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 counter
can not be incremented since it is implemented within the faulty entity.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
18 / 1392
1.3.3.3.2.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

due to radio link failure (radio link timeout or Lapdm timer expiry). After an
external handover, the target BSC considers that the CONNECT ACK has not
already been received.
Trigger condition

cause value of "radio link failure" is received on Abis interface for a TCH channel
(after successful DTAP establishment). 2) Whenever an 48.058 ERROR
INDICATION message is received on Abis interface and leads to a loss of call.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
19 / 1392
1.3.3.3.2.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 due
to BSS problem. It may happen that several causes of failures mentioned below
once, as soon as the call is released. After an external handover, the target BSC
considers 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&M

of call. 2) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a
cause value of "message sequence error" is received on Abis interface after
TCHDTAP establishment and leads to a loss of call. 3) Whenever a LAPD failure
is reported to the Layer 3 of the BSC (for an RSL supporting a TCH transaction
after successful TCH seizure) and leads to a loss of call. 4) Whenever a TCH
call release is initiated by the BSS O&M FAULT MANAGEMENT application part
or by the BSS TELECOM application part as the result of a system defense
action 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 software
resources (memory, timer reference, file reference...) or communication
problems between different processor boards). Notes : 1. TCH call releases
which 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 counter will
overestimate failures which are due to problems which are internal to the BSS.
However, due to the current implementation 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 counter can not be incremented since it is implemented
within the faulty entity.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
20 / 1392
1.3.3.3.2.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 phase

due to remote transcoder failure. This counter is not concerned by the channel
change procedure.
Trigger condition
Whenever a 48.058 CONNECTION FAILURE INDICATION message with a

cause value of "remote transcoder failure" is received on Abis interface for a
TCH channel (for an established call).
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
21 / 1392
1.3.3.3.2.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 due

to radio link failure (radio link timeout or Lapdm timer expiry), per TRX. This
counter takes into account TCH in traffic or in signaling mode. MC736 = C736
Trigger condition

(after successful seizure). 2) Whenever an 48.058 ERROR INDICATION
message is received on Abis interface and leads to a loss of call.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
22 / 1392
1.3.3.3.2.6 C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Long Name
NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX
Definition

remote transcoder failures (per TRX).
Trigger condition
The counter is incremented whenever a 48.058 CONNECTION FAILURE

INDICATION message with cause "Remote Transcoder Failure" is received
on Abis interface for an established TCH connection. The BSC considers a
TCH connection as "established" once a 44.018 ASSIGNMENT COMPLETE
message (in case of normal assignments or an internal intra-cell handovers) or
a 44.018 HANDOVER COMPLETE message (in case of an internal inter-cell
incoming HO or an external inter-cell incoming HO) has been received for the
TCH connection. Note 1: MC739 = C739. Note 2: The counter is incremented
only once per established TCH connection. Thus, even if the BTS sends several
48.058 CONNECTION FAILURE INDICATION messages with cause "Remote
Transcoder Failure" for a particular established TCH connection, BSC will
increment the counter only once for that connection."
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
23 / 1392
1.3.4 Handover
1.3.4.1 All Handover
1.3.4.3.2.1 )
1.3.4.2 SDCCH
1.3.4.2.1 All SDCCH
1.3.4.2.2 Failure
1.3.4.2.2.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 the

handover procedure (T3103) expires.
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
24 / 1392
1.3.4.2.3 Success
1.3.4.2.3.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.008
CLEAR COMMAND (cause= "normal event/call control") received while T8 is
running. Note: This counter counts both inter-PLMN and intra-PLMN handover
events.
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
25 / 1392
1.3.4.2.3.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 HANDOVER

COMPLETE message is received on Abis interface from the target cell for
an SDCCH Sub-channel. Note: This counter counts both inter-PLMN and
intra-PLMN handover events.
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
26 / 1392
1.3.4.3 TCH
1.3.4.3.1 All TCH
1.3.4.3.2.1 )
1.3.4.3.2 Failure
1.3.4.3.2.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 TCH
handover preparation and execution phases. This counter is incremented on the
cell 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 are
not related to a specific cell, the counter related to the serving cell will be
incremented. It may happen that several causes of failures mentioned below
once, as soon as the handover procedure fails. This counter takes into account
handovers from TCH in traffic or in signaling mode.
27 / 1392
Trigger condition
1) Whenever the BSC receives on Abis interface from the target cell negative
acknowledgment to the TCH channel activation involved in the handover
procedure. 2) Whenever the timer supervising the Channel Activation procedure
(T9103) expires on the target cell during activation of a TCH channel involved in
the handover procedure. 3) Whenever an 48.058 ERROR REPORT message
with a cause value of "O&M intervention" is received on Abis interface from
either the serving or the target cell during the external or internal inter-cell
handover procedure and leads to a transaction failure. 4) Whenever an 48.058
ERROR REPORT message with a cause value of "O&M intervention" is
received on Abis interface on either the old or the new channel during the
internal intra-cell handover procedure and leads to a transaction failure. 5)
Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value
of "message sequence error" is received on Abis interface from the serving
cell between the sending of the 48.058 CHANNEL ACTIVATION message and
the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT
during the internal inter-cell TCH handover and leads to a transaction failure. 6)
of "message sequence error" is received on Abis interface on the old channel
between the sending of the 48.058 CHANNEL ACTIVATION message and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the
internal intra-cell TCH handover and leads to a transaction failure. 7) Whenever
a LAPD failure related to either serving or target cell is reported to the Layer 3
of the BSC (for an RSL supporting a TCH transaction for handover purpose)
and leads to a transaction failure. 8) Whenever an TCH handover abortion is
timer reference, file reference...) or communication problems between
different processor boards). 9) Whenever a 48.058 CONNECTION FAILURE
INDICATION message with a cause value of "remote transcoder failure" is
received on Abis interface from the old channel between the sending of the
48.058 CHANNEL ACTIVATION message and the reception of the 48.058
CHANNEL ACTIVATION ACKNOWLEDGE during an internal intra-cell or
inter-cellTCH handover procedure and leads to a transaction failure. Notes :
1. TCH handover failures which 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 counter will overestimate failures which are due to problems
which are internal to the BSS. However, due to the current implementation 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 counter can not be incremented
since it is implemented within the faulty entity.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
28 / 1392
Type Definition
External Comment
29 / 1392
1.3.4.3.2.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 in
signaling mode. MC621 = C621
Trigger condition
1) Inter-cell TCH handover: whenever the timer supervising the handover

procedure (T3103) expires. 2) External TCH handover (2G -> 2G): whenever
the timer supervising the handover procedure on 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 a normal call release. In such a case, the
handover is considered as successful. 3) Intra-cell TCH handover: whenever
the timer supervising the handover procedure (T3107) expires. 4) 2G -> 3G HO:
whenever the timer supervising the 2G-3G handover procedure on the serving
cell (T3121) expires, 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 a case, the 2G->3G handover is considered as successful.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
30 / 1392
1.3.4.3.2.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. This
counter takes into account handovers from TCH in traffic or in signaling mode. It
does 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) Internal
inter-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) External
HO: Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "no
radio resource available" is received from the MSC by the serving BSC for an
outgoing external TCH HO. Note : the counter will be incremented for external
TCH HO if and only if the parameter RESP_REQ is set to 1. Note: This counter
counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
31 / 1392
1.3.4.3.2.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 problem

with reversion of the mobile to the old channel. Intracell, internal intercell and
external handovers are counted together. This counter takes into account
Trigger condition
1) External HO: Whenever a 44.018 HANDOVER FAILURE message is received

on Abis interface from the serving cell, during an external TCH handover. 2)
Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message is
received on Abis interface from the serving cell, during an internal inter-cell
TCH handover. 3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILURE
message is received on Abis interface on the serving channel, during an internal
intra-cell TCH handover. Note: This counter counts both inter-PLMN and
intra-PLMN handover events. Note: This counter counts handover to UMTS.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
32 / 1392
1.3.4.3.2.5 C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Long Name
NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Definition

without reversion of the mobile to the old channel (call drop). Intracell, internal
intercell and external handovers are counted together. This counter takes into
account handovers from TCH in traffic or in signaling mode. It does not take into
account DTM Assignments. MC714 = C714
Trigger condition
1) External TCH HO: Whenever the timer supervising the handover procedure on
the serving cell (T8) expires, except if a 48.008 CLEAR COMMAND with "normal
release. In such a case, the handover is considered as successful. 2) Internal
intercell TCH HO: Whenever the timer supervising the handover procedure
(T3103) expires during an internal inter-cell TCH handover. 3) Intracell TCH HO:
Whenever the timer supervising the handover procedure (T3107) expires during
an internal intra-cell Note: This counter counts both inter-PLMN and intra-PLMN
handover events. Note: This counter counts hantover to UMTS
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
33 / 1392
1.3.4.3.3 Success
1.3.4.3.3.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 intercell

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 received
while T8 is running. 2) Internal inter-cell HO: whenever 44.018HANDOVER
COMPLETE is received from the MS via the target cell on the TCH channel. 3)
Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is received
from the MS via the cell on the TCH channel. Note 1: This counter counts both
inter-PLMN and intra-PLMN handover events. Note 2: This counter counts
handover to UMTS.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
34 / 1392
1.3.4.3.3.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) handover

successes per TRX; since there are no reliable means at the target BSC to
distinguish external directed retry from external handover, the external directed
retries are counted by this counter. MC717b = C717b
Trigger condition
1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER

COMPLETE message is received on Abis interface from the target cell for a
TCH channel. 2) Intra-cell handover: whenever an 44.018 ASSIGNMENT
COMPLETE message is received on Abis interface on the target channel. Note:
This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
35 / 1392
1.3.5 Speech
1.3.5.1 All Speech
1.3.5.2 TFO
1.3.5.2.1 All TFO
1.3.5.2.2
1.3.5.2.2.1 C170 - NB_CALL_TFO
Long Name
NB_CALL_TFO
Definition
Number of TCHs assigned in the serving cell for which TFO has been
successfully established.
Trigger condition
For each assigned TCH, the counter is incremented the first time a 48.058 TFO
REPORT 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 incremented
only once per assigned TCH (i.e. the first time it is received for the assigned
TCH). Note 2: A TCH is seen as assigned in the serving cell between the
sending of 48.058 CHANNEL ACTIVATION message and the receipt of the
48.058 RF CHANNEL RELEASE message. This means that the counter can
be incremented either if the TCH is assigned to serve a normal assignment or
if the TCH is assigned to serve an incoming internal (inter-cell or intra-cell) or
external handover. Note 3: MC170 = C170
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
36 / 1392
1.3.5.2.2.2 C171 - NB_TFO_CODEC_REQ

Long Name
NB_TFO_CODEC_REQ
Definition
Number of codec mismatch resolutions or codec optimisations requested to

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

by the BSC.
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
37 / 1392
1.3.6 Telecom Procedure (QoS)

1.3.6.1 All Telecom Procedure (QoS)
)
)
38 / 1392
1.3.6.2
1.3.6.2.1 All
1.3.6.2.2
1.3.6.2.2.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, a

failure or a stop.
Trigger condition
Emission of MS Suspend message by the BSC to the MFS Emission of MS

Resume message by the BSC to the MFS A suspend message received from
MS with a "suspend cause" filtered by BSC will not be counted. Stop causes
could be: 1) External handover 2) MS channel failure.
Sub Domain 1
Telecom Procedure (QoS)
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
39 / 1392
1.3.6.2.2.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 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
40 / 1392
1.3.6.2.2.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 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
41 / 1392
1.3.6.2.3 Failure
1.3.6.2.3.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 (in

HR or FR usage) is available in the cell, timer T11 (case MSC requests for
queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced
(case QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is
started, and no free TCH can be found before timer expiry, consequently the
request is rejected (by 48.008 CLEAR REQUEST cause: "no radio resource
available"). Remark: If an internal directed retry is attempted and failed while
T11/T11_forced is running, the request is un-holded and the BSC waits for the
expiry of the relevant timer. Consequently, this counter must not be incremented
upon 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 T11
forced for a queued TCH normal assignment. Note 1: The HMI name of the
parameter QUEUE_ANYWAY is "FORCED_QUEUING". Note 2: In case of Mx
BSC, "no TCH available" could happen when the TCH processing capacity of
CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this
case, this counter and MC926 are incremented by one. Note 3: In IP mode, this
counter is increased by 1 if: - the cell mapped on a BTS is in IP congestion
status; - or the TCH processing capacity of AbisBTSGroup reaches the limit
defined by the NB_MAX_ACTIVE_TCH_TS parameter
Sub Domain 1
Sub Domain 2
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
42 / 1392
1.3.6.3 DTAP Assignment

1.3.6.3.1 All DTAP Assignment
1.3.6.3.2 Success
1.3.6.3.2.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 1
Sub Domain 2
DTAP Assignment
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
43 / 1392
1.3.6.3.2.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.
Sub Domain 1
Sub Domain 2
DTAP Assignment
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
44 / 1392
1.3.6.4 Immediate Assignment

1.3.6.4.1 All Immediate Assignment
1.3.6.4.2 Failure
1.3.6.4.2.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 to

congestion.
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 1
Sub Domain 2
Immediate Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
45 / 1392
1.3.6.4.2.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.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
46 / 1392
1.3.6.4.3 Success
1.3.6.4.3.1 C01 - NB_IMM_ASS_SUCC_MT
Long Name
NB_IMM_ASS_SUCC_MT
Definition
Number of immediate assignment plus SDCCH normal assignment successes

for Mobile Terminating procedure.
Trigger condition
Whenever an 48.058 ESTABLISH INDICATION message is received from

a CELL, with the L3_INFORMATION field including a 44.018 PAGING
RESPONSE message.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
47 / 1392
1.3.6.4.3.2 C02 - NB_IMM_ASS_SUCC_MO

Long Name
NB_IMM_ASS_SUCC_MO
Definition
Number of immediate assignment successes for Mobile Originating procedure.

MC02 = C02 = C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i. The
following counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecom
procedures on SDCCH.
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
48 / 1392
1.3.6.4.3.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 a

cell, with the L3 INFORMATION field containing a 44.018 L3 message with an
MIE message type set to LOCATION UPDATING REQUEST and with an MIE
Location updating type not set to a RESERVED value and a bit FOR set to 0.
This counter is incremented only if the L3 info message received has to be
forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
49 / 1392
1.3.6.4.3.4 C02b - NB_IMM_ASS_SUCC_MO_SMS

Long Name
NB_IMM_ASS_SUCC_MO_SMS
Definition
case: SMS procedure on SDCCH
Trigger condition

CELL, with the L3 INFORMATION field containing a 44.018 L3 message with an
MIE message type set to CM SERVICE REQUEST and with an MIE CM service
type set to "SMS". This counter is incremented only if the L3 info message
received has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
50 / 1392
1.3.6.4.3.5 C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV

Long Name
NB_IMM_ASS_SUCC_MO_SUP_SERV
Definition
case: Supplementary Service
Trigger condition

type set to "Supplementary Service". This counter is incremented only if the L3
info message received has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
51 / 1392
1.3.6.4.3.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

CELL, with the L3 INFORMATION field containing a 44.018 L3 message with
an MIE message type set to LOCATION UPDATING REQUEST and with an
MIE Location updating type not set to a RESERVED value and a bit FOR set
to 1. This counter is incremented only if the L3 info message received has
to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
52 / 1392
1.3.6.4.3.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

an MIE message type set to CM RE-ESTABLISHMENT REQUEST message.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
53 / 1392
1.3.6.4.3.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 Mobile

Originationg procedure, in case of L3 Info (within 48.058 ESTABLISH
INDICATION) unknown by the BSC but transferred to the MSC.
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
54 / 1392
1.3.6.4.3.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 Mobile

Originationg procedure, in case of IMSI Detach Indication.
Trigger condition

CELL, with L3_INFORMATION field containing a 44.018 L3 message with
an MIE message type set to IMSI DETACH INDICATION. This counter is
incremented only if the L3 info message received has to be forwarded to the
MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
55 / 1392
1.3.6.4.3.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

CELL, with the L3 INFORMATION field containg a 44.018 L3 message with an
MIE message type set to CM SERVICE REQUEST and an MIE CM service type
set to either : - "emergency call establishment", - or "mobile originating call
establishment" This counter is incremented only if the L3 info message received
has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
56 / 1392
1.3.6.4.3.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 MIE
message type set to CM SERVICE REQUEST and with an MIE CM service type
set to "Location Services" (LCS). This counter is incremented only if the L3 info
message received has to be forwarded to the MSC
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
57 / 1392
1.3.6.5 Normal Assignment

1.3.6.5.1 All Normal Assignment
)
)
1.3.6.5.2 Failure
1.3.6.5.2.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 failures

because of the non-queuing of the ASSIGNMENT REQUEST message. Case:
48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received when
no TCH is available in the cell. The request is rejected (by 48.008ASSIGNMENT
FAILURE, cause: "no radio resource available"), because the queuing procedure
is either: 1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR
(T11_forced=0 and QUEUE_ANYWAY=1)), or 2) 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 ASSIGNMENT

FAILURE (cause: "no radio resource available") for a TCH channel because
no TCH is available and either the queuing is disabled in the BSC (T11=0
and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the
queuing is enabled, QUEUE_ANYWAY=0, and the MSC does not request
a queuing. Note 1: The HMI name of the parameter QUEUE_ANYWAY is
"FORCED_QUEUING". Note 2: In case of Mx BSC, "no TCH available"
could happen when the TCH processing capacity of CCP reaches the limit
defined by the MAX_TCH_PER_CCP parameter. In this case, this counter
and MC926 are incremented by one. Note 3: In IP mode, this counter is
increased by 1 if: - the cell mapped on a BTS is in IP congestion status; - or
the TCH processing capacity of AbisBTSGroup reaches the limit defined by the
NB_MAX_ACTIVE_TCH_TS parameter
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
58 / 1392
1.3.6.5.2.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 HR

usage) is received when no TCH is available in the cell. The queuing is enabled
within the BSC, but the request is rejected (by 48.008ASSIGNMENT FAILURE,
cause: "no radio resource available"), because the queue is full and no request
of lower priority can be dequeued from the BSC queue.
Trigger condition

FAILURE (cause: "no radio resource available") for a TCH channel because the
queue is full and no request of lower priority can be de-queued. Note 1: In case
of Mx BSC, "no TCH available" could happen when the TCH processing capacity
of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In
this 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 congestion
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
59 / 1392
1.3.6.5.2.3 C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Long Name
NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Definition

queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (case
QUEUE_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 a
higher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the BSC sends
48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for the
first transaction. Remark: As soon as an internal directed retry is attempted,
the request is blocked within the BSC and cannot be dequeued by a higher
priority request.
Trigger condition
The counter is incremented upon the sending of the 48.008 ASSIGMENT

FAILURE (cause: "no radio resource available") for a de-queued TCH
request (i.e. normal assignment) due to the receipt of a higher priority
request. Note 1: The HMI name of the parameter QUEUE_ANYWAY is
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
60 / 1392
1.3.6.5.2.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 failures

due to MS access problem, per TRX. This counter also takes into account
DTM assignment -execution failures due to MS access problem for TCH
establishment in signaling mode (FR usage only). MC746b = C746b
Trigger condition
1) The timer T3107 in the BSS supervising the TCH channel seizure by the
mobile expires (following the sending of 44.018 ASSIGNMENT COMMAND for a
TCH channel that is not involved in a handover procedure). 2) The timer T3107
in the BSS supervising the TCH channel seizure by the mobile expires, following
the sending of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel in
signaling mode. 3) The BSC receives a 44.018 ASSIGNMENT FAILURE on
the old (SDCCH) channel during the normal assignment procedure except in
case of multiband cell, when the normal assignment procedure is performed
in the inner zone and the ASSIGNMENT FAILURE is received with the cause
"protocol error unspecified". 4) The BSC receives a 44.018 DTM ASSIGNMENT
FAILURE on the old (SDCCH) channel during the DTM assignment procedure,
for a TCH in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
61 / 1392
1.3.6.5.2.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
Trigger condition
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
62 / 1392
1.3.6.5.3 Success
1.3.6.5.3.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 TCH
establishment in signaling mode (FR usage only), for DTM. MC718 = C718
Trigger condition
Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis

interface for a TCH channel that is not involved in a handover procedure, in
traffic or in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
63 / 1392
1.4 Resource Availability & Usage

1.4.1 All Resource Availability & Usage
1.4.2 Resource Allocation & Management

1.4.2.1 All Resource Allocation & Management
64 / 1392
1.4.2.2
1.4.2.2.1 All
1.4.2.2.2
1.4.2.2.2.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 cell at each
A_TRAFFIC_LOAD period. This counter permits to tune the following
parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD and LOW_THRESHOLD.
This counter relates to the number of free TCH timeslots.
Trigger condition
At each A_TRAFFIC_LOAD period, whenever the BSC decision process

detects a "low" traffic_load. Remark : the number of "indefinite" traffic
load can be deduced from the counters NB_LOW_TRAFFIC_LOAD and
NB_HIGH_TRAFFIC_LOAD over the Accumulation Period.
Sub Domain 1
Resource Allocation & Management
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
65 / 1392
1.4.2.3 E-GSM
1.4.2.3.1 All E-GSM
1.4.2.3.2
1.4.2.3.2.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) of

MS supporting the E-GSM band, on a CELL basis. MC706 = C706
Trigger condition
Whenever a 44.018 CLASSMARK CHANGE message in the context of any

establishment causes different from location update is received on Abis
interface with a "Mobile Station Classmark 3" or a "Mobile Station Classmark 2"
Information Element field specifying that the MS supports the E-GSM band. The
counter 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 1
Sub Domain 2
E-GSM
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
66 / 1392

1.4.2.4.2
1.4.2.4.2.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 per cell at each
A_TRAFFIC_LOAD period. This counter permits to tune the following
parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD and HIGH_THRESHOLD.
This counter relates to the number of free TCH timeslots.
Trigger condition
At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects

a "high" traffic_load.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
67 / 1392
1.4.2.5 Service
1.4.2.5.1 All Service
1.4.2.5.2
1.4.2.5.2.1 C701a - NB_TCH_FR_REQ
Long Name
NB_TCH_FR_REQ
Definition
Number of TCH normal assignments requests from FR only mobiles (after

possible filtering from the MSC).
Trigger condition
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with
only GSM speech coding algorithm version 1 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
68 / 1392
1.4.2.5.2.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
only GSM speech coding algorithm version 1 full rate and GSM speech coding
algorithm version 1 half rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
69 / 1392
1.4.2.5.2.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, HR

and EFR.
Trigger condition
GSM speech coding algorithm version 1 full rate, GSM speech coding algorithm
version 1 half rate and GSM speech coding algorithm version 2 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
70 / 1392
1.4.2.5.2.4 C701d - NB_TCH_AMR_REQ

Long Name
NB_TCH_AMR_REQ
Definition
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition
GSM speech coding algorithm version 3 full rate or half rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
71 / 1392
1.4.2.5.2.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 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
72 / 1392
1.4.2.5.2.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 channel

is allocated in the BSC. This counter takes into account mode modify from TCH
signaling to TCH traffic (following a DTM assignment with a TCH in signaling
mode).
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, not
related to handover.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
73 / 1392
1.4.2.5.2.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 channel

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 1,
not related to handover.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
74 / 1392
1.4.2.5.2.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 - whose

channel is allocated in the BSC. This counter takes into account mode modify
from TCH signaling to TCH traffic (following a DTM assignment with a TCH in
signaling mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
75 / 1392
1.4.2.5.2.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 - whose

signaling mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
76 / 1392
1.4.2.5.2.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 - whose

channel is allocated in the BSC.
Trigger condition

indicating a HR channel with GSM speech coding algorithm version 3, not
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
77 / 1392
1.4.2.5.2.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 is

allocated in the BSC. This counter takes into account mode modify from TCH
mode).
Trigger condition

indicating a data call, not related to handover.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
78 / 1392
1.5 Traffic Load

1.5.1 All Traffic Load
1.5.2.5.2.1 )
1.5.2 Telecom Procedure (Traffic Load)

1.5.2.1 All Telecom Procedure (Traffic Load)
1.5.2.5.2.1 )
79 / 1392
1.5.2.2 Directed Retry

1.5.2.2.1 All Directed Retry
1.5.2.2.2 Internal
1.5.2.2.2.1 C15a - NB_INC_IDR_ALLOC
Long Name
NB_INC_IDR_ALLOC
Definition
MC15a=C15a, Number of incoming internal directed retry (towards a TCH

channel 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 CHANNEL
ACTIVATION message of a TCH channel is about to be sent during an internal
directed retry.
Sub Domain 1
Telecom Procedure (Traffic Load)
Sub Domain 2
Directed Retry
Sub Domain 3
Internal
Measured Object
Common cell
Type Name
Type Definition
External Comment
80 / 1392
1.5.2.3 Handover
1.5.2.3.1 All Handover
1.5.2.3.2 SDCCH
1.5.2.3.2.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 on

Abis Interface to activate an SDCCH channel for any handover purposes. Note:
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
SDCCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
81 / 1392
1.5.2.3.3 TCH
1.5.2.3.3.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 that

are put in BSC queue
Trigger condition
Further to the receipt of a 48.008 HANDOVER REQUEST message for TCH,

the counter is incremented: i) upon the sending of a 48.008 QUEUING
INDICATION message if the queuing is authorised by the MSC, or, ii) when
the handover request is queued in the cell if the queuing is not authorised by
the MSC and the request has its pre-emption indicator set (provided that the
flag EN_TCH_PREEMPT is set to Enable). Note: MC13b = C13b Note: This
counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
TCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
82 / 1392
1.5.2.3.3.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
means at the target BSC to distinguish external directed retry from external
handover, the external directed retries are counted by this counter.
Trigger condition
ACTIVATION message of a TCH channel is about to be sent during any
handover procedure. Note: This counter counts both inter-PLMN and
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
TCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
83 / 1392

1.5.2.4.2
1.5.2.4.2.1 C148 - NB_IMM_ASS_ALLOC
Long Name
NB_IMM_ASS_ALLOC
Definition
Number of immediate assignment plus SDCCH normal assignments -whose

SDCCH channel is allocated by the BSC.
Trigger condition
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent

on Abis Interface to activate an SDCCH channel for any purpose other than
handover.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
84 / 1392
1.5.2.5 Multiband
1.5.2.5.1 All Multiband
1.5.2.5.2.1 )
1.5.2.5.2
1.5.2.5.2.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 cell
basis. A MS is considered as multiband if it supports: - the P-GSM (or E-GSM
or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS
parameter is set to "GSM900 and DCS1800 bands", or, - the GSM850 and
the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to
"GSM850 and DCS1800 bands", or, - the GSM850 and the DCS1900 bands if
the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and DCS1900
bands", or, - the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the
PLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1900
bands".
Trigger condition
Whenever a 44.018 Classmark Change message in the context of any

establishment cause different from location update is received on Abis
interface from the MS with a "Mobile Station Classmark 3" Information Element
specifying that the MS supports: - the P-GSM (or E-GSM or R-GSM) and
the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set
to "GSM900 and DCS1800 bands", or, - the GSM850 and the DCS1800
bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850
and DCS1800 bands", or, - the GSM850 and the DCS1900 bands if the
bands". The counter 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 1
Sub Domain 2
Multiband
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
85 / 1392

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

put in BSC queue.
Trigger condition
Further to the receipt of a 48.008 ASSIGNMENT REQUEST message for

TCH, the counter is incremented: i) upon the sending of a 48.008 QUEUING
the assignment request is queued in the cell if the queuing is not authorised
by the MSC and the parameter QUEUE_ANYWAY is set, or, iii) when the
assignment request is queued in the cell if the queuing is not authorised by the
MSC and the request has its pre-emption indicator set (provided that the flag
EN_TCH_PREEMPT is set to Enable). Note 1: MC13a = C13a Note 2: The
HMI name of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
86 / 1392
1.5.2.6.2.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 channel

is allocated in the BSC, per TRX. This counter also takes into account normal
assignment whose RTCH channel is allocated in the BSC in signaling mode (FR
usage only), for DTM. MC703 = C703
Trigger condition

Abis Interface to activate a TCH channel for normal assignment, or for DTM
assignment with a TCH in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
87 / 1392
88 / 1392
2 BSC-TYPE 2 - Resource availability measurements
89 / 1392
2.1 All TYPE 2

C141 - AV_NB_TCH_QUEUED (Section 2.2.2.4.3.1 )
C24 - AV_NB_NOT_AVAIL_TRX_TS (Section 2.2.2.5.2.1 )
C250 - AV_NB_AVAIL_TCH (Section 2.2.2.4.2.1 )
C26 - AV_NB_AVAIL_SDCCH (Section 2.2.2.3.3.1 )
C27 - AV_NB_AVAIL_CCCH (Section 2.2.2.2.2.1 )
C28a - AV_NB_BUSY_CS_TS (Section 2.2.2.4.3.2 )
C29a - NB_MAX_SIMUL_BUSY_CS_TS (Section 2.2.2.4.3.3 )
C30 - AV_NB_BUSY_SDCCH (Section 2.2.2.3.4.1 )
C31 - NB_MAX_SIMUL_BUSY_SDCCH (Section 2.2.2.3.4.2 )
C320a - AV_NB_IDLE_TCH_INTERF_BAND1 (Section 2.2.2.4.3.4 )
C320b - AV_NB_IDLE_TCH_INTERF_BAND2 (Section 2.2.2.4.3.5 )
C320c - AV_NB_IDLE_TCH_INTERF_BAND3 (Section 2.2.2.4.3.6 )
C320d - AV_NB_IDLE_TCH_INTERF_BAND4 (Section 2.2.2.4.3.7 )
C320e - AV_NB_IDLE_TCH_INTERF_BAND5 (Section 2.2.2.4.3.8 )
C34 - TIME_ALL_AVAIL_TRX_TS_BUSY (Section 2.2.2.5.3.1 )
C803 - TIME_SDCCH_CONGESTION (Section 2.2.2.3.2.1 )

90 / 1392
2.2.2 Channel
2.2.2.1 All Channel
91 / 1392
2.2.2.2 CCCH
2.2.2.2.1 All CCCH
2.2.2.2.2 Availability
2.2.2.2.2.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 each

polling period are averaged, i.e. summed and divided by the number of
observations. The averaged value (real) is rounded up or down to the nearest
integer value.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Resource availability measurements
Type Definition
Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment
92 / 1392
2.2.2.3 SDCCH
2.2.2.3.1 All SDCCH
2.2.2.3.2
2.2.2.3.2.1 C803 - TIME_SDCCH_CONGESTION
Long Name
TIME_SDCCH_CONGESTION
Definition
Cumulated time (in seconds) during which the SDCCH request(s) are not served
because no SDCCH sub-channel is available.
Trigger condition
The time counter is started whenever a SDCCH request cannot be served. The
time counter is stopped whenever one of the following conditions is checked: - if
a SDCCH sub-channel becomes free and usable on a static SDCCH timeslot
or on a dynamic timeslot allocated as SDCCH (i.e. when the timeslot is known
from the SDCCH_RM module). The term "usable" means here that the SDCCH
sub-channel is not mapped on a TCU in a very high overload state, or, - if a
SDCCH request is served successfully. This condition corresponds to the case
the SDCCH_RM module requests the TCH_RM module for a dynamic SDCCH
timeslot.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
93 / 1392
2.2.2.3.3.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 SDCCH

timeslots).
Trigger condition

integer value. Note: "Available" has here to be understood as the operational
state of a timeslot. The timeslot is available if it is not "blocked" or "out of
service".
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
94 / 1392
2.2.2.3.4 Usage
2.2.2.3.4.1 C30 - AV_NB_BUSY_SDCCH
Long Name
AV_NB_BUSY_SDCCH
Definition
Average number of busy SDCCH subchannels, taking into account the following
SDCCH sub-channels: 1) Static SDCCH/x sub-channels, 2) Dynamic SDCCH
sub-channels which are dynamically allocated on the dynamic SDCCH/8
timeslots.
Trigger condition

observations. In order to provide one decimal place, the average value (real)
is multiplied by ten and then rounded up or down to the nearest integer value.
Note that the counter value that is indicated in the ASCII file, which can be
obtained via the OBSYNT interface, still has to be divided by 10, whereas the
value that is provided at the user interface is the correct one.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
95 / 1392
2.2.2.3.4.2 C31 - NB_MAX_SIMUL_BUSY_SDCCH

Long Name
NB_MAX_SIMUL_BUSY_SDCCH
Definition
Maximum number of simultaneously busy SDCCH subchannels, taking into

account the following SDCCH sub-channels: 1) Static SDCCH/x sub-channels,
2) Dynamic SDCCH sub-channels which are dynamically allocated on the
dynamic SDCCH/8 timeslots.
Trigger condition
At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to the cell:

C31 = MAX ["old" C31 value (i.e. before the channel activation), number of busy
SDCCH subchannels observed for the cell].
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
96 / 1392
2.2.2.4 TCH
2.2.2.4.1 All TCH
2.2.2.4.2.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 (for
HR or FR usage) or PDCH).
Trigger condition

observations. The averaged value is rounded up or down to the nearest integer
value. Note 1: "Available" has here to be understood as the operational state of
a timeslot. 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 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
97 / 1392
2.2.2.4.3 Usage
2.2.2.4.3.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 or

external handover requests.
Trigger condition

observations. In order to provide one decimal place, the averaged value (real)
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
98 / 1392
2.2.2.4.3.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 in

signaling 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 timeslots
and busy dynamic SDCCH/8 radio timeslots allocated as TCH. The sampling
period is set to the value indicated in the Status Inspection field. At the expiry of
the accumulation period, all samples are averaged (i.e. summed and divided
by the number of samples). The averaged value is rounded up or down to the
nearest value with an accuracy of 0.1. A TCH radio timeslot is considered as
busy during the time it is allocated to a given MS for TCH traffic (in HR or FR
usage). A dynamic SDCCH/8 timeslot allocated as TCH is considered as busy
during the time it is allocated to a given MS for TCH traffic. Note 1: the counter
value that is indicated 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).
The reported value shall then be divided by 10 afterwards so that the value that
is displayed to the end-user is the correct one. Note 2: This counter does not
take into account the PDCH radio timeslots allocated to the MFS.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
99 / 1392
2.2.2.4.3.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 or

FR usage, in traffic or in signaling mode) and simultaneously busy dynamic
SDCCH/8 radio timeslots allocated as TCH.
Trigger condition
Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated

as TCH becomes busy, the BSC determines the current number of busy TCH
radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslots
allocated as TCH. This counter is the maximum value of this number during
the accumulation period. This counter does not take into account the PDCHs
allocated to the MFS.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
100 / 1392
2.2.2.4.3.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 timeslots
belonging to the interference band 1. This number is updated upon the receipt
of 48.058 RF RESOURCE INDICATION.
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
101 / 1392
2.2.2.4.3.5 C320b - AV_NB_IDLE_TCH_INTERF_BAND2

Long Name
Definition
Trigger condition

observations. The average value (real) is rounded up or down to the nearest
integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
102 / 1392
2.2.2.4.3.6 C320c - AV_NB_IDLE_TCH_INTERF_BAND3

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
103 / 1392
2.2.2.4.3.7 C320d - AV_NB_IDLE_TCH_INTERF_BAND4

Long Name
Definition
Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FR
or HR usage belonging to the interference band 4. This number is updated upon
the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
104 / 1392
2.2.2.4.3.8 C320e - AV_NB_IDLE_TCH_INTERF_BAND5

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
105 / 1392
2.2.2.5 TRX_TS
2.2.2.5.1 All TRX_TS
2.2.2.5.2.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).
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TRX_TS
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
106 / 1392
2.2.2.5.3 Usage
2.2.2.5.3.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-channel
to 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 is
occupied by the CS part of a DTM call), or ii) if the TCH sub-channel is allocated
to the MFS to carry PS traffic.
Trigger condition
The counter is started when there is no free FR TCH sub-channel to serve an

incoming FR TCH request. The counter is stopped when there is a free FR TCH
sub-channel to serve an incoming FR TCH request.
Sub Domain 1
Channel
Sub Domain 2
TRX_TS
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
107 / 1392
108 / 1392
3 BSC-TYPE 3 - Resource usage on CCCH channel measurements
3 BSC-TYPE 3 - Resource usage on CCCH channel

measurements
109 / 1392
3.1 All TYPE 3

C8a - NB_PAGING_CMD (Section 3.2.2.2.2.1 )
C8b - NB_IMM_ASS_CMD (Section 3.2.2.2.2.2 )
C8c - NB_CHAN_REQD (Section 3.2.2.2.2.3 )
C8d - NB_IMM_ASS_REJ (Section 3.2.2.2.2.4 )
3.2 Traffic Load

3.2.2 Channel
3.2.2.1 All Channel
3.2.2.2 CCCH
3.2.2.2.1 All CCCH
110 / 1392
3.2.2.2.2
3.2.2.2.2.1 C8a - NB_PAGING_CMD
Long Name
NB_PAGING_CMD
Definition
PCH load: number of 48.058 PAGING COMMAND messages sent either for PS
traffic or for CS traffic on Abis towards the selected cell.
Trigger condition
Whenever a 48.058 PAGING COMMAND message (either for PS traffic or for

CS traffic) is about to be sent on Abis interface to the cell on the related TRX
timeslot.
Sub Domain 1
Channel
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, AGCH
load, RACH load)
External Comment
111 / 1392
3.2.2.2.2.2 C8b - NB_IMM_ASS_CMD

Long Name
NB_IMM_ASS_CMD
Definition
AGCH load: number of 48.058 IMMEDIATE ASSIGN COMMAND messages

sent for CS traffic on Abis to the MS.
Trigger condition
Whenever a 48.058 IMMEDIATE ASSIGN COMMAND message for CS traffic

is about 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 ASSIGN
COMMAND messages sent for PS traffic.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
load, RACH load)
External Comment
112 / 1392
3.2.2.2.2.3 C8c - NB_CHAN_REQD

Long Name
NB_CHAN_REQD
Definition
RACH load: number of 48.058 CHANNEL REQUIRED received via the selected
cell. All the CHANNEL REQUIRED messages are counted whatever the
Establishment Cause is.
Trigger condition
Whenever a 48.058 CHANNEL REQUIRED message (either for PS traffic or for

CS traffic) is received on Abis interface from the cell on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
load, RACH load)
External Comment
113 / 1392
3.2.2.2.2.4 C8d - NB_IMM_ASS_REJ

Long Name
NB_IMM_ASS_REJ
Definition
Number of 48.058 CHANNEL REQUIRED received while no SDCCH can be

allocated by the BSC (congestion), i.e. the number of 44.018IMMEDIATE
ASSIGNMENT REJECT sent to the MS via the selected cell.
Trigger condition
Whenever a 48.058 IMMEDIATE ASSIGNMENT COMMAND message is

about to be sent on Abis interface to the cell on the related TRX timeslot with
a "Full Immediate Assignment" Info Element containing a 44.018 IMMEDIATE
ASSIGNMENT REJECT message. Note: This counter only applies to CS traffic.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
load, RACH load)
External Comment
114 / 1392
4 BSC-TYPE 4 - Resource usage on SDCCH channel measurements
4 BSC-TYPE 4 - Resource usage on SDCCH channel

measurements
115 / 1392
4.1 All TYPE 4

C39 - NB_TIMES_SDCCH_BUSY (Section 4.2.2.2.2.1 )
C40 - TIME_SDCCH_BUSY (Section 4.3.2.2.2.1 )

4.2.2 Channel
4.2.2.1 All Channel
4.2.2.2 SDCCH
4.2.2.2.1 All SDCCH
4.2.2.2.2 Usage
4.2.2.2.2.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 are
busy.
Trigger condition
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent to a

CELL to activate an SDCCH Sub-channel on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
TRX_TS
Type Name
Resource usage on SDCCH channel measurements
Type Definition
Set of counters related to the usage of the SDCCH channel
External Comment
116 / 1392
4.3 Traffic Load

4.3.2 Channel
4.3.2.1 All Channel
4.3.2.2 SDCCH
4.3.2.2.1 All SDCCH
4.3.2.2.2
4.3.2.2.2.1 C40 - TIME_SDCCH_BUSY
Long Name
TIME_SDCCH_BUSY
Definition
Cumulated time during which the SDCCH sub-channels belonging to the related
static or dynamic SDCCH timeslot are busy.
Trigger condition
For the related static or dynamic SDCCH timeslot, the counter cumulates, over
the Accumulation Period, all time unit during which a SDCCH sub-channel is
busy. For each SDCCH allocation of the sub-channel: 1) The counter starts
being incremented after the sending of the 48.058 CHANNEL ACTIVATION
message concerning an SDCCH sub-channel on the related TRX timeslot.
2) The counter stops being incremented after the reception of a 48.058 RF
CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (supervising 48.058 RF CHANNEL RELEASE message)
concerning the SDCCH sub-channel previously activated on the related static
or dynamic SDCCH timeslot. Example; Let us consider that on a given static
SDCCH/8 timeslot, - SDCCH sub-channel 1 has been busy for 10 s, - SDCCH
sub-channel 2 has been busy for 20 s, - SDCCH sub-channel n (with 3 <= n <=
8) has not been busy at all. Then, at the expiry of the reporting period, the value
reported by this counter is 10 + 20 = 30 s.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Resource usage on SDCCH channel measurements
Type Definition
Set of counters related to the usage of the SDCCH channel
External Comment
117 / 1392
118 / 1392
5 BSC-TYPE 5 - Resource usage on TCH channel measurements
5 BSC-TYPE 5 - Resource usage on TCH channel

measurements
119 / 1392
5.1 All TYPE 5

C370a - NB_TCH_FR_ALLOC (Section 5.2.2.2.2.1 )
C370b - NB_TCH_HR_ALLOC (Section 5.2.2.2.2.2 )
C380a - TIME_FR_TCH_BUSY (Section 5.3.2.2.2.1 )
C380b - TIME_HR_TCH_BUSY (Section 5.3.2.2.2.2 )
C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS (Section 5.3.2.2.2.3 )
C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS (Section 5.3.2.2.2.4 )

5.2.2 Channel
5.2.2.1 All Channel
5.2.2.2 TCH
5.2.2.2.1 All TCH
120 / 1392
5.2.2.2.2 Usage
5.2.2.2.2.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 is

allocated 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 to

the cell to activate a full rate TCH channel for normal assignment, for DTM
assignment or handover, in traffic or in signaling mode.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
TRX_TS
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)
External Comment
121 / 1392
5.2.2.2.2.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 is

allocated in HR usage (i.e. the upper or lower HR sub-channel of the radio
timeslot is allocated), for normal assignment or handover.
Trigger condition
Whenever a CHANNEL_ACTIVATION message is about to be sent to the

cell to activate a half rate TCH subchannel (either upper or lower) for normal
assignment or handover.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
TRX_TS
Type Name
Type Definition
External Comment
122 / 1392
5.3 Traffic Load

5.3.2 Channel
5.3.2.1 All Channel
5.3.2.2 TCH
5.3.2.2.1 All TCH
123 / 1392
5.3.2.2.2
5.3.2.2.2.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/8
timeslot in FR usage (in traffic or in signaling mode) is busy.
Trigger condition
The counter cumulates over the Accumulation Period, per radio timeslot, all unit
times 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 CHANNEL
ACTIVATION message to the cell concerning a full rate TCH channel (in traffic
or in signaling mode) for the related TRX timeslot. 2) The counter stops
being incremented after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the
sending of the 48.058 RF CHANNEL RELEASE message) concerning the TCH
channel previously activated on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
External Comment
124 / 1392
5.3.2.2.2.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 in

HR 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/8
timeslot) is busy. Both "HR timeslots" are counted independently. For each
channel allocation: 1) The counter starts being incremented after the sending of
the 48.058 CHANNEL ACTIVATION message concerning a dynamic SDCCH/8
timeslot or an half rate TCH sub-channel mapped either on the upper half or the
lower half of the related TRX timeslot. 2) The counter stops being incremented
when no HR sub-channel is active anymore on the related TRX channel. This
is after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGE
message or the expiry of timer T_RCR_ACK twice (after the sending of the
48.058 RF CHANNEL RELEASE message) or the BSC internal radio resource
release due to any BSS problem concerning the last HR TCH channel (or the
dynamic SDCCH/8 timeslot) which was active on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
External Comment
125 / 1392
5.3.2.2.2.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/8
timeslot in FR usage (in traffic or in signaling mode) is busy by a multiband mobile
station. A MS is considered as multiband if it supports: - the P-GSM (or E-GSM
bands".
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/8
timeslot) is busy (in traffic or in signaling mode). For each channel
allocation : 1) The counter starts being incremented after the sending of
the 48.058 CHANNEL ACTIVATION message to the cell concerning : - a
full rate TCH channel (or the dynamic SDCCH/8 timeslot) for the related
TRX timeslot - a mobile which has sent a 44.018 CLASSMARK CHANGE
message with a "Mobile Station Classmark 3" Information Element field
bands". 2) The counter stops being incremented after the reception of a 48.058
RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
External Comment
126 / 1392
5.3.2.2.2.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 timeslot
in HR usage is busy by a multiband mobile station. A TCH radio timeslot (or a
dynamic SDCCH/8 timeslot) in HR usage is said busy by a multiband mobile
station when one or two HR sub-channels are busy by a multiband mobile
station. A MS is considered as multiband if it supports: - the P-GSM (or E-GSM
bands".
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/8
timeslot) is busy. For each channel allocation: 1) The counter starts being
incremented after the sending of the 48.058 CHANNEL ACTIVATION message
concerning : - 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 with
a "Mobile Station Classmark 3" Information Element field specifying that it
is 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 is
set to "GSM900 and DCS1800 bands", or, - the GSM850 and the DCS1800
bands". 2) The counter stops being incremented when no HR sub-channel
(or the dynamic SDCCH/8 timeslot) concerning a multiband mobile is active
anymore on the related TRX channel. This is after the reception of a 48.058
RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE
message) or the BSC internal radio resource release due to any BSS problem,
concerning the last HR TCH channel (or the dynamic SDCCH/8 timeslot) related
to a multiband mobile.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX_TS
Type Name
Type Definition
External Comment
127 / 1392
128 / 1392
6 BSC-TYPE 6 - TCH handover measurements
129 / 1392
6.1 All TYPE 6

C220 - NB_INC_EXT_TCH_HO_REQ (Section 6.2.3.3.2.1 )
C221 - NB_INC_EXT_TCH_HO_ATPT (Section 6.2.3.3.2.2 )
C230 - NB_INC_INT_TCH_HO_REQ (Section 6.2.3.4.2.1 )
C231 - NB_INC_INT_TCH_HO_ATPT (Section 6.2.3.4.2.2 )
C270 - NB_INTRA_TCH_HO_REQ (Section 6.2.3.5.2.1 )
C271 - NB_INTRA_TCH_HO_ATPT (Section 6.2.3.5.2.2 )
C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ (Section 6.2.3.7.2.1 )
C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL (Section
6.2.3.7.2.2 )
C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC (Section 6.3.2.2.2.1 )
C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH (Section 6.2.3.3.2.3 )
C42 - NB_INC_EXT_TCH_HO_SUCC (Section 6.2.3.3.2.4 )
C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS (Section 6.2.3.3.2.5
)
C440 - NB_TCH_HO_ATPT_23_TrafHandover (Section 6.2.2.2.2.1 )
C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover (Section 6.2.3.2.2.1 )
C447 - NB_TCH_HO_ATPT_26_BadQualHR (Section 6.2.3.2.2.2 )
C448 - NB_TCH_HO_ATPT_27_GoodQualFR (Section 6.2.3.2.2.3 )
C449 - NB_TCH_HO_ATPT_28_FastTraffic (Section 6.2.3.2.2.4 )
C450 - NB_TCH_HO_ATPT_22_TooShortDistance (Section 6.2.3.2.2.5 )
C45a - NB_OUT_EXT_TCH_REAL_HO_REQ (Section 6.2.3.6.2.1 )
C46 - NB_OUT_EXT_TCH_HO_SUCC (Section 6.2.3.6.2.2 )
C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES (Section 6.2.3.2.2.6 )
C461 - NB_TCH_HO_ATPT_29_TFO (Section 6.2.3.2.2.7 )
C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV (Section 6.2.3.6.2.3 )
C470 - NB_TCH_HO_ATPT_2_TooLowQualUp (Section 6.2.3.2.2.8 )
C471 - NB_TCH_HO_ATPT_3_TooLowLevUp (Section 6.2.3.2.2.9 )
C472 - NB_TCH_HO_ATPT_4_TooLowQualDown (Section 6.2.3.2.2.10 )
C473 - NB_TCH_HO_ATPT_5_TooLowLevDown (Section 6.2.3.2.2.11 )
C474 - NB_TCH_HO_ATPT_6_TooLongDistance (Section 6.2.3.2.2.12 )
C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp (Section 6.2.3.2.2.13 )
C477 - NB_TCH_HO_ATPT_16_TooHighLevInterfDown (Section 6.2.3.2.2.14 )
C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg (Section 6.2.3.2.2.15 )
C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand (Section
6.2.3.2.2.16 )
C48 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV (Section 6.2.3.6.2.4 )
C50 - NB_OUT_EXT_TCH_HO_ATPT (Section 6.2.3.6.2.5 )
C52 - NB_INC_INT_TCH_HO_SUCC (Section 6.2.3.4.2.3 )
130 / 1392
C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS (Section 6.2.3.4.2.4

)
C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS (Section 6.2.3.3.2.6 )
C541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
6.2.3.3.2.7 )
C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
6.2.3.4.2.5 )
C55a - NB_OUT_INT_TCH_HO_REQ (Section 6.2.3.7.2.3 )
C56 - NB_OUT_INT_TCH_HO_SUCC (Section 6.2.3.7.2.4 )
C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
6.2.3.5.2.3 )
C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV (Section 6.2.3.7.2.5 )
C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV (Section 6.2.3.7.2.6 )
C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell (Section
6.2.3.2.2.17 )
C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell (Section 6.2.3.2.2.18
)
C585e - NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell (Section
6.2.3.2.2.19 )
C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS (Section
6.2.3.2.2.20 )
C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone (Section 6.2.3.2.2.21 )
C586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone (Section
6.2.3.2.2.22 )
C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone (Section
6.2.3.2.2.23 )
C60 - NB_OUT_INT_TCH_HO_ATPT (Section 6.2.3.7.2.7 )
C62 - NB_INTRA_TCH_HO_SUCC (Section 6.2.3.5.2.4 )
C63 - NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV (Section 6.2.3.5.2.5 )
C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV (Section 6.2.3.5.2.6 )
C75 - NB_TCH_HO_MSC_TRIG (Section 6.2.3.2.2.24 )
6.2 Handover
6.2.1 All Handover
131 / 1392

6.2.3.7.2.2 )
)
6.2.3.2.2.16 )
)
6.2.3.3.2.7 )
6.2.3.4.2.5 )
6.2.3.5.2.3 )
132 / 1392

6.2.3.2.2.17 )
)
6.2.3.2.2.19 )
6.2.3.2.2.20 )
6.2.3.2.2.22 )
6.2.3.2.2.23 )
6.2.2 SDCCH+TCH
6.2.2.1 All SDCCH+TCH
6.2.2.2 Cause
6.2.2.2.1 All Cause
133 / 1392
6.2.2.2.2
6.2.2.2.2.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, with

the 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 BTS

because of cause 23. This counter is incremented in the serving cell. Note: This
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
TCH handover measurements
Type Definition
Set of counters related to the TCH handover procedure. The counters are
provided per handover category : incoming and outgoing, internal (inter-cell and
intra-cell) and external. The handover causes are also provided.
External Comment
134 / 1392
6.2.3 TCH
6.2.3.1 All TCH
6.2.3.7.2.2 )
)
6.2.3.2.2.16 )
)
135 / 1392

6.2.3.3.2.7 )
6.2.3.4.2.5 )
6.2.3.5.2.3 )
6.2.3.2.2.17 )
)
6.2.3.2.2.19 )
6.2.3.2.2.20 )
6.2.3.2.2.22 )
6.2.3.2.2.23 )
6.2.3.2 Cause
6.2.3.2.1 All Cause
136 / 1392

6.2.3.2.2.16 )
6.2.3.2.2.17 )
)
6.2.3.2.2.19 )
6.2.3.2.2.20 )
6.2.3.2.2.22 )
6.2.3.2.2.23 )
6.2.3.2.2
6.2.3.2.2.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).
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
137 / 1392
6.2.3.2.2.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 channel
adaptation due to bad radio quality" on a TCH channel.
Trigger condition
Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS

because of cause 26 on TCH.
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
138 / 1392
6.2.3.2.2.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 channel
adaptation due to good radio quality" on a TCH channel.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
139 / 1392
6.2.3.2.2.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

because of cause 28 on TCH. This counter is incremented in the serving cell.
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
140 / 1392
6.2.3.2.2.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: "too
short MS-BTS distance" on a TCH channel (in HR or FR usage). Only the outer
zones of extended cells are concerned by this counter.
Trigger condition
Whenever 44.018HANDOVER COMMAND is sent to the mobile via the BTS

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
141 / 1392
6.2.3.2.2.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 TCH
timeslots is less than or equal to NUM_TCH_EGNCY_HO.
Trigger condition
The counter is incremented on the serving cell whenever the 48.058 CHANNEL
ACTIVATION message allocating a TCH channel is sent and the following two
conditions are both fulfilled: 1) the TCH is allocated to serve i) an internal
handover Cause 2, 3, 4, 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 22, 27, or, ii) an
external handover Cause "Uplink quality", "Uplink strength", "Downlink quality",
"Downlink strength", "Distance", or iii) a normal assignment or an external
handover with the preemption indicator set (i.e. Preemption Capability Indicator
= 1 and EN_TCH_PREEMPT = Enable). 2) the number of free TCH timeslots is
less than or equal to NUM_TCH_EGNCY_HO. Note 1: This counter counts both
inter-PLMN and intra-PLMN handover events. Note 2: The HMI name of the
parameter NUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
142 / 1392
6.2.3.2.2.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 mismatch

resolution, TFO optimisation). MC461 = C461
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
143 / 1392
6.2.3.2.2.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: "uplink

quality too low" on a TCH channel (in HR or FR usage). This counter takes into
account handovers from TCH in traffic or in signaling mode.
Trigger condition

because of cause 2. This counter is incremented in the serving cell, Note: This
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
144 / 1392
6.2.3.2.2.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: "uplink

quality too low" on a TCH channel (in HR or FR usage). This counter takes into
account handovers from TCH in traffic or in signaling mode.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
145 / 1392
6.2.3.2.2.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 counter
takes 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 BTS

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
146 / 1392
6.2.3.2.2.11 C473 - NB_TCH_HO_ATPT_5_TooLowLevDown

Long Name
NB_TCH_HO_ATPT_5_TooLowLevDown
Definition

"downlink level too low" on a TCH channel (in HR or FR usage). This counter
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
147 / 1392
6.2.3.2.2.12 C474 - NB_TCH_HO_ATPT_6_TooLongDistance

Long Name
NB_TCH_HO_ATPT_6_TooLongDistance
Definition

"MS-BTS distance too long" on a TCH channel (in HR or FR usage). This
counter takes into account handovers from TCH in traffic or in signaling mode.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
148 / 1392
6.2.3.2.2.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 level
interference on uplink" on a TCH channel (in HR or FR usage). This counter
Trigger condition
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS

because of cause 15.
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
149 / 1392
6.2.3.2.2.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 level
interference on downlink" on a TCH channel (in HR or FR usage). This counter
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
150 / 1392
6.2.3.2.2.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: "too
low power budget" on a TCH channel (in FR or FR usage). This counter takes
into account handovers from TCH in traffic or in signaling mode.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
151 / 1392
6.2.3.2.2.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: "high
level in neighbour cell in the preferred band" on a TCH channel (in HR or FR
usage). This counter is related to multiband.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
152 / 1392
6.2.3.2.2.17 C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell

Long Name
NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell
Definition

"several consecutive bad SACCH frames received in a micro cell" on a TCH
channel (in HR or FR usage). This counter takes into account handovers
from TCH in traffic or in signaling mode. This counter is related to micro cell
environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
153 / 1392
6.2.3.2.2.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 a
TCH channel (in HR or FR usage). This counter takes into account handovers
environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
154 / 1392
6.2.3.2.2.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: "too
low level on the downlink in a microcell compared to a high threshold" on a
TCH channel (in HR or FR usage). This counter takes into account handovers
environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
155 / 1392
6.2.3.2.2.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: "high
level in neighbour lower layer for slow mobile" on a TCH channel (in HR or FR
usage). This counter is related to micro cell environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
156 / 1392
6.2.3.2.2.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 level
too low" on TCH channel (in HR or FR usage). This counter is related to
concentric cell environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
157 / 1392
6.2.3.2.2.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 downlink
level too low" on TCH channel (in HR or FR usage). This counter is related to
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
158 / 1392
6.2.3.2.2.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 and
downlink levels too high" on TCH channel (in HR or FR usage). This counter is
related to concentric cell environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
159 / 1392
6.2.3.2.2.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 A

interface from the MSC and timer T_HO_REQ_LOST is not running. Note: This
counter counts both inter-PLMN and intra-PLMN handover events. Note: This
counter does not count hantover to UMTS
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
160 / 1392
6.2.3.3 Incoming External

6.2.3.3.1 All Incoming External
)
6.2.3.3.2.7 )
6.2.3.3.2
6.2.3.3.2.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 the

target cell on TCH. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
161 / 1392
6.2.3.3.2.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 BSC

containing the 44.018HANDOVER COMMAND towards the target cell on TCH.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
162 / 1392
6.2.3.3.2.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 -preparation

failures 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 target
BSC to the MSC. 2) Whenever a 48.008 HANDOVER FAILURE message with
a cause value of "terrestrial circuit already allocated" is sent on A interface
from the target BSC to the MSC. 3) Whenever a 48.008 HANDOVER FAILURE
message with a cause value of "BSS not equipped" is sent on A interface from
the target BSC to the MSC. Note: This counter counts both inter-PLMN and
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
163 / 1392
6.2.3.3.2.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

interface from the target cell for a TCH channel that is involved in an external
TCH handover. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
164 / 1392
6.2.3.3.2.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 -execution

failures due to MS access problem.
Trigger condition

cause value of "handover access failure" is received on Abis interface from the
target cell for a TCH channel during an external TCH handover. 2) Whenever
the timer supervising the handover procedure on the target cell (T9113), expires
during an external TCH handover. 3) Whenever a 48.008 CLEAR COMMAND
with a cause value of "radio interface failure - reversion to old channel" is
received on A interface on the target BSC from the MSC during an external
TCH handover. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
165 / 1392
6.2.3.3.2.6 C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Long Name
NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS
Definition

failures due to congestion (C541a), or A-traffic-channel status mismatch
between the BSC and the MSC (C41b).
Trigger condition
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
166 / 1392
6.2.3.3.2.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

failures 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 the
MSC during an external TCH handover. Note 1: This counter counts both
inter-PLMN and intra-PLMN handover events. Note 2: In MX BSC, this counter
is incremented whenever a 48.008 HANDOVER FAILURE message with a
cause value of "no radio resource available" is sent due to the TCH processing
capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP
parameter. In this case, MC926 is also incremented by one. Note 3: In IP mode,
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
167 / 1392
6.2.3.4 Incoming Internal

6.2.3.4.1 All Incoming Internal
)
6.2.3.4.2.5 )
6.2.3.4.2
6.2.3.4.2.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) handover

requests.
Trigger condition
target 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
Measured Object
Common cell
Type Name
Type Definition
External Comment
168 / 1392
6.2.3.4.2.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) handover

attempts.
Trigger condition
44.018HANDOVER COMMAND is sent to the serving BTS for internal inter cell
TCH handover. However, the counter is incremented in the TARGET cell, based
on the target cell ID indicated by the HO Command message,
Sub Domain 1
TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
169 / 1392
6.2.3.4.2.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) handover

successes.
Trigger condition

interface from the target cell for a TCH channel that is involved in an internal
inter-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
170 / 1392
6.2.3.4.2.4 C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS

Long Name
NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS
Definition

-execution failures due to MS access problem; the mobile either reverts or does
not to the old channel.
Trigger condition
an internal inter-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
171 / 1392
6.2.3.4.2.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

-preparation failures due to congestion.
Trigger condition
Whenever an internal inter-cell TCH handover cannot be performed, because

the target cell is congested (no free TCH channel). Note 1: In MX BSC,
this counter is incremented whenever an internal inter-cell TCH handover
cannot be performed due to the TCH processing capacity of CCP reaches the
limit defined by the MAX_TCH_PER_CCP parameter. In this case, MC926
is also incremented by one. Note 2: In IP mode, this counter is increased
by 1 if: - the cell mapped on a BTS is in IP congestion status; - or the TCH
processing capacity of AbisBTSGroup reaches the limit defined by the
Sub Domain 1
TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
172 / 1392
6.2.3.5 Intra
6.2.3.5.1 All Intra
6.2.3.5.2.3 )
6.2.3.5.2
6.2.3.5.2.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 counter
takes into account handovers from TCH in traffic or in signaling mode. It does
not take into account DTM Assignments.
Trigger condition
Whenever the BSC process responsible for the handover procedure starts an
intra cell TCH handover procedure.
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
173 / 1392
6.2.3.5.2.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 counter
takes into account handovers from TCH in traffic or in signaling mode. It does
not take into account DTM Assignments.
Trigger condition
44.018 ASSIGNMENT COMMAND is sent to the BTS for intra cell handover
on TCH.
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
174 / 1392
6.2.3.5.2.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 failures

due to congestion. This counter takes into account handovers from TCH in
traffic or in signaling mode. It does not take into account DTM Assignments.
Trigger condition
Whenever a internal intra-cell TCH handover cannot be performed, because

there 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 be
performed due to the TCH processing capacity of CCP reaches the limit
defined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is
also incremented by one. Note 2: In IP mode, this counter is increased by
1 if: - the cell mapped on a BTS is in IP congestion status; - or the TCH
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
175 / 1392
6.2.3.5.2.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. This

does not take into account DTM Assignments.
Trigger condition

interface on the target channel for a TCH channel that is involved in an internal
intra-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
176 / 1392
6.2.3.5.2.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 failures

due MS access problem; the mobile is lost. This counter takes into account
DTM Assignments.
Trigger condition
an internal intra-cell.
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
177 / 1392
6.2.3.5.2.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 due

to MS access problem with reversion of the mobile to the old channel. This
does not take into account DTM Assignments.
Trigger condition
Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis

interface on the serving channel, during an internal intra-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
178 / 1392
6.2.3.6 Outgoing External

6.2.3.6.1 All Outgoing External
6.2.3.6.2
6.2.3.6.2.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. This

Trigger condition
Whenever a 48.008 HANDOVER REQUIRED message with the cell

identification discriminator set to a value identifying a GSM handover is sent
on A interface to the MSC for a TCH handover towards a 2G cell. If more
than one 48.008 HANDOVER REQUIRED is sent in the frame of the same
Handover procedure, the counter is incremented only once. 48.008 HANDOVER
REQUIRED is sent in following situations: 1) An external handover alarm has
been raised, with corresponding list of candidate cells. 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 External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
179 / 1392
6.2.3.6.2.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 signaling
mode.
Trigger condition
External TCH handover in the following cases: 1/ a 48.008 CLEAR COMMAND

message with a cause value of "handover successful" is received on A interface
on the serving BSC from the MSC. 2/ 48.008 CLEAR COMMAND (cause=
"normal event/call control") is received while T8 is running. Note: This counter
counts both inter-PLMN and intra-PLMN handover events. Note: This counter
doesnt count hantover to UMTS
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
180 / 1392
6.2.3.6.2.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 -execution

failures due to MS access problem with reversion of the mobile to the old
channel. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition
Whenever a 44.018 HANDOVER FAILURE message is received on Abis

interface from the serving cell , during an external TCH handover. Note 1: This
counter counts both inter-PLMN and intra-PLMN handover events. Note 2: This
counter does not count hantover to UMTS.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
181 / 1392
6.2.3.6.2.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 execution

failures due to MS access problem without reversion of the mobile to the old
channel (call drop). This counter takes into account handovers from TCH in
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 CLEAR
COMMAND with "normal event/call control" cause was received from the MSC,
leading to a normal call release. In such a case, the handover is considered
as successful. Note: This counter counts both inter-PLMN and intra-PLMN
handover events. Note: This counter does not count handover to UMTS
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
182 / 1392
6.2.3.6.2.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. This

Trigger condition
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis

interface on the serving channel, during an external TCH handover procedure.
Note 1: This counter counts both inter-PLMN and intra-PLMN handover events.
Note 2: This counter does not count handover to UMTS
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
183 / 1392
6.2.3.7 Outgoing Internal

6.2.3.7.1 All Outgoing Internal
6.2.3.7.2.2 )
6.2.3.7.2
6.2.3.7.2.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) handover

requests, plus the number of internal directed retries requests, towards the
inner zone of a target concentric cell.
Trigger condition
Whenever the BSC process responsible for the handover procedure at the
serving cell generates an HO alarm towards the inner zone of a target concentric
cell for internal inter-cell TCH handover, or for an internal directed retry.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
184 / 1392
6.2.3.7.2.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

-executions failures, plus the number of internal directed retries -execution
failures due to MS access problem, towards the inner zone of a target concentric
cell. 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 the
sending of 44.018HANDOVER COMMAND and is stopped upon the receipt
of 44.018HANDOVER COMPLETE).
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
185 / 1392
6.2.3.7.2.3 C55a - NB_OUT_INT_TCH_HO_REQ

Long Name
NB_OUT_INT_TCH_HO_REQ
Definition

requests. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition
target cell (among a list of target cells) for internal inter cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
186 / 1392
6.2.3.7.2.4 C56 - NB_OUT_INT_TCH_HO_SUCC

Long Name
NB_OUT_INT_TCH_HO_SUCC
Definition

successes. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition

interface from the target cell , during an internal inter-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
187 / 1392
6.2.3.7.2.5 C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV

Long Name
NB_OUT_INT_TCH_HO_EXEC_FAIL_REV
Definition

-execution failures due to MS access problem with reversion of the mobile to
the old channel. This counter takes into account handovers from TCH in traffic
or in signaling mode.
Trigger condition

interface from the serving cell, during an internal inter-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
188 / 1392
6.2.3.7.2.6 C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV

Long Name
NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV
Definition

-execution failures due to MS access problem without reversion of the mobile
to the old channel (call drop). This counter takes into account handovers from
TCH in traffic or in signaling mode.
Trigger condition
an internal inter-cell TCH handover.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
189 / 1392
6.2.3.7.2.7 C60 - NB_OUT_INT_TCH_HO_ATPT

Long Name
NB_OUT_INT_TCH_HO_ATPT
Definition

attempts. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition

interface on the serving channel, during an internal inter-cell TCH handover
procedure.
Sub Domain 1
TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
190 / 1392
6.3 Traffic Load



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

allocated in the BSC, in the inner zone of a concentric cell.
Trigger condition
Whenever 48.058CHANNEL ACTIVATION is about to be send on Abis to

activate a TCH channel in the inner zone of the concentric cell for any normal
assignment.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
191 / 1392
192 / 1392
7 BSC-TYPE 7 - LapD measurements
193 / 1392
7.1 All TYPE 7

L1.1 - NB_LAPD_INFO_FRAME_SENT (Section 7.4.2.2.2.1 )
L1.12 - NB_LAPD_CRC_ERROR (Section 7.2.2.2.2.1 )
L1.15 - NB_LAPD_INFO_FRAME_RESENT (Section 7.2.2.2.2.2 )
L1.16 - TIME_LAPD_UNAVAIL (Section 7.3.2.2.2.1 )
L1.17 - NB_LAPD_EST (Section 7.2.2.2.2.3 )
L1.18 - TIME_LAPD_CONG (Section 7.2.2.2.2.4 )
L1.2 - NB_LAPD_INFO_FRAME_REC (Section 7.4.2.2.2.2 )
L1.5 - NB_LAPD_RNR_SENT (Section 7.2.2.2.2.5 )
L1.6 - NB_LAPD_RNR_REC (Section 7.2.2.2.2.6 )

7.2.2 Interface
7.2.2.1 All Interface
7.2.2.2 Abis
7.2.2.2.1 All Abis
194 / 1392
7.2.2.2.2 LapD
7.2.2.2.2.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 CRC
error in a received Frame. Note 1: In case of LapD over UDP, this counter is
meaningless 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
External Comment
195 / 1392
7.2.2.2.2.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 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
196 / 1392
7.2.2.2.2.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 or

Timer recovery (data link reset initiated by the BTS). 2) Whenever the layer
2 receives an UA frame in the state Awaiting Establishment (i.e. data link
establishment, re-establishment or link reset initiated by the BSC).
Sub Domain 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
197 / 1392
7.2.2.2.2.4 L1.18 - TIME_LAPD_CONG

Long Name
TIME_LAPD_CONG
Definition
Time in seconds during which the LapD link is congested in transmission in

the BSC.
Trigger condition
This counter will be incremented with the number of seconds elapsed

between the reception of L2_CONGESTION_IND and the reception of
L2_END_CONGESTION_IND by the Layer 3 in the BSC
Sub Domain 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
198 / 1392
7.2.2.2.2.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 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
199 / 1392
7.2.2.2.2.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 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
200 / 1392

7.3.2 Interface
7.3.2.2 Abis
7.3.2.2.1 All Abis
7.3.2.2.2.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 elapsed

between LAPD layer entities initiation (first DL_ESTABLISH_ REQUEST
primitive sent by Layer 3 to Layer 2 for that logical LAPD link) and reception
of the DL-ESTABLISH-CONFIRM primitive for that logical LAPD link. 2) This
counter will also be incremented with the number of seconds elapsed between
reception of the DL-RELEASE-INDICATION primitive and reception of the
DL_ESTABLISH-CONFIRM primitive for that logical LAPD link.
Sub Domain 1
Interface
Sub Domain 2
Abis
Sub Domain 3
Availability
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
201 / 1392
7.4 Traffic Load

7.4.2 Interface
7.4.2.2 Abis
7.4.2.2.1 All Abis
7.4.2.2.2 LapD
7.4.2.2.2.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 the

re-transmissions.
Trigger condition
Whenever an Information Frame is transmitted on a logical LAPD link, which is

not a retransmission of a previous Information Frame.
Sub Domain 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
202 / 1392
7.4.2.2.2.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 the

re-transmissions.
Trigger condition
Whenever an Information Frame is received on a logical LAPD link.
Sub Domain 1
Interface
Sub Domain 2
Abis
Sub Domain 3
LapD
Measured Object
LapD
Type Name
LapD measurements
Type Definition
External Comment
203 / 1392
204 / 1392
8 BSC-TYPE 8 - X25 measurements
205 / 1392
8.1 All TYPE 8

X3.20 - NB_X25_INC_CALL_SUCC_CLOSED (Section 8.3.2.2.2.1 )
X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED (Section 8.3.2.2.2.2 )
X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED (Section 8.2.2.2.2.1 )
X3.23 - NB_X25_OUT_CALL_ABNORM_CLOSED (Section 8.2.2.2.2.2 )

8.2.2 Interface
8.2.2.2 OMC-BSC
8.2.2.2.1 All OMC-BSC
8.2.2.2.2 X25
8.2.2.2.2.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 seen
by the BSC.
Trigger condition
Whenever an incoming X.25 CALL is closed in an abnormal way.
Sub Domain 1
Interface
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
External Comment
206 / 1392
8.2.2.2.2.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 seen
by the BSC.
Trigger condition
Whenever an outgoing X.25 CALL is closed in an abnormal way.
Sub Domain 1
Interface
Sub Domain 2
OMC-BSC
Sub Domain 3
X25
Measured Object
X25
Type Name
X25 measurements
Type Definition
External Comment
207 / 1392
8.3 Traffic Load

8.3.2 Interface
8.3.2.2 OMC-BSC
8.3.2.2.1 All OMC-BSC
8.3.2.2.2 X25
8.3.2.2.2.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 1
Interface
Sub Domain 2
OMC-BSC
Sub Domain 3
X25
Measured Object
X25
Type Name
X25 measurements
Type Definition
External Comment
208 / 1392
8.3.2.2.2.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 1
Interface
Sub Domain 2
OMC-BSC
Sub Domain 3
X25
Measured Object
X25
Type Name
X25 measurements
Type Definition
External Comment
209 / 1392
210 / 1392
9 BSC-TYPE 9 - N7 measurements
211 / 1392
9.1 All TYPE 9

N1.1 - TIME_N7_ALIGNED (Section 9.3.2.2.2.1 )
N1.10 - NB_N7_CHANGEOVER (Section 9.2.2.2.2.1 )
N1.11 - NB_N7_CHANGEBACK (Section 9.2.2.2.2.2 )
N1.12 - NB_N7_RESTORATION (Section 9.2.2.2.2.3 )
N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE (Section 9.2.2.2.2.4 )
N1.3 - NB_N7_LINK_FAIL_FIB_BSN (Section 9.2.2.2.2.5 )
N1.4 - NB_N7_LINK_FAIL_T7_EXP (Section 9.2.2.2.2.6 )
N1.5 - NB_N7_LINK_FAIL_SU_ERROR_RATE (Section 9.2.2.2.2.7 )
N1.6 - NB_N7_LINK_FAIL_CONG (Section 9.2.2.2.2.8 )
N1.7 - NB_N7_LINK_FAIL_ALIGNMENT (Section 9.2.2.2.2.9 )
N1.8 - NB_N7_SU_REC_WITH_ERROR (Section 9.2.2.2.2.10 )
N1.9 - NB_N7_NEG_ACK_REC (Section 9.2.2.2.2.11 )
N2.7 - TIME_N7_UNAVAIL_ERROR_SL (Section 9.3.2.2.2.2 )
N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE (Section 9.3.2.2.2.3 )
N3.1 - NB_N7_SIF_SIO_SENT (Section 9.4.2.2.2.1 )
N3.10 - NB_N7_MSU_DISC_DUE_CONG (Section 9.2.2.2.2.12 )
N3.11 - NB_N7_CONG_WITH_MSU_LOST (Section 9.2.2.2.2.13 )
N3.2 - NB_N7_OCTETS_RESENT (Section 9.4.2.2.2.2 )
N3.3 - NB_N7_MSU_SENT (Section 9.4.2.2.2.3 )
N3.4 - NB_N7_SIF_SIO_REC (Section 9.4.2.2.2.4 )
N3.5 - NB_N7_MSU_REC (Section 9.4.2.2.2.5 )
N3.7 - TIME_N7_UNAVAIL_CONG (Section 9.3.2.2.2.4 )
N4.2 - TIME_N7_UNAVAIL_LINK_SET (Section 9.3.2.2.2.5 )

212 / 1392

9.2.2 Interface
9.2.2.2 A
9.2.2.2.1 All A
213 / 1392
9.2.2.2.2 Layers1-2-3
9.2.2.2.2.1 N1.10 - NB_N7_CHANGEOVER
Long Name
NB_N7_CHANGEOVER
Definition
Number of changeovers from the primary (observed) N7 SL to another

secondary one.
Trigger condition
Whenever a changeover is made from using the primary signalling link to the
secondary signalling link.
Sub Domain 1
Interface
Sub Domain 2
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.
External Comment
214 / 1392
9.2.2.2.2.2 N1.11 - NB_N7_CHANGEBACK

Long Name
NB_N7_CHANGEBACK
Definition
Number of changebacks from the secondary (observed) N7 SL to the primary

one.
Trigger condition
Whenever a change back is made from using the secondary signalling link
to the primary signalling link.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
215 / 1392
9.2.2.2.2.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 correctly
aligned after the removal of a failure condition, this counter will be incremented.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
216 / 1392
9.2.2.2.2.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 abnormal

Forward Indicator Bit (FIB) being received by the BSS. 2) Whenever a No.7
Signalling Link failure is detected due to an abnormal Backward Sequence
Number (BSN) being received by the BSS. 3) Whenever the timer supervising
the reception of an acknowledgement message (T7) expires. 4) Whenever a
No.7 Signalling Link failure is detected due to an excessive signal unit error rate
being detected. 5) Whenever a No.7 Signalling Link failure is detected due to
an excessive duration of Signalling Link congestion.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
217 / 1392
9.2.2.2.2.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 recieved

MSUs or fill-in SUs indicate the start of a retransmission when no NACK
has been sent. 2) Whenever two Backward Sequence Number values in 3
concecutive received MSUs or fill-in SUs are not the same as the previous one or
any of the Forward Sequence Number values of SUs in retransmission buffers.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
218 / 1392
9.2.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
219 / 1392
9.2.2.2.2.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 Signal

Unit error rate.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
220 / 1392
9.2.2.2.2.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 duration

of Signalling Link congestion.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
221 / 1392
9.2.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
222 / 1392
9.2.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
223 / 1392
9.2.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
224 / 1392
9.2.2.2.2.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 buffer

overflow caused by an extended period of Signalling Link congestion.
Trigger condition
Whenever an Message Signalling Unit (MSU) is discarded due to Signalling

Link congestion.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
225 / 1392
9.2.2.2.2.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 due
to congestion on the N7 SL.
Trigger condition
Whenever 1 or more MSUs are lost due to congestion on the signalling link.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
226 / 1392

9.3.2 Interface
9.3.2.2 A
9.3.2.2.1 All A
227 / 1392
9.3.2.2.2.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
aligned, this counter will be incremented every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
228 / 1392
9.3.2.2.2.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 a
fault on the N7 SL.
Trigger condition
Whenever the No.7 Signalling channel between the MSC and BSS fails, until the
time when the fault has been removed and the link aligned, this counter will be
incremented every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
229 / 1392
9.3.2.2.2.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 remote
MSC processor outage.
Trigger condition
Whenever the MSC indicates to the BSS that it is unable to process signalling
traffic due to an outage, this counter will be incremented every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
230 / 1392
9.3.2.2.2.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 incremented

every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
231 / 1392
9.3.2.2.2.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 available
on the N7.
Trigger condition
Whenever the Link Set towards the MSC is unavailable, this counter will be
updated every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Link Set
Type Name
N7 measurements
Type Definition
External Comment
232 / 1392
9.4 Traffic Load

9.4.2 Interface
9.4.2.2 A
9.4.2.2.1 All A
233 / 1392
9.4.2.2.2 Layers1-2-3
9.4.2.2.2.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, plus
one for the SIO octet.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
234 / 1392
9.4.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
235 / 1392
9.4.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
236 / 1392
9.4.2.2.2.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 Information

Octets (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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
237 / 1392
9.4.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
Layers1-2-3
Measured Object
N7 Signalling Link
Type Name
N7 measurements
Type Definition
External Comment
238 / 1392
10 BSC-TYPE 18 - A interface measurements
239 / 1392
10.1 All TYPE 18

C180a - NB_N7_CLEAR_REQ_RadioIntMessFail (Section 10.2.2.2.2.1 )
C180b - NB_N7_CLEAR_REQ_O&Minterv (Section 10.2.2.2.2.2 )
C180c - NB_N7_CLEAR_REQ_EquipFail (Section 10.2.2.2.2.3 )
C180d - NB_N7_CLEAR_REQ_RadioIntFail (Section 10.2.2.2.2.4 )
C180e - NB_N7_CLEAR_REQ_NoRadioResAvail (Section 10.2.2.2.2.5 )
C181a - NB_N7_ASS_FAIL_RadioIntMessFail (Section 10.2.2.2.2.6 )
C181b - NB_N7_ASS_FAIL_O&Minterv (Section 10.2.2.2.2.7 )
C181c - NB_N7_ASS_FAIL_EquipFail (Section 10.2.2.2.2.8 )
C181d - NB_N7_ASS_FAIL_NoRadioResAvail (Section 10.2.2.2.2.9 )
C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc (Section 10.2.2.2.2.10 )
C181f - NB_N7_ASS_FAIL_ReqTrans/RateUnav (Section 10.2.2.2.2.11 )
C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan (Section 10.2.2.2.2.12 )
C181h - NB_N7_ASS_FAIL_RadioIntFail (Section 10.2.2.2.2.13 )
C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp (Section 10.2.2.2.2.14 )
C181j - NB_N7_ASS_FAIL_BSSnotEquip (Section 10.2.2.2.2.15 )
C181k - NB_N7_ASS_FAIL_ProtocolError (Section 10.2.2.2.2.16 )
C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav (Section 10.2.2.2.2.17 )
C182 - NB_N7_CLEAR_REQ_EST_PHAS (Section 10.2.2.2.2.18 )
C750 - TIME_A_CHANNEL_BUSY (Section 10.3.2.2.2.1 )
C751 - NB_A_CHANNEL_ALLOC (Section 10.3.2.2.2.2 )

240 / 1392

10.2.2 Interface
10.2.2.2 A
10.2.2.2.1 All A
241 / 1392

10.2.2.2.2 BSSAP
10.2.2.2.2.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 "radio

interface message failure" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
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 and

08.08ASSIGNMENT FAILURE
External Comment
242 / 1392
10.2.2.2.2.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 the

MSC.
Trigger condition
Whenever a 48.008 CLEAR REQUEST message with a cause value of "O&M

intervention" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
243 / 1392
10.2.2.2.2.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 the

MSC.
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 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
244 / 1392
10.2.2.2.2.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 to

the MSC.
Trigger condition
Whenever a 48.008 CLEAR REQUEST message with a cause value of "radio

interface failure" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
245 / 1392
10.2.2.2.2.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 radio
resource available" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
246 / 1392
10.2.2.2.2.6 C181a - NB_N7_ASS_FAIL_RadioIntMessFail

Long Name
NB_N7_ASS_FAIL_RadioIntMessFail
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="radio interface message

failure") 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 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
247 / 1392
10.2.2.2.2.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") sent

to the MSC.
Trigger condition

"O&M intervention" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
248 / 1392
10.2.2.2.2.8 C181c - NB_N7_ASS_FAIL_EquipFail

Long Name
NB_N7_ASS_FAIL_EquipFail
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="equipment failure") sent

to the MSC.
Trigger condition

"equipment failure" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
249 / 1392
10.2.2.2.2.9 C181d - NB_N7_ASS_FAIL_NoRadioResAvail

Long Name
NB_N7_ASS_FAIL_NoRadioResAvail
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="no radio resource

available") sent to the MSC.
Trigger condition

"no radio resource available" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
250 / 1392
10.2.2.2.2.10 C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc

Long Name
NB_N7_ASS_FAIL_ReqTerResUnav/Alloc
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="requested terrestrial

resource unavailable", or "terrestrial resource already allocated") sent to the
MSC.
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)
"terrestrial resource already allocated" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
251 / 1392
10.2.2.2.2.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/rate

adaptation unavailable") sent to the MSC.
Trigger condition

"requested transcoding/rate adaptation unavailable" is sent on A interface to
the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
252 / 1392
10.2.2.2.2.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

"radio interface failure - reversion to old channel" is sent on A interface to the
MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
253 / 1392
10.2.2.2.2.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

"radio interface failure" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
254 / 1392
10.2.2.2.2.14 C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp

Long Name
NB_N7_ASS_FAIL_CipherAlgoNotSupp
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="ciphering algorithm not

supported") sent to the MSC.
Trigger condition

"cipher algorithm not supported" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
255 / 1392
10.2.2.2.2.15 C181j - NB_N7_ASS_FAIL_BSSnotEquip

Long Name
NB_N7_ASS_FAIL_BSSnotEquip
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="BSS not equiped") sent

to the MSC.
Trigger condition

"BSS not equiped" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
256 / 1392
10.2.2.2.2.16 C181k - NB_N7_ASS_FAIL_ProtocolError

Long Name
NB_N7_ASS_FAIL_ProtocolError
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="protocol error between

BSC and MSC") sent to the MSC.
Trigger condition

"protocol error between BSC and MSC" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
257 / 1392
10.2.2.2.2.17 C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav

Long Name
NB_N7_ASS_FAIL_ReqSpeechVersUnav
Definition
Number of 48.008ASSIGNMENT FAILURE (cause="requested speech version

unavailable") sent to the MSC.
Trigger condition

"requested speech version unavailable" is sent on A interface to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
258 / 1392
10.2.2.2.2.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 TCH
established phase, and for internal inter-cell and external TCH handover failures.
Intra-cell handover failures are not taken into account. This counter takes into
account TCH in traffic mode or in signaling mode.
Trigger condition
1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is

sent on A interface to the MSC, for a call in TCH established phase. Note that
this trigger takes into account TCH in traffic mode or in signaling mode. 2)
Whenever a 48.008 CLEAR REQUEST message is sent on A interface to the
MSC, after a Handover command is sent, during a TCH internal inter-cell HO.
3) Whenever a 48.008 CLEAR REQUEST message is sent on A interface to
the MSC, after a Handover command is sent, during a TCH external HO. 4)
Whenever a 48.008 CLEAR REQUEST message is sent on A interface to the
MSC, after a DTM Assignment Command is sent, during a DTM assignment,
for a MS which already had a TCH allocated (i.e. the TCH in DTM Assignment
Command is established in traffic mode).
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
BSSAP
Measured Object
BSC
Type Name
Type Definition

External Comment
259 / 1392
10.3 Traffic Load

10.3.2 Interface
10.3.2.2 A
10.3.2.2.1 All A
10.3.2.2.2
10.3.2.2.2.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 which
the A channel is busy. For each channel allocation: 1) The counter starts being
incremented when the A channel is activated (see C751) 2) The counter stops
being incremented when the A channel is deallocated after the reception of a
48.058 RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry
of timer T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL
RELEASE message).
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Measured Object
A interface channel
Type Name
Type Definition

External Comment
260 / 1392
10.3.2.2.2.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.008

ASSIGNMENT REQUEST. 2) Whenever a A channel is allocated following
the reception of 48.008 HANDOVER REQUEST 3) Whenever a A channel is
allocated during an internal handover procedure
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Measured Object
A interface channel
Type Name
Type Definition

External Comment
261 / 1392
262 / 1392
11 BSC-TYPE 19 - SMS PP measurements
263 / 1392
11.1 All TYPE 19

C190 - NB_SMS_PP_CON_MO_SDCCH (Section 11.2.2.2.3.1 )
C191 - NB_SMS_PP_CON_MT_SDCCH (Section 11.2.2.2.3.2 )
C192 - NB_SMS_PP_CON_MO_SACCH (Section 11.2.2.2.3.3 )
C193 - NB_SMS_PP_CON_MT_SACCH (Section 11.2.2.2.3.4 )
C194a - NB_SMS_PP_CON_REJ_RadioIntFail (Section 11.2.2.2.2.1 )
C194b - NB_SMS_PP_CON_REJ_BSSnotEquip (Section 11.2.2.2.2.2 )
C194c - NB_SMS_PP_CON_REJ_ProtocolError (Section 11.2.2.2.2.3 )
C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR (Section 11.2.2.2.2.4 )

11.2.2 Short Message Service

11.2.2.1 All Short Message Service
264 / 1392
11.2.2.2 Point to Point

11.2.2.2.1 All Point to Point
11.2.2.2.2 Failure
11.2.2.2.2.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 "radio
interface failure".
Trigger condition
Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 is sent from
BSC to MSC with a cause value of "radio interface failure".
Sub Domain 1
Short Message Service
Sub Domain 2
Point to Point
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
Set of counters related to the Short Message Service Point to Point. The SMS
transactions on SDCCH and SACCH channels, originating or terminating, are
counted.
External Comment
265 / 1392
11.2.2.2.2.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 not
equipped",
Trigger condition
Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 with a cause
value of "BSS not equipped" is sent on A interface from BSC to MSC.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
266 / 1392
11.2.2.2.2.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 "protocol
error between BSC and MSC".
Trigger condition
Whenever a 48.008 SAPI "n" REJECT message related to SAPI 3 with a cause
value of "protocol error between BSC and MSC" is sent on A interface from
BSC to MSC.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
267 / 1392
11.2.2.2.2.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 by

the BSC due to a LAPDm error.
Trigger condition
Whenever an 48.058 ERROR INDICATION message related to SAPI 3 is

received by the BSC with one of the following cause values : a) timer T200
expired (N200+1) times b) unsolicited DM response, multiple frame established
state c) sequence error.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
268 / 1392
11.2.2.2.3 Success
11.2.2.2.3.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 to

an SDCCH sub-channel is received by the BSC.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
269 / 1392
11.2.2.2.3.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 SDCCH

sub-channel is received by the BSC.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
270 / 1392
11.2.2.2.3.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 to

an SACCH sub-channel is received by the BSC.
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
271 / 1392
11.2.2.2.3.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 SACCH

Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
SMS PP measurements
Type Definition
counted.
External Comment
272 / 1392
12 BSC-TYPE 25 - SCCP measurements
273 / 1392
12.1 All TYPE 25

C153a - NB_N7_CON_EST_FAIL_DUE_NSS (Section 12.2.2.2.2.1 )
C153b - NB_N7_CON_EST_FAIL_DUE_BSS (Section 12.2.2.2.2.2 )
C251 - NB_N7_UNIT_DATA_SENT (Section 12.3.2.2.2.1 )
C252 - NB_N7_UNIT_DATA_REC (Section 12.3.2.2.2.2 )
C253 - NB_N7_CON_REQ_SENT (Section 12.3.2.2.2.3 )
C254 - NB_N7_CON_REQ_REC (Section 12.3.2.2.2.4 )
C255 - NB_N7_CON_CONF_SENT (Section 12.3.2.2.2.5 )
C256 - NB_N7_CON_CONF_REC (Section 12.3.2.2.2.6 )
C257 - NB_N7_CON_REF_SENT (Section 12.2.2.2.2.3 )
C258 - NB_N7_CON_REF_REC (Section 12.2.2.2.2.4 )

12.2.2 Interface
12.2.2.2 A
12.2.2.2.1 All A
274 / 1392
12.2.2.2.2 SCCP
12.2.2.2.2.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 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment
275 / 1392
12.2.2.2.2.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 yet
established.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
276 / 1392
12.2.2.2.2.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 from

the BSC to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
277 / 1392
12.2.2.2.2.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 interface

from the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
278 / 1392
12.3 Traffic Load

12.3.2 Interface
12.3.2.2 A
12.3.2.2.1 All A
279 / 1392
12.3.2.2.2 SCCP
12.3.2.2.2.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) is

sent from the BSC to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
280 / 1392
12.3.2.2.2.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) is

received from the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
281 / 1392
12.3.2.2.2.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 from

the BSC to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
282 / 1392
12.3.2.2.2.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 interface

from the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
283 / 1392
12.3.2.2.2.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 from

the BSC to the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
284 / 1392
12.3.2.2.2.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 interface

from the MSC.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
SCCP measurements
Type Definition
External Comment
285 / 1392
286 / 1392
13 BSC-TYPE 26 - TCH outgoing handover per adjacency measurements
13 BSC-TYPE 26 - TCH outgoing handover per adjacency

measurements
287 / 1392
13.1 All TYPE 26

C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT (Section 13.2.2.2.2.1 )
C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC (Section 13.2.2.2.2.2 )
C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV (Section
13.2.2.2.2.3 )
C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV (Section
13.2.2.2.2.4 )
C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT (Section
13.2.2.2.2.5 )
C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT (Section
13.2.2.2.2.6 )
C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT (Section
13.2.2.2.2.7 )
C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT (Section 13.2.2.2.2.8 )
13.2 Adjacency
13.2.1 All Adjacency
13.2.2.2.2.3 )
13.2.2.2.2.4 )
13.2.2.2.2.5 )
13.2.2.2.2.6 )
13.2.2.2.2.7 )
13.2.2 Fixed serving Cell

13.2.2.1 All Fixed serving Cell
13.2.2.2.2.3 )
13.2.2.2.2.4 )
13.2.2.2.2.5 )
288 / 1392

13.2.2.2.2.6 )
13.2.2.2.2.7 )
13.2.2.2
13.2.2.2.1 All
13.2.2.2.2
13.2.2.2.2.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 is
provided. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition
Whenever 44.018HANDOVER COMMAND is sent to the MS via the fixed

serving cell for an external or internal inter-cell TCH handover towards the
variable target cell. Note: This counter counts both inter-PLMN and intra-PLMN
handover 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.
External Comment
289 / 1392
13.2.2.2.2.2 C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC

Long Name
NB_ADJ_SCELL_OUT_TCH_HO_SUCC
Definition

handover successes. This counter takes into account handovers from TCH in
Trigger condition
1) Internal handover: whenever 44.018 HANDOVER_COMPLETE message

is received on Abis interface from the variable target cell during an internal
inter-cell TCH handover attempted from the fixed serving cell. 2) External
handover from the fixed serving cell to the 2G target cell in the following cases:
2a) 48.008 CLEAR COMMAND (cause = "handover successful") is received
at the serving BSC from the MSC. 2b) 48.008 CLEAR COMMAND (cause =
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
290 / 1392
13.2.2.2.2.3 C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV

Long Name
NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV
Definition

handover -execution failures due to MS access problem with reversion of the
mobile to the old channel. This counter takes into account handovers from
Trigger condition

interface from the fixed serving cell during an external or internal inter-cell TCH
handover attempted towards the variable 2G target cell. Note: This counter
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
291 / 1392
13.2.2.2.2.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

handover -execution failures due to MS access problem, without reversion of
the mobile to the old channel. This counter takes into account handovers from
Trigger condition
1) Internal handover: whenever the timer supervising the internal inter-cell TCH
handover procedure (T3103) from the fixed serving cell to the variable target cell
expires. 2) External handover: whenever the timer supervising the external TCH
handover procedure (T8) from the fixed serving cell to the variable target cell
expires, 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 a
case, the handover is considered as successful. Note: This counter counts both
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
292 / 1392
13.2.2.2.2.5 C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT

Long Name
NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT
Definition

handover attempts with emergency cause. This counter takes into account
Trigger condition
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is sent

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 variable target cell.
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
293 / 1392
13.2.2.2.2.6 C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT

Long Name
NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT
Definition

handover attempts with better cell cause. This counter takes into account
Trigger condition
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is

sent to the MS via the serving cell, for an outgoing handover cause 12, 14, 21
on a TCH channel, from the fixed serving cell to the variable target cell. Note:
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
294 / 1392
13.2.2.2.2.7 C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT

Long Name
NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT
Definition

handover attempts with traffic cause. This counter takes into account handovers
from TCH in traffic or in signaling mode.
Trigger condition
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is

sent to the MS via the serving cell, for an outgoing handover cause 23,24, 28 on
a TCH channel, from the fixed serving cell to the variable target cell. Note: This
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
295 / 1392
13.2.2.2.2.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 with

Forced directed retry cause.
Trigger condition
Whenever a 44.018 HANDOVER COMMAND message is sent to the MS for

an outgoing (external or internal) inter-cell directed retry Cause 20 from the
serving cell to a given target cell. Note: This counter counts both inter-PLMN
and intra-PLMN directed retry events.
Sub Domain 1
Fixed serving Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition
External Comment
296 / 1392
14 BSC-TYPE 27 - 2G TCH incoming handover per adjacency measurements
14 BSC-TYPE 27 - 2G TCH incoming handover per

adjacency measurements
297 / 1392
14.1 All TYPE 27

C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT (Section 14.2.2.2.2.1 )
C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC (Section 14.2.2.2.2.2 )
C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC (Section
14.2.2.2.2.3 )
C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT (Section
14.2.2.2.2.4 )
C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT (Section
14.2.2.2.2.5 )
C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT (Section 14.2.2.2.2.6
)
C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT (Section 14.2.2.2.2.7 )
C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT (Section 14.2.2.2.2.8 )
14.2 Adjacency
14.2.2.2.2.3 )
14.2.2.2.2.4 )
14.2.2.2.2.5 )
)
14.2.2 Fixed target Cell

14.2.2.1 All Fixed target Cell
14.2.2.2.2.3 )
14.2.2.2.2.4 )
14.2.2.2.2.5 )
)
298 / 1392
14.2.2.2
14.2.2.2.1 All
14.2.2.2.2
14.2.2.2.2.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 or

FR usage) handover attempts.
Trigger condition
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to the

MS via the variable serving cell for an internal inter-cell TCH handover towards
the fixed target cell. 2) External handover : whenever 48.008HANDOVER
REQUEST ACK is sent to the MSC from the target BSC for an external TCH
handover from the variable 2G serving cell towards the fixed target cell. The
Cell-identity of the serving and target cells is provided in the 48.008HANDOVER
REQUEST. Only handovers from a 2G cell shall be taken 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
Sub Domain 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
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 3G
are not counted in type 27).
External Comment
299 / 1392
14.2.2.2.2.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 FR

usage) handover successes.
Trigger condition
1) Whenever a 44.018 HANDOVER COMPLETE message is received on Abis

interface from the fixed target cell during an external or internal inter-cell TCH
handover attempted from the variable serving cell. Only handovers from a 2G
cell shall be taken 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 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
300 / 1392
14.2.2.2.2.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

usage) handover -execution failures due to MS access problem, with or without
reversion of the mobile to the old channel.
Trigger condition
1) Internal handover : - 44.018HANDOVER FAILURE (cause= "radio interface

failure, reversion to old channel") received from the variable serving cell during
an internal inter-cell TCH handover towards the fixed target cell. - T3103 expiry
2) External handover : - 48.058CONNECTION FAILURE INDICATION (cause=
"handover access failure") received on the new channel from the fixed target cell
- 48.008CLEAR COMMAND (cause= "radio interface failure, reversion to old
channel") received on the target BSC. Only handovers from a 2G cell shall be
taken 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:
Sub Domain 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
301 / 1392
14.2.2.2.2.4 C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT

Long Name
NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT
Definition

usage) handover attempts, with emergency cause.
Trigger condition
1) Internal inter-cell handover : whenever 44.018HANDOVER COMMAND

is sent to the MS via the variable serving cell for an internal inter-cell TCH
handover 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 to
the MSC from the target BSC for an external TCH handover from the variable
serving cell towards the fixed target cell. The Cell-identity of the serving and
target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause
2, 3, 4, 5, 6 Only handovers from a 2G cell shall be taken into account (if the
Sub Domain 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
302 / 1392
14.2.2.2.2.5 C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT

Long Name
NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT
Definition

usage) handover attempts, with better cell cause.
Trigger condition
1) Internal intercell handover : whenever 44.018HANDOVER COMMAND is sent

to the MS via the variable serving cell for an internal inter-cell TCH handover
towards the fixed target cell, with cause 12, 14, 21 2) External handover :
whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the
target BSC for an external TCH handover from the variable serving cell towards
the fixed target cell. The Cell-identity of the serving and target cells is provided
in the 48.008HANDOVER REQUEST with 48.008 cause 12 Only handovers
from a 2G cell shall be taken 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 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
303 / 1392
14.2.2.2.2.6 C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT

Long Name
NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT
Definition

usage) handover attempts, with traffic cause.
Trigger condition

the fixed target cell, with cause 23, 24, 28 2) External handover : whenever
48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC
for an external TCH handover from the variable serving cell towards the fixed
target cell. The Cell-identity of the serving and target cells is provided in the
48.008HANDOVER REQUEST with 48.008 cause 15. Only handovers from a
2G cell shall be taken 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 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
304 / 1392
14.2.2.2.2.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 retries

attempts, with Forced directed retry cause.
Trigger condition
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to

the MS via the variable serving cell for an internal inter-cell TCH handover
towards the fixed target cell, with cause 20 2) External handover : whenever
48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC
for an external TCH handover from the variable serving cell towards the fixed
target cell. The Cell-identity of the serving and target cells is provided in the
48.008HANDOVER REQUEST with 48.008 cause 13. Only handovers from a
handover events.
Sub Domain 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
305 / 1392
14.2.2.2.2.8 C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT

Long Name
NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT
Definition

usage) handover attempts, with unknown or missing cause.
Trigger condition

the fixed target cell, with unknown or missing cause. 2) External handover :
whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the
target BSC for an external TCH handover from the variable serving cell towards
the fixed target cell. The Cell-identity of the serving and target cells is provided
in 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
a 2G cell shall be taken into account (if the field Cell Identifier discriminator in
handover events.
Sub Domain 1
Fixed target Cell
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
306 / 1392
15 BSC-TYPE 28 - SDCCH handover
307 / 1392
15.1 All TYPE 28

C100 - NB_OUT_INT_SDCCH_HO_ATPT (Section 15.2.2.7.2.1 )
C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG (Section 15.2.2.5.2.1 )
C102 - NB_INTRA_SDCCH_HO_SUCC (Section 15.2.2.5.2.2 )
C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV (Section 15.2.2.5.2.3 )
C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV (Section 15.2.2.5.2.4 )
C115 - NB_SDCCH_HO_MSC_TRIG (Section 15.2.2.2.2.1 )
C310 - NB_INC_EXT_SDCCH_HO_REQ (Section 15.2.2.3.2.1 )
C311 - NB_INC_EXT_SDCCH_HO_ATPT (Section 15.2.2.3.2.2 )
C330 - NB_INC_INT_SDCCH_HO_REQ (Section 15.2.2.4.2.1 )
C331 - NB_INC_INT_SDCCH_HO_ATPT (Section 15.2.2.4.2.2 )
C360 - NB_INTRA_SDCCH_HO_REQ (Section 15.2.2.5.2.5 )
C361 - NB_INTRA_SDCCH_HO_ATPT (Section 15.2.2.5.2.6 )
C445 - NB_SDCCH_HO_ATPT_23_TrafHandover (Section 15.2.2.2.2.2 )
C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover (Section
15.2.2.2.2.3 )
C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance (Section 15.2.2.2.2.4 )
C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp (Section 15.2.2.2.2.5 )
C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp (Section 15.2.2.2.2.6 )
C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown (Section 15.2.2.2.2.7 )
C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown (Section 15.2.2.2.2.8 )
C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance (Section 15.2.2.2.2.9 )
C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp (Section 15.2.2.2.2.10
)
C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown (Section
15.2.2.2.2.11 )
C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg (Section 15.2.2.2.2.12 )
C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand (Section
15.2.2.2.2.13 )
C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell (Section
15.2.2.2.2.14 )
C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell (Section
15.2.2.2.2.15 )
C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell (Section
15.2.2.2.2.16 )
C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS (Section
15.2.2.2.2.17 )
C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR (Section
15.2.2.2.2.18 )
C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG (Section 15.2.2.3.2.3 )
C82 - NB_INC_EXT_SDCCH_HO_SUCC (Section 15.2.2.3.2.4 )
308 / 1392
C83 - NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS (Section

15.2.2.3.2.5 )
C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ (Section 15.2.2.6.2.1 )
C86 - NB_OUT_EXT_SDCCH_HO_SUCC (Section 15.2.2.6.2.2 )
C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV (Section 15.2.2.6.2.3 )
C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV (Section
15.2.2.6.2.4 )
C90 - NB_OUT_EXT_SDCCH_HO_ATPT (Section 15.2.2.6.2.5 )
C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG (Section 15.2.2.4.2.3 )
C92 - NB_INC_INT_SDCCH_HO_SUCC (Section 15.2.2.4.2.4 )
C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS (Section
15.2.2.4.2.5 )
C95a - NB_OUT_INT_SDCCH_HO_REQ (Section 15.2.2.7.2.2 )
C96 - NB_OUT_INT_SDCCH_HO_SUCC (Section 15.2.2.7.2.3 )
C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV (Section 15.2.2.7.2.4 )
C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV (Section 15.2.2.7.2.5
)
15.2 Handover
15.2.1 All Handover
15.2.2.2.2.3 )
309 / 1392

)
15.2.2.2.2.11 )
15.2.2.2.2.13 )
15.2.2.2.2.14 )
15.2.2.2.2.15 )
15.2.2.2.2.16 )
15.2.2.2.2.17 )
15.2.2.2.2.18 )
15.2.2.3.2.5 )
15.2.2.6.2.4 )
15.2.2.4.2.5 )
)
15.2.2 SDCCH
15.2.2.1 All SDCCH
310 / 1392

15.2.2.2.2.3 )
)
15.2.2.2.2.11 )
15.2.2.2.2.13 )
15.2.2.2.2.14 )
15.2.2.2.2.15 )
15.2.2.2.2.16 )
15.2.2.2.2.17 )
15.2.2.2.2.18 )
15.2.2.3.2.5 )
311 / 1392

15.2.2.6.2.4 )
15.2.2.4.2.5 )
)
15.2.2.2 Cause
15.2.2.2.1 All Cause
15.2.2.2.2.3 )
)
15.2.2.2.2.11 )
15.2.2.2.2.13 )
15.2.2.2.2.14 )
15.2.2.2.2.15 )
15.2.2.2.2.16 )
15.2.2.2.2.17 )
15.2.2.2.2.18 )
312 / 1392
15.2.2.2.2
15.2.2.2.2.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 A

interface from the MSC and timer T_HO_REQ_LOST is not running. Note: This
Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition
Set of counters related to SDCCH handover procedure.The counters are

External Comment
313 / 1392
15.2.2.2.2.2 C445 - NB_SDCCH_HO_ATPT_23_TrafHandover

Long Name
NB_SDCCH_HO_ATPT_23_TrafHandover
Definition
"traffic handover" on SDCCH. This counter counts also the directed retries.
Trigger condition

because of cause 23 on SDCCH. This counter is incremented in the serving cell.
Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
314 / 1392
15.2.2.2.2.3 C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover

Long Name
NB_SDCCH_HO_ATPT_24_GenCaptureHandover
Definition
"general capture handover" on SDCCH. This counter counts also the directed
retries.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
315 / 1392
15.2.2.2.2.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 cause

22: "too short MS-BTS distance". This cause is restricted to the extended
cells.This counter counts also the directed retries.
Trigger condition
Whenever 44.018 HANDOVER COMMAND is sent to the mobile via the BTS
Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
316 / 1392
15.2.2.2.2.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 triggered

with cause 2: "uplink quality too low".
Trigger condition

because of cause 2. This counter is incremented in the serving cell.
Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
317 / 1392
15.2.2.2.2.6 C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp

Long Name
NB_SDCCH_HO_ATPT_3_TooLowLevUp
Definition

3: "uplink level too low".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
318 / 1392
15.2.2.2.2.7 C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown

Long Name
NB_SDCCH_HO_ATPT_4_TooLowQualDown
Definition

4: "downlink quality too low".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
319 / 1392
15.2.2.2.2.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 triggered

with cause 5: "downlink level too low".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
320 / 1392
15.2.2.2.2.9 C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance

Long Name
NB_SDCCH_HO_ATPT_6_TooLongDistance
Definition

6: "MS-BTS distance too long".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
321 / 1392
15.2.2.2.2.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 level
interference on uplink".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
322 / 1392
15.2.2.2.2.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 level
interference on downlink".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
323 / 1392
15.2.2.2.2.12 C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg

Long Name
NB_SDCCH_HO_ATPT_12_TooLowPowBudg
Definition

12: "too low power budget".
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
324 / 1392
15.2.2.2.2.13 C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand

Long Name
NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand
Definition

21: "high level in neighbour cell in the preferred band". This counter is related
to multiband.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
325 / 1392
15.2.2.2.2.14 C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell

Long Name
NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell
Definition

7: "several consecutive bad SACCH frames received in a micro cell". This
counter is related to micro cell environment.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
326 / 1392
15.2.2.2.2.15 C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell

Long Name
NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell
Definition

17 "too low level on the uplink in a microcell compared to a high threshold". This
counter is related to micro cell environment.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
327 / 1392
15.2.2.2.2.16 C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell

Long Name
NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell
Definition

18: "too low level on the downlink in a microcell compared to a high threshold".
This counter is related to micro cell environment.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
328 / 1392
15.2.2.2.2.17 C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS

Long Name
NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS
Definition

14: "high level in neighbour lower layer cell for slow mobile". This counter is
related to micro cell environment.
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
329 / 1392
15.2.2.2.2.18 C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR

Long Name
NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR
Definition

20: "forced directed retry". This counter is related to a forced directed retry
(internal or external).
Trigger condition

Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
330 / 1392

15.2.2.3.2.5 )
15.2.2.3.2
15.2.2.3.2.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 target

cell on the SDCCH channel. Note: This counter counts both inter-PLMN and
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
331 / 1392
15.2.2.3.2.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 containing the

44.018HANDOVER COMMAND towards the target cell on the SDCCH channel.
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
332 / 1392
15.2.2.3.2.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 -preparation

Trigger condition

MSC during an external SDCCH handover. Note: This counter counts both
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
333 / 1392
15.2.2.3.2.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

interface from the target cell for an SDCCH Sub-channel that is involved in an
external SDCCH handover. Note: This counter counts both inter-PLMN and
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
334 / 1392
15.2.2.3.2.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 MS

access problem.
Trigger condition

cause value of "handover access failure" is received on Abis interface from the
target 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.008
CLEAR COMMAND with a cause value of "radio interface failure - reversion to
old channel" is received on A interface on the target BSC from the MSC during
an external SDCCH handover. Note: This counter counts both inter-PLMN and
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
335 / 1392

15.2.2.4.2.5 )
15.2.2.4.2
15.2.2.4.2.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
target cell (among a list of target cells) for internal inter cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
336 / 1392
15.2.2.4.2.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 internal
inter cell SDCCH handover. However, the counter is incremented in the TARGET
cell, based on the target cell ID indicated by the HO Command message,
Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
337 / 1392
15.2.2.4.2.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

Trigger condition
Whenever a internal inter-cell SDCCH handover cannot be performed, because

there is no free SDCCH Sub-channel to allocate the handover to.
Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
338 / 1392
15.2.2.4.2.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

interface from the target cell during an internal inter-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
339 / 1392
15.2.2.4.2.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 failures

due to MS access problem.
Trigger condition
1) Whenever the timer supervising the handover procedure (T3103) expires

during an internal inter-cell SDCCH handover. 2) Whenever a HANDOVER
FAILURE message is received on Abis interface from the serving cell during and
internal inter-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
340 / 1392
15.2.2.5 Intra
15.2.2.5.1 All Intra
15.2.2.5.2
15.2.2.5.2.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 due

to congestion.
Trigger condition
Whenever a internal intra-cell SDCCH handover cannot be performed, because

Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
341 / 1392
15.2.2.5.2.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 target

channel during an internal intra-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
342 / 1392
15.2.2.5.2.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 access

problem without reversion to the old channel.
Trigger condition
Whenever the timer supervising the internal intra-cell SDCCH handover

procedure (T3107) expires.
Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
343 / 1392
15.2.2.5.2.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 access

problem with reversion to the old channel.
Trigger condition
Whenever a 44.018 ASSIGNMENT FAILURE message is received on the

Serving Sub-channel, during an internal intra-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
344 / 1392
15.2.2.5.2.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 an
intra cell SDCCH handover procedure.
Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
345 / 1392
15.2.2.5.2.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 cell
handover on SDCCH.
Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
346 / 1392

15.2.2.6.2.4 )
15.2.2.6.2
15.2.2.6.2.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 interface

to the MSC for a SDCCH handover. If more than one 48.008 HANDOVER
REQUIRED is sent in the frame of the same Handover procedure, the counter is
incremented only once. 48.008 HANDOVER REQUIRED is sent in following
situations : 1) An external handover alarm has been raised, with corresponding
list of candidate cells. 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
SDCCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
347 / 1392
15.2.2.6.2.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 CLEAR

COMMAND message with a cause of "handover successful" is received on A
interface on the serving BSC from the MSC. 2/ 48.008 CLEAR COMMAND
(cause= "normal event/call control") received while T8 is running. Note: This
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
348 / 1392
15.2.2.6.2.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 MS

access problem with reversion to the old channel.
Trigger condition
Whenever a HANDOVER FAILURE message is received on Abis interface from

the serving cell, during an external SDCCH handover. Note: This counter
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
349 / 1392
15.2.2.6.2.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 MS

access problem without reversion to the old channel.
Trigger condition
(T8), expires during an external SDCCH handover, 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 a case, the handover is considered
as successful. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
350 / 1392
15.2.2.6.2.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

interface on the serving channel, during an external SDCCH handover
procedure. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
351 / 1392

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

interface to the mobile via the serving cell, during an internal inter-cell SDCCH
handover procedure.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
352 / 1392
15.2.2.7.2.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
target cell (among a list of target cells) for internal inter cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
353 / 1392
15.2.2.7.2.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

interface from the target cell, during an internal inter-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
354 / 1392
15.2.2.7.2.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 to

MS access problem with reversion to the old channel.
Trigger condition
Whenever a HANDOVER FAILURE message is received on Abis interface from

the serving cell, during an internal inter-cell SDCCH handover.
Sub Domain 1
SDCCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
355 / 1392
15.2.2.7.2.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 to

MS 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 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
SDCCH handover
Type Definition

External Comment
356 / 1392
16 BSC-TYPE 29 - Directed retry measurements
357 / 1392
16.1 All TYPE 29

C142a - NB_OUT_FORCED_IDR_SUCC (Section 16.2.2.3.3.1 )
C142b - NB_OUT_FORCED_EDR_SUCC (Section 16.2.2.2.2.1 )
C142c - NB_OUT_NOR_IDR_SUCC (Section 16.2.2.3.3.2 )
C142d - NB_OUT_NOR_EDR_SUCC (Section 16.2.2.2.2.2 )
C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV (Section 16.2.2.3.3.3 )
C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV (Section 16.2.2.3.3.4
)
C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV (Section 16.2.2.2.2.3 )
C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV (Section
16.2.2.2.2.4 )
C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV (Section 16.2.2.3.3.5 )
C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV (Section 16.2.2.3.3.6 )
C143g - NB_OUT_NOR_EDR_EXEC_FAIL_REV (Section 16.2.2.2.2.5 )
C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV (Section 16.2.2.2.2.6 )
C144a - NB_OUT_FORCED_IDR_REQ (Section 16.2.2.3.3.7 )
C144b - NB_OUT_FORCED_EDR_REQ (Section 16.2.2.2.2.7 )
C144c - NB_OUT_NOR_IDR_REQ (Section 16.2.2.3.3.8 )
C144d - NB_OUT_NOR_EDR_REQ (Section 16.2.2.2.2.8 )
C145a - NB_OUT_FORCED_IDR_ATPT (Section 16.2.2.3.3.9 )
C145b - NB_OUT_FORCED_EDR_ATPT (Section 16.2.2.2.2.9 )
C145c - NB_OUT_NOR_IDR_ATPT (Section 16.2.2.3.3.10 )
C145d - NB_OUT_NOR_EDR_ATPT (Section 16.2.2.2.2.10 )
C151 - NB_INC_IDR_SUCC (29) (Section 16.2.2.3.2.1 )
C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS (Section 16.2.2.3.2.2 )
C153 - NB_INC_IDR_REQ (Section 16.2.2.3.2.3 )
C154 - NB_INC_IDR_ATPT (Section 16.2.2.3.2.4 )
C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS (Section 16.2.2.3.2.5 )
16.2 Handover
16.2.1 All Handover
)
358 / 1392

16.2.2.2.2.4 )

)
16.2.2.2.2.4 )
359 / 1392

16.2.2.2 External
16.2.2.2.1 All External
16.2.2.2.2.4 )
360 / 1392
16.2.2.2.2 Outgoing
16.2.2.2.2.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 in

HR or FR usage) successes.
Trigger condition
Forced external directed retry in the following cases: 1/ 48.008CLEAR

COMMAND (cause = "handover successful") is received on the serving BSC
2/ 48.008 CLEAR COMMAND (cause = "normal event/call control") received
while T8 is running. Note: This counter counts both inter-PLMN and intra-PLMN
directed retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Directed retry measurements
Type Definition
Set of counters related to the directed retry procedure. The counters are
provided per directed retry category : incoming and outgoing, internal and
external, forced and normal.
External Comment
361 / 1392
16.2.2.2.2.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 in

Trigger condition
Normal external directed retry in the following cases: 1/ 48.008 CLEAR

COMMAND (cause = "handover successful") is received on the serving BSC
2/ 48.008 CLEAR COMMAND (cause = "normal event/call control") received
while T8 is running. Note: This counter counts both inter-PLMN and intra-PLMN
directed retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
362 / 1392
16.2.2.2.2.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 MS

access problem with reversion to the old channel. The target TCH channel
can be in HR or FR usage.
Trigger condition
Whenever 44.018 HANDOVER FAILURE is received from the MS via the

serving cell on the old channel (SDCCH). Note: This counter counts both
inter-PLMN and intra-PLMN directed retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
363 / 1392
16.2.2.2.2.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 MS

access problem without reversion to the old channel. The target TCH channel
Trigger condition
a forced external directed retry, 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 a case, the directed retry is considered as
successful. Note: This counter counts both inter-PLMN and intra-PLMN directed
retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
364 / 1392
16.2.2.2.2.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 MS

Trigger condition
Whenever 44.018 HANDOVER FAILURE is received from the MS via the

serving cell on the old channel (SDCCH). Note: This counter counts both
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
365 / 1392
16.2.2.2.2.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 MS

Trigger condition
a normal external directed retry, 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 a case, the directed retry is considered as
successful. Note: This counter counts both inter-PLMN and intra-PLMN directed
retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
366 / 1392
16.2.2.2.2.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 TCH
channel can be in HR or FR usage.
Trigger condition
Whenever the BSC process responsible for handover procedure starts a forced
external directed retry from the serving cell. Note: This counter counts both
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
367 / 1392
16.2.2.2.2.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 TCH
Trigger condition
Whenever the BSC process responsible for handover procedure starts a normal
external directed retry from the serving cell. Note: This counter counts both
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
368 / 1392
16.2.2.2.2.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 TCH
Trigger condition
Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving

cell on the SDCCH channel for a forced external directed retry. Note: This
counter counts both inter-PLMN and intra-PLMN directed retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
369 / 1392
16.2.2.2.2.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 TCH
Trigger condition

cell on the SDCCH channel for a normal external directed retry. Note: This
counter counts both inter-PLMN and intra-PLMN directed retry events.
Sub Domain 1
Directed Retry
Sub Domain 2
External
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
370 / 1392
16.2.2.3 Internal
)
16.2.2.3.2 Incoming
16.2.2.3.2.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 TCH

channel in HR or FR usage) successes.
Trigger condition
Whenever 44.018HANDOVER COMPLETE is received from the MS via the

target cell, for a forced or internal internal directed retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
371 / 1392
16.2.2.3.2.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 failures

due 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 the

serving cell 2) timer T3103 expiry (this timer supervizes the 44.018HANDOVER
COMMAND)
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
372 / 1392
16.2.2.3.2.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 the
target cell for forced or normal internal directed retry.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
373 / 1392
16.2.2.3.2.4 C154 - NB_INC_IDR_ATPT

Long Name
NB_INC_IDR_ATPT
Definition
Number of incoming internal directed retry (forced or normal) attempts. The

target TCH channel can be in HR or FR usage.
Trigger condition

cell on the SDCCH. However, the counter is incremented in the TARGET cell,
based on the target cell ID indicated by the HO Command message,
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
374 / 1392
16.2.2.3.2.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) -preparation

failures due to congestion (on Air or A-bis interface). The target TCH channel
Trigger condition
1) Whenever there are no free TCH in the target cell during a forced or normal
internal directed retry. 2) Whenever no TCH resource is available on A-bis
interface for a forced or normal internal directed retry. (not valid in B7). Note 1:
In MX BSC, this counter is incremented whenever a TCH cannot be not allocated
due to the TCH processing capacity of CCP reaches the limit defined by the
MAX_TCH_PER_CCP parameter. In this case, MC926 is also incremented by
one. Note 2: In IP mode, this counter is increased by 1 if: - the cell mapped
on a BTS is in IP congestion status; - or the TCH processing capacity of
AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TS
parameter
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
375 / 1392
16.2.2.3.3 Outgoing
16.2.2.3.3.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 in

Trigger condition

target cell, for a forced internal directed retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
376 / 1392
16.2.2.3.3.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 in

Trigger condition

target cell, for a normal internal directed retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
377 / 1392
16.2.2.3.3.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 MS

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

cell.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
378 / 1392
16.2.2.3.3.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 MS

Trigger condition
Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
379 / 1392
16.2.2.3.3.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 MS

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

cell.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
380 / 1392
16.2.2.3.3.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 MS

Trigger condition
Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
381 / 1392
16.2.2.3.3.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 in

HR or FR usage) requests.
Trigger condition
Whenever the BSC process responsible for handover procedure initiates a

forced internal directed retry from the serving cell.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
382 / 1392
16.2.2.3.3.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 TCH
Trigger condition
Whenever the BSC process responsible for handover procedure initiates a

normal internal directed retry from the serving cell.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
383 / 1392
16.2.2.3.3.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 TCH
Trigger condition

cell on the SDCCH channel for a forced internal directed retry.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
384 / 1392
16.2.2.3.3.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 TCH
Trigger condition

cell on the SDCCH channel for a normal internal directed retry.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Outgoing
Measured Object
Common cell
Type Name
Type Definition
External Comment
385 / 1392
386 / 1392
17 BSC-TYPE 30 - SMS CB measurements
387 / 1392
17.1 All TYPE 30

CB601 - NB_SMSCB_WRITE_REPL_SUCC (Section 17.3.2.2.2.1 )
CB602 - NB_SMSCB_KILL_MESS_SUCC (Section 17.3.2.2.2.2 )
CB603 - NB_SMS_CB_FAIL_IND (Section 17.2.2.2.2.1 )
CB604 - NB_SMS_CB_WRITE_REP_KILL_MESS_REJ (Section 17.2.2.2.2.2 )


17.2.2.2 Cell Broadcast

17.2.2.2.1 All Cell Broadcast
17.2.2.2.2 Failure
17.2.2.2.2.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 implicated
by the failure. The BSC detects a failure and request the CBC (by the FAILURE
INDICATION 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 is

incremented by the Cell-List mandatory IE.
Sub Domain 1
Sub Domain 2
Cell Broadcast
Sub Domain 3
Failure
Measured Object
BSC
Type Name
SMS CB measurements
Type Definition
Set of counters related to the Short Message Service Cell Broadcast.
External Comment
388 / 1392
17.2.2.2.2.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.

A WRITE REPLACE or a KILL MESSAGE request coming from the CBC is
received by the BSC. This request is 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 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
reject is the same for all cells, otherwise a REPORT SUCCESS is returned.
When a REPORT SUCCESS is returned, the Failure-List optional Information
Element specifies for each cell whose request has not been completed, the
cause and diagnostic of the failure.
Trigger condition
1) Whenever a WRITE REPLACE or a KILL MESSAGE request is totally

rejected by REPORT FAILURE (then, for all cells with the same cause), the
counter is incremented by the Cell-List IE value provided within the request
message. 2) Whenever a REPORT SUCCESS to a WRITE REPLACE or a KILL
MESSAGE request is returned to the CBC, the counter is incremented by the
number of cells provided within the Failure-List IE of the REPORT SUCCESS.
Sub Domain 1
Sub Domain 2
Cell Broadcast
Sub Domain 3
Failure
Measured Object
BSC
Type Name
SMS CB measurements
Type Definition
External Comment
389 / 1392
17.3 Traffic Load


17.3.2.2 Short Message Service

17.3.2.2.1 All Short Message Service
17.3.2.2.2 Cell Broadcast

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

REPLACE request coming from the CBC is received by the BSC. This request
is 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 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 reject is the same for all cells, otherwise
a REPORT SUCCESS is returned. When a REPORT SUCCESS is returned,
the No-of-Broadcasts-completed-list optional Information Element specifies the
number of cells successfully served by the request. This IE is not provided
when 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 cells
are served).
Sub Domain 1
Sub Domain 2
Sub Domain 3
Cell Broadcast
Measured Object
BSC
Type Name
SMS CB measurements
Type Definition
External Comment
390 / 1392
17.3.2.2.2.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 MESSAGE

request coming from the CBC is received by the BSC. This request is 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 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 reject is the same for all cells, otherwise a
REPORT SUCCESS is returned. When a REPORT SUCCESS is returned, the
No-of-Broadcasts-completed-list optional Information Element specifies the
number of cells successfully served by the request. This IE is not provided
when no cells can be served.
Trigger condition
Whenever a REPORT SUCCESS to a KILL MESSAGE 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 cells are
served).
Sub Domain 1
Sub Domain 2
Sub Domain 3
Cell Broadcast
Measured Object
BSC
Type Name
SMS CB measurements
Type Definition
External Comment
391 / 1392
392 / 1392
18 BSC-TYPE 31 - Radio Measurement Statistics
393 / 1392
18.1 All TYPE 31

RMS10 - VQ_NOISY_UL_INTERFERENCE (Section 18.2.2.2.2.1 )
RMS11 - VQ_NOISY_DL_INTERFERENCE (Section 18.2.2.2.2.2 )
RMS12 - VQ_NOISY_UL_COVERAGE (Section 18.2.2.2.2.3 )
RMS13 - VQ_NOISY_DL_COVERAGE (Section 18.2.2.2.2.4 )
RMS14 - VQ_NOISY_UL_UNDEFINED (Section 18.2.2.2.2.5 )
RMS15 - VQ_NOISY_DL_UNDEFINED (Section 18.2.2.2.2.6 )
RMS16 - VQ_NOISY_UL_BAD_FER (Section 18.2.2.2.2.7 )
RMS17 - VQ_NOISY_UL_GOOD_FER (Section 18.2.2.2.2.8 )
RMS18 - VQ_ABNORMAL_BAD_FER (Section 18.2.2.2.2.9 )
RMS31 - TOT_SEIZ_TCH (Section 18.3.2.2.2.1 )
RMS32 - TOT_MEAS (Section 18.2.2.2.2.10 )
RMS33 - TOT_MEAS_L1INFO_NOL3INFO (Section 18.2.2.2.2.11 )
RMS34 - TOT_MEAS_DTX_UL (Section 18.2.2.2.2.12 )
RMS35 - TOT_MEAS_DTX_DL (Section 18.2.2.2.2.13 )
RMS36 - PERC_TA_GT_TA_STAT (Section 18.2.2.2.2.14 )
RMS38 - TOT_EMR (Section 18.2.2.2.2.15 )
RMS3a - TPR_RXQUAL_UL_RXLEV_UL (Section 18.2.2.2.2.16 )
RMS3b - TMR_RXQUAL_UL_RXLEV_UL (Section 18.2.2.2.2.17 )
RMS41a - AMR_WB_GMSK_FR_UL_BAD (Section 18.2.2.2.2.18 )
RMS41b - MAX_AMR_WB_GMSK_FR_UL_BAD (Section 18.2.2.2.2.19 )
RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL (Section 18.2.2.2.2.20 )
RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL (Section 18.2.2.2.2.21
)
RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL (Section 18.2.2.2.2.22 )
RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL (Section 18.2.2.2.2.23
)
RMS44a - AMR_FR_UL_BAD (Section 18.2.2.2.2.24 )
RMS44b - MAX_AMR_FR_UL_BAD (Section 18.2.2.2.2.25 )
RMS45a - AMR_HR_UL_BAD (Section 18.2.2.2.2.26 )
RMS45b - MAX_AMR_HR_UL_BAD (Section 18.2.2.2.2.27 )
RMS46a - AMR_FR_UL_RXLEV_UL (Section 18.2.2.2.2.28 )
RMS46b - MAX_AMR_FR_UL_RXLEV_UL (Section 18.2.2.2.2.29 )
RMS47a - AMR_FR_DL_RXLEV_DL (Section 18.2.2.2.2.30 )
RMS47b - MAX_AMR_FR_DL_RXLEV_DL (Section 18.2.2.2.2.31 )
RMS48a - AMR_HR_UL_RXLEV_UL (Section 18.2.2.2.2.32 )
RMS48b - MAX_AMR_HR_UL_RXLEV_UL (Section 18.2.3.2.2.1 )
RMS49a - AMR_HR_DL_RXLEV_DL (Section 18.2.2.2.2.33 )
RMS49b - MAX_AMR_HR_DL_RXLEV_DL (Section 18.2.2.2.2.34 )
394 / 1392
RMS4a - TPR_RXQUAL_DL_RXLEV_DL (Section 18.2.2.2.2.35 )

RMS4b - TMR_RXQUAL_DL_RXLEV_DL (Section 18.2.2.2.2.36 )
RMS50a - TPR_TIMING_ADVANCE (Section 18.2.2.2.2.37 )
RMS50b - MAX_TIMING_ADVANCE (Section 18.2.2.2.2.38 )
RMS51 - TPR_UL_RXLEV_TA_BAND (Section 18.2.2.2.2.39 )
RMS52 - TPR_DL_RXLEV_TA_BAND (Section 18.2.2.2.2.40 )
RMS53 - TPR_UL_RXQUAL_TA_BAND (Section 18.2.2.2.2.41 )
RMS54 - TPR_DL_RXQUAL_TA_BAND (Section 18.2.2.2.2.42 )
RMS5a - TPR_BFI_RXLEV_UL (Section 18.2.2.2.2.43 )
RMS5b - TMR_BFI_RXLEV_UL (Section 18.2.2.2.2.44 )
RMS6a - TPR_RADIO_LINK (Section 18.2.2.2.2.45 )
RMS6b - MAX_RADIO_LINK (Section 18.2.2.2.2.46 )
RMS7a - TPR_PATH_BALANCE (Section 18.2.2.2.2.47 )
RMS7b - MAX_PATH_BALANCE (Section 18.2.2.2.2.48 )
RMS8a - TPR_CIN (Section 18.2.2.2.2.49 )
RMS8b - MR_CIN (Section 18.2.2.2.2.50 )
RMS9a - TPR_CIF (Section 18.2.2.2.2.51 )
RMS9b - MR_CIF (Section 18.2.2.2.2.52 )
RMSPw3 - MAX_POWER_PER_TRX (Section 18.2.2.2.2.53 )

395 / 1392

)
)
396 / 1392
18.2.2 RMS
18.2.2.1 All RMS
)
)
397 / 1392

398 / 1392
18.2.2.2
18.2.2.2.1 All
18.2.2.2.2
18.2.2.2.2.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_THRESHOLD This calculation is done
when 48.058 RF CHANNEL RELEASE is received for the observed call.
INTERFERED_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ >
VQ_RXQUAL and AV_RXLEV_UL_VQ>VQ_RXLEV AV_RXQUAL_UL_VQ :
average on VQ_AVERAGE measurements of RXQUAL_UL AV_RXLEV_UL_VQ
: average on VQ_AVERAGE measurements of RXLEV_UL NUM_UL_SAMPLES
: total number of averages calculated on UL measurements during the call on
the 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.
External Comment
399 / 1392
18.2.2.2.2.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_THRESHOLD This calculation is done
INTERFERED_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ >
VQ_RXQUAL and AV_RXLEV_DL_VQ>VQ_RXLEV AV_RXQUAL_DL_VQ :
average on VQ_AVERAGE measurements of RXQUAL_DL AV_RXLEV_DL_VQ
: average on VQ_AVERAGE measurements of RXLEV_DL NUM_DL_SAMPLES
: total number of averages calculated on DL measurements during the call on
the considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
400 / 1392
18.2.2.2.2.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_THRESHOLD This calculation is done
BAD_COVERAGE_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ >
VQ_RXQUAL and AV_RXLEV_UL_VQ<=VQ_RXLEV AV_RXQUAL_UL_VQ :
average on VQ_AVERAGE measurements of RXQUAL_UL AV_RXLEV_UL_VQ
: average on VQ_AVERAGE measurements of RXLEV_UL NUM_UL_SAMPLES
the considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
401 / 1392
18.2.2.2.2.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_THRESHOLD This calculation is done
BAD_COVERAGE_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ >
VQ_RXQUAL and AV_RXLEV_DL_VQ<=VQ_RXLEV AV_RXQUAL_DL_VQ :
average on VQ_AVERAGE measurements of RXQUAL_DL AV_RXLEV_DL_VQ
: average on VQ_AVERAGE measurements of RXLEV_DL NUM_DL_SAMPLES
the considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
402 / 1392
18.2.2.2.2.5 RMS14 - VQ_NOISY_UL_UNDEFINED

Long Name
VQ_NOISY_UL_UNDEFINED
Definition
Number of calls suffering from both problem of interference and bad coverage
on the uplink path. These calls are not counted in VQ_NOISY_UL_COVERAGE
or VQ_NOISY_UL_INTERFERENCE.
Trigger condition
Whenever a call verifies : 100*(BAD_COVERAGE_UL_SAMPLES

/ NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLD and
100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) <=
VQ_INTF_THRESHOLD and 100*(BAD_QUALITY_UL_SAMPLES
/ NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD This calculation
is done when 48.058 RF CHANNEL RELEASE is received
for the observed call. BAD_COVERAGE_UL_SAMPLES =
nb of times where AV_RXQUAL_UL_VQ > VQ_RXQUAL and
AV_RXLEV_UL_VQ<=VQ_RXLEV INTERFERED_UL_SAMPLES = nb of
times when AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ >
VQ_RXLEV BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES +
BAD_COVERAGE_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ
> VQ_RXQUAL AV_RXQUAL_UL_VQ : average on VQ_AVERAGE
measurements of RXQUAL_UL AV_RXLEV_UL_VQ : average on
VQ_AVERAGE measurements of RXLEV_UL NUM_UL_SAMPLES : total
number of averages calculated on UL measurements during the call on the
considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
403 / 1392
18.2.2.2.2.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 on
the downlink path. These calls are not counted in VQ_NOISY_DL_COVERAGE
or VQ_NOISY_DL_INTERFERENCE.
Trigger condition
Whenever a call verifies : 100*(BAD_COVERAGE_DL_SAMPLES

/ NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD and
100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) <=
VQ_INTF_THRESHOLD and 100*(BAD_QUALITY_DL_SAMPLES
/ NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD This calculation
is done when 48.058 RF CHANNEL RELEASE is received
for the observed call. BAD_COVERAGE_DL_SAMPLES =
nb of times where AV_RXQUAL_DL_VQ > VQ_RXQUAL and
AV_RXLEV_DL_VQ<=VQ_RXLEV INTERFERED_DL_SAMPLES = nb of
times when AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ >
VQ_RXLEV BAD_QUALITY_DL_SAMPLES = INTERFERED_DL_SAMPLES +
BAD_COVERAGE_DL_SAMPLES = nb of times when AV_RXQUAL_DL_VQ
> VQ_RXQUAL AV_RXQUAL_DL_VQ : average on VQ_AVERAGE
measurements of RXQUAL_DL AV_RXLEV_DL_VQ : average on
VQ_AVERAGE measurements of RXLEV_DL NUM_DL_SAMPLES : total
number of averages calculated on DL measurements during the call on the
considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
404 / 1392
18.2.2.2.2.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 FER
measurements on the uplink path.
Trigger condition
Whenever a call verifies : 100*(BAD_QUALITY_UL_SAMPLES

/ NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD and
100*(BAD_QUAL_BAD_FER_UL_SAMPLES / BAD_QUALITY_UL_SAMPLES)
> VQ_FER_THRESHOLD This calculation is done when 48.058 RF
CHANNEL RELEASE is received for the observed 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 when
AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER and AV_RXFER_UL_VQ
> VQ_BAD_RXFER * AV_RXQUAL_UL_VQ : average on VQ_AVERAGE
measurements of RXQUAL_UL * AV_RXLEV_UL_VQ : average on
VQ_AVERAGE measurements of RXLEV_UL * NUM_UL_SAMPLES : total
considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
405 / 1392
18.2.2.2.2.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 FER
measurements on the uplink path.
Trigger condition
Whenever a call verifies : 100*(BAD_QUALITY_UL_SAMPLES

/ NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
and 100*(BAD_QUAL_GOOD_FER_UL_SAMPLES /
BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD This calculation
is done when 48.058 RF CHANNEL RELEASE is received for the observed
call. BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES +
BAD_COVERAGE_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ >
VQ_RXQUAL BAD_QUAL_GOOD_FER_UL_SAMPLES = nb of times when
AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER and AV_RXFER_UL_VQ
<= VQ_GOOD_RXFER AV_RXQUAL_UL_VQ : average on VQ_AVERAGE
measurements of RXQUAL_UL AV_RXFER_UL_VQ : average on
VQ_AVERAGE measurements of FER_UL NUM_UL_SAMPLES : total
considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
406 / 1392
18.2.2.2.2.9 RMS18 - VQ_ABNORMAL_BAD_FER

Long Name
VQ_ABNORMAL_BAD_FER
Definition
Number of calls with fair quality measurements but with bad FER measurements
on the uplink path.
Trigger condition
Whenever a call verifies : 100*(FAIR_QUAL_BAD_FER_UL_SAMPLES

/ FAIR_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD This
calculation is done when 48.058 RF CHANNEL RELEASE is received
for the observed call. FAIR_QUAL_BAD_FER_UL_SAMPLES = nb
of times when AV_RXQUAL_UL_VQ<VQ_RXQUAL_VS_RXFER and
AV_RXFER_UL_VQ>VQ_BAD_RXFER AV_RXQUAL_UL_VQ : average on
VQ_AVERAGE measurements of RXQUAL_UL AV_RXFER_UL_VQ : average
on VQ_AVERAGE measurements of FER_UL NUM_UL_SAMPLES : total
considered TRX
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
407 / 1392
18.2.2.2.2.10 RMS32 - TOT_MEAS

Long Name
TOT_MEAS
Definition
Number of MEASUREMENT RESULTS messages sent and used for RMS

computation 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
Type Name
Type Definition
External Comment
408 / 1392
18.2.2.2.2.11 RMS33 - TOT_MEAS_L1INFO_NOL3INFO

Long Name
TOT_MEAS_L1INFO_NOL3INFO
Definition
Number of MEASUREMENT RESULTS messages sent without Layer 3

information but with Layer 1 present. The result is first calculated by the BTS at
a TRX level, then compilated by the BSC at a cell level. This counter reflects the
uplink quality, it is incremented due to bad uplink radio quality or long handover
interruptions.
Trigger condition
Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS

without 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
Type Name
Type Definition
External Comment
409 / 1392
18.2.2.2.2.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 the
uplink path.
Trigger condition

with DTX_UL=1, used for RMS.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
410 / 1392
18.2.2.2.2.13 RMS35 - TOT_MEAS_DTX_DL

Long Name
TOT_MEAS_DTX_DL
Definition
Number of measurement results indicating that DTX is used on the downlink

path, used for RMS.
Trigger condition

with DTX_UL=1, and used for RMS.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
411 / 1392
18.2.2.2.2.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 Edge
capable TRX)
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
412 / 1392
18.2.2.2.2.15 RMS38 - TOT_EMR

Long Name
TOT_EMR
Definition
Total number of Extended Measurement Results.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
413 / 1392
18.2.2.2.2.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
reports in which UL RXQUAL is equal to j and UL RXLEV is reported in level
band i (Cij) 2) corresponding averaged value of MS power level 3) corresponding
averaged value of Timing Advance For Cij, the result is given as follows : Cij=Vij
x 254 / Max_i, where Vij represents the real number of measurements, and
Max_i the greatest value of Vij, for i given (see RMS3b). Cij=0 indicates number
of measurements = 0 Cij=254 indicates number of measurements = Max_i
Cij=255 is 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
precision of 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
by 4, whereas the values that are provided at the user interface are the correct
ones. UL RXQUAL can take values from 0 to 7. Level band i is defined by :
MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_i MEAS_STAT_LEV_0
= -47 dBm, MEAS_STAT_LEV_10 = -110 dBm According to 3GPP, values of
RXLEV 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
Type Name
Type Definition
External Comment
414 / 1392
18.2.2.2.2.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 greatest
value of the Vij for a i given in RMS3a.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
415 / 1392
18.2.2.2.2.18 RMS41a - AMR_WB_GMSK_FR_UL_BAD

Long Name
AMR_WB_GMSK_FR_UL_BAD
Definition
Table of 3 results Each cell (i) of the table contains: number of FR AMR
WB GMSK UL bad 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 the greatest value of Vi (see RMS41b). - Ci=0 indicates
number of measurements = 0 - Ci=254 indicates number of measurements =
Max - Ci=255 is 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 codec
the number of bad speech frames received from the MS (or sent to the TC) in
uplink. 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
Type Name
Type Definition
External Comment
This counter is only reported for cells mapped on Evolium BTS.
416 / 1392
18.2.2.2.2.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.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
417 / 1392
18.2.2.2.2.20 RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL

Long Name
AMR_WB_GMSK _FR_UL_RXLEV_UL
Definition
Table of 3x10 results Each cell (i,k) of the table contains: 1) number of correct
UL speech frames using FR AMR WB GMSK codec k for which UL RXLEV is
reported in level band 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 greatest value of Vik, for i given (see RMS42b). - Cik=0
indicates number of measurements = 0 - Cik=254 indicates number of
measurements = Max_i - Cik=255 is reserved to indicate overflow. Level band
i is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_I j = i 1
MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBm 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. According 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 FR AMR WB
GMSK call and for each FR AMR WB GMSK codec the number of correct
speech frames received from the MS (or sent to the TRAU) in uplink. To insure
consistency of the results, only speech frames of type "Speech_Good" or
"SID_Update" shall be taken into account. At reception of the measurement
report of a given MS, the results are gathered in the line of the matrix
corresponding to reported UL RXLEV.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
418 / 1392
18.2.2.2.2.21 RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL

Long Name
MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL
Definition
value of the Vik for a i given in RMS42a.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
419 / 1392
18.2.2.2.2.22 RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL

Long Name
AMR_WB_GMSK_FR_DL_RXLEV_DL
Definition
Table of 3x10 results Each cell (i,k) of the table contains : 1) number of correct
DL speech frames using FR AMR WB GMSK codec k for which DL RXLEV is
reported in level band 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 greatest value of Vik, for i given (see RMS43b). Cik=0
indicates number of measurements = 0 Cik=254 indicates number of
measurements = Max_i Cik=255 is reserved to indicate overflow. Level band i
is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_i j = i - 1
MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBm 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. According 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 FR AMR WB
call and for each FR AMR WB codec the number of correct speech frames
received from the TC (or sent to the MS) in downlink. To insure consistency of
the results, only speech frames of type "Speech_Good" or "SID_Update" shall
be taken into account. At reception of the measurement report of a given MS,
the results are gathered in the line of the matrix
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
420 / 1392
18.2.2.2.2.23 RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL

Long Name
MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
421 / 1392
18.2.2.2.2.24 RMS44a - AMR_FR_UL_BAD

Long Name
AMR_FR_UL_BAD
Definition
Table of 8 results Each cell (i) of the table contains : number of AMR FR UL
bad 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 the
greatest value of Vi (see RMS44b). Ci=0 indicates number of measurements
= 0 Ci=254 indicates number of measurements = Max Ci=255 is reserved to
indicate overflow. AMR FR 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,
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 number
of bad speech frames received from the MS (or sent to the TC) in uplink. 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
Type Name
Type Definition
External Comment
422 / 1392
18.2.2.2.2.25 RMS44b - MAX_AMR_FR_UL_BAD

Long Name
MAX_AMR_FR_UL_BAD
Definition
Greatest value of the Vi in RM44a.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
423 / 1392
18.2.2.2.2.26 RMS45a - AMR_HR_UL_BAD

Long Name
AMR_HR_UL_BAD
Definition
Table of 5 results Each cell (i) of the table contains : number of AMR HR UL
bad 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 the
greatest value of Vi (see RMS45b). Ci=0 indicates number of measurements
= 0 Ci=254 indicates number of measurements = Max Ci=255 is reserved to
indicate 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 number
of bad speech frames received from the MS (or sent to the TC) in uplink. 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
Type Name
Type Definition
External Comment
424 / 1392
18.2.2.2.2.27 RMS45b - MAX_AMR_HR_UL_BAD

Long Name
MAX_AMR_HR_UL_BAD
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
425 / 1392
18.2.2.2.2.28 RMS46a - AMR_FR_UL_RXLEV_UL

Long Name
AMR_FR_UL_RXLEV_UL
Definition
UL speech frames using AMR FR codec k for which UL RXLEV is reported
in level band 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 greatest value 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 to indicate overflow. Level band i is defined by :
= -47 dBm, MEAS_STAT_LEV_10 = -110 dBm AMR FR 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, codec 6 = 7.95 kbit/s, codec 7 = 10.2 kbit/s,
codec 8 = 12.2 kbit/s According 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 and
for each AMR FR codec the number of correct speech frames received from the
MS (or sent to the TRAU) in uplink. To insure consistency of the results, only
speech frames of type "Speech_Good" or "SID_Update" shall be taken into
account. At reception of the measurement report of a given MS, the results are
gathered in the line of the matrix corresponding to reported UL RXLEV.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
426 / 1392
18.2.2.2.2.29 RMS46b - MAX_AMR_FR_UL_RXLEV_UL

Long Name
MAX_AMR_FR_UL_RXLEV_UL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
427 / 1392
18.2.2.2.2.30 RMS47a - AMR_FR_DL_RXLEV_DL

Long Name
AMR_FR_DL_RXLEV_DL
Definition
DL speech frames using AMR FR codec k for which DL RXLEV is reported
= -47 dBm, MEAS_STAT_LEV_10 = -110 dBm AMR FR codecs are defined by
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 According to 3GPP, values of RXLEV lower than -110 dBm
are considered as equal to -110 dBm
Trigger condition
for each AMR FR codec the number of correct speech frames received from the
TC (or sent to the MS) in downlink. To insure consistency of the results, only
gathered in the line of the matrix corresponding to reported DL RXLEV.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
428 / 1392
18.2.2.2.2.31 RMS47b - MAX_AMR_FR_DL_RXLEV_DL

Long Name
MAX_AMR_FR_DL_RXLEV_DL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
429 / 1392
18.2.2.2.2.32 RMS48a - AMR_HR_UL_RXLEV_UL

Long Name
AMR_HR_UL_RXLEV_UL
Definition
speech frames using AMR HR codec k for which UL RXLEV is reported in
level band 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
= -47 dBm, MEAS_STAT_LEV_10 = -110 dBm AMR HR codecs are defined by
6.7 kbit/s, codec 5 = 7.4 kbit/s. According to 3GPP, values of RXLEV lower than
-110 dBm are considered as equal to -110 dBm
Trigger condition
for each AMR HR codec the number of correct speech frames received from the
MS (or sent to the TRAU) in uplink. To insure consistency of the results, only
gathered in the line of the matrix corresponding to reported UL RXLEV.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
430 / 1392
18.2.2.2.2.33 RMS49a - AMR_HR_DL_RXLEV_DL

Long Name
AMR_HR_DL_RXLEV_DL
Definition
DL speech frames using AMR HR codec k for which DL RXLEV is reported
= -47 dBm, MEAS_STAT_LEV_10 = -110 dBm AMR HR codecs are defined by
6.7 kbit/s, codec 5 = 7.4 kbit/s. According to 3GPP, values of RXLEV lower than
-110 dBm are considered as equal to -110 dBm
Trigger condition
for each AMR HR codec the number of correct speech frames received from the
TC (or sent to the MS) in downlink. To insure consistency of the results, only
gathered in the line of the matrix corresponding to reported DL RXLEV.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
431 / 1392
18.2.2.2.2.34 RMS49b - MAX_AMR_HR_DL_RXLEV_DL

Long Name
MAX_AMR_HR_DL_RXLEV_DL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
432 / 1392
18.2.2.2.2.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 reports
in 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 : corresponding
averaged value of [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)] For
Evolium BTS : corresponding averaged value of [ MAX_POWER_PER_TRXabs(BS_TXPWR)]. BS_TXPWR is the BTS transmitted power defined relatively
to the maximum absolute output power of the BTS. BS_TXPWR is expressed
in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. Note
that the formula is written independently of the coding used for the variables.
The function abs() gives the absolute value of its argument. 3) corresponding
averaged value of Timing Advance For Cij, the result is given as follows : Cij=Vij
x 254 / Max_i, where Vij represents the real number of measurements, and
Max_i the greatest value of Vij, for i given (see RMS4b). Cij=0 indicates number
of measurements = 0 Cij=254 indicates number of measurements = Max_i
Cij=255 is 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
precision of 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
by 4, whereas the values that are provided at the user interface are the correct
ones. DL RXQUAL can take values from 0 to 7. Level band i is defined by :
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
Type Name
Type Definition
External Comment
433 / 1392
18.2.2.2.2.36 RMS4b - TMR_RXQUAL_DL_RXLEV_DL

Long Name
TMR_RXQUAL_DL_RXLEV_DL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
434 / 1392
18.2.2.2.2.37 RMS50a - TPR_TIMING_ADVANCE

Long Name
TPR_TIMING_ADVANCE
Definition
Table of 10 results Each cell (i) of the table contains : 1) number of reports in
which Timing Advance is in Timing Advance band i The result is given as follows
: Ci=MAX(ROUND[Vi x 254 / Max], 1), where Vi represents the real number of
measurements, and Max the greatest value of Vi, (see RMS50b). Ci=0 indicates
number of measurements = 0 Ci=254 indicates number of measurements
= Max Ci=255 is reserved to indicate overflow. Timing Advancee band is
defined by : MEAS_STAT_TA_(i-1)<= Timing Advance < MEAS_STAT_TA_i
MEAS_STAT_TA_0 = 0 bper, MEAS_STAT_TA_10 = 63 bper
Trigger condition
Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is in

the given interval of MEAS_STAT_TA.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
435 / 1392
18.2.2.2.2.38 RMS50b - MAX_TIMING_ADVANCE

Long Name
MAX_TIMING_ADVANCE
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
436 / 1392
18.2.2.2.2.39 RMS51 - TPR_UL_RXLEV_TA_BAND

Long Name
TPR_UL_RXLEV_TA_BAND
Definition
Table of 10 results Each cell (i) of the table contains : average value of UpLink
Rxlev of reports in TA band i. Averaged Rxlev is given with a precision of
2 digits after the comma (step size for coding = 0.01, -110 dBm coded 0,
-109.99 dBm coded 1...). i = 1...10 TA band i is defined by : MEAS_STAT_TA_
(i-1)<= Timing Advance < MEAS_STAT_TA_i MEAS_STAT_TA_0 = 0 bper,
MEAS_STAT_TA_10 = 63 bper. According to 3GPP, values of RXLEV lower
than -110 dBm are considered as equal to -110 dBm
Trigger condition
Whenever a MEASUREMENT RESULT is received, UL RXLEV is stored. At

the end of the measurement period, UL RXLEV corresponding to the same
TA band are averaged.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
437 / 1392
18.2.2.2.2.40 RMS52 - TPR_DL_RXLEV_TA_BAND

Long Name
TPR_DL_RXLEV_TA_BAND
Definition
Table of 10 results Each cell (i) of the table contains : average value of DownLink
Rxlev of reports in TA band i. Averaged Rxlev is given with a precision of
2 digits after the comma (step size for coding = 0.01, -110 dBm coded 0,
-109.99 dBm coded 1...). i = 1...10 TA band i is defined by : MEAS_STAT_TA_
(i-1)<= Timing Advance < MEAS_STAT_TA_i MEAS_STAT_TA_0 = 0 bper,
MEAS_STAT_TA_10 = 63 bper. According to 3GPP, values of RXLEV lower
than -110 dBm are considered as equal to -110 dBm
Trigger condition
Whenever a MEASUREMENT RESULT is received, DL RXLEV is stored. At

the end of the measurement period, DL RXLEV corresponding to the same
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
438 / 1392
18.2.2.2.2.41 RMS53 - TPR_UL_RXQUAL_TA_BAND

Long Name
TPR_UL_RXQUAL_TA_BAND
Definition
Table of 10 results Each cell (i) of the table contains : average value of UpLink
Rxqual of reports in TA band i. Averaged Rxqual is given with a precision of 2
digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01 coded 1, ...).
i = 1...10 TA band i is defined by : MEAS_STAT_TA_ (i-1)<= Timing Advance <
MEAS_STAT_TA_i MEAS_STAT_TA_0 = 0 bper, MEAS_STAT_TA_10 = 63 bper.
Trigger condition
Whenever a MEASUREMENT RESULT is received, UL RXQUAL is stored. At

the end of the measurement period, UL RXQUAL corresponding to the same
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
439 / 1392
18.2.2.2.2.42 RMS54 - TPR_DL_RXQUAL_TA_BAND

Long Name
TPR_DL_RXQUAL_TA_BAND
Definition
Table of 10 results Each cell (i) of the table contains : average value of DownLink
Rxqual of reports in TA band i. Averaged Rxqual is given with a precision of 2
digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01 coded 1, ...).
i = 1...10 TA band i is defined by : MEAS_STAT_TA_ (i-1)<= Timing Advance <
MEAS_STAT_TA_i MEAS_STAT_TA_0 = 0 bper, MEAS_STAT_TA_10 = 63 bper.
Trigger condition
Whenever a MEASUREMENT RESULT is received, DL RXQUAL is stored. At

the end of the measurement period, DL RXQUAL corresponding to the same
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
440 / 1392
18.2.2.2.2.43 RMS5a - TPR_BFI_RXLEV_UL

Long Name
TPR_BFI_RXLEV_UL
Definition
Table of 10x10 results Each cell (i,j) of the table contains : 1) number of
reports in which consecutive BFI counter is in BFI band j and UL RXLEV
is reported in level band I (Cij) The result is given as follows : Cij=Vij x
254 / Max_i, where Vij represents the real number of measurements, and
Max_i the greatest value of 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 to indicate overflow. BFI band is defined by
: MEAS_STAT_BFI_(j-1)<= Consecutive BFI counter < MEAS_STAT_BFI_j
MEAS_STAT_BFI_0 = 0, MEAS_STAT_BFI_10 = 25 Level band i is defined by :
Trigger condition
Whenever the Consecutive BFI counter is in the given interval of

MEAS_STAT_BFI, while RXLEV_UL for the same call is in the given interval
of MEAS_STAT_LEV. RMS5a is not incremented while DTX is applied on the
uplink path. Consecutive BFI counter is incremented : 1) Whenever, within the
period of the SACCH multiframe, a speech frame with BFI=1 is received while
the previous speech frame had also BFI=1. The counter must hold concurrently
several periods of consecutive bad speech frames within the SACCH multiframe.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
441 / 1392
18.2.2.2.2.44 RMS5b - TMR_BFI_RXLEV_UL

Long Name
TMR_BFI_RXLEV_UL
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
442 / 1392
18.2.2.2.2.45 RMS6a - TPR_RADIO_LINK

Long Name
TPR_RADIO_LINK
Definition
Table of 10 results Each cell (i) of the table contains : 1) number of reports in
which Radio linkI counter is in S band i The result is given as follows : Ci=Vi x
254 / Max_i, where Vi represents the real number of measurements, and Max_i
the greatest value of Vi (see RMS6b). Ci=0 indicates number of measurements
= 0 Ci=254 indicates number of measurements = Max_i Ci=255 is reserved
to indicate overflow. S band is defined by : MEAS_STAT_S_(i-1)<= Radio link
counter < MEAS_STAT_S_i MEAS_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
Type Name
Type Definition
External Comment
443 / 1392
18.2.2.2.2.46 RMS6b - MAX_RADIO_LINK

Long Name
MAX_RADIO_LINK
Definition
Greatest value of the Vi in RMS6a.
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
444 / 1392
18.2.2.2.2.47 RMS7a - TPR_PATH_BALANCE

Long Name
TPR_PATH_BALANCE
Definition
Table of 10 results Each cell (i) of the table contains : 1) number of reports
in which Path Balance is in Path Balance band i The result is given as
follows : Ci=Vi x 254 / Max_i, where Vi represents the real number of
measurements, and Max_i the greatest value of Vi, (see RMS7b). Ci=0
indicates number of measurements = 0 Ci=254 indicates number of
measurements = Max_i Ci=255 is reserved to indicate overflow. Path Balance
band is defined by : MEAS_STAT_PATH_BALANCE_(i-1)<= Path balance <
MEAS_STAT_PATH_BALANCE_i MEAS_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 is

in 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 defined
relatively to the maximum absolute output power of the BTS. BS_TXPWR
is expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in
dBm. RXLEV_UL and RXLEV_DL are the received signal levels by the base
station and by the mobile station respectively. They are expressed in dBm.
MS_TXPWR is the transmission power of the mobile station and expressed in
dBm, too. Note that the formula is written independently of the coding used for
the variables. The function abs() gives the absolute value of its argument.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
445 / 1392
18.2.2.2.2.48 RMS7b - MAX_PATH_BALANCE

Long Name
MAX_PATH_BALANCE
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
446 / 1392
18.2.2.2.2.49 RMS8a - TPR_CIN

Long Name
TPR_CIN
Definition
Table of 10 results per neighbour cell. Each cell i of the table contains
: 1) number of reports in which the C/I related to the neighbour cell is
reported in C/I band i. The result is given as follows : Ci=Vi x 254 /
RMS8b, where Vi represents the real number of measurements Ci=0
indicates number of measurements = 0 Ci=254 indicates number of
measurements = Max_i Ci=255 is reserved to indicate overflow. C/I band
is defined by : MEAS_STAT_PATH_C_I_(i-1)<= C/I < MEAS_STAT_C_I_i
MEAS_STAT_PATH_C_I_0 = -63 dB, MEAS_STAT_PATH_C_I_10 = 63 dB If
EN_BALANCED_CI = TRUE then C/I (dB) = RXLEV_DL + abs(BS_TXPWR
- BS_TXPWR_MAX) - RXLEV_NCELL Note that the formula is written
independently of the coding used for the variables. RXLEV_DL and
RXLEV_NCELL are the received signal levels of the serving and of the
neighbour cells, expressed in dBm. BS_TXPWR is the BTS transmitted power
and BS_TXPWR_MAX is the maximum allowed BTS transmission power.
Both are defined relatively to the maximum absolute output power of the BTS
(BTS_MAX_OUTPUT_POWER). BS_TXPWR and BS_TXPWR_MAX are
expressed in dB. The function abs() gives the absolute value of its argument.
else C/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)
Trigger condition
Whenever a measurement report indicates that C/I value for the call related to
the neighbour cell is included in the corresponding interval.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
447 / 1392
18.2.2.2.2.50 RMS8b - MR_CIN

Long Name
MR_CIN
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
448 / 1392
18.2.2.2.2.51 RMS9a - TPR_CIF

Long Name
TPR_CIF
Definition
Table of 10 results per frequency reported by extended measurement. Each

cell i of the table contains : 1) number of reports in which the C/I related to
the extended measurement frequency is reported in C/I band i. The result is
given as follows : Ci=Vi x 254 / RMS9b, where Vi represents the real number of
measurements Ci=0 indicates number of measurements = 0 Ci=254 indicates
number of measurements = Max_i Ci=255 is reserved to indicate overflow. C/I
band is defined by : MEAS_STAT_PATH_C_I_(i-1)<= C/I < MEAS_STAT_C_I_i
MEAS_STAT_PATH_C_I_0 = -63 dBm, MEAS_STAT_PATH_C_I_10 =
63 dBm If EN_BALANCED_CI = TRUE then C/I (dB) = RXLEV_DL +
abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELL Note that the formula
is written independently of the coding used for the variables. RXLEV_DL
and RXLEV_NCELL are the received signal levels of the serving and of the
neighbour cells, expressed in dBm. BS_TXPWR is the BTS transmitted power
and BS_TXPWR_MAX is the maximum allowed BTS transmission power.
Both are defined relatively to the maximum absolute output power of the BTS
(BTS_MAX_OUTPUT_POWER). BS_TXPWR and BS_TXPWR_MAX are
expressed in dB. The function abs() gives the absolute value of its argument.
else C/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)
Trigger condition
Whenever a measurement report indicates that C/I value for the extended
measurement frequency is included in the corresponding interval.
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
449 / 1392
18.2.2.2.2.52 RMS9b - MR_CIF

Long Name
MR_CIF
Definition
Trigger condition
Sub Domain 1
RMS
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
450 / 1392
18.2.2.2.2.53 RMSPw3 - MAX_POWER_PER_TRX

Long Name
MAX_POWER_PER_TRX
Definition
Maximum GMSK TRX power level applied at the BTS antenna output connector
in dBm. The power takes into account the different losses (cables, internal
combiners) and the internal/ external leveling but it does not take into account
the 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 the
power required by the BSC for the corresponding TRE (i.e. for the TRE on
which is mapped that TRX). If the operator defines a fine attenuation which will
impact the power of TREs in the cell, then RMSpw3 will also reflect this extra
attenuation.
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
Type Name
Type Definition
External Comment
451 / 1392
18.2.3 Speech
18.2.3.1 All Speech
18.2.3.2
18.2.3.2.1 All
18.2.3.2.2
18.2.3.2.2.1 RMS48b - MAX_AMR_HR_UL_RXLEV_UL
Long Name
MAX_AMR_HR_UL_RXLEV_UL
Definition
Trigger condition
Sub Domain 1
Speech
Sub Domain 2
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
452 / 1392

18.3.2 Channel
18.3.2.1 All Channel
18.3.2.2 TCH
18.3.2.2.1 All TCH
18.3.2.2.2 Usage
18.3.2.2.2.1 RMS31 - TOT_SEIZ_TCH
Long Name
TOT_SEIZ_TCH
Definition
Number of successful TCH seizures for the concerned cell. This counter takes
into account TCH in traffic or in signaling mode.
Trigger condition
Whenever an ESTABLISH INDICATION message is received from the MS to

indicate the activation of a TCH channel for normal assignment or handover.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
TRX
Type Name
Type Definition
External Comment
453 / 1392
454 / 1392
19 BSC-TYPE 32 - Change of frequency band measurements
19 BSC-TYPE 32 - Change of frequency band

measurements
455 / 1392
19.1 All TYPE 32

C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT (Section 19.2.2.2.2.1 )
C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC (Section 19.2.2.2.2.2 )
C404a - NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT (Section 19.2.2.2.2.3 )
C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC (Section 19.2.2.2.2.4 )
C420a - NB_INC_INT_TCH_HO_NEW_BAND_ATPT (Section 19.2.2.2.2.5 )
C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC (Section 19.2.2.2.2.6 )
C421a - NB_OUT_INT_TCH_HO_NEW_BAND_ATPT (Section 19.2.2.2.2.7 )
C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC (Section 19.2.2.2.2.8 )

19.2.2 Handover
19.2.2.2 TCH
19.2.2.2.1 All TCH
456 / 1392

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

including a change of the (TCH) frequency band.
Trigger condition
Whenever 48.008 HANDOVER_REQUEST_ACK is sent by the target BSC

containing the 44.018HANDOVER COMMAND towards the target cell on TCH
and the target and serving cell belong to different frequency bands. Remark:
The change of the (TCH) frequency band for an incoming external handover can
only be detected and taken into account if the adjacency link is defined in both
directions. In case of multiband cells, the BCCH frequency band of the serving
cell will be taken as reference. Note: This counter counts both inter-PLMN and
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Change of frequency band measurements
Type Definition
Set of counters related to handovers including a change of the TCH frequency

band.
External Comment
457 / 1392
19.2.2.2.2.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 successes

Trigger condition

interface from the target cell for a TCH channel that is involved in an external
TCH handover with a change of the frequency band. Remark: The change
of the (TCH) frequency band for an incoming external handover can only
be detected and taken into account if the adjacency link is defined in both
directions. In case of multiband cells, the BCCH frequency band of the serving
cell will be taken as reference. Note: This counter counts both inter-PLMN and
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
458 / 1392
19.2.2.2.2.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 attempts

Trigger condition

interface on the serving channel, during an external TCH handover procedure
including a change of the (TCH) frequency band. Note: This counter counts
both inter-PLMN and intra-PLMN handover events. In case of multiband cells,
the BCCH frequency band of the target cell will be taken as reference.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
459 / 1392
19.2.2.2.2.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 successes

Trigger condition
External TCH handover including a change of the TCH frequency band, in the
following cases: 1/ 48.008 CLEAR COMMAND message with a cause value of
"handover successful" is received. 2/ 48.008 CLEAR COMMAND (cause =
counts both inter-PLMN and intra-PLMN handover events. In case of multiband
cells, the BCCH frequency band of the target cell will be taken as reference.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
460 / 1392
19.2.2.2.2.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 attempts

Trigger condition
Whenever a 44.018HANDOVER COMMAND with a target cell belonging to a

different frequency band is sent to the serving BTS for internal inter cell TCH
handover. However, the counter is incremented in the TARGET cell, based on
the target cell ID indicated by the HO Command message. In case of multiband
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
461 / 1392
19.2.2.2.2.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 successes

Trigger condition

interface from the target cell for a TCH channel that is involved in an internal
inter-cell TCH handover including a change of the (TCH) frequency band. In
case of multiband cells, the BCCH frequency band of the target cell will be
taken as reference.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
462 / 1392
19.2.2.2.2.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 attempts

Trigger condition

interface on the serving channel, during an internal inter-cell TCH handover
procedure including a change of the (TCH) frequency band. In case of multiband
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
463 / 1392
19.2.2.2.2.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 successes

Trigger condition

interface from the target cell , during an internal inter-cell TCH handover
including a change of the (TCH) frequency band. In case of multiband cells, the
BCCH frequency band of the target cell will be taken as reference.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition

band.
External Comment
464 / 1392
20 BSC-TYPE 33 - Electro-Magnetic Emission counters
465 / 1392
20.1 All TYPE 33

E01 - EME_PWR_GSM (Section 20.2.2.2.2.1 )
E02 - EME_PWR_DCS (Section 20.2.2.2.2.2 )
20.2 Electro-Magnetic Emission

20.2.1 All Electro-Magnetic Emission
20.2.2
20.2.2.1 All
20.2.2.2
20.2.2.2.1 All
20.2.2.2.2
20.2.2.2.2.1 E01 - EME_PWR_GSM
Long Name
EME_PWR_GSM
Definition
Average emitted power at the BTS antenna output connector for the GSM
frequency 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 nor
P-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 average
emitted power is calculated and sent back to the BSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
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 is neither
900 MHz nor 850 MHz. This counter is only reported for cells mapped on
Evolium BTS.
466 / 1392
20.2.2.2.2.2 E02 - EME_PWR_DCS

Long Name
EME_PWR_DCS
Definition
Average emitted power at the BTS antenna output connector for the DCS
frequency band (DCS1800 or DCS1900). Counter coded in tenth of Watt. Value
0 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 average
emitted power is calculated and sent back to the BSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Electro-Magnetic Emission counters
Type Definition
Set of counters related to electromagetic emission measurements in the BTS.
External Comment
467 / 1392
468 / 1392
21 BSC-TYPE 34 - Voice Group Call Services
469 / 1392
21.1 All TYPE 34

V01 - NB_PTP_CALL_PREEMPTED_VGCS (Section 21.3.3.3.2.1 )
V021 - AV_PARALLEL_TCH_VGCS (Section 21.4.2.2.2.1 )
V022 - MAX_PARALLEL_TCH_VGCS (Section 21.4.2.2.2.2 )
V03 - NB_VGCS_ESTABLISHMENT_REQ (Section 21.3.3.2.2.1 )
V04 - NB_VGCS_ESTABLISHMENT_SUCC (Section 21.3.3.2.2.2 )
V05 - NB_CM_SERV_REQ_VGCS (Section 21.3.3.2.2.3 )
V06 - NB_VGC_RELEASED_VGCS (Section 21.3.2.2.2.1 )
V07 - NB_OUT_VGCS_HO_ATPT (Section 21.5.3.2.2.1 )
V08 - NB_OUT_VGCS_HO_SUCC (Section 21.5.3.2.2.2 )
V09 - NB_INC_VGCS_HO_SUCC (Section 21.2.2.2.2.1 )
V10 - NB_INC_VGCS_HO_ATPT (Section 21.2.2.2.2.2 )
V11 - NB_TALKER_CHANGE_VGCS (Section 21.5.3.2.2.3 )
V12 - NB_VGC_BLOCKED_VGCS (Section 21.3.3.2.2.4 )
V13 - NB_VGCS_NOTIFIFICATION_FACCH (Section 21.5.2.2.2.1 )
V14 - NB_ASS_REQ_ABLE_PREEMT (Section 21.3.3.2.2.5 )
V15 - NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT (Section 21.3.3.2.2.6 )
V16 - NB_VGCS_QUEUED (Section 21.5.3.2.2.4 )
V17 - NB_VGCS_ESTABLISHED (Section 21.5.3.2.2.5 )
V18 - NB_PREEMTED_TCH_VGCS (Section 21.3.4.2.2.1 )
V19 - NB_PAGING_FACCH (Section 21.5.2.2.2.2 )
21.2 Handover
21.2.1 All Handover
21.2.2 TCH
21.2.2.1 All TCH
470 / 1392
21.2.2.2
21.2.2.2.1 All
21.2.2.2.2
21.2.2.2.2.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 during

observation period. Since there are no reliable means at the target BSC to
retries 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 MS
in the target cell for the channel of the VGCS talker.
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Voice Group Call Services
Type Definition
Set of counters related to Voice Group Call Services (VGCS).
External Comment
471 / 1392
21.2.2.2.2.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 during

observation period. Intracell, internal intercell and external handovers are
counted together. Intracell handover are not counted.
Trigger condition
External handover : Whenever 48.008HANDOVER REQUEST ACK is sent by

the target BSC containing the 44.018HANDOVER COMMAND towards the
target cell on TCH, for a VGC-talker. Internal intercell handover : Whenever a
44.018HANDOVER COMMAND is sent to the serving BTS for internal inter
cell TCH handover, for a VGC talker. However, the counter is incremented in
the TARGET cell, based on the target cell ID indicated by the HO Command
message.
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
472 / 1392


21.3.2.2
21.3.2.2.1 All
21.3.2.2.2
21.3.2.2.2.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 received

from the MSC on the VGCS resource controlling SCCP connection, i. e. on the
SCCP connection initiated with VGCS/VBS ASSIGNMENT REQUEST.
Sub Domain 1
Established Phase
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
473 / 1392

21.3.3.2
21.3.3.2.1 All
21.3.3.2.2
21.3.3.2.2.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/VBS
ASSIGNMENT REQUEST from the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
474 / 1392
21.3.3.2.2.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.008
VGCS/VBS ASSIGNMENT RESULT to the MSC corresponding to a VGCS/VBS
ASSIGNMENT REQUEST.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
475 / 1392
21.3.3.2.2.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 observation

period.
Trigger condition
This counter is incremented each time the BSS receives a CM SERVICE

REQUEST message with parameter CM Service Type set to "Voice group call
establishment (1001)".
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
476 / 1392
21.3.3.2.2.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 observation
period.
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 message
with cause parameter set to "Resource unavailable (010)" whenever 1/ no TCH
is 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 shall
not be de-allocated until the end of the call (channel establishment on demand
forbidden by the MSC) 00000001" or "immediate and the resources may further
be de-allocated by the BSS (channel establishment on demand forbidden by the
MSC) 00000010" ; - queuing was requested by the MSC (parameter "priority.qa"
set to "queuing allowed 1") but disabled in the BSC ; - queuing was requested by
the 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 of
TCH allowed for VGCs has been reached ; - the 48.008 CLEAR REQUEST
message with cause parameter set to "resource unavailable 010" in case of
delayed allocation for a VGCH (i. e. sent over an SCCP connection previously
established with a 48.008 VGCS/VBS ASSIGNMENT REQUEST message
with parameter "assignment requirement" set to "delay allowed 00000000" and
parameter "priority.qa" set to "queuing not allowed 0", whenever no more TCH is
available or the maximum number of TCH allowed for VGCs has been reached.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
477 / 1392
21.3.3.2.2.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 during

observation period.
Trigger condition
This counter is incremented each time the BSC receives a 48.008

ASSIGNEMENT REQUEST message with "Preemption Capability indicator
(pci)" of "Priority" parameter set to "this allocation request may preempt an
existing connection (1)". Notes : 1) This counter is not limited to VGC, so it
also counts messages related to point-to-point calls. 2) Repetitions of the
ASSIGNMENT REQUEST message in case of channel modification are not
counted.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
478 / 1392
21.3.3.2.2.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 cell

during observation period.
Trigger condition
This counter is incremented each time the BSC receives from the MSC a
VGCS/VBS ASSIGNEMENT REQUEST message with "Preemption Capability
indicator (pci)" of "Priority" parameter set to "this allocation request may preempt
an existing connection (1)".
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
479 / 1392

21.3.3.3.2
21.3.3.3.2.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 during
observation period.
Trigger condition
This counter is incremented each time a 48.008 CLEAR REQUEST message is

sent to the MSC under the three following conditions : - "Cause" parameter is set
to "Premption (0101001)" ; - sent on a point-to-point SCCP connection, excluding
the VGCS talker connexion ; - sent further to the reception and processing of
either - a 48.008 VGCS/VBS ASSIGNEMENT REQUEST message received
from the MSC with "Priority" parameter having the information element
"Preemption Capability indicator (pci)" set to "this allocation request may preemt
an existing connection (1)" ; or - a 48.008 ASSIGNEMENT REQUEST message
received 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 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
480 / 1392

21.3.4.2
21.3.4.2.1 All
21.3.4.2.2
21.3.4.2.2.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.008

UPLINK RELEASE INDICATION with 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: Whatever
the TCH is pre-emted for (point-to-point call TCH, VGC talker TCH, VGC listener
TCH), the counter is incremented.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
481 / 1392

21.4.2 Channel
21.4.2.2 TCH
21.4.2.2.1 All TCH
21.4.2.2.2
21.4.2.2.2.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 observation
period. TCH used for VGC listening service and TCH used for VGC talking
service are both counted.
Trigger condition
allocated for VGCS. The sampling period is set to the value indicated in the
Status Inspection field. At the expiry of the accumulation period, all samples are
averaged with an accuracy of 0.1 (i.e. summed, multiplied by 10 and divided
nearest value. Note : The reported value shall then be divided by 10 so that the
value that is taken into acount (interger and decimal parts) is the correct one.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
482 / 1392
21.4.2.2.2.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 observation
period. TCH used for VGC listening service and TCH used for VGC talking
service are both counted.
Trigger condition
Whenever a TCH radio timeslot is allocated for VGCS, the BSC determines the
current number of busy TCH radio timeslots allocated to VGCS. This counter is
the maximum value of this number during the accumulation period. Note: both
talker TCH and listener TCH are counted.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
483 / 1392
21.5 Traffic Load

21.5.2 Channel
21.5.2.2
21.5.2.2.1 All
21.5.2.2.2
21.5.2.2.2.1 V13 - NB_VGCS_NOTIFIFICATION_FACCH
Long Name
NB_VGCS_NOTIFIFICATION_FACCH
Definition
Number of VGC notifications sent over FACCH per cell during observation
period.
Trigger condition
This counter is incremented each time the BSC sends a 48.058 UNIT DATA
REQUEST (NOTIFICATION/FACCH) message to the BTS with the indication
"Group Call Information". Note : this counter does not include paging requests.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
484 / 1392
21.5.2.2.2.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 DATA
REQUEST (NOTIFICATION/FACCH) message to the BTS with the indication
"Paging Information". Note : this counter does not include notification of VGCS.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
485 / 1392

21.5.3.2
21.5.3.2.1 All
21.5.3.2.2
21.5.3.2.2.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 during

counted together.
Trigger condition
Internal intercell HO, external HO : This counter is incremented each time the
44.018 HANDOVER COMMAND message is sent to the MS on the serving
channel, during a TCH handover procedure for a VGCS talker. Intracell HO :
This counter is incremented each time a 44.018 ASSIGNMENT COMMAND
message is sent to the MS for a TCH handover procedure for a VGCS talker.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
486 / 1392
21.5.3.2.2.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 during

counted together.
Trigger condition
This counter is incremented in following cases : 1) External HO: whenever

48.008 CLEAR COMMAND (cause="handover successful") is received on
the serving BSC on the channel of the CGCS talker ; 2) Internal inter-cell
HO: whenever 44.018 HANDOVER COMPLETE is received from the MS via
the target cell on the channel of the VGCS talker ; 3) Internal intra-cell HO:
whenever 44.018 ASSIGNMENT COMPLETE is received from the MS via the
cell on the channel of the VGCS talker.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
487 / 1392
21.5.3.2.2.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 is
the 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 UPLINK
REQUEST CONFIRMATION message to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
488 / 1392
21.5.3.2.2.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 INDICATION

message is sent to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
489 / 1392
21.5.3.2.2.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/VBS
SETUP ACKNOWLEDGE message to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
490 / 1392
22 BSC-TYPE 110 - Overview measurements
491 / 1392
22.1 All TYPE 110

MC01 - NB_IMM_ASS_SUCC_MT (Section 22.4.10.4.3.1 )
MC02 - NB_IMM_ASS_SUCC_MO (Section 22.4.10.4.3.2 )
MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD (Section 22.4.10.4.3.3 )
MC02b - NB_IMM_ASS_SUCC_MO_SMS (Section 22.4.10.4.3.4 )
MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV (Section 22.4.10.4.3.5 )
MC02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON (Section 22.4.10.4.3.6 )
MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST (Section 22.4.10.4.3.7 )
MC02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW (Section 22.4.10.4.3.8
)
MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH (Section 22.4.10.4.3.9 )
MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST (Section 22.4.10.4.3.10 )
MC02i - NB_IMM_ASS_SUCC_MO_LCS (Section 22.4.10.4.3.11 )
MC03 - NB_OUT_SDCCH_HO_SUCC (Section 22.4.5.2.3.1 )
MC04 - NB_IMM_ASS_PREP_FAIL_CONG (Section 22.4.10.4.2.1 )
MC07 - NB_SDCCH_DROP_OUT_HO (Section 22.4.5.2.2.1 )
MC10 - NB_INC_SDCCH_HO_SUCC (Section 22.4.5.2.3.2 )
MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG (Section 22.3.4.5.2.1 )
MC1040 - NB_HO_ATPT_23_TrafHandover (Section 22.3.5.3.2.1 )
MC1044 - NB_HO_ATPT_24_gencapture (Section 22.3.5.3.2.2 )
MC1050 - NB_HO_22_TooShortDistance (Section 22.3.5.3.2.3 )
MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB (Section 22.4.4.2.2.1 )
MC138 - NB_SDCCH_DROP_EST_PHAS_RLF (Section 22.4.4.2.2.2 )
MC13a - NB_TCH_NOR_ASS_QUEUED (Section 22.6.5.6.2.1 )
MC13b - NB_INC_EXT_TCH_HO_QUEUED (Section 22.6.5.3.3.1 )
MC140a - NB_TCH_NOR_ASS_REQ (Section 22.4.10.5.2.1 )
MC140b - NB_TCH_NOR_ASS_ATPT (Section 22.4.10.5.2.2 )
MC141 - AV_NB_TCH_QUEUED (Section 22.5.2.5.3.1 )
MC142e - NB_OUT_IDR_SUCC (Section 22.4.3.2.3.1 )
MC142f - NB_OUT_EDR_SUCC (Section 22.4.3.2.2.1 )
MC144e - NB_OUT_IDR_REQ (Section 22.6.5.2.3.1 )
MC144f - NB_OUT_EDR_REQ (Section 22.6.5.2.2.1 )
MC147 - NB_INC_SDCCH_HO_ALLOC (Section 22.6.5.3.2.1 )
MC148 - NB_IMM_ASS_ALLOC (Section 22.6.5.4.2.1 )
MC149 - NB_IMM_ASS_EXEC_FAIL_RADIO (Section 22.4.10.4.2.2 )
MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB (Section
22.4.5.3.2.1 )
MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB (Section 22.4.4.3.2.1 )
MC151 - NB_INC_IDR_SUCC (29) (Section 22.3.2.2.2.1 )
492 / 1392
MC153 - NB_INC_IDR_REQ (Section 22.3.2.2.2.2 )

MC15a - NB_INC_IDR_ALLOC (Section 22.6.5.2.3.2 )
MC15b - NB_INC_TCH_HO_ALLOC (Section 22.6.5.3.3.2 )
MC161 - NB_DTAP_NOR_ASS_SUCC (Section 22.4.10.3.2.1 )
MC162 - NB_TCH_DROP_DTAP_EST_PHAS (Section 22.4.4.3.2.2 )
MC170 - NB_CALL_TFO (Section 22.4.8.2.2.1 )
MC19 - NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) (Section
22.4.10.5.3.1 )
MC191 - NB_SMS_PP_CON_MT_SDCCH (Section 22.4.7.2.3.1 )
MC196 - NB_SMS_PP_CON_SUCC (Section 22.4.7.2.3.2 )
MC197 - NB_SMS_PP_CON_FAIL (Section 22.4.7.2.2.1 )
MC24 - AV_NB_NOT_AVAIL_TRX_TS (Section 22.5.2.6.2.1 )
MC250 - AV_NB_AVAIL_TCH (Section 22.5.2.5.2.1 )
MC26 - AV_NB_AVAIL_SDCCH (Section 22.5.2.4.3.1 )
MC27 - AV_NB_AVAIL_CCCH (Section 22.5.2.3.2.1 )
MC28a - AV_NB_BUSY_CS_TS (Section 22.5.2.5.3.2 )
MC29a - NB_MAX_SIMUL_BUSY_CS_TS (Section 22.5.2.5.3.3 )
MC31 - NB_MAX_SIMUL_BUSY_SDCCH (Section 22.5.2.4.4.1 )
MC320a - AV_NB_IDLE_TCH_INTERF_BAND1 (Section 22.5.2.5.3.4 )
MC320b - AV_NB_IDLE_TCH_INTERF_BAND2 (Section 22.5.2.5.3.5 )
MC320c - AV_NB_IDLE_TCH_INTERF_BAND3 (Section 22.5.2.5.3.6 )
MC320d - AV_NB_IDLE_TCH_INTERF_BAND4 (Section 22.5.2.5.3.7 )
MC320e - AV_NB_IDLE_TCH_INTERF_BAND5 (Section 22.5.2.5.3.8 )
MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY (Section 22.5.2.6.3.1 )
MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV (Section
22.5.2.2.2.1 )
MC350 - NB_N7_CON_REQ (Section 22.6.4.2.2.1 )
MC351 - NB_N7_CON_CONF (Section 22.6.4.2.2.2 )
MC36 - AV_NB_AVAIL_A_TRAF_CHAN (Section 22.5.2.2.2.2 )
MC370a - NB_TRX_FR_ALLOC (Section 22.5.2.5.3.9 )
MC370b - NB_TRX_HR_ALLOC (Section 22.5.2.5.3.10 )
MC380a - TIME_TRX_FR_BUSY (Section 22.6.3.5.2.1 )
MC380b - TIME_TRX_HR_BUSY (Section 22.6.3.5.2.2 )
MC380c - TIME_TRX_GSM_FR_BUSY (Section 22.6.3.5.2.3 )
MC380d - TIME_TRX_GSM_HR_BUSY (Section 22.6.3.5.2.4 )
MC380e - TIME_TRX_DCS_FR_BUSY (Section 22.6.3.5.2.5 )
MC380f - TIME_TRX_DCS_HR_BUSY (Section 22.6.3.5.2.6 )
MC381 - TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS (Section 22.6.3.5.2.7 )
MC390 - NB_TIMES_SDCCH_BUSY (110) (Section 22.5.2.4.4.2 )
MC400 - TIME_TRX_SDCCH_BUSY (Section 22.6.3.4.2.1 )
493 / 1392
MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH (Section

22.3.7.4.2.1 )
MC448a - NB_TCH_HO_ATPT_26_BadQualHR (Section 22.3.7.3.2.1 )
MC448b - NB_TCH_HO_ATPT_27_GoodQualFR (Section 22.3.7.3.2.2 )
MC449 - NB_TCH_HO_ATPT_28_FastTraffic (Section 22.3.7.3.2.3 )
MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION (Section
22.3.7.3.3.1 )
MC461 - NB_TCH_HO_ATPT_29_TFO (Section 22.3.7.3.2.4 )
MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ (Section 22.3.7.8.2.1 )
MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT (Section 22.3.7.8.2.2 )
MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC (Section 22.3.7.8.2.3 )
MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ (Section 22.3.7.4.2.2 )
MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT (Section 22.3.7.4.2.3 )
MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC (Section 22.3.7.4.2.4 )
MC480 - NB_TCH_HO_REQ_30_ReturnCSZone (Section 22.3.3.2.2.1 )
MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone (Section 22.3.3.2.2.2 )
MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS (Section 22.3.7.4.2.5 )
MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
22.3.7.4.2.6 )
MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
22.3.7.5.2.1 )
MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS (Section 22.3.2.2.2.3 )
MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
22.3.7.6.2.1 )
MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone (Section 22.3.7.3.2.5
)
MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone (Section
22.3.7.3.2.6 )
MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone (Section
22.3.7.3.2.7 )
MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR (Section 22.3.4.2.2.1 )
MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE (Section
22.4.10.5.3.2 )
MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL (Section
22.4.10.5.3.3 )
MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP (Section 22.4.10.2.3.1
)
MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ (Section
22.4.10.5.3.4 )
MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX (Section 22.4.5.3.2.2 )
MC642 - NB_INC_EXT_HO_SUCC (Section 22.3.5.4.2.1 )
MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS (Section 22.3.5.4.2.2 )
MC645a - NB_OUT_EXT_REAL_HO_REQ (Section 22.3.5.7.2.1 )
494 / 1392
MC646 - NB_OUT_EXT_HO_SUCC (Section 22.3.5.7.2.2 )

MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV (Section 22.3.5.7.2.3 )
MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV (Section 22.3.5.7.2.4 )
MC650 - NB_OUT_EXT_HO_ATPT (Section 22.3.5.7.2.5 )
MC652 - NB_INC_INT_HO_SUCC (Section 22.3.5.5.2.1 )
MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS (Section 22.3.5.5.2.2 )
MC655a - NB_OUT_INT_HO_REQ (Section 22.3.5.8.2.1 )
MC656 - NB_OUT_INT_HO_SUCC (Section 22.3.5.8.2.2 )
MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV (Section 22.3.5.8.2.3 )
MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV (Section 22.3.5.8.2.4 )
MC660 - NB_OUT_INT_HO_ATPT (Section 22.3.5.8.2.5 )
MC662 - NB_INTRA_HO_SUCC (Section 22.3.5.6.2.1 )
MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV (Section 22.3.5.6.2.2 )
MC667 - NB_INTRA_HO_EXEC_FAIL_REV (Section 22.3.5.6.2.3 )
MC670 - NB_HO_2_TooLowQualUp (Section 22.3.5.3.2.4 )
MC671 - NB_HO_3_TooLowLevUp (Section 22.3.5.3.2.5 )
MC672 - NB_HO_4_TooLowQualDown (Section 22.3.5.3.2.6 )
MC673 - NB_HO_5_TooLowLevDown (Section 22.3.5.3.2.7 )
MC674 - NB_HO_6_TooLongDistance (Section 22.3.5.3.2.8 )
MC675 - NB_HO_MSC_TRIG (Section 22.3.5.3.2.9 )
MC676 - NB_HO_15_TooHighLevInterfUp (Section 22.3.5.3.2.10 )
MC677 - NB_HO_16_TooHighLevInterfDown (Section 22.3.5.3.2.11 )
MC678 - NB_HO_12_TooLowPowBudg (Section 22.3.5.3.2.12 )
MC679 - NB_HO_21_HighLevNeigCellPrefBand (Section 22.3.5.3.2.13 )
MC701a - NB_TCH_FR_REQ (Section 22.5.4.5.2.1 )
MC701b - NB_TCH_DR_REQ (Section 22.5.4.5.2.2 )
MC701c - NB_TCH_DR_EFR_REQ (Section 22.5.4.5.2.3 )
MC701d - NB_TCH_AMR_REQ (Section 22.5.4.5.2.4 )
MC701e - NB_TCH_DATA_REQ (Section 22.5.4.5.2.5 )
MC701f - NB_TCH_FR_EFR_REQ (Section 22.5.4.5.2.6 )
MC701g - NB_TCH_NO_FR_REQ (Section 22.5.4.5.2.7 )
MC702a - NB_TCH_NOR_FR_ALLOC (Section 22.5.4.5.2.8 )
MC702b - NB_TCH_NOR_HR_ALLOC (Section 22.5.4.5.2.9 )
MC702c - NB_TCH_NOR_EFR_ALLOC (Section 22.5.4.5.2.10 )
MC703 - NB_TCH_NOR_ASS_ALLOC_TRX (Section 22.6.5.6.2.2 )
MC704a - NB_TCH_NOR_AMR_FR_ALLOC (Section 22.5.4.5.2.11 )
MC704b - NB_TCH_NOR_AMR_HR_ALLOC (Section 22.5.4.5.2.12 )
MC705 - NB_TCH_NOR_DATA_ALLOC (Section 22.5.4.5.2.13 )
MC706 - NB_EGSM_MS_ACCESS_EXCEPT_LU (Section 22.5.4.4.2.1 )
495 / 1392
MC710 - NB_TCH_OUT_HO_REQ_TRX (Section 22.3.7.7.2.1 )

MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX (Section 22.4.5.3.2.3 )
MC712 - NB_TCH_OUT_HO_SUCC_TRX (Section 22.4.5.3.3.1 )
MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX (Section 22.4.5.3.2.4 )
MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX (Section 22.4.5.3.2.5 )
MC717a - NB_INC_IDR_SUCC_TRX (Section 22.4.3.2.3.2 )
MC717b - NB_INC_TCH_HO_SUCC_TRX (Section 22.4.5.3.3.2 )
MC718 - NB_TCH_NOR_ASS_SUCC_TRX (Section 22.4.10.5.4.1 )
MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX (Section 22.4.4.3.2.3 )
MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX (Section
22.4.4.3.2.4 )
MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX (Section
22.4.10.5.3.5 )
MC785a - NB_HO_7_ConsBadSACCHmicroCell (Section 22.3.5.3.2.14 )
MC785d - NB_HO_17_TooLowLevUpMicroCell (Section 22.3.5.3.2.15 )
MC785e - NB_HO_18_TooLowLevDownMicroCell (Section 22.3.5.3.2.16 )
MC785f - NB_HO_14_HighLevNeigLowCellSlowMS (Section 22.3.5.3.2.17 )
MC800 - AV_NB_AVAIL_DYN_TS (Section 22.5.2.4.3.2 )
MC801a - AV_NB_BUSY_DYN_TCH (Section 22.5.2.5.3.11 )
MC801b - MAX_NB_BUSY_DYN_TCH (Section 22.5.2.5.3.12 )
MC802a - AV_NB_BUSY_DYN_SDCCH (Section 22.5.2.4.4.3 )
MC802b - MAX_NB_BUSY_DYN_SDCCH (Section 22.5.2.4.4.4 )
MC803 - TIME_SDCCH_CONGESTION (Section 22.5.2.4.2.1 )
MC804a - NB_UL_SINGLE_BLOCK_SIG_RACH (Section 22.6.3.3.2.1 )
MC804b - NB_UL_ONE_PHASE_SIG_RACH (Section 22.6.3.3.2.2 )
MC805a - NB_CHANNEL_ASSIGN_DL_AGCH (Section 22.6.3.3.2.3 )
MC805b - NB_CHANNEL_ASSIGN_DL_PCH (Section 22.6.3.3.2.4 )
MC81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG (Section 22.3.4.3.2.1
)
MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS (Section
22.4.10.5.3.6 )
MC820 - NB_INC_EXT_HO_REQ (Section 22.3.5.4.2.3 )
MC821 - NB_INC_EXT_HO_ATPT (Section 22.3.5.4.2.4 )
MC830 - NB_INC_INT_HO_REQ (Section 22.3.5.5.2.3 )
MC831 - NB_INC_INT_HO_ATPT (Section 22.3.5.5.2.4 )
MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL (Section
22.6.5.5.2.1 )
MC870 - NB_INTRA_HO_REQ (Section 22.3.5.6.2.4 )
MC871 - NB_INTRA_HO_ATPT (Section 22.3.5.6.2.5 )
MC8a - NB_CELL_PAGING_CMD (Section 22.6.3.3.2.5 )
496 / 1392
MC8b - NB_CELL_IMM_ASS_CMD (Section 22.6.3.3.2.6 )

MC8c - NB_CELL_CHAN_REQD (Section 22.6.3.3.2.7 )
MC8d - NB_CELL_IMM_ASS_REJ (Section 22.6.3.3.2.8 )
MC901 - NB_Suspend_Resume_req (Section 22.4.10.2.2.1 )
MC902 - Nb_Suspend_fail (Section 22.4.10.2.2.2 )
MC903 - Nb_Suspend_succ (Section 22.4.10.2.2.3 )
MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG (Section 22.3.4.4.2.1 )
MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT (Section
22.4.10.5.2.3 )
MC921b - NB_PREEMPT_CAP_ALLOC_SUCC (Section 22.4.10.5.2.4 )
MC921c - NB_PREEMPTED_CALLS (Section 22.4.10.5.2.5 )
MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC (Section
22.4.10.5.2.6 )
MC921e - NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE (Section
22.4.10.5.2.7 )
MC922a - NB_INC_EXT_3G_2G_HO_REQ (Section 22.3.5.2.2.1 )
MC922b - NB_INC_EXT_3G_2G_HO_SUCC (Section 22.3.5.2.2.2 )
MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC (Section
22.3.5.2.2.3 )
MC922d - NB_INC_EXT_3G_2G_HO_ATPT (Section 22.3.5.2.2.4 )
MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ (Section
22.3.7.2.2.1 )
MC922f - NB_INC_EXT_TCH_3G_2G_HO_REQ (Section 22.3.7.2.2.2 )
MC922g - NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG (Section
22.3.3.2.2.3 )
MC922h - TIME_3G_HOReject_HL (Section 22.5.4.2.2.1 )
MC923a - NB_LCS_REQ (Section 22.4.6.2.3.1 )
MC923b - NB_LCS_SUCC (Section 22.4.6.2.3.2 )
MC923c - NB_LCS_FAIL_LB (Section 22.4.6.2.2.1 )
MC923d - NB_LCS_ABORT (Section 22.4.6.2.2.2 )
MC924a - TIME_SPDCH_LIMIT_HIGH_LOAD (Section 22.6.3.5.2.8 )
MC924b - NB_OUT_2G_3G_HO_REQ (Section 22.3.7.8.2.4 )
MC924c - NB_OUT_2G_3G_HO_SUCC (Section 22.3.7.8.2.5 )
MC924d - NB_OUT_2G_3G_HO_ATPT (Section 22.3.7.8.2.6 )
MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV (Section 22.3.7.8.2.7 )
MC924f - NB_OUT_2G_3G_HO_EXEC_FAIL_REV (Section 22.3.7.8.2.8 )
MC924g - NB_OUT_2G_3G_HO_PREP_FAIL (Section 22.3.7.8.2.9 )
MC925a - NB_AGCH_USEFUL_BLOCKS_SENT (Section 22.6.3.2.2.1 )
MC925b - NB_PCH_USEFUL_BLOCKS_SENT (Section 22.6.3.2.2.2 )
MC925c - NB_BUSY_RACH_SLOTS (Section 22.6.3.2.2.3 )
MC925d - NB_CHANNEL_RQ_RADIO (Section 22.6.3.2.2.4 )
497 / 1392
MC925e - NB_ASSIGN_CMD_RECEIVED_ABIS (Section 22.6.3.2.2.5 )

MC925f - NB_ASSIGN_CMD_DISCARDED (Section 22.6.3.2.2.6 )
MC925g - NB_PAGING_CMD_RECEIVED_ABIS (Section 22.6.3.2.2.7 )
MC925h - NB_PAGING_CMD_DISCARDED (Section 22.6.3.2.2.8 )
MC926 - TCH_BLOCKING_OCCURENCES_BSC (Section 22.6.2.2.2.1 )
MC927a - NB_DTM_UL_TCH_ASS_ATPT (Section 22.5.4.3.2.1 )
MC927b - NB_DTM_DL_TCH_ASS_ATPT (Section 22.5.4.3.2.2 )
MC927c - NB_DTM_UL_PACKET_ASS_ATPT (Section 22.5.4.3.2.3 )
MC927d - NB_DTM_DL_PACKET_ASS_ATPT (Section 22.5.4.3.2.4 )
MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO (Section 22.5.4.3.2.5
)
MC927f - NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO (Section 22.5.4.3.2.6 )
MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL (Section
22.4.2.2.2.1 )
MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL (Section
22.4.9.2.2.1 )
MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL (Section
22.4.9.2.2.2 )
MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL (Section
22.4.9.2.2.3 )
MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE
(Section 22.4.9.2.2.4 )
MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE
(Section 22.4.9.2.2.5 )
MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UPLINK
(Section 22.4.9.2.2.6 )
MC928h NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK
(Section 22.4.9.2.2.7 )
MC928i - NB_TCH_DROP_OTHER_CAUSES (Section 22.4.9.2.2.8 )
MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED (Section 22.6.3.2.2.9 )
MC931 - NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC (Section 22.5.4.5.2.14
)
MC932 - NB_TCH_AMR_WB_GMSK_REQ (Section 22.5.4.5.2.15 )
MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS (Section 22.4.10.5.2.8 )
MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS (Section 22.3.7.4.2.7 )
MC935 - NB_CALL_TFO_AMR_WB (Section 22.4.8.2.2.2 )
MC936 - NB_HO_INTER_TFO_AMR_WB (Section 22.3.6.2.2.1 )
MC937 - NB_HO_EXT_TFO_AMR_WB (Section 22.3.6.2.2.2 )
MC938 - NB_CALL_TFO_AMR (Section 22.2.2.2.2.7 )
MC939 - NB_HO_INTER_TFO_AMR (Section 22.2.2.2.2.8 )
MC940 - Reserve_BSC_1 (Section 22.2.2.2.2.1 )
498 / 1392

MC950 - NB_HO_EXT_TFO_AMR (Section 22.2.2.2.2.9 )
MC959 - NB_PS_CHAN_REQD (Section 22.4.2.2.2.2 )
MC960 NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION
(Section 22.4.2.2.2.3 )
MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC (Section
22.4.2.2.2.4 )
MC963 NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION
(Section 22.4.2.2.2.5 )
MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC (Section
22.4.2.2.2.6 )
MN1.1 - TIME_N7_ALIGNED (Section 22.5.3.2.2.1 )
499 / 1392
22.2
22.2.1 All
22.2.2
22.2.2.1 All
22.2.2.2
22.2.2.2.1 All
22.2.2.2.2
22.2.2.2.2.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
External Comment
500 / 1392
22.2.2.2.2.2 MC941 - Reserve_BSC_2

Long Name
Reserve_BSC_2
Definition
For future usage
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
501 / 1392
22.2.2.2.2.3 MC942 - Reserve_BSC_3

Long Name
Reserve_BSC_3
Definition
For future usage
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
502 / 1392
22.2.2.2.2.4 MC943 - Reserve_BSC_4

Long Name
Reserve_BSC_4
Definition
For Future usage
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
503 / 1392
22.2.2.2.2.5 MC944 - Reserve_BSC_5

Long Name
Reserve_BSC_5
Definition
For future usage
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
504 / 1392
22.2.2.2.2.6 MC945 - Reserve_BSC_6

Long Name
Reserve_BSC_6
Definition
For future usage
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
505 / 1392
22.2.2.2.2.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 has
been successfully established).
Trigger condition
The value of this provisioned counter shall be set to "0".
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
506 / 1392
22.2.2.2.2.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 been
successfully established after an inter cell handover).
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
507 / 1392
22.2.2.2.2.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 been
successfully established after an external handover).
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
508 / 1392
22.3 Handover
22.3.1 All Handover
22.3.7.4.2.1 )
22.3.7.3.3.1 )
22.3.7.4.2.6 )
22.3.7.5.2.1 )
22.3.7.6.2.1 )
)
22.3.7.3.2.6 )
22.3.7.3.2.7 )
509 / 1392

)
510 / 1392

22.3.5.2.2.3 )
22.3.7.2.2.1 )
22.3.3.2.2.3 )
511 / 1392

22.3.2.2 Internal
22.3.2.2.2 Incoming
22.3.2.2.2.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 TCH

channel in HR or FR usage) successes.
Trigger condition

target cell, for a forced or internal internal directed retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
512 / 1392
22.3.2.2.2.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 the
target cell for forced or normal internal directed retry.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
513 / 1392
22.3.2.2.2.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) -preparation

failures due to congestion (on Air or A-bis interface). The target TCH channel
Trigger condition
1) Whenever there are no free TCH in the target cell during a forced or normal
internal directed retry. 2) Whenever no TCH resource is available on A-bis
interface for a forced or normal internal directed retry. (not valid in B7). Note 1:
In MX BSC, this counter is incremented whenever a TCH cannot be not allocated
due to the TCH processing capacity of CCP reaches the limit defined by the
MAX_TCH_PER_CCP parameter. In this case, MC926 is also incremented by
one. Note 2: In IP mode, this counter is increased by 1 if: - the cell mapped
on a BTS is in IP congestion status; - or the TCH processing capacity of
AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TS
parameter
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Incoming
Measured Object
Common cell
Type Name
Type Definition
External Comment
514 / 1392

22.3.3.2.2.3 )
22.3.3.2
22.3.3.2.1 All
22.3.3.2.2
22.3.3.2.2.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 to
CS zone, I.e. whenever at MAX_SPDCH_LIMIT calculation time, the BSC
detects that 1 TCH is allocated in both MAX_SPDCH_LIMIT zone and the non
pre-emptable PS zone and EN_RETURN_CS_ZONE_HO = Enabled.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
515 / 1392
22.3.3.2.2.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 HO

cause 30.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
516 / 1392
22.3.3.2.2.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 3G

high load in the target cell.
Trigger condition
Whenever a 48.008 HANDOVER FAILURE message is sent to the MSC with

cause "no radio resource available" for a TCH HO request coming from 3G, due
to 3G high load in the target cell. This counter shall be incremented only if
THR_CELL_LOAD_3G_REJECT < 100%.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
517 / 1392
22.3.4 SDCCH
22.3.4.1 All SDCCH
)
22.3.4.2 Cause
22.3.4.2.2
22.3.4.2.2.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 handover

attempts with cause 20: "forced directed retry". This counter is related to a
forced directed retry (internal or external).
Trigger condition

because of cause 20. Note: This counter counts both inter-PLMN and
Sub Domain 1
SDCCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
518 / 1392

)
22.3.4.3.2
22.3.4.3.2.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 -preparation

Trigger condition

MSC during an external SDCCH handover. Note: This counter counts both
Sub Domain 1
SDCCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
519 / 1392

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

Trigger condition
Whenever a internal inter-cell SDCCH handover cannot be performed, because

Sub Domain 1
SDCCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
520 / 1392
22.3.4.5 Intra
22.3.4.5.2
22.3.4.5.2.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 due

to congestion.
Trigger condition
Whenever a internal intra-cell SDCCH handover cannot be performed, because

Sub Domain 1
SDCCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
521 / 1392
22.3.5 SDCCH+TCH
22.3.5.1 All SDCCH+TCH
522 / 1392

22.3.5.2.2.3 )
22.3.5.2
22.3.5.2.1 All
22.3.5.2.2
22.3.5.2.2.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 UMTS

system.
Trigger condition
48.008 HANDOVER REQUEST received by the BSC for an SDCCH or TCH

external handover towards the target cell. Only handovers from a UMTS system
shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to 1011)
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
523 / 1392
22.3.5.2.2.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 UMTS

system.
Trigger condition
44.018HANDOVER_COMPLETE message received from the MS. Only

handovers from a UMTS system shall be taken into account (if the field Cell
Identifier discriminator in the I.E. Cell Identifier (serving) of the corresponding
48.008 HANDOVER REQUEST is set to 1011).
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
524 / 1392
22.3.5.2.2.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 execution

failures due to MS access problem, with or without reversion of the mobile to
the old channel.
Trigger condition
1) Reception of 48.058CONNECTION FAILURE INDICATION (cause=

"handover access failure") for a HO from a UMTS system. 2) Reception of
48.008CLEAR COMMAND (cause= "radio interface failure, reversion to old
channel") for a HO from a UMTS system. Handovers from a UMTS system are
identified 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 1
SDCCH+TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
525 / 1392
22.3.5.2.2.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 UMTS

system.
Trigger condition
Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSC

containing the 44.018HANDOVER COMMAND towards the target cell. Only
handovers from a UMTS system shall be taken into account (if the field Cell
Identifier discriminator in the I.E. Cell Identifier (serving) of the corresponding
48.008 HANDOVER REQUEST is set to 1011)
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
526 / 1392
22.3.5.3 Cause
22.3.5.3.2
22.3.5.3.2.1 MC1040 - NB_HO_ATPT_23_TrafHandover
Long Name
NB_HO_ATPT_23_TrafHandover
Definition
MC1040=C440+C445
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
527 / 1392
22.3.5.3.2.2 MC1044 - NB_HO_ATPT_24_gencapture

Long Name
NB_HO_ATPT_24_gencapture
Definition
MC1044=C444+C446
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
528 / 1392
22.3.5.3.2.3 MC1050 - NB_HO_22_TooShortDistance

Long Name
NB_HO_22_TooShortDistance
Definition
MC1050=C450+C454
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
529 / 1392
22.3.5.3.2.4 MC670 - NB_HO_2_TooLowQualUp

Long Name
NB_HO_2_TooLowQualUp
Definition
MC670=C470+C510
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
530 / 1392
22.3.5.3.2.5 MC671 - NB_HO_3_TooLowLevUp

Long Name
NB_HO_3_TooLowLevUp
Definition
MC671=C471+C511
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
531 / 1392
22.3.5.3.2.6 MC672 - NB_HO_4_TooLowQualDown

Long Name
NB_HO_4_TooLowQualDown
Definition
MC672=C472+C512
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
532 / 1392
22.3.5.3.2.7 MC673 - NB_HO_5_TooLowLevDown

Long Name
NB_HO_5_TooLowLevDown
Definition
MC673=C473+C513
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
533 / 1392
22.3.5.3.2.8 MC674 - NB_HO_6_TooLongDistance

Long Name
NB_HO_6_TooLongDistance
Definition
MC674=C474+C514
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
534 / 1392
22.3.5.3.2.9 MC675 - NB_HO_MSC_TRIG

Long Name
NB_HO_MSC_TRIG
Definition
MC675=C75+C115
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
535 / 1392
22.3.5.3.2.10 MC676 - NB_HO_15_TooHighLevInterfUp

Long Name
NB_HO_15_TooHighLevInterfUp
Definition
MC676=C476+C516
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
536 / 1392
22.3.5.3.2.11 MC677 - NB_HO_16_TooHighLevInterfDown

Long Name
NB_HO_16_TooHighLevInterfDown
Definition
MC677=C477+C517
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
537 / 1392
22.3.5.3.2.12 MC678 - NB_HO_12_TooLowPowBudg

Long Name
NB_HO_12_TooLowPowBudg
Definition
MC678=C478+C518
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
538 / 1392
22.3.5.3.2.13 MC679 - NB_HO_21_HighLevNeigCellPrefBand

Long Name
NB_HO_21_HighLevNeigCellPrefBand
Definition
MC679=C479+C519
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
539 / 1392
22.3.5.3.2.14 MC785a - NB_HO_7_ConsBadSACCHmicroCell

Long Name
NB_HO_7_ConsBadSACCHmicroCell
Definition
MC785a=C585a+C605a
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
540 / 1392
22.3.5.3.2.15 MC785d - NB_HO_17_TooLowLevUpMicroCell

Long Name
NB_HO_17_TooLowLevUpMicroCell
Definition
MC785d=C585d+C605d
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
541 / 1392
22.3.5.3.2.16 MC785e - NB_HO_18_TooLowLevDownMicroCell

Long Name
NB_HO_18_TooLowLevDownMicroCell
Definition
MC785e=C585e+C605e
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
542 / 1392
22.3.5.3.2.17 MC785f - NB_HO_14_HighLevNeigLowCellSlowMS

Long Name
NB_HO_14_HighLevNeigLowCellSlowMS
Definition
MC785f=C585f+C605f
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
543 / 1392

22.3.5.4.2
22.3.5.4.2.1 MC642 - NB_INC_EXT_HO_SUCC
Long Name
NB_INC_EXT_HO_SUCC
Definition
MC642=C42+C82
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
544 / 1392
22.3.5.4.2.2 MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS

Long Name
NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS
Definition
MC643=C43+C83
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
545 / 1392
22.3.5.4.2.3 MC820 - NB_INC_EXT_HO_REQ

Long Name
NB_INC_EXT_HO_REQ
Definition
MC820=C220+C310
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
546 / 1392
22.3.5.4.2.4 MC821 - NB_INC_EXT_HO_ATPT

Long Name
NB_INC_EXT_HO_ATPT
Definition
MC821=C221+C311
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
547 / 1392

22.3.5.5.2
22.3.5.5.2.1 MC652 - NB_INC_INT_HO_SUCC
Long Name
NB_INC_INT_HO_SUCC
Definition
MC652=C52+C92
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
548 / 1392
22.3.5.5.2.2 MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS

Long Name
NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS
Definition
MC653=C53+C93
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
549 / 1392
22.3.5.5.2.3 MC830 - NB_INC_INT_HO_REQ

Long Name
NB_INC_INT_HO_REQ
Definition
MC830=C230+C330
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
550 / 1392
22.3.5.5.2.4 MC831 - NB_INC_INT_HO_ATPT

Long Name
NB_INC_INT_HO_ATPT
Definition
MC831=C231+C331
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
551 / 1392
22.3.5.6 Intra
22.3.5.6.2
22.3.5.6.2.1 MC662 - NB_INTRA_HO_SUCC
Long Name
NB_INTRA_HO_SUCC
Definition
MC662=C62+C102
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
552 / 1392
22.3.5.6.2.2 MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV

Long Name
NB_INTRA_HO_EXEC_FAIL_NO_REV
Definition
MC663=C63+C103
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
553 / 1392
22.3.5.6.2.3 MC667 - NB_INTRA_HO_EXEC_FAIL_REV

Long Name
NB_INTRA_HO_EXEC_FAIL_REV
Definition
MC667=C67+C107
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
554 / 1392
22.3.5.6.2.4 MC870 - NB_INTRA_HO_REQ

Long Name
NB_INTRA_HO_REQ
Definition
MC870=C270+C360
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
555 / 1392
22.3.5.6.2.5 MC871 - NB_INTRA_HO_ATPT

Long Name
NB_INTRA_HO_ATPT
Definition
MC871=C271+C361
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
556 / 1392

22.3.5.7.2
22.3.5.7.2.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 cell identification

discriminator set to a value identifying a GSM handover is sent 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 one 48.008 HANDOVER
REQUIRED is sent in the frame of the same Handover procedure, the respective
counter is incremented only once. 48.008 HANDOVER REQUIRED is sent
in following situations: 1) An external handover alarm has been raised, with
corresponding list of candidate cells. 2) The list of candidate cells for the current
alarm has been updated.
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
557 / 1392
22.3.5.7.2.2 MC646 - NB_OUT_EXT_HO_SUCC

Long Name
NB_OUT_EXT_HO_SUCC
Definition
MC646=C46+C86
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
558 / 1392
22.3.5.7.2.3 MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV

Long Name
NB_OUT_EXT_HO_EXEC_FAIL_REV
Definition
MC647=C47+C87
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
559 / 1392
22.3.5.7.2.4 MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV

Long Name
NB_OUT_EXT_HO_EXEC_FAIL_NO_REV
Definition
MC648=C48+C88
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
560 / 1392
22.3.5.7.2.5 MC650 - NB_OUT_EXT_HO_ATPT

Long Name
NB_OUT_EXT_HO_ATPT
Definition
MC650=C50+C90
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
561 / 1392

22.3.5.8.2
22.3.5.8.2.1 MC655a - NB_OUT_INT_HO_REQ
Long Name
NB_OUT_INT_HO_REQ
Definition
MC655a=C55a+C95a
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
562 / 1392
22.3.5.8.2.2 MC656 - NB_OUT_INT_HO_SUCC

Long Name
NB_OUT_INT_HO_SUCC
Definition
MC656=C56+C96
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
563 / 1392
22.3.5.8.2.3 MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV

Long Name
NB_OUT_INT_HO_EXEC_FAIL_REV
Definition
MC657=C57+C97
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
564 / 1392
22.3.5.8.2.4 MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV

Long Name
NB_OUT_INT_HO_EXEC_FAIL_NO_REV
Definition
MC658=C58+C98
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
565 / 1392
22.3.5.8.2.5 MC660 - NB_OUT_INT_HO_ATPT

Long Name
NB_OUT_INT_HO_ATPT
Definition
MC660=C60+C100
Trigger condition
Sub Domain 1
SDCCH+TCH
Sub Domain 2
Outgoing Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
566 / 1392
22.3.6 Speech
22.3.6.1 All Speech
22.3.6.2 TFO
22.3.6.2.1 All TFO
22.3.6.2.2
22.3.6.2.2.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 successfully
established after an inter cell handover
Trigger condition
For each assigned TCH further to an inter cell handover, the counter is
incremented the first time a 48.058 TFO REPORT 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 assigned TCH (i.e. the first time it is received for the
assigned TCH). Note 2: This means that the counter is incremented only if the
TCH is assigned to serve an incoming inter-cell handover.
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
567 / 1392
22.3.6.2.2.2 MC937 - NB_HO_EXT_TFO_AMR_WB

Long Name
NB_HO_EXT_TFO_AMR_WB
Definition
established after an external handover
Trigger condition
For each assigned TCH further to an external handover, the counter is

incremented the first time a 48.058 TFO REPORT 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 assigned TCH (i.e. the first time it is received for the
assigned TCH). Note 2: This means that the counter is incremented only if the
TCH is assigned to serve an incoming iexternal handover.
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
568 / 1392
22.3.7 TCH
22.3.7.1 All TCH
22.3.7.4.2.1 )
22.3.7.3.3.1 )
22.3.7.4.2.6 )
22.3.7.5.2.1 )
22.3.7.6.2.1 )
)
22.3.7.3.2.6 )
22.3.7.3.2.7 )
22.3.7.2.2.1 )
569 / 1392
22.3.7.2
22.3.7.2.1 All
22.3.7.2.2
22.3.7.2.2.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 SAI

in 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
Measured Object
Common cell
Type Name
Type Definition
External Comment
570 / 1392
22.3.7.2.2.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 in

the source cell identifier
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
571 / 1392
22.3.7.3 Cause
22.3.7.3.3.1 )
)
22.3.7.3.2.6 )
22.3.7.3.2.7 )
22.3.7.3.2
22.3.7.3.2.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 channel
adaptation due to bad radio quality" on a TCH channel.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
572 / 1392
22.3.7.3.2.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 channel
adaptation due to good radio quality" on a TCH channel.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
573 / 1392
22.3.7.3.2.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

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
574 / 1392
22.3.7.3.2.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 mismatch

resolution, TFO optimisation). MC461 = C461
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
575 / 1392
22.3.7.3.2.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 level
too low" on TCH channel (in HR or FR usage). This counter is related to
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
576 / 1392
22.3.7.3.2.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 downlink
level too low" on TCH channel (in HR or FR usage). This counter is related to
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
577 / 1392
22.3.7.3.2.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 and
downlink levels too high" on TCH channel (in HR or FR usage). This counter is
related to concentric cell environment.
Trigger condition

Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
578 / 1392
22.3.7.3.3 Success
22.3.7.3.3.1 MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION
Long Name
NB_TCH_EMERGENCY_HO_PRESERVATION
Definition
Number of high priority TCH requests served when 1) the number of free TCH
timeslots is less than or equal to NUM_TCH_EGNCY_HO and, 2) the queue for
this cell is not empty.
Trigger condition
The counter is incremented on the serving cell whenever the 48.058 CHANNEL
ACTIVATION message allocating a TCH channel is sent and the following two
conditions are both fulfilled: 1) the TCH is allocated to serve i) an internal
handover Cause 2, 3, 4, 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 22, 27, or, ii) an
external handover Cause "Uplink quality", "Uplink strength", "Downlink quality",
"Downlink strength", "Distance", or iii) a normal assignment or an external
handover with the preemption indicator set (i.e. Preemption Capability Indicator
= 1 and EN_TCH_PREEMPT = Enable). 2) the number of free TCH timeslots
is less than or equal to NUM_TCH_EGNCY_HO and there is at least one
request queued for this cell. Note 1: This counter counts both inter-PLMN
and intra-PLMN handover events. Note 2: The HMI name of the parameter
NUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".
Sub Domain 1
TCH
Sub Domain 2
Cause
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
579 / 1392

22.3.7.4.2.1 )
22.3.7.4.2.6 )
22.3.7.4.2
22.3.7.4.2.1 MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH
Long Name
NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH
Definition

failures 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 target
BSC to the MSC. 2) Whenever a 48.008 HANDOVER FAILURE message with
a cause value of "terrestrial circuit already allocated" is sent on A interface
from the target BSC to the MSC. 3) Whenever a 48.008 HANDOVER FAILURE
message with a cause value of "BSS not equipped" is sent on A interface from
the target BSC to the MSC. Note: This counter counts both inter-PLMN and
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
580 / 1392
22.3.7.4.2.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 the

MSC on A interface for an external TCH handover or an external directed retry
triggered towards the target cell from a serving cell belonging to a PLMN
different from the PLMN of the target cell.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
581 / 1392
22.3.7.4.2.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 target

BSC containing the 44.018 HANDOVER COMMAND message for an external
TCH handover or an external directed retry triggered towards the target cell from
a serving cell belonging to a PLMN different from the PLMN of the target cell.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
582 / 1392
22.3.7.4.2.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 the

MS on Abis interface for an external TCH handover or an external directed
retry triggered towards the target cell from a serving cell belonging to a PLMN
different from the PLMN of the target cell.
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
583 / 1392
22.3.7.4.2.5 MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Long Name
NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS
Definition

failures due to congestion (C541a), or A-traffic-channel status mismatch
between the BSC and the MSC (C41b).
Trigger condition
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
584 / 1392
22.3.7.4.2.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

Trigger condition

MSC during an external TCH handover. Note 1: This counter counts both
inter-PLMN and intra-PLMN handover events. Note 2: In MX BSC, this counter
is incremented whenever a 48.008 HANDOVER FAILURE message with a
cause value of "no radio resource available" is sent due to the TCH processing
capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP
parameter. In this case, MC926 is also incremented by one. Note 3: In IP mode,
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
585 / 1392
22.3.7.4.2.7 MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS

Long Name
NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS
Definition

failures due to A interface mismatch between the BSC and the MSC.
Trigger condition

"circuit pool mismatch" is sent on A interface from the target BSC to the MSC.
Note: This counter counts both inter-PLMN and intra-PLMN handover event
Sub Domain 1
TCH
Sub Domain 2
Incoming External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
586 / 1392

22.3.7.5.2.1 )
22.3.7.5.2
22.3.7.5.2.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

Trigger condition
Whenever an internal inter-cell TCH handover cannot be performed, because

the target cell is congested (no free TCH channel). Note 1: In MX BSC,
this counter is incremented whenever an internal inter-cell TCH handover
cannot be performed due to the TCH processing capacity of CCP reaches the
limit defined by the MAX_TCH_PER_CCP parameter. In this case, MC926
is also incremented by one. Note 2: In IP mode, this counter is increased
by 1 if: - the cell mapped on a BTS is in IP congestion status; - or the TCH
Sub Domain 1
TCH
Sub Domain 2
Incoming Internal
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
587 / 1392
22.3.7.6 Intra
22.3.7.6.2.1 )
22.3.7.6.2
22.3.7.6.2.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 failures

due to congestion. This counter takes into account handovers from TCH in
traffic or in signaling mode. It does not take into account DTM Assignments.
Trigger condition
Whenever a internal intra-cell TCH handover cannot be performed, because

there 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 be
performed due to the TCH processing capacity of CCP reaches the limit
defined by the MAX_TCH_PER_CCP parameter. In this case, MC926 is
also incremented by one. Note 2: In IP mode, this counter is increased by
1 if: - the cell mapped on a BTS is in IP congestion status; - or the TCH
Sub Domain 1
TCH
Sub Domain 2
Intra
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
588 / 1392
22.3.7.7 Outgoing
22.3.7.7.1 All Outgoing
22.3.7.7.2
22.3.7.7.2.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 intercell

Trigger condition
1) Intracell HO: Whenever the BSC process responsible for the handover
procedure starts an intra cell TCH handover procedure. 2) Internal intercell HO:
target 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 on
A interface to the MSC. If more than one 48.008 HANDOVER REQUIRED is
sent in the frame of the same Handover procedure, the counter is incremented
only once. 48.008 HANDOVER REQUIRED is sent in following situations: 1) An
external handover alarm has been raised, with corresponding list of candidate
cells. 2) The list of candidate cells for the current alarm has been updated.
Sub Domain 1
TCH
Sub Domain 2
Outgoing
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
589 / 1392

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

counter takes into account TCH in traffic or in signaling mode.
Trigger condition
Whenever a 48.008 HANDOVER REQUIRED message with the cell

identification discriminator set to a value identifying a GSM handover is sent to
the MSC on A interface for an external TCH handover or an external directed
retry triggered towards a 2G cell belonging to a PLMN different from the PLMN
of the serving cell.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
590 / 1392
22.3.7.8.2.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. This

counter takes into account TCH in traffic or in signaling mode.
Trigger condition
Whenever a 44.018 HANDOVER COMMAND message is sent to the MS on

Abis interface for an external TCH handover or an external directed retry
triggered towards a 2G cell belonging to a PLMN different from the PLMN of
the serving cell.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
591 / 1392
22.3.7.8.2.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 PLMN

different from the PLMN of the serving cell in the following cases: 1/ 48.008
CLEAR COMMAND message with Cause "Handover successful" is received
from the MSC. 2/ 48.008 CLEAR COMMAND (cause = "normal event/call
control") received while T8 is running.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
592 / 1392
22.3.7.8.2.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 a

3G cell.
Trigger condition
Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface

to the MSC for a TCH handover to a 3G FDD cell. 48.008 HANDOVER
REQUIRED is 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 of candidate cells for the current alarm has been updated. Note: This
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
593 / 1392
22.3.7.8.2.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 successes

to a 3G cell.
Trigger condition
External TCH handover to a 3G cell, in the following cases: 1/ 48.008 CLEAR

COMMAND message with a cause value of "handover successful" is received
on 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:
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
594 / 1392
22.3.7.8.2.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 a

3G cell.
Trigger condition

interface on the serving channel, during an external TCH handover procedure
to a 3G cell. Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
595 / 1392
22.3.7.8.2.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 execution

failures to a 3G cell due to MS access problem without reversion of the mobile
to the old channel (call drop).
Trigger condition
(T3121), expires during an external TCH handover to a 3G cell, 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 a case, the handover
is considered as successful. Note: This counter counts both inter-PLMN and
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
596 / 1392
22.3.7.8.2.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 -execution

failures to a 3G cell due to MS access problem with reversion of the mobile to
the old channel.
Trigger condition

interface from the serving cell , during an external TCH handover to a 3G cell.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
597 / 1392
22.3.7.8.2.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 the

MSC 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 parameter
RESP_REQ is set to 1.
Sub Domain 1
TCH
Sub Domain 2
Outgoing External
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
598 / 1392

)
22.4.5.3.2.1 )
22.4.10.5.3.1 )
22.4.10.5.3.2 )
599 / 1392

22.4.10.5.3.3 )
)
22.4.10.5.3.4 )
22.4.4.3.2.4 )
22.4.10.5.3.5 )
22.4.10.5.3.6 )
22.4.10.5.2.3 )
22.4.10.5.2.6 )
22.4.10.5.2.7 )
22.4.2.2.2.1 )
22.4.9.2.2.1 )
22.4.9.2.2.2 )
600 / 1392

22.4.9.2.2.3 )
(Section 22.4.9.2.2.4 )
(Section 22.4.9.2.2.5 )
(Section 22.4.9.2.2.6 )
(Section 22.4.9.2.2.7 )
(Section 22.4.2.2.2.3 )
22.4.2.2.2.4 )
(Section 22.4.2.2.2.5 )
22.4.2.2.2.6 )
22.4.2 BSC
22.4.2.1 All BSC
22.4.2.2.2.1 )
(Section 22.4.2.2.2.3 )
22.4.2.2.2.4 )
(Section 22.4.2.2.2.5 )
22.4.2.2.2.6 )
601 / 1392
22.4.2.2
22.4.2.2.1 All
22.4.2.2.2
22.4.2.2.2.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 with

cause "radio link failure" is received on Abis interface for a TCH channel
message is received on Abis interface after TCH seizure and leads to a loss
of call. 3) Whenever the timer supervising the handover procedure (T3103)
expires during the inter-cell TCH handover. 4) Whenever the timer supervising
the handover procedure on the serving cell (T8) expires during the external
TCH handover. The BSC uses the last valid measurements (Note) received
for this MS. The counter is incremented if the following condition is fulfilled:
AV_RXQUAL_UL_HO > L_RXQUAL_UL_H + OFFSET_RXQUAL_FH And
AV_RXLEV_UL_HO <= RXLEV_UL_IH Note: "Last valid measurements"
means the last received 48.058 MEASUREMENT RESULT messages with
S-BFI flag set to "0".
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
602 / 1392
22.4.2.2.2.2 MC959 - NB_PS_CHAN_REQD

Long Name
NB_PS_CHAN_REQD
Definition
Number of 48.058 CHANNEL REQUIRED (for packet service) received via

the selected cell.
Trigger condition
This counter is incremented by one if: 1) the "RA (Random Access Reference)"
byte in the 48.058 CHANNEL REQUIRED message equals to the following
values: 011110xx, 01111x0x, 01111xx0 (one phase packet access); 01110xxx
(single block packet access), or; 2) EGPRS Request Reference optional IE is
included in the 48.058 CHANNEL REQUIRED message.
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
603 / 1392
22.4.2.2.2.3 MC960 NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION

Long Name
NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION
Definition
Number of 48.058 CHANNEL REQUIRED (for packet service) received and

discarded by the BSC in case of GSL CONGESTION.
Trigger condition
"48.058 CHANNEL REQUIRED (for packet service)" refers to one 48.058

CHANNEL REQUIRED message that contains the "EGPRS Request
Reference" optional IE; or the "RA (Random Access Reference)" byte of
48.058 CHANNEL REQUIRED message equals to the following values:
011110xx, 01111x0x, 01111xx0 (one phase packet access); 01110xxx
(single block packet access). This counter is incremented by one if a "48.058
CHANNEL REQUIRED (for packet service)" message is discarded by the
BSC in case of GSL congestion (for the handling of the GSL congestion: cf.
the BTP parameters NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC,
NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC,
NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC and
NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC).
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
604 / 1392
22.4.2.2.2.4 MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC

Long Name
NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC
Definition
Number of invalid 48.058 CHANNEL REQUIRED (for all establishment cause)

messages received by the BSC.
Trigger condition
Upon reception of a 48.058 CHANNEL REQUIRED message from the BTS, the
BSC checks firstly the content of message. If an error is found, the received
48.058 CHANNEL REQUIRED message is discarded by the BSC. The counter
MC962 is incremented by one each time the received 48.058 CHANNEL
REQUIRED message is discarded because one of the following errors have
been detected by the BSC: 1) The message syntax errors, for example (list
non-exclusive): 1a) the message length is incorrect: i.e., the EGPRS Request
Reference OIE is not present, but the length of message does not equal to "10";
or the EGPRS Request Reference OIE is present, but the length of message
does not equal to "13" (Note 1). 1b) the IE length is incorrect. 2) the Timeslot
Number received in the CHANNEL REQUIRED message does not equal to
0 or 2 (only timeslot 0 or 2 can be used as BCCH Timeslots). 3) The C-bits
(C5, C4, C3, C2 & C1) of Channel Number MIE is not equal to the coding
10001 "Uplink CCCH (RACH)". 4) In case where the GPRS service is allowed
(EN_GPRS = TRUE) and the GPRS service has already been activated in the
cell: the BSC checks the presence of EGPRS Request Reference optional
IE. If this OIE is not included, then the BSC checks the "RA (Random Access
Reference)" byte in the 48.058 CHANNEL REQUIRED message: if the bits 8,
7 and 6 of "RA (does not equal to one of the following values: 000, 100, 101,
110, 111 and "RA (Random Access Reference)" byte in the 48.058 CHANNEL
REQUIRED message does not equal to the following values: 011110xx,
01111x0x, 01111xx0 (one phase packet access); 01110xxx (single block packet
access), Note 2. 5) In case where the GPRS service is not allowed (EN_GPRS
= FALSE) or the GPRS service has not yet been activated in the cell: if the bits
8, 7 and 6 of "RA (Random Access Reference)" byte in the 48.058 CHANNEL
REQUIRED message does not equal to one of the following values: 000, 100,
101, 110, 111; or if EGPRS Request Reference optional IE is included in the
48.058 CHANNEL REQUIRED message. 6) The Access delay value is greater
than or equal to RACH_TA_FILTER. Note 1: the EGPRS Request Reference
IE is an optional (ALU proprietary) in the CHANNEL REQUIRED message. If
this optional IE is present, the length of CHANNEL REQUIRED message is 13
instead of 10. Note 2: if the EGPRS Request Reference OIE is included, the
BSC does not check the "RA (Random Access Reference)" byte in the 48.058
CHANNEL REQUIRED message.
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
605 / 1392
22.4.2.2.2.5 MC963 NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION

Long Name
NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION
Definition
Number of valid 48.058 CHANNEL REQUIRED (for non-(E)GPRS related

establishment cause) discarded by the BSC due to the congestion.
Trigger condition
Upon reception of a 48.058 CHANNEL REQUIRED message from the

BTS, the BSC checks firstly the content of received message (see counter
MC962). After having passed successfully this check, the BSC checks the
establishment cause in the received message. If the received 48.058 CHANNEL
REQUIRED message does not contain the "EGPRS Request Reference"
optional IE; or the "RA (Random Access Reference)" byte does not equal to the
following values: 011110xx, 01111x0x, 01111xx0 (one phase packet access);
01110xxx (single block packet access), then this message is considered as
a "CHANNEL REQUIRED (for non-(E)GPRS related establishment cause)"
message. The BSC may discard a "CHANNEL REQUIRED (for non-(E)GPRS
related establishment cause)" message in case of cell congestion. MC963 is
incremented by one each time a "CHANNEL REQUIRED (for non-(E)GPRS
related establishment cause)" message is discarded because one of the
following reasons: 1) The cell is unavailable for telecom traffic 2) there is no
SDCCH available and EN_IM_ASS_REJ = "disabled". 3) there is no SDCCH
available, and EN_IM_ASS_REJ = "enabled", and the Bits 8, 7 and 6 of "RA
(Random Access Reference)" byte in the 48.058 CHANNEL REQUIRED
message equals to "000", and the value of parameter WI_OP equals to 255. 4)
there is no SDCCH available, and EN_IM_ASS_REJ = "enabled", and the Bits
REQUIRED message equals to "100". 5) there is no SDCCH available, and
EN_IM_ASS_REJ = "enabled", and the Bits 8, 7 and 6 of "RA (Random Access
Reference)" byte in the 48.058 CHANNEL REQUIRED message equals to
"101", and the value of parameter WI_EC equals to 255. 6) there is no SDCCH
available, and EN_IM_ASS_REJ = "enabled", and the Bits 8, 7 and 6 of "RA
(Random Access Reference)" byte in the 48.058 CHANNEL REQUIRED
message equals to "110", and the value of parameter WI_CR equals to 255. 7)
there is no SDCCH available, and EN_IM_ASS_REJ = "enabled", and the Bits
REQUIRED message equals to "111", and the value of parameter WI_OC
equals to 255. 8) there is BSC inter-process congestion.
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
606 / 1392
22.4.2.2.2.6 MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC

Long Name
NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC
Definition
Number of valid 48.058 CHANNEL REQUIRED message, received by the BSC,

indicating the location update in their "establishment cause".
Trigger condition
MC964 is incremented to one whenever the "RA" octet (Octet 2 of Request

Reference IE) of valid 48.058 CHANNEL REQUIRED equals to "000xxxxx
(Location updating and the network does not set NECI bit to 1)".
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
607 / 1392

22.4.3.2 Internal
22.4.3.2.2 Failure
22.4.3.2.2.1 MC142f - NB_OUT_EDR_SUCC
Long Name
NB_OUT_EDR_SUCC
Definition
MC142f=C142b+C142d
Trigger condition
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
608 / 1392
22.4.3.2.3 Success
22.4.3.2.3.1 MC142e - NB_OUT_IDR_SUCC
Long Name
NB_OUT_IDR_SUCC
Definition
MC142e=C142a+C142c
Trigger condition
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
609 / 1392
22.4.3.2.3.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

interface from the target cell for a TCH channel involved in an internal directed
retry procedure.
Sub Domain 1
Directed Retry
Sub Domain 2
Internal
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
610 / 1392

22.4.4.3.2.4 )
22.4.4.2 SDCCH
22.4.4.2.1 All SDCCH
22.4.4.2.2 Failure
22.4.4.2.2.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 to

BSS problem.It may happen that several causes of failures mentioned below
once, 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 value
being received during the stable phase of an SDCCH transaction. 3) Telecom
Supervisory module caused the call to be cleared. 4) SDCCH was released due
to 0180 CLEAR_CMD message being received from BSSAPduring the stable
phase 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
Type Name
Type Definition
External Comment
611 / 1392
22.4.4.2.2.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

cause value of "radio link failure" is received on Abis interface for an SDCCH
channel. 2) Whenever an 48.058 ERROR INDICATION message is received on
Abis interface and leads to a loss of channel.
Sub Domain 1
Established Phase
Sub Domain 2
SDCCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
612 / 1392
22.4.4.3 TCH
22.4.4.3.1 All TCH
22.4.4.3.2.4 )
613 / 1392
22.4.4.3.2 Failure
22.4.4.3.2.1 MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB
Long Name
NB_TCH_DROP_EST_PHAS_BSS_PB
Definition

BSS problem. It may happen that several causes of failures mentioned below
once, as soon as the call is released. This counter takes into account TCH in
traffic or in signaling mode. It is not incremented in case of TCH drop during a
normal assignment, a handover or a DTM assignment.
Trigger condition
1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M

of call. 2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with a
cause value of "message sequence error" is received on Abis interface after TCH
seizure and leads to a loss of call. 3) Whenever a LAPD failure is reported to the
Layer 3 of the BSC (for an RSL supporting a TCH transaction after successful
TCH seizure) and leads to a loss of call. 4) Whenever a TCH call release is
timer reference, file reference...) or communication problems between different
processor boards). Notes : 1. TCH call releases which 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 counter will overestimate failures which
are due to problems which are internal to the BSS. However, due to the current
implementation 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 counter
can not be incremented since it is implemented within the faulty entity.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
614 / 1392
22.4.4.3.2.2 MC162 - NB_TCH_DROP_DTAP_EST_PHAS

Long Name
NB_TCH_DROP_DTAP_EST_PHAS
Definition
MC162 = C162a + C162b + C162c
Trigger condition
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
615 / 1392
22.4.4.3.2.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 due

to radio link failure (radio link timeout or Lapdm timer expiry), per TRX. This
counter takes into account TCH in traffic or in signaling mode. MC736 = C736
Trigger condition

message is received on Abis interface and leads to a loss of call.
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
616 / 1392
22.4.4.3.2.4 MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Long Name
NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX
Definition

remote transcoder failures (per TRX).
Trigger condition
The counter is incremented whenever a 48.058 CONNECTION FAILURE

INDICATION message with cause "Remote Transcoder Failure" is received
on Abis interface for an established TCH connection. The BSC considers a
TCH connection as "established" once a 44.018 ASSIGNMENT COMPLETE
message (in case of normal assignments or an internal intra-cell handovers) or
a 44.018 HANDOVER COMPLETE message (in case of an internal inter-cell
incoming HO or an external inter-cell incoming HO) has been received for the
TCH connection. Note 1: MC739 = C739. Note 2: The counter is incremented
only once per established TCH connection. Thus, even if the BTS sends several
48.058 CONNECTION FAILURE INDICATION messages with cause "Remote
Transcoder Failure" for a particular established TCH connection, BSC will
increment the counter only once for that connection."
Sub Domain 1
Established Phase
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
617 / 1392
22.4.5 Handover
22.4.5.3.2.1 )
22.4.5.2 SDCCH
22.4.5.2.2 Failure
22.4.5.2.2.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 the

handover procedure (T3103) expires.
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
618 / 1392
22.4.5.2.3 Success
22.4.5.2.3.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.008
CLEAR COMMAND (cause= "normal event/call control") received while T8 is
running. Note: This counter counts both inter-PLMN and intra-PLMN handover
events.
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
619 / 1392
22.4.5.2.3.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 HANDOVER

COMPLETE message is received on Abis interface from the target cell for
an SDCCH Sub-channel. Note: This counter counts both inter-PLMN and
Sub Domain 1
Handover
Sub Domain 2
SDCCH
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
620 / 1392
22.4.5.3 TCH
22.4.5.3.1 All TCH
22.4.5.3.2.1 )
22.4.5.3.2 Failure
22.4.5.3.2.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 TCH
handover preparation and execution phases. This counter is incremented on the
cell 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 are
not related to a specific cell, the counter related to the serving cell will be
incremented. It may happen that several causes of failures mentioned below
once, as soon as the handover procedure fails. This counter takes into account
621 / 1392
Trigger condition
1) Whenever the BSC receives on Abis interface from the target cell negative
acknowledgment to the TCH channel activation involved in the handover
procedure. 2) Whenever the timer supervising the Channel Activation procedure
(T9103) expires on the target cell during activation of a TCH channel involved in
the handover procedure. 3) Whenever an 48.058 ERROR REPORT message
with a cause value of "O&M intervention" is received on Abis interface from
either the serving or the target cell during the external or internal inter-cell
handover procedure and leads to a transaction failure. 4) Whenever an 48.058
ERROR REPORT message with a cause value of "O&M intervention" is
received on Abis interface on either the old or the new channel during the
internal intra-cell handover procedure and leads to a transaction failure. 5)
of "message sequence error" is received on Abis interface from the serving
cell between the sending of the 48.058 CHANNEL ACTIVATION message and
the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT
during the internal inter-cell TCH handover and leads to a transaction failure. 6)
of "message sequence error" is received on Abis interface on the old channel
between the sending of the 48.058 CHANNEL ACTIVATION message and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the
internal intra-cell TCH handover and leads to a transaction failure. 7) Whenever
a LAPD failure related to either serving or target cell is reported to the Layer 3
of the BSC (for an RSL supporting a TCH transaction for handover purpose)
and leads to a transaction failure. 8) Whenever an TCH handover abortion is
timer reference, file reference...) or communication problems between
different processor boards). 9) Whenever a 48.058 CONNECTION FAILURE
INDICATION message with a cause value of "remote transcoder failure" is
received on Abis interface from the old channel between the sending of the
48.058 CHANNEL ACTIVATION message and the reception of the 48.058
CHANNEL ACTIVATION ACKNOWLEDGE during an internal intra-cell or
inter-cellTCH handover procedure and leads to a transaction failure. Notes :
1. TCH handover failures which 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 counter will overestimate failures which are due to problems
which are internal to the BSS. However, due to the current implementation 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 counter can not be incremented
since it is implemented within the faulty entity.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
622 / 1392
Type Definition
External Comment
623 / 1392
22.4.5.3.2.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 in
signaling mode. MC621 = C621
Trigger condition
1) Inter-cell TCH handover: whenever the timer supervising the handover

procedure (T3103) expires. 2) External TCH handover (2G -> 2G): whenever
the timer supervising the handover procedure on 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 a normal call release. In such a case, the
handover is considered as successful. 3) Intra-cell TCH handover: whenever
the timer supervising the handover procedure (T3107) expires. 4) 2G -> 3G HO:
whenever the timer supervising the 2G-3G handover procedure on the serving
cell (T3121) expires, except if a 48.008 CLEAR COMMAND with "normal
release. In such a case, the 2G->3G handover is considered as successful.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
624 / 1392
22.4.5.3.2.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. This
does 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) Internal
inter-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) External
HO: Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "no
radio resource available" is received from the MSC by the serving BSC for an
outgoing external TCH HO. Note : the counter will be incremented for external
TCH HO if and only if the parameter RESP_REQ is set to 1. Note: This counter
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
625 / 1392
22.4.5.3.2.4 MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX

Long Name
NB_TCH_OUT_HO_FAIL_REV_TRX
Definition

with reversion of the mobile to the old channel. Intracell, internal intercell and
external handovers are counted together. This counter takes into account
Trigger condition
1) External HO: Whenever a 44.018 HANDOVER FAILURE message is received

on Abis interface from the serving cell, during an external TCH handover. 2)
Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message is
received on Abis interface from the serving cell, during an internal inter-cell
TCH handover. 3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILURE
message is received on Abis interface on the serving channel, during an internal
intra-cell TCH handover. Note: This counter counts both inter-PLMN and
intra-PLMN handover events. Note: This counter counts handover to UMTS.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
626 / 1392
22.4.5.3.2.5 MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Long Name
NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Definition

without reversion of the mobile to the old channel (call drop). Intracell, internal
intercell and external handovers are counted together. This counter takes into
account handovers from TCH in traffic or in signaling mode. It does not take into
account DTM Assignments. MC714 = C714
Trigger condition
1) External TCH HO: Whenever the timer supervising the handover procedure on
the serving cell (T8) expires, except if a 48.008 CLEAR COMMAND with "normal
release. In such a case, the handover is considered as successful. 2) Internal
intercell TCH HO: Whenever the timer supervising the handover procedure
(T3103) expires during an internal inter-cell TCH handover. 3) Intracell TCH HO:
an internal intra-cell Note: This counter counts both inter-PLMN and intra-PLMN
handover events. Note: This counter counts hantover to UMTS
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
627 / 1392
22.4.5.3.3 Success
22.4.5.3.3.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 intercell

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 received
while T8 is running. 2) Internal inter-cell HO: whenever 44.018HANDOVER
COMPLETE is received from the MS via the target cell on the TCH channel. 3)
Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is received
from the MS via the cell on the TCH channel. Note 1: This counter counts both
inter-PLMN and intra-PLMN handover events. Note 2: This counter counts
handover to UMTS.
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
628 / 1392
22.4.5.3.3.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) handover

successes per TRX; since there are no reliable means at the target BSC to
retries are counted by this counter. MC717b = C717b
Trigger condition
1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER

COMPLETE message is received on Abis interface from the target cell for a
TCH channel. 2) Intra-cell handover: whenever an 44.018 ASSIGNMENT
COMPLETE message is received on Abis interface on the target channel. Note:
Sub Domain 1
Handover
Sub Domain 2
TCH
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
629 / 1392
22.4.6 LCS
22.4.6.1 All LCS
22.4.6.2
22.4.6.2.1 All
22.4.6.2.2
22.4.6.2.2.1 MC923c - NB_LCS_FAIL_LB
Long Name
NB_LCS_FAIL_LB
Definition
Number of LCS requests rejected by the SMLC. The failed LCS requests
indicated by the SMLC to the BSC encompass the failure to determine
geographic location estimate and the failure of LCS assistance data delivery.
Trigger condition
Whenever a 09.31 PERFORM LOCATION RESPONSE message is received

from the SMLC with the OIE LCS Cause.
Sub Domain 1
LCS
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
630 / 1392
22.4.6.2.2.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 the

BSC from the MSC while an LCS procedure is ongoing.
Sub Domain 1
LCS
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
631 / 1392
22.4.6.2.3 SCCP
22.4.6.2.3.1 MC923a - NB_LCS_REQ
Long Name
NB_LCS_REQ
Definition
Number of LCS requests received from the MSC in CS domain. The LCS
requests encompass the geographic location requests and the LCS assistance
data requests.
Trigger condition
Whenever a 48.008 PERFORM LOCATION REQUEST message is received by

the BSC from the MSC.
Sub Domain 1
LCS
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
Common cell
Type Name
Type Definition
External Comment
632 / 1392
22.4.6.2.3.2 MC923b - NB_LCS_SUCC

Long Name
NB_LCS_SUCC
Definition
Number of successful LCS requests.The successful LCS requests encompass

the successful geographic location estimate and the successful LCS assistance
data delivery.
Trigger condition
Whenever a 48.008 PERFORM LOCATION RESPONSE message is sent to the

MSC without including the OIE LCS Cause.
Sub Domain 1
LCS
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
Common cell
Type Name
Type Definition
External Comment
633 / 1392

22.4.7.2 Point to Point

22.4.7.2.1 All Point to Point
22.4.7.2.2 Failure
22.4.7.2.2.1 MC197 - NB_SMS_PP_CON_FAIL
Long Name
NB_SMS_PP_CON_FAIL
Definition
MC197=C194a+C194b+C194c+C195
Trigger condition
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
634 / 1392
22.4.7.2.3 Success
22.4.7.2.3.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 SDCCH

Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
635 / 1392
22.4.7.2.3.2 MC196 - NB_SMS_PP_CON_SUCC

Long Name
NB_SMS_PP_CON_SUCC
Definition
MC196=C190+C191+C192+C193
Trigger condition
Sub Domain 1
Sub Domain 2
Point to Point
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
636 / 1392
22.4.8 Speech
22.4.8.1 All Speech
22.4.8.2 TFO
22.4.8.2.1 All TFO
22.4.8.2.2
22.4.8.2.2.1 MC170 - NB_CALL_TFO
Long Name
NB_CALL_TFO
Definition
Number of TCHs assigned in the serving cell for which TFO has been
successfully established.
Trigger condition
(i.e. TFO = 1 in the TFO Status IE). Note 1: This counter shall be incremented
only once per assigned TCH (i.e. the first time it is received for the assigned
TCH). Note 2: A TCH is seen as assigned in the serving cell between the
sending of 48.058 CHANNEL ACTIVATION message and the receipt of the
48.058 RF CHANNEL RELEASE message. This means that the counter can
be incremented either if the TCH is assigned to serve a normal assignment or
if the TCH is assigned to serve an incoming internal (inter-cell or intra-cell) or
external handover. Note 3: MC170 = C170
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
637 / 1392
22.4.8.2.2.2 MC935 - NB_CALL_TFO_AMR_WB

Long Name
NB_CALL_TFO_AMR_WB
Definition
established.
Trigger condition
(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 assigned
TCH (i.e. the first time it is received for the assigned TCH). Note 2: A TCH is
seen as assigned in the serving cell between the sending of 48.058 CHANNEL
ACTIVATION message and the receipt of the 48.058 RF CHANNEL RELEASE
message. This means that the counter can be incremented either if the TCH is
assigned to serve a normal assignment or if the TCH is assigned to serve an
incoming internal (inter-cell or intra-cell) or external handover.
Sub Domain 1
Speech
Sub Domain 2
TFO
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
638 / 1392
22.4.9 TCH
22.4.9.1 All TCH
22.4.9.2.2.1 )
22.4.9.2.2.2 )
22.4.9.2.2.3 )
(Section 22.4.9.2.2.4 )
(Section 22.4.9.2.2.5 )
(Section 22.4.9.2.2.6 )
(Section 22.4.9.2.2.7 )
639 / 1392
22.4.9.2
22.4.9.2.1 All
22.4.9.2.2
22.4.9.2.2.1 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

cause "radio link failure" is received on Abis interface for a TCH channel (after
successful seizure). 2) Whenever an 48.058 ERROR INDICATION message
is received on Abis interface after TCH seizure and leads to a loss of call.
during the inter-cell TCH handover. 4) Whenever the timer supervising the
handover procedure on the serving cell (T8) expires during the external TCH
handover. 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 the
following condition is fulfilled: AV_RXQUAL_UL_HO <= L_RXQUAL_UL_H +
OFFSET_RXQUAL_FH And AV_RXLEV_UL_HO < L_RXLEV_UL_H Note:
"Last valid measurements" means the last received 48.058 MEASUREMENT
RESULT messages with S-BFI flag set to "0".
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
640 / 1392
22.4.9.2.2.2 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

during the inter-cell TCH handover. 4) Whenever the timer supervising the
handover procedure on the serving cell (T8) expires during the external TCH
handover. 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) is not eligible. b) and the following condition is fulfilled:
AV_RXQUAL_DL_HO > L_RXQUAL_DL_H + OFFSET_RXQUAL_FH And
AV_RXLEV_DL_HO <= RXLEV_DL_IH Note: "Last valid measurements"
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
641 / 1392
22.4.9.2.2.3 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

is received on Abis interface after TCH seizure and leads to a loss of call. 3)
the inter-cell TCH handover. 4) Whenever the timer supervising the handover
procedure on the serving cell (T8) expires during the external TCH handover.
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), Cause 4 (MC928c) and Cause 3 (MC928b) are not eligible; b) and
the following condition is fulfilled: AV_RXQUAL_DL_HO <= L_RXQUAL_DL_H
+ OFFSET_RXQUAL_FH And AV_RXLEV_DL_HO < L_RXLEV_DL_H Note:
"Last valid measurements" means the last received 48.058 MEASUREMENT
RESULT messages with S-BFI flag set to "0".
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
642 / 1392
22.4.9.2.2.4 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

(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_ADVANCE Note: "Last valid measurements" means the last received
48.058 MEASUREMENT RESULT messages with S-BFI flag set to "0".
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
643 / 1392
22.4.9.2.2.5 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

(MC928a), Cause 4 (MC928c), Cause 3 (MC928b), Cause 5 (MC928d) and
Cause 6 (MC928e) are not eligible; b) and the following condition is fulfilled:
AV_RANGE_HO <= L_TIME_ADVANCE Note: "Last valid measurements"
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
644 / 1392
22.4.9.2.2.6 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 the
uplink).
Trigger condition

during the intra-cell TCH handover. 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), Cause 4 (MC928c), Cause 3
(MC928b), Cause 5 (MC928d), Cause 6 (MC928e) and Cause 22 (MC928f) are
not eligible; b) and the following condition is fulfilled: AV_RXQUAL_UL_HO >
THR_RXQUAL_CAUSE_15 + OFFSET_RXQUAL_FH And AV_RXLEV_UL_HO
> RXLEV_UL_IH Note: "Last valid measurements" means the last received
48.058 MEASUREMENT RESULT messages with S-BFI flag set to "0".
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
645 / 1392
22.4.9.2.2.7 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 the
downlink).
Trigger condition

during the intra-cell TCH handover. 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), Cause 3 (MC928b), Cause 4
(MC928c), Cause 5 (MC928d), Cause 6 (MC928e), Cause 22 (MC928f) and
Cause 15 (MC928g) are not eligible; b) and the following condition is fulfilled:
AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 + OFFSET_RXQUAL_FH
And AV_RXLEV_DL_HO > RXLEV_DL_IH Note: "Last valid measurements"
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
646 / 1392
22.4.9.2.2.8 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), Cause
5 (Too low level in DL), Cause 6 (Too long MS-BS distance), Cause 15 (Too high
interference level on the uplink), Cause 16 (Too high interference level on the
downlink), Cause 22 (Too short MS-BS distance).
Trigger condition

procedure (T3107) expires during the intra-cell TCH handover. 5) Whenever the
timer supervising the handover procedure on the serving cell (T8) expires during
the external TCH handover. The BSC uses the last measurements received
for 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) and
Cause 16 (MC928h) are not eligible.
Sub Domain 1
TCH
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
647 / 1392

)
22.4.10.5.3.1 )
22.4.10.5.3.2 )
22.4.10.5.3.3 )
)
22.4.10.5.3.4 )
22.4.10.5.3.5 )
22.4.10.5.3.6 )
22.4.10.5.2.3 )
648 / 1392

22.4.10.5.2.6 )
22.4.10.5.2.7 )
22.4.10.2
22.4.10.2.1 All
22.4.10.2.2
22.4.10.2.2.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, a

failure or a stop.
Trigger condition
Emission of MS Suspend message by the BSC to the MFS Emission of MS

Resume message by the BSC to the MFS A suspend message received from
MS with a "suspend cause" filtered by BSC will not be counted. Stop causes
could be: 1) External handover 2) MS channel failure.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
649 / 1392
22.4.10.2.2.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 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
650 / 1392
22.4.10.2.2.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 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
651 / 1392
22.4.10.2.3 Failure
22.4.10.2.3.1 MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Long Name
NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Definition

queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced
(case QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is
started, and no free TCH can be found before timer expiry, consequently the
request is rejected (by 48.008 CLEAR REQUEST cause: "no radio resource
available"). Remark: If an internal directed retry is attempted and failed while
T11/T11_forced is running, the request is un-holded and the BSC waits for the
expiry of the relevant timer. Consequently, this counter must not be incremented
upon 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 T11
forced for a queued TCH normal assignment. Note 1: The HMI name of the
parameter QUEUE_ANYWAY is "FORCED_QUEUING". Note 2: In case of Mx
BSC, "no TCH available" could happen when the TCH processing capacity of
CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this
case, this counter and MC926 are incremented by one. Note 3: In IP mode, this
counter is increased by 1 if: - the cell mapped on a BTS is in IP congestion
Sub Domain 1
Sub Domain 2
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
652 / 1392
22.4.10.3 DTAP Assignment

22.4.10.3.1 All DTAP Assignment
22.4.10.3.2 Success
22.4.10.3.2.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.
Sub Domain 1
Sub Domain 2
DTAP Assignment
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
653 / 1392

)
22.4.10.4.2 Failure
22.4.10.4.2.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 to

congestion.
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 1
Sub Domain 2
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
654 / 1392
22.4.10.4.2.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.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
655 / 1392
22.4.10.4.3 Success
22.4.10.4.3.1 MC01 - NB_IMM_ASS_SUCC_MT
Long Name
NB_IMM_ASS_SUCC_MT
Definition
Number of immediate assignment plus SDCCH normal assignment successes

for Mobile Terminating procedure.
Trigger condition
Whenever an 48.058 ESTABLISH INDICATION message is received from

a CELL, with the L3_INFORMATION field including a 44.018 PAGING
RESPONSE message.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
656 / 1392
22.4.10.4.3.2 MC02 - NB_IMM_ASS_SUCC_MO

Long Name
NB_IMM_ASS_SUCC_MO
Definition
Number of immediate assignment successes for Mobile Originating procedure.

MC02 = C02 = C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i. The
following counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecom
procedures on SDCCH.
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
657 / 1392
22.4.10.4.3.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

cell, with the L3 INFORMATION field containing a 44.018 L3 message with an
MIE message type set to LOCATION UPDATING REQUEST and with an MIE
Location updating type not set to a RESERVED value and a bit FOR set to 0.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
658 / 1392
22.4.10.4.3.4 MC02b - NB_IMM_ASS_SUCC_MO_SMS

Long Name
NB_IMM_ASS_SUCC_MO_SMS
Definition
case: SMS procedure on SDCCH
Trigger condition

type set to "SMS". This counter is incremented only if the L3 info message
received has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
659 / 1392
22.4.10.4.3.5 MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV

Long Name
NB_IMM_ASS_SUCC_MO_SUP_SERV
Definition
case: Supplementary Service
Trigger condition

type set to "Supplementary Service". This counter is incremented only if the L3
info message received has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
660 / 1392
22.4.10.4.3.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

an MIE message type set to LOCATION UPDATING REQUEST and with an
MIE Location updating type not set to a RESERVED value and a bit FOR set
to 1. This counter is incremented only if the L3 info message received has
to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
661 / 1392
22.4.10.4.3.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

an MIE message type set to CM RE-ESTABLISHMENT REQUEST message.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
662 / 1392
22.4.10.4.3.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 Mobile

Originationg procedure, in case of L3 Info (within 48.058 ESTABLISH
INDICATION) unknown by the BSC but transferred to the MSC.
Trigger condition
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
663 / 1392
22.4.10.4.3.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 Mobile

Originationg procedure, in case of IMSI Detach Indication.
Trigger condition

CELL, with L3_INFORMATION field containing a 44.018 L3 message with
an MIE message type set to IMSI DETACH INDICATION. This counter is
incremented only if the L3 info message received has to be forwarded to the
MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
664 / 1392
22.4.10.4.3.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

CELL, with the L3 INFORMATION field containg a 44.018 L3 message with an
MIE message type set to CM SERVICE REQUEST and an MIE CM service type
set to either : - "emergency call establishment", - or "mobile originating call
establishment" This counter is incremented only if the L3 info message received
has to be forwarded to the MSC.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
665 / 1392
22.4.10.4.3.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 MIE
message type set to CM SERVICE REQUEST and with an MIE CM service type
set to "Location Services" (LCS). This counter is incremented only if the L3 info
message received has to be forwarded to the MSC
Sub Domain 1
Sub Domain 2
Sub Domain 3
Success
Measured Object
Common cell
Type Name
Type Definition
External Comment
666 / 1392

22.4.10.5.3.1 )
22.4.10.5.3.2 )
22.4.10.5.3.3 )
22.4.10.5.3.4 )
22.4.10.5.3.5 )
22.4.10.5.3.6 )
22.4.10.5.2.3 )
22.4.10.5.2.6 )
22.4.10.5.2.7 )
667 / 1392
22.4.10.5.2
22.4.10.5.2.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 FR

usage). 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 allocated
to the MS are not taken into account). In this case, the TCH is established
in signaling mode
Trigger condition
1) Whenever a 48.008 ASSIGNMENT REQUEST message for a normal

TCH assignment is received from the MSC. 2) Whenever a BSCGP DTM
ASSIGNMENT COMMAND message is received from MFS for a MS camping
on a SDCCH
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
668 / 1392
22.4.10.5.2.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 FR

usage). This counter also takes into account DTM assignment commands for
TCH establishment in signaling mode (FR usage only).
Trigger condition
1) Whenever a 44.018 ASSIGNMENT COMMAND message for a normal TCH

assignment is sent to the MS. In case of multiband cell, only the first 44.018
ASSIGNMENT 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 protocol
error unspecified in the inner zone) is not counted. 2) Whenever a 44.018
DTM ASSIGNMENT COMMAND message is sent to the MS, containing the
assignment of a TCH in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
669 / 1392
22.4.10.5.2.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 TCH

Handover/Directed Retry Requests with the ability to preempt another call with
lower priority.
Trigger condition
1) Whenever the BSC receives a 48.008 ASSIGNMENT REQUEST message

with the pre-emption capability indication set (pci bit=1 in the Priority IE),
repetitions of the ASSIGNMENT REQUEST message in case of channel
modification are not counted, or 2) Whenever the BSC receives a 48.008
HANDOVER REQUEST message requesting a TCH channel with i) the
pre-emption capability indication set (pci bit=1) and Extra Information IE (or Old
BSS 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 is
set (prec bit = 1). Note: This counter counts both inter-PLMN and intra-PLMN
handover events.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
670 / 1392
22.4.10.5.2.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 or
without using the preemption feature).
Trigger condition
Whenever the BSC has selected a channel to activate a TCH channel related
to either 48.008 ASIGNMENT REQUEST, 48.008 VGCS/VBS ASSIGNMENT
REQUEST, 48.008 HANDOVER REQUEST, 48.008 ESTABLISH INDICATION
with the L3_INFORMATION field including a 44.018 NOTIFICATION
RESPONSE message and the call has the ability to pre-empt another call with
lower priority (i.e. pci = 1).
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
671 / 1392
22.4.10.5.2.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 INDICATION

message with preemption cause is sent to the MSC.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
672 / 1392
22.4.10.5.2.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 successfully

served 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 the

serving cell during the directed retry procedure because this call has been
successfully established in the target cell.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
673 / 1392
22.4.10.5.2.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) TCH
Handover/Directed Retry Successes indicating the facility of being preempt-able
by a call with a higher priority.
Trigger condition
1) Whenever the BSC sends a 48.008 ASSIGNMENT COMPLETE message

and the context of the call indicates that the preemption vulnerability indication
is set (pvi bit=1), or 2) Whenever the BSC sends a 48.008 HANDOVER
COMPLETE message and the context of the call indicates that the preemption
vulnerability indication is set (pvi bit=1), or 3) Whenever the BSC sends a 48.008
HANDOVER PERFORMED message and the context of the call indicates that
the preemption vulnerability indication is set (pvi bit=1). Note: This counter
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
674 / 1392
22.4.10.5.2.8 MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS

Long Name
NB_TCH_NOR_ASS_PREP_FAIL_PMIS
Definition

due to A interface mismatch between the BSC and the MSC.
Trigger condition

FAILURE (cause: "circuit pool mismatch")
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
675 / 1392
22.4.10.5.3 Failure
22.4.10.5.3.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 and
the MSC.
Trigger condition
1) Whenever an 48.008 ASSIGNMENT REQUEST message selects a TTCH

which is found to be unavailable by the BSS (Blocked or Busy). 2) Whenever
a 48.008 HANDOVER REQUEST message selects a TTCH which is found to
be unavailable by the BSS (Blocked or Busy). Note: This counter counts both
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
BSC
Type Name
Type Definition
External Comment
676 / 1392
22.4.10.5.3.2 MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE

Long Name
NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE
Definition

because of the non-queuing of the ASSIGNMENT REQUEST message. Case:
48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received when
no TCH is available in the cell. The request is rejected (by 48.008ASSIGNMENT
FAILURE, cause: "no radio resource available"), because the queuing procedure
is either: 1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR
(T11_forced=0 and QUEUE_ANYWAY=1)), or 2) enabled within the BSC, i.e.
T11 <> 0, but not requested by the MSC when QUEUE_ANYWAY=0.
Trigger condition

FAILURE (cause: "no radio resource available") for a TCH channel because
no TCH is available and either the queuing is disabled in the BSC (T11=0
and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the
queuing is enabled, QUEUE_ANYWAY=0, and the MSC does not request
a queuing. Note 1: The HMI name of the parameter QUEUE_ANYWAY is
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
677 / 1392
22.4.10.5.3.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 HR

usage) is received when no TCH is available in the cell. The queuing is enabled
within the BSC, but the request is rejected (by 48.008ASSIGNMENT FAILURE,
cause: "no radio resource available"), because the queue is full and no request
of lower priority can be dequeued from the BSC queue.
Trigger condition

FAILURE (cause: "no radio resource available") for a TCH channel because the
queue is full and no request of lower priority can be de-queued. Note 1: In case
of Mx BSC, "no TCH available" could happen when the TCH processing capacity
of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In
this case, this counter and MC926 are incremented by one. Note 2: In IP mode,
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
678 / 1392
22.4.10.5.3.4 MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ

Long Name
NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Definition

queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (case
QUEUE_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 a
higher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the BSC sends
48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for the
first transaction. Remark: As soon as an internal directed retry is attempted,
the request is blocked within the BSC and cannot be dequeued by a higher
priority request.
Trigger condition
The counter is incremented upon the sending of the 48.008 ASSIGMENT

FAILURE (cause: "no radio resource available") for a de-queued TCH
request (i.e. normal assignment) due to the receipt of a higher priority
request. Note 1: The HMI name of the parameter QUEUE_ANYWAY is
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
679 / 1392
22.4.10.5.3.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 failures

due to MS access problem, per TRX. This counter also takes into account
DTM assignment -execution failures due to MS access problem for TCH
establishment in signaling mode (FR usage only). MC746b = C746b
Trigger condition
1) The timer T3107 in the BSS supervising the TCH channel seizure by the
mobile expires (following the sending of 44.018 ASSIGNMENT COMMAND for a
TCH channel that is not involved in a handover procedure). 2) The timer T3107
in the BSS supervising the TCH channel seizure by the mobile expires, following
the sending of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel in
signaling mode. 3) The BSC receives a 44.018 ASSIGNMENT FAILURE on
the old (SDCCH) channel during the normal assignment procedure except in
case of multiband cell, when the normal assignment procedure is performed
in the inner zone and the ASSIGNMENT FAILURE is received with the cause
"protocol error unspecified". 4) The BSC receives a 44.018 DTM ASSIGNMENT
FAILURE on the old (SDCCH) channel during the DTM assignment procedure,
for a TCH in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
TRX
Type Name
Type Definition
External Comment
680 / 1392
22.4.10.5.3.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
Trigger condition
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Failure
Measured Object
Common cell
Type Name
Type Definition
External Comment
681 / 1392
22.4.10.5.4 Success
22.4.10.5.4.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 TCH
establishment in signaling mode (FR usage only), for DTM. MC718 = C718
Trigger condition

interface for a TCH channel that is not involved in a handover procedure, in
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Success
Measured Object
TRX
Type Name
Type Definition
External Comment
682 / 1392

22.5.2.2.2.1 )
683 / 1392

)
)
22.5.2 Channel
22.5.2.2.2.1 )
684 / 1392

22.5.2.2 A channel
22.5.2.2.1 All A channel
22.5.2.2.2.1 )
22.5.2.2.2.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, SPC
and synchro) that are blocked or out of service.
Trigger condition
Every 20 seconds, the TTCHs that satisfy one of the following conditions are
counted : a) Maintenance state is either IN TRAFFIC or FAULTY IN TRAFFIC or
WAIT TRAFFIC CLEAR and Telephonic state is blocked b) Maintenance state
is either OPERATOR OUT OF SERVICE or FAULTY OUT OF SERVICE Note:
This counter is not incremented if the channel is in the Maintenance state NOT
EQUIPPED, or if the channel is in use for signalling (N7), for a semi-permanent
connection (SPC), or for synchronisation (channel 0).
Sub Domain 1
Channel
Sub Domain 2
A channel
Sub Domain 3
Availability
Measured Object
BSC
Type Name
Type Definition
External Comment
685 / 1392
22.5.2.2.2.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-channels

except for N7, SPC and synchro).
Trigger condition
Every 20 seconds, the TTCHs that satisfay one of the following conditions are
counted : Maintenance state is either IN TRAFFIC or FAULTY IN TRAFFIC
or WAIT TRAFFIC CLEAR and Telephonic state is available free or available
busy. Note: This counter is not incremented if the channel is in the Maintenance
state NOT EQUIPPED, or if the channel is in use for signalling (N7), for a
semi-permanent connection (SPC), or for synchronisation (channel 0).
Sub Domain 1
Channel
Sub Domain 2
A channel
Sub Domain 3
Availability
Measured Object
BSC
Type Name
Type Definition
External Comment
686 / 1392
22.5.2.3 CCCH
22.5.2.3.1 All CCCH
22.5.2.3.2.1 MC27 - AV_NB_AVAIL_CCCH
Long Name
AV_NB_AVAIL_CCCH
Definition
Average number of available CCCH channels.
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
687 / 1392
22.5.2.4 SDCCH
22.5.2.4.2
22.5.2.4.2.1 MC803 - TIME_SDCCH_CONGESTION
Long Name
TIME_SDCCH_CONGESTION
Definition
Cumulated time (in seconds) during which the SDCCH request(s) are not served
because no SDCCH sub-channel is available.
Trigger condition
The time counter is started whenever a SDCCH request cannot be served. The
time counter is stopped whenever one of the following conditions is checked: - if
a SDCCH sub-channel becomes free and usable on a static SDCCH timeslot
or on a dynamic timeslot allocated as SDCCH (i.e. when the timeslot is known
from the SDCCH_RM module). The term "usable" means here that the SDCCH
sub-channel is not mapped on a TCU in a very high overload state, or, - if a
SDCCH request is served successfully. This condition corresponds to the case
the SDCCH_RM module requests the TCH_RM module for a dynamic SDCCH
timeslot.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
688 / 1392
22.5.2.4.3.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 SDCCH

timeslots).
Trigger condition

integer value. Note: "Available" has here to be understood as the operational
state of a timeslot. The timeslot is available if it is not "blocked" or "out of
service".
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
689 / 1392
22.5.2.4.3.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

value.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
690 / 1392
22.5.2.4.4 Usage
22.5.2.4.4.1 MC31 - NB_MAX_SIMUL_BUSY_SDCCH
Long Name
NB_MAX_SIMUL_BUSY_SDCCH
Definition
Maximum number of simultaneously busy SDCCH subchannels, taking into

account the following SDCCH sub-channels: 1) Static SDCCH/x sub-channels,
2) Dynamic SDCCH sub-channels which are dynamically allocated on the
Trigger condition
At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to the cell:

C31 = MAX ["old" C31 value (i.e. before the channel activation), number of busy
SDCCH subchannels observed for the cell].
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
691 / 1392
22.5.2.4.4.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_BUSY

in type 4.
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
TRX
Type Name
Type Definition
External Comment
692 / 1392
22.5.2.4.4.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 dynamic

SDCCH/8 timeslots.
Trigger condition
The BSC takes periodically a sample of the number of busy dynamic SDCCH
sub-channels. The sampling period is set to the value indicated in the Status
Inspection field. At the expiry of the accumulation period, all samples are
averaged (i.e. summed and divided by the number of samples). The averaged
value is rounded up or down to the nearest value with an accuracy of 0.1.
A dynamic SDCCH sub-channel is considered as busy during the time it is
allocated to a given MS for SDCCH traffic. Note that the counter value that is
indicated 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). The
reported value shall then be divided by 10 afterwards so that the value that is
displayed to the end-user is the correct one
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
693 / 1392
22.5.2.4.4.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 the

Trigger condition
Whenever a dynamic SDCCH sub-channel becomes busy, the BSC determines

the current number of busy dynamic SDCCH sub-channels. Counter MC802b is
the maximum value of this number during the accumulation period.
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
694 / 1392
22.5.2.5 TCH
22.5.2.5.1 All TCH
22.5.2.5.2.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 (for
HR or FR usage) or PDCH).
Trigger condition

value. Note 1: "Available" has here to be understood as the operational state of
a timeslot. 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 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
695 / 1392
22.5.2.5.3 Usage
22.5.2.5.3.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 or

external handover requests.
Trigger condition

observations. In order to provide one decimal place, the averaged value (real)
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
696 / 1392
22.5.2.5.3.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 in

signaling mode) and busy dynamic SDCCH/8 radio timeslot allocated as TCH.
Trigger condition
and busy dynamic SDCCH/8 radio timeslots allocated as TCH. The sampling
period is set to the value indicated in the Status Inspection field. At the expiry of
the accumulation period, all samples are averaged (i.e. summed and divided
nearest value with an accuracy of 0.1. A TCH radio timeslot is considered as
busy during the time it is allocated to a given MS for TCH traffic (in HR or FR
usage). A dynamic SDCCH/8 timeslot allocated as TCH is considered as busy
during the time it is allocated to a given MS for TCH traffic. Note 1: the counter
value that is indicated 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).
The reported value shall then be divided by 10 afterwards so that the value that
is displayed to the end-user is the correct one. Note 2: This counter does not
take into account the PDCH radio timeslots allocated to the MFS.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
697 / 1392
22.5.2.5.3.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 or

FR usage, in traffic or in signaling mode) and simultaneously busy dynamic
SDCCH/8 radio timeslots allocated as TCH.
Trigger condition
Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated

as TCH becomes busy, the BSC determines the current number of busy TCH
radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslots
allocated as TCH. This counter is the maximum value of this number during
the accumulation period. This counter does not take into account the PDCHs
allocated to the MFS.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
698 / 1392
22.5.2.5.3.4 MC320a - AV_NB_IDLE_TCH_INTERF_BAND1

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
699 / 1392
22.5.2.5.3.5 MC320b - AV_NB_IDLE_TCH_INTERF_BAND2

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
700 / 1392
22.5.2.5.3.6 MC320c - AV_NB_IDLE_TCH_INTERF_BAND3

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
701 / 1392
22.5.2.5.3.7 MC320d - AV_NB_IDLE_TCH_INTERF_BAND4

Long Name
Definition
Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FR
or HR usage belonging to the interference band 4. This number is updated upon
the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
702 / 1392
22.5.2.5.3.8 MC320e - AV_NB_IDLE_TCH_INTERF_BAND5

Long Name
Definition
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
703 / 1392
22.5.2.5.3.9 MC370a - NB_TRX_FR_ALLOC

Long Name
NB_TRX_FR_ALLOC
Definition
MC370A= SUM(all TRX_TS of the TRX) (C370A)
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
TRX
Type Name
Type Definition
External Comment
704 / 1392
22.5.2.5.3.10 MC370b - NB_TRX_HR_ALLOC

Long Name
NB_TRX_HR_ALLOC
Definition
MC370B= SUM(all TRX_TS of the TRX) (C370B)
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
TRX
Type Name
Type Definition
External Comment
705 / 1392
22.5.2.5.3.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 or

HR 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/8
timeslots allocated as TCH. The sampling period is set to the value indicated in
the Status Inspection field. At the expiry of the accumulation period, all samples
are averaged (i.e. summed and divided by the number of samples). The
averaged value is rounded up or down to the nearest value with an accuracy
of 0.1. A dynamic SDCCH/8 timeslot is considered as busy and allocated as
TCH during the time it is allocated to a given MS for TCH traffic (in FR or HR
usage). Note that the counter value that is indicated 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). The reported value shall then be divided by 10
afterwards so that the value that is displayed to the end-user is the correct one
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
706 / 1392
22.5.2.5.3.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 (in

FR or HR usage). This counter takes into account TCH in traffic or in signaling
mode.
Trigger condition
Whenever a dynamic SDCCH/8 timeslot allocated as TCH becomes busy, the

BSC determines the current number of busy dynamic SDCCH/8 timeslots
allocated as TCH (in HR or FR usage). Counter MC801b is the maximum value
of this number during the accumulation period.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
707 / 1392
22.5.2.6 TRX_TS
22.5.2.6.1 All TRX_TS
22.5.2.6.2.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).
Trigger condition

integer value.
Sub Domain 1
Channel
Sub Domain 2
TRX_TS
Sub Domain 3
Availability
Measured Object
Common cell
Type Name
Type Definition
External Comment
708 / 1392
22.5.2.6.3 Usage
22.5.2.6.3.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-channel
to 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 is
occupied by the CS part of a DTM call), or ii) if the TCH sub-channel is allocated
to the MFS to carry PS traffic.
Trigger condition
The counter is started when there is no free FR TCH sub-channel to serve an

incoming FR TCH request. The counter is stopped when there is a free FR TCH
sub-channel to serve an incoming FR TCH request.
Sub Domain 1
Channel
Sub Domain 2
TRX_TS
Sub Domain 3
Usage
Measured Object
Common cell
Type Name
Type Definition
External Comment
709 / 1392
22.5.3 Interface
22.5.3.2 A
22.5.3.2.1 All A
22.5.3.2.2.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
aligned, this counter will be incremented every second.
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
Availability
Measured Object
N7 Signalling Link
Type Name
Type Definition
External Comment
710 / 1392

)
)
711 / 1392
22.5.4.2
22.5.4.2.1 All
22.5.4.2.2
22.5.4.2.2.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 or

reported as indefinite while the previous state was high. This counter shall be
incremented only if THR_CELL_LOAD_3G_REJECT < 100%.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
712 / 1392
22.5.4.3 DTM Assignment

22.5.4.3.1 All DTM Assignment
)
22.5.4.3.2
22.5.4.3.2.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 ASSIGNMENT
COMMAND message that includes the "Description of the Uplink Packet
Channel Assignment" optional IE.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
713 / 1392
22.5.4.3.2.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 ASSIGNMENT
COMMAND message that includes the "Description of the Downlink Packet
Channel Assignment" optional IE.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
714 / 1392
22.5.4.3.2.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 the

TCH (sending of Packet Assignment Command with UL TBF).
Trigger condition
Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT
message that includes the "Description of the Uplink Packet Channel
Assignment" optional IE.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
715 / 1392
22.5.4.3.2.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 the

TCH (sending of Packet Assignment Command with DL TBF).
Trigger condition
Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT
message that includes the "Description of the Downlink Packet Channel
Assignment" optional IE.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
716 / 1392
22.5.4.3.2.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 (DTM
ASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018
DTM ASSIGNMENT COMMAND message that includes the "Description of the
Uplink Packet Channel Assignment" optional IE. 2) After having sent (through
the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the
"Description of the Uplink Packet Channel Assignment" optional IE, upon T3107
expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE (on the
old channel) nor ASSIGNMENT COMPLETE (on the new channel) messages.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
717 / 1392
22.5.4.3.2.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 (DTM
ASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018
DTM ASSIGNMENT COMMAND message that includes the "Description of the
Downlink Packet Channel Assignment" optional IE. 2) After having sent (through
the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the
"Description of the Downlink Packet Channel Assignment" optional IE, upon
T3107 expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE
(on the old channel) nor ASSIGNMENT COMPLETE (on the new channel)
messages.
Sub Domain 1
Sub Domain 2
DTM Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
718 / 1392
22.5.4.4 E-GSM
22.5.4.4.1 All E-GSM
22.5.4.4.2
22.5.4.4.2.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) of

MS supporting the E-GSM band, on a CELL basis. MC706 = C706
Trigger condition
Whenever a 44.018 CLASSMARK CHANGE message in the context of any

establishment causes different from location update is received on Abis
interface with a "Mobile Station Classmark 3" or a "Mobile Station Classmark 2"
Information Element field specifying that the MS supports the E-GSM band. The
counter 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 1
Sub Domain 2
E-GSM
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
719 / 1392
22.5.4.5 Service
22.5.4.5.1 All Service
)
22.5.4.5.2
22.5.4.5.2.1 MC701a - NB_TCH_FR_REQ
Long Name
NB_TCH_FR_REQ
Definition
Number of TCH normal assignments requests from FR only mobiles (after

possible filtering from the MSC).
Trigger condition
only GSM speech coding algorithm version 1 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
720 / 1392
22.5.4.5.2.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
algorithm version 1 half rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
721 / 1392
22.5.4.5.2.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, HR

and EFR.
Trigger condition
GSM speech coding algorithm version 1 full rate, GSM speech coding algorithm
version 1 half rate and GSM speech coding algorithm version 2 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
722 / 1392
22.5.4.5.2.4 MC701d - NB_TCH_AMR_REQ

Long Name
NB_TCH_AMR_REQ
Definition
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition
GSM speech coding algorithm version 3 full rate or half rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
723 / 1392
22.5.4.5.2.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 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
724 / 1392
22.5.4.5.2.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 FR

and EFR (after possible filtering from the MSC).
Trigger condition
algorithm version 2 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
725 / 1392
22.5.4.5.2.7 MC701g - NB_TCH_NO_FR_REQ

Long Name
NB_TCH_NO_FR_REQ
Definition
Number of TCH normal assignments requests from mobiles with following

speech capability (after possible filtering of the MSC): - HR only, - EFR&HR
only, - EFR only
Trigger condition
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with:
- only GSM speech coding algorithm version 1 half rate allowed - only GSM
speech coding algorithm version 1 half rate and version 2 full rate allowed - only
GSM speech coding algorithm version 2 full rate allowed
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
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 completion 2) MS
supporting AMR and not FR are taken into account in MC701d (although such
configuration is also forbidden by 3GPP).
726 / 1392
22.5.4.5.2.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 channel

is allocated in the BSC. This counter takes into account mode modify from TCH
mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
727 / 1392
22.5.4.5.2.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 channel

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 1,
not related to handover.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
728 / 1392
22.5.4.5.2.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 - whose

signaling mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
729 / 1392
22.5.4.5.2.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 - whose

signaling mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
730 / 1392
22.5.4.5.2.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 - whose

channel is allocated in the BSC.
Trigger condition

indicating a HR channel with GSM speech coding algorithm version 3, not
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
731 / 1392
22.5.4.5.2.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 is

allocated in the BSC. This counter takes into account mode modify from TCH
mode).
Trigger condition

indicating a data call, not related to handover.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
732 / 1392
22.5.4.5.2.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 mode
modify from TCH signaling to TCH traffic (following a DTM assignment with a
TCH in signaling mode).
Trigger condition

Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
733 / 1392
22.5.4.5.2.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
GSM speech coding algorithm version 5 full rate allowed.
Sub Domain 1
Sub Domain 2
Service
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
734 / 1392
22.6 Traffic Load

22.6.5.5.2.1 )
735 / 1392

22.6.2 BSC
22.6.2.1 All BSC
22.6.2.2
22.6.2.2.1 All
22.6.2.2.2
22.6.2.2.2.1 MC926 - TCH_BLOCKING_OCCURENCES_BSC
Long Name
TCH_BLOCKING_OCCURENCES_BSC
Definition
Number of TCH channel allocation rejected for cause : Maximum TCH

processing capacity of CCP reached
Trigger condition
Whenever a TCH cannot be allocated due to the TCH processing capacity of

CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter.
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
BSC
Type Name
Type Definition
External Comment
736 / 1392
22.6.3 Channel
737 / 1392
22.6.3.2
22.6.3.2.1 All
22.6.3.2.2
22.6.3.2.2.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 not
counted).
Trigger condition
This counter is increased each time an IMMEDIATE ASSIGNMENT or

IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT
REJECT or PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK
ASSIGNMENT message is taken from one AGCH queue and put on AGCH
channel. Note: for cells mapped on non-Evolium BTS, the value of this counter
is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
738 / 1392
22.6.3.2.2.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 not
counted).
Trigger condition
This counter is increased each time a PAGING REQUEST message is taken

from one Paging_Group FIFO and put on PCH channel. Note: for cells mapped
on non-Evolium BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
739 / 1392
22.6.3.2.2.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 the
RACH_MEASUREMENTS_RESULTS message, which contains the
following information: - N_VRACH: number of Access Bursts successfully
decoded - N_BUSY: number of RACH busy slots On reception of this
message, the following counters are updated: - NB_BUSY_RACH_SLOTS =
NB_BUSY_RACH_SLOTS + N_BUSY Note: for cells mapped on non-Evolium
BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
740 / 1392
22.6.3.2.2.4 MC925d - NB_CHANNEL_RQ_RADIO

Long Name
NB_CHANNEL_RQ_RADIO
Definition
Number of channel request messages received on the radio interface or number

of access bursts successfully decoded.
Trigger condition
Each 51-multiframes the Layer 1 reports the load on the RACH via the
RACH_MEASUREMENTS_RESULTS message, which contains the
following information: - N_VRACH: number of Access Bursts successfully
decoded - N_BUSY: number of RACH busy slots On reception of this
message, the following counters are updated: - NB_CHANNEL_RQ_RADIO
= NB_CHANNEL_RQ_RADIO + N_VRACH Note: for cells mapped on
non-Evolium BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
741 / 1392
22.6.3.2.2.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 the

BTS on Abis and had to be sent for CS and PS traffic to the MS. Note: This
counter does not count what it is really sent on the interface radio on the AGCH
channel because some messages can be discarded due to congestion some
others can be merged in one message (Immediate assignment extended) and
some others sent in PCH channel when the AGCH is up to 100%.
Trigger condition
This counter is increased each time an IMMEDIATE ASSIGNMENT COMMAND

message is received on Abis interface. Note: for cells mapped on non-Evolium
BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
742 / 1392
22.6.3.2.2.6 MC925f - NB_ASSIGN_CMD_DISCARDED

Long Name
NB_ASSIGN_CMD_DISCARDED
Definition
Number of 48.058 IMMEDIATE ASSIGN COMMAND messages received by the

BTS on Abis and discarded due to congestion.
Trigger condition
This counter is increased each time an IMMEDIATE ASSIGNMENT COMMAND

messages is discarded on detection of AGCH FIFO overload. Note: for cells
mapped on non-Evolium BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
743 / 1392
22.6.3.2.2.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 be

sent for CS and PS traffic to the MS. Note: This counter does not count what it
is really sent on the PCH channel of radio interface because some messages
can be 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 time
a PAGING COMMAND message is received on Abis interface. 2) Applicable
to the BSC Evolution only: a) This counter is increased by one each time a
PAGING COMMAND message is received on Abis interface. b) This counter
is increased by "n" each time a MULTIPLE PAGING COMMAND message is
received on Abis interface ("n" is the number of PAGING COMMAND contained
in the received MULTIPLE PAGING COMMAND message). Note: for cells
mapped on non-Evolium BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
744 / 1392
22.6.3.2.2.8 MC925h - NB_PAGING_CMD_DISCARDED

Long Name
NB_PAGING_CMD_DISCARDED
Definition
Number of PAGING COMMAND received by the BTS on Abis and discarded

due to congestion.
Trigger condition
1) Applicable to the legacy BSC only: this counter is increased by one each
time a PAGING COMMAND is discarded on detection of Paging_Group FIFO
overload. 2) Applicable to the BSC Evolution only: This counter is increased
by one each time a PAGING COMMAND is discarded on detection of Paging
Group FIFO overloaded (Note 1). Note 1: It does not matter whether the
discarded (and counted) PAGING COMMAND was received in an individual
PAGING COMMAND message or if it was received (as one of several PAGING
COMMANDs) within a MULTIPLE PAGING COMMAND message. Note: for
cells mapped on non-Evolium BTS, the value of this counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
745 / 1392
22.6.3.2.2.9 MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED

Long Name
NB_ABIS_PAGING_MESSAGE_RECEIVED
Definition
Number of PAGING COMMAND / MULTIPLE PAGING COMMAND message

received by the BTS on Abis.
Trigger condition
For legacy BSC, the value of this counter shall be set to "0". For BSC
EVOLUTION: a) This counter is increased by one each time a PAGING
COMMAND message is received on Abis interface. b) This counter is increased
by one each time a MULTIPLE PAGING COMMAND message is received on
Abis interface. Note: for cells mapped on non-Evolium BTS, the value of this
counter is set to zero.
Sub Domain 1
Channel
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
746 / 1392
22.6.3.3 CCCH
22.6.3.3.1 All CCCH
22.6.3.3.2
22.6.3.3.2.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 packet
access" received by the BSS.
Trigger condition
Whenever a 48.058 CHANNEL REQUIRED message with access cause "Single

block packet access" is received on Abis interface.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
747 / 1392
22.6.3.3.2.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 packet
access with request for single timeslot uplink transmission" received by the BSS.
Trigger condition
This counter is incremented whenever a 48.058 CHANNEL REQUIRED

message with access cause "One phase packet access with request for single
timeslot uplink transmission" is received on Abis interface.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
748 / 1392
22.6.3.3.2.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 for

MS in non-DRX mode.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
749 / 1392
22.6.3.3.2.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 for

MS in DRX mode.
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
750 / 1392
22.6.3.3.2.5 MC8a - NB_CELL_PAGING_CMD

Long Name
NB_CELL_PAGING_CMD
Definition
MC8A= SUM (all TRX_TS of the Cell) C8A
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
751 / 1392
22.6.3.3.2.6 MC8b - NB_CELL_IMM_ASS_CMD

Long Name
NB_CELL_IMM_ASS_CMD
Definition
MC8B= SUM (all TRX_TS of the Cell) C8B
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
752 / 1392
22.6.3.3.2.7 MC8c - NB_CELL_CHAN_REQD

Long Name
NB_CELL_CHAN_REQD
Definition
MC8C= SUM (all TRX_TS of the cell) C8C
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
753 / 1392
22.6.3.3.2.8 MC8d - NB_CELL_IMM_ASS_REJ

Long Name
NB_CELL_IMM_ASS_REJ
Definition
MC8D= SUM (all TRX_TS of the cell) C8D
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
CCCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
754 / 1392
22.6.3.4 SDCCH
22.6.3.4.2
22.6.3.4.2.1 MC400 - TIME_TRX_SDCCH_BUSY
Long Name
TIME_TRX_SDCCH_BUSY
Definition
MC400= SUM (all TRX_TS of the TRX) C40
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
SDCCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
755 / 1392
22.6.3.5 TCH
22.6.3.5.1 All TCH
22.6.3.5.2
22.6.3.5.2.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 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
756 / 1392
22.6.3.5.2.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 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
757 / 1392
22.6.3.5.2.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/8
timeslot in the GSM frequency band is busy in FR usage. This counter takes
into account TCH in traffic or in signaling mode.
Trigger condition
times during which the TCH FR channel in the GSM frequency band is busy. For
each channel allocation: The counter starts being incremented after the sending
of the 48.058 CHANNEL ACTIVATION message to the cell concerning a full rate
TCH channel for the related TRX timeslot. The counter stops being incremented
after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGE
message or the expiry of timer T_RCR_ACK twice (after the sending of the
48.058 RF CHANNEL RELEASE message) concerning the TCH channel
previously activated on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
758 / 1392
22.6.3.5.2.4 MC380d - TIME_TRX_GSM_HR_BUSY

Long Name
TIME_TRX_GSM_HR_BUSY
Definition
timeslot in the GSM frequency band is busy in HR usage.
Trigger condition
times during which the TCH HR channel in the GSM frequency band is busy.
For each channel allocation: The counter starts being incremented after the
sending of the 48.058 CHANNEL ACTIVATION message to the cell concerning
a half rate TCH channel for the related TRX timeslot. The counter stops
being incremented after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the
sending of the 48.058 RF CHANNEL RELEASE message) concerning the TCH
channel previously activated on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
759 / 1392
22.6.3.5.2.5 MC380e - TIME_TRX_DCS_FR_BUSY

Long Name
TIME_TRX_DCS_FR_BUSY
Definition
timeslot in the DCS/PCS frequency band is busy in FR usage. This counter
takes into account TCH in traffic or in signaling mode.
Trigger condition
The counter cumulates over the Accumulation Period, per radio timeslot, all
unit times during which the TCH FR channel in the DCS/PCS frequency band
is busy. For each channel allocation: The counter starts being incremented
after the sending of the 48.058 CHANNEL ACTIVATION message to the
cell concerning a full rate TCH channel for the related TRX timeslot. The
counter stops being incremented after the reception of a 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice
(after the sending of the 48.058 RF CHANNEL RELEASE message) concerning
the TCH channel previously activated on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
760 / 1392
22.6.3.5.2.6 MC380f - TIME_TRX_DCS_HR_BUSY

Long Name
TIME_TRX_DCS_HR_BUSY
Definition
timeslot in the DCS/PCS frequency band is busy in HR usage.
Trigger condition
The counter cumulates over the Accumulation Period, per radio timeslot, all
unit times during which the TCH HR channel in the DCS/PCS frequency band
is busy. For each channel allocation: The counter starts being incremented
after the sending of the 48.058 CHANNEL ACTIVATION message to the
cell concerning a half rate TCH channel for the related TRX timeslot. The
counter stops being incremented after the reception of a 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice
(after the sending of the 48.058 RF CHANNEL RELEASE message) concerning
the TCH channel previously activated on the related TRX timeslot.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
761 / 1392
22.6.3.5.2.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)
Trigger condition
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
762 / 1392
22.6.3.5.2.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 situation
impacts 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 equal

or below MAX_SPDCH_HIGH_LOAD. MAX_SPDCH_HIGH_LOAD is calculated
by the BSC based on MAX_PDCH_HIGH_LOAD and NB_TS_MPDCH O&M
parameters. The timer stops when MAX_SPDCH_LIMIT is greater than
MAX_SPDCH_HIGH_LOAD.
Sub Domain 1
Channel
Sub Domain 2
TCH
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
This counter replaces the B8 MFS counter P1.
763 / 1392
22.6.4 Interface
22.6.4.2 A
22.6.4.2.1 All A
22.6.4.2.2 SCCP
22.6.4.2.2.1 MC350 - NB_N7_CON_REQ
Long Name
NB_N7_CON_REQ
Definition
MC350=C253+C254
Trigger condition
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
Type Definition
External Comment
764 / 1392
22.6.4.2.2.2 MC351 - NB_N7_CON_CONF

Long Name
NB_N7_CON_CONF
Definition
MC351=C255+C256
Trigger condition
Sub Domain 1
Interface
Sub Domain 2
Sub Domain 3
SCCP
Measured Object
N7 Signalling Link
Type Name
Type Definition
External Comment
765 / 1392

22.6.5.5.2.1 )
22.6.5.2 Directed Retry

22.6.5.2.1 All Directed Retry
22.6.5.2.2 External
22.6.5.2.2.1 MC144f - NB_OUT_EDR_REQ
Long Name
NB_OUT_EDR_REQ
Definition
MC144f=C144b+C144d
Trigger condition
Sub Domain 1
Sub Domain 2
Directed Retry
Sub Domain 3
External
Measured Object
Common cell
Type Name
Type Definition
External Comment
766 / 1392
22.6.5.2.3 Internal
22.6.5.2.3.1 MC144e - NB_OUT_IDR_REQ
Long Name
NB_OUT_IDR_REQ
Definition
MC144e=C144a+C144c
Trigger condition
Sub Domain 1
Sub Domain 2
Directed Retry
Sub Domain 3
Internal
Measured Object
Common cell
Type Name
Type Definition
External Comment
767 / 1392
22.6.5.2.3.2 MC15a - NB_INC_IDR_ALLOC

Long Name
NB_INC_IDR_ALLOC
Definition
MC15a=C15a, Number of incoming internal directed retry (towards a TCH

channel in HR or FR usage) whose target channel is allocated by the BSC.
Trigger condition
ACTIVATION message of a TCH channel is about to be sent during an internal
directed retry.
Sub Domain 1
Sub Domain 2
Directed Retry
Sub Domain 3
Internal
Measured Object
Common cell
Type Name
Type Definition
External Comment
768 / 1392
22.6.5.3 Handover
22.6.5.3.1 All Handover
22.6.5.3.2 SDCCH
22.6.5.3.2.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

Abis Interface to activate an SDCCH channel for any handover purposes. Note:
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
SDCCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
769 / 1392
22.6.5.3.3 TCH
22.6.5.3.3.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 that

are put in BSC queue
Trigger condition
Further to the receipt of a 48.008 HANDOVER REQUEST message for TCH,

the counter is incremented: i) upon the sending of a 48.008 QUEUING
the handover request is queued in the cell if the queuing is not authorised by
the MSC and the request has its pre-emption indicator set (provided that the
flag EN_TCH_PREEMPT is set to Enable). Note: MC13b = C13b Note: This
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
TCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
770 / 1392
22.6.5.3.3.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
means at the target BSC to distinguish external directed retry from external
handover, the external directed retries are counted by this counter.
Trigger condition
ACTIVATION message of a TCH channel is about to be sent during any
handover procedure. Note: This counter counts both inter-PLMN and
Sub Domain 1
Sub Domain 2
Handover
Sub Domain 3
TCH
Measured Object
Common cell
Type Name
Type Definition
External Comment
771 / 1392

22.6.5.4.2
22.6.5.4.2.1 MC148 - NB_IMM_ASS_ALLOC
Long Name
NB_IMM_ASS_ALLOC
Definition
Number of immediate assignment plus SDCCH normal assignments -whose

SDCCH channel is allocated by the BSC.
Trigger condition
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent

on Abis Interface to activate an SDCCH channel for any purpose other than
handover.
Sub Domain 1
Sub Domain 2
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
772 / 1392
22.6.5.5 Multiband
22.6.5.5.1 All Multiband
22.6.5.5.2.1 )
22.6.5.5.2
22.6.5.5.2.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 cell
basis. A MS is considered as multiband if it supports: - the P-GSM (or E-GSM
bands".
Trigger condition
Whenever a 44.018 Classmark Change message in the context of any

establishment cause different from location update is received on Abis
interface from the MS with a "Mobile Station Classmark 3" Information Element
bands". The counter 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 1
Sub Domain 2
Multiband
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
773 / 1392

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

put in BSC queue.
Trigger condition
Further to the receipt of a 48.008 ASSIGNMENT REQUEST message for

TCH, the counter is incremented: i) upon the sending of a 48.008 QUEUING
the assignment request is queued in the cell if the queuing is not authorised
by the MSC and the parameter QUEUE_ANYWAY is set, or, iii) when the
assignment request is queued in the cell if the queuing is not authorised by the
MSC and the request has its pre-emption indicator set (provided that the flag
EN_TCH_PREEMPT is set to Enable). Note 1: MC13a = C13a Note 2: The
HMI name of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
Common cell
Type Name
Type Definition
External Comment
774 / 1392
22.6.5.6.2.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 channel

is allocated in the BSC, per TRX. This counter also takes into account normal
assignment whose RTCH channel is allocated in the BSC in signaling mode (FR
usage only), for DTM. MC703 = C703
Trigger condition

Abis Interface to activate a TCH channel for normal assignment, or for DTM
assignment with a TCH in signaling mode.
Sub Domain 1
Sub Domain 2
Normal Assignment
Sub Domain 3
Measured Object
TRX
Type Name
Type Definition
External Comment
775 / 1392
776 / 1392
23 BSC-TYPE 180 - 2G Traffic flow measurements
777 / 1392
23.1 All TYPE 180

C400 - NB_ADJ_BSC_INC_HO_REQ (Section 23.2.2.2.2.1 )
C401 - NB_ADJ_BSC_INC_HO_ATPT (Section 23.2.2.2.2.2 )
C402 - NB_ADJ_BSC_INC_HO_SUCC (Section 23.2.2.2.2.3 )
23.2 Adjacency
23.2.2 BSC
23.2.2.1 All BSC
778 / 1392
23.2.2.2
23.2.2.2.1 All
23.2.2.2.2
23.2.2.2.2.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 (in

HR or FR usage) handover requests. The internal and external directed retries
are counted.
Trigger condition
1) Internal handover : whenever an internal inter-cell SDCCH or TCH handover

is initiated by the handover process within the BSC from the serving cell to the
target cell. 2) External handover : 48.008 HANDOVER REQUEST received
(including the MIE "Cell identifier" of the serving cell) by the BSC for an SDCCH
or TCH external handover towards the target cell. Only handovers from a 2G cell
shall be taken 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).
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
2G Traffic flow measurements
Type Definition
Set of incoming external or internal inter-cell SDCCH or TCH (in HR or FR

usage) handover counters provided per adjacency: variable serving cell variable target cell. The internal and external directed retries are counted. Only
handovers / directed retries from 2G cells are taken into account (i.e. handovers
from 3G are not counted in type 180).
External Comment
779 / 1392
23.2.2.2.2.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 (in

HR or FR usage) handover attempts. The internal and external directed retries
are counted.
Trigger condition
1) Internal handover : 44.018 HANDOVER COMMAND sent to the MS via the

serving cell for an internal inter-cell SDCCH or TCH handover towards the target
cell. 2) External handover : 48.008 HANDOVER REQUEST ACK sent to the
MSC from the target BSC for an external SDCCH or TCH handover from the
serving cell to the target cell. The MIE "Cell-Identifier" of the serving cell&target
cell are provided in 48.008 HANDOVER REQUEST. Only handovers from a
handover events.
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
780 / 1392
23.2.2.2.2.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 directed
retries are counted.
Trigger condition
44.018HANDOVER_COMPLETE message received from the MS via the target

cell for an external or internal inter-cell SDCCH or TCH handover from the
serving cell. Only handovers from a 2G cell shall be taken into account (if the
Sub Domain 1
BSC
Sub Domain 2
Sub Domain 3
Measured Object
Adjacency-CGI
Type Name
Type Definition

External Comment
781 / 1392
782 / 1392
24 MFS-GPRS Counters
783 / 1392
24.1 All MFS-GPRS

P10 - NB_DL_LLC_BYTES_DISC_CONG (Section 24.4.4.3.2.1 )
P100c - CUMULATED_TIME_BUSY_GCH_CELL (Section 24.3.3.2.2.1 )
P100d - MAX_NB_BUSY_GCH_CELL (Section 24.3.3.2.2.2 )
P100e - MIN_NB_BUSY_GCH_CELL (Section 24.3.3.2.2.3 )
P100f - MAX_NB_GCH_BUSY_GPU (Section 24.3.3.2.2.4 )
P101 - CUMULATED_TIME_AVAIL_GCH_GPU (Section 24.3.3.2.2.5 )
P103 - NB_ERROR_UL_GCH_FRAME (Section 24.4.2.2.2.1 )
P104 - NB_LLC_PDU_GPU (Section 24.4.4.6.2.1 )
P105c - NB_DL_TBF_EST_FAIL_GPU_CONG (Section 24.2.4.5.2.1 )
P105d - NB_UL_TBF_EST_FAIL_GPU_CONG (Section 24.2.4.14.2.1 )
P105e - NB_DL_TBF_EST_FAIL_CPU_GPU (Section 24.2.4.5.2.2 )
P105f - NB_UL_TBF_EST_FAIL_CPU_GPU (Section 24.2.4.14.2.2 )
P105g - NB_DL_TBF_EST_FAIL_CONG_ATER (Section 24.2.4.5.2.3 )
P105h - NB_UL_TBF_EST_FAIL_CONG_ATER (Section 24.2.4.14.2.3 )
P105i - NB_DL_TBF_EST_FAIL_CONG_ABIS (Section 24.2.4.5.2.4 )
P105j - NB_UL_TBF_EST_FAIL_CONG_ABIS (Section 24.2.4.14.2.4 )
P105k - NB_DL_TBF_EST_FAIL_TOO_MANY_TBF (Section 24.2.4.5.2.5 )
P105l - NB_UL_TBF_EST_FAIL_TOO_MANY_TBF (Section 24.2.4.14.2.5 )
P106 - NB_TBF_EST_SUCC_GPU (Section 24.2.4.8.2.1 )
P107 - NB_TBF_EST_REQ_GPU (Section 24.2.4.8.2.2 )
P11 - NB_DL_TBF_REL_GB_PB_MStransDL (Section 24.2.4.7.2.1 )
P129a - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_ACK
(Section 24.3.5.9.2.1 )
P129b - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_NACK
(Section 24.3.5.9.2.2 )
P129c - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_ACK
(Section 24.3.5.9.2.3 )
P129d - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_NACK
(Section 24.3.5.9.2.4 )
P13 - TIME_DL_PDCH_CONG (Section 24.3.5.5.2.1 )
P14 - NB_DL_TBF_EST_FAIL_CONG (Section 24.2.4.5.2.6 )
P146 - NB_DL_TBF_REL_PREEMPTradio (Section 24.2.4.7.2.2 )
P147 - NB_UL_TBF_REL_PREEMPTradio (Section 24.2.4.16.2.1 )
P15 - NB_DL_TBF_EST_FAIL_RADIO_PB (Section 24.2.4.5.2.7 )
P16 - CUMULATED_OVERALL_DL_CONNECTION_TIME (Section
24.3.5.3.2.1 )
P160 - NB_DL_TBF_1_succ (Section 24.3.5.6.2.1 )
P161 - NB_UL_TBF_1_succ (Section 24.3.5.7.2.1 )
P162 - NB_DL_TBF_2_3_succ (Section 24.3.5.6.2.2 )
784 / 1392
P163 - NB_UL_TBF_2_3_succ (Section 24.3.5.7.2.2 )

P200 - NB_DOWNGRADED_MOVING_RT_PFC (Section 24.2.4.12.2.1 )
P201 - TIME_PTU_CPU_DSP_LOAD (Section 24.4.4.6.2.2 )
P202 - TIME_PTU_CPU_DSP_OVERLOAD (Section 24.4.4.6.2.3 )
P203 - NB_DL_TBF_EST_FAIL_PTU_DSP_LOAD (Section 24.2.4.5.2.8 )
P204 - NB_UL_TBF_EST_FAIL_PTU_DSP_LOAD (Section 24.2.4.14.2.6 )
P207 - NB_DL_TBF_REL_DL_DELAYED (Section 24.2.4.7.2.3 )
P208 - NB_UL_TBF_REL_EXTENDED_UL (Section 24.2.4.16.2.2 )
P209 - TIME_SOURCE_NC2_CELL_RESEL (Section 24.2.4.4.2.1 )
P20a - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1 (Section 24.4.4.5.2.1 )
P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2 (Section 24.4.4.5.2.2 )
P20c - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3 (Section 24.4.4.5.2.3 )
P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4 (Section 24.4.4.5.2.4 )
P20f - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1 (Section 24.4.4.5.2.5
)
P20g - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2 (Section 24.4.4.5.2.6
)
P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3 (Section 24.4.4.5.2.7
)
P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4 (Section 24.4.4.5.2.8
)
P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5 (Section 24.4.4.5.2.9
)
P20k - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6 (Section
24.4.4.5.2.10 )
P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7 (Section
24.4.4.5.2.11 )
P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8 (Section
24.4.4.5.2.12 )
P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9 (Section
24.4.4.5.2.13 )
P210 - TIME_TARGET_NC2_CELL_RESEL (Section 24.2.4.4.2.2 )
P211 - NB_TARGET_NC2_CELL_RESEL (Section 24.2.4.4.2.3 )
P212 - TIME_SOURCE_NACC_CELL_RESEL (Section 24.2.4.2.2.1 )
P213 - NB_SOURCE_NACC_CELL_RESEL (Section 24.2.4.2.2.2 )
P214 - NB_UL_TBF_ENT_EXTENDED_UPLINK (Section 24.2.4.14.2.7 )
P215 - NB_UL_TBF_RESUME_IN_EXTENDED_UPLINK (Section
24.2.4.14.2.8 )
P21a - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1 (Section 24.4.4.15.2.1
)
785 / 1392
P21b - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2 (Section 24.4.4.15.2.2

)
P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3 (Section 24.4.4.15.2.3
)
P21d - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4 (Section 24.4.4.15.2.4
)
P21f - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1 (Section
24.4.4.15.2.5 )
P21g - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2 (Section
24.4.4.15.2.6 )
P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3 (Section
24.4.4.15.2.7 )
P21i - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4 (Section
24.4.4.15.2.8 )
P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5 (Section
24.4.4.15.2.9 )
P21k - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6 (Section
24.4.4.15.2.10 )
P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7 (Section
24.4.4.15.2.11 )
P21m - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8 (Section
24.4.4.15.2.12 )
P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9 (Section
24.4.4.15.2.13 )
P22 - NB_UL_TBF_NORM_REL (Section 24.2.4.16.2.3 )
P220 - NB_MOVING_RT_PFC (Section 24.2.4.12.2.2 )
P221 - NB_PCCO_ACK_UL_NC2_CELL_RESEL (Section 24.2.4.4.2.4 )
P222 - NB_PCCO_ACK_DL_NC2_CELL_RESEL (Section 24.2.4.4.2.5 )
P223 - NB_PCCO_NC2_CELL_RESEL_DL_TBF (Section 24.2.4.4.2.6 )
P224 - NB_FLUSH_NC2_CELL_RESEL_DL_TBF (Section 24.2.4.4.2.7 )
P225 - NB_PCCF_NC2_CELL_RESEL_DL_TBF (Section 24.2.4.4.2.8 )
P226 - NB_PCCO_NC2_CELL_RESEL_UL_TBF (Section 24.2.4.4.2.9 )
P227 - NB_FLUSH_NC2_CELL_RESEL_UL_TBF (Section 24.2.4.4.2.10 )
P228 - NB_PCCF_NC2_CELL_RESEL_UL_TBF (Section 24.2.4.4.2.11 )
P229 - NB_RT_PFC_PREEMPTED (Section 24.2.4.12.2.3 )
P23 - NB_UL_LLC_BYTES_DISC_CONG (Section 24.4.4.13.2.1 )
P231 - NB_DOWNGRADED_RT_PFC_DEFENCE (Section 24.2.4.12.2.4 )
P232 - NB_MOVING_RT_PFC_TARGET (Section 24.2.4.12.2.5 )
P24 - NB_UL_TBF_REL_GB_PB_MStransUL (Section 24.2.4.16.2.4 )
P26 - TIME_UL_PDCH_CONG (Section 24.3.5.5.2.2 )
P27 - NB_UL_TBF_EST_FAIL_CONG (Section 24.2.4.14.2.9 )
P28 - NB_UL_TBF_EST_FAIL_RADIO_PB (Section 24.2.4.14.2.10 )
P2a - NB_LAPD_INFO_FRAME_RESENT (Section 24.2.2.2.2.1 )
786 / 1392
P2b - NB_LAPD_RNR_SENT (Section 24.2.2.2.2.2 )

P2c - NB_LAPD_RNR_REC (Section 24.2.2.2.2.3 )
P2d - NB_LAPD_EST (Section 24.2.2.2.2.4 )
P302b_1 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105 (Section
24.2.4.7.2.4 )
P302b_2 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF (Section
24.2.4.7.2.5 )
P302c_1 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101 (Section
24.2.4.16.2.5 )
24.2.4.16.2.6 )
P302c_3 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF (Section
24.2.4.16.2.7 )
P302c_4 NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM
(Section 24.2.4.16.2.8 )
P303a - NB_ABNORMAL_DL_TBF_REL (Section 24.2.4.7.2.6 )
P303b - NB_ABNORMAL_UL_TBF_REL (Section 24.2.4.16.2.9 )
P30a - NB_UL_TBF_EST_SUCC_MSidle_MastChan (Section 24.2.4.14.2.11 )
P30b - NB_UL_TBF_EST_SUCC_MStransDL (Section 24.2.4.14.2.12 )
P30c - NB_UL_TBF_EST_SUCC_MSidle_NO_MastChan (Section
24.2.4.14.2.13 )
P30d - NB_UL_TBF_EST_SUCC_EGPRS_PIM (Section 24.3.5.7.2.4 )
P310a - NB_STALL_IND_MS_GPRS (Section 24.4.4.7.2.1 )
P310b - NB_STALL_IND_MS_EGPRS (Section 24.4.4.7.2.2 )
P310c - NB_STALL_STATE_GPRS_DL_TBF (Section 24.4.4.7.2.3 )
P310d - NB_STALL_STATE_EGPRS_DL_TBF (Section 24.4.4.7.2.4 )
P32 - TIME_LAPD_NOT_AVAIL (Section 24.3.3.3.2.1 )
P33 - TIME_BEAR_CHAN_NOT_AVAIL (Section 24.3.4.2.2.1 )
P335 - AV_DL_TX_EFF_GPRS (Section 24.4.4.7.2.5 )
P336 - AV_UL_TX_EFF_GPRS (Section 24.4.4.7.2.6 )
P34 - TIME_PVC_NOT_AVAIL (Section 24.3.4.4.2.1 )
P34a - TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP (Section 24.3.4.5.2.1 )
P35 - MAX_NB_DL_TBF_SIMUL_EST (Section 24.3.5.6.2.4 )
P350a - NB_DL_RADIO_BLOCK_PDTCH (Section 24.4.4.5.2.14 )
P350b - NB_UL_RADIO_BLOCK_PDTCH (Section 24.4.4.15.2.14 )
P351a - NB_DL_CS_ADAPT_INCREASE (Section 24.4.4.7.2.7 )
P351b - NB_DL_CS_ADAPT_DECREASE (Section 24.4.4.7.2.8 )
P352a - NB_UL_CS_ADAPT_INCREASE (Section 24.4.4.7.2.9 )
P352b - NB_UL_CS_ADAPT_DECREASE (Section 24.4.4.7.2.10 )
P36 - AV_NB_DL_TBF_SIMUL_EST (Section 24.3.5.6.2.5 )
787 / 1392
P383a - TIME_ATERMUX_CONG (Section 24.3.3.2.2.6 )

P383b - TIME_HIGH_ATER_USAGE (Section 24.3.3.2.2.7 )
P384 - Time_DSP_Cong (Section 24.4.4.6.2.4 )
P385a - NB_DL_TBF_REL_STAGWINDOW (Section 24.2.4.7.2.7 )
P385b - NB_UL_TBF_REL_STAGWINDOW (Section 24.2.4.16.2.10 )
P38b - CUMULATED_TIME_PDCH_USED (Section 24.3.5.5.2.3 )
P38c - CUMULATED_TIME_PDCH_USED_EGPRS (Section 24.3.5.5.2.4 )
P38e - CUMULATED_TIME_PDCH_USED_DL_CELL (Section 24.3.5.5.2.5 )
P38f - CUMULATED_TIME_PDCH_USED_UL_CELL (Section 24.3.5.5.2.6 )
P39 - MAX_NB_UL_TBF_SIMUL_EST (Section 24.3.5.7.2.5 )
P391a - NB_PS_PAGING_REQ_GPU (Section 24.4.4.6.2.5 )
P391b - NB_CS_PAGING_REQ_GPU (Section 24.4.4.6.2.6 )
P392a - AV_NB_MS_CONTEXTS (Section 24.4.4.6.2.7 )
P392b - MAX_NB_MS_CONTEXTS (Section 24.4.4.6.2.8 )
P396a - NB_RLC_DL_TBF_RELEASE_REQ_FOR_CR (Section 24.2.4.7.2.8 )
P396b - NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR (Section 24.2.4.16.2.11
)
P397 - NB_FLUSH_MESSAGES (Section 24.2.4.3.2.1 )
P399 - SIG_BLKS_PRACH_LOAD (Section 24.4.4.12.2.1 )
P3a - NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS (Section 24.2.3.2.2.1
)
P3b - NB_BEAR_CHAN_FRAMES_DISC_INVALID_ADDR (Section
24.2.3.2.2.2 )
P4 - TIME_PVC_CONG_FRAME_RELAY (Section 24.3.4.4.2.2 )
P40 - AV_NB_UL_TBF_SIMUL_EST (Section 24.3.5.7.2.6 )
P400 - SIG_BLKS_PAGCH_LOAD (Section 24.4.4.9.2.1 )
P401 - SIG_BLKS_PACCH_UL_LOAD (Section 24.4.4.14.2.1 )
P402 - TIME_PMU_OVERLOAD (Section 24.4.4.6.2.9 )
P403a - NB_DL_RES_REALLOC_REQ_T1 (Section 24.2.4.6.2.1 )
P403b - NB_DL_RES_REALLOC_REQ_T2 (Section 24.2.4.6.3.1 )
P403c - NB_DL_RES_REALLOC_REQ_T3 (Section 24.2.4.6.4.1 )
P403d - NB_DL_RES_REALLOC_REQ_T4 (Section 24.2.4.6.5.1 )
P404a - NB_UL_RES_REALLOC_REQ_T1 (Section 24.2.4.15.2.1 )
P404b - NB_UL_RES_REALLOC_REQ_T2 (Section 24.2.4.15.3.1 )
P404c - NB_UL_RES_REALLOC_REQ_T3 (Section 24.2.4.15.4.1 )
P404d - NB_UL_RES_REALLOC_REQ_T4 (Section 24.2.4.15.5.1 )
P405a - NB_DL_RES_REALLOC_SUCC_T1 (Section 24.2.4.6.2.2 )
P405b - NB_DL_RES_REALLOC_SUCC_T2 (Section 24.2.4.6.3.2 )
P405c - NB_DL_RES_REALLOC_SUCC_T3 (Section 24.2.4.6.4.2 )
P405d - NB_DL_RES_REALLOC_SUCC_T4 (Section 24.2.4.6.5.2 )
788 / 1392
P406a - NB_UL_RES_REALLOC_SUCC_T1 (Section 24.2.4.15.2.2 )

P406b - NB_UL_RES_REALLOC_SUCC_T2 (Section 24.2.4.15.3.2 )
P406c - NB_UL_RES_REALLOC_SUCC_T3 (Section 24.2.4.15.4.2 )
P406d - NB_UL_RES_REALLOC_SUCC_T4 (Section 24.2.4.15.5.2 )
P407a - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T1 (Section
24.2.4.6.2.3 )
P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2 (Section
24.2.4.6.3.3 )
P407c - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3 (Section
24.2.4.6.4.3 )
P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4 (Section
24.2.4.6.5.3 )
P408a - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T1 (Section
24.2.4.15.2.3 )
P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2 (Section
24.2.4.15.3.3 )
P408c - NB_UL_TBF_RADIO_PB_RES_REALLOC_T3 (Section 24.2.4.15.4.3 )
P408d - NB_UL_TBF_RADIO_PB_RES_REALLOC_T4 (Section 24.2.4.15.5.3
)
P409 - CUMULATED_TIME_DL_BIASED_AND_OPTIMAL_DL_ALLOCATION
(Section 24.3.5.3.2.2 )
P41 - NB_KBYTES_SENT_TO_BSC (Section 24.4.2.3.2.1 )
P410 - CUMULATED_TIME_UL_BIASED_AND_OPTIMAL_UL_ALLOCATION
(Section 24.3.5.9.2.5 )
P411 - CUMULATED_TIME_DL_BIASED_DL_TBF (Section 24.3.5.3.2.3 )
P412 - CUMULATED_TIME_UL_BIASED_UL_TBF (Section 24.3.5.9.2.6 )
P413 - NB_GPRS_SESSIONS (Section 24.4.4.6.2.10 )
P414bis - CUMULATED_TIME_ALLOCATED_SPDCH (Section 24.3.5.5.2.7 )
P415bis - MAX_OF_ALLOCATED_SPDCH (Section 24.3.5.5.2.8 )
P416bis - MIN_OF_ALLOCATED_SPDCH (Section 24.3.5.5.2.9 )
P417 - NB_PREEMPTED_PDCH (Section 24.3.5.5.2.10 )
P419 - CUMULATED_TIME_DL_BIASED (Section 24.3.5.3.2.4 )
P42 - NB_KBYTES_RECEIVED_FROM_BSC (Section 24.4.2.3.2.2 )
P420 - CUMULATED_TIME_UL_BIASED (Section 24.3.5.9.2.7 )
P421 - NB_DUMMY_RLC_DATA_BLOCKS (Section 24.4.4.5.2.15 )
P422 - NB_DL_TBF_TRANSFER_RESUMPTION_IN_DELAYED_REL_STATE
(Section 24.2.4.5.2.9 )
P423a - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1 (Section
24.2.4.6.2.4 )
P423b - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2 (Section
24.2.4.6.3.4 )
P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3 (Section
24.2.4.6.4.4 )
789 / 1392
P423d - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4 (Section

24.2.4.6.5.4 )
P424a - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1 (Section
24.2.4.15.2.4 )
P424b - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2 (Section
24.2.4.15.3.4 )
P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3 (Section
24.2.4.15.4.4 )
P424d - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4 (Section
24.2.4.15.5.4 )
P425a - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1 (Section
24.2.4.6.2.5 )
P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2 (Section
24.2.4.6.3.5 )
P425c - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3 (Section
24.2.4.6.4.5 )
P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4 (Section
24.2.4.6.5.5 )
P426a - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1 (Section
24.2.4.15.2.5 )
P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2 (Section
24.2.4.15.3.5 )
P426c - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3 (Section
24.2.4.15.4.5 )
P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4 (Section
24.2.4.15.5.5 )
P43 - NB_DL_LLC_BYTES (Section 24.4.3.2.2.1 )
P431b - MAX_SOURCE_NC2_CELL_RESEL_TIME (Section 24.2.4.4.2.12 )
P431c - MIN_SOURCE_NC2_CELL_RESEL_TIME (Section 24.2.4.4.2.13 )
P432b - MAX_TARGET_NC2_CELL_RESEL_TIME (Section 24.2.4.4.2.14 )
P432c - MIN_TARGET_NC2_CELL_RESEL_TIME (Section 24.2.4.4.2.15 )
P433a - NB_NC2_CELL_RESEL_REQ_PT1 (Section 24.2.4.4.2.16 )
P433b - NB_NC2_CELL_RESEL_REQ_PT2 (Section 24.2.4.4.2.17 )
P433c - NB_NC2_CELL_RESEL_REQ_PT3 (Section 24.2.4.4.2.18 )
P433d - NB_NC2_CELL_RESEL_REQ_PT4 (Section 24.2.4.4.2.19 )
P434a - NB_NC2_UL_TBF_RELEASE (Section 24.2.4.16.2.12 )
P434b - NB_NC2_DL_TBF_RELEASE (Section 24.2.4.7.2.9 )
P434c - NB_NC0_UL_TBF_RELEASE (Section 24.2.4.16.2.13 )
P434d - NB_NC0_DL_TBF_RELEASE (Section 24.2.4.7.2.10 )
P435a - NB_NC2_CELL_RESEL_SUCC_PT1 (Section 24.2.4.4.2.20 )
P435b - NB_NC2_CELL_RESEL_SUCC_PT2 (Section 24.2.4.4.2.21 )
P435c - NB_NC2_CELL_RESEL_SUCC_PT3 (Section 24.2.4.4.2.22 )
P435d - NB_NC2_CELL_RESEL_SUCC_PT4 (Section 24.2.4.4.2.23 )
790 / 1392
P436 - NB_NC0_CELL_RESEL_Mstrans (Section 24.2.4.3.2.2 )

P437a - NB_NC2_CELL_RESEL_FAIL_REJECT_CELL (Section 24.2.4.4.2.24
)
P437b - NB_NC2_CELL_RESEL_FAIL_NO_REJECT_CELL (Section
24.2.4.4.2.25 )
P438a - SIG_BLKS_NC2_UL_PACCH_PTM_LOAD (Section 24.4.4.14.2.2 )
P438b - SIG_BLKS_NC2_DL_PACCH_PTM_LOAD (Section 24.4.4.4.2.1 )
P438c - SIG_BLKS_NC2_UL_PACCH_CCCH_LOAD (Section 24.4.4.14.2.3 )
P438d - SIG_BLKS_NC2_PRACH_LOAD (Section 24.4.4.12.2.2 )
P439 - SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD (Section 24.4.4.14.2.4 )
P43a - NB_DL_LLC_BYTES_GPRS_ACK (Section 24.4.4.3.2.2 )
P43b - NB_DL_LLC_BYTES_GPRS_NACK (Section 24.4.4.3.2.3 )
P43c - NB_DL_LLC_BYTES_EGPRS_ACK (Section 24.4.4.3.2.4 )
P43d - NB_DL_LLC_BYTES_EGPRS_NACK (Section 24.4.4.3.2.5 )
P44 - NB_UL_LLC_BYTES (Section 24.4.3.2.2.2 )
P440a - NB_REROUTING_INTRA_NSE (Section 24.2.4.11.2.1 )
P440b - NB_REROUTING_INTER_NSE_INTRA_BSS (Section 24.2.4.11.2.2 )
P440c - NB_REROUTING_INTER_NSE_INTER_BSS (Section 24.2.4.11.2.3 )
P441a - NB_IMPOSSIBLE_OR_UNREQUESTED_REROUTING_INR (Section
24.2.4.11.2.4 )
P441b - NB_UNREQUESTED_REROUTING_NOT_INR (Section 24.2.4.11.2.5
)
P441c - NB_IMPOSSIBLE_REROUTING_NOT_INR (Section 24.2.4.11.2.6 )
P44a - NB_UL_LLC_BYTES_GPRS_ACK (Section 24.4.4.13.2.2 )
P44b - NB_UL_LLC_BYTES_GPRS_NACK (Section 24.4.4.13.2.3 )
P44c - NB_UL_LLC_BYTES_EGPRS_ACK (Section 24.4.4.13.2.4 )
P44d - NB_UL_LLC_BYTES_EGPRS_NACK (Section 24.4.4.13.2.5 )
P45 - NB_KBYTES_RECEIVED_FROM_SGSN (Section 24.4.3.3.2.1 )
P450a - NB_R97_R98_MS_CONTEXT_GPU (Section 24.4.4.8.2.1 )
P450b - NB_GPRS_R99_MS_CONTEXT_GPU (Section 24.4.4.8.2.2 )
P450c - NB_EGPRS_R99_MS_CONTEXT_GPU (Section 24.4.4.8.2.3 )
P450d - NB_MS_CONTEXT_GPU (Section 24.4.4.8.2.4 )
P450e - NB_GERAN_FEATURE_PACK1_MS_CONTEXT_GPU (Section
24.4.4.8.2.5 )
P451a - CUMULATED_TIME_PDCH_UL_TBF_CELL (Section 24.3.5.7.2.7 )
P451b - CUMULATED_TIME_PDCH_DL_TBF_CELL (Section 24.3.5.6.2.6 )
P452 - CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL (Section
24.3.5.6.2.7 )
P453a_1 - DISTRIB_UL_TBF_DURATION_1 (Section 24.3.5.9.2.8 )
791 / 1392

P453b_1 - DISTRIB_DL_TBF_DURATION_1 (Section 24.3.5.3.2.5 )
P454a_1 - DISTRIB_UL_TBF_VOLUME_1 (Section 24.3.5.10.2.1 )
P454b_1 - DISTRIB_DL_TBF_VOLUME_1 (Section 24.3.5.4.2.3 )
P455a_1 - DISTRIB_UL_PDCH_UNIT_ALLOC_1 (Section 24.3.5.7.2.8 )
792 / 1392

P455b_1 - DISTRIB_DL_PDCH_UNIT_ALLOC_1 (Section 24.3.5.6.2.8 )
P456 - NB_PSI_PROC (Section 24.2.4.2.3.1 )
P457 - NB_PSI_MES (Section 24.4.4.4.2.2 )
P458 - NB_NEIGH_PSI_PROC (Section 24.2.4.2.2.3 )
P459 - NB_NEIGH_PSI_MES (Section 24.4.4.4.2.3 )
P45a - NB_KBYTES_RECEIVED_FROM_SGSN_GBIP (Section 24.4.3.4.2.1 )
P46 - NB_KBYTES_SENT_TO_SGSN (Section 24.4.3.3.2.2 )
P460b - MAX_SOURCE_NACC_CELL_RESEL_TIME (Section 24.2.4.2.2.4 )
P460c - MIN_SOURCE_NACC_CELL_RESEL_TIME (Section 24.2.4.2.2.5 )
P461 - CUMULATED_ACT_EXT_UL_CONNECTION_TIME (Section
24.3.5.9.2.18 )
P462 - NB_DUMMY_UL_BLOCKS (Section 24.4.4.15.2.15 )
P463 - NB_PFC_DOWNLOAD (Section 24.2.4.12.2.6 )
P464 - NB_NC2_CELL_RESEL_FAIL_LOAD (Section 24.2.4.4.2.26 )
P465 - MAX_NB_USED_EXTRA_BONUS_ABIS_NIBBLES (Section
24.3.2.2.2.1 )
P466 - CUMULATED_TIME_USED_EXTRA_BONUS_ABIS_NIBBLES
(Section 24.3.2.2.2.2 )
P469 - MAX_NB_DEFICIT_GCH (Section 24.3.3.2.2.8 )
P46a - NB_KBYTES_SENT_TO_SGSN_GBIP (Section 24.4.3.4.2.2 )
P470 - CUMULATED_TIME_DEFICIT_GCH (Section 24.3.3.2.2.9 )
P471 - CUMULATED_TIME_EXCESS_GCH (Section 24.3.3.2.2.10 )
793 / 1392
P472 - CUMULATED_TIME_FREE_EXTRA_BONUS_ABIS_NIBBLES (Section

24.3.2.2.2.3 )
P474 - CUMULATED_TIME_FREE_ATER_NIBBLES (Section 24.3.3.2.2.11 )
P484 - MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE (Section 24.3.2.2.2.4
)
P486 - MIN_NB_FREE_ATER_NIBBLE (Section 24.3.3.2.2.12 )
P488 - NB_RT_DL_TBF (Section 24.2.4.12.2.7 )
P489 - NB_RT_UL_TBF (Section 24.2.4.12.2.8 )
P49 - NB_IMM_ASS_AGCH (Section 24.4.4.2.2.1 )
P490 - NB_UNACK_NRT_PFC_CREATION (Section 24.2.4.12.2.9 )
P491 - NB_UNACK_RT_PFC_CREATION (Section 24.2.4.12.2.10 )
P492 - NB_DOWNGRADED_RT_PFC (Section 24.2.4.12.2.11 )
P493 - NB_PFC_REJECTED (Section 24.2.4.12.2.12 )
P494 - NB_PFC_DOWNLOAD_FAIL (Section 24.2.4.12.2.13 )
P495 - MAX_NB_USED_SPDCH_CELL (Section 24.3.5.5.2.11 )
P496 - MIN_NB_USED_SPDCH_CELL (Section 24.3.5.5.2.12 )
P497 - NB_RT_PFC_CREATION (Section 24.2.4.12.2.14 )
P498 - NB_NRT_PFC_CREATION (Section 24.2.4.12.2.15 )
P499 - NB_RT_PFC_CREATION_OK (Section 24.2.4.12.2.16 )
P5 - TIME_PVC_CONG_LEVEL1 (Section 24.3.4.4.2.3 )
P500 - NB_DTM_CAPABLE_MS_CONTEXT_GPU (Section 24.2.4.9.2.1 )
P501 - NB_DTM_MS_CONTEXT_CELL (Section 24.2.4.9.2.2 )
P502 - CUMULATED_DTM_TIME (Section 24.2.4.9.2.3 )
P503 - CUMULATED_DTM_DEDICATED_TIME (Section 24.2.4.9.2.4 )
P504 - CUMULATED_DTM_PTM_TIME (Section 24.2.4.9.2.5 )
P505 - NB_DTM_DL_TBF_EST_REQ (Section 24.2.4.9.2.6 )
P506 - NB_DTM_DL_TBF_EST_SUCC (Section 24.2.4.9.2.7 )
P507 - NB_DTM_UL_TBF_EST_REQ (Section 24.2.4.9.2.8 )
P508 - NB_DTM_UL_TBF_EST_SUCC (Section 24.2.4.9.2.9 )
P509 - NB_DTM_CS_DL_TBF_RELEASE (Section 24.2.4.9.2.10 )
P510 - NB_DTM_CS_UL_TBF_RELEASE (Section 24.2.4.9.2.11 )
P511 - NB_DTM_DL_TBF_FAIL_CONG (Section 24.2.4.9.2.12 )
P512 - NB_DTM_UL_TBF_FAIL_CONG (Section 24.2.4.9.2.13 )
P513 - NB_UL_LLC_BYTES_GTTP (Section 24.2.4.9.2.14 )
P514 - NB_DL_LLC_BYTES_GTTP (Section 24.2.4.9.2.15 )
P515 - NB_RT_PFC_CREATION_DTM_DEDICATED (Section 24.2.4.9.2.16 )
P516 - NB_RT_PFC_DOWNGRADED_DTM_DEDICATED (Section
24.2.4.9.2.17 )
P518 - NB_RT_PFC_CREATION_DTM_MODE (Section 24.2.4.9.2.18 )
P519 - NB_RT_PFC_DOWNGRADED_DTM_MODE (Section 24.2.4.9.2.19 )
794 / 1392
P52a - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_ACK
(Section 24.3.5.3.2.15 )
P52b - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_NACK
(Section 24.3.5.3.2.16 )
P52c - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_ACK
(Section 24.3.5.3.2.17 )
P52d - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_NACK
(Section 24.3.5.3.2.18 )
P530a_1 - NB_MS_MULTISLOT_CLASS_0_TO_10 (Section 24.4.4.8.2.6 )
P530a_3 - NB_MS_MULTISLOT_CLASS_3X (Section 24.4.4.8.2.8 )
P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_34 (Section 24.4.4.8.2.11 )
P531a_1 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1 (Section
24.3.5.8.2.1 )
24.3.5.8.2.2 )
24.3.5.8.2.3 )
24.3.5.8.2.4 )
24.3.5.8.2.5 )
24.3.5.8.2.6 )
24.3.5.8.2.7 )
24.3.5.8.2.8 )
24.3.5.8.2.9 )
24.3.5.8.2.10 )
24.3.5.8.2.11 )
P531b_1 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1 (Section
24.3.5.2.2.1 )
24.3.5.2.2.2 )
24.3.5.2.2.3 )
24.3.5.2.2.4 )
795 / 1392

24.3.5.8.2.12 )
24.3.5.8.2.13 )
24.3.5.2.2.5 )
24.3.5.2.2.6 )
24.3.5.8.2.14 )
24.3.5.2.2.7 )
24.3.5.8.2.15 )
P532a_1 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1 (Section
24.3.5.8.2.16 )
24.3.5.8.2.17 )
24.3.5.8.2.18 )
24.3.5.8.2.19 )
24.3.5.8.2.20 )
24.3.5.8.2.21 )
24.3.5.8.2.22 )
24.3.5.8.2.23 )
24.3.5.8.2.24 )
24.3.5.8.2.25 )
P532b_1 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1 (Section
24.3.5.2.2.8 )
24.3.5.2.2.9 )
24.3.5.2.2.10 )
24.3.5.2.2.11 )
24.3.5.2.2.12 )
24.3.5.2.2.13 )
796 / 1392

24.3.5.2.2.14 )
24.3.5.2.2.15 )
24.3.5.2.2.16 )
24.3.5.2.2.17 )
P53a - NB_PS_PAGING_REQ_PCH (Section 24.4.4.10.2.1 )
P53b - NB_CS_PAGING_REQ_PCH (Section 24.4.4.10.2.2 )
P53c - NB_IMM_ASS_PCH (Section 24.4.4.10.2.3 )
P55a - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS1 (Section 24.4.4.5.2.16 )
P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2 (Section 24.4.4.5.2.17 )
P55c - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3 (Section 24.4.4.5.2.18 )
P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4 (Section 24.4.4.5.2.19 )
P55e - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1 (Section 24.4.4.5.2.20
)
P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2 (Section 24.4.4.5.2.21 )
P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3 (Section 24.4.4.5.2.22
)
P55h - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4 (Section 24.4.4.5.2.23
)
P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5 (Section 24.4.4.5.2.24 )
P55j - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6 (Section 24.4.4.5.2.25 )
P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7 (Section 24.4.4.5.2.26
)
P55l - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8 (Section 24.4.4.5.2.27 )
P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9 (Section 24.4.4.5.2.28
)
P57a - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS1 (Section 24.4.4.15.2.16 )
P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2 (Section 24.4.4.15.2.17 )
P57c - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3 (Section 24.4.4.15.2.18 )
P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4 (Section 24.4.4.15.2.19 )
P57e - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1 (Section
24.4.4.15.2.20 )
P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2 (Section 24.4.4.15.2.21
)
P57g - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3 (Section
24.4.4.15.2.22 )
P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4 (Section
24.4.4.15.2.23 )
P57i - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5 (Section 24.4.4.15.2.24
)
797 / 1392
P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6 (Section 24.4.4.15.2.25

)
P57k - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7 (Section
24.4.4.15.2.26 )
P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8 (Section 24.4.4.15.2.27
)
P57m - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9 (Section
24.4.4.15.2.28 )
P59 - NB_DL_RLC_BLOCK_PACCH (Section 24.4.4.4.2.4 )
P594 - NB_EDA_MS_CONTEXT_GPU (Section 24.2.4.10.2.1 )
P595 - CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE
(Section 24.2.4.10.2.2 )
P596 - NB_EDA_USED_UL_TBF (Section 24.2.4.10.2.3 )
P597 - NB_EDA_ALLOWED_UL_TBF (Section 24.2.4.10.2.4 )
P598 - NB_DA_EDA_REALLOC_UL_TBF (Section 24.2.4.10.2.5 )
P60 - NB_UL_RLC_BLOCK_PACCH (Section 24.4.4.14.2.5 )
P61 - SIG_BLKS_PPCH_LOAD (Section 24.4.4.11.2.1 )
P61a - NB_PACK_PS_PAGING_REQ_PPCH (Section 24.4.4.11.2.2 )
P61b - NB_PACK_CS_PAGING_REQ_PPCH (Section 24.4.4.11.2.3 )
P62a - NB_UL_TBF_EST_REQ_MSidle_MastChan (Section 24.2.4.14.2.14 )
P62b - NB_UL_TBF_EST_REQ_MStransDL (Section 24.2.4.14.2.15 )
P62c - NB_UL_TBF_EST_REQ_MSidle_NO_MastChan (Section
24.2.4.14.2.16 )
P62d - NB_UL_TBF_EST_REQ_EGPRS_PIM (Section 24.3.5.6.2.18 )
P65 - NB_DL_TBF_EST_FAIL_GB_PB (Section 24.2.4.5.2.10 )
P66 - NB_UL_TBF_EST_FAIL_GB_PB (Section 24.2.4.14.2.17 )
P67 - TIME_BVC_NOT_AVAIL (Section 24.3.4.3.2.1 )
P6a - NB_PVC_FRAMES_DISC_7_CONSEC_1 (Section 24.2.3.3.2.1 )
P6b - NB_PVC_FRAMES_DISC_ZERO_INSER (Section 24.2.3.3.2.2 )
P6c - NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE (Section 24.2.3.3.2.3
)
P6d - NB_PVC_FRAMES_DISC_LENGTH_TOO_SHORT (Section
24.2.3.3.2.4 )
P72c - NB_DL_RLC_BYTES_PDTCH_LOST_CS (Section 24.4.4.5.2.29 )
P72d - NB_DL_RLC_BYTES_PDTCH_LOST_MCS (Section 24.4.4.5.2.30 )
P73c - NB_UL_RLC_BYTES_PDTCH_LOST_CS (Section 24.4.4.15.2.29 )
P73d - NB_UL_RLC_BYTES_PDTCH_LOST_MCS (Section 24.4.4.15.2.30 )
P74 - NB_DL_PDU_TRANSMITTED (Section 24.4.4.3.2.6 )
P75 - NB_UL_PDU_TRANSMITTED (Section 24.4.4.13.2.6 )
P76a - AV_PMU_CPU_POWER_BUDGET (Section 24.4.4.6.2.11 )
P77a - MAX_PMU_CPU_POWER_BUDGET (Section 24.4.4.6.2.12 )
798 / 1392
P9 - NB_DL_TBF_NORM_REL (Section 24.2.4.7.2.11 )

P90a - NB_DL_TBF_EST_SUCC_MS_Idle_DRX_MPDCH (Section
24.2.4.5.2.11 )
P90b - NB_DL_TBF_EST_SUCC_MS_Transfer_UL (Section 24.2.4.5.2.12 )
P90c - NB_DL_TBF_EST_SUCC_MS_IDLE_DRX_NO_MPDCH (Section
24.2.4.5.2.13 )
P90d - NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH (Section
24.2.4.5.2.14 )
P90e - NB_DL_TBF_EST_SUCC_T3192 (Section 24.2.4.5.2.15 )
P90f - NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH (Section
24.2.4.5.2.16 )
P90g - NB_DL_TBF_EST_SUCC_EGPRS_PIM (Section 24.3.5.6.2.19 )
P91a - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_MPDCH (Section
24.2.4.5.2.17 )
P91b - NB_DL_TBF_EST_REQ_MS_Transfer_UL (Section 24.2.4.5.2.18 )
P91c - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH (Section
24.2.4.5.2.19 )
P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH (Section
24.2.4.5.2.20 )
P91e - NB_DL_TBF_EST_REQ_T3192 (Section 24.2.4.5.2.21 )
P91f - NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH (Section
24.2.4.5.2.22 )
P91g - NB_DL_TBF_EST_REQ_EGPRS_PIM (Section 24.3.5.6.2.20 )
P95 - NB_DL_LLC_BYTES_REROUTED (Section 24.4.4.3.2.7 )
P96 - NB_DL_LLC_BYTES_NOT_REROUTED (Section 24.4.4.3.2.8 )
P97 - NB_DL_LLC_BYTES_REROUTED_RECEIVED (Section 24.4.4.3.2.9 )
P98a - NB_DL_TBF_REL_SUSP (Section 24.2.4.7.2.12 )
P98b - NB_UL_TBF_REL_SUSP (Section 24.2.4.16.2.14 )
P98c - NB_SUSPEND_REQ_FOR_DL_TBF (Section 24.2.4.13.2.1 )
P98d - NB_SUSPEND_REQ_FOR_UL_TBF (Section 24.2.4.13.2.2 )
P98e - NB_SUSP_DL_TBF_REL (Section 24.2.4.7.2.13 )
P98f - NB_SUSP_UL_TBF_REL (Section 24.2.4.16.2.15 )
P99 - NB_LLC_BYTES_DISC_SUSPEND (Section 24.4.4.3.2.10 )
24.2 Quality of service

24.2.1 All Quality of service
799 / 1392

24.2.4.14.2.8 )
800 / 1392

24.2.4.7.2.4 )
24.2.4.7.2.5 )
24.2.4.16.2.5 )
24.2.4.16.2.6 )
24.2.4.16.2.7 )
(Section 24.2.4.16.2.8 )
24.2.4.14.2.13 )
)
)
24.2.3.2.2.2 )
801 / 1392

24.2.4.6.2.3 )
24.2.4.6.3.3 )
24.2.4.6.4.3 )
24.2.4.6.5.3 )
24.2.4.15.2.3 )
24.2.4.15.3.3 )
)
(Section 24.2.4.5.2.9 )
24.2.4.6.2.4 )
24.2.4.6.3.4 )
24.2.4.6.4.4 )
24.2.4.6.5.4 )
24.2.4.15.2.4 )
24.2.4.15.3.4 )
24.2.4.15.4.4 )
24.2.4.15.5.4 )
24.2.4.6.2.5 )
802 / 1392

24.2.4.6.3.5 )
24.2.4.6.4.5 )
24.2.4.6.5.5 )
24.2.4.15.2.5 )
24.2.4.15.3.5 )
24.2.4.15.4.5 )
24.2.4.15.5.5 )
)
24.2.4.4.2.25 )
24.2.4.11.2.4 )
)
803 / 1392

24.2.4.9.2.17 )
(Section 24.2.4.10.2.2 )
804 / 1392

24.2.4.14.2.16 )
)
24.2.3.3.2.4 )
24.2.4.5.2.11 )
24.2.4.5.2.13 )
24.2.4.5.2.14 )
24.2.4.5.2.16 )
24.2.4.5.2.17 )
24.2.4.5.2.19 )
24.2.4.5.2.20 )
24.2.4.5.2.22 )
805 / 1392
24.2.2 Ater interface

24.2.2.1 All Ater interface
24.2.2.2 LapD
24.2.2.2.1 All LapD
24.2.2.2.2 N/A
24.2.2.2.2.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
Measured Object
LapD
External Comment
The (decimal) value 1 000 000 means Driver LAPD not available. LAPD not
established. Note : P32 indicates the time the LAPD is not available
806 / 1392
24.2.2.2.2.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 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
807 / 1392
24.2.2.2.2.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 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
808 / 1392
24.2.2.2.2.4 P2d - NB_LAPD_EST

Long Name
NB_LAPD_EST
Definition
Number of data link establishment, re-establishment and reset on the LapD logical
link.
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
BSC in LapD established state.
Sub Domain 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
809 / 1392
24.2.3 Gb interface
24.2.3.1 All Gb interface
)
24.2.3.2.2.2 )
)
24.2.3.3.2.4 )
24.2.3.2 Bearer Channel

24.2.3.2.1 All Bearer Channel
)
24.2.3.2.2.2 )
24.2.3.2.2 N/A
24.2.3.2.2.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 invalid

FCS.
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
External Comment
810 / 1392
24.2.3.2.2.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 invalid

address format.
Trigger Condition
Whenever a frame received on the Bearer Channel is discarded due to invalid

address format.
Sub Domain 1
Gb interface
Sub Domain 2
Bearer Channel
Sub Domain 3
N/A
Measured Object
Bearer Channel
External Comment
811 / 1392
24.2.3.3 PVC
24.2.3.3.1 All PVC
)
24.2.3.3.2.4 )
24.2.3.3.2 N/A
24.2.3.3.2.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 consecutive

bits set to "1".
Trigger Condition
Whenever a frame received on the PVC is discarded due to seven bits set to "1".
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
Bearer Channel
External Comment
812 / 1392
24.2.3.3.2.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 integral

number of octetes (zero insertion failure).
Trigger Condition
Whenever a frame received on the PVC is discarded due to a non integral number
of octets (zero insertion failure).
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
Bearer Channel
External Comment
813 / 1392
24.2.3.3.2.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 than
the maximum allowed (FR-INFO-SIZE.Max).
Trigger Condition
Whenever a frame received on the PVC is discarded due to the length greater than
the maximum allowed.
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
814 / 1392
24.2.3.3.2.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 than
the minimum allowed (FR-INFO-SIZE.Min).
Trigger Condition
Whenever a frame received on the PVC is discarded due to the length lower than
the minimum allowed.
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
815 / 1392
24.2.4 Radio interface

24.2.4.1 All Radio interface
24.2.4.14.2.8 )
816 / 1392

24.2.4.7.2.4 )
24.2.4.7.2.5 )
24.2.4.16.2.5 )
24.2.4.16.2.6 )
24.2.4.16.2.7 )
(Section 24.2.4.16.2.8 )
24.2.4.14.2.13 )
)
817 / 1392

24.2.4.6.2.3 )
24.2.4.6.3.3 )
24.2.4.6.4.3 )
24.2.4.6.5.3 )
24.2.4.15.2.3 )
24.2.4.15.3.3 )
)
(Section 24.2.4.5.2.9 )
24.2.4.6.2.4 )
24.2.4.6.3.4 )
24.2.4.6.4.4 )
24.2.4.6.5.4 )
24.2.4.15.2.4 )
24.2.4.15.3.4 )
24.2.4.15.4.4 )
24.2.4.15.5.4 )
24.2.4.6.2.5 )
24.2.4.6.3.5 )
818 / 1392

24.2.4.6.4.5 )
24.2.4.6.5.5 )
24.2.4.15.2.5 )
24.2.4.15.3.5 )
24.2.4.15.4.5 )
24.2.4.15.5.5 )
)
24.2.4.4.2.25 )
24.2.4.11.2.4 )
)
819 / 1392

24.2.4.9.2.17 )
(Section 24.2.4.10.2.2 )
820 / 1392

24.2.4.14.2.16 )
24.2.4.5.2.11 )
24.2.4.5.2.13 )
24.2.4.5.2.14 )
24.2.4.5.2.16 )
24.2.4.5.2.17 )
24.2.4.5.2.19 )
24.2.4.5.2.20 )
24.2.4.5.2.22 )
24.2.4.2 Cell reselections

24.2.4.2.1 All Cell reselections
821 / 1392
24.2.4.2.2 NACC
24.2.4.2.2.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 in

NC0 mode.
Trigger Condition
Within the granularity period, the MFS cumulates the duration of each successful
outgoing NACC cell reselections triggered by the BSS in the source cell. The
duration of a NACC cell reselection is measured in the source cell between the
start of emission of Packet Neighbour Cell Data messages (following the reception
of the Packet Cell Change Notification message) and the reception of the Flush-LL
message. 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
External Comment
822 / 1392
24.2.4.2.2.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 NC0
mode.
Trigger Condition
Within the granularity period, the MFS counts the number of each successful
outgoing NACC cell reselections triggered by the BSS in the source cell. A NACC
cell reselection is successful when in the source cell after the start of emission
of Packet Neighbour Cell Data messages (following the reception of the Packet
Cell Change Notification message) , the reception of the Flush-LL message is
received. 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
External Comment
823 / 1392
24.2.4.2.2.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 RLC
following a reception of PACKET CELL CHANGE
Sub Domain 1
Radio interface
Sub Domain 2
Cell reselections
Sub Domain 3
NACC
Measured Object
Cell
External Comment
824 / 1392
24.2.4.2.2.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 1
Radio interface
Sub Domain 2
Cell reselections
Sub Domain 3
NACC
Measured Object
Cell
External Comment
825 / 1392
24.2.4.2.2.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 1
Radio interface
Sub Domain 2
Cell reselections
Sub Domain 3
NACC
Measured Object
Cell
External Comment
826 / 1392
24.2.4.2.3 Packet (P)SI status

24.2.4.2.3.1 P456 - NB_PSI_PROC
Long Name
NB_PSI_PROC
Definition
Number of times the procedure of broadcast of serving cell PSI for Packet PSI
Status or the procedure of sending of Packet Serving Cell Data for Packet SI
Status is invoked.
Trigger Condition
Whenever RRM sends a request to PTU to send serving cell (P)SI to the MS for
Packet (P)SI Status procedure. The primitive used as trigger is PCC-PSCD-REQ.
Sub Domain 1
Radio interface
Sub Domain 2
Cell reselections
Sub Domain 3
Packet (P)SI status
Measured Object
Cell
External Comment
827 / 1392
24.2.4.3 Cell reselections in NC0

24.2.4.3.1 All Cell reselections in NC0
24.2.4.3.2 N/A
24.2.4.3.2.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 1
Radio interface
Sub Domain 2
Cell reselections in NC0
Sub Domain 3
N/A
Measured Object
Cell
External Comment
Note that NC2 cell reselections can only be triggered if the MS is in packet transfer
mode
828 / 1392
24.2.4.3.2.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 to

a NC0 cell reselection triggered while the MS was in packet transfer mode in the
old cell in the previous T_WAIT_FLUSH seconds. The counter is then incremented
for 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 message
concerns a DL or UL TBF which is(are) still on-going(s), ii) a Flush-LL message
is received from the SGSN and this Flush-LL message concerns a DL or UL
TBF which has(have) been abnormally released in the previous T_WAIT_FLUSH
seconds.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
829 / 1392
24.2.4.4 Cell reselections in NC2

24.2.4.4.1 All Cell reselections in NC2
)
24.2.4.4.2.25 )
830 / 1392
24.2.4.4.2 N/A
24.2.4.4.2.1 P209 - TIME_SOURCE_NC2_CELL_RESEL
Long Name
TIME_SOURCE_NC2_CELL_RESEL
Definition
Cumulated time duration of successful outgoing NC2 cell reselections (measured

in the source cell).
Trigger Condition
Within the granularity period, the MFS cumulates the duration of each successful
outgoing NC2 cell reselections triggered by the BSS in the source cell. The
duration of a NC2 cell reselection is measured in the source cell between the
acknowledgement of the Packet Cell Change Order message and the reception of
the Flush-LL message. The source cell is the cell where the NC cell reselections
are outgoing.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
The MFS can measure the duration of a NC cell reselection provided that the
Flush-LL message is received while the timer T_WAIT_FLUSH is still running. This
means that NC cell reselection duration longer than the timer T_WAIT_FLUSH
cannot be measured by this counter.
831 / 1392
24.2.4.4.2.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 cell

reselections (measured in the target cell).
Trigger Condition
Within the granularity period, the MFS cumulates the duration of the successful
incoming intra-RA intra-MFS NC2 cell reselections triggered by the BSS in the
source cell. The duration of a NC2 cell reselection is measured in the source cells
between the acknowledgement of the Packet Cell Change Order message and
the reception of the Flush-LL message. These measures are forwarded to the
target cell in the intra-MFS TLLI Rerouting Confirm message and then cumulated
in the target cell. The source cells are the cells where the NC cell reselections
are outgoing, whereas the target cell is the cell where the NC cell reselections
are incoming.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1) Only NC2 cell reselections involving a source cell which belongs to the same
routing area and same MFS as the target cell are taken into account in this
average. 2) The MFS can measure the duration of a NC cell reselection provided
that the Flush-LL message is received while the timer T_WAIT_FLUSH is still
running. This means that NC cell reselection duration longer than the timer
T_WAIT_FLUSH cannot be measured by this counter.
832 / 1392
24.2.4.4.2.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 successful
outgoing NC2 cell reselections triggered by the BSS in the source cell. A NC2
cell reselection is successful when in the source cells after the acknowledgement
of the Packet Cell Change Order message is received , the Flush-LL message is
received. These measures are forwarded to the target cell in the intra-MFS TLLI
Rerouting Confirm message and then cumulated in the target cell. The source
cells are the cells where the NC cell reselections are outgoing, whereas the target
cell is the cell where the NC cell reselections are incoming.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1) Only NC2 cell reselections involving a source cell which belongs to the same
routing area and same MFS as the target cell are taken into account in this
average. 2) The MFS can measure the duration of a NC cell reselection provided
that the Flush-LL message is received while the timer T_WAIT_FLUSH is still
running. This means that NC cell reselection duration longer than the timer
T_WAIT_FLUSH cannot be measured by this counter.
833 / 1392
24.2.4.4.2.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 UL

transfert.
Trigger Condition
The counter is incremented each time a Packet Control Acknowledgement is

received in acknowledgement of a Packet Cell Change Order while in UL transfert.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
834 / 1392
24.2.4.4.2.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 DL

transfert.
Trigger Condition
The counter is incremented each time a Packet Control Acknowledgement is

received in acknowledgement of a Packet Cell Change Order while in DL transfert.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
835 / 1392
24.2.4.4.2.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 Order
message to the MS while it has an ongoing DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a PCCO is sent for a MS supporting a DL TBF and an UL TBF, then both P223
and P226 are incremented.
836 / 1392
24.2.4.4.2.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 been
sent to the MS while in DL transfer.
Trigger Condition
Whenever the MFS receives a FLUSH-LL PDU from the SGSN after a Packet
Cell Change Order message has been sent to the MS while it has an ongoing in
DL TBF .
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a FLUSH is received for a MS supporting a DL TBF and an UL TBF, then both

P224 and P227 are incremented.
837 / 1392
24.2.4.4.2.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 Cell
Change 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 MS
after a Packet Cell Change Order message has been sent to the MS while it has
an ongoing DL TBF .
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a PCCF is received for a MS supporting a DL TBF and an UL TBF, then both

P225 and P228 are incremented
838 / 1392
24.2.4.4.2.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 Order
message to the MS while it has an ongoing UL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a PCCO is sent for a MS supporting a DL TBF and an UL TBF, then both P223
and P226 are incremented.
839 / 1392
24.2.4.4.2.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 been
sent to the MS while in UL transfer.
Trigger Condition
Whenever the MFS receives a FLUSH-LL PDU from the SGSN after a Packet Cell
Change Order message has been sent to the MS while it has an ongoing UL TBF .
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a FLUSH is received for a MS supporting a DL TBF and an UL TBF, then both

840 / 1392
24.2.4.4.2.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 Cell
Change 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 MS
after a Packet Cell Change Order message has been sent to the MS while it has
an ongoing UL TBF .
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
If a PCCF is received for a MS supporting a DL TBF and an UL TBF, then both

841 / 1392
24.2.4.4.2.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 in

the source cell)
Trigger Condition
Tide mark recording the maximum value of Counter P209
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
842 / 1392
24.2.4.4.2.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 in

the source cell)
Trigger Condition
Tide mark recording the minimum value of Counter P209
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
843 / 1392
24.2.4.4.2.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 cell

reselections (measured in the target cell).
Trigger Condition
Tide mark recording the maximum value of Counter P210
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
844 / 1392
24.2.4.4.2.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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
845 / 1392
24.2.4.4.2.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 due
to a "too low downlink received signal" (Cause PT1)
Trigger Condition
This counter is incremented whenever the RRM layer sends to the MS a Packet
Cell Change Order message for a NC2 cell reselection triggered due a "too low
downlink received signal" (Cause PT1). The repetitions of the Packet Cell Change
Order message for a given NC2 cell reselection alarm are not counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
846 / 1392
24.2.4.4.2.17 P433b - NB_NC2_CELL_RESEL_REQ_PT2

Long Name
Definition
Number of NC2 cell reselection requests for a MS in packet transfer mode due to
a "detection of a better neighbour cell" (Cause PT2)
Trigger Condition
Cell Change Order message for a NC2 cell reselection triggered due the "detection
of a better neighbour cell" (Cause PT2). The repetitions of the Packet Cell Change
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
847 / 1392
24.2.4.4.2.18 P433c - NB_NC2_CELL_RESEL_REQ_PT3

Long Name
Definition
a "too bad downlink radio quality" (Cause PT3)
Trigger Condition
Cell Change Order message for a NC2 cell reselection triggered due a "too bad
downlink radio quality" (Cause PT3). The repetitions of the Packet Cell Change
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
848 / 1392
24.2.4.4.2.19 P433d - NB_NC2_CELL_RESEL_REQ_PT4

Long Name
Definition
a "too bad uplink radio quality" (Cause PT4)
Trigger Condition
Cell Change Order message for a NC2 cell reselection triggered due a "too bad
uplink radio quality" (Cause PT4). The repetitions of the Packet Cell Change Order
message for a given NC2 cell reselection alarm are not counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
849 / 1392
24.2.4.4.2.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 due
to a "too low downlink received signal" (Cause PT1)
Trigger Condition
This counter is incremented upon receipt of a Flush-LL message corresponding

to a NC2 cell reselection triggered due to a "too low downlink received signal"
(Cause PT1).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
850 / 1392
24.2.4.4.2.21 P435b - NB_NC2_CELL_RESEL_SUCC_PT2

Long Name
Definition
to a "detection of a better neighbour cell" (Cause PT2)
Trigger Condition

to a NC2 cell reselection triggered due to a "detection of a better neighbour cell"
(Cause PT2).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
851 / 1392
24.2.4.4.2.22 P435c - NB_NC2_CELL_RESEL_SUCC_PT3

Long Name
Definition
to a "too bad downlink radio quality" (Cause PT3)
Trigger Condition

to a NC2 cell reselection triggered due to a "too bad downlink radio quality"
(Cause PT3).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
852 / 1392
24.2.4.4.2.23 P435d - NB_NC2_CELL_RESEL_SUCC_PT4

Long Name
Definition
to a "too bad uplink radio quality" (Cause PT4)
Trigger Condition

to a NC2 cell reselection triggered due to a "too bad uplink radio quality" (Cause
PT4).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
853 / 1392
24.2.4.4.2.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 reject
the target cell for a while.
Trigger Condition
This counter is incremented upon receipt of a 3GPP TS 04.60 Packet Cell Change
Failure message with Causes "Frequency not implemented", "No response on
target cell", or "Immediate Assign Reject or Packet Access Reject on target cell".
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
854 / 1392
24.2.4.4.2.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 to
reject the target cell for a while.
Trigger Condition
This counter is incremented upon receipt of a 3GPP TS 04.60 Packet Cell Change
Failure message with Causes "On going CS connection", "MS in GMM Standby
state", or "Forced to the Standby state".
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
855 / 1392
24.2.4.4.2.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 "immediate

assign reject" or "packet access rejact on target cell".
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
856 / 1392
24.2.4.5 DL TBF establishments

24.2.4.5.1 All DL TBF establishments
(Section 24.2.4.5.2.9 )
24.2.4.5.2.11 )
24.2.4.5.2.13 )
24.2.4.5.2.14 )
24.2.4.5.2.16 )
24.2.4.5.2.17 )
24.2.4.5.2.19 )
24.2.4.5.2.20 )
24.2.4.5.2.22 )
857 / 1392
24.2.4.5.2 N/A
24.2.4.5.2.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: This

counter applies to GPRS and EGPRS MS.
Trigger Condition
When a DL TBF cannot be established, due to GPU congestion (cause of the

failure of the last attempt before PDU life time expiry). GPU congestion means
that the maximum capacity of at least one DSP on the GPU is reached in terms
of resources GCH and/or PDCH. Generally, for all counters related to TBF
establishment failures, only the last reported failure cause is taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF establishments
Sub Domain 3
N/A
Measured Object
Cell
External Comment
858 / 1392
24.2.4.5.2.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 limitations

of the GPU. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition
Whenever a DL TBF cannot be established due to CPU processing power

limitations of the GPU.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
859 / 1392
24.2.4.5.2.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 lack

of Ater resources. A lack of Ater resources occurs when there is not enough
GCH to serve the DL TBF request. For BTS evolium : the number of GCH that
can be established and/or redistributed is < Nb_GCH_FOR_TBF_ESTAB and the
number of free Ater nibbles is < Nb_GCH_FOR_TBF_ESTAB. For DRFU BTS :
Lack of free Ater nibbles to serve the GCHs. The counter is incremented at the
expiry of the PDU lifetime when the last attempt fails to establish the DL TBF
due to a lack of transmission resources.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
860 / 1392
24.2.4.5.2.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:

Trigger Condition
The counter is incremented whenever a DL TBF establishment fails due to a

lack of Abis resources. A lack of Abis transmission resources occurs when
there is not enough Abis nibbles to serve the DL TBF request. For BTS
evolium : the number of GCH that can be established and or redistributed
is < 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. The
counter is incremented at the expiry of the PDU lifetime when the last attempt fails
to establish the DL TBF due to a lack of transmission resources.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
861 / 1392
24.2.4.5.2.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 to
guarantee a minimum throughput for the DL TBF. - This may happen when the
number of TBFs is too high compared to the number of available GCHs. - or
the MAX_TBF_TRX_DL constraint. Note: This counter applies to GPRS and
EGPRS MS.
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 GCH
available to serve the DL TBF is < Min_Nb_GCH. For DRFU BTS : Counter not
incremented (=0). 2) or the MAX_TBF_TRX_DL constraint: For BTS evolium :
The MAX_TBF_TRX_DL limit is reached on all the TRXs available for PS traffic in
the cell. For DRFU BTS : Counter not incremented (=0). Note : This counter is not
be incremented for RT PFCs. The counter is incremented at the expiry of the PDU
lifetime when the last attempt to establish the DL TBF has failed due to too low
number of available GCH (too many TBF on the TRX compared to the number of
available GCH) or due to the MAX_TBF_TRX_DL constraint.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
862 / 1392
24.2.4.5.2.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:

Trigger Condition
The counter is incremented whenever a DL TBF establishment fails due to a lack

of radio resources. A lack of radio resource occurs: i) if the maximum number of
MSs per slave PDCH in downlink is reached for all the slave PDCHs allocated to
the MFS, or ii) if there is no TAI or TFI left in the MFS. or iii) if no PDCH are granted
to MFS due to a CS congestion and max_pdch_high_load is null. The counter
is incremented at the expiry of the PDU lifetime when the last attempt fails to
establish the DL TBF due to a lack of radio resources.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
863 / 1392
24.2.4.5.2.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

operational state is "enabled" and the GCHs carrying the TBF are available for
traffic.
Trigger Condition
Whenever the 04.60 Packet CONTROL ACKNOWLEDGMENT message awaited

on PACCH from the mobile during a DL TBF establishment procedure is not
received on the scheduled block. The DL TBF establishment procedure may
be concurrent to an UL TBF reallocation procedure (trigger T2). Generally,
for all counters related to TBF establishment failures, only the last reported
failure cause is taken into account. That is the counter is incremented only after
Max_retrans_DL attempts to establish a DL TBF and no acknowledgement is
received from the Mobile Station. If the acknowledgement is received before
Max_retrans_DL retransmissions of the assignment message, then the counter is
not incremented at all.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
864 / 1392
24.2.4.5.2.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 the
internal cause CPU_DSP_LOAD.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
865 / 1392
24.2.4.5.2.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 "delayed
release" to "active". It corresponds to the TBF becoming active again after a
certain duration of delayed release state. This counter therefore provides the
number of DL TBF establishments which have been avoided by the delayed
downlink TBF release feature.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
866 / 1392
24.2.4.5.2.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 (Gb
interface problem) associated with the cell.
Trigger Condition
Whenever the BVC associated with the cell is unavailable (which implies: cell
operational state "disabled"), the counter is incremented with the number of DL
TBF in establishment phase. All pending LLC PDUs in the MFS are discarded for
the cell.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
867 / 1392
24.2.4.5.2.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 packet

idle mode and DRX mode. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition
This counter is incremented whenever a PACKET CONTROL

ACKNOWLEDGEMENT message is received on PACCH subsequent to a DL TBF
establishment performed on PCCCH for a MS in packet idle mode and DRX mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
868 / 1392
24.2.4.5.2.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 transfer

mode. Note: This counter applies to GPRS and EGPRS MS
Trigger Condition

establishment performed on PACCH for a MS in packet transfer mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
869 / 1392
24.2.4.5.2.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 packet

idle mode and DRX mode. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition

establishment performed on CCCH for a MS in packet idle mode and DRX mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
870 / 1392
24.2.4.5.2.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 packet

idle mode and non-DRX mode. Note: This counter applies to GPRS and EGPRS
MS.
Trigger Condition

ACKNOWLEDGEMENT message is received on PACCH subsequent to a DL
TBF establishment performed on PCCCH for a MS in packet idle mode and
non-DRX mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
871 / 1392
24.2.4.5.2.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 is

running at BSS side. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition
The counter is incremented whenever a PACKET CONTROL

establishment triggered while the timer T3192n was running.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
872 / 1392
24.2.4.5.2.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 packet

idle mode and non-DRX mode. Note: This counter applies to GPRS and EGPRS
MS.
Trigger Condition

establishment performed on CCCH for a MS in packet idle mode and non-DRX
mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
873 / 1392
24.2.4.5.2.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 mode

and DRX mode in case there is at least one PCCCH established in the cell. Note:
Trigger Condition
This counter is incremented whenever the MFS receives a DL LLC PDU for a
MS in packet idle mode and in DRX mode in case there is at least one PCCCH
established in the cell. Generally, all counters related to TBF establishment
requests only take into account the first attempt, i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
874 / 1392
24.2.4.5.2.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 transfer

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

uplink packet transfer mode. Note that the counter is incremented whether the
request is served with a (EGPRS) PACKET DOWNLINK ASSIGNMENT or a
PACKET TIMESLOT RECONFIGURE (which means that the UL TBF resources
are re-assigned upon concurrent DL TBF establishment). Generally, all counters
related to TBF establishment requests only take into account the first attempt,
i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
875 / 1392
24.2.4.5.2.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

and DRX mode in case there is no PCCCH established in the cell. Note: This
Trigger Condition
This counter is incremented whenever the MFS receives a DL LLC PDU for a MS
in packet idle mode and in DRX mode in case there is no PCCCH established in
the cell. Generally, all counters related to TBF establishment requests only take
into account the first attempt, i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
876 / 1392
24.2.4.5.2.20 P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH

Long Name
NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH
Definition

and non-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
in packet idle mode and in non-DRX mode in case there is at least one PCCCH
established in the cell. Generally, all counters related to TBF establishment
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
877 / 1392
24.2.4.5.2.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 is

running 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 timer
T3192n is running. Generally, all counters related to TBF establishment requests
only take into account the first attempt, i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
878 / 1392
24.2.4.5.2.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

and non-DRX mode , in case there is no PCCCH established in the cell. Note:
Trigger Condition
in packet idle mode and in non-DRX mode in case there is no PCCCH established
in the cell. Generally, all counters related to TBF establishment requests only take
into account the first attempt, i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
879 / 1392
24.2.4.6 DL TBF re-allocations

24.2.4.6.1 All DL TBF re-allocations
24.2.4.6.2.3 )
24.2.4.6.3.3 )
24.2.4.6.4.3 )
24.2.4.6.5.3 )
24.2.4.6.2.4 )
24.2.4.6.3.4 )
24.2.4.6.4.4 )
24.2.4.6.5.4 )
24.2.4.6.2.5 )
24.2.4.6.3.5 )
24.2.4.6.4.5 )
24.2.4.6.5.5 )
880 / 1392
24.2.4.6.2 T1
24.2.4.6.2.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 least
one 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 by

a CS pre-emption process. Two cases are possible : - a downlink TBF has its
PACCH impacted by a soft PDCH pre-emption, - the maximum allowed (M)CS of
a downlink TBF will no longer be possible to serve because of an M-EGCH link
size reduction due to a soft PDCH pre-emption. The M-EGCH link to consider
is the one of the TRX currently supporting the downlink TBF. That case is only
valid for Evolium BTSs and can only occur in case the basic Abis nibbles of
some of the soft-preempted PDCHs are currently being used by GCHs within
the considered M-EGCH link. Example : if a downlink EGPRS TBF has MCS-9
as its maximum allowed (M)CS and is established on a TRX whose M-EGCH
link owns 5 GCHs, then if the CS preemption process leads to an M-EGCH link
having only 4 GCHs left (because one of the GCHs of the M-EGCH link is using
a basic Abis nibble mapped to a pre-empted PDCH), then the downlink TBF will
be impacted, and the counter incremented. The counter is also incremented by
one each time a downlink TBF has a concurrent uplink TBF impacted by the CS
preemption process (the same conditions as the above ones apply for the uplink
direction), in case the downlink TBF was not impacted. In both cases, the MFS
will try to reallocate the resources of the MS, which will require reallocating the
TBFs in one or in both directions.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF re-allocations
Sub Domain 3
T1
Measured Object
Cell
External Comment
881 / 1392
24.2.4.6.2.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 a

downlink TBF (due to trigger T1).
Trigger Condition
A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource

reallocation attempt for that downlink TBF due to T1. If the PACKET CONTROL
ACKNOWLEDGEMENT acknowledges reallocation of both an uplink and a
downlink TBF, this counter shall be incremented as well as P406a. If after the
resource reallocation algorithm is run for a candidate Mobile Station having two
TBFs following T1, only the resources of the uplink TBF need to be reallocated,
the procedure shall be considered successful for the downlink TBF, irrespective
of the reallocation protocol outcome. Indeed, even if the reallocation protocol
fails for the uplink TBF, the downlink TBF will not be released and therefore this
can be considered as a success. This is another trigger for incrementing this
counter. This is required since P403a has been incremented. Similarly, if after the
TBFs following T1, there is a preparation failure but the PACCH of the downlink
TBF is not impacted by soft PDCH pre-emption, then the downlink TBF will remain
alive and this counter shall be incremented. The counter can be used to compute
the success rate of the reallocation execution phase. Note: this counter takes into
account also the successful T1 reallocations where the MAX_(M)CS of a DL TBF
is decreased without any change of its radio allocation.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
882 / 1392
24.2.4.6.2.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 downlink

TBF 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 for

resource 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 MS
is not bugged, it means that the radio conditions were too poor for the MS to
either correctly receive the reassignment message or for the MFS to receive the
acknowledgement from the MS. If an MS for which the resource reallocation
protocol was attempted but failed had two TBFs and both were being reallocated,
then both counters P407a and P408a shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
883 / 1392
24.2.4.6.2.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, T1

resource reallocation has been attempted but no candidate allocation could be
found. The TBF could therefore not be reallocated.
Trigger Condition
The counter is incremented each time a downlink TBF is impacted by a CS

pre-emption process , the resource reallocation algorithm is run but no candidate
allocation can be found for the downlink TBF. As such, it corresponds to a resource
reallocation preparation failure.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
884 / 1392
24.2.4.6.2.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 running
following T1 and an external TBF release request is received which forces to
stop the on-going resource reallocation (FLUSH-LL from the SGSN or GPRS
SUSPENSION REQUEST from the BSC).
Trigger Condition
The counter is incremented each time the resources of a downlink TBF are
being reallocated (ie either a PACKET DOWNLINK ASSIGNMENT or a PACKET
TIMESLOT RECONFIGURE message has been sent to the MS to reallocate its
downlink resources) and: - a FLUSH-LL is received from the SGSN, or - a GPRS
SUSPENSION REQUEST is received from the BSC for that Mobile Station before
the PACKET CONTROL ACKNOWLEDGEMENT is received.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
885 / 1392
24.2.4.6.3 T2
24.2.4.6.3.1 P403b - NB_DL_RES_REALLOC_REQ_T2
Long Name
Definition
Number of downlink TBFs which are candidate for resource reallocation upon
concurrent uplink TBF establishment.
Trigger Condition
The counter is incremented by one each time a concurrent uplink TBF

establishment request is received and the downlink TBF is candidate for resource
reallocation.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
886 / 1392
24.2.4.6.3.2 P405b - NB_DL_RES_REALLOC_SUCC_T2

Long Name
Definition

Trigger Condition

reallocation attempt for that TBF due to T2, i.e. due to the establishment of a
concurrent uplink TBF. Note that this counter shall be incremented only once even
if two TBF establishments are actually acknowledged. The counter can be used to
compute the success rate of the reallocation execution phase.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
887 / 1392
24.2.4.6.3.3 P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2

Long Name
Definition

Trigger Condition

acknowledgement from the MS. Note : because the corresponding uplink TBF
could not be established too, then P28 is also incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
888 / 1392
24.2.4.6.3.4 P423b - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2

Long Name
Definition
Number of attempts for downlink TBFs which were candidate for T2 resource
reallocation upon concurrent uplink TBF establishment but for which no better
candidate allocation could be found. The downlink TBFs were therefore not
reallocated.
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
be re-allocated and concurrence constraints make the uplink TBF establishment
impossible on the on-going downlink TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
889 / 1392
24.2.4.6.3.5 P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2

Long Name
Definition
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
890 / 1392
24.2.4.6.4 T3
24.2.4.6.4.1 P403c - NB_DL_RES_REALLOC_REQ_T3
Long Name
Definition
Number of downlink TBFs for which the corresponding Mobile Station was
candidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry
(due to trigger T3). Only candidate MSs for which the resource allocation algorithm
was called are taken into account.
Trigger Condition
Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incremented

by the number of DL TBFs for which the corresponding Mobile Station is
candidate for resource reallocation and for which the resource allocation algorithm
will be run to try and find a better allocation. This means that it is limited to
N_MAX_PERIODIC_REALLOC_T3 attempts upon each timer expiry. Note 1:
all downlink TBFs for which the resource allocation algorithm is run have to be
counted, even if the corresponding Mobile Station has an uplink-biased transfer
and therefore the MS is registered in the uplink list. Note 2: in case a given
mobile station has got two TBF(s) on-going and its resources are attempted to be
reallocated, then both P403c and P404c shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
891 / 1392
24.2.4.6.4.2 P405c - NB_DL_RES_REALLOC_SUCC_T3

Long Name
Definition

Trigger Condition

reallocation attempt for a downlink TBF due to T3. If the PACKET CONTROL
downlink TBF, both P405c and P406c shall be incremented. If after the resource
reallocation algorithm is run for a candidate Mobile Station having two TBFs
following T3, only the resources of the uplink TBF need to be reallocated, the
procedure shall be considered successful for the downlink TBF, irrespective of the
reallocation protocol outcome. Indeed, even if the reallocation protocol fails for
the uplink TBF, the downlink TBF will not be released and therefore this can be
considered as a success. This is another trigger for incrementing this counter.
This is required since P403c has been incremented. The counter can be used to
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
892 / 1392
24.2.4.6.4.3 P407c - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3

Long Name
Definition

Trigger Condition

acknowledgement from the MS. If an MS for which the resource reallocation was
attempted but failed had two TBFs and both were being reallocated, then both
counters P407c and P408c shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
893 / 1392
24.2.4.6.4.4 P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3

Long Name
Definition
Number of periodic attempts for downlink TBFs which were candidate for resource
reallocation 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 resource
reallocation 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 a
resource reallocation preparation failure.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
894 / 1392
24.2.4.6.4.5 P425c - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3

Long Name
Definition
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
895 / 1392
24.2.4.6.5 T4
24.2.4.6.5.1 P403d - NB_DL_RES_REALLOC_REQ_T4
Long Name
Definition
Number of downlink TBFs for which the corresponding Mobile Station was
candidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry
(due to Trigger T4). Only candidate MSs for which the resource allocation
algorithm was called are taken into account.
Trigger Condition

by the number of DL TBFs which are candidate for resource reallocation and
for which the resource allocation algorithm will tend to free EGPRS radio
resources.This means that it is limited to N_MAX_PERIODIC_REALLOC_T4
attempts upon each timer expiry. Note that in case a given mobile station has got
an UL and DL TBFs on-going and its resources are attempted to be reallocated
due to Trigger T4, then both P403d and P404d shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
896 / 1392
24.2.4.6.5.2 P405d - NB_DL_RES_REALLOC_SUCC_T4

Long Name
Definition
Number of T4 resource reallocation attempts that lead to reallocating successfully

a downlink TBF.
Trigger Condition
A Packet Control Acknowledgement message is received following a resource

reallocation attempt for a downlink TBF due to Trigger T4. Note that if the Packet
Control Acknowledgement message acknowledges reallocation of both an uplink
and a downlink TBF, both P405d and P406d shall be incremented. If after the
TBFs following T4, only the resources of the uplink TBF need to be reallocated,
the procedure shall be considered successful for the downlink TBF, irrespective of
the reallocation protocol outcome. Indeed, even if the reallocation protocol fails
for the uplink TBF, the downlink TBF will not be released and therefore this can
be considered as a success. This is another trigger for incrementing this counter.
This is required since P403d has been incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
The counter can be used to compute the success rate of the reallocation execution
phase.
897 / 1392
24.2.4.6.5.3 P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4

Long Name
Definition
Number of T4 resource reallocation attempts that lead to reallocating a downlink

TBF but the procedure failed due to radio problems and the TBF was released.
Trigger Condition

resource reallocation due to Trigger T4 for a downlink TBF but it was never
received, the TBF is released and this counter is incremented. Assuming that the
MS is not bugged, it means that the radio conditions were too poor for the MS to
counters P407d and P408d shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
898 / 1392
24.2.4.6.5.4 P423d - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4

Long Name
Definition
Number of periodic attempts for downlink TBFs which were candidate for T4
resource 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 resource
reallocation due to Trigger T4 but after the radio resource reallocation algorithm is
run, it is decided not to change its current allocation. As such, it corresponds to a
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
899 / 1392
24.2.4.6.5.5 P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4

Long Name
Definition
following T4 and an external TBF release request is received which forces to stop
the on-going resource reallocation (Flush-LL from the SGSN or GPRS suspension
request from the BSC)
Trigger Condition
being reallocated due Trigger T4 (i.e. either a Packet Uplink Assignment or a
Packet Timeslot Reconfigure message has been sent to the MS to reallocate its
uplink resources) and: - a FLUSH-LL is received from the SGSN, or - a GPRS
Suspension Request is received from the BSC for that Mobile Station before the
Packet Control Acknowledgement message is received.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
900 / 1392
24.2.4.7 DL TBF releases

24.2.4.7.1 All DL TBF releases
24.2.4.7.2.4 )
24.2.4.7.2.5 )
24.2.4.7.2 N/A
24.2.4.7.2.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 interface
problem) 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 incremented
by the number of DL TBF established on this cell. All pending LLC PDU in the
MFS are discarded.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
901 / 1392
24.2.4.7.2.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 of
TBF on a TRX (according the number of GCHs that will remain on the TRX after
the 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 are
Nb_TBFs_To_Release_DL TBF to release. The counter is incremented by the
value of Nb_TBFs_To_Release_DL.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
902 / 1392
24.2.4.7.2.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 TBF
is in downlink delayed phase.
Trigger Condition
Each time a DL TBF is released because of a radio failure when it is in downlink

delayed phase. Considered radio failures are: - a radio link lost due to N3105
(N3105 exceeds its limit) - too low TX efficiency.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
903 / 1392
24.2.4.7.2.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

radio failure 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: - a

radio link lost due to N3105 (N3105 exceeds its limit)
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
904 / 1392
24.2.4.7.2.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. Considered

radio 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 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
905 / 1392
24.2.4.7.2.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: - because

during the DL TBF no Packet Downlink Ack/Nack message is received for too long
a time, or, - because at the end of the DL TBF established in RLC acknowledged
mode no final Packet Downlink Ack/Nack message in RLC acknowledged
mode is received, or, - because at the end of the DL TBF established in RLC
unacknowledged mode no final Packet Control Acknowledgement message is
received.
Trigger Condition
The counter is incremented whenever a DL TBF is released: i) because the

timer T_TBF_ACTIV has expired, or, ii) because the timer T_TBF_BCK_REL
has expired. Note 1: The timer T_TBF_ACTIV is used to monitor the receipt
of the first DL LLC PDU after the TBF has been activated. Note 2: The timer
T_TBF_BCK_REL is used for three purposes: - during a DL TBF to monitor the
receipt of the Packet Downlink Ack/Nack messages when the transmit window
is stalled, - at the end of a DL TBF to monitor the receipt of the final Packet
Downlink Ack/Nack message (in RLC acknowledged mode) or final Packet Control
Acknowledgement message (in RLC unacknowledged mode), - at the end of an
UL TBF to monitor the receipt of the Packet Control Acknowledgement message
acknowledging the final Packet Uplink Ack/Nack message,
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
906 / 1392
24.2.4.7.2.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 stagnating
for too long a time.
Trigger Condition
The counter is incremented whenever a DL TBF is released because

the RLC counter N_StagnatingWindowDL exceeds the system parameter
N_STAGNATING_WINDOW_DL_LIMIT. In RLC acknowledged mode, the RLC
counter N_StagnatingWindowDL is incremented when the same oldest RLC data
block in the transmit window is not acknowledged by the received bitmap of the
last (EGPRS) Packet Downlink Ack/Nack message. Note: The cases where a DL
TBF is released because the transmit window has been stagnating for too long a
time should be due to MS errors.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
907 / 1392
24.2.4.7.2.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 of

the Flush message.
Trigger Condition
Whenever a DL TBF (establishing or on-going) is released due to the receipt of a

Flush 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. The
internal PCC-RLC-RELEASE-cnf primitive is used for incrementing the counter.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
908 / 1392
24.2.4.7.2.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 transition

from packet downlink transfer mode to packet idle mode further to the sending of
the first Packet Cell Change Order message. The counter is then incremented
whenever one of the following events occurs after the sending of the Packet Cell
Change Order message: i) an TBF-RELEASE-ind message with an abnormal
cause is received from RLC layer (for the DL TBF) while the MFS is waiting for the
acknowledgement of the Packet Cell Change Order message or while the MFS is
waiting for the FLUSH-LL message, or, ii) an TBF-RELEASE-cnf message is sent
to RLC layer (for the DL TBF) further to the receipt of the acknowledgement of
the Packet Cell Change Order message or further to the receipt of the Flush-LL
message. The counter is incremented only once per NC cell reselection execution.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
909 / 1392
24.2.4.7.2.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 release
of a DL TBF. The counter is then incremented for 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 message concerns a DL TBF which is still
on-going, ii) a Flush-LL message is received from the SGSN and this Flush-LL
message concerns a DL TBF which has been abnormally released in the previous
T_WAIT_FLUSH seconds.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
910 / 1392
24.2.4.7.2.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 to
the 04.60 RLC DATA BLOCK (FBI=1, polling) sent by the MFS for the last RLC
block to send, ie 04.60 (EGPRS) PACKET DOWNLINK ACK/NACK from the
mobile, with no DL retransmision required. This counter is also incremented in
case of DL TBF release due to concurrent establisment (UL + DL) i.e when the
MS is accessing the network via a Channel Request. (crossing cases DL data
and Channel Request from the MS).
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
911 / 1392
24.2.4.7.2.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 DL

packet transfer, the counter is incremented at each released TBF. When the TBF
is released due to a radio link failure linked to suspension, this counter is not
incremented (P302b is incremented in this case).
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
912 / 1392
24.2.4.7.2.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 from

BSC and the suspend procedure concerns a DL TBF which is still on-going 2) a
Suspend message is received from BSC and the suspend procedure concerns
a DL TBF which has been abnormally released in the previous T_WAIT_FLUSH
seconds.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
913 / 1392
24.2.4.8 DL/UL TBF monitoring per GPU

24.2.4.8.1 All DL/UL TBF monitoring per GPU
24.2.4.8.2 N/A
24.2.4.8.2.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 and

P30a,b,c (cell counters) for each cell mapped on GPU.
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL/UL TBF monitoring per GPU
Sub Domain 3
N/A
Measured Object
Sub_BSS (BSC/FABRIC)
External Comment
914 / 1392
24.2.4.8.2.2 P107 - NB_TBF_EST_REQ_GPU

Long Name
NB_TBF_EST_REQ_GPU
Definition
Number of Dl and UL establishments requests Sum of P91a,b,c,d,e,f and P62a,b,c

(cell counter ) for each cell mapped on GPU.
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL/UL TBF monitoring per GPU
Sub Domain 3
N/A
Measured Object
External Comment
915 / 1392
24.2.4.9 DTM
24.2.4.9.1 All DTM
24.2.4.9.2.17 )
24.2.4.9.2 N/A
24.2.4.9.2.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 MS is

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 of
the MS i.e. independently of information received from the BSC.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
External Comment
916 / 1392
24.2.4.9.2.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

BSC Shared DTM Info Indication with CS flag = 1 or - at reception of BSCGP
DTM REQUEST when no BSC Shared DTM Info Indication with CS flag had
been received previously for this MS or - at reception of BSCGP DTM GPRS
information carying an UL LLC PDU .
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
917 / 1392
24.2.4.9.2.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 the
first Packet downlink Ack/Nack message is received from the MS (case of DL
TBF)). Stopping : when in DTM mode the CS session or PS session are , normally
or abnormally , released. Note: The common duration during which a UL and a
DL are established is counted as one duration (UL and DL common time durations
are not cumulated). The time is provided in seconds with one significant value
after the comma (i.e. ROUND(10x) / 10). Note 1: The time duration of all periods
(active and delayed/extended) is taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
918 / 1392
24.2.4.9.2.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 start
of a CS session is received (first BSCGP BSC Shared DTM Info Indication with
CS=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
are received from the MS (case of UL TBF) or the first Packet downlink Ack/Nack
message 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 Info
Indication with CS=0 received) or when in dedicated mode , an indication of stop
of CS session is received. The time is provided in seconds with one significant
value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
919 / 1392
24.2.4.9.2.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 transfer

mode.
Trigger Condition
Cumulated time duration of all UL / DL TBFs established over the Granularity

period. Note : DTM capability of the MS is given in RA capabilities, which are
known only : - in case a DL LLC PDU has been received for this MS - in case
only an UL TBF exists, once the procedure for RA capability update is finished
(provided EN_RA_CAP_UPDATE = 1)
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
920 / 1392
24.2.4.9.2.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 a
MS in dedicated mode (and in GMM ready state). Note : - This counter applies
only to DTM capable mobiles. - DL LLC PDU sent with BSCGP DTM GPRS
information are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
921 / 1392
24.2.4.9.2.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 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
922 / 1392
24.2.4.9.2.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 Request
message.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
923 / 1392
24.2.4.9.2.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 block
for a MS in dedicated mode. Note 1 : This counter applies only to DTM capable
mobiles.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
924 / 1392
24.2.4.9.2.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 the
MS leaves the dual transfer mode or due to the establishment of a CS connection
when the MS enters the dual transfer mode. This counter also counts the DL
TBF release 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 or
an intracell handover occurs. - when in PTM the dedicated mode is entered.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
925 / 1392
24.2.4.9.2.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 the
MS leaves the dual transfer mode or due to the establishment of a CS connection
when the MS enters the dual transfer mode. This counter also counts the UL TBF
release due to an handover.
Trigger Condition
This counter is incremented for DTM capable MS with ongoing UL TBFs

established , when an abnormal UL TBF release, occurs : - when the DTM mode
is leaved ( release of the CS connection in DTM mode) - when in DTM mode an
intercell or an intracell handover occurs - when in PTM the dedicated mode is
entered.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
926 / 1392
24.2.4.9.2.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 due

to a lack of radio resources.
Trigger Condition
This counter is incremented when MFS has no suitable radio resources to enter in
DTM mode.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
927 / 1392
24.2.4.9.2.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 due

to a lack of radio resources.
Trigger Condition
This counter is incremented when the MFS sends the BSCGP DTM reject
message in case of lack of radio resources available.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
928 / 1392
24.2.4.9.2.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 in
the BSCGP DTM GPRS information messages received in MFS.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
929 / 1392
24.2.4.9.2.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 carried
in the BSCGP DTM GPRS information messages sent by MFS. Note : Possible
repetitions of the messages are not taken into account i.e only the DL_LLC_PDU
acknowledged by BSCGP DTM GPRS information ack message are take into
account.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
930 / 1392
24.2.4.9.2.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 a

PFC-CREATION is received and the PFC indicates streaming or conversational.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
931 / 1392
24.2.4.9.2.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 MFS

proposes a Default Best Effort ABQP in response to a RT-PFC creation received
in the cell.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
932 / 1392
24.2.4.9.2.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 a

PFC-CREATION is received and the PFC indicates streaming or conversational.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
933 / 1392
24.2.4.9.2.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 a
Default Best Effort ABQP in response to a RT-PFC creation received in the cell.
Sub Domain 1
Radio interface
Sub Domain 2
DTM
Sub Domain 3
N/A
Measured Object
Cell
External Comment
934 / 1392
24.2.4.10 EDA
24.2.4.10.1 All EDA
(Section 24.2.4.10.2.2 )
24.2.4.10.2 N/A
24.2.4.10.2.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 EDA
either in GPRS mode or in EGPRS mode or in both modes. If EDA is supported in
both modes, the counter shall be incremented only by one.
Sub Domain 1
Radio interface
Sub Domain 2
EDA
Sub Domain 3
N/A
Measured Object
External Comment
935 / 1392
24.2.4.10.2.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 connections
in active phase and operating in EDA mode , whatever the UL pdch EDA
configuration used, in the cell over the granularity period. The counter starts :
when an UL TBF in active phase and in DA mode is reallocated in EDA mode,
or when an UL TBF in EDA mode and in Extended Uplink TBF Mode wakes up
or when an UL TBF is established directly in EDA mode (in this case the start of
active phase is taken into account). The counter stops: when an UL TBF in EDA
mode goes to Extended Uplink TBF Mode, or when an UL TBF in active phase
and in EDA 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
TBFs and to both acknowledge or unacknowledge mode. Note 2 :The case the
UL TBF is released due to a NC cell reselection is managed as an abnormal UL
TBF release. The time is provided in seconds with one significant value after
the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
EDA
Sub Domain 3
N/A
Measured Object
Cell
External Comment
936 / 1392
24.2.4.10.2.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 their
lifetime.
Trigger Condition
This counter is incremented when an UL TBF is directly allocated in EDA mode or

is reallocated in EDA mode at least one time during its lifetime. Note: The counter
shall be incremented at most by one per uplink TBF.
Sub Domain 1
Radio interface
Sub Domain 2
EDA
Sub Domain 3
N/A
Measured Object
Cell
External Comment
937 / 1392
24.2.4.10.2.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 but
that 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 known to

be uplink and the mobile station is allowed to use the EDA mode. - The bias is
computed and equal to uplink and the mobile station is allowed to use the EDA
mode. Notes: - A mobile station is known here as allowed to use the EDA mode if
it supports EDA and if the OMC setting allows it using EDA. Note: - This means
the N_UL_BIAS_FOR_EDA (when superior to 1) and BIAS_LIMIT_EDA (when
superior to 1) conditions are not taken into account for this counter. -The counter
shall be incremented at most by one per uplink TBF.
Sub Domain 1
Radio interface
Sub Domain 2
EDA
Sub Domain 3
N/A
Measured Object
Cell
External Comment
938 / 1392
24.2.4.10.2.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 mode to

EDA mode or from EDA mode to DA mode. Note : Such TBF have necessarily
used at least one time the EDA mode during their lifetime.
Sub Domain 1
Radio interface
Sub Domain 2
EDA
Sub Domain 3
N/A
Measured Object
Cell
External Comment
939 / 1392
24.2.4.11 Inter-NSE DL LLC PDU re-routing

24.2.4.11.1 All Inter-NSE DL LLC PDU re-routing
24.2.4.11.2.4 )
)
24.2.4.11.2 N/A
24.2.4.11.2.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 an
order from the SGSN to reroute DL LLC PDUs to another cell belonging to the
same 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 SGSN
supports the INR option, not the new NSEI
Sub Domain 1
Radio interface
Sub Domain 2
Inter-NSE DL LLC PDU re-routing
Sub Domain 3
N/A
Measured Object
Cell
External Comment
940 / 1392
24.2.4.11.2.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 are
fulfilled to reroute DL LLC PDUs to another cell belonging to another NSE but to
the 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 supports
the Inter-NSE Rerouting feature and the MFS receives a FLUSH-LL message
containing the new BVCI and the new NSEI and the new NSEI is part of the
serving BSS, ii) or the SGSN does not support the Inter-NSE Rerouting feature
and the autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTING set
to enabled) and the MFS receives a FLUSH-LL message following a cell change
occuring between two NSEs within the same BSS and within the same routing
area.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
941 / 1392
24.2.4.11.2.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 are
fulfilled to reroute DL LLC PDUs to another cell belonging to another NSE and to
another 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
supports the Inter-NSE Rerouting feature and the MFS receives a FLUSH-LL
message containing the new BVCI and the new NSEI and the new NSEI is part
of a different BSS than the BSS of the source cell ii) or the SGSN does not
support the Inter-NSE Rerouting feature and the autonomous rerouting is enabled
(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives a
FLUSH-LL message following a cell change occuring between two NSEs and
between two different BSSs , within the same routing area.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
942 / 1392
24.2.4.11.2.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 Rerouting
feature, 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 the
Inter-NSE Rerouting feature and the MFS receives a FLUSH-LL message not
containing the new BVCI
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
943 / 1392
24.2.4.11.2.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 Rerouting
feature and autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTING
set 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 following
a 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 not
support the Inter-NSE Rerouting feature and autonomous rerouting is enabled
FLUSH-LL message not containing the new BVCI following a cell change occuring
within the same routing area and within the same NSE.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
944 / 1392
24.2.4.11.2.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 Rerouting
feature and autonomous rerouting is enabled (EN_AUTONOMOUS_REROUTING
set to enabled), the MFS counts the number of times the MFS receives a
FLUSH-LL message following a cell change occuring between two different
routing areas.
Trigger Condition
The counter is incremented in the following case: the SGSN does not
support the Inter-NSE Rerouting feature and autonomous rerouting is enabled
FLUSH-LL message following a cell change occuring between two different
routing areas.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
945 / 1392
24.2.4.12 PFC
24.2.4.12.1 All PFC
24.2.4.12.2 N/A
24.2.4.12.2.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 into

the cell.
Trigger Condition
- Incremented, in the target cell, when PCC cannot accept a RT-PFC getting into
the cell because of lack of resource and downgrades the RT-PFC to the Default
Best Effort ABQP. -Incremented when PCC cannot accept a RT-PFC getting into
the cell because the flag EN_STREAMING in the cell is set to OFF. Note : MS in
dedicated mode or in DTM mode are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
946 / 1392
24.2.4.12.2.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 cell
following a cell reselection.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
947 / 1392
24.2.4.12.2.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 each

time a RT-PFC is impacted.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
948 / 1392
24.2.4.12.2.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 Default
Best Effort ABQP due to defense mechanism (lack of resources) during its time life.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
949 / 1392
24.2.4.12.2.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 cell
reselection of the MS.
Trigger Condition
Incremented, in the source cell, when a RT-PFC is successfully forwarded

to another cell following a cell reselection. Note: This counter can be only
incremented if the MFS manages the target cell.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
950 / 1392
24.2.4.12.2.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 sent

to BSSGP. Note : Repetitions of PFC-DOWNLOAD performed by BSSGP are
not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
951 / 1392
24.2.4.12.2.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 to
RT mode.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
952 / 1392
24.2.4.12.2.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 to
RT mode.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
953 / 1392
24.2.4.12.2.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 is

received by RRM-PCC.
Trigger Condition
Incremented by RRM-PCC each time a PFC-CREATION is received with the 2

following characteristics : - The received PFC indicates either a background or an
interactive, - The received PFC indicates an unacknowledged RLC mode.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
954 / 1392
24.2.4.12.2.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 received

by RRM-PCC.
Trigger Condition
Incremented by RRM-PCC each time a PFC-CREATION is received with the

2 following characteristics : - The received PFC indicates a streaming , - The
received PFC indicates an unacknowledged RLC mode.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
955 / 1392
24.2.4.12.2.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 to

a RT-PFC creation received in the cell. - Incremented when PCC downgrades a
RT-PFC to the Default Best Effort ABQP by defense mechanism. - Incremented
when the received RT-PFC creation indicates streaming and EN_STREAMING
is false. - Incremented when the received PFC creation contains an inconsistent
ABQP content. - The MS RA capability cannot be retrieved from SGSN. Note :
MS in dedicated mode or in DTM mode are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
956 / 1392
24.2.4.12.2.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, or
because it is a RT-PFC with RLC unacknowledged mode. Incremented when the
maximum number of PFC per MS is reached.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
957 / 1392
24.2.4.12.2.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 is

received from BSSGP.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
958 / 1392
24.2.4.12.2.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 PFC

is either a streaming or a conversational.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
959 / 1392
24.2.4.12.2.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 PFC

is either a background or an interactive.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
960 / 1392
24.2.4.12.2.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 successfully

by RRM-PCC.
Trigger Condition
Incremented by RRM-PCC each time a streaming PFC-CREATION is received

and the PFC is created successfully without any downgrading.
Sub Domain 1
Radio interface
Sub Domain 2
PFC
Sub Domain 3
N/A
Measured Object
Cell
External Comment
961 / 1392
24.2.4.13 Suspend / Resume

24.2.4.13.1 All Suspend / Resume
24.2.4.13.2 N/A
24.2.4.13.2.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 1
Radio interface
Sub Domain 2
Suspend / Resume
Sub Domain 3
N/A
Measured Object
Cell
External Comment
962 / 1392
24.2.4.13.2.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 1
Radio interface
Sub Domain 2
Suspend / Resume
Sub Domain 3
N/A
Measured Object
Cell
External Comment
963 / 1392
24.2.4.14 UL TBF establishments

24.2.4.14.1 All UL TBF establishments
24.2.4.14.2.8 )
24.2.4.14.2.13 )
24.2.4.14.2.16 )
24.2.4.14.2 N/A
24.2.4.14.2.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: This

Trigger Condition
When an UL TBF cannot be established, due to GPU congestion. GPU congestion

means that the maximum capacity of at least one DSP on the GPU is reached in
terms of resources GCH and/or PDCH. Generally, for all counters related to TBF
establishment failures, only the last reported failure cause is taken into account.
Note: This counter may also be incremented when the MS have requested a single
block access on CCCH to send a 04.60 PACKET MEASUREMENT REPORT
message or a 04.60 PACKET CELL CHANGE FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF establishments
Sub Domain 3
N/A
Measured Object
Cell
External Comment
964 / 1392
24.2.4.14.2.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 limitations

of the GPU. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition
Whenever a UL TBF cannot be established due to CPU processing power

limitations of the GPU. Note: This counter may also be incremented when the
MS have requested a single block access on CCCH to send a 04.60 PACKET
MEASUREMENT REPORT message or a 04.60 PACKET CELL CHANGE
FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
965 / 1392
24.2.4.14.2.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:

Trigger Condition
The counter is incremented whenever a UL TBF establishment fails due to a lack

of Ater resources. A lack of Ater resources occurs when there is not enough Ater
nibbles to serve the UL TBF request. For BTS evolium : the number of GCH that
can be established and/or redistributed is < Nb_GCH_FOR_TBF_ESTAB and
the number of free Ater nibbles is < Nb_GCH_FOR_TBF_ESTAB. For DRFU
BTS : Lack of free Ater nibbles to serve the GCHs. 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, or receipt of a CHANNEL REQUEST on RACH when the UL TBF cannot
be served due to a lack of transmission resources. Note: This counter may also
be incremented when the MS have requested a single block access on CCCH to
send a 04.60 PACKET MEASUREMENT REPORT message or a 04.60 PACKET
CELL CHANGE FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
966 / 1392
24.2.4.14.2.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:

Trigger Condition
The counter is incremented whenever a UL TBF establishment fails due to a

lack of Abis resources. A lack of Abis transmission resources occurs when
there is not enough Abis nibbles to serve the UL TBF request. For BTS
evolium only : the number of GCH that can be established and or redistributed
is < 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. The
counter is incremented at the expiry of the PDU lifetime when the last attempt fails
to establish the UL TBF due to a lack of transmission resources. 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, or receipt of a CHANNEL REQUEST on RACH when the
UL TBF cannot be served due to a lack of transmission resources. Note: This
counter may also be incremented when the MS have requested a single block
access on CCCH to send a 04.60 PACKET MEASUREMENT REPORT message
or a 04.60 PACKET CELL CHANGE FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
967 / 1392
24.2.4.14.2.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 to
guarantee a minimum throughput for the UL TBF. - This may happen when the
number of TBFs is too high compared to the number of available GCHs. - - or
the MAX_TBF_TRX_UL constraint. Note: This counter applies to GPRS and
EGPRS MS.
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 GCH
available to serve the UL TBF is < Min_Nb_GCH. For DRFU BTS : Counter not
incremented (=0). 2) or the MAX_TBF_TRX_UL constraint: For BTS evolium :
The MAX_TBF_TRX_UL limit is reached on all the TRXs available for PS traffic
in the cell. For DRFU BTS : Counter not incremented (=0). The counter is
incremented at the expiry of the PDU lifetime (T_ul_access_max) or when the
attempt fails to establish the UL TBF due to too low number of available GCH
(too many TBFs on the TRX compared to the number of available GCHs) or due
to the MAX_TBF_TRX_UL constraint.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
968 / 1392
24.2.4.14.2.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 the
internal 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, or
receipt of a CHANNEL REQUEST on RACH when the UL TBF cannot be served
due to DSP CPU load / overload. Note: This counter may also be incremented
when the MS have requested a single block access on CCCH to send a 04.60
PACKET MEASUREMENT REPORT message or a 04.60 PACKET CELL
CHANGE FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
969 / 1392
24.2.4.14.2.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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
970 / 1392
24.2.4.14.2.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 "extended
uplink" to "active". It corresponds to the UL TBF becoming active again within
the extended uplink phase duration.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
971 / 1392
24.2.4.14.2.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:

Trigger Condition
The counter is incremented whenever an UL TBF establishment fails due to a lack

of radio resources. A lack of radio resource occurs: i) if the maximum number of
MSs per slave PDCH in uplink is reached for all the slave PDCHs allocated to the
MFS, or ii) if there is no TAI or TFI left in the MFS. or iii) if no PDCH are granted
to MFS due to a CS congestion and max_pdch_high_load is null. 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, or on receipt of a CHANNEL REQUEST on RACH when
the UL TBF cannot be served due to a lack of radio resources. Note: This counter
may also be incremented when the MS have requested a single block access on
CCCH to send a 04.60 PACKET MEASUREMENT REPORT message or a 04.60
PACKET CELL CHANGE FAILURE message.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
972 / 1392
24.2.4.14.2.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

operational state 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 on

reception of PCC-RLC-RELEASE-ind with Cause = "no transfer start" - Or after
Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource
reallocation due to T2 for a downlink TBF (with uplink TBF establishment) but
it was never received. Generally, for all counters related to TBF establishment
failures, only the last reported failure cause is taken into account
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
973 / 1392
24.2.4.14.2.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 in

packet idle mode - the MS have requested an uplink TBF establishment Note: This
Trigger Condition
This counter is incremented i) when the TLLI is received during a one phase
access UL TBF establishment triggered on PRACH, or ii) when the TBF start
indication is received during a two phase access UL TBF establishment triggered
on PRACH.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
974 / 1392
24.2.4.14.2.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 packet

transfer mode. Note: This counter applies to GPRS and EGPRS MS.
Trigger Condition
When the TBF start indication is received during an UL TBF establishment on

PACCH.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
975 / 1392
24.2.4.14.2.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

packet idle mode - the MS have requested an uplink TBF establishment Note: This
Trigger Condition
This counter is incremented i) when the TLLI is received during a one phase
access UL TBF establishment triggered on RACH, or ii) when the TBF start
indication is received during a two phase access UL TBF establishment triggered
on RACH.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
976 / 1392
24.2.4.14.2.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

packet idle mode - the MS requests an uplink TBF establishment Note 1: This
counter applies to GPRS and EGPRS MS. Note 2: The access cause "Single
Block without TBF establishment" is not taken into account in this counter, as this
access cause does not lead to the establishment of an uplink TBF.
Trigger Condition
This counter is incremented whenever a 04.60 (EGPRS) PACKET CHANNEL

REQUEST is received on PRACH from the MS requesting an uplink TBF
establishment (i.e. all access causes except the access cause "Single block
without TBF establishment"). Generally, all counters related to TBF establishment
requests only take into account the first attempt, i.e. no network repetitions are
counted. (Repetitions from the MS are counted.)
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
977 / 1392
24.2.4.14.2.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 packet

transfer 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] is

received on PACCH channel from the MS. Note that the counter is incremented
whether the request is served with a PACKET UPLINK ASSIGNMENT or a
PACKET TIMESLOT RECONFIGURE (which means that the DL TBF resources
are re-assigned upon concurrent UL TBF establishment). Generally, all counters
related to TBF establishment requests only take into account the first attempt,
i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
978 / 1392
24.2.4.14.2.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.

Note 1: This counter applies to GPRS and EGPRS MS. Note 2: This counter
takes into account requests leading to both an uplink TBF establishment or a
single block allocation used to carry a 04.60 PACKET MEASUREMENT REPORT
message or a 04.60 PACKET CELL CHANGE FAILURE message (when the
NC2 feature is activated).
Trigger Condition
This counter is incremented whenever a 04.18 CHANNEL REQUEST message

with access cause "One phase packet access" or "Single block packet access", or
a 04.18 EGPRS PACKET CHANNEL REQUEST is received on RACH from the
MS. Generally, all counters related to TBF establishment requests only take into
account the first attempt, i.e. no network repetitions are counted. (Repetitions
from the MS are counted.)
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
979 / 1392
24.2.4.14.2.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 (Gb
interface problem) associated with the cell.
Trigger Condition
Whenever the BVC associated with the cell is unavailable (which implies: cell
operational state "disabled"), the counter is incremented with the nb of UL TBF in
establishment phase.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
980 / 1392
24.2.4.15 UL TBF re-allocations

24.2.4.15.1 All UL TBF re-allocations
24.2.4.15.2.3 )
24.2.4.15.3.3 )
)
24.2.4.15.2.4 )
24.2.4.15.3.4 )
24.2.4.15.4.4 )
24.2.4.15.5.4 )
24.2.4.15.2.5 )
24.2.4.15.3.5 )
24.2.4.15.4.5 )
24.2.4.15.5.5 )
981 / 1392
24.2.4.15.2 T1
24.2.4.15.2.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 least
one 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 CS

pre-emption process. Two cases are possible : - a uplink TBF has its PACCH
impacted by a soft PDCH pre-emption, - the maximum allowed (M)CS of a uplink
TBF will no longer be possible to serve because of an M-EGCH link size reduction
due to a soft PDCH pre-emption. The M-EGCH link to consider is the one of the
TRX currently supporting the uplink TBF. That case is only valid for Evolium BTSs
and can only occur in case the basic Abis nibbles of some of the soft-preempted
PDCHs 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)CS
and is established on a TRX whose M-EGCH link owns 5 GCHs, then if the CS
preemption process leads to an M-EGCH link having only 4 GCHs left (because
one of the GCHs of the M-EGCH link is using a basic Abis nibble mapped to
a pre-empted PDCH), then the uplink TBF will be impacted, and the counter
incremented. The counter is also incremented by one each time a uplink TBF has
a concurrent downlink TBF impacted by the CS preemption process (the same
conditions as the above ones apply for the downlink direction), in case the uplink
TBF was not impacted. In both cases, the MFS will try to reallocate the resources
of the MS, which will require reallocating the TBFs in one or in both directions.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF re-allocations
Sub Domain 3
T1
Measured Object
Cell
External Comment
982 / 1392
24.2.4.15.2.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 an

uplink TBF (due to trigger T1).
Trigger Condition

reallocation attempt for that uplink TBF due to T1. If the PACKET CONTROL
downlink TBF, this counter shall be incremented as well as P405a. If after the
TBFs following T1, only the resources of the downlink TBF need to be reallocated,
the procedure shall be considered successful for the uplink TBF, irrespective of
for the downlink TBF, the uplink TBF will not be released and therefore this can
This is required since P404a has been incremented. Similarly, if after the resource
reallocation algorithm is run for a candidate Mobile Station having two TBFs
following T1, there is a preparation failure but the PACCH of the uplink TBF is not
impacted by soft PDCH pre-emption, then the uplink TBF will remain alive and this
counter shall be incremented. The counter can be used to compute the success
rate of the reallocation execution phase. Note: this counter takes into account also
the successful T1 reallocations where the MAX_(M)CS of an UL TBF is decreased
without any change of its radio allocation.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
983 / 1392
24.2.4.15.2.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 TBF

but the procedure failed due to radio problems and the TBF was released (due
to trigger T1).
Trigger Condition

resource reallocation due to T1 for an uplink TBF but it was never received,
acknowledgement from the MS. If an MS for which the resource reallocation
protocol was attempted but failed had two TBFs and both were being reallocated,
then both counters P407a and P408a shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
984 / 1392
24.2.4.15.2.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, T1

resource reallocation has been attempted but no candidate allocation could be
found. The TBF could therefore not be reallocated.
Trigger Condition
The counter is incremented each time a uplink TBF is impacted by a CS

pre-emption process , the resource reallocation algorithm is run but no candidate
allocation can be found for the uplink TBF. As such, it corresponds to a resource
reallocation preparation failure.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
985 / 1392
24.2.4.15.2.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 running
Trigger Condition
The counter is incremented each time the resources of an uplink TBF are
being reallocated (ie either a PACKET UPLINK ASSIGNMENT or a PACKET
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T1
Measured Object
Cell
External Comment
986 / 1392
24.2.4.15.3 T2
24.2.4.15.3.1 P404b - NB_UL_RES_REALLOC_REQ_T2
Long Name
Definition
Number of uplink TBFs which are candidate for resource reallocation upon
concurrent downlink TBF establishment.
Trigger Condition
The counter is incremented by one each time a concurrent downlink TBF

establishment request is received and the uplink TBF is candidate for resource
reallocation.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
987 / 1392
24.2.4.15.3.2 P406b - NB_UL_RES_REALLOC_SUCC_T2

Long Name
Definition

Trigger Condition

reallocation attempt for that TBF due to T2, i.e. due to the establishment of a
concurrent downlink TBF. Note that this counter shall be incremented only once
even if two TBF establishments are actually acknowledged. The counter can be
used to compute the success rate of the reallocation execution phase.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
988 / 1392
24.2.4.15.3.3 P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2

Long Name
NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2
Definition

to trigger T2).
Trigger Condition

acknowledgement from the MS. Note : because the corresponding downlink TBF
could not be established, then P15 is also incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
989 / 1392
24.2.4.15.3.4 P424b - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2

Long Name
Definition
Number of attempts for uplink TBFs which were candidate for T2 resource
reallocation upon concurrent downlink TBF establishment but for which no
candidate allocation could be found apart from their current allocation. The uplink
TBFs were therefore not reallocated.
Trigger Condition
Upon concurrent downlink TBF establishments, the counter is incremented when :

i) The downlink TBF cannot be served because the on-going uplink TBF cannot be
re-allocated and concurrence constraints make the downlink TBF establishment
impossible on the on-going uplink TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
990 / 1392
24.2.4.15.3.5 P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2

Long Name
Definition
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T2
Measured Object
Cell
External Comment
991 / 1392
24.2.4.15.4 T3
24.2.4.15.4.1 P404c - NB_UL_RES_REALLOC_REQ_T3
Long Name
Definition
Number of uplink TBFs for which the corresponding Mobile Station was candidate
for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due to
trigger T3). Only candidate MSs for which the resource allocation algorithm was
called are taken into account.
Trigger Condition

by the number of UL TBFs for which the corresponding Mobile Station is
candidate for resource reallocation and for which the resource allocation algorithm
will be run to try and find a better allocation. This means that it is limited to
N_MAX_PERIODIC_REALLOC_T3 attempts upon each timer expiry. Note 1:
all uplink TBFs for which the resource allocation algorithm is run have to be
counted, even if the corresponding Mobile Station has a downlink-biased transfer
and therefore the MS is registered in the downlink list. Note 2: in case a given
mobile station has got two TBF(s) on-going and its resources are attempted to
be reallocated,
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
992 / 1392
24.2.4.15.4.2 P406c - NB_UL_RES_REALLOC_SUCC_T3

Long Name
Definition

Trigger Condition

reallocation attempt for an uplink TBF due to T3. If the PACKET CONTROL
downlink TBF, this counter shall be incremented as well as P405c. If after the
This is required since P404c has been incremented. The counter can be used to
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
993 / 1392
24.2.4.15.4.3 P408c - NB_UL_TBF_RADIO_PB_RES_REALLOC_T3

Long Name
NB_UL_TBF_RADIO_PB_RES_REALLOC_T3
Definition

to trigger T3).
Trigger Condition

counters P407c and P408c shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
994 / 1392
24.2.4.15.4.4 P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3

Long Name
Definition
Number of periodic attempts for uplink TBFs which were candidate for resource
reallocation due to T3 but for which no candidate allocation could be found apart
from their current allocation. The uplink TBFs were therefore not reallocated.
Trigger Condition
The counter is incremented each time an uplink TBF is candidate for resource
reallocation 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 a
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
995 / 1392
24.2.4.15.4.5 P426c - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3

Long Name
Definition
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T3
Measured Object
Cell
External Comment
996 / 1392
24.2.4.15.5 T4
24.2.4.15.5.1 P404d - NB_UL_RES_REALLOC_REQ_T4
Long Name
Definition
Number of uplink TBFs for which the corresponding Mobile Station was candidate
for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due to
Trigger T4). Only candidate MSs for which the resource allocation algorithm was
called are taken into account.
Trigger Condition

by the number of UL TBFs which are candidate for resource reallocation and
for which the resource allocation algorithm will tend to free EGPRS radio
resources.This means that it is limited to N_MAX_PERIODIC_REALLOC_T4
attempts upon each timer expiry. Note that in case a given mobile station has got
an UL and DL TBFs on-going and its resources are attempted to be reallocated
due to Trigger T4, then both P403d and P404d shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
997 / 1392
24.2.4.15.5.2 P406d - NB_UL_RES_REALLOC_SUCC_T4

Long Name
Definition
Number of T4 resource reallocation attempts that lead to reallocating successfully

an uplink TBF
Trigger Condition
A Packet Control Acknowledgement message is received following a resource

reallocation attempt for an uplink TBF due to Trigger T4. Note that if the Packet
Control Acknowledgement message acknowledges reallocation of both an uplink
and a downlink TBFs, both P405d and P406d shall be incremented. If after the
This is required since P404d has been incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
The counter can be used to compute the success rate of the reallocation execution
phase.
998 / 1392
24.2.4.15.5.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 uplink

TBF but the procedure failed due to radio problems and the TBF was released.
Trigger Condition

resource reallocation due to Trigger T4 for an uplink TBF but it was never received,
counters P407d and P408d shall be incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
999 / 1392
24.2.4.15.5.4 P424d - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4

Long Name
Definition
Number of periodic attempts for uplink TBFs which were candidate for T4 resource
reallocation but for which no suitable candidate allocation could be found apart
from 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 resource
reallocation due to Trigger T4 but after the radio resource reallocation algorithm is
run, it is decided not to change its current allocation. As such, it corresponds to a
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
1000 / 1392
24.2.4.15.5.5 P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4

Long Name
Definition
following T4 and an external TBF release request is received which forces to stop
the on-going resource reallocation (Flush-LL from the SGSN or GPRS suspension
request from the BSC).
Trigger Condition
being reallocated due Trigger T4 (i.e. either a Packet Uplink Assignment or a
Packet Timeslot Reconfigure message has been sent to the MS to reallocate its
Suspension Request is received from the BSC for that Mobile Station before the
Packet Control Acknowledgement message is received.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
T4
Measured Object
Cell
External Comment
1001 / 1392
24.2.4.16 UL TBF releases

24.2.4.16.1 All UL TBF releases
24.2.4.16.2.5 )
24.2.4.16.2.6 )
24.2.4.16.2.7 )
(Section 24.2.4.16.2.8 )
)
24.2.4.16.2 N/A
24.2.4.16.2.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 of
TBF on a TRX (according the number of GCHs that will remain on the TRX after
the 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 are
Nb_TBFs_To_Release_UL TBF to release. The counter is incremented by the
value of Nb_TBFs_To_Release_UL.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1002 / 1392
24.2.4.16.2.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 in

extended uplink phase.
Trigger Condition
Each time a UL TBF is released because of a radio failure when it is in

extended uplink phase. Considered radio failures are: - a radio link lost due to
N3101 or N3103 (N3101 or N3103 exceeds its limit) - Too low TX efficiency. N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit).
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1003 / 1392
24.2.4.16.2.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 the
reply to the 04.60 PACKET ACK/NACK (FINAL, polling) sent by the MFS on the
last received RLC block, with no UL retransmission required.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1004 / 1392
24.2.4.16.2.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 interface
problem) 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 incremented
by the number of UL TBF established in this cell.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1005 / 1392
24.2.4.16.2.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

Trigger Condition
A UL TBF is released because of a radio failure. Considered radio failure is: - a

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1006 / 1392
24.2.4.16.2.6 P302c_2 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103

Long Name
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1007 / 1392
24.2.4.16.2.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

radio 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 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1008 / 1392
24.2.4.16.2.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

radio failure is: - a radio link lost due to N_POLLING_EUTM (N_POLLING_EUTM
exceeds its limit)
Trigger Condition

radio link lost due to N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit)
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1009 / 1392
24.2.4.16.2.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: - because

during the UL TBF no UL RLC blocks is received for too long a time, or - because
at the end of the UL TBF no answer to the final Packet Uplink Akc/Nack message
is received.
Trigger Condition
The counter is incremented whenever an UL TBF is released: i) because the RLC

counter 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 counter
N_UL_DUMMY is incremented whenever a dummy UL RLC block is received from
the MS. Note 2: The timer T_TBF_BCK_REL is used for three purposes: - during
a DL TBF to monitor the receipt of the Packet Downlink Ack/Nack messages when
the transmit window is stalled, - at the end of a DL TBF to monitor the receipt
of the final Packet Downlink Ack/Nack message (in RLC acknowledged mode)
or final Packet Control Acknowledgement message (in RLC unacknowledged
mode), - at the end of an UL TBF to monitor the receipt of the Packet Control
Acknowledgement message acknowledging the final Packet Uplink Ack/Nack
message,
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1010 / 1392
24.2.4.16.2.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 stagnating
for too long a time.
Trigger Condition
The counter is incremented whenever an UL TBF is released because

the RLC counter N_StagnatingWindowUL exceeds the system parameter
N_STAGNATING_WINDOW_UL_LIMIT. The RLC counter N_StagnatingWindowUL
is incremented provided that the receive window is stalled whenever an UL RLC
data 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 Uplink
Ack/Nack message. Note 1: The receive window state variable V(Q) denotes
the lowest BSN not yet received (modulo SNS). It corresponds to the oldest UL
RLC data block in the received window. Note 2: The cases where an UL TBF is
released because the receive window has been stagnating for too long a time
should be due to MS errors or radio problems (due to the non-receipt of Packet UL
Ack/Nack messages).
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1011 / 1392
24.2.4.16.2.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 the
Flush message.
Trigger Condition
Whenever a UL TBF (establishing or on-going) is released due to the receipt of a

Flush 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. The
internal PCC-RLC-RELEASE-cnf primitive is used for incrementing the counter.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1012 / 1392
24.2.4.16.2.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 transition

from packet uplink transfer mode to packet idle mode further to the sending of
the first Packet Cell Change Order message. The counter is then incremented
whenever one of the following events occurs after the sending of the Packet Cell
Change Order message: i) an TBF-RELEASE-ind message with an abnormal
cause is received from RLC layer (for the UL TBF) while the MFS is waiting for the
acknowledgement of the Packet Cell Change Order message or while the MFS is
waiting for the FLUSH-LL message, or, ii) an TBF-RELEASE-cnf message is sent
to RLC layer (for the UL TBF) further to the receipt of the acknowledgement of
the Packet Cell Change Order message or further to the receipt of the Flush-LL
message. The counter is incremented only once per NC cell reselection execution.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1013 / 1392
24.2.4.16.2.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 release
of an UL TBF. The counter is then incremented for 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 message concerns an UL TBF which is still
on-going, ii) a Flush-LL message is received from the SGSN and this Flush-LL
message concerns an UL TBF which has been abnormally released in the
previous T_WAIT_FLUSH seconds.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1014 / 1392
24.2.4.16.2.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 UL

packet transfer, the counter is incremented at each released TBF. When the TBF
is released due to a radio link failure linked to suspension, this counter is not
incremented (P302c is incremented in this case).
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1015 / 1392
24.2.4.16.2.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 from

BSC and the suspend procedure concerns an UL TBF which is still on-going 2) a
Suspend message is received from BSC and the suspend procedure concerns
an UL TBF which has been abnormally released in the previous T_WAIT_FLUSH
seconds.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF releases
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1016 / 1392
24.3 Resource availability and usage

24.3.1 All Resource availability and usage
(Section 24.3.5.9.2.1 )
(Section 24.3.5.9.2.2 )
(Section 24.3.5.9.2.3 )
(Section 24.3.5.9.2.4 )
24.3.5.3.2.1 )
1017 / 1392

(Section 24.3.5.3.2.2 )
(Section 24.3.5.9.2.5 )
24.3.5.6.2.7 )
1018 / 1392

1019 / 1392

24.3.5.9.2.18 )
24.3.2.2.2.1 )
(Section 24.3.2.2.2.2 )
24.3.2.2.2.3 )
)
(Section 24.3.5.3.2.15 )
(Section 24.3.5.3.2.16 )
(Section 24.3.5.3.2.17 )
(Section 24.3.5.3.2.18 )
24.3.5.8.2.1 )
24.3.5.8.2.2 )
24.3.5.8.2.3 )
24.3.5.8.2.4 )
24.3.5.8.2.5 )
24.3.5.8.2.6 )
24.3.5.8.2.7 )
24.3.5.8.2.8 )
24.3.5.8.2.9 )
1020 / 1392

24.3.5.8.2.10 )
24.3.5.8.2.11 )
24.3.5.2.2.1 )
24.3.5.2.2.2 )
24.3.5.2.2.3 )
24.3.5.2.2.4 )
24.3.5.8.2.12 )
24.3.5.8.2.13 )
24.3.5.2.2.5 )
24.3.5.2.2.6 )
24.3.5.8.2.14 )
24.3.5.2.2.7 )
24.3.5.8.2.15 )
24.3.5.8.2.16 )
24.3.5.8.2.17 )
24.3.5.8.2.18 )
24.3.5.8.2.19 )
24.3.5.8.2.20 )
24.3.5.8.2.21 )
24.3.5.8.2.22 )
24.3.5.8.2.23 )
24.3.5.8.2.24 )
24.3.5.8.2.25 )
1021 / 1392

24.3.5.2.2.8 )
24.3.5.2.2.9 )
24.3.5.2.2.10 )
24.3.5.2.2.11 )
24.3.5.2.2.12 )
24.3.5.2.2.13 )
24.3.5.2.2.14 )
24.3.5.2.2.15 )
24.3.5.2.2.16 )
24.3.5.2.2.17 )
24.3.2 Abis interface

24.3.2.1 All Abis interface
24.3.2.2.2.1 )
(Section 24.3.2.2.2.2 )
24.3.2.2.2.3 )
)
24.3.2.2 GCH
24.3.2.2.1 All GCH
24.3.2.2.2.1 )
(Section 24.3.2.2.2.2 )
24.3.2.2.2.3 )
1022 / 1392

)
24.3.2.2.2 N/A
24.3.2.2.2.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 (by
a GCH channel).
Trigger Condition
An internal counter tracks the current number of extra and bonus Abis nibbles used
in the cell. An Abis nibble is said used when it is either reserved for establishment
or used by a GCH. Whenever this internal counter is incremented, its new value is
compared with the stored maximum number of extra and bonus nibbles in the cell.
If this value is higher than the stored maximum value, the value becomes the new
maximum. In the particular case of a cell shared over two BTSs, the number is
computed 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
Measured Object
Cell
External Comment
1023 / 1392
24.3.2.2.2.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 or
a bonus Abis nibble is used in the cell. An Abis nibble is said used when it is either
reserved for establishment or used by a GCH. The time is provided in seconds
with one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Abis interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1024 / 1392
24.3.2.2.2.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 and
bonus Abis nibbles available. Free extra and bonus nibbles are extra and bonus
nibbles 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 is
observed . For each free bonus or extra Abis nibble, the counter cumulates over
the reporting period the time during which this nibble is free. An Abis nibble is said
free when it is neither reserved for establishment nor used by a GCH.
Sub Domain 1
Abis interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
BTS
External Comment
1025 / 1392
24.3.2.2.2.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 bonus
nibbles 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 bonus
Abis nibbles among all the values of free extra and bonus Abis nibbles obtained
over the granularity period. An Abis nibble is said free when it is neither reserved
for 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 granted
to the MFS for the concerned BTS.
Sub Domain 1
Abis interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
BTS
External Comment
1026 / 1392

24.3.3.2 GCH
24.3.3.2.1 All GCH
1027 / 1392
24.3.3.2.2 N/A
24.3.3.2.2.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,
a GCH is said busy when it is connected to a given PDCH. For an Evolium BTS, a
GCH 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 is busy in the cell. For a given GCH, the counter starts when the
associated Ater nibble becomes busy and stops on the sending of BSCGP
ABIS-NIBBLES-ALLOCATION message indicating the GCH deallocation. An Ater
nibble is said busy when it is either reserved for establishment or used by a GCH.
The transmission resources connected to carry master PDCHs are included in
this counter.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
This counter shall be aggegrated at GPU level by NPA. It is the equivalent of

P100a (B8), at cell level.
1028 / 1392
24.3.3.2.2.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
GCH is said busy when it is connected to a given PDCH. For an Evolium BTS, a
Trigger Condition
An internal counter tracks the current number of busy GCH in the cell. This internal
counter is incremented when the associated Ater nibble of a GCH becomes busy
or decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATION message
indicating the GCH deallocation. An Ater nibble is said busy when it is either
reserved for establishment or used by a GCH. Whenever this internal counter is
incremented, its new value is compared with the stored maximum number of
busy GCH in the cell. If this value is higher than the stored maximum value, the
value becomes the new maximum. At the begining of each granularity period , the
counter is initialized with the current number of busy GCH.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
This counter shall be aggregated by NPA at cell level. It is the equivalent of P100b
(B8) at cell level.
1029 / 1392
24.3.3.2.2.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, a
Trigger Condition
An internal counter tracks the current number of busy GCH in the cell. This internal
counter is incremented when the associated Ater nibble of a GCH becomes busy
or decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATION message
indicating the GCH deallocation. An Ater nibble is said busy when it is either
reserved for establishment or used by a GCH. Whenever this internal counter is
incremented, its new value is compared with the stored minimum number of busy
GCH in the cell. If this value is lower than the stored minimum value, the value
becomes the new minimum. At the begining of each granularity period , the
counter is initialised with the current number of busy GCH.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
This counter shall be aggregated by NPA at cell level.
1030 / 1392
24.3.3.2.2.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, a
Trigger Condition
An internal counter tracks the current number of busy GCH in the GPU. This
internal counter is incremented when the associated Ater nibble of a GCH becomes
busy or decremented on sending of a BSCGP ABIS-NIBBLES-ALLOCATION
message indicating the GCH deallocation. An Ater nibble is said busy when it
is either reserved for establishment or used by a GCH. Whenever this internal
counter is incremented, its new value is compared with the stored maximum
number of busy GCH in the GPU. If this value is higher than the stored maximum
value, the value becomes the new maximum. At the begining of each granularity
period , the counter is initialized with the current number of busy GCH.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
It is the equivalent of P100b (B8) at GPU level.
1031 / 1392
24.3.3.2.2.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) is
available in the GPU. The counter is integrated over all the GCH resources
configured in the GPU. Notes: 1) The term "available" refers to the operational
state of the GCH resource. A GCH resource is available if it is able to carry
PS traffic. A GCH resource is unavailable if it is not able to carry PS traffic, for
instance further to a PCM alarm or BSC indicates a GCH not-available. 2) A
GCH corresponds here to an Ater nibble.
Trigger Condition
The counter cumulates over the reporting period and over all the GCH resources
defined in the GPU the time during which a GCH resource is available in the
GPU. For a given GCH resource, the counter starts when the resource becomes
available and stops when the resource becomes unavailable.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1032 / 1392
24.3.3.2.2.6 P383a - TIME_ATERMUX_CONG

Long Name
TIME_ATERMUX_CONG
Definition
Atermux congestion duration (in seconds) due to a lack of Ater nibbles on the
Atermux 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 than
N_ATER_TS_MARGIN_GPU), - Stopped: when a GPU leaves the Atermux
congestion state (i.e. when there is at least N_ATER_TS_MARGIN_GPU free
Ater TS on the GPU).
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1033 / 1392
24.3.3.2.2.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, reaches
Ater_Usage_Threshold - stopped: when the percentage of used Ater nibbles, in
the GPU, drops below Ater_Usage_Threshold
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1034 / 1392
24.3.3.2.2.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 among
all the values of GCH in deficit obtained over the granularity period. 1) For
Evolium BTS: value = greatest value of the (Max(0,sum over all TRX in the
cell of Average_Target_Nb_GCH - Current_Nb_GCH)) values encountered
in the granularity period. Average_Target_Nb_GCH shall be 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) by
Nb_GCH(R_AVERAGE_EGPRS). The computing of Average_Target_Nb_GCH
will 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 MS
transfers 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 of
Target_Nb_GCH (Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shall not
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: - if
R_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 the
range [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 defined
in RRM-PRH, - if R_AVERAGE_EGPRS is in the range [54,4;59,2[ kbps, then
Nb_GCH(R_AVERAGE_EGPRS) = Nb_GCH(MCS-8) as defined in RRM-PRH, - if
R_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 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1035 / 1392
24.3.3.2.2.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 GCH
resources (16k channel). Note : GCH resources cover the established and the
reserved GCH.
Trigger Condition
The counter cumulates over the Granularity period and over all TRX of the cell
the time during which the GCH resources are in deficit. Deficit is computed as
follow : 1) For Evolium BTS: Deficit value = Max(0,sum over all TRX in the cell of
Average_Target_Nb_GCH - Current_Nb_GCH). Average_Target_Nb_GCH shall
be 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) by
will only differ from the one of Target_Nb_GCH for the long data MS transfers.
Target_Nb_GCH (Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shall not
R_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 =
0 Within the Granularity period, the deficit of GCH is observed. At each change
of value of the deficit (increase or decrease) the previous value of the deficit is
multiplied its time duration and summed with the cumulated time.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1036 / 1392
24.3.3.2.2.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 GCH
resources (16k channel). Note : GCH resources cover the established and the
reserved GCH.
Trigger Condition
The counter cumulates over the Granularity period and over all TRX of the cell
the time during which the GCH resources are in excess . Excess is computed as
follow : 1) For Evolium BTS: Excess value = Max(0,sum over all TRX in the cell of
Current_Nb_GCH - Average_Target_Nb_GCH). Average_Target_Nb_GCH shall
be 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)" by
will only differ from the one of Target_Nb_GCH for the long data MS transfers.
Target_Nb_GCH ("Nb_GCH(MAX_(E)GPRS_(M)CS_SHORT_DATA) shall not
R_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-EGCH
statistical Multiplexing). In this case , the counter value can be considered as non
significant. Within the Granularity period, the excess of GCH is observed. At
each change of value of the excess (increase or decrease) the previous value of
the 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 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1037 / 1392
24.3.3.2.2.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.
A free Ater nibble is an Ater nibble which is neither reserved for establishment
nor currently used by a GCH.
Trigger Condition
This counter can be computed by the difference between the counter P101 and
the sum over all the cells of P100c.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1038 / 1392
24.3.3.2.2.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 is
neither 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 nibbles
among all the values of free Ater nibbles obtained over the granularity period. At
the beginning of each granularity period, the counter is initialized with the current
number of free Ater nibbles.
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1039 / 1392
24.3.3.3 LapD
24.3.3.3.1 All LapD
24.3.3.3.2 N/A
24.3.3.3.2.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 the
administrative state "locked", and stops whenever the LapD operational state is
"enabled" and the administrative state "unlocked". The time is provided in seconds
with one significant value after the comma (ie ROUND(10x) / 10).
Sub Domain 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
1040 / 1392
24.3.4 Gb interface
24.3.4.2 Bearer Channel

24.3.4.2.1 All Bearer Channel
24.3.4.2.2 N/A
24.3.4.2.2.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" (LM
link integrity procedure failure as described in Q933 annex A), and stops whenever
the Bearer Channel operational state is "enabled" (LM link integrity procedure
recovery). The time is provided in seconds with one significant value after the
comma (ie ROUND(10x) / 10).
Sub Domain 1
Gb interface
Sub Domain 2
Bearer Channel
Sub Domain 3
N/A
Measured Object
Bearer Channel
External Comment
1041 / 1392
24.3.4.3 BVC (Cell)

24.3.4.3.1 All BVC (Cell)
24.3.4.3.2 N/A
24.3.4.3.2.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", and
stops whenever the PTP BVC status is "Operational, started". The time is provided
in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Gb interface
Sub Domain 2
BVC (Cell)
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1042 / 1392
24.3.4.4 PVC
24.3.4.4.1 All PVC
24.3.4.4.2 N/A
24.3.4.4.2.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 stops
whenever the PVC operational state is "enabled". The time is provided in seconds
with one significant value after the comma (ie ROUND(10x) / 10).
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1043 / 1392
24.3.4.4.2.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 Relay
network.
Trigger Condition
The time starts whenever S consecutive frames are received from the Frame
Relay 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 fixed
delay, after which the time is stopped. The time is provided in seconds with one
significant value after the comma (ie ROUND(10x) / 10).
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1044 / 1392
24.3.4.4.2.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
is managed by an hysteresis mechanism with two thresholds. The PVC enters the
congestion-level1 state whenever its occupation queue exceeds PVC-LEVEL1-UP
while the PVC was not congested. The PVC exits the congestion-level1 state
whenever its occupation queue is smaller than PVC-LEVEL1-DOWN.
Trigger Condition
The time starts whenever the PVC enters the congestion-level1 state, and stops
whenever the PVC exits this state. The time is provided in seconds with one
significant value after the comma (ie ROUND(10x) / 10).
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1045 / 1392
24.3.4.5 SGSN_IP_NSVC
24.3.4.5.1 All SGSN_IP_NSVC
24.3.4.5.2 N/A
24.3.4.5.2.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 1
Gb interface
Sub Domain 2
SGSN_IP_NSVC
Sub Domain 3
N/A
Measured Object
SGSN_IP_NSVC
External Comment
1046 / 1392

(Section 24.3.5.9.2.1 )
(Section 24.3.5.9.2.2 )
(Section 24.3.5.9.2.3 )
(Section 24.3.5.9.2.4 )
24.3.5.3.2.1 )
(Section 24.3.5.3.2.2 )
(Section 24.3.5.9.2.5 )
1047 / 1392

24.3.5.6.2.7 )
1048 / 1392

24.3.5.9.2.18 )
(Section 24.3.5.3.2.15 )
(Section 24.3.5.3.2.16 )
(Section 24.3.5.3.2.17 )
(Section 24.3.5.3.2.18 )
24.3.5.8.2.1 )
24.3.5.8.2.2 )
1049 / 1392

24.3.5.8.2.3 )
24.3.5.8.2.4 )
24.3.5.8.2.5 )
24.3.5.8.2.6 )
24.3.5.8.2.7 )
24.3.5.8.2.8 )
24.3.5.8.2.9 )
24.3.5.8.2.10 )
24.3.5.8.2.11 )
24.3.5.2.2.1 )
24.3.5.2.2.2 )
24.3.5.2.2.3 )
24.3.5.2.2.4 )
24.3.5.8.2.12 )
24.3.5.8.2.13 )
24.3.5.2.2.5 )
24.3.5.2.2.6 )
24.3.5.8.2.14 )
24.3.5.2.2.7 )
24.3.5.8.2.15 )
24.3.5.8.2.16 )
24.3.5.8.2.17 )
24.3.5.8.2.18 )
1050 / 1392

24.3.5.8.2.19 )
24.3.5.8.2.20 )
24.3.5.8.2.21 )
24.3.5.8.2.22 )
24.3.5.8.2.23 )
24.3.5.8.2.24 )
24.3.5.8.2.25 )
24.3.5.2.2.8 )
24.3.5.2.2.9 )
24.3.5.2.2.10 )
24.3.5.2.2.11 )
24.3.5.2.2.12 )
24.3.5.2.2.13 )
24.3.5.2.2.14 )
24.3.5.2.2.15 )
24.3.5.2.2.16 )
24.3.5.2.2.17 )
24.3.5.2 DL LLC data flow

24.3.5.2.1 All DL LLC data flow
24.3.5.2.2.1 )
24.3.5.2.2.2 )
24.3.5.2.2.3 )
1051 / 1392

24.3.5.2.2.4 )
24.3.5.2.2.5 )
24.3.5.2.2.6 )
24.3.5.2.2.7 )
24.3.5.2.2.8 )
24.3.5.2.2.9 )
24.3.5.2.2.10 )
24.3.5.2.2.11 )
24.3.5.2.2.12 )
24.3.5.2.2.13 )
24.3.5.2.2.14 )
24.3.5.2.2.15 )
24.3.5.2.2.16 )
24.3.5.2.2.17 )
1052 / 1392
24.3.5.2.2 N/A
24.3.5.2.2.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.

It contains : 1) number of EGPRS DL LLC throughput whose throughput
is in EGPRS LLC throughput class 1. EGPRS LLC throughput class 1
is defined by : EGPRS_LLC_throughput_THR_0<= LLC throughput <
EGPRS_LLC_throughput_THR_1 EGPRS_LLC_throughput_THR_0 = 0 kbit/s
Trigger Condition
During MS context lifetime , the DL LLC PDU size sent in the TBF established in
EGPRS mode and their transfer duration are cumulated. When the MS context is
deleted , the DL LLC throughput (cumulated DL LLC PDU size/cumulated transfer
duration) is estimated and the suitable class of the distribution is incremented by
one. 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 when
a LLC PDU (or a set of DL LLC PDU) have been correctly received by the MS .
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1053 / 1392

Long Name
Definition
Tenth class of the distribution on number of EGPRS DL LLC throughput.

is in EGPRS LLC throughput class 10. EGPRS LLC throughput class
10 is defined by : EGPRS_LLC_throughput_THR_9<= LLC throughput <
EGPRS_LLC_throughput_THR_10
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1054 / 1392

Long Name
Definition
Eleventh class of the distribution on number of EGPRS DL LLC throughput.

is defined by : EGPRS_LLC_throughput_THR_10 <= LLC throughput <
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1055 / 1392

Long Name
Definition
Second class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1056 / 1392

Long Name
Definition
Fifth class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1057 / 1392

Long Name
Definition
Sixth class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1058 / 1392

Long Name
Definition
Eighth class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1059 / 1392
24.3.5.2.2.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.

It contains : 1) number of GPRS DL LLC throughput whose throughput
is in GPRS LLC throughput class 1. GPRS LLC throughput class 1
is defined by : GPRS_LLC_throughput_THR_0<= LLC throughput <
GPRS_LLC_throughput_THR_1 GPRS_LLC_throughput_THR_0 = 0 kbit/s
Trigger Condition
GPRS mode and their transfer duration are cumulated. When the MS context is
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1060 / 1392

Long Name
Definition
Tenth class of the distribution on number of GPRS DL LLC throughput.

GPRS_LLC_throughput_THR_10
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1061 / 1392

Long Name
Definition
Second class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1062 / 1392

Long Name
Definition
Third class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1063 / 1392

Long Name
Definition
Fourth class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1064 / 1392

Long Name
Definition
Fifth class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1065 / 1392

Long Name
Definition
Sixth class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1066 / 1392

Long Name
Definition
Seventh class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1067 / 1392

Long Name
Definition
Eighth class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1068 / 1392

Long Name
Definition
Ninth class of the distribution on number of GPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1069 / 1392
24.3.5.3 DL TBF duration

24.3.5.3.1 All DL TBF duration
24.3.5.3.2.1 )
(Section 24.3.5.3.2.2 )
(Section 24.3.5.3.2.15 )
(Section 24.3.5.3.2.16 )
(Section 24.3.5.3.2.17 )
(Section 24.3.5.3.2.18 )
1070 / 1392
24.3.5.3.2 N/A
24.3.5.3.2.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 in
the cell over the Granularity period. Active as well as delayed release periods are
taken into account. Each time duration starts upon reception from the Mobile
Station of 04.60 PACKET CONTROL ACKNOWLEDGMENT on PACCH/U during
the DL TBF establishment procedure (either in response to a PACKET DOWNLINK
ASSIGNMENT or PACKET TIMESLOT RECONFIGURE, whichever is applicable).
In case of normal DL TBF releases, the counter stops for a given DL TBF upon
reception of the reply to the 04.60 RLC DATA BLOCK (FBI=1, polling) sent by the
MFS for the last RLC block to send, i.e. 04.60 (EGPRS) PACKET DOWNLINK
ACK/NACK from the MS and there is no retransmission required, if the TBF was in
RLC acknowledged mode or 04.60 PACKET CONTROL ACK if the TBF was in
RLC unacknowledged mode. This last RLC data block is the last actual data block
of 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
of abnormal DL TBF releases during active phase (i.e. not delayed phase), the
counter stops for a given DL TBF: - at the time when the RRM layer has received
the acknowledgment of the last DL LLC PDU (in case of RLC acknowledged
mode), or, - at the time when the RRM layer has sent the last DL LLC PDU to
the RLC layer (in case of RLC unacknowledged mode). In case of abnormal DL
TBF releases during delayed phase, the counter stops for a given DL TBF at the
time when the RRM layer has been informed that the DL TBF has entered the
delayed phase. The case the DL TBF is released due to a NC cell reselection is
managed as an abnormal DL TBF release. The time is provided in seconds with
one significant value after the comma (I.e. ROUND(10x)/10). The DL TBFs still
established at the expiration of the granularity period are not taken into account
in the cumulated value. They are taken into account only when the DL TBFs are
released. In case of traffic profile including a lot of "very long" TBF, this may lead
to a temporary under-estimated (then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1071 / 1392
24.3.5.3.2.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 of
PDCHs they need and the corresponding MSs are engaged in downlink-biased
transfers.
Trigger Condition
The counter is incremented by the duration during which all downlink TBFs of a cell
which serve a downlink-biased transfer are granted as many timeslots as needed.
The results are cumulated over the granularity period. When determining the
number of timeslots needed by the mobile station for the DL TBF, the MFS takes
into account: i) The MS multislot class (or the MS high multislot class if allowed in
the cell). The GPRS or EGPRS (possibly high) multislot class is used depending
on the DL TBF establishment mode (in GPRS mode or EGPRS mode). ii) The
bias of the transfer. For instance, for an MS belonging to multislot class 6, for
which the transfer is deemed downlink-biased, the requested number of timeslots
in downlink is 3 and not 2. iii) The value of the "traffic type" (signalling or data) 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 traffic type
from 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 when
the RRM layer has received the acknowledgment of the last DL LLC PDU (in case
of RLC acknowledged mode), or, - at the time when the RRM layer has sent the
last DL LLC PDU to the RLC layer (in case of RLC unacknowledged mode). In
case of abnormal DL TBF releases during delayed phase, the counter stops for a
given DL TBF at the time when the RRM layer has been informed that the DL TBF
has entered the delayed phase. The case the DL TBF is released due to a NC cell
reselection is managed as an abnormal DL TBF release. The time is provided in
seconds with one significant value after the comma (i.e. ROUND(10x) / 10). The
DL TBFs still established at the expiration of the granularity period are not taken
into account in the cumulated value. They are taken into account only when the DL
TBFs are released. In case of traffic profile including a lot of "very long" TBF, this
may lead to a temporary under-estimated (then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
- when the traffic type changes from "signalling" to "data" , the optimality is
re-assessed. - Once the traffic type is set to data, it can not be changed to
signalling, whatever the T-bit value.
1072 / 1392
24.3.5.3.2.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 and
there is a DL TBF serving the MS.
Trigger Condition
The counter is incremented by the duration during which MSs are deemed in a
downlink-biased transfer. Only the time during which there is a DL TBF serving
the MS is taken into account. 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
when the RRM layer has received the acknowledgment of the last DL LLC PDU (in
case of RLC acknowledged mode), or, - at the time when the RRM layer has sent
the last DL LLC PDU to the RLC layer (in case of RLC unacknowledged mode). In
case of abnormal DL TBF releases during delayed phase, the counter stops for a
given DL TBF at the time when the RRM layer has been informed that the DL TBF
has entered the delayed phase. The case the DL TBF is released due to a NC
cell reselection is managed as an abnormal DL TBF release. The time is provided
in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
The DL biased TBFs still established at the expiration of the granularity period are
not taken into account in the cumulated value. They are taken into account only
when the DL TBFs are released. In case of traffic profile including a lot of "very
long" TBF, this may lead to a temporary under-estimated (then over-estimated)
cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1073 / 1392
24.3.5.3.2.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 a
downlink-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 the
timer is stopped. When it changes back to downlink, the timer is restarted. If it
is uplink-biased, then the timer is started for that MS when the bias changes to
downlink. When it changes back to uplink, then the timer is stopped. When the
session ends, the timer for the MS is cumulated to P419. Note that when the MS
context is deemed downlink-biased and T3192 is running, even if there is no
on-going TBF, that duration shall be taken into account in this timer. In case the
MS has no on-going UL TBF and an abnormal DL TBF release is detected during
active phase (i.e. not delayed phase), the counter stops for the given MS: - at the
time when the RRM layer has received the acknowledgment of the last DL LLC
PDU (in case of RLC acknowledged mode), or, - at the time when the RRM layer
has sent the last DL LLC PDU to the RLC layer (in case of RLC unacknowledged
mode). In case the MS has no on-going UL TBF and an abnormal DL TBF release
is detected during delayed phase, the counter stops for the given MS at the time
when the RRM layer has been informed that the DL TBF has entered the delayed
phase. In case the MS has no on-going DL TBF and an abnormal UL TBF release
is detected, the counter stops for the given MS at the time when the RRM layer
has received the last UL LLC PDU. The case the DL TBF is released due to a
NC cell reselection is managed as an abnormal DL TBF release. Similarly, the
case the UL TBF is released due to a NC cell reselection is managed as an
abnormal UL TBF release. The time is provided in seconds with one significant
value after the comma (i.e. ROUND(10x) / 10). The MSs still DL biased at the
expiration of the granularity period are not taken into account in the cumulated
value. They are taken into account only when the biais change to UL. In case of
traffic profile including a lot of "very long" TBF with no bias changes, this may lead
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1074 / 1392
24.3.5.3.2.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) number of DL

TBFs whose duration is in duration band 1 Duration band 1 is defined by :
PD_DL_TBF_DURATION_THR_0<= duration < PD_DL_TBF_DURATION_THR_1
PD_DL_TBF_DURATION_THR_0 = 0 sec
Trigger Condition
DL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLC

unacknowledged mode are taken into account. Only the active phase of the TBF
is taken into account. The duration is measured as for P52a, P52b, P52c, P52d.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1075 / 1392

Long Name
Definition
Tenth cell of the duration on DL TBF duration. It contains : 1) number

of DL TBFs whose duration is in duration band 10 Duration band
10 is defined by : PD_DL_TBF_DURATION_THR_9<= duration <
PD_DL_TBF_DURATION_THR_10 PD_DL_TBF_DURATION_THR_10 = 16384
Trigger Condition

Whenever a TBF duration exceeds PD_DL_TBF_DURATION_THR_10, then it is
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1076 / 1392

Long Name
Definition
Second cell of the duration on DL TBF duration. It contains : 1) number of

DL TBFs whose duration is in duration band 2 Duration band 2 is defined by :
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1077 / 1392

Long Name
Definition
Third cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1078 / 1392

Long Name
Definition
Fourth cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1079 / 1392

Long Name
Definition
Fifth cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1080 / 1392

Long Name
Definition
Sixth cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1081 / 1392

Long Name
Definition
Seventh cell of the duration on DL TBF duration. It contains : 1) number of DL

TBFs whose duration is in duration band 7. Duration band 7 is defined by :
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1082 / 1392

Long Name
Definition
Eighth cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1083 / 1392

Long Name
Definition
Ninth cell of the duration on DL TBF duration. It contains : 1) number of DL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1084 / 1392
24.3.5.3.2.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 and
RLC acknowledged mode Note: An active DL TBF connection is a DL TBF not in
delayed release state.
Trigger Condition
The counter measures the cumulated time duration of all active DL TBFs
established in GPRS mode and in RLC acknowledged mode in the cell over the
granularity period. For a given DL TBF, the counter starts at the establishment
of the DL TBF in GPRS mode and RLC acknowledged mode upon the receipt
from the Mobile Station of 04.60 a PACKET CONTROL ACKNOWLEDGEMENT
message on PACCH/U during the DL TBF establishment procedure. Once the DL
TBF enters the delayed release state, the counter is suspended upon the receipt
from the mobile station of an 04.60 PACKET DOWNLINK ACK/NACK message
acknowledging the correct reception of all the useful 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 normal DL TBF releases, the counter stops
for a given DL TBF upon the receipt of the RLC indication indicating that the TBF
has entered the delayed phase. The DL TBF enters the delayed phase upon the
receipt of the acknowledgment of the last useful RLC data block with (FBI = 0 and
a polling indication). In case of abnormal DL TBF releases, the counter stops for a
given DL TBF at the time when the RRM layer has received the acknowledgment
of the last DL LLC PDU. The case the DL TBF is released due to a NC cell
seconds with one significant value after the comma (i.e. ROUND(10x)/10). The DL
TBFs still established at the expiration of the granularity period are not taken into
account in the cumulated value. They are taken into account only when the DL
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1085 / 1392
24.3.5.3.2.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 and
RLC unacknowledged mode Note: An active DL TBF connection is a DL TBF
not in delayed release state.
Trigger Condition
established in GPRS mode and in RLC unacknowledged mode in the cell over the
of the DL TBF in GPRS mode and RLC unacknowledged mode upon the receipt
TBF enters the delayed release state, the counter is suspended upon reception
from the mobile station of an 04.60 PACKET DOWNLINK ACK/NACK message
acknowledging the reception of the first RLC data block of the last useful DL 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 normal DL TBF
releases, the counter stops for a given TBF upon the receipt of the RLC indication
indicating that the TBF has entered the delayed phase. The DL TBF enters 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 counter stops for a
given DL TBF at the time when the RRM layer has sent the last DL LLC PDU to
the RLC layer. The case the DL TBF is released due to a NC cell reselection is
managed as an abnormal DL TBF release. The time is provided in seconds with
one significant value after the comma (i.e. ROUND(10x)/10). The DL TBFs still
in the cumulated value. They are taken into account only when the DL TBFs are
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1086 / 1392
24.3.5.3.2.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 and
RLC acknowledged mode. Note: An active DL TBF connection is a DL TBF not in
delayed release state.
Trigger Condition
established in EGPRS mode and in RLC acknowledged mode in the cell over the
of the DL TBF in EGPRS mode and RLC acknowledged mode upon the receipt
from the mobile station of an 04.60 EGPRS PACKET DOWNLINK ACK/NACK
message acknowledging the receipt of first DL RLC data block of the last DL LLC
PDU. 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 normal DL
TBF releases, the counter stops for a given DL TBF upon the receipt of the RLC
indication indicating that the TBF has entered the delayed phase. The DL TBF
enters the delayed phase upon the receipt of the acknowledgment of the last
useful RLC data block with (FBI = 0 and a polling indication). In case of abnormal
DL TBF releases, the counter stops for a given DL TBF at the time when the RRM
layer has received the acknowledgment of the last DL LLC PDU. The case the
DL TBF is released due to a NC cell reselection is managed as an abnormal DL
TBF release. The time is provided in seconds with one significant value after the
comma (i.e. ROUND(10x)/10). The DL TBFs still established at the expiration of
the granularity period are not taken into account in the cumulated value. They are
taken into account only when the DL TBFs are released. In case of traffic profile
including a lot of "very long" TBF, this may lead to a temporary under-estimated
(then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1087 / 1392
24.3.5.3.2.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 and
RLC unacknowledged mode. Note: An active DL TBF connection is a DL TBF
not in delayed release state.
Trigger Condition
established in EGPRS mode and in RLC unacknowledged mode in the cell over
the granularity period. For a given DL TBF, the counter starts at the establishment
of the DL TBF in EGPRS mode and RLC unacknowledged mode upon the receipt
from the mobile station of an 04.60 EGPRS PACKET DOWNLINK ACK/NACK
message acknowledging the reception of the first RLC data block of the last useful
DL 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 normal
DL TBF releases, the counter stops for a given TBF upon the receipt of the RLC
indication indicating that the TBF has entered the delayed phase. The DL TBF
enters 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 counter
stops for a given DL TBF at the time when the RRM layer has sent the last DL
LLC PDU to the RLC layer. The case the DL TBF is released due to a NC cell
seconds with one significant value after the comma (i.e. ROUND(10x)/10). The DL
TBFs still established at the expiration of the granularity period are not taken into
account in the cumulated value. They are taken into account only when the DL
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1088 / 1392
24.3.5.4 DL TBF LLC volume

24.3.5.4.1 All DL TBF LLC volume
24.3.5.4.2 N/A
24.3.5.4.2.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 UL TBFs whose LLC volume is in LLC volume band 3. LLC volume
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 unacknowledged
mode are taken into account. The volume is calculated as in P44.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1089 / 1392

Long Name
Definition
Fourth cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1090 / 1392
24.3.5.4.2.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 DL TBFs

whose LLC volume is in LLC volume band 1. LLC volume band 1 is defined by :
PD_DL_TBF_VOLUME_THR_0<= LLC volume < PD_DL_TBF_VOLUME_THR_1
PD_DL_TBF_VOLUME_THR_0 = 0 byte
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1091 / 1392

Long Name
Definition
Tenth cell of the distribution on volume of DL TBF. It contains : 1) number

of DL TBFs whose LLC volume is in LLC volume band 10. LLC volume
band 1 is defined by : PD_DL_TBF_VOLUME_THR_9<= LLC volume <
PD_DL_TBF_VOLUME_THR_10 PD_DL_TBF_VOLUME_THR_10 = 100 000
000 bytes
Trigger Condition
mode are taken into account. The volume is calculated as in P43. Whenever a
TBF volume exceeds PD_DL_TBF_VOLUME_THR_10, then it is not taken into
account.
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1092 / 1392

Long Name
Definition
Second cell of the distribution on volume of DL TBF. It contains : 1) number

PD_DL_TBF_VOLUME_THR_2
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1093 / 1392

Long Name
Definition
Third cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1094 / 1392

Long Name
Definition
Fourth cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1095 / 1392

Long Name
Definition
Fifth cell of the distribution on volume of DL TBF. It contains : 1) number of DL TBFs

PD_DL_TBF_VOLUME_THR_4<= LLC volume < PD_DL_TBF_VOLUME_THR_5
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1096 / 1392

Long Name
Definition
Sixth cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1097 / 1392

Long Name
Definition
Seventh cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1098 / 1392

Long Name
Definition
Eighth cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1099 / 1392

Long Name
Definition
Ninth cell of the distribution on volume of DL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1100 / 1392
24.3.5.5 PDCH
24.3.5.5.1 All PDCH
24.3.5.5.2 N/A
24.3.5.5.2.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 the

MFS, ie: - the maximum number of MSs per PDCH in downlink (set by
MAX_DL_TBF_SPDCH) is reached for all the slave PDCHs of the cell, and - all
MAX_SPDCH_LIMIT PDCHs granted by the BSC are used. OR 2) no resources
(TAI, TFI, PDCH) are available at MFS side to serve the mobile. The time stops as
soon as the above conditions are false. The time is provided in seconds with one
significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1101 / 1392
24.3.5.5.2.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 in

the BSC, i.e.: - the maximum number of MSs per PDCH in uplink (set by
MAX_UL_TBF_SPDCH) is reached for all the slave PDCHs of the cell, and - all
MAX_SPDCH_LIMIT PDCHs granted by the BSC are used. OR 2) no resources
(TAI, TFI, PDCH) are available at MFS side to serve the mobile. The time stops as
soon as the above conditions are false. The time is provided in seconds with one
significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1102 / 1392
24.3.5.5.2.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 slave
PDCH supported carries at least one UL or DL TBF (TBF established in GPRS
mode or EGPRS mode). Note 1: For downlink TBF, active , delayed phases are
taken into account. Note 2: The time is provided in seconds with one significant
digit 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 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1103 / 1392
24.3.5.5.2.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 TBF
established in EGPRS mode.
Trigger Condition
The timer is the sum of all unit times per slave PDCH during which the slave PDCH
supported at least one UL or DL TBF established in EGPRS mode. The time is
provided in seconds with one significant digit after the comma (i.e. ROUND(10x) /
10).
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1104 / 1392
24.3.5.5.2.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 or
EGPRS 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 slave
PDCH supported at least one DL TBF (established in GPRS mode or EGPRS
mode). Note: Only Active, delayed, extended phases of the TBF are taken into
account. The time is provided in seconds with one significant value after the
comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1105 / 1392
24.3.5.5.2.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 or
EGPRS 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 slave
PDCH supported at least one UL TBF (established in GPRS mode or EGPRS
mode). Note: Only Active, delayed, extended phases of the TBF are taken into
account. The time is provided in seconds with one significant value after the
comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1106 / 1392
24.3.5.5.2.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 the
whole granularity period.
Trigger Condition
When the granularity period starts, the counter is reset to 0. The current value
of SPDCHs allocated to the MFS by the BSC is multiplied by the duration until
the next allocated SPDCH update is received from the BSC (I.e. reception of
a (BSCGP) RADIO RESOURCE ALLOCATION INDICATION indicating a new
number of SPDCHs allocated to the MFS). Then the new value of allocated
SPDCH is multiplied by the duration until the next allocated SPDCH update , and
so on. The counter is the sum of all the computed values.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
Replaces P414 (B8 counter).
1107 / 1392
24.3.5.5.2.8 P415bis - MAX_OF_ALLOCATED_SPDCH

Long Name
MAX_OF_ALLOCATED_SPDCH
Definition
This counter gives the maximum value of allocated SPDCH during the whole
granularity period.
Trigger Condition
During the granularity period , at each receipt of the RADIO RESOURCE

ALLOCATION INDICATION
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1108 / 1392
24.3.5.5.2.9 P416bis - MIN_OF_ALLOCATED_SPDCH

Long Name
MIN_OF_ALLOCATED_SPDCH
Definition
This counter gives the minimum value of allocated SPDCH during the whole
granularity period.
Trigger Condition
During the granularity period , at each receipt of the RADIO RESOURCE

ALLOCATION INDICATION the value of allocated SPDCH is stored. At the end
of the granularity period, the minimum value of all the stored values is used
to update the counter.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1109 / 1392
24.3.5.5.2.10 P417 - NB_PREEMPTED_PDCH

Long Name
NB_PREEMPTED_PDCH
Definition
This counter measures the overall number of slave PDCHs which have been
released after having been marked by the soft pre-emption procedure in the cell
over the granularity period.
Trigger Condition
Each time the MFS receives a BSCGP RR ALLOCATION INDICATION message

from the BSC with a SPDCHs Allocation bitmap containing less PDCHs than
the current number of allocated slave PDCHs, the MFS has to mark the slave
PDCHs in excess as soft pre-empted. The counter is incremented by one each
time a slave PDCH is released due to pre-emption (i.e. it is incremented also
when 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 and
therefore the PDCH is given back immediately to the BSC, it shall be considered
in the calculation.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1110 / 1392
24.3.5.5.2.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 a
PDCH 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 by a
salve PDCH. - Decremented when no UL or DL TBF is carried by a slave PDCH.
Whenever this internal counter is incremented, its new value is compared with the
stored maximum number of used PDCHs in the cell. If this value is higher than
the stored maximum value, the value becomes the new maximum. The master
PDCHs are excluded from this counter.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1111 / 1392
24.3.5.5.2.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 PDCH
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 by a
salve PDCH. - Decremented when no UL or DL TBF is carried by a slave PDCH.
Whenever this internal counter is decremented, its new value is compared with the
stored minimum number of used PDCHs in the cell. If this value is lower than the
stored minimum value, the value becomes the new minimum.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1112 / 1392
24.3.5.6 PDCH allocation for DL TBF

24.3.5.6.1 All PDCH allocation for DL TBF
24.3.5.6.2.7 )
1113 / 1392
24.3.5.6.2 N/A
24.3.5.6.2.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 are

satisfied at once by the initial allocation.
Trigger Condition
Whenever the MFS allocates 1 PDCH for a DL TBF in case of an MS requesting 1

(or several) slot DL. When determining the number of timeslots requested by the
mobile station for the DL TBF, the MFS takes into account: i) The MS multislot
class. The GPRS or EGPRS multislot class is used depending on the DL TBF
establishment mode (in GPRS mode or EGPRS mode). ii) The bias of the transfer.
iii) The value of the T-bit indicated in the DL LLC PDU triggering the DL TBF
establishment. If the T-bit is set to signalling, only one PDCH is required.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH allocation for DL TBF
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1114 / 1392
24.3.5.6.2.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 which

are 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 case
of an MS requesting 2 slots DL (or 3 slots DL). When determining the number of
timeslots requested by the mobile station for the DL TBF, the MFS takes into
account: i) The MS multislot class. The GPRS or EGPRS multislot class is used
depending on the DL TBF establishment mode (in GPRS mode or EGPRS mode).
ii) The bias of the transfer. For instance, for an MS belonging to multislot class
10, for which the transfer is deemed uplink-biased, the requested number of
timeslots in downlink is 3 and not 4. iii) The value of the T-bit indicated in the DL
LLC PDU triggering the DL TBF establishment. If the T-bit is set to signalling, only
one PDCH is required.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1115 / 1392
24.3.5.6.2.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 which

are totally satisfied at once by the initial allocation.
Trigger Condition
Whenever the system MFS allocates exactly 4 PDCHs (or 5 PDCHs) for a DL
TBF in case of an MS requesting 4 slots DL (or 5 slots DL). When determining
the number of timeslots requested by the mobile station for the DL TBF, the MFS
takes into account: i) The MS multislot class (or the MS high multislot class if
allowed in the cell). The GPRS or EGPRS (possibly high) multislot class is used
depending on the DL TBF establishment mode (in GPRS mode or EGPRS mode).
ii) The bias of the transfer. For instance, for an MS belonging to multislot class
12, for which the transfer is deemed downlink-biased, the requested number of
timeslots in downlink is 4 and not 1. iii) The value of the T-bit indicated in the DL
LLC PDU triggering the DL TBF establishment. If the T-bit is set to signalling, only
one PDCH is required.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1116 / 1392
24.3.5.6.2.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 Granularity

period.
Trigger Condition
Within the Granularity period, the number of established DL TBF is observed at

each GAUGE-POLLING value; the maximum value is kept for the counter.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1117 / 1392
24.3.5.6.2.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 Granularity

period.
Trigger Condition
Within the Granularity period, the number of established DL TBF is observed at

each GAUGE-POLLING value. At Granularity period expiry, these observations
are averaged, ie summed and divided by the number of observations. The
averaged value (real) is multiplied by 10 and then rounded up or down to the
nearest interger value (ie ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1118 / 1392
24.3.5.6.2.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 the
TBF, 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 to a
DL TBF re-allocation. Note: Active , delayed, extended phases of the TBF are
taken into account (only). The time is provided in seconds with one significant
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1119 / 1392
24.3.5.6.2.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 purposes
uses 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 TBFs
established to carry GMM signalling traffic to the MS. It is stopped at the end of
the active phase of the DL TBF or on receipt of a DL LLC PDU without the T-bit
set. Note : such TBFs only have one PDCH allocated. The time is provided in
seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1120 / 1392
24.3.5.6.2.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. It

contains : 1) number of DL TBFs whose number of PDCH allocated
units 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_1 PD_DL_PDCH_UNIT_ALLOC_THR_0 = 0.
Trigger Condition
This distribution measures the number of PDCH units assigned to the MS in DL

at the release of the DL TBF. A DL PDCH unit represents the percentage of the
PDCHs that is used by the assigned DL TBF. This distribution is computed at the
release of each DL TBF (i.e. at the expiry of timer T3192). The number of PDCH
units is calculated as follows : 1) if EN_QOS_FEATURE is disable ( the PDCHs
allocated 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) The
sum on all PDCHs allocated to the TBF gives the number of PDCH units allocated
in DL. 2) ) if EN_QOS_FEATURE is enable (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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1121 / 1392

Long Name
Definition
Tenth 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 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_10
PD_DL_PDCH_UNIT_ALLOC_THR_10 = 5.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1122 / 1392

Long Name
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
: PD_DL_PDCH_UNIT_ALLOC_THR_1<= allocated PDCH units <
PD_DL_PDCH_UNIT_ALLOC_THR_2
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1123 / 1392

Long Name
Definition
Third cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1124 / 1392

Long Name
Definition
Fourth cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1125 / 1392

Long Name
Definition
Fifth cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1126 / 1392

Long Name
Definition
Sixth cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1127 / 1392

Long Name
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 band 7. PDCH units band 7 is defined
by : PD_DL_PDCH_UNIT_ALLOC_THR_6<= allocated PDCH units <
PD_DL_PDCH_UNIT_ALLOC_THR_7
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1128 / 1392

Long Name
Definition
Eighth cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1129 / 1392

Long Name
Definition
Ninth cell of the distribution on units of PDCH allocated to DL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1130 / 1392
24.3.5.6.2.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 capable

MS in packet idle mode.
Trigger Condition
The counter is incremented by one whenever the MFS receives: - An 04.18

EGPRS PACKET CHANNEL REQUEST message on RACH, or - An 04.60 EGPRS
PACKET CHANNEL REQUEST message on PRACH, or - An 04.60 PACKET
RESOURCE REQUEST message from an EGPRS capable MS. Generally, all
counters related to TBF establishment requests only take into account the first
attempt, i.e. no repetitions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1131 / 1392
24.3.5.6.2.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 packet

idle mode successfully served in EGPRS mode.
Trigger Condition
The counter is incremented whenever the MFS receives a PACKET CONTROL

ACKNOWLEDGEMENT message indicating that the DL TBF has been
successfully established on (P)CCCH in EGPRS mode.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1132 / 1392
24.3.5.6.2.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 packet

idle mode
Trigger Condition
The counter is incremented by one whenever the MFS receives a DL LLC PDU for
an EGPRS capable MS in packet idle mode. Note: If transmission resources are
available, this event will trigger a DL TBF establishment on (P)CCCH (in GPRS
mode or in EGPRS mode). Generally, all counters related to TBF establishment
Note: This counter only applies in an EGPRS cell. In case of GPRS-only cell,
this counter is not incremented.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1133 / 1392
24.3.5.7 PDCH allocation for UL TBF

24.3.5.7.1 All PDCH allocation for UL TBF
24.3.5.7.2 N/A
24.3.5.7.2.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 satisfied
at once by the initial allocation..
Trigger Condition
Whenever the MFS allocates 1 PDCH for an UL TBF in case of an MS requesting

1 (or several) slot UL. When determining the number of timeslots requested
by the mobile station for the UL TBF, the MFS takes into account: i) The MS
multislot class. The GPRS or EGPRS multislot class is used depending on the
UL TBF establishment mode (in GPRS mode or EGPRS mode). ii) The bias of
the transfer. For instance, for an MS belonging to multislot class 6, for which
the transfer is deemed downlink-biased, the requested number of timeslots in
uplink is 1 and not 2.
Sub Domain 1
Radio interface
Sub Domain 2
PDCH allocation for UL TBF
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1134 / 1392
24.3.5.7.2.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 are

totally satisfied at once by the initial allocation..
Trigger Condition
Whenever the MFS allocates exactly 2 PDCHs (or 3 PDCHs) for an UL TBF in
case of an MS requesting 2 slots UL (or 3 slots UL). When determining the number
of timeslots requested by the mobile station for the UL TBF, the MFS takes into
depending on the UL TBF establishment mode (in GPRS mode or EGPRS mode).
ii) The bias of the transfer. For instance, for an MS belonging to multislot class 6,
for which the transfer is deemed uplink-biased, the requested number of timeslots
in uplink is 2 and not 1.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1135 / 1392
24.3.5.7.2.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 are

totally satisfied at once by the initial allocation.
Trigger Condition
Whenever the MFS allocates exactly 4 PDCHs (or 5 PDCHs) for an UL TBF in
case of an MS requesting 4 slots UL (or 5 slots UL). When determining the number
of timeslots requested by the mobile station for the UL TBF, the MFS takes into
depending on the UL TBF establishment mode (in GPRS mode or EGPRS mode).
ii) The bias of the transfer. For instance, for an MS belonging to multislot class 12,
for which the transfer is deemed uplink-biased, the requested number of timeslots
in uplink is 4 and not 1.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1136 / 1392
24.3.5.7.2.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 idle

mode successfully served in EGPRS mode.
Trigger Condition
The counter is incremented in one of the following conditions: - whenever the

TLLI is received during a one phase access EGPRS UL TBF establishment, or whenever the TBF start indication is received during a two-phase access EGPRS
UL TBF establishment.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1137 / 1392
24.3.5.7.2.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 Granularity

period.
Trigger Condition
Within the Granularity period, the number of established UL TBF is observed at

each GAUGE-POLLING value; the maximum value is kept for the counter.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1138 / 1392
24.3.5.7.2.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 at

each GAUGE-POLLING value. At Granularity period expiry, these observations
are averaged, ie summed and divided by the number of observations. The
averaged value (real) is multiplied by 10 and then rounded up or down to the
nearest interger value (ie ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1139 / 1392
24.3.5.7.2.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 the
TBF, 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 to a
UL TBF re-allocation. Note: Active , delayed, extended phases of the TBF are
taken into account (only). The time is provided in seconds with one significant
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1140 / 1392
24.3.5.7.2.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. It

contains : 1) number of UL TBFs whose number of PDCH allocated
: PD_UL_PDCH_UNIT_ALLOC_THR_0<= allocated PDCH units <
PD_UL_PDCH_UNIT_ALLOC_THR_1 PD_UL_PDCH_UNIT_ALLOC_THR_0 = 0.
Trigger Condition
This distribution measures the number of PDCH units assigned to the MS in UL

at the release of the UL TBF. An UL PDCH unit represents the percentage of
the PDCHs that is used by the assigned UL TBF. This distribution is computed
at the release of each UL TBF (i.e. indication of reception of acknowledgement
of final PUAN). The number of PDCH units is calculated as follows : 1) if
EN_QOS_FEATURE is disable ( the PDCHs allocated 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 UL TBF on this PDCH) The sum on all PDCHs allocated to the
TBF gives the number of PDCH units allocated in UL. 2) ) if EN_QOS_FEATURE
is enable (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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1141 / 1392

Long Name
Definition
Tenth 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 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_10
PD_UL_PDCH_UNIT_ALLOC_THR_10 = 5.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1142 / 1392

Long Name
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
: PD_UL_PDCH_UNIT_ALLOC_THR_1<= allocated PDCH units <
PD_UL_PDCH_UNIT_ALLOC_THR_2
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1143 / 1392

Long Name
Definition
Third cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1144 / 1392

Long Name
Definition
Fourth cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1145 / 1392

Long Name
Definition
Fifth cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1146 / 1392

Long Name
Definition
Sixth cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1147 / 1392

Long Name
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 band 7. PDCH units band 7 is defined
by : PD_UL_PDCH_UNIT_ALLOC_THR_6<= allocated PDCH units <
PD_UL_PDCH_UNIT_ALLOC_THR_7
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1148 / 1392

Long Name
Definition
Eighth cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1149 / 1392

Long Name
Definition
Ninth cell of the distribution on units of PDCH allocated to UL TBFs. It contains : 1)

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1150 / 1392
24.3.5.8 UL LLC data flow

24.3.5.8.1 All UL LLC data flow
24.3.5.8.2.1 )
24.3.5.8.2.2 )
24.3.5.8.2.3 )
24.3.5.8.2.4 )
24.3.5.8.2.5 )
24.3.5.8.2.6 )
24.3.5.8.2.7 )
24.3.5.8.2.8 )
24.3.5.8.2.9 )
24.3.5.8.2.10 )
24.3.5.8.2.11 )
24.3.5.8.2.12 )
24.3.5.8.2.13 )
24.3.5.8.2.14 )
24.3.5.8.2.15 )
24.3.5.8.2.16 )
24.3.5.8.2.17 )
24.3.5.8.2.18 )
24.3.5.8.2.19 )
24.3.5.8.2.20 )
24.3.5.8.2.21 )
24.3.5.8.2.22 )
1151 / 1392

24.3.5.8.2.23 )
24.3.5.8.2.24 )
24.3.5.8.2.25 )
24.3.5.8.2 N/A
24.3.5.8.2.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.

It contains : 1) number of EGPRS UL LLC throughput whose throughput
EGPRS_LLC_throughput_THR_1 EGPRS_LLC_throughput_THR_0 = 0 kbit/s
Trigger Condition
During MS context lifetime , the size of the UL LLC PDU received in the TBF
established in EGPRS mode and their transfert duration are cumulated. When
the MS context is deleted , the UL LLC throughput (cumulated UL LLC PDU
size/cumulated transfer time) is estimated and the suitable class of the distribution
is incremented by one. Note : -Only UL LLC PDU whose TBF traffic type is data
are taken into account. - The size and transfer duration of a UL LLC PDU is
estimated by RRM when a UL LLC PDU have been correctly received from the MS.
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1152 / 1392

Long Name
Definition
Tenth class of the distribution on number of EGPRS UL LLC throughput.

is in EGPRS LLC throughput class 10. EGPRS LLC throughput class
10 is defined by : EGPRS_LLC_throughput_THR_9<= LLC throughput <
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1153 / 1392

Long Name
Definition
Eleventh class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1154 / 1392

Long Name
Definition
Second class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1155 / 1392

Long Name
Definition
Third class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1156 / 1392

Long Name
Definition
Fourth class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1157 / 1392

Long Name
Definition
Fifth class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1158 / 1392

Long Name
Definition
Sixth class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1159 / 1392

Long Name
Definition
Seventh class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1160 / 1392

Long Name
Definition
Eighth class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1161 / 1392

Long Name
Definition
Ninth class of the distribution on number of EGPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1162 / 1392

Long Name
Definition
Third class of the distribution on number of EGPRS DL LLC throughput.

is in EGPRS LLC throughput class3. EGPRS LLC throughput class 3
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1163 / 1392

Long Name
Definition
Fourth class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1164 / 1392

Long Name
Definition
Seventh class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1165 / 1392

Long Name
Definition
Ninth class of the distribution on number of EGPRS DL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1166 / 1392
24.3.5.8.2.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.

It contains : 1) number of GPRS UL LLC throughput whose throughput
GPRS_LLC_throughput_THR_1 GPRS_LLC_throughput_THR_0 = 0 kbit/s
Trigger Condition
established in GPRS mode and their transfert duration are cumulated. When
are taken into account. The size and transfer duration of a UL LLC PDU is
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1167 / 1392

Long Name
Definition
Tenth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1168 / 1392

Long Name
Definition
Second class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
is incremented by one. Note : -Only UL LLC PDU whose TBF traffic type is
data are taken into account. - The size and transfer duration of a UL LLC PDU
is provided by RLC to RRM when a UL LLC PDU have been correctly received
from the MS.
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1169 / 1392

Long Name
Definition
Third class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1170 / 1392

Long Name
Definition
Fourth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1171 / 1392

Long Name
Definition
Fifth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1172 / 1392

Long Name
Definition
Sixth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1173 / 1392

Long Name
Definition
Seventh class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1174 / 1392

Long Name
Definition
Eighth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1175 / 1392

Long Name
Definition
Ninth class of the distribution on number of GPRS UL LLC throughput.

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1176 / 1392
24.3.5.9 UL TBF duration

24.3.5.9.1 All UL TBF duration
(Section 24.3.5.9.2.1 )
(Section 24.3.5.9.2.2 )
(Section 24.3.5.9.2.3 )
(Section 24.3.5.9.2.4 )
(Section 24.3.5.9.2.5 )
24.3.5.9.2.18 )
1177 / 1392
24.3.5.9.2 N/A
24.3.5.9.2.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 and
RLC acknowledged mode. Note: An active UL TBF connection is an UL TBF
not in extended phase.
Trigger Condition
The counter measures the cumulated time duration of all UL TBFs established in
GPRS 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/Nack
message is delayed and the time during which the UL is in extended phase are 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 LLC PDU. Note 3 :
The case the UL TBF is released due to a NC cell reselection is managed as an
value after the comma (i.e. ROUND(10x) / 10). The UL TBFs still established at
the expiration of the granularity period are not taken into account in the cumulated
value. They are taken into account only when the UL TBFs are released. In case
of traffic profile including a lot of "very long" TBF, this may lead to a temporary
under-estimated (then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1178 / 1392
24.3.5.9.2.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 and
RLC unacknowledged mode. Note: An active UL TBF connection is an UL TBF
Trigger Condition
The counter measures the cumulated time duration of all UL TBFs established
in GPRS mode and RLC unacknowledged mode in the cell over the granularity
period. Note1 : The time during which the emission of the final Packet Uplink
Ack/Nack message is delayed and the time during which the UL is in extended
phase 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 LLC
PDU. Note 3 :The case the UL TBF is released due to a NC cell reselection is
managed as an abnormal UL TBF release. The time is provided in seconds with
one significant value after the comma (i.e. ROUND(10x) / 10). The UL TBFs still
in the cumulated value. They are taken into account only when the UL TBFs are
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1179 / 1392
24.3.5.9.2.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 and
RLC acknowledged mode. Note: An active UL TBF connection is an UL TBF
Trigger Condition
The counter measures the cumulated time duration of all UL TBFs established in
EGPRS 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/Nack
message and the time during which the UL is in extended phase delayed 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 LLC PDU. Note 3 :
value after the comma (i.e. ROUND(10x) / 10). The UL TBFs still established at
the expiration of the granularity period are not taken into account in the cumulated
value. They are taken into account only when the UL TBFs are released. In case
of traffic profile including a lot of "very long" TBF, this may lead to a temporary
under-estimated (then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1180 / 1392
24.3.5.9.2.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 and
RLC unacknowledged mode. Note: An active UL TBF connection is an UL TBF
Trigger Condition
The counter measures the cumulated time duration of all UL TBFs established
in EGPRS mode and RLC unacknowledged mode in the cell over the granularity
period. Note1 : The time during which the emission of the final Packet Uplink
Ack/Nack message and the time during which the UL is in extended phase
delayed is not taken into account. Note 2 :In case of abnormal UL TBF releases,
one significant value after the comma (i.e. ROUND(10x) / 10). The UL TBFs still
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1181 / 1392
24.3.5.9.2.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 number
of PDCHs they need and the corresponding MSs are engaged in uplink-biased
transfers.
Trigger Condition
The counter is incremented by the duration during which all uplink TBFs of a cell
which serve an uplink-biased transfer are granted as many timeslots as needed.
The results are cumulated over the granularity period. When determining the
number of timeslots needed by the mobile station for the UL TBF, the MFS takes
into account: i) The MS multislot class. The GPRS or EGPRS multislot class is
used depending on the UL TBF establishment mode (in GPRS mode or EGPRS
mode). ii) The bias of the transfer. For instance, for an MS belonging to multislot
class 6, for which the transfer is deemed uplink-biased, the requested number of
timeslots in uplink is 2 and not 1. iii) The value of the "traffic type" (signalling
or data) 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 traffic type from signalling to data. In case of abnormal UL TBF releases, the
counter stops at the time when the RRM layer has received the last UL LLC PDU.
value after the comma (i.e. ROUND(10x) / 10). The optimal UL biaised TBFs still
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
- when the traffic type changes from "signalling" to "data", the optimality is
re-assessed. - Once the traffic type is set to data, it can not be changed to
signalling, whatever the T-bit value.
1182 / 1392
24.3.5.9.2.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 and
there is an UL TBF serving the MS.
Trigger Condition
The counter is incremented by the duration during which MSs are deemed in an
uplink-biased transfer. Only the time during which there is an UL TBF serving the
MS is taken into account. In case of abnormal UL TBF releases, the counter stops
at the time when the RRM layer has received the last UL LLC PDU. The case the
UL TBF is released due to a NC cell reselection is managed as an abnormal UL
TBF release. The time is provided in seconds with one significant value after the
comma (i.e. ROUND(10x) / 10). The UL TBFs still established at the expiration of
the granularity period are not taken into account in the cumulated value. They are
taken into account only when the UL TBFs are released. In case of traffic profile
including a lot of "very long" TBF, this may lead to a temporary under-estimated
(then over-estimated) cumulated value.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1183 / 1392
24.3.5.9.2.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 in an
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, then
the timer is stopped. When it changes back to uplink, the timer is restarted. If it is
downlink-biased, then the timer is started for that MS when the bias changes to
uplink. When it changes back to downlink, then the timer is stopped. When the
session ends, the timer for the MS is cumulated to P420. Note that when the MS
context is deemed uplink-biased and T3192 is running, even if there is no on-going
TBF, that duration shall be taken into account in this timer. In case the MS has
no on-going UL TBF and an abnormal DL TBF release is detected during active
phase (i.e. not delayed phase), the counter stops for the given MS: - at the time
when the RRM layer has received the acknowledgment of the last DL LLC PDU
(in case of RLC acknowledged mode), or, - at the time when the RRM layer has
sent the last DL LLC PDU to the RLC layer (in case of RLC unacknowledged
mode). In case the MS has no on-going UL TBF and an abnormal DL TBF release
is detected during delayed phase, the counter stops for the given MS at the time
when the RRM layer has been informed that the DL TBF has entered the delayed
phase. In case the MS has no on-going DL TBF and an abnormal UL TBF release
is detected, the counter stops for the given MS at the time when the RRM layer
has received the last UL LLC PDU. The case the DL TBF is released due to a
NC cell reselection is managed as an abnormal DL TBF release. Similarly, the
case the UL TBF is released due to a NC cell reselection is managed as an
value after the comma (i.e. ROUND(10x) / 10). The MSs still UL biaised at the
expiration of the granularity period are not taken into account in the cumulated
value. They are taken into account only when the biais change to DL. In case of
traffic profile including a lot of "very long" TBF with no bias changes, this may lead
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1184 / 1392
24.3.5.9.2.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) number of UL

PD_UL_TBF_DURATION_THR_0<= duration < PD_UL_TBF_DURATION_THR_1
PD_UL_TBF_DURATION_THR_0 = 0 sec.
Trigger Condition
UL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLC

is taken into account. Duration is measured as for P129a, P129b, P129c, P129d.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1185 / 1392

Long Name
Definition
Tenth cell of the distribution on UL TBF duration. It contains : 1)

number of UL TBFs whose duration is in duration band 10 Duration
band 10 is defined by : PD_UL_TBF_DURATION_THR_9<= duration <
PD_UL_TBF_DURATION_THR_10 PD_UL_TBF_DURATION_THR_10 = 16384
Trigger Condition

Whenever a TBF duration exceeds PD_UL_TBF_DURATION_THR_10, then it is
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1186 / 1392

Long Name
Definition
Second cell of the distribution on UL TBF duration. It contains : 1) number of

UL TBFs whose duration is in duration band 2 Duration band 2 is defined by :
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1187 / 1392

Long Name
Definition
Third cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1188 / 1392

Long Name
Definition
Fourth cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1189 / 1392

Long Name
Definition
Fifth cell of the distribution on UL TBF duration. It contains : 1) number of UL

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1190 / 1392

Long Name
Definition
Sixth cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1191 / 1392

Long Name
Definition
Seventh cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1192 / 1392

Long Name
Definition
Eighth cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1193 / 1392

Long Name
Definition
Nineth cell of the distribution on UL TBF duration. It contains : 1) number of

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1194 / 1392
24.3.5.9.2.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 in
active 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 (the
first UL RLC data block has been received). The counter stops : For a given UL
TBF, at the release of the UL TBF in (E)GPRS mode. Note : This counter applies
to both GPRS and EGPRS TBFs and to both acknowledge or unacknowledge
mode. Note1 : The time during which the emission of the final Packet Uplink
Ack/Nack message is delayed and the time during which the UL is in extended
phase are taken into account. Note 2 :In case of abnormal UL TBF releases,
one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF duration
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1195 / 1392
24.3.5.10 UL TBF LLC volume

24.3.5.10.1 All UL TBF LLC volume
24.3.5.10.2 N/A
Long Name
Definition
First cell of the distribution on volume of UL TBF. It contains : 1) number of UL TBFs

PD_UL_TBF_VOLUME_THR_0<= LLC volume < PD_UL_TBF_VOLUME_THR_1
PD_UL_TBF_VOLUME_THR_0 = 0 byte
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1196 / 1392

Long Name
Definition
Tenth cell of the distribution on volume of UL TBF. It contains : 1) number

PD_UL_TBF_VOLUME_THR_10 PD_UL_TBF_VOLUME_THR_10 = 100 000
000 bytes
Trigger Condition
mode are taken into account. The volume is calculated as in P44. Whenever a
TBF volume exceeds PD_UL_TBF_VOLUME_THR_10, then it is not taken into
account.
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1197 / 1392

Long Name
Definition
Second cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1198 / 1392

Long Name
Definition
Fifth cell of the distribution on volume of UL TBF. It contains : 1) number of UL TBFs

PD_UL_TBF_VOLUME_THR_4<= LLC volume < PD_UL_TBF_VOLUME_THR_5
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1199 / 1392

Long Name
Definition
Sixth cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1200 / 1392

Long Name
Definition
Seventh cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1201 / 1392

Long Name
Definition
Eighth cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1202 / 1392

Long Name
Definition
Ninth cell of the distribution on volume of UL TBF. It contains : 1) number

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL TBF LLC volume
Sub Domain 3
N/A
Measured Object
DistCell
External Comment
1203 / 1392
24.4 Traffic load

24.4.1 All Traffic load
)
)
)
)
)
24.4.4.5.2.10 )
24.4.4.5.2.11 )
24.4.4.5.2.12 )
24.4.4.5.2.13 )
)
)
)
)
24.4.4.15.2.5 )
24.4.4.15.2.6 )
24.4.4.15.2.7 )
1204 / 1392

24.4.4.15.2.8 )
24.4.4.15.2.9 )
24.4.4.15.2.10 )
24.4.4.15.2.11 )
24.4.4.15.2.12 )
24.4.4.15.2.13 )
1205 / 1392

24.4.4.8.2.5 )
1206 / 1392

)
)
)
)
)
24.4.4.15.2.20 )
)
24.4.4.15.2.22 )
24.4.4.15.2.23 )
)
)
24.4.4.15.2.26 )
)
24.4.4.15.2.28 )
1207 / 1392


24.4.2.2 GCH
24.4.2.2.1 All GCH
24.4.2.2.2 N/A
24.4.2.2.2.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 correctly
decoded in the MFS (due a bad CRC).
Sub Domain 1
Ater interface
Sub Domain 2
GCH
Sub Domain 3
N/A
Measured Object
External Comment
1208 / 1392
24.4.2.3 LapD
24.4.2.3.1 All LapD
24.4.2.3.2 N/A
24.4.2.3.2.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 incremented
by the number of bytes of the message. The result is expressed in kilo bytes.
Sub Domain 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
1209 / 1392
24.4.2.3.2.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 is
incremented by the number of bytes of the message. The result is expressed
in kilo bytes.
Sub Domain 1
Ater interface
Sub Domain 2
LapD
Sub Domain 3
N/A
Measured Object
LapD
External Comment
1210 / 1392
24.4.3 Gb interface
24.4.3.2 BVC (Cell)

24.4.3.2.1 All BVC (Cell)
24.4.3.2.2 N/A
24.4.3.2.2.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 to
the cell, the counter is incremented by the number of bytes of the LLC PDU(s).
Sub Domain 1
Gb interface
Sub Domain 2
BVC (Cell)
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1211 / 1392
24.4.3.2.2.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 the

MAC/RLC sublayer to transmit to the SGSN, the counter is incremented by the
number of bytes of the LLC PDU(s).
Sub Domain 1
Gb interface
Sub Domain 2
BVC (Cell)
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1212 / 1392
24.4.3.3 PVC
24.4.3.3.1 All PVC
24.4.3.3.2 N/A
24.4.3.3.2.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 the
number of bytes of the message. The result is expressed in kilo bytes.
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1213 / 1392
24.4.3.3.2.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 of
bytes of the message. The result is expressed in kilo bytes.
Sub Domain 1
Gb interface
Sub Domain 2
PVC
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1214 / 1392
24.4.3.4 SGSN_IP_NSVC
24.4.3.4.1 All SGSN_IP_NSVC
24.4.3.4.2 N/A
24.4.3.4.2.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 the
number of bytes of the message. The result is expressed in kilo bytes.
Sub Domain 1
Gb interface
Sub Domain 2
SGSN_IP_NSVC
Sub Domain 3
N/A
Measured Object
SGSN_IP_NSVC
External Comment
1215 / 1392
24.4.3.4.2.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 of
bytes of the message. The result is expressed in kilo bytes.
Sub Domain 1
Gb interface
Sub Domain 2
SGSN_IP_NSVC
Sub Domain 3
N/A
Measured Object
SGSN_IP_NSVC
External Comment
1216 / 1392

)
)
)
)
)
24.4.4.5.2.10 )
24.4.4.5.2.11 )
24.4.4.5.2.12 )
24.4.4.5.2.13 )
)
)
)
)
24.4.4.15.2.5 )
24.4.4.15.2.6 )
24.4.4.15.2.7 )
24.4.4.15.2.8 )
1217 / 1392

24.4.4.15.2.9 )
24.4.4.15.2.10 )
24.4.4.15.2.11 )
24.4.4.15.2.12 )
24.4.4.15.2.13 )
1218 / 1392

24.4.4.8.2.5 )
)
)
)
1219 / 1392

)
)
24.4.4.15.2.20 )
)
24.4.4.15.2.22 )
24.4.4.15.2.23 )
)
)
24.4.4.15.2.26 )
)
24.4.4.15.2.28 )
1220 / 1392

24.4.4.2 AGCH
24.4.4.2.1 All AGCH
24.4.4.2.2 N/A
24.4.4.2.2.1 P49 - NB_IMM_ASS_AGCH
Long Name
NB_IMM_ASS_AGCH
Definition
Number of (BSCGP) IMMEDIATE ASSIGNMENT sent to the MS (through the BSC

which manages the AGCH resource) - for an UL TBF establisment, - for a DL TBF
establishment when the MS is in non-DRX mode, - for the allocation of an UL
block. 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 1
Radio interface
Sub Domain 2
AGCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1221 / 1392
24.4.4.3 DL LLC data flow

24.4.4.3.1 All DL LLC data flow
24.4.4.3.2 N/A
24.4.4.3.2.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 is
incremented by the number of bytes of the LLC PDU. 2) Whenever the MFS
receives a DL LLC PDU and the buffer in reception on the Gb interface is full, the
counter is incremented by the number of bytes of the LLC PDU to discard.
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1222 / 1392
24.4.4.3.2.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 the
RLC 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 correctly
received by the MS on a DL TBF established in GPRS mode and RLC
acknowledged mode, the counter is incremented by the number of bytes of the
corresponding DL LLC PDU.
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1223 / 1392
24.4.4.3.2.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 TBFs
established in GPRS mode and RLC unacknowledged mode.
Trigger Condition
transmitted to the MS on a DL TBF established in GPRS mode and RLC
unacknowledged mode, the counter is incremented by the number of bytes of the
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1224 / 1392
24.4.4.3.2.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 RLC
layer on DL TBFs established in EGPRS mode and RLC acknowledged mode.
Trigger Condition
received by the MS on a DL TBF established in EGPRS mode and RLC
acknowledged mode, the counter is incremented by the number of bytes of the
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1225 / 1392
24.4.4.3.2.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 TBFs
established in EGPRS mode and RLC unacknowledged mode.
Trigger Condition
Whenever the RRM layer is informed that a DL LLC PDU has been correctly
transmitted to the MS on a DL TBF established in GPRS mode and RLC
unacknowledged mode, the counter is incremented by the number of bytes of the
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1226 / 1392
24.4.4.3.2.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 be
discarded by the RRM layer (e.g. when a transmission problem is encountered on
the radio interface) without having been sent on the radio interface.
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1227 / 1392
24.4.4.3.2.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 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1228 / 1392
24.4.4.3.2.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 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1229 / 1392
24.4.4.3.2.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 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1230 / 1392
24.4.4.3.2.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 this
mobile. Queued PDUs or incoming PDUs received until suspend ack reception
from SGSN are deleted. The counter is expressed in "bytes".
Sub Domain 1
Radio interface
Sub Domain 2
DL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1231 / 1392
24.4.4.4 DL PACCH
24.4.4.4.1 All DL PACCH
24.4.4.4.2 N/A
24.4.4.4.2.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 transfer

mode and used to carry NC2 signalling messages.
Trigger Condition
The counter is incremented whenever the MFS sends a DL RLC control block on
PACCH/D due to the NC2 mode of operation for MS in packet transfer mode.
Therefore, this counter shall count the following downlink messages: - Packet
Measurement Order - Packet Cell Change Order.
Sub Domain 1
Radio interface
Sub Domain 2
DL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1232 / 1392
24.4.4.4.2.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 PSI
Status feature 2) To send a PACKET SERVING CELL DATA message for Packet
SI Status feature.
Sub Domain 1
Radio interface
Sub Domain 2
DL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1233 / 1392
24.4.4.4.2.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 CELL

DATA message for NACC feature.
Sub Domain 1
Radio interface
Sub Domain 2
DL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1234 / 1392
24.4.4.4.2.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). The
retransmitted blocks are counted.
Trigger Condition
Whenever the MFS sends a DL RLC Block (different from a dummy block) on
PACCH (RLC/MAC control messages). Note : PSCD/PNCD blocks are not taken
into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1235 / 1392
24.4.4.5 DL RLC data flow

24.4.4.5.1 All DL RLC data flow
)
)
)
)
)
24.4.4.5.2.10 )
24.4.4.5.2.11 )
24.4.4.5.2.12 )
24.4.4.5.2.13 )
)
)
)
)
1236 / 1392

)
24.4.4.5.2 N/A
24.4.4.5.2.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 containing

LLC Dummy UI Commands only) on PDTCH encoded in CS-1 retransmitted due
to unacknowledgement of the MS.
Trigger Condition
Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emission
window) on PDTCH encoded in CS-1 is retransmitted to the MS. The
retransmissions of DL RLC DATA blocks in PENDING status within the emission
window are not counted (these blocks may be re-transmitted at the end of a TBF
to speed up the release). In unacknowledged mode, P20a is equal to 0 (no
retransmission). Note that RLC blocks containing LLC Dummy UI Commands
only and that can be inserted by RLC to delay the release of the DL TBF are
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1237 / 1392
24.4.4.5.2.2 P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2

Long Name
Definition

Trigger Condition
retransmissions of DL RLC DATA blocks in PENDING status within the emission
to speed up the release). In unacknowledged mode, the counter is equal to 0 (no
retransmission). Note that RLC blocks containing LLC Dummy UI Commands
only and that can be inserted by RLC to delay the release of the DL TBF are
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1238 / 1392
24.4.4.5.2.3 P20c - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3

Long Name
Definition

Trigger Condition
retransmissions of DL RLC DATA blocks in PENDING status within the transmit
to speed up the release). In unacknowledged mode, P20c is equal to 0 (no
retransmission). Note 1: This counter does not count the blocks re-transmitted
at the end of a TBF to speed up the release or when the RLC transmit window
is stalled. Note 2: This counter does not count the RLC blocks containing LLC
Dummy UI Commands that can be inserted by RLC to delay the release of the
DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1239 / 1392
24.4.4.5.2.4 P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4

Long Name
Definition

Trigger Condition
retransmissions of DL RLC DATA blocks in PENDING status within the transmit
to speed up the release). In unacknowledged mode, P20d is equal to 0 (no
retransmission). Note 1: This counter does not count the blocks re-transmitted
at the end of a TBF to speed up the release or when the RLC transmit window
is stalled. Note 2: This counter does not count the RLC blocks containing LLC
Dummy UI Commands that can be inserted by RLC to delay the release of the
DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1240 / 1392
24.4.4.5.2.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 blocks

containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-1
retransmitted due to unacknowledgement of the MS.
Trigger Condition
window) on PDTCH encoded in MCS-1 is retransmitted to the MS, the counter is
incremented . The retransmissions of DL RLC DATA blocks in PENDING status
within the transmit window are not counted. In unacknowledged mode, the counter
is equal to 0 (no retransmission). Note 1: This counter does not count the RLC
blocks re-transmitted at the end of a TBF to speed up the release or when the RLC
transmit window is stalled. Note 2: This counter does not count the RLC blocks
containing LLC Dummy UI Commands that can be inserted by RLC to delay the
release of the DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1241 / 1392
24.4.4.5.2.6 P20g - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1242 / 1392
24.4.4.5.2.7 P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1243 / 1392
24.4.4.5.2.8 P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1244 / 1392
24.4.4.5.2.9 P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1245 / 1392
24.4.4.5.2.10 P20k - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1246 / 1392
24.4.4.5.2.11 P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1247 / 1392
24.4.4.5.2.12 P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1248 / 1392
24.4.4.5.2.13 P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9

Long Name
Definition

Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1249 / 1392
24.4.4.5.2.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 radio

blocks are counted.
Trigger Condition
The counter is incremented whenever the MFS sends a DL RLC/MAC data block
on PDTCH. Note that the RLC/MAC blocks containing LLC Dummy UI Commands
are also counted.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1250 / 1392
24.4.4.5.2.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 that
have been sent on the radio interface. Note: This counter applies to both GPRS
and EGPRS TBFs.
Trigger Condition
Each time one RLC data block is sent, if this RLC data block contains only Dummy
LLC UI Command PDUs, this counter is incremented. Note that both initial
transmissions and retransmissions are counted.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1251 / 1392
24.4.4.5.2.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 PDTCH

encoded in CS-1. The retransmitted blocks and RLC blocks containing LLC
Dummy UI Commands only are not counted.
Trigger Condition
Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-1 is

acknowledged by the MS for the first time (previously in PENDING or UNACK
state within the emission window). Note that RLC blocks containing LLC Dummy
UI Commands only and that have been inserted by RLC to delay the release of
the DL TBF are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1252 / 1392
24.4.4.5.2.17 P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1253 / 1392
24.4.4.5.2.18 P55c - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1254 / 1392
24.4.4.5.2.19 P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1255 / 1392
24.4.4.5.2.20 P55e - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1

Long Name
NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1
Definition

encoded in MCS-1.
Trigger Condition
Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-1 is

acknowledged by the MS for the first time. If a DL RLC data block needs to be
re-transmitted using a more robust MCS, the counter is incremented on receipt of
the first acknowledgement of the corresponding re-transmitted block(s). In this
case, only the counter corresponding to the MCS of the re-transmitted block(s) is
incremented. Only the blocks successfully acknowledged by the MS are counted
and these blocks are counted only once. Note that RLC blocks containing LLC
Dummy UI Commands only and that have been inserted by RLC to delay the
release of the DL TBF are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1256 / 1392
24.4.4.5.2.21 P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2

Long Name
Definition

encoded in MCS-2.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1257 / 1392
24.4.4.5.2.22 P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3

Long Name
Definition

encoded in MCS-3.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1258 / 1392
24.4.4.5.2.23 P55h - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4

Long Name
Definition

encoded in MCS-4
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1259 / 1392
24.4.4.5.2.24 P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5

Long Name
Definition

encoded in MCS-5.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1260 / 1392
24.4.4.5.2.25 P55j - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6

Long Name
Definition

encoded in MCS-6
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1261 / 1392
24.4.4.5.2.26 P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7

Long Name
Definition

encoded in MCS-7.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1262 / 1392
24.4.4.5.2.27 P55l - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8

Long Name
Definition

encoded in MCS-8.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1263 / 1392
24.4.4.5.2.28 P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9

Long Name
Definition

encoded in MCS-9.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1264 / 1392
24.4.4.5.2.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 blocks

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

PACKET DL ACK/NACK by the number of DL RLC data bytes of the DL 04.60 RLC
DATA BLOCK sent on PDTCH (encoded in CS-x with x = 1 to 4) since the previous
04.60 PACKET DL ACK/NACK that are unacknowledged (NACK status in the RBB
bitmap). In acknowledged mode, the value of the counter is equal to 0. Note that
RLC blocks containing LLC Dummy UI Commands only are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1265 / 1392
24.4.4.5.2.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 blocks

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

EGPRS PACKET DL ACK/NACK by the number of DL RLC data bytes of the DL
04.60 RLC DATA BLOCK sent on PDTCH (encoded in MCS-x with x = 1 to 9) since
the previous 04.60 EGPRS PACKET DL ACK/NACK that are unacknowledged
(NACK status in the RBB bitmap). In acknowledged mode, the value of the counter
is equal to 0. Note that RLC blocks containing LLC Dummy UI Commands only
are not taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
DL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1266 / 1392
24.4.4.6 GPU load

24.4.4.6.1 All GPU load
24.4.4.6.2 N/A
24.4.4.6.2.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) for
each cells mapped on GPU.
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1267 / 1392
24.4.4.6.2.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 is
loaded is computed. The time is provided in seconds with one significant value
after the comma (i.e. ROUND(10x) / 10). Note : A DSP is said loaded when its
CPU load is > =DSP_LOAD_THR1 and < DSP_LOAD_THR2.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1268 / 1392
24.4.4.6.2.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 overload
state.
Trigger Condition
During the granularity period, the cumulated time during which at least a DSP is
overloaded is computed. The time is provided in seconds with one significant
value after the comma (i.e. ROUND(10x) / 10). Note : A DSP is said overloaded
when its CPU load is > =DSP_LOAD_THR2.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1269 / 1392
24.4.4.6.2.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 state
because one of the following conditions is met: i) the maximum number of
GCHs 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
be handled by a DSP is reached (MAX_TRX_DSP value) , iii) the maximum
number of 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 used
within a DSP does not allow to serve new TBF (on this DSP) (current DSP memory
congestion state is different from NO_CONGESTION). The counter is stopped:
when all the DSP have left the congestion state.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1270 / 1392
24.4.4.6.2.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 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1271 / 1392
24.4.4.6.2.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 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1272 / 1392
24.4.4.6.2.7 P392a - AV_NB_MS_CONTEXTS

Long Name
AV_NB_MS_CONTEXTS
Definition
Average number of contexts of MS (in RRM) observed during the granularity

period.
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 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1273 / 1392
24.4.4.6.2.8 P392b - MAX_NB_MS_CONTEXTS

Long Name
MAX_NB_MS_CONTEXTS
Definition
Maximum number of active contexts of MS (in RRM) observed during the

granularity period.
Trigger Condition
Tide mark of counter P392a.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1274 / 1392
24.4.4.6.2.9 P402 - TIME_PMU_OVERLOAD

Long Name
TIME_PMU_OVERLOAD
Definition
Cumulative time during which the GPU stays in the PMU CPU overload state due
to 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 threshold
PMU_CPU_Overload. - Stops when the GPU leaves the PMU CPU overload
state, i.e. when the PMU CPU power budget is below or equal to the threshold
PMU_CPU_Overload
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1275 / 1392
24.4.4.6.2.10 P413 - NB_GPRS_SESSIONS

Long Name
NB_GPRS_SESSIONS
Definition
Number of (E)GPRS sessions. A session corresponds to a mobile station and the

BSS exchanging packet data using downlink TBFs, uplink TBFs or both. There is
always at least one TBF active across the whole duration of a session or T3192 is
running.
Trigger Condition
A (E)GPRS session starts when for one mobile station, there was no on-going
TBF and one TBF is established. It ends when for that mobile station, there was
one (or two) on-going TBF(s) and one (or both) is (are) released and T3192 is
no longer running. During a session, TBFs may be established and released in
both directions provided there is always at least one direction for which there is
an on-going TBF or T3192 is running. The detailed triggers are described below:
1) if an MS has got no TBF established and a DL or UL TBF is established then
the session 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 the
last UL RLC data block is received (and no retransmission is required in RLC
acknowledged mode); 3) in case an MS has got a DL TBF only, the current session
ends when the final (EGPRS) PACKET DOWNLINK ACK/NACK is received and no
retransmission 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) PACKET
DOWNLINK ACK/NACK is received and no retransmission is required in RLC
acknowledged mode, if T3192 is started, the session continues; 5) in case an MS
has 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 TBFs
on-going and one of the TBFs gets released, then the session continues; 7) in case
an MS has got both a DL and an UL TBFs on-going and both TBFs are released
at 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 TBF
established, T3192 is running and reaches its expiry value, the session ends.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1276 / 1392
24.4.4.6.2.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 budget
over the granularity period.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1277 / 1392
24.4.4.6.2.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 granularity
period.
Trigger Condition
Tidemark of the counter P76a.
Sub Domain 1
Radio interface
Sub Domain 2
GPU load
Sub Domain 3
N/A
Measured Object
External Comment
1278 / 1392
24.4.4.7 Link control at RLC layer

24.4.4.7.1 All Link control at RLC layer
24.4.4.7.2 N/A
24.4.4.7.2.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 indications
from the MS).
Sub Domain 1
Radio interface
Sub Domain 2
Link control at RLC layer
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1279 / 1392
24.4.4.7.2.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 indications
from the MS).
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1280 / 1392
24.4.4.7.2.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 GPRS
DL TBF.
Trigger Condition
Whenever the MFS RLC transmit window enters the stall state for a GPRS DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1281 / 1392
24.4.4.7.2.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 an
EGPRS DL TBF.
Trigger Condition
Whenever the MFS RLC transmit window enters the stall state for an EGPRS
DL TBF.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1282 / 1392
24.4.4.7.2.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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1283 / 1392
24.4.4.7.2.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 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1284 / 1392
24.4.4.7.2.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 less

robust coding scheme in the downlink direction for GPRS TBFs.
Trigger Condition
The counter is incremented whenever the RLC layer triggers a change of coding
scheme towards a less robust coding scheme in the downlink direction for a
GPRS TBF. Note 1: This counter is never incremented when the data transfer is
resumed while the DL TBF is in DL TBF delayed. Note 2: This counter does not
apply to EGPRS TBFs.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1285 / 1392
24.4.4.7.2.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 more

robust coding scheme in the downlink direction for GPRS TBFs.
Trigger Condition
scheme towards a more robust coding scheme in the downlink direction (with
the exception below) for a GPRS TBF. Although the coding scheme may be
changed to become more robust, this counter is not incremented in the following
situations: - When entering the delayed DL TBF release state to send Dummy
UI Command, - When ordered by the RRM layer (e.g. in reallocation when old
and new TRX having different radio configuration), - When a consecutive lost of
04.60 PACKET DOWNLINK ACK/NACK messages is detected, - When the data
transfer is resumed while the DL TBF is in DL TBF delayed state. Note: This
counter does not apply to EGPRS TBFs.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1286 / 1392
24.4.4.7.2.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 less

robust coding scheme in the uplink direction for GPRS TBFs.
Trigger Condition
scheme towards a less robust coding scheme in the uplink direction for a GPRS
TBF. Note: This counter does not apply to EGPRS TBFs.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1287 / 1392
24.4.4.7.2.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 more

robust coding scheme in the uplink direction for GPRS TBFs.
Trigger Condition
scheme towards a more robust coding scheme in the uplink direction for a GPRS
TBF. Although the coding scheme may be changed to become more robust, this
counter is not incremented in the following situations: - When ordered by the
RRM layer (e.g. in reallocation when old and new TRX having different radio
configuration), - When the network receives an invalid UL RLC data block or
nothing from the MS a certain number of times. Note: This counter does not
apply to EGPRS TBFs.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1288 / 1392
24.4.4.8 MS capability
24.4.4.8.1 All MS capability
24.4.4.8.2.5 )
24.4.4.8.2 N/A
24.4.4.8.2.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 received
for a given MS context in the GPU and indicates that the MS is compliant to the
3GPP standard Releases 1997 or 1998.
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1289 / 1392
24.4.4.8.2.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 onwards

mobile stations.
Trigger Condition
for a given MS context in the GPU and indicates that the MS is non-EGPRS
capable and compliant to the 3GPP standard Release 1999 onwards.
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1290 / 1392
24.4.4.8.2.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 onwards

mobile stations.
Trigger Condition
for a given MS context in the GPU and indicates that the MS is EGPRS capable
and compliant to the 3GPP standard Release 1999 onwards.
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1291 / 1392
24.4.4.8.2.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 is
received for a given MS context Note : This counter is incremented whatever the
MS release or feature supported by the MS.
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1292 / 1392
24.4.4.8.2.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 is
received for a given MS context and indicates that the MS supports the Geran
feature package 1.
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1293 / 1392
24.4.4.8.2.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 of
multislot classes 0 to 10.
Trigger Condition
The counter is incremented the first time the MS radio access capability is
received for a given MS context and indicates that the MS multislot class belongs
to the set of multislot classes 0 to 10. Note : - In the MS Radio Access Capability
parameter, only the GPRS multislot class, EGPRS multislot class , and High
Multislot Capability fields are taken into account if available. -If several multislot
class are available for the same MS (e-g GPRS MS class, EDGE MS class), then
only one will be taken into consideration to increment the proper counter, based
on 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 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1294 / 1392

Long Name
Definition
Number of MS contexts created for MS whose multislot class belongs to the set
of multislot classes 11 to 12.
Trigger Condition
for a given MS context and indicates that the MS multislot class belongs to the
set of multislot classes 11 to 12. Note : - In the MS Radio Access Capability
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1295 / 1392
24.4.4.8.2.8 P530a_3 - NB_MS_MULTISLOT_CLASS_3X

Long Name
NB_MS_MULTISLOT_CLASS_3X
Definition
multislot classes of type 3X .
Trigger Condition
set of multislot classes of type 3X. Note : - In the MS Radio Access Capability
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1296 / 1392
24.4.4.8.2.9 P530a_4 - NB_MS_MULTISLOT_CLASS_4X

Long Name
NB_MS_MULTISLOT_CLASS_4X
Definition
multislot classes of type 4X .
Trigger Condition
set of multislot classes of type 4X. Note : - In the MS Radio Access Capability
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1297 / 1392

Long Name
Definition
Number of MS contexts created for MS whose (PTM) high multislot class belongs
to 30-34.
Trigger Condition
for a given MS context and indicates that the MS (PTM) high multislot class
belongs to 30-34. Note : - In the MS Radio Access Capability parameter, only the
GPRS multislot class, EGPRS multislot class, and High Multislot Capability fields
are taken into account if available. -If several multislot classes are available for the
same MS, then only one will be taken into consideration to increment the proper
counter, based on 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 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1298 / 1392
24.4.4.8.2.11 P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_34

Long Name
Definition
Number of MS contexts created for MS whose DTM high multislot class belongs
to 31-34.
Trigger Condition
for a given MS context and indicates that the MS DTM high multislot class belongs
to 31-34. Note : - In the MS Radio Access Capability parameter, only the DTM
GPRS high multislot class and DTM EGPRS high multislot class fields are taken
into account if available. -If DTM GPRS and EGPRS high multislot classes are
available for the same MS, then only one will be taken into consideration, based on
the following priorities in decreasing order: 0-> DTM EGPRS high multislot class,
1-> DTM GPRS high multislot class,
Sub Domain 1
Radio interface
Sub Domain 2
MS capability
Sub Domain 3
N/A
Measured Object
External Comment
1299 / 1392
24.4.4.9 PAGCH
24.4.4.9.1 All PAGCH
24.4.4.9.2 N/A
24.4.4.9.2.1 P400 - SIG_BLKS_PAGCH_LOAD
Long Name
SIG_BLKS_PAGCH_LOAD
Definition
Dedicated PAGCH signalling load on all the existing MPDCHs. The dedicated
PAGCH signalling load represents the number of blocks dedicated to Packet Uplink
Assignment and Packet Access Reject messages over the granularity period.
It evaluated as the weighted sum of these messages sent over the granularity
period. A weight of 1 is given to the Packet UL Assignment messages sent on
PAGCH or PPCH. A weight of 0.5 (assuming that 2 access rejects are gathered
in one single block) is given to a Packet Access Reject sent either on PAGCH or
PPCH. Note that the Packet UL Assignment and Packet Access Reject messages
sent on PPCH are counted with P400.
Trigger Condition
The counter is incremented by 1 whenever a Packet UL Assignment is sent on

PAGCH or PPCH. The counter is incremented by 0.5 whenever a Packet Access
reject message is sent on PAGCH or PPCH.
Sub Domain 1
Radio interface
Sub Domain 2
PAGCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1300 / 1392
24.4.4.10 PCH
24.4.4.10.1 All PCH
24.4.4.10.2 N/A
24.4.4.10.2.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 (through

the BSC which manages the PCH resource). This counter gives an indication of
the PCH load used for GPRS.
Trigger Condition
Whenever a (BSCGP) PAGING REQUEST is sent to the MS for PS paging

whatever may be the paging area (RA, LA, ...)
Sub Domain 1
Radio interface
Sub Domain 2
PCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1301 / 1392
24.4.4.10.2.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 (through

the BSC which manages the PCH resource). This counter gives an indication of
the PCH load used for GPRS.
Trigger Condition
Whenever a (BSCGP) PAGING REQUEST is sent to the MS for CS paging

whatever may be the paging area (RA, LA, ...)
Sub Domain 1
Radio interface
Sub Domain 2
PCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1302 / 1392
24.4.4.10.2.3 P53c - NB_IMM_ASS_PCH

Long Name
NB_IMM_ASS_PCH
Definition
Number of (BSCGP) IMMEDIATE ASSIGNMENT sent to the MS (through the

BSC which manages the PCH resource) for a DL TBF establisment when the MS
is in DRX mode.
Trigger Condition
Whenever a (BSCGP) IMMEDIATE_ASSIGNMENT is sent to the MS on PCH.
Sub Domain 1
Radio interface
Sub Domain 2
PCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1303 / 1392
24.4.4.11 PPCH
24.4.4.11.1 All PPCH
24.4.4.11.2 N/A
24.4.4.11.2.1 P61 - SIG_BLKS_PPCH_LOAD
Long Name
SIG_BLKS_PPCH_LOAD
Definition
Dedicated PPCH signalling load on all the existing MPDCHs. The dedicated
PPCH signalling load represents the number of PPCH blocks dedicated to CS/PS
Paging requests and Packet Downlink Assignment messages over the granularity
period. It is evaluated as the weighted sum of these messages sent over the
granularity period. A weight of 0.5 (assuming that 2 paging requests are gathered
in one single block) is given to a CS and PS paging sent on PPCH. A weight of
1 is given to the Packet DL Assignment messages sent on PPCH (in DRX and
non DRX mode). Note that the Packet UL Assignment and Packet Access Reject
messages sent 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 on PPCH.

The counter is incremented by 1 whenever a Packet DL Assignment is sent on
PPCH.
Sub Domain 1
Radio interface
Sub Domain 2
PPCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1304 / 1392
24.4.4.11.2.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 on

PPCH. 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 1
Radio interface
Sub Domain 2
PPCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1305 / 1392
24.4.4.11.2.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 on

PPCH. 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 1
Radio interface
Sub Domain 2
PPCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1306 / 1392
24.4.4.12 PRACH
24.4.4.12.1 All PRACH
24.4.4.12.2 N/A
24.4.4.12.2.1 P399 - SIG_BLKS_PRACH_LOAD
Long Name
SIG_BLKS_PRACH_LOAD
Definition
PRACH signalling load (expressed in blocks) on all the existing MPDCHs. The
PRACH signalling load is the weighted sum of the used PRACH bursts over the
granularity period. A weight of 0.25 (4 bursts per block) is given to a PRACH burst
occurrence carrying a (EGPRS) Packet Channel Request, whereas a weight of
0.5 (1 collision = 2 MS attempts) is given to a PRACH burst occurrence on which a
collision has been detected.
Trigger Condition
The counter is updated whenever RRM receives from MAC the internal primitive
PRH-PRACH-COLLISION-REPORT-cnf indicating the number of PRACH burst
occurrences carrying a (EGPRS) Packet Channel Request message, and the
number of PRACH occurrences on which a collision has been detected. Remark:
The primitive PRH-PRACH-COLLISION-REPORT-cnf is regularly sent by the
PTU (on PMU demand).
Sub Domain 1
Radio interface
Sub Domain 2
PRACH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1307 / 1392
24.4.4.12.2.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 access
without TBF establishment".
Trigger Condition
The counter is incremented whenever the MFS receives a Packet Channel

Request messages with cause "Single block access without TBF establishment".
Sub Domain 1
Radio interface
Sub Domain 2
PRACH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1308 / 1392
24.4.4.13 UL LLC data flow

24.4.4.13.1 All UL LLC data flow
24.4.4.13.2 N/A
24.4.4.13.2.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 (the
MS is obviously in packet transfer mode UL).
Trigger Condition
Whenever an UL LLC PDU is discarded by the SNS sublayer due to congestion

situation on the Frame Relay.
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
PVC
External Comment
1309 / 1392
24.4.4.13.2.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 GPRS

mode and RLC acknowledged mode.
Trigger Condition
Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an UL
TBF established in GPRS mode and RLC acknowledged mode, the counter is
incremented by the number of bytes of the received UL LLC PDU.
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1310 / 1392
24.4.4.13.2.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 GPRS

mode and RLC unacknowledged mode.
Trigger Condition
TBF established in GPRS mode and RLC unacknowledged mode, the counter is
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1311 / 1392
24.4.4.13.2.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 in

EGPRS mode and RLC acknowledged mode.
Trigger Condition
TBF established in EGPRS mode and RLC acknowledged mode, the counter is
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1312 / 1392
24.4.4.13.2.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 in

EGPRS mode and RLC unacknowledged mode.
Trigger Condition
TBF established in EGPRS mode and RLC unacknowledged mode, the counter is
Sub Domain 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1313 / 1392
24.4.4.13.2.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 1
Radio interface
Sub Domain 2
UL LLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1314 / 1392
24.4.4.14 UL PACCH
24.4.4.14.1 All UL PACCH
24.4.4.14.2 N/A
24.4.4.14.2.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 signalling
load counts the number of PACCH/UL blocks used on PCCCHs over the
granularity period. The following messages are taken into account: - Packet
Control Ack reported on UL path sent in answer to Packet DL Assignment sent on
PCCCH; - Packet Resource Request reported on UL path sent in answer to Packet
UL Assignment sent on PCCCH; - Packet Cell Change Failure sent in an UL RLC
control block on PCCCH; - Packet Measurement Report sent in an UL RLC control
block on PCCCH. The messages sent on PACCH/UL of an on-going TBF are not
counted (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 a Packet UL Assignment sent on PCCCH; - a Packet Cell Change Failure or
a Packet Measurement Report message is received in an UL RLC control block
on PCCCH.
Sub Domain 1
Radio interface
Sub Domain 2
UL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1315 / 1392
24.4.4.14.2.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 transfer

mode and used to carry NC2 signalling messages.
Trigger Condition
The counter is incremented whenever the MFS receives an UL RLC control

block on PACCH/U due to the NC2 mode of operation for MS in packet transfer
mode. Therefore, this counter shall count the following uplink messages: - Packet
Measurement Report - Packet Cell Change Failure - Acknowledgement (valid or
not) of a Packet Cell Change Order message.
Sub Domain 1
Radio interface
Sub Domain 2
UL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1316 / 1392
24.4.4.14.2.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 packet

idle mode and used to carry NC2 signalling messages (when no PCCCH is
established in the cell)
Trigger Condition
The counter is incremented whenever the MFS receives a Packet Measurement

Report or a Packet Cell Change Failure message on a non-PCCCH from a MS in
packet idle mode.
Sub Domain 1
Radio interface
Sub Domain 2
UL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1317 / 1392
24.4.4.14.2.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 in

packet idle mode (when no PCCCH is established in the cell).
Trigger Condition
The counter is incremented whenever the MFS receives a Packet Resource

Request message on a slave PDCH (i.e. on a PDCH not carrying any PCCCH)
from a MS in packet idle mode.
Sub Domain 1
Radio interface
Sub Domain 2
UL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1318 / 1392
24.4.4.14.2.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) on
PACCH (RLC/MAC control message in normal burst format) whatever the mode
of the MS is (packet transfer or packet idle mode). On slave PDCHs, the counter
is incremented on receipt of one of the following messages: - a 04.60 PACKET
RESOURCE REQUEST message, - a 04.60 (EGPRS) PACKET DOWNLINK
ACK/NACK message, - a 04.60 PACKET CELL CHANGE FAILURE message, - a
04.60 PACKET MEASUREMENT REPORT message. - a 04.60 PACKET CELL
CHANGE NOTIFICATION message. - a 04.60 PACKET PSI STATUS message. a 04.60 PACKET SI STATUS message. - a 04 60 PACKET MOBILE TBF STATUS
message. On master PDCHs, the counter is incremented on receipt of one of
the following messages: - a 04.60 PACKET RESOURCE REQUEST message,
- a 04.60 PACKET CELL CHANGE FAILURE message, - a 04.60 PACKET
MEASUREMENT REPORT message.
Sub Domain 1
Radio interface
Sub Domain 2
UL PACCH
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1319 / 1392
24.4.4.15 UL RLC data flow

24.4.4.15.1 All UL RLC data flow
)
)
)
)
24.4.4.15.2.5 )
24.4.4.15.2.6 )
24.4.4.15.2.7 )
24.4.4.15.2.8 )
24.4.4.15.2.9 )
24.4.4.15.2.10 )
24.4.4.15.2.11 )
24.4.4.15.2.12 )
24.4.4.15.2.13 )
24.4.4.15.2.20 )
)
24.4.4.15.2.22 )
24.4.4.15.2.23 )
)
1320 / 1392

)
24.4.4.15.2.26 )
)
24.4.4.15.2.28 )
24.4.4.15.2 N/A
24.4.4.15.2.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-1

retransmitted due to unacknowledgement of the MFS.
Trigger Condition
Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in

CS-1 is correctly received by the MFS. In unacknowledged mode, the counter is
equal to 0 (no retransmission). The Packet Uplink Dummy Control Blocks for
Extended UL TBF mode feature shall not be taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1321 / 1392
24.4.4.15.2.2 P21b - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1322 / 1392
24.4.4.15.2.3 P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1323 / 1392
24.4.4.15.2.4 P21d - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1324 / 1392
24.4.4.15.2.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 PDTCH

encoded in MCS-1 retransmitted due to unacknowledgement of the MFS.
Trigger Condition
Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded

in MCS-1 is correctly received by the MFS, the counter is incremented. In
unacknowledged mode, the counter is equal to 0 (no retransmission). The Packet
Uplink Dummy Control Blocks for Extended UL TBF mode feature shall not be
taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1325 / 1392
24.4.4.15.2.6 P21g - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1326 / 1392
24.4.4.15.2.7 P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1327 / 1392
24.4.4.15.2.8 P21i - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1328 / 1392
24.4.4.15.2.9 P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1329 / 1392
24.4.4.15.2.10 P21k - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1330 / 1392
24.4.4.15.2.11 P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1331 / 1392
24.4.4.15.2.12 P21m - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1332 / 1392
24.4.4.15.2.13 P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9

Long Name
Definition

Trigger Condition

taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1333 / 1392
24.4.4.15.2.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 retransmitted

radio blocks are counted.
Trigger Condition
This counter is incremented whenever the MFS receives an UL RLC/MAC data

block on PDTCH. Packet Uplink Dummy Control Blocks shall not be taken into
account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1334 / 1392
24.4.4.15.2.15 P462 - NB_DUMMY_UL_BLOCKS

Long Name
NB_DUMMY_UL_BLOCKS
Definition
Number of Packet Uplink Dummy Control blocks received on the radio interface.
Note: This counter applies to both GPRS and EGPRS TBFs.
Trigger Condition
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1335 / 1392
24.4.4.15.2.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 PDTCH

encoded 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 is

received by the MFS for the first time. Packet Uplink Dummy Control Blocks shall
not be taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1336 / 1392
24.4.4.15.2.17 P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1337 / 1392
24.4.4.15.2.18 P57c - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3

Long Name
Definition

Trigger Condition
Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-3/4 is

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1338 / 1392
24.4.4.15.2.19 P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4

Long Name
Definition

Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1339 / 1392
24.4.4.15.2.20 P57e - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1

Long Name
NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1
Definition

encoded in MCS-1.
Trigger Condition
Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-1 is

received by the MFS for the first time. The retransmitted blocks are not counted.
Packet Uplink Dummy Control Blocks shall not be taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1340 / 1392
24.4.4.15.2.21 P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2

Long Name
Definition

encoded in MCS-2.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1341 / 1392
24.4.4.15.2.22 P57g - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3

Long Name
Definition

encoded in MCS-3.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1342 / 1392
24.4.4.15.2.23 P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4

Long Name
Definition

encoded in MCS-4.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1343 / 1392
24.4.4.15.2.24 P57i - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5

Long Name
Definition

encoded in MCS-5.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1344 / 1392
24.4.4.15.2.25 P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6

Long Name
Definition

encoded in MCS-6.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1345 / 1392
24.4.4.15.2.26 P57k - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7

Long Name
Definition

encoded in MCS-7.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1346 / 1392
24.4.4.15.2.27 P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8

Long Name
Definition

encoded in MCS-8.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1347 / 1392
24.4.4.15.2.28 P57m - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9

Long Name
Definition

encoded in MCS-9.
Trigger Condition

Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1348 / 1392
24.4.4.15.2.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 encoded

in CS-x (with x = 1 to 4) lost.
Trigger Condition
In unacknowledged mode, whenever a UL 04.60 RLC DATA BLOCK on PDTCH

encoded in CS-x (with x = 1 to 4) is not received (the awaited block defined to the
MS by the USF is not received), the counter is incremented by the DL RLC data
bytes expected in the UL RLC data block. In acknowledged mode, the value of the
counter is equal to 0. Lost RLC data block corresponding to the USFs scheduled
during the UL extension phase shall not be taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1349 / 1392
24.4.4.15.2.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 in

MCS-x (with x = 1 to 9) lost.
Trigger Condition
In unacknowledged mode, whenever a UL 04.60 RLC DATA BLOCK on PDTCH

encoded in MCS-x (with x = 1 to 9) is not received (the awaited block defined to the
MS by the USF is not received), the counter is incremented by the DL RLC data
bytes expected in the UL RLC data block. In acknowledged mode, the value of the
counter is equal to 0. Lost RLC data block corresponding to the USFs scheduled
during the UL extension phase shall not be taken into account.
Sub Domain 1
Radio interface
Sub Domain 2
UL RLC data flow
Sub Domain 3
N/A
Measured Object
Cell
External Comment
1350 / 1392
25 MFS-LCS Counters
25 MFS-LCS Counters
1351 / 1392
25 MFS-LCS Counters
25.1 All MFS-LCS

P800 - NB_LOC_REQ (Section 25.2.2.3.2.1 )
P801 - NB_ASSIST_DATA_REQ (Section 25.2.2.2.2.1 )
P802 - NB_ASSIST_DATA_SUCC (Section 25.2.2.2.2.2 )
P803 - NB_LOC_TA_SUCC (Section 25.2.2.3.2.2 )
P804 - NB_LOC_CONV_GPS_SUCC (Section 25.2.2.3.2.3 )
P805 - NB_LOC_MA_AGPS_SUCC (Section 25.2.2.3.2.4 )
P806 - NB_LOC_MB_AGPS_SUCC (Section 25.2.2.3.2.5 )
P807 - NB_LOC_TA_PCF_REQ (Section 25.2.2.5.2.1 )
P808 - NB_LOC_TA_PCF_SUCC (Section 25.2.2.5.2.2 )
P809 - NB_LOC_CONV_GPS_PCF_REQ (Section 25.2.2.5.2.3 )
P810 - NB_LOC_MA_AGPS_PCF_REQ (Section 25.2.2.5.2.4 )
P811 - NB_LOC_MA_AGPS_PCF_SUCC (Section 25.2.2.5.2.5 )
P812 - NB_LOC_MB_AGPS_PCF_REQ (Section 25.2.2.5.2.6 )
P813 - NB_LOC_MB_AGPS_PCF_SUCC (Section 25.2.2.5.2.7 )
P814 - NB_LCS_PROTOCOL_ERROR (Section 25.2.2.4.2.1 )
P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO (Section 25.2.2.4.2.2 )
P816 - NB_LCS_INTERRUPTED_INTER_BSC_HO (Section 25.2.2.4.2.3 )
P817 - NB_LCS_FAILURE_RRLP (Section 25.2.2.4.2.4 )
P818 - NB_LCS_FAILURE_TIMER_EXPIRY (Section 25.2.2.4.2.5 )
P819 - NB_LCS_FAILURE_INTERNAL (Section 25.2.2.4.2.6 )
P820 - NB_UNKNOWN_LCS_REQ (Section 25.2.2.4.2.7 )
P821 - NB_LOC_CONV_GPS_PCF_SUCC (Section 25.2.2.5.2.8 )
P822 - AV_TA_LAT (Section 25.3.2.2.5.1 )
P823 - AV_TA_LONG (Section 25.3.2.2.5.2 )
P824 - AV_CONV_GPS_LAT (Section 25.3.2.2.2.1 )
P825 - AV_CONV_GPS_LONG (Section 25.3.2.2.2.2 )
P826 - AV_MA_AGPS_LAT (Section 25.3.2.2.3.1 )
P827 - AV_MA_AGPS_LONG (Section 25.3.2.2.3.2 )
P828 - AV_MB_AGPS_LAT (Section 25.3.2.2.4.1 )
P829 - AV_MB_AGPS_LONG (Section 25.3.2.2.4.2 )
P830 - ST_DEV_TA_LAT (Section 25.3.2.2.5.3 )
P831 - ST_DEV_TA_LONG (Section 25.3.2.2.5.4 )
P832 - ST_DEV_CONV_GPS_LAT (Section 25.3.2.2.2.3 )
P833 - ST_DEV_CONV_GPS_LONG (Section 25.3.2.2.2.4 )
P834 - ST_DEV_MA_AGPS_LAT (Section 25.3.2.2.3.3 )
P835 - ST_DEV_MA_AGPS_LONG (Section 25.3.2.2.3.4 )
P836 - ST_DEV_MB_AGPS_LAT (Section 25.3.2.2.4.3 )
1352 / 1392
25 MFS-LCS Counters
P837 - ST_DEV_MB_AGPS_LONG (Section 25.3.2.2.4.4 )
25.2 Quality of service

25.2.1 All Quality of service

1353 / 1392
25 MFS-LCS Counters

25.2.2.2 Assistance data for MS

25.2.2.2.1 All Assistance data for MS
25.2.2.2.2 N/A
25.2.2.2.2.1 P801 - NB_ASSIST_DATA_REQ
Long Name
NB_ASSIST_DATA_REQ
Definition
Number of received LCS requests for GPS assistance data (initially requested by
the MS) received from the BSC.
Trigger Condition
Incremented each times the SMLC receives a BSCLP PERFORM LOCATION

REQUEST from the BSC with MIE Location Type set to "location assistance
information for the target MS" and CIE "GPS Assistance Data" is present.
Sub Domain 1
Radio interface
Sub Domain 2
Assistance data for MS
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1354 / 1392
25 MFS-LCS Counters
25.2.2.2.2.2 P802 - NB_ASSIST_DATA_SUCC

Long Name
NB_ASSIST_DATA_SUCC
Definition
Number of successful GPS assistance data delivery (initially requested by the

MS) responses sent to the BSC.
Trigger Condition
Incremented each times the SMLC sends a BSCLP PERFORM LOCATION

RESPONSE to the BSC without containing neither the OIE Location estimate nor
the OIE LCS cause (response in case of successful assistance data delivery).
Sub Domain 1
Radio interface
Sub Domain 2
Assistance data for MS
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1355 / 1392
25 MFS-LCS Counters
25.2.2.3 Location estimate

25.2.2.3.1 All Location estimate
25.2.2.3.2 N/A
25.2.2.3.2.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 LOCATION

REQUEST from BSC with MIE Location Type set to "current geographic location"
Sub Domain 1
Radio interface
Sub Domain 2
Location estimate
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1356 / 1392
25 MFS-LCS Counters
25.2.2.3.2.2 P803 - NB_LOC_TA_SUCC

Long Name
NB_LOC_TA_SUCC
Definition
Number of successful location responses sent to the BSC using TA positioning

method.
Trigger Condition
Incremented each times the SMLC sends to the BSC a BSCLP PERFORM
LOCATION RESPONSE message with the OIE Location Estimate and the OIE
Positioning Data containing field Positioning Method set to "Timing Advance", and
the associated field "usage" set to "Results used to generate location".
Sub Domain 1
Radio interface
Sub Domain 2
Location estimate
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1357 / 1392
25 MFS-LCS Counters
25.2.2.3.2.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 Conventional

GPS positioning method.
Trigger Condition
Positioning Data containing field Positioning Method set to "Conventional GPS",
and the associated field "usage" set to "Results used to generate location".
Sub Domain 1
Radio interface
Sub Domain 2
Location estimate
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1358 / 1392
25 MFS-LCS Counters
25.2.2.3.2.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 Assisted

A-GPS positioning method.
Trigger Condition
Positioning Data containing field Positioning Method set to "Mobile assisted GPS",
and the associated field "usage" set to "Results used to generate location".
Sub Domain 1
Radio interface
Sub Domain 2
Location estimate
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1359 / 1392
25 MFS-LCS Counters
25.2.2.3.2.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-GPS
positioning method.
Trigger Condition
Positioning Data containing field Positioning Method set to "Mobile based GPS",
and the associated field "usage" set to "results used to generate location".
Sub Domain 1
Radio interface
Sub Domain 2
Location estimate
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1360 / 1392
25 MFS-LCS Counters
25.2.2.4 Location estimate / Assistance data for MS

25.2.2.4.1 All Location estimate / Assistance data for MS
25.2.2.4.2 N/A
25.2.2.4.2.1 P814 - NB_LCS_PROTOCOL_ERROR
Long Name
NB_LCS_PROTOCOL_ERROR
Definition
Number of failed LCS procedures (considering LCS requests for MS positioning

and LCS requests for GPS assistance data) due to LCS protocol error.
Trigger Condition
Incremented whenever the SMLC sends to the BSC a BSCLP PERFORM

LOCATION 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 1
Radio interface
Sub Domain 2
Location estimate / Assistance data for MS
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1361 / 1392
25 MFS-LCS Counters
25.2.2.4.2.2 P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO

Long Name
NB_LCS_INTERRUPTED_INTRA_BSC_HO
Definition

and LCS requests for GPS assistance data) due to intra-BSC handover.
Trigger Condition
Incremented whenever the SMLC receives a BSCLP

PERFORM_LOCATION_ABORT with cause "Intra-BSC hand-over complete"
or when it receives either a BSCLP COI RESET or a BSCLP COI ABORT
with cause "intra-BSS hand-over".
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1362 / 1392
25 MFS-LCS Counters
25.2.2.4.2.3 P816 - NB_LCS_INTERRUPTED_INTER_BSC_HO

Long Name
NB_LCS_INTERRUPTED_INTER_BSC_HO
Definition

and LCS requests for GPS assistance data) due to inter-BSC hand-over.
Trigger Condition
Incremented whenever the SMLC receives a BSCLP

PERFORM_LOCATION_ABORT with cause "Inter-BSC hand-over on-going" or
when it receives a BSCLP COI ABORT with cause "inter-BSS hand-over".
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1363 / 1392
25 MFS-LCS Counters
25.2.2.4.2.4 P817 - NB_LCS_FAILURE_RRLP

Long Name
NB_LCS_FAILURE_RRLP
Definition

and 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 not
complete/understandable.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1364 / 1392
25 MFS-LCS Counters
25.2.2.4.2.5 P818 - NB_LCS_FAILURE_TIMER_EXPIRY

Long Name
NB_LCS_FAILURE_TIMER_EXPIRY
Definition

and 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 process
expires in the SMLC (Timer currently defined are: T_LCS_LowDelay,
T_LCS_DelayTolerent, T_RRLP_LowDelay, T_RRLP_DelayTolerent)
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1365 / 1392
25 MFS-LCS Counters
25.2.2.4.2.6 P819 - NB_LCS_FAILURE_INTERNAL

Long Name
NB_LCS_FAILURE_INTERNAL
Definition

and LCS requests for GPS assistance data) due internal problem detected by the
MFS/SMLC.
Trigger Condition
Incremented each times PRCF or PCF returns an error which is not linked to timer
expiry or to BSCLP/RRLP protocol error. and/or Incremented whenever the SMLC
sends to the BSC a BSCLP PERFORM LOCATION RESPONSE with LCS cause
IE set to: - System Failure - Congestion
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1366 / 1392
25 MFS-LCS Counters
25.2.2.4.2.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 LOCATION

REQUEST from BSC: - with MIE Location Type neither set to "Current geographic
location", nor to "Location assistance information for the target MS" - or with MIE
Location Type set to "Location assistance information for the target MS" but CIE
"GPS Assistance Data" is not present.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1367 / 1392
25 MFS-LCS Counters
25.2.2.5 Positioning method

25.2.2.5.1 All Positioning method
25.2.2.5.2 N/A
25.2.2.5.2.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 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1368 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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 estimation

without error indications.
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1369 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1370 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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
"MS assisted GPS".
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1371 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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-GPS

PCF.
Trigger Condition
Incremented each times the PCF "MS-assisted A-GPS" returns a position estimate
without error indications.
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1372 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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
"MS-based A-GPS".
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1373 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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 estimate

with no error indication.
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1374 / 1392
25 MFS-LCS Counters
25.2.2.5.2.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 GPS

PCF.
Trigger Condition
Incremented each times "Conventional GPS" PCF returns a position estimation

without error indication.
Sub Domain 1
Radio interface
Sub Domain 2
Positioning method
Sub Domain 3
N/A
Measured Object
LcsCell
External Comment
1375 / 1392
25 MFS-LCS Counters
25.3 Traffic load

25.3.1 All Traffic load

1376 / 1392
25 MFS-LCS Counters
25.3.2.2 Positioning statistics

25.3.2.2.1 All Positioning statistics
25.3.2.2.2 Conventional GPS

25.3.2.2.2.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 PCF
as well as the number of latitude measurements obtained with Conventional GPS
PCF. Whenever Conventional GPS PCF algorithm returns a positioning estimation
without error indications, - the sum is incremented by the latitude of the mobile
station. - the number of latitude measurements is incremented by one. At the
expiry of the reporting period, the MFS computes the average by dividing the
obtained sum by the obtained number of measurements.
Sub Domain 1
Radio interface
Sub Domain 2
Positioning statistics
Sub Domain 3
Conventional GPS
Measured Object
LcsCell
External Comment
1377 / 1392
25 MFS-LCS Counters
25.3.2.2.2.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 PCF
as well as the number of longitude measurements obtained with Conventional
GPS PCF. Whenever Conventional GPS PCF algorithm returns a positioning
estimation without error indications, - the sum is incremented by the longitude of
the mobile station. - the number of longitude measurements is incremented by
one. At the expiry of the reporting period, the MFS computes the average by
dividing the obtained sum by the obtained number of measurements.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
Conventional GPS
Measured Object
LcsCell
External Comment
1378 / 1392
25 MFS-LCS Counters
25.3.2.2.2.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 Conventional
GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared latitudes obtained with

Conventional GPS PCF, - a second sum S2 of latitudes obtained with Conventional
GPS PCF, - the number N of latitude measurements obtained with Conventional
GPS PCF. Whenever Conventional GPS PCF algorithm returns a positioning
estimation without error indications, - the first sum S1 is incremented by the
squared latitude of the mobile station, - the second sum S2 is incremented by
the latitude of the mobile station, - the number N of latitude measurements is
incremented by one. At the expiry of the reporting period, the MFS computes
the standard deviation as follows: Standard_Deviation = Square_Root(Variance)
where Variance = S1/N - (S2/N)^2.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
Conventional GPS
Measured Object
LcsCell
External Comment
1379 / 1392
25 MFS-LCS Counters
25.3.2.2.2.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 with

Conventional GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared longitudes obtained with

Conventional GPS PCF, - a second sum S2 of longitudes obtained with
Conventional GPS PCF, - the number N of longitude measurements obtained with
Conventional GPS PCF. Whenever Conventional GPS PCF algorithm returns a
positioning estimation without error indications, - the first sum S1 is incremented
by the squared longitude of the mobile station, - the second sum S2 is incremented
by the longitude of the mobile station, - the number N of longitude measurements
is incremented by one. At the expiry of the reporting period, the MFS computes
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
Conventional GPS
Measured Object
LcsCell
External Comment
1380 / 1392
25 MFS-LCS Counters
25.3.2.2.3 MS assisted A-GPS

25.3.2.2.3.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-GPS
PCF as well as the number of latitude measurements obtained with MS Assisted
A-GPS PCF. Whenever MS Assisted A-GPS PCF algorithm returns a positioning
estimation without error indications, - the sum is incremented by the latitude of the
mobile station. - the number of latitude measurements is incremented by one. At
the expiry of the reporting period, the MFS computes the average by dividing the
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS assisted A-GPS
Measured Object
LcsCell
External Comment
1381 / 1392
25 MFS-LCS Counters
25.3.2.2.3.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-GPS
PCF as well as the number of longitude measurements obtained with MS Assisted
estimation without error indications, - the sum is incremented by the longitude of
the mobile station. - the number of longitude measurements is incremented by
one. At the expiry of the reporting period, the MFS computes the average by
dividing the obtained sum by the obtained number of measurements.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS assisted A-GPS
Measured Object
LcsCell
External Comment
1382 / 1392
25 MFS-LCS Counters
25.3.2.2.3.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 Assisted
A-GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared latitudes obtained with MS

Assisted A-GPS PCF, - a second sum S2 of latitudes obtained with MS Assisted
A-GPS PCF, - the number N of latitude measurements obtained with MS Assisted
squared latitude of the mobile station, - the second sum S2 is incremented by
the latitude of the mobile station, - the number N of latitude measurements is
incremented by one. At the expiry of the reporting period, the MFS computes
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS assisted A-GPS
Measured Object
LcsCell
External Comment
1383 / 1392
25 MFS-LCS Counters
25.3.2.2.3.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 MS

Assisted A-GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared longitudes obtained with MS

Assisted A-GPS PCF, - a second sum S2 of longitudes obtained with MS Assisted
A-GPS PCF, - the number N of longitude measurements obtained with MS
Assisted A-GPS PCF. Whenever MS Assisted A-GPS PCF algorithm returns a
positioning estimation without error indications, - the first sum S1 is incremented
by the squared longitude of the mobile station, - the second sum S2 is incremented
by the longitude of the mobile station, - the number N of longitude measurements
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS assisted A-GPS
Measured Object
LcsCell
External Comment
1384 / 1392
25 MFS-LCS Counters
25.3.2.2.4 MS based A-GPS

25.3.2.2.4.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 PCF
as well as the number of latitude measurements obtained with MS Based A-GPS
PCF. Whenever MS Based A-GPS PCF algorithm returns a positioning estimation
without error indications, - the sum is incremented by the latitude of the mobile
station. - the number of latitude measurements is incremented by one. At the
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS based A-GPS
Measured Object
LcsCell
External Comment
1385 / 1392
25 MFS-LCS Counters
25.3.2.2.4.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 PCF
as well as the number of longitude measurements obtained with MS Based A-GPS
without error indications, - the sum is incremented by the longitude of the mobile
station. - the number of longitude measurements is incremented by one. At the
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS based A-GPS
Measured Object
LcsCell
External Comment
1386 / 1392
25 MFS-LCS Counters
25.3.2.2.4.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 Based
A-GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared latitudes obtained with MS Based
A-GPS PCF, - a second sum S2 of latitudes obtained with MS Based A-GPS
PCF, - the number N of latitude measurements obtained with MS Based A-GPS
without error indications, - the first sum S1 is incremented by the squared latitude
of the mobile station, - the second sum S2 is incremented by the latitude of the
mobile station, - the number N of latitude measurements is incremented by one.
At the expiry of the reporting period, the MFS computes the standard deviation as
follows: Standard_Deviation = Square_Root(Variance) where Variance = S1/N (S2/N)^2. At the expiry of the reporting period, the MFS computes the variance
by dividing the obtained sum by the obtained number of measurements. The
standard deviation is obtained by computing the square root of the variance.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS based A-GPS
Measured Object
LcsCell
External Comment
1387 / 1392
25 MFS-LCS Counters
25.3.2.2.4.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 Based
A-GPS PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared longitudes obtained with MS

Based A-GPS PCF, - a second sum S2 of longitudes obtained with MS Based
A-GPS PCF, - the number N of longitude measurements obtained with MS Based
A-GPS PCF. Whenever MS Based A-GPS PCF algorithm returns a positioning
squared longitude of the mobile station, - the second sum S2 is incremented by
the longitude of the mobile station, - the number N of longitude measurements
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
MS based A-GPS
Measured Object
LcsCell
External Comment
1388 / 1392
25 MFS-LCS Counters
25.3.2.2.5 TA positioning
25.3.2.2.5.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 as
well as the number of latitude measurements obtained with TA positioning PCF.
Whenever "CI+TA" PCF algorithm returns a positioning estimation without error
indications, - the sum is incremented by the latitude of the mobile station. - the
number of latitude measurements is incremented by one. At the expiry of the
reporting period, the MFS computes the average by dividing the obtained sum by
the obtained number of measurements.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
TA positioning
Measured Object
LcsCell
External Comment
1389 / 1392
25 MFS-LCS Counters
25.3.2.2.5.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 as
well as the number of longitude measurements obtained with TA positioning PCF.
indications, - the sum is incremented by the longitude of the mobile station. - the
number of longitude measurements is incremented by one. At the expiry of the
reporting period, the MFS computes the average by dividing the obtained sum by
the obtained number of measurements.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
TA positioning
Measured Object
LcsCell
External Comment
1390 / 1392
25 MFS-LCS Counters
25.3.2.2.5.3 P830 - ST_DEV_TA_LAT

Long Name
ST_DEV_TA_LAT
Definition
Standard deviation of the latitude of the mobile stations obtained with TA

positioning PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared latitudes obtained with TA

positioning PCF, - a second sum S2 of latitudes obtained with TA positioning PCF,
- the number N of latitude measurements obtained with TA positioning PCF.
indications, - the first sum S1 is incremented by the squared latitude of the mobile
station, - the second sum S2 is incremented by the latitude of the mobile station,
- the number N of latitude measurements is incremented by one. At the expiry
of the reporting period, the MFS computes the standard deviation as follows:
Standard_Deviation = Square_Root(Variance) where Variance = S1/N (S2/N)^2.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
TA positioning
Measured Object
LcsCell
External Comment
1391 / 1392
25 MFS-LCS Counters
25.3.2.2.5.4 P831 - ST_DEV_TA_LONG

Long Name
ST_DEV_TA_LONG
Definition
Standard deviation of the longitude of the mobile stations obtained with TA

positioning PCF
Trigger Condition
The MFS maintains: - a first sum S1 of squared longitudes obtained with TA

positioning PCF, - a second sum S2 of longitudes obtained with TA positioning
PCF, - the number N of longitude measurements obtained with TA positioning
PCF. Whenever "CI+TA" PCF algorithm returns a positioning estimation without
error indications, - the first sum S1 is incremented by the squared longitude of the
mobile station, - the second sum S2 is incremented by the longitude of the mobile
station, - the number N of longitude measurements is incremented by one. At the
expiry of the reporting period, the MFS computes the standard deviation as follows:
Standard_Deviation = Square_Root(Variance) where Variance = S1/N - (S2/N)^2.
Sub Domain 1
Radio interface
Sub Domain 2
Sub Domain 3
TA positioning
Measured Object
LcsCell
External Comment
1392 / 1392

B10 PM Counter Ed9 PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

B10 PM Counter Ed9 PDF

Caricato da

Copyright:

Formati disponibili

Alcatel-Lucent GSM

3BK 21255 AAAA PCZZA Ed.09

BLANK PAGE BREAK

3BK 21255 AAAA PCZZA Ed.09

BSC-TYPE 1 - Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3BK 21255 AAAA PCZZA Ed.09

3BK 21255 AAAA PCZZA Ed.09

Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353

3BK 21255 AAAA PCZZA Ed.09

3BK 21255 AAAA PCZZA Ed.09

The PM Counters include description of:

3BK 21255 AAAA PCZZA Ed.09

This manual is designed for Operations & Maintenance Center-Radio (OMC-R)

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1 BSC-TYPE 1 - Traffic measurements

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1.1 All TYPE 1

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL (Section 1.3.6.5.2.2

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercell

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1.3 Quality of Service

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

C713 - NB_TCH_OUT_HO_FAIL_REV_TRX (Section 1.3.4.3.2.4 )

1.3.2 Directed Retry

Number of incoming directed retry (towards a TCH channel in HR or FR usage)

Whenever a 44.018 HANDOVER COMPLETE message is received on Abis

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1.3.3 Established Phase

MC137=C137, Number of SDCCH drops in SDCCH established phase due to

1) LapD failure detected during the stable phase of an SDCCH transaction. 2)

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1.3.3.2.2.2 C138 - NB_SDCCH_DROP_EST_PHAS_RLF

1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

Number of TCH (in HR or FR usage) drops in TCH established phase due to

1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements

1.3.3.3.2.2 C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF

Number of TCH (in HR or FR usage) drops in TCH DTAP established phase

1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a

Set of counters related to the traffic evaluation per telecom procedures

3BK 21255 AAAA PCZZA Ed.09

1 BSC-TYPE 1 - Traffic measurements